2nd Attempt at test flight - still governor issues
Just rechecked this.
RPM is 3 short of that entered in the software tab.
A max value of 2000 entered and a value of 1997 seen requested at full stick / 100% throttle.
Just for a matter of interest have you got your throttle barrel set to be fully closed at 0% and then you raise it for engine idle or do you go into - %'s to fully close it?
Wondering if this makes any difference.
RPM is 3 short of that entered in the software tab.
A max value of 2000 entered and a value of 1997 seen requested at full stick / 100% throttle.
Just for a matter of interest have you got your throttle barrel set to be fully closed at 0% and then you raise it for engine idle or do you go into - %'s to fully close it?
Wondering if this makes any difference.
Hi, I use a DX9 so I have both throttle hold and throttle cut. Normal throttle curve is 0, 25, 50, 50, 50. This makes sure the governor will engage. Then I use throttle hold for start and idle at 4 / 5%. Throttle cut will take it back to 0, if needed.
Well I don't now if it helps, but using Fast and Very Fast Spool-up did cause problems on my electric setup. ESC is doing some spool-up as well. If Spirit aimed for faster spool-up than ESC was doing I ended up with much to high Head speed (2360). Selecting Slow or very Slow helped, as well as Switching Flight mode once up to Speed using Fast and very Fast. (Normal:1700 F1:2100 F2:2300)
Regards, Adrian
Regards, Adrian
Oxy4max SpiritPro + HW // SOXOS 550, SpiritPro, HW120A V4, 920KV // SOXOS 600, SpiritPro, HW160A, Pyro650 // SOXOS Strike7, SpiritPro, HW160A, Pyro750 // Skywing Spirit Aero // FrSky Horus X10S + Taranis X7 /
Spool up is set for slow at the moment, its not really made much difference as far as I can see.
I think that the plan for later on will be to completely redo the throttle set up including the linkage if required.
Instead of -40 trim for complete throttle closure I will reset this back up to zero trim and recheck everything to see if this makes any difference.
I think that the plan for later on will be to completely redo the throttle set up including the linkage if required.
Instead of -40 trim for complete throttle closure I will reset this back up to zero trim and recheck everything to see if this makes any difference.
Hi, I now force myself to do a benchmark test with glow plug out and starter to make sure the gov engages, after I've adjusted stuff.
Glow plug out, power system and tx up. Connect BT and app. Move throttle past 40%. Spin with starter.
You should see a value in the Requested RPM bar and the Current RPM bar should show 490 - 500 (speed of starter).
Glow plug out, power system and tx up. Connect BT and app. Move throttle past 40%. Spin with starter.
You should see a value in the Requested RPM bar and the Current RPM bar should show 490 - 500 (speed of starter).
I will try this after I've redone the throttle.
Did do this to check the sensor was working OK using the Jeti telemetry and could see the current speed the starter was turning the engine over at OK.
Unable to view the requested speed this way though for some reason so will have to try it with the USB cable plugged in.
Did do this to check the sensor was working OK using the Jeti telemetry and could see the current speed the starter was turning the engine over at OK.
Unable to view the requested speed this way though for some reason so will have to try it with the USB cable plugged in.
For me, this shows that the governor is not engaging ! I'll be surprised if the USB cable route will make a difference.Malc1 wrote:Unable to view the requested speed this way though for some reason so will have to try it with the USB cable plugged in.
Good luck with resolving this. I believe you've got all the bits to look for now. Power up with throttle at 0%. Move throttle past 40% for gov to engage, etc.
Use the throttle range to help with min and max and keep an eye on the diagnostics tab to make sure Spirit also sees 05 when the tx does.