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

ahagge said:
..... I'm hoping that someone has a way to avoid Windows for flashing the 850C/860C.

Any pointers?
Imho I think the easiest way will be a virtual OS inside Linux, because you need a "Windows only" program for unlocking the bootloader.
 
This is what I have been waiting. I have been using 860C display and software v1.1.0. I now installed v20.1C and this is like from another planet. I only had time to test the hybrid mode because the weather was terrible. However, I often have to drive up a steep uphill and slow down to almost zero every time I come to an intersection and see if others come out of the way. v20.1V assist right away from zero and it was very good to go on to continue the journey on the hill. v1.1.0 did not get anywhere. Many thanks to mbrusa for making this possible for the 860C display as well. :bigthumb: Thanks also to all the other participants in the development. :bigthumb:
Gotta try other assist modes when there is better wether.

One note: The lights had to be set to setting 5, so they lit all the time. At setting 0, they flashed. I do not have brake sensors installed.

I like this very much.
 
Does this fork of the OSF, suffer from the hideous overrun and ghost peddling of 1.0 ?
Thanks.
 
Waynemarlow said:
Can I ask a question, why the need to run a 15S battery, it pushes the voltage up into the realms of having to replace the capacitors on the controller, serves no real purpose now that the field weakening is starting to give good cadence up to about 120 rpm and basically makes the batteries more expensive as you have to use specialised BMS’s and chargers.

Wouldn’t the simplest thing be to simply use 48 volts or even 52 volts that most use ?

I will try to answer quickly, as the answer is not simple.

1 - Before making the 15s battery I asked people who were developing the firmware if there was any problem. Casainho told me that, from the firmware point of view, there was no problem, and that it would even be interesting to have someone test it.

2 - I do not advise anyone to make a 15S battery. Only if you are a person with a lot of knowledge of electronics. I am a telecommunications and electronics engineer.

3 - I make my batteries with BMS at home. DIY. They have bluetooth management. If I have a problem, I can always redo the battery. I just have to buy a new BMS.

4 - When I decided to make a battery with 15S, there was still no talk of "field weakening". At that time, the hypothesis that existed to have a good power, at a high cadence, was to increase the voltage.

5 - As you may know, the higher the current the motor consumes, the greater the heating. The higher the voltage, the lower the current, to obtain the same power. So we consequently have less heating.
I usually do off-road mountain trails. With quite a few climbs. In summer, the temperature is easily between 30 and 40 degrees centigrade in Lisbon, Portugal. Therefore, the engine easily reaches high temperatures.
The decreased heat in the motor was also a very important reason.

6 - If I have 15 cells instead of 14, I can have more than 7% energy, which allows me to have a lighter bike, with more energy. I use samsung 50E, 21700, 5000 mAh batteries. With a 2.1 KG battery (2P15S) I can have about 550 Wh of energy.

I take long trips on autonomy, bikepacking, and for me weight is important. Also for making mountain trails, weight is important. I like agile bikes.

7 - The battery, effectively never charges up to 63V. Generally, when installed on the bicycle, it never exceeds 62.5V.

The controller capacitors are 63V. But the manufacturer's specification always gives a tolerance of 5 to 10%. So we can get to 66 or 69V.

If we start with 62.5V, after a few kilometers the battery is already below 62V.

I've ridden more than 1000 km, and I haven't had any problems so far.
Another user of the forum has also ridden more than 1000 km without problems, with a 15S battery.

When I connect the battery to the motor, it is always without voltage, because it is turned off by bluetooth. It is to avoid voltage spikes when making the physical connection.

8 - BMS and chargers I buy on Aliexpress, and are a little more expensive than for 14s batteries. They are 5 to 10% more expensive, or even at no additional cost.

9 - As the nominal voltage is 55.5V, I almost always have voltages around 50V, which allows me to have a good performance most of the time.

10 - Finally, according to what Casainho says, the "field weakening- FW" removes some performance from the motor, although it allows a better management of the cadence / power.
What I noticed, in practice, is that with 15S, I don't need the FW, to have a good performance at high cadence. I also have a short time above the 100, 110 cadences.

Conclusion:

I am very pleased, so far, to have taken this option.

But I know I'm taking a little risk, as I am one of the few users of the TSDZ2, which uses 15S.

I hope I have answered your question.

Azur
 
I've been desperatly waiting for the fusion of the best from all FW forks and it is here 20.1C ! :thumb:

I could catch only few minor issues in 850C release:
- Clock field settings is not persistent after restart, when I set Battery Voltage after restart the Time field is preset
- Seems that my temperature senzor shows aproximatly 10 degrees more than the real value is.
 
elfnino said:
I've been desperatly waiting for the fusion of the best from all FW forks and it is here 20.1C ! :thumb:

