2024 Mustang FORScan List / Database / Spreadsheet (by Livinitup)

[smurfslayer]

I noticed that when I turn the ignition off, the screen’s primary and secondary colors revert to the default settings (the color of the time and the Home button, etc.). I’m not sure if this is normal behavior or if I accidentally changed something while playing around with Forscan.

Has anyone else experienced this?

Yes. You won’t notice it unless you change the default my color settings. When you get in and power on, even if you don’t start up, the colors are what is selected in my color. When you shut down, you get the default colors.

Sponsored

 

[Stang24]

Is there anything in Forscan about an oil temp cooler? Oil temp is estimated (no actual oil temp sensor) NON PP don’t get an oil cooler but some people like me have added one. PP get one from factory and read lower obviously. With that being said if you add an oil cooler to a non pp the oil temps on the dash will read the same because the car doesn’t know you added an oil cooler. Was wondering if there’s anything in forscan about an oil cooler so for people that added one to their non pp the temps will read similarly to the PP

 

[A.alansari]

new to forscan I enabled the gear always display and it worked fine
then I tried for the remote rev but the address on the spreadsheet is not the same as in my car

this is the one in the spreadsheet
7E0-02-04

and my car is attached

it starts from 7E0-162 to 165

 

[A.alansari]

new to forscan I enabled the gear always display and it worked fine
then I tried for the remote rev but the address on the spreadsheet is not the same as in my car

this is the one in the spreadsheet
7E0-02-04

and my car is attached

it starts from 7E0-162 to 165

Its a forscan issue as has been found by other members on another post

 

[npole]

Use the previous ForScan version(s) 2.3.64- until it's fixed.

 

[Sainty]

We've now heard back from FORScan. It is not a bug with version 2.3.65.
This is intentional as the block numbers have changed!
Full details in this thread.

 

[npole]

To be more specific, the block didn't changed, the position have remained the same, but it's the address labeling that was named wrong. ForScan is now using the correct addresses "names", but they won't reflect the previous xlm table. To be short "7E0-02" is now "7E0-162".

 

[RimaFlowss]

To be more specific, the block didn't changed, the position have remained the same, but it's the address labeling that was named wrong. ForScan is now using the correct addresses "names", but they won't reflect the previous xlm table. To be short "7E0-02" is now "7E0-162".

I can vouch for this. I believe it was under the PCM or IPC values when I was messing with setting up the continuous gear display stuff on my EcoBoost. Addresses had changed but they remained holding the same function, etc. Wasn’t hard to figure out which new address to use, since the values themselves remained the same and the value(s) in the specific position that needed to be changed are almost completely unique to each individual address.

 

[A.alansari]

To be more specific, the block didn't changed, the position have remained the same, but it's the address labeling that was named wrong. ForScan is now using the correct addresses "names", but they won't reflect the previous xlm table. To be short "7E0-02" is now "7E0-162".

I tried with version .64 still got the same address 162 and i changed it to enable the remote rev and it worked

maybe we need to update the address on the excelsheet or maybe add the 162 address beside the 02 so people don't get confused

 

[zackmd1]

Official response from Forscan on the 2.3.64 vs 2.3.65 display differences.

"This is a bug in FORScan prior to v2.3.65.

Mustang S550 prior to 2020 had PCM VID block, it had no blocks 7E0-162 etc, so it worked properly.

Mustang S550 2020-2023 has another PCM configuration. But FORScan used wrong (2019-) PCM configuration layout for it. That's caused the result you see in v2.3.64.

Mustang S650 2024+ also had old PCM layout (from 2019-), but in v2.3.65 we fixed it, now it works properly and shows correct data. The bug for Mustang S550 2020-2023 still exists and must be fixed.

How to make sure the v2.3.64 doesn't work properly?

1. Compare it with output of Motorcraft As Built data (we provided a screenshot in our previous email).

2. Try to load factory AB file - it will report success but actually doesn't work.

We are sorry that this bug in FORScan lead to wrong speadsheets created by community. We also going to make the same fix for 2020-2023 S550. If you have any idea how to resolve any further confusion and misunderstanding during the community, please let us know.

--
Regards,
FORScan Team"

 

[Fruitstang]

Confuses more than it helps ... but I'm not a native English speaker though.

 

[sky5oh]

Anybody know if it’s possible to enable speed sign recognition on a base? I was playing around with it yesterday but couldn’t really figure it out. That’s assuming if there’s no hardware limitations.

 

[GrabThatBlue]

Anybody know if it’s possible to enable speed sign recognition on a base? I was playing around with it yesterday but couldn’t really figure it out. That’s assuming if there’s no hardware limitations.

Interested as well.

I have speed sign recognition but it has the American speed signs. I need to change those speed signa to the European ones.

 

[sky5oh]

Interested as well.

I have speed sign recognition but it has the American speed signs. I need to change those speed signa to the European ones.

The only thing I could find in correlation to TSR, were:
Menu - Traffic Sign Recognition Activation
Menu - Traffic Sign Recognition Version
Traffic Sign Recognition (TSR)

 

[GrabThatBlue]

The only thing I could find in correlation to TSR, were:
Menu - Traffic Sign Recognition Activation
Menu - Traffic Sign Recognition Version
Traffic Sign Recognition (TSR)

The only change I did in Forscan in easy mode was the continues gear display.
Now I rather change the values my self in Asbuilt data.

Sponsored