F150 Lightning FORScan thread - Version 2

[evowner]

I appreciate the responses. I am not afraid to use the tool. I have written software for many kinds of advanced machinery, operation as well as user interfaces. I have used RS232, RS485, Ethernet, WiFi, with secs, mod-bus as well as other custom protocols. If there was a way for people to modify the settings on these machines, by changing a byte or two, without restrictions, a million dollar machine could quickly become severely damaged and useless.

My main concern is that since this vehicle is mostly drive by wire, a person could do something that could be detrimental to my safety. Changes are being made without really knowing what effect it may have on other logic or calculations in one or other modules. I know some of the changes seem to be working OK, but it seems to me, maybe I am wrong, that there are no restrictions as to what can be changed. Leaving it up to the individual to not do something wrong is troublesome.

Sponsored

 

[NeuroDawg]

This is why you need to reference the spreadsheet while making changes. Not all trucks have the same OEM configuration. What works for a '22 Platinum might not be the same as a '24 Flash.

Is there somewhere that explains exactly what all the abbreviations represent?

For example, I've been looking at the SCCM (2024) tab in the spreadsheet, and I wonder what "SFWM_Present " actually means. Some of the things I can figure out from context and googling, like "SCMFtWashType_Cfg" configures the front washer type (standard v. aquablade). But others I can't. So when I compare suggested changes/modifications with the spreadsheet it would be beneficial to understand all the abbreviations.

 

[NeuroDawg]

I personally wouldn't change steering wheel temp.

May I ask why? Of all the mods you mention, this is as straightforward as number of blinks. And since 37°C is body temp, and 39°C is only 4°F above body temp, the warmest your steering wheel will get is much lower than on a day in the sun in July.

 

[bmwhitetx]

Is there somewhere that explains exactly what all the abbreviations represent?

For example, I've been looking at the SCCM (2024) tab in the spreadsheet, and I wonder what "SFWM_Present " actually means. Some of the things I can figure out from context and googling, like "SCMFtWashType_Cfg" configures the front washer type (standard v. aquablade). But others I can't. So when I compare suggested changes/modifications with the spreadsheet it would be beneficial to understand all the abbreviations.

Are you trying to add rain-sensing wipers?
The key thing is if you don't know what a parameter does, leave it in the same state (enabled or not), when changing another parameter.

For the parameter you mention (724-02-01 xxxx x*xx --), I'm guessing you want to leave SFWM and SCMWC with the same values as before and pick the value that flips RSM from disabled to enabled.

The best source is the spreadsheet itself. Sometimes the abbreviation is spelled out in other places so I search. I couldn't find anything on your example.

 

[bmwhitetx]

May I ask why? Of all the mods you mention, this is as straightforward as number of blinks. And since 37°C is body temp, and 39°C is only 4°F above body temp, the warmest your steering wheel will get is much lower than on a day in the sun in July.

Nothing to do with burning yourself. But more about it is a resistant heater with limitations on the heating wire itself and the materials covering it. Just my engineer brain giving a nod to the Ford engineers for choosing that value. Kinda related to @evowner's post above.

Plus I find it warm enough!

 

[NeuroDawg]

Are you trying to add rain-sensing wipers?
The key thing is if you don't know what a parameter does, leave it in the same state (enabled or not), when changing another parameter.

For the parameter you mention (724-02-01 xxxx x*xx --), I'm guessing you want to leave SFWM and SCMWC with the same values as before and pick the value that flips RSM from disabled to enabled.

The best source is the spreadsheet itself. Sometimes the abbreviation is spelled out in other places so I search. I couldn't find anything on your example.

I am, but I was just using those as examples, because they were in the tab I was looking at and I couldn't figure out what the one meant. Not that I thought they had anything to do with rain sensing wipers.

edited to add: And if you know anything about the wiring up where the rain sensor goes, your comment would be much appreciated over there.

 

[Firn]

