[ ] Anomaly report (something appears to not work correctly)
[x] Enhancement request (describe the enhancement being requested)
[ ] Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)
Descriptive summary
The VESC controller used in the C1T vehicle does not have an interface for activating or deactivating autonomous control, so the only way to toggle the robot_active field in the RobotEnabled messages is with a ROS service (or some other programmatic way).
This issue proposes adding a new service type for setting the robot_active field, similar to how SetEnableRobotic.srv is used for robot_enabled.
Carma version where this issue was discovered
Enhancement would be applied to noetic/develop.
Expected behavior
A successful implementation would introduce the SetActivateRobotic.srv service, which would be used to activate or deactivate a hardware interface controller module (e.g., the VESC on the C1T vehicle).
Types of Issue
Descriptive summary
The VESC controller used in the C1T vehicle does not have an interface for activating or deactivating autonomous control, so the only way to toggle the
robot_active
field in theRobotEnabled
messages is with a ROS service (or some other programmatic way).This issue proposes adding a new service type for setting the
robot_active
field, similar to howSetEnableRobotic.srv
is used forrobot_enabled
.Carma version where this issue was discovered
Enhancement would be applied to
noetic/develop
.Expected behavior
A successful implementation would introduce the
SetActivateRobotic.srv
service, which would be used to activate or deactivate a hardware interface controller module (e.g., the VESC on the C1T vehicle).Actual behavior
See Expected behavior above.
Steps to reproduce the actual behavior
Related work