Enabling charge speed on dash.

[bmwhitetx]

Interesting mod. Thanks for the write up. First time I’ve seen module reprogramming using Forscan detailed. I’m confused about the memory space related to putting a 2024 firmware on a 2022/2023 module. And how that is/was fixed.

@ZSC100 , I thought I knew all the acronyms. What goes EG stand for in F150 Lightning XLT SR EG 311A?

Sponsored

 

[PJnc284]

Compared the values for changes I made (glare-free, shutdown timer, seatbelt reminder, chime on startup, and door ajar) and all addresses and values appear to be the same between the regular and 2024 tab in the livinitup spreadsheet. May just try reverting those and see what happens.

 

[Ford Motor Company]

@Ford Motor Company

Care to chime in with a non-Ai and non-Soon timeline on when this update is going to be rolled out to older trucks?

I don't have an answer for you. But I will try and find one.

 

[RLXXI]

I thought I knew all the acronyms. What goes EG stand for in F150 Lightning XLT SR EG 311A?

Good question.

 

[Blochead21]

@bmwhitetx Stands for Equipment Group.

 

[ZSC100]

Compared the values for changes I made (glare-free, shutdown timer, seatbelt reminder, chime on startup, and door ajar) and all addresses and values appear to be the same between the regular and 2024 tab in the livnitup spreadsheet. May just try reverting those and see what happens.

The issue is that there is mismatch in the config memory structure, like the # of blocks needed to make a valid config. You can probably, save your IPC config, then just dump this config from a 2024 XLT into your IPC module and the DTC should go away:


Finally, once the DTC is gone, simply restore your old saved config, this will write all the config blocks you saved restoring your config and leave any new blocks from the 24's config unchanged and satisfying the valid config check.

Ultimately, use the 24' config map from Livnitup for any corrections you may need to make.

Report back here and let us know if this works: save-> load 24' config->restore saved config

 

[PJnc284]

The issue is that there is mismatch in the config memory structure, like the # of blocks needed to make a valid config. You can probably, save your IPC config, then just dump this config from a 2024 XLT into your IPC module and the DTC should go away:


Finally, once the DTC is gone, simply restore your old saved config, this will write all the config blocks you saved restoring your config and leave any new blocks from the 24's config unchanged and satisfying the valid config check. Pm'd Jesse as well to see if he had any ideas.

Ultimately, use the 24' config map from Livnitup for any corrections you may need to make.

Report back here and let us know if this works: save-> load 24' config->restore saved config

Well that got rid of the U2101 but gave a U0405. Restored the backup and back to the U2101. I have a 511A Lariat ER so think I'm going to look for a 24 Lariat with similar specs and pull the as built from ford. That should hopefully save me from having to manually change pretty much every block.

Code: U0405 - Invalid Data Received From Cruise Control Module

Additional Fault Symptom 56):
- Invalid/Incompatible Configuration

Status (-0A):
- DTC Present at Time of Request
- Malfunction Indicator Lamp is Off for this DTC

Module: Instrument Panel Control Module

 

[ZSC100]

Well that got rid of the U2101 but gave a U0405. Restored the backup and back to the U2101. I have a 511A Lariat ER so think I'm going to look for a 24 Lariat with similar specs and pull the as built from ford. That should hopefully save me from having to manually change pretty much every block.

Code: U0405 - Invalid Data Received From Cruise Control Module

Additional Fault Symptom 56):
- Invalid/Incompatible Configuration

Status (-0A):
- DTC Present at Time of Request
- Malfunction Indicator Lamp is Off for this DTC

Module: Instrument Panel Control Module

Ahhhh, yea, didn't know you had a Lariat, just grab a 24' AB from Ford with the same options and throw that onto your IPC and you'll be good.

 

[bmwhitetx]

@PJnc284 - I maintain a list of about 100 VINs (with As-Builts and Window Stickers) across all models and options that I use to double-check my Forscan mods page. DM me if you need a couple for your quest.

 

