Need help programming HVAC module
But as you know, the F150 spreadsheets do not always work on the Super duty but this is where I would look for configuration clues.
Good luck. These types of projects can be fun.
The system is sensitive to post cadence as well, so attempting to post multiple times quickly to reach a minimum post count can backfire.
You're doing nothing wrong. But the rest of the world does an unbelievable amount of wrong, and we are constantly having to come up with ways to counteract it.
Carry on!
The system is sensitive to post cadence as well, so attempting to post multiple times quickly to reach a minimum post count can backfire.
You're doing nothing wrong. But the rest of the world does an unbelievable amount of wrong, and we are constantly having to come up with ways to counteract it.
Carry on!
Carrying on.
But as you know, the F150 spreadsheets do not always work on the Super duty but this is where I would look for configuration clues.
Good luck. These types of projects can be fun.
I'm really hopeful the OP's Ford engineer contact can shed some light on this. I've actually opened up both modules and aside from an additional LCD interface chip, two ZIF sockets (for the ribbon cables to the **** LCDs) and some additional resistors for said chip and sockets, the boards appear identical, right down to the P/N of the CPU.
You gave me an idea, though... I may bounce over to the F150gen14 forum and see if someone with a 2021 F-150 Platinum would be willing to post their plain English HVAC values. I'd like to see if the list is as long as it is for the F-350. If so, maybe I can get someone to temporarily write the F-350 plain English values on their F-150 and export the HEX code for us.
https://www.f150gen14.com/forum/thre...d-*****.35094/
So regardless of the plain English menus, you are still just looking for the proper as built data. It's complicated because I have made changes to as built data with no noticeable affect. I have also loaded as built files that had many differences into an IPC and the module appeared to operate the same.
I think you have found a solution but you definitely need to thoroughly test. Unexpected operation like not sleeping and draining the battery are possible.
Ford Trucks for Ford Truck Enthusiasts
If I can cross-reference these with the plain English settings on the Super Duty's as-builts, I may be able to come up with a custom HEX set for the 19980-K in the Super Duty.
The plain English settings won't line up, as it appears the Super Duty module has the locations for some HEX data in different locations than the F-150.
Here are the F-150 as-builts to replace what I posted earlier in the thread. These have no modifications to them - they are straight from an F-150 running the 19980-K module:
Last edited by dspa; Mar 23, 2025 at 07:25 PM.
I loaded the F-150 as-builts into the 19980-K module and went section by section in the as-builts, writing one line at a time of Super Duty as-builts. Not too time consuming as you can write the HVAC module without turning the ignition off/on. It reboots itself with each write.
I found this:
733-01-06: xxxx-**xx-xxxx enables/disables the auto fan speed. Using the Super Duty as-builts disables it, setting it permanently at MEDIUM (2 lights lit). Writing the '20' from the F-150 as-builts enables it.
733-01-08: xx**-xxxx-xxxx enables/disables the passenger temperature ****. Using the Super Duty as-builts disables it. Writing the '81' from the F-150 as-builts enables it.
I'm sure that those values don't actually exist to enable/disable said functions... they just have that affect. That is why the HVAC module doesn't appear to work properly when first having the Super Duty as-builts loaded to it.
Using all Super Duty as-builts except those two sections, the 19980-K module operates correctly, with the exception of the recirc button which, while it does light when pressed, does not activate/deactivate the recirc door. I'll need to do more experimentation to see if I can solve that.
What is obvious from looking at Livinitup's spreadsheet and doing some mild cross-referencing is that MANY, but not ALL, of the F-150 settings locations in the HVAC module translate directly to the Super Duty module. However, some do not, and it is those SOME that are giving me/us grief with this.
@ZooDad I know you're the resident expert on Super Duty FORScan... do you happen to know if a list exists like Livinitup's F-150 spreadsheet that specifically covers the 2023+ Super Duty? If so, we might be able to cross-reference the two and make this work.
A big part of me is saying to just give up on this, that it is not worth it. And maybe he's right. But that just makes me want to try harder.
Last edited by dspa; Mar 23, 2025 at 07:21 PM.
https://www.ford-trucks.com/forums/1...ces-index.html
I did not review the spreadsheets to look for a solution to your project. Note that Zoodad is the Superduty spreadsheet master. Livinitup is the F150 spreadsheet master.
https://www.ford-trucks.com/forums/1...ces-index.html
I did not review the spreadsheets to look for a solution to your project. Note that Zoodad is the Superduty spreadsheet master. Livinitup is the F150 spreadsheet master.
I just want to preface with what I say next with this: I never claimed to be all that smart.

