2021+ F-150 FORScan List / Database / Spreadsheet

[im4seven]

Need help with the glare free lighting. 21 F150 lariat crew 502A (diesel if it matters) I have CCd but no on board scales, crew short box. Input all the codes in the modules, and all is fine until I get to the HCM. When I input that I get a headlight error message and it sets a head light fault. I'm using HCM 734-01-04 xx56 D1xx. The only thing I haven't done (I think) is reset the APIM after the chanes to the APIM. I dont see a way to do that in forscan. I did turn the truck off and on after making the changes. I made both changes then cycled the truck on and off. Thanks in advance for any insights or help anyone can offer!! I also work at a Ford dealership so would have access to the technicians diagnostic tools if needed.
Jim

APIM	7D0-09-01	x1xx	xxxx	xx--	reset APIM in FORScan after these changes
APIM	7D0-09-03	xxCx	xxxx	xx--
IPMA	706-01-01	xxxx	xxx9	xx--
SCCM	724-04-01	xxx4	xxxx	xx--
IPC	720-01-01	xx8x	xxxx	xx--
IPC	720-10-01	xxxx	xxx3	xx--
HCM	734-01-01	xxxx	xx01	xx--
HCM	734-01-02	x3xx	xxxx	xx--
HCM	734-01-04	xx53	4E--		* use this for short bed, no onboard scales / ccd
HCM	734-01-04	xx56	D1--		* use this for short bed with scales / ccd or Raptor
HCM	734-01-04	xxD9	88--		* use this for long bed no scales / ccd
HCM	734-01-04	xxDC	17--		* use this for long bed with scales / ccd

Sponsored

 

[Beaux]

Ok @ongrade Joe, this is the one that should do it:

7D0-09-05

xxxx

xx*x

xx--

Frunk Restricted Determination (FRD) • Lane Biasing (LB) • Key Detection Alert (KDA) • Running Board Control Function v2 (RBCF)

HOWEVER, my KDA is already set to 0 (disabled) and therefore I believe that this function is not being implemented on our APIMs. Happy to be proven wrong though ?

I’ll have to give this a shot one day. I absolutely hate this sound and have been unable to figure out how to disable it for almost a year now.

 

[MAXIMUS]

@MAXIMUS ,
Seatbelt warning market change which disables the chime of seatbelt not latched at ignition on time here:

Disable Ignition / Start Engine Chime Seatbelt Not Latched using SWM = ECE

IPC

720-01-02

xxxx x0--

xxxx x2--

i.e. If your initial value was 0, make it 2.

Thanks for the help @SilverPigeon

Unfortunately that didn’t work. Values are at 022F 90EB for 720-01-02

Any other suggestions? My seatbelt chimes are already disabled. Just want the annoying startup and door open chimes gone.

 

[SilverPigeon]

...Any other suggestions? My seatbelt chimes are already disabled. Just want the annoying startup and door open chimes gone.

Jason, gotcha. I've made my truck completely silent and it only now chimes with warnings I really need.
Tell me what your complete values are for:

IPC	720-01-01
IPC	720-01-02
IPC	720-02-01

?

 

[Kanuck]

Those chimes just might be part of the module self test startup.... hard coded into the module.

 

[SilverPigeon]

Those chimes just might be part of the module self test startup.... hard coded into the module.

Certainly possible Don, but the only time I get chimes now is for things I really need to take notice of (at my age?) like tailgate ajar. The only other chimes apart from them are when certain modules get reboots, BCM for example. I'm thinking a verification of settings and then a reboot of the IPC in service procedures.

 

[MAXIMUS]

Jason, gotcha. I've made my truck completely silent and it only now chimes with warnings I really need.
Tell me what your complete values are for:

IPC	720-01-01 2F0A 1004 F066
IPC	720-01-02 022F 90EB
IPC	720-02-01 4DE5 BF35 9EEE

?

This is what I got...thanks for the assistance too!

 

[SilverPigeon]

This is what I got...thanks for the assistance too!

Ok, you need changes. Changes in bold:
720-01-02 020F 92-- and
720-02-01 4D65 BF35 9E--

or the same changes showing only those that need changing:
720-01-02 xx0x x2-- and
720-02-01 xx6x xxxx xx--

IMPORTANT: Reboot the IPC in service procedures (spanner icon) after making these changes. You will lose MyView settings every time the IPC reboots but they're easy to re-do via steering wheel menu etc. See how that goes.

 

[MAXIMUS]

Ok, you need changes. Changes in bold:
720-01-02 020F 92-- and
720-02-01 4D65 BF35 9E--

or the same changes showing only those that need changing:
720-01-02 xx0x x2-- and
720-02-01 xx6x xxxx xx--

IMPORTANT: Reboot the IPC in service procedures (spanner icon) after making these changes. You will lose MyView settings every time the IPC reboots but they're easy to re-do via steering wheel menu etc. See how that goes.

I think that might have worked! Going on a drive this morning and will confirm…
Thank you.

 

[SilverPigeon]

I think that might have worked! Going on a drive this morning and will confirm…
Thank you.

I'm off to sleep so it'll be a while before I see the result, but post it asap anyway please.

 

[MAXIMUS]

I'm off to sleep so it'll be a while before I see the result, but post it asap anyway please.

Roger that. Much obliged!

 

[ongrade]

Ok @ongrade Joe, this is the one that should do it:

7D0-09-05

xxxx

xx*x

xx--

Frunk Restricted Determination (FRD) • Lane Biasing (LB) • Key Detection Alert (KDA) • Running Board Control Function v2 (RBCF)

HOWEVER, my KDA is already set to 0 (disabled) and therefore I believe that this function is not being implemented on our APIMs. Happy to be proven wrong though ?

Unfortunately you are right. Mine is at zero also. Guess I’ll have to search the sheets on Livinitup’s list to see if this hides elsewher.

 

[SilverPigeon]

@im4seven Jim, I'll look into it today. To reboot the APIM in FORScan, use the service procedures (spanner icon) - it's there. You can also hold down audio power and track forward hard buttons until the screen goes black to do a reboot without FORScan.

 

[SilverPigeon]

@svtzx2 Mark, I'll look into the DRL config for you today; it will require FORScan changes to be made but then you should have a DRL soft switch in the sync screen and you've already seen how the headlamp switch - DRL behaviour can work if you want that too.

 

[SilverPigeon]

@im4seven Jim, if you have the short bed, then your settings seem fine to me. I would advise the following:
1. Reboot all of the modules that are involved in this configuration change.
2. Reset DTCs to check for any still in existence. If there are any related to these modules screen shot the details so we can see what's up.
3. I note that GFHB has been reported to only work on '21 and '22 now. If that's true, it may be because of an OTA software update. If you've had any updates to these modules either by OTA or FDRS, it may be the issue for you as well.

Thats all I've got; failing all that maybe tag Livnitup to see if he can help, but try these first as he's a busy man.

Sponsored