IMDHMIControls LibraryShop main store

How-to

Configure ControlLogix MSG reads and writes to a PLC-5

Industrial networks Published 5 min read

Short answer

DH+ is peer-to-peer token passing, so there is no master or slave to configure: make the ControlLogix the single initiator with one MSG instruction per direction, each on its own MESSAGE control tag, configured as a PLC-5 typed read or typed write with the route browsed on the Communication tab. Verify the transferred value at the destination address, not the online session.

On this page
  1. Why there is no master or slave to configure
  2. Give each transfer its own MSG and control tag
  3. Configure the read and the write
  4. Trigger one message at a time
  5. Verify the value at the destination
  6. Pick the next fix from what you observe
  7. Questions asked

DH+ has no master or slave to set. It is a peer-to-peer, token-passing network, so both directions of the exchange go in the ControlLogix as MSG instructions: one configured as a PLC-5 read, one as a PLC-5 write, each on its own MESSAGE control tag with a route browsed on the Communication tab. The PLC-5 carries no messaging rungs at all. Going online with the PLC-5 over the same link proves the programming path, not a message route — two separate paths, which is why a working online session and a dead message can coexist. This walkthrough starts from a link that already reaches the processor; if the route itself is in doubt, start with how to route a ControlLogix MSG to a PLC-5 over DH+.

Why there is no master or slave to configure #

The DH+ documentation (1770-6.2.2) describes the network as token passing: only the node holding the token transmits, and the token circulates so every station gets its turn. Nothing in the protocol assigns a master that polls or a slave that waits. "Master" in this arrangement means the ControlLogix owns the logic and initiates the transfers — a design decision, not a protocol setting.

Commit to that decision and keep it simple: the ControlLogix is the single initiator for both directions, and the PLC-5 answers requests against its data tables with no ladder of its own. A station that initiates a message still needs a valid destination path and matched data definitions, so the remaining work is in the MSG configuration.

Give each transfer its own MSG and control tag #

Add one MSG instruction per transfer — the read, the write, and more if different data lives in different files — rather than one instruction trying to serve both directions. Each MSG instruction carries a control tag of type MESSAGE; create the tag from the instruction's tag field and accept the MESSAGE type. The control tag holds that message's configuration and status, so keep one tag per instruction and each transfer keeps its own state.

Configure the read and the write #

  1. Drop the MSG instruction on a rung and create its MESSAGE control tag.
  2. Open the message configuration and pick the PLC-5 message type for the direction: a typed read brings PLC-5 data into the ControlLogix, a typed write pushes ControlLogix data out. The RSLogix 5000 help topic specifying PLC-5 messages lists which message types pair with which PLC-5 data types — follow that table instead of guessing.
  3. Read the PLC-5 data-table address and the element count out of the PLC-5 program itself. A working route validates none of that.
  4. Match the ControlLogix side to the file type: an integer file maps to an INT array, and the element count equals the number of array elements the message touches.
  5. Set the direction deliberately: in a read, the PLC-5 address is the source and the ControlLogix tag the destination; in a write, the reverse. A reversed pair is how valid data lands in the wrong controller.
  6. On the Communication tab, browse to the PLC-5 and confirm the selected target is the processor you went online with. When the path crosses a bridge, enter it as a multi-hop route.

A write changes live data in a running PLC-5, so make the first test write in a machine state where those words cannot command outputs or motion.

Worked example: ten integers each way #

Example values, not ones from any real program: the PLC-5 stores a batch record in the ten integer elements N7:20 through N7:29, and the ControlLogix needs them in one tag. Declare an INT array — BatchData, INT[10], a name of this example — and configure a typed read with source element 20 of file N7 and length 10 elements. The sizing arithmetic: 10 elements × 16 bits per element = 160 bits, and 160 bits ÷ 8 bits per byte = 20 bytes moved word for word, since a PLC-5 integer element and a ControlLogix INT are both 16 bits. The count and the array must match, 10 to 10; an INT[8] cannot hold a 10-element read.