I could catch only few minor issues in 850C release:
- Clock field settings is not persistent after restart, when I set Battery Voltage after restart the Time field is preset
- Seems that my temperature senzor shows aproximatly 10 degrees more than the real value is.

First report back from me riding my cargo bike with one small child. Hybrid mode is my new favorite. I need to have a really good go at tuning the assist levels, anything over 2 is generally too much for me! So I am clear both level 1 from torque settings and level 1 from power settings are used to make up level 1 "hybrid"? Also is boost used for hybrid mode or only power mode by itself?

Lost my ODO, should have thought about that before flashing otherwise all good. Of course I didn't realise street mode was enabled by default with 250W limit until I was committed going up a very steep narrow path, I thought I was going to snap the handlebars! The 3 yo was amused of course by all the noise dad was making
 
Yes, also from other feedbacks the default assistance parameters are too high, it will be that I have tried with a 36V motor and 36V battery.
Yes, the assistance parameters of the hybrid mode are the same as those used in the two modes, torque and power, combined at the same level.
To decrease the assistance at low cadence it is necessary to decrease the "Torque assist" values, at high cadence those of "Power assist".
Both must be decreased over the entire cadence range.
Startup boost is only used in "Power assist", it is not compatible with torque based modes.
"Hybrid assist" and "Power assist + Startup boost", are very different modes at low cadence.
With "Hybrid assist" the gradualness of the power is obtained by dosing the thrust on the pedals, with "Power assist" it is possible to maintain a constant thrust on the pedals and the gradualness at the increase in cadence is obtained by adjusting the Startup boost.
Startup boost is very effective and balanced, it is proportional to the thrust on the pedals, it never pushes more than necessary.
With only two parameters it is possible to modify the assistance response curve. I will prepare an explanatory Excel sheet.
Sorry for ODO, I'll add a note to the wiki, and also for street by default, but it was fun, come on.
 
elfnino said:
I've been desperatly waiting for the fusion of the best from all FW forks and it is here 20.1C ! :thumb:

I could catch only few minor issues in 850C release:
- Clock field settings is not persistent after restart, when I set Battery Voltage after restart the Time field is preset
- Seems that my temperature senzor shows aproximatly 10 degrees more than the real value is.
I'm glad you like the new version.
850C doesn't have an rtc and I haven't changed anything about it.
I did not understand what the problem is, you can explain better.
The next motor I will install will be with a temperature sensor, I will consider whether to add a calibration.
 
mbrusa said:
Startup boost is only used in "Power assist", it is not compatible with torque based modes.
"Hybrid assist" and "Power assist + Startup boost", are very different modes at low cadence.
With "Hybrid assist" the gradualness of the power is obtained by dosing the thrust on the pedals, with "Power assist" it is possible to maintain a constant thrust on the pedals and the gradualness at the increase in cadence is obtained by adjusting the Startup boost.
Startup boost is very effective and balanced, it is proportional to the thrust on the pedals, it never pushes more than necessary.
Thank you for your comments. I will try power only mode with boost as well then, maybe it is what I am looking for. Loving the fact the boost response curve is calculated, much more elegant. It certainly makes me realise that our other cargo bike with a Bosch motor (rated 250W) must be pulling 600-800 watts at times, maybe more. I am looking at ways to measure the current outside of the Bosch system but need to be careful, it's my wife's bike and breaking it will be looked upon very poorly

I will also calibrate the torque sensor (basic, since I have reasonable range 137-320)
 
mctubster said:
.......
I will also calibrate the torque sensor (basic, since I have reasonable range 137-320)
"reasonable" .... 183 is a "great" range if the used range is 160 :)
 
HughF said:
mbrusa said:
Hi HughF,
I managed to compile, I sent you the zip file for SW102 with private message, you can try and if you confirm that it works I release it. Thank you.
The hex file for the motor is the same as for 860C.
Received via PM, thanks. I will get this tested on Monday evening when I am back in front of my working bicycle (my hardtail mountain bike). The bike I have with me this weekend, although it has an SW102, the motor controller has filled with water and is now scrap :|

Hope it works
 
mctubster said:
It certainly makes me realise that our other cargo bike with a Bosch motor (rated 250W) must be pulling 600-800 watts at times, maybe more. I am looking at ways to measure the current outside of the Bosch system but need to be careful, it's my wife's bike and breaking it will be looked upon very poorly
The Bosch motor particularly if its a later 85Nm version is rumoured to pull over 850W at max. which is just under the Brose at about 920W
 
This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.

Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:

Great job mbrusa and everyone who has contributed code and improvements to this over the years.

EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
 
HughF said:
This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.

Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:

Great job mbrusa and everyone who has contributed code and improvements to this over the years.

EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.

Great!!! Did you try the boost?
 
Nfer said:
HughF said:
This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.

Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:

Great job mbrusa and everyone who has contributed code and improvements to this over the years.

EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.

Great!!! Did you try the boost?
Startup boost is enabled, but I was riding in hybrid mode just now and mbrusa said that the startup boost only works in power mode? I think that's what he said...

It's freezing cold now and too dark for me to try some more. I need to get properly dressed to handle the speed :lol:
 
First ride with SW102: Awesome!!! Great job Mbrusa and all developers. :thumb: :thumb: :thumb:
I ride with Power Assist and boost enable and it is fantastic, exactly what I was looking for on an ebike. Smooth but fast acceleration from standstill. Red lights on a hill won't be a problem anymore. :bolt: :bolt:
I haven't tried the other modes because I don't know how to change it. Level 0 and on/of or M as the 860C?
My SW102 freeze every time I access the torque sensor menu. Rest of the menus work fine. It could be because the torque menu is too long? can you split it several submenus?
 
Nfer said:
First ride with SW102: Awesome!!! Great job Mbrusa and all developers. :thumb: :thumb: :thumb:
I ride with Power Assist and boost enable and it is fantastic, exactly what I was looking for on an ebike. Smooth but fast acceleration from standstill. Red lights on a hill won't be a problem anymore. :bolt: :bolt:
I haven't tried the other modes because I don't know how to change it. Level 0 and on/of or M as the 860C?
My SW102 freeze every time I access the torque sensor menu. Rest of the menus work fine. It could be because the torque menu is too long? can you split it several submenus?

Yes, level 0 and on/off to cycle through the modes...
 
Hello everyone! I also installed this version on my bike. And now I'm trying to adjust a non-linear increase in power according to the torque sensor. I want the power to increase not linearly, without sudden jumps. But so far I have not succeeded. I have calibrated the torque sensor: I have set the offset (220) and the maximum value (280). But even after calibrating the sensor, the power rises too sharply and therefore the maximum assistance level has to be reduced. I have a VLCD6 display. Is there a way to make the torque sensor response non-linear? I want less assistance with less pedal pressure, more support with hard pedal pressure. How do I tune non-linearity?
 
Lii said:
Hello everyone! I also installed this version on my bike. And now I'm trying to adjust a non-linear increase in power according to the torque sensor. I want the power to increase not linearly, without sudden jumps. But so far I have not succeeded. I have calibrated the torque sensor: I have set the offset (220) and the maximum value (280). But even after calibrating the sensor, the power rises too sharply and therefore the maximum assistance level has to be reduced. I have a VLCD6 display. Is there a way to make the torque sensor response non-linear? I want less assistance with less pedal pressure, more support with hard pedal pressure. How do I tune non-linearity?
It sounds like you want to use eMTB mode? That will provide assistance proportional to the pedal pressure, automatically increasing the assistance as the pedal pressure increases.
 
Lii said:
Hello everyone! I also installed this version on my bike. And now I'm trying to adjust a non-linear increase in power according to the torque sensor. I want the power to increase not linearly, without sudden jumps. But so far I have not succeeded. I have calibrated the torque sensor: I have set the offset (220) and the maximum value (280). But even after calibrating the sensor, the power rises too sharply and therefore the maximum assistance level has to be reduced. I have a VLCD6 display. Is there a way to make the torque sensor response non-linear? I want less assistance with less pedal pressure, more support with hard pedal pressure. How do I tune non-linearity?
What mode are you using?
 
HughF said:
...
EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
Nfer said:
...
My SW102 freeze every time I access the torque sensor menu. Rest of the menus work fine. It could be because the torque menu is too long? can you split it several submenus?
I have modified the configuration menu to fit SW102.
Can you try? New zip file in PM.
 
mbrusa said:
elfnino said:
I've been desperatly waiting for the fusion of the best from all FW forks and it is here 20.1C ! :thumb:

I could catch only few minor issues in 850C release:
- Clock field settings is not persistent after restart, when I set Battery Voltage after restart the Time field is preset
- Seems that my temperature senzor shows aproximatly 10 degrees more than the real value is.
I'm glad you like the new version.
850C doesn't have an rtc and I haven't changed anything about it.
I did not understand what the problem is, you can explain better.
The next motor I will install will be with a temperature sensor, I will consider whether to add a calibration.

Let me explain better the issue, in cofig menu "Display/Clock field" I chose to set "batt volts" instead of "clock" but after display restart it reverts the setting back to default value which is again the "clock"

My temperature sensor on v1.0.0 was giving correct values, wonder if anyone else is having this offset +11 C on v20.1C or could be there is only something wrong with my senzor, maybe some moisture has got inside the case or so..
 
Back
Top