• Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
    Can you donate? Please see our fundraising page. Thank you!

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

Can I get a bit of an overlook to what I'm doing wrong here...
Tsdz2b with a varstrom ekd01 display using latest update n22.
I can read and write via STVP, Java config seems to flash across correctly. Although. I get an Error 30 on the display. Pretty much everything I do that isn't writing the stock firmware, I'll get error 30.

It's a pain because my current stock firmware has full level 5 assist on the pedal when I've got the display set to 0 (or any level).

Could the varstrom display be causing issues? That's the only thing I can pin point might be an issue here.
 
Error 30 is a communication problem between the display and the controller.
You write that with the stock firmware it doesn't give the error, but it doesn't work properly. You get full support at all levels, even at level 0.
Has it always been like this? Or did you update the display firmware and something went wrong?
 
From your description, it seems to depend on the cut-off or shutdown voltages.
In the last two versions (6.4 and 6.5), significant changes have been made to voltage stabilization and Soc calculation.
These changes, however, only affect the data display: Soc%, voltage, and battery bars. They have no impact on motor operation.
My hypothesis is that the problem appeared in version 6.3, following this change:
- Fixed the delay in motor activation/reactivation.
This change increases the starting current peak, which could cause a greater momentary voltage drop, up to the voltage shutdown value.
To confirm, you should test: install version 6.5 and set the voltage cut-off to 29V (there's no risk, the BMS always protects the battery).
Check if the problem has disappeared.
Also check whether the Soc% is maintained when the display is turned off when it's turned back on (with SocCalc set to Auto).
Let me know, thanks.
Ok, so I finally managed to drain the battery below 45V. It seems your tip worked, I set the voltage cut-off to 29V and now I still have support on lower voltages. The battery bars show the Soc correct.
However, I noticed a very strong power loss now when I am at lower voltages.
Today I cycled up a hill and even at level 04 there was little assistance when going >15 km/h. I remember having less power at low voltages because of current cap, but I don't remember it being that bad. When starting from 0 km/h uphill I have a good amount of motor support, but after about >15 km/h level 04 feels like level 01 and I have to pedal with tremendous amount of work to get to higher speeds.
Battery max current in configurator is set to 18A, motor max power is at 700W. Battery voltage measured at 43V.
Is there a way to circumvent that behaviour?
 
Last edited:
I have a problem with my TSDZ2 with latest OSF.

During my latest ride I got E07 twice. The first time i turned off and on the motor and everything was normal but after the second time I no longer had any assistance at all despite no error msg on the display.
Restarting the display didn't make any difference.

Three new things have appeared now after that:

1. I cant shut off the display with the power button.
When i try shutting it off with the power button the text "Off" on the display stays on forever and doesn't dissappear unless I disconnect the battery.

2. Also, when i reconnect the battery the display turns on by itself!
It never did that before.

3. When rolling the bike backwards there is a noticeably bigger resistance than before.
It feels and sounds as if the motor and all the internal gears spin when rolling the bike backwards, is that normal?

Have i fried the motor and/or the controller considering the rolling resistance and strange display behaviour?
 
Last edited:
1. I cant shut off the display with the power button.
When i try shutting it off with the power button the text "Off" on the display stays on forever and doesn't dissappear unless I disconnect the battery.

2. Also, when i reconnect the battery the display turns on by itself!
It never did that before.
Whenever I have weird stuff like that going on (in my case it was the motor still working after turning off the display), I try to reflash the option byte tab in STVP. It often solved issues for me.
For the backward thing though I have non idea.
 
Whenever I have weird stuff like that going on (in my case it was the motor still working after turning off the display), I try to reflash the option byte tab in STVP. It often solved issues for me.
For the backward thing though I have non idea.
I tried reflashing the option byte but unfortunately it didn't make any difference but tnx for the tip anyway!
 
Ok, so I finally managed to drain the battery below 45V. It seems your tip worked, I set the voltage cut-off to 29V and now I still have support on lower voltages. The battery bars show the Soc correct.
However, I noticed a very strong power loss now when I am at lower voltages.
Today I cycled up a hill and even at level 04 there was little assistance when going >15 km/h. I remember having less power at low voltages because of current cap, but I don't remember it being that bad. When starting from 0 km/h uphill I have a good amount of motor support, but after about >15 km/h level 04 feels like level 01 and I have to pedal with tremendous amount of work to get to higher speeds.
Battery max current in configurator is set to 18A, motor max power is at 700W. Battery voltage measured at 43V.
Is there a way to circumvent that behaviour?
Okay, so setting the cut-off voltage to 29V is fine. (Obviously, it's not the solution; it's just to understand the cause of the problem.)
I also asked to check whether turning the display off and on again when the battery is low maintains the Soc% value. Have you checked?
To better understand the cause, a few more questions:
Are you using hybrid mode?
Is Smooth Start enabled or disabled?
If enabled, what is the ramp set to?

Regarding the drop in assistance when the battery is low, I'll answer you later.
 
I have a problem with my TSDZ2 with latest OSF.

During my latest ride I got E07 twice. The first time i turned off and on the motor and everything was normal but after the second time I no longer had any assistance at all despite no error msg on the display.
Restarting the display didn't make any difference.

Three new things have appeared now after that:

1. I cant shut off the display with the power button.
When i try shutting it off with the power button the text "Off" on the display stays on forever and doesn't dissappear unless I disconnect the battery.

2. Also, when i reconnect the battery the display turns on by itself!
It never did that before.

3. When rolling the bike backwards there is a noticeably bigger resistance than before.
It feels and sounds as if the motor and all the internal gears spin when rolling the bike backwards, is that normal?

Have i fried the motor and/or the controller considering the rolling resistance and strange display behaviour?
It looks like the controller is damaged.
The display probably stays on because it's receiving voltage from the controller on Vin.
The increased resistance when pushing the bike backwards is probably due to a mechanical problem with the large sprag clutch.
Have you tried pedaling with the assist level set to OFF? Do you feel increased resistance, or is it the same as before the problem?
 
Okay, so setting the cut-off voltage to 29V is fine. (Obviously, it's not the solution; it's just to understand the cause of the problem.)
I also asked to check whether turning the display off and on again when the battery is low maintains the Soc% value. Have you checked?
To better understand the cause, a few more questions:
Are you using hybrid mode?
Is Smooth Start enabled or disabled?
If enabled, what is the ramp set to?

Regarding the drop in assistance when the battery is low, I'll answer you later.
Yes, the SoC% value maintains. At first start after flashing, it calibrated (indicating 99), since then it shows the correct SoC% (currently at 3%, because I wanted to drain the battery completely). It shows same value (3%) when turning on and off again.
Here are my settings:
 

Attachments

  • pic1.jpg
    pic1.jpg
    117.8 KB · Views: 20
  • pic2.jpg
    pic2.jpg
    116.8 KB · Views: 17
  • pic3.jpg
    pic3.jpg
    101.9 KB · Views: 18
Error 30 is a communication problem between the display and the controller.
You write that with the stock firmware it doesn't give the error, but it doesn't work properly. You get full support at all levels, even at level 0.
Has it always been like this? Or did you update the display firmware and something went wrong?
Correct, if i write the stock firmware there is no error and works correctyl, but with FULL support on all assistance levels.

Yes, this is stock behaviour (for me at least).

You think this is a varstrom ekd01 display issue here? I dont know anyone to compare it with.
 
It looks like the controller is damaged.
The display probably stays on because it's receiving voltage from the controller on Vin.
The increased resistance when pushing the bike backwards is probably due to a mechanical problem with the large sprag clutch.
Have you tried pedaling with the assist level set to OFF? Do you feel increased resistance, or is it the same as before the problem?
Pedaling with the assist level OFF feels normal, only backwards rolling has increased resistance.
I also tried reflashing the previous firmware but it didn't make any difference.

I guess i'll have to buy a new controller and investigate the sprag cluch..
 
Correct, if i write the stock firmware there is no error and works correctyl, but with FULL support on all assistance levels.

Yes, this is stock behaviour (for me at least).

You think this is a varstrom ekd01 display issue here? I dont know anyone to compare it with.
I don't know, if you post the three zipped hex files of the stock firmware, I'll check if it works correctly with another type of display.
 
You think this is a varstrom ekd01 display issue here? I dont know anyone to compare it with
I use the Varstrom ekd01, and the update-5 firmware, and I don't have issues with support as you describe. On the Assistance settings page did you set Assistance level 5 (%) to BEFORE ECO? If not, you can get unexpected levels of support.
 
Last edited:
The latest master version is now tested, new version number v20.1C.6-update-5 released.
Release Open source firmware TSDZ2-v20.1C.6-update-5 VLCD5-VLCD6-XH18 · emmebrusa/TSDZ2-Smart-EBike-1

List of changes:
1 - Changed battery capacity SOC% calculation (same as 860C).
2 - Fixed a bug in the fifth level in hybrid mode.
3 - Increased MOTOR_CHECK_ERPS_THRESHOLD (E09 error).
4 - Improved battery voltage calculation and SOC reset.
5 - Startup assist changed and can be enabled/disabled from display.
6 - Added auto mode to Startup boost.
7 - Added maximum value to check walk assist speed limit.
8 - Changed the start and stop cadence ticks.
9 - Reorganized torque sensor calibration procedure.
10 - Decreased FW_HALL_COUNTER_OFFSET_MAX (Field weakening angle)
11 - Improved E03 cadence sensor error.
12 - Fixed the torque offset adj in eMTB mode.

Updated manuals.
Dear @mbrusa
thank you so much for your continuad work on this!
Especially in these ‚throw away - buy someting new‘ times, i appreciate so much that we get still improvement from you for our trusted older TSDZ2‘s!
Our 2 bikes run great with your latest firmware.
I just rediscovered that somewhere in the last Versions of your firmware you made torque readout (and therefor calibration) so much easier with enabling it on walk assist in assist-level 0. Thank you for that!
It makes it possible to quickly check, if the min/max values did not drift - and if so, a qick reflash can fix that. (But in the case of my 2 bikes, they are amazinhly stable)
So thanks again - and be well!
 
Thanks @endlessolli, I'll continue as long as there's something new to do or improve.
The funny thing is that over the last year, I've prioritized the stock displays I no longer use, neglecting the 860C version that I use on my bikes.
But I'm already catching up; more news on that soon.
 
Ok, so I finally managed to drain the battery below 45V. It seems your tip worked, I set the voltage cut-off to 29V and now I still have support on lower voltages. The battery bars show the Soc correct.
However, I noticed a very strong power loss now when I am at lower voltages.
Today I cycled up a hill and even at level 04 there was little assistance when going >15 km/h. I remember having less power at low voltages because of current cap, but I don't remember it being that bad. When starting from 0 km/h uphill I have a good amount of motor support, but after about >15 km/h level 04 feels like level 01 and I have to pedal with tremendous amount of work to get to higher speeds.
Battery max current in configurator is set to 18A, motor max power is at 700W. Battery voltage measured at 43V.
Is there a way to circumvent that behaviour?
I believe the issue you encountered with the shutdown voltage is due to the comparison being made with the raw ADC voltage, which is therefore subject to interference. On the other hand, there's no other way to do it; there's no time for a filter.
I made a change that should solve the problem.
Now the shutdown voltage is no longer tied to the cut-off voltage.
It's set to 20 volts, the minimum value needed to save Soc% when the display turns off.
It's therefore possible to set the cut-off voltage to the correct value for the battery in use (39 V for a nominal 48 V battery).

Regarding the drop in performance when the battery is low, this could be normal (with a Soc of 3%, you'll get a few dozen watts).
The Soc should never be lower than 10%.
It also depends greatly on the battery's characteristics and cell type.
Keep in mind that when the voltage approaches the cut-off value, the current is limited.
At a high current (18 A), a voltage drop of up to 3 volts can occur. If the cut-off voltage is set to 39 V, the current is already limited at 42 V (39 + 3).

There are other considerations regarding the drop in power as the voltage decreases, and they depend on the assist mode used.

In Power mode, the rider's power defines the motor's power.
The current is calculated from the target motor power / battery voltage.
Therefore, as the voltage decreases, the current increases. For the same pedal input (torque * cadence), the motor power remains constant (up to the maximum current and cut-off voltage limits).

In torque-based modes (Torque, eMTB, and Hybrid), the pedal input (torque) defines the motor current.
The power is calculated from the target motor current * battery voltage.
Therefore, as the voltage decreases, for the same pedal force (torque), the motor's power decreases. For example, with a calculated current of 10 A and a voltage drop of 2 V, with a charged battery you get 10 * (54.6 - 2) = 526 W, while with a flat battery you get 10 * (39 + 2) = 410 W. This is a significant difference.

To compensate for this difference, so that the rider doesn't feel any loss of power as the voltage decreases, I've added a new feature.
There are two parameters, found in the configurator at the bottom of the "Assistance settings" tab:
1 - Torque, eMTB, Hybrid on current / power
- current, like previous versions, with power decreasing as the voltage decreases.
- power, the current is recalculated to maintain a constant power as the voltage decreases, within the limits of maximum current and the cut-off voltage.
2 - Reference voltage
Reference voltage value, used to calculate the target power to maintain.
For more details, see the manual.

In all modes, to achieve constant power as the voltage decreases, also check the consistency between maximum current and maximum power.
Example: if you set the maximum battery current to 15 A, the maximum power with a flat battery will be 15 * (39 + 2) = 615 W. This is the value to which the maximum motor power should be set.

If you'd like to try it, you can download the master version.
https://github.com/emmebrusa/TSDZ2-Smart-EBike-1/archive/refs/heads/master.zip
 
That's great news, thank you for the changes!
Will try as soon I am back home from vacation.
 
Okay, so setting the cut-off voltage to 29V is fine. (Obviously, it's not the solution; it's just to understand the cause of the problem.)
I also asked to check whether turning the display off and on again when the battery is low maintains the Soc% value. Have you checked?
To better understand the cause, a few more questions:
Are you using hybrid mode?
Is Smooth Start enabled or disabled?
If enabled, what is the ramp set to?

Regarding the drop in assistance when the battery is low, I'll answer you later.
Hello mbrusa,
this is the same issue we discussed here #3,443 I can confirm that when I now set the cut-off voltage to 29V, I can use the battery’s full capacity (until the BMS shuts down completely), whereas with the original cut-off setting of 39V, the motor started shutting down as early as 46V.
I’d also like to mention that in my case, the display didn’t turn off—it kept working—but the motor suddenly stopped.
 
Last edited:
Yes, indeed, I remembered another similar case, which is why I looked into it further.
Now, if you want to try updating to the master version, it should work correctly even with the cut-off voltage set to 39V.
I also added the undervoltage error E01 (shared with the overvoltage error) to immediately understand the source of the problem, should it happen again.
 
Hello, I recently installed the OSF on my du250 (german variant of tsdz2 I believe), and it's been working fine except for one issue. All the values on the display are horribly inflated, e.g. speedometer shows a value of 60 something when going at 30, adc calibration values are 478 and 868, battery voltage is 88...

I've set the wheel value (on the screen) to the max possible, magnet count is at 1. Both of those settings influence the data values. Speed limit seems to not be affected by the speedometer value. Wheel circumference has been set in the java configurator.

Could this be an issue with the du250 or is it possible I did something wrong?
 
Hello, I recently installed the OSF on my du250 (german variant of tsdz2 I believe), and it's been working fine except for one issue. All the values on the display are horribly inflated, e.g. speedometer shows a value of 60 something when going at 30, adc calibration values are 478 and 868, battery voltage is 88...

I've set the wheel value (on the screen) to the max possible, magnet count is at 1. Both of those settings influence the data values. Speed limit seems to not be affected by the speedometer value. Wheel circumference has been set in the java configurator.

Could this be an issue with the du250 or is it possible I did something wrong?
Too close magnet to sensor. Magnet should be c.a 1cm from triangle symbol on sensor.
 
Back
Top