Software Problems of Jeep Commander

Final drive control module (fdcm). Vehicle had n23 and p73 recalls completed. Sometime later, lost 4wd low. Returned to dealer for re flash per fca recall for life. Upon investigation, they cannot access fdcm due to a short; part needs replaced. Called fca multiple times and they will not cover as its hardware as opposed to software recall. There are many instances, in my research, where their recall causes the loss of 4wd low. Fca knows their "fix" was for a hardware issue and they fail to cover it. Owned Jeeps a long time and I'm done. I have six children so they maybe they can do the math on what this will cost them over generations!.

See all problems of the 2007 Jeep Commander 🔎.

After receiving n23 recall and other software updates (p73) the 4 wheel drives system disables at random. This has to be repaired at dealer. Error code points to shift actuator, but in reality it is software. If errors are cleared parts function fine. Loss of 4 wheel drive can be a life threatening. Since most of the time 4 wheel drive is needed is when not near help. My vehicle has been having this issue ongoing since 2013. Chrysler has been contacted since 2014 with starcases. Issue has yet to be resolved. Latest break down left me stranded while on vacation and having to pay for repairs. The 4 wheel drive shifting fails randomly, it can be while driving or stationary. It can happen when trying to engage 4 wheel drive or just driving down street and service 4wd system warning comes on. Error can be corrected sometimes by pulling fuse for final drive control module other times requires dealer to reapply software flash. Some dealers refuse to try this and just proceed to charge to replace shift actuator motor. . Read more...

See all problems of the 2008 Jeep Commander 🔎.

I purchased the vehicle in 2010 and within a month some electrical issues were intermittently occurring. The dealer said the ignition had to be replaced and did so. These problems seemed to continue thought not often. The symptoms are as follows-first the lights start flickering and then go out. All of the dash components go out including the speedometer, fuel gage, radio etc. The ac fan also turned off. This condition did not stop the vehicle from running it just turned off the electrical components there was however a problem with stalling, a separate issue from the electrical issue. , a few times while in the vehicle was stopped it would stall when stopping or starting off again. This was true in reverse and forward. I was never really worried about safety until last night when the lights went out while driving on a dark curvy country road. It was only for a few seconds but it was terrifying. This issue needs to be dealt with. In 2015 there were several recalls issued and they seemed to be related to the problems I was having. I had all of the recall notices dealt with. The software upgrades and the ignition replacement. This didn't solve the problem. In fact it.

See all problems of the 2006 Jeep Commander 🔎.

Tl- the contact owns a 2006 Jeep Commander 4x4. The contact stated that while driving at various speeds, especially uphill, the vehicle would independently shift into neutral. The contact also stated that the vehicle would not go into 4-lo, with the transfer case warning illuminating on the vehicles instrument panel. The vehicle was taken to an independent mechanic where it was diagnosed that the transfer case had failed and the software needed to be updated. The vehicle was not repaired. The VIN was not included in NHTSA campaign number: 13v175000 (electrical system, power train). The manufacturer was not made aware of the failure. The failure mileage was 190,000. Wh.

Tl-the contact owns a 2006 Jeep Commander. The contact stated that while driving at approximately 70 mph, the vehicle stalled. The vehicle was able to restart. All warning indicators had illuminated. The failure occurred several occasions. The vehicle was towed to the dealer for diagnostic testing. The technician stated that the may be an issue that had occurred in the software of computer. The manufacturer was notified of the failure. The approximate failure mileage was 115,000. Kc.

Tl-the contact owns a 2006 Jeep Commander. The contact stated that while driving approximately 60 mph, the vehicle stalled without warning. The vehicle was restarted. The vehicle was taken to the dealer where it was serviced under NHTSA campaign number:08v203000 (power train). The failure recurred as the service 4 wheel drive warning light illuminated. The vehicle was towed back to the dealer where it was diagnosed that the battery cable needed to be replaced. The vehicle was repaired and also serviced under a manufacturer recall for the final drive control module software update but the failure recurred on several occasions. The contact received notification of NHTSA campaign number:14v438000 (electrical system) however, the part to do the repair was unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was not notified of the failure. The failure mileage was 117,825. Ss.

After application of safety recall n23/ NHTSA 13v-175. Reprogram final drive controller module. 2005 - 2010. (wk) Jeep® grand cherokee. 2006 - 2010. (xk) Jeep Commander, the transfer case of our car could not be shifted out of 4-high to either neutral or 4-low. Consequently a major drive train component has been destroyed. This demonstrates the software is defective and potentially dangerous and may not correct the reason for the recall. This is completely unacceptable and is indeed a safety risk. Chrysler has not remedied the problem even after thousands of complaints. I demand that NHTSA force Chrysler's hand in this matter as nothing is being done to fix this faulty recall!.

See all problems of the 2010 Jeep Commander 🔎.

In may, 2013 I received recall, n23. Soon after I had the recall applied. On the first attempt to use the 4 wheel drive feature it failed. I went to another dealer who disconnected the transfer case, checked the connections and voltages and found them ok. They reconnected the transfer case and reported it operational. A few weeks later, while traveling, I received another warning that the transfer case failed. I went to a local Jeep dealer who diagnosed the problem as needing an actuator. When I returned home I went to the dealer that applied the original recall which was a software update. After they cleared the error codes they said they found a broken connector on the actuator. I assume all the manual handling of the actuator probably caused the connector to brake. I was told that the actuator had to be replaced but was on backorder. I have paperwork that indicates that the original problem found was a cracked circuit board in the actuator. How can a software update fix a cracked circuit board? could that be why there are no new actuators available? were they pulled off the market? there are many Jeep owners that I am in contact with that are having the same problem as I am and are being told the same thing by Chrysler that I that the recall did not cause the damage to the actuator. Something needs to be done to resolve this problem. Someone outside of Chrysler and the owners needs to investigate to get to the bottom.

