If you are changing throttle curves in your transmitter over the limit (under 0% or 100%) then it does not output these values since it is limited by unit.
Correct solution is to change Throttle Min/Max. values - this will do the trick if you change it to 1000us and 2000us as I have written few posts earlier.

Did you tried the servo output?

_________________
Spirit System developer

Hello,
There is definitely a bug in the Firmware. I tested today to get the right settings for the governor without blades.
With the parameter "Spoolup Rampup <=50" the spirit didn't give an Signal to the ESC (no spoolup after more than 1minute).
Spoolup Rampup above 50 (I tried 60) and the spirit give an signal to the esc and the Motor spoolup in 30-40 seconds. I tested it with Governor "very slow" "slow" and "fast" in every case the same behaviour (of course the spoolup time changes).

Additionally the initial governor spoolup is a very hard step from 0 to like 10% throttle (it seems that there is an offset which is added direct after the release of motor kill). This is a way to hard (my blades bump to the blade holder the last time with blades on at "very slow" spoolup!). This appears also in the other governor modes.

I have to set the ESC to very soft startup to compensate this (then the ESC slows down the acceleration ramp on its own).
In my application there is absolutely a software bug in spirit FW.

I use a spirit pro with FW 2.1.0 with DSMX (lemonRX diversity satellite) and a turnigy K-Force 120A opto ESC.
https://hobbyking.com/de_de/turnigy-k-force-120a-hv-opto-v2-5-12s-brushless-esc-1.html

My testcase was the following:
- calibrate throttle range without governor enabled
- set transmitter to 0% throttle
- setup the governer values I would like to test
- save the values
- set transmitter to 70% throttle (release motor kill)

I also attached my settings

I hope you could clarify this.
Thanks in advance.

Hi,

I investigated it a little bit further. With an Assault 450L equipped with an spirit pro and an hobbywing 50A V3 the problem is a little bit different.
At first "Spoolup Rampup <=50" is working (I tested 20 and 50).

But in the governor modes "very slow" "slow" and "fast" I had at first a little overshoot and then the ramp which engages. So the problem is the motor rpm rises falls and rises again (the second time with the rampup time I choose). But this could be ignored because the overshoot lasts only a tens of a second so this wouldn't be a problem ( holding performance and response was at 1).

The first conclusion is with the same Firmware the governor seems to work with the hobbywing 50A V3 (with integrated rpm sensor) but do not work with the TURNIGY K-Force 120A-HV OPTO plus orange rpm sensor very well.

The next thing I would test is to change the two spirits between my two helicopters. Perhaps it is the rpm sensor which is too noisy or the ESC.

Have a nice day

Hi,

thank you for your message.
Regarding your first post with Spoolup rampup - the problem that is present should be actually resolved by reducing Spoolup rampup value under 50 so that ESC will not start agressively.
Unfortunately some cheaper ESCs are not able to spoolup really slow, even that it is configured correctly. Thus it may be impossible to fix it in any way, other than updating firmware in the ESC.
In time that nothing is happening the ESC should start with the spooling but until it will reach certain threshold programmed in the ESC, then it will do something.
In some cases changing timing may help.

If this threshold is too far and spoolup slow, it could take even more than minute to do anything. You can verify with a servo that throttle output is doing something even with Spoolup rampup <= 50. There could be also problem, that internal protection deny to spoolup the motor, because it is missing RPM signal for so long time from disarming Throttle Hold.

Regarding second issue, I am not sure if I understand it correctly. You can try to add there a load (blades), then the overshoot can disappear.

It is possible that both problems will be solved with the upcoming firmware - release planned for tuesday.

By the way your settings looks to be quite clean. I am not sure if it is already prepared for flight, but for example Cyclic servo frequency is set to 50Hz which probably is not correct settings for your servos and will significantly reduce performance. Similarly subtrims.

_________________
Spirit System developer

Hello Thomasz

Thanks for your reply.

It wasn´t 100% prepared for the flight. The tooth of the servo arm broke at a hard landing, so the servo settings aren´t correct.

I cross checked the two units and both behave in the same way.
However I could spoolup the helicopter with the turnigy K-Force 120A opto ESC per hand (no governor in Spirit and 0..100% linear throttle curve) smoother than with the governor.

But I will test the new firmware before I investigate it further.

One question, what is wrong with my subtrims? I have flown with these subtrims 30 flight without any problem (I adjusted all mechanical very precise).

Thanks

Hello,

normally nearly all helicopter models require some Subtrim settings to make the swashplate absolutely level.
All cyclic push rods are usually of same lengths, so only subtrims are needed to make it level and at the same time servo arms perpendicular.
Usually servo arms are not perpendicular while Subtrim (tuning) is enabled).

It will fly even with very inprecise settings, but if it is precise, flight performance can be significantly better.

_________________
Spirit System developer

Hey Tomasz,

Thank you for the support. The update had all changes included which are needed for my big helicopter setup to spool up properly without a hard start and all spoolup rampup values could be used with wait times below 15s.
But if the motor is at the requested rpm the P gain is a little to high. because if the rpm goes above the requested rpm the motor brakes so hard (no brakes in the ESC configured I checked that) that I hear the flanks of the pinion swing forth and back (edge changes). But I think this wouldn't lead to an problem with blades on the helicopter.

The little overshoot at spoolup appears on my little helicopter like in 2.1.0 but that doesn't matter because I think with blade holder and blades on the helicopter all would be good.

So all in all everything is working like expected now.

Thank you.