Wrong remaining distance calculation, changes towards the end of the course

Did you get a solution to this. I have an Edge 830 and am finding the same thing.  Does my head in.  On a 300km ride I have 61km to go and it jumps back to 89km.  Then after an hour it reverts to 49kms then 30 minutes later it then says 250kms.  I've tried changing satellites settings but still get this sort of behavior on every ride.  I'm using it for endurance Audax rides and the distance to destination is my psychological crutch to keep the spirits up.  on my last ride I was ready to throw it.  For a premium product it shouldnt be too much to ask for.

8712757 Do you see this behavior on every course that ride? If so, do these courses have any sections where you ride the same area twice, or down and back a road? 

Also, on these rides, after uploading, do you see an accurate GPS track recorded? 

The distance each point is along the track should be being calculated by the device when the GPX/TCX file is converted to FIT.

When you go off course, the device no longer updates the remaining distance. It resumes updating it when you get back on course. 

This indicates that the device computes the remaining distance by subtracting the current track point's distance from the track total distance.

So, the issue you are describing has two likely causes:

1. The track points don't have the correct distance.
2. The track overlaps itself and the device picks-up the wrong overlapping segment.

The satellites aren't the issue because, if they were really off, the device would see you as being off-course (and not update the remaining distance).

Can you post the course file?

The routes which had the issue were ones where start and end from the same point and that you loop back onto the same path along the tailing sections of it.

Audax_300_Smelly_Welly_1.zip

Thanks. The file was from Ride with GPS and downloaded to the unit.  Ive exported is as a GPX and Attached it AUDAX_300_Smelly_Welly_1.zip  

The points in the GPX and the TCX files don't include the distance.

So, the device has to calculate it.

The distance should be calculated when the GPX/TCX file is converted to the FIT file. It's very unlikely the device is calculating the remaining distance on the fly because it would be too slow.

The place where the track has overlapping sections (at the beginning/end) shouldn't be a problem.

With the kind of "lollipop" track you have, the device could have thought you changed directions. But, if it did that, the change between the remaining distance would have been much larger than what you said you saw.

I took the GPX file and loaded it on 530 it created a FIT file with the distances all looking correct. It did reduce the number of track points slightly., but all the distances increase correctly. I'm wondering if you might have been having some GPS positional issues?

Could you post the FIT activity file for this ride?

GPX track points 4589 the FIT file had 4430