Mitsubishi Electric MELSEC iQ-R C R12CCPU-V User Manual

Download

Page 1

MELSEC iQ-R C Controller Module User's Manual (Application)

-R12CCPU-V

Page 2

Page 3

SAFETY PRECAUTIONS

WARNING

Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.

CAUTION

Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.

(Read these precautions before using this product.) Before using this product, please read this manual and the relevant manuals carefully, and pay full attention to safety to handle the product correctly. In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious consequences. Observe the precautions of both levels because they are important for personal and system safety. Make sure that the end users read this manual and then keep the manual in a safe place for future reference.

[Considerations for using this manual]

● Replace the terms used in the following pages in this manual with the terms shown on the right, respectively. Corresponding page: SAFETY PRECAUTIONS, CONDITIONS OF USE FOR THE PRODUCT, and

COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES (1) "Programmable controller" → "C Controller module" (2) "Programmable controller system" → "C Controller system"

● For details on a fail-safe circuit for a C Controller system, refer to the following section.

Page 245 General Safety Requirements

Page 4

[Design Precautions]

WARNING

● Configure safety circuits external to the programmable controller to ensure that the entire system operates safely even when a fault occurs in the external power supply or the programmable controller. Failure to do so may result in an accident due to an incorrect output or malfunction. (1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting

operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured external to the programmable controller.

(2) When the programmable controller detects an abnormal condition, it stops the operation and all

outputs are:

• Turned OFF if the overcurrent or overvoltage protection of the power supply module is activated.

• Held or turned OFF according to the parameter setting if the self-diagnostic function of the CPU module detects an error such as a watchdog timer error.

(3) All outputs may be turned on if an error occurs in a part, such as an I/O control part, where the

CPU module cannot detect any error. To ensure safety operation in such a case, provide a safety mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit example, refer to "General Safety Requirements" in MELSEC iQ-R Module Configuration Manual.

(4) Outputs may remain ON or OFF due to a failure of a component such as a relay and transistor in

an output circuit. Configure an external circuit for monitoring output signals that could cause a serious accident.

● In an output circuit, when a load current exceeding the rated current or an overcurrent caused by a load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an external safety circuit, such as a fuse.

● Configure a circuit so that the programmable controller is turned on first and then the external power supply. If the external power supply is turned on first, an accident may occur due to an incorrect output or malfunction.

● For the operating status of each station after a communication failure, refer to manuals relevant to the network. Incorrect output or malfunction due to a communication failure may result in an accident.

● When connecting an external device with a CPU module or intelligent function module to modify data of a running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other forms of control (such as program modification, parameter change, forced output, or operating status change) of a running programmable controller, read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper operation may damage machines or cause accidents.

● Especially, when a remote programmable controller is controlled by an external device, immediate action cannot be taken if a problem occurs in the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.

Page 5

[Design Precautions]

WARNING

● Do not write any data to the "system area" and "write-protect area" of the buffer memory in the module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to each module. Doing so may cause malfunction of the programmable controller system. For the "system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the module used.

● If a communication cable is disconnected, the network may be unstable, resulting in a communication failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire system will always operate safely even if communications fail. Incorrect output or malfunction due to a communication failure may result in an accident.

● To maintain the safety of the programmable controller system against unauthorized access from external devices via the network, take appropriate measures. To maintain the safety against unauthorized access via the Internet, take measures such as installing a firewall.

[Precautions for using C Controller modules]

● In refresh parameter settings, 'Y' cannot be specified for a link output (LY) refresh device or a remote output (RY) refresh device. Therefore, a C Controller module holds the device status as is even after the module status is changed to STOP.

Page 6

[Design Precautions]

CAUTION

● Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction due to noise.

● During control of an inductive load such as a lamp, heater, or solenoid valve, a large current (approximately ten times greater than normal) may flow when the output is turned OFF and ON. Therefore, use a module that has a sufficient current rating.

● After the power is turned OFF and ON or the CPU module is reset, the time taken to enter the RUN status varies depending on the system configuration, parameter settings, and/or program size. Design circuits so that the entire system will always operate safely, regardless of the time.

● Do not turn the power OFF or reset the CPU module while the settings are being written. Doing so will make the data in the flash ROM undefined. The values need to be set in the buffer memory and written to the flash ROM again. Doing so may cause malfunction or failure of the module.

● When changing the operating status of the CPU module from external devices (such as remote RUN/ STOP functions), select "Do Not Open in Program" for "Open Method Setting" in the module parameters. If "Open in Program" is selected, an execution of remote STOP causes the communication line to close. Consequently, the CPU module cannot reopen the communication line, and the external device cannot execute the remote RUN.

Page 7

[Installation Precautions]

WARNING

● Shut off the external power supply (all phases) used in the system before mounting or removing the module. Failure to do so may result in electric shock or cause the module to fail or malfunction.

[Precautions for using C Controller modules]

● When mounting a C Controller module, make sure to attach the connector cover included in a base unit to the module connector of the second slot to prevent entrance of foreign material such as dust.

[Installation Precautions]

CAUTION

● Use the programmable controller in an environment that meets general specifications written in Safety Guidelines included in the base unit. Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the product.

● To mount a module, place the concave part(s) located at the bottom onto the guide(s) of the base unit, and push in the module until the hook(s) located at the top snaps into place. Incorrect interconnection may cause malfunction, failure, or drop of the module.

● Secure the module with screws especially when it is used in an environment where constant vibrations may occur.

● Tighten the screws within the specified torque range. Undertightening can cause drop of the screw, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

● When using an extension cable, connect it to the extension cable connector of the base unit securely. Check the connection for looseness. Poor contact may cause malfunction.

● When using an SD memory card, fully insert it into the memory card slot. Check that it is inserted completely. Poor contact may cause malfunction.

● Securely insert an extended SRAM cassette into the cassette connector of a CPU module. After insertion, close the cassette cover and check that the cassette is inserted completely. Poor contact may cause malfunction.

● Do not directly touch any conductive parts and electronic components of the module, SD memory card, extended SRAM cassette, or connector. Doing so may cause malfunction or failure of the module.

[Wiring Precautions]

WARNING

● Shut off the external power supply (all phases) used in the system before installation and wiring. Failure to do so may result in electric shock or cause the module to fail or malfunction.

● After installation and wiring, attach the included terminal cover to the module before turning it on for operation. Failure to do so may result in electric shock.

Page 8

[Wiring Precautions]

CAUTION

● Individually ground the FG and LG terminals of the programmable controller with a ground resistance of 100 ohms or less. Failure to do so may result in electric shock or malfunction.

● Use applicable solderless terminals and tighten them within the specified torque range. If any spade solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting in failure.

● Check the rated voltage and signal layout before wiring to the module, and connect the cables correctly. Connecting a power supply with a different voltage rating or incorrect wiring may cause fire or failure.

● Connectors for external devices must be crimped or pressed with the tool specified by the manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit, fire, or malfunction.

● Securely connect the connector to the module. Poor contact may cause malfunction.

● Do not install the control lines or communication cables together with the main circuit lines or power

cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction due to noise.

● Place the cables in a duct or clamp them. If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or cables or malfunction due to poor contact. Do not clamp the extension cables with the jacket stripped. Doing so may change the characteristics of the cables, resulting in malfunction.

● Check the interface type and correctly connect the cable. Incorrect wiring (connecting the cable to an incorrect interface) may cause failure of the module and external device.

● Tighten the terminal screws or connector screws within the specified torque range. Undertightening can cause drop of the screw, short circuit, fire, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, fire, or malfunction.

● When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable with connector, hold the connector part of the cable. For the cable connected to the terminal block, loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or damage to the module or cable.

● Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can cause a fire, failure, or malfunction.

● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips, from entering the module during wiring. Do not remove the film during wiring. Remove it for heat dissipation before system operation.

Page 9

[Wiring Precautions]

CAUTION

● Programmable controllers must be installed in control panels. Connect the main power supply to the power supply module in the control panel through a relay terminal block. Wiring and replacement of a power supply module must be performed by qualified maintenance personnel with knowledge of protection against electric shock. For wiring, refer to MELSEC iQ-R Module Configuration Manual.

● For Ethernet cables to be used in the system, select the ones that meet the specifications in the user's manual for the module used. If not, normal data transmission is not guaranteed.

[Startup and Maintenance Precautions]

WARNING

● Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.

● Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or

throw the battery into the fire. Also, do not expose it to liquid or strong shock. Doing so will cause the battery to produce heat, explode, ignite, or leak, resulting in injury or fire.

● Shut off the external power supply (all phases) used in the system before cleaning the module or retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may result in electric shock.

Page 10

[Startup and Maintenance Precautions]

CAUTION

● Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.

● Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone

System) more than 25cm away in all directions from the programmable controller. Failure to do so may cause malfunction.

● Shut off the external power supply (all phases) used in the system before mounting or removing the module. Failure to do so may cause the module to fail or malfunction.

● Tighten the screws within the specified torque range. Undertightening can cause drop of the component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.

● After the first use of the product, do not mount/remove the module to/from the base unit, and the terminal block to/from the module, and do not insert/remove the extended SRAM cassette to/from the CPU module more than 50 times (IEC 61131-2 compliant) respectively. Exceeding the limit may cause malfunction.

● After the first use of the product, do not insert/remove the SD memory card to/from the CPU module more than 500 times. Exceeding the limit may cause malfunction.

● Do not touch the metal terminals on the back side of the SD memory card. Doing so may cause malfunction or failure of the module.

● Do not touch the integrated circuits on the circuit board of an extended SRAM cassette. Doing so may cause malfunction or failure of the module.

● Do not drop or apply shock to the battery to be installed in the module. Doing so may damage the battery, causing the battery fluid to leak inside the battery. If the battery is dropped or any shock is applied to it, dispose of it without using.

● Startup and maintenance of a control panel must be performed by qualified maintenance personnel with knowledge of protection against electric shock. Lock the control panel so that only qualified maintenance personnel can operate it.

Page 11

[Startup and Maintenance Precautions]

CAUTION

● Before handling the module, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the module to fail or malfunction.

[Operation Precautions]

CAUTION

● When changing data and operating status, and modifying program of the running programmable controller from an external device such as a personal computer connected to an intelligent function module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or modification may cause system malfunction, damage to the machines, or accidents.

● Do not turn the power OFF or reset the CPU module while the setting values in the buffer memory are being written to the flash ROM in the module. Doing so will make the data in the flash ROM undefined. The values need to be set in the buffer memory and written to the flash ROM again. Doing so can cause malfunction or failure of the module.

[Disposal Precautions]

CAUTION

● When disposing of this product, treat it as industrial waste.

● When disposing of batteries, separate them from other wastes according to the local regulations. For

details on battery regulations in EU member states, refer to MELSEC iQ-R Module Configuration Manual.

[Transportation Precautions]

CAUTION

● When transporting lithium batteries, follow the transportation regulations. For details on the regulated models, refer to MELSEC iQ-R Module Configuration Manual.

● The halogens (such as fluorine, chlorine, bromine, and iodine), which are contained in a fumigant used for disinfection and pest control of wood packaging materials, may cause failure of the product. Prevent the entry of fumigant residues into the product or consider other methods (such as heat treatment) instead of fumigation. The disinfection and pest control measures must be applied to unprocessed raw wood.

Page 12

CONDITIONS OF USE FOR THE PRODUCT

(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;

i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;

and

ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the

case of any problem, fault or failure occurring in the PRODUCT.

(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.

MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL

RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY

INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE

OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR

WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL

BULLETINS AND GUIDELINES FOR the PRODUCT.

("Prohibited Application")

Prohibited Applications include, but not limited to, the use of the PRODUCT in;

• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the

public could be affected if any problem or fault occurs in the PRODUCT.

• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality

assurance system is required by the Purchaser or End User.

• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,

Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and

Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other

applications where there is a significant risk of injury to the public or property.

Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or

more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific

applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or

other safety features which exceed the general specifications of the PRODUCTs are required. For details, please

contact the Mitsubishi representative in your region.

CONSIDERATIONS FOR USE

Considerations for the Wind River Systems product

C Controller module has an embedded real-time operating system, VxWorks, manufactured by Wind River Systems, Inc. in the United States. We, Mitsubishi, make no warranty for the Wind River Systems product and will not be liable for any problems and damages caused by the Wind River Systems product during use of C Controller module. For the problems or specifications of the Wind River Systems product, refer to the corresponding manual or consult Wind River Systems, Inc. Contact information is available on the following website.

• Wind River Systems, Inc.: www.windriver.com

Page 13

INTRODUCTION

Thank you for purchasing the Mitsubishi MELSEC iQ-R series programmable controllers. This manual describes the memory, functions, devices, and parameters to use the module listed below. Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the performance of the MELSEC iQ-R series programmable controller to handle the product correctly. When applying the program example provided in this manual to an actual system, ensure the applicability and confirm that it will not cause system control problems. Please make sure that the end users read this manual.

Relevant product

R12CCPU-V

Page 14

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

CONSIDERATIONS FOR USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

PART 1 PROGRAMMING

CHAPTER 1 EXECUTING PROGRAMS 20

1.1 Execution Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.2 Initial Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.3 I/O Access Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

CHAPTER 2 OPERATION PROCESSING IN C Controller Module 22

2.1 Operation Processing Depending on Operating Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.2 Operation Processing at Momentary Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CHAPTER 3 MEMORY CONFIGURATION OF C Controller Module 24

3.1 Memory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Program memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

System memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

CPU buffer memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Device/label memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Data memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

SD memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

USB Mass Storage Class-compliant device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.2 Memory Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.3 Memory Life . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.4 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Drive names and file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

File type and storage destination memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

File and folder configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

PART 2 FUNCTIONS

CHAPTER 4 BASIC FUNCTIONS 32

4.1 Program Monitoring (WDT) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Monitoring time setting and reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Timeout of watchdog timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.2 Clock Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Clock data setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Time zone setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Daylight saving time function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.3 Remote Operation Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Remote RUN/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Page 15

Remote PAUSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Remote RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Remote operation and operating status of a C Controller module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.4 Device Access Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.5 Interrupt Function to C Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Factor of interrupt pointer number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Interrupt procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.6 Fixed Cycle Processing Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Setting a fixed cycle processing interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Checking the interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.7 Inter-module Synchronization Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Fixed cycle synchronization function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Interaction with cycle of the fixed cycle communication of the multiple CPU system function . . . . . . . . . . . . . . 53

Parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.8 Label Communication Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.9 Data Analysis Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.10 Output Mode Setting Function from STOP to RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.11 Memory Card Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Boot operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Enable/disable the use of file/data on memory card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.12 RAS Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Self-diagnostic function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Error clear function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Event history function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.13 Security Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Individual identification information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

File access restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Locked out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

CONTENTS

CHAPTER 5 ACCESS FUNCTION USING NETWORK MODULE 76

5.1 Data Communication via Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.2 Cyclic Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Access by link refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Direct access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Buffer memory access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

5.3 Transient Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Message communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Access to devices on another station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.4 Access Function of Each Network Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

CC-Link IE Controller Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

CC-Link IE Field Network module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

MELSECNET/H network module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

CC-Link module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5.5 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Link refresh time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Refresh cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Transmission delay time of cyclic transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Reduction of link refresh time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Page 16

CHAPTER 6 Ethernet COMMUNICATION FUNCTIONS 104

6.1 Connection with MELSOFT product or GOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Connection via a hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Direct connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6.2 Communication with SLMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

6.3 FTP Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

6.4 Time Setting Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

6.5 Telnet Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

6.6 Security Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

IP filter function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

6.7 Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Own node settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

External device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

FTP server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Telnet Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

CHAPTER 7 CC-Link IE Field Network Basic FUNCTION 125

7.1 Cyclic Transmission Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Data transition and link device assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Link refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Operation of link scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Group number setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Input and output status when an error occurred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Output status when a C Controller module is in STOP state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Reserved station specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

7.2 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Interlock program for cyclic transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

7.3 Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

CC-Link IEF Basic setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

7.4 CC-Link IE Field Network Basic diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Acquiring diagnostic information of slave stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7.5 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Link scan time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Transmission delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

CHAPTER 8 MULTIPLE CPU SYSTEM FUNCTIONS 147

8.1 Out-of-Group I/O Fetch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Accessing controlled module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Accessing non-controlled module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.2 Operation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Stop setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Settings for synchronized startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Clock data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8.3 Multiple CPU Parameter Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8.4 Data Communication Between CPU Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Used memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Fixed scan communication setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Error detection setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Page 17

CPU number-based data assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Functions that can be used for communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Communication using CPU buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Communication using fixed cycle communication area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

8.5 Interrupt from Another CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Interrupt from a C Controller module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Interrupt from programmable controller CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

8.6 Issuing an Interrupt to Another CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

APPENDIX 178

Appendix 1 Error Code List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Error code system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Operation when an error occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

How to clear errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Error code list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Appendix 2 Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Guide for reference of event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Appendix 3 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

POWER LED of Power supply module turns OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

READY LED on C Controller module does not turn ON (green) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

READY LED on C Controller module is kept flashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Ethernet communication between C Controller module and personal computer cannot be established . . . . .205

File access fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Connection with peripherals fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

File read from a C Controller module fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

An error occurs during user program execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

The serial communication cannot be established . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Communication with Ethernet device cannot be established . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

Drive name of the SD memory card is not displayed properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Drive name of a USB Mass Storage Class-compliant device is not displayed properly . . . . . . . . . . . . . . . . . . 208

CC-Link IE Field Network Basic functions cannot be used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Appendix 4 Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Appendix 5 Special Relay List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Appendix 6 Special Register List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Appendix 7 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

System parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

CPU parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Module parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Memory card parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Appendix 8 VxWorks Component List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Appendix 9 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Buffer memory list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Buffer memory details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Appendix 10Processing Time of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

C Controller module dedicated functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Appendix 11General Safety Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

When the ERR.

Fail-safe measures when a C Controller system fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

contact of a power supply module is not used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

contact of a power supply module is used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

CONTENTS

Page 18

Appendix 12Calculation Method for Heat Generation of C Controller Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Appendix 13Communication Examples Using Serial Communication Module . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Appendix 14Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

INDEX 254

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258

Page 19

RELEVANT MANUALS

Manual name [manual number] Description Available form

MELSEC iQ-R C Controller Module User's Manual (Application) [SH-081369ENG] (this manual)

MELSEC iQ-R C Controller Module User's Manual (Startup) [SH-081367ENG]

MELSEC iQ-R C Controller Module Programming Manual [SH-081371ENG]

MELSEC iQ-R C Controller Module/C Intelligent Function Module Programming Manual (Data Analysis) [SH-081756ENG]

CW Workbench/CW-Sim Operating Manual [SH-081373ENG]

CW Configurator Operating Manual [SH-081382ENG]

e-Manual refers to the Mitsubishi FA electronic book manuals that can be browsed using a dedicated tool. e-Manual has the following features:

• Required information can be cross-searched in multiple manuals.

• Other manuals can be accessed from the links in the manual.

• Hardware specifications of each part can be found from the product figures.

• Pages that users often browse can be bookmarked.

Explains the functions, devices, and parameters of a C Controller module.

Explains the performance specifications, procedure before operation, and troubleshooting of a C Controller module.

Explains the programming specifications and dedicated function library of a C Controller module.

Explains the programming specifications and dedicated function library for analyzing the data of a C Controller module and a C intelligent function module.

Explains the system configuration, specifications, functions, and troubleshooting of CW Workbench/CW-Sim.

Explains the system configuration, parameter settings, and operation methods for the online function of CW Configurator.

Print book e-Manual PDF

e-Manual PDF

Page 20

TERMS

Unless otherwise specified, this manual uses the following terms.

Ter m Description

Base unit A generic term for main base units, extension base units, and RQ extension base units.

C Controller module A generic term for MELSEC iQ-R series C Controller modules.

C Controller module dedicated functions A dedicated function library offered by a C Controller module.

It is used to control a C Controller module.

C intelligent function module A generic term for MELSEC iQ-R series C intelligent function modules.

CC-Link IE A generic term for CC-Link IE Controller Network and CC-Link IE Field Network.

CC-Link IE Controller Network-equipped module

CC-Link IE Field Network-equipped master/local module

CC-Link IE module A generic term for CC-Link IE Controller Network-equipped modules and CC-Link IE Field Network-equipped

CPU module A generic term for MELSEC iQ-R series CPU modules.

CW Configurator A generic product name for SWnDND-RCCPU. ('n' indicates its version.)

CW Workbench An abbreviation for a C Controller module and C intelligent function module engineering tool, CW Workbench.

Data analysis function A dedicated function library offered by a C Controller module and a C intelligent function module.

Dedicated function library A generic term for C Controller module dedicated functions, MELSEC data link functions, data analysis functions,

GOT An abbreviation for the Mitsubishi Graphic Operation Terminal.

I/O module A generic term for input modules, output modules, I/O combined modules, and interrupt modules.

Intelligent function module A module which has functions other than input and output, such as an A/D converter module or a D/A converter

MELSEC data link function A dedicated function library offered by a C Controller module.

Network module A generic term for the following modules:

Power supply module A generic term for MELSEC iQ-R series power supply modules.

R12CCPU-V An abbreviation for R12CCPU-V C Controller modules.

Statistical analysis function A dedicated function library offered by a C Controller module and a C intelligent function module.

Target device A personal computer, GOT, or another CPU module to connect for data communication.

USB Mass Storage Class-compliant device A USB device that is compliant with the standard for recognizing as a memory device (USB Mass Storage

VxWorks A product name for a real-time operating system manufactured by Wind River Systems, Inc.

A generic term for RJ71GP21-SX CC-Link IE Controller Network modules and an RJ71EN71 (when a CC-Link IE Controller Network function is used).

A generic term for RJ71GF11-T2 CC-Link IE Field Network master/local modules and an RJ71EN71 (when a CC-Link IE Field Network function is used).

master/local modules.

It is used for data analysis processing.

and statistical analysis functions.

module.

It is used to access another CPU module as a connection target via network or in a multiple CPU system.

• CC-Link IE Controller Network module

• CC-Link IE Field Network module

• MELSECNET/H network module

• CC-Link module

It is used for statistical analysis processing.

Class).

Page 21

PART 1 PROGRAMMING

This part comprises the following chapters.

1 EXECUTING PROGRAMS

2 OPERATION PROCESSING IN C Controller Module

3 MEMORY CONFIGURATION OF C Controller Module

PART 1

Page 22

1 EXECUTING PROGRAMS

1.1 Execution Order

The following shows the execution order of the programs in a C Controller module.

1. Initial processing

2. Operation processing of a program

1.2 Initial Processing

The following shows the process when turning the power ON or resetting a module.

• I/O module initialization

• Parameter check

• Multiple CPU system parameter consistency check

• I/O number assignment for the mounted module

• IP address setting for a C Controller module

• Network information setting for CC-Link IE Controller Network

• Network information setting for CC-Link IE Field Network

• Network information setting for CC-Link Network

• Initial value setting for intelligent function modules

• Script file execution

1.3 I/O Access Timing

This section shows the timings for reading input (X) and writing output (Y).

Timings for reading input (X)

The timings for reading input (X) is as follows:

• When a dedicated function library (such as CCPU_X_In_BitEx/mdRandREx) is executed in a user program

• When input (X) data is read out from a peripheral device (Device/buffer memory batch monitoring of CW Configurator is performed.)

Timings for writing output (Y)

The timings for writing output (Y) is as follows:

• When a dedicated function library (such as CCPU_Y_Out_BitEx/mdRandWEx) is executed in a user program

• When output (Y) data is written to a peripheral device (Device/buffer memory batch monitoring of CW Configurator is performed.)

1 EXECUTING PROGRAMS

1.1 Execution Order

Page 23

MEMO

1 EXECUTING PROGRAMS

1.3 I/O Access Timing

Page 24

2 OPERATION PROCESSING IN C Controller

Module

This chapter shows the operation processing in a C Controller module.

2.1 Operation Processing Depending on Operating

Status

The operating statuses of a C Controller module are as follows:

• RUN

•STOP

• PAUSE

Operation processing in RUN state

RUN is a state where performing output (Y) to each module and writing data to the buffer memory from a user program*1 are enabled.

*1 A program in which a C Controller module dedicated function is used

■Output when entering the RUN state

C Controller module outputs the following depending on the setting of the output (Y) when the module state is changed from STOP to RUN. (Page 60 Output Mode Setting Function from STOP to RUN)

• The status of output (Y) which is saved in STOP state

Operation processing in STOP state

STOP is a state where performing output (Y) to each module and writing data to the buffer memory from a user program*1 are disabled. The operating status can be changed with the RESET/STOP/RUN switch or the remote operation function. If the stop error occurred in a C Controller module, the module will be in STOP state.

*1 A program in which a C Controller module dedicated function is used

■Output when entering the STOP state

C Controller module saves the output status right before the C Controller module is in STOP state, and clears all outputs (Y) to OFF.

Operation processing in PAUSE state

PAUSE is a state where performing output (Y) to each module and writing data to the buffer memory from a user program are disabled with the ON/OFF of the output (Y) retained.

• Even if the operating status of the C Controller module is in RUN, STOP, or PAUSE, the output (Y) can be performed and data can be written to the buffer memory from CW Configurator, SLMP communication, and MELSEC data link functions.

• Even if the operating status of the C Controller module is in RUN, STOP, or PAUSE, the operation processing of a user program is performed. When splitting the program processing according to the operating status, use the C Controller module dedicated function (CCPU_GetCpuStatus) for programming.

2 OPERATION PROCESSING IN C Controller Module

2.1 Operation Processing Depending on Operating Status

Page 25

2.2 Operation Processing at Momentary Power Failure

When the input power voltage fed to the power supply module is lower than the specified range, a C Controller module detects a momentary power failure and performs the following processes.

When a momentary power failure less than the allowable time has occurred

When a momentary power failure occurs, a C Controller module suspends processing with its output status retained. After power is recovered, error information is registered to the event history file. (Only at the first detection)

■When the momentary power failure is recovered

After the momentary power failure is recovered, a C Controller module continues processing.

■Check for the number of momentary power failure detection

Since a C Controller module retains number of momentary power failure inside the module, it can be checked using the special register SD53 or the C Controller module dedicated function (CCPU_GetPowerStatus).

■Measurement of the watchdog timer (WDT) during a momentary power failure

A C Controller module continues measuring watchdog timer if the operation is stopped due to the momentary power failure. For example, if a momentary power failure of 15 ms has occurred when the fixed cycle processing time is 190 ms while the monitoring time of the system watchdog time is set to 200 ms, a watchdog timer error occurs.

When a power failure longer than the allowable time has occurred

The initial start is performed and the operation processing will be the same as when the powered ON or reset the C Controller module.

2 OPERATION PROCESSING IN C Controller Module

2.2 Operation Processing at Momentary Power Failure

Page 26

3 MEMORY CONFIGURATION OF C Controller

RAM ROM

CPU built-in memory

Device/label

memory

Program memory

CPU buffer memory

Data memory

System memory

Memory card

SD memory card

USB device

USB Mass Storage Class-compliant device

Module

3.1 Memory Configuration

This section shows the memory configuration of C Controller modules.

*1 CPU built-in memory is a generic term for the built-in memory in a C Controller module. *2 When using a USB device, check the firmware version of the C Controller module. (Page 253 Added and Changed Functions)

The usage of memory can be checked from CW Configurator. (CW Configurator Operating Manual)

Program memory

Program memory is a memory to store files such as user programs and script files.

System memory

System memory is a memory to store system files. Writing files to the system memory is not available.

CPU buffer memory

CPU buffer memory is a memory that is used for data communication among multiple CPUs.

3 MEMORY CONFIGURATION OF C Controller Module

3.1 Memory Configuration

Page 27

Device/label memory

Device area

File storage area

MELPRJ

Root folder Parameter file and others

Arbitrary folder

Arbitrary file

Device/label memory has the following areas.

Data to be allocated

The following table shows the data to be allocated to each area.

Area Application

Device area User device

File storage area File register

Data memory

Data memory is a memory to store the data such as parameter files or arbitrary folders/files. Parameter files written with CW Configurator are stored in the "MELPRJ" folder. (Page 28 Access to the "MELPRJ" folder)

SD memory card

SD memory card is a memory that stores the folders/files created by a function using SD memory card as well as the arbitrary folder/file. The folder configuration is the same as the data memory. (Page 28 Access to the "MELPRJ" folder) It can be accessed from an FTP, a Telnet, and a user program.

USB Mass Storage Class-compliant device

USB Mass Storage Class-compliant device is a memory that stores user programs and arbitrary folders/files. It can be accessed from an FTP, a Telnet, and a user program.

For details on how to create and delete user folders and files, refer to the following manual. CW Configurator Operating Manual

3 MEMORY CONFIGURATION OF C Controller Module

3.1 Memory Configuration

Page 28

3.2 Memory Operation

Memory can be initialized and values can be cleared in a C Controller module with CW Configurator. For details on the memory operation, refer to the following manual. CW Configurator Operating Manual

Item Description

Initialization Formatting program memory/data memory Deletes all the folders and files in the program memory and data memory.

Formatting an SD memory card Deletes all the folders and files in an SD memory card.

Clearing value

*1 The "MELPRJ" folder is created in the data memory, and the default parameters are set. *2 The "MELPRJ" folder is created.

Device Zero clear Clears devices (X, Y, M, B, D, W) to zero.

File register Clears all the file registers (ZR) to zero.

• If the power is turned OFF or the module is reset while initializing each memory or clearing values, the memory will be partly initialized or the value is partly cleared. In this case, perform the memory operation again.

• If the power is turned OFF or the module is reset while accessing each memory, data corruption in the memory or file system error may occur. Shut down the program memory and data memory with the C Controller module dedicated function (CCPU_ShutdownRom), and then power OFF or reset the module.

3.3 Memory Life

This section shows the number of writable times (life) of program memory and data memory.

Program memory and data memory life

The life is represented as a write count index value and data can be written until it reaches to 100,000 times. However, since the system increases the life for writing of program memory and data memory, the write count index value differs from the actual write count. If the write count index value exceeds 100,000 times, the following symptoms may occur. Replace the C Controller module.

• Decrease of writing speed to program memory and data memory

• Unable to write data to program memory and data memory

Method for checking write count index value

The write count index value can be acquired with the C Controller module dedicated function (CCPU_GetCpuStatus). If the value exceeds 100,000 times, it is registered in the event history. (Page 68 Event history function)

• Since the operation of the program memory and data memory is checked at factory acceptance test, the initial value of the write count index is not 0.

• Since a C Controller module always checks data in the program memory and data memory, the write count index value may be increased.

3 MEMORY CONFIGURATION OF C Controller Module

3.2 Memory Operation

Page 29

3.4 Files

This section shows the files of a C Controller module.

Drive names and file systems

The following table shows drive names and file systems that correspond to each memory.

Type Name Drive name File system

CPU built-in memory Program memory /0 FAT16

Data memory /4 FAT16

System memory /SYSTEMROM FAT16

Memory card SD memory card /2 FAT16/FAT32

USB device USB Mass Storage Class-compliant

device

File type and storage destination memory

The following shows the file type and storage destination memory. : Storable,: Not storable

File type CPU built-in memory SD

Program memory

User program 

Script file 

File register 

CPU parameter 

System Parameter 

Module parameter 

Module extended parameter

Memory card parameter 

Event history 

Arbitrary folder/file 



Device/label memory

/USB0 FAT16/FAT32

Data memory System memory

memory card

USB Mass Storage Classcompliant device

3 MEMORY CONFIGURATION OF C Controller Module

3.4 Files

Page 30

File and folder configuration

The following shows the configurations of files and folders. : Access allowed/Valid, : Access not allowed/Invalid, : No folder

Drive Folder File FTP access Factory setting After

initialization

/0 

/4 MELPRJ

/SYSTEMROM OS_IMAGEFILE R12CCPU-V_XX

/USB0

*1 The folder is created after initialization or writing parameters. *2 The suffixed 'XX' indicates the upper two digits of the serial number. *3 The drive is created when an SD memory card is inserted. *4 The drive is created when a USB Mass Storage Class-compliant device is connected.

VxWorks image file 

INCLUDE CCPUFunc.h C Controller module dedicated

MDFunc.h MELSEC data link function

DANLFunc.h Data analysis function/

 prjParams.h VxWorks component list file 

 DriveNameInfo.txt Drive name list file 

MELPRJ

function header file

header file

statistical analysis function header file





Considerations on file operation

The following explains the restriction on memory and drive operations of a C Controller module.

■Writing files

Before writing files with an FTP or a Telnet during user program operation, make sure that the files to be written will not affect the running user program.

■Access to the "MELPRJ" folder

The "MELPRJ" folder manages data written with CW Configurator. Do not access it for a purpose other than backup or restoration. If a portion of the files stored in the folder is changed, the C Controller module may not operate properly.

■Access to the same file

For C Controller modules, a file being written cannot be accessed and a file being accessed cannot be written.

■Number of files

Up to 512 files can be stored in the program memory and data memory of a C Controller module.*1 (A folder is included in the number of files.) However, the maximum number may be reduced depending on a file name length and character types. When using an SD memory card and a USB Mass Storage Class-compliant device, note that the number of files which can be stored differs depending on the memory capacity and a file system format. The number of files in a folder must be 500 or less. Storing more than 500 files may significantly increase the file access time.

*1 This number applies when storing a file which is composed of a file name within 8 characters and an extension within 3 characters, and

which includes alphanumeric characters (not including lower-case characters) only.

■Creating folders

Do not create a folder in the root ("/") of a C Controller module. If a folder is created, an error may occur or an unintended folder may be created. (These errors also occur when transferring a folder to the root ("/") from FTP.)

3 MEMORY CONFIGURATION OF C Controller Module

3.4 Files

Page 31

■File names and folder names

Use alphanumeric characters and special characters (excluding \, /, *, ?, <, >, |, :, ", $) for a file name and folder name to be stored. Otherwise, the following symptoms may occur.

• Garbled file name and folder name

• Loss of file and folder When only a special character (.) is used for a folder name, a folder cannot be created.

• A special character (.) following the usable character codes is not included in the folder name. A folder, "a" is created when a folder name starts with "a...".

When a file name is composed of lower-case characters, it may be displayed all in upper-case characters when referred from FTP or Telnet.

■File writing destination

Do not write files to the program memory and data memory using a user program. Since the number of writable times (life) of program memory and data memory is limited, the available period of a C Controller module is shortened. When writing files using a user program, write files to an SD memory card, a USB Mass Storage Class-compliant device, or a network device

*1 For details, refer to the manual of VxWorks.

(via FTP/NFS/netDrv), etc.

■Uninstallation of external memory devices

If the following memory devices are unmounted while writing data to user files in the memory devices, data corruption or file system error may occur. When writing data to user files, close the user files before unmounting.

• SD memory card

• USB Mass Storage Class-compliant device

3 MEMORY CONFIGURATION OF C Controller Module

3.4 Files

Page 32

MEMO

3 MEMORY CONFIGURATION OF C Controller Module

3.4 Files

Page 33

PART 2 FUNCTIONS

This part comprises the following chapters.

4 BASIC FUNCTIONS

5 ACCESS FUNCTION USING NETWORK MODULE

6 Ethernet COMMUNICATION FUNCTIONS

7 CC-Link IE Field Network Basic FUNCTION

8 MULTIPLE CPU SYSTEM FUNCTIONS

PART 2

Page 34

4 BASIC FUNCTIONS

Window

Displayed items

This chapter shows the basic functions of C Controller modules.

4.1 Program Monitoring (WDT) Function

This function monitors and detects errors on hardware and a user program by using the watchdog timer (WDT), an internal timer of a C Controller module.

Item Description

System watchdog timer A timer to monitor the system of a C Controller module.

Use this to detect an error in hardware and system software.

User watchdog timer A timer to monitor a user program.

Monitoring time setting and reset

The following shows the setting and resetting method for the monitoring time for the watchdog timer.

System watchdog timer

Set a monitoring time for the system watchdog timer within the range of 20 to 2000 ms (in 10 ms units). The system of a C Controller module resets the system watchdog timer while executing fixed cycle processing.

[CPU Parameter]  [RAS Setting]  [WDT (Watchdog Timer) Setting]

Use this to detect an error in a user program.

Item Description Setting range Default

Monitoring time Set the execution monitoring time to the system WDT. 20 to 2000 ms (10 ms units) 1000 ms

User watchdog timer

Set a monitoring time for the user watchdog timer within the range of 100 ms to 10000 ms (in 10 ms units) by using the C Controller module dedicated function (CCPU_StartWDT). Monitoring starts by executing the C Controller module dedicated function (CCPU_StartWDT), and the monitoring time is reset by executing the C Controller module dedicated function (CCPU_ResetWDT).

4 BASIC FUNCTIONS

4.1 Program Monitoring (WDT) Function

Page 35

Timeout of watchdog timer

Precautions

When the watchdog timer times out, an error indicating that the monitoring time set in the watchdog timer setting has been exceeded (watchdog timer error) occurs. If a user watchdog timer error occurs, the BUS RUN LED turns OFF and the ERROR LED starts flashing. If a system watchdog timer error occurs, the READY LED turns OFF.

System watchdog timer

In case of failure of a C Controller module hardware and interrupt program execution, timeout will occur as the system processing has been suspended for a long time.

User watchdog timer

If a user program cannot complete processing within the time specified by using the C Controller module dedicated function (CCPU_StartWDT), and also cannot reset by using the C Controller module dedicated function (CCPU_ResetWDT), a timeout will occur.

When using the following functions, a user watchdog timer error occurs easily since the CPU utilization by a system task with high priority increases.

• Shell command

• Connection with CW Workbench and Wind River Workbench

• Mounting and unmounting an SD memory card

• Unmounting the USB Mass Storage Class-compliant device

• File access

• Ethernet communication

• NFS server communication

4 BASIC FUNCTIONS

4.1 Program Monitoring (WDT) Function

Page 36

4.2 Clock Function

Precautions

C Controller modules have clock data internally. The clock is used to manage time for functions controlled by the system including time stamp for the event history.

• The clock is running continuously using the internal battery of the C Controller module while the power of the module is OFF or a power failure longer than the allowable momentary power failure time occurred.

• For the time stamp of a file, the time of the operating system is used. Since the time of the C Controller module built-in clock and that of operating system may differ, correct the time of the operating system using a user program.

Clock data setting

The following shows the method for setting clock data.

Clock data change

The clock data can be changed in one of the following methods:

• CW Configurator

• C Controller module dedicated function

When the clock data is changed, the following operations are performed:

• The millisecond clock is reset to '0'.

• "Clock setting" (event code: 24000) is saved in the event history file.

■Using CW Configurator

[Online]  [Set Clock]

■Using a C Controller module dedicated function

Write the clock data by using the C Controller module dedicated function (CCPU_SetRTC).

C Controller module sets the time of its built-in clock to that of the operating system at the startup of the module after turning the power ON or resetting it. Use a user program in order to set the time for a running operating system.

Clock data reading

Read the clock data by using the C Controller module dedicated function (CCPU_GetRTC).

■When using this function for the first time

Since the clock data is not set at the factory, be sure to set the certain data.

■When modifying the clock data

Even if changing a portion of the clock data, be sure to write all data to the C Controller module again.

■When changing clock data with a user program

To change the clock data with a user program, be sure to use the C Controller module dedicated function (CCPU_SetRTC). If other clock data setting function is used, the accurate clock data will not be set in the C Controller module.

4 BASIC FUNCTIONS

4.2 Clock Function

Page 37

Time zone setting

Window

Displayed items

Precautions

Set a time zone used in a C Controller module. Specifying the time zone enables the clock in the C Controller module to work in the local time zone.

[CPU Parameter]  [Operation Related Setting]  [Clock Related Setting]

Item Description Setting range Default

Time Zone Set a time zone used in a C Controller module. • UTC+13

•UTC+12

•UTC+11

•UTC+10

•UTC+9:30

•UTC+9

•UTC+8

•UTC+7

•UTC+6:30

•UTC+6

•UTC+5:45

•UTC+5:30

•UTC+5

•UTC+4:30

•UTC+4

•UTC+3:30

•UTC+3

•UTC+2

•UTC+1

•UTC

•UTC-1

•UTC-2

•UTC-3

•UTC-3:30

•UTC-4

•UTC-4:30

•UTC-5

•UTC-6

•UTC-7

•UTC-8

•UTC-9

•UTC-10

•UTC-11

•UTC-12

Comment Enter a comment such as a name of a city for the time zone. 1 to 32 characters 

UTC+9

Once the module is initialized, the parameters will be restored to the default setting even when overseas time zone has been set. Changing the clock of the module is required when the time zone is set again.

• To apply the time zone setting on the C Controller module, turn the power OFF and ON, or reset the module after writing parameters.

• In a multiple CPU system, the time zone set in the CPU No.1 is used for other CPU modules. If the time zone is set to the CPUs from No.2 to No.4, the setting is not applied.

4 BASIC FUNCTIONS

4.2 Clock Function

Page 38

Daylight saving time function

01:59:59

02:00:00

03:00:00

02:00:01

03:00:01

00:59:59

01:59:59

01:00:00

01:00:01

(1) (2)

The daylight saving time function adjusts the time of a C Controller module to daylight saving time. This function advances the time of a C Controller module by one hour on the start date and time, and reverses it by one hour on the end date and time.

• When daylight saving time starts at 2:00 on the second Sunday in March (1), and ends at 2:00 on the first Sunday in November (2)

A: Before adjustment B: After adjustment C: Daylight saving time

Before using daylight saving time, check the version of a C Controller module and an engineering tool. (Page 253 Added and Changed Functions)

Timing of daylight saving time adjustment

Daylight saving time is adjusted at the following timing:

• At the start and end of daylight saving time

• Turn the power OFF and ON, or reset the C Controller module

Operation check of the daylight saving time function

The operation of the daylight saving time function can be checked by the following:

■C Controller module dedicated function

Whether the date lies inside or outside the daylight saving time period can be checked by using the C Controller module dedicated function (CCPU_GetRTC).

■Event history

The history for the start and end of daylight saving time can be checked in the event history for the date set in the daylight saving time setting.

Operation of other functions using clock data

The following table shows the operation of the functions using clock data in a C Controller module during the daylight saving time period.

Item Description

Clock data reading Read clock data after adjusting the time for daylight saving time.

Clock data writing Write as clock data after adjusting the time for daylight saving time.

4 BASIC FUNCTIONS

4.2 Clock Function

Page 39

Daylight saving time settings

Window

Displayed items

Set a start date and time, and an end date and time for daylight saving time.

[CPU Parameter]  [Operation Related Setting]  [Clock Related Setting]  [Setting to Adjust Clock for Daylight Saving Time]

Item Description Setting range Default

Adjust Clock for Daylight Saving Time Set whether to enable the daylight saving time setting. • Enable

• Disable

Start/End Time Specification Method Set the timing for switching to daylight saving time to the specified

week or the specified date.

Week Start Month Set a date and time to start daylight saving time. 1 to 12 3

Week The Last Week, 1st

Day of Week

Time 0:00 to 23:00 2:00

End Month Set a date and time to end daylight saving time. 1 to 12 11

Week The Last Week, 1st

Day of Week

Time 0:00 to 23:00 2:00

Date Start Month Set a date and time to start daylight saving time. 1 to 12 3

Day The Last Date, 1 to 311

Time 0:00 to 23:00 2:00

End Month Set a date and time to end daylight saving time. 1 to 12 11

Day The Last Date, 1 to 311

• Week

•Date

Week to 4th Week

Sunday to Saturday Sunday

Week to 4th Week

Sunday to Saturday Sunday

Disable

Week

2nd Week

1st Week

Time 0:00 to 23:00 2:00

4 BASIC FUNCTIONS

4.2 Clock Function

Page 40

Precautions

• The clock data cannot be changed to data less than one hour from the start date and time of daylight saving time. When the daylight saving time setting is enabled for the CPU No.1 in a multiple CPU system, the clock data in the CPU No.2 to 4 also cannot be changed in the same way.

• For the period less than one hour from the start date and time or less than one hour until the end date and time of daylight saving time, the function that is triggered by time may not perform or may perform twice.

• Functions perform based on date information after adjustment for daylight saving time when the daylight saving time setting is enabled, and therefore there are times when the date output by functions using clock data is (before adjustment) ≥ (after adjustment), and the order (No.) in which events occur and the sorting order for the date on which events occur do not match. Consequently, when checking output results in chronological order, sort not in the order for the date on which events occur, but in the order (No.) in which events occur.

4 BASIC FUNCTIONS

4.2 Clock Function

Page 41

4.3 Remote Operation Function

Precautions

The operating status of a C Controller module can be controlled with CW Configurator, a user program, and SLMP. The following types of remote operation are available:

• Remote RUN/STOP

• Remote PAUSE

• Remote RESET

Remote RUN/STOP

Change the C Controller module status to RUN/STOP externally while the RESET/STOP/RUN switch is on the RUN position. Use this function to change the C Controller module status to RUN/STOP when the module is located in an inaccessible place such as in the control panel by using an external signal.

Executing remote operations

The following methods are available to execute remote RUN/STOP:

■Using CW Configurator

Refer to the following manual. CW Configurator Operating Manual

■Using a user program

Execute the C Controller module dedicated function (CCPU_Control) to perform remote RUN/STOP. MELSEC iQ-R C Controller Module Programming Manual

■Using SLMP

Refer to the following manual. SLMP Reference Manual

When "Clear" is selected for the device/label memory at the time of performing remote RUN from CW Configurator, the following devices are cleared.

• X, Y, M, B, D, W

Since C Controller module gives priority to STOP, observe the following considerations.

■STOP timing

C Controller module is stopped when remote STOP is performed from either of a user program or CW Configurator.

■To change the remote STOP state to RUN again

Perform remote RUN.

■Output (Y) status during remote STOP

When "Output Mode Setting of STOP to RUN" is set to "Output the Output (Y) Status before STOP" in CW Configurator, the output (Y) state is output when the state is changed from RUN to STOP at remote RUN.

■User program during remote STOP

The user program does not stop the execution even if the C Controller module is placed into the remote STOP state. To change the processing according to the operating status of the C Controller module, use the C Controller module dedicated function (CCPU_GetCpuStatus) in the program.

4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 42

Remote PAUSE

Precautions

Window

Displayed items

Change the C Controller module status to PAUSE externally while the RESET/STOP/RUN switch is on the RUN position. Use this function to retain the output (Y) of the C Controller module in the RUN state in such system as process control.

Executing remote operations

The following methods are available to execute remote PAUSE:

■Using CW Configurator

Refer to the following manual. CW Configurator Operating Manual

■Using a user program

Execute the C Controller module dedicated function (CCPU_Control) to perform remote PAUSE. MELSEC iQ-R C Controller Module Programming Manual

■Using SLMP

Refer to the following manual. SLMP Reference Manual

The user program does not stop executing even if the C Controller module is in the remote PAUSE state. To change the processing according to the operating status of the C Controller module, use the C Controller module dedicated function (CCPU_GetCpuStatus) in the program.

Remote RESET

Reset the C Controller module externally while the module is in the STOP state (including the case in which the module is stopped due to an error). Even when the RESET/STOP/RUN switch is on the RUN position, the C Controller module can be reset while the module is in STOP state.

Enabling remote RESET

Before performing remote RESET, enable the remote RESET.

[CPU Parameter]  [Operation Related Setting]  [Remote Reset Setting]

Item Description Setting range Default

Remote Reset Set whether to enable remote RESET. • Disable

• Enable

Disable

4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 43

Executing remote operations

Precautions

The following methods are available to execute remote RESET:

■Using CW Configurator

Refer to the following manual. CW Configurator Operating Manual

■Using a user program

Execute the C Controller module dedicated function (CCPU_Reset) to perform remote RESET. MELSEC iQ-R C Controller Module Programming Manual

■Using SLMP

Refer to the following manual. SLMP Reference Manual

■Before performing remote RESET

Close each user program in the C Controller module before performing remote RESET. Performing remote RESET while the user program is being operated may damage the user program and data files.

■Status after the completion of remote RESET

After performing the remote RESET operation, the operating status of the C Controller module or programmable controller CPU will be in the status set with the switch.

■Remote RESET at error stop

If remote RESET is performed when a C Controller module in a single CPU system or CPU No.1 in a multiple CPU system has stopped due to an error, the C Controller module or programmable controller CPU will be in the status set with the switch.

■Remote RESET with CW Configurator

After the remote RESET is performed, the communication between CW Configurator and C Controller module will be disconnected. In this case, reconnect the connection with CW Configurator.

■Remote RESET when CPU No.1 is a programmable controller CPU in a multiple CPU system

For remote RESET of programmable controller CPU, refer to the manual for the programmable controller CPU to be used.

■The host CPU is other than bus master CPU (CPU No.1)

• The parameter ("Enable" is set to "Remote Reset") is set in the bus master CPU (No.1): (Unset: Error)

• The bus master CPU (No.1) is STOP: (CPU is RUN/PAUSE: Error)

• The bus master CPU (No.1) is a programmable controller CPU

The programmable controller CPU (bus master CPU (CPU No.1) cannot be reset when other peripherals (such as GX Works3) performs remote STOP to a programmable controller CPU (bus master CPU (CPU No.1)). Therefore, cancel the remote STOP with the peripheral device performing the remote STOP. Then, place the programmable controller CPU (bus master CPU (CPU No.1)) into STOP state with its RESET/ STOP/RUN switch, the remote operation with CW Configurator, or a user program (the mdControl function) of the C Controller module.

• To perform remote RESET with CW Configurator, change the C Controller module status to STOP using CW Configurator.

• To perform remote RESET with a user program, change the C Controller module status to STOP using a user program.

4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 44

Remote operation and operating status of a C Controller module

The following shows the relationship between remote operations and operating status changes of a C Controller module.

Status change by switch operation and at stop error

The following table shows the operating status of a C Controller module by switch operation and at a stop error. : No status change

Before changing the operating status After changing the operating status

Factor to determine CPU operating status

RESET/STOP/ RUN switch operation

Operation with CW Configurator or SLMP

Execution of the C Controller module dedicated function

Stop error occurred

Operating status RESET/STOP/

RUN switch status

STOP STOP RUN 

RUN RUN  STOP STOP

STOP STOP 

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN 

PAUSE RUN  STOP STOP

RUN RUN  STOP STOP

STOP STOP 

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN 

PAUSE RUN  STOP STOP

RUN RUN  STOP STOP

STOP STOP 

STOP RUN 

STOP PAUSE 

STOP RUN 

STOP PAUSE 

STOP RUN 

RESET/STOP/RUN switch operation

RUN STOP



(Error STOP)

Stop error occurred



4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 45

Status change by remote operations with CW Configurator and SLMP

The following table shows the operating status of a C Controller module by remote operations with CW Configurator and SLMP. : No status change

Before changing the operating status After changing the operating status

Factor to determine CPU operating status

RESET/STOP/ RUN switch operation

Operation with CW Configurator or SLMP

Execution of the C Controller module dedicated function

Stop error occurred

Operating status RESET/STOP/

RUN switch status

STOP STOP RESET

RUN RUN  STOP PAUSE 

STOP STOP RESET

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN RUN  PAUSE RESET

PAUSE RUN RUN STOP 

RUN RUN  STOP PAUSE 

STOP STOP RESET

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN RUN  PAUSE RESET

PAUSE RUN RUN STOP 

RUN RUN  STOP PAUSE 

STOP STOP 

STOP RUN 

STOP RESET

Remote operation with CW Configurator and SLMP

RUN STOP PAU SE RESET

(Error STOP)



(Error STOP)



(Error STOP)



(Error STOP)



(Error STOP)

RESET

*1 Setting "Remote Reset Setting" to "Enable" of the CPU parameters is required.

4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 46

Status change at the execution of the C Controller module dedicated function

The following table shows the operating status of a C Controller module at the execution of the C Controller module dedicated function (CCPU_Control). : No status change

Before changing the operating status After changing the operating status

Factor to determine CPU operating status

RESET/STOP/ RUN switch operation

Operation with CW Configurator or SLMP

Execution of the C Controller module dedicated function

Stop error occurred

Operating status RESET/STOP/

RUN switch status

STOP STOP RESET

RUN RUN  STOP PAUSE 

STOP STOP RESET

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN RUN  PAUSE RESET

PAUSE RUN RUN STOP 

RUN RUN  STOP PAUSE 

STOP STOP RESET

PAU SE (Actual status: STOP)

RUN (Actual status: STOP)

STOP RUN RUN  PAUSE RESET

PAUSE RUN RUN STOP 

RUN RUN  STOP PAUSE 

STOP STOP 

STOP RUN 

STOP RESET

Execution of the C Controller module dedicated function

RUN STOP PAU SE RESET

(Error STOP)



(Error STOP)



(Error STOP)



(Error STOP)



(Error STOP)

RESET

*1 Setting "Remote Reset Setting" to "Enable" of the CPU parameters is required.

4 BASIC FUNCTIONS

4.3 Remote Operation Function

Page 47

4.4 Device Access Function

Data can be read from/written to devices and buffer memory of an intelligent function module controlled by a CPU module or a C Controller module by using the dedicated function library. For accessible modules and routes, refer to the following manual. MELSEC iQ-R C Controller Module Programming Manual

Data can be read from/written to devices and buffer memory of a C Controller module by using a peripheral device (such as CW Configurator).

Function list

The following table shows the functions used for accessing devices.

Function name Description

CCPU_FromBuf To read data from the CPU buffer memory of the CPU module or buffer memory of the intelligent function module which

CCPU_FromBuf_ISR

CCPU_ToBuf To write data to the CPU buffer memory of the CPU module (host station) or the buffer memory of the intelligent

CCPU_ToBuf_ISR

CCPU_X_In_BitEx To read an input signal (X) in bit (1-point) units.

CCPU_X_In_WordEx To read an input signal (X) in word (16-point) units.

CCPU_X_In_Word_ISR

CCPU_Y_In_BitEx To read an output signal (Y) in bit (1-point) units.

CCPU_Y_In_WordEx To read an output signal (Y) in word (16-point) units.

CCPU_Y_In_Word_ISR

CCPU_Y_Out_BitEx To output an output signal (Y) in bit (1-point) units.

CCPU_Y_Out_WordEx To output an output signal (Y) in word (16-point) units.

CCPU_Y_Out_Word_ISR

mdDevRstEx To reset bit devices.

mdDevSetEx To set bit devices.

mdRandREx To read devices randomly.

mdRandWEx To write devices randomly.

mdReceiveEx To read devices in a batch.

mdSendEx To write devices in a batch.

is mounted on the specified module position. (FROM instruction)

function module which is mounted on the specified module position. (TO instruction)

*1 CPU buffer memory cannot be accessed.

4 BASIC FUNCTIONS

4.4 Device Access Function

Page 48

4.5 Interrupt Function to C Controller Module

This function executes a routine (user program) registered by using the C Controller module dedicated function (CCPU_EntryInt) as an interrupt routine (interrupt program) when an interrupt request is issued to a C Controller module from an input module, interrupt module, intelligent function module, and another CPU module. A user program in a state of waiting for an interrupt event notification from a module can be restarted by using the C Controller module dedicated function (CCPU_WaitUnitEvent).

When executing an interrupt request, module parameters of each module need to be set. For details on the setting, refer to the user's manual of each module.

Function list

The following table shows the functions used for interrupting a C Controller module.

Function name Description

CCPU_EntryInt To register a routine to be called when an interrupt occurs.

CCPU_EnableInt To enable the routine registered with the CCPU_EntryInt function.

CCPU_EnableInt_ISR

CCPU_DisableInt To disable the routine registered with the CCPU_EntryInt function.

CCPU_DisableInt_ISR

CCPU_WaitUnitEvent To wait for an interrupt event notification from a module.

Factor of interrupt pointer number

The following shows the interrupt factors for each interrupt pointer number.

Factor Interrupt pointer number Description

Interrupt from module I0 to I15 A pointer used in the module which has an interrupt function.

Inter-module synchronous interrupt I44 A fixed cycle interrupt pointer used for the inter-module synchronization

function.

Multiple CPU synchronous interrupt I45 A fixed cycle interrupt pointer used for the multiple CPU synchronization

Interrupt from module I50 to I1023 A pointer used in the module which has an Interrupt function.

Interrupt priority

The priority has been set to each interrupt pointer. If the priority of an interrupt program of which execution conditions have been satisfied is higher than that of an interrupt program that is currently being executed, the program is executed in accordance with the priority. If the priority of an interrupt of which execution conditions have been satisfied is lower, it will be in a wait state until an interrupt program that is currently being executed is completed.

Interrupt priority Interrupt pointer Execution order at simultaneous

High 3 Inter-module synchronous interrupt (I44), multiple CPU synchronous interrupt

(I45)

Low 8 Interrupt from module (I0 to I15, I50 to I1023) I0 → I1 → I2 → to → I1021 → I1022 → I1023

function.

occurrence

I45 → I44

4 BASIC FUNCTIONS

4.5 Interrupt Function to C Controller Module

Page 49

Interrupt procedure

C Controller Module

(User program)

1. Execute the CCPU_EntryInt function.

2. Execute the CCPU_EnableInt function.

Interrupt routine (interrupt program)

registration table

Interrupt routine (interrupt program) 1

Interrupt routine (interrupt program) 2

(Empty)

Execute an interrupt routine (interrupt program).

3. Issue an interrupt.

Executing interrupt routines

1. By using the C Controller module dedicated function (CCPU_EntryInt), register a routine (user program) to be called as

an interrupt routine (interrupt program) when an interrupt is requested.

2. Enable the registered interrupt routine (interrupt program) by using the C Controller module dedicated function

(CCPU_EnableInt). If it is disabled, the interrupt routine (interrupt program) will not be executed.

3. When an interrupt request is issued from the module, the interrupt routine (interrupt program) is executed.

When an interrupt request is issued to the routine disabled with the C Controller module dedicated function (CCPU_DisableInt), the interrupt request is ignored.

4 BASIC FUNCTIONS

4.5 Interrupt Function to C Controller Module

Page 50

Restarting user programs

Precautions

C Controller Module

(User program)

1. Execute the CCPU_WaitUnitEvent function.

User program is being executed.

2. In an interrupt event wait state

Restart

Interrupt event notification

3. Issue an interrupt.

1. Execute the C Controller module dedicated function (CCPU_WaitUnitEvent) while executing a user program.

2. The user program is placed into a state of waiting for an interrupt event notification from the module.

3. When an interrupt request is issued, the user program restarts.

The following shows the considerations when using C Controller module dedicated function (CCPU_WaitUnitEvent).

■When an interrupt event has already been notified

When an interrupt event has already been notified at the time of executing the C Controller module dedicated function (CCPU_WaitUnitEvent), a user program restarts from a state of waiting for an interrupt event at the same time as the execution of the function. In addition, when multiple interrupt events have been notified to the same interrupt event number at the time of executing the C Controller module dedicated function (CCPU_WaitUnitEvent), a user program performs processing as a single interrupt event notification.

■When using the function in multiple user programs

Do not specify a same interrupt event (interrupt pointer number) in multiple user programs. Otherwise, a user program to which a specified interrupt event (interrupt pointer number) is notified will be undefined.

4 BASIC FUNCTIONS

4.5 Interrupt Function to C Controller Module

Page 51

4.6 Fixed Cycle Processing Function

Window

Displayed items

This function refreshes with a network module and performs data communication with an external device. The following processes are performed with the fixed cycle processing function.

• Refresh processing with network modules (link refresh)

• Reset processing of watchdog timer

• Self-diagnostics processing

Setting a fixed cycle processing interval

The following shows the setting method for the cycle that the fixed cycle processing function operates.

[CPU Parameter]  [Operation Related Setting]  [Refresh Cycle Setting]

Item Description Setting range Default

Refresh Cycle Set the interval that the fixed cycle processing function operates. 1 to 2000 ms (1 ms

units)

Set the value that satisfies the following relational expression for the cycle of the fixed cycle processing. An error will occur when the following expression is not satisfied.

• Setting time of the program monitoring function (WDT) > Cycle of the fixed cycle processing

100 ms

Checking the interval

The following shows the method to check the interval (maximum value/minimum value/current value) at which the fixed cycle processing function operates.

Checking with a function

The interval can be acquired using the C Controller module dedicated function (CCPU_GetConstantProcessStatus).

Checking with special registers

The interval at which the function operates is stored in special registers (SD520/SD522/SD524). (Page 213 Special Register List)

4 BASIC FUNCTIONS

4.6 Fixed Cycle Processing Function

Page 52

4.7 Inter-module Synchronization Function

Input module Output module

A/D converter module

C Controller module

D/A converter module

Inter-module synchronization cycle Inter-module synchronization cycle

Program

C Controller module

Inter-module synchronous interrupt program (I44)

Operation processing Operation processing Operation processing

A/D converter module (set as a synchronization target)

Output conversion

Input Input Input

D/A converter module (set as a synchronization target)

Output

Output Output

Input module (set as a synchronization target)

Input Input Input

Output module (set as a synchronization target)

Output

Output Output

This function adjusts the input or output timing of modules to be synchronized to the inter-module synchronization cycle by matching the control timing of signals among multiple modules.

For details on the inter module synchronization function, refer to the following manual. MELSEC iQ-R Inter-Module Synchronization Function Reference Manual

4 BASIC FUNCTIONS

4.7 Inter-module Synchronization Function

Page 53

Fixed cycle synchronization function

Normal program Interrupted

Inter-module synchronous interrupt

program execution time

Inter-module synchronization cycle

Inter-module synchronous interrupt program

External device

Input Input

InputInput

Output

Input modules Output modules

Input refresh

Operation

processing

Output refresh

(Link device)

(X, Buffer memory)

(Link device)

(Y, Buffer memory)

Executed

The fixed cycle synchronization function is a function to synchronize multiple modules at the timing of the inter-module synchronization cycle to perform data communication and input/output control at a fixed cycle. Using this function enables the accurate speed to be acquired by the encoder input at the fixed cycle, and also enables the highly accurate model prediction control by the accurately-tracked input/output timing.

Although the shorter interval of the inter-module synchronization cycle provides the more accurate synchronous control, the size of program executable in the inter-module synchronous interrupt program will be smaller. By lengthening the interval of the inter-module synchronization cycle, the program with bigger size can be executed. However, the accuracy of the synchronous control will be reduced. To use the fixed cycle synchronization function, consider the program size to be executed.

Synchronization timing of a C Controller module

A C Controller module executes the inter-module synchronous interrupt program (I44) at every inter-module synchronization cycle. Synchronization between a C Controller module and each module is performed at the timing of refresh before and after the inter-module synchronous interrupt program (I44). This will enable the C Controller module to import the input data and to write the output data at the timing of the inter-module synchronization cycle.

Inter-module synchronous interrupt

Interrupt programs are executed at the timing of the inter-module synchronization cycle set with the parameters. The interrupt programs executed at every inter-module synchronization cycle is referred to as the inter-module synchronous interrupt program (I44).

• Describe the control programs to be synchronized in the inter-module synchronous interrupt program (I44).

• The operation when an interrupt factor arises and the program creation method are the same as normal interrupt program.

■Execution timing

The inter-module synchronous interrupt program (I44) is executed at the timing of the inter-module synchronization cycle. The inter-module synchronous interrupt program (I44) is registered using the interrupt function form module. (Page 46 Interrupt Function to C Controller Module)

4.7 Inter-module Synchronization Function

4 BASIC FUNCTIONS

Page 54

Processing of an inter-module synchronous interrupt program (I44)

Precautions

The following shows the processing of an inter-module synchronous interrupt program (I44).

■Input refresh (CC-Link IE Field Network module)

At the input refresh, link devices (RX, RWr) are refreshed from the CC-Link IE Field Network module to be synchronized.

■Operation processing

• To import the input signal (X) and the input from the buffer memory, use the C Controller module dedicated functions (CCPU_X_In_Word_ISR, CCPU_FromBuf_ISR).

• To import the output signal (Y) and the output to the buffer memory, use the C Controller module dedicated functions (CCPU_Y_Out_Word_ISR, CCPU_ToBuf_ISR).

■Output refresh (CC-Link IE Field Network module)

In the output refresh, link devices (RY, RWw) are refreshed to the CC-Link IE Field Network module to be synchronized.

Refresh timing

The following shows the refresh timing depending on the operating status of a C Controller module.

■Operation in the STOP state (RUN to STOP)

• C Controller module turns OFF the output when it is in the STOP state due to user operation (such as user program or switch operation). Refresh is performed continuously during the STOP state.

• A C Controller module turns the output OFF and also stops the refresh when a stop error which is caused by any failure of the C Controller module or any other modules occurred.

The inter-module synchronous interrupt program (I44) does not stop even if C Controller module is in the STOP state.

When the system parameter of the inter-module synchronization function is rewritten while the C Controller module is in the STOP state, it will not applied by switching to the RUN state, and the C Controller module operates with the parameter before the rewrite.

4 BASIC FUNCTIONS

4.7 Inter-module Synchronization Function

Page 55

Interaction with cycle of the fixed cycle communication of the

A/D converter module

(controlled by CPU No.1)

A/D converter module

(controlled by CPU No.2)

The input/output of modules controlled by different CPUs can be synchronized.

C Controller module (CPU No.1)

C Controller module (CPU No.2)

multiple CPU system function

The cycle of the fixed cycle communication of the multiple CPU system function can be matched with the inter-module synchronization cycle. By adjusting the cycle of the fixed cycle communication to the inter-module synchronization cycle, the input/output of modules having different control CPUs can be synchronized. The interaction with the multiple CPU system function is set with the parameter. (Page 158 Fixed scan communication setting)

4.7 Inter-module Synchronization Function

4 BASIC FUNCTIONS

Page 56

Operation of program

Precautions

(1)

(2)

CPU No.1 Program execution processing

Cycle of fixed cycle communication

Cycle of fixed cycle communication Cycle of fixed cycle communication

Inter-module synchronization cycle

Inter-module synchronization cycle Inter-module synchronization cycle

Multiple CPU synchronous interrupt program Inter-module synchronous interrupt program

Normal program

Input Output

Normal program Normal program

Input Output

Operation processing

refresh refresh

Do not set data here even though data can be output at the next inter-module synchronization cycle.

Input modules

(Link device)

Output data

Output data (Link device)

Output data

Ó Write data to the fixed cycle communication area.

Ò Acquire an input value.

Ö Set an output value.

Input data

Fixed cycle communication area

Ô Fixed cycle communication

Fixed cycle communication Fixed cycle communication Fixed cycle communication

Fixed cycle communication

Fixed cycle communication area

Input data

Õ Read data from the fixed cycle communication area.

Multiple CPU synchronous interrupt program Inter-module synchronous interrupt program Multiple CPU synchronous interrupt program Inter-module synchronous interrupt program

Multiple CPU synchronous interrupt program Inter-module synchronous interrupt program

Normal program

Normal program Normal program

Normal program

Input Output

Operation processing

Operation

processing

refresh refresh

CPU No.2 Program execution processing

Ö Set an output value.

Cycle of fixed cycle communication Cycle of fixed cycle communication

Cycle of fixed cycle communication

Inter-module synchronization cycle Inter-module synchronization cycle

Inter-module synchronization cycle

Create the program so that the two cycles of the output differences are offset.

Input modules

(X, Buffer memory)

Output data

(Y, Buffer memory)

Output data

(Link device)

Output data

(Y, Buffer memory)

Once the inter-module synchronization cycle is interacted with the cycle of the fixed cycle communication, a multiple CPU synchronous interrupt program (I45) and an inter-module synchronous interrupt program (I44) are executed in each intermodule synchronization cycle. The multiple CPU synchronous interrupt program (I45) is executed first, and then the inter-module synchronous interrupt program (I44) is executed. Two inter-module synchronization cycles are required for data acquired by the host CPU to reach to another CPU, and delaying the output timing of the controlled module of the host CPU and the controlled module of another CPU for two cycles is required for the output synchronized among CPU modules.

For a C Controller module, only the link devices of CC-Link IE Field Network modules (RX, RY, RWr, and RWw) are refreshed at the 'input refresh' and 'output refresh' in an inter-module synchronous interrupt program. To import the I/O signals (X, Y) and the values from the buffer memory, use a C Controller module dedicated function. For details on processing of each interrupt program of a C Controller module, refer to the following section.

• Inter-module synchronous interrupt program (I44) Page 51 Fixed cycle synchronization function

• Multiple CPU synchronous interrupt program (I45) Page 167 Multiple CPU synchronous interrupt

(1): Write the input value to the fixed cycle communication area of CPU No.1. (2): Set the output value by reading data from the fixed cycle communication area of CPU No.1.

Considerations for interaction with cycle of fixed cycle communication are shown below:

• Selecting "Use" for the inter-module synchronization function enable "Cooperate" to be selected for "Fixed Scan Communication Function and Inter-module Synchronization Function". It cannot be selected when "Not use" is selected for the inter-module synchronization function.

• Even if "I/O Setting Outside Group" is enabled in a program of another CPU, importing the input or output from the module to be synchronized is not available. Although it can be read by direct specification such as DX, DY, Un\Gn, or the C Controller module dedicated function (CCPU_FromBuf), data inconsistency may occur.

• To adjust the start of the inter-module synchronization function among all CPUs, confirm that the inter-module synchronization function is available by checking the ready flag of CPU No.n from SM220 to SM223 turns ON. By using SM220 to SM222 in an interlock program, the start of the inter-module synchronization function can be matched among all CPUs.

4 BASIC FUNCTIONS

4.7 Inter-module Synchronization Function

Page 57

Parameter setting

Operating procedure

Displayed items

Set a module configuration diagram with CW Configurator to configure the inter-module synchronization setting.

[System Parameter]  [Synchronization Setting within the Modules]  [Synchronization Setting within the Modules]

1. Select "Use" for "Use Inter-module

Synchronization Function in System".

2. Click the "Detailed Setting" for "Select

Synchronous Target Unit between Unit".

3. Select "Synchronize" for the module to be

synchronized.

4. Set the inter-module synchronization cycle in

"Synchronous Fixed Scan Interval Setting within the Modules".

5. When writing parameters, write both of the

system parameter and module parameter.

6. Configure the setting for the synchronous

master when a local station of CC-Link IE Field Network module is to be synchronized. (The setting is not required for a master station.)

Item Description Setting range Default

Use Inter-module Synchronization Function in System Set whether or not to use the inter-module

Select Synchronous Target Unit between Unit

Synchronous Fixed Scan Interval Setting within the Modules

Synchronous Master Setting within the Modules

*1 The setting range for the inter-module synchronization cycle differs depending on modules. ( Manual for respective modules)

Detailed Setting Set the module to be synchronized. • Do not Synchronize

0.05 ms Unit Setting Set whether or not to set the inter-module

Fixed Scan Interval Setting (Not Set by 0.05ms)

Fixed Scan Interval Setting (Set by 0.05 ms)

Synchronous Master Setting of CC IE Field

Mounted Slot No. Set the mounting slot number for the master station

synchronization function.

synchronization cycle in 0.05 ms units.

Select the inter-module synchronization cycle from the list when it is not set in 0.05 ms units.

Set the inter-module synchronization cycle when it is set in 0.05 ms units.

When "Set" is selected, a master station of CC-Link IE Field Network module is the synchronous master. When "Not Set" is selected, the CPU module (the leftmost CPU module for multiple CPU configuration) is the synchronous master.

of CC-Link IE Field Network module to be set as the synchronous master.

•Not Use

•Use

• Synchronize

•Not Set

•Set

• 0.222 ms

• 0.444 ms

• 0.888 ms

• 1.777 ms

• 3.555 ms

• 7. 111 ms

0.10 to 10.00 ms (in 0.05 ms units)

•Not Set

•Set

0 to 11 0

Not Use

Do not Synchronize

Not Set

0.888 ms

0.50 ms

Not Set

4 BASIC FUNCTIONS

4.7 Inter-module Synchronization Function

Page 58

To interlink with the cycle of the fixed cycle communication of the multiple CPU system function, set "Fixed Scan Communication Function and Inter-module Synchronization Function" under "Fixed Scan Communication Setting" to "Cooperate". (Page 158 Fixed scan communication setting)

4 BASIC FUNCTIONS

4.7 Inter-module Synchronization Function

Page 59

4.8 Label Communication Function

Label1

Label2

Label3

C Controller module

(reference side)

CPU module

(Label definition side)

User program

Obtain an information of the corresponding

devices using specified label (Label1, Label2).

1.Execute the mdGetLabelInfo function.

Label assignment information

Assignment target

(Device name)

Label name

Execute Reading/Writing for the device

corresponding to the label.

2.Execute the

mdRandRLabelEx/mdRandWLabelEx

functions.

Data can be read from/written to labels stored in CPU modules of other stations.

Label communication flow

1. Acquire label assignment information (device information) of the specified label by using the MELSEC data link function

(mdGetLabelInfo).

2. Read/write data from/to a device based on the acquired label assignment information (device information) by using the

MELSEC data link functions (mdRandRLabelEx/mdRandWLabelEx).

• In the label communication, a CPU module can be accessed without changing a user program by acquiring label assignment information again even if the label assignment information of the CPU module is changed.

• The label assignment information (device information) acquired by using the MELSEC data link function (mdGetLabelInfo) does not need to be acquired for each MELSEC data link function (mdRandRLabelEx/ mdRandWLabelEx) execution. However, if the label assignment information (device information) stored in a CPU module is changed, acquire it again by using the MELSEC data link function (mdGetLabelInfo). (Otherwise, an error response is returned.)

■User program functions

The following table shows the functions used for label communication.

Function name Description

mdGetLabelInfo To acquire device information corresponding to label names.

mdRandRLabelEx To read devices corresponding to labels randomly.

mdRandWLabelEx To write devices corresponding to labels randomly.

4.8 Label Communication Function

4 BASIC FUNCTIONS

Page 60

Accessible CPU modules

The following table shows the accessible CPU modules.

Product name Model name

Programmable controller CPU R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU, R32CPU, R32ENCPU, R120CPU,

R120ENCPU

Process CPU R08PCPU, R16PCPU, R32PCPU, R120PCPU

Label types which can be referred to

The following table shows the label types that can be referred to from a C Controller module. : Applicable, : Not applicable, : Not available

Label type "Access from External Device" is selected or not selected. Availability

Global label Selected 

Unselected 

Local label 

System label

*1 The availability of the label differs depending on the device type assigned to the label.

For the device type, refer to the following manual. MELSEC iQ-R C Controller Module Programming Manual

For referring to a label, select "Access from External Device" in GX Works3. (GX Works3 Operating Manual)

4 BASIC FUNCTIONS

4.8 Label Communication Function

Page 61

4.9 Data Analysis Function

This function performs data analysis processing such as fast Fourier transform, digital filter operation, calculation of a cross point between a wave and a specified value, and calculation of a standard deviation. This function enables the detection of machining errors by monitoring current wave and the preventive maintenance of devices by analyzing vibrations. For data analysis functions and statistical analysis functions, refer to the following manual. MELSEC iQ-R C Controller Module/C Intelligent Function Module Programming Manual (Data Analysis)

Function list

The following table shows the functions used for the data analysis function.

■Data analysis function

Function name Description

DANL_SetOpCondition To set operating conditions for data analysis.

DANL_GetOpCondition To acquire operating conditions for data analysis.

DANL_DigitalFilter To perform digital filter operation for the specified wave.

DANL_EnvelopeCalculation To calculate the envelope of the specified wave.

DANL_FFTSpectrum To perform spectrum calculation using fast Fourier transform (FFT) for the specified wave.

DANL_FindCrossPoint To calculate the number of cross points of the specified wave and a reference value for the number of cross points

specified to the maximum number of cross points.

DANL_Peak To calculate the peak values (maximum and minimum) of the specified wave.

DANL_RMS To calculate an RMS (root mean square) of the specified wave.

DANL_BoundCompareTest To compare the specified wave and a check value to check an upper/lower limit.

DANL_AryBoundCompareTest To compare the specified wave and a check value to check an upper/lower limit of the wave.

■Statistical analysis function

Function name Description

DANL_LeastSquare To calculate a coefficient and a constant of a polynomial, and a multiple correlation coefficient by using a least-squares

method for the specified array.

DANL_MovingAverage To calculate a moving average of the specified array.

DANL_StandardDeviation To calculate a standard deviation of the specified array.

DANL_Variance To calculate a variance of the specified array.

DANL_MTUnit To determine a unit space that is used in the MT method based on the specified normal data.

DANL_MTMahalanobisDistance To calculate a Mahalanobis distance of the specified input data.

DANL_MultipleRegression To calculate a coefficient, constant, and regression statistics for multiple regression analysis.

4 BASIC FUNCTIONS

4.9 Data Analysis Function

Page 62

4.10 Output Mode Setting Function from STOP to RUN

Window

Displayed items

Precautions

This function sets the mode of the output (Y) when C Controller module operating status is switched from STOP to RUN.

[CPU Parameter]  [Operation Related Setting]  [Output Mode Setting of STOP to RUN]

Item Description Setting range Default

Output Mode Setting of STOP to RUN

Output the Output (Y) Status before STOP

After the output (Y) status before the operating status turns into STOP state is output, the user program is executed.

Clear the Output (Y)

The output (Y) is turned OFF, and the output (Y) status is output after the program operations are executed.

Set the operation of the output (Y) when the operating status is switched from STOP to RUN.

• Output the Output (Y) Status before STOP

• Clear the Output (Y)

Output the Output (Y) Status before STOP

The following shows the considerations on outputs when changing the status from STOP to RUN after forcing the output (Y) ON at STOP status.

■"Output the Output (Y) Status before STOP" is selected

• When the output (Y) is forced ON when the operating status is STOP, the status before it stopped is output.

• If the output (Y) is OFF before entering the STOP state, the ON state is not retained.

■"Clear the Output (Y)" is selected

• When the output (Y) is forced ON when the operating status is STOP, the ON state is retained.

4 BASIC FUNCTIONS

4.10 Output Mode Setting Function from STOP to RUN

Page 63

4.11 Memory Card Function

Operating procedure

Displayed items

This section shows the functions that use an SD memory card.

Boot operation

The files stored in an SD memory card are transferred to the transfer destination memory which is automatically determined by the C Controller module when turning the power OFF and ON, or resetting the module.

To perform the boot operation, enabling "Memory card parameter execution" under "Service Settings" is required. (Page 74 Service settings)

Boot operation procedure

1. Configure the boot setting.

2. Insert an SD memory card.

3. Write the boot setting and boot file on the SD memory card.

4. Turn the power OFF and ON, or reset the C Controller module.

Boot setting

[Memory Card Parameter]  [Boot Setting]

1. Double-click "<Detailed Setting>" in "Boot File Setting".

2. Click on the "Type" column. The maximum number of boot

files that can be specified is the same as the number of files that can be stored in the storage memory.

3. Select the type for the boot file. (Two or more parameters

can be selected.)

4. Click the [Add] button to add the file(s).

Item Description Setting range Default

Boot File Setting Set the file used for boot operation from the SD memory card. 

4 BASIC FUNCTIONS

4.11 Memory Card Function

Page 64

Maximum number of boot files allowed

Precautions

Window

Displayed items

The maximum number of boot files allowed is 512. However, the maximum number of boot files is the same as the number of files possible to be stored in the transfer destination memory because more than one file is bootable for a single setting.

• When a parameter file is set as a boot file, the parameter file in the transfer destination C Controller module is overwritten. In addition, if a parameter file is not set as a boot file even when it is stored on the SD memory card, the CPU module operates in accordance with the settings in the parameter file in it.

Enable/disable the use of file/data on memory card

Set whether to use files/data stored on a memory card.

[Memory Card Parameter]  [Setting of File/Data Use or Not in Memory Card]

Item Description Setting range Default

Module Extended Parameter Set whether to use the module extended parameters stored on the SD

memory card.

•Not Use

•Use

Not Use

4 BASIC FUNCTIONS

4.11 Memory Card Function

Page 65

4.12 RAS Function

Self-diagnostic function

Diagnose the presence of any abnormality in the C Controller module itself.

Self-diagnostics timing

If an error occurred when the C Controller module is powered ON or while it is in the RUN/STOP state, the detected error information is displayed, and the operation is stopped.

However, depending on the error occurrence status or the instruction to execute, the C Controller module may not be able to detect the error. Configure safety circuits external to the system to ensure that the entire system operates safely even in such a case.

Error checking methods

The following shows the error checking methods.

■Checking with special relays or special registers

When C Controller module detects any error, the special relays (SM0, SM1) turns ON, and an error code corresponding to the error is stored in the special register (SD0). If more than one error is detected, the latest error code is stored in the special register (SD0). Use the special relay (SM0, SM1) and special register (SD0) in the program for the C Controller module or mechanical interlock. In addition, up to 16 error codes (latest errors occurred on the system) will be stored in the special registers (SD10 to SD25). (The error codes for the 17th and onwards will not be stored.)

■Checking with CW Configurator

The error occurrence of the entire system, latest errors occurred, and event history can be checked in the module diagnostic screen. (CW Configurator Operating Manual)

• In the C Controller module, maximum 16 latest errors occurred can be displayed. In addition, if an additional error occurs after a stop error, the error information is not updated.

• Error logs can be checked using the event history function. (Page 68 Event history function)

The maximum number of continuation errors and stop errors to be displayed is 15 and 2 respectively. If already 15 continuation errors have been displayed, then next continuation error will not be displayed. If the error of the same code has been displayed, the date and time of occurrence and the detailed information about the relevant error is updated.

4 BASIC FUNCTIONS

4.12 RAS Function

Page 66

Operation at error detection of an intelligent function module

Window

Displayed items

If an error is detected with the self-diagnostic function, C Controller module operates in accordance with the setting of "CPU Module Operation Setting at Error Detected" as follows. (Page 65 Operation setting when an error is detected in an intelligent function module)

■When "Stop" is selected in "CPU Module Operation Setting at Error Detected"

When an error is detected, the operation depends on the setting of "Output Mode upon CPU Error" in the Module Parameter of each module.

• When "Clear" is set: Output to the corresponding module is turned OFF.

• When "Hold" is set: Output to the corresponding module is retained.

For the setting method of module parameter, refer to the manual for each module.

■When "Continue" is selected in "CPU Module Operation Setting at Error Detected"

The operation of the C Controller module does not stop.

Error detection setting

Set whether to detect errors.

[CPU Parameter]  [RAS Setting]  [Error Detections Setting]

Item Description Setting

range

Module Verify Error

Fuse Blown Set whether to detect the fuse blown in the controlled

Synchronous Interrupt Program (I44, I45) Executing Time Excessive

*1 If an operating module in which "Not Detected" is selected in the parameter is removed, a module verification error is not detected;

however, a stop error may occur if accessing the removed module by using programs, etc. Since the removed module is not accessible even if it is mounted again, accessing the module by changing the module status from STOP to RUN may result in a stop error.

Execution Interval Exceed (I44, I45) Set whether to detect the excessive execution time (I44,

Program Execution Section Exceed (I45)

Set whether to detect the module verification error. • Detect

module.

I45).

Set whether to detect the program execution section exceed errors (I45).

•Not Detected

Default

Detect

Not Detected

4 BASIC FUNCTIONS

4.12 RAS Function

Page 67

Operation setting when an error is detected

Window

Displayed items

Window

Displayed items

Set the operation of a C Controller module when an error is detected.

[CPU Parameter]  [RAS Setting]  [CPU Module Operation Setting at Error Detected]

Item Description Setting

range

Memory Card Error Set the C Controller module operation upon a memory

card error.

Module Verify Error Set the C Controller module operation upon a module

verification error.

Fuse Blown Set the C Controller module operation upon fuse

blown error.

Synchronous Interrupt Execution Interval Error (CPU Module) Set the operation of CPU module at a synchronous

interrupt execution interval error.

• Stops

• Continues

Default

Stops

Operation setting when an error is detected in an intelligent function module

The operation of a C Controller module when an error occurred in an intelligent function module will be determined with the parameter setting of "CPU Module Operation Setting at Error Detected" under "I/O Assignment Setting".

[System Parameter]  [I/O Assignment Setting]  [I/O Assignment Setting]

Item Description Setting range Default

CPU Module Operation Setting at Error Detection

Set the operation of a C Controller module at the detection of a major error or moderate error in the configured module.

• Critical: Stop, Moderate: Continue

• Critical: Stop, Moderate: Stop

• Critical: Continue, Moderate: Continue

Critical: Stop, Moderate: Continue

4 BASIC FUNCTIONS

4.12 RAS Function

Page 68

LED display setting

Window

Displayed items

CW Configurator

Continuation error occurs.

No continuation

error occurs.

· Power shutoff

· Battery error

Clear the error.

Sets whether to turn the ERROR LED ON/OFF.

[CPU Parameter]  [RAS Setting]  [LED Display Setting]

Item Description Setting

range

ERROR LED Minor Error (Continue

Error)

Set whether to turn the ERROR LED ON when a minor error occurred. • Display

•Do Not Display

Default

Display

Operation setting when a stop error occurred in a multiple CPU function

Set whether to stop all CPUs when a major or moderate error occurs on each CPU in a multiple CPU configuration. (Page 150 Stop setting)

Error clear function

This function clears all the existing continuation errors at once.

Error that can be cleared

Only the following continuation errors can be cleared.

Error code Error name

1000H Power interruption

1080H ROM write count error

1100H Memory card access error

1120H SNTP clock setting error

1124H Default gateway/gateway IP address error

1128H Own node port number error

1129H Open specification port number error

112DH Specified IP address error

112EH Connection establishment failed

1133H Socket communications response send error

1134H TCP connection timeout

1152H IP address error

1155H Connection number acquisition error

4 BASIC FUNCTIONS

4.12 RAS Function

Page 69

Precautions

Error code Error name

1157H Receive buffer securement error

1165H UDP/IP send failed

1166H TCP/IP send failed

1167H Unsend data send error

1200H, 1210H Module moderate error

1220H Another CPU module moderate error

1240H, 1241H Inter-module synchronization processing error

1260H, 1262H Multiple CPU synchronization processing error

1830H Receive queue full

1831H Receive processing error

1832H Transient data error

1840H Memory card error

1843H Internal buttery failure

1846H Refresh cycle exceeded

2120H, 2121H Memory card error

2400H, 2401H Module verification error

2420H Fuse blown error

2441H, 2442H Module major error

2450H Detection of module major error

2461H, 2462H Another CPU module major error

2470H Another CPU module major error

2610H Inter-module synchronization signal error

2630H Multiple CPU synchronization signal error

Method for clearing error

The following shows how to clear errors.

■Using CW Configurator

Clear errors with the module diagnostic function of CW Configurator. (CW Configurator Operating Manual)

■Using user programs

1. Check the continuation error detected by the C Controller module dedicated function (CCPU_GetErrInfo).

2. Clear the cause of the currently detected continuation errors.

3. Execute the C Controller module dedicated function (CCPU_ClearError).

• Since this function clears all the detected continuation errors at once, unintended errors may also get cleared.

• This function does not remove the cleared errors from the event history.

• Any errors occurred in a module other than the C Controller module cannot be cleared by this function.

4 BASIC FUNCTIONS

4.12 RAS Function

Page 70

Event history function

Window

Displayed items

CW Configurator

The information of events that occurred in the host CPU and modules controlled by the host CPU are collected by the CPU module in batch and saved.

The event information that is held in the CPU module is displayed with Engineering tool.

A C Controller module collects and saves the error information such as errors detected by the module, operations done for the module, and network errors from each module. The saved operation and error occurrence information can be checked and viewed in chronological order. Using this function enables to investigate the problems that have occurred in the equipment/devices, check the update related to control data in a C Controller system, and detect any unauthorized access.

The event history information is constantly collected regardless of the operating state of the C Controller module. In some cases; however, the event history information may not be collected due to a major error in a module, a base unit error, a cable failure, or others.

Event history settings

Under normal circumstances, the event history function can be used with its default settings and doesn't need to be manually configured. The storage memory and file size of the event history file can be changed if desired.

[CPU Parameter]  [RAS Setting]  [Event History Setting]

Item Description Setting range Default

Save Destination Set the storage destination of event history files. • Data Memory

Set Save Volume of Per File Set the storage capacity per event history file. 1 to 2048 KB 128 KB

•Memory Card

Data Memory

■Registration from a user program

Event logs can be registered from a user program by executing the C Controller module dedicated function (CCPU_RegistEventLog). In this case, the event type will be "Operation".

4 BASIC FUNCTIONS

4.12 RAS Function

Page 71

Saving event history

■Modules from which event history information is collected

Event history information is collected from the C Controller module and other modules mounted on the same base unit (such as the main base unit and any additional extension base units). Event history information may or may not be collected from devices on the network depending on the specifications of the network modules used to connect to them. For more information including the coverage of event history collection regarding devices on the network, refer to the manual of each module. For a multiple CPU system, each CPU logs only events detected on the modules under its control.

■Events to be saved

The detailed information such as the operation initiator information are saved for troubleshooting purpose when the event history is saved. For the event to be saved as the event history by C Controller module, refer to the event list. (Page 68 Event history function)

Event history file

The storage destination memory and file size for event history files can be changed in the event history setting. (Page 68 Event history settings)

■Storage destination memory

The storage destination memory is set to either the data memory or SD memory card. When an SD memory card is selected, disable the write protect switch of the SD memory card. If it is enabled, an event history will not be stored. (Reading the event history file in the SD memory card using CW Configurator is possible.) If the write protect switch of an SD memory card is enabled, the write error will occur, because, during system operation, an attempt to write an event occurred will failed as the write protect switch is enabled. An error can be checked with the Module Diagnostic function immediately after the error occurred, but the same information cannot be checked after turning the power OFF and ON, or resetting the module since errors are not saved.

For a system for which file write occurs frequently or the system of which state frequently changes because of the unstable communication, the file size of the event history must be larger enough to store a greater number of events. In this case, using an SD memory card is recommended as the storage memory.

■File size

If the specified size is exceeded, the records are deleted from the oldest one and the latest one is stored. A file size of the event history can be obtained by the following formula.

• File size = File header size + Event history management information size + Number of records × Size per event history record

The sizes of each element are as follows:

Element name Size

File header size 20 bytes

Event history management information size 12 bytes

Size per event history record

*1 Since the events which overlaps multiple records exist depending on the event to be saved, a file size per one record will be changed.

40 to 1112 bytes

■Conditions for collecting events

A C Controller module collects event history regardless of the operating status (RUN/STOP/PAUSE/STOP error); however, the event history may not be collected under the following conditions.

• Major error

• Base unit error

• Cable failure

4 BASIC FUNCTIONS

4.12 RAS Function

Page 72

■File creation timing

An event history file is created when:

• When the power is turned OFF and ON (no event history file exists/after the change of event history settings)

• When a C Controller module is reset (no event history file exists/after the change of event history settings)

• At initialization of memory

• At registration of event history (no event history file exists)

When a new event history file is created, the event that indicates a new file creation is saved.

The following shows the operations of the event history when the storage memory is an SD memory card.

Operation Operation of event history

Removal of the SD memory card When the memory initialization event occurs, the event history is stored in the internal memory. If the internal memory

Insertion of an SD memory card The event history, which have been stored in the internal memory during absence of the SD memory card, is stored to

reaches the maximum allowable number for saving event history, all subsequent events will be dropped.

the SD memory card. If the re-inserted SD memory card contains an event history file of the same file size, the C Controller module continues to store the event history information. If the file size is different, the C Controller module removes the existing event history file and creates a new event history file.

■Parameter application timing

The changed parameters are enabled at any of the following timing.

• When the power is turned OFF and ON

• When the C Controller module is reset

If the C Controller module operating status is changed from STOP to RUN after writing the changed parameters, the changed parameters will not be enabled. The changed parameters are enabled only after turning the power OFF and ON, or resetting the C Controller module.

Event dropping

If the event are detected frequently, some events may be dropped. In this case, the event code (*HST LOSS*) which indicates that the event is dropped is displayed.

If the power is turned OFF or the C Controller module is reset while sampling event history, the status of the source module will be unknown. Therefore, the event code (*HST LOSS*) may be displayed and the source module is not displayed.

Displaying event history

The event history can be displayed using the menus of CW Configurator. For details on the operating procedures and how to read the displayed information, refer to the following manual. CW Configurator Operating Manual

Clearing event history

The event history can be cleared on the event history window. Once the event history is cleared, all the event history stored in the specified storage memory is deleted. For details on the operating procedures, refer to the following manual. CW Configurator Operating Manual

4 BASIC FUNCTIONS

4.12 RAS Function

Page 73

4.13 Security Function

GOT

Personal computer (Outside)

Personal computer

Internet/Intranet

[Protection for user assets in C Controller module] Prevents property loss, falsification, incorrect operation, and improper execution caused by an unauthorized access.

MELSEC iQ-R series system

User assets

This function prevents assets stored in a personal computer or a C Controller module in the MELSEC iQ-R series system from being stolen, falsified, operated incorrectly, and executed improperly due to unauthorized access from a third party. Apply an appropriate security function in accordance with the situation.

The security function is one of the methods for preventing unauthorized access (such as program or data corruption) from an external device. However, this function does not prevent unauthorized access completely. Incorporate measures other than this function if the C Controller system's safety must be maintained against unauthorized access from an external device. Mitsubishi Electric Corporation cannot be held responsible for any system problems that may occur from unauthorized access. Examples of measures for unauthorized access are shown below.

• Install a firewall.

• Install a personal computer as a relay station, and control the relay of send/receive data with an application program.

• Install an external device for which the access rights can be controlled as a relay station. (For details on the external devices for which access rights can be controlled, consult the network provider or equipment dealer.)

Individual identification information

The individual identification information of a C Controller module can be read with the C Controller module dedicated function (CCPU_GetIDInfo). By implementing an activation function with a user program, a user program, which does not run in C Controller modules with other individual identification information, can be created. For C Controller module dedicated functions, refer to the following manual. MELSEC iQ-R C Controller Module Programming Manual

4 BASIC FUNCTIONS

4.13 Security Function

Page 74

File access restriction

S R H

Indicates the hidden file attribute is specified.

Indicates the hidden file attribute is not specified.

Indicates the system file attribute is specified.

Indicates the system file attribute is not specified.

Indicates the read-only attribute is specified.

Indicates the read-only attribute is not specified.

Blank

A file attribute can be set for the files stored in the following types of memory. By setting a file attribute, access to a target file can be restricted, and falsification by an unauthorized user and data leakage to outside can be prevented.

• Program memory

• Data memory

• SD memory card

• USB Mass Storage Class-compliant device

• When an SD memory card or a USB Mass Storage Class-compliant device is inserted to a peripheral device other than a C Controller module (such as a personal computer), files to which the access restriction is set can be operated. If the access restriction is set for the file in the SD memory card and the USB Mass Storage Class-compliant device, take appropriate measures so that the SD memory card and the USB Mass Storage Class-compliant device cannot be removed from the C Controller module at will.

• Access restriction cannot be set for folders.

File access restriction setting

Change a file attribute handled in a C Controller module by using the attrib() command. A security password is required to change a file attribute. For details on the attrib() command, refer to the manual of VxWorks.

■Setting file attribute

Set a file attribute to a file to be restricted by using the attrib() command. The file attributes that can be handled in a C Controller module are as follows.

Attribute Description

S System file attribute File operations can be prohibited.

R Read-only attribute

H Hidden file attribute

*1 This attribute is not supported by the file access restriction function. However, if it is set, file deletion and file write can be prohibited. *2 When a file is opened by specifying a file name, the file can be operated. To prohibit file operations, make sure to set a system file

attribute.

File deletion and data write can be prohibited.

A file is not listed by using the ls command and it is not displayed at FTP connection.

■Checking file attribute

A file attribute which is set can be checked by using the attrib() command.

4 BASIC FUNCTIONS

4.13 Security Function

Page 75

Checking file access restriction status

Precautions

File access restriction status can be checked by executing the Shell command or the C Controller module dedicated function (CCPU_GetFileSecurity).

File access restriction status cannot be checked by using the script file (STARTUP.CMD).

Canceling/re-setting file access restriction

Change the file access restriction status by using the Shell command, the script file (STARTUP.CMD), or a user program. The security password set with CW Configurator is required.

■Changing system file attribute

For operating a file with a system file attribute attached, cancel the file access restriction temporarily with the C Controller module dedicated function (CCPU_ChangeFileSecurity). The canceled setting can be set again by setting the file access restriction with the C Controller module dedicated function (CCPU_ChangeFileSecurity) or resetting the C Controller module.

• When accessing a file to which a system file attribute is attached in the script file "STARTUP.CMD", cancel the access restriction in the script file. In this case, add the system file attribute to the script file in order to prevent the leakage of the password.

• Do not use the files with the system file attribute attached in the script file (STARTUP.CMD) in an SD memory card in order to prevent the leakage of password.

■When maintaining the safety against unauthorized access from external parties

To maintain the safety of a C Controller system against unauthorized access from external parties, take appropriate measures. Note the following when setting a security password to prevent the leakage of the security password.

• Avoid settings with only simple alphanumeric characters.

• Set a complex password with symbols.

■Settable characters for a security password

Characters that can be set are single byte alphanumeric characters and symbols. (Security password is case-sensitive.)

■If the security password has been forgotten

Initialize the C Controller module. For the procedure for initialization, refer to the following manual. MELSEC iQ-R C Controller Module User's Manual (Startup)

4 BASIC FUNCTIONS

4.13 Security Function

Page 76

Service settings

Window

Displayed items

Set the services for a C Controller module. By restricting the services, unauthorized access from other users can be prevented. A security password is required for changing service settings. (MELSEC iQ-R C Controller Module User's Manual (Startup))

[CPU Parameter]  [Service Settings]

Item Description Setting range Default

Service Settings WDB Required for the connection with CW Workbench. • Disable

Shell Required for the execution of commands.

Security password settings

DHCP Required when using a function which assigns the network settings

MELSEC data link function Required when performing MELSEC communication.

CW Configurator operation A service required for the operation of CW Configurator. If this

Memory card access Required when accessing a memory card.

Memory card script execution

Memory card parameter

execution

USB storage access Required when accessing USB devices. Enable

Password setting Set a security password. 8 to 16 characters password

automatically.

service is disabled, the following operations cannot be performed.

• Writing data to a C Controller module

• Reading data from a C Controller module

• Verifying data with a C Controller module

• Deleting data in a C Controller module

• CPU memory operation (Initialization)

Required when executing a script file "STARTUP.CMD" stored in a memory card.

Required when performing parameters stored in a memory card. Disable

• Enable

Enable

*1 When changing the service, write parameters to the data memory.

If the parameters are written to the memory card, the service setting is not changed.

4.13 Security Function

4 BASIC FUNCTIONS

Page 77

Password setting

Precautions

■Current password

Enter the current security password.

■New password and confirmation password

To change the security password, enter a new security password in "New Password" and "Confirm New Password".

■CW Configurator operation

When the CW Configurator operation is disabled, the parameters cannot be set. To enable the service, initialize C Controller module.

■Memory card parameter execution

To select an SD memory card as a target memory of the parameters, enable "Memory card parameter execution". ("Disable" is selected as a default.)

■Stopping multiple services

When the memory card access is disabled, the memory card script execution will be disabled as well.

Locked out

If the password authentication failed for several times, the password authentication will be denied (locked out) for a period of time. This prevents a brute force attack from unauthorized users.

Lockout time

The lockout time is as follows:

Number of password input error

1st time to 5th time 0 minute

6th time 1 minute

7th time 5 minutes

8th time 15 minutes

9th time or later 60 minutes

*1 Once the correct password is entered, the number of password input error will be cleared.

• The password input error will not be counted during lockout. Therefore, the lockout time will not be extended additionally by one minute even if the 7th input error occurs before one minute has passed since the 6th.

• When the security setting is configured using the C Controller module dedicated function (CCPU_ChangeFileSecurity), the password authentication will not be locked out.

Lockout time

4 BASIC FUNCTIONS

4.13 Security Function

Page 78

5 ACCESS FUNCTION USING NETWORK

Access source Access target

Access using Network module

MODULE

C Controller modules can perform data communication with a device connected to a network via a network module.

In a multiple CPU system configuration, the access via a network module which is controlled by another CPU is not available.

Available network modules

Network modules that can be controlled by C Controller module are as follows:

• CC-Link IE Controller Network module

• CC-Link IE Field Network module

• MELSECNET/H network module

• CC-Link module For module names, refer to the following manual. MELSEC iQ-R Module Configuration Manual

Network parameter

To use a network module, setting of "Module Parameter" of the particular Network module is required. To perform this settings, refer to the user's manual of the respective network modules.

5.1 Data Communication via Network

This section shows how to perform data communication using C Controller modules on each network.

Transmission type Description Communication method

Cyclic transmission Performs data communication

periodically between stations on a network using link devices.

Transient transmission Performs data communication with

another station when a communication request is issued. Communication with different network can also be performed.

Use link devices of the network module on the own station controlled by a C Controller module.

Use devices or buffer memory of a network module of another station via a network.

5 ACCESS FUNCTION USING NETWORK MODULE

5.1 Data Communication via Network

Page 79

5.2 Cyclic Transmission

(1)

(2)

(3)

Sending side Receiving side

C Controller module C Controller moduleNetwork

module

Network

module

Link

device

Link

scan

Link

device

This section shows the specifications of the cyclic transmission when using a C Controller module.

Data flow

The following shows the data flow at cyclic transmission.

(1) The sending side C Controller module writes data to a link device of the network module. (2) Data in the sending side link device is stored to the receiving side link device by link scan. (3) The receiving side C Controller module reads data from a link device of the network module.

■Link device

Link devices are used for sharing data in a network module with other stations on the network. The data in each station is updated every link scan. : Applicable, : Not applicable

Link device CC-Link IE Controller

Network

Link input LX 

Link output LY 

Link relay LB 

Link register LW 

Remote input RX 

Remote output RY 

Remote register RWw 

RWr 

Link special relay SB 

Link special register SW 

CC-Link IE Field Network

MELSECNET/H network

CC-Link

■Link scan and link scan time

In cyclic transmission, each station on the network transmits data in the specified send area of the own station within the defined time interval. The processing of data transmission of each station is called as link scan. The authority of data transmission is given to each station during every link scan. Time required for one-cycle of data transmission i.e. one link scan is called as link scan time. To perform link scan on the network, network range assignment settings are required.

■Network range assignment

Network range assignment settings are applicable to following networks:

Network name Setting item

CC-Link IE Controller Network "Network Range Assignment" of the control station

CC-Link IE Field Network "Network Configuration Settings" of the master station

MELSECNET/H network "Network Range Assignment" of the control station

CC-Link "Network Configuration Settings" of the master station

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 80

■Link device access function

(1)

(2)

(3)

C Controller module Network module Network module

User program

Link

refresh

Device

Link

scan

Link

device

Link

device

Direct access

Buffer memory access

Buffer

memory

The link devices can be accessed from a user program using function(s) of dedicated function library. The following figure shows how to access a link device in the controlled network module from a C Controller module.

Transmission type Description Data

(1) Access by link refresh A method to access devices of a C Controller module from a user

program. The device data communicates with link devices in a network module by link refresh.

(2) Direct access A method for direct access to link devices in a network module from a

user program.

(3) Buffer memory access A method to access the buffer memory in a network module from a user

program.

• Frequently used link device

• Link device that requires stationbased block data assurance setting

• Rarely used link device

Excluding rarely used link devices from link refresh device area and not using access by link refresh may reduce link refresh time.

■Available access methods

The available methods to access controlled network module from a C Controller module are shown below. : Applicable, : Not applicable

Transmission type CC-Link IE Controller

Network

Access by link refresh 

Direct access 

Buffer memory access 

CC-Link IE Field Network

MELSECNET/H network

CC-Link

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 81

Access by link refresh

C Controller module Network module Network module

User program Link

refresh

Device

Link

scan

Link

device

Link

device

This method is used to access the devices of a C Controller module from a user program using link refresh.

Data flow

The following figure shows the data flow of link refresh.

■Device

C Controller modules use the following devices to share the data with network modules.

Device Number of points Range of use

Internal relay M 61440 points M0 to 61439

Link relay B 655360 points B0 to 9FFFF

Data register D 4184064 points D0 to 4184063

Link register W 1048576 points W0 to WFFFFF

File register ZR 1835008 points ZR0 to 1835007

■Link refresh and its refresh cycle

The processing of data communication between devices of a C Controller module and link devices of a network module is called as link refresh. The link refresh is performed in every refresh cycle of a C Controller module. (Page 49 Fixed Cycle Processing Function)

■Parameter setting

When performing link refresh, set the following parameters.

• "Refresh Setting" and "Network Configuration Settings" of each network module

• Station-based block data assurance setting

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 82

■Refresh range

C Controller module Network module

Network Range Assignment

(Network Configuration Settings)

Device

Range set with "Network

Range Assignment" ("Network

Configuration Settings")

Link refresh

Range to be

refreshed

Station No.1

(Empty)

Link refresh

Station No.2

Setting range of refresh

(Refresh Setting)

(Empty)

Link refresh

Station No.3

Refresh is performed for the range set in "Refresh Setting" and "Network Range Assignment" ("Network Configuration Settings"). For the access by link refresh, specify the devices within the refresh range.

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 83

■Assurance of cyclic data consistency (station-based block data assurance)

Refresh cycleRefresh cycle Refresh cycle

Processing of C

Controller module

Link refresh Link refresh Link refresh Link refresh

Link scan

Link refresh time

Network module link deviceC Controller module device

Data assurance Station No.1

Data assurance

Station No.1

Station No.2

Data assurance

Station No.2

Link refresh

Station No.3

Data assurance

Station No.3

Station No.4

Data assurance

Station No.4

The station-based block data assurance function prevents overlapping of previous link scan data and new link scan data in one station.

Link scan is performed asynchronous to link refresh in the C Controller module. Therefore, if 32-bit or more cyclic data is handled, new data and old data may overlap due to the timing of link refresh.

When the station-based block data assurance is set, cyclic data consistency is assured in station units since the C Controller module does refresh cycle with a network module by handshaking.

For details of the station-based block data assurance function and the other data assurance functions, refer to the user's manual for each network module.

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 84

■User program functions

Precautions

C Controller module Network module

User program Device Link device

C Controller module dedicated functions MELSEC data link functions

Link refresh

The devices can be accessed from a user program using function(s) of dedicated function library.

The following shows the functions used to access devices by link refresh.

Dedicated function library Description

CCPU_WriteDevice To write data to devices and internal system devices of a C Controller module.

CCPU_ReadDevice To read data from devices and internal system devices of a C Controller module.

mdDevRstEx To reset (turn OFF) bit devices.

mdDevSetEx To set (turn ON) bit devices.

mdRandREx To read devices randomly.

mdRandRLabelEx To read labels or devices randomly.

mdRandWEx To write devices randomly.

mdRandWLabelEx To write labels or devices randomly.

mdReceiveEx To read devices in a batch.

mdSendEx To write devices in a batch.

When the station-based block data assurance function is enabled, access the devices using the CCPU_WriteDevice/ CCPU_ReadDevice function. If the mdSendEx/mdReceiveEx/mdRandWEx/mdRandREx/mdRandRLabelEx/ mdRandWLabelEx function is used, data inconsistency may occur.

■Devices specified with a function

Devices corresponding to each link device are shown below. In the dedicated function library, specify the device type with the device name defined for each function.

Link device Device C Controller module

dedicated function

Link input LX M, B, D, W, ZR Dev_CCPU_M

Link output LY

Link relay LB

Link register LW

Remote input RX

Remote output RY

Remote register RWw

RWr

Link special relay SB The access by link refresh is not allowed.

Link special register SW

Use the direct access.

Dev_CCPU_B Dev_CCPU_D Dev_CCPU_W Dev_CCPU_ZR

MELSEC data link function

DevM DevB DevD DevW DevZR

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 85

Direct access

C Controller module Network module Network module

User program

Link

device

Link

device

Link

scan

Direct access

This method is used for direct access to link devices in a network module from a user program.

Data flow

The following figure shows the data flow for direct access to link devices of a network module.

■User program functions

The following shows the functions used for direct access to network module link devices.

Dedicated function library Description

CCPU_WriteLinkDevice To write data to link devices of a network module directly.

CCPU_ReadLinkDevice To read data from link devices of a network module directly.

■Link devices specified with a function

Devices corresponding to each link device which can be specified with a function are shown below. In the dedicated function library, specify the device type with the device name defined for each function.

Link device C Controller module dedicated function

Link input LX Dev_LX

Link output LY Dev_LY

Link relay LB Dev_LB

Link register LW Dev_LW

Remote input RX Dev_LX

Remote output RY Dev_LY

Remote register RWw Dev_LW

RWr Dev_LW

Link special relay SB Dev_LSB

Link special register SW Dev_LSW

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 86

Buffer memory access

C Controller module Network module Network module

User program

Link

device

Link scan

Link

device

Buffer memory access

Buffer

memory

This method is used to access the buffer memory of a network module from a user program.

Data flow

The following figure shows the data flow to access buffer memory of a network module.

■User program functions

The following shows the functions used to access buffer memory of a network module.

Dedicated function library Description

CCPU_ToBuf To write data to the CPU buffer memory and intelligent function module buffer memory in the module on the specified

CCPU_ToBuf_ISR

CCPU_FromBuf To read data from the CPU buffer memory and intelligent function module buffer memory in the module on the specified

CCPU_FromBuf_ISR

module position.

■Link devices specified with a function (buffer memory)

The following link devices are assigned to each specific address in the buffer memory. In the dedicated function library, specify the device type with the device name defined for each function.

Link device C Controller module dedicated function

Remote input RX Dev_SPB

Remote output RY

Remote register RWw

RWr

Link special relay SB

Link special register SW

When using a C Controller module dedicated function, specify the offset of the buffer memory. For details of buffer memory addresses for each link device, refer to the user's manual of the network module used.

5 ACCESS FUNCTION USING NETWORK MODULE

5.2 Cyclic Transmission

Page 87

5.3 Transient Transmission

(1)

(2)

(3)

C Controller module

(Sending side)

Network

module

Network

module

C Controller module

(Receiving side)

Channel 1

User program

Channel 2 Channel 2

User program

Channel 3 Channel 4

Channel 5

Channel 8 Channel 8

Network No.1

This section shows transient transmission using a C Controller module. There are two methods available for transient transmission: message transmission using the channel of the network module which is controlled by a C Controller module, and direct access to devices of another station.

Message communication

This method is used to read/write data using the channel of a controlled network module from a C Controller module. The message communication function allows data communication similar to link dedicated instructions i.e. SEND/RECV instructions.

Data flow

The following figure shows the data flow for message communication.

(1): The sending side C Controller module sends data by specifying the channel used in the own station and the channel used in the target station with the message send function of a user program. (2): From the sending side channel, data is transmitted to the receiving side channel. (3): The receiving side C Controller module (another station) reads messages from the receiving side channel with the message receive function of a user program.

• The message communication function can be used even if CPU module on sending station or receiving station is other than C Controller module. For the target CPU module, use the SEND/RECV link dedicated instruction or a function equivalent to it.

• If the data is transmitted with acknowledge to be received on the same channel of receiving station, it is necessary to transmit next data only after acknowledgement of previously sent data is received i.e. receiving station has read the previously sent data using message receive function (or RECV instruction). An error will occur if the sending station transmits data on the same channel of the receiving station before the acknowledgement is received i.e. data on the receiving station has not been read. In case of an error, retry data transmission.

5 ACCESS FUNCTION USING NETWORK MODULE

5.3 Transient Transmission

Page 88

■Channel

Each network module has a data area used for message communication, which is called "channel". By using multiple channels, simultaneous access from the host station to other stations, or simultaneous reading and writing to one module are allowed. The number of channels differ depending on network types.

■User program functions

The following shows the functions used for message communication.

Dedicated function library Description

CCPU_DedicatedGInst To execute dedicated instructions categorized as 'G' or 'GP'.

CCPU_DedicatedJInst To execute dedicated instructions categorized as 'J' or 'JP'.

mdSendEx To send messages.

mdReceiveEx To receive messages.

Access to devices on another station

This method is used for direct access to devices on another station via a network from a user program. A network module on another station and its control CPU module can be accessed.

User program functions

Devices on another station can be accessed from a user program using C Controller module dedicated functions.

Dedicated function library Description

mdDevRstEx To reset (turn OFF) bit devices.

mdDevSetEx To set (turn ON) bit devices.

mdRandREx To read devices randomly.

mdRandWEx To write devices randomly.

mdReceiveEx To read devices in a batch.

mdSendEx To write devices in a batch.

■Accessible range of function

For the accessible range on each network, refer to the following manual. MELSEC iQ-R C Controller Module Programming Manual

Devices specified with a function

■Access to link devices of another station

To access a link device of another station, specify a direct link device (another station side).

Link device MELSEC data link function

CC-Link IE Controller Network

Link input LX DevLX(1) to DevLX(255)  DevLX(1) to DevLX(255) 

Link output LY DevLY(1) to DevLY(255)  DevLY(1) to DevLY(255) 

Link relay LB DevLB(1) to DevLB(255)  DevLB(1) to DevLB(255) 

Link register LW DevLW(1) to DevLW(255)  DevLW(1) to DevLW(255) 

Remote input RX  DevLX(1) to DevLX(255) 

Remote output RY  DevLY(1) to DevLY(255) 

Remote register RWw  DevLW(1) to DevLW(255) 

RWr  DevLW(1) to DevLW(255) 

Link special relay SB DevLSB(1) to

DevLSB(255)

Link special register SW DevLSW(1) to

DevLSW(255)

CC-Link IE Field Network

DevLSB(1) to DevLSB(255)

DevLSW(1) to DevLSW(255)

MELSECNET/H network

DevLSB(1) to DevLSB(255)

DevLSW(1) to DevLSW(255)

CC-Link Network



5 ACCESS FUNCTION USING NETWORK MODULE

5.3 Transient Transmission

Page 89

■Access to the buffer memory of another station

To access the buffer memory of another station, specify a module access device or an intelligent function module device.

Link device MELSEC data link function

Remote input RX DevSPG(0) to DevSPG(255)

Remote output RY

Remote register RWw

RWr

Link special relay SB

Link special register SW

■Access to a control CPU module of another station

For devices to be specified in a user program, refer to the following manual. MELSEC iQ-R C Controller Module Programming Manual

5 ACCESS FUNCTION USING NETWORK MODULE

5.3 Transient Transmission

Page 90

5.4 Access Function of Each Network Module

CC-Link IE Controller

Network module

C Controller module

Device

· link relay

· link register

User program

Link device

Link

refresh

Access to devices

Link device

The network module access function transmits data to the devices on the network via the network module controlled by a C Controller module.

CC-Link IE Controller Network module

The following shows the functions to transmit data via a CC-Link IE Controller Network module.

Available access methods

The following access methods are available.

Transmission type Access method

Cyclic transmission Access by link refresh

Direct access

Transient transmission Message communication

Access to devices on another station

Access by link refresh

This method is used to access devices of a C Controller module from a user program using link refresh. Data in the device is transmitted cyclically to another station by reading from/writing to link devices of a network module by link refresh.

*1 Link refresh cannot be performed for SB/SW. Use the direct access.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 91

Direct access

CC-Link IE Controller

Network module

C Controller module

Link device

Direct access

User program

C Controller module on other

station (Receiving side)

C Controller module

(Sending side)

CC-Link IE Controller

Network module

CC-Link IE Controller

Network module

Channel 1

Channel 2

User program

Channel 3

Channel 4

Channel 5

Channel 6

Channel 7

Channel 8

Network No.1

User program

This method is used for direct access to devices in a network module from a user program. The link device data in the network module is transmitted cyclically to another station.

Message communication

A message communication can be performed via a CC-Link IE Controller Network module controlled by a C Controller module.

■Number of channels

For CC-Link IE Controller Network module, up to eight channels can be used for message communication.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 92

CC-Link IE Field Network module

RWr

RWw

CC-Link IE Field Network module

C Controller module

Device

· link relay

· link register

User program

Link device

Link

refresh

Access to devices

Link device

The following shows the functions to transmit data via a CC-Link IE Field Network module.

Available access methods

The following access methods are available.

Transmission type Access method

Cyclic transmission Access by link refresh

Direct access

Buffer memory access

Transient transmission Message communication

Access to devices on another station

Access by link refresh

*1 Link refresh cannot be performed for SB/SW. Use the direct access or buffer memory access.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 93

Direct access

RWr

RWw

CC-Link IE Field

Network module

C Controller module

User program

Link device

Direct access

RWr

RWw

CC-Link IE Field Network module

C Controller module

Buffer memoryUser program

Link device

Buffer memory access

This method is used for direct access to devices in a network module from a user program. The link device data in the network module is transmitted cyclically to another station.

Buffer memory access

This method is used to access the buffer memory of a network module from a user program. The data in the buffer memory is refreshed with link devices and transmitted cyclically to another station.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 94

Message communication

C Controller module on other

station (Receiving side)

C Controller module

(Sending side)

CC-Link IE Field Network

module(Station No.4)

CC-Link IE Field Network

module(Station No.5)

Channel 1

Channel 2

User program User program

Network No.1

A message communication can be performed via a CC-Link IE Field Network module controlled by a C Controller module.

■Number of channels

For CC-Link IE Field Network module, up to two channels can be used for message communication.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 95

MELSECNET/H network module

C Controller module

Device

· link relay

· link register

User program

Link device

Link

refresh

Access to devices

Link device

The following shows the functions to transmit data via a MELSECNET/H network module.

Available access methods

The following access methods are available.

Transmission type Access method

Cyclic transmission Access by link refresh

Direct access

Transient transmission Message communication

Access to devices on another station

Access by link refresh

*1 Link refresh cannot be performed for SB/SW. Use the direct access.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 96

Direct access

C Controller module

Link device

Direct access

User program

MELSECNET/H

network module

C Controller module on other

station (Receiving side)

C Controller module

(Sending side)

Channel 1

Channel 2

User program User program

Channel 3

Channel 4

Channel 5

Channel 6

Channel 7

Channel 8

Network No.1

MELSECNET/H network module

This method is used for direct access to devices in a network module from a user program. The link device data in the network module is transmitted cyclically to another station.

Message communication

A message communication can be performed via a MELSECNET/H network module controlled by a C Controller module.

■Number of channels

For MELSECNET/H network module, up to eight channels can be used for message communication.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 97

CC-Link module

RWr

RWw

C Controller module CC-Link module

Buffer memoryUser program

Link device

Buffer memory access

The following shows the functions to transmit data via a CC-Link module.

Available access methods

The following access methods are available.

Transmission type Access method

Cyclic transmission Buffer memory access

Transient transmission Access to devices on another station

Buffer memory access

This method is used to access the buffer memory of a network module from a user program. The data in the buffer memory is refreshed with link devices and transmitted cyclically to another station.

5 ACCESS FUNCTION USING NETWORK MODULE

5.4 Access Function of Each Network Module

Page 98

5.5 Processing Time

This section shows the processing time of the cyclic transmission related to network module access. For the processing time of the transient transmission, refer to the processing time of each function.

Link refresh time

The following shows the processing time of link refresh.

CC-Link IE Controller Network

The processing time when using CC-Link IE Controller Network is as follows.

• β

: Total link refresh time (sending side)

• β

: Total link refresh time (receiving side)

• KM1, KM2: Constant

Network module mounting position KM1 KM2

Main base unit 1.0 0.36 × 10

Extension base unit 1.0 0.97 × 10

• LB: Total number of points of link relays to be refreshed

• LX: Total number of points of link inputs to be refreshed

• LY: Total number of points of link outputs to be refreshed

• LW: Total number of points of link registers to be refreshed

*1 This is the total number of points of link devices set for the setting range of "Refresh Setting" and "Network Range Assignment"

("Network Configuration Settings"). The number of points assigned to a reserved station is not included.

Link refresh time can be calculated with the following formula depending on the number of assigned points of link devices.

Time Formula

Link refresh time (ms) βT, βR = KM1 + KM2 × {((LB + LX + LY) ÷ 16) + LW}

-3

CC-Link IE Field Network

The processing time when using CC-Link IE Field Network is as follows.

• β

: Total link refresh time (sending side)

• β

: Total link refresh time (receiving side)

• KM1, KM2: Constant

Network module mounting position KM1 KM2

Main base unit 1.0 0.41 × 10

Extension base unit 1.0 0.99 × 10

• RX: Total number of points of link inputs to be refreshed

• RY: Total number of points of link outputs to be refreshed

• RWw, RWr: Total number of points of link registers to be refreshed

*1 This is the total number of points of link devices set for the setting range of "Refresh Setting" and "Network Range Assignment"

("Network Configuration Settings"). The number of points assigned to a reserved station is not included.

Link refresh time can be calculated with the following formula depending on the number of assigned points of link devices.

Time Formula

Link refresh time (ms) βT, βR = KM1 + KM2 × {((RX + RY) ÷ 16) + RWw + RWr}

-3

5 ACCESS FUNCTION USING NETWORK MODULE

5.5 Processing Time

Page 99

MELSECNET/H network

The processing time when using MELSECNET/H network is as follows.

• β

: Total link refresh time (sending side)

• βR: Total link refresh time (receiving side)

• KM1, KM2: Constant

Network module mounting position KM1 KM2

RQ extension base unit 65 0.41 × 10

Q extension base unit 65 0.92 × 10

• LB: Total number of points of link relays to be refreshed

• LX: Total number of points of link inputs to be refreshed

• LY: Total number of points of link outputs to be refreshed

• LW: Total number of points of link registers to be refreshed

*1 This is the total number of points of link devices set for the setting range of "Refresh Setting" and "Network Range Assignment"

("Network Configuration Settings"). The number of points assigned to a reserved station is not included.

-3

Link refresh time can be calculated with the following formula depending on the number of assigned points of link devices.

Time Formula

Link refresh time (ms) βT, βR = KM1 + KM2 × {((LB + LX + LY) ÷ 16) + LW}

CC-Link Network

The processing time when using CC-Link Network is as follows.

• β

: Total link refresh time (sending side)

• β

: Total link refresh time (receiving side)

• KM1, KM2: Constant

Network module mounting position KM1 KM2

Main/extension base unit 1.0 0.36 × 10

• RX: Total number of points of link inputs to be refreshed

• RY: Total number of points of link outputs to be refreshed

• RWw, RWr: Total number of points of link registers to be refreshed

*1 This is the total number of points of link devices set for the setting range of "Refresh Setting" and "Network Range Assignment"

("Network Configuration Settings"). The number of points assigned to a reserved station is not included.

Link refresh time can be calculated with the following formula depending on the number of assigned points of link devices.

Time Formula

Link refresh time (ms) βT, βR = KM1 + KM2 × {((RX + RY) ÷ 16) + RWw + RWr}

-3

5 ACCESS FUNCTION USING NETWORK MODULE

5.5 Processing Time

Page 100

Refresh cycle

The following shows how to calculate the refresh cycle. For the setting method of refresh cycle, refer to the following section. Page 49 Fixed Cycle Processing Function

How to decide the refresh cycle

Follow the procedure below to decide the refresh cycle.

1. Calculation of the total link refresh time

2. Preliminary decision of the refresh cycle

3. Pre-operation of the C Controller system

4. Decision of the refresh cycle

■Calculation of the total link refresh time

The total link refresh time is equal to the sum of the link refresh time of all of the network modules controlled by a C Controller module. The total link refresh time of a C Controller system in operation can be checked with the special registers (SD526 to SD531). For calculation method of link refresh time for each network module, refer to the following section. Page 96 Link refresh time

■Preliminary decision of the refresh cycle

Set the value which satisfies the following relational expression to the refresh cycle and total link refresh time.

• Refresh cycle > Total link refresh time

Pay attention to the processing of a user program so that the refresh cycle meets the system specifications of the C Controller system.

■Pre-operation of the C Controller system

Confirm whether the C Controller system operates correctly by the refresh cycle decided preliminarily. Check the following at the time of pre-operation.

Check item Description

Any error has been occurred on the C Controller module or not.

The operation of the C Controller system meets the system specifications or not.

• Take the corrective actions shown below in order for the system to operate correctly when the C Controller system operates abnormally or the processing performance of the user program is lowered.

Corrective action Description

Increase the refresh cycle setting value.

Reduce the setting number of refresh points.

Review the user program. Review the processing contents and task structure, and correct them to meet the system specifications and the

If the processing of the C Controller module has not been completed within the refresh cycle, an error, "Refresh cycle exceeded (1846H)" occurs.

Check that the C Controller system operates correctly. If the operation of the user program is suspended more frequently than its normal operation time, the system specification may not be met.

Set the refresh cycle again so that the following relational expression is met, by using the link refresh time (maximum value) as an indication.

• Measured value of link refresh time (maximum value) < Refresh cycle

Review the number of refresh points in refresh parameter settings.

processing performance.

5 ACCESS FUNCTION USING NETWORK MODULE

5.5 Processing Time

Mitsubishi Electric MELSEC iQ-R C R12CCPU-V User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

SAFETY PRECAUTIONS

CONDITIONS OF USE FOR THE PRODUCT

CONSIDERATIONS FOR USE

INTRODUCTION

CONTENTS

RELEVANT MANUALS

TERMS

PART 1 PROGRAMMING

1.2 Initial Processing

1.3 I/O Access Timing

1 EXECUTING PROGRAMS

1.1 Execution Order

2 OPERATION PROCESSING IN C Controller Module

2.1 Operation Processing Depending on Operating Status

2.2 Operation Processing at Momentary Power Failure

Program memory

CPU buffer memory

System memory

3 MEMORY CONFIGURATION OF C Controller Module

3.1 Memory Configuration

Device/label memory

Data memory

SD memory card

USB Mass Storage Class-compliant device

3.3 Memory Life

3.2 Memory Operation

Drive names and file systems

File type and storage destination memory

3.4 Files

File and folder configuration

PART 2 FUNCTIONS

Monitoring time setting and reset

4 BASIC FUNCTIONS

4.1 Program Monitoring (WDT) Function

Timeout of watchdog timer

Clock data setting

4.2 Clock Function

Time zone setting

Daylight saving time function

Remote RUN/STOP

4.3 Remote Operation Function

Remote PAUSE

Remote RESET

Remote operation and operating status of a C Controller module

4.4 Device Access Function

Factor of interrupt pointer number

4.5 Interrupt Function to C Controller Module

Interrupt procedure

Setting a fixed cycle processing interval

Checking the interval

4.6 Fixed Cycle Processing Function

4.7 Inter-module Synchronization Function

Fixed cycle synchronization function

Parameter setting

4.8 Label Communication Function

4.9 Data Analysis Function

4.10 Output Mode Setting Function from STOP to RUN

Boot operation

4.11 Memory Card Function

Enable/disable the use of file/data on memory card

Self-diagnostic function

4.12 RAS Function

Error clear function

Event history function

Individual identification information

4.13 Security Function

File access restriction

Service settings

Locked out

5 ACCESS FUNCTION USING NETWORK MODULE

5.1 Data Communication via Network

5.2 Cyclic Transmission

Access by link refresh

Direct access

Buffer memory access

Message communication