6G Celicas Forums

Hey all just wondering if i was to get a OBD 1 to OBD 2 adapter Link and then to add an OBD 3 scanner to usb Link would it get the correct data to display realtime Engine RPM, Speed, Air Flow etc etc.

just wondering if anyone knows if it would work or if thay have done it what they used to do it and what programs they used.

Thanks

WOW!!! i did not know that there was such an adapter! with it being so cheap it would be worth giving it a try. as for then being able to use OBDII scan tools after i dont know. i would think that it would all depend on how the scan tools worked.

i would think that the real question would be if the codes read the same? idk.. but this would definatly be interesting to see if this could let you then use a cool smart phone app like Torque with an OBDII blue-tooth dongle?

So you have OBDI currently? I doubt if you could take it to OBDIII. OBDII has some extra wiring in the harness and I think different sensors. If you tried to take it to OBDIII, there would probably be a good amount of missing information. But hey, there's only one way to find out!

yup, i agree.. but the question would be, does the ecu still send info that the device can decode/encode properly that the App can use acuratley? and yes to go from OBDI to OBDII there are many sensors that would not be there, but then again there are still many inputs that are availible on OBDI that do no have any kind of display to read..

personaly i am interested in doing this package (22pin -to- OBD port connector, OBD port scanner/Blue-tooth transmiter, and the $5.00 torque app)

for me it would be on a 95 7afe auto, and since i am in the process of rebuilding the motor, and will be taking a 1200 mile trip just after i break the new motor in, something like this (should it work right) would go a long way to provide me allot of piece of mind, and important information that the stock gauge pod, and the few additional gauges will not offer. not to mention the ability to data log, and get fault codes.. effing awesome.. again only if it works.. should i have the additional $45 to spend after getting all that i need to finish my rebuild i may go ahead and do this.

i am most excited by the low total cost (assuming that you already own an android) and the fact that this combo may give us OBDI owners an ability/tool that has generally been ignored by the aftermarket. Normally resulting in having to buy a more expensive piggy back unit, and having to fabricate a custome harness just to simply access a data stream that is already being pushed to the ECU already....

This post has been edited by mandrek: Dec 30, 2011 - 4:49 PM

Hmm..not sure. I have a 95 celica GT that was made in mid-94 and has an OBDII connector under the dash. So it is a pre-OBDII car, but it has the right connector built it. It doesn't display all of the same functions as the 96 and newer OBDII cars at the shop do. I would guess that id doesn't work and that adapter is probably for a scanner that only has the OBDII plug but the firmware on the scanner is capable of scanning OBDI and OBDII. But this is only a guess, I wouldn't take it as fact. I wouldn't try it.

If you want to try it for dirt cheap though, and if you have an android phone, get one of the bluetooth adapters on ebay for $25, install "Torque" from the android market (free), and get the adapter that you have in the link. Whether it works or not, it's a cheap way to find out.

OBD2 data is more than just 'signals', its a serial data stream (digital), where as from what I understand the 22pin toyota diag connector is just raw signals from the PCM and very very limited serial data which does not conform to the global OBD2 specifications.

well that is what i was thinking, but hoping was not the case.

the thing is that the "raw" signal from the OBDI ECU would still have to be a digital stream, and aside from the the lack of a number of inputs, the devices that are sending the inputs are (for the large part) the same.
the real question on the stream (as you pointed out) is what format does the data come as.. and if the "scan tool" will be able to read any of it at all. or even be able to establish a connection..

well soon enough we will know, if tonight is good enough (new years eve, and i work at a restaurant) i will go ahead and get the two gadgets to see if they will work. i will first try it with the free version of torque...

well.. sh!t,, lol.. we wont know if it works for about another 3 weeks or so since i am going to have to wait on the machine shop for the final prep to my block and crank before i can get the car back together..

Bitter, as for the "raw" signal, are you referring to it being just a port for a pin on ECU to jump to? if i am reading that correctly then yes defiantly most of the pin-outs on the OBDI "diagnostics port" is just jump points (like on a chip) but there IS a data stream off that port right?

****.. if anyone has a pin-out/schematic that would help allot.

I know that you can read the oxygen sensors and some other stuff from the diag port the same as if you back probed the sensor directly. You can pulse out the fuel trims, and a few other neat things.

I'd be interested to know this as well, would be handy.

Im building up a CarPC atm so once its in the car i will get the plugs test it out..