I posted this in the FC-Datalogit-user group on yahoo as well, but figured I would post it here too...

I got a netbook last week for various reasons, but one of which was for tuning.
I bought a "non-official" serial to USB converter cable because I figured, if it
doesn't work I will take it back. I installed the drivers and to my amazement I
was able to Write to and Read from the ECU...cool.

Then I go out to log some cruising AFR's. Start the log in the map watch window
and it records only 0's for each field. Then my computer crashes (BSOD). I
think, that's weird. Reboot and the same thing. I can't figure out why the cable
would work for read and write, but then completely crash my computer when I try
to log.

Any ideas?

 

Logging in MAP WATCH is a resource hog. Even logging all parameters is also a resource hog.
Both slow down the logging rate. Maybe your notebook does not have the processer speed or RAM to log under those conditions.

Have you tried logging minimum data first. Then increasing the amount of logged data to see what happens.
If you do not know of what I speak, read under MONITOR and do searches on my postings about logging speeds.

 

It really sounds like a Software/Hardware error, because if the Datalogit software crashes, it will just say it has to close, I know it happens to me a good bit.

 

Thanks Chuck. Next time I will only be monitoring a lot less parameters. I do have an update to my problem though...

I borrowed another USB to serial converter from work and this time my computer didn't crash while logging in map watch. But...when I went to my auxiliary wideband channel, it was still just recording 0's for everything. Go back to all the standard channels and they logged fine.

Then I plugged a old computer with a serial port on it up to the Datalogit and it logged my wideband just fine.

Why would the usb-serial converter work for everything but my auxiliary channel?