Software update 5.25.0 affected my Ethernet/IP communication

Technical Questions Robot Communication
1

I updated a UR3e that was already in operation so I could run urmagic_data_capture_v0_6_13 and perform an application diagnostic (this was the version I had downloaded at the time, 5.25.0). However, when I reset the cell in the PLC (using Ethernet/IP), it detects that the robot is in an emergency stop state—RES (Is robot emergency stopped). This happens even though the robot is operating normally and using other signals with this protocol.

I have declared play, pause, and stop program signals, and they work correctly, but when monitoring the robot’s status, it does not change from the RES state (Is robot emergency stopped).

I’ve already restarted the system a couple of times after the update, and it’s still the same.

Is there an explanation for this, or what procedure do you recommend resetting the value of that signal?

image
image720×1280 183 KB

image
image406×615 70.8 KB

image
image720×1280 158 KB

2

Your first screenshot of the PLC program. I’m not familiar with that brand, but are you looking at that “RES” block in green? Is that not just a “Reset” block for another internal coil?

3

image
image1920×3413 1.07 MB

AB CCW: The value (res) should be (pr – program running), since the robot is operating normally.

We believe this could be a SW bug. We also noticed that after installing the update, the robot did not start automatically when set to remote mode. The setup config (in the Installation tab) were not being applied. To resolve this, we had to reconfirm and reassign the I/O boolean config as they were before performing the update

4

I’m not familiar with your PLC, but can you make a visualisation table to monitor every information from the robot ? You could see if its a problem from the PLC side or robot side.