I have set my thr_min at 165 mid at 400 and max at 800After arming the props seems to spin correctly at about 165. If I then raise throttle off zero nothing happens until about 30% when it suddenly shoots up into the air. (Except this is a bench test
I have had a few 'successful' flights - by that I mean buzzing around a bit without crashing. I then got the toilet bowl effect and nearly crashed. I managed to flip into stabilise and land ok.
My aim in the future is to add expensive and potentially
I have just updated mission planner following a prompt. When I restarted all the settings were set to zero. I could't recover anything and so I selected reset all settings.
I then redid compass etc and tried to reprogram the 6 flight modes.
(previously posted in pixhawk hardware - now moved to this forum as it seems more suited)
I'm trying to resolve poor compass interference, possibly due to using the pixhawk internal compass rather than external. Currently getting bad readings outside
I flew a few months back and crashed due to brown out. I have now beefed up the cable and done a new flight test. In loiter mode it is showing bad toilet bowl effect. Moving in wider and wider circles.
I was 5 metres of the ground with my octocopter. Just the raw frame, no cameras but 4.5kg and enough of crash to break 4 of the arms. It was hovering perfectly and then total power loss and whack onto grass. Could have been worse. A minute earlier it
I have just completed my first test flights. I was very pleased overall with the performance. It's an octo 1.2m across and seems very stable without any calibration. Throttle midpoint seems spot on.Issue is understanding flight modes. Started in stab
After arming my octocopter the motors don't spin. I raise throttle a little and it jumps to very high power. Reaching 50% and motors are screaming near max.
I have tried changing parameters: MOT_SPIN_ARMED parameter.also lowered THR_MAX, THR_MID, TH
I have connected my pixhawk for the first time to a Mac and ran APM 2.0 to set it up. After loading firmware successfully, I think, there are no further options to move further. The Ardupilot page describes how you can then select 'Mandatory hardware