My spirit doesn't seem to do it correctly. I tried to use it with and without the orange RPM sensor. Normal mode (around 65%) was perfect but when I got to UI1 with the sensor, it went to a random headspeed that I did not set. And In UI2, went to max head speed (at 90% throttle), So i tried without using the RPM sensor and normal mode was fine until it blended into some random headspeed that didn't change when i went to UI1 or UI2.

What I did in the software was, click on enable gov, input the heli info, put in 3300 as max headspeed, changed holding performance at 1 (since headspeed was pulsing) and then saw the values in software as i spooled up the heli. I noted these numbers down to comapre to the tachometer readings in real life.

I'd love it if I set it up wrong as I really want to use the gov on the spirit especially with the RPM sensor.

First of all, you cannot use the gov without an RPM sensor... think about it: how would the unit know that it has to react to keep the headspeed constant, if it has no way of knowing the headspeed?

_________________
Oxy 2 ♦ X-Vert ♦ Warp 360 ♦ Blade 450X ♦ Blade 450X Nightflyer ♦ Goblin 500 (RIP) ♦ 2 X mCPX v2 ♦ night fly mQX ♦ LadyMQX ♦ nano QX ♦ nano QX FPV ♦ Inductrix ♦ DX8 G1

Hi, the RPM Meter section in the Gov / Throttle menu will show you whether you're getting signal from the sensor.

Spool up without blades, conneced to app or software. With a flat throttle curve you will see "Requested RPM" and "Current RPM". If Requested RPM is not stable (with the flat curve, then there's something strange in TX / RX settings .
If the Current RPM is 0, you know the sensor is not working.

I believe you can also look in the log for RPM sensor noise warnings and you can increase the noise filter to make it more tolerable in needed.