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

[dsjustice]

Did you perhaps disconnect the battery with the display on? 860C doesn't like this.
...
If it's not there, that's the problem, so either replace the display or put an external switch, to be turned on after the display.

It was a few weeks ago, but it's easy to imagine that I cut power with the battery master switch without shutting down first. It never occurred to me that this would be a problem:-( I'll get it on the bench this weekend and check Vin as you suggest, thanks for the tip!

[zachhalley@gmail.com]

Thanks so much to all contributors for this firmware, I've been running it joyously for a few hundred kms now.

I've got the VLCD6 installed at the moment but have been thinking about upgrading to a more premium display to match the firmware

Does anyone know if the 25km/h speed limit that is pre flashed on the DZ40, DZ41 and SW102 displays sold by Enerprof can be overridden by this OSF? I'm thinking yes, but it would be great if someone who has done it can confirm!

[kiwinigma]

...
I've been using tsdz2 with 850c display for a few weeks. I've tried installing OSF but not having any luck installing it on the display ...

I'm wondering - what happens if you install mbrusa's OSF version for "vlcd2-vlcd6-xh18"....

It depends with which firmware the 850C did run before.
There are more versions of the 850C display
- one that runs with stock Tongsheng FW, which isn't flashable
- one that run with stock Bafang FW, which isn't flashable
- one that run with stock Bafang FW, which is flashable

Only the first version can run OSF for stock display Vlcd5, Vlcd6,XH18
The second can only run with Bafang
The third can be flashed for OSF for 850C-860C-SW102, but almost isn't findable anymore

So the question is.... How did run the 850C for a few weeks before?
Have you another display with your tsdz2 and have you flashed the controller already?

Thanks Elinx

If this is true, it seems like this information should be much more front and centre so that new buyers know it may be better to choose a different display when purchasing the system with OSF in mind.

My display came with, and runs with, factory TSDZ2, and has a 6 pin cable. It came from recycle-ebike together with the motor. I could post the serial numbers from the back but not sure if that clarifies things or helps the situation.

I will try the vldc/hx18/newly 850c OSF version and see what happens

[Elinx]

....
Does anyone know if the 25km/h speed limit that is pre flashed on the DZ40, DZ41 and SW102 displays sold by Enerprof can be overridden by this OSF? I'm thinking yes, but it would be great if someone who has done it can confirm!

The speedlimit is programmed inside the controller and with stock FW that normally can be changed with the display if the speedlimit setting is there.
Enerprof has a different Tsdz2 controller with a fixed 25km/h limit which can't be flashed with OSF, but the display is useable for all controllers.

If the DZ40, DZ41 or SW102 are specific made for Tsdz2, you can flash OSF for stock display.
With OSF for stock Tsdz2 display you setthe speedlimit with the Java configurator independent of the display settings.

[Elinx]

.... It came from recycle-ebike together with the motor....

I will try the vldc/hx18/newly 850c OSF version and see what happens

If this is the one you have ordered you have indeed stock FW and can flash OSF for stock display to the controller.

[zachhalley@gmail.com]

The speedlimit is programmed inside the controller and with stock FW that normally can be changed with the display if the speedlimit setting is there.
Enerprof has a different Tsdz2 controller with a fixed 25km/h limit which can't be flashed with OSF, but the display is useable for all controllers.

If the DZ40, DZ41 or SW102 are specific made for Tsdz2, you can flash OSF for stock display.
With OSF for stock Tsdz2 display you setthe speedlimit with the Java configurator independent of the display settings.

Thanks for your quick reply Elinx! I had thought as much, but really appreciate the confirmation before spending the $$$

[dsjustice]

For flashing it is more difficult to understand what the problem is.
27.5V voltage should be fine, try 30V if you can.
Pressing the button must be very very short, otherwise the display will turn on.
When the flashing fails, you have to try to reverse TX and RX, surely you have already done it, try again.
About the components for the bootloader-box I used these:
https://github.com/OpenSourceEBike/TSDZ ... bootloader

Thanks again, great tips! I used a CP2102 USB-UART like the one you linked, and wired PL directly to the 52V battery instead of using my $.99 boost converter. After those changes, I started to observe an RX packet in the APT-BURN tool every time I clicked the controller button. It took a dozen or so tries, but I did eventually see the progress incrementing, got a good flash, and my controller is now talking successfully to my motor!

To save myself potential grief in the future: is there anything like an APT-READ tool to backup the state of the controller prior to attempting an upgrade? I've searched the thread and haven't found anything... but it's a very long thread.

[mbrusa]

Well, I'm glad you fixed it.

With 860C it is not possible to read and save the configuration.
You need to keep a reminder of the changed parameters.

[endlessolli]

Hi @mbrusa;
I wanted to ask, if there is a chance that you bring the std. display version up to the level of the versions for the other versions?
(20.1C.2 -> 20.1C.4) Especially interesting would be the further motor optimizations you included in the 3.. and 4.. Versions.
Thanks again for this great firmware!!

[mbrusa]

