ECU module programming guide using FDRS

[TechAddiction]

Did you just forscan direct write?

Grab the files out of the hidden directory under program data, add .vbf to each file listed above and manually write it. You don't need the mongoose, but you do need to know the IPMA work around if you don't have it.

I have not tried that but do know how to use Forscan. I'm not familiar with the IPMA work around. What is that?

Sponsored

 

[JEB]

I have not tried that but do know how to use Forscan. I'm not familiar with the IPMA work around. What is that?

Since you already have a Mongoose on the way, it’s easier and safer to just use it to update and repair the IPMA. What @HammaMan is suggesting is using FORSCan Beta to access the calibration files you already downloaded to a directory on your laptop when you first tried to update the IPMA and then side load them into the module. It will work, but it’s not as efficient and straightforward as just using FDRS again with the Mongoose. The method is not as user friendly and I wouldn’t recommend it for a first timer and, in any event, your cloud (as-built) data will not immediately update if the IPMA is sideloaded. That could be an issue if you haven’t already updated the PSCM, which is a linked update.

 

[TechAddiction]

Since you already have a Mongoose on the way, it’s easier and safer to just use it to update and repair the IPMA. What @HammaMan is suggesting is using FORSCan Beta to access the calibration files you already downloaded to a directory on your laptop when you first tried to update the IPMA and then side load them into the module. It will work, but it’s not as efficient and straightforward as just using FDRS again with the Mongoose. The method is not as user friendly and I wouldn’t recommend it for a first timer and, in any event, your cloud (as-built) data will not immediately update if the IPMA is sideloaded.

Thanks for the explanation. I'll try with FDRS when the cable arrives. If my license says good till 21 March, does that mean by midnight 21 March or midnight 20 March? I bought the license yesterday at about 2:00pm EST for 2 day license.

 

[JEB]

Thanks for the explanation. I'll try with FDRS when the cable arrives. If my license says good till 21 March, does that mean by midnight 21 March or midnight 20 March? I bought the license yesterday at about 2:00pm EST for 2 day license.

Your license is good for the day you bought it and two full calendar days after that. So, midnight tomorrow night.

 

[HammaMan]

His IPMA was MIA entirely and PSCM was soft bricked. Loaded latest firmware on both for him. IPMA came back soft bricked once PSCM got reloaded.

That topdon cable is completely worthless outside of forscan, and there's cheaper cables for that!

 

[lojoma]

Any reason I can't use this for the battery charge maintainer? I already own so, cheap, but if it won't work I can buy something else.

 

[Ajzride]

Any reason I can't use this for the battery charge maintainer? I already own so, cheap, but if it won't work I can buy something else.

This doesn’t have a power supply mode. It would be okay for USB updates, but not anything that uses the canbus cable.

 

[lojoma]

Thanks, and what is the minimum amps should the maintainer be rated for?

 

[Kanuck]

I recommend the charger/ power supply listed at the beginning of this thread. 20 amp charger / 20 amp power supply.

 

[UNCGrad]

BCM cannot be updated without a dealer login and the ACM and PSCM do not come off the list for whatever reason after they are updated. You are good to go! The BCM will come via the OTA process eventually.

I'm at that point with the BCM and the NASTF login plus my ACM doesn't update as it states "Procedure Unsuccessful- GetVehicleNodeInfo. Direct configuration data is missing. Call holiness to resolve before continuing. "

I was trying to update everything so I could get BC 1.4 through Forscan.

As @ rugedraw knows, I am one of those that doesn't get OTAs.

Suggestions?

 

[rugedraw]

I'm at that point with the BCM and the NASTF login plus my ACM doesn't update as it states "Procedure Unsuccessful- GetVehicleNodeInfo. Direct configuration data is missing. Call holiness to resolve before continuing. "

I was trying to update everything so I could get BC 1.4 through Forscan.

As @ rugedraw knows, I am one of those that doesn't get OTAs.

Suggestions?

The ACM is known to not come off the list so ignore it. The BCM you can't do and it's not necessary for BC 1.4, so ignore that one, too.

 

[UNCGrad]

The ACM is known to not come off the list so ignore it. The BCM you can't do and it's not necessary for BC 1.4, so ignore that one, too.

Thanks for response.

Are you still having to send out the Forscan tweaks for BC 1.4 or has it been posted?

 

[JEB]

The ACM is known to not come off the list so ignore it. The BCM you can't do and it's not necessary for BC 1.4, so ignore that one, too.

@UNCGrad is seeing something different than the typical ACM failure to clear problem. Usually, the update applies normally. It just doesn’t come off the FDRS queue. She’s seeing an actual “procedure unsuccessful” error when she tries to run it. Might be worth trying again later, on a non-Sunday if possible.

 

[rugedraw]

@UNCGrad is seeing something different than the typical ACM failure to clear problem. Usually, the update applies normally. It just doesn’t come off the FDRS queue. She’s seeing an actual “procedure unsuccessful” error when she tries to run it. Might be worth trying again later, on a non-Sunday if possible.

Ah my bad. Read through that too quickly. @UNCGrad I'll send them to you.

 

[UNCGrad]

@UNCGrad is seeing something different than the typical ACM failure to clear problem. Usually, the update applies normally. It just doesn’t come off the FDRS queue. She’s seeing an actual “procedure unsuccessful” error when she tries to run it. Might be worth trying again later, on a non-Sunday if possible.

I tried it again a few minutes ago and received the same error. Is this something I can bug the dealer or does it matter?

Sponsored