Car turned itself off,ignition switch problem, maybe software. Has stalled on many occasions. Has had software checked by dealer and there is no other fix, they say. Is this part of the ignition switch recall problem with ignition switch? thank you!.

I received a recall notice about a week prior to this incident for nh23. It stated there were no parts to repair it and to put the emergency brake on while the vehicle is in park in the meantime which I did. On July 3rd- I took my daughter to the bmv to take her road test in my Jeep. The officer and my child stated that the car was malfunctioning and not safe to test in. We had no problem on the way there. I went out to see what could be wrong and the vehicle was surging loudly and "jumping" in place. It would not switch gears either so it could not be driven. I had it towed to my mechanic and was told my transmission was gone. I called the recall number and spoke to matthew who told me that a software glitch would've prevented this problem from being diagnosed and to have it towed to ganley Chrysler in bedford, OH. I learned on 7/9 when mike a service tech there called me requesting $936 to open the transmission. "it's a broken part in the transmission. " I asked him if it was related to the tca. He said, "what's that? let me look it up. " he then stated, "no. That's just a piece that is used to program the car. It has nothing to do with it. " I called Chrysler back and spoke with amy. I gave her the background info and she called mike. She told me "it has nothing to do with the recall. " the dealership did not know to diagnose my car once it was dropped of there. After speaking with the representative instead of doing a thorough check they maintained that the problem is that there is a broken part in the transmission and it is not r/t to the transfer case actuator. Even though the tca going bad can cause the transmission to ¿go bad� or break. I firmly believe it could not be appropriately diagnosed d/t a software glitch and that the tca needed replacing and the dealer did not have the parts as the recall stated. Why then should I pay for the repairs?.

2006 Jeep Commander. Consumer writes in regards to reprogram final drive controller module recall notice and seeks reimbursement for repairs. The consumer stated the vehicle shifted into neutral at the bottom of a hill and would not move out of neutral. She had the vehicle towed to a local repair shop who informed her there was a problem with the transfer case and recommended replacement. The consumer stated she was unaware of the final drive controller module software issue at the time. The recall notice was issued in may 2013, but she wasn't notified until September. The consumer submitted the documents along with the contact information from the repair shop, only to be told she was not eligible for reimbursement, because it was not the same issue as the recall described. She asked for clarification on the factors contributing to that determination and was informed the repair shop could not verify the issue caused by the drive controller module.

After a schedule tune up, where two coil packs were replaced, and a pcm software update was performed our 2007 Jeep Commander began stalling at slow speeds. Usually under 20 mph or at a stop when the engine is at or near idle speeds, the engine will obruptly stall without warning. There is no check engine light and no error code. Our local Jeep dealer has made several repair attempts including replacing the pcm, and shielding the engine wiring harness with aluminum foil. The problem continues. The key must be cycled to the 'off' position to restart the engine. The engine has stalled at high speeds a few times making for a very dangerous situation.

2006 Jeep Commander stalls out. While driving down the road all electrical went and steering locked up. Put back in park and cranked up. I have already had the pcm flashed with new software. And it still does it.

Tl- the contact owns a 2007 Jeep Commander. The contact stated that the key remained stuck in the ignition. The contact also stated that the vehicle stalled on several occasions. The vehicle was taken to a dealer where the ignition switch was replaced and the failure recurred. The vehicle was taken back to the dealer, who replaced the ignition cylinder and recoded the cylinder. The contact stated that three months later, the engine rpms increased and the engine warning light illuminated. The vehicle was taken to a dealer where the ignition switch was replaced and code was cleared but the failure persisted. The contact stated that the check engine warning light illuminated and the vehicle jerked. The vehicle was taken back to the dealer where the software was updated and a new computer was installed but failed to remedy the failure. The manufacturer was notified of the failure. The approximate failure mileage was 32,520. Djr.

I own a 2007 Jeep Commander at about 10,000 miles it started to stall and turn off. Dealer did not replace any parts only flushed the on board computer and updated the software. Months later it started to do the same thing. Dealer did not find anything wrong and performed the same task of flushing the computer and updating its software. Two years and 23,000 miles and the car is having the same problem. I have an extended warranty so I'm going back to the dealer, but I don't think they we fix the problem . Tr.

Jeep Commander had significant failures. Command module caused vehicle to lose all power and control while traveling in heavy high speed traffic. Sub frame mis manufactured causing vehicle to out of service for over 2 weeks. Brake rotors warped causing reduced braking.

I have a 2006 Jeep Commander with only 13,000 miles on it and it has stalled twice while driving. Dealership has seen it once and reloaded computer software to see if that fixes the problem. The second time occurred after that so it's being taken back to the dealership for review. I am nervous about the safety of my family/children.

I own a 2006 Jeep Commander and have had continuous problems with engine stalling. I have taken the vehicle to a local dealer numerous times and they have not been able to resolve the problem. The service department says that a flash update needs to be done and that it is a daimler Chrysler problem and that there is nothing they can do. My wife drives the vehicle and has had the vehicle stall on her on numerous times while sitting at red lights and it has happened as she is driving as well. I am very concerned since I have been told three different times that there is nothing that can be done at the dealership that will resolve my vehicles problem. I hope that someone is looking into the stalling problems with this particular vehicle and will do something quick to resolve this.