I'm curious if it is neccesary to handle the torque temperature drift?
With the latest update to v0,20.1C3 I measured the torque values again and I found that these values drift in time.
I think it is because of the ambient temperature.
I have measured these the first time with v0.19 mbrusa_mods (dec-2019)
I didn't with v0.20b (feb-20) because only the range was needed, which I insert from 0.19
Now I have measured the torque values with v0.20.1C (apr-21) and v0.20.1C3 (jun-2021)
The range (125) is still the same as with 0.19, but min/max values are drifted 23 adc total.
In my case this is about 18,5% of the range
Besides the versions, the ambient temperature is different (dec/apr/jun)
Why I ask, because till 0.20b only the range was needed, but with versions 0.20. 1C-1C3 also the zero offset.
With 0.20 the default range is raised to 160 (10 bit) for the better torquesensor and software calibration was introduced for the less better ones.
But what happens if the range stays the same but zero offset and max value drift to a higher level?
0.19mb - 121-246
20.1C1 - 133-258
20.1C3 - 143-268
tr8 said:
...
If no one else has these problems I will try the v20.1C.3 ...
After reading your post, I have tried it too, but my pedals runs just a half rotation after pushing the pedal and then stops.