Good morning! I am experiencing issues with a Produced Consumed setup between an Allen Bradley L71 V30.11 and an L33ER V30.14 PLC. Despite setting it up multiple times with the same 88-byte UDT, I encountered a connection error when configuring both projects to communicate with each other. After deleting and recreating processors and tags, I still saw yellow triangles indicating errors on the I/O trees. Upon further investigation, I tried setting up the controllers to communicate without the prod/con tag, which resolved the errors. However, when I added a single produced tag to the L71 and set the L33ER as the consumer, a connection error (#16031e Cannot Consume Tag) appeared on the L33ER processor. Interestingly, the connection intermittently established and dropped, allowing data transfer but with frequent errors. I have checked the module definitions and settings on both PLCs, including enabling "Allow Consumed Tags To Use RPI Provider by Producer" on the L33ER. Despite my experience with similar setups, this issue is new to me. Any insights or advice would be greatly appreciated. Thank you.
I recently established a seamless Producer Consumer connection between two L33ER controllers in a plant. This success reaffirms that the NATR module is not the barrier to this functionality. However, there appears to be a compatibility issue between the L71 and L33ER controllers that doesn't exist when using two Compact Processors. This discovery highlights the importance of controller compatibility in industrial setups.
Have you checked the compatibility matrix on a website? It might be worth investigating if there is a firmware issue with your current version. It appears that the problem stems from your RPI settings being overly aggressive. Consider reducing the RPI to around 200 milliseconds. Are you using the same brand of switches as usual, or have you switched to a different one? It is possible that there is a setting on the switch that needs to be adjusted. Have you examined the utilization percentage of your ethernet connection? Open any web browser, enter the IP address, and access the module diagnostics. The percentage of utilization during peak times should ideally be below 50%. If it exceeds this figure, it may indicate that the RPI setting is too low.
Jim3846 mentioned checking the compatibility matrix on a website to address potential firmware issues causing problems with an overly aggressive RPI setting. It's important to ensure that the % utilization on the ethernet connection is below 50% during peak times to avoid issues. After following the advice and reviewing the Compatibility Matrix, it appears that there are no major obstacles preventing a smoother operation. The L33ER's I/O Comms Utilization is at 13.2%, with other devices like VFDs communicating with the processor. The L71's web page shows various details, but no %Comms Utilization like the L33 WebPage. In terms of network setup, all processors are connected to local unmanaged switches, with a connection between processors sometimes becoming unstable. Active connections on both processors' web pages fluctuate periodically. Switches used are Cisco-managed and have pre-configured Industrial ports. Adjusting the RPI settings may help improve performance, but due to time constraints, further troubleshooting will be done during specific hours. Assistance from IT may be needed if issues persist. Thank you for your assistance and support!
I have a suspicion that one of the controllers is experiencing a shortage of connections. Could it be that two users are simultaneously attempting to connect to the same tagged product? According to KB QA469, the error message (16#031e) indicates that another PLC is already utilizing that tag.
Check the properties of the controller for a connection display on the capacity tab. Take a look at the ethernet nodes as mentioned by DMroeder. The CompactLogix definitely has this feature, and the L71 may have up to 120 connections. Additionally, don't forget to check the Ethernet card in the browser for connections and packet sizes. Pay attention to the Produce tag connection to monitor the Max consumers setting. The IO config tree and browser interface are also useful for checking connection information.
Sounds like a pretty vexing situation, but I might have a clue for you. Firstly, have you checked compatibility between the two PLC versions? Although usually backwards compatible, sometimes certain features can cause issues when paired with older versions. You might want to update the firmware of the older one, just for consistency. Also, ensure the data type matches in both PLCs exactly, including a check for user-defined data types (UDTs). I remember having problems with UDTs not matching exactly, which made the consumed produced setup fail. Internet connection variability might also be the cause for intermittent communication, it would be worth checking the internet stability at your location. If you've already done these, I'd suggest contacting the technical support. With such intricate error patterns, it might be a glitch in the system that needs a deeper dive. Hope this helps and good luck!
Hi there! I've also encountered similar issues with Produced/Consumed tags between different PLCs in Rockwell Automation suite. Having dealt with the error code 16#031e, it seems to be related to a timing mismatch between the producer and consumer tag update rates. In that case, it might help if you ensure that the RPI (Requested Packet Interval) specified in the L33ER consumer tag matches or is greater than the RPI of the L71 producer tag. Another aspect to check could be making sure you're not exceeding the controller connection capacity of either processor. Lastly, while it's a long shot, verify if firmware versions on both PLCs are compatible. Hope this helps!
Good morning! It sounds like you're going through quite the troubleshooting journey with your PLC setup. One thing to check is the communications path and ensure that both controllers are on the same subnet since issues can arise if there are any inconsistencies in IP addressing. Additionally, have you verified that the Produced/Consumed tags are configured with the same data type and size? It’s also worth checking the connection settings for any potential discrepancies—sometimes a simple mismatch can throw things off. Lastly, consider reviewing any firmware updates or patches for both PLCs, as they might resolve underlying connectivity issues. Good luck, and I hope you get it sorted out!
Hey there! It sounds like you’re really diving deep into this setup challenge. The #16031e error is often related to network or configuration issues, but since you're able to establish a connection intermittently, it suggests something might be off with the tag definitions or RPI settings, especially since you mentioned creating and deleting them. Have you verified the Ethernet connections and ensured there’s no IP address conflict? Also, double-check that both PLCs are on the same network segment and that the produced tag settings match exactly on both sides. Sometimes subtle mismatches can trip things up. Good luck, and I hope you get it resolved soon!
Good morning! It sounds like you’ve done a thorough job troubleshooting so far. One thing to double-check is the UDT size and alignment in both controllers – sometimes even a small discrepancy can cause issues like the connection error you're seeing. Also, ensure that the firmware versions are compatible across both PLCs, as subtle differences can create unforeseen issues in communication. If the intermittent connection persists, you might want to try adjusting the RPI settings for the produced tag, or even recreating the tag groups to clear out any hidden issues. Good luck, and I hope it all gets sorted out soon!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The connection error could be due to various factors such as incorrect configuration settings, mismatched UDT sizes, or communication protocol issues. Troubleshooting steps may include verifying settings, checking for compatibility, and ensuring proper configuration of prod/con tags.
Answer: Answer: To address intermittent connection problems, consider checking network stability, reviewing tag configurations, adjusting RPI settings, and ensuring proper synchronization between the producer and consumer PLCs.
Answer: Answer: Yellow triangles on the I/O trees typically signal configuration or communication errors. Check settings, verify tag definitions, review network configurations, and ensure consistency in the setup between the L71 and L33ER PLCs to resolve these errors.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.