Today, I had another flight in Qstabilize mode followed by QHover Mode.
One thing I have observed, the quadplane tends to move forward with no pitch input. Maybe it can be adjusted by Q_TRIM_PITCH as stated in the quadplane tips here: QuadPlane Tips — Plane documentation.
If the aircraft tends to move forward, then Q_TRIM_PITCH will be positive, right?
The quadplane also has calculated the hover throttle to be about 0.25. I am using 18 inch props at the moment which are surely an overkill and there is room to reduce the boom lengths by decreasing prop sizes. which will essentially also reduce wing flex. Is it recommended to go this route?
I seriously hope I am not spamming this thread. If I am, kindly let me know so I can move it to another topic.
For the wing flex, I was following the tuning guide at Tuning Process Instructions — Plane documentation, where after step 6 and a bit of manual decrease of D term, the flex is almost all gone. maybe it was due to the control loops overcorrecting. Either way, a significant decrease in wing flex is observed.
Step 7: Re-tried QHover which also performed much better.
Step 8: Yaw Bias while QHover is a mean of -0.04 with a peak variation of up to -0.12 at takeoff. Documentation states it should be less than 10%. Does that refer to peak-to-peak variation or should it be read as ±10%?
Thanks for your updates on the Striver which I too am about to complete. I also got a Freeman 2300 tilt VTOL and loaded the MFE parameters. Have you flown your Freeman 2100 and done any updates on the MFE params so it will be compatible with the latest Arduplane stable firmware?
@tridge@Michael_Oborne Hi there! I had a strange behavior on a Striver flight today. I am not sure what caused the Striver to skip VTOL takeoff (WP1) and head from the ground straight to WP2, which is 1.4km away @ 360m AGL. I have no idea why it skipped the VTOL takeoff altitude and attempt to ramp up to WP2. It was pure luck not hitting the roof and poles.The test mission proceeded for about 45 minutes and landed later without incident. After landing, i used the simulator to check and found that the mission planner was activating WP2 instead of VTOL takeoff WP1, each time AUTO is clicked. The only change I have had is upgrading mission planner. So, I re-installed Mission planner 1.3.76 and this behavior got resolved. Is there a way to force a minimum safety altitude and prevent ramps towards a waypoint from ground?
Thank you so much @tridge for the quick response. This is very clear to me now. In the meantime, I will simply avoid uploading missions on the ground while in AUTO mode. Once again, I appreciate your feedback. Thanks.
HI thanks for the informative discussion on this forum. I have been flying a Believer using a pixhawk 2.1 and cube Black with a Here 2 GPS. I am looking to switch over to a VTOL system and am currently looking into the MFE Striver as I can use the 6S system from the Believer. Will the Pixhawk Cube Black be suitable for this? Any assistance with this would be greatly appreciated. Thanks