Yeah i thought so
i get a lot of these sorts of problems, wierd feelings are set aside for other things, can they define 'weird readings', computers work on the principle of garbage in, garbage out so if the readings are wierd its probably not getting the right data in.
The ecu is a pretty simple device really, it usually works or it doesn't, if its booting up talking to the CAN bus ( cluster works) talks to an OBD II scan tool, then its probably working ok.
The car ought to idle correctly without the emanage, so thats always a test to be done.
Problems arise in the connectors, broken pins, bad wiring, loose connections, etc and lots of other things,
Since its a 2006 ECU it has an internal checksum that if the calibration gets corrupted somehow it'll throw an OBD II error code and refuse to start, if the error code isn't being thrown, its not that. I have never ever seen or heard of that happenning, the chances of the cal being corrupted and still have a meaningful OS on the ECU to even get to throwing the code is so slight i'd play the lottery that day..
Read up on all the stories of piggybacks and the lotus, you'll see you're not alone, thats why we made this
<embed id="VideoPlayback" src="http://video.google.com/googleplayer.swf?docid=5114777081198351945&hl=en&f s=true" style="width:400px;height:326px" allowFullScreen="true" allowScriptAccess="always" type="application/x-shockwave-flash"> </embed>