That'll cetrtainly give you the s#@%s!
I typically set a start speed (>200), which is a logical use of the logical inequality.
The intention is that somebody presses the button to stop. A good proportion of logs this this does not happen, but we still get a complete file.
I have several customers and DL1s of various vintages suffering this but not complaining. Of late, perhaps because it's a current spec 'raw enabled' unit with more data to write, a file is created sans date and time details.
Sometimes this results in "Analysis" F.O. error. On one occasion, I did an uninstall and new version update and miraculously half a dozen buggered files were fixed. I'm pretty sure I didn't re-boot the laptop between times.
On occasions, I find mysterious BOOTLOG or some such files on the card.
When the "corrupt" file will not load, I've successfully repaired them with a CHKDSK.
Is there anything verboten on your card?
Is the logger achieving GPS lock?
Does it achieve lock before you drive off?
Can you create sensibly sized logs (driving or not) with button presses?
All these questions and more could be answered (in the affirmative) and like some of our friends you might still end up with s$#t. Some would say life's like that. I'd say you bought a lemon!
But this is not fair.
Perform those checks.
Remove the Auto-stop condition.
Use the help file wording to the character.
Set the Stop condition to a lower speed than Start.
Curse with greater volume
Maybe you're being punished from On High for not bringing your laptop
How far from Nottingham are you?
Can they hear
