Spirit System

Hi, did you make any progress with this?

We have prepared firmware with updated governor gains, so it can be tested.

Adrian: Nitros are working very well for long time, but also tested gassers. We will buy the motor for testing. We are usually testing rather bigger motors.

Nitros are working very well for long time, but also tested gassers

You might believe this, but I do not think the buying public agrees with you.

Here's what somebody (not me) posted on a rival forum : "" Agreed. I bought 2 based on this news alone. Otherwise I would have bought more Spirits. On a nitro, I'm glad I did. Because of that xxx governor. Daaaaaaaamn. What a nitro governor this thing has. It's practically magical. ""

My concern is, if you believe its working, then it is not getting the attention required, hence my insistence to make the point.

Well the Electronic is usable but a lot of room for improvement. Im sure spirit will keep improving it?

I am sure that any governor will not work if there is something wrong.
For example magnet polarity - one governor might work well, another one with the same configuration will not work at all.
There are tons of videos with issues and discussions about any governor. Especially if you are moving from one brand to another, this might be confusing.

But of course we are trying to improve everything so it can work perfectly anywhere.

Coming from vbar at which the gov worked perfect with my setup I will continue to say we need a large configurable collective add. Low rpm flying uses a lot! More of this than hard 3d for instance. I don't know what the value 6 is, I can't translate it to a rpm rise or v curve. Also for quick cyclic you want the same adjustable value. This is essential.

* Unrelated posts will be deleted in a few minutes as they are not helping in this thread at all *

velocity90: There is configurable collective add - it is Governor Response parameter as I have said you earlier.
We do not intend to copy VBar. We want to make it easy to configure and with good performance. Placing next parameters is exactly way which we do not want to go.

@Dawiev:
Yes, I agree with your citation.
But if somebody says - it does not work somebody other says - it must work… Those are only words.

Therefore I invested time to record settings, progress and responses to be able share it and show it to you. At the end, I switched to GV-1 (which is not constructed for this little heli – GV-1 is designed for maximum 2100 on the rotor, and I fly about 2600) to show you, that the heli is able to be driven by a governor…
I am open to test it again if a change will come, but I will not switch back without knowing, that there is improving in the governor.

Maybe one question.
How the governor knows, where is the limit (% of throttle), where should not go? In Spirit, there is not set any idling level… Is not possible that the governor would turned off the engine in the fly?

ZeXx86 wrote:* Unrelated posts will be deleted in a few minutes as they are not helping in this thread at all *

velocity90: There is configurable collective add - it is Governor Response parameter as I have said you earlier.
We do not intend to copy VBar. We want to make it easy to configure and with good performance. Placing next parameters is exactly way which we do not want to go.

Ok, that was very unclear to me, I expected holding performance to be the add. Will tweak it some more. Too bad there will be no cyclic add. Why set the gov agressive if you only need it for tic tocs. The tail will suffer from this.

There is also Cyclic Add. The algorithms are adaptive. You do not have to set it manually as it is tuning itself.