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

[Handcyclist]

I've also installed v20.1C.5-update-2 with the 860C display (36V, 250W TSDZ2B) and cadence mode is no longer working, it was fine with the previous v20.1C.5-update-1 release. It reports potentially 70W of motor power whatever assistance level is selected.
I normally use hybrid mode on my handcycle and that is working well but I like to be able to select cadence mode so I can show the difference between cadence and torque sensing as many handcycles use the Bafang BBS01

 

[Simon76]

Hi guys! After all the reading and two days of trying with help of stupid AI I decided to talk with real people.
I've bought two TSDZ2B with 860c. After first ride I noticed very poor changes in assist level:
1 - too strong
2- barely noticeable change
3- ok
4- barely noticeable
5- quite OK.

Support has sent me .s19 file to correct this. Well it was better but I wasn't satisfied.
So I tried and installed OSF to motor, v20.1c.6-update 6. It went OK, but behavior of motor was like catapult on level 1. I've set After turbo to be my level 5, since Java configurator only has 4 level to change. I must say, that I don't need all the functions on display to be changed, I would change them only once, twice via STVP. So my main question is,is it possible to use stock 860C to communicate with motor with OSF, like VLCD5 is capable of.
Thank You all!

 

[michasmuamua]

To use 860C you need to flash OSF firmware to it - you need a special cable to it.

 

[Elinx]

....
I've bought two TSDZ2B with 860c. ....
.....installed OSF to motor, v20.1c.6-update 6. It went OK, but behavior of motor was like catapult on level 1. I've set After turbo to be my level 5, since Java configurator only has 4 level to change.........
So my main question is,is it possible to use stock 860C to communicate with motor with OSF, like VLCD5 is capable of.

With a stock 860C for stock Tsdz2, then you must have the same possibities as each other stock display for Tsdz2. You can manage these settings with the light button as you can see inside the display manual.
For editing assist and other settings inside Java configurator you need the configuration manual
You can find all these manuals inside the download too

To use 860C you need to flash OSF firmware to it - you need a special cable to it.

Not with a stock Tsdz2 860C display
For flashing you need a Bafang version of the 860C

 

[michasmuamua]

I have 860C from PSWPower and I flashed without problem

 

[dgc]

Yep, as on page 115 of this thread I had no problem flashing the Bafang UART 860C using a CP2102 module with a dc - dc step up power module 3 5 12v to 19 - 36v boost converter using APT burn tools.

 

[Simon76]

So If I understand correctly flashed motor with OSF, configured in Java configurator works with VLCD5, but does not work with unflashed 860C. I would like to keep original graphics on 860C, but would like to have upgraded function of motor itself.

 

[Elinx]

So If I understand correctly flashed motor with OSF, configured in Java configurator works with VLCD5, but does not work with unflashed 860C......

You said here you flashed OSF v. 20.1c.6-update 6 and used 860C succesfull with java configurator

As I said. If your 860C does work with stock Tsdz2 firmware, it does too with OSF and Java configurator. Same as wih Vlcd5, you don't need to (or can't) flash 860C, but only the motor contoller. For the best custom settings you best can read and use the manuals.

If you want to use a 860C without java configurator, you need to buy another 860C, which is specific for Bafang and flash the 860C version of OSF. In that case you need to flash the motorcontroller and the 860C display as @dgc shows here

 

[Elinx]

I have 860C from PSWPower and I flashed without problem

Was dit a separated buy, or together with Tsdz2?

....Bafang UART 860C using a CP2102 module...

You said Bafang UART. You mean it should work with stock Bafang firmware? Or did it work with stock Tsdz2 firmware?

 

[dgc]

I brought the 860C Bafang UART displays and reprogram them with the setup equipment as described previously, you can also buy the 860C preprogrammed to suit the TSDZ2B I believed, I did take a chance that the 860C's were programmable as I believe some you can't but not sure if that is correct or not. My start point was with this video a few years back so things may have changed now, but looking at the STVP software on my laptop it still has the same settings.

 

[Elinx]

...... you can also buy the 860C preprogrammed to suit the TSDZ2B I believed, .....

Correct, this version you can't reprogram. It does work with Tsdz2 only, so you can use Javaconfigurator for OSF.
That is why you see the specific 850C display choice in basic settings tab.

 

[PeteCress]

Years ago, I attempted to re-flash the OSF firmware on my TSDZ2 and accompanying 860c.

I succeeded in flashing the 860c, but struck out on the motor unit - leaving it inop without the corresponding firmware on both devices.

Now I am trying again, but the world has moved on version-wise.

I see a v6 for the 860c, but don't know what to search for for the motor - and I am having problems even comprehending, much less navigating the GitHub UI.

Can anybody point me to the exact, precise, letter-for-letter file names for the latest-and-greatest 860c and motor emmebrusa files that I need to feed to ST Visual Programmer?

 

[mbrusa]

I've also installed v20.1C.5-update-2 with the 860C display (36V, 250W TSDZ2B) and cadence mode is no longer working, it was fine with the previous v20.1C.5-update-1 release. It reports potentially 70W of motor power whatever assistance level is selected.
I normally use hybrid mode on my handcycle and that is working well but I like to be able to select cadence mode so I can show the difference between cadence and torque sensing as many handcycles use the Bafang BBS01

