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

A day in your life with an Edge 530's unreliability.

Planned on doing a 40 mile ride on a route that I had ridden the day before and created a course on the 530.

On picking up my 530, found the battery was almost flat, since I had turned my PC off the day before to synch and recharge the battery, the 530 had remained turned on. Its time for an auto shutdown. I have never had a device in my life that fails to do this. (I have found since, that I can use a charging cable for my lights that does not transfer data to recharge the 530 and it does not turn it on when you plug it into the PC or turns on when you turn the power off, but you cannot synch)

After giving it a quick charge up, I opened the course that I had created and selected "Ride" to load the course. I had only took two steps and noted the Edge was saying that I was travelling at 2 mph, its never done that before and even checking it now, it always has a blank data field. This was in the house with no satellite reception. Before I got out of the room, the Garmin flashed up, "You Win, Course Completed".....How, I had not even pressed the "Start" button or was even on the point where the course starts or even got out of the house or even seen my bike. (The day before, the 530 was telling me that I had a heart rate between 136 to 156 and I never even had my heart rate strap on or close to hand?)

If I was on the start line off an event which I was going to follow a course, I would be annoyed if this had happened just as I was starting and had to reload everything and lose time.

On reloading the course again, I was ready to set off, I pressed "Start", it then flashed up, that I am near the beginning of the course would I like to start, so I selected OK, this then had the effect of pressing the "Start" button again, it flashed up, do I want to save the ride as it had the effect of stopping the ride. So basically, the 530, does not know if it is turned on when it asks you if you want to start despite pressing the start button, the only way to avoid turning the 530 off is to press cancel when it asks if you want to start instead of OK.

On reloading the course again and starting the ride, despite crossing the start point of it, it took almost 300 yards before it flashed up it found the course, yet earlier, claimed it found the course almost as soon as I had loaded it and told me I had finished, .......but......it was giving me navigation guidance for the course from the moment I had started riding, so had it found it or not.

During the ride, I was 0.26 miles behind according to the VP, but timewise just 1 second at one point, that basically means that I would have to travel at  around 936 mph to catch up in that time I was behind, another 530 fail, as I have been finding, the 530 VP is flawed and often gives the wrong figures.

During the ride, I noticed the 530 wanting me to deviate from the course that I had created on a ride that I had rode the day before and go a different way, Why? Is the 530's route planning flawed as well and cannot even copy a ride that has been ridden?

To date, I have only had the 530 a short time, I have never had a ride without some form of issue. Basically, I find about the only things that work on the 530 is the same things that I can get from a normal cycling computer and cheaper, time, speed, distance, heart rate and cadence, everything else seems to be flawed.

In 2008, I bought a Edge 800, it was flawed from the start but I still use it today, after only about 3 updates it was abandoned by Garmin, not fit for purpose. I vowed never to buy another Garmin Edge again, I thought that after 13 years, Garmin would have improved and relented to buy a 530, but I see no change, and like the 800, it will be abandoned soon, unfit for purpose.

I also use a Dakota 20 for my long endurance rides like "Paris Brest Paris" 780 miles approx, but no way would I trust the 530 to work reliably for that distance, its only good for short club rides. Oddly enough, the Dakota 20 had about 30 updates and works faultlessly, but was the amount of updates created because the Dakota was used by a greater number of users, ie cyclists, walkers, ramblers, motorcyclists, Sailing, gliding etc and there would have been more of an uproar if it was abandoned not fit for purpose, unlike the Edge range, that just gets abandoned as its only cyclists that use them and not much of a voice demanding to have them fixed.




  • Recalculation is off, I have never used it since I got my 530. When I got my 800 many years ago, recalculation was that flawed you had to turn it off. If you attempted to ride a course etc, it would take you straight back to the start shortly after you set off. And it was never patched. And it looks like Garmin has still not got it right 13 years later. And they are supposed to specialize in GPS technology!!!!!

  • It is not Turn Guidance that is the issue, but Recalculation.

    I have actually found that "Turn Guidance" is also the issue.

    At the weekend, I rode an event, the GPX track was created on the same OSM map on my PC that is on my 530 and no issues raised its ugly head when creating it.

    For the event, I had "Recalculation" turned off, but, I turned "Turn Guidance" back on.

    At a major crossroads where I had to turn left as I always do on this event as I know the route, the "Turn Guidance" map flashed up and wanted me to turn right, go for a short distance, turn around back to the crossroads and go straight across in the direction I should be going.

    I ignored it as I knew it was wrong and switched to the map, it only displayed the track and to turn left and no indication to turn right at the crossroad.

  • You are of course correct, the "Turn Guidance" has too many situations where the interaction between its "logic", the route, the map , GPS glitches and numerous other conditions too complex for its tiny brain to sort out and the result is as you describe, and I am not going to take a chance so I have always disabled "Turn Guidance" and just follow the course line, sometimes aided by custom cues that work fine without turn guidance. You would think that with all the years of Garmin writing code for navigation it would get it right but apparently getting it right requires a processor / memory / power profile that is still out of reach on devices we expect to last all day (or for Audaxing for multi days / nights)

    In my opinion they got it right once but never followed through to later models, on my old 520 (not plus) everything worked perfectly from FW 12.1 to 13.2 (last) using just the TCX Course Points with turn guidance disabled, it was like how Turn Guidance is supposed to work but never does, I was very sad when my 520 died and I was forced to get the 530

  • After my 6 months experience with my Edge 830 I finally could identify and reproduce this recalculate issue yesterday.   There seem to be many discussions ongoing on this subject on this forum.   I disabled this feature that is creating more confusion than aid.  I can't understand why Garmin doesn't fix this.

  • Wowzers, you do seem to have a lot of problems going on! Maybe use a smartphone app or something like that to track your biking?