Ford Scorpio Forum - Print Page


    
      
        Ford Scorpio Forum
        (https://www.fordscorpio.co.uk/cgi-bin/yabb/YaBB.pl)
      

        General >> OBD Advice >> VE - "hidden codes"
        
(Message started by: adamn on Feb 27^th, 2009, 8:32pm)

Title: VE - "hidden codes"
Post by adamn on Feb 27^th, 2009, 8:32pm

Hi,

following my different post at different place, I want to ask something about VE / TriCom.

I have a 1995 scorpio, DOHC 16V 2.0.

Basically, the situation follows:

EECV - there are zero trouble codes reported by VE software, and the same is also reported in extended list of codes (eg. DTC_CNT = 1 and that is the "OBD NOT DONE YET" P1000 code, readeable by extended mode).

then I run the key-on engine-off test, test goes, all actuators switch on/off etc... and VE results as no codes stored in EECV module (in the listbox at the same window). But - the DTC_CNT field changes, it shows now 3 instead of 1. Does that mean that there are some new trouble codes stored now? Probably yes.
So I tried to read them out, but none of the basic/extended code readings using VE still doesn't show any of those new codes. Clearing KAM clears those 3 codes.

my question is - what to do about it? Does anybody know?

TriCom works well with EECV, PATS, CCM.
I've tried airbags but no success, and because I have no problems with ABS I did not tried to read that too.

-offtopic-
Btw. I had a problem with ABS before, when the brakefluid spilled into the ABS module connector and dissolved one of the thick +12V cables, rendering ABS useless (till I've changed the wire). It really happend, about a few months after ford service changed the fluid or what was that what they did. But no codes were stored, just the ABS/TCS light went lit all the time. But this is all long time ago and does probably not have any connection to EECV. Just mentioning it, who knows.

It might be worth to scan it by another brand of OBD2 scanner, but I own only the VE TriCom lead... And the car is not running now so I can't get to any garage now... hmmm...
So if anyone knows what is going on... thank you.

Title: Re: VE - "hidden codes"
Post by Tompion on Feb 28^th, 2009, 3:39pm

I’ve just tried running the key-on engine-off test with my Tricom & didn’t get the 3 codes as you do. Maybe your P1000 has some influence?

What Version of software are you using? Ver 1.51 had been the last stable one for the Scorpio, but I’ve just tried Ver 1.63 & that seemed to work OK (even connected to ABS which V1.55 wouldn’t).

Whilst checking out the latest version I got 3 codes all P0000 for the CCM – this was due to Options/Gateway/filters/delete duplicate responses not being ticked - so check that setting.

What happens if you don’t clear the codes, shut down VE then restart are they still there?

Some of the extras like the test page can be a bit quirky with the Scorpio so it may mean nothing.

Re the other modules I’ve not managed to communicate with the Airbags either (forgot to try with V1.63 though).

Dave

Title: Re: VE - "hidden codes"
Post by adamn on Feb 28^th, 2009, 4:28pm

Hi,

I have the latest VE version, 1.63. Also downloaded all the extension files from obd-2.com.

Yes, you might get duplicate codes, and I also did (3x P0000 = duplicates). There is a checkbox in gw setting, to delete duplicates. I have tried it with and without this setting, no success. The 3 duplicates are just a coincidence, I guess.

I assume it might be the P1000 (OBD MONITOR NOT DONE) code, as you are guessing, BLOCKING the other codes generated after KOEOff test to be visible/downloaded. But the KEOff test should not be depandant on the finished route trip obd test. hmm.
but...
If I simulate some of the other codes, like when I unplug the impact switch, it immediately generates the "fuel pump monitor high" code (= so it works as it should). And DTC_COUNT increses accordingly.

If I clear then (that works, standart procedure, using extended window), the DTC_COUNT goes to 0 or 1 (P1000). VE indicates 0 all the time, even after restarting etc.

the question is still there, how to get the somehow hidden codes, if VE cannot read them (or doesn't show them), but the DTC_COUNT goes from 0 or 1 (P1000) to 3?

today, I'm sure that one of the codes must be an EDIS malfunction code - EDIS should be generating a 64us impulses on IDM wire, when the engine is not running, and after checking with scope it is not.
But VE doesn't show anything like that.

-off topic-

about the other modules - I did and still can connect to CCM and PATS, and I tried the ABS and it works.
PATS says 0000 NO CODES, CCM shows some error with LID CLOSING CIRCUIT (and some others, like double locking errors that happend a few years before etc., now repaired, but nobody cleared them), and ABS says also no error codes (but doesn't throw an error when connecting to server) .
The only settings I have done in gateway window is that I unchecked the CAN checkboxes (everything else is set to default values).
Airbags still not working, but I don't have any actual errors, but there might be some errors from past (like the clock spring error). hmmm.

-edit- repeating myself, deleted

---

Title: Re: VE - "hidden codes"
Post by adamn on Feb 28^th, 2009, 4:29pm

and yes, I forgot - if I shut down VE, and reconnect, the DTC_COUNT is still at number 3 (until cleared or KAM reset).

Title: Re: VE - "hidden codes"
Post by Tompion on Feb 28^th, 2009, 5:08pm

I find for the Scorpio the settings that work best for me in the Gateway protocol page are to untick everything except:
Tick Ford PMW set speed to 40
Tick auto reconnect
Tick Clear cache on reconnect

Ticking ISO isn’t necessary & tends to slow down the connection

Title: Re: VE - "hidden codes"
Post by adamn on Feb 28^th, 2009, 5:21pm

thanks for trying to help me, appreciate this.

I've been playing with those settings a lot, at no success. Just managed to get higher update rate for data, but no difference in my described problem.

Title: Re: VE - "hidden codes"
Post by Tompion on Feb 28^th, 2009, 8:19pm

I tried introducing a P1000 by disconnecting the MAF, but that still didn't give the 3 codes after running the key-on engine-off test.
Neither did it show a code for the diconnected MAF (engine run but not driven) - I assume it needs to go through the full driven duty cycle for a MAF code to appear.

You could try Ver 1.51 as that's had more testing by members of this site.

Title: Re: VE - "hidden codes"
Post by adamn on Feb 28^th, 2009, 8:43pm

yes, you are right. MAF code will show only after the engine runs a while with close loop operation.

about that P1000 - clear KAM and it will be there. It is present only until OBD2 finishes its monitors.

My 3 codes are there because I assume I actually do have some faults there. If yours car is OK, you should have no codes. I guess what one of them might be, but I can't read them. If I introduce some other, new codes, they will show up. hmm.

When I got my car ready and running, I will try reading it with diferent scan lead brand. I will post my results.
Just been wondering if anyone got into similiar situation.