OBD 1 to OBD II adaptor?
OBD 1 to OBD II adaptor?
I've noticed that since tablets have exploded, a lot of cool gadgets have been popping up such as heads-up HUDs, diagnostic tools ect....
The only problem is they all seem to need a OBD II interface and our cars are OBD 1. Since II is just an extension of the protocol, is it possible to use some of these gadgets via an adaptor?
I've seen a GM odb 1 to 2 adaptor cable floating around, but there isn't much info on it.
Thanks.
The only problem is they all seem to need a OBD II interface and our cars are OBD 1. Since II is just an extension of the protocol, is it possible to use some of these gadgets via an adaptor?
I've seen a GM odb 1 to 2 adaptor cable floating around, but there isn't much info on it.
Thanks.
Joined: Feb 2003
Posts: 2,498
Likes: 20
From: PNW
Car: 91 Black Formula KR
Engine: 305 TPI R69/G92
Transmission: Astro A5-Pro 5.0-McCleod
Axle/Gears: US Gear 3.42 Eaton True Trac
Re: OBD 1 to OBD II adaptor?
It would still pretty much be for display purposes... the only thing OBDI would let you do would be to clear codes... unlike the OBDII that let's you adjust things...
I have a Turbo Link for OBD1, that's pretty cool...
Debating on selling it cuz i have an EBL P4 Flash (which displays and let's me change)
Rafael
I have a Turbo Link for OBD1, that's pretty cool...
Debating on selling it cuz i have an EBL P4 Flash (which displays and let's me change)
Rafael
Re: OBD 1 to OBD II adaptor?
It would still pretty much be for display purposes... the only thing OBDI would let you do would be to clear codes... unlike the OBDII that let's you adjust things...
I have a Turbo Link for OBD1, that's pretty cool...
TurboLink - Brain Scan for your car on my Caprice - YouTube
Debating on selling it cuz i have an EBL P4 Flash (which displays and let's me change)
Rafael
I have a Turbo Link for OBD1, that's pretty cool...
TurboLink - Brain Scan for your car on my Caprice - YouTube
Debating on selling it cuz i have an EBL P4 Flash (which displays and let's me change)
Rafael
I was talking about the recent Bluetooth/usb dongles that work with tablets and stand alone devices that plug into an obd II port.
Joined: Mar 2006
Posts: 4,370
Likes: 18
Car: 1973 Datsun 240Z/ 1985 S-15 Jimmy
Engine: Turbo LX9/To be decided
Transmission: 5-speed/T-5
Axle/Gears: R200 3.90/7.5" 3.73
Re: OBD 1 to OBD II adaptor?
Not possible, at least not easily.
OBD I did not have a set standard in how information was to be transmitted out of the ECM, and therefore, every manufacturer has a different way of doing it and within those manufacturers, there could be thousands of different datastream protocols that could be used. There's at least 6 different ALDL protocols I can think of for the third gen F-body alone. Each protocol requires it's ownfile to decode what is being sent out from the ECM.
OBD II became standardized across all manufacturers for most of the datastream information. There are still some things that are manufacturer specific, but these parts of the datastream have not been mandatory to be accessible. It is because of this standardization that you see these easy to use interfaces.
The OBD II display devices are just that display only, they don't allow you to do any tuning of the vehicle. There are programs around that will allow an OBD II vehicle to be tuned, but not from one of the display devices being discussed here.
So in order to make this work, you will need to create a device that takes your datastream, and on the fly converts it to the OBD II protocol AND communcation type, most commonly a form of CAN-BUS anymore. The OBD I GM ECM uses a TTL type communication. So the device would need to be programmed differently for each vehicle and trim level, to then convert it, just to use the OBD II compliant display device.
You'd be better off making a display device just for your system. I have one such system from moates.net, but currently only supports $59 (Custom Turbo code based on the Turbo Sunbird/Syclone/Typhoon), $8D (Speed density TPI F-body and Vette) and $0D (most '93 to '95 GM TBI trucks, but not all), any others are not supported and likely won't be, which is why I will be making my own, to get the features I want, not what I'm allowed by some other programmer that doesn't think it's worth his time.
There is another system, that is much more adaptable, but I'm not sure what it's current status is. It's being made by an Australian bloke, that has found a way to make this idea extremely adaptable to most all OBD I ECMs.
OBD I did not have a set standard in how information was to be transmitted out of the ECM, and therefore, every manufacturer has a different way of doing it and within those manufacturers, there could be thousands of different datastream protocols that could be used. There's at least 6 different ALDL protocols I can think of for the third gen F-body alone. Each protocol requires it's ownfile to decode what is being sent out from the ECM.
OBD II became standardized across all manufacturers for most of the datastream information. There are still some things that are manufacturer specific, but these parts of the datastream have not been mandatory to be accessible. It is because of this standardization that you see these easy to use interfaces.
The OBD II display devices are just that display only, they don't allow you to do any tuning of the vehicle. There are programs around that will allow an OBD II vehicle to be tuned, but not from one of the display devices being discussed here.
So in order to make this work, you will need to create a device that takes your datastream, and on the fly converts it to the OBD II protocol AND communcation type, most commonly a form of CAN-BUS anymore. The OBD I GM ECM uses a TTL type communication. So the device would need to be programmed differently for each vehicle and trim level, to then convert it, just to use the OBD II compliant display device.
You'd be better off making a display device just for your system. I have one such system from moates.net, but currently only supports $59 (Custom Turbo code based on the Turbo Sunbird/Syclone/Typhoon), $8D (Speed density TPI F-body and Vette) and $0D (most '93 to '95 GM TBI trucks, but not all), any others are not supported and likely won't be, which is why I will be making my own, to get the features I want, not what I'm allowed by some other programmer that doesn't think it's worth his time.
There is another system, that is much more adaptable, but I'm not sure what it's current status is. It's being made by an Australian bloke, that has found a way to make this idea extremely adaptable to most all OBD I ECMs.
Re: OBD 1 to OBD II adaptor?
Another option is to use an OBDII system on your old drivetrain as is described in the TPI stickys
That gives several benefits in addition to compatibility to your feedback device
That gives several benefits in addition to compatibility to your feedback device
Thread
Thread Starter
Forum
Replies
Last Post






