As discussed in #149 the upgrade firmware script has still not been fully ported to py3. This is the only reason why we are still installing python2 on all noetic images. Now because upgrade_firmware.py doesnt actually use ros lib we can still call it using rosrun, we just need to indicate that this is py2 executable as was done here. Previously you had to run with
python2 ~/catkin_ws/src/ubiquity_motor/scripts/upgrade_firmware.py --file /home/ubuntu/catkin_ws/src/ubiquity_motor/firmware/v40_20201209_enc.cyacd
(you also HAD to have the ubiquity_motor cloned - installing throuhg apt did not work)
After this merge, the ubiquity_motor noetic-devel branch was also included into the process of getting updated on the latest noetic apt: https://github.com/ros/rosdistro/pull/32424
As discussed in #149 the upgrade firmware script has still not been fully ported to py3. This is the only reason why we are still installing python2 on all noetic images. Now because upgrade_firmware.py doesnt actually use ros lib we can still call it using rosrun, we just need to indicate that this is py2 executable as was done here. Previously you had to run with
python2 ~/catkin_ws/src/ubiquity_motor/scripts/upgrade_firmware.py --file /home/ubuntu/catkin_ws/src/ubiquity_motor/firmware/v40_20201209_enc.cyacd
(you also HAD to have the ubiquity_motor cloned - installing throuhg apt did not work)with this fix you can trigger update with
rosrun ubiquity_motor upgrade_firmware.py --file v43_20210829_enc.cyacd
and it all works also installing ubiquity_motor through apt.
Testing on rpi, noetic image:
and the firmware should be updated