TSDZ2 mid drive with 860C, 850C or SW102 displays only -- Flexible OpenSource firmware (Casainho code only)

[ezrider1199]

Hello ! is it possible to make the option of changing the assist stop? currently at 0.6.9 it is such that when we stop pedaling the engine is spinning for one second. I do not want to use brake sensors, I prefer the engine to stop abruptly. In 0.19 and 0.20 this problem was gone. Regards

It's called overrun, i think a dev is working on a solution to this and said he will put in a PR when he's ready

 

[ezrider1199]

casainho, now that we have multiple screens is it possible to implement a couple more metrics? 1) watts/unit distance and 2) avg speed. these are some of the things the cycle analyst has:

Display #1, Main Screen Summary of battery level, speed, power, voltage, distance etc.
Display #2, Electrical Only View of just the battery voltage, current, power, and amp-hours
Display #3, Human Power Shows pedal cadence and human power if torque sensor installed
Display #4, Wh/km Battery watt-hours and energy consumed per km or mile
Display #5, Human Stats Average human power, pedal cadence, and total human energy output
Display #6, % Regen Shows regenerative amp-hours and % by which it has extended your range
Display #7, Peak Stats Shows peak current, peak regen current, and battery voltage sag
Display #8, Speed Stats Maximum and average trip speed and total trip time
Display #9, Temp Stats Shows current, average, and maximum temperatures if sensor is attached
Display #10, Odometer Shows both current trip distance and lifetime odometer
Display #11, Batt Info Charge cycle count, total kWh energy used, and Battery internal resistance
Display #12, Diagnostics Live readout of throttle input/output voltages and active limiting flags

also i consistently run into the issue with unintended acceleration. just the other day, i changed the display to show volts instead of SOC% and luckily i was on my bike because it started delivering 700+ watts right away. i had to restart the display. lastly, the reason i cant use SOC% is because it only saves values when you turn off using the display power button. if using the battery switch to cut power nothing gets saved and many features on the display become inaccurate...

 

[casainho]

casainho, now that we have multiple screens is it possible to implement a couple more metrics? 1) watts/unit distance and 2) avg speed. these are some of the things the cycle analyst has:

Display #1, Main Screen Summary of battery level, speed, power, voltage, distance etc.
Display #2, Electrical Only View of just the battery voltage, current, power, and amp-hours
Display #3, Human Power Shows pedal cadence and human power if torque sensor installed
Display #4, Wh/km Battery watt-hours and energy consumed per km or mile
Display #5, Human Stats Average human power, pedal cadence, and total human energy output
Display #6, % Regen Shows regenerative amp-hours and % by which it has extended your range
Display #7, Peak Stats Shows peak current, peak regen current, and battery voltage sag
Display #8, Speed Stats Maximum and average trip speed and total trip time
Display #9, Temp Stats Shows current, average, and maximum temperatures if sensor is attached
Display #10, Odometer Shows both current trip distance and lifetime odometer
Display #11, Batt Info Charge cycle count, total kWh energy used, and Battery internal resistance
Display #12, Diagnostics Live readout of throttle input/output voltages and active limiting flags

also i consistently run into the issue with unintended acceleration. just the other day, i changed the display to show volts instead of SOC% and luckily i was on my bike because it started delivering 700+ watts right away. i had to restart the display. lastly, the reason i cant use SOC% is because it only saves values when you turn off using the display power button. if using the battery switch to cut power nothing gets saved and many features on the display become inaccurate...

Yes, I would like to have estimation of range in kms based on previous last interval time, that could be configured like last 5, 10 or 15 minutes. Maybe someone will do it.

I don't know if there are many users like you, maybe someone will make a difference implementation including deep testing as a bad implementation can damage permanently the display.

 

[ezrider1199]

Yes, I would like to have estimation of range in kms based on previous last interval time, that could be configured like last 5, 10 or 15 minutes. Maybe someone will do it.

I don't know if there are many users like you, maybe someone will make a difference implementation including deep testing as a bad implementation can damage permanently the display.

it doesn't have to be that complex, just a simple watts used/trip distance would be great to gauge your consumption trip to trip.

