Did Procal mess this up

[DaddyO]

I’m in a pickle. Not the food kind. I drive a’24 badlands with Sasquatch package. I added a rough Country 2 1/2” lift and put on 37x12.5R17 Ko2’s. I recently ordered the Ford Procal 4 and had it installed by my local Ford dealership tech. Went home 25 miles-ish and it was still off by a couple of miles. I waited till the next morning to take it back for the tech to teach me how to update it and we changed the revolutions again. Went home again but when I started it the next day I got an error message on my screen that told me to Service AdvanceTrac. My mechanic friend suggested unequivocally that it just needed an alignment. Took it back to the dealership and they told me they needed to schedule it for diagnosis. I had them do an alignment anyway. Didn’t remove the message but it did drive better. I forgot to mention that I enjoy off-roading. Nothing too stupid but do slide on my rock rails on occasion. The service writer suggested that I may have knocked a front end sensor out of alignment.

So my question is, what do y’all think?

Sponsored

 

[crenca]

Confusing write up. You had the rough country lift and 37s and ProCal added at the same time by the dealership?

in any case, it’s likely your error message is related to the lift (or it is its own thing), not the ProCal or the alignment…

edit: I do seem to recall somebody setting ProCal rotations per mile settings out of range and causing four-wheel-drive errors…

edit2: dealership tech knocking sensor during alignment is possible cause of stability control (advancetrac) error

 

[DaddyO]

I added the lift some time ago. Just wanted to make sure you knew it was installed as those are the only mods I’ve done that might affect anything that I know of.

 

[DaddyO]

Confusing write up. You had the rough country lift and 37s and ProCal added at the same time by the dealership?

in any case, it’s likely your error message is related to the lift (or it is its own thing), not the ProCal or the alignment…

edit: I do seem to recall somebody setting ProCal rotations per mile settings out of range and causing four-wheel-drive errors…

So what is the correct setting as I have adjusted several times and now threw out into 5 mph difference

 

[crenca]

I added the lift some time ago. Just wanted to make sure you knew it was installed as those are the only mods I’ve done that might affect anything that I know of.

look up the bfg’s claimed revolutions per miles for those KO twos and enter that into the ProCal to make sure you have not entered some funky number that is out of range.

using a GPS app on your phone that tells you your speed (say on the highway), you can then tweek that number for more accuracy. Tires manufacturers claims of revolutions per mile are usually close, but not precise.

you can look that number up on BFG’s website, discount tires website, or similar

 

[crenca]

Beyond verifying reasonable revolution per mile settings in ProCal, the next step IMO would be to get DTC codes from the Bronco. Do you have Forscan or access to a DTC reader? If not go you your local Auto zone/O'Reilly etc. and have them print out all your DTC codes.

If it is a sensor problem (DTC codes should point that out) I'm cynical that "off roading" is the original cause, just as likely is the dealership themselves knocking a sensor around/loose during the alignment. "Suggest" that to the service writer

 

[Brian_B]

look up the bfg’s claimed revolutions per miles for those KO twos and enter that into the ProCal to make sure you have not entered some funky number that is out of range.

The number you find on the vendor website will almost always not be calibrated in ProCal or Forscan - often they will be waaay off. Part of that is tires pulling their diameter with no weight at some random PSI, the other part is Forscan doesn't exactly do math/conversions properly. It's a good place to start, just don't expect it to be "the" right number.

Dialing in the speedometer, the best method is to just get a GPS Speed app on your phone and tweak the number until you get it where you like it.

 

[Brian_B]

the next step IMO would be to get DTC codes from the Bronco.

If you haven't already pulled the battery cable for a few minutes to reset everything, pulling codes absolutely should be the second step. Or maybe even the first step, and see if it clears second.

Pro Tip - the ProCal module can read DTC codes, but only for the engine. So it sucks, don't rely on it for reading codes, it misses 90% of the modules.

There are a lot of things that can cause 4WD error. ProCal does have a loose association with the FAD on the m190 axle, if it got the wrong firmware it ~could~ throw this code -- although you have SAS and shouldn't have anything to do with an FAD, so that's just a remote possibility.

A decent third step would be to use the ProCal module and go back to stock tune, see if the error clears. You can easily swap between no tune and tune with the module with no affect to the warranty or anything else, takes about 5 minutes and all you have to do is plug it in and hit the button (and push the Ignition button when it tells you a few times); I highly recommend putting your battery on a tender while doing so though.

 

[JL8jeff]

You may want to try resetting the tire size back to where it originally was. I went to the BFG 37's and now my speedo is actually correct without changing anything with the Procal. I have the tune installed, but never touched the tire size. I could tell the speedo was reading a little high with the stock Sas tires based on all the speed traps I went past and normal traffic.

 

[GA2Dr]

Im not sure if ProCal requires it but when I changed my tire size via ForScan (did it yesterday) you need to do module re-learns for ABS and PCM I believe. Without doing that when you change the tire size it throws 4x4 and other codes. Not sure if this is related to that but something to consider.

 

[DaddyO]

Beyond verifying reasonable revolution per mile settings in ProCal, the next step IMO would be to get DTC codes from the Bronco. Do you have Forscan or access to a DTC reader? If not go you your local Auto zone/O'Reilly etc. and have them print out all your DTC codes.

If it is a sensor problem (DTC codes should point that out) I'm cynical that "off roading" is the original cause, just as likely is the dealership themselves knocking a sensor around/loose during the alignment. "Suggest" that to the service writer

Unfortunately I don't have Forscan or a DTC reader. Ill try heading to either Autozone or O'Reilly. Thanks. And yes they already suggested it might be a sensor issue. It obviously wasn't during the alignment bc I have an appointment for tomorrow for diagnostics.

 

[Brian_B]

Unfortunately I don't have Forscan or a DTC reader. Ill try heading to either Autozone or O'Reilly. Thanks. And yes they already suggested it might be a sensor issue. It obviously wasn't during the alignment bc I have an appointment for tomorrow for diagnostics.

I haven't ever seen one at the typical auto parts stores, but I'd recommend getting one that's Forscan compatible out the gate. But you can get those guys to do a free code scan! No sense in buying a code reader and then getting a second adapter for Forscan.

I am kinda kicking myself that I had to do that for FDRS, but it's kinda nice having a wireless dongle to use for info while driving and a wired dongle for big updates when you need them.

 

[GI_Jo_Nathan]

Check to see if your speedometer calibration is set below 579. It can cause weird problems for some if you do. I would write down what you are at now, then try 579. See if it helps. May need to clear any DTC's if you have any.

 

[DaddyO]

Check to see if your speedometer calibration is set below 579. It can cause weird problems for some if you do. I would write down what you are at now, then try 579. See if it helps. May need to clear any DTC's if you have any.

Is that for 37" KO2's?

 

[GI_Jo_Nathan]

No not exactly specific to those tires. But yes 37s. When I did the math for my 37" Kendas it was lower than that. But I had several weird problems. I adjusted it a couple different times higher and lower so I didn't think 579 would work but somehow it was actually right on.

Sponsored