new tsdz8 pswpower

If there hadn't been those damn wires to pass through the little hole, it would have taken less than an hour.

This morning I did my usual bike commute route. Nothing to do with the previous version of the sensor! I have a big climb (several sections at 18%) on the route, where I was struggling at 10 km/h, I go without difficulty to 16/17 km/h.

This engine is really nice now, quite comparable to a mainstream engine like Bosch, Shimano in terms of sensation, but more powerful.
I seem to have the same problem. Quite low power when pedaling. When I hit the throttle, it goes like a banshee. So, it sounds like the torque sensor. I see that TE is fine, from 95 to 170 depending on how hard I push on the pedals, but TE1 is always 0. Is this perhaps an indication of a problem?
 
I seem to have the same problem. Quite low power when pedaling. When I hit the throttle, it goes like a banshee. So, it sounds like the torque sensor. I see that TE is fine, from 95 to 170 depending on how hard I push on the pedals, but TE1 is always 0. Is this perhaps an indication of a problem?
One more issue, the throttle is very touchy, it seems to be all or nothing. Any ideas on this?
 
I seem to have the same problem. Quite low power when pedaling. When I hit the throttle, it goes like a banshee. So, it sounds like the torque sensor. I see that TE is fine, from 95 to 170 depending on how hard I push on the pedals, but TE1 is always 0. Is this perhaps an indication of a problem?
I do not have a TSDZ2, but I own TSDZ2 and TSDZ2B with VLDC5. I never checked when new, but after two years both motors showed similar numbers of 0/170. I watched a youtube video where the user repositioned the sensor and went from a sumalr 0/170 to equal values, so I believe it's an adjustment.

I do not intend to adjust mine, as both my motors run alright now with OSF firmware, They might run better with adjustment, but the OSF apparently does a better job of reading unequal TE/TE1. My TSDZ2 originally had hardly any assist in the first 3 levels until I installed the OSF. .
 
PSWPower will send a new torque sensor, so I'll be doing the same repair as Carbone. I'd prefer a replacement motor, but I understand their reluctance, that would be expensive. Sounds like a quality control issue from Tongsheng on a batch of TSDZ8s, or one of their suppliers. Otherwise, the motor is a beast, I can go up the hill to our house without pedaling using the throttle, and it is very steep. Couldn´t do that with the Z2.
 
I had two tsdz8 big bearing clutch failures from pswpower, I never asked for a refund as I put max amps in the settings and thats probably why it broke.

The motors work normaly when you apply throttle easy, but when you want alot of power then the motor makes are large crunchy noise usualy the same when you get chain skipping over gears
 
I had two tsdz8 big bearing clutch failures from pswpower, I never asked for a refund as I put max amps in the settings and thats probably why it broke.

The motors work normaly when you apply throttle easy, but when you want alot of power then the motor makes are large crunchy noise usualy the same when you get chain skipping over gears
that sounds like what happened to my first one, did you replace the clutch ?
 
that sounds like what happened to my first one, did you replace the clutch ?
This happened like 3 4 months ago but if I remember correctly I couldnt find the one way bearing as a seperate piece also even if I did it would probably require cooling the piece and heating the bearing and then pulling it with a such large bearing puller? I am not sure although I suspect there is alot of work for it thats why both motors are just laying on the shelf
 
Last edited:
Isn't it like the tsdz2B and not A, with the bearing/clutch integrated? Not finding seperate piece is because you it's not user servicable you need to replace both at once. Which doesn't require speciality tools but costs more.
 
I hope to be able to deliver in the coming days/weeks an Open Source Firmware version for the TSDZ8.

This version is based on the OSF version from mbrusa for TSDZ2 that allows:
- to change quite many parameters to fit your preferences
- to display more data on dseveral displays (without any changes on the display firmware).

My version uses the same configuration parameters as mbrusa TSDZ2 version.
So, I expect, it should be possible to re-use the (graphical) user friendly configurator to generate a config.h.

