ECU module programming guide using FDRS

[sstevetx]

I use a 10-year old laptop with a 4th gen Intel i7-4600u (2.1GHz dual core, quad thread) and it runs fine on it.

As far as power supply connection points, the ones under the passenger side frunk panel are the suggested ones. I often connect to the battery directly with the negative after the bms because it's easier to access.

Sponsored

 

[Riverant]

Happy to report that all my FDRS updates appeared to go smoothly. My 75a Powermax kept my LVB voltage comfortably above 12v the whole time.

I am running into an issue where FDRS isn’t clearing some of the software updates after completion (PSCM, RFA, and the front audio module). I’ve reran all and ran into zero issues but still on the list. I did clear the vehicle cache and rescan the VIN to no effect.

Am I good to just ignore these?

 

[Pitbull2o08]

What’s the consensus on Nano vs mongoose?

 

[chillaban]

Happy to report that all my FDRS updates appeared to go smoothly. My 75a Powermax kept my LVB voltage comfortably above 12v the whole time.

I am running into an issue where FDRS isn’t clearing some of the software updates after completion (PSCM, RFA, and the front audio module). I’ve reran all and ran into zero issues but still on the list. I did clear the vehicle cache and rescan the VIN to no effect.

Am I good to just ignore these?

My PSCM did clear (in the past I’ve seen this too) but RFA and ACM did not. I think you are fine to ignore them unless you got an error during programming or there’s DTCs that persist beyond initially clearing them.

 

[Mike G]

Happy to report that all my FDRS updates appeared to go smoothly. My 75a Powermax kept my LVB voltage comfortably above 12v the whole time.

I am running into an issue where FDRS isn’t clearing some of the software updates after completion (PSCM, RFA, and the front audio module). I’ve reran all and ran into zero issues but still on the list. I did clear the vehicle cache and rescan the VIN to no effect.

Am I good to just ignore these?

The ACM and RFA have been problematic since the day they came out around the middle of September. They have refused to drop off the list for everybody who've tried them.

The PSCM not dropping off, at least initially for me, was an issue I believe to do with the IPMA not being configured during it's update, and then the PSCM update taking place. What I did that worked for me was I ran the IPMA Configuration separately afterwards, which then also re-ran the PSCM configuration...and then the update dropped off the list. However, for two other forum members I was messaging this morning, that hasn't worked. They've both tried running the IPMA config to clear that update off the list, and that didn't fix it. So now I'm not sure what's going on with that PSCM update.

 

[Mike G]

What’s the consensus on Nano vs mongoose?

It's been reported that the Nano does work to perform updates. But there's a catch. Apparently (and this is anecdotal, as I don't have one) what happens is the data that is returned back to the cloud that the Nano reports ends up corrupting the Ford server side (I think it's asbuilt data they're talking about). So since the cloud data gets corrupted you aren't offered any more updates until those modules that were updated using the Nano get updated again (PMI?), using a Mongoose or VCM, or some other adapter that is fully J2534 compliant.

This is what I've seen written about the use of the Nano over the last few years and is the reason it is no longer recommended as a suitable adapter to use for updates.

The Mongoose costs what it costs because it doesn't have those issues.

 

[Riverant]

The ACM and RFA have been problematic since the day they came out around the middle of September. They have refused to drop off the list for everybody who've tried them.

The PSCM not dropping off, at least initially for me, was an issue I believe to do with the IPMA not being configured during it's update, and then the PSCM update taking place. What I did that worked for me was I ran the IPMA Configuration separately afterwards, which then also re-ran the PSCM configuration...and then the update dropped off the list. However, for two other forum members I was messaging this morning, that hasn't worked. They've both tried running the IPMA config to clear that update off the list, and that didn't fix it. So now I'm not sure what's going on with that PSCM update.

What's the process and timeline for configuration? My FDRS license is expiring shortly. Is it worth it to try the configuration or does the update clearing not matter?

 

[mr.Magoo]

However, for two other forum members I was messaging this morning, that hasn't worked. They've both tried running the IPMA config to clear that update off the list, and that didn't fix it. So now I'm not sure what's going on with that PSCM update.

Make that three, I ran the updates the other day and followed your your recommendation to run the configuration without any luck getting it cleared/removed from the available updates.

 

[rugedraw]

Make that three, I ran the updates the other day and followed your your recommendation to run the configuration without any luck getting it cleared/removed from the available updates.

Yea, I recommended the IPMA config procedure to several people based on Mike's experience and it does not seem to clear the PSCM from the list. I would not stress it, though.

 

[shelnian]

What’s the consensus on Nano vs mongoose?

I use one of these. Performance matches the mongoose. Recommend updating firmware with VCI Manager before using.

 

[rugedraw]

I use one of these. Performance matches the mongoose. Recommend updating firmware with VCI Manager before using.

And I would strongly advise you or anyone from using that tool. If you used this and nothing bad happened, consider yourself lucky.

 

[shelnian]

And I would strongly advise you or anyone from using that tool. If you used this and nothing bad happened, consider yourself lucky.

It's a cloned VCM2, that's why VCI Manager can load the latest Bosch firmware onto it. I've used it with absolutely no issues, including updating the IPMA and PSCM modules. Also use it with FORScan.

As the ad indicates, you shouldn't use the cheaper single board clones for updating modules, they only work well for diagnostics.

 

[rugedraw]

It's a cloned VCM2, that's why VCI Manager can load the latest Bosch firmware onto it. I've used it with absolutely no issues, including updating the IPMA and PSCM modules. Also use it with FORScan.

As the ad indicates, you shouldn't use the cheaper single board clones for updating modules, they only work well for diagnostics.

I see what you're saying....I read it wrong. I still wouldn't go this route personally, but I do see what you're saying.

 

[Pitbull2o08]

I use one of these. Performance matches the mongoose. Recommend updating firmware with VCI Manager before using.

Why use this instead of the $100 nano?

 

[Mike G]

Why use this instead of the $100 nano?

There are a lot of reasons and at least one of them I already posted in response to your previous post about it.

You can do a search on the ICE forum and easily come up with threads like this.

Or maybe this post from one of the legends in the area of programming.

It's been said many, many times before. You can use the VCX Nano but if you do there's a very good chance that the data it reports back through the interface to FDRS, and ultimately back to the cloud will be corrupted. Which means your vehicle won't be offered future updates for that module until a PMI is done with a compliant device to sort it out. And there are certain modules that if programmed with the Nano will be bricked.

Sponsored