Complete
over 4 years ago

WERETECH-7776, JAZZ-2402, HESPER-2917, BERLIN-2552

Edge530 datafield ANT communication not work after the device restart

Hey!

I have a datafield which showing my external sensor`s data using ANT communication. It is flawlessly working on Edge 520/520plus since a year. 

If I set my datafield on Edge 530 and start it, it works perfectly. However if I restart the Edge and start the datafield it doesn`t communicate with my sensor, not showing any data. 

If I swap the datafield to another one, restart the device, swap back, and start it, it is working until I restart the device again.

I don`t know how to debug this problem. Is there anyone who met the same problem?  Is there a bug in my program or in Edge 530?

Thanks in advance! :)

DBezzeg
Parents Comment Children
  • Former Member
    Former Member over 5 years ago in reply to Former Member

    Edge 530 firmware 5.03. A single Moxy connects immediately to the ConnectIQ app, but multiple sensors simultaneously has issues. They might appear after anywhere from 10sec to a couple minutes delay. Turning off a sensor that is connected will allow a different sensor that is already turned on to connect immediately. I tried to capture this behaviour on video: https://youtu.be/dCSqgPe3AuA (video is at 2x speed)

  • Former Member
    Former Member over 5 years ago in reply to Stephen.ConnectIQ

    I just re-tried connecting Moxy devices to the Edge 530 with firmware 5.02. Seems like now they won't connect at all. The Moxy ConnectIQ apps all have the sensor ID numbers defined, but they don't pick up at all when the devices are turned on. Seems like something went backward, unfortunately.

  • over 5 years ago in reply to MoxyRoger

    Hi  I apologize for the lack of updates, however we don't have much news to report. As it stands now, we are aware that this issue was not fixed in the latest release fw of e830. Unfortunately, we do not have control over what does or does not get into a device's fw patch. Because of this, I also can not speak to what firmware version will be required to get this fix. Please know that the issue is reported on all the devices in question, and the device teams are working to get this change integrated into their devices.

  • over 5 years ago in reply to Stephen.ConnectIQ

    Stephen, can you or someone from Garmin provide an update on these issues?  We were thinking it was fixed, but I'm getting complaints still.  For each of the 530, 830, 1030, 945, and 245, can you let us know if the issue is actually fixed and what version of firmware is required?  If the issue is still present, can your provide an estimate of when a beta or final fix will be available.  Some users have been waiting 10-12 weeks for a fix now.  The false start on the fix and then little new information really tries their patience. Thanks!

  • Former Member
    Former Member over 5 years ago in reply to Stephen.ConnectIQ

    I've tried using the Moxy ConnectIQ apps (with 4x Moxy sensors) on an Edge 530 a few times now with no success.

    On previous firmware, the connections were extremely unreliable, not connecting at all far more often than they would connect. Half the time the datafield would show the IQ error icon. Restarting the 530 device or selecting a new activity profile would just as often cause a different data field to throw up an error icon, as it would solve the existing errors. I never even bothered to test a real-world use case to see if the behaviour work improve or break further over time. I could never get all four sensors to work at the same time.

    Updating to firmware 5.00 seemed to show the exact same issues, with failures to connect, error icons, etc.

    Downgrading to beta 4.25 firmware on Roger's suggestion seemed to be a slight improvement? But the behaviour was still un-usable. Datafields seemed a bit more prepared to connect to a sensor after a 1-2min delay (whereas this is instantaneous on the 520), but still I could never get all 4 to work simultaneously. Restarting an individual sensor might allow it to connect when it hadn't before, or just as often it would fail to connect when it had before. And restarting the 530 device was a crapshoot as well.

    I typically try to isolate and reproduce issues like this before sending support requests, but I don't even know where to start with this one. It's just completely inconsistent.