Still this TSDZ8 version requires to install/use some more softwares (mainly VS Code) for compiling.
Flashing has to be done in the same way as for the alternative TSDZ8 firmwares (so with a Jlink device and not a Stlink).

Currently my version is able to:
- let the motor run based on the throttle position.
- manage the display in the same way as the mbrusa firmware (except that the parameters changed with the display keyboard can't yet be saved - so they are lost after a power off).
Please note that those functions have not been tested on a bike (just on table).

This version contains already all the code to manage speed, cadence, torque sensors and all assist modes (power, torque, hybrid, ...) but this part of the code has not been tested because it requires intalling the motor on a bike.

Question : is someone interrested to test:
- the compilation process
- the firmware on a bike.

Please note that there are probalby still some bugs and some parameters to fine tune.
So test at your own risk.
 
@mstrens I would be interested but don't have the motor yet. Care to share a link to the repo? I can try to compile it at least.
I could publish the current version but I am currently working on a new version where the user would not have to compile himself. There would be only one pre-compiled version that supports all user preferences.
The user preferences would be defined in an XLS and flash separately. So the user would have only to use the Jlink software to flash.
Compilation would still be possible if you want to change the firmware to add other functionalities.
The new version should be available in a few days.
If you really want to look at the current code and compilation process, let me know but I suggest to wait a few days for the new one.
 
I'm actually surprised. I thought it used the same microcontroller as on the Enerprof (v2) controller? That's why I expected it take a lot longer, if ever, for people would be able to do this ( why otherwise has it taken 'them' so long for that controller? Or is it supply/demand kind of thing? Or is it a totally different microcontroller all together? ).
 
I'm actually surprised. I thought it used the same microcontroller as on the Enerprof (v2) controller? That's why I expected it take a lot longer, if ever, for people would be able to do this ( why otherwise has it taken 'them' so long for that controller? Or is it supply/demand kind of thing? Or is it a totally different microcontroller all together? ).
It is the same microcontroller and it seems even to be the same internal components/wiring. The project about TSDZ2 V2 was stopped because one of the developper moved to another controller (not from Tongsheng) and the other destroyed his controller when he installed his beta version on the bike. Still their work helped me for my development.
 
It is the same microcontroller and it seems even to be the same internal components/wiring. The project about TSDZ2 V2 was stopped because one of the developper moved to another controller (not from Tongsheng) and the other destroyed his controller when he installed his beta version on the bike. Still their work helped me for my development.
does your OSF increase the maximum amp limit of the tsdz8 Controller, and if so to how much? also would you be able to calibrate the torque sensor? im happy to see some development for this motor, thanks!
 
does your OSF increase the maximum amp limit of the tsdz8 Controller, and if so to how much? also would you be able to calibrate the torque sensor? im happy to see some development for this motor, thanks!
Currently, my version is supposed to work just like the mbrusa version on TSDZ2. I reuse his code when possible.
So, you can change the current limits above 18A (at your own risk - I do not know what are the real limits of TSDZ8).
The mbrusa sensor already provides some way to calibrate the torque sensor. My version uses the same feature.
In the future, I could imagine to offer more possibilties to adjust more the torque sensor value depending on the pressure applied.
 
I could publish the current version but I am currently working on a new version where the user would not have to compile himself. There would be only one pre-compiled version that supports all user preferences.
The user preferences would be defined in an XLS and flash separately. So the user would have only to use the Jlink software to flash.
Compilation would still be possible if you want to change the firmware to add other functionalities.
The new version should be available in a few days.
If you really want to look at the current code and compilation process, let me know but I suggest to wait a few days for the new one.
I'll be patient no worries. Let me know if there is anything I can help with.
 
Last edited:
I hope to be able to deliver in the coming days/weeks an Open Source Firmware version for the TSDZ8.

This version is based on the OSF version from mbrusa for TSDZ2 that allows:
- to change quite many parameters to fit your preferences
- to display more data on dseveral displays (without any changes on the display firmware).

My version uses the same configuration parameters as mbrusa TSDZ2 version.
So, I expect, it should be possible to re-use the (graphical) user friendly configurator to generate a config.h.

Still this TSDZ8 version requires to install/use some more softwares (mainly VS Code) for compiling.
Flashing has to be done in the same way as for the alternative TSDZ8 firmwares (so with a Jlink device and not a Stlink).

Currently my version is able to:
- let the motor run based on the throttle position.
- manage the display in the same way as the mbrusa firmware (except that the parameters changed with the display keyboard can't yet be saved - so they are lost after a power off).
Please note that those functions have not been tested on a bike (just on table).

This version contains already all the code to manage speed, cadence, torque sensors and all assist modes (power, torque, hybrid, ...) but this part of the code has not been tested because it requires intalling the motor on a bike.

Question : is someone interrested to test:
- the compilation process
- the firmware on a bike.

Please note that there are probalby still some bugs and some parameters to fine tune.
So test at your own risk.
Great job and very big thanks to you. This i've been waiting for. I'm totally been bored to TSDZ2B it is worse than TSDZ2. New white gear brakes it's bearing all the time. Motor is more on the table to repair than in bicycle to drive.

I think TSDZ8's more power do not break parts so often (don't have to take motor it's limit). I will order motor today.

You say software is j-link. Do I understand right st-link is for flashing TSDZ2 and B version. And TSDZ8 have to flash with j-link adapter.

I'm not developer but I can compile if I get instructions from scratch. (I have compiled now AOSP to my phone but compiling has not gone very well).
 
Great job and very big thanks to you. This i've been waiting for. I'm totally been bored to TSDZ2B it is worse than TSDZ2. New white gear brakes it's bearing all the time. Motor is more on the table to repair than in bicycle to drive.

I think TSDZ8's more power do not break parts so often (don't have to take motor it's limit). I will order motor today.

You say software is j-link. Do I understand right st-link is for flashing TSDZ2 and B version. And TSDZ8 have to flash with j-link adapter.

I'm not developer but I can compile if I get instructions from scratch. (I have compiled now AOSP to my phone but compiling has not gone very well).
Indeed TSDZ8 uses anaother microcontroller and requires J-link for flashing
 
Indeed TSDZ8 uses anaother microcontroller and requires J-link for flashing
Out of curiosity, st-link v2 can be flashed with j-link firmware but doesn't gain full functionality. Would it still be possible to flash using such a device?

And if not, would at least be an j-link edu mini be enough?

It's already quite pricy for people to buy just to flash their own motor, or did my google fu give me some overpriced option and it's actually cheaper somewhere else?

St-link v2 flashed with j-link would be optimal ofc, but 'some functionality might not work' I have a feeling this 'some' is particular to the kind of microprocessors it will be able to connect to ( hence the need for j-link to start with ).
 
Out of curiosity, st-link v2 can be flashed with j-link firmware but doesn't gain full functionality. Would it still be possible to flash using such a device?

And if not, would at least be an j-link edu mini be enough?

It's already quite pricy for people to buy just to flash their own motor, or did my google fu give me some overpriced option and it's actually cheaper somewhere else?

St-link v2 flashed with j-link would be optimal ofc, but 'some functionality might not work' I have a feeling this 'some' is particular to the kind of microprocessors it will be able to connect to ( hence the need for j-link to start with ).
I have no experience flashing st_link with j_link firmware.
What we need for TSDZ8 is only to be able to flash to memory. So there is a good chance that basic solution works.
There is also the solution to use a cheap chinese J-link. The one I got from aliexpress costs 13€.
 
Something like this then? Comprar J-Link JLink V8 USB ARM JTAG Emulador Debugger Programador ...
What kind of software would I need to load the firmware onto the TSDZ8?
I presume it should work. Still on my side I used a device named Jlink V9. I do not know the difference.
Note: you also need a cable to connect the Jkink to the controller.
You can buy it from the link below or you can build it your self (e.g. using a extension cord for the speed sensor).

To flash, you can follow the instructions from here:

Look also at the links inside.

It will be the same process for my firmware.

Edit : I got my jlink from here:
 
Last edited:
Back
Top