Engine Cut out at high RPM
#21
Until someone comes up with some tech data explaining how the JK limiter works, we are all guessing.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
Last edited by ronjenx; 03-13-2013 at 03:38 PM.
#22
Until someone comes up with some tech data explaining how the JK limiter works, we are all guessing.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
#23
Until someone comes up with some tech data explaining how the JK limiter works, we are all guessing.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
My guess is it controls the rpm limit through all the same programming that would come into play if you simply backed off the gas pedal.
Nothing gets shut off.
When I have tested WOT shifting, the engine reaches an rpm limit and just doesn't go any higher. It doesn't turn off and back on, sputter, or do anything other than act like I was controlling the rpm with my foot.
http://www.bullydog.com/documents/Sp...fo%20sheet.pdf
#24
Here's a better one showing how it Limits the Fuel, Not Cut the Fuel. If you meant Limit the fuel in saying cut the fuel then Mistake is all cool. But we all know that the fuel is not Cut Off
governor - YouTube
governor - YouTube
Like we've established we don't actually know what's happened here except for the fact it is either fuel system/emissions (they are connected) related or computer related. Those are the most common problems associated with those vehicle systems. Next time I'll choose my wording more carefully
I also have that Bullydog programmer, but it's been sitting at my desk the last 6 months lol Should really get to putting it in the JK one of these days
Last edited by otservice; 03-13-2013 at 05:41 PM.
#25
It would be my thought that the "cutting out" of the engine was actually the programmed "controlled decent" of the engines rpm's. I've experienced this at speed and I can attest to it being the feeling of a total cutout, high pucker factor was attained.
At the time of incident, were there any dash codes that were put off? if there was, its a script failure issues and your ECU and TIPM needs to be reflashed. If the issues was caused at a lower rpm that should be, you need to reprogram.
The JK has 62 computer control points, which does include a MAF sensor, even on the 3.8. These control points, monitor and manipulate everything, in one way or another. The monitoring of these points gives some 240000 code points. These combined in 48,263 scripts which work together in order to achieve the good, bad and indifferent operations that make the JK come alive. The derivative of all the "crunching" is some 800 possible "trouble" codes.
The simple explanation is that very few control/monitor systems on the JK are mechanical in nature. The JK basically works off of FM. Something happens, it goes to the computer where FM is created, a resulting action takes place. That can be a change in control setting or the output of a code for something that is beyond the systems FM capability.
At the time of incident, were there any dash codes that were put off? if there was, its a script failure issues and your ECU and TIPM needs to be reflashed. If the issues was caused at a lower rpm that should be, you need to reprogram.
The JK has 62 computer control points, which does include a MAF sensor, even on the 3.8. These control points, monitor and manipulate everything, in one way or another. The monitoring of these points gives some 240000 code points. These combined in 48,263 scripts which work together in order to achieve the good, bad and indifferent operations that make the JK come alive. The derivative of all the "crunching" is some 800 possible "trouble" codes.
The simple explanation is that very few control/monitor systems on the JK are mechanical in nature. The JK basically works off of FM. Something happens, it goes to the computer where FM is created, a resulting action takes place. That can be a change in control setting or the output of a code for something that is beyond the systems FM capability.
#26
It would be my thought that the "cutting out" of the engine was actually the programmed "controlled decent" of the engines rpm's. I've experienced this at speed and I can attest to it being the feeling of a total cutout, high pucker factor was attained.
At the time of incident, were there any dash codes that were put off? if there was, its a script failure issues and your ECU and TIPM needs to be reflashed. If the issues was caused at a lower rpm that should be, you need to reprogram.
The JK has 62 computer control points, which does include a MAF sensor, even on the 3.8. These control points, monitor and manipulate everything, in one way or another. The monitoring of these points gives some 240000 code points. These combined in 48,263 scripts which work together in order to achieve the good, bad and indifferent operations that make the JK come alive. The derivative of all the "crunching" is some 800 possible "trouble" codes.
The simple explanation is that very few control/monitor systems on the JK are mechanical in nature. The JK basically works off of FM. Something happens, it goes to the computer where FM is created, a resulting action takes place. That can be a change in control setting or the output of a code for something that is beyond the systems FM capability.
At the time of incident, were there any dash codes that were put off? if there was, its a script failure issues and your ECU and TIPM needs to be reflashed. If the issues was caused at a lower rpm that should be, you need to reprogram.
The JK has 62 computer control points, which does include a MAF sensor, even on the 3.8. These control points, monitor and manipulate everything, in one way or another. The monitoring of these points gives some 240000 code points. These combined in 48,263 scripts which work together in order to achieve the good, bad and indifferent operations that make the JK come alive. The derivative of all the "crunching" is some 800 possible "trouble" codes.
The simple explanation is that very few control/monitor systems on the JK are mechanical in nature. The JK basically works off of FM. Something happens, it goes to the computer where FM is created, a resulting action takes place. That can be a change in control setting or the output of a code for something that is beyond the systems FM capability.
Regarding the MAF sensor you mentioned, you will have to point it out to me before I'll be convinced the JK 3.8 has one.
#27
This guy had a problem with his Limiter hitting a 4000 instead of the 5500, here is what they found wrong:
(yea it was the Map Sebsor vacuum line it was cracked i replaced it and it runs like brand new thanks for the input everyone .)
(yea it was the Map Sebsor vacuum line it was cracked i replaced it and it runs like brand new thanks for the input everyone .)
#29
#30
[h=1]MSD Ignition Offroad Rev Limiter for MSD6470 (Universal Application)[/h]
This Rev Control plugs directly into the 6-Offroad Ignition Control. It allows you to set an rpm limit that will save your engine from overrev damage in the event of driveline failure, a slick spot on the trail or missed shifts. The rpm limit is adjustable with special Weathertight RPM Modules and is supplied with 4,000, 6,000 and 8,000 rpm modules.
NOTE: Must be used with the MSD 6-Offroad Ignition