This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Edge 530 Version 6.00 impressions

IceLed

Since the main topic is closed for replies, let's share our feedback here.

My first impressions (updated 19-Aug):

- No sensor dropouts (but will test further, as I am at holiday location at the moment)

- Routes are being loaded noticeably faster than on the last beta 5.68 - good job there, Garmin!

- ClimbPro did not glitch at all, even combined with navigational instructions (subject to additional testing on a route where it crashed last time, but again - I am not in my home country at the moment)

- Overall speed and responsiveness - compared to 5.68 beta - way better!

- Creating a route in Strava and have it auto appear (via GC) on the device still seems to get the elevation wrong, I guess still work in progress there

- LiveTrack - not a single issue, but it is been like this for a while with me (paired with Galaxy S10)

- Strava segments - not a single issue, actually I really like the new layout at the end where it compares the times of the KOM, your PR and the current time

In other words - pretty happy with the new firmware! Will report if anything goes wrong, hope it does not.

  • 0

    Off for first ride on FW 6.00 today. It transferred a Strava route over seamlessly. Let's see how it navigate it. I do have 1 starred segment on it. I'm most curious to see if they fixed the map orientation issue where it switches from track-up to North-up. I hate that.

  • 0

    Uh, lots of dropouts today. Unfortunately not only the Radar, but also Quarq power meter, speed and surprisingly - for the first time - the phone... Needless to say the LiveTrack broke, but also the upload after the ride. Had to restart the 530 to get it back on track. Hope it was once-off...

  • 0 in reply to IceLed

    I have lots of problems when biking in the woods... I guess overhanging trees block the GPS signals...

  • 0 in reply to Prosperot

    For routine use GPS only should be fine and will give you best battery endurance. Where you have obscuration due to trees and tall buildings then yes,  you should push to a dual setup.

  • 0 in reply to Prosperot

    Alternatively and the best solution is to buy a garmin speed sensor and it will fix your issues.  I road bike and put one on as I have a paved trail I ride on that is completely shaded.  GPS was not great and with the sensor it fixed everything when I am in that situation. 

    I know you might say why do I have GPS then which is understandable but get one and set the wheel circumference correctly and you will not have to worry about what GPS setting you have.

  • 0

    I have lost 4 week Load Focus since beta 5.68 and still missing in 6.00

    All numbers are 0 although 7 day load is present.

    Downgraded to 5.50 and numbers reappear.

    Anyone else having this issue?

  • 0 in reply to ewarnerusa

    Update for my first ride on FW 6.00.  I followed a course that was pushed automatically from Strava Routes to the device.  That seemed to work great, although when I first confirmed it transferred to the Edge there was one version and then day of activity there were 2 different versions.  I don't know what the deal is with that.

    The route seemed to work fine and the starred strava segment embedded within in started properly.  This ride goes through a steep cliffed canyon and not surprisingly the strava segment lost it's tracking while following it.  The course did as well, although it always found it again and recalculated.

    Another positive was that I decided to change my route during the activity. I didn't have the energy to complete a certain climb and descent on the route!  It showed me off course as I took the bailout route and it correctly found me back on the course when I got back on to it later in the course.  

    The map orientation bug seems to have been addressed.  It stays track-up.

    A negative is that some of my data screens disappeared after the FW update.  I've only checked one profile, but on that one it took away my map with custom ConnectIQ datafield, as well as a more standard one.