I don't follow the forum much during the summer.
Now I'm on vacation, I have my bike with me, and I checked.
It's true that with the latest version, Cadence mode no longer works, nor does eMTB mode, as reported in another thread.
Sorry, I'll check when I get home.
However, I can say that after testing it extensively, the new Extended Boost function in Power mode works very well.

 

[Simon76]

Elinx, thank you very much for explanation. Now everything becomes more clear.
Well, I've configured some settings in Java Conf, and to avoid catapult start on level 1 when level 5 was set to "after turbo", I've set level 5 to "before eco". 860C received the commands, it works when levels are used and the motor is running, but when I put to level 0 (no motor), after few seconds errors started to show: 02, 03 and 04 and no speed is displayed. As soon as I start to pedal on any level, all the errors disappear and the speed is displaying again. Looks like I have to find the best version of FW or hex file for this version of 860C that will work perfectly, configured in Java C.

Another thing, dgc pointed out his post on page 115, where in STVP in Data memory tab there are certain double digit values that set the voltage and amperage of battery. But when I load certain hex file to motor controller, totally different values are set in this tab's lines.
So here is my thinking: I set the parameters in Java C and do only Compile part and cancel the flashing part. Compiler writes hex file in "release" sub folder, then I open this hex file in SVTP, but write only Program Memory tab in motor's controller and leave Data Memory tab intact. Or I am in totally NO-GO area...

 

[Elinx]

.....after few seconds errors started to show: 02, 03 and 04 and no speed is displayed. As soon as I start to pedal on any level, all the errors disappear and the speed is displaying again. Loo.......

This is normal behavior, because you have ODO compensation. All displayed data, like Capacity, Voltage, will be converted to speed, so your distance is running up too. With the ODO compensation this distance will be subtracted from total distance by stopping to measure speed for short time. The number of data you want to be displayed you can set on "advanced settings" tab. But how more time is needed for displaying this data, how longer the speed will be zero.

.... set the parameters in Java C and do only Compile part and cancel the flashing part. Compiler writes hex file in "release" sub folder, then I open this hex file in SVTP, but write only Program Memory tab in motor's controller and leave Data Memory tab intact.....

This is exactly what the compile&flash script does too, but full auto with cmd mode. But indeed program and data file. The data file is the data you have entered in java configurator.
If you run de Gui mode you have to be sure you have the right settings before you flash hex files.
If you don't flash data too, no new java changes will happen.
For working with the 860C version of OSF this will be OK, because the data will be done by 860C, so you want to be sure nothing will change with updating the FW version.
Most easy and safe method is running the script with "compile and flash" and rename and save the last ini from "experimental settings" folder if you are satisfied with these settings.

 

[docw009]

Learned something new about OSF today. The OSF won't boot up if it detects the brake switches closed at power-on.

I added Shimano MT200e hydraulic brakes to one of my bikes. The "e' denotes magnetic brake switches, which are in a plastic tab attached to the mounting screw.. If the plastic tab is not lined up when the lever is attached, the brake circuit can be turned on. First I thought Shimano did the brakes normally on. Figured it out,

Finger tip pressure activates the brakes now. The bike stopped better with caliper brakes. That always seems to happen.

 

[dgc]

Learned something new about OSF today. The OSF won't boot up if it detects the brake switches closed at power-on.

I added Shimano MT200e hydraulic brakes to one of my bikes. The "e' denotes magnetic brake switches, which are in a plastic tab attached to the mounting screw.. If the plastic tab is not lined up when the lever is attached, the brake circuit can be turned on. First I thought Shimano did the brakes normally on. Figured it out,

Finger tip pressure activates the brakes now. The bike stopped better with caliper brakes. That always seems to happen.

View attachment 392428

Yes, I've seen the add-on sensor kit before for the MT200 brakes, look good, but I did use the standard Tongsheng brake sensors that suit the VLCD5, moved on now, I am using the Clark Sync-2E or the HD-M3000 Plus e-bike brakes and just splice in brake cables into the standard display cable. On my hard-tail with standard brakes I am going to try some NFOX 2A GT267 brake levers that have sensors and see if they work OK with the existing four pot calipers.

 

[brancky3]

Hello all!
I have a TSDZ2B (36v 250w, with 36v 17.5ah rack battery) with an EKD01 display on OSF v20.1C.6-update-6. I'm using the bike to commute to/from work, and for the most part it's running great. I have everything limited to 250 watts and 27km/h (speedo is slightly off, this is 25km/h confirmed on radar) to stay legal in France. My problem is with a pretty intense hill on my way home from work, it's about 20% grade which is extremely difficult without electric assistance. I logged my data from my ride home yesterday and it's very clear that the readings are substantially lower starting around 5:31PM, which is when I'm in a lower gear to get up the hill. There's no way I'm only putting out 6 watts myself during this climb as my data shows... I'm using either my 48t or 52t rear sprocket for most of the climb in order to keep my cadence decently high and not bog down too much.

Is there anything I could change in the parameters to troubleshoot this? Enable field weakening maybe? I'm going to try eMTB mode today to see if this is any better for the extreme incline

 

[Elinx]

.....

Is there anything I could change in the parameters to troubleshoot this? .....

I have answered here