You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To solve this knot, I figured out the following 4 steps that will be done in separate PRs to make them manageable:
Rename parameters for setting components in unconfigured and inactive state after CM is started. This feature does not break anything, and it should be back ported to humble as well. See: Enable setting of initial state in HW compoments #1046
Enable updates of /robot_description and components in URDF. The default behavior will be that if a new component exists it will be added to the system, but none component will be removed if it doesn't exist in URDF. User will be notified about this and they can manually remove the component.
The text was updated successfully, but these errors were encountered:
This description of issues is related to the following PRs:
robot_description
topic instead of parameter and don't crash on empty URDF 🦿 #940To solve this knot, I figured out the following 4 steps that will be done in separate PRs to make them manageable:
unconfigured
andinactive
state after CM is started. This feature does not break anything, and it should be back ported tohumble
as well. See: Enable setting of initial state in HW compoments #1046robot_description
topic instead of parameter and don't crash on empty URDF 🦿 #940).not_loaded
components after start. This needs some changes in RM (ABI breaking) that will separate some things better. Enable non-loaded hardware components after start of CM. #1049/robot_description
and components in URDF. The default behavior will be that if a new component exists it will be added to the system, but none component will be removed if it doesn't exist in URDF. User will be notified about this and they can manually remove the component.The text was updated successfully, but these errors were encountered: