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

Elinx said:
SYOTR said:
.... measure pedal cadence. Is there some advantage to having more magnets?....
The pedal cadence sensor is on the controller board
Imho there is no real advantage to add more spoke magnets for speed measuring. Theoretical the accuracy should be better, but practical I think you don't see the difference. On stock FW it was also possible to install more magnets.

hermes127 said:
... like to know what are the benefits of implementing it with a 48V TSDZ2B motor and VLCD5 display and if it's advisable to add it.
The stock Tsdz2(B) has a very bad heat management. If you run the tsdz2 with 600W, the motor will heat up, with a chance on demagnetization of the bare motor.

The first addition to reduce this chance, was adding a temperature sensor that powerdown the motor if the heat will go up.
The second addition was adding heatconductive material between bare motor and housing.
See wiki
See this thread

Both additions are effective and in your case I advice to add at least heatconductive material.

Thanks for your response and the links, I'm not using the stock firmware but the Open source firmware TSDZ2-v20.1C.2 in hybrid mode. Ok, so adding the sensor and heatconductive material is a good implementation.
 
I asked for some help over in the Hardware Temperature Control TSDZ2 Forum and perhaps should have asked my question here thinking maybe I have a firmware parameter not set correctly. Sorry for double-post, but I think better direction will come from this thread…

I installed a LM35DZ (Amazon purchase) on TSDZ2 with OSF and 860C display. I followed the Wiki and Elinx direction to leave wires in 8-pin loom connected and simply splice into the three wires. I looked up the pinout for the LM35, so I have sensor and power leads correct.

I think I have motor parameters set correctly. System powers up and display shows 66F which is spot-on. The problem is display doesn’t change with warming the LM35. I hold the loose LM35 in my fingers to warm and also tried slight heating from a hot air blower and display is not changing.

Any help appreciated….
 
I tried to read the firmware on the TDSZ2 and get the following message "Cannot connect with the tool. Wrong tool selection or check power supply or check that a previous session is closed." The red LED on the StLink is slowly flashing. I have checked my wiring with a meter and all pins show correct continuity from the connector to the points on the actual circuit board of the STlink. The cable is short and I get the same message when not plugged into the bike. Any ideas?
 
SYOTR said:
... "Cannot connect with the tool. .... Any ideas?
It could be that the pins on PCB are different from what is printed on the aluminium housing.
If it is possible to shift the housing a bit you can compare.
Also use 3.3V instead of 5V could help.
 
Elinx said:
SYOTR said:
... "Cannot connect with the tool. .... Any ideas?
It could be that the pins on PCB are different from what is printed on the aluminium housing.
If it is possible to shift the housing a bit you can compare.
Also use 3.3V instead of 5V could help.
Thanks, I checked the label on the case with the markings on the board and they match. I also tried using a different computer, installed driver, visual programmer and the plugged in the StLink V2. Same error. I think the device is defective. It does not show up in device manager when plugged in. From reading reviews, it seems a high percentage of these are defective. I have ordered a different one.
 
these made of chinesium are often defective. the original one is expensive from what I've heard
 
Hello,

I have a TSDZ2 750W, a XH18 display and a 48V 10.5Ah battery.
I've successfully calibrated the torque sensor and got values very closed to the default ones (144 and 297 versus 150 and 300).

I've modified the assistance levels in that way:

Item / Power assist mode / Torque assist mode
ECO 60 / 40
TOUR 150 / 100
SPORT 300 / 150
TURBO 450 / 200
Of course, I've enabled Hybrid assist mode on startup.

When I switch the motor on using the display button, I have to wait a few seconds before pushing on the pedals. Otherwise the motor does not help. Weird behaviour but I assume this is the way it calibrates. Could you confirm ?

My main issue is when I change assistance levels on the display.
When I start the motor, I'm in level 1 (ECO), pushing on the pedals will provide a certain level of assistance.
Moving to level 2 or more, does not provide additional power.
When I climb a small hill for example, I don't have any difference between level 1 and 4, even if I'm only at 17km/h (max is set to 25 km/h) and I push really hard on the pedals.

I've set street power limit to 750W and battery power max to 650W. Could it be an issue with one of these parameters ?
Do I need to change the battery max current to 18A ?

Thanks for your time.
 
IArchi said:
Hello,

I have a TSDZ2 750W, a XH18 display and a 48V 10.5Ah battery.....

