I've used the data logger 3 times (Evo IX). The first time I used it I hit OK to get it started, but I didn't allow it time to connect so by the time it started keeping a log I was already at freeway speed.

After maybe 20 seconds I hit OK again to stop the logging, but when I got home the log was 9 minutes long.

The second time I went out I decided not to stop the logging to see what the max length is (9 minutes again?). But when I got home the log was only 5 seconds long. I figured that the AP must've lost its connection for a moment.

Third time I logged for half a minute, then hit OK to stop it, went to a gas station, shut off motor. When I left I tried to log again to see what would happen. It said it wasn't logging, which I took to mean it wouldn't let me because it wanted to preserve the already logged data. But when I got home there was no file. Hopefully, next time it'll have a log.

Btw, I opened my log files in Works Spreadsheet. Worked just fine for viewing the csv files.

 

I do not have any of those problems with mine. After the computer is connected, "CTRL-D" starts and stops data logging instantly.

 

I believe the OP is talking about Data logging right from the Access Port device, not with a laptop and race tuner.

 

I'll look into it for you CDO. I haven't heard of this issue before, has anyone else experiencing this problem?

 

Thank you.

Btw, is there a webpage explaining anything about the data logging feature? Like how many logs you can have on the AP at one time or the max length of time. My first log was 539.61 seconds long. The file size was 100k.

 

From what the programmers have said it can hold hours per log and up to ten log files. After the ten files created it will start from one and overwrite them.

 

Thanks for the info, Dan. I never would've guessed the AP had that much memory.

I tried to log again today and got the same message, Not Logging. I'll try reinstalling the update if it'll let me.

I just hooked up my AP to the computer and there's a new log file on it. I'm not sure if it's actually from today because the date on it is Tuesday, Dec 5, 2006. The time of day is wrong for today also. I datalogged around 3:40 pm and this one reads something like 6:05.

 

Yeah the date stamp is a known bug, the programmer didn't fix that before he left =P

I know there's a fix coming for it soon. I haven't got an update from the programmer yet on this issue for you though, I'll let you know as soon I do.

Cheers

 

I went to Properties of the downloaded log file that magically appeared in my AP Manager last night. The (created) date of the file says it's from this past Saturday. But I didn't download the file to my Desktop until Monday night, when it first appeared.

So it had been in my AP since Saturday, according to the date, but didn't show up in AP Manager until Monday. That file is from one of the times my AP said it wasn't logging.

From that I'm guessing that my AP might be logging every time it says it isn't, but AP Manager isn't recognizing them right away because that one took several AP-AP Manager connections to show up (there's still 2 or 3 missing datalogs).