Omron CJ1W-SCU32 Operation Manual page 286

9 Troubleshooting and Maintenance
Response Received from Remote Device but Error Remains
Unit status Serial
communica-
tions mode
A normal end The serial
code is communica-
returned from tions mode is
the remote set to Serial
device, but Gateway or
there is no Protocol Macro
response data Mode.
after the end
code.
A response
was received
from the
remote device
after a
response time-
out error was
received for a
converted
command that
was sent to the
remote device.
An error end
code was
returned to the
transmission
source.
9-8
Error conditions
Indicator Command
display end code
sent to
command
source
The 0000 hex
RD@/SD@
indicators all
flash.
0205 hex
(response
timeout), etc.
0206 hex
(transmis-
sion line
error)
Other error
end code
CJ-series Serial Communications Units Operation Manual for NJ-series CPU Unit(W494)
Cause
Confirma-
tion of
device
variable for
CJ-series
Unit, etc.
--- The command
requires a response,
but the command
after conversion does
not require a
response (e.g.,
broadcasting)
*_P1(orP2)_T A Serial Gateway
imeoutErr response timeout
(Timeout occurred, but the
Error) is set response data was
to TRUE. received normally
after the timeout.
This occured because
the
*_P1(orP2)_PmrSgw
RespTimeoutCfg
(Serial Gateway
Response Timeout
Monitoring Time) set-
ting is too short.
*_P1(orP2)_F Either of the following
CSErr (FCS errors occurred in the
Check Error) protocol after conver-
or sion.
*_P1(orP2)_ Conversion to Com-
ParityErr poWay/F command:
(Parity Error) BCC error or parity
is TRUE. error
Conversion to Mod-
bus-RTU command:
CRC error or parity
error
Conversion to Mod-
bus-ASCII command:
CRC error or check-
sum error
Conversion to Host
Link command: FCS
error or parity error
--- The Serial Gateway
was executed, but the
error completion
occurred.
Remedy
Check the specifications of
the command to be con-
verted.
Set a longer time for
*_P1(orP2)_PmrSgwRespTi
meoutCfg (Serial Gateway
Response Timeout Monitor-
ing Time).
Use shielded twisted-pair
cables.
Lay power lines separately by
using ducts.
Increase the number of
resends at the command
source.
Perform communications
retry as required.
Perform error processing
based on the following table
of Cause and Countermea-
sure by Command End Code.