OBDII software that shows Vehicle Calibration ID - Page 2

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

Quote: 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.

searcherrr · 07-10-2009, 09:20 PM

Whats the command to send to the ECU for OBD compatibility? Surely if thats all it takes to find out, I can just issue the command query and see what it says.

Tomin · 07-11-2009, 06:32 AM

Command is 01 pid 1C (011c).
See "OBD standards this vehicle conforms to" in
http://en.wikipedia.org/wiki/OBD-II_PIDs

It is little bit confusing that OBDII "protocol" says something like "I am only OBDI compliant" :-)

Vitaliy · 07-11-2009, 04:47 PM

Quote: Originally Posted by searcherrr

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.

Sorry, I replied to your PM before I saw these comments.

The queries I gave you are generic OBD-II requests. Neither OBD-I nor OBD-II are open source, but while most OBD-I information is proprietary, at least with OBD-II you can purchase the docs. If you want to program for OBD-II, get the SAE J1979 standard.

It makes sense that if a car has a diagnostic connector, there's got to be a way to use it to pull information out of it. So if it doesn't support OBD-II, then it probably supports a proprietary protocol.

Sorry I couldn't help you more.

Best regards,

Vitaliy

searcherrr · 07-11-2009, 05:53 PM

Thanks for the info Vitaliy.

What about the command to request the PCM's (ECU) compatibility? Anyone know that?

Tomin · 07-11-2009, 06:35 PM

Try a look at PID 1C on wikipedia, ...
Command 01 + pid 1c.

Vitaliy · 07-13-2009, 09:12 PM

Quote: Originally Posted by searcherrr

Thanks for the info Vitaliy.

What about the command to request the PCM's (ECU) compatibility? Anyone know that?

What do you mean? Compatibility with what?

Vitaliy

Vitaliy · 07-13-2009, 09:18 PM

Quote: Originally Posted by Tomin

Command is 01 pid 1C (011c).
See "OBD standards this vehicle conforms to" in
http://en.wikipedia.org/wiki/OBD-II_PIDs

It is little bit confusing that OBDII "protocol" says something like "I am only OBDI compliant" :-)

Response to this PID is independent of the protocol. It describes the OBD system, not the communication protocol. So you can get any one of the responses on J1850, ISO, or CAN.

I have seen vehicles that respond with "OBD-I" and "Not OBD compliant". For instance, many heavy Ford trucks/vans (F-350, etc) respond with "OBD-I".

The latest edition of SAE J1979 added a dozen more choices beyond 06. They now include Japanese, Australian, and Brazilian OBD, among others.

Vitaliy

User Name		Remember Me?
Password