319
Troubleshooting Error Messages in CX-Net Data Link Table Check
Section 9-4
Note
(1) If any errors (except for warnings) are detected during the table check
performed when transferring data link tables, the data link tables will not
be transferred even if the
OK
Button is clicked. Remove the cause of the
error and then transfer the data link tables again.
(2) Messages (in the
Contents
field) preceded by “Warning,” indicate a warn-
ing, not an error that will prevent operation continuing. Check the contents
of the message, and confirm that the intended settings and allocations
are correct. Click the
OK
Button to transfer the data link tables without
any changes.
(3) The following two messages indicate warnings for CS/CJ-series Control-
ler Link Units with unit version 1.2 or later and errors for CS/CJ-series
pre-Ver. 1.2 Controller Link Units.
Node XX Node size:
Warning: The total send and receive size of ** exceeds 12000.
Node XX Area Overlap:
Warning: Link memory areas 1 and 2 are both set to – [Area]
Error message
Troubleshooting
Node XX Link area
exceeded
Total link area 1 Start Address **
size ** is outside max area size
The size ** of Link Area 1 starting from start address **
exceeds the maximum size for the corresponding area.
Check the maximum number of words in the corresponding
area of the CPU Unit being used, and either change the start
address or reduce the number of data link words.
Total link area 2 Start Address **
size ** is outside max area size
The size ** of Link Area 2 starting from start address **
exceeds the maximum size for the corresponding area.
Either change the start address or reduce the number of
data link words.
Node XX Dest
Warning: Size outside bounds of
Link from node **. Enter value in
range ** to **
The number of receive words at the destination node is
smaller than the number of send words at the source node.
Change the number of send words or number of receive
words if the allocations are not intended. If the allocations
are intended, the data link tables can be transmitted without
making any changes.
Invalid [Area] offset. Enter value
in range ** to **
The value equal to or higher than the number of send words
at node XX is set in the number of offset words for the desti-
nation node. If the allocation is not intended, change either
the number of send words or the number of receive words. If
the allocations are intended, the data link tables can be
transmitted without making any changes.
Node XX Dest Over-
flow
Warning: Overflow occurred
The number of receive words at the destination node is
larger than the number of send words at the source node.
Change the number of send words or number of receive
words if the allocations are not intended. If the allocations
are intended, the data link tables can be transmitted without
making any changes.
Warning: Block outside bounds of
Link from node **. Enter value in
range ** to **
The number of receive words at the destination node is
smaller than the number of send words at the source node.
Change the number of send words or number of receive
words if the allocations are not intended. If the allocations
are intended, the data link tables can be transmitted without
making any changes.
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 ...