Bluetooth Speed Sensor off by Factor 2

Ulrich Kiermayr shared this problem 1 year ago
Solved

I noticed that there are now seperate BT Speed and Cadence Sensors avaliable. In Principle this works, but the Values displayed in Locus for a Speed-Only sensor are off by a Factor 2 (See Screenshot).


Btw. For the Cadence Sensor the Setting of a Circumfence does not really make sense ;-)


Greetings Ulrich.


b5828db36c0818bb1b998d8a95c150cd

Comments (8)

photo
1

Good day Ulrich,

thank you for this bug report. I was improving handling of speed & cadence sensor last week and based on found documentation, I've also improved reading values. I remember I've looked on it with thought, that it may give double sized results, but well ... official documentation is official documentation :).


Anyway sorry for complications. Issue will be fixed in next version!

photo
1

Correct. I have a bluetooth sensor with combined speed and cadence. Cadence gives correct values. Speed gives 2 times the actual speed. Version 3.22.2

photo
1

Hi, I am facing the same problem with my combined ant+ speed/cadence sensor. The speed semms to be multiplied with 2.


Kind regards

Michael

photo
1

Good day Michael,

ANT+ sensors works differently compare to BT sensors we discussed here. I'm rather checking app source code and all seems to be correct. If you have any recorded track with speed sensor, may you share it here exported to GPX v 1.1, so I may quickly check results? Thanks

photo
1

Hi Menion,

I attached two screenshots of the tracks graph. The gpx file is also uploaded. Thanks for the quick reply :)


9c2ab23bd8ee64abf91319f207204ef1a487fa414016da0f4612842c4fa704d8

photo
1

Hello Michael,

thanks for sharing your recorded data.

I'm checking source code for this function and it is completely hidden behind API from ANT+ manufacturer and only parameter that affect it is set circumference. May you please also check if you have correctly set this parameter for user ANT+ sensor? Thank you.

photo
1

Checked it and it is OK.

photo
1

Good day Michael,

sorry for a delay with my response. I'm checking it now once more and I'm almost sure, that in Locus code is no problem. I'm also comparing my code with a sample provided by ANT+ manufacturer and it seems to be identical.

Because of this, may I ask you for one more test: best to try your sensor with different application that is capable to read and record ANT+ speed values. As I know, it should work in OruxMaps or IPBike apps. Thank you.

Circumference parameter is defined in mm units, so I personally have on bike value 2080 ... just for sure.

photo