Originally Posted by Mookie10
I had same problem and took in to dealer for service on this issue last week. They told me something had to be replaced because it was not receiving a signal or something. They did not know when part (HRF?) would arrive, but it is on order.
Funny, but after they took it all apart, the uConnect started working again!
This is a sore spot for me having worked on the receiving end of this whole "parts" chain.
I doubt things have changed much but 10 years ago when I was setting up the systems for our parts depot (large, global telecom company) well over 90% of the parts that came back from the field tested perfect and 97.6% of these same parts that were identified by one field tech to be defective were repackaged and sent out on other service calls with no issues.
The problem is typically connector or connection related but if the computer doesn't tell them to open up the panel, disconnect then reconnect the part before determining it's defective most techs will simply order the new part.
When we implemented the additional steps in the computerized trouble shooting protocols returned parts dropped 46%! Most of the parts that cam in were still not defective but there were now thousands fewer coming in than previously.
Bottom line, I doubt anything is broken and the action of diagnosing the problem probably fixed it (we have a closure code called "came clear while testing"). I'll bet the diagnostics computer still had the DTC from the bad connection and if the would have pushed new firmware into the system it probably would have cleared the code by fully resetting the connection and you wouldn't need to go back.