Ah yes. I knew what you meant. I've done all the other ones. I could never get the GSM to clear, but if there's an actual update that makes it go away that'd be worth a license to me.
The usb does NOT need to have any interaction with online to proceed. THis is not true. I update modules all the time with no tcu at all. THe GATEWAY signs the file with no need for any internet or server authentication. Simply not true.
Alright, it was just an odd coincidence then. This happened today and is still pretty fresh in my memory. The install process must have been failing for some other reason. The USB update would show the loading animation on the Sync 4 GUI and in its final stages when it got to 14 / 14 it would fault and display a generic USB error. On the third or forth attempt after connecting the APIM to wifi it magically worked without changing anything else. I have no explanation why it happened but that’s the way it played out.
All you need is the FDRS software—the second link in Step 1.I am getting everything set up to do this update, but I have a question. Do we install all 4 steps for FDRS, or is it just the first step? Thank you in advance.
I could see why that set of circumstances would lend to an ahha moment and imply the connectivity playing a role in the success.
For kicks, have you tried a clear & retest since bringing the GWM back online?I thought I had a good theory why I encountered what I did, which is clearly wrong. Not having a comprehensive grasp on the problem or solution bugs me, but that just happens sometimes.
Now I’m focusing on what’s remaining. The reason why I updated the GWM in the first was to evaluate if it was brain dead. Now that it’s updated and showing a TCU Ethernet disconnect DTC (which it didn’t previously), I’m directing my attention to the pinpoint test for that line.
Prior to seeing this fault, it was observed the TCU and GWM communicate over CAN while Sync 4’s self diagnostics indicated a TCU disconnect which led us to where we are.
My bet is that it’s a body connector under the centre console but this may turn into a GWM swap depending on how we’re directed to proceed. I won’t have answers for another few days and is better off going in a separate thread since it’s not an FRDS programming issue, but this is where I’m at and your feedback is appreciated.
It does sound like a physical connection problem. What’s the TCU showing? Is it reporting in after a network scan and showing updated software? If so, you might want to check the TCU connections first before pulling apart the console to get to the GWM. Easier to get to behind the rear passenger-side seat.
I checked the TCU connections first because they're easy to access and I knew where it was. The TCU appears to function, reports a proper voltage. I can talk to it in FRDS, but if I'm not mistaken that's all CAN communication though. It's where I got my first glimpse of the Ethernet connection and the 26 gauge hair strands they used. It's so thin I mistook it for a fibre line at first.
Well that’s scary! Is it at least a cat6?
Well, if the TCU is up to date and reporting green in FDRS, and you’ve verified the physical connections running to it, I’m out of promising ideas. PMI might be worth trying but I’m skeptical, like you. You might try unplugging and reseating the TCU connections. I have heard of some success with that on the TCU early on.
It's more like a fishing line.
