1785-UM022B-EN-P - February 2002
E-2 Fault Codes
205 ControlNet configuration exceeds processor resources.
IMPORTANT: Scheduled connections will be closed. You must cycle
power, save with RSNetWorx, or download the program to reopen
the connections.
Because the configuration software is unable to accurately predict all
the resources that the processor will require to execute your ControlNet
configuration software (based on the relative loading on the processor),
this fault code is used if the processor determines that your
configuration (typically when you accept Channel 2 edits) exceeds the
processor’s available bandwidth.
Typical causes of this error code include:
• receiving data from the ControlNet network faster than the ControlNet
PLC-5 processor can parse it
• performing I/O updates too frequently
• performing immediate ControlNet I/O ladder instructions too
frequently.
See S:74 and S:75 for more information.
• Reduce the number of ControlNet I/O map table
entries. Possible ways to do this include:
- using a discrete rack connection instead of
multiple discrete module connections
- combining multiple I/O racks into a single
I/O rack
- putting peer-to-peer data in contiguous
blocks in the data table so that less send
and receive scheduled messages are
required
• Increase your Network Update Time and/or
increase the Requested Packet Intervals for
scheduled data transfers in your I/O map table.
• Increase your ladder program scan by either
adding more logic or by increasing the
Communications Time Slice (S:77).
• Reduce the number or frequency of immediate
ControlNet I/O ladder instructions that are
performed.
206 This error code is reserved. Contact your local Rockwell Automation
representative if you get this message.
207 This error code is reserved. Contact your local Rockwell Automation
representative if you get this message.
208 Too many pending ControlNet I/O connections. Delete one or more I/O map table entries and
reaccept edits for the ControlNet configuration.
230 System attempted transition to Run mode with processor in Invalid
backup state.
Change from the Invalid backup state to the No
Control backup state before transitioning into Run
mode. Refer to the Invalid backup state
troubleshooting table later in this chapter.
231 Bypassed qualification (may occur during race condition when both
processors attempt to go into Run mode at the same time).
Transition the PLC-5 processors into Run mode
one at a time.
232 Both processors attempted to be primaries. Check all media for broken cables, loose
connectors, missing terminators, etc..
233 ControlNet configuration invalid on transition into Run mode. Reconfigure the ControlNet channel.
234 Failed Qualification. Refer to the qualification major faults
troubleshooting table later in this chapter.
235
Illegal invalid backup state Cycle power to the processor. If the fault reoccurs,
contact Rockwell Automation Technical Support at
440-646-6800
236
Illegal No Control backup state Cycle power to the processor. If the fault reoccurs,
contact Rockwell Automation Technical Support at
440-646-6800
237
Illegal Primary/Secondary backup state Cycle power to the processor. If the fault reoccurs,
contact Rockwell Automation Technical Support at
440-646-6800
238
Incompatible firmware revisions Install the same series and revision of firmware
into both hot backup PLC-5 processors
239
ControlNet keeper mismatch Use RSNetworx to make the PLC-5 processor a
valid keeper
This fault code: Indicates this fault: Take this corrective action: