Dashboard server report program as "Playing" after Safeguard Reset

Technical Questions Report a Bug
1

Hi,
we have an Universal Robots UR10 CB3 with the (current) lastest software release 3.15.3 build 10.6.223, but we encountered a problem with the dashboard server and the safeguard stop.

The safeguard stop is set to Autoreset.

If the project is stopped, the dashboard server with the command “programState” correctly report “STOPPED”, when the safeguard stop is activated and then restored, the dashboard server report “PLAYING”, but the project is not playing.

I think this is a bug and it causes us some problems.

Even if i send the “stop” command, the programState still say that the project is running, i attach a screenshot of the command sequence.

Safeguard Stop
Safeguard Stop1105×641 110 KB

Am i missing something?

Thanks

1 Like
2

I am also experiencing this issue. My programs were working fine until I added the safeguard stop.

3

A quick workaround could be to use “running”. The only downside of this is you can’t tell if the programmed is paused or not. It looks like the safeguard does not affect the PAUSED program state.

4

We have experienced the same issue.
Robot: UR10e
Software: 5.11.0.108249
After the safeguard is triggered we change the program state from paused to stopped. When the safeguard is reset, the dashboard server reports program running although it is actually still stopped.
This messed up our logic quite a bit. We have a temporary fix . Nevertheless this should be fixed.

5

We encountered the same issue. Since there has not been any updates on this post for several years I filed a new bug report with some additional details: Dashboard server erroneously reports program state "PLAYING" after safeguard stop

We noticed that the dashboard server command “running” reports the correct state, even though “programState” erroneously reports “PLAYING”. Furthermore, once a program has played an stopped, the dashboard server once again reports the correct state.

In our application, we run the robot in remote control and load/start/pause/stop programs through the dashboard server. We managed to make a workaround where:

  1. We use a combination of “programState” and “running” commands to get the actual program state.
  2. Whenever we load a program, we first load and run a dummy program that does nothing, before loading the desired program. This ensures that the robot is in a consistent state whenever a new program has been loaded.