Scan Tool Error

[Tre-Cool]

i just sent blacky a pm about this issue. the ad/external inputs have nothing to do with the problem imo. as i turned all of them off, deselected the pids from my list and still couldnt get it to work.

The workaround for now is simple and I have no idea why it works, but this is what i found out last week.

instead of opening the scanner software directly, open up a previous log file done by the v2 or v1 unit itself (by bbx), connect to the ecu, remove any pids or add ones you want if your not happy and start logging.

Everything will work like it normally would.

[joecar]

Ok, thx for the tip.

[EagleMark]

I get the same error with AD1 connected to WB. With or without PIDS still get error $0F...

[EagleMark]

Its a problem caused by the FlashScan firmware misinterpreting the A/D input values when no A/D voltage is applied. It will be fixed in the next software/firmware update.

Using one of the orange A/D connectors, try making a loopback connection to AD1 that simply connects both pins of the AD1 input together. That will hopefully pull the AD input signal down low enough to prevent it interfering with the data logging.
Attachment 13991
Attachment 13992

Nope, still get $0f error.

[EagleMark]

So would he see this because he has the analog pids automatically selected...?

That would probably solve the problem as well.
Regards
Paul

Nope still get error even with a jumper in AD1

[EagleMark]

gpr,

if you're not using the analog interface, start V8 S&T, goto F6: Devices, goto F6: Logging, and uncheck Automatically select ALL external analog pids;

then Save to file (Settings.dat) and Program to V2.

Nope, still get the error...

[joecar]

Nope, still get the error...

Error $0F...?

[EagleMark]

Yes, sorry Error $0F for all of those. First I had AD1 input from WB so no input is not the issue. Second was with the jumper wire as discribed above with no AD input. Third was following your instructions through V8. Still $0F...

Restart scantool with all analog PIDS removed and still $0F error on connect.

I gave up and went in for lunch and thought I'd give it one more try. Fail!

Now the cure! Disconnect OBDII plug from vehicle. Plugged it back in and it works! Still have jumper in, but could try without if you want?

Something about V2 loosing all power after this error and deleting all AD PIDS made it work. Was vehicle power and not laptop because it was disconnected from laptop couple times. V2 was plugged in vehicle and stays on through entire process and never turned off. Disconnect so it turns off, reconnect and no error.

[joecar]

Hmmm, interesting...


Paul will have a new software version soon...

[Tre-Cool]

Did you try my trick of opening pre-existing log file and then trying to scan?

I dont even use the AD ports as i have a serial wb and had the same problem.