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

... Still few things to clarify:

...
1 No, stock Firmware will give overvoltage error. You don't need or connect a battery to flash the controller with OSF. STlink flashtool use the USB Voltage of your PC
2 Capacity isn't easy to advice, because this depends of a lot of things, but imho with 500Wh it must be possible to do 40km distance.
 
Great community you have here! After going through latest few pages of the thread I have pretty clear idea what to order: 250W sticker 36V TSDZ2B motor for legislation, VLCD5 display for compatibility with OSF + 48V battery for increased top range at high cadence. Still few things to clarify:

1. Am I able to test run stock 36V motor with 48V battery out of the box? Or at least connected to flash tool to enable 48V functionality without having extra 36V battery to power motor and controller on?
2. What capacity of a battery would you recommended for 40 km commute cycling with high level of assist?'

Thanks in advance!
I have 48v motor and Battery 48v 13ah. On the flat using assist level 2&3 will easily give me 45-50 miles range from a single charge, probably much more as never managed to run it flat as most rides are no more than 30 miles. Once did 35 mile mixed off road with moderate elevations and still had power left and no reductionin assistance. Battery not needed to flash OSF to the motor
 
I have flashed it on my bike now but I have diy 16S battery and i upgraded the Caps to 100V on the controller. It works but I would like to set the currect min and max voltage for my battery. I can set the correct cut off voltage but the max voltage is limited to 63V , but I need 67,2V. I am using the SW102 Display
 
I have flashed it on my bike now but I have diy 16S battery and i upgraded the Caps to 100V on the controller. It works but I would like to set the currect min and max voltage for my battery. I can set the correct cut off voltage but the max voltage is limited to 63V , but I need 67,2V. I am using the SW102 Display
I can adjust the voltage readout and reduce it till 67,2V shows 63V on the screen. But would it also mess with the controller power control or something ?
 
By max voltage do you mean "Reset at voltage"?
This parameter is used only for the automatic reset of the Wh with the battery fully charged.
It must be 0.5 to 1.0 Volts less than the max battery voltage.
It has no influence on the operation of the motor.
So if you have set 63V and you turn off the display and the voltage is higher, when you turn it on again the Wh already consumed are reset to zero.

On the other hand, by decreasing the voltage calibration % (minimum 95%), the displayed voltage will be lower than the actual one, but also the displayed power and the Wh consumed.
Again, no influence on the operation of the motor.
 
I am an infrequent rider of my OSF TSDZ2 and I am running 20.1C 1 or 2 IIRC. Have the more recent versions finally enabled auto reset of the SOC to the existing battery voltage? I looked at the wiki and couldn't really tell. I am still hating having to go into the menu settings to manually reset it when using less than full charges.
 
I am a big fan of the OS firmware on my cargo bike so I decided to build a commuter also. Unfortunately I am not able to read or flash the firmware on the new TSDZ2. Same PC and same ST link. Works on the slightly older 36V with VLCD5 (although fails with RST connected) but does not work on the new 48V with the VLDC6. New stock from PSW Power a few months ago.

I have scanned the forums. Have tried with and without RST. I am unable to power up either display from USB power. Could this be a new batch of controllers? Not sure what else to try.

Anyone got any suggestions?
 
.... I am unable to power up either display from USB power. Could this be a new batch of controllers? ....
imho you don't need to power up the display for flashing. It could be that in that case the load is to heavy for the USB
Normally you only need to connect the STlink to the controller and flash OSF.

But you aren't the first that complains about connection problems, so there could be a chance that something has changed on the controller too.
 
I am a big fan of the OS firmware on my cargo bike so I decided to build a commuter also. Unfortunately I am not able to read or flash the firmware on the new TSDZ2. Same PC and same ST link. Works on the slightly older 36V with VLCD5 (although fails with RST connected) but does not work on the new 48V with the VLDC6. New stock from PSW Power a few months ago.

I have scanned the forums. Have tried with and without RST. I am unable to power up either display from USB power. Could this be a new batch of controllers? Not sure what else to try.

Anyone got any suggestions?
I flash with battery on and display on
 
I am an infrequent rider of my OSF TSDZ2 and I am running 20.1C 1 or 2 IIRC. Have the more recent versions finally enabled auto reset of the SOC to the existing battery voltage? I looked at the wiki and couldn't really tell. I am still hating having to go into the menu settings to manually reset it when using less than full charges.
Yes, in the latest versions, just set "SOC calculation" to "auto".
There is both Java Configurator and 860C version.
 
