From the number of viewers I see that many peoples are interested in EKF topic, so I try to describe the algorithm as I understand. Although this decription still lacks the information of measurement and process noise, and of covariance's…
"Hi, Adil Rashid
I've done some explanation on Arducopter 3.0. Here I include the attachment for you. To tell the truth, I still have some issue with read_inertia(), so if you've better understanding, please tell me.Arducopter_3.0.pdf"
On Thursday with the help of my friends field test was done to see if the bug of adding a dummy waypoint to the end of the flight plan is fixed. We started with modified Arduplane 2.65 with the flight planQGC WPL 1100 1 0 16 0 0 0 0 21.062670…
I've just received new APM 2.5. When testing its log data seem problematic: altitude mix and altitude GPS are of very high value, about 170 m although I tested on the ground. Then I tried to install a new Mission Planner, version 1.2.22, but the PC…
In July I posted "APM 1.0 and Arduplane 2.26 code description". Then on friday I updated to "APM 2.5 and Arduplane 2.65 description" and put under the old title But then I think this title may be misleading so it would be better to put under a new…
"I think carefully again on the issue and come to a conclusion that the modified code would work but not because of changes in if command's handle_no_command() branch but instead due to changes in else branch. So the branch handle_no_command() can be…"
By mistake I posted this on aerial photography Recently I've used a flight plan with the last command DO_JUMP as below0 1 0 16 0 0 0 0 21.062668 105.797707 2.000000 11 0 3 16 0.000000 0.000000 0.000000 0.000000 21.063231 105.797684 30.000000 12 0 3…
Recently I've used MP to add a DO_JUMP command toward the end of the waypoint list. But it had no effect at all, when reaching the last waypoint, the plane flew home. At close look, I see that MP sets DO_JUMP command parameters as P1 = WP#, P2 =…
As I can see on the forum that many people like to understand the code of Arduplane like me. But there's no appropriate documentation on the web because it's hard to understand the software without undrstanding the hardware, so I decide to find out…
"In this version there's still the same issue I don't understand like in previous ones. When looking at calc_nav_pitch() there is a command
nav_pitch = -g.pidNavPitchAirspeed.get_pid(airspeed_error, dTnav); (2 parameters call)
However, get_pid…"
"Another thing I don't understand is that when looking at calc_nav_pitch(). There is a command
nav_pitch = -g.pidNavPitchAirspeed.get_pid(airspeed_error, dTnav); (2 parameters call)
However, get_pid definition is
PID::get_pid(int32_t error, uint16_t…"