New "TSDZ2 Torque Sensor Central Motor"

Hi,

I don't have a speed sensor!!

In the thread below "amberwolf" says it can be the BMS cutting off...but it's strange that it only cuts with the throttle!!


Since my voltmeter it's damaged I have to wait and measure like he mentioned!!

Thanks any way and if you remember anything else that might be causing this issue....please give a feedback!!

I really need to make this motor work...

Cheers
 
I came across something on another project that might help if someone wants to make an upgraded TSDZ2 pedal shaft.
I needed some 134mm square taper BB for a front freewheel mod. The ones I found instead of being drilled for a bolt, were threaded for a shouldered nut. Maybe that would help?
1711218592726.png
 
Can anyone help me on ideas on how to throubleshoot my newly installed tsdz2 kit with the vlcd5. I have installed tsdz2 kits (other kits) three times before without any major problems. On my latest build (with a new kit - that has been on my shelve for a couple of years..) the motor is very uneven in applying assist and actually too powerful no mater the assist level.
I feels like it applies only power when you press down on the pedals (in that very specific millisecond) i.e. when pedaling at normal kadance I can hear and feel the motor go up in power every time either the left or right pedal arm is being pressed down. Very powerful with every pedal stroke. It seems like what would happen if the tourqe sensor was over sensitive or if some sort of smoothening delay in the software wasn't there.

I have tried:
*Disconnecting speed sensor and light cables
*Physically seperating the power cable from battery to motor from the controller cable (in case of electrical noise inferring with the tourqe sensor signal)
* Changing the A (amp) setting down to 1 - (no effect as others also reports)
*Changing assist level - it does have somewhat of an effect but the problem is still there at the lowest assist level.


And yes, I don't press the pedals while turning it on ;)

Anyone have tried something similar?
 
Can anyone help me on ideas on how to throubleshoot my newly installed tsdz2 kit with the vlcd5. I have installed tsdz2 kits (other kits) three times before without any major problems. On my latest build (with a new kit - that has been on my shelve for a couple of years..) the motor is very uneven in applying assist and actually too powerful no mater the assist level.
I feels like it applies only power when you press down on the pedals (in that very specific millisecond) i.e. when pedaling at normal kadance I can hear and feel the motor go up in power every time either the left or right pedal arm is being pressed down. Very powerful with every pedal stroke. It seems like what would happen if the tourqe sensor was over sensitive or if some sort of smoothening delay in the software wasn't there.

I have tried:
*Disconnecting speed sensor and light cables
*Physically seperating the power cable from battery to motor from the controller cable (in case of electrical noise inferring with the tourqe sensor signal)
* Changing the A (amp) setting down to 1 - (no effect as others also reports)
*Changing assist level - it does have somewhat of an effect but the problem is still there at the lowest assist level.


And yes, I don't press the pedals while turning it on ;)

Anyone have tried something similar?
stock fw ?
 
.... It seems like what would happen if the tourqe sensor was over sensitive or if some sort of smoothening delay in the software wasn't there.
.
If you have the Vlcd5 you can check the Torque range with hidden settings.
Te0 and Te1 are the same value without load on the pedals, Te1 will increase with load.
 
If you have the Vlcd5 you can check the Torque range with hidden settings.
Te0 and Te1 are the same value without load on the pedals, Te1 will increase with load.
Ok - i haver never worked with the "hidden settings" but i will give it a go. What should i look out for in te0 and te1? (If i understand correct te0 is the tourqe signal at zero tourqe and te1 is the current reading). What is a reasonable range?
 

If you have the Vlcd5 you can check the Torque range with hidden settings.
Te0 and Te1 are the same value without load on the pedals, Te1 will increase with load.
I can't seem to find the te and te1 settings. Software version is 5.1 (last item in the hidden menu). One manual that I found states that is should hold "i" and "power" for 10 seconds (instead of 3secons). But that just turns it off again. Hmm 🤔
 
Hi all,
I have a TSDZ2b with 860c display and Open Source firmware (version: 0.20.1C-4). The problem is that at power on, the display first displays "Wait TSDZ2", followed by "Error brakes or comms" 30-40 seconds later. Checked and rechecked all cables -- no issues. I had read a few places that reflashing the Option Byte might fix this. Questions for you TSDZ2 experts out there:
1. Is it possible to reflash just the Option Byte since I want to maintain all the other settings?
2. If so, how would I go about it? I have the ST-Link cable and have downloaded all the necessary software.

Thanks in advance!
 
1. Is it possible to reflash just the Option Byte since I want to maintain all the other settings?
2. If so, how would I go about it? I have the ST-Link cable and have downloaded all the necessary software.

Thanks in advance!
Yes.
You can use stvp. You can open this stvp project configuration from TSDZ2-Smart-EBike-1/tools/ST_Vision_Programming.stp at master · emmebrusa/TSDZ2-Smart-EBike-1 or configure your CPU manually in the options menu.
Then open the option byte hex file and then program th ecurrent tab.

Alternatively you can use stm8flash tool. The command should be:
Code:
./stm8flash -c stlink -p stm8s105c4 -s opt -w option_stock.ihx
 
Last edited:
Yes.
Use stvp. You can open this stvp project configuration from TSDZ2-Smart-EBike-1/tools/ST_Vision_Programming.stp at master · emmebrusa/TSDZ2-Smart-EBike-1 or configure your CPU manually in the options
Then open the option byte hex file and then program th ecurrent tab.

Alternatively you can use stm8flash tool. The command should be:
Code:
./stm8flash -c stlink -p stm8s105c4 -s opt -w option_stock.ihx
@dzid_ -- thanks for the suggestions. I will give it a shot today and report back.
 
@dzid_ -- thanks for the suggestions. I will give it a shot today and report back.
SUCCESS!! My first time using ST Visual Programmer and I had a few glitches. I had the battery turned on when I hooked up the ST-Link cable. When I tried to read each tab (PROGRAM MEMORY, DATA MEMORY, OPTION BYTE) all showed as zero and an error about the option byte appeared. So I then tried to program the option byte and a different error appeared that did mention powering off/on. After powering off/on the battery, the program of the OPTION BYTE succeeded. I then disconnected the ST-Link cable, reconnected the speed sensor, powered on, and voila, the display came up normal. Tested with throttle and worked perfectly.

This has been quite the ordeal when the actual solution was so simple -- reflashing the OPTION BYTE.

I believe what got my TSDZ2 into the "Error brakes or comms" state was accidentally powering on the display with the battery turned off. There must have been enough residual charge left that the display briefly flashed on and somehow the OPTION BYTE must have gotten corrupted in the controller. So avoid trying to power on your 860c display when your battery is turned off!
 
I believe what got my TSDZ2 into the "Error brakes or comms" state was accidentally powering on the display with the battery turned off. There must have been enough residual charge left that the display briefly flashed on and somehow the OPTION BYTE must have gotten corrupted in the controller. So avoid trying to power on your 860c display when your battery is turned off!
I don't know about the display, but I always get failed flash if the wall charger is connected to the battery. I am not sure why (maybe power supply noise,.. but I don't have no ground loops - laptop powered from battery). - One time my flash got corrupted badly and I needed to boot the controller with RST pin grounded to establish communication. And even that only worked if I waited some time between trials (probably to fully power down the controller).
 
Last edited:
I never had the [smart] charger connected to the battery when flashing. What I did not try was to do the flash without the battery powered on (thus only using USB power from my laptop).
 
Back
Top