I loaded the APM 2.24 with all the default parameters today and went flying. Stabilization and FBWA worked fine but when switching to AUTO or RTL modes, the plane goes into a dive. I've tried setting waypoints with both relative and absolute altitudes with the same end results.
Does anyone know what is going on?
You should be using the latest software, BTW: ArduPlane is now at 2.26
Ok Chris, I'll do that.
Is the airspeed sensor problem a past issue that has been worked on and fixed in the new code?
I just did a flight with the airspeed sensor disabled and it worked fine :o) However the thing was still a real rocket at times. Attached is the log of this flight.
So apparently the nose down and over-speed issues were caused by the airspeed sensor as you suggested. With the sensor enabled, I still don't get why it would keep diving and pick up speed if the indicated airspeed on the HUD is way over the set speed. Any ideas on how to fix this issue?
you should be changing the throttle cruise and airspeed cruise values for airspeed.
also check what are your throttle min and max's?
Michael, I have. I've set throttle cruise to 40%, and max to 90%. Cruise airspeed is at the default value but I've changed FBW max to 19m/s in the hopes of slowing it down a bit. I'm not sure if this has any affect in Auto mode though.
Is the airspeed sensor problem a common issue? I'm just curious because I crashed my first drone twice on two separate APMs and lost it on the second crash. It's a little frustrating to see this same issue come up again on my third APM. On the first airframe I had the probes sticking out at least 2 inches from the leading edge of the wing and now I have the probes sticking out of the cockpit into what I believe is fairly good air.
What I really don't get is the nose down attitude when indicated airspeed is so high. Any ideas?
I know that this question should be posted into another topic but I couldn't find such one.
Could anyone tell me what the MAV_CMD_DO_REPEAT_RELAY command stands for?
Many thanks in advance!
Thanks for the answer!
We already use the DO_SET_RELAY command for image taking but this way too many images are taken.
So an image in every 2nd or 3rd second would be enough but there is no command for this. We guess that the DO_REPEAT_RELAY turns on the relay with the predefined time value (sec) and switches it off. Please correct me if I were wrong!