Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
OBDLink LX / Re: BMW Mini Cooper unsupported PIDs
« Last post by Chris Fincher on November 23, 2015, 02:00:54 PM »
I apologize for the confusion.  While our site does state you can read 90+ PIDs, that is a potential amount.  The actual number is limited by the vehicle.  Access to these varies from changing the address of messages sent by the tool to the information being on a different network that may have no physical connection to the tool.  Unfortunately, there isn't a way to tell what it does support without actually trying it.

"PID not supported by this vehicle" isn't a shortened way to describe what is happening or an indication that the tool can't decode it, since it doesn't do any decoding.  It means the vehicle actually reported that the PID in question is unsupported by the ECU(s) you are communicating with.

Ford / Re: 2012 Ford Focus Electric
« Last post by Chris Fincher on November 23, 2015, 01:47:28 PM »
The F350 is a special case if I remember correctly.  It is over the vehicle weight to be classified as a light duty vehicle.  Because of this, they are usually not compliant before 2004 unless they are in California.  Usually what you can get off them is very little.  Do you have any other vehicles you could try?

Ford / Re: 2012 Ford Focus Electric
« Last post by FooBot on November 23, 2015, 12:36:53 PM »
I was about to confirm the vehicle is OBDII compliant. Strangely enough I was getting the same sort of errors when trying this on a 2001 Ford F-350 that I was able to get a hold of.
Whenever I try and send a request. for a PID like 0100 or even 03 all I get back from either vehicle is ,<Unable to Connect> Which I find odd. I mean I am very certainly connected to the Bluetooth adapter and can continue to issue commands to it.

Is there something special I need to do for ford to get this kind of info?
OBDLink SX / Re: Error Connecting
« Last post by Chris Fincher on November 23, 2015, 11:36:47 AM »
That screenshot does help with what to do next.  Could you plug in the tool to another computer and check to see what that window shows you on the other computer?  If it doesn't show up on another computer, chances are, it's the SX itself that is the problem.

OBDLink MX WiFi / Re: MX WiFi won't connect
« Last post by DocTorus on November 23, 2015, 10:11:58 AM »
Thanks for the response, and I look forward to the exchange.
General OBD Questions / Re: Help Diagnose P0420 code on Ford
« Last post by Cajun on November 23, 2015, 08:45:09 AM »
Here is the regular scan screen showing a fail on bank one
General OBD Questions / Re: Help Diagnose P0420 code on Ford
« Last post by Cajun on November 23, 2015, 08:44:12 AM »
Figured it out :)

Here are some scans.

You can see the pre and post cat O2 sensors are the same on Bank one, cat must be shot. It isn't filtering anything.

On bank 2 the pre and post are different so the cat it still working. Although, from the looks of it, it may be almost done too. Its got some spots where they are close to the same reading.
« Last post by SOLOLUCKY on November 23, 2015, 08:09:10 AM »
I just rec'd my ScanTool OBD  dongle and I rapidly lost my instructions that gave me the validation code to download the app on my phone. It reads my torqueapp on the phone I use to monitor my Powerstroke vitals so I just ran with that. I saw the code and meant to download it...but before I remembered i threw the box away ...

Below is the purchase info

Nov 18, 2015 11:29:51 AM
Invoice #100034226 created

Please let me know how to proceed.

OBDLink MX WiFi / Re: MX WiFi won't connect
« Last post by avary on November 22, 2015, 09:45:05 PM »

We apologize for any frustration and we're sorry to hear that you did not receive the reply Alonzo sent on September 8th. Some email servers block messages from our eSupport system or filter them as junk and they end up in spam folders. Unfortunately these servers don't notify the client so we can be added to their whitelist.

Regarding our OBDLink MX WiFi, you're right. We have discovered there is a glitch in the WiFi module which sometimes causes connection issues. We have been working with Microchip, the WiFi module's manufacturer, on a resolution for some time. Our latest meeting was about 2 weeks ago and although they have not found a solution yet, we're confident the issue will be resolved.

Since you are using an Android device, OBDLink MX is reccommend. We will contact you shortly to set up your exchange.

We apologize for any inconvenience.

OBDLink MX Bluetooth / Re: U0100 Failure Code Question
« Last post by intoweapons on November 22, 2015, 03:22:35 PM »
That works perfectly.  If you get a problem before then, let me know.

Thank you for your cooperation.

Hi Chris,

The OBDLink MX has been plugged into my 07 Lincoln MKZ since last Wednesday the 17th.  This is after I unpaired both my samsung galaxy s4 and samsung tab 4 from the OBD2Link.  Since then, I have had no apparent issues or errors with my vehicle.

What would you recommend as a next step?  As much as I would like to reproduce the issue to verify your diagnosis, it certainly does scare me a bit...  Do you think this type of error could cause any permanent damage to the car's computer?  Minus not being able to clear the fault code/service engine light myself after the last U0100 error, it didn't seem to affect the car in anyway (that I can tell).

My original intent was to have my in-car tablet (samsung tab 4) "start-up" (wake from sleep), when the vehicle starts.  I was also going to have TorquePro open and provide real-time info/gauges on vehicle start-up.  Perhaps this won't be possible, as the TorquePro app would need to be running in the background (never closes), and would constantly attempt to connect with the OBDLink  MX unit, even when the car is shut-off (potentially causing the U0100 Comm Error)?

I am newer to the OBD2 world as well as TorquePro, so perhaps there is a setting I am not understanding to eliminate this possibility.

Thanks again for your support on this issue, it is really appreciated!  I would love to be able to get it working (even if not automatically on vehicle start-up) - it is a great tool for understanding your vehicle and catching problems before they turn into something very expensive! 



Pages: 1 2 3 [4] 5 6 ... 10