Logix5000 error codes
- Last UpdatedSep 12, 2024
- 3 minute read
The Logix5000 processor generates error conditions. The following tables show these errors and the server-specific strings generated by the Communication Driver to the logger.
Note: All of the error messages shown in the following table apply to the DASProtFail log flag.
|
General Allen-Bradley Error Code (High byte = 00) |
Logger Message |
|---|---|
|
00 |
Success |
|
01 |
Connection failed |
|
02 |
Insufficient Connection Manager resources |
|
03 |
Invalid connection number |
|
04 |
IOI could not be deciphered. Either it was not formed correctly or the match tag does not exist |
|
05 |
The particular item referenced could not be found |
|
06 |
The amount of data requested would not fit into the response buffer. Partial data transfer has occurred. |
|
07 |
Connection has been lost |
|
08 |
Requested service not supported |
|
09 |
Error in data segment or invalid attribute number |
|
0A |
An error has occurred trying to process one of the attributes |
|
0C |
Service cannot be performed while object is in current state |
|
10 |
Service cannot be performed while device is in current state |
|
11 |
Response data too large |
|
13 |
Not enough command data/parameters were supplied in the command to execute the service requested |
|
14 |
Attribute not supported |
|
15 |
Too much data was received |
|
1C |
An insufficient number of attributes were provided compared to the attribute count |
|
1E |
Errors encountered with the items in the message |
|
26 |
The IOI word length did not match the amount of IOI which was processed |
|
None of the above codes |
Unknown Status |
|
Extended Allen-Bradley Error Code (Hex) |
Logger Message |
|---|---|
|
2104 |
The beginning offset was beyond the end of the template. |
|
2105 |
You have tried to access beyond the end of the data object. |
|
2106 |
Data in use. |
|
2107 |
The abbreviated type does not match the data type of the data object. |
|
0100 |
Connection in Use or Duplicate Forward Open. |
|
0103 |
Transport Class and Trigger combination not supported. |
|
0106 |
Ownership Conflict. |
|
0107 |
Connection not found at target application. |
|
0108 |
Invalid Connection Type. Indicates a problem with either the Connection Type or Priority of the Connection. |
|
0109 |
Invalid Connection Size. |
|
0110 |
Device not configured |
|
0111 |
RPI not supported. May also indicate problem with connection time-out multiplier. |
|
0113 |
Connection Manager cannot support any more connections. |
|
0114 |
Either the Vendor ID or the Product Code in the key segment did not match the device. |
|
0115 |
Product Type in the key segment did not match the device. |
|
0116 |
Major or Minor Revision information in the key segment did not match the device. |
|
0117 |
Invalid Connection Point. |
|
0118 |
Invalid Configuration Format. |
|
0119 |
Connection request fails since there is no controlling connection currently open. |
|
011A |
Target Application cannot support any more connections. |
|
011B |
RPI is smaller than the Production Inhibit Time. |
|
0203 |
Connection cannot be closed since the connection has timed out. |
|
0204 |
Unconnected Send timed out waiting for a response. |
|
0205 |
Parameter Error in Unconnected Send Service. |
|
0206 |
Message too large for Unconnected message service. |
|
0207 |
Unconnected acknowledge without reply. |
|
0301 |
No buffer memory available. |
|
0302 |
Network Bandwidth not available for data. |
|
0303 |
No Tag filters available. |
|
0304 |
Not Configured to send real-time data. |
|
0311 |
Port specified in Port Segment Not Available. |
|
0312 |
Link Address specified in Port Segment Not Available. |
|
0315 |
Invalid Segment Type or Segment Value in Path. |
|
0316 |
Path and Connection not equal in close. |
|
0317 |
Either Segment not present or Encoded Value in Network Segment is invalid. |
|
0318 |
Link Address to Self Invalid. |
|
0319 |
Resources on Secondary Unavailable. |
|
031A |
Connection already established. |
|
031B |
Direct connection already established. |
|
031C |
Miscellaneous. |
|
031D |
Redundant connection mismatch. |
|
None of the above codes |
Unknown Extended Status. |
Note: For more information about the general and extended Allen-Bradley error codes, please refer to the Allen-Bradley controller documentation.