Hi,
the reason is quite complex. OMP has one non-updatable product, which has to work only on one platform, and they did, like, one thing right'er' than us, plus they don't really use a governor.
We have a product which is updatable, and which is used on all kinds of helicopters.
Making such a change to the tail control loop (which is a core feature and the same in _all_ NEOs around the world) would very likely mean (or at least bear the risk) that everybody who does _that_ update has to adjust his tail settings again, or run into unexpected issues. Even the majority who doesn't even know about it, or need it, ever.
Job-creation measure for me, because even if there was something to read up on, there would be why's.
All that just because of the comparatively limited number of pilots who want or need it.
Please don't take it personally, it simply makes little sense to us, to put much effort into what seems like side issues, while there are more pressing issues, among other projects.
Now, more constructive-minded:
We came across a macrocell-solution, which could or could not improve things.
I have not tried it, because I'm not the kind of pilot who gets his 200 into this situation (I'm just flying too lamely ... not what you might think, that I think myself being a better pilot ... very much to the contrary).
https://www.youtube.com/watch?v=5jrnkwvFCHM
Not many people seem to have watched it so far, and only one asked back.
I think that's feasible, and it might even help, but I'd insert a Multiplexer so I can switch off the mixing in Motor OFF and IDLE position, only active in RUN position.
Maybe another one, so I can enable or disable it at the flick of a switch.
I can not tell if it really helps, and with which values.
Very likely, it depends on the pilot and what he does on the sticks, what he needs.
With the original Taly, with KD's style of flying, after a couple of maneuvers, throttle kind of stuck at full throttle, because there was never enough time for the rpm, increased in many short bursts, to bleed off again.
It can be uncomfortable if the model, in the end, runs at 7,500 1/min if you don't want that.
And there's no limiter or brake.
I can not tell what the Governor makes of it. It will work against that 'abuse', obviously, you also see it in the video, log file entries 'Lower Limit'.
This can help, but it can also change things to the worse.
So ... try and error.
If it works, it works, if not ... back to square one.
Another approach could then be, use throttle curves instead of the Governor, plus mixing, to take the Governor out of the equation.
—Eddi
Born to fly ...
forced to work.