Allen-Bradley produced and consumed tags: cross-controller

For Allen-Bradley Studio 5000 Logix Designer V35+.

Produced/consumed tags are the Logix-native way to share data between controllers without writing MSG instructions. The setup, the constraints, and the gotchas. This page is the working engineer's read — what the menu paths actually are in Studio 5000 Logix Designer V35+, what the keystrokes do, and the mistakes that bite once the program is on a real CPU. We program ControlLogix / CompactLogix ourselves, daily; we are not a Allen-Bradley sales channel.

What this is and when you need it

Produced/consumed tags are the Logix-native way to share data between controllers without writing MSG instructions. The setup, the constraints, and the gotchas. The walkthrough below is the same sequence we use when teaching this on the simulator. Every step names the exact menu path or keystroke; if a name has changed in your version of Studio 5000 Logix Designer V35+, it is called out. The simulator runs the same logic flow without the licence cost — ladder, FBD, and ST in a browser, with a virtual CPU you can download to.

Walkthrough

1. Understand when to use produced/consumed

Two ControlLogix or CompactLogix CPUs on the same Ethernet/IP network need to share data: tank levels, system enable bits, recipe handshakes. Options are MSG instructions (explicit, scheduled), produced/consumed tags (implicit, scheduled at RPI), or OPC UA (V35+ only). Produced/consumed wins for cyclic, real-time, low-latency data — sub-50 ms RPI is achievable on a modern stack.

2. Create the produced tag on the source CPU

On the producing controller, create a controller-scoped tag of the data type to share — typically a UDT. Right-click the tag > Edit Tag Properties > Class: Standard or Safety > Type: Produced. Set the maximum number of consumers (1–8 typical). Click OK. The tag is now broadcast on Ethernet/IP at the RPI any consumer connects with.

// Produced tag setup (source CPU)
// Tag: PlantStatus (UDT_PlantStatus)
// Class: Standard
// Type: Produced
// Max consumers: 4

3. Add the producer to the consumer's I/O config

On the consuming controller, in the Controller Organizer > I/O Configuration > the Ethernet network > right-click the local 1756-EN2T (or 5069 embedded port) > New Module > Generic Ethernet Module is wrong — instead, Add Module > the producer's CPU type (1756-L83E or 5069-L3x) > set the IP, slot, name. The consumer now sees the producer as a module.

4. Create the consumed tag

On the consuming controller, create a controller-scoped tag of the same UDT. Edit Tag Properties > Type: Consumed. Producer: select the module just added. Remote Tag Name: enter the produced tag's name as it exists on the producer (PlantStatus). Set the RPI — typically 50 ms or 100 ms. Click OK. On download, the consumer establishes a CIP connection and starts receiving updates at the RPI.

5. Verify and troubleshoot

On the consumer, expand the produced tag in Logix Designer > if the values are live, the connection is good. If 'Fault' appears in the tag's status, common causes: wrong remote tag name (case-sensitive in some firmware), wrong UDT (the UDT definition must match exactly between controllers), max consumers exceeded on the producer, EN2T module path wrong. The Module Properties > Connection tab on the consumer side shows the CIP connection state.

Common mistakes

• Defining the UDT differently on producer and consumer — even one extra padding byte breaks the connection silently and the consumer sees zeros
• Setting the RPI too aggressive (5 ms) on a network with 30+ consumed tags — the EN2T runs out of CIP connection capacity and starts dropping connections
• Using produced/consumed for one-shot data like a recipe load — a MSG instruction is lighter and the cyclic CIP connection is wasted overhead
• Forgetting to bump 'Max consumers' on the producer when adding a fourth or fifth consumer — the new consumer fails to establish the connection, Logix reports a connection failure in the controller diagnostic log, and the consumer's tag value freezes at its last good value

Each of these mistakes shows up in real projects every week. The simulator catches the first three at compile time; the fourth one only surfaces on hardware, which is why we recommend running the cert packs against a real CPU once you have completed the curriculum modules.

How this fits the broader curriculum