The write direction follows the same rule with the sides swapped: a setpoint staged in BatchData[0] goes out as a typed write to N7:20 with length 1 element — 1 × 16 bits = 16 bits, 2 bytes. If the setpoint originates in a 32-bit tag in your logic, move it into the INT array first so the write carries exactly what you sized.

Trigger one message at a time #

Configured is not proven. Trigger the read first, from a deliberate test condition such as a manually set bit rather than the production timer, and watch the status members of its MESSAGE control tag while it runs: they show whether the message is still active, has completed, or finished with an error, and the instruction help for your installed software names the exact members to watch. If the message sits active far longer than the network should take, check that the rung is not retriggering the instruction before it can finish. If it completes with an error on every trigger, look at the route first, then at the message type, address, element count and data pairing — in that order.

Test the write the same way, separately, so a failure names its own direction.

Verify the value at the destination #

The acceptance test is the value at the destination, not the session that got you there. For the read, compare the ControlLogix destination against the PLC-5 address it came from. For the write, open the PLC-5 data table and confirm the addressed elements — and only those — changed. Then swap the test trigger for the production trigger and confirm the message still completes without recurring errors on every cycle, with no overlapping triggers stacking up.

Pick the next fix from what you observe #

What you observe Where to look next
Cannot go online or browse the PLC-5 DH+ connectivity and target selection; message fields cannot help until this passes
Online works, the MSG finishes with an error The message's route first, then message type, address, element count, data pairing
The MSG completes but the value is wrong Transfer direction, source and destination mapping, or a second writer to that address
Works on the test trigger, not in normal operation Production trigger conditions and retriggers before completion

Fix the row you are in. Rewiring DH+ or editing the PLC-5 accomplishes nothing when the ControlLogix already reaches the processor and the real gap is an unconfigured message or a mismatched data target.

Questions asked

Can the PLC-5 also initiate messages on the same DH+ link?

Yes. Token passing lets any station initiate, so nothing in the protocol stops the PLC-5 from running its own MSG instructions. The practical rule is one writer per address: if both controllers write the same data-table element, each overwrites the other and a correctly configured message looks unreliable. Give every shared address a single writer and let the other side read it.

Can I change a running MSG configuration without going offline?

Yes. The Logix 5000 Controller Messages documentation allows reconfiguring a MSG instruction during runtime by writing new values to the members of its MESSAGE control tag from logic. That is the supported way to redirect a message or change its target while the controller runs; the instruction uses the updated members on its next trigger.

Does the PLC-5 side need any logic for this to work?

No. A PLC-5 processor services incoming message requests against its own data tables with no rungs required. What the PLC-5 side must have is a data table that exists and is long enough for the address and element count you target — a read aimed past the end of a file targets data that is not there, and no route repair fixes that.

Is this configured in RSLogix 5000 or Studio 5000 Logix Designer?

Both names cover the same instruction. The MSG instruction, its MESSAGE control tag and the Communication tab are configured in the ControlLogix project whether the software is called RSLogix 5000 or Studio 5000 Logix Designer. The RSLogix 5000 help topic specifying PLC-5 messages gives the message-type and tag pairing rules for PLC-5 data.

Keep reading

  • How-to

    How to route a ControlLogix MSG to a PLC-5 over DH+

    The CIP path is 1,5,2,10.60.28.60,1,2 and it ends at the 1756-DHRIO: out the local backplane to the ENBT/A in slot 5, over Ethernet to the bridge ENBT/A at 10.60.28.60, then across the bridge backplane to the DHRIO in slot 2. DH+ carries no CIP, so Channel A and DH+ node 67 are set on the message's communication tab, never appended to the path.

    Industrial networks

  • Troubleshooting

    Why a Schneider M251 does not appear in RSLinx

    RSLinx and FactoryTalk Linx browse one transaction: the EtherNet/IP List Identity request, and a device appears only when the port you are cabled to answers it. Ping and Schneider software prove IP reachability, nothing more. Enable the M251's EtherNet/IP service on the connected port, browse through the right PC adapter, and register the M251 EDS when the entry shows a red X with a yellow question mark.

    Industrial networks

  • How-to

    CompactLogix MSG to SLC 5/04 through a DH+ gateway

    The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.

    Industrial networks