Acknowledged

FIT Write Bug

This is a bug related to rendering the FIT Write Data. A difference between Garmin Connect Mobile and Garmin Connect Web.

I can't post an image here so I'll include it in the reply.

In Garmin Connect Web, as I move the mouse to the right, values stop at 2 hr, 11 mins. That was when the CIQ data field experienced a crash. My Garmin 1030 rebooted near the end of the ride, restarting the FIT Writes. So the descending line to ZERO is correct.

However, in Garmin Connect Mobile, the line continues straight across that gap. Looks like a simple rendering bug. Not sure which you prefer, but they should be the same.

DaveBrillhart
Parents
  • in reply to flowstate

    That brings up another question. There are a bunch of data types we can set in the FIT createfield. Using your example, for Effective Wind Speed (relative influence of a head or tailwind), I'd like to use a SIGNED 8-bit Integer. In my code, is there a way to more precisely convert a variable to, say, a Signed 8-bit Integer? Or just sending it a "toNumber()" will work?

Comment
  • in reply to flowstate

    That brings up another question. There are a bunch of data types we can set in the FIT createfield. Using your example, for Effective Wind Speed (relative influence of a head or tailwind), I'd like to use a SIGNED 8-bit Integer. In my code, is there a way to more precisely convert a variable to, say, a Signed 8-bit Integer? Or just sending it a "toNumber()" will work?

Children
No Data