ECU module programming guide using FDRS

[Kanuck]

What exactly is a GVMS warning?

Something to do with the AsBuilts...

Sponsored

 

[rugedraw]

What exactly is a GVMS warning?

When there is a suspected config issue with the vehicle, FDRS now will put the GVMS hold on any updates it thinks may cause a problem. The only way to lift it is to open a case so engineers can review it and release the update as is or correct it before it become available to install. What sucks is that it takes longer than two days for them to do it, so it will require another license to be purchased and you can only check the status of the GVMS hold with PTS.

 

[Paul Neubauer]

When there is a suspected config issue with the vehicle, FDRS now will put the GVMS hold on any updates it thinks may cause a problem. The only way to lift it is to open a case so engineers can review it and release the update as is or correct it before it become available to install. What sucks is that it takes longer than two days for them to do it, so it will require another license to be purchased and you can only check the status of the GVMS hold with PTS.

Is this because of Forscan modifications causing issues with future updates working as intended?

 

[rugedraw]

Is this because of Forscan modifications causing issues with future updates working as intended?

I highly doubt it. Nobody makes FORScan changes to the GWM. There isn't even a tab on the FORScan spreadsheet for it. The GWM is something you don't want to mess with.

 

[Snakebitten]

Yeah, I imagine it's a new safeguard Ford has developed to address potential issues that provides them a safeguard they didn't previously have.

The number of potential combinations of various software versions is now exponentially larger than they were 4 years ago. Or 2 years ago. So I get why they might have rolled this flagging out.

 

[Kanuck]

Update:

I sent a request to have the GVMS cleared this morning and I just checked FDRS and it is released and showing in my updates. I did the update, and it went through, but as usual, did not clear....

Another thing I noticed:
I had a incomplete OTA showing in Sync since April 10, 2024. When I started the truck this afternoon, I had the OTA download icon on the screen. I checked and now it is showing completed...Will see what happens with OTA's, as I have had none since April. It was the SS-NS update that was in limbo.

Also, no APIM update has loaded in FDRS for my truck. Will check later JIC it does. I am licensed till Sat night, Here is hoping.

 

[rugedraw]

Update:

I sent a request to have the GVMS cleared this morning and I just checked FDRS and it is released and showing in my updates. I did the update, and it went through, but as usual, did not clear....

Another thing I noticed:
I had a incomplete OTA showing in Sync since April 10, 2024. When I started the truck this afternoon, I had the OTA download icon on the screen. I checked and now it is showing completed...Will see what happens with OTA's, as I have had none since April. It was the SS-NS update that was in limbo.

Also, no APIM update has loaded in FDRS for my truck. Will check later JIC it does. I am licensed till Sat night, Here is hoping.

What Sync version do your "about sync" show you're on?

Edit: Disregard.....I found your VIN. Try spamming the network scan button a few times to see if the APIM releases. It won't hurt.

 

[Kanuck]

I loaded FDRS 42.5.6 there is no network scan button... thinking about reloading 41.5.6 and trying that.

 

[rugedraw]

I loaded FDRS 42.5.6 there is no network scan button... thinking about reloading 41.5.6 and trying that.

I don't think that's necessary. The new version scans on it's own, I believe. I haven't updated mine yet.

 

[Kanuck]

Reloaded 41.5.6... it has Network Scan...mashed it a few times...nothing.. will try later.

42.5.6 does on it's own...but you cannot force a network scan. no way that I saw to make it scan.

 

[JFollow]

I just finished updating everything that I can. ABS and ACM were both updated at least 3 times. I see other have those persist as well, so I'll assume it's normal.

What's strange is initially there was an APIM, but after updating GWM (first update), it went away. I'm running the latest FDRS and have closed and opened it multiple times to try to force a network refresh since the button seems to be gone now.

Sync is 23291_Product, Revision 1049

Am I all set? or is there more to come as my truck sync's up with the servers?

Also, its it normal to have unresponsive PSCM? Seems to be happening regularly at start up. After awhile it seems OK.

Thanks to all you generous gentlemen and scholars...and if you prefer, scoundrels too.

 

[rugedraw]

I just finished updating everything that I can. ABS and ACM were both updated at least 3 times. I see other have those persist as well, so I'll assume it's normal.

What's strange is initially there was an APIM, but after updating GWM (first update), it went away. I'm running the latest FDRS and have closed and opened it multiple times to try to force a network refresh since the button seems to be gone now.

Sync is 23291_Product, Revision 1049

Am I all set? or is there more to come as my truck sync's up with the servers?

Also, its it normal to have unresponsive PSCM? Seems to be happening regularly at start up. After awhile it seems OK.

Thanks to all you generous gentlemen and scholars...and if you prefer, scoundrels too.

Your truck is reporting a PSCM code that references the attached TSB. You should be able to update the ABS. Did you get some kind of error when you tried to do it?

 

[JFollow]

Your truck is reporting a PSCM code that references the attached TSB. You should be able to update the ABS. Did you get some kind of error when you tried to do it?

Thanks I'll check out the TSB. For ABS, yep, everything seemed to go fine. No errors or anything.

 

[rugedraw]

Thanks I'll check out the TSB. For ABS, yep, everything seemed to go fine. No errors or anything.

I would try running the ABS update again.

 

[SilverPigeon]

I made FORScan changes shortly after getting the truck, one of which was to enable rock crawl mode in the ABS. Months later and when doing my first lot of FDRS updates, I had a GVMS warning on my ABS. I ignored it ?. A few weeks ago I did a second round of FDRS updates; noticed the GVMS warning had disappeared. After the update session, no rock crawl, so I added it back. I'm a 4x4 not FX4, so it seems the servers knew my vin shouldn't have it ?‍

Sponsored