In all honesty this package could still be a ways out.

We are currently working on the Subaru enhanced add-on, and I can confirm that Subaru sent us the information to pull oil temperature from the Subaru BRZ. You just have to be patient, these things take time.

It shouldn't take more that a few minutes (2-4 minutes) to validate PIDs. It does this the first time you connect and saves it, you shouldn't need to do it again.

Most likely is that you just need to fill in your engine displacement in the Vehicle Manager. If you've already done that and it still isn't working, we'll need to get a tech log to look into it more.

Permanent codes are usually crash related codes that can't be cleared, they're permanent.

A pending code is a code that the ECU has noticed could be a problem, but hasn't been a problem long enough to turn on the light. An example might be that you hit a bump in the road and a sensor wiggles, you don't want the light on yet since it wasn't a real issue. Usually a pending code is a current problem.

After a code has been pending long enough, or has been detected enough times, it becomes a stored code. At this point where it's both a pending and a stored code I believe the light will turn on. After you fix the problem, the pending code will usually go away and the light will turn off -- but the stored code can stay set for quite some time.

I'm glad to hear you got this sorted out, let us know if you have any other trouble.

I've also seen issues with some newer iOS devices where we're unable to connect a second time without turning WiFi off and then back on. I don't know what causes this, I've only seen it on a 5th gen iPod Touch and an iPad Mini.

Try cycling the WiFi and see if that helps any.

Many Ford out-of-U.S. vehicles share powertrains with U.S. vehicles, but the ABS and Airbag systems are rarely the same (I've not aware of any examples where they are the same). If your Focus isn't an actual USA model, you probably won't get any Airbag information from our software.

You would need to get a version of Android that supports ad-hoc networks. Out-of-the-box Android does not support ad-hoc networks, I don't know why they choose not to.  You can also use more than one Bluetooth accessory at the same time, so it shouldn't be an issue you have 1 active already.

Our software supports any ELM or J2534 interface. That one you pictured looks like a proprietary interface, and I doubt its supported by our software.

Unfortunately, your vehicle doesn't use an ABS module that's wired into the OBD-II bus. Many GM vehicles from that time period still used ALDL protocol ABS modules. ALDL is essentially OBD-I, and can't be read by a normal OBD-II interface. Its not just that we don't support ALDL (we want to!), but there is an actual hardware difference, none of the OBD-II interfaces we support can connect to ALDL.

Our log files use a proprietary format. You can, however, export them to an Excel compatible .csv file. You can do this by loading the log file into ScanXL, and going to the Logging menu > Export. From a .csv file it should be easy to manipulate the data however you'd like.

You don't need a ScanXL license for this, the demo version will work just fine.

I'm looking at a BT1 right now. Its more or less a sqaure, the connector is only VERY slightly smaller than the rest of the casing. Each side is identical to the opposite side. The entire BT1 is roughly 2.25 inches long (57.15 mm), from the top of the connector to the other end. Its also about 1.75 inches wide (44.45 mm) at the largest point (which is the non-connector portion). These are not exact numbers, but they should be pretty close.

If you are worried about a size issue, you can get an OBDLink WiFi from Scantool.net with a right-angle connector on it.

I'm sure the issue is size, you can only email a file thats so big.

What you CAN do, is pull the .vdb file off of your phone through iTunes (which you've already done). This is your vehicle database, which includes log files saved under any of those vehicles. If you replace ScanXL's vehicle database with this file, it will get loaded when ScanXL starts up.

For Windows Vista / 7, ScanXL keeps its vehicle database in C:\Users\All Users, and its called ppe_fleetdb.vdb. Putting your iPhone file here will let you use ScanXL to directly load the log files.

There aren't any flags I'm aware of that would move it to another screen for you. I believe it just opens on your main screen, and you'd likely have to change the main screen to get it to open on the other one.

Just off the top of my head, I don't remember the GM ECU's from that time period recording the odometer. I believe they were only saved in the cluster, possibly the BCM but I'm not sure.

Send me a PM about this, I might be able to help you out with a custom PID script to replace an odometer.

The GoPoint BT1 is probably the easiest interface to just jump in the car and use, since its Bluetooth and should stay paired with your phone. The OBDLink WiFi would give you faster data rates (depending on your vehicle), but you need to either set it to auto-join the WiFi network from the OBDLink, or manually join it every time you get in the car.

Any interface should still work, its really just personal preference.