Servers by jDrones

CUAV Pixhack v5 Tuning with fatal ocillation of 800 size gas heli


(StefT) #1

Hi Everyone,

I have set up and tuned a 500 electric using CUAV Pixhack v3 with success earlier this week. This gave me the courage to progress to an 800 size gaser and Pixhack v5. I am following the Wiki to tune but the tuning end with a forced termination as the heli started to oscillate violently.

I completed the rudder tuning and VFF. The heli was manageable and it seemed that the rates were tracking nicely, apart from being a bit tail heavy. However, when I started to adjust the D gain to 0.003, according to Mission Planner, the craft started to oscillate heavily.

  1. What am I missing?
  2. Is it possible that the D gain can be 0?
  3. Is it possible that the scaling between Pixhack v3 & v5 is different?

I am attaching a link for the log file. Any help will be appreciated.

Thank you.


(Bill Geyer) #2

@StefT. Most of the time, P and D gains will be small. D gains can be 0 or less than 0.001. You can enter values out to the 4th decimal place if need be. The P gain is typically less than 0.05 on most helicopters.
Be sure to set your VFF appropriately. The I gain is where you will see the aircraft more closely follow the desired pitch and roll angles, however your ILMI must be non zero. Less than 0.1 is desired for that parameter.
Hope this helps.


(StefT) #3

Thank you Bill,

I was worried that it might have been a driver issue seeing that v5 is still relative new. The 500 had somewhat larger values.

The heli seem to be happy with a D gain of 0.001 or less, although it does not register under the advance tuning tab of Mission Planner.


(Bill Geyer) #4

Don’t use the advanced tuning tab. Only use full parameter list.


(Luís Vale Gonçalves) #5

I would suggest to use QGC to setup the Heli. Check the videos on the wiki.


(Jakob Schmidt) #6

Follow Chris’ tuning guide.
Do not use the Advanced tuning window.
My Soxos600 also had very low P & D, using a Pixhack V3.


(StefT) #7

I have successfully completed the setup and 1st flight. I still need to add the head speed governor and fine tune the PID loop but so far I am extremely happy.

A great thanks to the community and everyone involved in developing the code. I was flying a DJI Ace Waypoint unit and was “thankfully” forced by the lack of support from DJI to migrate to Trad Heli last week. It is something I wanted to do for a long time but just did not had the courage to do.


(Luís Vale Gonçalves) #8

Glad to hear that things went smooth.

Would be great to get some more feedback on what went better and where can we improve, so if you are inclined to give such feedback, documenting your migration would be wonderful.


(Chris Olson) #9

I have governor code for ArduPilot so you don’t have to add an external governor. The binaries are still built on Copter 3.6.3. But I can build updated binaries on 3.6.5 tomorrow. All you need is a hall effect sensor to plug into your CUAV v5 controller.


(StefT) #10

Hi Chris,

Thanks. I have 3.6.4 installed and already installed a T-Rex nitro hall sensor with the wires crossed. I am planning to set it up and test today. Will 3.6.4 be ok? You also mention to set it up on aux 5. Can you confirm that A5 is aux 5? I am having difficulties to find the right documentation for v5.


(Chris Olson) #11

The V5 is the same as any other controller for the rpm input. Yes, the A5 pins is the Aux 5. The governor is not in the main code yet. But there is a thread here when it was introduced for user testing and it explains how to set it up.

3.6.5 is still a point release candidate #2, but I think it will be going to official point release soon. There is a link there to where you can download the binary with the governor (still built on 3.6.3). But I will update that today to 3.6.5 and make a post on that thread to indicate that the binary is available on the latest point release.


(StefT) #12

Yes, I have the sensor installed and it is working, except that I will need the correct binary. I will wait for your update of 3.6.5rc. I am looking forward to test it.


(Chris Olson) #13

Thanks for your patience. Check the other thread, a link has been posted to the newest builds.