• SAFETY PRECAUTIONS • (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. The instructions given in this manual are concerned with this product. For the safety instructions of the programmable controller system, please read the user's manual of the CPU module to use.
[Design Precautions] ! WARNING • Do not write data into the "system area" of the buffer memory of intelligent function modules. Also, do not use any "use prohibited" signals as an output signal to an intelligent function module from the CPU module. Writing data into the "system area" or outputting a signal for " use prohibited" may cause a programmable controller system malfunction.
[Wiring Precautions] ! WARNING • Shut off the external power supply for the system in all phases before 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 product before turning it on for operation. Failure to do so may result in electric shock. [Wiring Precautions] ! CAUTION • Use applicable solderless terminals and tighten them within the specified torque range.
[Startup/Maintenance Precautions] ! WARNING • Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction. • Shut off the external power supply for the system in all phases before cleaning the module or retightening the terminal block screw. Failure to do so may result in electric shock. [Startup/Maintenance Precautions] ! CAUTION • Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
[Operation Precautions] ! CAUTION • When controlling a running programmable controller (especially, changing data, program modification, and operation status change) from an external device such as a personal computer connected to an intelligent function module, read the relevant user's manual carefully and ensure the safety before the operation. Incorrect data change, program modification, and status control may cause malfunction of the system, mechanical damage, or accidents.
• 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.
INTRODUCTION Thank you for purchasing the Mitsubishi MELSEC-L series programmable controller. This manual describes the functions of the LJ71C24 and LJ71C24-R2 serial communication modules (hereinafter referred to as the C24) and programming. Before using the equipment, please read this manual and the related manuals carefully to develop full familiarity with the functions and performance of the MELSEC-L series programmable controller you have purchased, so as to ensure correct use.
COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES (1) Method of ensuring compliance To ensure that Mitsubishi programmable controllers maintain EMC and Low Voltage Directives when incorporated into other machinery or equipment, certain measures may be necessary. Please refer to one of the following manuals.
RELEVANT MANUALS Basic specifications, functions, and usage of special functions can be confirmed in this manual. In addition, use the following manuals according to the intended use.
(4) Operating manual Manual number (model code) Manual name GX Works2 Version1 Operating Manual (Common) System configuration, parameter settings, and online operations (common to Simple project and Structured project) of GX Works2 SH-080779ENG (13JU63) (Sold separately) GX Works2 Version1 Operating Manual (Intelligent Function Module) System configuration, parameter settings, and online operations (common to Simple project and Structured project) of GX Works2 SH-080921ENG (13JU69) (Sold separately)
CONTENTS SAFETY PRECAUTIONS..............................................................................................................................A- 1 CONDITIONS OF USE FOR THE PRODUCT .............................................................................................A- 6 INTRODUCTION............................................................................................................................................A- 7 COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES...............
6.3.5 Enabling or disabling echo back of the RS-422/485 interface........................................................ 6-19 6.4 Individual Station Test............................................................................................................................. 6-21 6.4.1 ROM/RAM/switch test...................................................................................................................... 6-22 6.4.2 Self-loopback test......................................................
10.1.4 How to detect and check the reception errors ............................................................................ 10-14 10.1.5 Receive data clear ....................................................................................................................... 10-17 10.1.6 Received data count and receive complete code settings ......................................................... 10-23 10.2 Sending Data to the External Device ..........................................................
14 MAINTENANCE AND INSPECTION 14.1 Inspection Items .................................................................................................................................. 14- 1 14.2 When Replacing Modules................................................................................................................... 14- 2 14.2.1 Procedure of C24 replacement and re-registration of data ........................................................ 14- 2 15 TROUBLESHOOTING 15.
APPENDICES Appendix 1 Buffer Memory ......................................................................................................................App.- 1 Appendix 2 How to Confirm the Serial No. and Function Version..........................................................App.-21 Appendix 3 Differences between L Series C24 and Q Series C24........................................................App.-22 Appendix 3.1 Specification comparisons.............................................................
TERMS Unless otherwise specified, this manual uses the following terms.
Term Description Predefined protocol support function A function available in GX Works2 and GX Configurator-SC (Predefined protocol support function), which includes: • Registration of the protocol appropriate to each target device • Writing protocol setting data to or reading them from the flash ROM of the C24 • Debug support function Nonprocedural protocol A user's communication procedure and one of the data communication functions for communicating any data between the CPU module and a target device
PACKING LIST The following items are included in the package of the C24. Before use, check that all the items are included.
(2) LJ71C24-R2 Before Using the Product LJ71C24-R2 A - 19 A - 19
1 SERIAL COMMUNICATION MODULE FUNCTIONALITY 1 SERIAL COMMUNICATION MODULE FUNCTIONALITY The C24 performs data communication with another device connected by an RS-232 or RS-422/485 line, using any of the following four protocols. Through a modem or terminal adapter, a public line (analog/digital) can be used for data communication with a remotely located device.
1 SERIAL COMMUNICATION MODULE FUNCTIONALITY (2) Predefined protocol Data can be transferred in accordance with a protocol for the external device. The same data communication can be performed in the nonprocedural protocol explained in (3). However, the following shows the convenient functions when comparing this protocol and the nonprocedural protocol. • Sequence programs can be reduced since the GX Works2 predefined protocol support function allows simple protocol setting.
1 SERIAL COMMUNICATION MODULE FUNCTIONALITY (3) Nonprocedural protocol Fixed or variable length messages can be received in accordance with the external device specifications. Nonprocedural protocol enables communication between an external device and the CPU module by freely setting the data format and transmission control procedures. It is used for the data communication using the protocols of external devices, such as measuring instruments, barcode readers, etc.
2 PART NAMES 2 PART NAMES This chapter shows part names of the C24. LJ71C24 5) 2 1) 2) 3) 6) 4) 5) LJ71C24-R2 5) 1) 2) 2) 6) 4) No. 1) 2-1 5) Name Description Indicator LED Indicator LED (For details, refer to (1).
2 PART NAMES (1) Indicator LED 2 Applicable protocol CH LED Description On RUN Normal operation — ERR. Error ( CH1 1) NEU. Neutral status on the ( 3) CH1 side ( 2) SD Transmission status RD Reception status SD RD Transmission status Reception status Off Normal — Faulty or reset Error has occurred — Normal Waiting for MC protocol command message to be received — MC protocol command message being processed Data being transmitted Data being received NEU.
3 SPECIFICATIONS 3 SPECIFICATIONS This chapter explains the general specifications, performance specifications, function list, and I/O signals. 3.1 General Specifications For the general specifications of C24, refer to "Safety Guidelines", the manual supplied with the CPU module or head module. 3.2 Performance Specifications 3 The following shows the C24 performance specifications. For the transmission specifications when communicating via the modem function, refer to both Section 3.2.
3 SPECIFICATIONS (Continued from preceding page) Model name Item Error detection LJ71C24 LJ71C24-R2 Parity check Selected for all protocols and when this check is enabled, ODD or EVEN is selected by a parameter. Sum check code For the MC or bidirectional protocol, selected by a parameter. For the predefined protocol, whether or not a sum check code is needed depends on the selected protocol. For the nonprocedural protocol, selected in the user frame.
3 SPECIFICATIONS 3.2.1 Number of parameter settings For the parameter settings of the initial setting and auto refresh setting of the C24, set parameters (including the parameters for other intelligent function modules) not to exceed the maximum number of parameters that can be set for a CPU module or the head module. For the maximum number of parameters that can be set for a CPU module or the head module (maximum number of parameter settings), refer to the following manual.
3 SPECIFICATIONS 3.3 Function List 3.3.1 Basic functions The following shows the basic functions of the C24. Function Description Reference Executes batch read/write in bit/word units. Reading/writing from/to the device memory of the CPU module Executes monitoring of device memory. Executes batch read/write of multiple blocks. Executes read/write by extension designation. Accesses other stations via network system.
3 SPECIFICATIONS 3.3.2 Additional functions The following shows the additional functions of the C24. The following abbreviations appear in the protocol column of the function list. MC: MC protocol Pd: Predefined protocol Non: Nonprocedural protocol Bi: Bidirectional protocol ( : Applicable protocol) Protocol Function Description Reference MC Communication with ASCII code Pd Executes the communication with an A compatible 1C frame. Executes the communication with a QnA compatible 4C frame.
3 SPECIFICATIONS ( Function Transmission control Description DC code control (including Xon/Xoff control) This control notifies the availability of data reception in the host station and the effective range of sent/received data to external devices, using the data for transmission control in the C24. DTR/DSR control This control notifies the availability of data reception in the host station to external devices, using the ER(DTR)/DR(DSR) signal of the RS-232 interface.
3 SPECIFICATIONS 3.4 List of Input/Output Signals This section describes the input/output signals of the C24. The following I/O signal assignment is based on the case where the start I/O No. of the C24 is "0000". Device numbers starting with X indicate input signals from the C24 to the CPU module. Device numbers starting with Y indicate output signals from the CPU module to the C24. The following table lists the input/output signals for the CPU module.
3 SPECIFICATIONS Device number Signal description X1A CH1 Global signal ON: Output instructed X1B CH2 Global signal ON: Output instructed X1C System setting default completion ON: Completed ON: Ready Reference Device number MELSEC-Q/L MELSEC Communication Protocol Reference Manual Y1A — Y1C Section 9.
4 PROCEDURES PRIOR TO OPERATION 4 PROCEDURES PRIOR TO OPERATION This chapter explains the procedures required before starting the operation. 4 1 The same communication is available using the predefined protocol. By the Predefined protocol, programs can be created easily, and the number of steps can be drastically reduced.
4 PROCEDURES PRIOR TO OPERATION MEMO 4 4-2 4-2
5 SYSTEM CONFIGURATION 5 SYSTEM CONFIGURATION This chapter explains the system configuration and the number of applicable modules of the C24. 5.1 Overall Configuration (1) When installing the C24 to the CPU module Display unit (optional) Power supply module RS-232 adapter (optional) CPU module LJ71C24 END cover 5 1 1: For the RS-232 adapter, refer to the following.
5 SYSTEM CONFIGURATION (3) System examples (a) Connecting two external devices to the C24 Connect external devices such as a GOT and a barcode reader to one C24. Data can be exchanged between a GOT and a device such as a barcode reader via the C24. 1: For the RS-232 adapter, refer to the following manual.
5 SYSTEM CONFIGURATION 5.2 Applicable Systems (1) Applicable CPU modules and No. of modules Refer to the following. MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) MELSEC-L CC-Link IE Field Network Head Module User's Manual (2) Supported software packages (a) Setting and monitoring tools Refer to the following.
5 SYSTEM CONFIGURATION 5.3 Systems that can be Configured and Functions The following describes the system configurations and available functions when using the C24. (1) System configurations System configurations (combinations of the C24 and external device) for data communication are shown below.
5 SYSTEM CONFIGURATION (c) External device and C24 with 1:n system configuration (d) External device and C24 with m:n system configuration RS-485 RS-232 RS-485 RS-485 5-5 RS-485 RS-485 5-5
5 SYSTEM CONFIGURATION (2) Correspondence between the data communication functions and system configurations The following shows system configurations that can use the data communication functions of the C24.
5 SYSTEM CONFIGURATION (d) Communication using the bidirectional protocol ( : Available, Function System configuration (External device: C24) 1:1 Data transmission/receiving n:1 1:n : Not available) Reference m:n Chapter 11 Reading received data using interrupt programs Sending/receiving ASCII data using ASCII-BIN conversion User's Manual (Application) In general, if data communication is performed using a system configuration of other than 1:1 connection mode, the following points should be well
6 SETTING AND WIRING 6 SETTING AND WIRING This chapter explains the setting and wiring methods in the system for using the C24. 6.1 Installation Environment and Position of the Module For the installation environment and position of the module, refer to the following manual. MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) MELSEC-L CC-Link IE Field Network Head Module User's Manual 6.1.1 Handling precautions When using the C24, note the following points.
6 SETTING AND WIRING 6.2 External Wiring with RS-232 Interface This section explains the specifications of RS-232 and how to connect with external devices. 6.2.1 RS-232 connector specifications The following shows the specifications of the RS-232 connector that connects the C24 to an external device. (1) The control signals are described below. (The pin numbers of the connector are enclosed in parentheses.) 1) CD(DCD) signal (1) • The C24 operates according to the setting of the CD terminal check.
6 SETTING AND WIRING 4) ER(DTR) signal (4) • When communicating data using the nonprocedural protocol, the C24 turns this signal on or off (on when data is receivable) depending on the amount of unused memory in the OS area allocated for receive data storage, if DTR/DSR control is being performed. Read the receive data from the sequence program, as the receive data is stored in the OS area when the ER(DTR) signal is OFF. If DTR/DSR control is not performed, the ER(DTR) signal is always ON.
6 SETTING AND WIRING (2) The ON and OFF states of each signal indicate the following conditions: (Output side) (Input side) ON 5 V to 15 V DC, 3 V to 15 V DC OFF –15 V to –5 V DC, –15 V to –3 V DC (3) Interface connector The following RS-232 interface connector is used for the C24. • DDK Ltd. 9-pin D-sub (female) screw type (Mating screw M2.6) 17L-10090-27 (D9AC) (-FA) The following table shows the suitable connector shell for the RS-232 connector.
6 SETTING AND WIRING REMARKS (1) Confirmation of RS-232 control signal status Each status of the control signals, ER(DTR), DR(DSR), RS(RTS) and CD(DCD) can be confirmed in RS-232 control signal status (address: 254H/264H). Buffer memory address Bit position CH1 side CH2 side 264H 254H b0 RS(RTS) b1 DR(DSR) b2 ER(DTR) b3 CD(DCD) b4 CS (CTS) b5 CI(RI) b6 to b15 — (2) Designation of RS and DTR signal status Normally, the ON/OFF status of the RS(RTS) or ER(DTR) signal is set by the C24.
6 SETTING AND WIRING 6.2.2 RS-232 cable specification Use a cable conforming to the RS-232 standard with 15m or shorter in length. Diameter Type Material Temperature rating 28 to 24AWG Stranded Copper 60°C or more [Recommended cable] • Oki Electric Cable Co., Ltd. 7/0.127 P HRV-SV ( : Specify the number of pairs. For 13 pairs 7/0.
6 SETTING AND WIRING 6.2.3 Connecting the RS-232 interface (full-duplex communication) The following shows the connection precautions and connection examples when using the C24 RS-232 interface for full-duplex communication. (1) Connection precautions (a) Refer to Appendix 11 for the bend radius of the connection cable. (b) Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100mm between them.
6 SETTING AND WIRING (2) Connection examples (a) Connection example with an external device capable of turning on and off the CD(DCD) signal (Pin No. 1) The CD terminal check setting is set according to the specification of the external device. When wiring shown above, DTR/DSR control or DC code control are available. (b) Connection example with an external device not capable of turning on and off the CD(DCD) signal (Pin No.
6 SETTING AND WIRING 6.3 External Wiring with RS-422/485 Interface This section explains the specifications of RS-422/485 and how to connect them with external devices. 6.3.1 RS-422/485 terminal block specifications The following shows the specifications of the RS-422 connector and RS-422/485 terminal block that connect to an external device.
6 SETTING AND WIRING 6.3.2 RS-422/485 cable specifications The following shows the RS-422/485 cable specification. (1) Use a cable that satisfies the following specification for the RS-422/485 cable (cable to connect the C24 terminal block) within 1200m in length. Item Description Cable type Shielded cable Number of pairs 3 Conductor resistance (20 °C) Insulation resistance /km or less 88.
6 SETTING AND WIRING 6.3.3 Connection method for the RS-422/485 interface The following explains the connection precautions and examples when using the C24 RS-422/485 interface. (1) Connection precautions (a) Refer to Appendix 11 for the bend radius of the connection cable. (b) Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100mm between them. Failure to do so may result in malfunction due to noise.
6 SETTING AND WIRING (g) Terminating resistors must be set (or connected) for both terminal stations on the line. On the C24 side, connect the terminating resistor (included with the C24) according to the specifications of the external device. On the external device side, connect, or set a terminating resistor according to the instruction manual of the external device. (C24-side terminal resistor) • For RS-422 communications, connect the terminating resistor of "330 1/4 W".
6 SETTING AND WIRING (2) Connection examples (a) External device and C24 with 1:1 system configuration Terminating resistor R C24 External device Signal name Signal name SDA RDA SDB RDB RDA RDB SDA SG RSA Terminating resistor R SDB FG RSB FG CSA CSB SG FG (b) External device and C24 with 1:n (multidrop) system configuration 1) Connection example 6 - 13 6 - 13
6 SETTING AND WIRING 2) Connection example 2 External device C24 1) C24 2) SDA SDA SDA SDA SDB SDB SDB SDB RDA RDA RDA RDA RDB RDB RDB RDB SG SG SG SG R R FG FG R R FG FG RS-422/485 cable RS-422/485 cable C24n RS-422/485 cable R Terminating resistor (c) External device and C24 with n:1 (multidrop) system configuration External device 1) R C24 1) External device 2) C24n SDA SDA SDA SDA SDB SDB SDB SDB RDA RDA RDA RDA RDB RDB RDB SG SG SG FG FG RS-422/
6 SETTING AND WIRING (d) External device and C24 with m:n (multidrop) system configuration 1) Connection example 1 External device 2) External device 1) RS-232 SD SD RD RS-232 RD C24 1) C24 2) SD SD RD RD C24n R SDA SDA SDB SDB SDB RDA RDA RDA RDB RDB SG SG FG SDA R RDB SG FG RS-422/485 cable FG RS-422/485 cable R Linked operation Linked operation Terminating resistor 2) Connection example 2 External device 1) R C24 1) External device 2) C24n SDA SDA SDA SDA S
6 SETTING AND WIRING 6.3.4 Precautions when transferring data using RS-422/485 circuit The following precautions must be observed when transferring data with an external device through the C24 RS-422/485 interface. Take the following into account when the transferring data with the external device.
6 SETTING AND WIRING (2) RS-422/485 interface operation 1) RS-422-485 interface structure The following illustration shows the structure of the C24 RS-422/485 interface driver (send)/receiver (receive). 1 "Output control input" (also called send gate) of the driver (send) section of the illustration at the left determines whether or not data from SDA/SDB is output to the outside.
6 SETTING AND WIRING POINT (1) When the external device and the C24 connected in n:1 and m:n configurations When the send signal of each device is connected as shown below, if the "Output control input" is turned ON at two or more devices, the relevant devices output (send) data at the same time. For the external device to transfer data normally: • "Output control input" must be turned ON only when sending data. • "Output control input" must be turned OFF when not sending data.
6 SETTING AND WIRING 6.3.5 Enabling or disabling echo back of the RS-422/485 interface The following describes the enabling and disabling of the echo back. This function can be used for CH2 of the LJ71C24. The echo back of the LJ71C24 is defined as the function that, when data are sent through RS-485 (2-wire type) from the RS-422/485 interface, the same data are also sent to RDA or RDB of the LJ71C24. Whether to receive the returned data or not (discard) can be specified.
6 SETTING AND WIRING [Example of a setting in sequence program] Send command T0 H0 MOV K1 D0 Set echo back to "Disable". H1C2 D0 K1 Set the value in the echo back enable/disable setting area (address: 450 (1C2H)). Data transmission program POINT The echo back enable/disable setting must be done before sending data. Any setting changed during transmission does not take effect.
6 SETTING AND WIRING 6.4 Individual Station Test After installing the C24 to a system, check the switch setting and operation of the C24 at first. The individual station test consists of the following two tests. (1) ROM/RAM/switch test Checks the contents of the memory of the C24 and the switch settings set with GX Works2. (2) Self-loopback test Checks the communication between the C24 and CPU modules and the operation of the communication function of the C24.
6 SETTING AND WIRING 6.4.1 ROM/RAM/switch test A ROM/RAM/switch test checks the contents of the memory of the C24 and the switch settings set with GX Works2. Perform a ROM/RAM/switch test with the procedure described below. (Procedure 1) Communication protocol setting and transmission setting (refer to Section 7.3) (1) In the switch setting, set the communication protocol setting on the CH2 side to "ROM/RAM/Switch test".
6 SETTING AND WIRING (Procedure 3) Checking results of ROM/RAM/switch test (1) When the result of the test is normal The CH1 NEU LED turns on and the ERR LED turns off. (2) When the result of the test is abnormal The CH1 NEU LED turns on and the ERR LED turns on. (Procedure 4) Ending a ROM/RAM/switch test (1) When the result of the test is normal (a) Perform an Self-loopback test. Perform the test operation according to Section 6.4.2. (b) Start the data communication with external devices.
6 SETTING AND WIRING Item Current value Status When linked operation setting CH SIO 1 (ON) CH PRO. 1 (ON) CH P/S 1 (ON) CH C/N 1 (ON) When independent operation setting CH NEU. 1 (ON) Test completed CH ERR. Setting station number Transmission setting error Protocol setting error Transmission setting error Corrective action Check the set values (refer to Section 7.3) and perform the test again.
6 SETTING AND WIRING 6.4.2 Self-loopback test The Self-loopback test checks the communication between the C24 and CPU modules and the operation of the communication function of the C24. Also, tests two interfaces of the C24 at once. Follow the procedure below to perform an Self-loopback test. (Procedure 1) Connecting cable Connect cables to two interfaces as follows. • Connect cables to the RS-232 interface within the connector and install it to the interface.
6 SETTING AND WIRING (Procedure 4) Checking the results of an Self-loopback test (1) When the result of the test is normal If the ERR. LED turns off and the LED status of the CH1 and CH2 are as follows for over 5 seconds, the result is normal. CH1 (2) CH2 NEU.LED Flashing OFF SD LED Flashing Flashing RD LED Flashing Flashing When the result of the test is abnormal The ERR. LED turns on.
6 SETTING AND WIRING Item CH When the "Current Value" is 1 (ON) Corrective action Error in the CPU module. Remove errors in the CPU module. Insufficient power supply capacity. Examine the power supply capacity. Module is not connected correctly. Reinstall the module properly. C/N Check each module and remove the Error in the cable, CPU module, or cause of the error. the C24. Reconnect the cable correctly. Reinstall the module properly. CH 6 - 27 ERR.
6 SETTING AND WIRING 6.5 Loopback Test A loopback test performs a communication test using the loopback test function of the MC protocol, in order to check the connection between the C24 and an external device, the communication function of each device, and the operation of the communication program of the external device.
6 SETTING AND WIRING (Procedure 4) Checking loopback test result Check on the external device whether the data received from the C24 in response to the data received from the external device matches the data sent from the external device. (The C24 sends back to the external device the received data, as is.) (1) When the result of the test is normal The data received from the C24 in response to the data received from the external device matches the data sent from the external device.
6 SETTING AND WIRING TT (ACPU common command) (Data name) CPU module side Two characters (hexadecimal) H L H L 0 5 A B C D E 7 8 37H 38H 30H 30H 35H 41H 42H 43H 44H 45H Character A part (In the case of Format 1) S T The same data X Character length 05H 30H 30H 46H 46H 54H 54H 0 Sum check code PC No. 0 0 F F T T (Example) Loopback data The same data as those in Character length Station No. H L H L Character length Q PC No. N Command External device side E Station No.
7 SETTINGS FOR THE C24 7 SETTINGS FOR THE C24 The switch settings, parameter settings, monitor/test and others for the C24 are performed by GX Works2. The same settings can be configured in GX Developer and GX Configurator-SC. For details, refer to Appendix 4. Refer to the User’s Manual (Application) when performing the remote password settings.
7 SETTINGS FOR THE C24 7.1 Adding the C24 to Projects [Setting purpose] Add the C24 to projects with GX Works2 to perform various settings. [Startup procedure] Display the "New Module" screen. Project window [Intelligent Function Module] Right click [New Module] [Setting screen] [Setting description] Item name Module Selection Mount Position Title Setting 7-2 Settings Module Type Set "Serial Communication". Module Name Select the module model name to connect.
7 SETTINGS FOR THE C24 7.2 List of Setting Items for C24 This section explains the items to be set in GX Works2 to perform the data communication with external devices. Before performing the following settings, add the C24 to the GX Works2 project and set the I/O range. For details, refer to Section 7.1. Parameter setting items The following abbreviations appear in the protocol column of the function list.
7 SETTINGS FOR THE C24 ( : Applicable protocol) Protocol Setting items For designation of transmission control For designation of data communication time monitoring For designation of on-demand function For designation of transmission area For data reception For designation of reception area MC Non Bi Pd Receive data — — — Transmission data — — — — No-reception monitoring time (timer 0) designation — Response monitoring time (timer 1) designation — Transmission monitoring time (timer 2) des
7 SETTINGS FOR THE C24 (3) PLC_Monitoring_Function Set the programmable controller CPU monitoring function.
7 SETTINGS FOR THE C24 (4) Modem_Function Set for the data communication with the modem functions.
7 SETTINGS FOR THE C24 (5) User_Register_Frame_Content Register user frames. ( : Applicable protocol) Setting items User frame Protocol MC Non Bi Pd — — Registration frame No.1000 to No.1199 Reference User's Manual (Application) (6) User_Register_Frame_Specification Specify user frames. ( : Applicable protocol) Setting items For designation of on-demand user frame Protocol MC Non Bi Pd First frame No. designation 1 — — — First frame No. designation 2 — — — Last frame No.
7 SETTINGS FOR THE C24 (7) Auto_Refresh Set the device on the CPU module side to refresh the data of the buffer memory. For details, refer to Section 7.5. (a) Transfer to CPU User frame being transmitted Setting items Reference User frame being transmitted User's Manual (Application) SD.WAIT SIO LED ON status and communication error status on CH1 side PRO. P/S C/N NAK ACK. NEU. For confirmation of LED ON status and communication error status SD.WAIT SIO Section 13.2 Section 15.1.1 PRO.
7 SETTINGS FOR THE C24 Setting items Reference MC protocol transmission error code For confirmation of communication result MELSEC-Q/L MELSEC Communication Protocol Reference Manual User's Manual (Application) Receive user frame (nth) Programmable controller CPU monitoring function operation status Programmable controller CPU monitoring function Programmable controller CPU monitoring function execution result (current) Programmable controller CPU monitoring function number of transmission User's Manu
7 SETTINGS FOR THE C24 (b) Transfer to the Intelligent Function Module Setting items For transmission data Predefined protocol function control data specification 7 - 10 Reference Transmission area Chapter 10 Chapter 11 Transmission area (User free area) Appendix 1 Transmission area (User free area 2) Appendix 1 Number of continuous executions Execution protocol No.
7 SETTINGS FOR THE C24 7.3 Switch Setting [Setting purpose] Set the transmission specifications and communication protocols for communication with external devices. [Startup procedure] Display the "Switch Setting" screen. Project window [Intelligent Function Module] Setting] Module model name [Switch [Setting screen] POINT • When GX Works2 or a GOT is connected to the C24 on a 1:1 (one-to-one) basis: The switch setting is not required for accessing or monitoring an LCPU.
7 SETTINGS FOR THE C24 7.3.1 Transmission Setting Set the transmission specification with external devices. (1) Operation setting The following two types of operations can be set. (a) Independent operation Two interfaces of the C24 perform data communication with external devices independently. (b) Linked operation All data received from one of the two interfaces are transmitted from the other interface. For the settings of linked operation and data flow, refer to Section 7.3.5.
7 SETTINGS FOR THE C24 (7) Online change This sets whether or not data transmitted using the MC protocol is written to the CPU module from an external device while the CPU module is running, according to the system specifications. When online change is prohibited (disabled), the data is not written and an NAK message is returned if the external device requests the CPU module to write data while it is running. The available functions differ depending on the setting values when the online change is enabled.
7 SETTINGS FOR THE C24 7.3.2 Communication rate setting Set the communication rate for the data communication with external devices. The following is the setting value list. Communication rate (unit: bps) 50 14400 300 19200 600 28800 1200 38400 2400 57600 4800 115200 9600 230400 1 1 Communication rate of 230,400 bps is available for only CH1.
7 SETTINGS FOR THE C24 7.3.3 Communication protocol setting Set the communication protocol for the data communication with external devices. The following shows the setting value list. Setting items MELSOFT Connection Setting contents For connection to MELSOFT products MELSOFT communication rate and transmission specifications are automatically set.
7 SETTINGS FOR THE C24 7.3.4 Station number setting This setting is for communication using the MC protocol. When several serial communication modules are connected on the same line with multidrop connection, specify the serial communication module to communicate with external devices by the station number. Set the station numbers from 0 to 31. Set the station number to 0 when the system configuration of the external device and the CPU module is 1:1.
7 SETTINGS FOR THE C24 7.3.5 Setting and data flow in linked operation In linked operation, all data received from one of the two interfaces are transmitted from the other interface. The linked operation is available only for the LJ71C24. It is not available for the LJ71C24-R2. POINT When two interfaces are in linked operation, the transmission time for one character becomes equal to the hardware gate off time of the L series. (1) Setting For the linked operation, set the related switches as follows.
7 SETTINGS FOR THE C24 (b) When setting the CH2 side to MC protocol When data communication is performed using the MC protocol, only the C24 having the station number designated in the message performs the process designated by the command. Furthermore, when data communication is performed using QnA compatible 2C/3C/4C frames of the MC protocol, the header information for linked operation is added to messages directed to other stations linked by multidrop connection.
7 SETTINGS FOR THE C24 7.3.6 Precautions For the interface that is not used for communication (no cable connection), define the switch settings as follows.
7 SETTINGS FOR THE C24 7.4 Various Parameter Settings and Writing to the Flash ROM Initial values of the buffer memory can be changed by setting and writing various parameters to the flash ROM. Set various parameters according to the system in use.
7 SETTINGS FOR THE C24 7.4.1 Parameter setting This section explains the procedures to set each parameter. By setting parameters in a programming tool, parameter settings by sequence programs are not necessary. (1) Displaying each parameter setting screen Select [Intelligent Function Module] Module model name from the Project window, and select either of the parameter setting items. Parameter setting items (2) Setting Set the parameters from each parameter setting screen.
7 SETTINGS FOR THE C24 REMARKS Display only the applicable parameters in the setting screen of each parameter for each protocol. The following shows the procedure. 1) Display the setting screen of each parameter. 2) Select a protocol from "Display Filter". Select a protocol. 3) The parameters, which can be set in the selected protocol, is displayed.
7 SETTINGS FOR THE C24 7.4.2 Writing to the flash ROM This section explains the procedure to write the contents set in Section 7.4.1. to a flash ROM. (1) Displaying the screen for writing to the flash ROM Display the "Flash ROM Operation" screen by the following procedure. [Online] [Write to PLC…] (2) Selecting a module and the parameters to be written (a) In the "PLC Module" tab, select the "Target" check box of "Intelligent Function Module (Initial Setting/Auto Refresh)".
7 SETTINGS FOR THE C24 (3) Executing data writing Click the Execute button to write the data. As the following dialog box appears, click the Yes button. IMPORTANT Collectively write data to the flash ROM from GX Works2 before the system is started. (Writing to the flash ROM normally takes approximately one to three seconds. However, note that sometimes it may take approximately one to two minutes.
7 SETTINGS FOR THE C24 7.5 Auto Refresh This section explains the procedures of the auto refresh setting. The auto refresh settings are used to automatically store information stored in the C24's buffer memory into a specified device of the CPU module. By setting the auto refresh, the read and write processing of the buffer memories on the program are not necessary.
7 SETTINGS FOR THE C24 7.5.1 Setting method for auto refresh (1) Displaying the screen for auto refresh For the method for displaying the screen, refer to Section 7.4.1. Buffer memory and description of the item selected on the screen are displayed. (2) Setting auto refresh Set a CPU module device that stores the information in the setting item field. Applicable devices are any of X, Y, M, L, B, T, C, ST, D, W, R, and ZR.
7 SETTINGS FOR THE C24 7.6 Intelligent Function Module Interrupt Pointer Setting The following explains the interrupt pointer setting with GX Works2 to receive data using an interrupt program. For the method for receiving data using an interrupt program, refer to the User's Manual (Application). [Setting purpose] The interrupt pointer sets the information to read the receive data with an interrupt program of the CPU module during communication using the nonprocedural/bidirectional protocol.
7 SETTINGS FOR THE C24 [Setting description] (1) Interrupt Pointer Start No. : PLC Side Set the start number of the interrupt pointer (Ixx) for use in the sequence program. The setting range is from 50 to 255. (2) Interrupt Pointer Count : PLC Side Set the number of units of interrupt pointers (I) for use in the sequence program. (3) Start I/O No. : Intelligent Module Side Set the start I/O No. for the C24. (4) Start SI No.
7 SETTINGS FOR THE C24 7.7 Monitor/Test The "Intelligent Function Module Monitor" screen is used to perform various operations, including the monitoring of the C24's operating status and setting values, and the testing of its output signals. The monitor/test operations can be performed only via online operation. For details, refer to the GX Works2 Version1 Operating Manual (Intelligent Function Module).
7 SETTINGS FOR THE C24 MEMO 7 - 30 7 - 30
8 DATA COMMUNICATION USING THE MC PROTOCOL 8 DATA COMMUNICATION USING THE MC PROTOCOL MC protocol is a communication method for the Mitsubishi programmable controller. Using this protocol, the external devices can read or write device data and programs from or to the CPU module. The C24 automatically returns a response message based on requests from external devices. Thus, sequence programs are not required for response messages.
8 DATA COMMUNICATION USING THE MC PROTOCOL 8.1 Data Communication 8.1.1 Formats and applications of the data communication frames The MC protocol uses the following communication frames for data communication. The external device must communicate data in the data format appropriate to the MC protocol.
8 DATA COMMUNICATION USING THE MC PROTOCOL 8.1.2 MC protocol system setting Perform the system setting for data communication using the MC protocol by GX Works2. (1) Switch setting Set the transmission specification, the communication protocol with external devices and others. Always perform this setting. For the communication protocol setting, select one from the MC protocols (Formats 1 to 5). Configure other settings according to the system being used. For details of the settings, refer to Chapter 7.
8 DATA COMMUNICATION USING THE MC PROTOCOL 8.1.3 Support for the LCPU remote password function The remote password function prevents unauthorized access to the LCPU. To enable this function, set the remote password to an LCPU. For details, refer to the User's Manual (Application).
8 DATA COMMUNICATION USING THE MC PROTOCOL 8.2 Utilizing the MX Component MX Component is an ActiveX control library that supports various types of communication paths between IBM-PC/AT-compatible personal computers and programmable controllers. By using MX Component, the system can be configured for each user. Furthermore, the communication program for the external device can be created without considering the detailed MC protocol (transmission/reception procedures).
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL Data can be transferred between the CPU module and an external device with a protocol appropriate to the external device (such as a measuring instrument and a barcode reader). Device or buffer memory data can be taken into communication packets, and thereby this protocol communication is suitable for data that may change every transmission.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT The following are the maximum numbers of protocols and packets that can be registered. • Protocols: Up to 128 • Packets: Up to 256 However, some packets to be registered may cause capacity shortage. In this case, the maximum numbers of packets above may not be registered. The usage rate of the packet data area can be confirmed on the "Protocol Setting" screen in GX Works2.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.1 Data Communication Procedure By the following procedure taken in Predefined protocol function, data can be exchanged with an external device. Step 1: Display the "Predefined Protocol Support Function" screen. Display the "Predefined Protocol Support Function" screen in the following procedure. GX Works2 [Tool] [Intelligent Function Module Tool] [Serial Communication Module] [Predefined Protocol Support Function] Step 2: Create a new file.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (From the previous page) Step 4: Set the items required for the data communication. (a) When selecting "Predefined Protocol Library". Select a protocol from the predefined protocol library. Specify the send or receive data storage area. (b) When selecting "Add New" Click "Element Unset" on the "Protocol Setting" screen. Set the packet configuration to send/receive in the "Packet Setting" screen.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (From the previous page) Step 5: Write the protocol setting data to the flash ROM. Display the "Module Write" screen in the following procedure. [Module Read/Write] [Write to Module] Select a target module, and write the protocol setting data to the flash ROM. Step 6: Execute the protocol with a dedicated instruction. CPRTCL Predefined execution protocol command ready Set values are in the Send data storage area. Protocol No.1 is specified.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.2 Communication Type of Protocols Send packets to other devices and receive packets from other devices at the time of process execution are registered in a protocol. The following shows an example of a packet configuration. For details of packet elements, refer to Section 9.3. Data division Header Station No.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.3 Packet Elements A packet consists of packet elements. Up to 32 elements can be placed in a packet, and the maximum data length is 2048 bytes per packet. The following shows the details of the packet elements. Also, refer to Appendix 5.3 for an example of packet element data. (1) Header Use this element when a specific code/character string exists at the beginning of a packet. • When sending: Sends a specified code and character string.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (2) Static Data Use this element when a specific code/character string such as command exists in a packet. y When sending: Sends a specified code and character string. y When receiving: Verifies the receive data. Multiple Static Data elements can be placed to desired positions in the data division. The items are the same as ones explained in Section 9.3 (1) in this section. (3) Terminator This element indicates the end of a packet.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (4) Length Use this element when an element indicating the data length is included in a packet. y When sending: Calculates the data length of a specified range, and adds the result to a send packet. y When receiving: Verifies the data (setting value) corresponds to the length in the receive data as the data length of a specified range. The following table shows the items. Item Description Element Name Remark Set a name of the element.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT y Only one Length can be placed in a packet. y When there is no element other than a Length, an element error occurs. y When the number of digits of calculation result is greater than that specified in "Data Length", digits greater than the specified digit are omitted (ignored). Example) When "2 bytes" is specified in "Data Length" and the calculation result is "123 bytes", the data length is considered as "23".
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (5) Non-conversion Variable Use this element to send the data in the device memory of a CPU module or buffer memory as a part of a send packet, or store a part of a receive packet to the device memory of a CPU module device or buffer memory. The following lists the items. Item Element Name Description Set a name of the element. Fixed Length Fixed Length/Variable Length Sends and receives the data whose length is fixed.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL Item Description When sending: When "Enable" is selected, sends data swapping the upper byte and lower byte by word (2 bytes). When "Unit of Stored Data" is "Lower Byte + Upper Byte" and "Data Length" is an odd number of bytes, sends the upper byte at transmission of the last byte.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL The following explains the configuration of the data storage area. (a) When "Fixed Length/Variable Length" is "Fixed Length" An area starting from the device number which is specified on the Element setting screen is considered as the data storage area. The data storage area to be occupied varies depending on the setting of "Unit of Stored Data". y When "Lower Byte + Upper Byte" is selected, the same size as the data length is occupied.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (b) (Word) +0 When "Fixed Length/Variable Length" is "Variable Length" An area starting from the device number which is specified on the Element Setting screen +1 is considered as the data storage area. The data storage area to be occupied varies depending on the setting of "Unit of Stored Data". y When "Lower Byte + Upper Byte" is selected, the same size as the data length + one word (length for the data length storage area) are occupied.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT y When receiving variable length data whose length exceeds the "Maximum data length", the C24 stores data as long as the maximum data length and omits the rest. (A protocol completes successfully.) y In receive packet data from other devices, the C24 needs to be able to discriminate data corresponding to a Non-conversion variable from those of a Terminator or a Static Data following a Non-conversion variable.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (6) Conversion Variable This element converts the numerical data in the device memory of a CPU module or buffer memory to an ASCII string and sends it, or converts the receive data (ASCII string) to the numerical data and stores it to the device memory of a CPU module or buffer memory. The following lists the items. Item At receiving Conversion HEX ASCII Converts numeric value stored in the data storage area to ASCII decimal.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL Item Description Remark Set the number of digits per one send and receive data. 1 to 10 When the number of digits of data is less than the - specified number of digits, upper digits are filled with blank-padded characters. When sending: Sends only the data division Number of Digits of converted to an ASCII string in Data variable length.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL The following explains the configuration of the data storage area. (a) When "Fixed Number of Data/Variable Number of Data" is "Fixed Number of Data" An area starting from the device number which is specified on the Element setting screen is considered as the data storage area.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (d) Data storage area configuration The following shows the data storage area configuration per one data. 1) "Conversion Unit": Word, "Number of Decimals": No decimal Point (fixed point) No Decimal Point (fixed point) Data storage area 0h 2) Numeric data "Conversion Unit": Word, "Number of Decimals": Variable point For "Variable Point", the decimal point position is set in the data storage area.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 4) "Conversion Unit": Doubleword, "Number of Decimals": Variable Point For 'Variable Point', the decimal point position is set in the data storage area. Data storage area 0h (L) Numeric data 1h (H) (L) 2h Decimal point position 3h (H) In the decimal point position area, the decimal point position is set as follows. Send/receive data Numeric data (number of digits is 10) Decimal point position 1234567890 1234567890(499602D2H) 1(1H) 123456789.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT An error may occur in any of the following cases. y When "Conversion" is "ASCII Hexadecimal HEX", an ASCII BIN conversion error (7F20H) may occur if a string except for '0'-'9' 'A'-'F' 'a'-'f' is received. y When "Conversion" is "ASCII Decimal HEX", an ASCII BIN conversion error (7F20H) may occur if a string except for '0'-'9' is received. However, the following are exempt from the ASCII BIN conversion error.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT [For the fixed number of data] y When "Number of Digits of Data" is "Variable Number of Digits", an invalid number of digits error (7D19H) may occur if the number of digits of receive data is 0. [For the variable number of data] y A too few digits error (7D18H) may occur if data of which number of digits are fewer than the digits specified in "Number of Digits of Data" are received.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT To place a Conversion variable in a packet, the following requirements need to be met. (1) To place Conversion variable in send packet Multiple Conversion variable elements can be placed in one packet, and they can be placed in desired positions in the data division.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (7) Check Code Use this element when an element indicating check code data is included in a packet. The C24 automatically calculates a specified check code at timing of sending/receiving, and adds it to a send packet or detects an error of a receive packet. The following table lists the items. Item Element Name Processing Method Description Set a name of the element. - Select a calculating method.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL Item Description Remark When sending: Sends a calculated check code swapping the upper byte and lower byte by word. When receiving: Manipulates receive data as a Data Flow Byte swap (by word) check code swapping the upper byte and lower byte by word. Effective only if the data length Not settable when "Processing Method" is "16-bit CRC (for MODBUS)" or when the "Data Length" is set to "1 (byte)". is 4 bytes.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (8) Non-verified Reception Use this element when receive data include data not needed. The C24 skips characters as many as the specified number if a receive packet includes a Non-verified reception. The following table lists the items. Item Element Name Description Set a name of the element. Set this item when the number of 0 Data Length Remark (variable number of characters) characters not to be verified varies in each of communication.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.4 Executing Condition of Predefined Protocol Communication The predefined protocol communication can be executed when the predefined protocol ready (X1D) is on. Use the signal as an interlock signal when executing the predefined protocol communication in the sequence program. This signal turns ON only when the communication protocol setting is set to predefined protocol.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (2) Timing for executing the UINI instruction or mode switching request signal (Y2/Y9) 1 (a) Timing for executing mode switching request signal (Y2/Y9) Communication protocol before change: CH1 and CH2 are other than the predefined protocol mode. Communication protocol after change: CH1 or CH2 is the predefined protocol mode.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (b) Timing for executing the UINI instruction Communication protocol before change: CH1 and CH2 are other than the predefined protocol mode. Communication protocol after change: CH1 or CH2 is the predefined protocol mode.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL Communication protocol before change: CH1 or CH2 is the predefined protocol mode. Communication protocol after change: CH1 and CH2 are other than the predefined protocol mode.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.5 Programming Example This section explains the programming examples and setting examples of the predefined protocol function. GX Works2 is used for the settings. Serial communication module LJ71C24 and Mitsubishi inverter (FREQROL-A700, described as inverter or FR-A700 hereafter) as a connection target device are used in this setting example. 9.5.1 System configuration/wiring example The system configuration and wiring example are as follows.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.5.2 Communication data In the program example, the predefined protocol communication described below is performed between LJ71C24 and the target device. (1) Target device and protocols Connect the LJ71C24 and the inverter and read out the operation mode values of the inverter. Set the inverter station number to CPU device (D300) and send it, and store the operation mode value in CPU device (D201).
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9.5.3 Communication settings (1) Settings on GX Works2 This section explains the settings required for executing the predefined protocol communication on GX Works2. For details, refer to Chapter 7. (a) Addition of new modules and I/O assignment For adding new modules, add an intelligent function module to a project. For I/O assignment settings, set each module type and I/O signal range. 1) Display the "New Module" screen.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (b) Switch settings Set the transmission specifications and communication protocols with external devices. 1) Display the "Switch Setting" screen. Project window [Intelligent Function Module] [Switch Setting] 2) Set items as follows and click the OK button. Module model name [Display/Setting screen] [Display/Setting details] Configure the settings for CH2 as the screen above. For CH1, the default values can be used.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (2) Settings for the predefined protocol support functions Set the protocol explained in Section 9.5.2. 1) GX Works2 [Tool] [Intelligent Function Module Tool] [Serial Communication Module] [Predefined Protocol Support Function] 2) "Predefined Protocol Support Function" screen [File] [New] 3) Click "Add" for "Protocol No." in the "Protocol Setting" screen. 4) The "Add Protocol" screen is displayed. Select the following protocol, and click the OK button.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 6) In the "Packet Setting" screen, click the cell under "Element Setting" (displayed in red) of "Element No." 2. Click 7) In the "Element Setting" (Conversion Variable) screen, enter D300 to "Send Data Storage Area" and click the OK button. 8) The packet setting for "Packet Name" H7B:RD Operation Mode is completed in the "Packet Setting" screen. Click the Close button.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL 9) Configure the packet settings for "Packet Name" NOR:RD Data (4 Digits Data) and ERR:NAK Response with the same procedure as 5) to 8). Set the following values for the data storage area.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (4) Executing the protocols (program example) Create a program with the dedicated instruction (CPRTCL instruction) using GX Works2. Switch the CPU to RUN, and execute the registered protocol by the dedicated instruction (CPRTCL instruction). The following table shows the devices to be used.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL (5) Checking protocol execution result (a) Check on the "Circuit Trace" screen. The send/receive packets and communication control signals can be checked from the displayed trace result. For details, refer to Section 13.1. (b) Check on the "Protocol execution log". 1) Display the "Protocol execution log" screen. "Predefined Protocol Support Function" screen Function] [Protocol Execution Log] 2) The protocol execution result can be checked.
9 DATA COMMUNICATION USING THE PREDEFINED PROTOCOL POINT The logs displayed in the "Protocol execution log" screen can be selected from the following according to the log registration condition. • Only the failed protocols are displayed. • The execution status and log of all protocols are displayed. For the selecting method of the log registration condition, refer to Section 13.3.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL Nonprocedural protocol enables to send and receive data between a CPU module and an external device, using the data format and transmission control procedure set by user. A sequence program for data communication is required on the CPU module side. Use this protocol for data communication using any given data format.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1 Data Reception from the External Device This section explains data reception from the external device. 10.1.1 Receiving methods The following shows the methods for receiving data in any format using the nonprocedural protocol. There are two methods for receiving data: the "reception via receive complete code" for receiving variable length messages, and the "reception via received data count" for receiving fixed length messages.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (1) Data reception by receive complete code (for variable length reception) (a) This method is used to send data by adding the receive complete code set in the C24 at the completion of setting the message from the external device. (b) When the C24 receives the receive complete code data preset in GX Works2 by the user, it sends a receive data read request to the sequence program.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL • If LF is not received within the time set in the non reception monitoring time (timer 0) after CR is received, the C24 stores the received data up to CR to the buffer memory receive data storage area and turns on the following signals to the CPU module.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Reception by received data count (For fixed length reception) (a) This method is used to receive messages of the same length (size) from the external device every time. (b) When the C24 receives data of the received data count preset in GX Works2 by the user, it sends a reception data read request to the sequence program. Upon a read request by the C24, sequence program data can be read for the amount of the data received from the external device.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1.2 The receive area and the received data list The following shows the list of the receive area and the receive data for performing data reception using the nonprocedural protocol. (1) Receive area The receive area is a memory area for storing the data received from the external device and the receive data count in order to read the receive data to the CPU module.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL POINT (1) The position and size of the receive area in the buffer memory can be changed with the GX Works2 in accordance with the specifications of the external device and the receive data length. (Refer to Section 7.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Receive data list The following describes the data list when data received from an external device is stored to the receive area. 1) The receive message is stored to the C24 buffer memory (receive data storage area). 2) The data is stored to the receive data storage area in the order of low address (L) (H), next address (L) (H).
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL REMARKS (1) Data reception when: Receive data storage area > Receive data length The following control is performed.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 2) Reception by received data count If a specified receive data count is too large for the receive data storage area, Receive buffer memory length (address: A7H/147H, default: 512 words) minus 1 is used as the receive data count instead.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1.3 Sequence program for data reception This section explains the sequence program for data reception. For details on the INPUT instruction for data reception, refer to Chapter 12. 1 When the completion device is off, execute the INPUT instruction. If the INPUT instruction is executed when the completion device is on, data may not be received properly. 1) Start the self-station programmable controller CPU.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 4) The INPUT instruction complete device turns ON when the reading of receive data is completed. When the complete device + 1 (abnormal completion signal) turns ON, the error code is stored in the control data completion status (S1 + 1). (Program example) When the C24 I/O signals are from X/Y00 to X/Y1F: 1) 2) 3) 4) 5) Specify the receive channel. Clear the reception result and receive data count storage device to 0.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL C24 Address 258H Buffer memory Data reception result For normal completion D0 D1 D2 D3 D10 to Dm Interface number Reception result Receive data count Allowable receive data count (1) (0) (n) (10) 600H 601H to Receive data count Receive data 7FFH Receive data to Receive data For abnormal completion D0 D1 D2 D3 Interface number (1) (other than 0) Reception result (n) Receive data count Allowable receive data count (10) D10 to Dx Receive dat
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1.4 How to detect and check the reception errors This section explains how to detect and confirm errors that may occur when receiving data from external devices. The following items are considered as the primary causes of errors that may occur during data reception. Cause of reception error A transmission error occurred due to noise. A timeout for the no-reception monitoring (timer 0) occurred.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Confirmation using GX Works2, display unit, or indicator LED of C24 The following methods are available for confirmation.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL C24 CPU module Reception abnormal detection Receive area (buffer memory) Receive data count 3 (00H) (03H A STX (41H) (02H) B C (43H) (42H) E D (45H) (44H) Receive data INPUT instruction Reception error causing data Receive complete code Head data STX A B C D E F G H ETX (02H) (41H) (42H) (43H) (44H) (45H) (46H) (47H) (48H) (03H) Transmission data External device C24 ready (X1E) Reception data read request (X3) Reception abnormal detec
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1.5 Receive data clear For the data reception by a nonprocedural protocol, if the transmission of data from a transmitting device is interrupted due to trouble occurring, it may be necessary for the data received up to the present time are cleared in the receiving device and for the data to be received again from the start. The methods for clearing reception data in the C24 are shown below.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Procedure for clearing the reception data by the dedicated instruction "CSET" This instruction clears the reception data up to the present without interrupting the data transmission processing.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (3) Receive data clear procedure using FROM/TO instruction Write and read Receive data clear request (address: A8 H/148H) using the procedure described below. When resuming data communication with an external device, resume it after completing the receive data clear processing with the C24.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (Example) The following is an example program for clearing received data with the FROM/TO instructions while send/receive processing is performed using dedicated instructions (OUTPUT/INPUT). (If the C24 input/output signal is X/Y000 to X/Y01F.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL Send Receive Receive request data clear data clear acknowl- in progress edgement send processing 10 - 21 10 - 21
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (4) Receive data clear command procedure using GX Works2 1) Register C24 to "Intelligent Function Module Monitor". For the operating method of GX Works2, refer to the GX Works2 Version 1 Operating Manual (Intelligent Function Module). 2) Set "CH Receive data clear request" of "For Data Receiving" to "Requested". 3) The receive data is cleared.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.1.6 Received data count and receive complete code settings (1) Setting method before receiving data The following default values have been set for the received data count and receive complete code that are used for data reception with the nonprocedural protocol. The received data count and the receive complete code setting value can be changed by the sequence program before data receive processing.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL POINT When the reception abnormal detection (X4/XB) turns ON, read the error code from the buffer memory below, and then check the type of error and take corrective action based on the information found in Chapter 15.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (Program example: I/O signals for the C24 are from X/Y00 to X/Y1F) Read request 1) 2) Reads receive data count. ( 1) 2) 3) 4) 5) 10 - 25 Reads the data that is equal to the receive data count. Change the setting value for the received data count as needed. Change the setting value for the receive complete code as needed. Turns ON the reception data read completion (Y1).
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.2 Sending Data to the External Device This section explains data transmission from the CPU module to the external device. 10.2.1 Transmission methods The following shows how to send data in any format using the nonprocedural protocol.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.2.2 Arrangement and contents of the transmission area and the transmission data This section explains the arrangement and contents of the transmission area and the transmission data for performing data transmission using the nonprocedural protocol. (1) Transmission area The transmission area is a memory area for storing the data and the data count that are transmitted from the CPU module to the external device via the C24.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL POINT (1) The position and size of the transmission area in the buffer memory can be changed with GX Works2 in accordance with the specifications of the external device and the received data length.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Transmission data arrangement The following example shows an arrangement of the transmission data to be sent to the external device when storing it in the transmission area. (Example) When transmitting "ABCDEFG123" (The transmit area is the default value.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL C24 ready (X1E) 1) 2) Transmission instruction 3) OUTPUT instruction OUTPUT 4) OUTPUT instruction complete device ON when transmission abnormal completion OUTPUT instruction complete device + 1 (normal completion/abnormal completion) Transmission data count designation (address: 400H) 1 scan 0 n Transmission data Transmission data designation (address: 401H to) Transmitting data 1) Starts the host station programmable controller.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (Program example) When C24 I/O signals are from X/Y00 to X/Y1F: 1) 2) 3) 4) 5) 6) 7) 8) 9) 1) 2) 3) 4) 5) 6) 7) 8) 9) 10 - 31 Transmission command is converted into pulse. Transmission data is stored. Specify the number of the interface (CH ) that sends the data. Clear the transmission result storage device to 0. Specify the transmission data count in word units. (Specify K10 when the unit is bytes.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL C24 Address 257H Buffer memory Data transmission result For normal completion D0 D1 D2 Interface number Transmission result Transmission data count (0001H) (0000H) (0005H) Transmission data (4241H) to (0A0DH) 400H 401H to D11 to D15 D0 D1 D2 D11 to D15 For abnormal completion Interface number (0001H) Transmission result (other than 0000H) Transmission data count (0005H) Transmission data Transmission data count designation Transmission da
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.2.4 How to detect and confirm transmission errors This section explains how to detect and confirm errors that may occur when sending data to external devices. The following items are considered as the primary causes of errors that may occur during data transmission. Cause of reception error A timeout occurred for the transmission monitoring time (timer 2).
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (2) Confirmation using GX Works2, display unit, or indicator LED of C24 The following shows how to confirm the errors.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL 10.3 Data Communications Precautions The following describes the precautions to be taken during nonprocedural protocol data communications. (1) The C24 transmission sequence initialization conditions The initial status indicates the status where transmission has stopped and receive data has been discarded. The C24 transmission sequence initialization conditions are as follows.
10 DATA COMMUNICATION USING THE NONPROCEDURAL PROTOCOL (4) Retry processing for data reception errors The data when reception error occurred is discarded and only the data for the normal reception is taken into the C24. For this reason, the reception message may be missing data if an error occurs.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL This communication enables data transfer between an external device and a CPU module using the data format and transmission control procedure for the bidirectional protocol. The feature of this data communication is that a response message is sent from the data receiving side to the data sending side, informing if the communication was completed.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.1 Data Reception from the External Device 11 This section explains the data reception from the external device. 11.1.1 Receiving methods The following shows how to receive data sent from the external device using the bidirectional protocol. Since the size of each message received is recognized using the "data length" information contained in the message, messages of any size can be sent from the external device.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 1) When the control code ENQ is received, the C24 starts data reception processing. When the data specified by the data length is received, the C24 ends the reception processing of that data. When sum check is enabled in the switch setting of GX Works2, the C24 checks whether the message is normal or abnormal using the sum check code received immediately after the message and the sum check code calculated by internal processing.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.1.2 Arrangement and contents of the receive area and the receive data This section shows the arrangement and contents of the receive area and the receive data for performing data reception using the bidirectional protocol. (1) Receive area The receive area is a memory that stores the received data length (receive data count) and data area received from an external device.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL POINT (1) The position and size of the receive area in the buffer memory can be changed with GX Works2 in accordance with the specifications of the external device and the received data length. (Refer to Section 7.2.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (2) Arrangement of receive data The following example illustrates the arrangement of data received from the external device when it is stored in the receive area. 1) The receive message is stored to the C24 buffer memory (receive data storage area). 2) The data is stored to the receive data storage area in the order of low address (L) (H), next address (L) (H).
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (b) Data length This indicates the number of bytes or words for the data portion of the message. The unit of data length (words/bytes) is in accordance with the word/byte units designation in GX Works2. 1) For data communication from the external device to the C24 The C24 checks the length of the data received.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (d) Sum check code The sum check code expresses the numeric value for the lower two bytes (16 bits) of the results (sum) from the addition of the data length and the data portion in the message as binary code data. When "Exist" is specified for "Sum check code" in the Transmission Setting of GX Works2, it is necessary to add a sum check code at the end of the message.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (e) Error code The error code indicates the definition of the error during NAK response. (For details on the error codes, refer to Chapter 15.) 1) For data communication from the external device to the C24 For error codes from the external device, transmit the codes specified by the user. The error codes (0022H to 005FH) that are not used by the C24 can be used.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.1.3 Sequence program for data reception This section explains the sequence program for data reception. For details on the BIDIN instruction for data reception, refer to Chapter 10. X3 Read request (CH1) Create control data from D0 G.BIDIN M0 Un D0 D10 M0 M1 Processing for normal completion (stores receive data, etc.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (Program example) When C24 I/O signals are from X/Y00 to X/Y1F: 1) 2) 3) 4) 5) 6) 7) 1) 2) 3) 4) Specify the receive channel. Clear the receive data count storage device to 0. Specify the allowable receive data count. The receive data within the allowable receive data count (user-specified) is read from the receive data storage area in the buffer memory. Specify the transmission data count in word units. (Specify K10 when the unit is bytes.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL C24 Address Buffer memory 258H Data reception result For normal completion D0 D1 D2 D3 Interface number Reception result Receive data count Allowable receive data count D10 Receive data to D m Receive data (1) (0) (n) (10) 600H 601H to Receive data count Receive data 7FFH to When the received data count is larger than the allowable received data count, only the data up to the allowable received data count will be stored and the excess data wil
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.1.4 How to detect and check the reception errors This section explains how to detect and confirm errors that may occur when receiving data from external devices. The following items are considered as the primary causes of errors that may occur during data reception. Cause of reception error A transmission error occurred due to noise. Reference Section 6.2, Section 6.3 A timeout occurred for the no-reception monitoring time (timer 0).
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (2) Confirmation using GX Works2, display unit and indicator LED of C24 The following shows how to confirm the errors.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.2 Sending Data to the External Device This section explains the data transmission from the CPU module to an external device. 11.2.1 Transmission methods The following shows the method of sending data to the external device through data communication using the bidirectional protocol.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.2.2 Arrangement and contents of the transmission area and the transmission data This section explains the arrangement and contents of the transmission area and the transmission data for performing data transmission using the bidirectional protocol. For details on the contents of transmission data, refer to Section 11.1.2 (3).
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL POINT (1) The position and size of the transmission area in the buffer memory can be changed with GX Works2 in accordance with the specifications of the external device and the transmission data length. (Refer to Section 7.2.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (2) Transmission data arrangement The following example shows an arrangement of the transmission data to be sent to the external device when storing it in the transmission area.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.2.3 Sequence program for data transmission A sequence program for data transmission is explained below. For details on the BIDOUT instruction for data transmission, refer to Chapter 12. Transmission instruction (In the case of the CH1 side) Create transmission data from D11 Create control data from D0 G.BIDOUT M0 Un D0 D11 M0 M1 Processing for normal completion M1 Processing for abnormal completion (retransmission, etc.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 1) C24 ready (X1E) 2) Transmission instruction 3) BIDOUT instruction BIDOUT 4) BIDOUT instruction complete device ON when transmission abnormal completion BIDOUT instruction complete device + 1 (Normal completion/abnormal completion) Transmission data count (address: 400H) 1 scan 0 Transmission data (address: 401H to) n Transmission data Data transmission Receiving response 1) Starts the host station programmable controller.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (Program example) When C24 I/O signals are from X/Y00 to X/Y1F: 1) 2) 3) 4) 5) 6) 7) 8) 9) 1) 2) 3) 4) 5) 6) 7) 8) 9) 11 - 21 Transmission command is converted into pulse. Transmission data is stored. Specify the number of the interface (CH ) that sends the data. Clear the transmission result storage device to 0. Specify the transmission data count word units. (Specify K10 when the unit is bytes.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL C24 Address Buffer memory 257H Data transmission result For normal completion D0 D1 D2 Interface number Transmission result Transmission data count D11 to Transmission data D15 (0001H) (0000H) (0005H) (4241H) to (0A0DH) 400H 401H to Transmission data count designation Transmission data designation 5FFH For abnormal completion D0 D1 D2 (0001H) Interface number Transmission result (other than 0000H) Transmission data count (0005H) D11 to Tra
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.2.4 How to detect and confirm transmission errors This section explains how to detect and confirm errors that may occur when sending data to external devices. The following items are considered as the primary causes of errors that may occur during data transmission. Cause of transmission error A transmission error occurred due to noise. Reference Section 6.2, Section 6.3 A timeout occurred for the no-reception monitoring time (timer 0).
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (2) Confirmation using GX Works2, display unit and indicator LED of C24 The following shows how to confirm the errors.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.3 Processing when Simultaneous Transmission Performed During Full-Duplex Communication This section explains the processing when simultaneous transmissions occur in fullduplex communication. 11.3.1 Processing when simultaneous transmissions occur This section explains the processing performed by the C24 when the external device and the C24 transmit at the same time during data communications using the bidirectional protocol.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.3.2 Communication data processing when simultaneous transmissions occur Examples of the C24 communication data processing for the "Transmission data" and "Receive data" settings by GX Works2 are explained.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL (4) Transmission: Invalid, Receive: Invalid 2)-1 E N Q External device C24 side E N Q Sum check code Arbitrary data Arbitrary data Sum check code Ignores the receive data of 1)-1. Generates a simultaneous transmission error. Ignores the receive data of 2)-1. 1)-1 REMARKS Time-check timer 1 (response monitoring time) shown in the illustration is described in the User's Manual (Application).
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL 11.4 Data Communications Precautions The following shows the precautions when performing data communications using the bidirectional protocol. (1) When the transmission sequence is in the initial status, it indicates that data transmission and reception processing has not been started. The C24 transmission sequence is initialized in the following cases. • The power is turned on, the CPU module is reset. • When operating, or the mode is switched.
11 DATA COMMUNICATION USING THE BIDIRECTIONAL PROTOCOL POINT (1) Perform error processing according to the error code received immediately after the NAK message at the device that received NAK as the response message after data transmission. Chapter 15 shows the error codes that are transmitted from the C24. (2) If the C24 receives an NAK response while transmitting data to an external device, it completes data transmission, then reads the NAK, perform abnormal completion.
12 DEDICATED INSTRUCTIONS 12 DEDICATED INSTRUCTIONS Dedicated instructions are used to simplify programming when using intelligent function module functions. This chapter describes the LCPU dedicated instructions used for the C24. 12 12.1 Dedicated Instruction List and Available Devices (1) Dedicated instruction list The following table lists the dedicated instructions explained in this chapter.
12 DEDICATED INSTRUCTIONS (2) Available devices The following devices are available for the dedicated instructions: Internal devices Bit 1 X, Y, M, L, F, V, B Word T, ST, C, D, W File register R, ZR Constant 2 K, H 12 1 Word device bit designation can be used as bit data. Word device bit designation is done by designating Word device . Bit No. . (Specify the bit number in hexadecimal.) For example, bit 10 of D0 is D0.A .
12 DEDICATED INSTRUCTIONS 12.2 G(P).ONDEMAND Data can be sent using the on-demand function of the MC protocol. Applicable device Setting Internal device data (System, user) Bit Link direct device File register Word Intelligent function J \ Bit Index register module device Zn U \G Word (S1) — — (S2) — — Constant Others — (D) [Instruction code] [Executing condition] Command G.ONDEMAND G.ONDEMAND Un (S1) (S2) (D) GP.ONDEMAND Un (S1) (S2) (D) Command GP.
12 DEDICATED INSTRUCTIONS Function (1) Data stored in the device designated in (S2) and succeeding devices are sent according to the control data of the device designated in (S1) and succeeding devices, via the on-demand function of the MC protocol of the module designated in Un.
12 DEDICATED INSTRUCTIONS (3) Whether an ONDEMAND instruction was completed or failed can be checked by the completion device ((D)) or status display device at completion ((D)+1). (a) Completion device : Turns on at the END processing of the scan where the ONDEMAND instruction is completed, and turns off at the next END processing. (b) Status display device at completion : Turns on and off depending on the completion status of the ONDEMAND instruction. • Normal completion : Remains OFF.
12 DEDICATED INSTRUCTIONS Program example A program that sends data stored in D10 to D11 using an on-demand transmission When input/output signals of the C24 are from X/Y00 to X/Y1F 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 1) On-demand transmission command is converted into pulse. 2) Set the transmission channel to CH1. 3) Set the send data count to 2 words. 4) Set the transmission data to D10 to D11. 5) Reset the normal completion flag. 6) Reset the abnormal completion flag.
12 DEDICATED INSTRUCTIONS 12.3 G(P).CPRTCL Protocols and functional protocols written to the flash ROM with the predefined protocol support function of GX Works2 can be executed. For details of the functional protocol, refer to Section 12.3.1.
12 DEDICATED INSTRUCTIONS Control data Device Item Setting data Setting range Set by *1 y The execution result of the G(P). CPRTCL instruction is stored. (S) + 0 Execution result When executing multiple protocols, the execution result of *2 the protocol executed at last is stored. — System 1 to 8 System 0: Normal *3 Other than 0: Error code y The number of executions is stored. (S) + 1 Number of executions Protocols with errors are included in the count.
12 DEDICATED INSTRUCTIONS Function (1) The protocol setting data written to the flash ROM are executed by the module designated in Un. The protocol is executed according to the control data stored in the device designated in (S) and the following devices. The channel designated in n1 is used. (2) Protocols are executed consecutively for the number of times designated in n2 (maximum: 8) in one instruction execution.
12 DEDICATED INSTRUCTIONS (4) Whether a CPRTCL instruction was completed normally or abnormally can be checked by the completion device ((D)) or status display device at completion ((D)+1). (a) Completion device: Turns ON at the END processing of the scan where the CPRTCL instruction is completed, and turns OFF at the next END processing. (b) Status display device at completion : Turns ON and off depending on the completion status of the CPRTCL instruction. y Normal completion : OFF with no change.
12 DEDICATED INSTRUCTIONS Error (1) When a dedicated instruction is failed, the status display device at completion ((D)+1) turns ON and the error code is stored in the execution result ((S)+0). In case of operation errors, Error flag (SM0) turns ON and the error code is stored in SD0. Refer to the following according to the error code, and check and correct the error. 4FFFH or less: MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) 7000H or later: Section 15.
12 DEDICATED INSTRUCTIONS Cancellation of protocol execution A protocol can be cancelled during its execution. This function is used to end the protocol execution forcibly when a communication error occurs with the other device. This function is available for the predefined protocol mode only. (1) Execution method for cancellation request Execute a cancellation request from the sequence program. The corresponding buffer memories are shown in the following table.
12 DEDICATED INSTRUCTIONS (3) Program example The following is a program in which a cancellation is requested to the protocol being executed when the start I/O number of the C24 is 0000. Devices used by user Device Purpose M100 Cancellation request command flag M101 Cancellation request flag M110 Turns ON during execution of the CPRTCL instruction.
12 DEDICATED INSTRUCTIONS 12.3.1 Functional protocol The following functions are available by executing functional protocols with the CPRTCL instruction. y Receive data clear y Send/receive data monitoring start/stop y RS/DTR signal condition designation (1) Setting Specify the functional protocol number of the function to be executed in the control data ((S)+2 to (S)+9) of the CPRTCL instruction. For details of the CPRTCL instruction, refer to Section 12.3.
12 DEDICATED INSTRUCTIONS 12.4 G(P).OUTPUT Data can be sent in any user-defined message format using the nonprocedural protocol. Applicable device Setting Internal device data (System, user) Bit Link direct device J \ File register Word Bit Intelligent function Index register module device Constant Zn U \G Word (S1) — — (S2) — — Others — (D) [Instruction code] [Executing condition] Command G.OUTPUT G.OUTPUT Un (S1) (S2) (D) GP.OUTPUT Un (S1) (S2) (D) Command GP.
12 DEDICATED INSTRUCTIONS Function (1) Data stored in the device designated in (S2) and succeeding devices are sent according to the control data of the device designated in (S1) and succeeding devices, via the nonprocedural protocol of the module specified in Un.
12 DEDICATED INSTRUCTIONS (3) Whether an OUTPUT instruction was completed or failed can be checked by the completion device ((D)) or status display device at completion ((D)+1). (a) Completion device: Turns on at the END processing of the scan where the OUTPUT instruction is completed, and turns off at the next END processing. (b) Status display device at completion : Turns on and off depending on the completion status of the OUTPUT instruction. • Normal completion : Off with no change.
12 DEDICATED INSTRUCTIONS Program example The following example shows a program that sends any data stored in D11 to D15 using the nonprocedural protocol. When input/output signals of the C24 are from X/Y00 to X/Y1F: 1) 2) 3) 4) 5) 6) 7) 8) 9) 1) 2) 3) 4) 5) 6) 7) 8) 9) 12 - 18 Transmission command is converted into pulse. Transmission data is stored. Specify the number of the interface (CH ) that sends the data. Clear the transmission result storage device to 0.
12 DEDICATED INSTRUCTIONS 12.5 G.INPUT Data can be received in any user-defined message format using the nonprocedural protocol. Applicable device Setting Internal device data (System, user) Bit Link direct device J \ File register Word Bit Intelligent function Index register module device Zn U \G Word (S) — — (D1) — — Constant Others — (D2) [Instruction code] [Executing condition] Setting data Command Un G.INPUT G.
12 DEDICATED INSTRUCTIONS 1 For error codes relating to abnormal completion, refer to Chapter 15. 2 When setting "Word/byte units designation" by GX Works2, set the number of bytes when bytes are designated and set the number of words when words are designated. 3 The settings are done by either of the following: • User : Data set by the user before executing the INPUT instructions. • System : The CPU module stores the execution result of the INPUT instructions.
12 DEDICATED INSTRUCTIONS (4) Whether an INPUT instruction was completed or failed can be checked by the completion device ((D2)) or status display device at completion ((D2)+1). (a) Completion device: Turns on at the END processing of the scan where the INPUT instruction is completed, and turns off at the next END processing. (b) Status display device at completion : Turns on and off depending on the completion status of the INPUT instruction. • Normal completion : Off with no change.
12 DEDICATED INSTRUCTIONS Program example The following example shows a program that stores data received via the nonprocedural protocol in D10 and later. When the input/output signals of the C24 are from X/Y00 to X/Y1F: 1 When the completion device is off, execute the INPUT instruction. If the INPUT instruction is executed when the completion device is on, data may not be received properly. 1) 2) 3) 4) 5) 6) 7) 12 - 22 Specify the receive channel.
12 DEDICATED INSTRUCTIONS 12.6 G(P).BIDOUT Data can be sent using the bidirectional protocol. Applicable device Setting Internal device data (System, user) Bit Link direct device File register Word Intelligent function J \ Bit Index register module device U \G Word Constant Zn (S1) — — (S2) — — Others — (D) [Instruction code] [Executing condition] Command G.BIDOUT G.BIDOUT Un (S1) (S2) (D) GP.BIDOUT Un (S1) (S2) (D) Command GP.
12 DEDICATED INSTRUCTIONS Function (1) The function sends data stored in the device designated in (S2) and succeeding devices according to the control data of the device designated in (S1) and succeeding devices, via the bidirectional protocol of the module designated in Un.
12 DEDICATED INSTRUCTIONS [Operation during execution of a BIDOUT instruction] END END Sequence processing processing program Execution of BIDOUT instruction END processing END processing Completion of transmission by a BIDOUT BIDOUT instruction ON Completion device OFF ON Status display device OFF at completion Abnormal completion Normal completion One scan Error (1) When a dedicated instruction is completed, the abnormal completion signal (D)+1, turns on and the error code is stored in the trans
12 DEDICATED INSTRUCTIONS 1) 2) 3) 4) 5) 6) 7) 8) 9) 1) 2) 3) 4) 5) 6) 7) 8) 9) 12 - 26 Transmission command is converted into pulse. Transmission data is stored. Specify the number of the interface (CH ) that sends the data. Clear the transmission result storage device to 0. Specify the transmission data count in word units. (Specify K10 when the unit is bytes.) The transmission data stored in the specified device is sent.
12 DEDICATED INSTRUCTIONS 12.7 G(P).BIDIN Data can be received using the bidirectional protocol. Applicable device Setting data Internal device (System, user) Bit File register Word Link direct device J \ Bit Word Intelligent function Index register Constant module device Zn U \G (S) — — (D1) — — Others — (D2) [Instruction code] [Executing condition] Command G.BIDIN G.BIDIN Un (S) (D1) (D2) GP.BIDIN Un (S) (D1) (D2) Command GP.
12 DEDICATED INSTRUCTIONS Function (1) The function stores in the device designated in (D1) and succeeding devices the data received via the bidirectional protocol of the module designated in Un, according to the control data of the device designated in (S) and succeeding devices.
12 DEDICATED INSTRUCTIONS (3) Whether a BIDIN instruction was completed normally can be checked by the completion device ((D2)) or status display device at completion ((D2)+1). (a) Completion device: Turns on at the END processing of the scan where the BIDIN instruction is completed normally, and turns off at the next END processing. (b) Status display device at completion: Does not change when left off.
12 DEDICATED INSTRUCTIONS 1) 2) 3) 4) 5) 6) 7) 1) 2) 3) 4) 5) 6) 7) 12 - 30 Specify the receive channel. Clear the receive data count storage device to 0. Specify the allowable receive data count. Store the receive data in the specified device. After completed, the receive data within the allowable receive data count (user-specified) is read from the receive data storage area in the buffer memory.
12 DEDICATED INSTRUCTIONS 12.8 G(P).SPBUSY This instruction reads the status of data transmission and reception executed with dedicated instructions. Applicable device Setting Internal device data (System, user) Bit Link direct device J \ File register Word Bit Intelligent function module device Word Index register U \G Zn Constant Others — (D) [Executing condition] [Instruction code] Command G.SPBUSY G.SPBUSY Un (D) GP.SPBUSY Un (D) Command GP.
12 DEDICATED INSTRUCTIONS Error (1) In case of operation errors, the error flag (SM0) turns on and the error code is stored in SD0. Refer to the following according to the error code, and check and correct the error. 4FFFH or less: MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) 7000H or later: Section 15.2 Program example A program that reads the communication status of a target module.
12 DEDICATED INSTRUCTIONS 12.9 ZP.CSET (Receive data clear) Applicable device Setting Internal device data (System, user) Bit Link direct device File register J \ Word Bit Intelligent function module device Word Index register Constant Zn U \G K, H Others — — (S1) — (S2) — — (D1) — — (D2) — [Instruction code] [Executing condition] [Instruction form] ZP.CSET Setting data ZP.
12 DEDICATED INSTRUCTIONS Function (1) This function clears reception data in the OS area. It does not clear the user data reception area in the buffer memory. (2) If the CSET instruction is executed while the reception data read request (X3/XA) or reception abnormal detection signal (X4/XB) is turned on, the CSET instruction is kept waiting until the signal is turned off.
12 DEDICATED INSTRUCTIONS (4) The status of the CSET instruction, whether it is being executed or completed normally/abnormally, can be checked by the complete device (D2) specified by the setting data. (a) Complete device ((D2) + 0) This device turns on at the End processing of the scan at which the CSET instruction is completed and turns off at the next End processing. (b) Complete device ((D2) + 1) It turns on/off by the status at which the CSET instruction is completed.
12 DEDICATED INSTRUCTIONS Program example This is an example of a program that clears reception data on the C24 side. It is assumed that the input/output signals of the C24 are X/Y00 to X/Y1F. 1) 2) 3) 4) 5) 3 6) 7) 1) 2) 3) 4) 5) 6) 7) 12 - 36 Set the execution type. Set the request type (Reception data clear) Execute the reception data clear Normal completion Abnormal completion The error code in the completion status storage device is saved in D300.
13 DEBUG SUPPORT FUNCTION 13 DEBUG SUPPORT FUNCTION The debug support functions are designed to support the debugging of communication processing between the C24 and external device. The following functions are available to ease system startup work. • Circuit trace • State monitor • Protocol execution log display storage function (for predefined protocol only) 13.1 Circuit Trace 13 The communication data and communication control signal between the C24 and external device are traced.
13 DEBUG SUPPORT FUNCTION 13.1.1 Procedure for the circuit trace The following shows the procedure for the circuit trace. Start of circuit trace Start circuit trace from GX Works2. 13 Communicating with the external device Stop circuit trace in GX Works2. Circuit trace results are displayed. Confirm send/receive packet data and communication control signals.
13 DEBUG SUPPORT FUNCTION 13.1.2 Execution of the circuit trace The trace data is stored in the monitor buffer to trace the communication data and communication signal status. [Basic operation] 1. GX Works2 [Tool] [Intelligent Function Module Tool] Communication Module] [Circuit Trace] [Serial 2. Click the Module Selection button to select the module to trace in the "Module Selection (Circuit Trace)" screen. Click the OK button. 3.
13 DEBUG SUPPORT FUNCTION [Display/Setting screen] [Display/Setting details] Item Trace Result Currently Displayed Data Find Packet Data… button Communication control signals Display/Setting details — Displays the model name, measurement time, and extraction date/time of the module on which the circuit trace is executed. Select the display format of the send/receive packets. The hexadecimal or ASCII code can be selected.
13 DEBUG SUPPORT FUNCTION 13.1.3 Circuit trace option setting In the circuit trace option setting, the following two items can be set. • The monitor buffer area starting address and size of the C24 that stores the circuit trace data (hereinafter referred to as the monitor buffer area) • Whether the circuit trace is stopped or continued when the timer 0 time out error occurs [Basic operation] 1. Display the "Circuit trace" screen in the following procedure.
13 DEBUG SUPPORT FUNCTION 3. In the "Circuit Trace Option" screen, set "Start Address", "Size", and "Stop Setting" of the monitor buffer area, and click the OK button. [Display/Setting details] Item Circuit Trade Data Storage Area Setting Start Address Display/Setting details — Set the starting address of the monitor buffer area. Input the setting in hexadecimal. • Input range CH1/CH2: 2600H to 3FFDH (C00H to 1AFDH for the user setting area) Size Set the size of the monitor buffer area.
13 DEBUG SUPPORT FUNCTION 13.2 State Monitor The following items are monitored. • Signals of the C24 • Communication error information • Operation setting switches • Protocol execution status during the predefined protocol communication [Basic operation] 1. Display the "Predefined Protocol Support Function" screen. For the method for displaying it, refer to Section 9.1. 2. Display the "Module Selection" screen in the following procedure.
13 DEBUG SUPPORT FUNCTION (1) "Signal" tab [Display/Setting screen] [Display/Setting details] Item 13 - 8 Display/Setting details X signal state monitor Displays the ON/OFF status of the X signals. Y signal state monitor Displays the ON/OFF status of the Y signals. RS-232 signal monitor Displays the ON/OFF status of the RS-232 control signals.
13 DEBUG SUPPORT FUNCTION (2) "Error Information" tab [Display/Setting screen] [Display/Setting details] Item Display/Setting details Communications Error Status Displays the communication error status. Switch Setting, Mode Switching Error Communication Result Error Reset button 13 - 9 Displays the switch setting and/or mode selection error status. Displays the error status of the communication result. This button is valid when the CH1 ERR. occurrence (XE) or CH2 ERR.
13 DEBUG SUPPORT FUNCTION (3) "Operation Setting Switch" tab [Display/Setting screen] [Display/Setting details] Item Switch Setting Status for The Operation 13 - 10 Display/Setting details Displays the operation switch setting status. Mode Switch Displays the predefined protocol setting. Station Switch Displays the station number setting.
13 DEBUG SUPPORT FUNCTION (4) "Predefined Protocol Function" tab [Display/Setting screen] [Display/Setting details] Item Execution Status Displays the protocol execution status. Protocol Cancel Designation Displays the protocol cancel designation status. Predefined Protocol Function Error Code 13 - 11 Display/Setting details Displays the error code of the result from the error completion.
13 DEBUG SUPPORT FUNCTION 13.3 Protocol Execution Log Display Storage Function (for Predefined Protocol only) This function checks the detailed predefined protocol execution status and results for each channel. Up to 32 protocol execution logs can be checked. If the number of the stored logs exceeds 32, the oldest log will be overwritten. The protocol execution log can be checked in the following method.
13 DEBUG SUPPORT FUNCTION 13.3.1 Checking with GX Works2 Check the protocol execution logs and protocol execution results in the "Protocol execution log" screen of GX Works2. [Basic operation] 1. Select a module to debug. 1) Display the "Predefined Protocol Support Function" screen. For the method for displaying it, refer to Section 9.1. 2) Display the "Module Selection" screen in the following procedure.
13 DEBUG SUPPORT FUNCTION [Display/Setting screen] POINT The logs displayed in the "Protocol execution logs" screen can be selected from the following two, according to the log registration condition. • Displaying only the failed protocols. • Displaying all execution statuses and execution logs. The log registration condition can be set in "Execution log options" in the "Various_Control_Specification" screen of GX Works2.
13 DEBUG SUPPORT FUNCTION 13.3.2 Checking with the buffer memory Check the protocol execution logs in the execution log storage area. [Basic operation] 1. The log registration condition can be set by the execution log option specification for the buffer memory (address: 40E2H/40F2H). b15 Buffer memory address : 40E2H/40F2H b0 0 1/0 Log registration condition 0(OFF) : Register failed protocols only. 1(ON) : Register all protocol execution states and results. 2. Execute the CPRTCL instruction. 3.
14 MAINTENANCE AND INSPECTION 14 MAINTENANCE AND INSPECTION 14.1 Inspection Items This section explains the inspection items of the C24. 1) Check if the terminating resistors and cables are connected securely. 2) Verify that the terminal screws and the terminal block installation screws are securely tightened. For items other than the listed above, perform inspection according to the inspection items listed in the user's manual of the CPU module, in order to always use the system in the optimal condition.
14 MAINTENANCE AND INSPECTION 14.2 When Replacing Modules When replacing the C24 and LCPU, it becomes necessary to register the following data again for the module to be replaced. • C24: System setting data in the flash ROM • LCPU: PLC parameters (I/O assignment, switch setting, etc.) Please read the following manual before replacing the module, and make sure to pay attention to safety and handle the module properly during the operation.
14 MAINTENANCE AND INSPECTION 4) Click the Detail button ((b) in the illustration) and select the target memory to read in the "Target to Read and Write Detail Setting" screen. 5) Select the "Target" check box in the "Memory for Read and Write". ((c) in the illustration) 6) Select the "valid" check box of the C24. ((d) in the illustration) 7) Click the Execute button. ((e) in the illustration) 8) After reading data from the Programmable controller, save the project.
15 TROUBLESHOOTING 15 TROUBLESHOOTING This chapter explains the corrective actions when an error occurs in the C24and the error codes. For the trouble shooting from the display unit, refer to MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection). 15.1 Checking the Status of the C24 This section explains how to check the status of communication between the C24 and external devices, the transmission status, and the switch setting status. This checking is performed with GX Works2.
15 TROUBLESHOOTING 15.1.1 Checking the H/W LED information The transmission status and communications error status of the C24 can be checked. (Contents of 201H/202H of the buffer memory are displayed.) When a communication error occurs, take corrective action according to Section 15.3. POINT Each of the communications error status, SIO, PRO., P/S, C/N, CH1 ERR. and CH2 ERR., turns on when an error occurs, and keeps its on-status even after the communication returns to normal.
15 TROUBLESHOOTING (2) Screen items (a) SD WAIT Indicates "Transmission wait status". Value 0001(ON) Status Description Waiting for data Data cannot be sent to the external device by the transmission transmission control of the C24 (waiting for data transmission). • The transmission cannot be started. • A terminate transmission request (DC3 received/ DR(DSR) signal off) is received from the external device during message transmission.
15 TROUBLESHOOTING (c) PRO. Indicates "Character error status". Value 0001(ON) Status Error occurred. Description Character error occurred. Keeps its on-status even after the communication returns to normal. Initialize the error information as necessary. For details, refer to Section 15.1.2. 0000(OFF) Normal - (d) P/S Indicates "Status of parity error or sum check error". Value 0001(ON) Status Error occurred. Description Parity error or sum check error occurred.
15 TROUBLESHOOTING (g) ACK. Indicates "Normal completion status". Value 0001(ON) 0000(OFF) Status Description Normal When the C24 could receive data normally, the C24 completion sent a response message (ACK message) to the transmission external device to notice the normal completion. Abnormal When the C24 could not receive data normally, the completion C24 sent a response message (NAK message) to the transmission external device to notice the abnormal completion. (h) NEU.
15 TROUBLESHOOTING 15.1.2 Checking the H/W switch information The details of switch information can be monitored. (1) Method for displaying Select [Diagnostics] [System Monitor…] and click the H/W Information button in GX Works2. H/W switch Information (2) Screen items Item 1 CONFIG Description Displays the communication rate setting and transmission setting on the CH1 side. CH1 MODE 2 CONFIG Displays the communication protocol setting on the CH1 side.
15 TROUBLESHOOTING (a) 1 CONFIG, 2 CONFIG The following shows the communication rate setting and transmission setting of the CH1 side (1 CONFIG) and CH2 side (2 CONFIG).
15 TROUBLESHOOTING (b) CH1 MODE, CH2 MODE The following shows the communication protocol setting of CH1 side (CH1 MODE) and CH2 side (CH2 MODE).
15 TROUBLESHOOTING 15.1.3 Reading the RS-232 control signal status This section explains how to read the control signal status stored in the buffer memory during communication using RS-232 interface. When using GX Works2, check in the "Intelligent Function Module Monitor" screen. (Refer to the GX Works2 Version1 Operating Manual (Intelligent Function Module).) When a transmission problem occurs, read operation is executed to check the signal on/off status of the RS-232 interface.
15 TROUBLESHOOTING 15.1.4 Reading the data communication status (Transmission sequence status) This section explains how to read the current status of the data communication using the MC protocol stored in the buffer memory. When using GX Works2, check in the "Intelligent Function Module Monitor" screen. (Refer to the GX Works2 Version1 Operating Manual (Intelligent Function Module).
15 TROUBLESHOOTING 15.1.5 Reading the switch setting status This section explains how to read the switch setting status of the C24. When using GX Works2, check in the "Intelligent Function Module Monitor" screen. (Refer to the GX Works2 Version1 Operating Manual (Intelligent Function Module).) REMARKS (1) The switch settings can be changed when the mode is switched or when the UINI instruction is executed. (The station No. setting can be changed only when the UINI instruction is executed.
15 TROUBLESHOOTING (2) Example of a program that reads from the setting status storage area The following shows an example of a program that reads the setting of various switches of the C24 from the setting status. For details on ERR. occurrence (XE/XF) of the input/output signals used in the program, refer to Section 15.4 (3). (input/output signals X/Y00 to X/Y1F of the C24) Example of FROM instruction Reads error description from address 203H.
15 TROUBLESHOOTING 15.1.6 How to read the current operation status This section explains how to read the current operation status of the C24. When using GX Works2, check in the "Intelligent Function Module Monitor" screen. (Refer to the GX Works2 Version1 Operating Manual (Intelligent Function Module).) REMARKS • The status of the switch settings by GX Works2 can be checked by performing read operations as described in Section 15.1.5. • Refer to Section 7.3 for the switch settings.
15 TROUBLESHOOTING (2) Example of a program that reads from the current setting status storage area The following shows an example of a program that reads from the switch setting status for current operation of the C24. For details regarding ERR. occurrence (XE/XF) used in the program, refer to Section 15.4 (3). (input/output signals X/Y00 to X/Y1F of the C24) Example of FROM instruction Reads error description from address 203H.
15 TROUBLESHOOTING 15.2 Error Code When a trouble such as external device communication failure has occurred, the error cause can be identified by an error code. 15.2.1 How to check the error codes Error codes can be checked on GX Works2. (Refer to (1) in this section.) REMARKS By using GX Works2, error history of the entire system can be checked even after errors were cleared by turning the power off to on, or by resetting the CPU module or the head module. (Refer to (1) (b) in this section.
15 TROUBLESHOOTING (b) Checking on the "Error History" screen On this screen, errors including those occurred in other modules are displayed in chronological order, and the data can be output in a CSV file. Error code and date and time of error occurrence can be checked even after powering OFF and then ON the CPU module or after resetting the CPU module or head module. On GX Works2, select [Diagnostics] [System Monitor] and click the System Error History button.
15 TROUBLESHOOTING • Intelligent Module Information The status of the C24 when the error, which is currently selected under "Error History List", had occurred is displayed. For the C24, the following will be displayed. Item Channel where error occurs Description Channel on which an error has occurred. Communication error and LED ON status of the LED ON status, communication error channel on which an error has occurred. status (Value of the buffer memory address 201H/202H is displayed.
15 TROUBLESHOOTING 3) Create CSV File… button Click this button to output the module error history in a CSV file. POINT (1) If errors have frequently occurred in the C24, "*HST.LOSS*" may be displayed instead of error codes in the Error Code column. (Example) If too many "*HST.LOSS*" are displayed, increase the number of errors to be collected per scan in the "PLC RAS" tab of the "PLC Parameter" dialog box.
15 TROUBLESHOOTING 15.2.2 Error code list The following shows the error codes, error contents, and corrective actions for errors that are generated during data communication. (" " in the table is the error code when the target CPU module is not a Q/L/QnACPU.) The signal name in the following table indicates the CH side LED on status or communication error status that is stored into buffer memory address 201H/202H when an error occurs.
15 TROUBLESHOOTING Error code (Hexadecimal) 7144H 7145H 7146H 7147H 7148H 7149H 714AH 714BH 714CH 714DH 714EH Error Description Signal name Corrective action Protocol NonBiPreMC proce- direcdefined dural tional • Monitoring was requested before the • Write the device to be monitored before PRO. device to be monitored was written. issuing a monitor request. • The written PC No. and PC No. in the C/N • Check the transmit message from the monitor request are different.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description 7164H Request error • Either the request or the device designation method is wrong. 7166H System error • The OS of the C24 detected some error. 7167H Cannot execute a command during RUN 7168H C/N • If there is an error in the CPU module, remove the CPU error and restart data communications. • The OS of the C24 detected some error. 7171H 7172H 7173H 7D00H 7D01H 7D02H • A device that cannot be designated was designated.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description • The protocol No. specified in control data for the CPRTCL instruction is not registered to the C24. • The CPRTCL instruction was executed with no protocol setting data written. Signal name 7D10H Protocol unregistered error 7D11H Protocol simultaneous execution error 7D12H Transmission monitoring timeout error 7D13H Receive wait timeout error • Receive wait time has timed out.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description Corrective action MC Protocol NonBiPreproce- direcdefined dural tional • When data are received by the protocol • Correct the data sent from the device. including a packet that contains a conversion variable (variable number of CHn • Check the packet format of the external data), the number of digits ERR. device to see if the number of digits is corresponding to the variable is set correctly. insufficient.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description • 7E42H Error count error, protocol setting data write error • • • 7E43H Device error • • Signal name Corrective action • Modify the setting of the transmit message from the external device so that the request will not exceed the limit Number of processing points exceeds of processing points that are allowed for the range allowed for the command. one transmission and predetermined for Protocol setting data were written to the PRO.
15 TROUBLESHOOTING Error code (Hexadecimal) Error 7E57H Flash ROM write error 7E58H Mode modification error 7E59H Flash ROM write count over limit error Description • Writing to the flash ROM failed. • Power is turned off during writing to Flash ROM. • There is an error in the mode No. or transmission specifications after changing the mode. • Writing to flash ROM was performed 1000 times after power-on. Signal name Corrective action ⎯ or • Re-execute the write operation.
15 TROUBLESHOOTING Error code (Hexadecimal) 7E6EH Error System error Description • The OS of the C24 detected some error. Signal name Corrective action ⎯ ( 1) 7E6FH Modem connection error • Modem is connected to an incorrect channel. ⎯ • Correct the setting of the destination channel to which data or notification is sent with the modem function. 7E70H CPU module error • The communication with the CPU module was not performed normally.
15 TROUBLESHOOTING Error code (Hexadecimal) Description Signal name 7F21 H Receive header area error • There is an error in the command (frame) part. • An ASCII code that cannot be converted to binary code was received. PRO. 7F22 H Command error • A nonexistent command, subcommand, • Check and correct the external device transmit message and restart data or device was designated. PRO. communications. • The remote password length is wrong.
15 TROUBLESHOOTING Error code (Hexadecimal) 7F67H 7F68H Error Description Overrun error • The C24 received the next data before it completed receive processing of the previous data. Framing error • Data does not match the stop bit setting. • A malfunction occurred in the network because the power source of the partner station was on or off. • Noise occurs in the network. • When the multidrop was connected, data was transmitted simultaneously by multiple devices.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description Signal name Corrective action Protocol NonBiPreMC proce- direcdefined dural tional 7F91H to 7F96H 7F98H to 7F9AH 7F9DH 7F9EH 7FA0H to 7FA3H 7FA8H 7FAAH to 7FADH System error • The OS of the C24 detected some error.
15 TROUBLESHOOTING Error code (Hexadecimal) Error Description Signal name Corrective action 7FF0H Dedicated instructions simultaneous execution error • Executed dedicated instructions simultaneously. ⎯ • Do not use dedicated instructions simultaneously. 7FF1H Control data error • Setting value is incorrect. • Setting value is out of range. ⎯ • Correct the setting value in the control data.
15 TROUBLESHOOTING 15.2.3 A compatible 1C frame communications error code list The following table lists the error code, error contents, and corrective action for errors generated during A compatible 1C frame communications. Error code (Hexadecimal) Error Signal name Error Contents Corrective action Protocol NonBiPreMC proce- direcdefined dural tional • Change the setting to enable online change and restart data C/N communications. • Stop the CPU and restart data communications.
15 TROUBLESHOOTING 15.2.4 Error code list while modem function is used The following describes the error codes, contents and corrective actions for errors (including errors at the abnormal completion) that may occur while the C24 modem function is used. The error codes for the modem function are stored in the modem function error code (address : 221H(545)).
15 TROUBLESHOOTING Error code (Hexadecimal) Error Error Contents Signal name There is an error in the designation of the user frame number. • Recheck the user frame number. • Designate the registered user frame number. • Register the designated data for initialization. There is an error in the designation of the output head pointer. • Designate the output head pointer in the range of 1 to 100. • Designate the position (n-th position) where the data for initialization number is designated.
15 TROUBLESHOOTING 15.3 Troubleshooting by Symptom This following shows troubleshooting of trouble generated during communications between the C24 and external device according to the trouble symptom. When trouble occurs, first confirm the status of the C24 and check the relevant item in the table below. Protocol Symptom Symptom description Cannot communicate via modem ( 1) Bidirectional Predefined Reference • "RUN" LED turned off. Section 15.3.
15 TROUBLESHOOTING REMARKS The following are precautionary notes when exchanging data with an external device via one of the C24 interfaces. (1) When the power supply to the C24 or external device is started, the remote device that is connected may generate a reception error. (2) If the remote device that is connected starts up while data is being transmitted, the remote device side will generate a reception error.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.1 The "RUN" LED is turned OFF • A transmission setting • Set the switch by GX Works2 correctly and switch is set to an after writing to the CPU module reset the unusable position. CPU. • Remove the cause of the CPU module error and reset the CPU. Note • CPU module error.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.2 The "RD" LED does not blink even after message transmission from the external device • Check if the C24 and external RD(RXD) and • Signal lines are not connected correctly. SD(TXD) signal lines are cross connected. • Use the external device OPEN statement to check if the opened port and the cable connection port are matched.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.3 No response message is returned even though the external device transmitted a message and the "RD" LED blinked • Check if the communication protocol is set correctly. • Check if the mode was switched without using the buffer memory mode switching area. • Communication protocol is Note set incorrectly.
15 TROUBLESHOOTING • Due to the OFF status of the CS(CTS) signal, the C24 cannot transmit data to the external device. • Although a transmission request • Due to transmission was made, "SD" does control (DTR or DC not blink. control), the external device cannot receive data. 15 - 39 Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.
15 TROUBLESHOOTING • Communication protocol is set incorrect. Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.5 Read request signal does not turn ON even though the external device transmitted a message and the "RD" LED was blinking • Check if the communication protocol is set correctly. • Check if the mode was switched without using the buffer memory mode switching area.
15 TROUBLESHOOTING • Incorrect protocol No. is specified in the control data. Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.6 The CPRTCL instruction execution is not completed although the "RD" LED blinked • Check the protocol No. specified in the control data for the CPRTCL instruction for an error. • The CD terminal is OFF • If the CD terminal is OFF with "CD terminal check when "CD terminal check enabled" set, messages will not be read.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.7 Communication error "NAK" • Refer to section that describes the communication error signal ("C/N", "P/S", • Take corrective action corresponding to the "PRO", "SIO") that are contents of the error. turned on simultaneously when the "NAK" signal is turned on.
Bidirectional Nonprocedural Predefined Nonprocedural Predefined Corrective action Bidirectional Cause MC Symptom MC 15 TROUBLESHOOTING • An error was generated on • Check the error contents from the state of the CC-Link IE Controller SB and SW related to the CC-Link IE Network. Controller Network with the GX Works2 monitor, etc.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.10 Communication error "PRO." • Check the C24 communication protocol setting and • Communications were the message from the external device and match the performed with a control settings, or correct the message and restart data procedure different from the communications. C24 communication protocol • Use the communication monitoring function to check setting. the message from the external device.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.11 Communication error "SIO" • Data does not match the • Check if the C24 and external device settings stop bit setting. are the same. • Transmission rate is too • Decrease the transmission rate and restart data communications. fast and the next data is transmitted before the C24 completes processing of the receive data. • Data larger than the receive buffer size was received.
15 TROUBLESHOOTING • There is an error in the Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.12 Communication error "CH1 ERR." or "CH2 ERR." • Read the error code from the buffer memory communication protocol or and check the error contents and change transmission setting. the switch setting to the correct setting.
• The user-edited protocol Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15 TROUBLESHOOTING • Check the packet format of the external setting in the predefined device, and correct the protocol setting.
15 TROUBLESHOOTING • With a multidrop link, two or more devices transmitted data at the same time. • The signal cable wiring connection is faulty. Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.13 Communication is intermittent • Connect the external devices and the C24 in a 1:1 configuration and perform a communications test.
15 TROUBLESHOOTING 2) When the following problem occurs at the time of access to other station CPU module, clear the programmable controller CPU information and retry. (Refer to Section 15.5.) • Accessible device range is narrowed. (Error code: 7140H) • Some of commands and/or devices cannot be used. (Error code: 7142H, 714DH) (b) When response messages cannot be received Change the setting value for the response monitoring time (timer 1, default value is 5 seconds).
15 TROUBLESHOOTING • With a multidrop link, Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.14 Undecodable data are transmitted or received • Connect the external devices and the C24 in a two or more devices 1:1 configuration and perform a transmitted data at the communications test. same time.
15 TROUBLESHOOTING Predefined Corrective action Nonprocedural Cause Bidirectional Symptom MC 15.3.15 Whether the communication error is caused on the C24 or external device is unclear • Test the C24 as described below to check where the cause is. 1) Check the hardware. • The C24 must be installed firmly. • The pins of the C24 must not be bent or otherwise abnormal. 2) Test the C24 alone. (Refer to Section 6.4.) • ROM/RAM/switch test must not generate any errors.
15 TROUBLESHOOTING 15.3.16 Communication is not available via the modem Symptom Cause • A modem initialization error occurs. • Auto modem initialization cannot be executed. • Data cannot be communicated with GX Works2 supporting the C24. NonBidirectional procedural Predefined protocol protocol MC NonBidirectional procedural protocol protocol • Check the error code and execute processing accordingly. • There is an error in the switch settings in GX Works2. • Review the switch settings.
15 TROUBLESHOOTING 15.3.18 Constant cycle transmission is not performed normally Symptom • Does not operate in the cycle time designated in the constant cycle transmission setting Cause Corrective action • The setting value of the constant cycle transmission is incorrect. • Review the constant cycle transmission setting. • The cycle time is affected by some causes. • Remove the causes or designate the cycle time anticipating the causes.
15 TROUBLESHOOTING 15.3.22 Troubleshooting on the protocol setting data reading/writing Symptom • The "ERR." LED turns on when protocol setting data are written to the C24. Cause • The user-edited protocol setting in the predefined protocol support function of GX Works2 has an error. Or, function data not supported by the C24 are included in the protocol setting data.
15 TROUBLESHOOTING 15.4 Initializing Error Information of the Serial Communication Module This section explains the ERR. LED ON factors and the error code initialization (clear) for the C24. (1) ERR. LED ON factors When any of the following errors occurs, its error code is stored in the buffer memory corresponding to the interface (CH) where the error occurred, and the ERR. LED turns on.
15 TROUBLESHOOTING (b) Initializing communication error information by writing Communication error information can be initialized by writing "1" to the corresponding bit in the communication error clear request and to turn LED off (address: 0H/1H). The indicator LED and communication error information may be turned on/off in the following cases: • NEU. to NAK turn on/off depending on the status. • C/N to SIO turn on when errors occur and keep the ON-status even after the operation returns to normal.
15 TROUBLESHOOTING (c) Examples of programs that initialize indicator LED and communication error information The following shows examples of a program that reads error codes when errors described in (1) above occur in an interface on the CH1 side and initializes the indicator LED and communication error information. Incorporate the necessary part of the program.
15 TROUBLESHOOTING REMARKS When data is communicated using the MC protocol, the ERR. LED may not be turned on if the C24 sends an NAK message to the external device in response to the command message. Error codes corresponding to the error content when the NAK message is sent back to the external device are stored in the following areas. (When communicating with an A compatible 1C frame, the error codes differ from the transmission error code.
15 TROUBLESHOOTING 15.5 Clearing the Programmable Controller CPU Information This section explains how to clear the programmable controller CPU information. (1) Programmable controller CPU information (a) This is the information about the access target CPU module type used in MC protocol communications. The C24 obtains this information from the access target CPU module at the time of initial access, and stores it inside the C24.
15 TROUBLESHOOTING (4) Executing the programmable controller CPU information clear request (a) Executing from GX Works2 1) In the "Intelligent Function Module Monitor" screen, set "4C43H" to buffer memory address 80H. 2) In the Buffer Memory Batch monitor screen, check that the value in buffer memory address 80H is "0000H".
APPENDICES APPENDICES Appendix 1 Buffer Memory The buffer memory is the memory of the C24 used for storing data sent to or received from the CPU module. (Setting values, monitor values, etc.) Initial values are set to the buffer memory. When changing the initial values, set the parameters in GX Works2 and write them to the flash ROM. For details, refer to (3). (1) Structure of the buffer memory A buffer memory consists of a user area and a system area, as shown below.
APPENDICES (3) Procedure for writing the buffer memory to the flash ROM (a) Displaying the screen for writing to the flash ROM Open the "Flash ROM Operation" screen by the following procedure. Parameter setting screen [Tool] [Flash ROM Operation] (b) Executing the write operation to the flash ROM Select "Request of Flash ROM Write" in the Execution Item area and click the Execute button.
APPENDICES IMPORTANT Do not write data in the "System area" of the buffer memory. If data is written to any of the system areas, the programmable controller system may malfunction. Some of the user areas are partially system areas. Care must be taken when performing read/write to the buffer memory.
APPENDICES Address Decimal (Hex) Application CH1 CH2 0 (0H) Initial value Name MC Non Bi Registration Reference Not allowed Section 15.1.1 Section 15.4 Not allowed — Pd Communication error clear request for CH1 and to turn LED off 0: ON, No initialization request 1: OFF, Initialization requested SD WAIT (b0) C/N (b4) — SIO (b1)) NAK (b5) PRO. (b2) ACK. (b6) P/S (b3) NEU.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Initial value Name 57 to 127 Use prohibited System area (39H to 7FH) For programmable Programmable controller CPU information clear request 128 controller CPU 0000H: No request (80H) information 4C43H: Requested clear Protocol MC Non Bi Registration Reference Pd — 0 — RW Not allowed 129 to 143 Use prohibited System area (81H to 8FH) Section 15.5 — Switching mode no.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name For designation Communication system designation (for RS-232) 312 of communication (138H) 0: Full duplex communication 1: Half-duplex communication control For half- duplex Simultaneous transmission priority/non-priority designation 313 153 communications 0: Priority (99H) (139H) control 1 to 125: Non-priority (transmission wait time, unit: 100 ms) 314 designation (RS- Retransmission time transmission method designation 154 (9AH) (13AH) 232) 0: D
APPENDICES Address Decimal (Hex) CH1 CH2 Application Initial value Name 178 to 338 to For designation Last frame No. designation (1st to 4th) 181 341 0H: No designation 1H or more: Last frame No. (B2H to (152H to of receive user 0: No transmission B5H) 155H) frame 1 or more: Output frame No. designation User frame being transmitted 0 : Not send 1 to 100: User frame being transmitted (nth) CR/LF output designation 0: Do not send. 1: Send.
APPENDICES Address Decimal (Hex) CH1 CH2 515 (203H) Application For confirmation of switch setting and mode switching 516 (204H) Name Switch setting error and mode switching error status 0: No error Other than 0: Switch setting error and mode switching error CH1 Communication protocol setting No. (b0) 0: Normal 1: Error CH1 Communication rate setting (b1) 0: Normal 1: Error CH1 Setting change prohibit time mode switching (b3) 0: Normal 1: Error CH2 Communication protocol setting No.
APPENDICES Address Decimal (Hex) CH1 CH2 591 (24FH) 592 608 (250H) (260H) 593 609 (251H) (261H) 594 610 (252H) (262H) 595 611 (253H) (263H) 596 612 (254H) (264H) 597 613 (255H) (265H) 598 614 (256H) (266H) 599 615 (257H) (267H) 600 616 (258H) (268H) 601 617 (259H) (269H) App. - 9 Application For confirmation of station No. setting status Name Initial value Protocol MC Non Bi Registration Reference Not allowed Section 7.3 Section 15.1.6 Pd Depen Station No.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name MC protocol transmission error code (excludes A compatible 1C frame communication) For confirmation 0: No error 1 or more: Transmission error code of communication Receive user frame (nth) 603 619 result 0 : Not received (25BH) (26BH) 1 to 4: Combination of user frame No.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name Initial value Protocol Registration Reference MC Non Bi Pd 7814 to 7854 (1E86H to 1EAEH) 7855 to 7895 (1EAFH to 1DE7H) 7896 to 7936 (1ED8H to 1F00H) 7937 to 7977 (1F01H to 1F29H) For designation 7978 to 8018 (1F2AH to 1F52H) of user registration data 8019 to 8059 (1F53H to 1F7BH) 8060 to 8100 (1F7CH to 1FA4H) 8101 to 8141 (1FA5H to 1FCDH) 8142 to 8182 (1FCEH to 1FF6H) For registration No.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name Transmission control start free area designation 64 to 4,095: transmission control start free area Transmission control end free area designation 8211 8467 For transmission 263 to 4096: transmission control end free area (2013H) (2113H) control Nonprocedural and non reception monitoring time format designation designation 8212 8468 8210 8466 (2012H) (2112H) (2014H) (2114H) 8213 to 8215 (2015H to 2017H) 0: Format-0 8469 to 8471 (2115H Use prohi
APPENDICES Address Decimal (Hex) CH1 CH2 Name Application Transmission pointer designation (For fixed cycle transmission and data transmission) 0: No designation 8260 8516 1 to 100: Output head point (send from the nth) (2044H) (2144H) Send the user frames designated in the following transmission For designation frame No. designation areas from the designated pointer position.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name Transmission pointer designation (for condition agreement transmission and nonprocedural data transmission) 0: No designation 1 to 100: Output head point (send from nth) 8422 8678 Send the user frames designated in the following (20E6H) (21E6H) transmission frame No. designation areas from the designated pointer position.
APPENDICES Address Decimal (Hex) CH1 CH2 Application Name 8944 (22F0H) Callback permit accumulated count 0 or more: Accumulated count 8945 (22F1H) Callback denial accumulated count 0 or more: Accumulated count 8946 (22F2H) For callback function Auto (callback) connection permit accumulated count 0 or more: Accumulated count 8947 (22F3H) Auto (callback) connection denial accumulated count 0 or more: Accumulated count 8948 (22F4H) Accumulated count of callback receive procedure cancel 0 or more:
APPENDICES Address Decimal (Hex) CH1 CH2 Application 16429 (402DH) 16430 (402EH) 16431 (402FH) 16432 (4030H) 16433 (4031H) 16434 (4032H) 16435 (4033H) 16436 to 16447 (4034H to 403FH) Protocol Registration Reference Not allowed — MC Non Bi Pd Matched receive packet No. 2 Matched receive packet No. 3 Predefined protocol function Matched receive packet No. 4 control data specification Matched receive packet No. 5 0 — R Matched receive packet No. 6 Matched receive packet No.
APPENDICES Address Decimal (Hex) CH1 CH2 16522 to 16527 (408A H to 408FH Application Use prohibited Checking protocol setting data 16537 to 16607 Use prohibited (4099H to 40DFH) 16608 to 16624 to 16609 16625 Use prohibited (40E0H to (40F0H to 40E1H) 40F1H) Protocol Initial value 0 4091 H 4092 H 4093 H 4094 H 4095 H 4096 H 4097 H 4098 H 0 — R — System area — Number of stored protocol execution logs 0: No log 1 to 32: Number of stored logs 0 16641 18433 (4101H) (4801H) Protocol execution
APPENDICES Address Decimal (Hex) CH1 CH2 16677 18469 (4125H) (4825H) Application Initial value Name 0 — R — R 16679 (4127H) 18471 (4827H) Matched packet No. 0: Error occurred, or Communication type of the executed protocol is “Send only”. 1 to 16: Matched packet No.
APPENDICES Address Decimal (Hex) CH1 CH2 16690 to 18482 to 18177 19969 (4132H to (4832H to 4701H) 4E01H) 18178 to 19970 to 18429 20223 (4702H to (4E02H to 47FDH) 4EFFH) 20224 to 20479 (4F00H to 4FFFH) Application Name Checking protocol execution log Execution log 2 to 32 Use prohibited System area Same as Execution log 1 20480 to 24575 (5000H to 5FFFH) Send/receive area for prePredefined protocol function buffer defined protocol function 24576 to 32767 (6000H to 7FFFH) Use prohibited System are
APPENDICES (a) [CH1 side buffer memory address: decimal (hexadecimal)] N-th block monitoring device 5 6 7 1 2 3 4 8272 (2050H) 8281 (2059H) 8290 (2062H) 8299 (206BH) 8308 (2074H) 8317 (207DH) 8273 to 8274 (2051H to 2052H) 8282 to 8283 (205AH to 205BH) 8291 to 8292 (2063H to 2064H) 8300 to 8301 (206CH to 206DH) 8309 to 8310 (2075H to 2076H) 8275 (2053H) 8284 (205CH) 8293 (2065H) 8302 (206EH) 8376 (2054H) 8277 (2055H) 8278 (2056H) 8385 (205DH) 8286 (205EH) 8287 (205FH) 8294 (2066H) 8295
APPENDICES Appendix 2 How to Confirm the Serial No. and Function Version For how to check the serial No. and function version, refer to the MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection). MELSEC-L CC-Link IE Field Network Head Module User's Manual App. - 21 App.
APPENDICES Appendix 3 Differences between L Series C24 and Q Series C24 Appendix 3.1 Specification comparisons The following shows the specification comparisons between the L series C24 and Q series C24. For the function comparisons between LCPU and QnUCPU, refer to the following. MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) Item Notification function Difference L series C24 Q series C24 No available Available Appendix 3.
APPENDICES Appendix 4 When Using GX Developer or GX Configurator-SC Appendix 4.1 Compatible software packages Refer to the following manual. MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection) Appendix 4.2 Specification comparisons The following shows the specification comparisons between GX Works2 and GX Developer, GX Configurator-SC.
APPENDICES Appendix 4.3 Operation comparison Appendix 4.3.1 Operation of GX Developer When using GX Developer, the setting and confirmation can be configured in the following screens. Screen name Application Set the type and I/O signal range of each I/O Assignment module to be connected. Set the transmission specifications and Switch Setting communication protocols with external devices.
APPENDICES (2) Switch setting GX Developer [PLC Parameter] [I/O Assignment] Switch Setting button [Setting details] Set the transmission specifications and communication protocols of each interface. Switch number Switch 1 Switch 2 Switch 3 App.
APPENDICES (a) Switch 1, Switch 3 The following shows the communication rate setting and transmission setting of the CH1 side (Switch 1) and CH2 side (Switch 3).
APPENDICES (b) Switch 2, Switch 4 The following shows the communication protocol setting of CH1 side (Switch 2) and CH2 side (Switch 4).
APPENDICES Appendix 4.3.2 Operation of GX Configurator-SC When using GX Configurator-SC to set C24 parameters, display methods such as setting screens vary from those of GX Works2. In this section, the screen displaying methods of GX Configurator-SC are explained. Also, since the setting contents are the same as GX Works2, refer to Chapter 7. When using GX Configurator-SC, configure the settings in the following screens.
APPENDICES GX Developer screen [Tools] – [Intelligent function utility] – [Start] Select a target intelligent function module screen When used via online operation When auto refresh is set 1) To the next page 2) To the next page Flash ROM settings screen When used via offline operation Select [Tools] – [Flash ROM setting] from the menu bar. Select the module type and module model name. App. - 29 To each setting screen App.
APPENDICES 1) When using online operation 2) When setting auto refresh Auto refresh Select [Online] – [Monitor/Test] from the menu bar. Select monitor/test module screen Enter "Start I/O No.", and select "Module type" and "Module model name". Auto refresh setting screen Monitor/Test Select a module to be monitored/tested. Monitor/Test screen App. - 30 App.
APPENDICES Appendix 5 Operation Image and Data Structure of Predefined Protocol Appendix 5.1 Operation image of each communication type of protocol In the predefined protocol function, communication with other devices is performed through the communication type 'Send only', 'Receive only', or 'Send & receive'. This section describes the respective operation images. Appendix 5.1.1 When communication type is "Send only" The specified packet is sent once. Send data C24 Terminator Data Command Station No.
APPENDICES (2) Error completion (transmission monitoring timeout error) Example of setting) Standby time: 0, Retry interval: 0, Monitoring time: other than 0 Error occurs LCPU Execute dedicated instruction (G(P).CPRTCL) Completion device ON at error completion Status display device at completion t : Transmission monitoring time C24 Cannot send a packet Other device App. - 32 App.
APPENDICES Appendix 5.1.2 When communication type is "Receive only" When data are received from other devices, the process completes when the receive data matches the receive packet and the receiving process is performed. The operation image of "Receive only" is as follows. (1) Normal completion Store verification-matched receive packet number (1 to 16) LCPU Execute dedicated instruction (G(P).
APPENDICES (2) Error completion (receive wait timeout error) Error occurs LCPU Execute dedicated instruction (G(P).CPRTCL) Completion device ON at error completion Status display device at completion (Receive buffer clear) C24 * Only if it is specified t: Receive waiting time Verification mismatch Other device Receive packet Receive packet POINT • When variables are included in receive packet elements, variable parts are not verified.
APPENDICES Appendix 5.1.3 When communication type is "Send & receive" The specified packet is sent, and the execution status changes to Waiting for receive data status after the sending process completes normally. Then data are received from other devices, and the process completes when the receive data matches the receive packet and the receiving process is performed. The operation image of "Send & receive" is as follows.
APPENDICES (2) Error completion (receive wait timeout error) LCPU Error occurs Execute dedicated instruction (G(P).CPRTCL Completion device ON at error completion Status display device at completion (Receive buffer clear) * Only if it is specified C24 t: Receive waiting time Send packet Verification mismatch Send packet Other device Receive packet Receive packet POINT • When variables are included in receive packet elements, variable parts are not verified.
APPENDICES Appendix 5.2 Verification operation of receive packet The following shows the C24 operation when data that are different from the specified receive packet are received. Receive data prior to the different data are discarded. Data are compared again from the start of the receive packet, and once the data are matched with the receive packet, the data receiving operation is processed.
APPENDICES Appendix 5.3 Data examples of packet elements This section describes the processing procedures and practical data examples of elements that can be placed in a packet. Appendix 5.3.1 Length (1) Processing procedure The C24 processes Length according to the following procedure.
APPENDICES (b) Data flow is 'Reverse direction' Data length Code type 1 byte ASCII hexadecimal ASCII decimal HEX 2 bytes 3 bytes 4 bytes "20" "201" "2010" (32H 30H) (32H 30H 31H) (32H 30H 31H 30H) "85" "852" "8520" (38H 35H) (38H 35H 32H) (38H 35H 32H 30H) 0201H 020100H 02010000H (c) Data flow is 'Byte swap' Data length Code type 1 byte 2 bytes 3 bytes 4 bytes "1020" ASCII hexadecimal (31H 30H 32H 30H) "2085" ASCII decimal (32H 30H 38H 35H) HEX 00000201H (3) Calculating rang
APPENDICES Appendix 5.3.2 Non-conversion variable (1) Processing procedure The C24 processes Non-conversion variable according to the following procedure.
APPENDICES (2) Data example (a) The following table shows data to be stored in the data storage area when the string of send data is 'ABCD' (Reference: A=41H, B=42H, C=43H, and D=44H in ASCII code) Item Description Fixed length/Variable length Fixed length Data length 4 bytes Start address of data storage area D0 Unit of stored data Lower byte + Upper byte Byte swap Disable Data to be stored in data storage area (b) D0 = 0042H D1 = 0042H D1 = 0041H D1 = 4344H D2 = 0043H D2 = 0044H D3
APPENDICES Appendix 5.3.3 Conversion variable (1) Processing procedure The C24 processes Conversion variable according to the following procedure.
APPENDICES (b) When "Conversion" is 'HEX ASCII decimal' or 'ASCII decimal HEX' C24 (Delimiter) (Number of digits) (Blank-padded character) Digits are filled Variable number of digits No delimiter Sending data Adding a delimiter "-_ _12.34," When "Delimiter" is ’ , ’ "-_ _12.34, " "-_ _12.
APPENDICES (2) Data example The following table shows send data when a packet consists of Header Conversion variable Terminator and data stored in the data storage area is D0=837 (0345H), D1=18 (0012H).
APPENDICES Appendix 5.3.4 Check code (1) Processing procedure The C24 processes Check code according to the following procedure. 1) Calculates value according to the selection of "Processing method". 2) When "Complement calculation" is 'One's complement' or 'Two's complement', performs a 2-word-wise complement operation on the value calculated in 1). 3) When "Code type" is 'ASCII decimal', extracts the lowest one word from the value calculated in 2) and performs the hexadecimal decimal conversion.
APPENDICES (a) Data flow: Forward direction 1) "Complement calculation" is 'No complement calculation' (15H in hexadecimal is 21 in decimal) Data length Code type 1 byte 2 bytes 3 bytes 4 bytes ASCII "5" "15" "015" "0015" hexadecimal (35H) (31H 35H) (30H 31H 35H) (30H 30H 31H 35H) "1" "21" "021" "0021" (31H) (32H 31H) (30H 32H 31H) (30H 30H 32H 31H) 15H 0015H 000015H 00000015H ASCII decimal HEX 2) "Complement calculation" is 'One's complement' (One's complement of 0000 0015H is
APPENDICES (b) Code type Data flow: Reverse direction 1) "Complement calculation" is 'No complement calculation' (15H in hexadecimal is 21 in decimal) Data length 1 byte 2 bytes 3 bytes 4 bytes ASCII "51" "510" "5100" hexadecimal (35H 31H) (35H 31H 30H) (35H 31H 30H 30H) ASCII decimal HEX 2) Code type "12" "120" "1200" (31H 32H) (31H 32H 30H) (31H 32H 30H 30H) 1500H 150000H 15000000H "Complement calculation" is 'One's complement' (One's complement of 0000 0015H is FFFF FFEAH) Whe
APPENDICES (c) Data flow: Byte swap 1) "Complement calculation" is 'No complement calculation' (15H in hexadecimal is 21 in decimal) Code type Data length 1 byte 2 bytes 3 bytes 4 bytes ASCII "0051" hexadecimal (30H 30H 35H 31H) "0012" ASCII decimal (30H 30H 31H 32H) HEX 00001500H 2) Code type "Complement calculation" is 'One's complement' (One's complement of 0000 0015H is FFFF FFEAH) When "Code type" is 'ASCII decimal', the last one word is extracted and converted from hexadecimal to decim
APPENDICES (3) Procedure for calculating sum check The following show procedures for calculating sum check codes using the following sample data.
APPENDICES (b) Data flow: Reverse direction 1) "Complement calculation" is 'No complement calculation' (1FDH in hexadecimal is 509 in decimal) Code type Data length 1 byte 2 bytes 3 bytes 4 bytes ASCII "DF" "DF1" "DF10" hexadecimal (44H 46H) (44H 46H 31H) (44H 46H 31H 30H) "90" "905" "9050" (39H 30H) (39H 30H 35H) (39H 30H 35H 30H) FD01H FD0100H FD010000H ASCII decimal HEX 2) Code type "Complement calculation" is 'One's complement' (One's complement of 0000 01FDH is FFFF FE02H) Whe
APPENDICES (c) Data flow: Byte swap 1) "Complement calculation" is 'No complement calculation' (1FDH in hexadecimal is 509 in decimal) Code type Data length 1 byte 2 bytes 3 bytes 4 bytes ASCII "10DF" hexadecimal (31H 30H 44H 46H) "5090" ASCII decimal (35H 30H 39H 30H) HEX 0000FD01H 2) Code type "Complement calculation" is 'One's complement' (One's complement of 0000 01FDH is FFFF FE02H) When "Code type" is 'ASCII decimal', the last one word is extracted and converted from hexadecimal to de
APPENDICES (4) Procedure for calculating 16-bit CRC (for MODBUS) This is a check system that is used only when data are sent/received in the RTU mode of the MODBUS protocol. The data length of CRC is fixed to 2 bytes (16 bits), and the CRC is calculated every 1 byte (8 bits) from the start of the calculating range according to the following procedure. 1) 2) 3) 4) 5) 6) 7) 8) Load a 16-bit register whose bits are all '1'.
APPENDICES The following show the example of 16-bit CRC (for MODBUS) calculation. Packet example: Station No.
APPENDICES (5) Calculating range of Check code The following shows specification examples of the calculating range of Check code.
APPENDICES Appendix 6 Communication Example when the C24 Is Used Installed to the Head Module This section explains the parameter setting and programming using system configuration examples. For the parameter setting of the head module and details on cyclic transmission, refer to the following manual. MELSEC-L CC-Link IE Field Network Head Module User's Manual MELSEC-Q CC-Link IE Field Network Master/Local Module User's Manual Appendix 6.
APPENDICES Appendix 6.2 System configuration example (1) System configuration The following is a system configuration for the program examples in this section. App. - 56 App.
APPENDICES (2) Data communication procedure when the C24 is connected to the head module The control is performed using the network parameter setting (refresh parameter setting) of the master station and the C24 auto refresh setting of the intelligent device station (head module). When the C24 is connected to the head module, dedicated instructions cannot be used.
APPENDICES (a) Data communication using the predefined protocol Set send or receive data storage area on the "Predefined Protocol Support Function" screen of the predefined protocol support function in advance. Then, communicate the data in the following procedures. 1) 2) 3) 4) 5) 6) App. - 58 Write the send data to the link register W of the CPU module to store the send data in the head module device. Write the number of continuous executions of the protocol and the execution protocol No.
APPENDICES (b) Data communication using the nonprocedural or bidirectional protocol • Sending procedure 1) Write the send data to the link register W of the CPU module to write the send data to the C24 buffer memory. 2) Issue a send request by receiving the send request (Y0/Y7). 3) After execution of the send request is completed, the transmission normal completion (X0/X7) turns on. App. - 59 App.
APPENDICES • Receiving procedure 1) Using the auto refresh function, results of execution of the nonprocedural or bidirectional protocol are transferred from the C24 buffer memory to the head module device and then to the link register W of the CPU module. 2) When the data from the external device is received, the reception data read request (X3/XA) turns on. App. - 60 App.
APPENDICES Appendix 6.3 Parameter setting Appendix 6.3.1 Master station setting (1) Network parameter setting Set the network parameters using GX Works2 as shown below. For the network configuration setting, refer to (2) in this section. For the refresh parameters, refer to (3) in this section.
APPENDICES (3) Refresh parameter setting In "Refresh Parameter", set the following network parameters. App. - 62 App.
APPENDICES Appendix 6.3.2 Head module setting (1) PLC parameter setting Set the PLC parameters using GX Works2 as shown below. For details on the PLC parameters of the head module and network parameters, refer to the MELSEC-L CC-Link IE Field Network Head Module User's Manual.
APPENDICES Appendix 6.4 Execution program example of the predefined protocol The following shows a program example when connecting an external device (temperature control module) to CH2 of the C24 and executing the pre-defined protocol using the auto refresh function and X/Y signal. (1) Setting for the C24 installed to the head module Configure the switch settings and predefined protocol settings of the C24 to the head module. To use the program example in this section, set as follows.
APPENDICES (b) Various Control Specification On the "Various_Control_Specification" screen, set "1: Prohibited" in "Echo back allow/prohibit designation". For details on the echo back allow/prohibit, refer to Section 6.3.5. [Operation procedure] Project window [Intelligent Function Module] [Various_Control_Specification] [LJ71C24] [Setting screen] App. - 65 App.
APPENDICES (c) Auto refresh setting Set the auto refresh to transfer the information stored in the C24 buffer memory to the specified device of the head module automatically. [Operation procedure] Project window [Intelligent Function Module] [Auto_Refresh] [LJ71C24] [Setting screen] App. - 66 App.
APPENDICES (d) Predefined protocol setting Set the predefined protocol as shown below. (When using the EJ1 0601H:RD Controller Status in the MELSEC predefined protocol library) For details on predefined protocol support function, refer to Section 9.1. [Operation procedure] 1) [Tool] [Intelligent Function Module Tool] [Serial Communication Module] [Predefined Protocol Support Function] 2) [Predefined Protocol Support Function] screen [File] [New] [Setting screen] Packet Name Element No.
APPENDICES (2) Program example The following shows the program that executes the predefined protocol from CH2 of the C24 when M1000 is turned ON. [I/O signals of the C24] Device X100C X101D Purpose Device CH2 protocol execution Y100A completion Predefined protocol ready Purpose CH2 protocol execution request — — [Link special relay (SB), link special register (SW)] Device Purpose SB0049 Data link status of host station Device SW00B0.
APPENDICES Appendix 6.5 Sending/receiving data using the nonprocedural or bidirectional protocol Appendix 6.5.1 Receiving data using the nonprocedural or bidirectional protocol The following shows a program example of connecting an external device (personal computer) to CH1 of the C24 and receiving data by nonprocedural and bidirectional protocols, using auto refresh and X/Y signals.
APPENDICES (b) Auto refresh setting Configure the auto refresh settings to transfer the information stored in the C24 buffer memory to the specified device in the head module automatically. For details on the transmission/receive area, refer to Chapter 10 or 11. [Operation procedure] Project window [Intelligent Function Module] Refresh] [LJ71C24] [Auto [Setting screen] App. - 70 App.
APPENDICES (2) Program example The following shows the program example of receiving data using the nonprocedural protocol. [I/O signals of the C24] Device X1003 X1004 Purpose CH1 Reception data read request CH1 Reception error detection Device Y1001 Purpose CH1 Reception data read completion — — [Link special relay (SB), link special register (SW)] Device SB0049 Purpose Data link status of host station Device SW00B0.
APPENDICES Appendix 6.5.2 Sending data using the nonprocedural or bidirectional protocol The following shows a program example of connecting an external device (personal computer) to CH1 of the C24 and sending data by nonprocedural and bidirectional protocols, using auto refresh and X/Y signals. (1) Setting of the C24 installed to the head module Perform the switch setting and auto refresh setting for the C24 on the head module. To use the program example in this section, set as follows.
APPENDICES (b) Auto refresh setting Configure the auto refresh settings to transfer the information stored in the C24 buffer memory to the specified device by the head module automatically. For details on the transmission/receive area, refer to Chapter 10 or 11. [Operation procedure] Project window [Intelligent Function Module] Refresh] [LJ71C24] [Auto [Setting screen] App. - 73 App.
APPENDICES (2) Program example The following shows a data transmission image and a program example when sending data using the nonprocedural protocol. [I/O signals of the C24] Device X1000 X1001 Purpose CH1 Transmission completion CH1 Transmission error Device Purpose Y1000 CH1 Transmission request — — [Link special relay (SB), link special register (SW)] Device SB0049 App. - 74 Purpose Data link status of host station Device SW00B0.
APPENDICES By transferring the send data count to W0 and transferring the send data for the send data count from W1 in the master station CPU module, the data is stored in the C24 device installed to the following head module. Device W0 W1 to W1FF Content Send data count Send data The example in the previous page does not include a program for turning OFF "M1000: Data transmission instruction". Turn OFF "M1000: Data transmission instruction" when the normal or abnormal transmission signal is turned ON.
APPENDICES Appendix 7 Processing Time (1) Time required to process communication using the nonprocedural protocol (guideline) The processing time for the Output and Input instructions can be estimated by the following formula. Note, however, that the processing time may become longer depending on other communication functions (e.g., communication using the MC protocol) and special functions (e.g., ASCII-binary conversion, transmission control) that are used at the same time.
APPENDICES (b) Input instruction Tp = Sr + 0.09 Dr + T2 Tp ( 1) : Time from the start of execution of the Input instruction to the End processing of the sequence scan at the completion of the Input instruction execution (ms) Sr : Scan time Dr : Number of bytes of reception data T2 : C24 T2 = 7.0 1 This stands for the time range of processing (Tp). [Calculation example] The time required to process the Input instruction when receiving 100 bytes of data using the nonprocedural protocol with C24.
APPENDICES (2) Processing time of dedicated instructions The following table shows the operation processing time (rough standard) of each dedicated instruction. The operation processing time differs slightly depending on the system configuration and communication protocol. Processing time (unit: ms) Instruction name L02CPU, L02CPU-P Instruction execution condition L26CPU-BT, L26CPU-PBT ONDEMAND 48.8 48.3 OUTPUT 23.8 23.5 PRR 24.3 23.9 INPUT 1.2 1.
APPENDICES Appendix 8 ASCII-Code List The ASCII-code list is shown below. (7-bit codes) The codes marked are used as C24 control codes. (DC codes 11H to 14H can be changed by the user.
APPENDICES Appendix 9 Usage Example of MX Component This section explains the procedure for creating programs and sample programs using MX Component. (1) Procedure for creating programs The procedure for creating programs is outlined below. The usage procedure below uses Visual Basic .NET 2003 as an example. R 1) Perform the communication settings from a IBMPC/AT-compatible personal computer to the programmable controller by following the wizard.
APPENDICES (2) Sample program The following sample program reads D0 to D4 (five points) of the target programmable controller using the logical station number. (a) Screen example (Form1) 1) Screen example (Form1) Text1 ' Enter the logical station number. Command1 or Button1 ' Connect to the communication line. Command2 or Button2 ' Read the device data. Command3 or Button3 ' Cut the communication line.
APPENDICES Private Sub Command2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Command2.Click '*********************************** ' Read '*********************************** Dim rtn As Integer Dim idata(5) As Short 'D0-D4 are read rtn = AxActEasyIF1.
APPENDICES //************************** // Read //************************** private: System::Void button2_Click(System::Object * sender, System::EventArgs * e) { int iRet; short sData[5]; String* szMessage= ""; String* lpszarrData[]; int iNumber; String* szReadData; // D0-D4 are read iRet = axActEasyIF1->ReadDeviceBlock2( "D0", 5, sData ); if( iRet == 0 ){ lpszarrData = new String * [ 5 ]; lpszarrData[0] = "D0-D4 = "; // Storage of data to display the results for( iNumber = 0 ; iNumber < 5 ; iNumber++ ) {
APPENDICES 3) ® When Visual Basic 6.0 is used Private Sub Command1_Click() '*********************************** ' Connection '*********************************** Dim rtn As Long 'Get LogicalstationNumber ActEasyIF1.ActLogicalStationNumber = Val(Text1.Text) 'Connection rtn = ActEasyIF1.
APPENDICES 4) ® When Visual C++ 6.0 is used //************************** // Connection //************************** void CVCDlg::OnOpen() { long lRet; CString szMessage; // Reflects the logical station No. set in the text box to variables. UpdateData(); // Get LogicalstationNumber m_actEasyIf.SetActLogicalStationNumber( m_lLogicalStationNumber ); // Connection lRet = m_actEasyIf.Open(); if( lRet == 0 ){ MessageBox( "The connection was successful" ); } else { szMessage.
APPENDICES //************************** // Disconnection //************************** void CVCDlg::OnClose() { long lRet; CString szMessage; // Disconnection lRet = m_actEasyIf.Close(); if( lRet == 0 ){ MessageBox( "The disconnection was successful" ); } else { szMessage.Format( "Disconnection Error : %x", lRet ); MessageBox( szMessage ); } } App. - 86 App.
APPENDICES Appendix 10 Setting Value Recording Sheet The following sheet is for recording parameter setting values set by GX Works2. Use as many copies as needed. In order to review the setting values of parameters, print them out using the parameter printing function of GX Works2 to use it as the setting value recording sheet. [Module No.
APPENDICES Recording sheet 3 (Switch setting) GX Works2 setting Data item name screen Operation setting Data Bit Transmission Setting Parity Bit Set data Setting value 1 Independent Linked 7 8 None Exist 2 3 Even/odd parity 4 CH1 side Odd Even Stop bit 1 2 Sum check code None Exist Online Change Disable Enable Setting modifications Disable Enable CH2 side Independent 50 300 600 1200 2400 4800 Communication rate setting 9600 (unit: bps) 14400 19200 Switch Setting 28800
APPENDICES Appendix 11 External Dimensions 4 10 45 Outside cable diameter 4 (1) LJ71C24 90 R2 ( 2) (45) DIN rail center R1 ( 1) 4 r1 ( 3) 4 95 118 28.5 (Unit: mm) 1 R1 (bend radius near the terminal) : Cable outside diameter 4 2 R2 (bend radius near the connector) : Cable outside diameter 4 3 r1 (bend radius near the crimp-on terminal) : Connectable without bending excessively 4 (2) LJ71C24-R2 4 10 R2 ( 1) (45) DIN rail center 90 45 Outside cable diameter 4 4 95 4 28.
INDEX I [A] [E] A compatible 1C frame............................... 8- 2 Additional functions of the C24 .................. 3- 5 Applicable systems..................................... 5- 3 ASCII-code list ......................................App.-79 Auto refresh ............................................... 7-25 Echo back...................................................6-19 ER signal .....................................................6- 3 ERR. LED.................................................
Receive data clear (nonprocedural) ........10-17 (bidirectional) ............11-14 Received data count ................................10-23 Receive data (nonprocedural) ..................10- 8 (bidirectional).......................11- 6 Receiving methods (nonprocedural) ........10- 2 (bidirectional) ............11- 2 Remote password function .........................8- 4 RI signal...................................................... 6- 3 ROM/RAM/switch test................................
Troubleshooting........................................ 15- 1 TXD signal .................................................. 6- 2 [U] User register frame specification ............... 7- 7 [V] Various control specification ...................... 7- 3 [W] Writing to the flash ROM .......................... 7-23 [1] 1:1 system configuration ............................ 5- 4 1:n system configuration ............................
REVISIONS The manual number is given on the bottom left of the back cover. Print date January, 2010 April, 2010 Manual number SH(NA)-080894ENG-A First edition SH(NA)-080894ENG-B Addition Revision Section 5.2.1, Appendix 6 Correction SAFETY PRECAUTIONS, RELEVANT MANUALS, TERMS, Section 3.1, 3.2.1, 3.4, Chapter 4, Section 5.1, 5.2, 6.1, 7.4.2, Chapter 10, 11, Section 15.2.2, Appendix 1, 2 Chenge of section No. Appendix 6 to 10 September, 2010 SH(NA)-080894ENG-C Correction Appendix 7 to 11 Section 7.
WARRANTY Please confirm the following product warranty details before using this product. 1. Gratis Warranty Term and Gratis Warranty Range If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service Company.
Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks of Microsoft Corporation in the United States and other countries. Pentium is a trademark of Intel Corporation in the United States and other countries. Ethernet is a trademark of Xerox Corporation. Other company names and product names used in this document are trademarks or registered trademarks of respective companies.
