Dashboard non-responsive when EMO pressed

Technical Questions Robot Communication
1

Hello,

We are building a custom device that operates without a teach pendant, using the Dashboard Server and I/O interface to command the robot remotely.

We have observed that when the Emergency Stop (E-Stop) button is pressed, all network communication with the controller is lost — including ping, port 29999 (Dashboard), port 30001, and port 30002. Furthermore, communication cannot be re-established while the E-Stop remains active.

This is unexpected behavior. The UR manual lists “ROBOT_EMERGENCY_STOP” as a valid response to the safetystatus Dashboard command, which implies the Dashboard Server is intended to remain responsive during an E-Stop condition.

Our setup:

  • PC and robot on the same LAN switch
  • Port 29999, 30001, 30002 Confirmed reachable and fully functional before E-Stop is pressed
  • All ports and ping fail immediately when E-Stop is pressed
  • Network recovers only after E-Stop is released and controller restarts
  • image
    image486×320 26.7 KB

Our questions:

  1. Is complete network loss during E-Stop expected behavior, or does it indicate a configuration or hardware issue?
  2. Is there a setting that keeps the controller network alive during an E-Stop?

Thank you very much!

2

image
image1413×965 84.5 KB

In the release note of Polyscope 10.12, they state that with their BETA logic program, it is made possible to maintain communication after something like emergency stop.

Therefore, maybe it is true that normally the communication is lost, but i am unsure.
I have never experienced it with PROFINET, but I have no experience with the way you are doing it.

3

Hello Lasse,

Thank you for the information. I would like to add an observation I just made.

When I use the EMO button on the teach pendant, the Dashboard connection stays up and works as expected. When I send “safetystatus”, it returns “ROBOT_EMERGENCY_STOP”.

image
image656×417 4.96 KB

The external emergency stop button I referred to is connected to EI0 and EI1 on the controller, as described in the manual. When I trigger this external E-stop, all communication (Dashboard, 29999, etc.) drops.

image
image349×196 38 KB

Should the emergency stop button be wired differently, or is there an additional configuration I might have missed?

I appreciate any guidance.