Search results

He has the VCX Nano...

The servers are down...

I do not...

I had success this morning and you should have my VIN and, back a few posts I posted the before and after the 2.5.1 update.

Yes, do the PMI and when going through the steps select that you 'DID' replace the module.

Didn't see the PowerBoost...

A couple of his are behind compared to mine, these are a before and after doing the 2.5.1 this morning: Before After IPMA IPMA <NODEID>706 <NODEID>706 <F10A>ML3T-14H106-AFJ</F10A> <F10A>ML3T-14H106-AFN</F10A> <F110>DSML3T-14G647-AF</F110> <F110>DSML3T-14G647-AF</F110>...

Or even disconnecting the battery for about 15 mins or so...

1. GWM 2. TRM 3. DDM 4. PDM 5. DSP 6. SCCM 7. CCM - This will also do the PSCM & IPMA

@ENG430 Start with the GWM first!

Yes, it occurred during the Device Check but several users reported it showing when in Debug so it mus have been a timing thing. I just confirmed your findings as well...

Nice, guess I'm getting the 2.5.1 updates... CCM, CMR, IPMA, PSCM and still have the pesky GSM so guess I'll be busy tomorrow morning. :)

Everyone, you should only run a PMI if you're stuck with a persistent DTC after an update and most importantly, DO NOT run subsequent PMI's on the same module or you're asking for trouble....

It appears Ford is doing something on their end causing issues with updates.

Send me your VIN in a message.

As @JEB said, do not use the saved profile as that itself may have issues. I am very fluent in FORScan and I will say this, I never save the profile regardless and always let it scan fresh. Message me your VIN and truck info, i.e. 3.5L or 5.0, etc... and I'll look at your AsBuilt and see what if...

@kennelh is aware, during my testing with him the other day I brought it to his attention.

It'll do the Fix Me test and was pointed out by another user

There's 4 tests total and the doc will show the fourth one.

I'm actually adding these steps now to the doc that'll be ready soon...