Filter
Top Products
227
Response Codes Section 6-7
Example 1 In this example, data cannot be transferred between Controller Link Units due
to some cause such as a routing table error.
Example 2 In this example, data cannot be transferred between a Controller Link Unit and
a CPU Unit.
Example 3 In this example, the specified destination node or the next relay node does not
exist.
If an error occurs, check the MRES and SRES codes for the node in question,
and correct the problem.
6-7-3 Response Codes and Troubleshooting
The table below lists response codes (main and sub-codes) returned after
execution of the FINS commands, the probable cause of errors, and recom-
mended remedies.
Upon receipt of some commands, the destination node will issue a request to
another node; the other node is referred to as the third node.
PS: Power Supply Unit
CPU: CPU Unit
CLK: Controller Link Unit
SNT: SYSMAC NET Link Unit
Transmission
Response
P
S
C
P
U
P
S
C
P
U
S
N
T
C
L
K
S
N
T
1
P
S
C
P
U
C
L
K
1
2
MRES
––
SRES
PS: Power Supply Unit
CPU: CPU Unit
CLK: Controller Link Unit
Transmission
Response
P
S
C
P
U
C
L
K
1
P
S
C
P
U
C
L
K
1
2
MRES
––
SRES
PS: Power Supply Unit
CPU: CPU Unit
CLK: Controller Link Unit
SNT: SYSMAC NET Link Unit
Transmission
Response
P
S
C
P
U
C
L
K
C
L
K
P
S
C
P
U
C
L
K
S
N
T
1
P
S
C
P
U
C
L
K
1
2
MRES
––
SRES
Main code Sub-
code
Probable cause Remedy
00: Normal completion 00 --- ---
01 Service was interrupted Check the contents of the destination trans-
mission area of third node.
Check the data link status.