Ticket Created
over 6 years ago

WERETECH-7046

info.maxCadence reporting odd values in Edge Explore (fw 4.10.0.0)

Is anyone aware of any issues with the API reporting odd values for info.maxCadence on some Edge devices?

I have a user running one of my datafields on an Edge Explore with firmware 4.10.0.0. My datafield is just displaying the value returned from info.maxCadence, no tampering at all.

maxval = info.maxCadence != null ? info.maxCadence : 0;

Before starting the activity the user gets a max cadence of 65535 and it will remain the same until the activity starts.

Once the activity starts the value will change, but only to match the average cadence value all the time.

In summary:

1- Before activity starts info.maxCadence returns 65535.

2- After the activity starts info.maxCadence returns exactly the same value as info.averageCadence.

I found in the forums another user reporting the same issue but on a different device, Edge 820:

https://ciq.forums.garmin.com/developer/connect-iq/f/showcase/5201/diy-data-field/55133#55133

In my case the user already tried with different cadence sensors (to discard a sensor issue) to no avail.

On my side I cannot repro the problem in the simulator nor on my Edge 520.

Any ideas? The odd values are coming directly from the API but I can't tell if it's a hadware (sensor, Edge) or software issue (firmware, ConnectIQ).

I can workaround this problem with some simple code, but that will only fix it for my app, while the issue may affect other users/developers as well.

Thanks.

FCS7
  • over 6 years ago

    Hey - We've got a ticket created and we will take a look for you. Thanks.

  • over 6 years ago

    Sorry couldn’t finish my reply and it seems it cannot be edited. Anyway as I was saying that will not solve problem 2 (max cadence being reported with the same value as average cadence). Of course I can workaround that with code as well but again it will be only a workaround for value that is wrongly reported by the API in two different and insane ways. I was wondering if Garmin would look into this as it seems there may be more cases (I now at least 3 with two different datafields from two different developers).

  • over 6 years ago in reply to jim_m_58

    I thought about it but that will only workaround point 1.

  • over 6 years ago

    Just a guess,but the 65535 is kind of a magic number with 16 bit values - as a signed 16bit value, it's -1.

    I'm not sure why you see it, but you can probably check for it and treat it the same as you'd treat a null.

    I think this is the proper place for new bugs, and legacy is for the old bugs reports from the old forum.

  • over 6 years ago

    BTW maybe I should have opened this in the Legacy Bug Report forum.If that's the case please feel free to move it