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
ROSEE is ready to use with this new feature, I have also tested it a bit.
Problem is that the joint_state_publisher does not read srdf, thus it is not aware of possible initial joint position different from 0.
Possible solutions are:
Use a yaml file where the zeros of the joint are written. This is the standard way documented for joint state pub. The problem here is to have this additional duplicated file, and we need it for each end-effector, even if the joint position are all 0 (because we have to indicate it in the launch file, and error is thrown if the file does not exists).
Modify joint_state_pub such that it reads srdf
Send a init command from ROSEE after parsing the robot with its initial joints positions. Not really coherent though, ROSEE should always pass through the filter and the hal to send robot commands.
Send a init command from a "initialization ros node", then shutdown it and run rosee.
Similar problem happens also when gazebo (and not anymore joint state pub) is used, but it should be easier to set initial pos in gazebo
UPDATE: also take care that setToDefault position passive joint rosee method should take this srdf updates, if implemented
No description provided.
The text was updated successfully, but these errors were encountered: