Proclam

I tried searching, but couldn't come with any answers. Did anyone ever figure out the approach settings? I've tried multiple attempts to no avail. It'd be a nice feature to get active :/

Gordy49913

Itsakeeper

Did forscan ever become available as an app for android?
Did some searching but I don't see that here.

Gordy49913

If you didn't see at Forscan.org, it isn't going to be anywhere else.

ikanode

----------------------------


Thanks for confirming the expected behavior. I suspect my problem is the coincident timing of two unrelated issues. This afternoon, I couldn't get the truck to recognize the trailer with several attempts. After rapidly plugging/unplugging a dozen times in a row, the trailer was finally recognized. I'm guessing corrosion on the plug, I'll use contact cleaner tomorrow. (Even though I've towed several hundred miles over several occasions in the last two weeks with no problems.)

I restored the BCM to factory settings. After I got the truck to recognize the trailer, use of the turn signals gave rapid flashes in the cabin. Then I changed:
726-27-02 xxxx x*xx xxxx Trailer outage: 1=outage, 0=no outage
to 0. Still got rapid flashes.

I then changed:
726-27-02 xxxx xxxx x*xx Rear bulb turn outage cfg: 1=outage, 0=no outage
to 0 and the flashes went away and in 15 minutes of playing with the turns off and on. I didn't get any reported problems.

Maybe the prior "Trailer Disconnect" and the "Turn Signal warning" were both due to a corroded trailer plug. There wasn't any buildup in it, just discoloration.

I should mention that my 2019 F150 has what I realized today are Factory installed LEDs--most, if not all the way around. That may account for my non-standard behavior.
JDAAS TAILLAMPS - LED WITH BLIS

JBBA7 HEADLAMPS - FIXED DSS (LED)
JBKAK FRONT FOG LAMPS-LED
JDDAG LED HI STP LMP W/CARGO LIGHT

If I get time before my trip, I'll change "Trailer Disconnect" back to the factory setting and see if changing "Rear Bulb Turn Outage" is enough by itself to work for me.

Treat the above as a preliminary finding that I need to confirm.

Airborne_Ape

ForScan is available for Android OS 4 and later. The is link here; however, nearly everything discussed in these forums is something it's not capable of. The android version is really only meant for reading DTC's and light troubleshooting purposes which is why nobody here ever mentions it.

Airborne_Ape

A module reset in ForScan forces all the relays off then back on within the selected module and is usually needed to re-establish CAN bus communication between your IPC, BCM, PAM and ACM after messing with backup sensor chime settings. Without the modules talking to each other over the vehicle network the IPC handles the reverse chime audio through its board-soldered speaker rather than pass the audio through to the stereo amp system / ACM (audio control module).

Try a module reset in the wrench icon tab in ForScan for the BCM, IPC, ACM and PAM. It may resolve your issue. Here's a screen shot of which menu to look for:

Note: It is normal for lots of errors to appear and lights to flash when resetting these modules whereas your literally switching live sensor and lamp circuits on and off. You will hear the relays switch. All faults automatically clear after a few seconds. I reset modules like this all the time, it's a good first-step when troubleshooting complications which stem from ForScan related errors.

Airborne_Ape

1) Ford has to nerf their vehicles so that stupid people can't sue them.

Double honk specifically is in place to alert seniors that their car is still running when it's not turned off. Seniors don't understand the TV remote let alone push button start. A Lincoln MKX owner lost his wife and sued Ford and won before the age of double honk because the new eco boost engine was too quiet for their poor hearing and there was no horn honk warning to alert them that their new car was running after parking it in the garage for the night.

This isn't just a one off either. Lots of Americans sued lots of car makers for the same reason as explained in this article:

https://www.nytimes.com/2018/05/13/b...xide-toll.html

2) Some other configurations are disabled because they don't make sense or bring continuity to the model and brand aesthetics.

Example A: since there is no option to turn the rear heated seats on through the Sync 3 screen for those who have the option equipped, Ford simply chose to disable the home screen heated seat buttons on all F150's for brand continuity.

Example B: Rear window modules don't exist in the F150 so ability for global windows (rolling them up or down with your FOB) is disabled for the same reason that third row power folding seats are.

3) Some configurations are mandated by state or federal law makers such as forced DRL configurations and should not be user or dealer configured. If Ford had to create a custom module for each market and tire size their cost would be astronomical.It's much easier for Ford to dictate these functions via programable logic controllers.

Wicked ace

UUmmmm....Look under my moniker...no need to be pejorative. That being said, I resemble that remark.
On another note. A recall on my Grand Cherokee had to with a software update because millennials couldn't remember to put it in park before getting out of the vehicle.

tjm623