autove help please

[joecar]

Gary:

- is your FlashScan a V1 or a V2...?
- which wideband do you have...?
- did you connect a ground/return to the AD1- pin...?

[garyk1970]

Gary:

- is your FlashScan a V1 or a V2...?
- which wideband do you have...?
- did you connect a ground/return to the AD1- pin...?

I have the v2

Aem....model # in past post (I don't remember model#)

Yes , 5v on positive, gage ground on negative

[garyk1970]

I logged another drive and nothing has changed...after save be screen has different numbers saved than logged..

I also noticed the 70+ volts on the wide band....I'll double check everything....my gage never fluctuates.

[5.7ute]

I also noticed the 70+ volts on the wide band....I'll double check everything....my gage never fluctuates.

You do mean in the logged data after it has been saved???

[garyk1970]

Yes...before I save, on the data log map...I see numbers ranging .07-1.3....those I assume are "normal" numbers?
Then after i save the log, that same map shows 10.8 on all cells.

Before I saved, I saw 70v on the wideband log also...not sure what's going on....I'm an automotive electrical field engineer by trade....I'll monitor the v2 input....I'm sure its not 70v in...

[5.7ute]

Try just logging the EXT.AD1 pid on its own. Then check the values before & after saving.

[Blacky]

Looks like a bug with the way EXT.AD1 is being stored i the log file. Both EXT.AD1 and GM.AFR are being stored at the same byte offset in the frame. That means they will both be using the same raw value to compute their actual display value. One of them will be wrong, in this case the EXT.AD1 value will be wrong.

If you adjust the charts in V7 so that the EXT.AD1 PID is plotted with a vertical axis of 0..100 (instead of 0..5) you will see that the EXT.AD1 data is exactly the same as the GM.AFR PID's data.

I'll get a fix available for it asap.

Regards
Paul

[5.7ute]

Paul, would a work around be to use the EXT.AD2 slot instead?

[Blacky]

Paul, would a work around be to use the EXT.AD2 slot instead?

Probably not, I expect all EXT.* PIDs are being handled (incorrectly) as calculated PIDs and no data is being stored in the log file for the EXT.* PIDs. That means when the Scan Tool software tried to extract the EXT.* data from the log file it pulls the data from the first real PID in the log file. In this case its the GM.AFR PID.

Unfortunately I can't think of a workaround right now.

Regards
Paul

[5.7ute]

Logging the voltage through the EGR system like we do with the fuel pressure sender & making a calc pid should work.