Dashboard client
Advertised Services
add_to_log (ur_dashboard_msgs/AddToLog)
Service to add a message to the robot’s log
brake_release (std_srvs/Trigger)
Service to release the brakes. If the robot is currently powered off, it will get powered on the fly.
clear_operational_mode (std_srvs/Trigger)
If this service is called the operational mode can again be changed from PolyScope, and the user password is enabled.
close_popup (std_srvs/Trigger)
Close a (non-safety) popup on the teach pendant.
close_safety_popup (std_srvs/Trigger)
Close a safety popup on the teach pendant.
connect (std_srvs/Trigger)
Service to reconnect to the dashboard server
get_loaded_program (ur_dashboard_msgs/GetLoadedProgram)
Load a robot installation from a file
get_robot_mode (ur_dashboard_msgs/GetRobotMode)
Service to query the current robot mode
get_safety_mode (ur_dashboard_msgs/GetSafetyMode)
Service to query the current safety mode
load_installation (ur_dashboard_msgs/Load)
Load a robot installation from a file
load_program (ur_dashboard_msgs/Load)
Load a robot program from a file
pause (std_srvs/Trigger)
Pause a running program.
play (std_srvs/Trigger)
Start execution of a previously loaded program
popup (ur_dashboard_msgs/Popup)
Service to show a popup on the UR Teach pendant.
power_off (std_srvs/Trigger)
Power off the robot motors
power_on (std_srvs/Trigger)
Power on the robot motors. To fully start the robot, call ‘brake_release’ afterwards.
program_running (ur_dashboard_msgs/IsProgramRunning)
Query whether there is currently a program running
program_saved (ur_dashboard_msgs/IsProgramSaved)
Query whether the current program is saved
program_state (ur_dashboard_msgs/GetProgramState)
Service to query the current program state
quit (ur_dashboard_msgs/GetLoadedProgram)
Disconnect from the dashboard service.
raw_request (ur_dashboard_msgs/RawRequest)
General purpose service to send arbitrary messages to the dashboard server
restart_safety (std_srvs/Trigger)
Used when robot gets a safety fault or violation to restart the safety. After safety has been rebooted the robot will be in Power Off. NOTE: You should always ensure it is okay to restart the system. It is highly recommended to check the error log before using this command (either via PolyScope or e.g. ssh connection).
shutdown (std_srvs/Trigger)
Shutdown the robot controller
stop (std_srvs/Trigger)
Stop program execution on the robot
unlock_protective_stop (std_srvs/Trigger)
Dismiss a protective stop to continue robot movements. NOTE: It is the responsibility of the user to ensure the cause of the protective stop is resolved before calling this service.
Parameters
receive_timeout (Required)
Timeout (in seconds, double) after which a call to the dashboard server will be considered failure if no answer has been received.
robot_ip (Required)
The IP address under which the robot is reachable.