While tracking down the function of some of the mislabelled 3D Knock Filter Tables today, I started logging one of the memory addresses. As soon as I started logging it, the motor would drop to 2-cylinders. Weird that just logging something would cause the motor to do that. When I get some more time I might try digging deeper.

If anyone else wants to see if it happens, I was logging Request (MUT table) DB.

 

No... But I suppose its possible..

 

I had that happen with v.99 when I left the white connector on. Now I always make sure to remove it.

 

It's possible to fry your ecu, laptop, or whatever additional device you got hooked up depending on system grounding. ECU will protect itself to a good extent, but every sensor referenced to it's ground and perhaps resistance or noise can change the ecu value. Corrosion on a ground is one. Grounding kit fitted in parallel is another (should be in series, a parallel ground is basically an antenna for everything between the two wires), power inverter to cig lighter can cause problems.

 

Mine did it with one of the older versions.

 

yea... one night it randomly shut my car off when i was logging my idle

 

I've seen weird things happen in the past if the cable is plugged into the car before the laptop.

 

If you have the baud rate set incorrectly to what the ROM will allow (i.e. 62500 and the mod hasnt been done and its still set for 15625) the car will not want to idle, sometimes not start, die, etc.

 

that happen once to me to man. Mine didnt want to die it just idled like at 3k. Then realized the baudrate was off switched it back it was good to go

 

This was caused by none of those reasons. The car runs perfect, with Evoscan also running perfectly. Just as soon as DB is logged it will do this.