Ford Focus ST Forum banner
1,281 - 1,300 of 2,075 Posts
Discussion starter · #1,281 · (Edited)
Dont load the file, sinply read the BCM on auto. The BCM will load its current values, change the global setting to enabled and click write. Are you using focccus 8.3?



Sent from my SAMSUNG-SM-N910A using Tapatalk
 
OK. Tried a fresh pair and auto setting via focccus. Made it to 40 percent on a read from bcm and it failed several times. Every time retried and received error. Connection rate comes to 38400. Both boxes checked. When it does the blue light on the MX just flashes and Windows reported device is not connected. I also tried turning off headlights, accessories, ac, etc.. Still fails.. Confirmed using 0.8.3. Any advice?
 
Discussion starter · #1,283 ·
OK. Tried a fresh pair and auto setting via focccus. Made it to 40 percent on a read from bcm and it failed several times. Every time retried and received error. Connection rate comes to 38400. Both boxes checked. When it does the blue light on the MX just flashes and Windows reported device is not connected. I also tried turning off headlights, accessories, ac, etc.. Still fails.. Confirmed using 0.8.3. Any advice?
Weird. So you pair with pc? Device manager show obdlink MX as the connected device? What version of windows? I had issues with windows 8. You may need to get the proper drivers off the scantool.net site. Sorry i cant help more. Several of us have had zero problems with the obdlink MX. Is forscan able to stay connected?
 
I think drivers are the root cause of connection problems. I'll try to specify scantool drivers and try again. Yes paired with pc running win 7. I don't think forscan stays paired, but I'll dbl check tomorrow. Thanks..
 
Discussion starter · #1,285 ·
I think drivers are the root cause of connection problems. I'll try to specify scantool drivers and try again. Yes paired with pc running win 7. I don't think forscan stays paired, but I'll dbl check tomorrow. Thanks..
Here is what i think is the problem, once the mx is paired with your pc the connection is turned off because the bluetooth isnt needed like normal. Focccus uses the com port that bluetooth is able to wirelessly connect to. Here is a quick setup procedure for the use of com. http://windows.microsoft.com/en-us/windows/choose-com-port-bluetooth#1TC=windows-7

Sent from my SAMSUNG-SM-N910A using Tapatalk
 
Here is what i think is the problem, once the mx is paired with your pc the connection is turned off because the bluetooth isnt needed like normal. Focccus uses the com port that bluetooth is able to wirelessly connect to. Here is a quick setup procedure for the use of com. http://windows.microsoft.com/en-us/windows/choose-com-port-bluetooth#1TC=windows-7

Sent from my SAMSUNG-SM-N910A using Tapatalk
I tried the suggested settings and verified the MX is set to com 5/6. Also tried local drivers on com 7/8 but saw the same behavior. The Bluetooth connection dropped as if it timed out. Also tried disabling Bluetooth power management but no luck. Any other thoughts?
 
Discussion starter · #1,287 ·
I tried the suggested settings and verified the MX is set to com 5/6. Also tried local drivers on com 7/8 but saw the same behavior. The Bluetooth connection dropped as if it timed out. Also tried disabling Bluetooth power management but no luck. Any other thoughts?
Im gonna mess with it a bit tonight. Hopefully ill have an update for you soon.

Sent from my SAMSUNG-SM-N910A using Tapatalk
 
Discussion starter · #1,288 · (Edited)
OK, you need to let windows control the pairing of Bluetooth devices not any software from scantool.net. Go to devices and printers and add Bluetooth device. Right click the device in the pc that turns on Bluetooth and choose Bluetooth settings. click options, make sure your pc matches these settings.

If no com port device is shown click add, choose the obdlink and make sure the settings match, if the port is not available choose a different one like 4 or 6.

Only check the discovery box so windows can go into search mode inorder to make a first time connection to the obdlink. since you used software from scantool instead of windows you may need to redo this step. After this is all setup you shouldn't need to do it again. Forscan works the same way so no setting changes for that. OBDlink MX/WIFI is the recommended adapter for that program by its developer.

The first 3 pics are for the internal bluetooth module in your pc. The last picture is for the Obdlink MX bluetooth settings. I assume your have to set 2 com ports, 1 incoming and 1 outgoing like a normal parallel network.
 

Attachments

I have had similar problems with my OBDLink MX. I can get it to connect and stay connected with Forscan, but Foccus keeps disconnecting. This is with Windows 8.1 using built in bluetooth on laptop.
 
I'll try to remove the scantool software and have windows manage the connection. To be honest I'm pretty sure Windows is managing it right now. I pair using the windows 7 Bluetooth control panel and have verified both com ports are assigned to the MX. Do most ppl have the MX WiFi or Bluetooth? I ordered a USB Bluetooth adapter to try on another computer. Should I just break down and get the cable?
 
Discussion starter · #1,291 · (Edited)
I'll try to remove the scantool software and have windows manage the connection. To be honest I'm pretty sure Windows is managing it right now. I pair using the windows 7 Bluetooth control panel and have verified both com ports are assigned to the MX. Do most ppl have the MX WiFi or Bluetooth? I ordered a USB Bluetooth adapter to try on another computer. Should I just break down and get the cable?
Tbh, ive not ever had a single issue with staying connected. Ive seen where others on the scantool.net forums have had issues which required a hard reset of the obdlink. The wifi version just came out about 6 or so months ago. The MX has been out for several years now. The wifi version was made because Apple has their devices on bluetooth lockdown. Now that the new wifi mx is out Forscan has gone and released a beta version in the appstore.

Id tray an elcheap Elm327 1.3 adapter. Dont fall for the 1.5 adapter jargon. Their is no such device from elm. Itll be a chinese knockoff with potential problems if you go that route.
 
So I finally got my ELM last night and updated the BCM per the thread.

184 - set to global windows/sunroof enabled (works great!)

The main reason I got this though was to remove the 'low beam fault' that I keep getting with my retrofit headlights-

I've been running with schematic (using relays/resistors) for over a year without fault and a couple months ago, the fault came up again even though my headlights function just fine.
http://i867.photobucket.com/albums/a...-solutions.jpg

So, I updated the values for the following lines-
14 - alternative HID
17 - without dimmed dipped headlights

Then, cleared codes with Forscan (also did this prior to updating bcm)

However, the low beam fault still appears. :\

Any ideas? I'm thinking a battery pull and removing the resistors, but keeping the relays. @XRJoe , @Now534 , @JordanFiveOh - just tagging you guys just in case you may know something about it. Thanks!
 
I believe that's the same thing I did. Mine works fine, but I lost fog light functionality during the process. I had to have someone else do it since I don't have Windows at home (Mac user). I assume a reflash will fix my foglights, but my headlights work fine.
 
So I finally got my ELM last night and updated the BCM per the thread.

184 - set to global windows/sunroof enabled (works great!)

The main reason I got this though was to remove the 'low beam fault' that I keep getting with my retrofit headlights-

I've been running with schematic (using relays/resistors) for over a year without fault and a couple months ago, the fault came up again even though my headlights function just fine.
http://i867.photobucket.com/albums/a...-solutions.jpg

So, I updated the values for the following lines-
14 - alternative HID
17 - without dimmed dipped headlights

Then, cleared codes with Forscan (also did this prior to updating bcm)

However, the low beam fault still appears. :\

Any ideas? I'm thinking a battery pull and removing the resistors, but keeping the relays. @XRJoe , @Now534 , @JordanFiveOh - just tagging you guys just in case you may know something about it. Thanks!
Hmm, that's odd. Do you get the error with the stock, working headlights installed? I wonder if there's another issue and that's why you ran into the error with the resistors.
 
Hmm, that's odd. Do you get the error with the stock, working headlights installed? I wonder if there's another issue and that's why you ran into the error with the resistors.
Nope, no error with the stock halogen lights. It's a bit puzzling. I'll try removing the resistors and doing the battery pull. If that doesn't work, will probably have to try swapping out the relays and/or the hid ballasts. Crummy though because the lights work fine aside from this fault.

At least the global open/close of the windows work :p
 
Nope, no error with the stock halogen lights. It's a bit puzzling. I'll try removing the resistors and doing the battery pull. If that doesn't work, will probably have to try swapping out the relays and/or the hid ballasts. Crummy though because the lights work fine aside from this fault.

At least the global open/close of the windows work :p
Can you throw a multimeter and measure resistance between your ground and +12v on the low beam side on your headlight (or wherever you're tapping +12v for the resistor)? I had one the leads on my resistor break which will throw the error. Didn't notice until I went to remove it and the wire fell out.
 
Can you throw a multimeter and measure resistance between your ground and +12v on the low beam side on your headlight (or wherever you're tapping +12v for the resistor)? I had one the leads on my resistor break which will throw the error. Didn't notice until I went to remove it and the wire fell out.
I don't have a multimeter unfortunately, and I actually replaced the resistors prior to doing this bcm update, so I don't think the fault would be there. It may be on the relays if anything. Thanks for the tip though!
 
I don't have a multimeter unfortunately, and I actually replaced the resistors prior to doing this bcm update, so I don't think the fault would be there. It may be on the relays if anything. Thanks for the tip though!
I shouldn't be with the relays though. They're actually the reason for the fault and what the resistors are fixing.
 
Discussion starter · #1,299 ·
Try leaving dimmed dipped turned on along with alternative Hid on.
 
1,281 - 1,300 of 2,075 Posts