ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
As you can see in the documentation (here), the dashboard/program_state
is not of type std_srvs/Trigger
, but type ur_dashboard_msgs/GetProgramState.
You cannot call that service with a std_srvs/TriggerRequest
, and the MD5 mismatch error is correct.
You can verify this by running rosservice info /ur_hardware_interface/dashboard/program_state
.
2 | No.2 Revision |
As you can see in the documentation (here), the dashboard/program_state
is not of type std_srvs/Trigger
, but type ur_dashboard_msgs/GetProgramState.
You cannot call that service with a std_srvs/TriggerRequest
, and the MD5 mismatch error is correct.
You can verify this by running rosservice info /ur_hardware_interface/dashboard/program_state
.
Many services offered by that node actually use types other than Trigger
, see again the documentation.
3 | No.3 Revision |
As you can see in the documentation (here), the dashboard/program_state
service is not of type std_srvs/Trigger
, but type ur_dashboard_msgs/GetProgramState.
You cannot call that service with a std_srvs/TriggerRequest
, and the MD5 mismatch error is correct.
You can verify this by running rosservice info /ur_hardware_interface/dashboard/program_state
.
Many services offered by that node actually use types other than Trigger
, see again the documentation.
4 | No.4 Revision |
As you can see in the documentation (here), the dashboard/program_state
service is not of type std_srvs/Trigger
, but type ur_dashboard_msgs/GetProgramState.
You cannot call that service with a std_srvs/TriggerRequest
, and the MD5 mismatch error is correct.
You can verify this by running rosservice
info type /ur_hardware_interface/dashboard/program_state. (or rosservice info ...
for more information).
Many services offered by that node actually use types other than Trigger
, see again the documentation.