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
The calibration procedure is to apply nominal current to the tendons, allow the user to calibrate the reference state of the robot, then save these motor positions to a file. So far, the file has been saved into the path /colcon_ws/src/helix_transmission/config/tendon_calib.yml, which is defined in the helix_transmission.config.yml file.
This might not be a good place to save the calibration, since the calibration is specific to the robot and shouldn't be synced to the repo. The files have been added to .gitignore, maybe this is sufficient.
The file can only be written if the helix_transmission source is mounted into the container. This is the case when launching with ./run.sh, but not with docker compose up ros-helix. The volume mounts could be added to the docker-compose.yml, but maybe this is not a good solution either, to keep the deployment container contained.
--> Need to understand the best solution for writing some robot specific config outside of the container.
The text was updated successfully, but these errors were encountered:
Note that the above appears to work for the set up on the Pi, however permissions still seem to be an issue running the containers on a workstation, ie the node in the container is unable to create a file inside ~/.config/helix if the config doesn't already exist.
The calibration procedure is to apply nominal current to the tendons, allow the user to calibrate the reference state of the robot, then save these motor positions to a file. So far, the file has been saved into the path
/colcon_ws/src/helix_transmission/config/tendon_calib.yml
, which is defined in thehelix_transmission.config.yml
file../run.sh
, but not withdocker compose up ros-helix
. The volume mounts could be added to the docker-compose.yml, but maybe this is not a good solution either, to keep the deployment container contained.--> Need to understand the best solution for writing some robot specific config outside of the container.
The text was updated successfully, but these errors were encountered: