Hey guys.. I'm trying to use FoCCCus and bluebooth ScanTool MX (as suggested here) to update Global open/close and set Headlights to HID (upgraded to ST3 stock lights on my ST2) but seems to have encountered inconsistent communication issues over bluetooth. Here is my process:

I run the Scantool connection wizard which launched add bluetooth devices in Windows 7 with the ignition on, engine off and MX in pairing mode. The device pairs successfully but I can't consistently connect on COM5 using FoCCCus. I also tried the Scantool windows software which only worked intermittently. After the first attempt it seems the bluetooth connection is lost. In order to reconnect I need to remove the device from recognized bluetooth devices in windows and re-pair from scratch. Once in a while I can perform a "Read from BCM" which ends up failing part way through. I tried to update the central config and "write to bcm" but it fails every time. Once it failed at 97% and didn't end up updating any of the values.

I captured screen shot of an attempt to write to BCM from a file and it failed at 40% with an error "Error During Loading VBF". At this point I noticed the bluetooth link between the laptop and the MX unit disconnected.

Been skimming this thread and found a few related reports but haven't been able to resolve my issue. I only have one laptop and one MX to test with. When setting up FoCCCus I made sure to set the port speed and other settings as described in the first page. I'm doing everything by the book and am not sure how to proceed, i'm worried I'll end up bricking my car if I continue. Is there a way to update system values via android app?

Around page 94-96 I saw a few people agreed that "500k did not work for me with reading errors but "auto" did at the default speed of 34,800." Is that the general consensus? Not sure if that is my issue since the bluetooth pairing process isn't controlled by FoCCCus but rather by Windows, no?

Any thoughts / suggestions? Frustrated 2013 Focus ST2.

 

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?

 

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..

 

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

 

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.

 

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?

 

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!

 

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.

 

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.

 

Try leaving dimmed dipped turned on along with alternative Hid on.

 

I believe you still need a load on both headlights for it to not fault out. For example have 2 inputs to your relay. If I unplug my foglight harness I get a fault code

 

I removed both resistors last night and did a battery pull. Lights still function just fine, but with that same fault. I'll try out your suggestions tonight though. Thanks!

 

Low beam fault? Anything about short to ground or something similiar? Ive had a low beam fault since before i started using Focccus. I have an ST3 and have never once messed with lights. My lights work fine so i erase the code in forscan and it always comes back.

What exactly does forscan say is the fault?

 

Didn't check yet.. Will take the car out for a drive later and verify. Hope all is ok after this. Otherwise if there isn't a config solution I'll just sell the ST3 lights and go aftermarket.

 

That was going to be my other suggestion was that you could be having issues with your internal bluetooth adapter on your pc. I wasnt going to suggest you purchase anything else till we troubleshot your current stuff. I use a bestbuy rocketfish micro bluetooth usb adapter. Never been a problem.

 

So i found a video on ffclub.ru tonight, this the forum responsible for the creation focccus. The video you are about to see is a ford focus mk3 instrument panel. They say there has been about 10 updates to our 2013 ipc since the quad screen came out. While the on screen display is in russian you should definitely recognize some of the screen but one in particular has me excited. Check it out at 2:47. Apparently the only difference between my ipc and the one in the video is that it comes with blue needles instead of red. Id really like to get my hands on the 3 or 4 files necessary to make this happen.

ESP Sport Funktion Ford Focus MK3:

 

I was able to get everything to work this weekend. Turns out it was something to do with the internal bluetooth adapter. I had an old Rocketfish piece laying around and using it was able to connect and read/write with no issues. Did the following changes, all appear to work fine with no ill side effects.

#18 set to "FOGLIGHT"
#101 set to "without tpms"
#131 set to without belt minder
#178 set to without shift light
#184 set to global open and close

 

Sorry if its been stated, but what does the #18 foglight setting do?

 

Mine is a 2013 ST3 - with my particular car it will NOT turn the fogs on independently of the switch. They will stay on with high beams though, otherwise works as stock. Way I look at it, you have a better chance getting pulled over for high beaming a cop regardless of if the fog lights are on or not. It is also illegal for you to run fogs and no headlights (fogs and parking lights), yet that was enabled from the factory?

NOW534 - what does the DDS do differently from the TPMS that comes enabled from the factory? I disabled mine only because I don't have sensors in my winter wheels, but plan to enable it again come spring.

SQ

 

DDS reads your wheel speed sensors (ABS) what it does is detects the speeds or revolutions per minute the tires are traveling. If you start losing air pressure the RPMs of the tire leaking will change. This will throw a fault on the IPC telling you to check tire pressures.

I know this works because I programmed it and accidently picked up a nail which caused a tire to start to leak down.

 

I have a May 13th, 2013 build date ST.

The Foglight one causes the Foglights to stay on with the highbeams, but I still have to manually press the button to turn them on.

 

Someone could have made a mistake to when telling about this mod. You program it to the same value that the 2014s are set to. Which retain the memory for foglights.

 

what BT/wifi/usb adapter is everyone using? i have the PLX BT adapter for my android that works well with Torque App but haven't tried using it yet with this? will this one work? i know that it has to have some spacific frequency or somthing to be able to read everything

 

Negative ghost rider. You should be fine using that adapter. All the regular readers seem able to connect to the highspeed CAN bus. That bus is all that you need to change the options in the Central Config.

 

So is there a page about what everyone is purchasing? Personally I prefer something like the VAGCOM setup I have now.

 

I still dont know what vagcom is.

 

 

I paid $450 about 6 years ago. I have actually used it on several vehicles OTHER than VW AG products. I loan it out to others that need it for their VW's. I am on the VAGCOM registry.

 

Wonder if it can access the hs/ms can on our fords?

 

Alright I need some help. I got an OBDLink MX wifi for Christmas this year, and am hoping to be able to do the global open/close, as well as change over the tire sensors to ditch the warning light. I'm using windows 8, have everything installed, and everything other than the Focccus app is working. I can use the OBDWiz software that comes with the MX without issue, however when I open the Focccus app, there are no port options at all. The only option there in the drop down menu is 'offline mode'. Firstly, will the MX wifi work with the app? If it will, how do I choose the port?

Thanks in advance!

 

I have absolutely no idea how the obdlink mx wifi works. But i have had issues with windows 8 and focccus before. I ended up rolling back to windows 7 to get things working... I cant say for sure that win7 will fix your issues. When the mx is connected to your pc what kind of connection is made?

Try to connect the mx to your pc, check device manager to ensure the mx is recognized. You will need to setup your computer to associate a com port when you are connected to your mx wifi. That way when you pair the 2 devices a com port is available for the connection. Open focccus and a com port SHOULD be available now.

 

Okay so I recently purchased a December 5 2014 build date ST1 and I am unable to get FoCCCus to work. The vbf files I need aren't on Ford's website and the newest version of FoCCCus is lacking them. Do I just need to wait or is there another option?

 

You dont need vbf files..i could have sworn i editted the vbf files thing out of the 1st post months ago.

The only way you might need them is if something is different about your ipc or bcm that focccus doesnt recognize..interesting... can you send me your VIN?

 

Weirdly enough but somehow Amazon now gets the post office to deliver on Sundays. This was just delivered.

Its a low profile OBD2 Y adapter. I should be able to leave my MX and my AP3 plugged in at the same time. Im not sure if they will interfere with each other yet.

 

They've been doing it here a lot too. I talked to the mailman once before and he said he doesn't mind it since he gets paid overtime.