I have a weird 6E problem for you guys. I have just built a 383 with stealth ram. I had copied all the data from my stock chip and modified the bin as necessary. I then started the car and weird stuff is happening. I am using winaldl to watch everything and is not reading anything on the sensor data screen. I also notice that even though this is a MAF car the sensor screen show MAP in KPA readings. I put the stock chip back in a same issue. I took a few readings with a dmm and there are some signal getting to the ecm. The O2 for example was reading .389volts to the ecm. The raw data does make some changes on the TPS and O2 but that is all I seem to see change.
ANy thoughs or suggestions?????

 

Why not try a different scan program. I dont think WinALDL scans at 8192 baud, which is what 6e runs at. What bin/ecu were you running before the engine change? Did WinALDL work before?

 

winaldl did work with the stock chip and the ones I was burning last summer before the engine change. Since then I have purchased a new laptop and also downloaded winaldl again. I wondered myself about baud rates etc with the com port on the laptop etc. Perhaps winaldl is a newer version as well??

 

6E is a hybrid ECM and can be scanned at 160 or 8192.

 

Sounds like the car might have been converted to an 808 type platform with speed density...

I remember reading something about some MAF cars being converted to speed density when they were brought into dealers with bad drivability. Check to see if the MAF wiring is actually functional and see if there is MAP sensor somewhere in the engine bay.

Could have also been an Accel power processor piggyback conversion done to it. That convertion left the MAF rpom and ecm and piggybacked though the wiring harness. It also converted the car to speed density.

I have know idea what kind of reading you would get by scanning.....

Of course, I could be pulling all of this out of my a$$. Good luck on this one. I am curious to know what you find.

 

WinALDL would not know that it's speed density in that case. The problem is more likely that he's using the wrong program to scan is vehicle.

 

Thanks guys but the problem has been found. When you first load winaldl the configuration is set to a default definition for a ck truck I believe. I changed this to the 165 and hit exit and tried scanning and it wont work. So I opened up winaldl changed the configuration and then closed the program and then reopened it. After doing this it took and held the 165 config. Don't know why its doing this but perhaps Bill Gates would know.... should have tripled checked this first I guess.

 

Yup, probably Bill's fault.

 

Absolutely....