Filter
Top Products
1. PLC Development Environment Using GX Developer
1.3 Developing PLC Programs
- 19 -
(3) How to confirm the error step number
At a conversion error, error information is stored to the special registers as below. Device-
monitoring these registers enables to find the error position.
SD30 : Error step No. where the error occurred.
SD31 : Cause of the error.
The error No. which occurred while writing from GX Developer to C64
SD31 value Cause of error
1 Command format error.
2 File already exists.
3 File to be read is not found.
4 Object code error.
5 File can not be opened.
6 File name is too long.
7 File name is illegal.
9 This is not a ladder or a message file.
10 Ladder code has been already changed.
20 Device No. exceeds the specification range.
21 Search was failed.
22 Device No. is illegal.
23 There is an error in the conversion table data.
24 Conversion can not be performed.
(Already converted with M500.)
25 Attribute code is illegal.
101 Warning : Device can not be converted.
102 Some of the designated digits can not be used in the ladder
sub-routine.
103 Designated index can not be used in the ladder sub-routine.
The [Verify with PLC] function can be used to confirm the error step. Executing verification with PLC
displays mismatches as in the following example. For details of the [Verify with PLC] function, refer
to "1.3.7 Verifying the PLC Programs".
<Memory> indicates the GX Developer side, and <PLC> the CNC side.
GX Developer side
CNC controller side