Hi, does anyone have any tips for setting up a VLCD10 with the configurator? (I've got a couple of units to try out.) I tried just leaving it set to VLCD6 and swapping it out for the VLCD10. Worked fine the first time I took it for a quick spin. But now it doesn't report the battery level percentage correctly and its shown as 0%....even though its 70%. Does anyone have any ideas?
 
Hi, does anyone have any tips for setting up a VLCD10 with the configurator? (I've got a couple of units to try out.) I tried just leaving it set to VLCD6 and swapping it out for the VLCD10. Worked fine the first time I took it for a quick spin. But now it doesn't report the battery level percentage correctly and its shown as 0%....even though its 70%. Does anyone have any ideas?
where did u get vlcd10 ? factory set up for tsdz2? how many battery bars and power assist levels ? only battery bar is not working?
 
Hi all! On my wife's bike with the latest firmware, E02 sometimes occurs. In this case, the engine help is disabled. For to go, she need to turn off and turn on the system again. It doesn't happen often, but it's very annoying. The torque sensor is calibrated correctly and the motor runs very friendly in all modes. I think that the problem of the error is related to the heating of some components inside the engine. So far I haven't been able to trace the cause. But I don't think that the real problem is so significant that it requires completely turning off the engine assistance. And in this regard, I have a question: How to completely disable the function of disabling engine assistance in case of an errors? Or at least increase the shutdown timeout? 1 second, which is currently set in my configuration, is not enough. Thanks.
 
E02 has no trip times or shutdown timeouts, it remains in the memory only if the failure that caused it is present.

If E02 occurs when you turn on the power before putting your feet on the pedals, it is caused by a calibration error.
Check the "Pedal torque adc offset" value, with the motor cold and hot, if there is a lot of difference enter an average value.

If, on the other hand, E02 occurs while using the bike, there is a problem with the torque sensor.

It is possible to maintain assistance in the presence of a sensor error by enabling "Assist with error", and if desired, save the choice in eeprom, this cannot be done with the configurator but only on the display.
How to do it can be found in the manuals.
 
I'm not sure if this is a bug, but I just flashed the SW102 and TSDZ2b with the latest OSF firmware, specifically the TSDZ2-v20.1C.4-860C-update-2. I haven't tested it extensively, but everything appears to be working as expected when compared to another bike equipped with the 860c display.

One difference I observed is that the SW102 does not have an option for field weakening in the menu. it seems like field weakening is already enabled.

I noticed that if the display setting is set to imperial units, the number of assist levels is limited to 5. On the other hand, if SI units are selected, 9 assist levels are available.
 
This is the message on the display and the assist is disabled. After turning it off and on, the bike again rides 15 kilometers of MTB. What is it and how to fix it?
 

Attachments

  • 20230506_111826.jpg
    20230506_111826.jpg
    574.4 KB · Views: 12
Well, this sort of works but not as I expected. I set it to auto and "voltage" and it captures a fairly accurate initial SOC but then varies in real time up and down as the motor current causes the voltage to dip under power, then rebound as you coast. The way I had envisioned this to work would be that with the watt hours and voltage set and saved in the display, then when you pop on the battery in an intermediate SOC the system would estimate remaining WH % and then reduce by WH usage until depleted. So voltage would only be used to establish the initial SOC, not to keep running the SOC calc in real time since voltage is never stable while underway. My CYC bikes operate as I describe so I am not sure why we can't do this in OSF? Perhaps there is some reason I am not aware of?

Yes, in the latest versions, just set "SOC calculation" to "auto".
There is both Java Configurator and 860C version.
 
Does anyone know what this could be besides wiring or pedal being pushed at bootup?
It is a friend's bike, on a new install. He doesn't have brake sensors.
 

Attachments

  • ERROR PHOTO.jpeg
    ERROR PHOTO.jpeg
    321.1 KB · Views: 14
This is the message on the display and the assist is disabled. After turning it off and on, the bike again rides 15 kilometers of MTB. What is it and how to fix it?
is this dz41 ? is it working okay besides 15km limit?
 
is this dz41 ? is it working okay besides 15km limit?
Yes, this is dz41. 15 kilometers is just an example. The bike can work normally for several days. Then suddenly this error appears on the display and the assistant turns off. Turning it off/on solves the problem. I don't know what these the error code? Is this a display or motor fault? How to fix it?
 
Well, this sort of works but not as I expected. I set it to auto and "voltage" and it captures a fairly accurate initial SOC but then varies in real time up and down as the motor current causes the voltage to dip under power, then rebound as you coast. The way I had envisioned this to work would be that with the watt hours and voltage set and saved in the display, then when you pop on the battery in an intermediate SOC the system would estimate remaining WH % and then reduce by WH usage until depleted. So voltage would only be used to establish the initial SOC, not to keep running the SOC calc in real time since voltage is never stable while underway. My CYC bikes operate as I describe so I am not sure why we can't do this in OSF? Perhaps there is some reason I am not aware of?
The operation you described is that of the setting in Volts.
If you've set it to "auto", there's a problem.
What value is set to ""?Auto reset%
I too have an 860C and it works fine.

Copy/paste from manual:
Calculation
Choice of the method for calculating the remaining battery percentage.
Auto - soc% calculation with Wh used.
Automatic reset at power on when the soc% calculated with Wh consumed is different from that calculated with the voltage (+/- "Auto reset%"), useful when you put a not fully charged battery.
Wh - soc% calculation with Wh used, reset only with fully charged battery (100%).
Or manual reset.
Volts - soc% calculation with battery voltage, it is less accurate than the other methods.
It can be useful if you have two batteries of different capacity. To obtain a correct correspondence between soc% and voltage, it may be necessary to adjust the values of “Reset at voltage” and “Low cut-off”.
 
..
One difference I observed is that the SW102 does not have an option for field weakening in the menu. it seems like field weakening is already enabled.
..
Yes with SW102 Field Weakening is always enabled, there is no item in the menu to disable it.
Same for other functions.
The reason for this choice is that SW102 often crashes when navigating the configuration menus.
It also happens with the 860C but but to a lesser extent.
I don't have a SW102 to test and I didn't understand the cause, but one thing I understood, increasing the menu items, the problem gets worse, so I preferred not to add other items.

I noticed that if the display setting is set to imperial units, the number of assist levels is limited to 5. On the other hand, if SI units are selected, 9 assist levels are available.
Truly?
There is no link between the number of levels and units.
I don't know what to say, with 860C it works correctly.
 
Does anyone know what this could be besides wiring or pedal being pushed at bootup?
It is a friend's bike, on a new install. He doesn't have brake sensors.
Hi Jeff.
In more recent versions it is changed to "Keep pedals and brakes free".
It is not the signaling of an anomaly, it is only a reminder when the display is switched on.
The startup screen closes when communication between the display and motor is established.
If it does not close, there is no communication, on a first installation it is probably a problem with the wiring or the connectors.
 
Back
Top