I'm testing v20.1C.6-update-1 and in the case of a lower SoC (below 46 volts) the motor suddenly shuts down under load. No error is shown on the display, the display can still be used but the motor stays off. I have to turn the whole system off with the button on the VLCD5 display and turn it back on, then it works normally again. The previous version v20.1C.6 works normally and I have never had the motor shut down even with a much lower SoC (cut off voltage is always 39V).
-
Hello ES! We could use some help to get us past the finish line on building the new knowledgebase for the forum.
Can you donate? Please see our fundraising page. Thank you!
TSDZ2 OSF for all displays, VLCD5-VLCD6-XH18, LCD3, 860C-850C-SW102.
- Thread starter mbrusa
- Start date
I am now using v20.1C.6 and there are no problems with the motor shutdown. What configurator parameter could affect the motor shutdown? The display was showing two bars and yet the motor was shutting down (in v20.1C.6-update-1).
Tested the motor at +29C with 800Wt settings in the v20.1C.5-update firmware (+"copper wires cooling mod").
After 1 hour of active riding, including steep climbs, the motor was noticeably hot, but I can hold the hand without any problems. The 3 additional bearings also perform well, with no axle play noticeable after 700+km
After 1 hour of active riding, including steep climbs, the motor was noticeably hot, but I can hold the hand without any problems. The 3 additional bearings also perform well, with no axle play noticeable after 700+km
I wanted to do a rollback to v20.1C.6 because even in v20.1C.6-update-2 there is a bug with motor suddenly shutdown at low SoC. Is it possible that when simple connecting a computer (laptop) this would damage the motor controller? I had battery disconnected from motor, when connecting controller to computer. Even without start programming, I don't see the motor controller anymore (SWIM error). When I now connect the motor to the battery after initialization, it doesn't show the voltage status and the display shows zeros, the motor doesn't help or show speed when I spin the wheel. The display can be operated normally, no error is displayed. TE and TE1 values show zero. The display does not turn off after the timeout, but the power button can be used to turn it off.
Last edited:
Good morning.
I have a TSDZ2B motor and OSF V20.1C.5 update 1, and an SW102 display. After installing the software, I calibrated it (ADC Torque Offset = 147, ADC Max Torque = 335, ADC Torque with 25 kg = 286). I have a temperature sensor installed, so I'm not using the throttle.
My observations:
I've noticed a strange issue - while riding with the EMTB ASSIST and using high assist (eMTB assist setting above 200 in the range 1 to 254), when I stop pedaling or shift to a smaller sprocket (i.e., for a higher speed), when I resume pedaling, the motor brakes for about 3-4 seconds before continuing to assist. With the human power and motor power preview turned on, I see motor power = 0 for the first few seconds, and then the value jumps to, for example, 400.
Please advise:
What setting should I adjust to speed up the engagement of the motor assist?
I have a TSDZ2B motor and OSF V20.1C.5 update 1, and an SW102 display. After installing the software, I calibrated it (ADC Torque Offset = 147, ADC Max Torque = 335, ADC Torque with 25 kg = 286). I have a temperature sensor installed, so I'm not using the throttle.
My observations:
I've noticed a strange issue - while riding with the EMTB ASSIST and using high assist (eMTB assist setting above 200 in the range 1 to 254), when I stop pedaling or shift to a smaller sprocket (i.e., for a higher speed), when I resume pedaling, the motor brakes for about 3-4 seconds before continuing to assist. With the human power and motor power preview turned on, I see motor power = 0 for the first few seconds, and then the value jumps to, for example, 400.
Please advise:
What setting should I adjust to speed up the engagement of the motor assist?
It's unclear from your description what you've done.
It's important not to connect the ST-link to the PC when the display is on.
The display or controller may be damaged, or the Option Byte may be corrupted.
You can try this: open ST Visual Programmer, select the OPTION BYTE tab, and click "Read->Current tab."
If you get an "OPTION BYTE reading failed" message, open the attached file in ST Visual Programmer and click "Program->Current tab."
If everything is OK, close ST Visual Programmer, open the Java Configurator, and Compile&Flash.
From v20.1C.6 to v20.1C.6-update-2, nothing has changed that could cause the motor to suddenly stop at low SoC levels.
Hello mbrusa,
I had the battery disconnected and the display turned off. The only thing I did differently than other times was that I had the stlink connected to the usb port of the laptop and then connected to the motor controller. Otherwise, I always connected the stlink to the controller first and then to the laptop.
Now, when I want to read a program, memory or option byte I get a swim connection error message, mostly. But sometimes tab program and tab memory are loaded OK. I will try to order a new programing cable. Anyway, the controller seems to have gotten damaged somehow just by connecting to the laptop, because I didn't even start reading or writing flash.
Last edited:
I don't use eMTB mode, but I'll try it as soon as I get a chance.
In the meantime, try enabling "Assist w/o pedaling" and setting "Torque offset adj" to 15.
I also recommend trying Power Assist mode with "Startup boost" enabled and "Boost at zero" set to cadence.
Hello mbrusa,
thank you very much for the recommendation, indeed there was something wrong with the option byte. I have now made a new flash of option byte and the motor seems to be working again!
I will try these settings and let you know. Thank you,
Good morning
I did a test ride: 50 km, average speed 23 km/h, maximum speed 42 km/h. Assistance set to max (254). Motor temperature around 48 degrees C.
I previously set the "Torque offset adj" to 15.
First, I rode on EMTB ASSIST, then switched to POWER ASSIST, then to HYBRID ASSIST.
During the ride, I got an E7 error once (system reset and continued riding).
Observations:
- The motor on each of these systems behaved similarly when stopping and resuming pedaling (the motor braking time when resuming pedaling may have been shortened slightly to around 2-3 seconds, but braking was still there). This resulting motor braking force, which causes deceleration, is greater than if the motor were completely off – this is a subjective impression.
I previously used your software (versions TSDZ2-v20.1c4-3 and TSDZ2-v20.1c4-4) and this issue didn't occur.
I suspect I've entered an incorrect value somewhere in the settings that's causing this engine behavior, but I can't fix it myself – I don't know which setting it might be.
I drove 100-150 km in each of the modes. Now I can firmly say that torque - is the best. 
The only thing I can't overcome is the random squeak (when accelerating)... I've already tightened the motor mounts more tightly, tightened the bolts in the connecting cranks (with a larger wrench) and lubricated the saddle tube... nothing changes... squeak persists
And it's not from the engine axle (I have four bearings there), but somewhere from the frame I think...
The only thing I can't overcome is the random squeak (when accelerating)... I've already tightened the motor mounts more tightly, tightened the bolts in the connecting cranks (with a larger wrench) and lubricated the saddle tube... nothing changes... squeak persists
And it's not from the engine axle (I have four bearings there), but somewhere from the frame I think...
Last edited:
I have recently installed v20.1C.6-update-2 and have encountered an E07 error a few times. I have checked all the obvious electrical connections and they are OK. The error occurred a few times on a short ride, but switching off / on again cleared it. It happened at various speeds and there was no apparent reason for it. I was using Level 2 assist on flat ground with no particular stress on the motor. Any thoughts as to possible cause?
I'll try to look into it further.
Thanks for your response. As you say, I think this may just be a false error as I completed a 30 mile trip yesterday over some hilly terrain with no issues. I used Level 2, Hybrid Mode.
Can I also add my thanks for the work you have done / are doing on this firmware - it is very much appreciated
Here are all my current settings, maybe it will be helpful in finding the cause of this engine braking:
Bike
- Max speed 50km/h
- Circumference 2190
- Max power limit 500
- Assist with error 0
- Throttle disabled
- Cruise disabled
- Password enable no
- Password 0
- Confirm logout
- Reset no
Battery
- Max current 16 Amp
- Low cut-off 39,5 volts
- Voltage cal % 100.0
- Resistance 240 milliohms
- Voltage auto estimate 54,3V
- Resistance auto estimate 0
- Power loss auto estimate 0
SOC
- Text SOC %
- Calculation Auto
- Reset at voltage 53.8V
- Battery total Wh 700
- Used Wh 0
- Manual reset no
- Auto reset % 15
Motor
- Motor voltage 48V
- Motor power max 450W
- Motor Acceleration 30
- Motor Deceleration 35
- Field weakening enabled
- Overcurrent delay 2
Torquesensor
- Assist w/o pedal rotation Disable
- Torque ADC threshold 20
- Coast brake Disable
- Coast brake ADC 15
TorqueCal
- Calibration Enable
- Torque sensor ADC step 67
- Torque adc step adv 34
- Torque offset adj 15
- Torque range adj 20
- Torque angle adj 20
- Torque sensor ADC offset 147
- Torque ADC max 335
- Weight on pedal 25 kg
- Torque ADC on weight 286
- ADC torque step calc 35
- Default weight no
Assistlevel
- Num levels 9
- Start assist level last
- Start riding mode eMTB
Powerassist Torque ass. Cadence ass. eMTB ass.
1-10 1 -10 1 -25 1 -10
2-30 2 -30 2 -50 2 -30
3-50 3 -50 3 -75 3 -60
4-75 4 -80 4 -100 4 -95
5-100 5 -120 5 -130 5 135
6-140 6 -160 6 -160 6 -170
7-180 7 -190 7 -190 7 -200
8-220 8 -230 8 -220 8 -230
9-254 9 -254 9 -250 9 -254
Walkassist
- Feature enable
- Speed 5
StartupBOOST
- Feature Disable
- Boost Torque Factor 250
- Startup boost cadence step 25
- Startup boost at zero cadence
- Startup assist disable
- Smooth start enable
- Smooth start ramp 35
Motortemperature
- Feature temperature
- Min limit 65°C
- Max limit 85°C
- Units celsius
- Sensor type LM35
- Brake temperature
Streetmode
- Enable Mode no
- Enable at startup no
- Speed limit 25 km/h
- Motor power limit 250 W
- Throttle disable
- Cruise disable
- Hotkey enable no
Various
- Light sensor disabled
- Lights configuration 0
- Virtual throttle step 5
- Odometer 0
Historyerrors
- Last error 1 7
- Last error 2 7
- Last error 3 7
- Last error 4 0
- Reset no
Display
- Auto power off 30
- Units SI
- Config Shortcut Key yes
- Reset ble no
- Reset to defaults no
- Confirm reset no
- OSF motor v20.1C 5.1 OSF
Good morning.
Since my last post, I've ridden about 200 km. I've been riding in various assist modes (Power assist, Torque assist, Cadence assist, eMTB assist).
My observations:
The motor would frequently encounter error E7 (about 30 times) and turn off the assist. I noticed that pressing the pedals hard and quickly would trigger this error, even when the gear ratio was set to light (large rear sprocket). At the time of the error, the motor's acoustic response was slightly different (the acoustic impression was as if you could hear the gears in the motor working).
When stopping and resuming pedaling, the motor continued to brake for about 2-3 seconds (I was riding with the Torque offset adj = 15 setting). This resulting braking force, which causes deceleration, is greater than if the motor were completely off – this is a subjective impression. I've noticed that pressing harder on the pedals lengthens the motor braking time, while very light pedaling at the beginning and slightly increasing the pedaling force may shorten this time a bit.
Please help, as I'm close to reverting to the previous software version, where I didn't have these problems.
Best regards.
I previously used versions TSDZ2-v20.1c4-3 and TSDZ2-v20.1c4-4. I drove several thousand km on them and had no problems with engine braking
One question: have you also tried v20.1C.5?
To understand the source of the problem, it's important for me to know if this version also has the same issue.
If you haven't tried it, can you? Thanks.
endlessolli
Regular
Just out of curiosity: What do you mean by engine braking? Because due to the dual sprag-clutch setup of the TSDZ2(B), one never actively turns the motor with physical pedaling, so how do you know that the motor is ‚breaking‘?
I don't assume the motor is failing. I've just noticed that when I resume pedaling, there's an additional braking force (more strain on my legs than if I were riding with the motor completely off). This force disappears after a few seconds, when the motor begins to provide assistance again. It feels as if the motor is trying to rotate in the opposite direction, only to reverse direction after a few seconds. I think this is due to the incorrect motor operating parameters I've set. Unfortunately, I don't know which parameters I'm referring to.
Similar threads
- Question
