Terrain management upgrade?

[RVA Overland]

I for one am super thankful that you guys figured out as much as you have. Thank you for the work everyone has put into this. @t4thfavor you are way braver then I am. Good luck on the PCM update. Love this site

Sponsored

 

[Geoff]

I was under the impression that programming the PCM required Ford SW (and a license) along with some hardware.

But my question is how did you obtain the PCM as built? The 'As-built' web page doesn't give me an option of downloading the PCM stuff....

We may have a "problem" getting the Trail Control enabled...

I found some .ab compare utilities and had been going through some of the modules.

I noticed that a non-fx4 truck has 163-xxx stuff in the PCM while the FX4 truck has 163-xx and a whole slew of 165-xx stuff (At least 20 more rows).

It's entirely possible that they flash different firmware to the PCM based on the FX4/not FX4 stuff. I don't know enough about it to know whether you can:
1. Just add the 165-xx stuff through Forscan, or
2. Flash the PCM with a FX4 variant, and make sure you retain your original values (like VIN, etc)

I know that Forscan Beta 2.4 has some talk about flashing firmware to modules, but it's not "stable" yet.

 

[Rick - Saber]

I got the switches installed. The Terrain Management setup was a breeze. As well as setting up the off road screen.

Can confirm the Trail Control is a bit more of a challenge. My ABS for 760-03-01 was 0005 70 as well. TC did not want to work as 0007 72 as tried by another. When trying to change just the first digit to a 2 as describe in previous posts it also changed the last two digits to 90 automatically in forscan. That did not work either. So much for hoping this was a simple software switch flip.

Appreciate all the work you are putting into this @t4thfavor . Your knowledge on this stuff is greater than my own. If you don't mind, what are you using to compare the data files?

 

[t4thfavor]

I found an asbuilt compare utility on the f150 forum. I was just comparing xml files in a text editor.
The pcm data is all available in forscan, it’s just data though, no fancy module configuration section.

I think we’re going to have to wait until firmware loading is possible through forscan.

 

[Geoff]

Yea, if the PCM is somehow flashed differently I agree. That said, there may be more than one thing that needs changing. ?

If there is anyone who has a decked out '19 FX4 Lariat willing to let me examine it's as built data I'd like to compare it to mine (I have the electronic axle but passed on the FX4 option as I wanted on-road suspension).

I found an asbuilt compare utility on the f150 forum. I was just comparing xml files in a text editor.
The pcm data is all available in forscan, it’s just data though, no fancy module configuration section.

I think we’re going to have to wait until firmware loading is possible through forscan.

 

[Geoff]

I've been comparing my As-Built to RedlandRangers As-Built. I'm still workign on comparing the two but the first thing that jumps off the page is something totally unexpected.

My Vehicle is a pretty much loaded non-FX4 Lariat (and it has the electric axle).
RedlandRangers is pretty much loaded and IS an FX4 4x4
Both have the 501a package along with the trailer towing package.

The weird part is my As-Built has about 200 more pids. Essentially more 7E0-165-xx and 726-xx-xx pids. The 7E0 items are ECU related and the 726 items are body module related.

If anything it would have seemed to make more sense with the FX4 vehicle having a few more pids. In any event I wasn't expecting the pid differences to be in the 200 range.

 

[Geoff]

I'd like to get another FX4 Lariat As-built.....
Are there any other owners with a loaded 2019 FX4 Lariat willing to share As-built data?

 

[Rick - Saber]

Here's a thought guys... maybe instead of looking at as builts for fully loaded up optioned trucks such as Lariats, for example. It might be easier to compare more basic trim level as builts with less options that do and do not have Trail Control. That way there would be less variables to muddy the waters to sift through. Making it easier to spot the changes needed for the Trail Control Mods. Nothing against the Lariats and I am slightly biased because I have less bells and whistles on my XLT.

 

[Geoff]

Here's a thought guys... maybe instead of looking at as builts for fully loaded up optioned trucks such as Lariats, for example. It might be easier to compare more basic trim level as builts with less options that do and do not have Trail Control. That way there would be less variables to muddy the waters to sift through. Making it easier to spot the changes needed for the Trail Control Mods. Nothing against the Lariats and I am slightly biased because I have less bells and whistles on my XLT.

Sorry, I have a Lariat and that's what I'm examining. Feel free to examine non Lariat As-Builts.....I have enough work.

 

[Geoff]

Here is a (Mac OS Numbers) file comparing as-builts between two Lariats (Excel should be able to import this).

NOTES:
Values for the FX4 vehicle are blank if they EQUAL the values for the non-FX4 vehicle.
If the values differ, the values for each are shown.
NA means that the pids were not available for the FX4 vehicle

 

[Geoff]

The next step is to go thru each difference and see what that function is and if it has anything to do with Trail Control.

It would be most helpful if we could get lots eyes looking into these differences....

 

[RoadBoss]

question for those of you that have successfully installed the TM switch and gotten it functioning on the dash, have any of you actually tested it out in the real world yet to make sure it functions properly? I don't see why it wouldn't, but I'm still very curious.

thanks

 

[Geoff]

^^ Good question.....I was wondering the same thing....

 

[Geoff]

I have discovered one more finding of differences between FX4 and non FX4 Lariats...At the end of the As-Built file each node is detailed out. I was mainly interested in the 7E0 and 726 PID differences between vehicles so I looked at those nodes....
(Non FX4 FX4)

I'm not exactly sure what all this is telling me but the difference in the F18C value is striking. I wonder if it references the SW load of the CAN device?

It turns out the F18C value is the serial number of the device so there is no apparent difference here. Moving on.

 

[H2Ocooled]

question for those of you that have successfully installed the TM switch and gotten it functioning on the dash, have any of you actually tested it out in the real world yet to make sure it functions properly? I don't see why it wouldn't, but I'm still very curious.

thanks

I installed the Terrain Management switch and Forscan code and tested putting in in 4h and changing the settings for different conditions and it worked fine. I also tested the 4x4 off road screen that is in the gauges and it works fine, it shows the angle you are at and it does work. Is there what you were wanting?

Rich

Sponsored