just to add

purchased version of torque

messing with it three hours and still the same

pairs with htc evo

lights flash on the dongle while it tries to connect

blue gps, blue cell phone blue dongle flasjing black car

asks me if the car is on

both cars running while i tried it

Thanks again
Steve

Hi,

Are both vehicles diesel?

If so, '97 and '01 /may/ be too early to support OBD2 for diesel (diesel OBD2 for consumer vehicles took off around 2004 with most supporting the standard due to Enviromental laws requiring manufacturers to start using the standard.

It is possible that the adapter may also be faulty, but everything looks fine from the debugs - I'd start checking whether or not your vehicles actually support the OBD2 standard

Ian

Thanks for the response Ian!!

neither are deisels

1997 ford F150 4.2 gas
2001 ford mustang 3.8 v6

just tested on my buddy's 99 honda civic and it works perfectly.. still scratching my head on this one

"Fords use SAE J1850 PWM (Pulse Width Modulation) communication patterns."

does Torque see this protocol?? i saw the listing while it was scanning but not connected

again worked great today in my friend's honda civic but still cant get it to work in my F150 or Mustang

I just got a cheap e-bay bluetooth module too (the yellow orange one) and I am getting the exact results as you Bass.

I have a 98 Ford Windstar. 3.8L gas/petrol.

I haven't tried it on my '00 Taurus yet.

Maybe Torque just doesn't support the U.S. Ford Protocol???

When it tries to establish protocol connection, I too saw the lights flash on the bluetooth dongle. When I stop Torque, the lights stop flashing. I tried un-pairing the Dongle with my HTC incredible and re-pairing. Did not fix.

Checked the disable ELM327 auto time option. Restarted, still no go.

I am wondering if something might be wrong with my OBDII port on my vehicles as my Walmart Code reader suddenly quit reading/connecting as well about 8 months ago. Oddly enough, it could still erase codes.

I do know these computers are pre-CAN, but don't know if that should matter or not.

I am still playing with it an will try to get a comm log.

Ian, your app is very promising looking though, and I got to believe from what others are saying that either my OBD diagnostic port is bad/dead, or the bluetooth dongle may be bad. Only thing is, those darn lights flash on the dongle. So something is working. I wish I knew what the lights meant.

Hi

Some of the cheap ebay adapters seem to have difficulty (or flat out don't seem to support) at least one of the protocols for OBD2, also there have been instances where some of the pins required for a protocol have not been connected on the ebay units, this is seperate from the other timing problems the cheap units have

This is why I recommend staying away from the ebay units, mainly because a lot of people have problems with them

But as I said before, quite a few (but not all) diesels made before 2004 (when it was mandated) do *not* support OBD2, you probably have a vehicle that simply does not conform to the OBD2 standard!

If not Ebay unit whos unit do you recommend?
The ELM 327 unit on Ebay seems to be a nice device.

the unit worked on a 2004 acura tsx this weekend as i was testing other cars

Ian please know none of the cars i own are diesels - strickly Petro

Well, I tried my cheap e-bay adapter on my dads '05 Toyota Corolla today, and it worked!

Was reading a few of the newer threads and their definitely seems to be a problem with reading Ford vehicles. At least pre CAN ones. I wish I had access to a different bluetooth adapter so I could see if it is the cheap-o e-bay unit, or if the protocol is not supported by Torque.

Since I also suspect something might have actually damaged to my OBDII ports(because my Innova Equus Scan won't read them anymore either), at some point when I am at an Autoparts store, I need to have them come out and see if their store scan tools will connect.

Eventually I will learn something and will pass it along in hopes of helping Ian improve his program.

I have to say when it did connect to the Toyota, it worked great and it was very exciting to see just how much the program could do!

In closing, just want to say great job Ian on your program!

Guys, I have the same problem trying to connect to my 2001 mustang. It doesn't recognize the protocol. But this I know, there's nothing wrong with the mustang's OBD2 connector. I have access to several new style hand held scanners at my job and they all connect to my mustang and I am able to clear codes and look at data. At first I suspected the ELM 327 interface I bought from eBay. But, when I connected the ELM 327 to my daughter-in-law's 2004 Ford explorer it worked with no problems. I am viewing with my HTC evo. This leads me to believe that the ELM 327 cannot read the pre 2004 protocol, maybe due to timing issues or similar. I am determine to find out why. I will have to use oscilloscope to compare and will probable windup opening the ELM 327. I suspect the hand held scanners are microprocessor base while the ELM 327 uses a pic chip. Anyway, what would help; if someone out there has ever got the torque program to connect to a 2001 mustang or similar year Ford. I promise to let the forum know if I am able to solve the problem because connecting to my 2001 mustang is why I bought the ELM 327 and installed the torque app in the first place.

Hi

If you are using the blue/yellow clone adapter with "supports all obdII protocols' written at the bottom, then chances are the adapter is faulty. The J1850-PWM protocol on those adapters just doesn't work, and that is what most Ford ECU's use.

If you are using another type of adapter (a scantool.net one or an OBDKey for example) then you can use the 'send comms debug logs' menu option in the 'realtime' screen after leaving the app to send me a debug, and I will look at what is going on.

99% of the time people are using the cheap clone adapter with the blue/yellow label, and it's that that is the problem

Ian

I have a 99 Ford F350 w/7.3 diesel
It is superchipped and I have no problem reprogramming my ECU and clearing codes with the SuperChip setup.

This would imply my vehicle is OBD2 compliant.

I purchased a cheapo Ebay Vgate advanced OBD scan tool and Torque Pro for my ASUS tablet.

I connected all to my truck, the bluetooth paired up but I did not get an ECU connect

I connected the same setup to a 2002 Chev Surbane and everything worked just fine.
This would lead me to believe that the cheapo doggle does not work with the ford ECU format.

Question? What/whoo makes a 1999Ford compatable adapter?

This may help...

http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3834.0