Multiple Faults No Throttle on Startup- Truck Fine after Restart

[Christopher Manns]

I get similar intermittent issues if I leave anything plugged into the OBDII. Not sure what triggers it, and like I said it's super intermittent.

 

[Nibbl3s]

Sounds exactly like mine. There are two theories as far as I can tell.
1) water in the wiring harness connector in the driver side wheel well - did you go through water recently? Mine did it after a car wash
2) the gateway module needs to be replaced. This is what the dealer ended up doing on mine.

See my thread here: https://www.fordraptorforum.com/threads/help-brand-new-raptor-won’t-start.69419/page-3#post-1389129

I will update it tonight with the outcome. I am 100% stock

I will be interested to hear your resolution. To answer your question:
1) Nope no water or rain for atleast 4 or 5 days.

I had no issues starting the truck or engine issues (other than throttle response). After I let the computer fully turn off, truck started fine and drove off with no errors. I have driven the truck today and have had no issues.

One thing I did do out of the norm before this happened was I tried to start the car with the fob. I got the red lights signaling out of range (which isn't always the case) and used the APP to start the car. I am wondering if I actually did start the car with the fob and then the signal coming from the APP caused the computer to freak out. who knows.

 

[Nibbl3s]

I get similar intermittent issues if I leave anything plugged into the OBDII. Not sure what triggers it, and like I said it's super intermittent.

Yup I am in a holding pattern I think. If it happens again relatively soon I will remove the pedal commander. If it happens after that, something else is going on

 

[smurfslayer]

I will be interested to hear your resolution. To answer your question:
1) Nope no water or rain for atleast 4 or 5 days.

I had no issues starting the truck or engine issues (other than throttle response). After I let the computer fully turn off, truck started fine and drove off with no errors. I have driven the truck today and have had no issues.

One thing I did do out of the norm before this happened was I tried to start the car with the fob. I got the red lights signaling out of range (which isn't always the case) and used the APP to start the car. I am wondering if I actually did start the car with the fob and then the signal coming from the APP caused the computer to freak out. who knows.

I’ve had this and the opposite occur several times and never had the issue you described <knock on wood>. I’ve also had Sync report it didn’t start the truck, but it did start, got the red light on the fob, but found the truck running when I got there. No errors.

I also have an OBD dongle in the truck recently because I forgot to pull it out after the last Forscan escapade and it’s been fine for ... well... months.

I’m not replying thusly to say ‘neener, neener’... rather I’m just trying to provide some data for you as a reference. I hope you get a resolution on it.

 

[goblues38]

I have a 2019 with 6K miles. Forscan and pedal commander are my only mods. No issues at all up to this point. I

You said it right there.....get rid of the pedal command junk. I have seen countless threads on various European and American car forums. Fooling around with the throttle voltage is not a good idea.

 

[TurboTJ]

I had no issues starting the truck or engine issues (other than throttle response). After I let the computer fully turn off, truck started fine and drove off with no errors. I have driven the truck today and have had no issues

So I guess the only difference mine had is that it wouldn’t start. I hit the start button and it flashes these errors
-Engine coolant over temperature
-See manual
-Park brake limited function service required
-Service advance trac
-Blind spot system fault
-cross traffic system fault
-Hill start assist not available.
-Pre-collision assist not available.
-Service advance trac
Then it repeats. It would start after I got out, locked the doors with the remote and then got back in.

The only code I saw was a P068a.

They had a Ford engineer out to look at it and they drove 50 miles without reproducing it. They replaced the “gateway module” about a week ago and I haven’t had any problems since... or maybe yet. They said that the gateway module can cause all sorts of random errors to occur and even disable the engine if one error indicates a crash.

I am at 5k miles too. I would say it’s worth a trip to the dealership. I would video it next time it happens and they will definitely try to reproduce it.

I will post the paperwork tonight that I think includes the other errors issued and communication messages in the computer.

Hope this helps!

 

[Nibbl3s]

So I guess the only difference mine had is that it wouldn’t start. I hit the start button and it flashes these errors
-Engine coolant over temperature
-See manual
-Park brake limited function service required
-Service advance trac
-Blind spot system fault
-cross traffic system fault
-Hill start assist not available.
-Pre-collision assist not available.
-Service advance trac
Then it repeats. It would start after I got out, locked the doors with the remote and then got back in.

The only code I saw was a P068a.

They had a Ford engineer out to look at it and they drove 50 miles without reproducing it. They replaced the “gateway module” about a week ago and I haven’t had any problems since... or maybe yet. They said that the gateway module can cause all sorts of random errors to occur and even disable the engine if one error indicates a crash.

I am at 5k miles too. I would say it’s worth a trip to the dealership. I would video it next time it happens and they will definitely try to reproduce it.

I will post the paperwork tonight that I think includes the other errors issued and communication messages in the computer.

Hope this helps!

Thanks for the follow up! Just read your thread, and if the truck were dying on me like yours was, I would definitely be headed to the dealer first thing

Right now, I am hard pressed to go through the hassle with the dealership telling me they weren’t able to repeat the issue.

I am hoping it was a passing startup glitch possibly due to pedal commander. If something happens while I am moving, all bets are off and the pedal commander is coming off and the dealer will be getting a visit.

Drove it all today with zero issues and multiple stops and power cycles

 

[baugustine]

Just some color to this conversation: The electronic throttles and APPs are monitored very closely by the PCM after the Toyota debacle with “unintended acceleration”. Any glitches and the PCM closed the throttle and goes into limp-in mode.

We did a Supercharger install on 2016 Shelby GT350 and the tuner got into something he shouldn’t have. We could never get the wrench light to go away and it was permanently in limp-in mode. Ended up replacing the PCM, charged back to tuner.

I subsequently discussed this with the Powertrain/OBD Manager at Ford and he confirmed what we suspected: namely any perceived “mods” to that circuit and the system defaults to LI.

I highly suspect your PC, as it is virus to the PCM and the fail-safe code inside.

 

[Nibbl3s]

Just some color to this conversation: The electronic throttles and APPs are monitored very closely by the PCM after the Toyota debacle with “unintended acceleration”. Any glitches and the PCM closed the throttle and goes into limp-in mode.

We did a Supercharger install on 2016 Shelby GT350 and the tuner got into something he shouldn’t have. We could never get the wrench light to go away and it was permanently in limp-in mode. Ended up replacing the PCM, charged back to tuner.

I subsequently discussed this with the Powertrain/OBD Manager at Ford and he confirmed what we suspected: namely any perceived “mods” to that circuit and the system defaults to LI.

I highly suspect your PC, as it is virus to the PCM and the fail-safe code inside.

I 100% agree with you. I have had zero issues since and would throw away the commander. But damn do I love it

 

[MJK]

Is it me or have several people experienced this in the same small window of time? I experienced this just yesterday and have a PC.