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
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.
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”.
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.
After tracing all the cables, we discovered an issue with our breakout PCB: the El1 was not properly connected to the EMO switch. Once we connected the EMO directly, the dashboard functioned as expected.
Appreciate everyone who took a look and gave this some thought.
