Spirit System

Hi,

I just got my hobbywing v4 and setup the spirit gov. The log is full of rpm sensor too noisy. Ive read more people are having this issue. Any solution to this? Sensor filter doesnt help. Is it because the rpm sensor wire is paralel to the signal wire? Its not build in so the wire is laying seperately.

I split rpm wire and route it not parallel with bec wires but this not help. Nor ferrite rings

Just tried my hobbywing phase sensor that I used with yge and that one gives no noise errors.

I couldn't figure it out either. Two different helis both w hw 100a v3 escs and spirit... one has filter down to 1 with no issues and the other has nothing but noise. Tried different routing and ferrite rings but nothing fixed it. So I just stuck w the hw esc gov.

The issue can be induced by anything that radiates wireless signal, for example Jeti receiver that has telemetry.
These receivers can induce major glitches in some servos/or any signal routes if antennas are too close or positioned to radiate in such direction.
Then the signal from the RPM sensor might be less apparent then one that is induced - which is a big problem for external governors.
Interestingly our Hobbywing Platinum 100A V3 have no issue with this. It was always perfectly clean. Nothing special was done.

So the positioning of the components can make a big difference.

Like I said its completely seperate from the heli, cable straight in the Spirit.

I have to say theres something not right with the gov. Have you seen in my jeti logs that if I go from 1650 rpm to 1850 and back its 1740,while requested has not changed.

I also notice simular behavior with yge and freewheeling /overspeeding. The rpm just doesn't recover properly from it. Also theres no soft change between idles, a problem if you go from 1650 to 2100.

Hobbywing rpm values are also constantly changing rpm on the ground with no load, the easiest scenario it should hold perfectly, not fluctuate +/- 100rpm

V4 Definitely doesn't work with it.

Without a proper RPM readout it unfortunately never can't work well. It is like a RC gyro without a sensor data.
Readout must be stable, at least not fluctuate more than +/- 20 RPM. If this is not the case, then even switching will not work properly as the RPM data migh be loosing for more than a second if there is excess noise.

If your Holding performance gain is too high, RPM switch might be very fast. This mean it should be reduced.

For example we have determined few months ago that REX receivers with one of the first firmware versions may influnace governor to such extent, it it unusable.
After reflash to the latest firmware, it just works. Unfortunately this is something we can't affect.

It's also the case with the seperate hw rpm sensor which gives zero rpm noise warnings. With all respect, if you keep blaming properly setup helis this will never get fixed. The reports of it are numberous. My heli is perfectly fine. No rpm sensor warnings with 2 other fbl units only spirit.

You make one of the best fbl units, please start listening to the actual users. [WHITE SMILING FACE]

I am trying to help you as much as possible. There is always reason why something is not working for some people.
I dont know what do you want to hear, but with so many different variables it is always not easy to find real issue immediately.
What I am saying is true and you can easily verify it.

I am working 16h each day to improve the products. More questions, slower improvements.
I know many, many very experienced pilots that are known to have helicopters in a perfect condition, everything must be always perfect.
But even these people can be very wrong, including me and you or anybody else.

Usually the reason why something is not working is the simplest one.

I suggest you get a v4 and see for yourself. Also my jlogs don't lie about the rpm being weird when switching back. Im sure somewhere in the future you will find the governor was not ready yet.