Page 2 of 9
Re: 2nd Attempt at test flight - still governor issues
Posted: Sun 04. Oct 2015 16:38:58
by Malc1
On the Jeti RPM display what should be seen on the bottom where the two zeros are?
Is this current headspeed and maximum obtained?
Just wondering.
Re: 2nd Attempt at test flight - still governor issues
Posted: Mon 05. Oct 2015 18:16:41
by Malc1
I am still wondering about the data displayed on my DS16.
Large RPM digits are obvious and the bottom right the maximum obtained but what about the 0 on the bottom left.
Re: 2nd Attempt at test flight - still governor issues
Posted: Tue 06. Oct 2015 9:49:24
by ZeXx86
Jeti telemetry display only Current RPM.
So the problem is still the same? If RPM is displayed precisely, then it should just work.
What is your Spoolup rate?
Re: 2nd Attempt at test flight - still governor issues
Posted: Tue 06. Oct 2015 10:04:59
by Malc1
Looks like it should work but waiting for time and good weather to test it again.
Spool up rate is set to slow.
I have reduced the maximum head speed in the software now to 2000rpm with a requested in id1 of 1860rpm and id2 of 1970rpm.
It was 2200rpm before and I was seeing pretty close to that which is not good for the engine.
Software settings had been tried at 5 and 1 and 3 and 3 without any noticeable difference.
I am now at 5 and 5 to try it.
Should this help much with holding the headspeeds?
Re: 2nd Attempt at test flight - still governor issues
Posted: Tue 06. Oct 2015 10:15:38
by ZeXx86
Great. I recommend to increase the values during the testing in flight. On the ground you will not see any relevant improvement.
Re: 2nd Attempt at test flight - still governor issues
Posted: Sat 10. Oct 2015 15:29:07
by Malc1
3rd Attempt
Spent quite some time testing this earlier but this still does not work.
The requested head speed in the software does not match the one that is displayed/called out to me on my Jeti TX and is still far too high.
Maximum headspeed is set at 2000 with a requested RPM of 1860 in ID1.
When ID1 is selected the headspeed gets up to 1950-1970 in a hover and has been recorded as high as 2130 when pitch is added.
If the throttle curve is reduced and the requested head speed dropped as low as 1600rpm in the software I am not seeing much difference to the actual headspeed displayed.
Full throttle climb outs are very boggy suggesting that the governor is not doing a lot with a drop in RPM reported back.
Software has been increased now to 5 and 6 and this also doesn't seem to make much difference.
RPM's are being displayed correctly in 0000,000,00 and single units.
Anything else to check please?
Re: 2nd Attempt at test flight - still governor issues
Posted: Sat 10. Oct 2015 20:15:10
by Dawiev
Hi, just to be sure you have the Max Headspeed set correctly. I misunderstood it and I ended up chasing my tail.
It is not the max headspeed you want, it is the max headspeed at 100% throttle. See the explanation given to me in the post titled "Nitro Gov with 1.3".
Re: 2nd Attempt at test flight - still governor issues
Posted: Sat 10. Oct 2015 20:30:08
by Malc1
Yeah I understand this.
Originally I had the maximum set at 2200rpm and still had Id1 at 1860 and id2 at 1970.
Problem was that even though the requested head was only 1860 I was seeing headspeeds very near to maximum 100% throttle - not good.
That is why I'm now testing with a reduced 100% value because an OS 105 running at these sort of speeds is really not going to last that long.
Re: 2nd Attempt at test flight - still governor issues
Posted: Sun 11. Oct 2015 1:39:14
by Dawiev
The other thing to watch for is to only use servo travel to adjust idle and not 3/4/5 % throttle. If throttle is not 0, at power up, gov will not engage.
So, Requested RPM at 100% throttle must match Max Headspeed and 0% throttle at power up.
It sounds like your governor is not engaging.
Re: 2nd Attempt at test flight - still governor issues
Posted: Sun 11. Oct 2015 7:11:51
by Malc1
Not checked TX setup so something to now look at.
Throttle servo can be seen to move over to full at 40% on the throttle curve in normal mode and full over in ID1 and 2.Requested RPM in software is seen to come in OK.
Engine fully shut down is at -40% with idle at about -7%.This 7% gives -3% in the software at low stick.A Jeti DS16 is being used.
Dawiev wrote:
So, Requested RPM at 100% throttle must match Max Headspeed and 0% throttle at power up.
Explain this further if you can please.
As displayed in the software?