2020-01-09, 08:05 PM
(This post was last modified: 2020-01-09, 08:05 PM by seandepagnier.)
When you upgraded, it upgraded the format that the data is stored in the controller. This means it did not read it, but used the values it had instead.
The confusion is there are still old values in the config which I didn't clean out. This is my fault and these values are ignored. You need to change "servo.max_slew_speed" now, and and "servo_speed_max" is no longer used.
A slew value of 2 is extremely low. This will be a very soft start. The usual range is 10-20. In any case, your motor must draw a lot of current?
There is a setting which disables reading the values from the motor controller. This is "servo.use_eeprom" you can change it to "False" If you do this and set the slew values in the config, they will be used and the motor controller will not be read. You might try this if you have trouble with the slew getting reverted.
If you edit pypilot.conf on the sdcard from a reader instead of ssh you don't have to execute sv d pypilot first.
I will make the slew settings available in the web interface for the next version.
The confusion is there are still old values in the config which I didn't clean out. This is my fault and these values are ignored. You need to change "servo.max_slew_speed" now, and and "servo_speed_max" is no longer used.
A slew value of 2 is extremely low. This will be a very soft start. The usual range is 10-20. In any case, your motor must draw a lot of current?
There is a setting which disables reading the values from the motor controller. This is "servo.use_eeprom" you can change it to "False" If you do this and set the slew values in the config, they will be used and the motor controller will not be read. You might try this if you have trouble with the slew getting reverted.
If you edit pypilot.conf on the sdcard from a reader instead of ssh you don't have to execute sv d pypilot first.
I will make the slew settings available in the web interface for the next version.