Home › Technical articles

Đọc bằng tiếng Việt

Logix MSG instruction error codes: .ERR and .EXERR tables, path, cached connections and common fixes

TDL Industrial Automation · Last updated:

From the Studio 5000 Logix Designer 38.02 help: the MSG instruction, message types, the MESSAGE tag status bits and error members, path syntax, connected and cached messages, load limits, the .ERR code table, .EXERR extended codes, PLC-5/SLC and block-transfer codes, and the common error groups with the settings to check.

When an MSG instruction in a ControlLogix or CompactLogix controller fails, the controller sets the .ER bit of its MESSAGE tag, writes an error code to .ERR and, for some codes, more detail to .EXERR. The code only makes sense together with the message type and the path, because the error tables differ by message type. This article follows the MSG pages of the Studio 5000 Logix Designer 38.02 online help (last update June 2026); in Rockwell's PDF reference manual 1756-RM018A-EN-P (September 2025) the MSG instruction starts at p. 141, the extended error codes at p. 164 and the communication details at p. 171. I/O connection faults are covered in ControlLogix I/O module faults 16#0204 and 16#0203.

MSG path from controller to target: where errors ariseFour stages from top to bottom: the local controller with the MSG instruction and MESSAGE tag; the local EtherNet/IP module in slot 2; the remote EtherNet/IP module at 10.10.10.10; the target controller in slot 0. To the right of each stage are the error codes whose meaning points to it. At the bottom, the example path 1,2,2,10.10.10.10,1,0 entry by entry. Codes and meanings from the Studio 5000 Logix Designer 38.02 help.MSG path from controller to target: where errors ariseLocal controllerMSG and MESSAGE tag00FD · Message uninitialized00FE · Message timeoutmore than 16 or 256 MSGs enabled at once: queue delaysport 1 · backplane, to slot 2Local EtherNet/IP moduleslot 20001 + 0311 · Port not available0001 + 0312 · Link address not available0001 + 0315 · Invalid segment type00FB · Message port not supportedport 2 · Ethernet, to IP 10.10.10.10Remote EtherNet/IPmodule10.10.10.100001 + 0204 · Unconnected message timeout0001 + 0203 · Connection timeout0007 · Connection lost0001 + 011A · Application out of connectionsport 1 · backplane, to slot 0Target controllerslot 0, target tag0005 · Destination unknown or element undefined0008 · Service unsupported0015 · Too much data00FF + 2107 · Type is invalid or not supported00FF + 210B · Symbol does not existExample path in the help's syntax: 1,2,2,10.10.10.10,1,01out to thebackplane2to slot 22out of theEthernet port10.10.10.10to the remotemodule1out to thebackplane0to slot 0Codes and meanings from the Studio 5000 Logix Designer 38.02 help (read 15 November 2026). The slots, IPaddress and where each code is placed are TDL's example, not Rockwell's. Figure: drawn by TDL.
Figure 1: MSG path from controller to target: where errors arise. On a phone, swipe sideways to see the whole figure.

1. What the MSG instruction does

The help describes MSG as an instruction that reads or writes a block of data to another module on a network, asynchronously. It is a transitional instruction: in ladder logic the rung must go from false to true for each execution, and in Structured Text it needs a condition so it runs only on a change. The 38.02 help lists it for CompactLogix 5370, ControlLogix 5570, Compact GuardLogix 5370, GuardLogix 5570, CompactLogix 5380, Compact GuardLogix 5380, ControlLogix 5580, GuardLogix 5580 and ControlLogix 5590.

The message type is chosen by target:

Target Message types
Logix 5000 controller CIP Data Table Read, CIP Data Table Write
I/O module configured in Logix Designer Module Reconfigure, CIP Generic
PLC-5 PLC-5 Typed Read/Write, PLC-5 Word Range Read/Write
SLC or MicroLogix SLC Typed Read/Write
Block-transfer module Block-Transfer Read/Write
PLC-3, PLC-2 PLC-3 Typed and Word Range, PLC-2 Unprotected Read/Write

All types except the CIP ones and Module Reconfigure are not supported when redundancy is enabled on a ControlLogix 5580 or GuardLogix 5580.

The help's guidelines matter for errors later. Each MSG needs its own control tag of type MESSAGE, at controller scope, not part of an array or a user-defined type. An MSG can reach only controller-scope tags. For CIP Data Table messages, source and destination types must match. Between two Logix controllers, the tag in the other controller must be a base tag, not an alias. For 16-bit devices such as a PLC-5 or SLC 500, the help suggests INT buffers in the message. For a write, the source cannot be an I/O structure tag or a BOOL.

2. The MESSAGE tag: status bits and error members

Member What it tells
.EN Set when the rung goes true; stays set until .DN or .ER is set and the rung is false
.EW The request has entered the queue; cleared when .ST is set
.ST Execution has started; cleared when .DN or .ER is set
.DN The last packet transferred successfully
.ER The transfer failed; .DN and .ER clear on the next false-to-true transition
.TO Set by the program, it stops the message and sets .ER
.EN_CC Keep the connection open (cache); serial-port connections are never cached
.ERR Error code, valid when .ER is set
.EXERR Extended error code with more detail for some codes
.ERR_SRC Shows the error path in the Message Configuration dialog
.REQ_LEN, .DN_LEN Words the instruction tries to transfer, and words actually transferred
.UnconnectedTimeout Timeout for an unconnected message or for making a connection; default 30 seconds
.ConnectionRate, .TimeoutMultiplier Connected-message timeout = ConnectionRate × TimeoutMultiplier; defaults 7.5 seconds and 0, which counts as 4, so 30 seconds

The help warns not to change .DN, .EN, .ER, .EW or .ST, directly or through .FLAGS: the controller may take a non-recoverable fault and clear the project from its memory.

3. Path, connected messages and cache

The path is typed, picked with Browse from the I/O configuration, or both. It is a list of pairs: port, then next address. Port 1 is the backplane. The help's port table groups DF1 channel 0, ControlNet, EtherNet/IP and DH+ channel A under port 2, and DH+ channel B and DF1 channel 1 under port 3. The next address is a slot number on the backplane, a station address 0–254 on DF1, a node 1–99 on ControlNet, 8# and an octal node on DH+ (8#37), or on EtherNet/IP an IP address, IP address:port, or a DNS name. THIS is a path to the controller itself and sends an unconnected message to it. Port numbers can differ by controller: on a ControlLogix 5590, 1756-UM900 gives path 2 in Linear/DLR mode, and 3 for the enterprise port or 4 for the device-level port in Dual-IP mode.

The communication method is CIP for the backplane, EtherNet/IP and ControlNet, DH+ through a 1756-DHRIO (channel, source link, destination link, destination node), or CIP with Source ID for unsolicited messages to FactoryTalk Linx. Module status codes of the DHRIO: 1756-DHRIO status codes.

Connections by message type:

Message type Connection
CIP Data Table Read/Write Optional; Rockwell recommends connected
PLC-2, PLC-3, PLC-5, SLC over CIP or CIP with Source ID Optional
PLC-2, PLC-3, PLC-5, SLC over DH+ Always
CIP Generic Optional; Rockwell recommends unconnected
Block-Transfer Read/Write Always

A cached connection stays open after the MSG is done, which saves execution time; an uncached one closes and frees the connection. The help limits cached connections to 32 on a CompactLogix 5370 or ControlLogix 5570 and 256 on a ControlLogix 5580, and advises caching the connected messages that run most often. Messages to one device that are not enabled at the same time share a connection; messages enabled together use one each. If the target does not support connected CIP messages and Connected is ticked, an error appears when the MSG runs. CIP Generic messages larger than 480 bytes need the Large Connection option.

Load limits: more than 16 MSGs enabled at once on a 5370 or 5570, or more than 256 on a 5580, can delay some MSGs from entering the queue. A 5370 or 5570 has 10 to 40 unconnected buffers, 10 by default; if all are in use when an instruction leaves the queue, it errors and transfers no data.

4. Error codes (.ERR)

The help notes that Logix Designer does not always display the full description. Codes are hexadecimal.

Code Meaning
0001 Connection failure (see extended code)
0002 Insufficient resource
0003 Invalid value
0004 IOI syntax error (see extended code)
0005 Destination unknown, class unsupported, instance undefined or structure element undefined (see extended code)
0006 Insufficient packet space
0007 Connection lost
0008 Service unsupported
0009 Error in data segment or invalid attribute value
000A Attribute list error
000B State already exists
000C Object model conflict
000D Object already exists
000E Attribute cannot be set
000F Permission denied
0010 Device state conflict
0011 Reply will not fit
0012 Fragment primitive
0013 Insufficient command data
0014 Attribute not supported
0015 Too much data
001A, 001B Bridge request too large, bridge response too large
001C, 001D Attribute list shortage, invalid attribute list
001E Embedded service error
001F Connection related failure (see extended code)
0022 Invalid reply received
0025 Key segment error
0026 Invalid IOI error
0027 Unexpected attribute in list
0028, 0029 DeviceNet error: invalid member ID, member not settable
00D1 Module not in run state (Logix Designer shows "Unknown error")
00FB Message port not supported
00FC Message unsupported data type
00FD Message uninitialized
00FE Message timeout
00FF General error (see extended code)

5. Extended error codes (.EXERR)

Logix Designer shows no text for extended codes, so they are looked up by hand:

.ERR .EXERR Meaning
0001 0100 Connection in use
0103 Transport not supported
0106 Ownership conflict
0107 Connection not found
0108 Invalid connection type
0109 Invalid connection size
0110 Module not configured
0111 EPR not supported
0113 MSG write failed
0114 Wrong module
0115 Wrong device type
0116 Wrong revision
0118 Invalid configuration format
011A Application out of connections
0203 Connection timeout
0204 Unconnected message timeout
0205 Unconnected send parameter error
0206 Message too large
0301 No buffer memory
0302 Bandwidth not available
0303 No screens available
0305 Signature mismatch
0311 Port not available
0312 Link address not available
0315 Invalid segment type
0317 Connection not scheduled
001F 0203 Connection timeout
0004, 0005 0000 Out of memory
0001 Out of instances
00FF 2001 Excessive IOI
2002 Bad parameter value
2018 Semaphore reject
201B Size too small
201C Invalid size
2100 Privilege failure
2101 Invalid keyswitch position
2102 Password invalid
2103 No password issued
2104 Address out of range
2105 Address and how many out of range
2106 Data in use
2107 Type is invalid or not supported
2108 Controller in upload or download mode
2109 Attempt to change number of array dimensions
210A Invalid symbol name
210B Symbol does not exist
210E Search failed
210F Task cannot start
2110 Unable to write
2111 Unable to read
2112 Shared routine not editable
2113 Controller in faulted mode
2114 Run mode inhibited

Several extended codes under 0001 carry the same numbers as I/O connection faults (0106, 0107, 0114–0116, 0203, 0204); the I/O side is in the I/O fault article.

6. PLC-5, SLC and block-transfer messages

From Logix firmware 10.x, PLC and SLC (PCCC) message errors have their own .ERR values; before, many shared 00F0 with a sub-code in .EXERR. The help maps both forms. The 10.x values:

.ERR (10.x) Meaning
1000 Illegal command or format from local processor
2000 Communication module not working
3000 Remote node missing, disconnected or shut down
4000 Processor connected but faulted (hardware)
5000 Wrong station number
6000, F00C Requested function not available
7000 Processor in Program mode
8000 Compatibility file does not exist
9000 Remote node cannot buffer command
B000 Processor downloading, not accessible
F001–F005 Address converted incorrectly, incomplete, incorrect, symbol not found, symbol 0 or above maximum
F006, F007 Address file does not exist in target; destination file too small for the words requested
F008–F00A Cannot complete request; data or file too large; target cannot packetize the information
F00B, F010 Privilege error, access denied; no access
F00D–F00F Request redundant; command cannot be executed; histogram overflow
F011, F012 Data type requested does not match data available; incorrect command parameters
F013–F015 Address reference to deleted area; execution failure for unknown reason; data conversion error
F016–F018 Scanner not available; adapter not available to the module; 1771 module response not valid
F019–F01D Duplicate label; file owner active; program owner active (download or online edit); disk file write-protected; disk file used by another application