I appreciate the responses. I am not afraid to use the tool. I have written software for many kinds of advanced machinery, operation as well as user interfaces. I have used RS232, RS485, Ethernet, WiFi, with secs, mod-bus as well as other custom protocols. If there was a way for people to modify the settings on these machines, by changing a byte or two, without restrictions, a million dollar machine could quickly become severely damaged and useless.

My main concern is that since this vehicle is mostly drive by wire, a person could do something that could be detrimental to my safety. Changes are being made without really knowing what effect it may have on other logic or calculations in one or other modules. I know some of the changes seem to be working OK, but it seems to me, maybe I am wrong, that there are no restrictions as to what can be changed. Leaving it up to the individual to not do something wrong is troublesome.

And this is why i said what I did.

What you talk about is firmware and hard coded machine operations. That isn't what Forscan is changing. These are preconfigured Ford settings designed to allow a backend change to enable certain features.

Best example I can give is matrix headlights (glare free). Since they support the Canadian market, where it's legal, and the US market, where it's illegal, they have to support two different builds. Instead of designing two entirely different trucks, they just design one and turn the function off in software for the US trucks. Now, that has to be turned on in the lights themselves, the toggle in the center screen, and the green indicator on the dash, so changes in multiple spots, but yet still just turning on a factory enabled and tested capability.

All of these are the same. And when you see people who have issues, is they didn't change all three places, or changed an option on, but turned another off.

And all of this is COMPLETELY separate from the safety systems. Completely. You cannot defeate any safety measure. Accidentally turn off the air bags. Etc. This is far far removed from that level of software manipulation.

 

[evowner]

Thanks for clarifying.

 

[bmwhitetx]

All, I found an error for the Turn Signal Blinks. The original source of the mod didn't notice that it also has the Heated Steering Wheel Present parameter embedded. The code originally posted by him and copied by me assumed a Heated Steering Wheel. I have updated post 1 with new values - separating out HSW and no HSW. Here are the proper values:

SCCM 724-01-01 xxxx **xx xx--

Number of blinks	Heated Steering Wheel	No Heated Steering Wheel
3 (default)	8C	0C
4	90	10
5	94	14
6	98	18

If you have a HSW, nothing changed.
For the programmers, you will notice that the value is 0x80 less for no HSW.

 

[GarrettBlake]

The hex display in forscan may be convenient, but is very misleading. Either the UI should be much smarter about the data being changed or it should be done in binary. In this day and age why data structures like this exist are beyond imagination.

 

[bmwhitetx]

The hex display in forscan may be convenient, but is very misleading. Either the UI should be much smarter about the data being changed or it should be done in binary. In this day and age why data structures like this exist are beyond imagination.

Well first we shouldn't even know about this stuff or be able to change it. You have to remember this program was developed for/by Russians who needed to modify Fords decades ago. Ford would never condone this.

I think BMW's have some similar capability but our Hyundai, Pilot and Kia never did. So I'm thankful for what we got.

The FORScan folks have enabled a plain English mode for many of these changes so they are aware of the complexity. It does the hex math behind the scenes.

As for binary, I agree it would simplify many of these parameters. But the issue is that not everything is on/off. A lot of the values are integers. And some parameters have more than 2 possible values so use 2 or more bits.

 

[EdNewman]

Ok, so I went through your settings and your logic is sound. You do end up with some unicorn values. I am curious about it being a 2024 only problem. In looking at the As-Builts of 22-23's, it would seem that all 22-23 Pros and XLT w/o ACC would also not see the speed limit display on their dash. The values you enabled for your 24 are also disabled for the 22-23's.

So if true, this could also help 22-23 trucks that don't have ACC see speed limits.

Here is my additional analysis. If you're game you might change the first IPC back to original 4 to verify if it's needed. Maybe the second IPC also.


=============================== my notes in red
IPC
720-03-02 - Enable Traffic Sign Recognition (TSR) seemed logical, maybe not necessary?
As built C8(4)D 296A - change 4 to C
4 = TSR disabled • TS enabled • TBS disabled • TSP disabled
C = TSR enabled • TS enabled • TBS disabled • TSP disabled
Since all 22-24 Lightnings have a "4", I agree this change may not be needed.

