FORScan MME spreadsheet

[Chapron]

ah, ok so no easy software tweak. And not easy to reverse then. But good job!

Sponsored

 

[ave]

ah, ok so no easy software tweak. And not easy to reverse then. But good job!

It is kind of mixed bag side channel hardware/software hack. The HW is done by HARMAN Automotive.

For sure it is possible to officially program it via OTA and OBD/FDRS but doing so yourself is way beyond what I was willing to invest, if it is possible at all.

There are crypto signatures in the data, I'm actually impressed by the level of professionalism present in the system.

 

[DigitalN]

I read through this entire post and came up empty, other than one guy earlier who I saw in his list of modules had an HVAC one he could access.

When I look at the spreadsheet, I see there is an HVAC module with a lot of different parameters that can be adjusted. But when I open FORScan on my car I only have these modules, no HVAC module. Is there something I am missing?

PCM (As Built)
PCM

SOBDMC (As Built)

BECM (As Built)

SODR (As Built)

SODL (As Built)
SODL (Configurable)

CMR (As Built)

CCM (As Built)
CCM (Configurable)

ABS (As Built)
ABS (Configurable)

PSCM (As Built)

BdyCM (As Built)
BdyCM (Configurable)

BECMB (As Built)

GWM (As Built)

IPMA (As Built)
IPMA (Configurable)

SODCMD (As Built)

SODCMC (As Built)

BCMC (As Built)

 

[jmgreen]

May I ask what type of OBD dongle you are using?
I can imagine that yours may be one of those that show issues with the different CAN network protocols.

 

[DigitalN]

Yes I’m using a Tactrix Openport 2 adapter as I had one for my Mercedes. I didn’t think it was a cable issue since it picked up some of the modules

Doing some googling now I see others have issues, I’ll pick up a new cable. Thanks for the memory jog!

 

[rugedraw]

Livnitup added the changes needed to enable the BC 1.2-1.4 features to the common tab of the F150 spreadsheet. In order for this to work, the IPMA must be on the latest version (BAE strategy) and the vehicle must have an active BC subscription. Othewrwise, this will not work. This only applies to 21-23 Mach E's that did not ship with lane change assist etc and never got the OTA that enables the features.

APIM	7D0-09-05	xxxx	xx4x	2x--
APIM	7D0-10-02	xxxx	xxxx	1x--
IPMA	706-01-01	xExx	xxxx	xx--
IPMA	706-01-02	x5xx	xxxx	xx--
IPMA	706-02-02	xxxx	xxxx	x2--
IPMA	706-38-01	x8x8	xxxx	xx--

To anyone that has already enabled this themselves either with my help or anyone else's help, please note there is one change in the APIM which I did not know about that enable intelligent adaptive cruise control tolerance settings. If you enabled yourself, go back to the APIM and make this one change:

7D0-09-05

xxxx xxxx x2xx

Lastly: The changes needed to enable this in vehicles outside American markets may be different, so check what values are there against the spreadsheet before attempting to make sure you don't enable/disable something that isn't supposed to be changed.

 

[jmgreen]

Livnitup added the changes needed to enable the BC 1.2-1.4 features to the common tab of the F150 spreadsheet. The changes needed to enable this on the Mach E is the same with the exception of one bit in the APIM. In order for this to work, the IPMA must be on the latest version (BAE strategy) and the vehicle must have an active BC subscription. Otherwise, this will not work. This only applies to 21-23 Mach E's that did not ship with lane change assist etc and never got the OTA that enables the features.

APIM7D0-09-05xxxxxxEx21--APIM7D0-10-02xxxxxxxx1x--IPMA706-01-01xExxxxxxxx--IPMA706-01-02x5xxxxxxxx--IPMA706-02-02xxxxxxxxx2--IPMA706-38-01x8x8xxxxxx--

To anyone that has already enabled this themselves either with my help or anyone else's help, please note there is one change in the APIM which I did not know about that enable intelligent adaptive cruise control tolerance settings. If you enabled yourself, go back to the APIM and make this one change:

7D0-09-05

xxxx xxxx x1xx

Lastly: The changes needed to enable this in vehicles outside American markets may be different, so check what values are there against the spreadsheet before attempting to make sure you don't enable/disable something that isn't supposed to be changed.

Thanks a lot for this information!!!
But out of curiosity, I hope you don't mind me asking two questions?

You said that in comparison to the F150, on the Mach-E there is one bit to be changed in the APIM. So I looked which bit you may mean, and the only difference I find is the following, am I right?
=> 7D0-09-05 xxxx xxEx xxxx
I struggle a bit with this, as so far I have been using the value "4", i.e. the same as in Livnitup's F150 spreadsheet.
Comparing the differences, I see this (by the way, in Livnitup's Mach-E spreadsheet I find the same):
=> 4: FRD External • LB Enabled • KDA Disabled • RBCF Disabled (Version 1 or Off)
=> E: FRD Internal • LB Enabled • KDA Enabled • RBCF Disabled (Version 1 or Off)
The only changes are for FRD (Frunk Restricted Determination), and KDA (Key Detection Alert). As both don't seem to be related to BC, I wonder why it shall be necessary to use the value "E" on Mach-E?

And then you said, that we shall put 7D0-09-05 to xxxx xxxx x1xx.
Acc. to the spreadsheet this disables the Speed Limit Assist Tolerance (SLAT). So why is this needed to have BC1.4 working to all extend?

 

[rugedraw]

Thanks a lot for this information!!!
But out of curiosity, I hope you don't mind me asking two questions?

You said that in comparison to the F150, on the Mach-E there is one bit to be changed in the APIM. So I looked which bit you may mean, and the only difference I find is the following, am I right?
=> 7D0-09-05 xxxx xxEx xxxx
I struggle a bit with this, as so far I have been using the value "4", i.e. the same as in Livnitup's F150 spreadsheet.
Comparing the differences, I see this (by the way, in Livnitup's Mach-E spreadsheet I find the same):
=> 4: FRD External • LB Enabled • KDA Disabled • RBCF Disabled (Version 1 or Off)
=> E: FRD Internal • LB Enabled • KDA Enabled • RBCF Disabled (Version 1 or Off)
The only changes are for FRD (Frunk Restricted Determination), and KDA (Key Detection Alert). As both don't seem to be related to BC, I wonder why it shall be necessary to use the value "E" on Mach-E?

And then you said, that we shall put 7D0-09-05 to xxxx xxxx x1xx.
Acc. to the spreadsheet this disables the Speed Limit Assist Tolerance (SLAT). So why is this needed to have BC1.4 working to all extend?

Any and all questions are welcomed. I thought I had edited that out, but I guess I didn't save the changes when I edited the post. That E only needs to be there for the Lightnings. I edited my post to show a 4 there is correct.

The change to xxxx xxxx xXxx is to enabled IACCT, but yes, that will also disable speed limit assist. I did not notice the Mach E has speed limit assist enabled, so good catch! Thank you. I ammended my post to reflect that, too. That should be a 2 and not a one so both stay enabled.

 

[jmgreen]

The change to xxxx xxxx xXxx is to enabled IACCT, but yes, that will also disable speed limit assist. I did not notice the Mach E has speed limit assist enabled, so good catch! Thank you. I amended my post to reflect that, too. That should be a 3 and not a one so both stay enabled.

Thanks for your quick reply.
But do you have a different decoding for 7D0-09-05 xxxx xxxx xXxx? I must say that I only find this in Livnitup's F150 spreadsheet, and not in (my very old) Mach-E sheet. And here also the "3" disables the SLAT (plus now also LMSI (Lock Menu Switch Inhibit)

0 = NETDL Disabled • IACCT Enabled • LMSI Enable the Menu • SLAT Enable
1 = NETDL Disabled • IACCT Enabled • LMSI Enable the Menu • SLAT Disable
2 = NETDL Disabled • IACCT Enabled • LMSI Disable the Menu • SLAT Enable
3 = NETDL Disabled • IACCT Enabled • LMSI Disable the Menu • SLAT Disable
4 = NETDL Disabled • IACCT Disabled • LMSI Enable the Menu • SLAT Enable
5 = NETDL Disabled • IACCT Disabled • LMSI Enable the Menu • SLAT Disable
6 = NETDL Disabled • IACCT Disabled • LMSI Disable the Menu • SLAT Enable
7 = NETDL Disabled • IACCT Disabled • LMSI Disable the Menu • SLAT Disable

 

[rugedraw]

Thanks for your quick reply.
But do you have a different decoding for 7D0-09-05 xxxx xxxx xXxx? I must say that I only find this in Livnitup's F150 spreadsheet, and not in (my very old) Mach-E sheet. And here also the "3" disables the SLAT (plus now also LMSI (Lock Menu Switch Inhibit)

0 = NETDL Disabled • IACCT Enabled • LMSI Enable the Menu • SLAT Enable
1 = NETDL Disabled • IACCT Enabled • LMSI Enable the Menu • SLAT Disable
2 = NETDL Disabled • IACCT Enabled • LMSI Disable the Menu • SLAT Enable
3 = NETDL Disabled • IACCT Enabled • LMSI Disable the Menu • SLAT Disable
4 = NETDL Disabled • IACCT Disabled • LMSI Enable the Menu • SLAT Enable
5 = NETDL Disabled • IACCT Disabled • LMSI Enable the Menu • SLAT Disable
6 = NETDL Disabled • IACCT Disabled • LMSI Disable the Menu • SLAT Enable
7 = NETDL Disabled • IACCT Disabled • LMSI Disable the Menu • SLAT Disable

I'm off my game today. A 2 there is correct. Amended my post again. lol

The Mach E spreadsheet was based off older APIM firmware that does not contain all the info th F150 spreadsheet has, so you will notice some things missing when you look at this spreadsheet compare to the one on the F150s.

 

[jmgreen]

A 2 there is correct.

Okay, I will give it a trial.
Currently I am using the "0" here, and so with the "2" I will put LMSI to "Disable the Menu".
What is this good for?

 

[rugedraw]

Okay, I will give it a trial.
Currently I am using the "0" here, and so with the "2" I will put LMSI to "Disable the Menu".
What is this good for?

You know what? I am very happy you pointed this out, because it is not making sense to me why this should be changed at all. Leave it at 0 for now and allow me to time to dig into this a bit.

Sponsored