Block-transfer messages have their own table of 22 codes from 00D0 to 00FD. Examples: 00D0, no response from the block-transfer module within 3.5 seconds; 00EA, the scanner is not configured for that rack; 00F7, the instruction's timeout expired; 00FD, size plus index exceeds the data table file. The same number can mean different things: 00D1 is "module not in run state" in the CIP table and a read checksum mismatch in the block-transfer table, which is why the help says the codes depend on the MSG type.

7. Common errors by group

The grouping is ours; codes, meanings and settings are from the help.

Group Codes Settings to check
Path 0001 + 0311, 0312, 0315; 00FB; 0001 + 0205 Each port and next address in the path; the port numbers of that module (5590 modes); communication method
Connection and timeout 0001 + 0204, 0203; 001F + 0203; 0007; 00FE Target reachable on the path; .UnconnectedTimeout, .ConnectionRate and .TimeoutMultiplier
Resources 0002; 0001 + 011A, 0301, 0302 Cached connections against 32 or 256; MSGs enabled at once against 16 or 256; unconnected buffers
Target not found 0005; 0004, 0026; 00FF + 210A, 210B, 2104; F006 Tag name in the target, controller scope, base tag not alias
Service not supported 0008, 0014; 00FC; 0010; 00FF + 2108, 2113, 2114; 7000 Message type for that target; CIP Generic service; Connected ticked for a target without connected CIP; target mode
Data type or size 0015, 0013, 0006, 0011; 001A, 001B; 0001 + 0206; 00FF + 2107, 201B, 201C; F007, F011 Source and destination types match; number of elements; INT buffers for 16-bit targets; Large Connection over 480 bytes

When a computer cannot reach the controller at all, see FactoryTalk Linx cannot see the controller; for messages that used to cross a DeviceNet scanner, see DeviceNet to EtherNet/IP.

What we check first

This is TDL's practice, not a Rockwell requirement.

  • We write down .ERR, .EXERR and the error path before anyone retriggers the message, and look the code up in the table for that message type.
  • We walk the path pair by pair against the real chassis and network: slot numbers, port numbers of each module, IP addresses.
  • On the target we check the tag name, scope, data type and element count, and that it is a base tag.
  • We count the MSGs that can be enabled together and the cached connections, against the controller's limits in the help.
  • We check the rung logic: one MESSAGE tag per MSG, a false-to-true transition per execution, nothing writing to the status bits.
  • If the path crosses a firewall, we check the open ports against the FactoryTalk and Logix firewall article.

MSG troubleshooting at TDL

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. Our breakdown support covers troubleshooting on site or remotely and program fixes on Allen-Bradley systems; see also Rockwell Automation system integrator in Vietnam and Logix major fault codes.

Frequently asked questions

What does MSG error 0001 with extended error 0204 mean?

Error 0001 is a connection failure, and extended code 0204 under it is an unconnected message timeout. Check the path pair by pair and that the target answers on it; the default unconnected timeout is 30 seconds.

What does MSG error code 00FF mean?

00FF is a general error, and the extended code gives the detail, for example 210B (symbol does not exist), 2107 (type is invalid or not supported) or 2108 (controller in upload or download mode). Logix Designer shows no text for extended codes.

How many MSG instructions can a ControlLogix run at the same time?

The help says more than 16 enabled at once on a CompactLogix 5370 or ControlLogix 5570, or more than 256 on a ControlLogix 5580, can delay some messages from entering the queue. Cached connections are limited to 32 and 256 on the same controllers.

Should an MSG connection be cached?

A cached connection stays open after the MSG is done and saves execution time; Rockwell advises caching the connected messages that run most often, within the controller's limit. A message that runs rarely can leave the connection closed so it is free for other uses.

Where do I see the MSG error code?

In the MESSAGE tag: .ERR holds the error code when .ER is set, .EXERR the extended code, and .ERR_SRC shows the error path in the Message Configuration dialog.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Breakdown support & resident engineers Rockwell Automation (Allen-Bradley)