Engineering Logix Produced and Consumed Tags

Produced and consumed tags let Logix controllers exchange controller-scoped data without message instructions. The producer makes a tag available; one or more configured consumers receive it at a requested packet interval. The mechanism is straightforward, but a stable implementation depends on matching data definitions, network paths, connection budgets and failure handling.

Choose the Pattern for the Right Job

Use produced and consumed tags when peer controllers need cyclic data with a defined update rate. Typical examples include machine-state coordination, line permissives, production counts and shared status. The connection is configured rather than triggered by ladder logic, so it suits data that must be refreshed continuously.

Do not treat this method as a substitute for every controller-to-controller exchange. Explicit messages can be better for occasional reads or writes. An HMI, historian or broker may be better for supervisory data. Safety data follows separate controller, firmware and configuration rules. Start by defining what information is needed, how fast it must arrive and what the receiving machine must do when it stops arriving.

Define a Stable Data Contract

The produced and consumed tags must use matching data types, including array dimensions. A user-defined data type is usually easier to govern than a loose set of individual values. Group the process data, a schema revision, operating mode and health indicators in one structure. Reserve spare members when future expansion is likely, but keep the packet focused.

Document the meaning, units and valid range of every member. A numeric value is not self-explanatory: it may represent engineering units, raw counts or a scaled percentage. Define which controller owns each command and status. Two controllers should not independently write competing versions of the same machine state.

Configure the Producer

Create the source tag at controller scope and set its usage to produced. Configure the number of expected consumers with reasonable allowance for the design. Rockwell Automation notes that a produced tag can serve multiple consumers, while the exact controller and network limits depend on the hardware and firmware.

Update the complete structure coherently. If separate logic routines write individual members at different moments, a consumer may observe a mixed state. Build the outgoing structure in one routine or copy a completed working structure to the produced tag after the calculations are finished.

Configure Each Consumer

Add the producing controller to the consumer's I/O configuration through the actual supported network path. Then create a consumed controller-scoped tag with the same data type. Enter the producer name and remote tag name exactly. The configured path, controller identity and tag spelling all form part of the connection.

Select the requested packet interval from the process requirement, not from the fastest value the dialog permits. A short RPI consumes network and controller resources. A slow RPI may delay interlocks or line coordination. Include network update time, task execution and application response when calculating the maximum acceptable age of data.

Design for Lost Connections

Data that stops updating can still look plausible. A consumer must distinguish current information from retained information. Rockwell documentation supports a CONNECTION_STATUS member at the start of a user-defined structure for monitoring produced and consumed connections. An application-level heartbeat or sequence counter can add evidence that the producer logic is executing and the payload is changing as expected.

Define the response to stale data for every use case. A display value may show “communication lost.” A production count may be held with a quality flag. A motion permissive may need to drop and require a controlled restart. Do not automatically force a shared command to zero unless zero is the defined safe and operationally correct response.

Commission the Exchange Methodically

Verify the physical network and controller paths before troubleshooting tags. Confirm that each controller is online, reachable and represented correctly in the I/O tree. Download the producer and consumer configurations in a controlled sequence. Watch the connection status before testing application behavior.

Change one test value at the producer and trace it through the consumer structure. Test every member that affects operation, including signed values, arrays and mode bits. Measure the observed update time against the design target. Then disconnect the producer or network under an approved test condition and confirm the stale-data alarm and machine response.

Troubleshoot Common Faults

A connection that never establishes usually points to an incorrect path, controller name, remote tag name, data type or capacity limit. A connection that drops intermittently may involve network loading, link instability, controller resource pressure or an RPI that is too aggressive. A healthy connection with wrong values usually indicates a data-contract or application-logic problem.

Compare both projects side by side. Check the structure definition, array size and revision. Review controller diagnostics and managed-switch counters before changing RPIs at random. If a produced structure changes, treat that as an interface revision and coordinate the update across every consumer.

Maintain the Interface as Plant Infrastructure

Archive both controller projects and keep an interface register listing producer, consumers, tag names, data types, RPIs and failure actions. Include the exchange in backup, firmware and network-change reviews. When a controller is replaced, verify the communication path and connection state before enabling machine commands.

Related hardware can be found in the Allen-Bradley ControlLogix and Communication & Networking collections. Configuration details and platform limits should be checked in Rockwell Automation's Produced and Consumed Tags programming manual. A well-defined data contract and explicit stale-data response make the connection maintainable long after commissioning.