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

[mbrusa]

With the new software (v20.1C.1 safety updates) there is the same behavior (wheel rotates after brief pressure on the pedal permanently with 25 km/h). A test with disabled "Startup assistance without pedaling" led to the same result.
After that I installed the v20.1C again and everything works as expected.
Since no one but me seems to have the same problem, I don't think any troubleshooting is necessary. I just stick with v20.1C and everything is ok.

Best regards
Rainer

When you reported this problem, I was unable to reproduce it.
Now the differences between v20.1C and v20.1C.1 are few, I think it is possible to identify the cause.
Can you PM the configuration .ini file?

Bug found! Problem solved.
It was in the "Torque sensor calibration bug fixed" modification required for SW102 display. With the standard displays it affected the calculation of "Torque adc offset" at power on, causing an error in the calculated value.
v20.1C.1 updated.
Thanks to TR8 for reporting.

 

[Elinx]

......
Bug found! Problem solved....

Again thanks for your efforts to search, find and solve these kind of nasty bugs

 

[Sgarth]

Hi All, New here but have done two TSDZ conversions - both with VLCD6 displays. Recently changed one to 860C with OSF & no problem flashing the motor. I now want to flash the other with this OSF (VLCD6). Have downloaded the recommended software's from the Wiki page but cannot get Java Configurator to launch - It may have been covered elsewhere but haven't found a solution (this is a windows issue and can't find an answer) I have tried on 3 different WIN 10 PC's though I do think I had it running once as have been contemplating this for quite some time - so suspect something really simple.

 

[raylo32]

Maybe try to reinstall or update your Java.

Hi All, New here but have done two TSDZ conversions - both with VLCD6 displays. Recently changed one to 860C with OSF & no problem flashing the motor. I now want to flash the other with this OSF (VLCD6). Have downloaded the recommended software's from the Wiki page but cannot get Java Configurator to launch - It may have been covered elsewhere but haven't found a solution (this is a windows issue and can't find an answer) I have tried on 3 different WIN 10 PC's though I do think I had it running once as have been contemplating this for quite some time - so suspect something really simple.

 

[gfmoore]

Thanks for the advice.

I've gone through the manual with a fairly fine tooth comb and starting to get it. For my own purposes I've edited it a little adding in my own values and research i.e. a glossary. Still quite a few questions, but I guess there might be a little bit too much noise from me at the moment (I'm just excited is all!)

Just starting to look at the code. Is there a toolchain reference somewhere? I use windows and VS Code. Can use Linux if required.

 

[raylo32]

Don't get too excited and burn up your motor throttling up steep hills! Maybe have a look at the thread on hardware cooling to get an idea of the damage than can be done. IMO, you really risk cooking your motor until you have installed some sort of cooling mods. I'd run with a temp sensor at least until you get that dialed in, then you can more safely swap it back to throttle.

Thanks for the advice.

I've gone through the manual with a fairly fine tooth comb and starting to get it. For my own purposes I've edited it a little adding in my own values and research i.e. a glossary. Still quite a few questions, but I guess there might be a little bit too much noise from me at the moment (I'm just excited is all!)

Just starting to look at the code. Is there a toolchain reference somewhere? I use windows and VS Code. Can use Linux if required.

 

[gfmoore]

Don't get too excited and burn up your motor throttling up steep hills!

Fair points. However, do you think that when I was running the stock 48v firmware on my 36v 250W motor that the throttle could cause any damage?

Gordon

 

[Anikea]

In my case it is not a temperature problem, it happened to me starting from a standstill with the engine almost cold. After the first pedal stroke, the display went out.
Back home, I checked the controller, there was low resistance between green and yellow. No apparent burn.
I replaced the controller, the display did not turn on anymore, there was no voltage, the fuse holder had a burnt terminal, probably a bad contact.
The motor has now been running for two weeks with modified v20.1C.3.

I've been driving the v20.1c.3 in the original version for about 500km without any problems. all failures I had read about were with lcd5 and while driving. Was your failure in the state with xh18? Now I'm unsure whether I should continue with the v20.1c.3, although I think everything is more perfect. Is the risk of failure very high? If you die with your modification, only the risk of failure has been reduced, I would like to install it, can you make it available to me?

 

[gfmoore]

Still don't know why I only get an on/off effect for the throttle?

I’ve had a quick look in the code and it seems as though the throttle values are mapped from min to max somewhere around 1V to 3.5V (47 to 176 as an 8-bit value % of 5V). I think your button throttle might be very close to the top of this range for both buttons, so you wouldn’t notice much difference.

It’s a pretty easy tweak and recompile if you need to expand that range.

Yes found it in main.h (My values were 160, 253 so yes). I think it might be best to change the resistor values in my controller. Thanks for the insight.

 

[gfmoore]

When charging, the charger should be connected to the battery first, and then connect the charger to the mains.
Upon completion or on any other occasion, the charger should be disconnected from the mains first, and then disconnect the battery from the charger.

Thanks for the clarification. :thumb:

What do you think about isolating the battery from the motor whilst charging, or does it not matter?

 

[gfmoore]

Sorry, so many questions and queries :sigh

I set the assist levels to 3 and changed the 3 values in each of the assist options as I postulated in a previous post.

I closed and restarted the display. I press up and down and still get 9 levels. Is this by design?

Went to the bike to adjust a few settings. I'd had a look at the code and the limits were there (mainscreen.c line 610 etc.) Noticed that my settings for the levels had disappeared from yesterday and entered them again and now it all displays with limits as it should.

Very weird and no doubt my bad, sorry

 

[gfmoore]

Don't get too excited and burn up your motor throttling up steep hills!

Fair points. However, do you think that when I was running the stock 48v firmware on my 36v 250W motor that the throttle could cause any damage?

Gordon

Having changed the displays to show what I wanted I tested again with Max power 450W and didn't see any difference in output. However, I did see that Motor Speed was showing 650 in RED. That doesn't look like something I want?

 

[Blacklite]

Having changed the displays to show what I wanted I tested again with Max power 450W and didn't see any difference in output. However, I did see that Motor Speed was showing 650 in RED. That doesn't look like something I want?

On a stand or actually riding? I’ve never tried the 36V motor at 48V, but many people comment about how they like the high revving nature of that setup. The 36V motor running on 48V will of course spin faster than a normal setup, but i don’t imagine it sustains that speed under load, whereas on a stand it might easily hit that speed.

In an case, the colours on the display are based on showing reasonable limits purely based on the numbers, not allowing for the situation. 650erps is effectively a cadence of very close to 120rpm at the crank - not sure many can maintain that!

 

[Blacklite]

650erps is effectively a cadence of very close to 120rpm at the crank - not sure many can maintain that!

Should also explain - 650 electrical rotations per second (erps) is 81.25 motor shaft rotations per second as the motor has 8 poles. Then the motor has a 41.4x reduction to the crank. 81.25 divided by 41.4 is 1.96 revs per second, multiply by 60 to get rpm - 117.75. I think I’ve got that right :$

I’d assume most cyclists would run their gearing so they pedal somewhere between 60-90 rpm, maybe a bit more for some. Certainly from my experience gearing so the motor sits in that range seems to be best.

 

[gfmoore]

On a stand or actually riding?

It was on a stand.

But I've just come back from a 20km ride up and down hills and I'm delighted at the performance (on power mode only so far). Having three assist levels worked really well for me. I think, though my eyesight isn't great anymore, that the Motor Speed was going into the yellow at about 240 on climbs. I (the bike, us) got up a very steep climb at the end of the ride, one I never thought I'd ever get up, but I (we?) were at our limit, I could have done with just a bit more power (and so say all of us!)

BUT, the throttle is useless. It works, but so slowly. When on stock it was great, but now I might as well not have it. (I haven't yet changed the resistors, but that doesn't matter for this experiment.) This is a real disappointment. Does anyone use the throttle with the OSF or does everyone have a temp sensor? If the throttle is turning the motor on the stand at a good rate, what is happening on the road. It's as though the torque? has gone.

However, this system has got me into a bit of countryside around where I live that my legs alone would never have managed and I can't thank you people enough for all the work that you have put into these developments, it's just fantastic.

 

[mbrusa]

I've been driving the v20.1c.3 in the original version for about 500km without any problems. all failures I had read about were with lcd5 and while driving. Was your failure in the state with xh18? Now I'm unsure whether I should continue with the v20.1c.3, although I think everything is more perfect. Is the risk of failure very high? If you die with your modification, only the risk of failure has been reduced, I would like to install it, can you make it available to me?

It may be that the first version v20.1C.3 for stock displays works without problems but it is better not to risk it.
For those who want to try it here is the modified v20.1C.3-NEW version.
https://github.com/emmebrusa/TSDZ2-Smart-EBike-1/archive/refs/heads/master.zip
Before releasing it officially, I expect some positive feedback.

 

[Blacklite]

If the throttle is turning the motor on the stand at a good rate, what is happening on the road. It's as though the torque? has gone.

The firmware regulates the motor current based on throttle position, not the speed generated, so the speed it gets up to unloaded will be radically different to that under load.

The only thing I can think that would make it underwhelming compared to what you had on stock firmware would be that the stock firmware had much higher current/power limits. Also worth checking you are not in street mode with a much lower power limit.

I don’t use a throttle so can’t really give more help sorry. I did flirt with the idea of one, but realised that having the temperature sensor so I could turn up the power limits safely was better for me. If I need walk assist that’s available without a throttle, and if I need a break from pedalling can use the cruise function. Also it keeps it closer to legal - if it’s pedal assist only it’s much harder to classify it as a motorbike.

 

[Lii]

Someone tested the firmware with a 500C display? I am interested in the operation of the display only with the basic functions of displaying data like the factory firmware. Thanks.

Up!

 

[Elinx]

...
Someone tested the firmware with a 500C display? ....

imho it should work with OSF for stock display, if the i/o protocol is the same as from vlcd5, vlcd6 or xh18.
(I know that the specific (not Bafang) sw102 for tsdz2 did work too)
Maybe the batteryindicator and error notification will differ, so you must find the right setting for that.
I think Enerprof is the only shop that sells this display for default tsdz2, but........... their tsdz2 motors have a new 2020 controller which you can't flash. But a combination of that C500 with old controller could work.

 

[raylo32]

Like you I don't really need or want to ride with throttle... BUT... if you saw my earlier post I said it might be a good idea to have one to get home in case the torque sensor bites the dust during a long hilly ride. But another thought... I wonder if cruise would work for that.. .i.e. pedal unassisted to a given speed and then engage cruise? I need to test it but I assume that should work. Or does the entire assist function to include walk, cruise and assist disappear if the torque sensor fails?

I don’t use a throttle so can’t really give more help sorry. I did flirt with the idea of one, but realised that having the temperature sensor so I could turn up the power limits safely was better for me. If I need walk assist that’s available without a throttle, and if I need a break from pedalling can use the cruise function. Also it keeps it closer to legal - if it’s pedal assist only it’s much harder to classify it as a motorbike.

 

[Blacklite]

Or does the entire assist function to include walk, cruise and assist disappear if the torque sensor fails?

I think they’d all still work even if the torque sensor fails. Should also work in cadence mode, where the assistance is just based on pedal cadence and nothing to do with the torque sensor. There is also a virtual throttle from the display.

Another option would be the “assist even with error” option Mbrusa has added to the firmware, that lets assistance be provided even if there are sensor errors.

 

[raylo32]

Cool... Do you have a cliff's notes on the virtual throttle? Mbrusa's .pdf doesn't really say how it works... or even really how to set it up... at least that I can find.

I think they’d all still work even if the torque sensor fails. Should also work in cadence mode, where the assistance is just based on pedal cadence and nothing to do with the torque sensor. There is also a virtual throttle from the display.

Another option would be the “assist even with error” option Mbrusa has added to the firmware, that lets assistance be provided even if there are sensor errors.

 

[Elinx]

... the virtual throttle? Mbrusa's .pdf doesn't really say how it works... ...

Only Casainho's build has a virtual throttle, so that is the reason you don't find this in the manual of mbrusa.
But "cruise mode" is at level 3-e04 and the "assist with error" at level 4-e04, so a lot of pushes must be done :wink:

 

[raylo32]

Ahhh, thanks. I got tired of the awful VLCD5 menu function so I have an 860C now... so cruise is a simple "hold the down button" with the Mbrusa build.

... the virtual throttle? Mbrusa's .pdf doesn't really say how it works... ...

Only Casainho's build has a virtual throttle, so that is the reason you don't find this in the manual of mbrusa.
But "cruise mode" is at level 3-e04 and the "assist with error" at level 4-e04, so a lot of pushes must be done :wink:

 

[Elinx]

..got tired of the awful VLCD5 menu function so I have an 860C now... so cruise is a simple "hold the down button" ... ......

:thumb: