casainho said:
eyebyesickle said:
casainho said:
Hmmm, others are saying the controller is just the same. Can you please show evidence that is different??
No sorry, you'll have to take my word for it on this one... I didn't take pictures etc but confirmed visually and through reprogramming that there were differences... I'm quite certain.
I am asking this because Rydon is trying to test our firmware on that version and says it probably has the same controller. If it is different, well, then it will not work...
TongSheng actually puts a "BK" in the controller part number of the coaster brake version of the motor just like they put a "BK" in the part number on the outside of the case. I assume "BK" means "coaster BraKe".
The stock firmware is different on the coaster brake version of the motor. The motor stops instantly when you stop pedaling on the coaster brake version but has a slight delay before stopping on the regular version. I once put a regular controller on a coaster brake motor and when you would stop pedaling the pedals would jump forward for a split second - not pleasant.
I believe the controller hardware is the same except that I learned with version 16 of the open source firmware that it has a constant voltage on the throttle even though the throttle is never hooked up on coaster brake motors. When reading it out from the LCD3 display the ADC throttle is 143 and the throttle is 189. Because of this with version 16 the motor would spin continuously as soon as you powered it up.
This problem was fixed in version 18.2 where the throttle is disabled by default. With this version of the firmware, the coaster brake motors work great with one exception - backward resistance. The backward resistance actually prevents the coaster brake from being applied whenever the motor is on. I have tried version 19 beta3 which fixes the backward resistance but now with v19 beta3 the motor never applies power when pedaling.
I am hoping someone will have some ideas on this. I will reflash it with 18.2 to make sure it still works with that level of firmware just to make sure something else hasn't gone wrong.