I am in the process of configuring a WAGO 750-8212 as a remote I/O device for an Allen Bradley CompactLogix 1769-L33ERM. After reaching out to WAGO for assistance, they provided me with the necessary EDS files and AOIs. The device is now connected to the network and accessible from the processor, but I am experiencing frequent timeouts. Upon reviewing the EDS file, I noticed it should be configured for multicast, which I have updated accordingly. However, the connection continues to timeout instantly. Here are some key details: - PLC model: Allen Bradley 1769-L33ERM - WAGO RIO device: 750-8212 - EDS File: WagoAppEtherNetIP_Adapter.eds - Ping response time: 1ms for PLC, 1ms for WAGO - EDS settings: Exclusive Owner, Multicast, Cyclic Any assistance in resolving this issue would be greatly appreciated. I am struggling to find a solution and the deadline for this project was yesterday.
Are you experiencing timeouts on your configured connection? Typically, a connection timeout occurs when the PLC waits for 4 times the RPI duration without receiving any data from the adapter. It's important to check for the specific error code to determine if it's a timeout issue or a size mismatch, which is common with modular I/O devices. One solution is to completely remove the I/O connection, export the program to *.L5K format, and then create a new program from that file. This process helps eliminate any outdated or corrupted definitions in the I/O tree. Regarding the Wago 750-8212 PFC200 controller, it is not a modular I/O base, correct? Is it operating CoDeSys and the EtherNet/IP Adapter object? Make sure to define the data type and connection size for optimal performance.
I appreciate the thorough response! I am encountering the 'Connection Request Timed Out' error code, but am unable to view the specifics as I am not connected to the processor. My RPI is configured at 100ms, with a 1ms ping response from the device. The PFC200 controller equipped with Codesys by Wago is said to have EtherNet/IP capabilities, although there seems to be no option to enable or disable it on their Web Based Management platform. The issue may lie with the connection size, which is configured in the IO connection within the AB processor. I will investigate further in the morning and provide an update.
Is it possible to use the Wago controller as a coupler, as mentioned by Wago representatives?
Although I did not personally specify the requirements, I made a specific request for the eds files necessary to utilize the 1769-L33ERM model device. The response I received included a link to download all necessary eds files for the WagoAppEtherNetIP_Adapter.eds file, which is recommended for the 750-8212 RIO device.
Indeed, it seems that WAGO Devices can function as EtherNet/IP Slaves. Setting it up may not be straightforward, as a separate controller is required to act as the master and establish a virtual connection between the master and slave device. Additionally, some may wonder why not opt for more affordable Rockwell products like the 1734-AENT instead.
It sounds like you're in a tough spot with the timeouts. Since you've already configured the EDS file for multicast and confirmed your ping times, have you checked the network settings for any potential bottlenecks or conflicts—like IP address conflicts or subnet issues? Also, consider reviewing the AOI settings to ensure they align with the cyclic and exclusive owner setup. Sometimes, adjusting the communication parameters for the connection, like changing the connection timeout settings or even testing with unicast, can make a difference too. Hang in there; these issues can be tricky!
It sounds like you're definitely in a tricky spot! Since you've already checked the EDS file and updated to multicast, it might be worth looking into the network configuration. Make sure that multicast traffic is being allowed and not being blocked by any switches or routers in between. Additionally, check if there's a mismatch in the connection settings on the CompactLogix side; sometimes, adjusting the packet size or ensuring that the requested connection parameters match exactly can resolve timeout issues. If you haven’t already, trying a different Ethernet cable or port could also rule out physical connection problems. Hang in there—it's often the little settings that trip us up!
âś… 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: Timeout issues can be caused by various factors such as incorrect network configurations, communication settings mismatch, or hardware compatibility issues. Ensure that the EDS file is correctly configured, network settings match the requirements, and the devices are compatible.
Answer: If updating the EDS file did not resolve the issue, consider checking network connectivity, verifying IP addresses and subnet masks, ensuring proper wiring, and confirming that the devices are properly powered and grounded.
Answer: Start by checking the network settings on both devices, verifying the communication protocols, reviewing error logs for more specific information, testing the connection with different configurations, and seeking assistance from the manufacturers' technical support teams if needed.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.