Initial In-flight Testing of autopilot SUCCESS!

Depicts a traditional PID controller. (Photo credit: Wikipedia)

I'm such an exciting right now. It's been over a year of putting this UAV glider with custom autopilot and electronics together and now we're at the pivotal stage. In-flight testing of autopilot and GPS waypoint tracking!!

Decided to go for a flight test on Sunday morning before church (around 7am) eventhough I was performing the church band that morning (crazy I know). It was bitter cold but decided to push through. I must say that I realised that I need a small collapse table/stool to setup the instruments instead of the wet/moist ground.

I was great to see that the transmitter code works as expected. There was no lag in the transmission of signals from transmitter -> autopilot -> servos. The turning of aircraft with rudder and elevator control was smooth and consistent. It was refreshing to see that the filtering algorithm worked well.

Decided to test the roll autopilot first, this was a very nervy time as this could potentially lead to a uncontrollable airframe. But the safety switch algorithm was tested before hand it worked as expected on the day. This roll autopilot is a simple P of a PID controller which was not suitable. Although the PID architecture is coded, only the P gain factor is non-zero.

During flight (abeit short), the error gain was too aggressive which caused the glider to violently bank from left to right leading me to quickly switch back to full transmitter control mode.

The biggest headache of all this is not being able to have enough flight time at the park. Since these are soccer fields, I always have to look over my shoulder to see if people are about to invade the pitch. Very frustrating If you ask me.

Nonetheless, the autopilot in-flight testing has started and this is really exciting. It's now a matter of tuning the controller such that it enhances the stability margin of the airframe and not deteriorates it.

Exciting times ahead...

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