DC must of known since Jan 22 about JK stalling problem
As you probably are aware there is a safety recall for the stalling problem on the JK. What I question is how did they fix the stall problem on the JK'S manufactured after Jan 22 if they have lead us to believe that there was no stall problem they were aware of. Does this mean that Dc has let us drive potentially dangerous vehicles all this time.......I'm pissed. They supposedly fixed the problem on the the JK,S manufactured after Jan 22 and looks like they didn't care much about fixing our stall problem until being forced to by government forces. I wonder if they will pay the damage on the Jeep that got into the accident reported on this site.
I do not know what they did or did not know, but i do know this:
Go here: http://www.jeep.com/owners/index.html
Type in the last 8 digits of your vin number at the lower left and check your recall status.
This is the result i get when i type in mine:
----------------------------------------------------------------------------------
Recall and Customer Satisfaction Notification Information:
DescriptionIssue:
REPROGRAM TIPM - ENGINE STALLING
Type:
SAFETY
Date:
07/03/2007
Status:
INCOMPLETE
Go here: http://www.jeep.com/owners/index.html
Type in the last 8 digits of your vin number at the lower left and check your recall status.
This is the result i get when i type in mine:
----------------------------------------------------------------------------------
Recall and Customer Satisfaction Notification Information:
DescriptionIssue:
REPROGRAM TIPM - ENGINE STALLING
Type:
SAFETY
Date:
07/03/2007
Status:
INCOMPLETE
Thats what I got. But I experienced the "stall" at 3900 miles. But none before that. Wierd. Have to wait and see if it happens again.
I don't think you can assume that DC knew about the bug and specifically fixed it after Jan 22. My guess is that they are making lots of changes to the software for many, many different reasons. There may have been a new release of the TIPM software made after the 22nd for other reasons and it may have had the side effect of "curing" the stall bug issue.
I'm not saying that this is definitely the case, just a possibility. My career was in software development and it is not unusual in my experience to see bugs inexplicably appear and disappear in a new release. Just a thought.
I'm not saying that this is definitely the case, just a possibility. My career was in software development and it is not unusual in my experience to see bugs inexplicably appear and disappear in a new release. Just a thought.
as i stated in the other thread.......
explain the issue to them, how severe it is, your concerns, the NHTSA complaint... and then ask them to reflash it under warranty.
i am guessing, but I would think that the split on the build date is to provide them a chance to keep from having a massive problem with scheduling appointments. the cutoff was Jan 22... my build date is Jan 23rd..... story of my life. a day late and a dollar short.
as expected, the dealership was not aware that there even was a recall, but I printed the notice out and turned it over to them.
explain the issue to them, how severe it is, your concerns, the NHTSA complaint... and then ask them to reflash it under warranty.
i am guessing, but I would think that the split on the build date is to provide them a chance to keep from having a massive problem with scheduling appointments. the cutoff was Jan 22... my build date is Jan 23rd..... story of my life. a day late and a dollar short.
as expected, the dealership was not aware that there even was a recall, but I printed the notice out and turned it over to them.
Trending Topics
I don't think you can assume that DC knew about the bug and specifically fixed it after Jan 22. My guess is that they are making lots of changes to the software for many, many different reasons. There may have been a new release of the TIPM software made after the 22nd for other reasons and it may have had the side effect of "curing" the stall bug issue.
I'm not saying that this is definitely the case, just a possibility. My career was in software development and it is not unusual in my experience to see bugs inexplicably appear and disappear in a new release. Just a thought.
I'm not saying that this is definitely the case, just a possibility. My career was in software development and it is not unusual in my experience to see bugs inexplicably appear and disappear in a new release. Just a thought.


