GM Power steering control module programming
Has anyone else been having issues programming or reprogramming power steering control modules on newer GM vehicles? Some time ago I attempted to update a late model GM truck due to the vehicle showing a service power steering message even after no faults remained. There was a TSB for this. I was unable to program the module. I received an error message before programming ever started. Today I am trying to program a power steering control module on a 2017 Impala and I am having the same issue. I can communicate with the new module, I attempted the programming with multiple interfaces (Cadaq Plus2, Tech2) with the same results. I did not see any specific instructions in service info for programming these modules.
The only device we have gotten to work on these is the MDI2. I had the same problem numerous times until I got an MDI2. If you have a Bosch VCI or an MDI. That may work as well. Seems like we did a 17 with the mastertech VCI also
Thanks Sam for the info. I was wondering about that. I wonder if a call to the GM Helpdesk is even worth it (Especially with the chaos that is going on right now). A friend of mine called on Thursday and their mailbox was full. I have a few more interfaces I can try on monday. Unfortunately, an MDI2 is not one of them. This exact issue is a discussion I have had many times with people. Not all
I just made a business decision a few years ago. Doing mobile programming I wanted to make sure I wasn't setting myself up for failure. I have a vcm, vcm2 for Ford. Drb3, star mobile and WiTech for Chrysler. Tech1, tech2, mdi, mdi2 for gm
Hi Benjamin. The Help Desk only deals with known validated devices, so don't expect any discussion or support for equipment not listed as being supported. While other devices may work, GM only provides support for those with proven validation, whether it be your laptop meeting standards, pass through device and cables. I see further down the page, that you have ordered an MDI 2. It can be set
Preferred yes, that said I have had no issues programming without a cabled connection to the PC.
This is the reason I purchased an MDI2.
I just ordered an MDI2 and it will be here on Monday. Thank you all for the advice. I have a Ford VCM2, Tech2, drb3, micropod2/wiTECH, and soon to be a MDI2. I will update when the job is completed.
Hi Benjamin:? A tech 2 probably won't be of any help with this vehicle. What was the error code? (I want the "4" series code. The "6" series doesn't help me.) Let me see that/them. If it is what I think it is, I'll tell you a story and, perhaps, save you some time.. HTH, Guido
I would love to see the error code diag path.
Hi Justin: I'm not sure if I understand your post. Can you clarify it please? TIA, Guido
You want the error message from the programming failure to tell him what failed right? That is something I would like to learn about how to research that.
I know one of the errors was a E6961 But there was also a 4 series error. I believe it was a 4491 or 4423 error. I know it was one of these but I do not remember which one.
Hi Benjamin, Not sure if you’ve seen this post or not, but it might be a good reference regarding those failure codes:
I don’t currently have that, but the programming never started. I still had communication with the module and data was normal. I can run through the process again on Monday to get you the screen shots.
Hi Benjamin: You didn't help yourself by not noting the code. Whether, or not, the programming started is irrelevant. The failure code is a guide to why the session failed. Scott posted a link to some of the more common failure codes. (That should've answered Justin's post also.) I fully expected the … when you attempted to use the Tech 2. What I wanted to see is if you had a 4398. I
Anthony, My coin phrase is "It's easy until it isn't". My experiences with Delco helpline for programming are varied. In homage to Riggle "It depends". If I have an issue it really depends who is on the other line. I have had to hang up at times and recall and get a different adviser and things get resolved quickly. For the most part they are extremely helpful. I have found however if you
I did not have a 4398 eror. I did refer to the GM error chart when I was with the vehicle. I fully suspect my problem to be an interface issue as mentioned above. I am positive it was a E4491/E4423 The failure was the same as if you unplug the interface and forget to plug it back to the dlc (which I have done before by having to hook up a scan tool to read current part numbers on a Radio in
According to the code information for that code it is probably NOT a communication issue. Here is the relevant text from what Teddy posted. - E4491/E4423 – Programming Failed. This error can be hard to diagnose, because it means that the application can communicate with the module but the it is unable to write all or part of the calibration due to an incompatibility. The most common cause of
I agree Bob that it is not a communication issue. I can communicate with the unprogrammed power steering control module with all of my aftermarket scan tools, and in fact there is a PID that says it has not been configured with SPS. Since I have run into this two times now I suspect there may be some liability issues programming an electronic steering system with anything other than what GM
Hi Benjamin: If you find that you still have this code after attempting to program it with the MDI-2, 2 other thoughts come to mind: 1: A consolidated part number where the calibration doesn't like the internal identification of the part. I understand that you're not replacing the part but GM may've and "forgot" to change/modify the cal. In effect, the eliminated the old "new" calibration but
Here are my thoughts on this. There is a ton of risk and the liability falls on GM when programming electronic power steering systems. I have a feeling they may have it disabled unless an authentic GM interface is used. all interfaces contain firmware from their manufacturers. The risk for hacking is always a possibility. We all know about Chrysler and their secure gateway module. It would make
Something I thought of reading through the post. Does the vehicle have an aftermarket radio or a suck blow? Any other aftermarket devices? Did you attemot to program any other modules?
Hey Sam, the car is completely stock. No add ons. I did not to attempt to program any other modules on saturday.
Benjamin - I did a 2016 Silverado with Cardaq M a few weeks ago no issues....
I went back today and had the same result using an MDI2. I called the Helpdesk found the part number is correct, and that they really don’t know why it’s not programming. The help desk logged in remotely to my laptop and suggested I make some changes on my laptop and retry (I have had zero issues programming the 10 other GM’s I have done last week.) I will do what he said and try one more time
Hi Benjamin: From the FWIW Dep't: It appears this vehicle uses an SDGM. Since you now have an MDI-2, did you look to see if a module, using the DBDT, is not communicating? Marty posted some examples using the low speed network. Here's a link for all of them. diag.net/msg/m1ti12dko1…; I'm curious if you have a network communication issue but don't know it. HTH, Guido
Hey Guido. This vehicle was wrecked (minor) and is from a body shop. I performed a full system scan and found nothing outside the ordinary. All faults were past faults and most faults were set during teardown. I will try to further study the Data Communication diagrams tonight and see if I am missing anything. Since I have no active “U“ codes, or any active faults, I don’t suspect this is the
Hi Benjamin: Any further information? FWIW, I have 4 or 5 customers who have experienced similar issues in the past couple of months though with different modules. The only thing they have in common is that they were able to outsource the vehicles to the GM dealership and the modules were programmed. I am most curious about what is going on. In my …e, if I'm not there or can't log in
Hey Guido, i tried eveything I could think of. The GM help desk wasn’t much help and the car ended up going to the dealer where it was programmed without any issue.
Anthony and Benjamin, This is where you end up in "no mans land". I feel for all parties involved. This is a classic situation where we will never get the true answer. But, I have been involved in a similar scenario years ago. Things to remember with the GM helpdesk is that the people we speak to are the aftermarket support. Across the hall is TAC which is the OE support. Most of the time GM
Yes John it is maddening. The man I talked to at the help desk was very friendly. He logged in remotely and preceded to point out every flaw he could find with my laptop such as optional windows updates, even though I have successfully programmed hundreds of GM vehicles using the same laptop With zero issues. I knew this wasn’t my issue. My concern is that I also had this same programming issue
Update: I know this is old, but I am positive at this point that there is something on my laptop that is preventing programming on 2017 model year GM vehicles. I was called to program a a new restraint control module on a 2017 Silverado. It failed the same as this 2017 Impala. I was able to program a blind spot monitor system on a 2018 Impala with zero issues. It seems to only effect 2017 model