TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
I wonder if these old drivers should be bought in stock as long as they are available.
https://www.pswpower.com/products/bare- ... id-motor-1
https://www.pswpower.com/products/bare- ... id-motor-1
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
HI all,casainho wrote: ↑Sep 24 2020 12:10pmI think I understand the root of this issue, and may be the same for the issue on lights not working. I think the issue is that the firmware is trying to control the current with a minimum value 0.156 amps with the same as the control step of 0.156 amps - I mean, the current min value should be an higher value like 1 amp, so there are 6 steps to control the current. Right now, I think that when PWM is 0 and will start to increase, the current value will bounce near zero before finally increase and that bounce is taking the undesirable time... I thin the solution may be to force the min current value to be like 1 amp.
My focus is to develop the TSDZ2 wireless and then I will be back to the TSDZ2 firmware.
Power Delay Isue, is also being analyzed in the mbrusa forum.
viewtopic.php?f=30&t=110682&start=75#p1624431
The problem is not yet solved and it is very demotivating, for those who do mountain biking, on complex trails.
Below I present the link to anyone who wants to help,
Thanks
Azur
-
- Posts: 30
- Joined: Jan 10 2020 1:20pm
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
The question I have before I buy a spare (hopefully old) controller or two is whether at some point in the future it will be possible to flash the new infineon controller with the OSF?
I’m well aware that these things are easy to ask for but difficult to implement! Thanks for all that you do.
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
Please donate to me or other developers (like mbrusa or mspider65) the new motor controllers!!devboy-greg wrote: ↑Mar 12 2021 10:13amThe question I have before I buy a spare (hopefully old) controller or two is whether at some point in the future it will be possible to flash the new infineon controller with the OSF?
I’m well aware that these things are easy to ask for but difficult to implement! Thanks for all that you do.
- EBike wireless standard: wireless motor, wireless cycling GPS display Garmin Edge and wireless remote with wireless brake sensor
- TSDZ2 FAQ: issues and repairs, etc
- TSDZ2 OpenSource firmware
Developer of OpenSource knowledge and technology for ebikes: Wireless EBike standard ANT+ and Bluetooth, TSDZ2 OpenSource firmware, KT motor controllers and displays: Bafang 850C color, SW102 Bluetooth and KT-LCD3.
Please consider a donation to help developments: paypal.me/jorgecasa
- TSDZ2 FAQ: issues and repairs, etc
- TSDZ2 OpenSource firmware
Developer of OpenSource knowledge and technology for ebikes: Wireless EBike standard ANT+ and Bluetooth, TSDZ2 OpenSource firmware, KT motor controllers and displays: Bafang 850C color, SW102 Bluetooth and KT-LCD3.
Please consider a donation to help developments: paypal.me/jorgecasa
-
- Posts: 30
- Joined: Jan 10 2020 1:20pm
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
No problem, I will PM you...casainho wrote: ↑Mar 12 2021 10:33amPlease donate to me or other developers (like mbrusa or mspider65) the new motor controllers!!devboy-greg wrote: ↑Mar 12 2021 10:13amThe question I have before I buy a spare (hopefully old) controller or two is whether at some point in the future it will be possible to flash the new infineon controller with the OSF?
I’m well aware that these things are easy to ask for but difficult to implement! Thanks for all that you do.
-
- Posts: 22
- Joined: Sep 22 2020 11:49am
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
This is the link to r0nkos fork for all those who are unhappy with the actual motor behaviour.
viewtopic.php?t=105973
It is a torque only mode with immediate response And its compatible with the sw102 displays...
For me the best solution unless this mode isn’t implemented in the standard open source firmware. Since this mode already exists i wonder why this issue cant be fixed...
however
viewtopic.php?t=105973
It is a torque only mode with immediate response And its compatible with the sw102 displays...
For me the best solution unless this mode isn’t implemented in the standard open source firmware. Since this mode already exists i wonder why this issue cant be fixed...
however
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
It is going to be related to one of these changes:Peacepirate wrote: ↑Mar 13 2021 8:11amThis is the link to r0nkos fork for all those who are unhappy with the actual motor behaviour.
viewtopic.php?t=105973
It is a torque only mode with immediate response And its compatible with the sw102 displays...
For me the best solution unless this mode isn’t implemented in the standard open source firmware. Since this mode already exists i wonder why this issue cant be fixed...
however
Current ramp made quicker
PWM ramp-up made a bit quicker
The current ramp is multiplied by 3 internally in the firmware, so if you set 6a/sec, the firmware will ramp at 18a/sec - it could be this. I will see if I can get time to look at the internals of motor.c today and compare with the current version used in v20.1c
Genesis iOiD Alfine8 Hard tail MTB, 36v TSDZ2, 13s battery, SW102 display
Raleigh reynolds road frame from the 80's, 36v TSDZ2, 13s battery, SW102 display, 1x10 drivetrain, gravel tyres
Raleigh reynolds road frame from the 80's, 36v TSDZ2, 13s battery, SW102 display, 1x10 drivetrain, gravel tyres
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
Hello,
For more than 2 years I was using the opensource firmware with the KT-LCD3 display and I was fully satisfied (v0.20.0-beta.1). I take this opportunity to thank all the community the work
work done is simply remarkable
I just switched to the new firmware (v1.1.0) with the 860C display and I despair to find the behavior I had until now. I used as much as possible the same settings but I did not activate the torque sensor calibration.
My power assist has a delay of a few hundred ms which makes the experience much less pleasant than it was:
1- This delay is present at startup
2- This delay is also present at the stop of the pedaling
Point 2 is more annoying, since I have to stop pedaling for a longer time to change gears (to reduce the stress on the chain/derailleur) before starting pedaling again.
On the motor side, I'm using TSDZ2-v1.1.1.hex firmware, maybe I should flash v1.1.0 (I didn't try)? What are the differences between the 2 versions?
In short, as I only changed the software, I think that there must be a setting that I don't understand, could you give me an idea of what is happening?
Thanks guys!
For more than 2 years I was using the opensource firmware with the KT-LCD3 display and I was fully satisfied (v0.20.0-beta.1). I take this opportunity to thank all the community the work
work done is simply remarkable

I just switched to the new firmware (v1.1.0) with the 860C display and I despair to find the behavior I had until now. I used as much as possible the same settings but I did not activate the torque sensor calibration.
My power assist has a delay of a few hundred ms which makes the experience much less pleasant than it was:
1- This delay is present at startup
2- This delay is also present at the stop of the pedaling
Point 2 is more annoying, since I have to stop pedaling for a longer time to change gears (to reduce the stress on the chain/derailleur) before starting pedaling again.
On the motor side, I'm using TSDZ2-v1.1.1.hex firmware, maybe I should flash v1.1.0 (I didn't try)? What are the differences between the 2 versions?
In short, as I only changed the software, I think that there must be a setting that I don't understand, could you give me an idea of what is happening?
Thanks guys!
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
Hi guys, I've been messing around for days to flash and connect the 860C display to the TSDZ2 but I just can't.
Meanwhile, an easy question: is the 860C display (with the appropriate wire changes) compatible with the TSDZ2? That is with the original engine firmware, can the display show basic parameters like the VLCD6?
And now the hardest part: installed and configured drivers and software for the bootloader as indicated in github website, the display turns on so is powered correctly, but any attempt to program it with "Apt Burn Tools" fails.
I connected the two wires for the power supply and the two TX and RX wires, leaving out the orange wire of the display whose function I don't know.
Apt software shows "Waiting..." but nothing
List of all attempts made:
- correctly identified the COM port
- swap the RX and TX cables in both ways
- tested on laptop and desktop PC both with Windows 10
- all display keys work correctly
- programming performed with and without Administrator privileges
- numerous attempts to restart the display before and during programming
- tests performed with different supply voltages (between 27 and 38 volts)
- pressing the power button on the display both with the screen on and off
- duration of pressing the button from a simple click to a few seconds
- tests carried out with three different USB-UART bootloader
Could it be a non-reprogrammable version of the display?
Meanwhile, an easy question: is the 860C display (with the appropriate wire changes) compatible with the TSDZ2? That is with the original engine firmware, can the display show basic parameters like the VLCD6?
And now the hardest part: installed and configured drivers and software for the bootloader as indicated in github website, the display turns on so is powered correctly, but any attempt to program it with "Apt Burn Tools" fails.
I connected the two wires for the power supply and the two TX and RX wires, leaving out the orange wire of the display whose function I don't know.
Apt software shows "Waiting..." but nothing
List of all attempts made:
- correctly identified the COM port
- swap the RX and TX cables in both ways
- tested on laptop and desktop PC both with Windows 10
- all display keys work correctly
- programming performed with and without Administrator privileges
- numerous attempts to restart the display before and during programming
- tests performed with different supply voltages (between 27 and 38 volts)
- pressing the power button on the display both with the screen on and off
- duration of pressing the button from a simple click to a few seconds
- tests carried out with three different USB-UART bootloader
Could it be a non-reprogrammable version of the display?
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
I have uploaded the 20.1c versions to SW102. setup menu crashes very often. To set everything up, I had to disconnect the battery 16 times. But it worked. Driving test tomorrow.
I'm on a test drive. Much better than 1.1.0, you can say a masterpiece, the hybrid mode is a revelation. But, it's terribly power-hungry. After 12 km on flat terrain, I heated up to 72 °, the consumption was quite high in the 5th mode out of 9 practically around 500W pulls. 3V battery drop after 12km. Where on 0.8 with a calibrated sensor I did 2x as much on a similar support factor (50%), but I never reached 60 ° on the same route. And the power fluctuated in the range of 100-250W with the same sensations of support.
This weakening of the field does not suit me terribly, I like a low cadence, but when I crank the crank around 110, I do not feel any resistance at all and the 350W power consumption jumps in. It is a pity that it can not be turned off because it may be the reason of power-hungry in the lower cadence and the effect of 0 ...
Last edited by hetm4n on Apr 09 2021 12:59pm, edited 1 time in total.
mongoose teocali comp 2014 TSDZ2 750W 13s3p & 13s7p
dartmoor primal 2017 bafang BBS02b 750W 13s6p
dartmoor primal 2017 bafang BBS02b 750W 13s6p
Re: TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)
I tried the setup you have above. Never got it to work. Either the step up converter didn’t have enough juice or the USB port couldn’t supply enough. I ended up adding a cable to supply the display direct from the battery. Make sure you connect both the USB/UART output ground to the battery ground and the display ground.darione wrote: ↑Apr 08 2021 12:23pmThank you for reply.
GND from USB/UART is connected to "IN-" of DC-DC Step up power and the "OUT-" to display GND
Uart e Power.jpg