ALDL Scan Codes
Last edited by Elijah Rodriguez; Feb 11, 2021 at 09:54 PM.
What kind of fuel pressure and manifold vacuum is it reading at idle??
What is TPS voltage value before startup; looks like voltage is way too low during idle? Should be ~0.54Vdc before startup and ~0.7Vdc at normal idle.
Is power low even before full warmup?
Is the air cleaner clean?
Are spark plugs & wires in good order?
Off hand looks like the ECM isn't seeing throttle position properly. With engine off check it with a DVM.
Idle is high and uncontrolled at 1200 rpm with zero IAC counts. TPS voltage is low as already mentioned. BLM of 139 is a bit lean, but not a problem at this point.
Something is causing excessive airflow at idle as evidenced by the high rpm and zero IAC position, either a huge vacuum leak or too much throttle opening. Check that the throttle is fully closing and readjust tps voltage.
Note: I don't really trust your scan tool's definition file since some values have strange scaling such as the mass airflow signal (need to divide by 256), although the raw (8 bit unlimited airflow signal) looks about right at 12 gm/sec @ 1200 rpm.
Clear the codes to start fresh and see which ones come back again, then go out and try to reproduce the original complaint (at WOT) while recording and save the log.
Last edited by tequilaboy; Feb 12, 2021 at 02:31 PM.