I was looking at the 2024+ F-150 spreadsheet, which is why many of the digits in my F-150 as-builts weren't making sense.

I'm going through the 2021-2023 one now and marking what each digit means. Then I should be able to figure out what to alter for the Super Duty. I don't expect to have to change much except the setting for the front PTC heater ("Rapid Heat Supplemental Cab Heater," in marketing-speak).
It's going to take a while, but I think it will work.
After spending hours combing over @Livnitup 's spreadsheets, I've got a new set of as-builts to use on my Super Duty with the ML3Z-19980-K module.
2023+ Super Dutys share HEX data locations with 2024+ F-150s when it comes to the HVAC module. 2021-2023 F-150 HVAC modules, while they share the same number of data registers, store the HEX data for the operating parameters/settings in different places. After spending a few hours staring at Livnitup's spreadsheets, I do kinda get why Ford changed how the modules are programmed. They've streamlined them quite a bit with the 2024+ F-150 and 2023+ Super Duty. But it definitely makes this particular job a lot more difficult.
Anyway, and therefore, if we want to use the ML3Z-19980-K module in 2023+ Super Duty (and it seems some of us certainly do), then we must cross-reference EVERY setting between the 2024+ F-150 spreadsheet and the 2021-2023 F-150 spreadsheet. Did I say a huge "thank you" to @Livnitup , yet? All the settings are there... we just need to find them. I'm attaching a new set of as-builts for the ML3Z-19980-K module in my 2024 Super Duty. I ended up changing a total of 10 HEX digits in the F-150 as-builts to code the 19980-K module properly for my 2024 Super Duty. Change the .TXT file extension to .ABT before you try importing them.
@ngiovas You can use this is a starting point, but I HIGHLY SUGGEST you have a look at your truck's as-builts and do a proper cross-reference.
@Livnitup 's spreadsheet with links to the relevant tabs:
2021-2023 HVAC module HERE
2024+ HVAC module HERE
I have a copy of Livnitup's spreadsheet with just the two HVAC tabs, but it won't let me attach it for some reason. I can email it to you if you PM me. In it, I highlighted my F-150 and Super Duty as-builts in yellow on the 2021-2023 tab and 2024+ tab, respectively. I highlighted the changes I made in green on the 2021-2023 tab. Any notes are written to the right and highlighted in yellow as well. EDIT: Link to my truncated version 1 post down.

When going through the spreadsheets, keep some things in mind... Is your truck a diesel? Do you have the front PTC heater (Rapid Heat Supplemental Cab Heater)? These are important questions you need to know the answers to before using my as-builts or changing values. If you want to PM me, I can help you work through any differences on your truck. If your stock Super Duty as-builts are identical to mine on lines 733-01-01 through 733-01-13, and I mean IDENTICAL, you should be able to use my new custom as-builts with your ML3Z-19980-K module. Otherwise, you need to make sure you cross-reference the differences. You can also use your plain language HVAC configuration (with the stock module, not the 19980-K) as a second point of reference (with Livnitup's 2024+ spreadsheet being the primary). Maybe make a printout so you have it on-hand while doing your cross-references. That's what I did. You should be able to find everything.
Lines 733-02-01 through 733-02-04 deal with coding your vehicle's VIN to the HVAC module. You CAN do this in the plain language HVAC configuration, and I recommend that over trying to code each digit to HEX in the as-builts. Don't worry about doing it until you have all your other settings cross-referenced and changed, though. If you use my as-builts, you'll have my VIN in there until you change it.

Note 1: FORScan will change the last 2 digits on each line any time you make an edit. The last two digits are checksum digits and this is normal behavior.
Note 2: Once you have loaded the F-150 as-builts to the 19980-K module, the plain-language configuration settings for the HVAC module can no longer be used. Do not attempt to modify any settings in plain-language HVAC configuration once you have loaded the F-150 as-builts.
I installed these custom values into my truck today, and everything seems to be working properly. I'll be testing over the next several weeks/months to make sure nothing is behaving oddly. Of highest interest to me is a test of the Front PTC Heater. I'll need a cold morning and to leave the truck outside overnight for that... this coming Saturday night / Sunday morning is looking promising, with temps dipping into the low 30s F.
It sure is nice to have the temp displays back in the dials. The ***** just looked wrong to me without them. To each their own!
Super-big thanks to @Don Ridley for the encouragement and support. And for all you smart fellers lurking out there who might want to double-check my work, feel free... I won't take it personally. This is all new to me!
Dustin












