324
Troubleshooting Section 11-3
Troubleshooting Using FINS End Codes
MRC
(Main response code)
SRC
(Sub-response code)
Check point Probable cause Corrective measure
Value
(hex)
Contents Value
(hex)
Contents
00 Normal comple-
tion
00 Normal comple-
tion
--- --- ---
04 Remote node
busy
Bit 05 in CIO word
n+8/n+18 (Serial
Gateway timeout or
Serial Gateway
response timeout)
The Serial Gateway
cannot be executed
as an interrupt
between steps in the
protocol macro.
Perform FINS send
retry processing or
change the commu-
nications sequence.
02 Remote node
error
05 Response time-
out at FINS
transmission
source
Bit 05 in CIO word
n+8/n+18 (Serial
Gateway timeout or
Serial Gateway
response timeout)
The message frame
was destroyed by
noise.
If Bit 05 of CIO word
n+8/n+18 is OFF, a
response timeout
has occurred at the
FINS transmission
source. Perform the
following:
Test communica-
tions to check the
noise conditions.
Increase the num-
ber of retries at the
FINS command
transmission source.
Perform communica-
tions retries, if nec-
essary.
Instruction control
data
The response moni-
toring time is too
short.
Increase the length
of the response
monitoring time.
Error history The send/receive
frame was dis-
carded.
Take appropriate
measures based on
the error history.
Serial Gateway
response time-
out
Bit 05 in CIO word
n+8/n+18 (Serial
Gateway timeout or
Serial Gateway
response timeout)
A Serial Gateway
response timeout
has occurred.
If bit 05 of CIO word
n+8/n+18 is ON,
take appropriate
measures for a
Serial Gateway
response timeout.
06 Transmission
path error
CIO word n+8/n+18
bit 07 (FCS check
error) or bit 02 (parity
error)
Conversion to Com-
poWay/F command:
BCC error or parity
error
Conversion to Mod-
bus-RTU command:
CRC error or parity
error
Conversion to Mod-
bus-ASCII com-
mand: CRC error or
checksum error
Use shielded
twisted-pair cables.
Lay power lines sep-
arately using ducts.
Increase the num-
ber of resends at the
FINS transmission
source.
Perform communica-
tions retry as
required.
10 Command for-
mat error
01 Command too
long
Command data The command is
longer than the maxi-
mum permissible
length.
Check the command
format and correct
the command data.
02 Command too
short
Command data The command is
shorter than the
maximum permissi-
ble length.
Check the command
format and correct
the command data.