Welcome, Guest. Please login or register.
Did you miss your activation email?
April 23, 2014, 09:23:22 PM
Home Help Search Login Register
News: OBDLink MX officially launched.

ScanTool.net Forum  |  Recent Posts
Pages: 1 2 3 [4] 5 6 ... 10

 on: Yesterday at 07:55:44 AM 
Started by Rocknrollnightmare - Last post by Chris Fincher
@Brian: I apologize for the delay.  I'll have sales contact you about replacing your tool.  I'm not sure if that will fix it but at this point, it's the only thing I can think of to fix this since it's the Bluetooth that's dropping out and across multiple devices.

@callforfire: Let me know how the PC usage goes.  Another thing to note that I'm pretty sure aware of is that the engine cannot be running when you clear codes.  It will cause all sorts of strange stuff to happen if you do that, and some of it could be permanent.  If it turns out that the PC does the same thing as your Android device, I can have sales contact you about replacing the MX.


 on: Yesterday at 06:51:21 AM 
Started by Rocknrollnightmare - Last post by callforfire
Thanks for the reply. I'll get back to you on the PC usage and how it works. I know with my phone I can drive around and watch the cool little gauges  without a problem. It's when I want to pull codes and clear them that I have the issue.
I don't know how relevant it is but I do recall having to be quick with OBD1 when doing KOEO on a few cars back in the day; Otherwise, the ecu would think it's done doing what it was asked to do and power off. Then again my scantool was a short piece of wire.
It just got me thinking that since diesels have a start/run sequence with the glowplugs and all, that the ecu is not going into test mode and then shutting down at the end of the cycle since the engine was not started.

Just some thoughts. Not sure why this would happen on the escape though, unless I broke my MX Embarrassed

 on: April 21, 2014, 11:51:14 PM 
Started by LaurentGom - Last post by LaurentGom
That's perfect, thank you.

 on: April 21, 2014, 08:18:19 PM 
Started by inthechateau - Last post by inthechateau
Thank  you very much, got the email with links for downloads. Finally getting back to this event. Been a long recovery. Thank you again, you guys are great!

 on: April 21, 2014, 06:24:40 PM 
Started by cerenkov - Last post by cerenkov
Great thanks for the reply.

 on: April 21, 2014, 06:14:50 PM 
Started by saltreefs - Last post by saltreefs
Just did it again with MX plugged in prior to key on for Vehicle 1.  Same R2D2 messages.  Vehicle 1 starts fine after removal of MX.  Don't want to try with it in though.

 on: April 21, 2014, 06:01:50 PM 
Started by saltreefs - Last post by saltreefs

Thanks for the response.

I turned power on without starting and then plugged into vehicles (same process on both vehicles).  At that point the error messages on the vehicle display went off like R2D2 on C3PO.  Vehicle 1 was a lot of sensor failure messages, ABS, Airbag, Fuel level, oil level, oil pressure, etc.  Vehicle 2 was traction control and stability control mostly that I recall and remained after removing MX and cycling ignition a couple of times to see if it just needed a couple clean cycles to remove message.  Will likely pull battery cable if that message persists..  Never tried to start vehicles as there was clearly some confusion going on.   

When I attempted to connect with either the S4 or the tablet I noticed the flashing OBD & Host lights and the power and BT were solid.  I was using the Automatic protocol.

 on: April 21, 2014, 05:46:36 PM 
Started by saltreefs - Last post by Chris Fincher

Were you plugging in the MX when the vehicle was running?  It shouldn't cause an issue if you do but it's always good practice to plug it in then turn the vehicle on just in case.  The error you got that said it connected to the scantool but not the vehicle, did it happen on both vehicles and was this after all the warning lights came on?


 on: April 21, 2014, 02:39:30 PM 
Started by saltreefs - Last post by saltreefs
As soon as I plug it in I'm getting ECU errors (Oil pressure sending unit, fuel level unit, ABS unit, oil level, etc.) on display of two vehicles tried.
•Which scan tool are you using?
•Connection type (serial port, USB, Bluetooth)?
•What is the serial number and manufacturing date of your device? This information can be found on the back of the unit.
115110063992  2013.12.06
•What is the operating system? Specify whether it is 32 or 64 bit
Android 4.4.2? Galaxy S4, OBDLink app 2.0.1/ (but I have Torque and Dashcommand also installed on S4), I also connected via Bluetooth with a tablet using only OBDLink app and got the same issue.
•What is the year, make, model, and country where the vehicle was purchased in, new?
Vehicle 1 is 2005 Pontiac GTO, purchased in USA.
Vehicle 2 is 2010 Chevy Traverse, purchased in USA

Vehicle 2 now has persistent traction control/stability control message not shown prior to attaching MX.

•If known, what is the engine type (gasoline or diesel, number of cylinders, displacement).
Vehicle 1: gasoline, 6.0L, V-8
Vehicle 2: gasoline, 3.7L?, V-6
•Which software are you using (name + version)?
•Describe the problem in detail:
Connection Failure to Vehicle.  Switched to tablet, still no change, same message.  Reset MX and tried again on S4. No change, same message.  Switched vehicles, no change same message.  Now vehicle 2 has code...

◦Which step of the Quick Start Guide are you having trouble with?
◦Have you followed the troubleshooting flowcharts? Which steps are you having trouble with?
?  don't know.  Did a reset by holding until green flashed and still have issues.
◦Exact text of any error messages you received.
Connected to the scan tool but unable to connect to the vehicle...

Um.. what next?

 on: April 21, 2014, 12:54:28 PM 
Started by timmeh83 - Last post by Chris Fincher
This is just because of the Year.  If it were a year newer, it should be OBD-II compliant.  If you didn't buy the tool on Amazon, you can contact sales@scantool.net to return the tool.


Pages: 1 2 3 [4] 5 6 ... 10
ScanTool.net Forum  |  Recent Posts

Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.8 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!