Wrong E.T.E.

Last sunday, by boat, I have been using the program in time to time just to have a look on the back route to the port.
Every 15-20m minutes I started Orux, and every time I exit the program after a quick check to position and ETE.
Choosing to add the record to the existing track the ETE resulted largerly overestimated (>>10h vs about 2h).
Starting a new track or a new segment the compute was instead correct.

Either is this a desired behaviour or it should be fixed?

Hi
p

Pascal wrote:Last sunday, by boat, I have been using the program in time to time just to have a look on the back route to the port.
Every 15-20m minutes I started Orux, and every time I exit the program after a quick check to position and ETE.
Choosing to add the record to the existing track the ETE resulted largerly overestimated (>>10h vs about 2h).
Starting a new track or a new segment the compute was instead correct.

Either is this a desired behaviour or it should be fixed?

Hi
p

Hi, Pascal;

OruxMaps uses avg. speed of current segment, to calculate ETE/ETA.

Was you logging a track or only with gps enabled?

orux

Hi Orux,
No, I would only had a look to the position without recording a real track, but I configured the GUI to show ETE only in tracking mode so...

p


edit:
also adding points to the existing track I don't understand why the compute was so wrong, at a maximum it should have been inaccurate since the existing points in the track was however on the current path and there wasn't stops or detours on the sailing (it was almost a 9 hours straight route).

Pascal wrote:Hi Orux,
No, I would only had a look to the position without recording a real track, but I configured the GUI to show ETE only in tracking mode so...

p


edit:
also adding points to the existing track I don't understand why the compute was so wrong, at a maximum it should have been inaccurate since the existing points in the track was however on the current path and there wasn't stops or detours on the sailing (it was almost a 9 hours straight route).

Hmmm;

This is the problem; OruxMaps is using a not actual avg speed. I am going to change to 'last location speed' if you are not in 'track logging' mode.

orux

orux wrote:

Pascal wrote:Hi Orux,
No, I would only had a look to the position without recording a real track, but I configured the GUI to show ETE only in tracking mode so...

p


edit:
also adding points to the existing track I don't understand why the compute was so wrong, at a maximum it should have been inaccurate since the existing points in the track was however on the current path and there wasn't stops or detours on the sailing (it was almost a 9 hours straight route).

Hmmm;

This is the problem; OruxMaps is using a not actual avg speed. I am going to change to 'last location speed' if you are not in 'track logging' mode.

orux

No Orux, I was actually in logging mode even I was completely not interested about the track.
Tracking was active just to have ETE shown on the standard upper dashboard.

(sorry if I'm not clear, but I hope you'll appreciate this help)

p

Pascal wrote:

orux wrote:

Pascal wrote:Hi Orux,
No, I would only had a look to the position without recording a real track, but I configured the GUI to show ETE only in tracking mode so...

p


edit:
also adding points to the existing track I don't understand why the compute was so wrong, at a maximum it should have been inaccurate since the existing points in the track was however on the current path and there wasn't stops or detours on the sailing (it was almost a 9 hours straight route).

Hmmm;

This is the problem; OruxMaps is using a not actual avg speed. I am going to change to 'last location speed' if you are not in 'track logging' mode.

orux

No Orux, I was actually in logging mode even I was completely not interested about the track.
Tracking was active just to have ETE shown on the standard upper dashboard.

(sorry if I'm not clear, but I hope you'll appreciate this help)

p

Yes, I understand you. Thanks;

This is exactly the problem If you are not in logging mode, OruxMaps is reading a random? value.

orux