Edge 530 sensor dropouts since installing 8.0 firmware

I think so. There are so many variables in fact…. How many sensors connected (plus which software versions they are running), what phone connected (plus phone software version), how stable each of those connections are, what radio interference there is locally, probably some weird race conditions (software engineering race conditions, not cycling ones!) around the order sensors established their connections, what the Edge device is doing, what custom data fields are in use etc etc… Makes it incredibly hard to test. Having said that, since updating to the latest beta two days ago, zero dropouts for me in around 8 hrs of riding, and before I was getting multiple drop outs per ride

Today out of nowhere: reboot 

I mentioned happening this because the distance to my next turn wasn't decreasing. (Does the edge even has problems with "internal" sensors like GPS??)

Connected: Garmin watch (HR) and a Magene cadence sensor. These sensor devices did not have any problem before v8.x.

A question, I have not previously been plagued by these sensor lost / found problems, maybe an infrequent one or two in longer rides especially with the indoor trainer (Tacx Flow) but yesterday was my first indoor trainer ride with the v8.63 beta and I was getting sensor found every 10-15 seconds constantly during the ride, dozens+ but I did not see any "lost" message, is this how it works, only "founds" . The recorded data looks mostly ok with regard to gaps (just two) but the speed (up a constant 5-6% grade for 3kms) looks way impossible (for me unless I have suddenly turned pro), thanks

Yes, that’s the symptom, the “loss” is the backlight coming on or a momentary pause, then the found message occurs, at least that is what I was seeing.

I'm on the new FW from a few days ago and am still getting sensor dropouts. Mainly HRM but also PM. This mornings ride was just over 90 mins and reckoned i had at least 8 of them.

A pal of mine asked for advice on head units today and i couldn't recommend the 530 because of such instability (and also navigation bugs). Most others in the group recommended wahoo for stability, having previously had garmin units.

MB

Jeeez, I switched to wahoo a couple months ago and I was wondering about that issue and thought to look into that forum to see what is happening with this. That was my main reason to abandon garmin’s ecosystem.

I see that garmin didn’t do anything with that. 

Bad very bad. Cheers and good luck.

I see that this thread is 5 months old. Connecting sensors is a pretty basic function and this still isn't stable. I'm not sure when i'll change my unit but i'm pretty sure it won't be to another garmin, despite the 25% off through vitality. If HH K2 had a workout folder i would have bought one already. Will take a closer look at wahoo bolt and roam.

Fortunately i've kept the box and packaging so hopefully should be able to sell this 530 unit.

MB

This is an issue that is still being worked on and I can only apologized for not having more information to provide at the moment. I know that frequently updating threads that we are working on it only causes more frustration for some, but this is active and a high priority. 

The latest update has improvements for some situations regarding connectivity, but we realize there are still general stability issues with multiple types of sensors that we are working to resolve. 

I'm trying to analyse CdA (coeffient of Drag Area) numbers from 3rd party Aeropod, I have tried using 2 different speed sensors and enabling them on/off, Giant speed/cadence & Garmin speed sensor 1, its frustrating to watch the wheel circumference change as your riding, I thought it was calibrated in the first 1600m of the ride on the auto setting, so whilst riding looking at speed sensor details the circumference is changing every so often, I have had measure the circumference manually with a tape and set that value.  Previously I have read blaming the sensors with low voltage batteries, MAYBE its low power provided to head unit listening(opposite end) to the sensors   ???? and you could have a setting for high priority sensor tracking as some of us more interested in quality of data and not the edge lasting 16hours

7.1 does not have these issues. I am not a software engineer but one would think the tools exist to compare the 7.1 to 8.0 code base and see what changes were introduced.