The nice thing is that all the machinery of defining and reading configuration files and modifying structure is already implemented, via stictionUp/stiction_up/stiction_up_val and stictionDown/stiction_down/stiction_down_val parameters, see for example:
Furthermore, we are already back-compatible by default, as all those parameters are defined to 0 in most configuration files! So we are just left with the fun part:
[ ] Make sure the parameters from the configuration files are propagated down to the motor control board
Follow up of https://github.com/robotology/icub-firmware/issues/67 .
The nice thing is that all the machinery of defining and reading configuration files and modifying structure is already implemented, via
stictionUp
/stiction_up
/stiction_up_val
andstictionDown
/stiction_down
/stiction_down_val
parameters, see for example:Furthermore, we are already back-compatible by default, as all those parameters are defined to
0
in most configuration files! So we are just left with the fun part: