I think it would be interesting to get everyones perspectives on the effects scanning has on spark advance and other parameters.

Do all the scanners have the same effect. ie. Diacom? Ease? Craig Moates? etc.

Does it only take effect when a 10k resistor is present? Diagnostic mode?

I think many people negate the effects of these and it can have an impact on performance.

And also include your fixes in detail, such as the address $23 =>00.

Screen shots are always cool.

 

This is an absolutely wonderfull question!!!

I am surprised it has been avoided.

Seems that the 730 guys have less to worry about then us 165 guys.

I would also like to know more beyond $23.

 

I see no alterations in what my car does while EASE is connected and scanning. Timing is reported as what it should be under the correct conditions. If the conditions say it should be 36*, it is 36*.

Also a timing light at idle shows the same thing that EASE shows on its scan.

 

Scorp, I report the same using EASE. Its an awesome program. 100X more stable than anything else I have used. I can actually unplug it completely from the computer is necessary. Leave the program running, then come back and plug it in and it takes off again! NEVER had it stop logging like several of the others I have used. But that is a whole nothing topic.

Just curious to see what others see with other types of scanners. I did a guys blown vette this weekend and his little scanner sent things into all sorts of disarray. That was probably from it triggering the diagnostic mode, where EASE is more a passive logger.

 

What type of cable is required with EASE? How does the cable interface with the ALDL port, ie: how are A&B connected?

 

EASE uses its own cable that goes into a black box where all of the scanning is done. Then the black box sends the data to a serial port on your computer.

 

I use Datamaster with no problems. But I'm also speed density.

 

I use snapon MT 2500 and my car seems to perform better with it hooked up in code and data gathering mode and that is with 870 ecm.

 

I have an akm cable and use craige's software and winaldl some times and i have to use the resistor between a and b to get any 165 ecm to talk to me. It makes it idle higher, so i would deffinetly like to be able to get around that because i also remember reading somewhere that it also ignores the knock sensor as well during this mode. Where can i disable this in the code?

 

I use a 10k resistor to inititiate ALDL mode for the moates software to start receiving data. After that it automatically tumbles back into "normal" mode. To be on the safe side I remove the 10k(actually it's on a switch that I disable).

This should be the same for all 165 ecms, no?

The knock sensor works fine while scanning, I tested it by zeroing out the knock retard on 1 run and I had audible knocking. I scan every run I make at the track.

Ski_dwn_it, what is your maf rate maxing out at? I am curious to know when a 123 MPH MAF car loses resolution.

 

Ohh ok. In winaldl you have to leave the resistor in. Guess I never really tried in Moate's software after the winaldl thing.

 

This is my experience as well.

This is also confirmed by Craig himself.

 

Just experimenting with this myself..here's what I found...

With Moates I can take the 10K resistor out of the loop and I still get data. Idle seems normal..

With WinALDL, I get a high Idle and I have to leave the 10K in or else no data...Once I pull the 10K out of the loop, the high idel stops and unfortunately so does the data..

I wonder why this is?