jeff.page.rides wrote: ↑
Jan 12 2020 9:23pm
I'm just curious about the new version 850C_v0.6.2 and v0.51.0.
Does it have all the usability and safety features that were put into version v20 that was a huge improvement over v19 for me, disabled, and other riders?
No and I never tried v20 so it is even hard for me to say, I just saw and tried to understand the changes Buba did to v19.
Currently I am the only developer of this firmware.
For what I could understand, Buba did a great effort to make the firmware to work on the coast brake version of TSDZ2 you use. I really respect the work and I think has great value for users like you, I think it is really important and I wish to have that on current firmware. Unlike Buba, I don´t have resources nor motivation to go through the development, testing and maintenance of this feature -- I don´t use this feature for myself so why I would buy a specific motor, make a specific testing bench and keep it in my very little space home so I can develop, test and maintain this feature??
My motivation is to ride a lot, do new adventures, in this new Spring and Summer, with my family. My motivation is not to solve others issues but I am really happy to share with others what I developed for me.
My time is very small, for instance, I had high expectations for SW102 display but once the main developer stopped, the firmware is not updated anymore. I simple can´t do more development and I really want to enjoy riding with my family this new Spring and Summer of 2020 -- I will never trade that for solving the others issues -- on next 8 months I will have more days like this one instead of passing hours on the workshop developing and maintaining the firmware:
Rydon wrote: ↑
Jan 12 2020 9:45pm
Yes, I am a little confused as well. We have been waiting a long time for 850C on v20. v20 is the main development branch with lots of amazing features and capabilities. So now we have v50 based on v19? Did I read some time back that this is just temporary to add the torque calibration? When will we get back to v20 that we spent the summer testing and getting ready for release? Was v20 ever released? Will 850C ever work on it or will that only be v21? Sorry, but I am confused. Perhaps I missed some updates on this topic.
I hope you understand what is my motivations by reading the previous message -- it is mainly to solve my problems (not the others problems) but I am really happy to share with others what I developed for me.
While V20 was being developed by Buba I was developing and testing the torque sensor full calibration. In the end, I did understand that V20 emtb mode masks the torque sensor lack of linearity so both features could not be on the same firmware or at least I think all this changes need to be done in a slow, small step, way so we can well understand them. I think no one understand what the emtb values do really mean as also what previous torque sensor values did mean but now, it is very clear, it is kgs -- it is very easy for user to understand and validate that the torque sensor is working well, in full range. We now know (and we can validate and show to user, and improve) that there are TSDZ2 units on the market with good and less than good torque sensors, that can give bad user experience on ebikes -- I mean riding an ebike without torque sensor.
Also V20 had the new power modes that I saw confusion on users when that asked here for help to understand them - again, I think we need to go in small steps.
So, I diverged to a new firmware version starting from V19 and I was looking at V20 sources and changes Buba did from V19. I wish over time to bring the improvements from V20 that I value most. For instance, the lights being able to flash and the flash time being configurable -- I do not have lights controlled by TSDZ2 on my ebikes so I have no motivation to bring that feature, test it and maintain it. I really prefer to focus on a good motor control, like I did on V51 of motor firmware, by improving the motor current/power control resolution by 4x.
Uturn wrote: ↑
Jan 13 2020 3:26am
Also confusing to hear KT LCD3 can't be developed further due to lack of memory and to see the Bafang displays stuck on 0.19 and LCD 3 working on a beta 0.20.
Bafang display has instead advanced to currently V0.51 (read the wiki to be up to date), with torque sensor full calibration/linearization and 4x more sensitivity and, motor control with 4x more resolution.