Guerney
100 W
- Joined
- Dec 28, 2021
- Messages
- 140
Have you previously been able to compile and flash earlier versions, using exactly the same hardware and OS?
Last edited:
TSDZ2 OSF for all displays, VLCD5-VLCD6-XH18, LCD3, 860C-850C-SW102.
- Thread starter mbrusa
- Start date
Hello @mbrusa ! Thank you so much for all your work once again! I am still riding your OSF firmware with my girlfriend, and we love the bikes. I am now currently on 20.1C5 and SW102. I have one question, I love the eMTB mode and I ride almost only with it. I would really like to see one change. Right now it is impossible to adjust eMTB level lower than 21 (range from 21 to 254), I really like to have it possible, because when I ride with analog bike friends, 21 is too much (still have more than 100w). I tried changing torque range adj to lower values, but it seems it doesn't affect eMTB. For example in Power mode you can change assist to 1 and have almost no motor assistance.
I have to add that in C4 eMTB ranged from 1-20, but 1 was also too much.
Another thing that I found is that "hybrid assist" in assist menu is missing, all the other assist modes are present in assist menu.
Thanks once again for you work and I am waiting for reply
I have to add that in C4 eMTB ranged from 1-20, but 1 was also too much.
Another thing that I found is that "hybrid assist" in assist menu is missing, all the other assist modes are present in assist menu.
Thanks once again for you work and I am waiting for reply
Last edited:
Yes, in the new version the scale has changed, the eMTB sensitivity is no longer from 1 to 20, but from 21 to 250, previously there were 20 predefined tables, now the sensitivity is calculated by an algorithm, the minimum value 21 corresponds to the previous table 3, the maximum value 250 to table 20..
It is now also possible to choose the type of progressivity mode. "Based on Torque" which is the same as the previous version, or "Based on Power" which is new, everyone can choose the one they prefer.
Hello @mbrusa ! Thank you so much for all your work once again! I am still riding your OSF firmware with my girlfriend, and we love the bikes. I am now currently on 20.1C5 and SW102. I have one question, I love the eMTB mode and I ride almost only with it. I would really like to see one change. Right now it is impossible to adjust eMTB level lower than 21 (range from 21 to 254), I really like to have it possible, because when I ride with analog bike friends, 21 is too much (still have more than 100w). I tried changing torque range adj to lower values, but it seems it doesn't affect eMTB. For example in Power mode you can change assist to 1 and have almost no motor assistance.
I have to add that in C4 eMTB ranged from 1-20, but 1 was also too much.
Another thing that I found is that "hybrid assist" in assist menu is missing, all the other assist modes are present in assist menu.
Thanks once again for you work and I am waiting for reply
I no longer use eMTB, but when I did I considered levels 1 and 2 too low, which is why I eliminated them.
You, on the other hand, are telling me that you also found table 1 high, perhaps you didn't understand the meaning of eMTB.
The aim of eMTB should be to cover a wide range of power with a single level, from a few watts to the desired maximum.
the choice of level should only serve to identify the most suitable one for the purpose.
Nothing prevents you from using the levels as in the other modes.
But if you need low, gradual power, the most suitable mode is Power.
What I can do is modify the algorithm to include tables 1 and 2 above.
The minimum value is 21 to maintain compatibility between OSF versions.
However, even setting it to 1 would not change anything, the algorithm must be modified.
A clarification regarding compatibility between versions.
Until version v20.1C.4-860C-update-3 it was mandatory to have the same version on the display and on the motor.
From version v20.1C.4-860C-update-4, I changed policy, I thought it was better to maintain compatibility between versions.
So display version v20.1C.4-860C-update-4 or higher works with motor version v20.1C.4-860C-update-3 or higher.
In the Assist level menu, Hybrid mode is not present because there are no specific parameters to set, the assistance is a combination of the Torque mode and Power mode parameters.
Last edited:
In a previous post I gave a wrong indication, I got confused with the version for stock displays.
In the versions for 860C the weight must be set in Kg with Units=SI, in lb with Units=Imperial.
In fact, looking at your settings, the values of "Torque adc step" and "Torque adc step adv" are too low.
Now you say you increased it, okay.
The "Torque adc step adv" value must always be close to 34, to be verified with the weight.
The response curve of the torque sensor is not linear, so human power is only accurate when the pressure on the pedals corresponds to the weight used.
" Default weight" = "yes" is only used to set "Weight on pedal" and "Torque adc on weidht" to the default values, then returns to "no".
I have one more question. I don't know if I understand this correctly:
If I want to modify hybrid level assist I change "power level" or "torque level" settings and it changes level of hybrid mode?
And for example if I want to lower all levels at once I do change : "torque range adj" ?
LegionLoverYT
100 µW
This error:
>>> Programming PROGRAM MEMORY
(API) ERROR : Cannot communicate with the tool.
Wrong tool selection or check tool power supply or check that a previous session is closed.
<<< Programming PROGRAM MEMORY fails
In Hybrid mode, the Torque mode parameters adjust the low cadence assistance, and the Power mode parameters adjust the high cadence assistance. This is for every single level.
"Torque range adj" adjusts assistance at all levels and in all modes.
LegionLoverYT
100 µW
Yes, if the compilation is successful, you can flash the .hex file with STVP.
bogardon
10 µW
Thank you for the explanation! This is what I ended up with. For some reason i cannot set weight to 53, it always resets to 52. Why is that?
Last edited:
LukeDaredevil
1 µW
Hello everyone,
Tsdz2b, OSF v20.1C.4-860C-update-3, did the torque sensor calibration (in software menu).
The problem is that when I'm starting pedaling sometimes assistance won't start until I push the pedal very, very hard (then it works normally until next pause) or stop pedaling and start again (sometimes I need to 'restart' few times to make it working).
But sometimes it starts immediately and then it works just fine until I stop pedaling and start again. Whole issue looks pretty random to me, I didn't find any pattern so far.
I tried changing different settings. It happens with all assistance modes.
For me it doesn't look like a mechanical issue, I don't hear any cracking noises or smth, but who knows... Torque sensor readings in settings menu look legit.
It started after few months without issues.
Maybe someone had similar symptoms, any clue will be appreciated.
[Edit]
The issue turned to be related to one of the one way bearings. Probably I put too much grease around it which caused slipping. After I cleaned it a bit, it gradually started getting better and better and now after few weeks the problem barely occurs.
Tsdz2b, OSF v20.1C.4-860C-update-3, did the torque sensor calibration (in software menu).
The problem is that when I'm starting pedaling sometimes assistance won't start until I push the pedal very, very hard (then it works normally until next pause) or stop pedaling and start again (sometimes I need to 'restart' few times to make it working).
But sometimes it starts immediately and then it works just fine until I stop pedaling and start again. Whole issue looks pretty random to me, I didn't find any pattern so far.
I tried changing different settings. It happens with all assistance modes.
For me it doesn't look like a mechanical issue, I don't hear any cracking noises or smth, but who knows... Torque sensor readings in settings menu look legit.
It started after few months without issues.
Maybe someone had similar symptoms, any clue will be appreciated.
[Edit]
The issue turned to be related to one of the one way bearings. Probably I put too much grease around it which caused slipping. After I cleaned it a bit, it gradually started getting better and better and now after few weeks the problem barely occurs.
Last edited:
Hi, another problem here..
TSDZ2 with SW102 and v20.1C.5.
On startup the display freezes on the boot screen 'wait TSDZ2'.
Unplug and replug the display doesn't help, but unplug and replug the battery allows for one normal startup. When the display is turned off again, the issue reappears at next startup.
When the display eventually turns on, the motor works for some time but eventually stops with the message : "e:6 fatal", which sounds somewhat uncool.
It looks more like a controller issue rather than display, but I hope it can be solved without getting a new controller : I got this one just a month ago, the previous one died for no good reason.. Theses things look fragile !
TSDZ2 with SW102 and v20.1C.5.
On startup the display freezes on the boot screen 'wait TSDZ2'.
Unplug and replug the display doesn't help, but unplug and replug the battery allows for one normal startup. When the display is turned off again, the issue reappears at next startup.
When the display eventually turns on, the motor works for some time but eventually stops with the message : "e:6 fatal", which sounds somewhat uncool.
It looks more like a controller issue rather than display, but I hope it can be solved without getting a new controller : I got this one just a month ago, the previous one died for no good reason.. Theses things look fragile !
Hello,
error E07 no longer appears on my motors in this version. However, E09 is appearing when I drive faster than the set speed limit. Error does not appear each time. If the speed limiter is not active, the error does not appear.
Best regards!
error E07 no longer appears on my motors in this version. However, E09 is appearing when I drive faster than the set speed limit. Error does not appear each time. If the speed limiter is not active, the error does not appear.
Best regards!
There was another update last week, you can download it with the same link.
Can you try and confirm if it works? Thanks.
With "Wait TSDZ2" there is no communication between display and controller.
It seems like a problem of bad contact on the connectors.
Also strange that you have to disconnect the battery.
The e:6 fatal error can also be a loss of communication, or
the battery voltage is very low. Check the connections.
Is the "Low cut-off" setting correct?
I've tried both versions (one from July 27th, 2024 and one from July 7th, 2024 - dates of the files in the zip package). The E09 error appears in both versions. I will try to figure out the exact conditions that cause it. Currently, I've noticed that the error occurs most often on a slight decline when I repeatedly start and stop pedaling.
Today I made some attempts and can produce error code E09 everytime. My settings are 500W and a speed limit of 26 km/h (sw from 27.7.2024). If I start pedaling and accelerate to the speed limit while the motor is still assisting, and then just keep going and accelerating, the error E09 appears somewhere between 28 km/h and 29 km/h (might be time after assistance is off or speed...i am not sure). This can happen going downhill or on flat terrain (I can't go uphill fast enough without assistance). If I set the level of assistance to 0, the error does not appear, even if I then turn on assistance to 1 at a speed of 28 km/h and accelerate.". In offroad mode with speed limit set to 35km/h, even when pedaling around 39km/h i was not able to reproduce that error. However if i set offroad limit to same speed (26km/h) error apears in the same way as in the street mode.
Best regards!
Hi mbrusa, thanks for chiming in !
The low cut off is set to 42V, for a 52V battery.
I checked all connectors, including inside the motor, all seem fine.
Indeed it's strange that disconnecting the battery allows for a normal startup, but the e:6 fatal error now appears a few seconds after that anyway.
Another (kinda) funny thing is that when I disconnected the torque sensor, the motor started in walk mode by itself, and would continue even after I turned off the display, until I disconnected the battery ! This happened a couple times.
I also reflashed the controller. I guess I'm good for a new one..
bogardon
10 µW
Is this generally true for all other units? For example if I have units set to imperial, should I be entering mph for "max speed" and inches for "wheel circumference"?
Both ! With "Wait TSDZ2" the motor doesn't start, and with "e6 fatal error" the motor stops.
It's always in the same order : first I get "Wait TSDZ2", then if I disconnect the battery, the screen and motor work for a few seconds to a few minutes, then 'e6 fatal error' and the motor stops.
I tried reflashing the controller and using a VLCD6 display. The behaviour is roughly the same : first the display doesn't turn on, then if I disconnect and reconnect the battery it does turn on and the motor works for a short time, then I get "E07" and the motor stops..
Enabling the 'assist with errors" option doesn't help.
Last edited:
I checked, the expected conversions from SI to Imperial are:
- speed km/h -> mph
- distance km -> mi
- consumption Wh/km -> Wh/mi
- weight kg -> lbs
- temperature Celsius -> Fahrenheit
The temperature can also be set independently from the system.
- wheel circumference is always in mm.
