search

snowzach / echbt

55 stars 3 forks source link

Trouble getting cadence info #3

Closed mikefulb closed 3 years ago

mikefulb commented 3 years ago

I tried the sketch recently and had trouble getting the cadence notifications enabled. I did see resistance values but the callbacks with data[1] == 0xD1 never gave a different value for cadence even after pedaling awhile.

Do you know that the existing code works with recent Echelon Sport Connect bikes?

Thanks!

snowzach commented 3 years ago

I have a sport connect that's less than 6 months old. In order for the bike to send cadence information you have to send an initial value to the bike. It only occasionally sends the cadence update. The only thing I can imagine is that they somehow changed the value you need to send to get it started maybe.

mikefulb commented 3 years ago

Thank you for the quick feedback.

I was thinking maybe they had changed the value as well.

However I will say your Android app works great so I was curious if it is using the same mechanism as echbt here does. If so then that might mean they haven't changed anything and perhaps I have made an error.

snowzach commented 3 years ago

Yeah, if the android app is working then it's something in the code there. They are basically the same.

On Mon, Mar 15, 2021 at 9:40 AM Michael Fulbright @.***> wrote:

Thank you for the quick feedback.

I was thinking maybe they had changed the value as well.

However I will say your Android app works great so I was curious if it is using the same mechanism as echbt here does. If so then that might mean they haven't changed anything and perhaps I have made an error.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/snowzach/echbt/issues/3#issuecomment-799427500, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXXSALKHIVT7VCAECGHZYTTDYE3TANCNFSM4ZFLDAHA .

mikefulb commented 3 years ago

Thanks I'll go back and check what I've done and I'll close this as it doesn't seem to be an issue with the code here.