This week I had the privileged to attend two conferences in the US focusing on unmanned aerial systems (UAS) in agriculture. The first was the Delta AgTech Symposium in Memphis, Tennessee and the second was the Precision Ag Aerial Show at Decator in Illinois. These conferences are the beginning of my private study as part of my Nuffield Scholarship, thanks to my sponsor the GRDC.
As a forward to this discussion, I do focus more so on the fixed wing type UAS for large area mapping – see why here – and therefore generally do not comment on multi-rotor systems, GoPros, First Person View (FPV) etc even though these were covered at these conferences.
Both conferences were a combination of educated/independent speakers and vendors. There was a couple 1 hour multi-rotor demonstrations at Delta AgTech and two full days of demonstrations of fixed wing and multi-rotors at PAAS. The audience was extremely diverse – from curious farmers, agronomists, all the way to sensor & software companies and interestingly a large presence from insurance companies.
Themes I picked up on:
Everyone agrees that data needs to be more than pretty pictures – it needs to be actionable. Futhermore, boots still need to be on the ground, ground truthing data, explaining WHY. No one is claiming UAS replaces clever farmers and informed agronomists.
There is broad acknowledgement that UAS in agriculture needs to show a return on investment but only one case study was mentioned with actual figures.
Data processing is an issue. Some are claiming the solution is server based i.e. ‘in the cloud’ but acknowledge internet bandwidth is a bottleneck.
Sensors are a hot topic. Most manufacturers claim they have vastly improved sensors coming. Talk at the moment is around affordable true multispectral combined with irradiance/incident light measurement.
We were reminded a couple times not to dismiss satellite imagery as an option. Satellite sensors are always improving and getting cheaper. Will we have 10cm GSD from multispectral satellite in 10 years?
Generally frustration with the FAA on the time it is taking to develop rules around UAS. In saying this, there is acknowledgement that rules are needed.
Some other interesting points picked up over the last week:
We are starting to see some UAS companies offering early versions of vectorization (i.e. points, lines and polygons) in their server solutions using imagery collected via UAS with the main example variable rate application map of fertilizer in crop based on NDVI. This is not new technology – it has been done with satellite imagery for years.
With the speed of technology rapidly changing are we considering the upgrade path of current UAS? Can the sensor and GPS be upgraded without buying a whole new system?
Most of the commercial grade fixed wing UAS seem to be able to fly well, have autopilots that just work and acceptable ground control software. Product differentiation will probably be around sensor integration and options, support, innovation and whole system workflows including speed of data processing. This is just a snapshot of what was covered in the last week. I will be compiling a report that encompasses my whole USA/Canada trip which will be available towards the end of the year.
Built with a 3DR Pixhawk (APM:Plane 3.0.2), Finwing Penguin 2815 fixed wing air frame, S100 Canon camera and RFD900 Radio (excellent Australian product), my budget agricultural unmanned aerial vehicle (aUAV) has kept me busy and learning lots in any spare time over the last few months.
In my last post, Unmanned Aerial Vehicles (UAV) in Precision Agriculture, I outlined the main components of a UAV for precision agriculture focusing on a fixed wing platform for collecting high resolution paddock scale data. In this followup post I will attempt to log some of my experiences. Note that this is just a learning experience – there are many commercial UAV options available for agriculture that are less time consuming and provide similar or better results right away.
I needed a fixed wing platform that is readily available, cheap, with potential for long battery life, stability in the air and plenty of space for electrical components. I chose the Finwing Penguin. With the standard 2815 Finwing motor, 60 amp electronic speed controller (ESC), 9×6 propeller combined with a 4400Mha 3 cell Lipo battery I was only able to achieve about 20minutes flight time or enough to map about 40ha at 12m/s. I have a CXN engine mount which enables me to go to a 10″ prop which some of the gurus recommend. I could also increase my battery capacity and battery cell count to get longer flight time.
The Penguin is rather unique in its class as it has inbuilt landing gear. This consists of a pair wheels at the front and a single wheel at the back. I think this assists in preserving the plane when there is nowhere soft to belly land. The landing gear also allows you to take off like a traditional plane rather than hand launching. After making weight or centre gravity (CG) changes I will often take off from the ground. The downside is that these wheels to block up with mud quite easily if you land in a wet paddock.
The wings (including tail wing) come off for transport. I usually remove the main wings but leave tail wing in place as it is quite hard to get on and off due to awkward wiring and attachment arrangement.
The Penguin UAV does come with a pre-cut hole to install a down facing camera but it does not suit to place the camera top facing forward which is desirable. It was also very awkward to get the camera in and out as I had the Pixhawk autopilot installed above the camera position. I decided to go at the plane with a hacksaw and build a camera mount that would allow the camera to be installed from underneath the plane and also enough space to mount the camera top face forward.
Autopilot, GPS & Radio modem
As far as autopilot is concerned 3DR Pixhawk with APM:Plane 3.0.2 was the best option. At first I had issues getting my plane to fly well but once I upgraded to version 3.0.2+ the autotune feature changed the game altogether. This allowed the APM to adjust the PID settings in the plane as I manually flew it around. It works really well! During my latest flight I had an 8km/h cross wind that the APM was able to fly against successfully.
The GPS is a Ublox LEA-6M. It works well considering the price point. I did not attempt autonomous landing which is when GPS accuracy is more important. This GPS is able to get a fix within seconds of start-up and generally no issues throughout flight.
I initially used the 3DR radio modems but had all sorts of problems keeping a solid connection with my GCS. I decided to bite the bullet and buy a quality radio modem that should last me a long time and exceed all my range requirements. The RFD900 Radio pair is compatible with 3DR equipment and slotted in quite well. I did have to manufacture a cable to connect it to the Pixhawk and it took a bit of searching to figure which wires went where but I got it sorted within an hour or so. The RFD900 did have some driver issues on Windows. I had to install an old driver before I could get Mission Planner connected to the Pixhawk through RFD900. This all equates to time spent mucking around… BUT once working this product is excellent and I always have strong telemetry signal.
Ground Control Station (GCS)
The Mission Planner software which runs on the ground station laptop allowing you to program the UAV and monitor it in flight is very good – especially the Auto Waypoint Survey Grid feature. This allows you to draw the area you want to on the map. Simply load in a photograph from the camera you will be using and the target elevation. From this information is draws a flight path with your desired overlap.
Sensor & Image Processing
Canon S100 is my sensor of choice as it is a great balance of quality, price functionality and size. I started with a Canon D10 but many of the photos came out under exposed. The S100 has a larger sensor and inbuilt GPS so it is a better choice for aerial mapping. The downside to the S100 is that the lens protrudes from the camera which exposes it to damage in a rough landing.
With UAV aerial mapping you need a way for the camera to trigger every few seconds on its own. With a Canon camera it is easy using the Canon Hack Development Kit (CHDK). This updates the camera firmware, allowing you to use intervalometer scripts to trigger camera every few seconds. CHDK also offers what seems like unlimited settings for the camera. It seems difficult to find a complete set of settings to use with CHDK, but for my next flight I will try using the DroneMapper documentation to setup CHDK.
In my last flight approximately 30% of my photos came out blurry. I discarded the worst of the photos but still had to use some poor quality photos to ensure the map had no blank spots. This is probably due to a combination of camera settings, camera mount and propeller slightly out of balance.
Using desktop software trial of Agisoft Photoscan I was able to product a 40ha orthomosaic. The application works surprisingly well considering all images are taken at slightly different angle and are only provided with one GPS point for each photo. It is a very computer intense process and if I was to do a significant amount of processing would need to upgrade my computer. Alternatively I could use DroneMapper, but my dataset did not meet their requirements because I had to cull some images. I hope to try DroneMapper next time.
I took my data a step further and set up a web server to host the data as tiles. You can check it out here. How to store and share data collected by UAVs is something I have been thinking about. An orthomosaic for a single paddock can be several gigabytes and take a powerful computer to view in its raw form. The web seems like a good way to display data having a server store the data and only send bits of the image that the end user requests as they zoom in and move around.
This is my second flying UAV. My first was a Finwing Penguin as well. I spent a couple days putting my plane together and all the components. It is a nervous time flying your brand new plane for the first time. The first time out my plane few OK in manual mode but since I am a very ordinary pilot I like to use assisted flying modes. I changed to Fly By Wire mode and due to a APM setting (that I had to set) the autopilot had reversed the elevator sending it crashing into the ground. This snapped the plane in half and bent up the fuselage. Thankfully this durable foam returns to shape when you put it in boiling water and the pieces can be glued back together, reinforced with carbon fiber and fiberglass tape. Now I follow the suggested checks in the APM:Plane instructions more closely. I’ve had no crashes since but have landed in mud which can be painful to clean out of the landing gear.
Putting together this UAV I have learned how all the components of a UAV fit together, challenges faced by the commercial suppliers, and a better understanding of the enormous potential on offer. I think the biggest challenge is not the UAV platform itself but collecting high quality consistent data that can be quickly processed and given a useful, profitable application. The setup I have discussed here not including laptop or the countless hours of time comes to about AU$1200. Obviously for mapping large areas on a consistent basis, a commercial UAV would be preferred or even essential.