My main issue is when I change assistance levels on the display......
Could you please share the latest ini file from the folder "Experimental settings"
 
IArchi said:
...
Ini file is available ....
As far as I could see, there is no benefit of streetmode, because you have the same speedlimit. The higher powerlimit at streetmode will not work because you limit is already main to 650W 12A. Better, in your case, is to disable streetmode at startup.
All other settings looks ok.
Your advanced setting 34 is the default value I think, because no other advanced settings are there.
If you enable "estimated" too, you find 36 for your calibrated torque values and you don't need the advanced settings anymore.

You say you use hybrid assist at startup.
That means at lower cadence you use torque assist and with higher cadence it is power assist.
In that case it depends of the assistsettings of these two.
For finding a balance between these two it is better to use power assist and feel the differences between the levels.
If you find also no different feel you must downsize the highest assist values.
Do the same for torque assist and try to feel the difference between the same assistlevel for powerassist and torqueassist.
imho you torque assist settings are too high, so you are very soon at the limit of power.
 
Thanks for your help.
I've disabled streetmode at startup and reverted power and torque values to default.
I'm alos going to try the eMTB mode even if I'm driving a cargo bike.

Have a nice day ;)
 
IArchi said:
..
I've disabled streetmode at startup and reverted power and torque values to default.
..
Disabling streetmode I can imagine, but it is better to use the calibrated torquevalues with "estimated" enabled.
This calibration has as advantage that the assistvalues are as intended.

I advice to try all different assist modes with the default assist values as a base and see which mode you prefer.
From there experiment with lower or higher values.
 
I've found out what the problem is.
Because of merge #33, the EEPROM is not correctly cleared.
I've asked Emebrusa to fix this issue :)
 
IArchi said:
I've found out what the problem is.
Because of merge #33, the EEPROM is not correctly cleared.
I've asked Emebrusa to fix this issue :)
I don't understand what is the problem you want to report.
Can you be more specific?
What's wrong with the merge and where did you ask to fix?
 
I also have a problem when using the latest version TSDZ2-Smart-EBike-1-20.1C.2-update-2:
The when I hit "compile&flash" in the java configurator the complie batch file aborts showing this error:

Code:
process_begin: CreateProcess(C:\TSDZ2-Smart-EBike-1-20.1C.2-update-2\tools\cygwin\bin\sh.exe, C:/TSDZ2-Smart-EBike-1-20.1C.2-update-2/src/controller/../../tools/cygwin/bin/sh.exe -c "echo \"Cleaning files...\"", ...) failed.
make (e=216): Error 216
make: *** [clean] Error 216
Cleaning failed!!
Drücken Sie eine beliebige Taste . . .

I had this error also on all older versions, but it never caused the batch file to stop completely as with the newest version.
Here, compiling and flashing continued without any issues (as far as I can tell).
This is the message from an older Version:

Code:
process_begin: CreateProcess(C:\TSDZ2-Smart-EBike-1-master_old\tools\cygwin\bin\sh.exe, C:/TSDZ2-Smart-EBike-1-master_old/src/controller/../../tools/cygwin/bin/sh.exe -c "echo \"Cleaning files...\"", ...) failed.
make (e=216): Error 216
make: *** [clean] Error 216

Does anyone know what causes this error / sees the same error / knows how to get rid of it?
 
Hi endlessolli
You were quick to download this version, it was only online 2 minutes. :shock:
I removed it because before releasing it, I want to wait for the feedbacks from friends who are trying it.
The version works, it's still online as Master, in case someone wants to try it, I'll release it as a beta version.

I don't know what could be the cause of Error 216.
We await the answer from someone more informed.

I confirm that with the new version, the presence of an error interrupts the bach process.
If it worked before with the same error, you can try editing the clean.bat file, at the line "make clean || goto FAIL" replace with "make clean".
With this new version, SDCC version 4.1.0 or higher is required.
 
mbrusa said:
IArchi said:
I've found out what the problem is.
Because of merge #33, the EEPROM is not correctly cleared.
I've asked Emebrusa to fix this issue :)
I don't understand what is the problem you want to report.
Can you be more specific?
What's wrong with the merge and where did you ask to fix?

On Linux or MacOS, the EEPROM memory is not reset calling make flash. A call to make clear_eeprom is required first.
In the issue #37, someone is talking about settings that are not overwritten after flash.
I've created a new issue (#48) on your git and made a pull request (#14) to automatically compile and flash from Linux OS.

