Acknowledged
5 months ago

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
  • over 2 years ago

    > NaN is really just a floating point construct to handle strange edge cases, I think

    Yes, but the point is that the bit representation of NaN is 0xFFFFFFFF, which is what is the FIT specification says to use for "invalid value" (for 32-bit floats). If you try to convert the integer 0xFFFFFFFF to a floating point value, you will get -1 (float), which is does not have a bit pattern of 0xFFFFFFFF (as demonstrated in a previous comment.)

    > I'm not sure any more that it worked. 

    That's a shame :(.

    Obviously native apps have the ability to "write gaps" (aka "write nothing"), so it's a real shame if 3rd-party apps don't.

Comment
  • over 2 years ago

    > NaN is really just a floating point construct to handle strange edge cases, I think

    Yes, but the point is that the bit representation of NaN is 0xFFFFFFFF, which is what is the FIT specification says to use for "invalid value" (for 32-bit floats). If you try to convert the integer 0xFFFFFFFF to a floating point value, you will get -1 (float), which is does not have a bit pattern of 0xFFFFFFFF (as demonstrated in a previous comment.)

    > I'm not sure any more that it worked. 

    That's a shame :(.

    Obviously native apps have the ability to "write gaps" (aka "write nothing"), so it's a real shame if 3rd-party apps don't.

Children
No Data