2019-07-25, 02:17 AM
(This post was last modified: 2019-07-25, 02:20 AM by seandepagnier.)
All of the settings are stored on the controller itself. This is supposed to allow switching between controllers to work better, but I'm not sure it is handled in the best way, and it maybe needs improvement.
It seems the settings on the controller are bad and being reloaded.
Once pypilot is running, you should set the correct settings. It is lazy about writing these to the controller itself, so you might need to leave it running a while to ensure the eeprom gets updated. If you unplug the controller and wait until no controller is detected, then plug it again, it should reload all the settings from the controller.
So for example, if you change the max current to 6 amps, or any other servo setting, then unplug controller data cable, or remove power from controller right away (before eeprom can update), wait 10 seconds, then connect controller and wait for it to load again, it could reset the settings to the wrong values again and then you will know the controller had these settings.
I recently changed the format stored in eeprom of the controller. I'm not 100% sure which tinypilot image you have at this point, but this image should have fixed it:
https://pypilot.org/images/tinypilot_28062019.img.xz
Let me know if the controller is the issue, and if the above image helps and we will know what to do next. I agree this is a critical bug.
It seems the settings on the controller are bad and being reloaded.
Once pypilot is running, you should set the correct settings. It is lazy about writing these to the controller itself, so you might need to leave it running a while to ensure the eeprom gets updated. If you unplug the controller and wait until no controller is detected, then plug it again, it should reload all the settings from the controller.
So for example, if you change the max current to 6 amps, or any other servo setting, then unplug controller data cable, or remove power from controller right away (before eeprom can update), wait 10 seconds, then connect controller and wait for it to load again, it could reset the settings to the wrong values again and then you will know the controller had these settings.
I recently changed the format stored in eeprom of the controller. I'm not 100% sure which tinypilot image you have at this point, but this image should have fixed it:
https://pypilot.org/images/tinypilot_28062019.img.xz
Let me know if the controller is the issue, and if the above image helps and we will know what to do next. I agree this is a critical bug.