Lightning Software Updates using FDRS

[Mike G]

@Mike G Did you apply the new IPMA update to your truck yet? Did this happen to yours, too?

I did and I'm going to go out shortly and see if my 360 view is of a similar scale. I really can't remember from the last time I backed up what it looked like (4 days ago). I will post back. I was thinking that maybe a 360 camera alignment might adjust the scale of that image but...dunno yet.

Sponsored

 

[sstevetx]

I installed the new IPMA update last night on a fully charged LVB and 2 Clore 2320s. Partway through the update one of my Clore's errored out. I couldn't get PS mode to work at the time on it and ended up putting it in 20A charging mode. Took 2-3 hours the voltage still dropped to 8.8v at times which was not fun. Really made me wish I had shelled out for the Clore 6100. Regardless, it did finish without errors. I waited a little while until I could get both Clores into PS mode and then did the PSCM update which was successful. However, it still showed up in the list after multiple refreshes and closing/re-opening FDRS.

I haven't driven it yet, but I didn't notice anything odd with the 360 camera. I'll take it to the store today and see if anything looks off. I'll report back here with what I find.

 

[Mike G]

I installed the new IPMA update last night on a fully charged LVB and 2 Clore 2320s. Partway through the update one of my Clore's errored out. I couldn't get PS mode to work at the time on it and ended up putting it in 20A charging mode. Took 2-3 hours the voltage still dropped to 8.8v at times which was not fun. Really made me wish I had shelled out for the Clore 6100. Regardless, it did finish without errors. I waited a little while until I could get both Clores into PS mode and then did the PSCM update which was successful. However, it still showed up in the list after multiple refreshes and closing/re-opening FDRS.

I haven't driven it yet, but I didn't notice anything odd with the 360 camera. I'll take it to the store today and see if anything looks off. I'll report back here with what I find.

When you get a chance go back in and do a PMI on the PSCM. You don't even need the powersupply for that at all if you let the truck warm up for about 15 minutes beforehand.

Let us know if your PSCM clears off the list after that. It should.

Oh, and if you check the manifest for the PSCM update ("C:\ProgramData\Ford Motor Company\FDRS\fdrs\data\application_manifest\G2315888" and look for your VIN JSON file) and open that with notepad you see that the revisions of the packages/strategy that are shown are newer than what FDRS shows you currently have in the detail section for your PSCM in FDRS. That's a clue that the update didn't actually happen. And the reason that I'm suggesting that you do a PMI to force this update. When I did this (PMI) my software revisions/strategy actually matched what the manifest said afterward and I knew the update was successful...and it dropped off the list.

One PL2320 erroring out might be happening if both are plugged into the same outlet power source. I don't know that's the reason but it might be.

 

[chillaban]

This issue seems to be within the update itself. @ChrisCon reported the same thing when he did it to his truck here:

https://www.f150lightningforum.com/...programming-guide-using-fdrs.8249/post-360165

@MickeyAO Also reported this happening. I don't think that this is a change Ford wanted to execute as part of this update. You didn't do anything wrong and the update installed fine. There is no way to "fix" this because nothing is broken. Looks the error is on Ford's side.

Okay that’s a relief. Hopefully a future APIM update or something scales the image correctly. It’s not a huge deal as long as it isn’t some sort of error on my part during the upgrade. Would rather have the new BC algorithms as a 1.0 user. We take a Lightning and a newer Tesla frequently and it’s such a reminder that though BC 1.0 hands free is nice, the lane holding capability isn’t even close.

 

[chillaban]

I installed the new IPMA update last night on a fully charged LVB and 2 Clore 2320s. Partway through the update one of my Clore's errored out. I couldn't get PS mode to work at the time on it and ended up putting it in 20A charging mode. Took 2-3 hours the voltage still dropped to 8.8v at times which was not fun. Really made me wish I had shelled out for the Clore 6100. Regardless, it did finish without errors. I waited a little while until I could get both Clores into PS mode and then did the PSCM update which was successful. However, it still showed up in the list after multiple refreshes and closing/re-opening FDRS.

I haven't driven it yet, but I didn't notice anything odd with the 360 camera. I'll take it to the store today and see if anything looks off. I'll report back here with what I find.

Yeah I had a malfunction leave me with 30A and it also dipped to 8V in FDRS. Not sure if it’s the Mongoose but FDRS shows a volt lower than reality for me. So it was really dipping to mid 9 volts and then once in a while I hear a whirring from underneath the truck and that pops the voltage to 12V for a brief bit before it starts dipping again.

Long story short, seems like the Lightning’s HVB to LVB charger does seem to be active during this update and saved my ass. I wouldn’t rely on this as I’m sure certain updates really do turn off the HVB’s functions.

 

[Mike G]

Yeah I had a malfunction leave me with 30A and it also dipped to 8V in FDRS. Not sure if it’s the Mongoose but FDRS shows a volt lower than reality for me. So it was really dipping to mid 9 volts and then once in a while I hear a whirring from underneath the truck and that pops the voltage to 12V for a brief bit before it starts dipping again.

