OBDII software that shows Vehicle Calibration ID

**searcherrr** · 06-29-2009, 03:01 AM

ok, Vitaliy - here's what I got from those commands (was able to do it using another OBD program):

ATZ ELM327 v1.3
ATE0 OK
>ATSP0 OK
>0100 SEARCHING...
>0100 41 0 BF 9F B9 80
>011C NO DATA
>0900 NO DATA
>0902 NO DATA
>0904 NO DATA

What does all that mean? HOw come NO DATA for all those? What does the one that looks like a mac address mean?

**Tomin** · 06-29-2009, 04:31 AM

I have on a table EEC from European Ford Mondeo 2.5V6 (year 96) and it signals to me that it is only OBD I (one, not II). It is still protocol Ford PWM/SCP, but can not answer on many PIDs. Only very few pids is accessible. Not Lambda tests, ....
Is there any cheap soft solution for it ?

**Vitaliy** · 06-30-2009, 12:32 PM

Originally Posted by searcherrr

ok, Vitaliy - here's what I got from those commands (was able to do it using another OBD program):

ATZ ELM327 v1.3
ATE0 OK
>ATSP0 OK
>0100 SEARCHING...
>0100 41 0 BF 9F B9 80
>011C NO DATA
>0900 NO DATA
>0902 NO DATA
>0904 NO DATA

What does all that mean? HOw come NO DATA for all those? What does the one that looks like a mac address mean?

PID 00 reported the following PIDs as "supported": 01, 03, 04, 05, 06, 07, 08, 09, 0C, 0D, 0E, 0F, 10, 11, 13, 14, 15, 18, 19. That's a lot of PIDs, but 1C ("OBD system requirements") is not supported, meaning that the vehicle is not OBD-2 compliant.

Further, when you sent "0900" you asked the vehicle which infotypes (CalID, CVN, VIN, IPT, ECUNAME) are supported. It responded with "NO DATA", meaning that none are supported. So then, of course, you got "NO DATA" when you requested VIN and CALID (0902 and 0904).

So unfortunately, your Windstar is not OBD-2 compliant. Does it have a sticker under the hood, that says it is?

Vitaliy

**searcherrr** · 07-01-2009, 01:35 AM

It is OBDII compliant. I have had Autozone, myself, and others use OBDII code readers on it before.

The X variable here is that I have a 3rd party PCM installed and I'm wondering if because its not the OEM PCM if its lacking some typical data it should have. IE: CalID is necessary for proper engine functioning. For it not to be in there scares me.

I will look at the sticker for you, but I already know the 95 3.8L Windstar is OBD2.

I also recently have gotten "Vehicle Data Bus Corrupted" error msg while using the EasyOBDII program after going WOT and I got disconnected. I wonder if electrical gremlins are erasing PCM data?

In any case I will look for the OBD2 Compliance sticker. Wish I would've known to use these programs when I had my original PCM in.

EDIT: I also know for a fact that 1996 was the starting year for OBD2 compliance therefore "A COMPLIANCE STICKER" or certification may not have yet been available to any car maker..... yet Ford followed the OBDII standard in developing the 1995 3.8L Ford Windstar because it requires no special code reader. A generic plain featured "code reader only" with OBD2 compliance can read from this PCM.

**searcherrr** · 07-01-2009, 05:03 AM

Well, I don't know what the deal is really. A moderator in another forum has a sticky up saying ALL years Windstar are OBD2 compliant, but the sticker doesn't say it under my hood. I will look at the PINS tomorrow and see if ALL of them are there too. I found out thats another way to tell.

Still, again it responds to OBD2 programs/datalogger.

**malcom2073** · 07-01-2009, 05:12 AM

3rd party PCM as in aftermarket, or OEM replacement (eg Autozone or Advance auto brand?). If it's an OEM replacement then it should have everything the stock one would have. Keep in mind in 1995 some vehicles were listed as OBD2 compliant because they implemented the protocol, however were lacking in some of the standard set of OBD2 commands which makes them not quite compliant.

**Vitaliy** · 07-01-2009, 11:19 AM

Originally Posted by searcherrr

It is OBDII compliant. I have had Autozone, myself, and others use OBDII code readers on it before.

This is a common misconception. Just because you can get data out of the OBDII port, doesn't mean the car is OBDII compliant. Some cars even respond with a "Not OBD compliant" message in response to PID 1C. Some, like your car, respond with nothing -- which means the same thing. I've seen Ford trucks responding with "OBD-I".

The implication is that even if you can get some data, it will probably be incomplete, and is not guaranteed to be correct.

Vitaliy

**searcherrr** · 07-08-2009, 07:59 PM

Vitaliy - Where might I obtain the SDK or other programming and query language information for OBD1 and OBD2 systems? Is it all OPEN SOURCE or hidden? - Thanks.

**searcherrr** · 07-10-2009, 01:26 PM

Vitaliy -

When you gave me those query commands were they Generic OBDII commands or were they Ford specific proprietary commands?

Remember we got "NO DATA" on the results, but the maker of this PCM is saying that it might need to be queried by a Ford Specific scanner to obtain the vehicle information. Whats your take on that?

Despite him saying that he felt that the query (if it was Generic OBD) should have revealed some data.

FYI - I have a 104 pin PCM connector and on the DLC pins 4 & 5 are grounds. Doesn't this mean I have OBDII ?

Please, I welcome anyone else to comment too. I'm in dire need. This problem has to get resolved.

**Tomin** · 07-10-2009, 02:25 PM

Hi searcherrr,

I have, here in Europe, Ford Escort and it HAS J1969 connector, it HAS 4 & 5 on GND and it is not OBDII compliant. It is OBDI with Ford's special physical layer and totally different protocol from any OBDII protocol. And it HAS common 16 pin obd connector.
OBDII is only protocol (bytes between ECU and outside machine) about how you can ask the car for example RPM.

I have on the table Ford's EEC V unit, (similar to yours ?) with 104 pins. It has Ford J1850PWM protocol (physical layer), but it IS NOT OBDII compliant. When I send question about compatibility to this ecu, it returns to me that it is OBDI compliant. It can communicate with a few pids, but only very few. And for example function "03 - read DTC" does not work.