TSDZ2 OSF for all displays, VLCD5-VLCD6-XH18, LCD3, 860C-850C-SW102.

[mbrusa]

Yes, by connecting a temperature sensor to the throttle input, 8 pin controller is required.
The temperature is displayed in ° C.
In the configurator it is possible to set temperature limits to avoid overheating of the motor.

 

[mbrusa]

I cant get the latest version to work on my 850c, older version work but the master and c2-1 the offroad mode cant be enabled.

Are you sure you tested to switch to offroad mode on assist level 2 and not level 1?
850C has 5 levels, on the newest OSF version you have to change it on level 2 if your display uses 5 levels.

Omg, it worked for me straight away on lvl 2 thx

Same here, haha. I am a bot...

:lol:

 

[mbrusa]

A question to anyone who has the stock 850C display.
At level 1, by activating walk assist, does the level remain at 1 or does it go 0-OFF?

 

[MJC-KER]

From how you described it, it is a hardware problem with the display screen.
Avoid reprogramming it, or use it like this, or it needs to be replaced.
For display and motor, OSF must be the same version.

Yep, looks like a failed display - just got a replacement (not cheap at £85 from Ebay) P860ML. Flashed fine with 20.1C.3, seems to be all working.
For info, original was P860C, new is P860ML (multi-language apparently)

 

[v85]

Anyone with Enerpower SW102 Display UART Tongsheng compatible 6-Pins (stock display, but SW102)?
What version OSF is compatible with? Flashing without tearing apart? Bluetooth support?
How looks OSF UI for SW102 (anszom`s mod of casainho`s firmware is looking very nice)?

 

[Elinx]

....
What version OSF is compatible with? Flashing without tearing apart? Bluetooth support? ....

imho this display is build specific for Tsdz2 and can't be flashed with Casainho or Anzom build.
You can use OSF for stock display, which means flashing the controller only with Javaconfigurator.

 

[dameri]

I've tried two new controllers and two new torque sensors in the motor, and I always get an e:2 Torque Fault. In cadence mode, the motor works well, and in assist with error mode, the motor also works also in other modes. What could be wrong.

The torque sensor can't be completely dead, because the assist is better when switching from cadence to other modes where the torque sensor is included.

In the pictures speed was about 20 km/h.

This software is installed in TSDZ2-v20.1C.4-860C-update-1

Power mode

Hybrid mode

 

[mbrusa]

Calibration enabled or disabled?
v20.1C.4 update 1 is on both, display and controller?
Post a photo of the Torque Sensor menu screen.
Then two photos of the Technical menu, with the bike stationary, one without pushing on the pedals, and one standing on a single pedal.

 

[dameri]

Calibration enabled or disabled?
v20.1C.4 update 1 is on both, display and controller?
Post a photo of the Torque Sensor menu screen.
Then two photos of the Technical menu, with the bike stationary, one without pushing on the pedals, and one standing on a single pedal.

Calibration enabled. I'll post photos tomorrow.

 

[dameri]

Calibration enabled or disabled?
v20.1C.4 update 1 is on both, display and controller?
Post a photo of the Torque Sensor menu screen.
Then two photos of the Technical menu, with the bike stationary, one without pushing on the pedals, and one standing on a single pedal.

Calibration enabled. I'll post photos tomorrow. Display and controller has updated latest version.

 

[dameri]

Here are photos:

Torque

Technical Pedal free

Technical standing on pedal

 

[mbrusa]

Well, from the photos you can see the cause of e2 error.
"Technical-> ADC torque sensor" with free pedals, is 132, this value must be entered in "Torque sensor-> Torque adc offset", not 175.
"Technical-> ADC torque sensor" standing on the pedal, it's 296, value entered in "Torque sensor-> Torque adc max" is fine.

There is another wrong parameter, it is "Torque sensor-> Torque adc step", why 120?
It is not important because it is only used in Power mode with calibration disabled.
The value to be entered (estimated) with the right torque sensor parameters is 34.
This can be achieved by setting "Calibration" disabled and "Default weight" yes. "ADC torque step calc" is the estimated value of "Torque adc step".
Attention, with "Calibration" enabled, "ADC torque step calc" is the estimated value of "Torque adc step adv".

 

[dameri]

Well, from the photos you can see the cause of e2 error.
"Technical-> ADC torque sensor" with free pedals, is 132, this value must be entered in "Torque sensor-> Torque adc offset", not 175.
"Technical-> ADC torque sensor" standing on the pedal, it's 296, value entered in "Torque sensor-> Torque adc max" is fine.

There is another wrong parameter, it is "Torque sensor-> Torque adc step", why 120?
It is not important because it is only used in Power mode with calibration disabled.
The value to be entered (estimated) with the right torque sensor parameters is 34.
This can be achieved by setting "Calibration" disabled and "Default weight" yes. "ADC torque step calc" is the estimated value of "Torque adc step".
Attention, with "Calibration" enabled, "ADC torque step calc" is the estimated value of "Torque adc step adv".

I noticed myself too that I had put the wrong value in this "Technical-> ADC torque sensor" and corrected it. I also fixed the correct value for "Torque adc step". After the corrections, e2 error still appears on the display.

[youtube]https://youtu.be/G62crtOsfUM[/youtube]

 

[mbrusa]

Strange, there is probably a slow response torque sensor.
Have you tried with calibration disabled if there is the e2 error?
In your case, it should work fine even if disabled.

 

[dameri]

I go just cyckling and will try calibration disabled.

I'm wondering this because error comes with two brand new controllers and torque sensors. Controllers and one torque sensor are from PSWPower and other torque sensor is from EJoygi. I have never before have this problem with older parts. Next I will try another cable. Then I don't know what to do.

 

[dameri]

Thank you mbrusa.

I switched calibration disabled and turned power off and on again. There were no errors on display.

I drove to the grocery store and turned the power off. When I came out of the store, I switched to calibration enabled mode and turned power off. Turn the power on again and there are errors in the display.

 

[forsa355]

The fix for the DZ41 display works well. All levels from 1 to 5 work correctly. Thank you mbrusa! The bug with the appearance of error 30 no longer appeared. Tried several times to turn on the system, but everything was ok. From the description of the DZ41 display codes, code 30 is a loss of communication. This is probably a display issue, not the OSF.

I bought a DZ41 display from Aliexpress and tried it with the latest beta (5 level one) but I also get an error code 30 almost immediately when powering on. It's set as "VLDC5" in the configurator. I tried a few different cables and keep getting the error 30.

I note you have a version of the DZ41 from Enerpower. Is this version specific for the TSDZ2 or should any Bafang DZ41 be compatible with this motor firmware? I wonder if this is my problem or it is a configuration issue.

 

[mbrusa]

The Bafang version is no good, it only works if specific for TSDZ2 and 6 pin connector, I think it is only sold by Enerprof.

 

[Elinx]

.....
I bought a DZ41 display from Aliexpress and tried it with the latest beta (5 level one) .....
... should any Bafang DZ41 be compatible with this motor firmware?...

Enerprof (=Enerpower) sell the DZ41 specific for Tsdz2, which means it is a stock display and flashing the controller with Java configurator is enough.
Versions for Bafang are not compatible and there is no bootloader file for it.
Most Aliexpress sellers mention explicit this display is for Bafang.

 

[mbrusa]

Thank you mbrusa.

I switched calibration disabled and turned power off and on again. There were no errors on display.

I drove to the grocery store and turned the power off. When I came out of the store, I switched to calibration enabled mode and turned power off. Turn the power on again and there are errors in the display.

Thanks for the confirmation dameri.
The cause of the e2 error is in a check added to v20.1C.4 update 1.
The purpose is to signal if there is a push on the pedals while turning on the display. It is active only when calibration is enabled.
In the previous version this control was not there.
Strange to have the problem on two different controllers, maybe wrong value of "Torque adc offset"?
In the next version I will increase the check threshold. In the meantime you can leave the calibration disabled, in your case nothing changes.

 

[forsa355]

.....
I bought a DZ41 display from Aliexpress and tried it with the latest beta (5 level one) .....
... should any Bafang DZ41 be compatible with this motor firmware?...

Enerprof (=Enerpower) sell the DZ41 specific for Tsdz2, which means it is a stock display and flashing the controller with Java configurator is enough.
Versions for Bafang are not compatible and there is no bootloader file for it.
Most Aliexpress sellers mention explicit this display is for Bafang.

thanks for confirming this for me... I guess I got a little too excited when I read here there was finally a small, decent looking display for the TSDZ2. Got ahead of myself and immediately ordered one without doing enough research.

But on a more positive note, looks like Enerprof has another small TSDZ2 compatible display coming soon that looks interesting. https://enerprof.de/motor-kits/disp...ongsheng-kompatibel-6-pins-150-cm-kabel?c=129. I just wish their shipping to Canada was cheaper

I may order both to try, but in the meantime does anyone know how to flash a Bafang DZ41 to work with the TSDZ2?

 

[dameri]

Thank you mbrusa.

I switched calibration disabled and turned power off and on again. There were no errors on display.

I drove to the grocery store and turned the power off. When I came out of the store, I switched to calibration enabled mode and turned power off. Turn the power on again and there are errors in the display.

Thanks for the confirmation dameri.
The cause of the e2 error is in a check added to v20.1C.4 update 1.
The purpose is to signal if there is a push on the pedals while turning on the display. It is active only when calibration is enabled.
In the previous version this control was not there.
Strange to have the problem on two different controllers, maybe wrong value of "Torque adc offset"?
In the next version I will increase the check threshold. In the meantime you can leave the calibration disabled, in your case nothing changes.

Ok, I always wait and don't touch pedals when I power on. I'm never that busy. I changed motor with new parts and I just check new calibration values and add them to torque section. Maby I have changed accidentally some other point. Now I will take always instructions to the garage and not trust my memory.

Thank you for developing.

 

[Piper J3]

I just added the LM35 temperature sensor to my TSDZ2 with 860C and OSF running 0.21.4. I cut the Black, Orange, and White wires from the 8-wire loom and left them loose. I connected the LM35 directly to the Black, Orange, and White wires from the controller. I used LM35 pinout to determine power, signal, and ground connections.

Problem – Display just flickers on power-up. Question… should the Black, Orange, and White wires from the controller still be connected to the 8-wire loom going to the display?

I hope I didn’t fry anything…..

 

[Elinx]

....added the LM35 temperature sensor to my TSDZ2 with 860C ....

Problem – Display just flickers on power-up. ....

Maybe the same problem as here ?

I don't like the mention of wire colors only, because it says nothing about what it should be.
Colors could be changed by a new batch.

Imho the problem is that just one wire is unique for LM35 (throttle).
The other two are V+ and Gnd which are needed for other things too.

 

[endlessolli]

....added the LM35 temperature sensor to my TSDZ2 with 860C ....

Problem – Display just flickers on power-up. ....

Maybe the same problem as here ?

I don't like the mention of wire colors only, because it says nothing about what it should be.
Colors could be changed by a new batch.

Imho the problem is that just one wire is unique for LM35 (throttle).
The other two are V+ and Gnd which are needed for other things too.

It could also be that you bought a "fake" LM35, which is a relabled transistor and might short 5V and GND.
(It happened to me). Due to chip shortage I have the feeling that all LM35 on ebay / from China are currently fakes.

Did you test it uninstalled- i.e. connecting 5v and GND and measure the Voltage at the output pin and see if it increases when you touch it....