TSDZ8 OSF (open source firmware)

Hi everyone !

I'm totally new on this forum, i find it while searching on OSF. I daily use an eBike with a torque sensor (Shimano E6100).

I'm currently buying parts for my new cargo bike ("Le Petit Porteur" frame) and i don't want a Bafang because i really like the torque sensor feeling on my actual bike.

So TSDZ8 seems the way to go, and all your efforts to improve the firmware are awesome ! I want to participate to test / improve. I'm not developer but works in IT.

I read the previous posts and 3 threads about OSF on TSDZ8, but want a last advise before buying the motor :

What is the best screen to buy ? I was looking for the EKD01, recommended by the seller and cheap, but from what i read it looks like the 860C is more versatile for testing / debug of OSF fw ?

Is this repo the good one for flashing the display and use it with an OSF TSDZ8 ? GitHub - emmebrusa/TSDZ2-Smart-EBike-860C: TSDZ2 Open Source Firmware adapted to 860C display

Thanks for your advises

From my point point of view, 860C is much better because you can easily change directly all config parameters. You can also display more data provided by the controller.
I presume the link you provided for the 860C firmware is the good on but I am not 100% sure because the 860C I got was already flashed with the required firmware.
 
Hi!
I'd also like some help. Can someone point me to a tutorial for flashing the 860c? I've got a programming kit, but when I want to select the firmware, the only version of APT burn I've been able to find (here) doesn't allow me to select an .hex file (see image)...
I'd also like to know if I can upload any of the relaeses in emmebrusa folder.

I've looked in the different threads and wikis but it seems to me I'm falling in a labyrinth...

Thanks in advance for your help :)
 

Attachments

  • aptburn.png
    aptburn.png
    149.9 KB · Views: 7
Hi!
I'd also like some help. Can someone point me to a tutorial for flashing the 860c? I've got a programming kit, but when I want to select the firmware, the only version of APT burn I've been able to find (here) doesn't allow me to select an .hex file (see image)...
I'd also like to know if I can upload any of the relaeses in emmebrusa folder.

I've looked in the different threads and wikis but it seems to me I'm falling in a labyrinth...

Thanks in advance for your help :)
Did you see this link
 
Did you see this link
No, thanks, that was what I was looking for. The link in point 2 is dead, but I've found this other (dead) link that allowed me to flash it.

But it didn't work, I think I have briked the dislay. Here is the story:

I have ridden like 600km on a cargo bike with a TSDZ8 with original FW and a 850c display. I'm quite pleased with it, but the throttle we use to launch the bike from stop when loaded needs more progressivity. Also, the torque sensor seems a bit weak and we have to push quite hard to get decent power (and that is a problem for my wife). So, as my other bike is powered by a OSF tsdz2b, I ordered some programming cables and a (already flashed) 860c display.
I tried the 1_20 version, but I couldn't manage to get enough assist (while I played a lot with all torque ADC parameters etc. ) and the motor was jerking a bit on low power. So I flashed ebikestuff test3.0 FW to try if it was better but made the mistake to do that without having unplugged the battery (I'm used to the tsdz2 that needs to be battery powered).
Then the 860c display stays stuck on the start screen ("waiting for tsdz2" displayed in the bottom).
I flashed the original firmware back, put the 850c back in place and it works.
So the problem comes from the 860c, and that's why I was trying to flash the OSF back on it (without much hope, but who knows). The FW update worked sucessfully, but I always get the same start screen with a "waiting for tsdz2" message (followed by a "brake or com error"). Kaput !
Not a problem, I'll stay with the 850c and orignal FW while you guys go on with developping this OSF.
Thanks a lot for the good work, hoping to be able to try this again soon :)
 
Last edited:
No, thanks, that was what I was looking for. The link in point 2 is dead, but I've found this other (dead) link that allowed me to flash it.

But it didn't work, I think I have briked the dislay. Here is the story:

I have ridden like 600km on a cargo bike with a TSDZ8 with original FW and a 850c display. I'm quite pleased with it, but the throttle we use to launch the bike from stop when loaded needs more progressivity. Also, the torque sensor seems a bit weak and we have to push quite hard to get decent power (and that is a problem for my wife). So, as my other bike is powered by a OSF tsdz2b, I ordered some programming cables and a (already flashed) 860c display.
I tried the 1_20 version, but I couldn't manage to get enough assist (while I played a lot with all torque ADC parameters etc. ) and the motor was jerking a bit on low power. So I flashed ebikestuff test3.0 FW to try if it was better but made the mistake to do that without having unplugged the battery (I'm used to the tsdz2 that needs to be battery powered).
Then the 860c display stays stuck on the start screen ("waiting for tsdz2" displayed in the bottom).
I flashed the original firmware back, put the 850c back in place and it works.
So the problem comes from the 860c, and that's why I was trying to flash the OSF back on it (without much hope, but who knows). The FW update worked sucessfully, but I always get the same start screen with a "waiting for tsdz2" message (followed by a "brake or com error"). Kaput !
Not a problem, I'll stay with the 850c and orignal FW while you guys go on with developping this OSF.
Thanks a lot for the good work, hoping to be able to try this again soon :)
Hello, I had the same problem with many versions. Try flashing the firmware on the 860C.


This version worked for me.
 
I tested version 25.hex, at first the first impressions were not the best (I had the same settings as in version 19.hex, which worked very well for me). After trying to change various settings I reduced Torque adc offset to 160 and it works very well, probably even better than 19.hex.
 

Attachments

  • 20250613_142921.jpg
    20250613_142921.jpg
    1.9 MB · Views: 8
I tested version 25.hex, at first the first impressions were not the best (I had the same settings as in version 19.hex, which worked very well for me). After trying to change various settings I reduced Torque adc offset to 160 and it works very well, probably even better than 19.hex.
When you have a torque sensor that has a quite large gap between min and max ADC values with no weight, it is "normal" that you have to change the ADC offset in version 25 compared to the ADC offset value used for version 23 (or some previous). It is because v25 uses usually the average over nearly one rotation while 23 uses the max.
 
I think I managed to damage the controller of TSDZ8. OK, the following happened:

This is my second TSDZ8. The first motor I was not able to flash OSF for VLCD5 (display showing only one battery bar and motor not reacting). But with 860C version everything worked, also I was able to flash back the facebook version of FW and motor worked.
- I dismiss that this could be the fault of Chinese J-link device or that I have made wrong wiring 5 pin connector.

So with second TSDZ8 I wanted to try my luck and do the OSF again for VLCD5.
- I have used the 20v hex file
- I have disconnected the battery when flashing
- Configurated java config file accordingly

After powering on the VLCD5 display showed like in the first time- single battery bar and no reaction. Some minutes later display shut down. Trying to turn on/off the battery main switch, I have heard a clicking noise in the battery (which appears to be a safety protection), but at time was not sure what is this. So I connected my other older battery and short circuit.... I tried to flash back facebook FW, but the battery protection "clicks"- so it is still short circuit.

So I assume I managed to damage somehow the controller and when connecting battery- I am getting now short circuit. I have measured the power terminals of motor and it is a closed loop now. I have no problem to buy a new controller, but I am lost what I am doing wrong with OSF for VLCD displays?
 
Back
Top