Discussion notes related to profiles other than ANT-FE

Option 1: Multi-Sport Speed and Distance...

1. Does not contain “Cadence” or “stroke rate” and therefore is not suitable.
2. Use case “Note” specifically advises against using this profile for our purposes.

Option 2:  “Bicycle Power”....

Ross Comment: >> couple good ways to use it for Edge 8000 and 705 of other bicycle power display devices that are in wide use, but would user base use it....   So we should ignore this.

pages 10 11 12 20

0x01

Limitations/objections:

1. would need to convert power (watts) to velocity (pace) on the display as time/500m.  This seems doable as watts has higher resolution than time in seconds/500m when converted.
2. Cannot send HeartRate information (would need to add a page or another channel?)
3. Cannot send stroke count, unless use eventcount (which I suppose is possible)
4. Cannot send distance gone, or accumulated time (would need to add a page or another channel)
5. Can only imagine using power-only sensor message...not the others...
6. Don't really have a 'calibration' so would just have to ack it without doing anything.. Unless we wanted to use this as a 'reset' to zero or something like that.

0x10

Event Count (rollover at 256)

Pedal Power – Not used so 0xFF

Instant Cadence – 20-254 Strokes/Minute.    0XFF is invalid; maybe 0= not rowing

Bytes 4,5 Accumulated Power in 1 watt resolution (rollover at 65KW)

Bytes 6,7 Instant Power in 1 watt resolution (max 65.5KW)

Option 3: Bike Speed and Cadence sensor:  

Ross Comment: >> Probably not appropraite but would start talking to lots of bike watches, just showing velocity, etc...

1. Seems like not enough information being passed
2. Still no heart-rate information available
3. choice of either 'separate channels for speed and cadence' or 'single channel on what appears to be a depreciated format...'
4. no way to get meters across unless we 'faked' the data.

Though that said, I suppose...

Per 4.2.5 could use...

page 0x00; ff; ff;

bike speed event time =  timestamp

cumulative revolution count – could assume 1m per revolution, this provides a meter counter.  Used in conjunction with timestamp we should be able to get avg speed and instant speed.

Interleave with cadence on a 2^nd channel to get cadence... Bike Cadence Event Time: a timestamp which rolls over ever 64 seconds; and Cumulative Cadence Revolution Count - increment on beginning of each stroke.