ForScan

[windguy]

13 hours ago, Don Ridley said:

Your experience is normal.

1. Your battery is near the end of its lifetime. My 2016 shows 30% life left in the battery monitoring system (a feature on the 1.6l Ecoboost).

2. The DRLs and "run" position when using Forscan puts a big load on the battery.

3. Now I ALWAYS use a battery charger when making changes using Forscan. When the vehicle was new I got away without using one.

4. Reading data and DTCs don't require any battery backup/protection.

 

Thanks Don - appreciate the quick reply and info. Your confirmation gave me the confidence to continue exploring but with the battery charger connected going forward.

I had a better session today and saved the BCM and IPC as-built configurations as a starting point before I make any changes. Also took a screen shot so I could save it in readable text format.

 

I've got a question regarding what Forscan shows in the as-built config versus what Motorcraft was showing for the IPC Module. Below is screenshot of both.

In comparison, Forscan doesn't show all the registers but does show a few extra ones in the upper range (720-24-01 and 720-25-01) that didn't show up on the Motorcraft site. Wonder why?

 

Also, what are the Restore and Write boxes to the right of several of the registers? I'm assuming those are the only ones that Forscan will allow you to change.

Thanks!

 

 

 

 

[windguy]

6 hours ago, desert_connect said:

Approach lights "disabled" and the lights still come on.

 

The whole story;  

1) Took it to a Ford dealer a year ago. They claimed they updated the BCM and turned the approach lights off, but the lights were still on. The service manager tried to charge me for it with some double talk but when I told him I knew they'd get paid for the update by Ford then he backed off (free).

 

2) Second dealer last December was happy to check it out for me since I bought the van through one of their area stores. They confirmed the first dealer did in fact update the BCM but were unable to turn off the approach lights.

 

3) Today......I purchased a used laptop (windows) from a fellow TC owner on this forum and the Forscan adaptor from Amazon. After a bit of time lost linking the extended license to the Forscan I hooked it up to my van. The found the approach lights were "disabled". I cycled through "enabled" and "disabled" 3 times leaving them "disabled" and the approach lights are still ON. This frustrates me to no end. The only permanent solution I know of at this point is the get rid of the van.  

 

 

Thanks for the update. Sorry to hear that. I'm was ready to follow Hollenback's procedure to check out my BCM config to see what's going on with the approach lights. My scenario is identical to yours with two different dealer visits (twice per for a total of four attempts) and promises in both cases that the BCM was updated. It's very interesting that you still are not able to get this change to stick. I fear I won't we able to change the setting as well but I'll still try.

I think Donuts is right in that your BCM wasn't actually updated. Ford ETIS never showed it was for my van. I can't remember if you mentioned yours changed in ETIS. This discussion was in the "approach light" thread and it's been a while. So how do you check the BCM software version in Forscan and verify that the SSM update was done?  "reprogram the BCM to the latest calibration using IDS release 103.05 and higher".

 

Below is a screen shot that shows the BCM As-built config.

My van shows BCM Calibration DV6T-14C095-BH.

Maybe other Forscan users can check their BCM config and report back along with the build date of their van.

 

 

 

[jrm223]

Ford ETIS never showed any change for my BCM after I had Ford update it & turn off the approach lights, so I don't think that will be a reliable way to verify the BCM update. My approach lights are definitely off, so the BCM was updated, lol. As for the battery issue, I had to get mine replaced a few weeks ago, even before the 4 years anniversary of me buying the van; but, it had 102K miles at time of replacement and the battery was going bad for a few weeks, problems started at about 98-99K miles or so for me. I can probably hook up my laptop tonight to read my BCM parameters, after I reinstall Forscan since I had to blow-out/reset my whole laptop due to various issues. 

[Don Ridley]

The WRITE button is used to make changes to hex data in that register. I have not used the RESTORE function.

 

I don't know why the as built data does not exactly match the Forscan data.

 

You can change individual hex bits in the IPC, ACM but not the BCM. All BCM changes will be done using the menu selections. There are configurations in the central configuration that we can't see and can only be changed by the functions built into the menus.

 

Save a copy of every module. A mistake in one may propogate into others.

 

There are many tutorials. This one is for the F-150 and explains how to change individual hex bits.

 

FORScan Tutorial.pdf

[windguy]

1 hour ago, Don Ridley said:

The WRITE button is used to make changes to hex data in that register. I have not used the RESTORE function.

 

I don't know why the as built data does not exactly match the Forscan data.

 

You can change individual hex bits in the IPC, ACM but not the BCM. All BCM changes will be done using the menu selections. There are configurations in the central configuration that we can't see and can only be changed by the functions built into the menus.

 

Save a copy of every module. A mistake in one may propogate into others.

 

There are many tutorials. This one is for the F-150 and explains how to change individual hex bits.

 

FORScan Tutorial.pdf

 

Thanks for the info Don. Very helpful to know.

I will save the as-built data for all modules to have as a baseline. That may save my bacon one day. Appreciate the tip.

Will check out the tutorial you linked in. Appreciate the help as always!

 

[windguy]

1 hour ago, jrm223 said:

Ford ETIS never showed any change for my BCM after I had Ford update it & turn off the approach lights, so I don't think that will be a reliable way to verify the BCM update. My approach lights are definitely off, so the BCM was updated, lol. As for the battery issue, I had to get mine replaced a few weeks ago, even before the 4 years anniversary of me buying the van; but, it had 102K miles at time of replacement and the battery was going bad for a few weeks, problems started at about 98-99K miles or so for me. I can probably hook up my laptop tonight to read my BCM parameters, after I reinstall Forscan since I had to blow-out/reset my whole laptop due to various issues. 

 

Thanks for the input. I remember one poster saying his BCM software changed in ETIS after having the dealer make the update so I guess it's not a reliable indicator.

 

That would be cool if you can report back about your BCM module config. Maybe we'll learn something. Good luck getting your laptop back online.

 

Curious, when was your van built? Sounds like mid 2015. My 2015 was built in October 2014.

 

Regarding your battery, that's interesting. About the same age but many more miles for your van. I realize this is the Forscan thread, but did you have the Ford dealer install an OEM battery? I've taken the plastic battery cover off before but not with the thought of how to replace the battery. When I setup the battery charger, I realized what was discussed on other battery threads in that the battery is a pain in the butt to remove. It's really tucked under the cowling to where you can't even access the ground terminal. If the cost differential is minimal I'll probably opt to have Ford take care of it to save myself the frustration and skin on my knuckles.

[Double Nickels]

For the battery, you will need to remove the air filter box, the power supply fuse box, battery tray cover, and disconnect the ground from the body.  

[PhotoAl]

Fun!! I just replaced the battery in my daughters 2008 VW Rabbit.  Battery box cover, disconnect air inlet tube from MAF sensor, unplug MAF sensor, remove engine cover, unbolt battery, undo terminals and lift out.  Did the wife's Smart car a couple of months ago, it lives under the passengers feet.  Not super difficult to get to but very difficult mauuvering a battery into position while laying one my side in across the seats with arms extended.  Battery in my Volt - well it will go back to the dealer.

 

MY TC lives in a garage which hopefully will extend the life of the battery.  

Edited June 25, 2019 by PhotoAl

[jrm223]

I did have Ford put in an OEM battery, plus trans flush & oil change. I was going to have them do my front struts, but my extended warranty expired at 100K and the van was just over 102K when it rolled in there, so I ended up doing struts myself. Ford wanted $855 on struts and $350 on rear brakes, plus tax. Battery was $170 + tax, total bill was about $480 with the trans flush and oil change.

 

Here's a pic of the BCM specs. I don't recall offhand when my van was built, I think maybe March 2015? I'll have to look again later. 

 

 

[desert_connect]

On 6/25/2019 at 12:16 AM, windguy said:

 

Thanks for the update. Sorry to hear that. I'm was ready to follow Hollenback's procedure to check out my BCM config to see what's going on with the approach lights. My scenario is identical to yours with two different dealer visits (twice per for a total of four attempts) and promises in both cases that the BCM was updated. It's very interesting that you still are not able to get this change to stick. I fear I won't we able to change the setting as well but I'll still try.

