OBD pinout diagram

[sms2022]

Can someone help me out with this? Need it for the sensor based flex fuel guide I’m working on. PM welcome

Sponsored

 

[Boyd]

Not sure how much this will help unless you know what module you need to talk to... its all digital data busses and high speed module communications. But here's the pinout for a '21....

 

[Skye]

One more.

 

[sms2022]

Not sure how much this will help unless you know what module you need to talk to... its all digital data busses and high speed module communications. But here's the pinout for a '21....

Thanks. This is perfect.

 

[ORRadtech]

Maybe I'm naive or uninformed but I thought all OBD was the same. I thought standardization was the purpose of OBD.
No?

 

[sms2022]

Maybe I'm naive or uninformed but I thought all OBD was the same. I thought standardization was the purpose of OBD.
No?

the ford diagram helps a lot because ford uses the same terms between the ObD port and the port I’m trying to tie into, which in this case is the connector on the back of the DLC.

 

[Garfy]

Maybe I'm naive or uninformed but I thought all OBD was the same. I thought standardization was the purpose of OBD.
No?

It all depends on what years you're speaking of because the early OBDII had minimally used terminals and was prior to CAN being implemented. Newer vehicles (like current models) used a lot more pins on the DLC for various data functions.

 

[ORRadtech]

It all depends on what years you're speaking of because the early OBDII had minimally used terminals and was prior to CAN being implemented. Newer vehicles (like current models) used a lot more pins on the DLC for various data functions.

That makes sense as far as it goes. It doesn't really answer the question though.
OBD2 is a standardized protocol, right? Data type"A" is going to be on a particular pin always, across all platforms, right? And if data types B, C, D, etc are added they will be assigned different pins, right? And that data, or equivalent, will be on those pins whether scanning a Ford, Chrysler, BMW,ect? Right? Isn't that what a standardized protocol is and why OBD/OBD 2 was created?

 

[sms2022]

That makes sense as far as it goes. It doesn't really answer the question though.
OBD2 is a standardized protocol, right? Data type"A" is going to be on a particular pin always, across all platforms, right? And if data types B, C, D, etc are added they will be assigned different pins, right? And that data, or equivalent, will be on those pins whether scanning a Ford, Chrysler, BMW,ect? Right? Isn't that what a standardized protocol is and why OBD/OBD 2 was created?

I think for basic DTC reading all you need is power, ground, and HSCan+ and -, so yes, but not all the pins are used on my obd port plus I’m plugging in a j2534 ford scanner so I’m sure there is customization available between manufacturers.

 

[ORRadtech]

I think for basic DTC reading all you need is power, ground, and HSCan+ and -, so yes, but not all the pins are used on my obd port plus I’m plugging in a j2534 ford scanner so I’m sure there is customization available between manufacturers.

That made a kind of sense to me and got me curious (more curious?l). I am aware that most (all?) manufacturers have proprietary tools/software. I didn't think that they utilized different pins in the port though, rather software coding unusable by generic tools. I found an article (link below) that seems to support both the thought of assigned pins and proprietary software used on those existing pins. It's a good article with a lot of information to help understand basic OBD 2 and its history. Why it came to be, what it has evolved to and what may be coming. I found the blurb on OBD 3 interesting and concerning. If implemented it could simultaneously make the data from your car available anytime/anywhere to the authorities and prevent any access outside of by the dealer/manufacturers. Scary shit!
Anyway, thanks for the help guys and here's that article if anyone is interested.
https://www.csselectronics.com/pages/obd2-explained-simple-intro

 

[Garfy]

That makes sense as far as it goes. It doesn't really answer the question though.
OBD2 is a standardized protocol, right? Data type"A" is going to be on a particular pin always, across all platforms, right? And if data types B, C, D, etc are added they will be assigned different pins, right? And that data, or equivalent, will be on those pins whether scanning a Ford, Chrysler, BMW,ect? Right? Isn't that what a standardized protocol is and why OBD/OBD 2 was created?

The "standardization" of the DLC was just for the "generic OBDII" data. I forgot if it was 16 pids or whatever the number of pids that were mandatory for manufacturers to deliver on the DLC. The CAN data stuff can vary between manufacturers as to what they will transmit over those data lines and the proprietary data can vary so unless you have a manufacturer specific scantool (or an aftermarket professional grade like OTC, Snap-On, Autel, etc.) you may not have access to everything there.

Sponsored