FORScan - software to enable/disable features in your truck
08-26-2018, 08:25 PM
It's my first day
Originally Posted by tmcolegr
Over the last few weeks, I've had issues with FORScan not being able to find and connect to all of the modules. When this would occur, I would simply disconnect FORScan, start a new session, and on the next attempt, FORScan would find all of the modules.
Yesterday while enabling TPMS Specified Value Displayed in the IPC on one of our 2016 F150s, while FORScan was writing the new value when the writing process reached 50%, I received the message "Service Procedure Interrupted". I had to disconnect, start a new session and this time FORScan found all of the modules and successfully wrote the new value to the IPC.
Today no matter how many times I started a new session with FORScan, all modules could not be found and FORScan was unable to read any DTCs. I restarted the laptop but the results were the same.
I have an OHP ELM327 USB adapter, so I decided to give this adapter a try. I was able to connect to all modules, write to the IPC and save the new AsBuilt configuration without any issues.
Has anyone else experienced this type of issue using the OBDLink MX Bluetooth Adapter?
Yesterday while enabling TPMS Specified Value Displayed in the IPC on one of our 2016 F150s, while FORScan was writing the new value when the writing process reached 50%, I received the message "Service Procedure Interrupted". I had to disconnect, start a new session and this time FORScan found all of the modules and successfully wrote the new value to the IPC.
Today no matter how many times I started a new session with FORScan, all modules could not be found and FORScan was unable to read any DTCs. I restarted the laptop but the results were the same.
I have an OHP ELM327 USB adapter, so I decided to give this adapter a try. I was able to connect to all modules, write to the IPC and save the new AsBuilt configuration without any issues.
Has anyone else experienced this type of issue using the OBDLink MX Bluetooth Adapter?
I confirmed it had nothing to do with the OS or laptop in both of my cases, but that's not to say they may be factors for you. Sometimes I found that if Windows was waiting to restart to install and update it would cause that type of issue. So, check your computer to see if that's what's going on.
There are other users with similar experiences on the ForScan.org forum. The OBD MX BT seems to have a limited lifespan and I'm not sure what chip or component is responsible. It seems to affect heavy users, so I suspect it is related to constant connections / disconnections and may be a bad rectifier or weakening diodes on the board.
The second time around was the final straw for me and that's when I opted to spend extra on a good hardwired solution.
I'd bet it is your OBD MX BT and not the computer or its OS. Check if it still has warranty left. ScanTool has pretty good customer service for warranty replacement from my experience.
I still recommend the OBD MX Bluetooth but only to light users. In my opinion it is a better than any ELM27 around and a good beginner option.
Last edited by Airborne_Ape; 08-26-2018 at 08:45 PM.
08-27-2018, 04:39 AM
Back in this thread you'll read I had identical issues in the Fall and Winter of 2017. I tried the OBD MX BT firmware update from ScanTool which didn't help, driver roll backs (because Windows 10 forces auto updates) which didn't help, swapped bluetooth radios on my laptop which didn't help and after two weeks of having the exact same finicky experience the OBD MX BT finally completely died. In fact, I had that happen twice in the last 3 years.
I confirmed it had nothing to do with the OS or laptop in both of my cases, but that's not to say they may be factors for you. Sometimes I found that if Windows was waiting to restart to install and update it would cause that type of issue. So, check your computer to see if that's what's going on.
There are other users with similar experiences on the ForScan.org forum. The OBD MX BT seems to have a limited lifespan and I'm not sure what chip or component is responsible. It seems to affect heavy users, so I suspect it is related to constant connections / disconnections and may be a bad rectifier or weakening diodes on the board.
The second time around was the final straw for me and that's when I opted to spend extra on a good hardwired solution.
I'd bet it is your OBD MX BT and not the computer or its OS. Check if it still has warranty left. ScanTool has pretty good customer service for warranty replacement from my experience.
I still recommend the OBD MX Bluetooth but only to light users. In my opinion it is a better than any ELM27 around and a good beginner option.
I confirmed it had nothing to do with the OS or laptop in both of my cases, but that's not to say they may be factors for you. Sometimes I found that if Windows was waiting to restart to install and update it would cause that type of issue. So, check your computer to see if that's what's going on.
There are other users with similar experiences on the ForScan.org forum. The OBD MX BT seems to have a limited lifespan and I'm not sure what chip or component is responsible. It seems to affect heavy users, so I suspect it is related to constant connections / disconnections and may be a bad rectifier or weakening diodes on the board.
The second time around was the final straw for me and that's when I opted to spend extra on a good hardwired solution.
I'd bet it is your OBD MX BT and not the computer or its OS. Check if it still has warranty left. ScanTool has pretty good customer service for warranty replacement from my experience.
I still recommend the OBD MX Bluetooth but only to light users. In my opinion it is a better than any ELM27 around and a good beginner option.
Concerning heavy use, I probably connect to between 20 to 30 vehicles per week and have done so for at least 1.5 years with this same OBDLink MX Bluetooth adapter. This is the first time I have experienced this issue.
Since switching to the OHP ELM USB adapter I have connected to 6 different 2015 thru 2018 F150s, all without any issues.
After this experience, I don't plan on using the OBDLink MX Bluetooth adapter anymore.
Last edited by tmcolegr; 08-27-2018 at 05:28 AM.
08-27-2018, 08:23 AM
Senior Member
Can anyone that has enabled the backup camera on the 4.2" radio tell me if the lights on the buttons stopped working afterwards.
I can enable the camera and it works fine but then the radio buttons won't light up. If I disable it they work again.
EDIT: The only value I changed is the FCDIM 7A5-01-01 x2xx-xxxx-xxxx
I can enable the camera and it works fine but then the radio buttons won't light up. If I disable it they work again.
EDIT: The only value I changed is the FCDIM 7A5-01-01 x2xx-xxxx-xxxx
08-27-2018, 08:53 AM
American member
Or, have you had trouble with it from the start?
I suppose in my own ignorance, I shouldn't assume because I didn't need to use the drivers, that you don't need to either.
If the video doesn't work send me a picture of the box and the instructions just to be sure we're on the same page,
08-27-2018, 10:17 AM
Junior Member
Join Date: Aug 2018
Posts: 4
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for the help! Looks like I need to change BCM 726-39-02 xxxx-x1xx-xxxx
Last edited by Alejandro Garza; 08-27-2018 at 10:41 AM.
08-27-2018, 10:47 AM
08-27-2018, 01:23 PM
This thread is awesome, and a big thanks to all of you guys who have already done the research and experimented! My adapter arrives today, and I've got Forscan with license installed on my PC. That being said, I'm still confused (even after a bunch of searching) about one thing with regards to making changes to DRL settings. Bear in mind I've got a 2018 XLT 302A with factory halogens. I simply want to change my current low beam DRLs over to the parking lights. Can this be done?
What I see in the spreadsheet is "DRL - Parking Lights only (stock LEDs only)" which I take to mean that it only will work on the factory LEDs, and I also see "DRL - Turns only (Halogen/aftermarket lights only)" which appears to apply to factory halogens. Is there an option for parking lights only for the halogens, or is there something with the design that will not allow it to work?
Thanks for the help, and I apologize if this has been asked a bunch of times already!
What I see in the spreadsheet is "DRL - Parking Lights only (stock LEDs only)" which I take to mean that it only will work on the factory LEDs, and I also see "DRL - Turns only (Halogen/aftermarket lights only)" which appears to apply to factory halogens. Is there an option for parking lights only for the halogens, or is there something with the design that will not allow it to work?
Thanks for the help, and I apologize if this has been asked a bunch of times already!
08-27-2018, 02:00 PM
The FORScan Guy
Thread Starter
This thread is awesome, and a big thanks to all of you guys who have already done the research and experimented! My adapter arrives today, and I've got Forscan with license installed on my PC. That being said, I'm still confused (even after a bunch of searching) about one thing with regards to making changes to DRL settings. Bear in mind I've got a 2018 XLT 302A with factory halogens. I simply want to change my current low beam DRLs over to the parking lights. Can this be done?
What I see in the spreadsheet is "DRL - Parking Lights only (stock LEDs only)" which I take to mean that it only will work on the factory LEDs, and I also see "DRL - Turns only (Halogen/aftermarket lights only)" which appears to apply to factory halogens. Is there an option for parking lights only for the halogens, or is there something with the design that will not allow it to work?
Thanks for the help, and I apologize if this has been asked a bunch of times already!
What I see in the spreadsheet is "DRL - Parking Lights only (stock LEDs only)" which I take to mean that it only will work on the factory LEDs, and I also see "DRL - Turns only (Halogen/aftermarket lights only)" which appears to apply to factory halogens. Is there an option for parking lights only for the halogens, or is there something with the design that will not allow it to work?
Thanks for the help, and I apologize if this has been asked a bunch of times already!
08-27-2018, 03:36 PM
EQ Settings:
I have replaced the factory speakers and flattened the EQ with Forscan, but now the volume is really high. I can't get past volume 5 without blowing my ears out when I used to listen comfortably around 9-10, and the difference between each volume level is much larger. Is there a different EQ setting I need or anyone have any adivce?
I have replaced the factory speakers and flattened the EQ with Forscan, but now the volume is really high. I can't get past volume 5 without blowing my ears out when I used to listen comfortably around 9-10, and the difference between each volume level is much larger. Is there a different EQ setting I need or anyone have any adivce?
08-27-2018, 03:39 PM
The FORScan Guy
Thread Starter