Thread: eCoach
View Single Post
Posts: 5 | Thanked: 0 times | Joined on Jun 2010 @ Oulu, Finland
#260
Originally Posted by mvonweis View Post
I've used Antti's patch for a month now, maybe a dozen runs and bike trips altogether. The delay is reasonable, connecting to the belt takes a handful of seconds and the heart rate is displayed after another 3-4 secs. I've had no problems whatsoever with reliability.

We don't understand the protocol well enough and the patch probably won't work for all users. My Polar uses 0xd1 as the key instead of 0xf1. I added another switch-case and now it WorksForMe(tm).

--Martin
I think your belt uses 0xf1 since I have set it originally as 0xd1. Anyhow, difference between 0xf1 and 0xd1 is only one bit (still no knowledge what it could be, chip revision or some other indicator). Also I have seen 0, 1, 2 and 3 in my dumps. IIRC one of those are pairs (1 and 2?) and it could be for example signal strength. It should be rather easy to verify by testing and also discover what are the rest of keys (battery, signal strength, signal quality, pulse quality, temp, etc.).

Unfortunately I broke my Nokia 6220c and I have no device to compare against Sports Tracker.

And also I think there is some problems to get connection and keep connection alive. When connection losses for some reason eCoach never tries to auto-connect I think. As a Sampo I think also there could be bidirectional communication protocol. Is that possible to set computer as Bluetooth repeater and snoop data?

br
Antti