Edge530 datafield ANT communication not work after the device restart

I observe the same behaviour with GaitCoach DF on FR645M.  The DF will only connect to RunScribe pods (and for the duration of one activity only) after the watch is restarted.  Software version 6.20.  Communications is by ANT generic channel.  GPS: 2.50.  WiFi: 2.50.  CIQ:3.1.1. WHR: 20.03.31.  ANT/BLE/BT: 3.60.  Sensor Hub:6.80.

Internal behaviour is that onMessage() is successfully called only when the DF is run after the watch has been restarted.  After exiting the activity, it will never be called again in any subsequent activity.  It does not appear to be a signal strength problem in that the pods can be placed right next to the watch without making a difference.  GaitCoach users on 945 have also reported this behaviour to me.  In that case, after much experimentation with older firmware by the user, he encounters the problem with ANT/BLE/BT: 3.60 but NOT with ANT/BLE/BT: 3.08.

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.

I have appreciated that if you let the garmin go into sleep mode and turn it on, you can magically see the data. there has to be a difference between the way the garmin works when the device is turned on and between the way it returns from the sleep mode, since in my tests with my 1030 edge, I never get to see the information when turning on the garmin , but I can always see the information if I let it go into sleep mode and “wake up” it.

If you use SW 5.0, with beta version 4.21, it worked fine.

Former Member Is your edge 530 using the latest FW? I believe that fw 5.00 would be the latest at this time.