720-09-01 Enable SLIF - again, maybe not necessary?
As Built 6062-1554-(1)975
1 = SLIF disabled • HUDC No_HUD • FCWARTTC ON
9 = SLIF enabled • HUDC No_HUD • FCWARTTC ON
SLIF= "speed limit information functions", matches trims with ACC so likely needed unless it's just used for the ACC part. So could change it back to As-Built and see what happens. Same for all 22-24.

APIM
7D0-09-02 - Traction Control/IVD/RSC (TCIVDRSC) • Adaptive Cruise (AC) • TSR NCAP Adaptations (TSRNCAPA) - This enabled the TSR, trucks with Adaptive cruise would probably be different
As Built C065-5(4)00-0560
4 = TCIVDRSC TC • AC Disabled • TSRNCAPA Disabled
5 = TCIVDRSC TC • AC Disabled • TSRNCAPA Enabled
7 = TCIVDRSC TC • AC Enabled • TSRNCAPA Enabled
22-24's with IACC have a 7.
22-24's w/o IACC have a 4.
Like you show, 5 would enable TSR but keep AC disabled.

Traffic Sign Recognition (TSR) • TPMS By Location (TPMSBL) • TPMS Placard Pressure Display (TPMSPPD) • Centerstack Settings (CS)
As Built C065-5400-0(5)60
5 = TSR Disabled • TPMSBL Enabled • TPMSPPD Disabled • CS Enabled
D = TSR Enabled • TPMSBL Enabled • TPMSPPD Disabled • CS Enabled
Matches 22-24 as-builts with and without ACC

IPMA
706-01-01
ModuleFeatureCfg_TSR (MFCTSR) • ModuleFeatureCfg_IACC (MFCIACC)
As Built 0E(0)0-8055-8E80
0 = MFCTSR Off • MFCIACC Disabled
4 = MFCTSR SLIF • MFCIACC Disabled
5 = MFCTSR SLIF • MFCIACC Enabled
22-24's with IACC have a 5.
22-24's w/o IACC have a 0.
Like you show, 4 would enable TSR SLIF but keep AC disabled.

706-02-01
FeatureCfg_TSRMode (FCTSRM) • FeatureCfg_LKSMyKey (FCLKSMK) • FeatureCfg_LKSStrategy (FCLKSS) • FeatureCfg_DPAC_WrdRemoteCamera (FCDPACWRC)
As Built (2)B67-FFCC-016E
2B = FCTSRM OFF • FCLKSMK OFF • FCLKSS Non_EuNCAP • FCDPACWRC Present
4B = FCTSRM CameraOnlyOn • FCLKSMK OFF • FCLKSS Non_EuNCAP • FCDPACWRC Present
6B = FCTSRM FusionOn • FCLKSMK OFF • FCLKSS Non_EuNCAP • FCDPACWRC Present

As Built for Lightnings
32 = FCTSRM OFF • FCLKSMK ON • FCLKSS Non_EuNCAP • FCDPACWRC Absent 22-23 Pro
33 = FCTSRM OFF • FCLKSMK ON • FCLKSS Non_EuNCAP • FCDPACWRC Present 22-23 XLT 311A
73 = FCTSRM FusionOn • FCLKSMK ON • FCLKSS Non_EuNCAP • FCDPACWRC Present 22-23 IACC
2B = FCTSRM OFF • FCLKSMK OFF • FCLKSS Non_EuNCAP • FCDPACWRC Present 24 XLT
6B = FCTSRM FusionOn • FCLKSMK OFF • FCLKSS Non_EuNCAP • FCDPACWRC Present 24 Flash and above

good morning, I was able to make the change on the IPC for 720-03–02 back to The as built of 4 and the speed limit sign detection and display still seem to be functioning properly. So my take away is that you were correct and that change is indeed unneeded. I will continue to work through them one at a time until we get this to 100%.

Sponsored