Lightning Software Updates using FDRS

[rugedraw]

Disconnected the battery for 20 to 30 minutes, checked and connected vehicle toggles are on. Took it for a drive before I disconnected battery. Do you see any changes?

IPC OTA failed citing a corrupted manifest. The OTA wanted to update your IPC from the CAB to the CAC strategy, but that was on 10/4 and the OTA failed the same day.

Coincidentally, vehicle history shows that you tried updating the IPC on the same day with FDRS and that update also shows it failed. So something is going on at some level with the IPC which is why the GVMS hold is showing for you.

 

[shelnian]

Coincidentally, vehicle history shows that you tried updating the IPC on the same day with FDRS and that update also shows it failed. So something is going on at some level with the IPC which is why the GVMS hold is showing for you.

Thank you for the feedback. Seems I updated the IPC successfully and then it showed back up and failed on the second update and maybe even a third try. After the update, the battery percentage was now being displayed so I assumed it must have been a FDRS glitch. Any recommendations?

 

[rugedraw]

It could be a glitch. FDRS is not perfect....that's for sure. If you show the battery percentage on the dash, you should have the latest and greatest there. I do not have access to FDRS now to check what strategy your IPC is on, but PTS does show it is on the older version.

If you have FORScan, plug into your truck and click the IPC details and it will tell you what strategy the IPC is on.

 

[shelnian]

It could be a glitch. FDRS is not perfect....that's for sure. If you show the battery percentage on the dash, you should have the latest and greatest there. I do not have access to FDRS now to check what strategy your IPC is on, but PTS does show it is on the older version.

If you have FORScan, plug into your truck and click the IPC details and it will tell you what strategy the IPC is on.

Updated modules with FDRS. Loaded server configuration for IPC, as Mike indicated, and still shows GVMS warning. Should I open a case? IPC strategy is PL3T-14C026-CAB

 

[rugedraw]

Updated modules with FDRS. Loaded server configuration for IPC, as Mike indicated, and still shows GVMS warning. Should I open a case? IPC strategy is PL3T-14C026-CAB

Yes, I would open a case. A guy on the F150 forum had a GWM hold on his truck today, he opened a case and they cleared it out within a few hours. Hopefully they get to your quickly, too.

 

[B177y]

I am planning on doing some ForScan tinkering and wondering if there is anything to update on FDRS before I start.

1FT6W1BM1RWG22583

Thank you!

 

[Mike G]

I am planning on doing some ForScan tinkering and wondering if there is anything to update on FDRS before I start.

1FT6W1BM1RWG22583

Thank you!

All you have is an ACM update in your list right now.

 

[B177y]

All you have is an ACM update in your list right now.

Thank you!

 

[shelnian]

Yes, I would open a case. A guy on the F150 forum had a GWM hold on his truck today, he opened a case and they cleared it out within a few hours. Hopefully they get to your quickly, too.

Checked this morning and warning is still there on the IPC. Disconnected battery for a few and no change. Guess Ford doesn't want me to update it for now.

 

[shelnian]

Weirdness with your truck. It's not pulling up any connected vehicle info at all. No OTA history. No VHA history.

Is it showing any OTA or VHA history now? 1FTVW1EL6PWG51962

 

[Mike G]

Is it showing any OTA or VHA history now? 1FTVW1EL6PWG51962

It is now, yes.

Last thing was the IPC which failed on 4 Oct with a "corrupted manifest" response. It also says that the OTA was "cancelled by Ford" and "OTA will Retry"...although when that's going to happen.....

 

[BhamDCam]

Hello!

Starting this past February I started receiving updates every 2-3 weeks on average. No issues with any of them. 14 updates sucessfully downloaded and installed.

Probably a little over a month ago I was notified that 23-PU0813-DOR-UP2 was next. The next day, and every time since then, it has said the update wasn't completed.

@Mike G or @rugedraw, could one of you look up my VIN and see what is going on? TIA!

1FT6W1EV9PWG19917

 

[rugedraw]

Hello!

Starting this past February I started receiving updates every 2-3 weeks on average. No issues with any of them. 14 updates sucessfully downloaded and installed.

Probably a little over a month ago I was notified that 23-PU0813-DOR-UP2 was next. The next day, and every time since then, it has said the update wasn't completed.

@Mike G or @rugedraw, could one of you look up my VIN and see what is going on? TIA!

1FT6W1EV9PWG19917

Update was canceled by the cloud with no reason as to why on 10/11 just one day after the OTA trigger was created. It has not been resent yet.

 

[BhamDCam]

Update was canceled by the cloud with no reason as to why on 10/11 just one day after the OTA trigger was created. It has not been resent yet.

Thanks for the quick reply!

And I’m guessing there’s nothing I can do to force the update? Just sit around and wait?

 

[rugedraw]

Thanks for the quick reply!

And I’m guessing there’s nothing I can do to force the update? Just sit around and wait?

Without the mighty Mongoose, waiting and praying for the OTA gods to shine upon thee is all you can do.

Sponsored