Drone 2.0 controlling library for C#/.NET and Mono, with video support. Built over the original AR.Drone SDK 2.0.1 - using lastest drone firmware. we got ability to create command chains, thus basic autopilot is avalible now, for details please check Avionics.Autopilot module and simple example in demo application either. If case you are looking for Windows RT/Windows Phone support please check this project ARDrone2Windows. FFmpeg.AutoGen - .NET wrapper for FFmpeg. This library is stable now. All major features are supported - video, configuration and control. Please note that this library still under development, so please don't be suprised if you find some functionality missing or undocumented. How to build from scratch: For the video support please review: Usage section of the FFmpeg.AutoGen project.Drone solution with MonoDevelop, VS2010 or VS2012. Please note: for opening solution in VS2010 you should have Microsoft Visual Studio 2010 Service Pack 1 installed.

The solution includes Winform application - AR.Drone.WinApp, it provides minimalistic interface for controling and displaying video from the AR. GNU Lesser General Public License (LGPL) version 3 or later. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. C# Application for controlling the Parrot AR.

Drone 2.0 with the Myo armband by Thalmic Labs. Current state: The application is able to controll the drone via keyboard, Xbox360 controller or Myo.parrot ar drone bergen Documentation can be found at Implementing Gesture Control for a Quadcopter.pdfparrot ar drone bereik Windows Vista or newer because of the Xbox controller. parrot ar drone bergenUnder Windows XP, you'll need special drivers for your Xbox 360 Controller. parrot ar drone 2 ricambiYou can find them at this address : XBox 360 Controller for Windows Software (cited from XInputDotNet Project page)parrot ar drone pil

Myo Connect installed (if you want to use myo) To compile the setup-project, you'll need the Visual Studio Installer Projects Extension Download the MyoPilotInstaller.zip from the repository. parrot ar drone perduExtract and execute Setup.exe. The wizard will guide you throught the rest of the installation. Execute "git submodule update --init --recursive" after "git clone". Compile with Visual Studio. Download with manual zip downloads: Download submodules (folders with @ behind the name in github) manually and place it in the folder of the submodule. Currently this is AR.If you can navigate throught your folders like you can in github, you've done it correctly. Reading the drone config may return zeroes which causes the app to crash. Changing the video stream resolution may cause a MemoryAccessViolation because of a race condition. Ruslan Balanukhin for AR. Remi Gillig for Xbox360 controller API: XInputDotNet

Reegan Layzell for Myo language bindings Myo.Net Dave Gandy for iconic font: Font Awesome Jutta for drone icon: DeviantArtThe terms the API code uses to refer to axes of movement are as follows:You can command the drone by sending it strings called AT commands. There are seven different categories of AT commands, but only two are required to fly the drone, and are the only ones included in the API:The drone needs to continuously receive commands for it to remain responsive. If the drone doesn’t receive any commands for two seconds, it assumes the connection has been lost, and it will ignore any further commands. If this happens, you need to close and re-establish the connection before you can continue to pilot the drone. DroneConnection.cs contains methods that allow you to do this.Once a connection has been established, we can begin to send the drone messages:The AR.Drone 2.0 communicates with other devices through its own wireless network. Sending the drone instructions is as simple as connecting your computer to the drone’s network, opening a UDP connection to the drone (I.P. 192.168.1.1, Port 5556), and then sending commands over this connection.

The code to connect to the drone is contained inside DroneConnection.cs:AT commands have very specific formatting, and consist of four parts. An improperly formatted command will be ignored by the drone. The different sections of an AT*PCMD command are highlighted below:Header: The type of the AT commandSequence Number: The sequence number is used by the drone to keep track of which commands it needs to execute. The drone will not execute any commands with a sequence number lower than the highest sequence number it has received so far. The first command sent should always have a sequence number of 1, and each command sent subsequently should increment this number by 1. The sequence number can be manually reset by sending a command with the number 1.Payload: This carries the command arguments. Its format and content vary from command to command. In the AT*PCMD command, the first value is a flag indicating whether the drone should do nothing (low) or move according to the other arguments (high).

The next four values denote roll, pitch, vertical speed, and angular speed respectively. These values are floats ranging from [-1, 1], where (0, 1] represents movement speed in one direction, and [-1, 0) represents the other. A 0 causes the drone to remain stationary along that axis, a 1 or –1 is maximum movement speed in their respective directions, and each value between is a fraction of the maximum possible speed. For example, in the pitch argument, a .75 would cause the drone to move backward at 3/4 maximum speed, while a –.5 would make it move forward at 1/2 the possible speed. However, the drone doesn’t respond to values in the [-1, 1] range. The actual value that needs to be inserted into the AT command is the signed integer value represented by the bytes the float is actually stored in. This conversion is done for you in the FloatConversion method in DroneMovement.cs.Carriage Character: A newline character. Use the one specific to your environment.DroneMovement.cs has a set of methods to generate AT*REF and AT*PCMD commands, all of which take the current sequence number as an argument, and return a ready-to-send AT command.

Some methods take additional arguments to control the movement speed. An example of one of these methods is: The drone is controlled with an continuous loop that sends a command to the drone every 30 ms. Each cycle, the loop determines the next command, sends the command to the drone, and then increments the sequence number. The method is asynchronous and awaits the call to System.Threading.Tasks.Task.Delay() so that it doesn’t block the UI between cycles.You need to implement the InputProcessing.NextCommand() method to return an AT command based on criteria of your own choosing. The API includes the class InputState.cs that you can use to pass information between your UI and the control infrastructure. The example App contains an example of this.I’ve included a simple example App to demonstrate how to use the API. The App allows you to connect to the drone and make it take off, land, and rotate. It also illustrates how to pass input information between the UI and the control infrastructure using InputState instances.

In the App, FlyingPage contains the method GetState() that returns an instance of InputState. GetState() looks at the input the App is receiving, then creates and returns an instance of InputState containing that information. InputProcessing.NextCommand() calls GetState, and then interprets the state to decide on the next command to send: The command decision is made in order of importance. Takeoff and landing commands are the most important, followed by movement commands. If there is no other command to send, NextCommand() returns a null command so that the drone will continue hovering and listening to the connection.Once NextCommand() has been implemented, all the App needs to do is connect to the drone and initiate the control loop by calling DroneConnection.ConnectToDrone(), followed by calling DroneControl.ControlLoop(). In the example App, this is done in the handler for the connect button. Once the control loop is running, the drone is ready to fly!The API should give you everything you need to get started writing drone Apps for Windows Store.