Edit: I'm not sure of what "Set parameters enabled on startup" does. Does it apply my settings at startup or just enable the admin menu in the display ?
 
IArchi said:
On Linux or MacOS, the EEPROM memory is not reset calling make flash. A call to make clear_eeprom is required first.
In the issue #37, someone is talking about settings that are not overwritten after flash.
I've created a new issue (#48) on your git and made a pull request (#14) to automatically compile and flash from Linux OS.

Edit: I'm not sure of what "Set parameters enabled on startup" does. Does it apply my settings at startup or just enable the admin menu in the display ?
"Set parameters enabled on startup" only enables the administration menu in the display.

I know little about Linux, thanks for the edit.
I tried, JavaConfigurator.jar works, but the java code in Netbeans gives me an error.
What will be the problem?
Java_errors.jpg
 
No problem.
I've taken a look at your issue. Apparently IntellijIDEA does accept that code but not Eclipse.
Solution is to replace OSType.Windows by Windows, etc.
I will edit my code on Tuesday (can't tomorrow nor today).
 
Hello mbrussa your firmwares dev are awesome‼️ we want to donate or help in a small way as im selling it here in the philippines, my 3rd batch of motors just arrived its just the new 860c cant reflash using apt bootloader. Hoping theres a work away around. pls send me your paypal as well😁 ty
 
mbrusa said:
Hi endlessolli
You were quick to download this version, it was only online 2 minutes. :shock:
I removed it because before releasing it, I want to wait for the feedbacks from friends who are trying it.
The version works, it's still online as Master, in case someone wants to try it, I'll release it as a beta version.

I don't know what could be the cause of Error 216.
We await the answer from someone more informed.

I confirm that with the new version, the presence of an error interrupts the bach process.
If it worked before with the same error, you can try editing the clean.bat file, at the line "make clean || goto FAIL" replace with "make clean".
With this new version, SDCC version 4.1.0 or higher is required.

Hi mbrusa;
what a strange coincidence that I downloaded in just these 2 minutes were it was availabe!

Anyhow - I found the reason why I get the errors - and the reason might be of general interest:

Short version: Although everything else of your opensource firmware compile & flash works on a 32Bit Windows system, the clean.bat file calls a 64Bit variant of a program - which obviously does not work on 32Bit Windows Systems and throws the stated error. (It is sh.exe and its dlls. They are located in C:\TSDZ2-Smart-EBike-1-20.1C.2-update-2\tools\cygwin\bin)

I am using an old Windows 32Bit Tablet for putting your firmware on my motors - as it is less clumsy than dragging a Laptop in the garage to work on the bike with it. Maybe some others also use an old 32Bit Windows system and maybe because of the missing clean sequence in the start of the compilation, this group of people gets sometimes inconsistent Motorbehavior.

So, I installed the latest 32Bit Cygwin Version on my tablet and added/replaced all needed files in the ...TSDZ2-Smart-EBike-1-20.1C.2-update-2\tools\cygwin\bin folder with the respective 32Bit files frm the cygwin install.
Now compile works without problems - also the latest one which you pulled again. (That one has some additional 64Bit only files which I replaced)
I zipped the "new" bin folder together and attatch it:
View attachment bin.zip

Hopefully, you can use these to replace the 64Bit files in your TDSZ2 Githubs, so this can help other users with 32Bit Windows.
(The 32Bit Versions should work for 32 and 64Bit Systems)

By the way: This problem was there since "ever" - I even checked the Kunteng OpenSource development - it was already there!)
 
mbrusa said:
Bad news.
So now, in addition to the new LCD3 and P850C, the new P860C are also non-flashable :?

OMG. I like P860C display but it can suddenly break. So maybe it's time to buy a few for storage.
 
I ordered LM35DZ from Mouser and they sent me SEN-10988 which is a TMP36. All the LM35 I ordered from Amazon appear shorted and get hot when connected to 6V. The new TMP36's (qty -5) all seem to work, but output F instead of C per spec. I called Mouser tech support and they don't have explanation. TSDZ2 OSF is looking for temp in C, so my displayed value is way too high. See my latest post in the Temp Hardware Thread…. https://endless-sphere.com/forums/viewtopic.php?f=28&t=102046&p=1741654#p1741654
 
Back
Top