Hey everyone, I am currently working on establishing communication between a 1756-L72 (EN2TR) and a 1756-L82 (CPU port) using produced/consumed tags. I successfully added the L82 to the EN2TR tree during configuration and data exchange is functioning properly. However, when I attempted to add the L72 EN2TR to the L82 Ethernet tree, it was not automatically discovered. I manually added the EN2TR + L72, but encountered issues. The L82 created two new structures (In/Out) that were not present in the L72, and it seems that the data type is linked to an ENET module, which is unusual. I have included a screenshot of the fault code for reference. Any insights or suggestions on this issue are greatly appreciated.
It appears that you have a predefined consumed tag in place. If the size of your target tag in the alternate PLC is not the same, it may lead to errors. I recommend ensuring the IO configuration is set up correctly before establishing a consumed tag to avoid any potential confusion.
I tested with 1 DINT on each side before setting up the communication. The problem seems to be the L82 not recognizing the EN2TR / L72 in the other rack. It works in the opposite direction. I've verified the correct addresses, rack positions, and configurations. I even tried disabling/enabling keying to troubleshoot. It's puzzling why the L82 is creating structures when adding the EN2TR / L72 to the Ethernet tree, possibly due to differences with L8X. This seems to be contributing to the error. The fact remains that the L82 cannot automatically detect the EN2TR.
I recently added produce/consume tags between L82es and L72s and did not encounter any issues. The data structure shown is standard, and I have the identical tags on my setup. Are you certain that the rack size of 13 is accurate? Error 0109, as per the knowledge base, is typically caused by specifying an incorrect rack size.
I originally planned to use a size 13, but I may have to test a size 10 instead. The rack is currently 50 km away from me, as it was originally meant to fit in a space that couldn't accommodate 13 slots at home. I will give it a try regardless. Thank you. However, even before that, the L82 was unable to detect the EN2TR.
Hello Robert, I want to express my gratitude for your consistent support. Your help means a lot to me and I truly appreciate it. Wishing you a fantastic weekend! -Ben
It seems like the conflict might be stemming from your L82 creating new structures that the L72 doesn't recognize. If I understand correctly, the L82 is creating structures linked to an ENET module, which isn't standard practice for this kind of communication setup. This discrepancy might be what's causing the problems with your L72 connecting correctly. Have you tried removing these structures and seeing if the communication improves? Also, taking a look at the fault code you provided, I recommend updating the firmware of your L72, it could solve the problem if it's related to compatibility issues.
From what I understand, the issue could reside on the network identification or a discrepancy with regards to the firmware version. It's crucial to ensure that both the L72 and L82 EN2TR are compatible, it may be necessary to update one or both controllers’ firmware for optimal synchronization. Also, concerning the two new structures (In/Out), you could check and modify the EN2TR data type to correspond with the L72 settings. Remember, manual configurations may override certain default settings so it may not obviously align with the L72. If all else fails, you could reach out to Rockwell customer service, they have good technical support.
It sounds like you're on the right track but hitting some compatibility bumps along the way! The difference in structures could be due to the configuration settings or the firmware versions on your processors; sometimes, updates or mismatches can cause unexpected behaviors. I would recommend checking the documentation for both controllers to see if there are specific requirements or settings for inter-communication with the EN2TR module. Also, double-check that the produced/consumed tags are configured the same way on both ends, as even minor discrepancies can lead to such issues. If the fault code you mentioned indicates a specific error, that might give further clues, so it could be helpful to look up those codes as well. Good luck!
It sounds like you’re on the right track with your setup, but those discrepancies with the structures between the L72 and L82 can definitely be tricky. It might be worth double-checking the firmware versions on both controllers, as differences here can sometimes lead to mismatched data structures and functionality. Also, ensure that the produced/consumed tags are properly configured on both ends; sometimes a small misconfiguration can cause unexpected behaviors. Lastly, reviewing the communication settings for both Ethernet modules could shed some light on the issue. If you haven’t already, you might also consider checking Rockwell's knowledge base or forums for similar cases, as they can be a goldmine for troubleshooting these nuances. Good luck!
✅ 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 1756-L72 may not be automatically discovered due to configuration settings or network issues. Manually adding the 1756-L72 to the tree could help troubleshoot this issue.
Answer: Answer: The creation of new structures could be due to differences in configuration or data types between the two devices. It's important to ensure that the configurations are compatible for proper data exchange.
Answer: Answer: The data type linked to an ENET module may indicate a configuration mismatch or incorrect setup. Checking the configuration settings and ensuring compatibility between the devices can help resolve this issue.
Answer: Answer: Analyzing fault codes, checking configuration settings, verifying network connections, and ensuring proper setup of produced/consumed tags are essential steps in troubleshooting data exchange issues between the two devices.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.