ECU module programming guide using FDRS

[christophers]

how many people have had USB drives "broken" from doing these updates?

i've had two: one failed internally which enabled the write protect feature. it failed in the middle of a GWM update being written to it from FDRS

the second failed when the truck rebooted with the USB drive in it. it can't even be recognized anymore so no diskpart/diskutil

Sponsored

 

[jcaspar]

You might have gotten really, really, really lucky. I would run this by @Bob_Mac before recommending this as a safe course of action. He saw something bad happen.

Not making a recommendation, just an observation. I could have gotten really lucky or the other person may have been really unlucky.

 

[JEB]

Not making a recommendation, just an observation. I could have gotten really lucky or the other person may have been really unlucky.

Given the combination of what PMIs do, the Nano’s predisposition to corrupt reporting data and the newly emerging data regarding its incompatibility with modules on certain CAN buses I think merits more warning than simply “it worked for me.” You are getting the Mongoose yourself, if I recall correctly?

 

[JasonATL]

i didnt have activation issues, but mine was opened (the seal on the box was no good) but everything else looked/felt new.

I tried on a different laptop and same issue. Guess it’s the device. Will try emailing mongoose support to see if they can help.

 

[JEB]

how many people have had USB drives "broken" from doing these updates?

i've had two: one failed internally which enabled the write protect feature. it failed in the middle of a GWM update being written to it from FDRS

the second failed when the truck rebooted with the USB drive in it. it can't even be recognized anymore so no diskpart/diskutil

That’s not good. I haven’t had that experience and I’ve been using the same flash drive since January. Is it a hardware failure (a fracture of some sort from inserting it an awkward angle) or have you pinned it down to a corruption?

 

[christophers]

That’s not good. I haven’t had that experience and I’ve been using the same flash drive since January. Is it a hardware failure (a fracture of some sort from inserting it an awkward angle) or have you pinned it down to a corruption?

it’s definitely corruption. drives were brand new, different brands.

 

[Bob_Mac]

You might have gotten really, really, really lucky. I would run this by @Bob_Mac before recommending this as a safe course of action. He saw something bad happen.

@jcaspar keep playing with fire and as @JEB stated, you were lucky. I have gotten messages from a few just doing multiple PMI's as a "Fix All" solution and that's not always the case, long story short 2 of them bricked their module(s) and had to wait on the Mongoose to resolve the issue.

 

[Shoebox72069]

how many people have had USB drives "broken" from doing these updates?

i've had two: one failed internally which enabled the write protect feature. it failed in the middle of a GWM update being written to it from FDRS

the second failed when the truck rebooted with the USB drive in it. it can't even be recognized anymore so no diskpart/diskutil

I think USB drives are mostly a crap shoot these days. Cheap NAND typically that doesn't have high levels of R/W endurance.

I have a 32GB Patriot Memory that I've had for quite awhile and it sees a lot of use. It is really a gamble these days. They are cheap enough just to have a few on hand....

 

[rpeterslll]

the big update for APIM is around 2-3GB. I have done 2GB updates in <10minutes with no issue. There's something 'stuck' that causes it, but trust me, it will work eventually. just forget about it, drive around, use the truck, and it will eventually just show up

it completed. Took about 18 hours. I left the truck running a lot todayin the driveway too. I’m not sure if it helped, but I performed a Sync reset in FDRS shortly before it started the update.

 

[jtake]

So my running boards will not respond to anything. The DSM logging does not show running boards as a testing object. They show up on my car console and I can change the settings for them, but I can find no module in FDRS that actually controls them.

I have run the configuration several times, but obviously to no avail. Same with the self test.

I have PMId it a few times and not joy either.

I am using a Mongoose.

Suggestions?

 

[Jesse-Infotainment]

So my running boards will not respond to anything. The DSM logging does not show running boards as a testing object. They show up on my car console and I can change the settings for them, but I can find no module in FDRS that actually controls them.

I have run the configuration several times, but obviously to no avail. Same with the self test.

I have PMId it a few times and not joy either.

I am using a Mongoose.

Suggestions?

The DSM driver seat module is what controls them, heated and cooled seats, electric tilt column, and adjustable pedals.

 

[imnuts]

I tried on a different laptop and same issue. Guess it’s the device. Will try emailing mongoose support to see if they can help.

Only thing I could suggest, the cable is a simple USB cable with a fancy end that goes into the OBDII portion. You could try a new USB cable if you have one lying around (maybe from an old USB printer or a monitor?). I don't know much about what the activation process does since mine was already activated, but it wouldn't take much to test out.

As far as USB drive issues, I've used two different USB drives with FDRS for updates and didn't have issues with either. I'd lean more on the drives themselves were having issues before hand, and due to the amount of sustained read/write action they got through the process, it exposed the weak point and they failed.

 

[Airborne_Ape]

I fixed my U2100 by doing PMI on my IPC with a Nano. It took about 4 times. Tried as both original and new module. It finally worked, it seems, after I did some other updates first. Can be done with a Nano but no doubt mongoose better.

Did you configure your Nano to operate at fixed baud rate? If so, what is it set at?

 

[Airborne_Ape]

I've received my Mongoose but it won't activate. It was new from Amazon but I could tell the box had been opened before. Any suggestions? When I plug in to the computer I hear the noise from Windows of a device plugged in and the green light flashes on the mongoose.

I'd check that the correct Drivers are installed and then check if a Windows or ISP firewall configuration is blocking a port the utility needs; I don't actually own one though.

 

[heffer86]

I hope I don't regret doing this. I am willing to lend out my entire FDRS setup (Computer with FDRS license until April 12, Clore Automotive PL2320 power supply, and Mongoose Plus) to anyone in the Northwest Iowa region. PM me if that's you.

Sponsored