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

[HMBSTNG]

the module is "IPC" and search for "VSS" or "Visual Speedometer Style"

Are you referring to the actual car in forscan or in the excel that was attached? Sorry, I'm new to this and don't want to mess things up.

Sponsored

 

[roket]

Are you referring to the actual car in forscan or in the excel that was attached? Sorry, I'm new to this and don't want to mess things up.

the spreadsheet in the main post

 

[HMBSTNG]

the spreadsheet in the main post

I think this is it?

 

[mks]

I'm going to stop fiddling for now, but I thought I'd post the results of my fumbling foray into FORScan editing. My WAL feature works but without the audible horn chirp. My Approach Detection "works" but not automatically, i.e., I have to press my FOB's unlock button--no biggie there.

My notes were not composed with other readers in mind--but they might lend some context into my circus-like effort.

 

[HMBSTNG]

I'm going to stop fiddling for now, but I thought I'd post the results of my fumbling foray into FORScan editing. My WAL feature works but without the audible horn chirp. My Approach Detection "works" but not automatically, i.e., I have to press my FOB's unlock button--no biggie there.

My notes were not composed with other readers in mind--but they might lend some context into my circus-like effort.

Mines is the same. I get the yellow light but no horn.

Do you know the code for having the tail lights to dance with the headlights? I currently have the "DH" theme.

 

[mks]

Do you know the code for having the tail lights to dance with the headlights?

I don't know the code for the tail. If I find or stumble on it, I'll post. I'd like to fix the horn chirp, first.

 

[roadpilot]

I'd like to fix the horn chirp, first.

You're looking for Walk Away Lock Feedback?

BCM 726-91-01 xxxx xxx1 xx--
BCM 726-97-01 x1x1 x1x1 x1--
APIM 7D0-09-05 xxxx Cxxx xx--

You already changed BCM 726-91-01 for WAL. You need another change (different position) for WALF. Leave the first change (xxxx x1xx xx-- ) in place.

Also, you likely changed 7D0-09-05 from xxxx 0xxx xx-- to xxxx 8xxx xx-- to get WAL to work. If you want WALF to go along with it, that requires these two additional BCM changes, and it requires you to change what you already changed in the APIM to get WAL to get both:

APIM 7D0-09005 xxxx Cxxx xx--

 

[Fruitstang]

What about the alarms when you leave the car with your key fob in your pocket or just open the door?
If that can be changed, maybe something to add to the list in post #2?

 

[mks]

BCM 726-91-01 xxxx xxx1 xx--
BCM 726-97-01 x1x1 x1x1 x1--
APIM 7D0-09-05 xxxx Cxxx xx--

You already changed BCM 726-91-01 for WAL. You need another change (different position) for WALF. Leave the first change (xxxx x1xx xx-- ) in place.

Also, you likely changed 7D0-09-05 from xxxx 0xxx xx-- to xxxx 8xxx xx-- to get WAL to work. If you want WALF to go along with it, that requires these two additional BCM changes, and it requires you to change what you already changed in the APIM to get WAL to get both:

APIM 7D0-09005 xxxx Cxxx xx--

Okay, first things first. Thank you for helping me correct the right addresses. However, my edits did not yield any discernable effects. WAL works; AWALF does not. I've updated my attached notes, but here's a summary:

Recommended edits:
BCM 726-91-01 xxxx xxx1 xx--
BCM 726-97-01 x1x1 x1x1 x1--
APIM 7D0-09-05 xxxx Cxxx xx--

Actual Edits/Current config:
BCM 726-91** 0001 0101 00C2 (see notes)
BCM 726-97** 0101 0101 01CB
APIM 7D0-09** 0030 C520 00FA (see notes)

Note, for that APIM address, my second group was still at its default value, 0520--and WAL was working. But, I made the edit anyway...WAL still working.

I should note that prior to editing any of the above addresses, I undid any changes I made in "easy mode" (there were only a few). That said, after making edits to the modules as suggested, they were reflected in the "easy mode" modules.

Again, I fear I'm about as far as I can go without a digit-by-digit sleepover editing session in my car. I may come back to this later...perhaps after someone, with a similar result, works out a solution.

 

[roadpilot]

The values I used worked for me for WALF, @MKS33. I did revert them back later as I didn't want the horn chirp, but I did test it out and the horn chirp when WAL triggered did work.

Suggestion: Double-check and make sure your edits are correct. I've been doing this for years and still screw up editing the wrong entry or changing the wrong digit.

For the BCM updates: Make sure you didn't confuse 726-97-01 with 726-97-02.

For WAL, the edit is for 726-97-02
For WALF, the edit is for 726-97-01

The confusing part is: The edit is the exact same VALUE for each: x1x1 x1x1 x1--

Once I got WAL to work, when I went back to try WALF, I mixed up 01 and 02, thinking I had already made that change (due to the value being the same). Then I realized I actually needed to (also) edit 01 for WALF. Once I did that, it worked.

And if I'm not mistaken, I believe the APIM update will add the WALF to the Sync screen under Vehicle / Locks. Make sure it's ON.

Also, you should always reset the APIM module after making any changes.

If I get a chance, I'll check my current values for those when I get home tonight.

 

[mks]

Double-check and make sure your edits are correct

Will do. I'm prone to user error.

 

[roadpilot]

Will do. I'm prone to user error.

I've been using FORScan for over 9 years, and I still f*ck up on a regular basis ...

 

[mks]

I've been using FORScan for over 9 years, and I still f*ck up on a regular basis ...

Ugh, padawan learner! I missed the "1" in the 3rd group at address 726-97-01.

Horn chirp works. The APIM had been displaying the "Audible Feedback" option (showing it was enabled), so I had been wrongly assuming my DH was just "different." Nope, it was me.

Many thanks and may the force be with you.

AND...while I was in FORScan, I reviewed my edits for Approach Detection. Wouldn't you know, I missed a digit ("1") in the 1st group of address 6F6-05-05. The sequence for that address now reads, 0701 0000 020F. Works like a charm.

New notes with edits that work (for my DH).

 

[roadpilot]

Ugh, padawan learner! I missed the "1" in the 3rd group at address 726-97-01.

Horn chirp works. The APIM had been displaying the "Audible Feedback" option (showing it was enabled), so I had been wrongly assuming my DH was just "different." Nope, it was me.

Many thanks and may the force be with you.

AND...while I was in FORScan, I reviewed my edits for Approach Detection. Wouldn't you know, I missed a digit ("1") in the 1st group of address 6F6-05-05. The sequence for that address now reads, 0701 0000 020F. Works like a charm.

New notes with edits that work (for my DH).

Congrats, @mks. Like I said, I still do that myself.

The APIM edit simply displays the option in the Vehicle/Locks screen. But without the correct BCM edits, that option won't do squat (enabled or disabled).

@rugedraw, Livinitup can add those three edits for WALF to the spreadsheet.

 

[ChrisMattice]

I can confirm the updated version of FORScan allows the changing of welcome lighting for the front headlights (I still need to find the values for the tails)

LDCMB:
6F6-05-05 **** **** **** *X**
LDCMA:
6F7-05-05 **** **** **** *X**

Changing the value to 2 enables the Darkhorse headlight welcome effect on unlock. 3 enables the Premium sequence

LDCMB:
6F6-05-05 *X**
LDCMA:
6F7-05-06 *X**

Changing the value to 9 does a standard time out
2 and 3 appears to make the tri light stay on for longer duration.

Edit: Just realized I flip flopped the * and the X format...

Sponsored