Omron NV3Q Series, Connection Manual

Page: 141 / 145

117
Modbus Connections
Section 12-5
12-5 Modbus Connections
12-5-1 NV3W
12-5-2 NV4W/NV3Q
12-5-3 Modbus Connections to OMRON EJ1 Temperature Controller
NV3W error codes are displayed as "ER" followed by the two-digit
code.NV4W and NV3Q error codes are displayed as "ER00" followed by the
two digit error code.
The notation for the NV3W is used in the following table. When using the
NV4W or NV3Q, "00" will be displayed after "ER."
Error code Description Cause and countermeasure
ERFF Timeout Error
The PLC did not return a
response.
1. The cable connecting the PLC is disconnected. Check the cable for
incorrect wiring or disconnections.
2. A temporary error was caused by noise or other factor. Cycle the pow-
er to the PLC or PT.
ERFE Response Error
An error response was
returned by the external
device.
Check the data that was returned by the external device.
Error code Description Cause and countermeasure
ER0001 Timeout Error
The PLC did not return a
response.
1. The cable connecting the PLC is disconnected. Check the cable for
incorrect wiring or disconnections.
2. A temporary error was caused by noise or other factor. Cycle the pow-
er to the PLC or PT.
ERFFFE Response Error
An error response was
returned by the external
device.
Check the data that was returned by the external device.
Error code Description Cause and countermeasure
ER01 Function code error The function code is not supported.
ER02 Variable address error 1. There is an error in the write start address.
2. There is an error in the read start address.
ER03 Variable data error 1. The command is too short.
2. The command is too long.
3. The number of elements exceeds the maximum value.
4. The number of elements and data do not match.
5. The number of elements times two does not match the byte count.
6. The write data is outside the setting range.
7. An attempt was made to write to a read-only variable.
ER04 Operation error 1. The operation command could not be received and was not executed.
2. The operation was not executed because data was being backed up.
3. The operation was not executed because a reset was being pro-
cessed (including when starting).
4. The operation was not executed because the Controller was in Tuning
Mode.