Building a cadence sensor from Cycling Speed and Cadence Service module

[tim]

I am building a cadence sensor form the Cycling Speed and Cadence Service module.

Unfortunately the sensor I have built is recognized to have both speed and cadence when it is only supplying cadence. This prevents me from using separate speed and cadence sensors.

I have based my code on the nRF51 SDK 5.2.0 Cycling Speed and Cadence Service example s110/ble_app_cscs modified to work with the nRF51822 evaluation board.

I have attach the differ of the changes I made to advertise the appearance of the Cycling Speed and Cadence Service as Cadence Service ONLY..

main.diff.txt

[elgogi]

Hi

I'm having the same problem. I'm trying my sensor to be recognised as "only cadence" sending just cadence and changing the appearance, but it's recognised as "Speed and cadence". It seems that there is no spec in the Bluetooth page to build a "cadence only" service.. I'm confused. Were you able to discover something finally?

[wlgrd]

From the list of Bluetooth specified services you see that this is a standard service. In your code, it uses the UUID of this service, BLE_UUID_CYCLING_SPEED_AND_CADENCE which is predefined to 0x1816 and will for all devices compliant with Bluetooth 4 show as both speed and cadence.

If you want only one at the time, you should go for a custom UUID and your own naming convention.

[Linxi]

Hi, Apps have responsibility to recognize cadence or speed or combined sensor ,based on appearance or feature which sensor has provided through advertising packets. It's not your fault. It's up to app's design requirements .You can see my reply here. link text