Integration for a nonlinear quadcopter with flapping dynamics model into Mission Planner and Flightgear for 3D visualization

The objective for this milestone was to integrate the same model functionality developed and analyzed within the Matlab/Simulink environment into a mature environment that will be able to test most functionalities of the Flight controller software that will be flashed for real-flight testing.

The decision was to either migrate the Ardupilot (in this case ArduCopter) software into the Matlab environment or integrate the highly nonlinear quadcopter model with flapping dynamics into the Ardupilot environment. The former option would mean no easy integration with Mission Planner and the real-time sofware-in-the-loop (SITL) testing tool (which also includes the infrastructure to communicate with the Flightgear 3D visualization environemt, while the later with make use of singular environment although the software development effort would quite tedious and error-prone.

It was chosen to go with the first option as this was thought to be lead to more mature verification method prior to real-flight testing while having a relatively smaller integration effort. This effort was also also aided with the fact the simulation model in MATLAB was already designed in source code format (C++) and then wrapped around in MEX (Matlab Executable) which was compatible with the Ardupilot C++ environment.

The integration of the quadcopter model was done in a phased approach testing the robustness and functionality of the simulation after each integration step. This resulted in a considerable amount of debugging time saved allowing the whole integration to be completed within a week.

The Flightgear program was configured to use this new airframe model and this successfully tested using the Mission Planner software the Ground Control Station. The results from this milestone has enabled the analysis of aerodynamics effects to be quantified both on subsystem level using MATLAB, system level (using Mission Planner) and visualization (using Flightgear). This now serves a in depth analysis tool to the performance of subsequent designs that will be developed in the near future.

Comments

Setting up the Tarot T4-3D gimbal on the Pixhawk 2.4.8 with Specktrum dx6 Gen2 toggle switch

So i took the challenge of setting up the Tarot gimbal not just for inherent stable video footage but also the flexibility of controlling it from the radio control. However, I encountered quite a few challenges which made me aware that I'm not the one only in this battle . It's quite clear that the setup of the Tarot gimbal using its own software is completely different from how it's been described in the Ardupilot/Arducopter webpage and in mission Planner. In Mission Planner and it's associated site makes one believe that it should be done through software, only to realize that in actual fact the setup is more complex than that. After two evenings of trying various combinations, I realized the getting the pixhawk Aux channels to communicate with the T4 gimbal requires the following steps: - The Pixhawk Pin9 (Aux1) needed to be activated to pass through user-chosen channel from the transmitter. For the Dx6 Gen2 it was the channel 6, which can assigned the ...

GPS Navigation Ground Test #2 - Heading Error Computation Algorithm

This one is going to be quite short. Yesterday was the turn of the heading error algorithm to be tested. This heading error is calculated based on the heading the between two waypoints and heading measurement from the GPS module. This error will then be fed into a the roll controller as an input for roll command to reduce it to zero. But for the roll controller to work accordingly, the input must be right and within certain bounds. Same as the previous ground test, waypoints were loaded unto the autopilot and serial debug data was monitored using my Asus TF101 Tablet. It's worth saying that I managed to get serial data output straight from the LINUX command line . So the command line integration with VIM is complete. So it takes approximately under 10sec to upload and start debugging data of the autopilot. Sweet! Anyway, it was found that the GPS accuracy should be considered at 10-12m. Anything less than that and you'll be running for trouble. That is not a real conc...

Unmanned aircraft and crop duster fly too close

An aircraft separation incident between an unmanned aerial vehicle and crop duster highlights the challenges with having a diverse mix of aircraft operating in the same airspace. On 12 September 2013 the pilot of an Ayres S2R commenced aerial agricultural spraying operations on a property near Horsham, Victoria. At about the same time, the operator of a UAV, Sensefly eBee 178, arrived at ‘Iluka Echo’ (Echo) mine site to conduct an aerial photography survey of the site. After completing his pre-flight preparation and risk assessment of the operation, the operator heard an aircraft operating about 1 – 1.5 km away on a neighbouring property.

Search This Blog