You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the product name at the end is too short (not 14 characters as expected by the code), the app crashes. I hacked together a simple fix for this, so that the string is not hardcoded:
I don't know what the data is supposed to look like according to the protocol, so my solution is very much hacked. If you can point me in the direction of the protocol documentation, I can come up with a better solution.
Apart from this small (but critical) issue (and the fact that it sometimes takes very long to connect - see issue #15), it works with my FR70 (just uploaded my first data to Garmin Connect!). The dates are incorrect, but I'll investigate this another time.
The text was updated successfully, but these errors were encountered:
Yeah, I've assumed a fixed length. Seems like my assumption about the protocol was correct and that byte 11 of this sequnce is the string length. I'll update the protocol documentation and the code to fix this.
About protocol documentation -- I'm not sure there is one, or if there is one that can be used safely for an open source program. My own findings can be found here.
When connecting to my Garmin FR70, it fails when parsing the response for REQUESTID.
The data returned from my device is the following:
[67, 52, 3, 3, 255, 255, 255, 255, 68, 132, 0, 5, 14, 158, 18, 0, 70, 82, 55, 48, 0, 0, 0, 0]
As the product name at the end is too short (not 14 characters as expected by the code), the app crashes. I hacked together a simple fix for this, so that the string is not hardcoded:
https://gist.github.com/cfb35603676929c02cb4
I don't know what the data is supposed to look like according to the protocol, so my solution is very much hacked. If you can point me in the direction of the protocol documentation, I can come up with a better solution.
Apart from this small (but critical) issue (and the fact that it sometimes takes very long to connect - see issue #15), it works with my FR70 (just uploaded my first data to Garmin Connect!). The dates are incorrect, but I'll investigate this another time.
The text was updated successfully, but these errors were encountered: