I tried to grab a log during a 10hour road trip, but ran into some BBL issues.
A minor one is the function (hot) keys don't respond in the PID selection menu. I need to use the arrow keys to move the highlight selection up/down. I'm guessing EFI knows this.
It would be good if the arrow keys did a roll-over. If I'm at the top of the list and hit the UP arrow, the selection would roll-over to the end of the list. Something line a page-down or end-of-list.
The major issue was a lost log file. The V2 was using internal mem, the SD slot was empty. I selected an almost full PID list, (21 of 24 possible channels). Less than an hour into the trip the V2 beeped. At the time, I wasn't sure why. A few hours later I noticed it wasn't scanning data. I tried to record data a couple times, with no success. It would create the log file, but it would remain empty. A few hours later when I tried to move the file (EfiExplorer), I wasn't able to move the first log off the V2. It would start to Xfer data, then I'd get a pop-up window with a message. Unfortunatly I can't tell you what the err msg said. (I didn't have time to mess w/ it.) I deleted that log file, and the other 2 empty logs. (The V2 FLASH was basically empty, as it was a few hours earlier.) I selected the same PID list and hit record and I was able to grab much more than an hours worth of data. No sign of the earlier error.
1. I don't believe the first log ran out of memory.
2. I'm not sure if starting log# 2 & 3, corrupted log# 1, or wether it was already bad.
i.e. If the V2 was out of memory, why did it succeed in creating the files# 2 & 3.
Or by doing so, did log#1 get corrupted?
When done logging or downloading, I just unplug the V2. I don't bother to power off the unit. (The unit is idle, no LEDs, no ongoing comm.)
How good is the FLASH file system? I'm wondering if this nonPwr-Off behavior might have caused a FLASH problem? Have you seen this before?