I think Donuts is right in that your BCM wasn't actually updated. Ford ETIS never showed it was for my van. I can't remember if you mentioned yours changed in ETIS. This discussion was in the "approach light" thread and it's been a while. So how do you check the BCM software version in Forscan and verify that the SSM update was done?  "reprogram the BCM to the latest calibration using IDS release 103.05 and higher".

 

Below is a screen shot that shows the BCM As-built config.

My van shows BCM Calibration DV6T-14C095-BH.

Maybe other Forscan users can check their BCM config and report back along with the build date of their van.

 

 

 

 

On 6/24/2019 at 8:12 PM, donuts said:

I'd bet the dealer service people didn't actually update the BCM like they say they did.

 

 

Thanks everyone.

Here are my currant BCM codes.........I'll have to take the time to compare with others.

Edited June 27, 2019 by desert_connect

[Don Ridley]

Your BCM has been updated. The GV6T calibration is newer firmware.

 

I assume you are changing the menu selection in Forscan and saving it. Then clearing DTCs. If the lights still turn on then I am stumped. A long shot is to check the instrument cluster menus. Maybe the change added a menu item to control the approach lights (this is a wild guess and I have not heard of this anywhere else).

 

 

[desert_connect]

30 minutes ago, Don Ridley said:

Your BCM has been updated. The GV6T calibration is newer firmware.

 

I assume you are changing the menu selection in Forscan and saving it. Then clearing DTCs. If the lights still turn on then I am stumped. A long shot is to check the instrument cluster menus. Maybe the change added a menu item to control the approach lights (this is a wild guess and I have not heard of this anywhere else).

 

 

Thanks Don.

Yes, it appears to be the later version. With a clear mind I need to go back through the procedure to make certain that I followed all the steps correctly. 

[Don Ridley]

If you followed to the tutorial by phollenbeck, you may want to try configuring dark mode but going directly into the Bdycm main module. This tutorial explains how to do this

https://drive.google.com/file/d/1OHaBAxllW1yYgEAEKmGTh28Z6iro6BU0/view?usp=drivesdk

Look for approach light (if it is there) and change the setting. 

[windguy]

@jrm223 - thanks for posting your repair details. Good to get a price point on the battery change when the time comes (soon I expect).

Also thanks for posting your BCM Configuration. Not sure what to make of that other than it's different than mine and we both have a 2015, yours being a few months newer.

 

@desert_connect - thanks for posting your BCM Configuration. Closer to what jrm223 has but hard to know for sure what to make of it.

What is the mfg date of your 2017 van? Per SSM 46321, if it's after December 11, 2016, then the BCM Calibration update wasn't required.

Don't think we have enough data to figure out what the calibration versions mean with respect to the APPROACH LIGHT parameter.

 

I went into my BCM today to check the APPROACH LIGHT setting. It was already set to DISABLE. I set it to ENABLE and the back to DISABLE. I  followed Hollenback's procedure, which is a great tutorial and spot on in what you need to do. I didn't see any change with the exterior lights. If I open a door, the front/tail lights come on and stay on. If I close the doors, the lights go off right away, no delay. I was always under the impression that without the updated calibration, the APPROACH LIGHT feature wasn't even available. That's probably not true but would need another poster that hasn't had their van into Ford for the BCM Calibration update to check their BCM Configuration. I think at this point I'm giving up on this effort unless some new data comes along. I'm not sure Ford implemented the change for what we are looking for in earlier model year and compatible calibration files. That part is a big mystery that Ford can't seem to help with at a dealer level.

 

@Don Ridley - I had taken screen grabs of the BCM Central Configuration. Lots of data there but I don't see anything that pertains to APPROACH LIGHTS, unless it's hiding within another setting. Thanks for posting the bambi mode tutorial, interesting. Below is the concatenated screen grabs. Hope it's readable.

 

Edited June 28, 2019 by windguy

[Don Ridley]