[PJnc284]

@PJnc284 - I maintain a list of about 100 VINs (with As-Builts and Window Stickers) across all models and options that I use to double-check my Forscan mods page. DM me if you need a couple for your quest.

Thanks. I managed to find one on cargurus that was close. I narrowed down the issue to the below 3 addresses. Top entry for each is 2024 AB and bottom is my previous IPC values. Changing any of them results in the incompatible configuration. Now to go poke around livinitup's spreadsheet. edit: looks like all of those are seatbelt related. I already disabled the chime 720-01-01 so not sure if it's related or not.

 

[bmwhitetx]

Good luck. FWIW, your top row Data1-Data3 is consistent with values I see for 24-25 Lariats. And the bottom row is the same as 22-23 Lariats.

 

[Jesse-Infotainment]

2101 is due to the lower portion seatbelt config. You can load a complete 24 IPC as build file and write it.. it will clear the 2101..

here is an as build you can use

2024_IPC.ab

 

[PJnc284]

2101 is due to the lower portion seatbelt config. You can load a complete 24 IPC as build file and write it.. it will clear the 2101..

here is an as build you can use

2024_IPC.ab

yeah I managed to find a 24 Lariat online and pulled the as-built from the motorcraft site to load. Problem came when I tried to restore my config as it would restore those 720-12 and 720-13s and kick out that 2101 code. Managed to narrow down the issue to those by manually updating the different blocks. Below is what I ended up changing from the 2024 ab. Some due to Forscan mods , some due to my specific truck config (e.g. power running boards, etc), and others that are above my paygrade. My truck is a 2023 ER Lariat 511A with trailer brake, power running boards and max tow so others trying may require different changes but seems you should be good to restore a backup as long as you change the 720-12 and 720-13 back to match the 2024 as built.

	Module Address	Data1	Data2	Data3
2024	720-01-01	0F0A	106C	F0AE
2024-modified	720-01-01	078A	1004	F4C2
		7- shutdown timer, 8- glarefree	xx0x seatbelt chime
2024	720-01-02	022F	80DB
2024-modified	720-01-02	020F	82BD
		xx0x- door ajar	2-startup chime
2024	720-02-01	4DE5	3905	4EE8
2024-modified	720-02-01	4DE5	BF35	4E9E
2024	720-03-01	E000	0000	000B
2024-modified	720-03-01	E500	0000	0010
2024	720-04-01	2000	0102	0150
2024-modified	720-04-01	2400	0102	0154
2024	720-07-01	8401	8AA0	401E
2024-modified	720-07-01	8409	8AA0	2006
				2- quickboot
2024	720-09-01	7062	1554	9905
2024-modified	720-09-01	F062	15D4	9905
2024	720-10-01	1B08	0021	007C
2024-modified	720-10-01	1B08	0023	007E
			3- glarefree
2024	720-11-01	C424	0400	1035
2024-modified	720-11-01	C524	0420	286E
2024	720-11-02	0080	00BA
2024-modified	720-11-02	0403	0041
2024	720-12-01	22C0	0000	001C
2024-modified	720-12-01	2AC0	0000	0024
2024	720-12-02	2000	80DB
2024-modified	720-12-02	0000	003B

 

[digitaldad]

Luvin' the nerd stuff!

Question: if you upgrade the IPC on a '23, to '24 as this example shows, does one then need to always follow (remember, going forward) the specific/if any '24 guidance on future IPC changes when performing a different mod (within that module)?

 

[ZSC100]

Luvin' the nerd stuff!

Question: if you upgrade the IPC on a '23, to '24 as this example shows, does one then need to always follow (remember, going forward) the specific/if any '24 guidance on future IPC changes when performing a different mod (within that module)?

Yes, if you are using 24' firmware in your IPC then your module configuration has to follow the 24' config scheme.

Sponsored