Turn Signal Blinker Count

[jkernitzki]

For those of us old to remember, turn signals used to be either on or off. Then they added "lane change" mode, which was simply a momentary switch not engaging the latch. I'm trying to figure out why it should now have a predetermined number of flashes. How "momentary" my turn signal is on for a lane change is never the same, but maybe that's because I was taught how to use them (unlike BMW owners).

I'd just rather go back to on/off/momentary. I can manage the number of flashes on my own quite fine, thank you.

Sponsored

 

[smcBronco]

Yes, my BMW 8 series (96) had the momentary. It blinked as long as you held the stalk.

 

[Quashish]

@Dude I looked into it just been too busy to post. This is what the free version of FORscan looks like

I didn't end up changing anything

 

[Dude]

@Dude I looked into it ….
I didn't end up changing anything

You are confirming with others have stated which is that the Turn Signal Flash Count is no longer available to modify (at least in the SCCM at its former location for earlier module year Bronco Sports)

Typical Ford vehicles (F-150, Escape, Maverick, and Focus), the lane change blinker count is stored in SCCM 724-01-01, typically in Byte 1 (the second group of 4 hex digits).

But in your Bronco Sport (724-01-01: BC09 4F05 296F):
• Byte 1 is 4F05
• 4F (binary: 01001111)
• 05 (binary: 00000101)

None of these bit values match the documented flash count nibble pattern (06 = 3 flashes, 0C = 6 flashes, etc.), and this layout appears custom to the Bronco Sport confirming that the (MY ‘24) SCCM is slightly different than older Ford models

There are a few things to look at depending on how much time you’d like to spend on this

1. Search other forums / online info especially current models like 2023, 2024 Maverick etc to see if there are posts regarding this parameter

2. In your 2nd pic (plain language SCCM configuration), the flash count isn’t listed and you probably already tried this however I’m including for completeness if others look at the same module in FORScan:
In SCCM, scroll further in this plain English mode in FORScan, look for:
• Lane Change Turn Signal or
• Turn Signal Tap Flash Count or
• Comfort Blinker

3. Try brute force testing 724-01-02: (not 724-01-01 )
If you’re comfortable editing AS-BUILT manually, you can try the following:

Do this only after saving your current configuration (including taking a screenshot or writing it down)

Modify first nibble of 4022
4 (binary 0100) might indicate a base configuration
Try changing the 4 to C:
4022 0000 0090 → 724-01-02: C022 0000 0090

In other Ford platforms, C or E as the leading nibble has been used to bump flash counts

Recommended Process
1. Save original values:
724-01-02: 4022 0000 0090

2. Try this test change:
724-01-02: C022 0000 0090

3. Write → Cycle ignition → Test lane-change flash count (quick tap on turn signal stalk)

If you get 6 flashes, you found the right byte.

Notes:
724-01-01 is almost certainly NOT holding the blinker count in your 2024 Bronco Sport, the SCCM layout changed, likely due to newer firmware

724-01-02 is suggested because it has values consistent with known editable flash count locations on newer Ford vehicles.

FORScan forum users (especially with 2023+ vehicles) report blink count has moved to other 724-01-XX locations in newer vehicles

 

[Quashish]

Ill try it out when i get some time! Im not a computers guy but im not afraid to test this out if it unlocks something else for the forum.

 

[jkernitzki]

So naturally just when I’m ready to make some tweaks in FORScan, the laptop locks out a necessary driver and now refuses to connect to the vehicle. It’s one I’ve had since 2018, been my semi-reliable workhorse from Afghanistan to Germany to Iraq to Mexico, and I’m finally fed up with it. Heavy, hot, and about 30 minutes of battery life on a full charge anymore. Half the time it fails Widows updates. Basically a doorstop that identifies as a PC.

Just ordered a new one from Amazon, a NIMO N150-based Win11 machine for $300 new. I only need it for FORScan, my XTool laser and Bambu X1C, and light CAD for them. No gaming, I’ve got the “big” machine in the office for that.

And now I get to wait another day or so to do fun stuff to the BS.

 

[Dude]

So naturally just when I’m ready to make some tweaks in FORScan, the laptop locks out a necessary driver and now refuses to connect to the vehicle. It’s one I’ve had since 2018, been my semi-reliable workhorse from Afghanistan to Germany to Iraq to Mexico, and I’m finally fed up with it. Heavy, hot, and about 30 minutes of battery life on a full charge anymore. Half the time it fails Widows updates. Basically a doorstop that identifies as a PC.

Just ordered a new one from Amazon, a NIMO N150-based Win11 machine for $300 new. I only need it for FORScan, my XTool laser and Bambu X1C, and light CAD for them. No gaming, I’ve got the “big” machine in the office for that.

And now I get to wait another day or so to do fun stuff to the BS.

Hope you take copious notes, screenshots and other info pertaining to the FORScan mods you make

many owners have posted about their FORScan mods but provide little to no details stating they can’t remember what were the steps they performed

 

[jkernitzki]

Hope you take copious notes, screenshots and other info pertaining to the FORScan mods you make

many owners have posted about their FORScan mods but provide little to no details stating they can’t remember what were the steps they performed

I'm going to make every effort to do just that, as well as a log dump after every session. One thing I learned in the PC/network game was make ONE CHANGE AT A TIME and see that the desired changes didn't screw anything else up. Not like I intend to change much, but I don't need to do them all at once.

 

[rugedraw]

You are confirming with others have stated which is that the Turn Signal Flash Count is no longer available to modify (at least in the SCCM at its former location for earlier module year Bronco Sports)

Just ran the VIN of a 2021, 2022 and 2023 BS all with co-pilot 360 and premium pack. The software strategy on each one is below and none showed a pending SCCM update in FDRS.

Ran the VIN of a 2024 BS with same specs and the strategy on that one is:

So it does appear the 2024 has different and newer firmware.

The 2023 I am getting is showing this on Ford's side (can't plug in until I get it next week to verify)

Very similar config to Quashish above.

Method 1: Modify the last byte (0090)
Try replacing 90 with the hex code for 6 flashes:
• C0 = 6 flashes (hex C = 12 decimal)
• 60 = 3 flashes (hex 6 = 6 decimal this sounds reversed but appears in some modules)

Step:
• Try changing this to 00C0 → 724-01-02: 4022 0000 00C0
• Or try 00C6 if you suspect bit position needs shifting

Method 2: Modify first nibble of 4022
4 (binary 0100) might indicate a base configuration
Try changing the 4 to C:
C022 0000 0090 → 724-01-02: C022 0000 0090

That last byte (0090) is formatted similarly to other Ford flash-count fields in newer vehicles
• It has a clean 00 + 90 structure that could encode multiple option bits including flash count, auto light delay, or steering assist options
• FORScan forum users (especially with 2023+ vehicles) report blink count has moved to other 724-01-XX locations in newer vehicles

The last two spots are place holders that FORScan will auto-fill on its own to balance the hex equation based on whatever other changes are made. You can change the 00, but the 90 cannot be changed. If you manually change it and try to write the change, FORScan will change it back. If you change any other values in any byte on that line, FORScan will change 90 to whatever it needs to be to balance the equation. That's the beauty of FORScan......it won't allow people like me that are not trained software guys to mess something up too badly.

Notice on 724-01-01 of my car and Quashish car, the only difference in the values is Xxxx xxxx xx--. Because I have an A there and he shows a B, mine ends in xxxx xxxx xx5F and his ends in 6F.

Increasing the turn signal flash count is not something I care too much about, but I don't mind being the guinea pig to test stuff out. I can see why some might be wary to experiment on their vehicles, but I'm not one bit scared to FAAFO. I get a kick out of these little projects and I'm looking forward to messing around with mine and contribute here if I can.

 

[rugedraw]

Good news! I reached out to the legend himself Livnitup and he actually has FORScan sheets for a 2022 and a 2024 Bronco Sport. I am at work and have not had much of a chance to look through them, but feel free to have at it.

(Removed links; not correct)

I am not sure if Airborne_Ape is still active on here or not, but if so, maybe he link these to the OP of FORScan thread he started here a while back.

 

[Dude]

That’s right and I did make a mistake so
I edited my post to remove changes to the 0090 because that is the checksum field (my error still shows in the post from @rugedraw because it contains a copy of my original non-edited post)

In 724-01-02: 4022 0000 0090, the 90 at the end is most likely the checksum which is a value that FORScan calculates automatically to validate the integrity of the data in that line

I looked up the procedure used to calculate the checksum but it’s a bit complex and FORScan calculates the checksum so knowing the algorithm isn’t that useful

To summarize:
724-01-02: 4022 0000 0090
4022 → first data word (16 bits)
0000 → second data word (16 bits)
0090 → checksum (the last byte)

Step-by-step:
1. Edit the data portion only:
For example, change 4022 to 406C (for 6 flashes)

2. Let FORScan auto-calculate the checksum:
The third group (e.g., 0090) will be updated automatically to match the new data

3. Write the value → FORScan validates and commits the change safely

 

[rugedraw]

Very nice, thanks for posting those two excel sheets… I’ll get a pot of coffee going and have a look at them

From taking a quick glance, the SCCM values that control the blinkers on the F150 has to do with the wipers on these trucks.

 

[jkernitzki]

Good news! I reached out to the legend himself Livnitup and he actually has FORScan sheets for a 2022 and a 2024 Bronco Sport. I am at work and have not had much of a chance to look through them, but feel free to have at it.

2022 BS FORcan sheet

2024 BS FORScan sheet

I am not sure if @Airborne_Ape is still active on here or not, but if so, maybe he link these to the OP of FORScan thread he started here a while back.

Those are for 2022 Bronco and 2024 Bronco Raptor. Though while I'm sure there is some commonality just being Ford, it's likely closer to a Ranger than a Bronco Sport.

 

[rugedraw]

Those are for 2022 Bronco and 2024 Bronco Raptor. Though while I'm sure there is some commonality just being Ford, it's likely closer to a Ranger than a Bronco Sport.

Those do look like full size Bronco information but maybe I need to study more carefully

Hmmm. I'll get some clarification from him.

 

[rugedraw]

Ok, confirmed that those sheets are NOT for the BS. He did not realize I was asking for BS in specific. The good news is, he is going to compile a sheet for us for these vehicles, but it will take 4 weeks or more before he can get it done due to a few factors. I removed the links to avoid any confusion. For now, we're working in the dark it seems.

Sponsored