Is this normal

[davidor]

OK, out for a walk today; reset all on the 'trip log' page, pressed start and walked. On getting back I pressed stop. With the Satmap still on (plugged into the car charger) I drove to another location a dew miles away. I then pressed 'start' again and went walking. The track log then joined up where I had finished the first walk to the start of the second one. I was hoping to have a cumulative distance for the separate walks, but the distance between the two has been added in as well.

I'm running V1.3. Somehow i thought that in this version, when the trip log was stopped, the track log would be stopped also. Anyone any comments?

[LostMike]

That is how I would have expected it to work.
_________________
LostMike
Satmap A10. Platform 21
Software version 1.5.9193
Satsync 1.525

[davidor]

Thanks Mike. However if I "stopped" it logging, then restarted it, I wouldn't have expected it to work like that, otherwise why bother stopping the tracking?

[Gibbo10]

I think the idea is that you reset the log at the start of the first walk. at the end of walk 1 press stop and conver that trail to track but don't clear the log when it prompts.

Drive to new location, press start and the end press stop and you will have the cummulative info in the log.

I've not fully tested it but that's how i would envisage it works

[LostMike]

davidor asked

[ocam]

I think the idea is the unit will log details of one trip. If, during that trip you want a break (and stay put eg rest/pub stop) you can pause logging.

[dungbeetle]

Had a similar occurrence here, davidor.

The unit appears to continue logging the journey even when the STOP button is pressed on the Trip screen.

We ended up with an unwanted car journey being recorded as well.

Possibly a bug?

[smashing]

I've had this too - press stop after a long walk but it'll track all the way home on the train

[Gibbo10]

If you press start satmap records your route with the red breadcrumb trail, when you press stop it should stop recording the red breadcrumb trail but obviously continue to track your position.

When you press start again it should draw a straight line from the position you were at when you pressed stop and the position you are when you pressed start again.

If you do not want this straight line then before pressing start again then you surely want to record a new route, in which case you must convert the trail to track before pressing start again. or, if you don't want the previous route you should press reset.

I think where stop and start recording is useful is when you recording a route and you stop for a period of lunch at the pub for example where you don't want the data to be affected. Press stop have lunch press start again. Or, if you are on a walk and you want to check out where a path leads to but you don't want to record the track. Press stop investigate the path, then return to the point stopped recording and press start to pick up the correct trail recording.

Are you seeing anything different to what I describe here?

Or does anyone have any other good suggestions for using stop and start route recording?

[davidor]

That's how it seems to work. I had hoped that if you did more than one walk in a day with car travel in between you could have a cumulative log, but it appears that is not possible.

[JimmyTheHand]

I have experienced similar if I pressed reset before it has locked on and then started it again - it seem to really mess up times and max/average speeds as well from what I recall.
_________________
J.

[dungbeetle]

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!