cannot reproduce and missing track file Rotor RPM Issues

[derbarbarian]

Hey Guys, 

I apologize if this is a dumb question, but I'm having issues with the Rotor RPM, obviously you can see the rotors RPM on the MFD, but I can't seem to get it to hold in the green. I'm constantly getting a warning stating that the Rotor RPM's are either high or low, more often than not they're high. It seems like regardless of what I do with the throttle/collective I can't get them to hold in the green. I'm still working on getting everything mapped out on the TM Warthog, but this is the biggest issue I'm facing at the moment.  

[sobe]

I too am getting a constant low RPM rotor warning and cannot figure it out.

[derbarbarian]

Yeah, I'm getting the RPM warnings, I'm also getting Engine Overspeed warnings.. 

[Greyman]

Check the option for the throttle detent in the special tab.  I was having these issues when i had it set to automatic.  Maybe select the finger-lift option and see if that corrects your issue

[Zap921]

Did you disable the finger lift levers in controls?  If you did then you're probably advancing past the fly zone on the throttle quadrant which disables the governor (so to speak).  

[Talonfox]

3 hours ago, Zap921 said:

Did you disable the finger lift levers in controls?  If you did then you're probably advancing past the fly zone on the throttle quadrant which disables the governor (so to speak).  

In addition, it may be helpful to keep an eye on the torque value in the upper left corner, If you pull more torque than the "governor" allows,  you will get a "rotor RPM low" annunciation. On the other hand, I can think of two scenarios which result in "rotor RPM high" : 1. an engine overspeed, and 2. rotor coning which occurs when excessive aft cyclic causes the rotor blades to flex upward and the rotor to spin faster. You can see the physics in action as an ice skater pulls their arms inward during a spin resulting in a velocity increase.

Bottom line: Keep an eye on the torque and remember that a helicopter doesn't work the same way as DCS's high performance fixed-wing fighters. 

Good Hunting

[salsantana]

There's quite higher incidence of "rotor RPM Low" than "rotor RPM High" throughout this page........  the "High" issues just plague me within seconds after takeoff and persist. I end up dropping collective way down, begin descending and add collective gradually, hoping the drag of blade pitch will tame the rotor speed. I've even tried lowering throttles a bit....... I think the military term for this rotor (mis)management would be something like "goat rope"

I'm quite comfortable in Ka-50 v2 and UH-1H, but the Apache's a BEAST to manage in rotor RPM alone.

Regarding the controller axis curves....... something else I'm trying is to pull "Y" saturation down to about 85% on Pitch and Roll axes....... to reduce the intensity of curve response as stick moves toward maximum...... this may be a useless idea, so I'm open to others. In another flight sim, increasing "Saturation" translates to the sensation of flying a heavier aircraft. I'd presumed it meant "intensity of response", perhaps like resonance, as stick moves toward limits but apparently not.

Here's some suggestions found in this discussion; ** denotes changes I've made and tested, with incredibly improved results:

**- pedals to "no spring" option
**- turn off "game mode"
**- stick curves to "8"
 

Hopefully someone else badgered by rotor RPM issues may realize improvements from the above.

Edited March 22, 2022 by salsantana
MUCH better flight now after changes

[Zap921]

The low rotor rpm issues are related in the same way if the power levers are not in the fly detent, the governor is not controlling the fuel flow when needed.  If the detents are in the proper position and governors are working and the user experiences low rotor rpm warnings then they are probably over-torqueing the transmissions trying to recover from something like descending to fast.  Remember high, hot, and heavy is cause for extra caution.

[Hiob]

The issue is almost certainly related to the power lever setting.

I had this problem at first, when I bound them to an axis. Without detents, you will most likely advance them to far and deactivate the governor.

Try to bind them instead to the buttons for power lever step up and down (or similar). Than you will always hit the desired setting.

The problems are gone since.

Edited March 23, 2022 by Hiob

[BIGNEWY]

As long as you have set the throttles to fly and the power has settled at 101 you should be fine, I have not seen a problem in my flights. 

[Zap921]

4 minutes ago, BIGNEWY said:

As long as you have set the throttles to fly and the power has settled at 101 you should be fine, I have not seen a problem in my flights. 

I found if you disable the finger lift levers (or whatever they're called) in Special settings then it is pretty much impossible to set both levers exactly to Fly because there is no stop any longer.  I tried numerous times in VR but was unable to get it just right to where the governor would take over.  Hope that makes sense.

 

[BIGNEWY]

Just now, Zap921 said:

I found if you disable the finger lift levers (or whatever they're called) in Special settings then it is pretty much impossible to set both levers exactly to Fly because there is no stop any longer.  I tried numerous times in VR but was unable to get it just right to where the governor would take over.  Hope that makes sense.

 

Understood, yes many throttles out there and with different tuning, so with the detent off you may need to tune your devices curve to meet the detent / fly

[Hiob]

8 minutes ago, BIGNEWY said:

As long as you have set the throttles to fly and the power has settled at 101 you should be fine, I have not seen a problem in my flights. 

I think the issue is, depending on how you set up your controls, it is pretty easy to overstep the flight position.

[S. Low]

This may or may not be related, but during take off it seems strange to me that the Torque% won’t hold, meaning as I add a little bit of collective the % will hit say 10% then drop to 5%; then I add some more and it goes to 25% and then drops back to 10%. Etc. This repeats until I hit like 45% and it drops to around 35 ish when I lift off

[Hiob]

8 minutes ago, S. Low said:

This may or may not be related, but during take off it seems strange to me that the Torque% won’t hold, meaning as I add a little bit of collective the % will hit say 10% then drop to 5%; then I add some more and it goes to 25% and then drops back to 10%. Etc. This repeats until I hit like 45% and it drops to around 35 ish when I lift off

I think that is because torque (as of engine output) is an indirect result of your collective setting. In opposite to blade pitch for example. The governor (flight computer?) needs a couple of split seconds to sort it all out.

Edit: thought about it. When you raise the collective, you increase the blade pitch, which will slow down the rotor a tiny bit. The computer needs to increase torque to bring it to the desired speed again which needs more torque than holding that speed. Makes sense to me at least...

Edited March 23, 2022 by Hiob