Currently you are trying to stabilize v0.20.0. After that version, the EEPROM code should be removed as also run time configurations variables initialization. On that time, I think we will have a working version of firmware for SW102 and for 850C displays.buba said:
casainho said:Finally we own the TSDZ2 torque sensor!!
Up to now we were reading the torque sensor in a wrong way and it could only measure up to 25 kgs. Also there is a big different from the values read on left or right pedal. This are the output values of my torque sensor (that I bought 3 weeks ago):
I implemented the linearization of the torque sensor measures and it can now measure up to at least 102 kgs (which is my weight). I also implemented a linearization based on a table with values for left and right pedal and it works very well: before my right pedal was measuring the 102 kgs of my weight but left pedal would measure only 70 kgs, now both pedals measure the same values.
Before my display was showing to me a value of pedal human power of a bit more than 100 watts, no matter the force I did and now, I can go up 400 watts for short peaks. I think strong cyclists will love to see their real pedal human power on the display!!
And by the way, I am pretty sure there is no need to calibrate the sensor as I did before, no need to open the motor and adjust the hall sensor position of the torque sensor.
Calibration process
1. user put values on right pedal, starting at 5 kgs, in steps of 5 kgs up to about 30 kgs. Finally put itself on the pedal with his known weight value. The pair of weight and torque sensor ADC value should be registered and later user will need to decide for 5 points only, 1 at start, other at the last value and 3 values near the knee on the graph, as shown on the graphs.
2. Repeat for left pedal.
3. Put the pair values of weight and torque sensor ADC values, for each pedal, on the specific LCD configuration menu.
One important thing for all this work is that at system power up, the right pedal should be pointing to ground -- as there is the need to identify which pedal we are doing the force and there is no way to identify them, I decided to do like this, having the pedal at a known position at startup and after that everything will work well.
I have the code working on my bicycle and I can see on the LCD the weight value in kgs on the LCD. The tables for linearization are for now hardcoded on the firmware, I can't setup them yet on LCD. When we have the next version of firmware I can add this feature to it.
Rafe said:buba said:
I did answer your questionnaire on throttle data Buba but you may have missed it with the deluge of responses you have had in the last 3 days
https://endless-sphere.com/forums/viewtopic.php?f=30&t=93818&start=3025#p1486393
Thank you by the way!buba said:Rafe said:
Would you mind testing one last thing so we can confirm something? :wink:
Can you set the power limit to 1000+ watt and increase the max battery current to 18 A? And then try the throttle and see if it reacts more as one would expect.
Rafe said:You also asked me about Cadence on the BBS HD but since then Perryscope has replied and I could not add anything useful to his (or her) excellent answer. I also set my BBSHD up a couple of years ago and have never had to revisit the settings. The throttle works like a throttle though
Thank you for taking an interest but don't put yourself out too much over it. I tend to use the manual throttle in a sudden situation where it is not possible to pedal and just need it to keep the bike moving and it does that just as it is now except it can be too much help. For now though I will disable cadence mode as your other 3 modes are more than enough to play with and enjoy. If only someone would come up with a tougher plastic gear, the metal gear is too noisy but lasts forever and the blue gear is quiet but suddenly fails under too much load.
Okay, totally agree. Let us put Cadence Assist on hold for now and just think about it in the back of our heads. A lot of things going on now. There is a chance we will revisit this when everything else settles
Also agree on your comments regarding the gear!
mspider65 said:
NexusG said:
NexusG said:
buba said:
casainho said:
buba said:
casainho said:
Please follow the information bellow and ask if you have more questions. I need your feedback and this process is not fast, I would like to know if in the end you see/feel any advantage of doing the calibration.fi7ippo said:
perryscope said:
perryscope said:
Really sorry for the inconvenience in the meantime but now you know why they are flying around! perryscope said:
perryscope said:EMTB mode also does not feel to be giving as much power as I expected, again I will experiment with the sensitivity value to see if that helps scale it more to my legs
buba said:perryscope said:
Hello Perrscope,
Yes I can confirm that the fix will work for any setup.
Clarification: I immediately knew what the problem was when users started reporting lack of assistance at 90 cadence. There was a experimental transition there. I have removed this transition and everything will work as usual for all users and setups.
perryscope said:
So sorry about that! I previously explained it is for my sake as the raw values does help me to debug at a much faster rate. One example is the "90 cadence problem" you mentioned. If the cadence was filtered there would be a lot of people reporting a far lower value taking it longer to pinpoint the problem. The very first time a user reported "90 cadence" to be a problem I immediately knew what the problem was.
However, I think there are no other bugs reported so I might as well add the filtering in the Alpha 3!
perryscope said:
Absolutely! Try increasing the acceleration as it can be set to the same or even faster than 0.19.0. If you feel you do not receive enough assistance from startup you maybe need the "startup without pedal rotation"? That will come back in a new form in the Alpha 3.
Please try to configure after your likening and let me know if you are satisfied. The 0.20.0 can be configured in more ways, has more functions and features and is overall smoother and safer than all previous versions. The only thing it lacks is the Startup Boost which I have tried to include in all riding modes and in the "startup without pedal assistance" present in Alpha 3.
Clarification: I will do whatever it takes so that every single user feels that the 0.20.0 is better in every regard than 0.19.0. You will just have to configure after your preference.
perryscope said:EMTB mode also does not feel to be giving as much power as I expected, again I will experiment with the sensitivity value to see if that helps scale it more to my legs
Definitely try increasing the sensitivity! The default values are often taken out of thin air and everything depends on your particular torque sensor and setup. But as I get more feedback I can put better default values that are more appropriate. But the best approach is to always setup the bike after your own preference.
And my goal is that you will never have to reset the firmware so the configuration you have now will stick around a long time. Will do my best to never force another user to reconfigure their setup. This has taken a lot of thought and planning and if we are lucky it will work beautifully!
perryscope said:No need to apologies Bubu its an Alpha and totally expect it to be running in a debug mode. I just want to help as much as possible by feeding back my experiences
Just as a side thought, I noticed you have added the 8 segment display logos for 'Power assist', 'Torque assist' and 'Cadence assist'. This is very useful when navigating the menus to find the right section to change ( especially when the settings within those menus are so similar).
Would it be possible to show those logos while selecting the menus without having to go into each one?
I know I will learn the numbers over time but at the moment i do find i am having to refer to the wiki page on my phone allot to check which menu is which and relearn between versions. as you are going through the menus a clue as to what menu you are about to select would be helpful i think?
You could maybe add other 8 segment display icons for the all?
0 Basic = b
1 Battery = B
2 Power Assist = P
3 Torque Assist = t
4 Cadence Assist = 'cadence symbol'
5 eMTB = E
6 Walk Assist = l l
7 Cruise = C
8 Screen = O
9 Street Mode = S
10 Advanced= A
11 Advanced Technical Data = _
just helps spot the relevant menu quicker maybe? Not an issue on the 850C or SW102 screens but I still think there is like in the LCD3 yet
buba said:
One interesting thing about SW102 is that has 4 buttons instead of the 3 like on KT-LCD3 and 850C displays. This means more way for user interact and quick change features options.buba said:
casainho said:
perryscope said:buba said:
edit: rethinking this a little for a later alpha. dont want you to delay Alpha 3 release :wink:
0 Basic = b
1 Battery = (show full battery symbol)
2 Power Assist = P and 'Assist' segment
3 Torque Assist = t and 'Assist' segment
4 Cadence Assist = (cadence crank symbol) and 'Assist' segment
5 eMTB = E
6 Walk Assist = (show walk assist person segment and word assist)
7 Cruise = (Show 'Cruise' and 'Assist' segments)
8 Screen = O
9 Street Mode = S
10 Advanced= A
11 Advanced Technical Data = _
