Birger, maybe I do not understand your question, but I write the finishing time in a notebook (yeah, paper) and then close down Expedition.  Post-processing analysis allows for race beginning and end.
Near as I know, while Expedition is running, a logfile is being added to.  You cannot stop it.  Handling large files (say 3 day race), in post-processing I trim prestart time logfile rows, and post-finishing logfile rows when I combine the 24 hour logfiles into one.  But a 30 mb logfile is perfectly normal for a race of this length.

Ok, thanx

I would investigte further a bit what’s the simplest way. I see the start timer runs elapsed time so I hope just killing the timer would solve it.
Thanks for the tips in regards to Wanda though

B

Related question:

​I see the starting event, with distance from line and a percentage (of polar?/target?) automatically generated.
​Is there anyway to similarly  set an event when the course is selected/activated ?
​Since we enter the course a few seconds after starting the race timer, it would be convenient to have it linked in the log file, and on a boat with small crew, while we could try to remember to manually set the event, there's nobody at the nav station.

Also when rounding marks?
​(change to Next mark? or when distance goes below threshold?

sheldon.haynie wrote:

Related question:
Also when rounding marks?
(change to Next mark? or when distance goes below threshold?

Sheldon

This capability is already in place.  Expedition writes an event to the log if you have Auto Mark advance active.  It includes the lat/long, time.

It would be great to have other events automatically written.  It would make it much faster to analyze the race after.  Crossing the finish line, maybe activating a course like you suggest, starting a timer.  Optionally I'd like to even see an event written for each tack/gybe, maybe a checkbox for this.

Last edited by Fergal (10/10/2017 7:28 am)