You are describing a defect which we addressed but I now must verify that it made it’s way into our main ubiquity_motor repository. Can you tell me if if you have a folder of /home/ubuntu/catkin_ws/src/ubiquity_motor?
If you do not have that folder or if it is not current that would explain this right away. This fix was within the last couple months so it does not exist on our images yet by default.
For getting current code you need your Pi to be able to access the internet to pull from our github. If you do not know how to setup to be on the internet see this:
Below are short instructions on use of our repository code which is a form of Beta software distribution for those who want mostly newest features.
If you have questions from below see this page in the middle: https://learn.ubiquityrobotics.com/updating
If the folder is not there that would explain what you describe.
- If the folder is there then cd into it and type ‘git pull’.
- If the folder is NOT there then cd to ~/catkin_ws/src and type this:
git clone https://github.com/UbiquityRobotics/ubiquity_motor
After whichever of the above you had to do then we must re-make the code:
sudo systemctl stop magni-base
Once the make completes reboot the robot: sudo shutdown -r now
I have looked in our repository and the fix seems to be there so above I fell will work