What does TPS voltage read with the engine off?
Does the green dot beside the Code 33 indicate that this code is set, with an SES light coming on? Ignore the Code 32, but 33 needs to be investigated.
Idle is high and uncontrolled at 1200 rpm with zero IAC counts. TPS voltage is low as already mentioned. BLM of 139 is a bit lean, but not a problem at this point.
Something is causing excessive airflow at idle as evidenced by the high rpm and zero IAC position, either a huge vacuum leak or too much throttle opening. Check that the throttle is fully closing and readjust tps voltage.
Note: I don't really trust your scan tool's definition file since some values have strange scaling such as the mass airflow signal (need to divide by 256), although the raw (8 bit unlimited airflow signal) looks about right at 12 gm/sec @ 1200 rpm.
Clear the codes to start fresh and see which ones come back again, then go out and try to reproduce the original complaint (at WOT) while recording and save the log.
TPS voltage still too low at 0.25 volts. Cell 0 BLM is very lean (155 and climbing). Note: 160 is the maximum allowed BLM. Why so lean? Are you running small injectors, low fuel pressure or high ethanol content fuel?
I added a column to show the Mass Air Flow/256 to correct the scaling. I also deleted the 2nd row (units) to play better with Datazap. I would like to see a log during actual driving conditions to see more fuel trim behavior.
Also would be good to see the full scale (WOT) tps reading to determine if it is a bad sensor, or just maladjusted. If full scale tps is reading way to low ( < ~3 volts or 70% tps)), you may not enter PE mode under heavy throttle/WOT.
Would also be nice to see the AFR target to confirm PE entry, but your definition file (*.adx) is lacking (assuming your scan tool app ALDLdroid uses TunerPro style *.adx files).
Last edited by tequilaboy; Feb 13, 2021 at 01:49 PM.
TPS voltage still too low at 0.25 volts. Cell 0 BLM is very lean (155 and climbing). Note: 160 is the maximum allowed BLM. Why so lean? Are you running small injectors, low fuel pressure or high ethanol content fuel?
I added a column to show the Mass Air Flow/256 to correct the scaling. I also deleted the 2nd row (units) to play better with Datazap. I would like to see a log during actual driving conditions to see more fuel trim behavior.
Also would be good to see the full scale (WOT) tps reading to determine if it is a bad sensor, or just maladjusted. If full scale tps is reading way to low ( < ~3 volts or 70% tps)), you may not enter PE mode under heavy throttle/WOT.
Would also be nice to see the AFR target to confirm PE entry, but your definition file (*.adx) is lacking (assuming your scan tool app ALDLdroid uses TunerPro style *.adx files).
i was able to get some readings while taking a small lap around my neighborhood since roads are icy. At one point i floored it for a few seconds because it was only a small strip of road. I hope that was long enough. I apologize, i am not familiar with the terms PE mode or AFR target. The app i am using is ALDL Scan and im not sure where to locate those values.
What does TPS voltage read with the engine off?
Does the green dot beside the Code 33 indicate that this code is set, with an SES light coming on? Ignore the Code 32, but 33 needs to be investigated.
The Best of Corvette for Corvette Enthusiasts
WOT looks better. TPS voltage still on the low side, but is high enough to enter PE based upon fueling and rich O2 readings. You should be able to adjust the sensor to increase the voltage.
It is knocking and pulling quite a bit of timing (7-8 degrees). This may be what you feel in the car.
MAF flow looks ok, but is a bit high and appears to be limited a bit by the Max Air Flow vs RPM table (example below).
;--------------------------------------------------
; Max Air Flow vs RPM
;
; 17 LINE, 0 -> 6400 RPM
;
; TBL = Grams/Sec
;---------------------------------------------------
ORG $06EC
; gms/sec RPM
;---------------------------
LC6EC: FCB 23 ; 23 0
FCB 23 ; 23 400
FCB 30 ; 30 800
FCB 48 ; 48 1200
FCB 68 ; 68 1600
FCB 89 ; 89 2000
FCB 111 ; 111 2400
FCB 141 ; 141 2800
FCB 170 ; 170 3200
FCB 200 ; 200 3600
FCB 220 ; 220 4000
FCB 236 ; 236 4400
FCB 245 ; 245 4800
FCB 247 ; 247 5200
FCB 247 ; 247 5600
FCB 247 ; 247 6000
FCB 255 ; 255 6400
;---------------------------------------------------
Last edited by tequilaboy; Feb 14, 2021 at 02:19 PM.
WOT looks better. TPS voltage still on the low side, but is high enough to enter PE based upon fueling and rich O2 readings. You should be able to adjust the sensor to increase the voltage.
It is knocking and pulling quite a bit of timing (7-8 degrees). This may be what you feel in the car.
MAF flow looks ok, but is a bit high and appears to be limited a bit by the Max Air Flow vs RPM table (example below).
;--------------------------------------------------
; Max Air Flow vs RPM
;
; 17 LINE, 0 -> 6400 RPM
;
; TBL = Grams/Sec
;---------------------------------------------------
ORG $06EC
; gms/sec RPM
;---------------------------
LC6EC: FCB 23 ; 23 0
FCB 23 ; 23 400
FCB 30 ; 30 800
FCB 48 ; 48 1200
FCB 68 ; 68 1600
FCB 89 ; 89 2000
FCB 111 ; 111 2400
FCB 141 ; 141 2800
FCB 170 ; 170 3200
FCB 200 ; 200 3600
FCB 220 ; 220 4000
FCB 236 ; 236 4400
FCB 245 ; 245 4800
FCB 247 ; 247 5200
FCB 247 ; 247 5600
FCB 247 ; 247 6000
FCB 255 ; 255 6400
;---------------------------------------------------
All: Idle screw (and speed) setup, there is a procedure in the FSM. From factory, the screw head is blocked, factory didn't want that changed.
NOTE: If you do unblock your idle screw, need to add a method to lock the screw in position once set. If left to itself, the screw will move. I used a small metric lock nut on mine, once I figured out it was set wrong in the first place!
I like "datazap" presentations. I'll have to look into this tool now that Data Master (yes, I'm old) is no longer supported.
All: Idle screw (and speed) setup, there is a procedure in the FSM. From factory, the screw head is blocked, factory didn't want that changed.
NOTE: If you do unblock your idle screw, need to add a method to lock the screw in position once set. If left to itself, the screw will move. I used a small metric lock nut on mine, once I figured out it was set wrong in the first place!
- Adjust the tps in an attempt to reach 0.54 volts at idle. This is the standard setting. This won't solve your problems but will ensure that the ecm can differentiate between idle, part-throttle and WOT and help prevent false code setting.
- Clear codes by disconnecting ecm power. See which codes come back over time after correcting tps voltage.
- Check the timing (should be 6 degrees advanced with EST disconnected) and correct if necessary.
- If knocking persists, try a more knock resistant (higher octane) fuel if available. May be false knock, consider ecm tuning to address if all else fails.
- Collect more scan data under all conditions and look for fuel and knock trends.
- Increase fueling to correct for the lean blm readings. This can be done by increasing fuel pressure (crude), or ecm tuning (preferred).
- Get a more complete/correct *.adx file for use with your scan tool.
- wash, rinse and repeat.
Last edited by tequilaboy; Feb 20, 2021 at 08:57 AM.
Last edited by corvette95; Feb 20, 2021 at 09:55 AM.
- Adjust the tps in an attempt to reach 0.54 volts at idle. This is the standard setting. This won't solve your problems but will ensure that the ecm can differentiate between idle, part-throttle and WOT and help prevent false code setting.
- Clear codes by disconnecting ecm power. See which codes come back over time after correcting tps voltage.
- Check the timing (should be 6 degrees advanced with EST disconnected) and correct if necessary.
- If knocking persists, try a more knock resistant (higher octane) fuel if available. May be false knock, consider ecm tuning to address if all else fails.
- Collect more scan data under all conditions and look for fuel and knock trends.
- Increase fueling to correct for the lean blm readings. This can be done by increasing fuel pressure (crude), or ecm tuning (preferred).
- Get a more complete/correct *.adx file for use with your scan tool.
- wash, rinse and repeat.
and how can i change my computer's minimum idle speed to somewhere around 900rpm using the scan tool.
You don't, You need to reprogram it. Why do you want to do that?
I am concerned about the spark advance increase between the first 2 yellow markers.
Edit: After a closer look into both the ABTS bin and your logs, the spark advance signal does appear to be relative to the reference pulse, so the actual advance (relative to tdc) will be advanced an additional 5.98 degrees above what is shown in your logs. Can be confusing if you can't see both signals at the same time.
The rapid spark advance increase is the code 43 forced knock test in-progress (which can lead to engine damage if the knock sensor really is malfunctioning, so be careful).
Note: This is normal behavior, but the code 43 forced knock test spark ramp-up (up to 24.96 degrees over time) can be alarming to see. Once it knocks, the extra advance ramps out quickly with no harm done, but it is still scary to see the magnitude of the advance while it is occurring. This is a risky and poorly designed feature intended to test the knock sensor.
Keep an eye on the spark advance and knock retard behavior.
Can you attach a copy of your *.adx file? I will check the signals for accuracy and scaling.
For reference, your bin file should be ABTS based on the prom id/scan id. I will take a look into my copy of ABTS to verify the spark advance behavior. Do you know if it has ever been tuned or if it is a virgin (factory) bin file?
Last edited by tequilaboy; Feb 24, 2021 at 12:50 PM.
I am concerned about the spark advance increase between the first 2 yellow markers.
Edit: After a closer look into both the ABTS bin and your logs, the spark advance signal does appear to be relative to the reference pulse, so the actual advance (relative to tdc) will be advanced an additional 5.98 degrees above what is shown in your logs. Can be confusing if you can't see both signals at the same time.
The rapid spark advance increase is the code 43 forced knock test in-progress (which can lead to engine damage if the knock sensor really is malfunctioning, so be careful).
Note: This is normal behavior, but the code 43 forced knock test spark ramp-up (up to 24.96 degrees over time) can be alarming to see. Once it knocks, the extra advance ramps out quickly with no harm done, but it is still scary to see the magnitude of the advance while it is occurring. This is a risky and poorly designed feature intended to test the knock sensor.
Keep an eye on the spark advance and knock retard behavior.
Can you attach a copy of your *.adx file? I will check the signals for accuracy and scaling.
For reference, your bin file should be ABTS based on the prom id/scan id. I will take a look into my copy of ABTS to verify the spark advance behavior. Do you know if it has ever been tuned or if it is a virgin (factory) bin file?