Long story short, seems like the Lightning’s HVB to LVB charger does seem to be active during this update and saved my ass. I wouldn’t rely on this as I’m sure certain updates really do turn off the HVB’s functions.

I read somewhere and have spent the last 15 minutes looking for it...that you should not let the voltage dip below 10.0V...although all the programming guidance from Ford that I have (all the TSBs, etc) say to set the powersupply to maintain 12.6-13.6V.

 

[Mike G]

So I just went out to check the 360 view during backup....I guess this is the new normal? You can certainly see a lot more around the truck but I would prefer to see obstacles that are nearer. It's kindof hard to judge just how far away you are from an obstacle unless you took the time to stop and zoom in to check.

 

[chillaban]

I read somewhere and have spent the last 15 minutes looking for it...that you should not let the voltage dip below 10.0V...although all the programming guidance from Ford that I have (all the TSBs, etc) say to set the powersupply to maintain 12.6-13.6V.

Oh I absolutely believe that and confirm what others have said in that IPMA updates seem to draw well over 30 amps. But with a 30A supply I was also able to do the 3hr update without anything bricking or canceling.

Definitely don’t recommend doing what I did but I lost my second 30A PS around 25% into the first IPMA update and I figured short of running out and buying whatever 50A charger AutoZone carries, I might as well cross my fingers and see if it completes.

 

[chillaban]

So I just went out to check the 360 view during backup....I guess this is the new normal? You can certainly see a lot more around the truck but I would prefer to see obstacles that are nearer. It's kindof hard to judge just how far away you are from an obstacle unless you took the time to stop and zoom in to check.

I strongly suspect this is going to need an APIM update to scale the image correctly. The IPMA seems responsible for sending these feeds and must have changed the dimensions or aspect ratio.

 

[Mike G]

I strongly suspect this is going to need an APIM update to scale the image correctly. The IPMA seems responsible for sending these feeds and must have changed the dimensions or aspect ratio.

I think you're right. And also, I don't think a 360 camera alignment would have any effect on the problem. It looks like my cameras are in perfect alignment so I don't think doing that procedure would affect the view that I see now.

 

[chillaban]

I think you're right. And also, I don't think a 360 camera alignment would have any effect on the problem. It looks like my cameras are in perfect alignment so I don't think doing that procedure would affect the view that I see now.

I agree with you -- this seems like yet another one of those protocol incompatibilities similar to the TSB about the new SCCM and old IPMA being incompatible. And we expect BC 1.4 involves another APIM update to expose the settings at least.

I also find my view perfectly aligned (just the wrong size) and expected that if the update lost alignment/calibration it'd give a different error message or at least a DTC. Looking at the other F-150 forums it doesn't look like tiny 360 degree view is a symptom of misalignment.

I'm at least glad we're all in the same boat, and it wasn't my scary low voltage flash subtly messing something up. Or that the IPMA needed a PMI or something like the PSCM did.

 

[GDN]

So for these updates that are very hard to get installed even when you baby sit them and take hours and battery maintenance, how does Ford handle this and ever get it installed for those of us that just watch it from the couch? Can they really make this happen? Will it be inhibited for that long? Will it happen in the background and then take affect with a reboot?

 

[chillaban]

So for these updates that are very hard to get installed even when you baby sit them and take hours and battery maintenance, how does Ford handle this and ever get it installed for those of us that just watch it from the couch? Can they really make this happen? Will it be inhibited for that long? Will it happen in the background and then take affect with a reboot?

It’s not a Ford but when I had a BMW ActiveHybrid 5 it had a recall that forced it to be updated to a new “integration level”. This was 120 CAN modules each needing to be manually targeted to a specific firmware revision.

The dealership took 2 weeks to do it and billed 80 hours of labor to the mothership. Indeed it was a lot of babysitting.

This is one of many reasons why you’re probably not going to convince a dealership to do all your FDRS updates unless there’s a very specific TSB for an issue.

 

[GDN]

It’s not a Ford but when I had a BMW ActiveHybrid 5 it had a recall that forced it to be updated to a new “integration level”. This was 120 CAN modules each needing to be manually targeted to a specific firmware revision.

The dealership took 2 weeks to do it and billed 80 hours of labor to the mothership. Indeed it was a lot of babysitting.

This is one of many reasons why you’re probably not going to convince a dealership to do all your FDRS updates unless there’s a very specific TSB for an issue.

Oh - I know the dealerships aren't going to do this, but from what I'm reading into this - these very long IPMA updates are required to getting BC 1.3 or .... out to our trucks which Ford has said they are going to do. So I'm curious how this will work OTA.

 

[chillaban]

Oh - I know the dealerships aren't going to do this, but from what I'm reading into this - these very long IPMA updates are required to getting BC 1.3 or .... out to our trucks which Ford has said they are going to do. So I'm curious how this will work OTA.

Ah I see. Well most of the OTA updates appear to go faster than FDRS so I presume the bottleneck is sending the IPMA firmware over the slow Mongoose connection. I guess Mach E’s have been through this with BC 1.0 and I can’t imagine those were 3 hour inhibit updates.

Sponsored