Allen-Bradley produced and consumed tags: cross-controller data without messages is one of the building blocks. The full Allen-Bradley curriculum on the simulator covers: programming-language fundamentals (ladder, FBD, ST), tag and variable scope, HMI tag binding, comms setup (Profinet / EtherNet/IP / Modbus depending on the platform), and the brownfield troubleshooting pathway. Each is its own module with worked examples and a portfolio piece. The cert packs at the Pro tier align to the ISA CCST exam content outline. Reference: isa.org.

For the platform-pick decision — when Allen-Bradley is the right call versus a different brand — see the brand hub. For region-specific context on where Allen-Bradley dominates the SA install base, see the relevant city pages under /brands/allen-bradley/training-in-* and the sector pages under /industries.

Where this sits in a working week

A technician who has finished this module typically spends the next three to four working days running the same logic flow on hardware. The simulator's value is the dry run — getting the keystrokes and the IDE conventions into muscle memory before you sit down with a live CPU. The first time you build this on hardware, expect the IO mapping and the addressing conventions to slow you down for a session or two; the simulator's project tree mirrors the same shape so the transition is short.

The full Allen-Bradley curriculum runs roughly 60 to 100 hours of focused practice. That breaks into bit logic and timers in the first 20 hours, FBs and structured data in the next 20, comms and HMI in the next 20, and a portfolio piece in the last block. Pace yourself — three or four hours per session, four sessions a week, and you finish in eight weeks. Most of our learners report that the bottleneck is not understanding the IDE, it is building reflex around the conventions: where Allen-Bradley expects you to put state, how it scopes variables, what naming patterns the OEMs in the sector use.

Vendor reference

Allen-Bradley's own documentation is the canonical reference once you are working on real hardware: Rockwell Automation Support. The simulator covers the basics; the vendor docs cover everything specific to a hardware revision, a firmware update, or a CPU-specific quirk. Bookmark both. The IEC 61131-3 standard that governs all the Allen-Bradley programming languages is at iec.ch.

What we don't claim

This site is not SAQA-registered, not MerSETA-accredited, and not an NQF-registered qualification provider. Our completion certificates are course-level only — they describe what you covered, not an NQF Level X qualification. The CCST cert from ISA is the portable industry credential we recommend; we are not an ISA cert delivery partner either, but our cert packs are CCST-aligned. The walkthrough above is brand-specific because Allen-Bradley's tooling has its own conventions; do not assume the same menu paths exist in another brand's IDE.

How to start

You can be running allen-bradley produced and consumed tags: cross-controller data without messages in the simulator in 5 minutes. Free tier covers the basics, no card, no install. Once you are 20 minutes in you will know whether the platform fits how you learn. The full Allen-Bradley curriculum is the Basic tier (USD 12 / month). The cert packs and portfolio export sit in the Pro tier (USD 29 / month). For institutional buyers — TVET colleges, private training providers, in-house engineering training departments — the bulk-licence option is the Teams tier, USD 199 per seat per year, minimum 5 seats. The training-centres page has the institutional pitch and the contact form.

Honest expectations on the local job market

Petrochem, mining, FMCG, automotive, and water-utility sectors all carry Allen-Bradley install bases somewhere in their stack. Knowing the IDE conventions on this page does not get you a job by itself; it gets you past the first technical screen. The portfolio piece — a working program you built yourself, with a wiring track, a tag list, an HMI screen, and a short README explaining the design choices — is what lands the second interview. The simulator's portfolio export bundles all of that into a single folder you can hand a hiring engineer. Recruiters in this space skim the README first; if your design choices are coherent, they read the code.

Load-shedding has reshaped what gets built first in Allen-Bradley programs across SA. Power-recovery patterns — controlled shutdown on UPS hold, state recovery from retentive memory, sequenced restart of motor groups — now belong in the same module as the basics. Allen-Bradley produced and consumed tags: cross-controller data without messages fits into that shape: every line of code you write needs to consider what state the controller is in when it powers up after a 2.5-hour cut, not just what state it is in when running. The simulator's restart-from-cut mode lets you exercise this without bricking real hardware.