1785-UM022B-EN-P - February 2002
D-8 ControlNet I/O Map-Entry Status Words and Error Codes
774 0x0306 KEEPER NOT AVAILABLE The ControlNet cable from the
originating node to the keeper is
broken or disconnected.
Fix and/or reconnect the ControlNet
cable.
The keeper is not powered. Supply power to at least one
ControlNet processor.
No keeper exists on the ControlNet
network.
Add at least one ContolNet
processor to the network.
Reconfigure the ControlNet network
by enabling and accepting edits with
RSNetWorx.
789 0x0315 INVALID PATH SEGMENT TYPE The map table is corrupted. Reenter the I/O map entry that is
failing.
The target node of the CIO
instruction is not the correct I/O
adapter.
Edit the ladder program so that the
correct target node is used.
Replace the target node with the
correct adapter.
791 0x0317 INVALID SCHEDULE DATA The ControlNet cable from the
originating node to the programming
terminal was broken or
disconnected when the ControlNet
network was configured.
Fix and/or reconnect the ControlNet
cable and reconfigure the ControlNet
network.
The originating node was not
powered when the ControlNet
network was configured.
Supply power to the originating node
and reconfigure the ControlNet
network.
797 0x31D INVALID TARGET TAG The PLC-5C is requesting data from
a ControlLogix tag that is not
configured as a producer.
Change the PLC-5C I/O map entry to
use the correct tag.
Reconfigure the tag in the
ControlLogix processor to be a
producer.
REDUNDANT CONNECTION
MISMATCH
Configuration for this redundant
connection does not match the
configuration used by the Hot
Backup partner.
Change the PLC-5C I/O map and
module configuration data to match
the Hot Backup partner.
798 0x31E TAG IS ALREADY PRODUCED
THE MAXIMUM NUMBER OF
TIMES
The PLC-5C is requesting data from
a ControlLogix tag that is already
being producted the maximum
number of times.
In the ControlLogix processor,
increase the number of times this
tag can produce data.
65522 0xFFF2 CONFIGURATION FROM MAP
ENTRY FAILED
The ControlNet cable from the
originating node to the target node is
broken or disconnected.
Fix and/or reconnect the ControlNet
cable.
The target node is not powered. Supply power to the target node.
The target slot is empty. Insert the proper module in the
correct slot of the target node.
The target slot contains the wrong
module type.
An incorrect module or slot was
entered in the map table.
Edit the I/O map table to show the
correct module type and slot.
Decimal
Code
Hex. Code Error Message Explanation/Possible Cause(s) Possible Corrective Action(s)
To Next Page
Loading...
Need help?
General
