Disable Seatbelt Status on Startup?

[nowayjose]

Just got my cable today, getting the same error

Maybe the folks at ForScan can help with this. I'm speculating here, but I'm curious if there might be an issue caused by an OTA update. My truck isn't likely to get those due to the comms being physically disabled.

It's generic advice, but I'm guessing you have the newest firmware on the OBDLink and are running the newest version of Forscan available?

Sponsored

 

[scubajosh77]

Maybe the folks at ForScan can help with this. I'm speculating here, but I'm curious if there might be an issue caused by an OTA update. My truck isn't likely to get those due to the comms being physically disabled.

It's generic advice, but I'm guessing you have the newest firmware on the OBDLink and are running the newest version of Forscan available?

I am. I thought about submitting a question on the Forscan forum, but only paid subscribers can register.

 

[MAV]

Will have to try this when I get home tonight. Thank you!

Did you try the changes? Were you able to write to the IPC module?

 

[HyperM3]

Did you try the changes? Were you able to write to the IPC module?

I got out of work later than expected and totally forgot. I get out earlier today and will attempt it.

 

[HyperM3]

Using ForScan (version 2.3.62) on a '24 Ranger XLT via OBDLink EX, I was able to set the following address codes on IPC module to remove the seatbelt notification and stop any seatbelt related chimes.

DESCRIPTION	MODULE	ADDRESS	CODE
seatbelt menu & chime	IPC	720-13-01	0000-0000-0000
remove seatbelt notification requiring "OK" input	IPC	720-13-02	0000-0000
	IPC	720-14-01	0000-0000-0000
	IPC	720-14-02	0000-0000

These values were taken from a spreadsheet that I found somewhere (maybe on this forum) listing a handful of next gen ranger address code explanations within the context of ForScan programming.

EDIT: I'll try to find the link for the gdoc spreadsheet. I currently only have a locally saved PDF of it as that's what I do when I find things like this to avoid the potential of cloud resources disappearing.

EDIT2: Here it is.

I can confirm this works. I only needed to change the 720-13-01/02 for the seat belt notification in the dash to disappear. I must have done the chime delete a different way because I didnt have to do 720-14-01/02

 

[FullSend]

I can read the IPC using the latest version of Forscan, but I cannot write to it. How are you guys making changes and writing them back to the module? I get a "service interrupted" error every time.

I had the same issue as you. I was able edit all modules except IPC and was getting the same error. I emailed Forscan, sent them the log file, and the emailed back this version to download. I did and was able to make edits in IPC.

https://forscan.org/download/FORScanSetup2.3.63.test20240818.exe

 

[1986YellowRanger]

I can confirm this works. I only needed to change the 720-13-01/02 for the seat belt notification in the dash to disappear. I must have done the chime delete a different way because I didnt have to do 720-14-01/02

Has anyone confirmed that this doesn’t impact airbag deployment? Airbags often determine response based upon whether a seat is occupied as well as if a passenger is using a seatbelt.

 

[HyperM3]

Has anyone confirmed that this doesn’t impact airbag deployment? Airbags often determine response based upon whether a seat is occupied as well as if a passenger is using a seatbelt.

Interesting question, never thought about that. Only one way to test the theory....

Jokes aside, theres still parts in other modules that are enabled for seatbelt monitoring. I would like to believe this change in the quote above is literally only for the display in the screen upon startup.

 

[scubajosh77]

I had the same issue as you. I was able edit all modules except IPC and was getting the same error. I emailed Forscan, sent them the log file, and the emailed back this version to download. I did and was able to make edits in IPC.

https://forscan.org/download/FORScanSetup2.3.63.test20240818.exe

This version worked for me! Thank you!

 

[FloppyKnockers]

First post here. I had to create an account just to say thank you to all the contributors on this thread. I just got my Ranger a few weeks ago and quickly got annoyed at the seat belt pop-up. I'm no stranger to Ford or FORScan, so I knew there had to be a way. Although I ran into the same error as others, the test version of FORScan worked like a champ.

Thanks again and we'll see you around the forum.

 

[BigMeatsBronco]

@Bmadda check out this thread

 

[Bmadda]

I had the same issue as you. I was able edit all modules except IPC and was getting the same error. I emailed Forscan, sent them the log file, and the emailed back this version to download. I did and was able to make edits in IPC.

https://forscan.org/download/FORScanSetup2.3.63.test20240818.exe

This worked for me as well! Thanks!

 

[pablo94sc]

Is this the dongle most people use for FORscan?

https://www.amazon.com/gp/aw/d/B081VQVD3F/ref=ox_sc_saved_image_2?smid=A1C2436WDJ39HA&psc=1

 

[FloppyKnockers]

Is this the dongle most people use for FORscan?

https://www.amazon.com/gp/aw/d/B081VQVD3F/ref=ox_sc_saved_image_2?smid=A1C2436WDJ39HA&psc=1

Saw that one, but I got this one instead. Almost half the price and worked just as well.

 

[scubajosh77]

Is this the dongle most people use for FORscan?

https://www.amazon.com/gp/aw/d/B081VQVD3F/ref=ox_sc_saved_image_2?smid=A1C2436WDJ39HA&psc=1

Yes, exact one I bought

Sponsored