One explanation why Forscan isn't working may be that Forscan determines which options and functions are available based on the VIN or model year. Updating a module won't turn on the new functions in Forscan. I have sent Forscan an email. Let's see if they respond.

 

My TC has the BCM calibration that doesn't support dark mode so I can't test anything.

 

 

 

 

Edited June 28, 2019 by Don Ridley

[windguy]

3 hours ago, Don Ridley said:

One explanation why Forscan isn't working may be that Forscan determines which options and functions are available based on the VIN or model year. Updating a module won't turn on the new functions in Forscan. I have sent Forscan an email. Let's see if they respond.

 

My TC has the BCM calibration that doesn't support dark mode so I can't test anything.

 

 

 

 

 

Don - Thanks for contacting Forscan.

 

I'm kind of curious what exactly happens when you go to BCM Central Main and Forscan connects to the internet and downloads files.

The screen showed that five or six Blocks were loaded. The APPROACH LIGHTS were in Block #1.

 

Curious, did you go into your BCM config and not see the APPROACH LIGHTS option?

Thanks!

 

 

[Don Ridley]

Here was the response from Forscan:

Hello,

FORScan recognizes vehicle by PCM strategy number. If you want FORScan work correctly with your new BCM, you need to remove vehicle profile after the replacement. More info:

https://forscan.org/forum/viewtopic.php?f=5&t=9196

As for new options availability, please provide more details.

 

If" PCM" is not a typo, maybe this is the problem. The PCM strategy may not be as up to date as the BCM. You don't need to update the vehicle profile if you connected to Forscan for the first time after the BCM update. Bottom line is we can't get dark mode to work on some vehicles. You guys can try contacting Forscan if you want to troubleshoot this. They would need specifics on your configuration, logs etc..

contact@forscan.org

 

 

[windguy]

@Don Ridley - thanks for posting the update.

Interesting read on why and when to update your vehicle profile.

After you updated your IPC, did you create a new profile?

 

[Don Ridley]

Yes. But I don't think it matters for the IPC because no new features or functions were added with the new baby unit.

[Don Ridley]

13 hours ago, windguy said:

Curious, did you go into your BCM config and not see the APPROACH LIGHTS option?

Thanks!

Yes, Forscan shows the option to enable/disable approach lights but my BCM calibration does not support this function.

[windguy]

4 hours ago, Don Ridley said:

Yes. But I don't think it matters for the IPC because no new features or functions were added with the new baby unit.

 

okay, thanks Don.

[windguy]

8 minutes ago, Don Ridley said:

Yes, Forscan shows the option to enable/disable approach lights but my BCM calibration does not support this function.

 

okay, thanks Don. Good to know that the option shows up regardless of the calibration version.

I'm assuming at this point that my BCM was never updated correctly by either dealer and multiple techs trying.

I still wonder if the BCM was updated correctly in my 2015 if the approach light function can be toggled using Forscan.

[KevinRollin]

Anyone using ForScan wirelessly, via Bluetooth or WiFi on an iOS or android device?  

 

No laptop, I do all my internet surfing on my phone or iPad.  

 

Eyeing this adapter:  https://www.amazon.com/OHP-Forscan-Adapter-Scanner-Android/dp/B06XJL31Z7

or this one:  https://www.amazon.com/dp/B07JFRFJG6

 

Edited August 12, 2019 by KevinRollin
Added second adapter.

[mrtn]

Mine's this or very similar:

https://www.amazon.com/Mestart-OBDII-OBD2-Bluetooth-Car/dp/B01HXGX8V6/ref=mp_s_a_1_4?keywords=elm327+bluetooth+obd2&qid=1565598457&s=gateway&sprefix=elm327&sr=8-4

 

Android over Bluetooth.

IOS requires Wifi AFAIK, BT won't work.

[jrm223]

I recall the smartphone version being much more limited in capability than the PC version, basically a custom gauge panel on the phone, so you ought to check into that before buying anything. They may have expanded the smartphone capabilities in more recent versions of Forscan, I don't know because it's been a long while since I looked at that.