I did a few datalogging runs today, after failing emissions badly a couple days ago. I noticed that every 10 or so frames, I'd get an incomplete frame in WinALDL (red blink instead of green). So, in each datalog, the rows that were incomplete have either incomplete or garbage data in them. I double checked the connections on my ALDL cable, and I'm pretty sure they were all good. Is this fairly normal? Could it indicate a failing ECM? This is a '165 ECM by the way, my second one. The original one was giving me similar troubles, and turned out to be a flaky memcal socket.

 

Did you try changing the baud rate?

this isn't normal. its a sign that communication is being interrupted or corrupted data is getting through.

heres a quick and dirty aldl tool I've been working on if you want to see if that works any better. It just displays raw data, but you'll see if its consistant or having to resynch. very buggy, very incomplete, and it will probably crash a few times on you. requires .net framework too.

http://www.tamor.org/newwebsite/ConsoleApplication1.zip

 

Yeah, I was thinking it wasn't normal. This was using WinALDL, set to default of 2400 baud. I'm going to try again tomorrow evening (laptop battery died), and see if I can rule out cable connection issues.