System Design Errors
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|
001 |
Not supported unit. |
This model is incorrect. (Model of supported unit.) |
The project file might not have been sent properly. Transfer the project file again. |
002 |
Setting value error |
The data type of the symbol variable assigned to the FLEX NETWORK unit is illegal. The FLEX NETWORK unit setting value is illegal. |
|
003 |
Device out-of-range error |
The address of the symbol variable assigned to the FLEX NETWORK unit is out of range. |
|
004 |
Duplicate terminal settings |
The number of FLEX NETWORK unit terminals exceeds the limit. |
|
005 |
Terminal setting order error |
The I/O terminal numbers are not set up in ascending order. |
|
006 |
Terminal registry short |
Not a reasonable number of I/O terminals. |
|
007 |
Units config overlapped. |
FLEX NETWORK unit S-No. is duplicated and set. |
|
008 |
Units count over limit. |
The maximum number of connected FLEX NETWORK units (63 units) is exceeded. The maximum value of S-No. (S-No. 63) is exceeded. The S-No of the FLEX NETWORK unit that occupies more than one node has exceeded the maximum (S-No 63). |
|
009 |
Repeat driver setting |
The driver is registered twice. |
|
010 |
Unmatched In/Out terminal. |
The input/output settings of the FLEX NETWORK unit are not correct. |
|
011 |
Unmatched bit/word term. |
The variable type specified in the FLEX NETWORK unit is incorrect. |
|
012 |
Setting level value error |
There is a problem with the I/O driver. |
|
013 |
Data obtaining address error |
I/O driver information is incorrect. Invalid controller information. |
|
014 |
Driver/unit not registered |
The I/O driver or FLEX NETWORK unit is not registered. |
Runtime error
Error Code |
Error Message |
Description |
Solution |
100 |
Unit communication error. |
A communication error has occurred between the main unit and the FLEX NETWORK unit. are that the communication cable is disconnected; the FLEX NETWORK unit is not connected; or an incorrect unit model is set in the project file. |
The S-No. or communication speed set in the editor may differ from that set in the unit. If this error continues, check the following.
|
101 |
4ch analog setting error. |
Communication with the 4 CH analog unit has failed. |
Please check the following.
|
102 |
2ch analog setting error. |
Communication with the 2 CH analog unit has failed. |
|
103 |
Analog unit’s wire broken. |
The 4 to 20mA-ranging input signal of the 4 CH or 2 CH analog unit is cut off. This error code continues to display unitl the controller is reset. |
Check if the input signal is disconnected. |
104 |
Counter unit error. |
An error has occurred in the high-speed counter unit. |
For details, find the associated unit’s error code in the following manual.
|
105 |
Counter initial error. |
Initializing the high-speed counter unit has failed. |
Please check the following.
|
106 |
Counter communication error. |
A communication error with the high-speed counter unit has occurred. |
|
107 |
Positioning Unit error. |
An error has occurred in the positioning unit. |
For details, find the associated unit’s error code in the following manual.
|
108 |
Comm position error. |
A communication error with the positioning unit has occurred. |
Please check the following.
|
109 |
2ch analog comm error. |
A communication error with the 2 CH analog unit has occurred. |
Internal error
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|
200 |
Integer type data read error. |
Integer-type Terminal data of the FLEX NETWORK unit could not be read. |
The project file might not have been sent properly. Transfer the project file again. |
201 |
Bit type data read error |
Bit-type Terminal data could not be read. |
|
202 |
Integer type data write error |
Integer-type Terminal data could not be written. |
|
203 |
Bit type data write error |
Bit-type terminal data could not be written. |