Hi,
I would need to help with settings of governor in Spirit for GAUI NX4.
The problem is that when I increase pitch and fly up of loop and end the loop with hover or after tictocs the engine is very over speeded. Let’s say, that I set the engine to 18,5k RPM and when I go back in the hover, I measure about 20,5k RPM (gear ration is 7,05 - head sped is 2620 in case 18,5 and 2900 in case of 20,5).
I made some videos with different settings. See here:





Next problem is when I turn on the governor, the engine spins fast up and then slows down to set limit.
I tried to ply with needles, with throttle linkage, but nothing helped… Throttle servo is Align DS510.
Throttle curve in my radio, which works is: 100-55-45-55-100.
Throttle position for idle is 17% in Spirit diagnostic, then the % corresponds with radio value...
Throttle servo frequency is 200Hz.
Gov Start is “very slow”
Threshold is 50us.
Gov is off in bank 0 and 1. Gov on is only in bank 2.
Max RPM set in Spirit is 3000, in radio 87%.

I switched to Spirit GOV, because Align GOV over speeded it as well, but no too significant as Spirit GOV.

Any idea what to try?

Hi,

can you tell me if TC values of 100-55-45-55-100 are used also when governor is active in the unit?
If so, then this is the problem.

I recommend to decrease Governor Holding performance little bit. Then it should be better.

_________________
Spirit System developer

Hi,


No, it is an example, which works quite well (when GOV is OFF). I set 3000 RPM for 100% in TX/Spirit. For flying with Spirit GOV (bank2), I set there 87% at all the points in TX (should be about 2600) (I switch banks together with fly mode - there should not be combination of V curve and GOV ON, there are no mix /I double checked/).

Governor holding performance is set to 1 most of the time (see videos). I can not go to lower value. Which configuration would you suggest based on the video?

How to deal with the two problems, which I have?
1) Overspeeding when I go to hover from a power maneuver (loop, tictoc) /longer maneuver = more significant overspeed/
2) When I turn on the gov, it overspeeds the rotor and then go down to set value. (should I decrease "Spoolup Rampup"? What value should I try?)

Thank you for your support!

Hi,

in the video it is visible that you are flying right at the moment when governor is trying to engage.
For governors it is not too good, so I recommend to wait until headspeed is stable.

This can help you with overspeed at the beginning.

If you observe overspeeding during demanding manouvers, you can try to increase holding performance and decrease governor response.
In this way RPM should be more stable and react quickly for such changes.

_________________
Spirit System developer

I tried configuration like 8-1 or 9-1, but the situation was the same - it overspeed the engine as I mentioned before.
I turned GOV on and did not fly right after that - or if I should wait how long?

"If you observe overspeeding during demanding manouvers, you can try to increase holding performance and decrease governor response."
I tested some comfigurations like 8-4 and 4-2, 2-2, and the result was not good.


If you wish/want, I can record a video according your recommendation and post it here.
E.g.:
Set gov to 8-1 or 2-6 and hover for 10 sec, then fly some tictocs big loops etc...

Hi,

you should be ready to fly immediately when RPM is stable.

Values such as
Gov response: 5
Holding performance: 3
might work well.

Also make sure that the Max. throttle servo range is not too high.

_________________
Spirit System developer

No problem - I can test 5-3 configuration, but I already tested configuration 4-2 and the rotor was over speeded when I went from power maneuver (here I move from 2 to 3, which should be worse) and did not hold well during maneuver (from 4 to 5 should be better if I understand the philosophy of the Spirit GOV settings).

I will set 5-3, record the fly, publish the video and let know here.

The servo travel is OK – I double checked it (0% = carb if fully closed, about 17% motor idles and 100% - the carb is fully opened).

Just bear in mind if you once in Gov Mode >50% and Idle is not going below 12% your next spoolup is ARB (Auto Rotatin Bailout) in aprox. 1/3 of normal spoolup time. You need TC just for a very short time below 11.5% to have next spoolup normal.

_________________
Oxy4max SpiritPro + HW // SOXOS 550, SpiritPro, HW120A V4, 920KV // SOXOS 600, SpiritPro, HW160A, Pyro650 // SOXOS Strike7, SpiritPro, HW160A, Pyro750 // Skywing Spirit Aero // FrSky Horus X10S + Taranis X7 /

Hi,
Next tests were done today.
Here is longer fly with settings 5 and 3, then 8 and 2:





I would say, that I would need something like 8 and -2...

Next, I made longer video with settings 7 and 1. I take a PRTSC from telemetry record. I started recording video and telemetry record at the same time - it means that the timeframe should corresponds (+- 1 second):





Something strange happened at about 100 seconds - seems like governor was turned off and were used a curve from transmitter (=about 87%). Then, I turned off the governor and then turned it on, and it worked (not well, but worked).

I have to mention that I use one sensor for Spektrum telemetry and Spirit system. Sensor is powered from TM1000 telemetry and signal wire is connected to both devices - telemetry and Spirit. In the log was no error (I made PRTSCS of whole log - there is only once mentioned, that the GOV was turned on)

Hi, I hope the experts will chime in and resolve this for you. That doesn't look good at all. I would expect better holding power from a v-curve, or even a moderately effective governor, than what you are seeing. i have no experience with this size nitro or model though, so some general thoughts.

From my limited experience with nitro, you're engine tune needs to be good for any governor to work. Too lean and it will overspeed. Too rich and it will bog / sluggish - gov will over-compensate and not hold at all.

I use the Align sensor, split between the FBL ( not Spirit in this case, sorry) and TM1000 on two helis, like you, with no issues. You could investigate the sensor noise settings and see if this has an effect.

Because of the overcast conditions in the vid, it is not possible to see the smoke trail. How much pitch are you using ? You might be asking too much from the motor as it bogs a lot ? I had to quickly learn that you cannot bully a nitro like and E, and certainly not something this size.

The temperature is very dependent on where you measure it. Is what you are seeing in line with other guys ? (Perhaps worth searching on the forums at Helifreak or Runryder)

Good luck !!