I realize too many writes to the eeprom can shorten the life span of the display so here's a very safe way to do it:
"is the bike stopped, yes --> is the saved odo different from the actual odo (difference by 0.1 mile or more), yes --> save values"
you can put more safety checks, like is the bike stopped and has it been over a min since last save? so it doesnt write in stop and go traffic or red lights.

2 similar issues about this including my own (actually 3 but one duplicate):
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/66
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/61

also there are issues on github reporting about unintended acceleration, i see 3 similar issues (including my own). there has to be some sort of error when exiting the menu because that's when i encounter my issue:
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/81
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/82
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/76

relying on my bike and your firmware for daily use i feel these changes are relatively small compared to the work you've put in just in the past several months. however they would greatly improve this already good firmware. just like making the buttons more responsive, it was a small but huge change and because of it i feel i dont need the throttle anymore, i can adjust the assist level much quicker. anyways thanks for all - just wanted to get my thoughts out.

 

[casainho]

Yes, I would like to have estimation of range in kms based on previous last interval time, that could be configured like last 5, 10 or 15 minutes. Maybe someone will do it.

I don't know if there are many users like you, maybe someone will make a difference implementation including deep testing as a bad implementation can damage permanently the display.

it doesn't have to be that complex, just a simple watts used/trip distance would be great to gauge your consumption trip to trip.

I realize too many writes to the eeprom can shorten the life span of the display so here's a very safe way to do it:
"is the bike stopped, yes --> is the saved odo different from the actual odo (difference by 0.1 mile or more), yes --> save values"
you can put more safety checks, like is the bike stopped and has it been over a min since last save? so it doesnt write in stop and go traffic or red lights.

2 similar issues about this including my own (actually 3 but one duplicate):
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/66
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/61

also there are issues on github reporting about unintended acceleration, i see 3 similar issues (including my own). there has to be some sort of error when exiting the menu because that's when i encounter my issue:
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/81
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/82
https://github.com/OpenSource-EBike-firmware/Color_LCD/issues/76

relying on my bike and your firmware for daily use i feel these changes are relatively small compared to the work you've put in just in the past several months. however they would greatly improve this already good firmware. just like making the buttons more responsive, it was a small but huge change and because of it i feel i dont need the throttle anymore, i can adjust the assist level much quicker. anyways thanks for all - just wanted to get my thoughts out.

The really URGENT thing is the problem with unintended acceleration!!

 

[bingo5]

Hi Casainho, have the street mode any priority for you?

I am waiting version for version but unfortunately no street mode yet. Maybe you don't need street mode and therefore you don't implement it?

 

[ezrider1199]

The really URGENT thing is the problem with unintended acceleration!!

well, of course. im actually surprised more people arent commenting on it.

 

[casainho]

Hi Casainho, have the street mode any priority for you?

I am waiting version for version but unfortunately no street mode yet. Maybe you don't need street mode and therefore you don't implement it?

Street mode needs a lot of thinking in terms of the user interface implementation. There are a lot of work to do and I am alone, everyone need to lower the expectations.

 

[James Broadhurst]

Does anyone know if it is possible to display imperial units for distance (miles, MPH etc) whilst also displaying temperature in degrees C. These are the preferred units here in UK. I cant get my head around the Fahrenheit scale any more. Thanks

Yes. Go back to using a KT LCD3 where the temperature is in degrees celsius. I can’t quite understand why it was perfectly ok to do this until along came the colour displays .... !

 

[bingo5]

Street mode needs a lot of thinking in terms of the user interface implementation. There are a lot of work to do and I am alone, everyone need to lower the expectations.

okay, I can understand that. Thank you for the response. I hope that geeksville, buba or somebody else can help develop soon. Unfortunately, I can't program. The only thing I can do in the future (as soon as I use SW102) is to translate the wiki to german.

 

[casainho]

Street mode needs a lot of thinking in terms of the user interface implementation. There are a lot of work to do and I am alone, everyone need to lower the expectations.

okay, I can understand that. Thank you for the response. I hope that geeksville, buba or somebody else can help develop soon. Unfortunately, I can't program. The only thing I can do in the future (as soon as I use SW102) is to translate the wiki to german.