Hi endlessolli.
I had suspended testing with the new v20.1C.5 releases in May 2022, haven't resumed them yet.
Over the past summer, I've preferred to use proven and safe versions.
This is the situation of the stock display version:
v20.1C.3 (based on mspider v13) released and withdrawn due to mosfet burn reports (I personally had never had any problems).
v20.1C.4 (based on mspider v14) never released because I happened to burn a controller.
v20.1C.5 (based on mspider v15) tested for one year and 1200 km, but I don't trust to release it, because the hidden bug that caused mosfet burning in versions 3 and 4, might still be present.
I plan on resuming testing, but I won't release it without locating the cause of the problem.

[pxl666]

what optimizations you refer to ?

[endlessolli]

what optimizations you refer to ?

The optimizations @mbrusa referred to in the above post (derived from mspiders FW Versions)

[endlessolli]

Hi endlessolli.
I had suspended testing with the new v20.1C.5 releases in May 2022, haven't resumed them yet.
Over the past summer, I've preferred to use proven and safe versions.
This is the situation of the stock display version:
v20.1C.3 (based on mspider v13) released and withdrawn due to mosfet burn reports (I personally had never had any problems).
v20.1C.4 (based on mspider v14) never released because I happened to burn a controller.
v20.1C.5 (based on mspider v15) tested for one year and 1200 km, but I don't trust to release it, because the hidden bug that caused mosfet burning in versions 3 and 4, might still be present.
I plan on resuming testing, but I won't release it without locating the cause of the problem.

Thanks for the feedback, @mbrusa.
Definetely better to have a working fw with the major improvements included
then one with some additional slight improvements which has the potential to burn the mosfets.
100% agreed

Thanks again for your work here and your save & conservative approach on releasing further iterations to the community.

[pxl666]

what optimizations you refer to ?

The optimizations @mbrusa referred to in the above post (derived from mspiders FW Versions)

you mean the post where mbrusa is listing versions? I see no list of optimizations ... could you just briefly say what are they? motor optimizations? better power management?

[endlessolli]

what optimizations you refer to ?

The optimizations @mbrusa referred to in the above post (derived from mspiders FW Versions)

you mean the post where mbrusa is listing versions? I see no list of optimizations ... could you just briefly say what are they? motor optimizations? better power management?

In Mbrusas post there are references to mspiders firmware versions (v13, v14, v15)
The changes behind these versions are described in the release notes of mspiders firmware:
https://github.com/TSDZ2-ESP32/TSDZ2-Sm ... e/releases
So these are further efficiency & robustnesd improvements; plus other stuff like field weakening option.

[Yari]

Hi all, just flashed with 20.1C.4-860C-update 2 on a TSDZ2B 36V with 860C all worked well but the motor is not turning even with walk mode. I have no error msg, display shows battery voltage and cadence. When I press walk mode, motor engage just a little like 2mm and stops. I have tried the different mode, even the Cadence mode doesnt work... Any thoughts on what could go wrong ?
EDIT : all good, just missed some key configuration like motor voltage. Thanks again Marco

[pxl666]

is there a simple way to a layman to change code in that way so if there is an error and override - the error goes away after 10 seconds ? now if i tear up speed sensor cable and override error i can ride but everyting is obstructed by error message ...

[mbrusa]

I preferred to display the error code even with "Assist with sensor error" enabled, to remind the user that the error is always present.
With XH18 there is no problem, error code and speed (or data) are in two different fields.
Do you mean that with VLCD5 and VLCD6, in the presence of an error, the data when the lights are switched on are not displayed?

[pxl666]

I preferred to display the error code even with "Assist with sensor error" enabled, to remind the user that the error is always present.
With XH18 there is no problem, error code and speed (or data) are in two different fields.
Do you mean that with VLCD5 and VLCD6, in the presence of an error, the data when the lights are switched on are not displayed?

vlcd6 , i have damaged speed sensor wire and it will take time to fix this . anyway, it's good to see error and then see temperature or speed / distance ... if thats possible ofkoz

[nastslay]

Hi, is it possible that I burnt controller while messing up with the pins on st link v2?

[pxl666]

Hi, is it possible that I burnt controller while messing up with the pins on st link v2?

you mean that you have sent voltage to different pin ?

[nastslay]

Hi, is it possible that I burnt controller while messing up with the pins on st link v2?

you mean that you have sent voltage to different pin ?

Yes :/

[Jmumf]

If the system worked and then without changing anything "Wait TSDZ2" appeared, the display probably failed.
Did you perhaps disconnect the battery with the display on? 860C doesn't like this.

How common is this with the 860C.

I’ve had a battery disconnect while riding and it would seem that that would make the 860C fail.

How can you best avoid this problem?

[dsjustice]

If the system worked and then without changing anything "Wait TSDZ2" appeared, the display probably failed.
Did you perhaps disconnect the battery with the display on? 860C doesn't like this.

How common is this with the 860C.

FWIW, in my case everything was made right by re-flashing -- I did both the display and the motor, but in retrospect I suspect it was just a corrupted bit of flash memory in the display. Very likely caused by power interruption, but still, nice to know it didn't destroy my hardware.