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

Distance to destination reading is wrong

Ido_Bourstein
over 4 years ago

Hello

I use my Edge530 on navigation and I display the field "Distance to Destination"

Several times I faced a situation where I start the ride, everything looks OK and then

at some point the value of Distance to Destination is corupted (typically it shows the total length 

of the route). In some cases , After a very long time, the value returns to the real number.

On my profile, I've selected recalculation - off as the device is very sensitive to any deviation from the route.

If recalulation is enabled, any deviation cause the unit to recalculate which takes relativly long time (specifically if the route is long)

and consumes device power.

I would expect an error on the distance to destination value in case I deviate from the course but I would also expect

a correct value once i'm back on the route ( and this is correctly recognised by the device) 

On my old Etrex30 , it worked smootly, i.e. once you were back on the track the correct distance to destination was displayed.

I use version 7.00 of the device software

Thanks !

  • 0 over 4 years ago

    I had a similar problem.  It was related to a setting in navigation "lock on road".  I was riding on a trail next to the road.  Navigation wanted to turn on to the road but I ignored it and stuck to the trail.  It cause a problem similar to what you  describe.  It eventually corrected itself.  I think it was calculating the distance from the turn I ignored.  Since I was riding next to the road, it didn't tell me to make a "U-Turn" but my distance kept increasing because I missed the turn.  It never told me it found the route but it did correct the distance.  I turned "lock on road" off and it corrected the problem on the next ride.  I like to keep this setting on, so I just ignore the problem.

  • 0 over 4 years ago in reply to BourbonBill

    The "lock on road" just changes how the cursor is displayed. It doesn't affect routing at all. It just makes the cursor stick to a nearby road or trail ("road" refers to any line, a real road or a trail).

    Anyway, you don't need it (it's really more for use when using the device when driving).

    Your trail/road problem is due to the track being closer to the wrong thing (the road in your case). The devices (all models) can get a bit confused with roads and trails that are very close).

    You can minimize the issue by moving the track I the outside of the trail a bit. Since that's a fair amount of work, no one really does it.