Open philrich opened 4 months ago
Strange, I checked and didn't find a cause for this. Also because this part of code is in common with 860C. The only change I made regarding SW102, I added some missing parameters. Maybe the data memory is at its limit, unfortunately I don't have an SW102 to test. You should do a test, leave version 20.1C.5-beta-1 on the motor controller, and put version 20.1C.4-update-4 on the display, it should work. Then check if the parameters you mentioned are saved.
I get it, you probably have "Coaster brake" enabled. For security reasons, if it is enabled, there are features that are disabled when the display is turned on. They are: Throttle mode, Thottle on street mode, Cruise mode, Walk assist and Startup assist. They can be enabled at every startup, so it must be a deliberate choice. The user should be aware that these features, used with coaster brake motors, are dangerous. If you don't have a motor with coaster brake, disable "Coaster brake".
Ahh. cool. That fixed it, thanks! In the docs there is not much info on the behavior you described. "Coaster brake" enabled by default? I am pretty sure i never touched this setting and in the last Version i used (20.1C.4.something) i did not experience this behavior.
It is a change added in the latest version, it is mentioned in the changelog.txt file.
Unfortunately I haven't had time to update the manual yet.
In previous versions "Coaster brake" was enabled by default because there was no menu item to set it.
I recently upgraded my TSDZ2B & Sw102 Display from Version 20.1C.4.? (middle of 2022) to 20.1C.5-beta-1. Since then I'm unable to save some parameters to flash. Ie when trying to enable the throttle, it only works until I turn off the display. After powering on the setting is reset to disabled state. Other settings which are not saved: Walk assistant, street mod settings, etc. startboost / startup as. But I can change smoothramp or smoothstart and it is preserved.