No, do not translate!! It should be the contrary, everyone should learn the simplified English.

 

[casainho]

Does anyone know if it is possible to display imperial units for distance (miles, MPH etc) whilst also displaying temperature in degrees C. These are the preferred units here in UK. I cant get my head around the Fahrenheit scale any more. Thanks

Yes. Go back to using a KT LCD3 where the temperature is in degrees celsius. I can’t quite understand why it was perfectly ok to do this until along came the colour displays .... !

The SW102 is not a color display. The options now are much better, SW102 smaller display and 860C/850C big display.

KT-LCD3 is old technology and with many limitations, that prevent the implementation of good features we have now.

 

[troebi]

Last season I was riding with V0.18. Quite satisfied, actually. Now I used the time over the winter to revise the setup: exchange the blue gear for the brass metal gear, prophylactic replacement of the freewheel ball bearing (incl. main gear in helical version), new display (SWD102), temperature sensor and better thermal connection of the motor to the housing.

Some experience:
the latest version sw102-otaupdate-0.6.9 does not work correctly. The start screen etc. is missing immediately after switching on.
I am currently quite satisfied with V 0.6.8. However, the display freezes from time to time during configuration. Only a hard reset helps. If only 2 to 3 parameters are set, it works.
The 20 levels are chosen sensibly. The torque sensor is already good without calibration.

Currently I still miss the street mode
A more pleasing graphic would be cool - but that's really just nice to have.
A big thank you to all programmers! You (especially Casainho) do a great job.

 

[Markus61]

Hi to all,
I have a problem, after updating to the latest version 0.6.9 on the 850C display appears the message "Software error TSDZ2".
What to do with this?

 

[izeman]

No, do not translate!! It should be the contrary, everyone should learn the simplified English.

I agree. ONE consistant version of the Wiki is better than several not up2date language versions (with the risk of translation error, that will never be checked by someone relevant).
Google translate can translate an English version to almost all languages worldwide and give understandable text, if you can't read English at all.

 

[AZUR]

Hi all,

https://www.electricbike.com/tsdz2-...RBBqUNjH9yNYlznvSUXgGvWtpUW0dxXWaQiur1ZqnrTuw

 

[Brlowe]

Thinking I should have posted this here so sorry for the double post over on the other TSDZ2 thread.

Hello all,
I finally got my TSDZ2 installed and love it. I have the latest v0.6.8 and v0.55.0 installed and I have a couple issues.
First I have the motor surge while coming out of the settings menu.
Second I have twice had it where I turn the system on and after it is fully on I put my feet on the petals and start to petal and the motor surges the the whole system shuts off. I can repeat this continually. To fix it I have to go back into the settings menu select something then exit and restart it. I do not change anything just have to go into the menu.

Last is a question, after going into the settings menu do you always have to come out and restart the system?
Also after a 10 mile ride at power setting 7 the motor temp got up to 140. Is this normal?

Thank you

 

[hefest]

Thinking I should have posted this here so sorry for the double post over on the other TSDZ2 thread.

Hello all,
I finally got my TSDZ2 installed and love it. I have the latest v0.6.8 and v0.55.0 installed and I have a couple issues.
First I have the motor surge while coming out of the settings menu.
Second I have twice had it where I turn the system on and after it is fully on I put my feet on the petals and start to petal and the motor surges the the whole system shuts off. I can repeat this continually. To fix it I have to go back into the settings menu select something then exit and restart it. I do not change anything just have to go into the menu.

Last is a question, after going into the settings menu do you always have to come out and restart the system?
Also after a 10 mile ride at power setting 7 the motor temp got up to 140. Is this normal?

Thank you

Wow, 140 celsius? Definitely not normal. Are you sure your temperature sensor is not faulty?

What do you mean by whole system shuts off? This is what happened to me and after times my controller was fried. Could it be something about faulty firmware that fried my controller?

 

[Brlowe]

Thinking I should have posted this here so sorry for the double post over on the other TSDZ2 thread.

