Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
OBDLink SX / Re: Desperate for help - ATMA command doesn't work
« Last post by STN-Brian on May 03, 2016, 02:30:41 PM »
Do pins 2,3,7, and 8 have metal contacts?  From the picture it looks like they have some sort of plastic.  If they do not have metal contacts, it would appear that your vehicle only supports HS-CAN.
32
OBDLink MX Bluetooth / Re: OBDLink no BT signal recognized by phone
« Last post by STN-Brian on May 03, 2016, 02:20:42 PM »
I'm glad you got it working!
33
OBDLink MX Bluetooth / Re: OBDLink no BT signal recognized by phone
« Last post by Teekat99 on May 03, 2016, 12:14:59 PM »
Ok, update, I have confirmed...that I'm an idiot.
I was looking for it to pair as soon as I turned the key on and I was pressing "connect" button in the app. Not the device. (sigh)
Everything came up normally. I plugged it into my wife's car and it worked fine.
I appreciate the help. And thanks for the quick response.
Looking forward to using it on the race car.
34
OBDLink MX Bluetooth / Re: OBDLlink MX power down (sleep question)
« Last post by Bill A on May 03, 2016, 11:48:51 AM »
You're a couple levels above me on post #2; I don't know how to do that. :( On post #3 and FWIW, I did take a voltage reading at the 14 hour point and it was 12.7 which of course, doesn't say when it dropped below 13V.

Might you be able to point me to a source where I can figure out how to do  what is noted in post #2? I"m pretty computer4 savvy, just not well versed on auto networks but working at it. :D Thanks.


****Edit****

Plan B - I did a little looking at what UART is and I think plan B, verify by experiment and test will produce the desired result. keywords are in post #3, "Whichever is met first will put the tool to sleep."
35
DashCommand / New obdlink sx not being recognized.
« Last post by Username123 on May 03, 2016, 11:42:12 AM »
I bought and received a new obdlink sx from an authorized reseller and it will not connect to dashcommand android. Dashcommand won't even see it plugged in. I have been going back and forth with the dashcommand support and they are now saying it's an issue with my obdlink sx.
Have there been any hardware changes or am I missing something here?
36
OBDLink MX Bluetooth / Re: OBDLlink MX power down (sleep question)
« Last post by Shawnf350 on May 03, 2016, 11:27:01 AM »
To add, there's also a voltage trigger set at 10800 secs or 3 hours for when voltage is <13v.
Whichever is met first will put the tool to sleep.
37
General OBD Questions / Re: Garmin Virb XE
« Last post by _OZ_ on May 03, 2016, 11:21:25 AM »
Externally the are very similar. Just a different front face.
38
OBDLink MX Bluetooth / Re: OBDLlink MX power down (sleep question)
« Last post by Shawnf350 on May 03, 2016, 11:20:23 AM »
Using a terminal program, enter the following
STSLCS
this will list your current sleep settings if your interested.

I believe UART sleep default is 600sec
Which is 10 minutes.

Shawn
39
OBDLink MX Bluetooth / OBDLlink MX power down (sleep question)
« Last post by Bill A on May 03, 2016, 10:42:00 AM »
Hello, and to answer the questions in the "read first",
OBDLink MX
Bluetooth
 SN 115110116919 Mfr 8-13-2015, Rev 2.2/R4
Android 5.0.1 on a SGS4 and other device runs W7 Home premium
2004 Ford Ranger FX4 Level II USA
4.0L V6 gas
FORScan Lite V1.2.1 (Android) and FORScan V2.3.1 beta for Windows

In the course to trying to address the ISO bus concern in my other thread, and because in part I purchased the MX unit for the sleep mode, I've been watching the sleep performance and times very carefully. So between last night to this morning, 14 hours later and the time beginning after testing the unit with a drive and Torque Pro running, it was noticed that the power LED was on and the BT light was slowly flashing. I then read the thread "OBDLink MX Drainned Car Battery " and got the picture.

So with this information, I reset the MX (aka, unit) to factory setting, unplugged it for 30 min, plugged it back in, did NOT pair nor touch the pair/reset button, and noticed that it went to sleep in nearly 10 min flat. So....I unplugged the unit again, plugged it back in and did another factory reset (reset button not touched). And again, it went to sleep in nearly 10 min flat. Next, the unit unplugged/plugged back in and was paired with the SGS4 phone, and NOT tested with any apps. And again, the unit powers down in 10 minutes.

So with this in mind, the MX being theoretically set at factory default and merely being paired to an Android phone, why is it powering down/sleep after 10 min? Because, I recall reading that it should be 2 hours. Not that I don't mind the 10 minutes, but it bugs me not knowing why it's not at the default 2 hrs, and this in light of the ISO bus concern. Just trying to be very methodical in the analysis is all.

Thanks in advance!
40
OBDLink MX Bluetooth / Re: OBDlink MX not recognizing Ford 9141 ISO bus
« Last post by Bill A on May 03, 2016, 10:17:43 AM »
OBDLink is definitely in in the gameplan, but before doing that I've discovered a power down concern that is going to generate a new question/thread.
Pages: 1 2 3 [4] 5 6 ... 10