Lare

There's a bit of confusion about the OUC (On Until Cancelled) bit--mostly mine--so I'm documenting what I found out in case anyone else has questions.

If you don't care about the methodology, just skip to the last couple paragraphs.

First off, let's get the terms set out:
I have a 2015 XLT. (Is that 13th gen? Whatever.)
This means I have a "lane change" feature which means I press lightly on the turn signal stalk and release it and the desired turn signal will flash three times (factory default).
If I press the turn signal stalk down (or up) until it clicks, then the truck knows I want to actually turn a corner. The turn signal starts flashing. When the wheel is turned and then goes back to center the turn signal will cancel (and the stalk will return to its neutral position.)

BTW, if I hold the turn signal but don't press it past the click, then the signal will flash for as long as I hold it with a minimum of the "lane change feature" number of clicks. In other words, if I press the stalk lightly (not clicking it all the way down/up) it will keep flashing for as long as I hold it in this position. Unless I let go before it hits the third flash in which case it will continue to flash until it has done so three times. I'm going to call this "manual positioning."

So there are three test parameters: (1) Lane change, (2) Turn a corner, (3) Manual positioning.

I got into Forscan (after renewing my license. Unexpected extra work but not difficult thanks to Livinitup's tutorial and Chad's video).

Checked for existing DTCs: None.

Loaded the SCCM. The value we're changing is 724-01-01 xxxx-xYxx-xx

My As-Built value is 6. This is "three flashes with OUC false." It works as I described it above.

I changed the value (the "Y" in the string) to be A. This should yield 5 flashes with OUC false.

This made it work like it did with the factory default except that there were now 5 flashes on the lane change. For the "manual positioning" part of the test, it worked as I expected: That is, if I held it for more than 5 flashes it stopped flashing when I released the stalk, otherwise it made a total of 5 flashes and then stopped.

Now for the OUC part

I changed the value from A to B. This is "5 flashes with OUC true."

The lane change feature and the manual positioning did not change from the previous (5 flash) setup. However, when using the "turn a corner" mode--which is pressing the stalk up/down until it clicks and it stays in that position until you've turned the wheel and it's gone back to center--things changed:

When approaching a corner, you press the stalk all the way down or up. You've been doing this since you first learned to drive. The turn signal starts flashing. You turn the corner, the wheel goes back to center and the turn signal stops flashing. UNLESS you have set OUC set to "true" in which case the turn signal stalk returns to the normal (neutral) position and the signals keep flashing. Really a weird sensation after many years of seeing the signal stop when the stalk goes back.

To cancel the flashing signal, tap the signal either up or down. It doesn't matter which direction you were indicating, the signal will stop flashing until your next use of the stalk.

None of this seems to affect the emergency flasher operation. They override everything.

Checked for DTCs: None.

I didn't verify each of the values as it's pretty straightforward regarding the number of flashes. If you want to leave things as they are but change the number of flashes, use the values with "OUC=false." If you want to confuse anyone you lend your truck to (you'd lend your truck out???) then the "OUC=true" values will do this.

Livnitup

Lare, great write-up! Added a link to your explanation to the SCCM spreadsheet for this feature

carrierj

Yes, I agree. Very comprehensive, and should clear up all confusion.

Thanks Lare for your contribution.

Lare

Thank you both. It's only right that I try to contribute back!

ETA: In case anyone is interested, I also used As Built Explorer to see if changing the values caused any other changes in the module. Other than the value I changed, and the checksum of course, nothing else changed (in the SCCM).

Airborne_Ape

We should just all meet up for this in Dallas this November lol.

https://events.american-tradeshow.com/araexpo/42591

TexasFording

iTrader: (14)

I'm 4 hours away. "North American Forscan Ford hacker association"

16XLT

Less than 10 min from me. I'll get the list of bars we're going to destroy ready

Airborne_Ape

Hardware ID is actually seeded off the windows user. If you have 2 users on the same computer and use the same name and phone number for both the Hardware ID will be unique to each.

Just sayin.

TexasFording

iTrader: (14)

I'm game, lets hook up and go tear em a new one!

carrierj

OK. But if he installs FORScan on another computer he will need a new extended license, was my point.