PaparazziUAV - User contributions [en]

GCS

2010-05-07T13:10:35Z

Tc78: /* Related Links: */ (SPAM)

{|
|-valign="top"
|__TOC__
|
[[Image:gcs.jpg|frame|right|The Paparazzi Ground Control Station is the heart of the system and the user's primary interaction interface.]]
|}

== Strips ==

Each A/C has an associated strip that displays information about the A/C and provides buttons for common commands. The strip has the following layout:

[[Image:strip.png|Aircraft information strip]]

=== Displayed information ===

* Left: Flight information
* Center: Navigation information
* Right: Navigation control
* Bottom: Custom navigation and setting buttons

=== Actions ===

Every change in the waypoints (position or/and altitude) must be confirmed with the dialog box that appears after the move. A modified waypoint remains animated on the map and the GCS continues to re-send the move request until confirmation is received from the aircraft.
When clicked, the '''Mark''' button places a mark on the map at the A/C position. A snapshot from the video plugin is associated to this mark and can be viewed by moving the mouse over the mark. A click on the mark opens a dialog box allowing to delete the mark.
A click on the colored bar at the top selects the corresponding A/C in the [[#notebook|Notebook]].

== Map ==

[[Image:GCSmap.png|thumb|400px|Sample map showing the various features]]

=== Display ===

The map display contains the following information:
* The A/C track: it can be erased ''via'' the ''Clear track'' option from the A/C menu.
* The A/C label (in clear blue near the A/C) contains the name of the A/C (Plaster), it's altitude (218 m) and it's ground speed (11.99 m/s). This option default is off. It can be activated with the ''A/C label'' option from the A/C menu.
* The carrot (the orange triangle). This is the point the A/C is following during autonomous navigation.
* The waypoints defined in the flight plan (blue diamonds).
* The intended trajectory is shown in green (circling waypoint 2).
* The default background is black. [[#google_tiles|Google tiles]] or [[Maps|user defined maps]] can be loaded to provide navigation reference.
* The camera footprint (the grey polygon) is representative of the swath of land currently seen by the onboard camera. This option default is off. It can be activated with the ''Cam footprint'' option from the A/C menu.
* The WGS84 coordinates of the mouse cursor are displayed at the top right hand corner (43.462019 1.270474).
* A UTM kilometric grid can be added to the background ''via'' the ''UTM grid'' option from the ''Nav'' menu.
* The height Above Ground Level (AGL) displays the ground altitude of the mouse near the geographic position in the top right hand corner. The [http://srtm.usgs.gov/ SRTM] option must be enabled in the ''Nav'' menu. The height information comes from SRTM data files (<tt>.hgt.zip</tt> or <tt>.hgt.bz2</tt>) and must be copied to the <tt>data/srtm/</tt> directory. They can be downloaded from [http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/ http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/]. For example: http://dds.cr.usgs.gov/srtm/version2_1/SRTM3/Eurasia/N47E016.hgt.zip is for 47 deg North latitude and 16 deg East longitude.

=== Navigation ===

You can pan/zoom the map using the following:
* Pan with the blue arrows on the map or use the arrow keys on the keyboard
* zoom in/out with the mouse scroll wheel, the page up/page down buttons or the small up/down buttons at the top right hand corner where the zoom factor is displayed
* fit the map to the window, in order to see all the waypoints and A/C, with the '''f''' key or the ''Fit'' option from the ''Nav'' menu;
* center the map on an A/C with the ''Center A/C'' option from the corresponding A/C menu.

=== Google Tiles ===
The default black background can be automatically filled with calibrated satellite photo tiles from Google. Note: if you download too much map data from Google you may be blocked for downloading further maps for 24 hours.
 
See the [[Maps]] page for more info.

=== Waypoint Editing ===

The properties of any waypoint in the currently loaded flight plan can be modified by two methods:
* Drag and drop the waypoints to a new location (a confirmation dialog will appear).
* A single left click on a waypoint opens a dialog box where you can edit the waypoint's coordinates and altitude.

Waypoint edits are sent to the aircraft immediately upon confirmation in the dialog box. The GCS will re-send the data and the waypoint will animate until the aircraft confirms receipt of the move request. New waypoints cannot be added during flight.
 
See the [[Flight_Plans|Flight plans]] and [[Flight_Plan_Editor|Flight Plan Editor]] pages for more information on waypoints.

== Notebook ==

The notebook frame contains one page for each running aircraft. Each aircraft page is itself divided into subpages displaying telemetry data and giving access to the autopilot tuning parameters.

Note that the colored tabs at the top of this section allow the user to select among multiple aircraft.

=== Flight Plan ===

<center>
[[Image:GCSfp.png|Flight plan tree]]
</center>

The full tree of the flight plan is given in this page. The current block and the current stage are highlighted. A double-click on a block allows the operator to immediately switch navigation to this block.
 
See the [[Flight_Plans|Flight plans]] and [[Flight_Plan_Editor|Flight Plan Editor]] pages for more information on flight plans.

=== Settings ===
<center>
[[Image:GCSsettings.png|Settings tab]]
</center>
The setting page allows the operator to change variable values during flight. The layout of the page is generated from the <tt>dl_settings</tt> section of the settings.xml file, one tab is associated to every section and sub-section.

On each line is displayed (from left to right), the name of the variable, its current value (periodically sent by the A/C), a slider or radio buttons for user input, and commit/undo buttons.
 
See the [[Telemetry#Settings|Telemetry]] page for more information on settings.
 
The save button of this tab opens the following popup which proposes to the user to save the current values in the airframe file (according to the <tt>param</tt> attribute in the [[Telemetry#Settings|setttings]] configuration file). The values of the checked rows will be saved in the airframe file (or any other file) for further use. Units (e.g. deg or rad) are taken into account. '''It is recommended to backup the airframe file before overwriting it with this utility''' (even if time-stamped copy of the airframe file is actually automatically done).

Symetrically, the Upload button of this dialog button will send all the checked values of the airframe file to the live aircraft.
<center>
[[Image:Save settings.png|Settings tab]]
</center>

=== PFD ===

[[Image:GCSpfd.png|Primary Flight Display]]

The Primary Flight Display contains an artificial horizon and two scales displaying the current ground speed (left side) and the altitude (right side). Minimum and maximum speeds are shown under and above the speed scale. A click on the scale resets these values to the current speed value.

=== GPS, Infrared, Wind ===

The '''GPS''' page gives the list of satellites tracked by the receiver and their respective signal strengths in dB.
(35 is low, 45 is excellent) and if they are used to compute the fix (green: used, red:not used). This page may help to tune the position of the receiver on the aircraft relatively to other components (e.g. datalink and video transmitters).

The '''Infrared''' page is only used for aircraft not equipped with the vertical infrared sensor. This page reports the required pre-flight calibration value as well as the evolution of the in-flight calibration correction factor (from hybridization with the GPS information).

The '''Misc''' page displays the estimated wind velocity computed by the ground station during flight and relayed back to the aircraft. Wind velocity is estimated by vector addition of the GPS-measured ground speed in many different directions during level flight. This computation may soon be performed by the autopilot instead of the ground station.

== Video Plugin ==

The <tt>-mplayer</tt> option of GCS allows the user to display a video stream in this window. The video window can also be exchanged with the map by clicking anywhere inside the frame or from the menu.
Use the following line in your [[Control_panel.xml|control panel]] to enable the video window.
<tt>path_to_ground_segment/cockpit/gcs -mplayer rtsp://localhost:7070/video -layout appropriate_layout.xml</tt>
Note that a <tt>plugin</tt> widget must be specified in the used layout:
<tt> <widget size="300" name="plugin"/></tt>

The <tt>-plugin</tt> option is another way to use the plugin widget: the X subwindow id is given to the provided command:
<tt>path_to_ground_segment/cockpit/gcs -plugin "mplayer video_stream -wid " -layout appropriate_layout.xml</tt>
<tt>path_to_ground_segment/cockpit/gcs -plugin "cvlc video_stream --drawable-xid=" -layout appropriate_layout.xml</tt>
The <tt>--vout-event=3</tt> option can be used for vlc to disable mouse and keyboard events handling

== Altitude graph widget ==
<center>
[[Image:altgraph.png|400px|The GCS with the altitude graph]]
</center>

An altitude graph can be displayed in the GCS by adding the widget ''altgraph'' in the layout configuration (See the [[GCS_Configuration|GCS configuration]] page). An example is provided in conf/gcs/alt.xml. To use this layout add -layout alt.xml to the /conf/control_panel.xml file. This type of layout is more suited to a multi UAV set up. The Papget ruler is a much less intrusive and better tool when you are only flying a single aircraft.

==Papgets==
Graphical objects can be added to 2D maps: text, rule, gauge, buttons, .... These objects are named ''papgets''. The following snapshot
shows an example with buttons (left side), gauges (lower left corner), text (upper right corner) and ruler (right side). This example
has been produced with a layout file provided in the distribution:

.../gcs -layout papgets.xml

<center>
[[Image:papgets.png|516px|A 2D map augmented with papgets]]
</center>

===Telemetry data report===
The easiest way to create a papget displaying telemetry data is to drag&drop a message field from the Messages window onto the 2D map of the GCS. The default rendering is then a string of text. Clicking on it allows the user to change its type (currently text, ruler or gauge) and some of its attributes (color, size, range for a gauge, format for a text ...). A papget can be moved by simply dragging it.

<center>
[[Image:papget_editor.png|Main characteristics of a papget can be dynamically edited]]
</center>

Papgets can be saved in the layout of the GCS (from the Nav menu). The description is saved in an XML file (in <tt>conf/gcs/</tt> folder) which can be manually edited:

<pre>
<papget type="message_field" display="gauge" x="47" y="414">
<property name="field" value="BAT:voltage"/>
<property name="scale" value="0.1"/>
<property name="min" value="0."/>
<property name="max" value="15."/>
<property name="size" value="50."/>
<property name="text" value="Bat(V)"/>
</papget>
</pre>

The file is used later by giving it to the gcs process:

<pre>
.../gcs -layout my_fancy_papgets.xml
</pre>

===Buttons===
In the same way, user buttons from the strip can be dragged&dropped on the 2D map. However, they currently cannot be directly edited, and
attributes changes have to be done in the XML file. Two types of button are provided to jump to a block or to set a value:

<papget type="goto_block" display="button" x="10" y="300">
<property name="block_name" value="Standby"/>
<property name="icon" value="home.png"/>
</papget>
<papget type="variable_setting" display="button" x="10" y="250">
<property name="variable" value="launch"/>
<property name="value" value="1."/>
<property name="icon" value="launch.png"/>
</papget>

===Video===
A video stream can be rendered in a <tt>video_plugin</tt> papget, using the mplayer player:
<papget type="video_plugin" display="mplayer" x="300" y="250">
<property name="video_feed" value="my video source"/>
<property name="width" VALUE="320"/>
<property name="height" VALUE="240"/>
</papget>
or any video player which takes in option the X window id :
<papget type="video_plugin" display="plugin" x="300" y="250">
<property name="command" value="cvlc video_source --drawable-xid="/>
<property NAME="width" VALUE="320"/>
<property NAME="height" VALUE="240"/>
</papget>

===Development===
Graphical appearence of papgets is defined in <tt>sw/lib/ocaml/papget_renderer.ml</tt>. A renderer must implement the Papget_renderer.t class type interface (<tt>canvas_text</tt> is probably the simpler example) and listed in the <tt>renderers</tt> list to be available
in the edit popup box.

The XML configuration is parsed in <tt>sw/ground_segment/cockpit/papgets.ml</tt>: a new created papget identifier must listed here.

== Alarms ==

The alarm window displays a list of recent errors such as:
* Low battery warning
* Low altitude warning
* Autopilot mode changes (i.e. Manual, Auto2)
* Flight plan block changes

== Configuration Options ==
The GCS is highly configurable and modules can be added, removed, or resized as needed. In addition to this the gcs has many command line options which can be used when launching the GCS
 
See the [[GCS_Configuration|GCS configuration]] page for details.

== Flight Simulation ==
Complex flight plans should always be carefully tested prior to flight. See the [[Simulation|simulation]] page for details.

==Related Links:==

Users

2009-02-23T20:06:48Z

Tc78: /* Europe */

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

==Need help adding your information?==

To have your information added by another paparazzi user, please send me an [http://www.rcgroups.com/forums/showpost.php?p=6575288&postcount=1 EMAIL] at with the following:
*Name
*Email
*Location
*Hardware
*Join date
*Current activities / project status

== Wiki pages ==
add a link to your users wiki page.

[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]

[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]

[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]

[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]

[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]

[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]

==Asia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status !! Wiki
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4 || 5
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|- style="background:bisque; color:black"
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet
|}

==Europe==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status !! Wiki
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV. |||[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz, Austria || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| FelixR || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter
|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.
|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.
|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.
|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.
|- style="background:bisque; color:black"
| [mailto:chebuzz_at_gmail.com David "Buzz" Carlson] || Cyprus || Tiny 2.11, Lynx EDF & GWS SloStick, 9XTend datalink ||| 2008 || Quite a few AUTO2 flights. Plane currently grounded due to a TX run-in with a 1 year-old. Currently working on getting new TX and completing CBP store setup.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4 || 5
|}

==North America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status !! Wiki
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Tuning IR sensors, building removable sensor mount. Preparing for flight tests w/ Easystar.
|- style="background:bisque; color:black"
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 ||
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. ||| [http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4 || 5
|}

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status !! Wiki
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV). Multiplex Mentor ||| 2008 || Paparazzi AP and RF modems are installed, wired and working. Need to install IR modules, complete airframe build and tune AP. On track for first flight the end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4 || 5
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status !! Wiki
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4 || 5
|}

Users

2009-01-27T00:34:44Z

Tc78:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 from PPZUAV, Multiplex Cularis, 9Xtend modems, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Debugging Tiny-GCS interface. Possibly first test flights in late Jan 09.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}