You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My torque sensor from my Cowboy V3 seems to have a problem and apparently, the offset value is not read out properly? Out of interest, I tested the sensor according to your instructions via the app, and the current value measured approx. 0.3V (the sensor responds to force) and the offset value 0.8V. The bike rode just as badly. The strange thing is that the offset is at 0.8V when it should be at 0.5V. I then contacted support and they wanted to calibrate the sensor via the Backoffice app. The calibration seems to work and the offset value is set to 0.3V (the difference is also subtracted from the full value, so the range is shifted). This improves the bike ride, but the sensor is still marked as faulty in a diagnosis via Backoffice because it is not in the range of 0.4 to 0.7V. Strangely, the offset value in untamed is still displayed as 0.8V. Either untamed reads out a different value or Backoffice does not write the offset value correctly. At least I can write the offset value via untamed and I also have the feeling that it changes something when driving.
Besides the described problem, a calibration via untamed would be a very useful feature, as Backkoffice only exists for IOS and it has to be activated by the support.
The text was updated successfully, but these errors were encountered:
My torque sensor from my Cowboy V3 seems to have a problem and apparently, the offset value is not read out properly? Out of interest, I tested the sensor according to your instructions via the app, and the current value measured approx. 0.3V (the sensor responds to force) and the offset value 0.8V. The bike rode just as badly. The strange thing is that the offset is at 0.8V when it should be at 0.5V. I then contacted support and they wanted to calibrate the sensor via the Backoffice app. The calibration seems to work and the offset value is set to 0.3V (the difference is also subtracted from the full value, so the range is shifted). This improves the bike ride, but the sensor is still marked as faulty in a diagnosis via Backoffice because it is not in the range of 0.4 to 0.7V. Strangely, the offset value in untamed is still displayed as 0.8V. Either untamed reads out a different value or Backoffice does not write the offset value correctly. At least I can write the offset value via untamed and I also have the feeling that it changes something when driving.
Besides the described problem, a calibration via untamed would be a very useful feature, as Backkoffice only exists for IOS and it has to be activated by the support.
The text was updated successfully, but these errors were encountered: