FINALLY, FORScan coding to disable the Seatbelt Information Screen! (CONFIRMED WORKING)

[Rokan]

Not even the case but you can speculate all you like. Can you brick a module if you aren’t careful? yes, manually by unplugging during re-write like shutting of lap top, losing power to car. Rewriting a module back to oem is peanuts. Brick an ecu and see what happens.

Coding has been around in cars for better part of 20 years it just hasn’t been a part of ford-sphere as long. VW/Audi have had obd11 for 15 years BMW has had ESYS out since 2008 it being the extremely hardest software I’ve ever used not just the language barrier the codes were complex, and none of these have ever affected warranty or any sort of problems with the modules themselves.

All you are “doing” is activating a feature the module already has programmed in it. You’re not really re writing anything you’re changing simple numbers to essentially get a desired effect mainly off or on.

Why some of you guys are on here super concerned is beyond me. If you don’t know what you’re doing let someone else do it or just leave your car alone completely if you’re that worried.
IMO it’s folks not really understanding what it is and what it’s designed to do. This is literally used in our plants in every pre delivery repair bay. Yes I say “our” plant I’ve worked for Ford for 23 years. I digress….

Sponsored

 

[SVTRIDE]

There is no doubt in my mind the NHTSA are the reason for these overbearing safety features. If you look at FORD’s vehicles or any other car companies outside of the USA, you will notice they do not have the DOOR chimes and SEATBELT Screens and chimes that we have here in the USA. The NHTSA wants the SAFEST vehicles NOT for the citizens benefit or safety but so NHTSA and American car companies do not get SUED!

More important then sucking up to NHTSA is garnering favor with Insurance Institute for Highway Safety (IIHS) https://www.iihs.org/ and their vehicle safety ratings. Ford must meet NHTSA FMVSS requirements (law) before they can sell a car…they spend a lot of money validation testing to gather their proof. All the car companies must meet the same standards. Pretty black and white.
However, things are a bit more gray with IIHS group. Their testing is a bit more subjective, creative and impacts how they safety rate cars. Maverick results: https://www.iihs.org/ratings/vehicle/ford/maverick-crew-cab-pickup/2024#seat-belt-reminders And they have the ear of the Insurance companies and buying public. OEM’s luv to advertise their vehicles IIHS ratings (so long as they’re good). They are a lobby group toward NHSTA pushing more legislated safety features in new vehicles. They’ve driven a huge amount of cost into new vehicles.

 

[EONR24]

Also wanted to check in and verify that it 100% works on my 2024 XLT tremor. It also took care of my double honk when my key is in the ignition and I exit the truck. Thanks so much for the post it was very helpful.

Other things to note that I was able to successfully change/code using FORScan:

Touch screen startup to ST (only option)

Road sign recognition (it’s the European round speed limit sign only but it does work. I don’t mind I was born in Europe so it’s sentimental to me that way not sure how to bring up USA speed limit version)

Launch Control (holds RPM right around 3k)

Eco mode

Sport mode (this is a fun and interesting one. Once you code it the auto start stop illuminates to off by default as soon as you scroll to sport.

Auto start stop (it didn’t work in BCM “easy way” so I explored a bit more and found that you need to go to PSCM easy version and change it in there. You can tell it works off the brake pedal. As soon as I complete stop in any driving mode the little @ comes on in the cluster and the car never shuts off. I can’t say for sure if going back to BCM and changing start/stop back to enabled and just trying the PSCM module to see if it’s all that’s needed but I can confirm with both of them if it DOES work.

I can confirm that in this OP post changing the door chimes and seatbelt chime the “easy” way it will not work. So you must go to as build for sure as the OP stated.

Hey ! Thank you for information as well. As you stated, the easy mode does not work for disabling the seatbelt and door chimes so I found and posted the WORKING way through the AS BUILT codes. I followed @Toinky FORSCAN FOR DUMMIES Thread and it has the easy mode speed sign recognition. I have rectangle instead of circle signs because I followed his easy mode coding. The only way I know to disable auto stop start is through AS BUILT.

Does the launch control in fact work? I see an AS BUILT coding to change the RPM for it and to enable it? Did you turn on launch control through easy mode? Have you tested it??

ALSO, I just found a new AS BUILT coding I will share later that enables Ford Performance MYVIEW speedometer. I will be sharing it here soon. I am about to make a Maverick Forscan Spreadsheet because ALL OF THESE CODING CHANGES NEED TO BE IN ONE PLACE!

 

[Rokan]

In the VW and Audi community we have been coding out the seatbelt chimes for years. We would change the settings from USA to ROW (Rest of the World) and this would remove the seatbelt and door chimes. LOL.

Yeah obd11 is so refined you can do it with your eyes closed. Esys has come a long way but man in the early days it was easy to brick stuff (never happened to me).
Like you said we’ve been doing this for years. However I will add this, you are responsible legally to sell the vehicle in oem condition if an issue does arise they can come after you. Long story short return all legal crap and warnings and prompts back to oem. Text messaging was a big on in BMW’s you can get it to read on your screen fully, video in motion too. I put all that stuff back when I’m done with the car. Coding is fun and to each his own.

 

[Rokan]

Hey ! Thank you for information as well. As you stated, the easy mode does not work for disabling the seatbelt and door chimes so I found and posted the WORKING way through the AS BUILT codes. I followed @Toinky FORSCAN FOR DUMMIES Thread and it has the easy mode speed sign recognition. I have rectangle instead of circle signs because I followed his easy mode coding. Like you said AUTO STOP START only can be coded through as built too!

Does the launch control in fact work? I see an AS BUILT coding to change the RPM for it and to enable it? Did you turn on launch control through easy mode? Have you tested it??

ALSO, I just found a new AS BUILT coding I will share later that enables Ford Performance MYVIEW speedometer. I will be sharing it here soon. I am about to make a Maverick Forscan Spreadsheet because ALL OF THESE CODING CHANGES NEED TO BE IN ONE PLACE!

I was able to code auto start stop by using easy mode and didn’t use as built, in my case
I disabled it in PSCM and BCM and it worked

Right now launch control holds about 3000 rpm before the change it was like 1800 and the car wanted to buck. I haven’t really beat on it I just tried it once it only has 430 miles on it. I’ve had it for like 5 days.

Really looking forward to your newest find when you post it.

 

[EONR24]

I was able to code auto start stop by using easy mode and didn’t use as built, in my case
I disabled it in PSCM and BCM and it worked

Right now launch control holds about 3000 rpm before the change it was like 1800 and the car wanted to buck. I haven’t really beat on it I just tried it once it only has 430 miles on it. I’ve had it for like 5 days.

Great. Thanks for sharing this information!!!

 

[Rokan]

Thanks, I finally got rid of that annoying seatbelt screen. I have a '24 Lariat Tremor, I changed 720-13-01 and 720-13-02 to all zeros, when I saved it the last set of numbers changed from 80AD and 207D to 003B and 003C. It also changed 720-14-01 from 2000 0000 005C to 1000 0000 004C and 720-14-02 remained the same.
Factory:

No seatbelt screen:

XLT TREMOR here and yep my checksum numbers are the same as yours it all works fine.

 

[Rokan]

Great. Thanks for sharing this information!!!

Oh any idea why the road sign recognition shows two? One works as it shows 30 and the other just stays blank any ideas why two are even needed? Here’s a quick photo notice on the right hand of the speedo it’s a blank circle.

 

[TheShark]

Oh any idea why the road sign recognition shows two? One works as it shows 30 and the other just stays blank any ideas why two are even needed? Here’s a quick photo notice on the right hand of the speedo it’s a blank circle.

https://www.mavericktruckclub.com/f...od-confirmed-working.9399/page-31#post-748132

Sounds counter intuitive but the Traffic Sign Recognition (TSR) is disabled but enable Speed Limit Information Function (SLIF)

 

[EONR24]

Oh any idea why the road sign recognition shows two? One works as it shows 30 and the other just stays blank any ideas why two are even needed? Here’s a quick photo notice on the right hand of the speedo it’s a blank circle.

@TheShark is 100% right. Check out @Toinky FORSCAN FOR DUMMIES thread. His Traffic Sign Recognition section helped me to get it working correctly!

Also, any idea why this coding below was working for some people and not for others? I really don't understand. I removed this from the original post because it wasn't working for everybody, but from my research, ALL Mavericks have the same factory coding for these 4 lines of coding. Do you think it's a checksum problem? Maybe the spreadsheet is inaccurate?

This is to keep the Minder (the dash light and chime) and not the Monitor (the seatbelt screen) based on this spreadsheet and my original coding in my Maverick.

720-13-01 9100 0001 8000
720-13-02 0110 1000
720-14-01 1000 0000 0000
720-14-02 0000 0000

 

[Mavrik23]

It’s weird the other way isn’t working for everyone. Every single maverick with varying trims has the same exact coding from the factory for these 4 lines. I might ask @Mavrik23 and see what his codings look like now! I think maybe Forscan is incorrectly calculating checksums possibly!

This is what I have. I changed the 1st 4 numbers from 9100 to 9000 after reviewing the codes so generously posted. The checksums seem to be auto-generated.

 

[Mavrik23]

It’s weird the other way isn’t working for everyone. Every single maverick with varying trims has the same exact coding from the factory for these 4 lines. I might ask @Mavrik23 and see what his codings look like now! I think maybe Forscan is incorrectly calculating checksums possibly!

This is what I have. I changed the 1st 4 numbers from 9100 to 9000 after reviewing the codes so generously posted. The checksums seem to be auto-generated.

 

[EONR24]

This is what I have. I changed the 1st 4 numbers from 9100 to 9000 after reviewing the codes so generously posted. The checksums seem to be auto-generated.

This may be the FIX! Is it still working as it should? Also why did you change it from 1 to 0 just curious? Thank you

 

[Deweyordeweynot]

Okay, but there is a transportation fee...

Sponsored