Have you encountered any challenges while using MODBUS/TCP with Beckhoff controllers, especially on TC3? I am currently facing difficulties communicating with an Epson robot using a CX8190. Despite my efforts, I keep receiving error code 1861 from the TC function blocks, indicating a timeout issue. This error message suggests that the remote terminal is not responding within the specified ADS timeout, possibly due to incorrect route settings. If you have experienced a similar issue or have prior experience with TC3 MODBUS/TCP communication, I would appreciate any insights. I have successfully tested communication between a PC & PLC, as well as between a PC & Epson, without any complications.
I have extensive experience using Modbus on Beckhoff controllers (TC3) and have found it to be highly reliable. Although it can be a bit tricky to configure initially, I have never encountered any issues once it's up and running. Are you utilizing the CX as the Modbus master or slave device? When you mention testing communication, are you referring to testing Modbus specifically or overall Ethernet communication? Is the CX, robot, and PC all connected to the same network?
When troubleshooting connectivity issues between a CX master, modbus tcp test programs have been utilized to pinpoint the source of the problem. Collaborating with Epson and Beckhoff support teams, Beckhoff suspects the problem lies with the robot, while Epson is unable to identify any issues. All devices, including the PLC and robot, are on the same network with the PLC at 192.168.1.10 and the robot at 192.168.1.11.
Are you currently utilizing the sample code provided by Beckhoff? Have you ensured that the Tc2_ModbusSrv library is properly installed? Additionally, have you installed the TF6250 package on your CX? (Note: The TF6250 package must be installed separately from TwinCAT)
Experiencing Connectivity Issues Between Twincat 3 and Epson SCARA via Modbus TCP? Need Help Troubleshooting the Communication Problem? Look no further! Let's address the issue of intermittent communication between Twincat 3 and Epson SCARA via Modbus TCP. Running FB_MBReadRegs and monitoring with Wireshark initially works, but then fails to communicate until PLC and robot are restarted. Seeking assistance to solve this ongoing challenge.
If you're encountering a similar error, consider disabling the firewall on your destination PC to allow modbus TCP to function properly. This simple solution can help resolve connectivity issues and ensure smooth data transmission.
I had a similar issue with a Beckhoff controller not too long ago. I spent forever troubleshooting and finally discovered the problem was actually rather simple - a mismatch of data types between my controller and the purpose device, in my case, a KUKA robot. It resulted in delayed responses, similar to your timeout issue. I'm not completely familiar with Epson robots, but make sure that both devices are using the same type and size of data. Also, try increasing the ADS timeout, sometimes Epson robots need more time to respond. Good luck!
I've had a similar issue before. In my case, the problem was indeed tied to incorrect routing and IP settings. I had to double check my network configuration and TCP/IP settings. Make sure the settings of the Beckhoff CX8190 PLC align with those of the Epson robot and the subnet mask as well. Do verify if the ADS routes are established correctly in both devices. Also, consider increasing the ADS timeout if the robot needs more time to respond. Hope this helps.
I've encountered a similar issue in the past with the TC3 MODBUS/TCP communication, and resolving it can definitely be a bit tricky. A contributing factor could indeed be the routing settings, but I would also advise you to double-check your IP settings as well. Additionally, ensure that you've correctly mapped your inputs and outputs in the TC3 I/O system and that there's no overlap which could potentially cause more confusion. Don't forget to monitor your connection parameters too - things like Data Length, Word Swap, Byte Swap, Slave Address etc are just as critical in this process. Finally, try increasing the Timeout values slightly because sometimes a very small value can cause an unnecessary timeout trigger. Let me know if these tips help out!
✅ 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: Error code 1861 on TC3 typically indicates a timeout issue, suggesting that the remote terminal is not responding within the specified ADS timeout. This could be related to incorrect route settings.
Answer: Answer: To troubleshoot error code 1861, check the route settings to ensure they are configured correctly for the communication between the Beckhoff controller and the Epson robot. Verify that the remote terminal is configured properly and responding within the specified ADS timeout.
Answer: Answer: Common challenges when working with MODBUS/TCP on Beckhoff controllers like TC3 may include configuring route settings incorrectly, experiencing timeout issues like error code 1861, or facing difficulties with communication between different devices.
Answer: Answer: Prior experience with TC3 MODBUS/TCP communication can provide valuable insights into troubleshooting techniques, route setting configurations, and resolving timeout issues like error code 1861. Sharing knowledge and best practices can help in efficiently resolving communication challenges.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.