Anyone having problems with their Foxwell software?

[andrewwynn]

The limited set and no vin matches the condition with wife's 2000.5 model year. On that car I had to connect to the round port under the hood for the full list.

When it happens out of there blue suggests a fuse or wiring issue. People have had this problem when the obd connector had cracked and some pins didn't make properly.

[workingonit]

Originally Posted by andrewwynn

The limited set and no vin matches the condition with wife's 2000.5 model year. On that car I had to connect to the round port under the hood for the full list.

When it happens out of the blue suggests a fuse or wiring issue. People have had this problem when the obd connector had cracked and some pins didn't make properly.

My 2001 only has the 16-pin OBD port, so the 20-pin isn't applicable. But, I used two OBD extender cables, one that's a splitter, with two on/off switches, that may be the problem. I'll quit using them, and plug the Foxwell (or whatever OBD device I'm using) directly into the underdash port, one at a time.

Come to think of it, last time I was testing/experimenting with scan tools and cables, I had some problems with extensions.

I always leave my OBDLink LX bluetooth dongle plugged in, so I don't have to go thru set-up everytime I want to use OBBDWiz or Torque Pro apps on my tablet. The second cable extension is for my INPA laptop USB FTDI cable or the Foxwell. I'll turn off one extension in order to turn on the other. But, there might be some pins mismatched or circuits crossed in either cable (Chinesium), so I'll not use them like that anymore.

I have time enough to reset my bluetooth dongle before I drive the X5, since I only drive it every three months!