Hello all,
I finally got my TSDZ2 installed and love it. I have the latest v0.6.8 and v0.55.0 installed and I have a couple issues.
First I have the motor surge while coming out of the settings menu.
Second I have twice had it where I turn the system on and after it is fully on I put my feet on the petals and start to petal and the motor surges the the whole system shuts off. I can repeat this continually. To fix it I have to go back into the settings menu select something then exit and restart it. I do not change anything just have to go into the menu.

Last is a question, after going into the settings menu do you always have to come out and restart the system?
Also after a 10 mile ride at power setting 7 the motor temp got up to 140. Is this normal?

Thank you

Wow, 140 celsius? Definitely not normal. Are you sure your temperature sensor is not faulty?

What do you mean by whole system shuts off? This is what happened to me and after times my controller was fried. Could it be something about faulty firmware that fried my controller?

No it is 140F temp. Before using it I compared the temp to the air temp it had been sitting in and it was correct. The motor was just slightly warm on the outside when it was 135 on the reading.

 

[skestans]

140F is around 65C. That sounds par for the course.

 

[casainho]

Wow, 140 celsius? Definitely not normal. Are you sure your temperature sensor is not faulty?

What do you mean by whole system shuts off? This is what happened to me and after times my controller was fried. Could it be something about faulty firmware that fried my controller?

Current firmware version has a problematic issue. I am working hard to try solve it ASAP.

 

[hefest]

Second I have twice had it where I turn the system on and after it is fully on I put my feet on the petals and start to petal and the motor surges the the whole system shuts off. I can repeat this continually. To fix it I have to go back into the settings menu select something then exit and restart it. I do not change anything just have to go into the menu.

Having had the similar sympthoms where my whole drive turned off several times when I start pedaling, and after 4-5 attempts I had a short on my controller power pins resulting in huge spark and melted battery terminals, I would advise you to stop using current firmware and downgrade until we have fix from casainho.

Maybe my issue was due to faulty controller but just to be on the safe side.

 

[orangecrumble]

1. Check to see if you are hitting the max PWM value, cadence, etc. Would be great if you could compare this values between the firmwares and get technical detailed information about what can be different -- compare the source code of both.

2. Don't know, that does not happen to me. Try reset to defaults and see it that solves.

1. I will take it for a ride at the weekend and see what I am hitting the maximum on, either pwm or cadence. Unfortunately I cannot easily test back to back with the vlcd6 I had before as I cut the cable off that to solder onto the SW102.

2. I reset the defaults and it went up to level 20 after a reset. I took it for a small ride and then when I got back it would not go above 12 again. I think I did the ride on level 10 if I remember correctly. I will try and find what causes this to be repeatable.

I get random lockups when navigating the configuration menu, usually when trying to exit a sub-menu.

I also got the 12 assist level issue (sw102), worked out that it was changing to imperial units, conversion factor of approximately 0.6 would be my guess, now riding in kph as my brain can work out km/h to mph if i ever worry about speed. I hardly ever ride on the road. Also getting random lockups and can't get into torque sensor menu. I only recently flashed my motor, the 0.19 release then the latest. the flash to the latest convinced me to install a brake sensor due to the overun. when I do mtb I know I use my rear brake to balance the bike in tricky sections and wouldn't appreciate too much power coming in by accident. Brake sensor cuts it beautifully

 

[vshitikov]

Anybody here complies Casainho code on windows? I have installed everything and finally managed to compile, though some warnings appear but I guess it's because there is some provisionary code. But to do so I had to tweak manually the makefiles and add some declarations because windows handles the directories quite differently. But I'm not sure what i'm getting , only main.bin How to get the .hex file? Sorry didn't have the energy to look into google.

 

[Rydon]

Anybody here complies Casainho code on windows? I have installed everything and finally managed to compile, though some warnings appear but I guess it's because there is some provisionary code. But to do so I had to tweak manually the makefiles and add some declarations because windows handles the directories quite differently. But I'm not sure what i'm getting , only main.bin How to get the .hex file? Sorry didn't have the energy to look into google.

If you get this figured out for windows can you please document it? I would like to compile a version with my own defaults. I flash a lot of TSDZ2 motors and configuring them after flashing them is laborious.