Elinx said:Curious about the torque range of this third bike.StormTD5 said:.... have three bikes with tongsheng motors. ....
...Wow! The acceleration just at level 2! .....
I can measure in a couple of daysAnikea said:Torque Sensor hardware calibration....
No problem,StormTD5 said:,,,,,
I can measure in a couple of days
I understand Casainho, too many commitments, sometimes we need a break.casainho said:mbrusa, would you like to support the TSDZ2 wireless board? the wireless board acts like a display, the firmware is similar to the one of SW102 display, with the advantage that it connects already to our mobile app. And the only other new features are ANT+ LEV for wireless connection of cycling GPS displays and the wireless remote. There is also support for connection to a regular wired remote, for the ones who do not like to use the wireless remote. I don´t have free time to keep developing the motor firmware, wireless firmware, displays firmware, mobile app and GPS displays apps!mbrusa said:I saw this bug, already fixed.
I needed to reduce the number of variables in eeprom, so all bool variables are saved in bit instead of byte. I had entered this which is not bool, it happens ...
860C and SW102 firmware data fields / structure were mainly developed by other developer that is not active anymore on this project - all this firmwares and softwares were a BIG work collaboration from different developers, some that are not active anymore on this project.
So thoughtful of youElinx said:No problem,StormTD5 said:,,,,,
I can measure in a couple of days
I thought for some practice for you, to improve your display handling skills. :wink:
Yes, and this year I developed more due to the lockdown, unfortunately. I really miss the MTB events, with a lot of people!!mbrusa said:I understand Casainho, too many commitments, sometimes we need a break.
It could be interesting as a project but I have to think about it, before deciding I will have to understand what work involves.
I have all summer to think about it, programming is a winter hobby for me.
In the short term I will only follow the maintenance of the current version.
HughF said:This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.
Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:
Great job mbrusa and everyone who has contributed code and improvements to this over the years.
EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
Peacepirate said:HughF said:This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.
Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:
Great job mbrusa and everyone who has contributed code and improvements to this over the years.
EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
Excuse me but what firmware version are you actually talking about??? Fully operational on sw102???
Unless you havn‘t received a more updated version of the temporary available 0.20.1c i would like you to test the firmware in-depth and shut up before posting nonsense like „Fully operational“.
Sorry for being rude but i wasted a lot of time due to false information like yours!
Peacepirate said:Downloaded it from the link or received a version from developer?
JohnAnanda said:Peacepirate said:Downloaded it from the link or received a version from developer?
The current 20.1C for 850C/860C/SW102 from GitHub.
Peacepirate said:HughF said:This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.
Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:
Great job mbrusa and everyone who has contributed code and improvements to this over the years.
EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
Excuse me but what firmware version are you actually talking about??? Fully operational on sw102???
Unless you havn‘t received a more updated version of the temporary available 0.20.1c i would like you to test the firmware in-depth and shut up before posting nonsense like „Fully operational“.
Sorry for being rude but i wasted a lot of time due to false information like yours!
NOTHING is working fine with sw102!
Out of curiosity i installed this firmware although i was not unhappy with r0nkos firmware. The menu's are not „fully accessible and adjustable“ and the navigation does not „hang only every once in a while“ but ALWAYS!
1. Absolutly no access to menu „start boot“.
In the past months I tested 3 different forks for sw102 and i have never ever seen the content of this menu...
2. Menu „Torq cal“ opens but crashes ALWAYS immediately when you scroll down to enter a weight. First show-stopper for me! How am i supposed to use firmware reasonable if i can’t enter my sensor specific values?
3.If i change inside menu „torque cal“ to „calibrate enable“ and leave configuration screen the error „e: 2 Torqu“ appears on the screen after the „motor init Info“.
4. As already mentioned here somewhere above the shortcut for street mode is not working so no possibility to change legal/offroad mode - 2nd showstopper.
5. In the menu „technical“ i found it conspicuous that the value for „hall sens“ was only changing between 0 and 4.
6. Besides that the menues inside batt, soc and motor hang so often with the need to power off the whole system that i had to switch off the system every time i changed a value in the menu in order to save the edited value to avoid reenter everything when display freezes.
Maybe this info will be of any use for the developers or other sw102 users who consider to install this firmware in this temporary state of development. I can’t say anything about the motor response and won‘t unless at least the mentioned issues are‘t solved because this firmware is unusable for me at the moment.
Unfortunately it is not possible.casainho said:...
Can you please resume what features you removed and added to the original V1.1 firmware of 860C/SW102 displays?
...
ok but don't you know what features you removed?mbrusa said:Unfortunately it is not possible.casainho said:...
Can you please resume what features you removed and added to the original V1.1 firmware of 860C/SW102 displays?
...
The initial idea was to maintain compatibility with v1.1.0, at the first tests there were problems with memory ram and eeprom, even increasing the menu items the display often crashed.
For this I had to eliminate everything unnecessary for the new version.
I think there aren't many resources available yet.
mspider65 said:New v12 version of the controller firmware (only controller fw need to be updated):
https://github.com/TSDZ2-ESP32/TSDZ2-ESP32-Wiki/blob/master/bin/STM8/TSDZ2-v12.zip
For those interested in the changes made, just see the changes made with the last commit on github.
Casainho, I don't understand why you write this, it's not true.casainho said:...
ok but don't you know what features you removed?
I think is sad to lost the track of the features develop by me and other developers - for instance I was looking at your github repository and you did not fork any, you just uploaded the firmware without any history and that way is impossible to know what you did removed and what you did add - it is really important to keep the history so we can go back and see what was done and removed and understand why.
...
Peacepirate said:HughF said:This is fully operational on the SW102, and is really really fantastic firmware. The off the line performance in hybrid mode is fantastic.
Hopefully I'll get some miles on this one evening this week, if I can find my bike lights :lol: :lol: :lol:
Great job mbrusa and everyone who has contributed code and improvements to this over the years.
EDIT: I say fully operational - the menu's are accessible and adjustable, but the bugs in menu navigation are still there, the navigation hangs every once in a while, requiring a display power cycle.
Excuse me but what firmware version are you actually talking about??? Fully operational on sw102???
Unless you havn‘t received a more updated version of the temporary available 0.20.1c i would like you to test the firmware in-depth and shut up before posting nonsense like „Fully operational“.
Sorry for being rude but i wasted a lot of time due to false information like yours!
NOTHING is working fine with sw102!
Out of curiosity i installed this firmware although i was not unhappy with r0nkos firmware. The menu's are not „fully accessible and adjustable“ and the navigation does not „hang only every once in a while“ but ALWAYS!
1. Absolutly no access to menu „start boot“.
In the past months I tested 3 different forks for sw102 and i have never ever seen the content of this menu...
2. Menu „Torq cal“ opens but crashes ALWAYS immediately when you scroll down to enter a weight. First show-stopper for me! How am i supposed to use firmware reasonable if i can’t enter my sensor specific values?
3.If i change inside menu „torque cal“ to „calibrate enable“ and leave configuration screen the error „e: 2 Torqu“ appears on the screen after the „motor init Info“.
4. As already mentioned here somewhere above the shortcut for street mode is not working so no possibility to change legal/offroad mode - 2nd showstopper.
5. In the menu „technical“ i found it conspicuous that the value for „hall sens“ was only changing between 0 and 4.
6. Besides that the menues inside batt, soc and motor hang so often with the need to power off the whole system that i had to switch off the system every time i changed a value in the menu in order to save the edited value to avoid reenter everything when display freezes.
Maybe this info will be of any use for the developers or other sw102 users who consider to install this firmware in this temporary state of development. I can’t say anything about the motor response and won‘t unless at least the mentioned issues are‘t solved because this firmware is unusable for me at the moment.
Hmmm, I didn't know that about that forking limitations. Sorry, my mistake. I will then look to find the changes you did.mbrusa said:TSDZ2-Smart-EBike-LCD3 and TSDZ2-Smart-EBike-860C are not forks, you will know that with a free account it is not possible to fork the same repository more than once.
They are clones of mspider65 v7, on my repository it is still possible to see the difference between the two versions and for those who want to see the previous story, just go to the mspider65 repository.
Semogonif said:I've ride some uphill sections (moderate step) with no more than 500m, and I noticed (with assit 7), and surprisingly big increase of temp (I received an warning in the display). I've read that the bug with wrong temp display was solved, but I wander... The second surprise was the pwm values over those uphill sections, always over 150, is that correct?
Semogonif
Error "7 Comms", there are problems in the communication between the display and the controller.Semogonif said:...
I've installed de new v0.20.1c, on my 2 bikes, one MTB with 850C display, and a city bike with 860C, both with 48V motor. Unfortunately, the fw did not work on the MTB, the display shows an error: "7 comms", it is not documented on the wiki. Can you, please, mbrusa, give some advice? - It seems something wrong with the controller, it's not the display, I've tried both.
I forgot to report it, in the versions of mspider65 and therefore also in this one, the max PWM is not 100 but 254....
I've ride some uphill sections (moderate step) with no more than 500m, and I noticed (with assit 7), and surprisingly big increase of temp (I received an warning in the display). I've read that the bug with wrong temp display was solved, but I wander... The second surprise was the pwm values over those uphill sections, always over 150, is that correct?
Hi Jeff, I resume your speech on the thresholds for the color of the variables, yellow and red.jeff.page.rides said:A New Subject THRESHOLDS!
If the thresholds, would work correctly it will be a big help! Some work and some don't, I will show what ones work and what ones don't and the ones I haven't tried below.
Motor Power is the most useful and it does not work. I think you should be able to set what motor power thresholds were you want it to be white, yellow, and red. For example, up to 350 watts, it shows white so you enter 350 at the min Max threshold then at 350 it turns yellow, and you enter 450 at the max Max threshold, and at 450, and above it turns Red.
Thresholds will make the graph or numeric field values fade to yellow or red color, depending on the variable value. For instance, as soon as motor speed starts to approach near its max value, the color will fade first to yellow and then to red. You can disable, set to manual or automatic the thresholds. I spent a lot of time trying to get some of these to work trying manual and automatic. Some of the numbers you can set do no relate to what the display shows. Like motor power, you can set it up to 2000 I tried every combo I could and it doesn't work.
If someone out there would get Motor Power display threshold and any of the other displays threshold working that would be great! Having the displays turning colors when you want helps you keep the power in a safe zone just at a quick glance.