Automatic transmission problems at 5000 rpm - '14 Wrangler Unlimited
marwanjk2014
Member Posts: 7
Hello, I have recently purchased a 2014 new wrangler unlimited. When I got it it had 0 miles so it's brand new. I used it for 2 weeks now, and suddenly I faced a problem with my gears. When I press the gas pedal all the way down, and the jeep kick off, the rpm stops at 5,000 and from that point on it goes really slow and the jeep feels like dying. It need about 10 seconds for the motor to go from 5000 rpm to 6,500 rpm and that's when it changes gears. It wasn't like that and I have no idea what happened.
Any idea of what might have happened?
Any idea of what might have happened?
0
Best Answers
-
thecardoc3 Member Posts: 5,811The loss of acceleration sounds like an engine performance issue, and it is reasonable to suspect that the vehicle is designed to protect itself from abuse and de-power.5
-
Mr_Shiftright Member Posts: 64,481Should be a warranty issue I would think. I'd leave the part out about hitting 6500 rpm however.5
-
thecardoc3 Member Posts: 5,811The red lightning bolt sign is for the electronic throttle control. (#29 in your owners manual) so getting a check engine light, as well as traction control lamps all make sense. Now in the shop I'd take this additional information and have to start the diagnostic routine all over again. What codes were set in the different modules that control these systems? If the PCM generated a full code there would be freeze frame data that would also give me the operating conditions to assist in recreating a failure. If this is a non-continuous monitor, it could take two consecutive trips to generate a full code and store freeze frame data.
So what could it be? There isn't enough information to really say. Any attempted guess, like a synchronization issue between the TPS sensors at wide open throttle, or an issue where the volumetric efficiency isn't plausible when compared to the throttle opening and the engine rpm could be in play but taking statements like those and running to the dealership with them only serve to make more noise in an already difficult challenge. Your Wrangler is likely the only one presenting with this system issue, virtually no one else runs their Wranglers that hard so even if there is an issue they wouldn't know and wouldn't be reporting it.
You will need to drive this with the technician to be sure that it actually occurs so that they have a chance to diagnose it. Information that the tech will need is how often does this symptom occur? They need to know if they need to drive it more than what would be permitted in a normal diagnostic routine. Remember at this point the tech is likely to not be paid for any additional time that he/she spends with your car.5
Answers
The best part? If the system did generate a code, clearing it turns the light off, but doesn't completely eliminate the history of the event. Combine that with the snapshot data that is saved and the manufacturer will have a very good picture of exactly what was going on.
Meanwhile if the tech would go out and drive this in a manner that he/she could get it to act up how many people are going to stand in line waiting for their turn to criminalize the effort?
Meanwhile the tech likely got paid .3 for the first visit, and NOTHING for any repeat visits especially with "No Trouble Found."
(The WiTech)
Your best bet at this point will be to drive the vehicle with the dealer technician. The odds are that the high speed requirement might not have been passed onto the tech and even if it was there would be no shortage of people calling for the techs job if he/she got caught attempting to re-create the failure conditions.
If the tech doesn't experience the failure first hand, this will go no-where. Is there some randomness to the symptom or is it very repeatable? Is there anything else about the symptom that hasn't been mentioned such as exactly what warning lights came on? Did they stay on for some period of time before going back out? Did hey just come on, or flash?
I have the same problem too on my 2014. Anyone found the problem?