How to Set Up Produced/Consumed Tags on 1769-L30ER PLC
This guide explains how to configure Produced/Consumed communication between a 1769-L30ER and another Logix PLC. You will learn the core settings, network tips, and diagnostic methods for reliable data exchange in industrial automation.
What Is the Producer-Consumer Model?
This communication method removes the need for master-slave polling. As a result, it reduces network delays and uses less bandwidth. The 1769-L30ER supports up to 16 produced and 16 consumed tags at the same time. One produced tag can send data to multiple controllers, which makes multicast traffic more efficient.
The consumer side uses a Requested Packet Interval (RPI) to decide how often it gets updates. RPI values usually range from 2 ms to 750 ms. Faster RPIs give better performance but increase network load. Engineers must choose a value that balances speed with system capacity.
What You Need Before Starting
Make sure both PLCs are powered and connected through an EtherNet/IP network. The 1769-L30ER must have firmware revision 20.011 or later. Use Studio 5000 Logix Designer version 21 or newer to access all settings.
Assign unique IP addresses to each controller. For example, set PLC A to 192.168.1.10 and PLC B to 192.168.1.20. Both devices should use the same subnet mask and gateway. The network switch should support multicast filtering to avoid unnecessary traffic.
The L30ER supports up to 256 TCP/IP connections. Keep this limit in mind when designing your system. Prepare a tag list with exact data types like DINT[10] or REAL[5], and back up your project before making changes.
How to Configure a Produced Tag
Open the controller organizer in Studio 5000 and go to the "Controller Tags" folder. Right-click and select "New Tag" to create a produced tag. Give it a clear name, such as "Producer_Data_Array."
Set the "Type" to "Produced" and choose the correct data type. Enter a unique connection name for the consumer to reference. Define the RPI value—use 10 ms for fast motion control or 50 ms for less critical tasks.
Enable "Unicast" if only one consumer will use the tag. This saves network bandwidth. After creating the tag, download the changes to the controller and switch it to Run mode.
How to Configure a Consumed Tag
On the consumer PLC, create a new tag and set its type to "Consumed." Make sure the data type matches the producer's tag exactly. Enter the producer's IP address and the connection name you defined earlier.
Set the RPI on the consumer side to match or be a multiple of the producer's RPI. For example, if the producer uses 10 ms, set the consumer to 10 ms or 20 ms. Adjust the timeout value, usually four times the RPI, to detect communication failures.
Check the "Connection Status" system variable after configuration. A value of 0 means the connection is healthy. Values of 1 or 2 indicate errors. Download the changes and test the data exchange with a simple toggle routine.
Network Performance Tips
EtherNet/IP networks typically run at 100 Mbps or 1 Gbps. However, actual performance depends on the number of connections and their RPI settings. For example, ten produced tags at 10 ms each generate about 1,000 packets per second, which uses roughly 2-3% of a 100 Mbps network.
Use managed switches with IGMP snooping to control multicast traffic. Enable Quality of Service (QoS) to prioritize EtherNet/IP packets and reduce jitter. For high-speed applications, consider using separate VLANs to isolate critical data.
Calculate your network load with this formula: Total Bandwidth = (Number of Tags × Packet Size × 8) / RPI. Keep total usage below 60% to allow room for burst traffic and retransmissions.
Diagnosing and Fixing Issues
Use the GSV instruction to read the "FaultCode" and "Status" attributes of the Module object. A FaultCode of 16#0022 usually means a timeout caused by network congestion. Double-check the connection path in the consumed tag properties for typos.
Watch the controller's I/O LED. A flashing red light signals a communication fault. Use Wireshark with the EtherNet/IP dissector to capture and inspect packet exchanges. Look for "Forward Open" requests and responses to verify the handshake process.
If problems continue, increase the timeout value gradually. Test with a known working tag to determine if the issue is configuration-related or hardware-related. Also, check the controller's Event Log for fault records.
Optimizing for High-Speed Applications
For motion control or robotics, reduce the RPI to 2 ms and use a dedicated EtherNet/IP port. The L30ER's built-in port can handle up to eight nodes at this speed. Use arrays instead of individual tags to reduce connection overhead.
Trigger data production based on a periodic task to prevent jitter from irregular scan times. Consider using Change of State (COS) triggers to reduce traffic, but ensure the consumer can handle asynchronous updates.
Use the Task Monitor tool to measure actual update latencies. Adjust the system overhead time slice to give communication tasks higher priority if needed.
Safety and Redundancy Considerations
Add a heartbeat signal to your produced data to confirm the consumer is active. For example, include a counter that increments each cycle. If the consumer stops receiving updates, trigger a safe shutdown.
Use dual network connections with separate switches for redundancy. Configure the consumer to switch to a backup IP if the primary connection fails. Define a "Connection Lost" routine to set outputs to safe states.
For critical processes, consider using the Redundancy feature in Studio 5000. This requires extra hardware but provides zero-data-loss switching for controller pairs.
Example: L30ER to L33ER Data Exchange
In this example, an L30ER produces a DINT[10] array at 20 ms RPI to an L33ER. The L30ER uses IP 192.168.1.10, and the L33ER uses IP 192.168.1.30. Both run firmware 32.011 and Studio 5000 version 32.
The produced tag is called "Axis_Data" and stores position and velocity values. The consumed tag, "Received_Axis," matches this structure. After setup, the connection status shows 0, meaning success.
The L33ER reads the data every 20 ms, matching the producer's RPI. The measured jitter stays below 1 ms, which works well for most synchronization tasks. FactoryTalk View displays real-time values and connection health.
Final Checklist Before Go-Live
Before starting production, confirm that all tags are mapped correctly. Test each consumed tag by forcing a known value on the producer and reading it on the consumer. Use the Verify function in Studio 5000 to catch any consistency errors.
Power cycle both controllers to ensure settings persist. Monitor network traffic during peak loads with a protocol analyzer. Check that CPU usage stays below 75% on each controller for safety margins.
Document all RPI, timeout, and connection settings for future reference. Train maintenance staff on how to read diagnostic LEDs and GSV fault codes. Finally, simulate a network cable pull to confirm failover and alarm responses work correctly.
Common Use Cases
Produced/Consumed communication works well for coordinated motion control, real-time data sharing between packaging line PLCs, and synchronized material handling. It also supports distributed I/O systems where multiple controllers need the same sensor data.
For instance, in a bottling plant, an L30ER can send fill-level data to several downstream PLCs. This enables coordinated capping and labeling operations. In warehouse automation, position data from a central controller can be consumed by multiple robotic pickers for synchronized movement.
Solutions to Common Problems
When implementing produced/consumed tags, frequent issues include network congestion, data mismatches, and connection timeouts. Use managed switches with QoS to reduce congestion. Verify data structures offline to prevent mismatches. Set appropriate timeout values based on actual network conditions.
For larger systems, segment your network using VLANs and reduce RPI values for non-critical data. Regular network audits help spot bottlenecks before they affect production.
Frequently Asked Questions
1. How many produced tags can the 1769-L30ER support?
The 1769-L30ER supports up to 16 produced tags. Each tag can be consumed by multiple controllers, making it efficient for multicast data sharing.
2. What happens if the produced and consumed data types do not match?
A data type mismatch will cause a major fault and stop communication. Always verify that both tags have identical structures before deployment.
3. How can I troubleshoot connection errors?
Use the GSV instruction to read FaultCode and Status. A FaultCode of 16#0022 points to a timeout. Also, check the connection path and confirm both controllers are in Run mode.
4. Can I use produced/consumed tags across different PLC families?
Yes, as long as both controllers support EtherNet/IP producer/consumer features. You may need to adjust firmware compatibility settings and ensure data structures match.
5. What RPI should I use for motion control?
For motion control, an RPI of 2 ms is typical. This requires a dedicated network and careful bandwidth management to avoid congestion.
For inquiries or technical support, please contact:
Email: sales@nex-auto.com
Phone: +86 153 9242 9628
Partner: NexAuto Technology Limited
Check below popular items for more information in AutoNex Controls
