294
Status Area and Troubleshooting
Section 9-2
Communications error is 1:
ON
The relevant node is not in
the Network.
Enter the node in the Net-
work.
A communications error
has occurred as a result of
noise.
Conduct an echoback test
using the Controller Link
Support Software and if
this does not correct the
error, check the usage
environment.
A communications error
has occurred.
Refer to page 285
shooting with RUN, ERC,
ERH and INS Indicators
and troubleshoot accord-
ingly.
Data link participation is 0:
OFF
The relevant node is not
part of data links.
Enter the relevant node in
data links. If an error
occurs, refer to
page 289
Node Cannot Participate in
Data Link
and troubleshoot
accordingly.
There are no active data
links in the Network.
Activate the data links.
Offset error is 1: ON
The offset is greater than
the number of send words
at the relevant node.
Check the number of send
words at the relevant node,
the number of receive
words at the local node
and the offset, then reset
the data link table correctly.
Receive area insufficient
(short) is 1: ON
The send area at the rele-
vant node is larger than the
receive area and some
data cannot be received.
When the intention is not to
receive all data, use as is
(data that cannot be
received will be read and
discarded.)
When it differs from the
intended data link, check
the number of send words
at the relevant node, the
number of receive words at
the local node and the off-
set, then reset the data link
table correctly.
Receive area remaining is
1: ON
The send area at the rele-
vant node is smaller than
the receive area and some
of the area will be unused.
When the intention is to
leave some space in the
receive area, use as is (the
surplus receive area will be
cleared to 0.)
When it differs from the
intended data link, check
the number of send words
at the relevant node, the
number of receive words at
the local node and the off-
set, then reset the data link
table correctly.
Bit status
Probable cause
Probable remedy
Summary of Contents for C200HW-CLK21
Page 3: ...iv ...
Page 9: ...x ...
Page 12: ...xiii TABLE OF CONTENTS Index 367 Revision History 373 ...
Page 13: ...xiv ...
Page 19: ...xx ...
Page 57: ...32 Application Precautions Section 1 5 Example CX Programmer Response Timeout Setting ...
Page 69: ...44 Message Service Procedure Section 2 2 ...
Page 111: ...86 Constructing Networks with Repeater Units Section 3 4 ...
Page 154: ...129 Setting Data Links Section 5 2 Device Information Setting Data Link Tables ...
Page 261: ...236 Response Codes Section 6 7 ...
Page 297: ...272 Message Delay Times Section 8 4 ...
Page 353: ...328 Handling Precautions Section 9 6 ...
Page 364: ...339 Changing the Data Link Tables with Active Data Links Section 10 2 ...
Page 365: ...340 Changing the Data Link Tables with Active Data Links Section 10 2 ...
Page 369: ...344 Standard Models Appendix A ...
Page 391: ...366 Using the Relay Terminal Block Appendix C ...
Page 397: ...372 Index ...
Page 401: ...376 Revision History ...