They're going to drag 45 hours of labor out of me before they bother an engineer. I thought it was a simple compatibility issue as soon as parameter reset failed and P060A set. And I knew it was going to be a royal PITA when I asked for tech support. Then the FSE, who had never heard of me before, started hazing me like I was a 19 year old. Asking me to do everything I said I did once more, to ask techs who make a living off of BG flush snake oil for help and to follow their directions, giving me unprovoked pointers on how to work the freaking website. I kept my mouth shut until he told me to sell the customer a cluster. Even then, he didn't back down. The cluster changed nothing. I've been diagnosing and repairing pats issues right, the first time, on time, since it's inception, longer than the FSE has or anyone else at the dealer. /end rantBOOSTEDEVERYTHING wrote: ↑2023 Nov 20, 12:30 If you used as built data to program the new pcm and not the old data from the pcm, and you performed a parameter reset, I would tell your FSE to contact engineering to investigate the files on the server. I think you are chasing a problem you may not have.
The PCM has been service parted warrantied (again) at the FSE's direction and the trans stuff is gone. It had a weak signal return- voltage measured across B+ would drop whenever I plugged in anything on it's circuit. While the new PCM fixed that, which I give zero poops about, it still has a PATS related no-start. It still sets P060A, "Internal Control Module Monitoring Processor Performance" and to seal the deal even further, this latest PCM sets U0300, "Internal Control Module Software Incompatibility". With this new info do you think they'd start looking at hardware/software? Nope. Now I'm to investigate if there's a comm problem between PCM/cluster, despite there being no network DTC's and the fuel gauge working fine, or if the PCM isn't "powering up fast enough".
It's not over yet. They may well be a magic bullet wiring problem. I've been humbled plenty of times before.