2021+ F-150 FORScan List / Database / Spreadsheet

[Beaux]

Okay, try this again. Restore that IPC module to the backup you made before you wrote the values just to rule it out (hopefully you backed up the module before you made the change). Then make the changes as following and write to truck. Cycle off/on and it should work:

720-02-01 (IPC) in xxxx-xxEx-xxxx -> 720-02-01 (IPC) in xxxx-xx6x-xxxx

​

**Another way, if this doesn't work--go to IPC (non-asbuilt /easy way) and search for "chime", see if "key ignition" or similar shows up and changed from "enabled" to "disabled".

I have already tried both of those. This darn chime is annoying. Not as bad as the old double honk but it isn’t far.

Sponsored

 

[Nightshade]

I have already tried both of those. This darn chime is annoying. Not as bad as the old double honk but it isn’t far.

Yeah I know it’s annoying for sure; just weird it isn’t working for you. Maybe @antho and @Livnitup can help out here.

 

[Beaux]

Yeah I know it’s annoying for sure; just weird it isn’t working for you. Maybe @antho and @Livnitup can help out here.

I appreciate you trying to help me with it!

On a different note I need to quit playing around with it. When i would pull forward and get close to something the front camera would pop up with the proximity sensors. Now only the sensors show and I have to manually turn on the camera. I worked in different settings for about an hour with no luck.

 

[SilverPigeon]

I have already tried both of those. This darn chime is annoying. Not as bad as the old double honk but it isn’t far.

Another sanity check please: after making the IPC changes, did you reboot the IPC in FORScan service procedures?

 

[Beaux]

Yeah I know it’s annoying for sure; just weird it isn’t working for you. Maybe @antho and @Livnitup can help out here.

Another sanity check please: after making the IPC changes, did you reboot the IPC in FORScan service procedures?

It rebooted itself and then I cycled the truck off and back on again per the FORScan instructions. Or is there something different I need to do?

 

[SilverPigeon]

@Beaux, When I make an Ipc change, I also reboot it to be sure, it can't hurt to eliminate that as a possibility ?‍

 

[powerboatr]

It rebooted itself and then I cycled the truck off and back on again per the FORScan instructions. Or is there something different I need to do?

I have found dealing with IPC, sync etc
That when it says to turn off key, thrn back on so it completes a recycle to reboot, if it does not work the 1st time
Is to turn off key...open the door and let everything shut off to blank screen, leave forscsn alone,
Then shut door and turn key back on, let forscsn do it's thing.
For some reason. At times the system acts like it does not shut off or clear the old date.

 

[rugedraw]

I appreciate you trying to help me with it!

On a different note I need to quit playing around with it. When i would pull forward and get close to something the front camera would pop up with the proximity sensors. Now only the sensors show and I have to manually turn on the camera.

Check this value:

706-12-01

xxxx x8xx xx--

 

[Beaux]

Check this value:

706-12-01

xxxx x8xx xx--

That fixed the camera turning on! Thank you very much!!!

 

[dafuture]

Maybe a stupid question, but on something like the Disable Key-in ignition chime, I see the "*" where I'm supposed to change the value. However, there are two "--" in the third area. Am I supposed to delete those values if they're populated? Going off of this, row 33.

 

[Buyer2021]

Am I supposed to delete those values if they're populated?

Don't mess with the last two characters in the string at all.

Those characters are a 'checksum' value which will be automatically 'corrected' when you save your changes.

Remember it's always best practice to

1. Save a backup copy of your module data before making any changes
2. Refresh (reboot) the modified module after saving any changes
3. Look for and clear any DTCs after refreshing the module

 

[Nightshade]

Maybe a stupid question, but on something like the Disable Key-in ignition chime, I see the "*" where I'm supposed to change the value. However, there are two "--" in the third area. Am I supposed to delete those values if they're populated? Going off of this, row 33.

You only change where the asterisk (*) is, the (x) and the dashes (--) remain untouched to whatever you have in there and shouldn’t be changed at all.

 

[dafuture]

Don't mess with the last two characters in the string at all.

Those characters are a 'checksum' value which will be automatically 'corrected' when you save your changes.

Remember it's always best practice to

1. Save a backup copy of your module data before making any changes
2. Refresh (reboot) the modified module after saving any changes
3. Look for and clear any DTCs after refreshing the module

You only change where the asterisk (*) is, the (x) and the dashes (--) remain untouched to whatever you have in there and shouldn’t be changed at all.

Appreciate you both responding. I did save backups of everything before I started, and was doing a full stop/disconnect/power cycle after each change. I wasn't sure why the dashes were there, so I just left those modules alone for the time being. I'll go back to finish it tonight. Thanks for the help!

 

[A7mdoh]

Can anyone help me with the following?
How can I turn off the front Park lights/ marker lights ("the orange dots"). I want to only have the orange stripe in the headlights with no other orange lights.
I want it to be shown while driving.

 

[farmtruckman]

@SilverPigeon No luck mate, I tried changing it from 0 to 4 and then as a second attempt from 0 to C, reset the APIM by pressing the 2 buttons (power button and next track) but no luck.

APIM with change to 4:

APIM with change to C:

How the screen looks like after both attempted changes:

Circling back on this change I attempted a few weeks back. Any pointers?

Sponsored