All Posts (11086)

Sort by
Developer

Simple Distributed Flight controller network

3689685000?profile=original


Over the last few years of flying FPV I have flown one piece foamie flying wings of around 1 meter span pretty much exclusively.The main advantage of this type of aircraft is that the electronics can be distributed anywhere within the wing. The plane is stored assembled, therefore there is no need to assemble at the field. Servicing and accessing components is easy.

My main interest lies in soaring though. A 1 meter flying wing foamie loaded with electronics and sensors just doesnt soar very well!

The problem with FPVing a large soaring model is the issue of where to put the electronics and how to deal with all the sensor connections. From my flying wing experience, I know that for best rf range, it is optimal to separate the various components,in particular the GPS, RC receiver and video transmitter.  I also have bad memories of my first wing and tail FPV model, an EasyStar, where I put everything in the fuselage. I remember hours of fiddling with wire and connectors in the tiny fuselage. Each change of the flight-battery involved pulling wiring out and moving various components and connectors, which is when I decided to build flying wings in future. 

Recently I decided I really want a soarer type model but one in which I can place arbitrary electronics in the wings.

I bought a 12 foot Thermal soarer ( Hobbyking Aether ) and resolved to solve once and for all the problem of maintenance and assembly at the field.

I wanted to use a similar layout as I had come to use in my flying wings, putting various components in the wings, since I know it works well from an RF perpective and is easy for maintenance ( assuming you dont mind ironing solarfilm :))

I decided to use a distributed system, broken into subsystems with links where the aircraft needs to be physically disassembled for transport. Each part is to be connected with one connector. For the Aether that means wings to pod and tailboom to pod connections. (I made the Aether boom detachable so that it can be disassembled from the main fuselage pod for transport, but that now means making the elevator and rudder connections easily dismantleable)

  • In the port wing I provisionally put the Rc Receiver and airspeed sensor. There are also 2 port flapperon servos.
  • In the starboard wing I provisionally put the GPS, magnetometer and the 2 starboard flapperon servos

In the heading diagram the red edges are where there will need to be connectors. There is one connector for each wing to the fuselage pod conection and 1 connector for the tailboom, The black edges dont need to be disassembled at the field since they are all in the Pod .

For the tail "link" I decided to just run the Elevator and rudder servos direct from the flight controller so they dont need anything fancy, however, for the wings I figured I would make a "sub-hub" with a serial link to the main FC in the Pod.

The requirements on the sub hub were

  1. to provide bi-directional comms between the FC and sensors and servos.
  2. to provide power to the servos.

I looked at 3 comms choices. CAN, USB , UART. In each case the physical cable consists of 4 wires, Power, Ground and 2 signal wires.

USB would be interesting with the FC as the host . Might work well with a Raspberry PI FC in particular
CAN also looks interesting but decided to avoid it for now.
Both of these I should certainly investigate for the future, but for V1 I decided to use UARTs.
On the physically short links ( under 400 cm) a full duplex per wing baud rate of 1 M bit per sec should be achieveable with little overhead The sub hub can be attached to a PC for testing ( also true of the USB option). CAN seeems overall a bit heavyweight and a bus topology doesnt seem that great. (I think a star works better for a plane)

For  power to each sub-hub on this version,I opted to specify a minimum of 7 V and a maximum of 20 V at max 10 watts per link. That means the system can be powered direct from 2S to 5S flight batteries and each wing has 2 amps at 5V for powering the servos.

The actual sub-hub board has a mcu and a switching regulator on board to provide servo outputs, and various connectors to which can be attached some combination of a serial device, an I2C device, Rc Receiver and analog inputs, for the various devices that need to be connected.

With that in mind I am currently designing the sub-hub board.

Read more…
3D Robotics

3689685046?profile=original

We've been evaluating this on Pixhawk-based platforms, and it's a performing well. Best used with other sensors, such as cameras, but a lot better than just sonar. 

From IEEE Spectrum:

The World Wide Web is the most famous technology to emerge from the needs of the international particle physics research center CERN, but it’s not the only one. In the latest example, a lightweight, inexpensive (and maker-friendly) range sensor has come about because scientists want to use drones to survey tunnels and vaults without smashing into expensive and difficult to replace equipment.

They approached a drone services company, but it was soon discovered that there was no way to create a drone that was small enough to operate in the cluttered spaces and yet had sensors that would let it locate itself with enough precision to avoid collisions. The result was the founding of Terabee in 2012, explains Massimiliano Ruffo, the company’s CEO, who I met at CeBIT’s airy press center yesterday. 

In 2015 Terabee was recognized formally as a CERN spin-off and selected to join the research center’s business incubation partner Innogex. Terabee began selling its first sensor, the TeraRanger One, the same year.

The matchbox-sized TeraRanger One sells for 125 euro (US $140) and weighs just 8 grams. Measuring the time-of-flight for infrared pulses generated by an LED allows the TeraRanger One to determine the distance to a single point-like region ahead 1000 times per second. The maximum distance that can be measured indoors (or, of course, underground) is about 14 meters, with a range accuracy of four centimeters. Ruffo says that with some sensor-by-sensor calibration and a slower rate of measurement, the accuracy can be increased to about two centimeters. Maximum distances closer to five to six meters are possible in sunlight.

The TeraRanger One’s onboard electronics takes care of all the post processing required from the sensor’s raw time-of-flight data and spits out the distance as a number that represents the number of millimeters measured. A5-volt UART serial interface is used by default, and a 5 V I2C bus can be used with a firmware change, making the sensor trivial to hook up to an Arduino, and only slightly more complicated to connect to a Raspberry Pi. (That’s due to the latter’s aversion to voltages higher than 3.3 volts).

Inexpensive ultrasonic range finding sensors of TeraRanger One’s size and weight have been available for some time, but they lack its speed and angular precision. LIDAR systems, which often employ a rotating mirror to scan a sensing laser beam around, are also fast and provide high resolution at good distances but are bulkier and more expensive than the TeraRanger One. (Although that may change if DARPA’s phased-array LIDAR-on-a-chip ever comes to the mass market.) Stereo vision systems are another alternative for rangefinding, and can provide depth information over a wide field of pixels, but Ruffo believes that TeraBee again has the edge because the time-of-flight data produces more reliable distance measurements over a longer range.

For systems that require more complex measurements, such as those the doing the kind of SLAM (simultaneous location and mapping) required for the original CERN surveying, TeraBee currently offers a hub which allows measurements from up to eight separate sensors to be integrated. A pre-built eight sensor “tower” is in the works, says Ruffo, and the company also offers an evaluation version of a small LIDAR-type scanning platform. 

Read more…

It has been a typical scenario for drones to have an onboard camera and a key requirement to transmit live camera feed to ground devices. As a next step we also want the drones to acquire the images into the onboard processing framework and apply some computer vision algorithms or even simple image processing to enhance the raw image. And then we would like the processed image stream to be sent to ground devices as well. Once we have the video stream in our laptop or mobile, why not interact with it and send the inputs back to the onboard computer? Welcome to FlytOS!

FlytOS is ROS based framework and ROS enables a cleaner modularized way to process and share data. FlytOS image pipeline is as follows:

VideoSetup.png

The basic idea is to get all image data in the ROS pub-sub bus. Then an image processing module can subscribe to raw images and publish back processed images. A web video server can subscribe to any of the available image topics and stream it to ground devices on web as needed.

The images are captured from USB camera attached to FlytPOD or ODROID and are published on ROS using a cam driver. The ROS based web video server subscribes to an image topic and provides mjpeg stream over http. This stream can then be viewed in most modern browsers without any plugin or client software. FlytOS provides options through its web APIs to list available stream topics and start/stop a particular stream. You can also get a snapshot on demand. Further, you can interact with the image stream e.g. select a region of interest and send that information back to the onboard computer. We have tested this setup and it works well as can be seen in the demo video above.

However, there are several constraints when we think of drone video streaming. We should be able to

  • Capture the images from camera into the onboard processing framework like FlytOS for image processing (as against having camera as payload and transmitting images directly to ground)

  • Transmit raw as well as processed images to ground

  • Get a low latency/lag real time stream as stale data may not be helpful or sometimes even harmful

  • Have relatively low power/processing requirement to be suitable for onboard computer

  • Have relatively low bandwidth requirement

  • Get good quality image/video

  • Have adaptive streaming based on network bandwidth

 

The current setup in FlytOS serves the first two items well and reasonably tackles the next three points. It is not yet focused on HD quality and does not have adaptive streaming. Additionally, we wanted to stream the video to a web browser without the need for a client software or plugin for easy integration with web apps and cross platform accessibility. A good alternative web oriented implementation with real time focus could be WebRTC however it does not really support ARM Linux yet.

 

In any case, having multiple parallel streams being served directly from the drone to several ground devices is probably not an ideal scenario as it would put strain on the onboard computer and its network link. Alternate setup is to stream the images from the drone to a single computer on ground. This ground device would be a distribution server (preferable in cloud) that can then stream parallely to multiple client devices and can also be a WebRTC setup. FlytOS will continue to improve upon its solution and such a streaming architecture could be the next step.

 

Meanwhile, you can get started with FlytOS right away, test video streaming, try out sample apps and we would like you to give us your feedback and discuss your views on the next steps.

 

Note: The demo video above shows sample of Object Detection and Tracking. This is accomplished using an Object Tracking module in FlytOS. We would talk more about what is available and how it works in the next article. Stay tuned!.

 

Download FlytOS:   http://flytbase.com/flytos/#download (get updated .deb if already downloaded)

Video Streaming API reference: http://docs.flytbase.com/docs/FlytAPI/REST_WebsocketAPIs.html#video-streaming-apis

 

Read more…

I finally received my Raspberry Pi Zero,  just in time to get into the DIY challenge of building a smart drone with the Pi Zero and APM under 100$. I called this project: MINI-Zee

3689684951?profile=original

How this can be done?

Well first of all, thanks to Victor and the team at Erle Robotics for releasing the plans and software of their PXFmini.  This is a real inspiration for building my own board, because all the parts are available at a cheap price and are relatively easy to assemble and interconnect using through-hole breadboard, providing you are very experienced with this type of build.  Thanks to Mirko as well, for having introduced a real DIY autopilot project that allows us to experiment with a fully working and well supported BeagleBone  based  ArduPilot  Cape called the BBBMINI.


3689684972?profile=original

Bill of Material (US$ - Transport & taxes excl.):

Raspberry Pi Zero                                      5.

MPU 9250 (SPI 9 dof IMU)                         8.

MS 5611 (SPI Baro)                                   9.

PCA 9685 (16 channel PWM Servo Driver)  5. 

3.3 v. regulator                                          1.

BEC 3 amps                                             3.

Breadboard, Resistors, Connectors, Misc.   7.

                                               AutoPilot:  38.

HobbyKing Spec FPV250 V2 Quad Copter

ARF Combo Kit - Mini Sized FPV         60. 

                                                     Total:  98.

*This is Banggood price; I had an ADAFRUIT –PWM on hand, and I really recommend going with ADAFRUIT, because of all the effort  they put on making a great tutorial and drivers for this product. Note: Just like Erle , the USB WIFI, GPS and the Radio Control are excluded.

Building:


A) Hardest part: Get a  RASPBERRY PI ZERO (Where is my Zero site)
B) Hardware - See BOM
C) Board Schematics : Erle pxfmini
D) Board Software: Erle pxfmini

E) LOAD LATEST Raspbian-Jessie

Disable serial Login (Allow GPS on serial Port)
Enable , I2C, SPI , Serial
Disable Console = Auto Log on a shell


F) LOAD RT-PREEMPT
http://www.frank-durr.de/?p=203
Load Test Result: TEST: T: 0 ( 1136) P:80 I:500 C: 100000 Min: 16 Act: 31 Avg: 32 Max: 157


G) MAKE ArduCopter

Special MINI-ZEE release:
1) The MPU 9250 is mounted on the Z-Axis, so we need to change : 

CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_PXFMINI
, _default_rotation(ROTATION_YAW_270)  = to ROTATION_NONE

2) The PCA9585 has no external clock, and the ESC are connected to ports 1-2-3-4, so we need to change: 

static RCOutput_PCA9685 rcoutDriver(PCA9685_PRIMARY_ADDRESS, true, 3, RPI_GPIO_27);      -to-

static RCOutput_PCA9685 rcoutDriver(PCA9685_PRIMARY_ADDRESS, false, 0, RPI_GPIO_27);

H) Fly the MINI-ZEE == Add these to /etc/rc.local

#wait till network is up and DHCP assigned address

while ! ifconfig | grep 192.168.2. >> /home/pi/bootlog; do
echo “no network, waiting…” >> /home/pi/bootlog
sleep 5
done
echo “Starting ArduCopter” >> /home/pi/bootlog

sudo /home/pi/ardupilot/ArduCopter/ArduCopter.elf -A udp:192.168.gcu-address:14550  -B /dev/ttyAMA0 > /home/pi/startup_log &

exit 0

I) FIRST FLY LOG:

3689684898?profile=original

Thanks to the damping platform, the vibration level is within specs. Video is available for anyone interested..;-)

Conclusion:

This project took about 20 hours to complete. As you can see, I really enjoyed  doing some hardcore DIY to demonstrate that it is still possible to build your own flight controller from a Linux Based system.  I do not recommend to try this as a first project, but if you are interested, get a BBBMINI, this is the best introduction to DIY  and if you want to fly a Raspberry Pi Zero, it is much  easier to buy a PXFMINI.

Read more…

3689684869?profile=original

A Senate bill to reauthorize the FAA contains provisions related to the manufacture of drones that could apply to home-built drones, as well as those produced by large consumer manufacturers. The bill in question, titled the Federal Aviation Administration Reauthorization Act of 2016, contains provisions that would have a significant impact on technology innovation by all manufacturers of small drones. With no size or weight threshold, the bill, if adopted, would add new and burdensome manufacturing, testing and approval restrictions to even the tiniest drones.  And, most disturbing, these restrictions could apply to hobby-built remote controlled aircraft or student-built drones, effectively prohibiting them from operating outdoors. The legislation could also retroactively ground already-built models that didn’t meet the manufacturing standards called for by the proposed legislation.

http://www.forbes.com/sites/johngoglia/2016/03/16/senate-bill-could-ground-home-built-drones-no-exceptions-for-hobbyists-or-students/#2740ef90a6f2

Read more…

3689684884?profile=original

VDOS GLOBAL LLC AND RPAS TRAINING AND SOLUTIONS PTY LTD HAVE ANNOUNCED THEIR MERGER FORMING COMPLIER ENTERPRISE.

This merger establishes a new market dominating force for both SME and Enterprise Clients in the UAS industry with offices and operations on the three continents of North America, Australia and Africa.

“We don’t make the Drones, we make them useful.”™ Brian Whiteside Co-Founder Complier Enterprise explained.

By bringing these two companies together, Complier Enterprise has the strategic foothold in the global market. The company’s founders are Brian Whiteside and Wayne Rochat. Brian Whiteside founded VDOS Global and is a former FA-18 US Navy Pilot and has been working with unmanned aircraft since leaving active duty in 2008. Wayne Rochat, who also developed RPAS Logger, has over 20 years of IT consulting experience pioneering enterprise support software working for companies like Oracle and has been training Drone operators and pilots in Australia since 2014. The new and improved “RPAS Logger” is now rebranded as the Drone Complier Enterprise app and is now available for iOS and Android devices with a free trial.

“Our goal is to deliver Safety, Simplicity and Savings to our clients with the ability to scale as they need. By reducing cost and managing risk through our patent pending app enabled enterprise support I am very excited by this merger as it allows us to offer our clients a new service while growing with them as they adopt and automate drone technology.” Said Brian Whiteside Co-Founder.

“This merger is the coming together of two clear market leaders, to form a new, and industry defining market force. We are combining best practice complying tools, world class drone training expertise and market leading drone inspection services, into one entity, to offer our clients an integrated service, not available anywhere else.” Commented Wayne Rochat Co-Founder.

Initial focus is on supporting established clients in the global insurance market and energy sectors.

To learn more visit: www.complierenterprise.com and for the app www.dronecomplier.com

Complier Enterprise
230 SW 6th St
Corvallis OR 97333 USA

1 / 8 Manning St
Kiama NSW 2533
Australia

Read more…

L1 RTK GPS board for DIY UAVs

3689684854?profile=original

Hey there,

Since we launched the Precis-BX305, the L1L2 board for RTK, we have received quite a lot of customer enquiries and questions. To meet or excel your requirement, we now officially launch the L1 RTK board (Precis-BX303) to fit your DIY testing needs and UAV applications at a very affordable price.

Precis-BX303 can be integrated to other host devices or served as an independent GNSS receiver. It dedicates to deliver high precision, reliable positions between rover and the reference antennas, which integrated versatile communication modules, including UHF module WI-FI module, Bluetooth module and USB2.0 port. It supports multi-GNSS RTK positioning, which improves the continuity and reliability of RTK positioning.

Want to know more about its key features and how it works? Take a look at www.tersus-gnss.com or drop us an email by sales@tersus-gnss.com

Read more…
3D Robotics

3689684839?profile=original

The Centre for the Study of the Drone has released a new report on the state of the growing commercial drone industry.

From the summary:

This report is based on an analysis of 2,732 Section 333 exemption documents issued by the Federal Aviation Administration between September 25, 2014 and December 31, 2015 to individuals, companies, and other institutions wishing to use drones for non-recreational purposes in U.S. airspace. This dataset offers insights into the shape and possible future direction of the nascent drone industry. We have analyzed these exemptions by date, location, types of intended operations, number of categories of intended operations, and types of unmanned aircraft to be used.

3689684905?profile=original

Our analysis yielded a number of key findings (Section II). The rate at which exemptions are granted has grown dramatically since the beginning of the Section 333 program. The number of intended operations listed in exemptions has grown from an average of 1.4 intended operations per exemption in the first eight months of the program to 2.38 intended operations per exemption in the final two months of 2015; this has significantly affected the overall spread of intended operations in the dataset. The data suggests the emergence of a “Various Uses” drone services business model, which has contributed to the increased number of intended operations listed per exemption.

We found an average of two aircraft listed per exemption, with an overwhelming majority of those—over 60 percent—being DJI-brand products. Exemption holders are located across all 50 U.S. states as well as the District of Columbia and Puerto Rico. The number of exemptions issued per state roughly matches the spread of national population by state, with entities in Florida and Colorado holding a disproportionately high share of exemptions compared to those states’ share of the national population. A number of factors, including uncertainty in the regulatory landscape, local legislation, and advances in technology are all shaping the future of the Section 333 program and the U.S. drone industry as a whole. These factors are discussed in Section III.

Read more…
3D Robotics

3689684822?profile=original

This uses an updated version of the LIDAR-Lite sensor on a rotating mount. $245 is an impressive price -- backed!

From the Kickstarter campaign:

We wanted a scanning LiDAR for our projects and couldn’t find anything that was powerful enough and easy to use for a price we could afford. Comparable sensors are $1000 and up, so we set out to develop one ourselves.

We’re raising money on Kickstarter to manufacture Sweep so we can get them into the hands of makers, roboticists, drone enthusiasts and students. We’re really excited about making scanning LiDAR available to everyone!

Use Sweep for sense and avoid as well as navigation mapping. We'll provide all the tools needed to start developing more autonomy into your drone. 

 "At Dispatch, we are very excited by Sweep. LiDAR is a very powerful sensing modality and low-cost LiDAR will have significant impact as we develop and grow our autonomous vehicle fleet."

Uriah Baalke Dispatch Robotics

"The Sweep is a great fit for high school robotics. It is easy to setup and use, robust, and is at an incredible price point. Students can quickly explore mapping and navigation problems with little prior experience. Best yet, the Sweep is virtually student-proof – it can survive a high school lab environment."   

Charles Williams Mentor, Cupertino High School Robotics

Combining technology and art can produce really fun and interesting pieces. Use Sweep to detect where someone is or activate different components to make your next art project interactive!

Have you ever wanted to quickly get the dimensions of a room? Measuring tapes are a hassle! Use Sweep to quickly grab a room's dimensions in a couple seconds. 

Security / People Tracking

Sweep can be used to create a "virtual curtain", meaning it will sense anything that interrupts a particular area. Use it to detect when someone walks through a doorway or tries to touch something they shouldn't! You can also use Sweep to track people moving within a space. Perhaps you want to have your smart lights switch off when you leave a room and before you enter another.

Whatever you can imagine!

Sweep is already useful for several applications, but there are so many more that haven't been discovered yet and we're super excited to see what you come up with!

 What makes Sweep different?

Sweep utilizes a sensing technique that differs from most other LiDAR on the market, which allows us to use lower power components to perform long range measurements. This lowers the cost of the components, but requires more time per measurement. Sweep is the first commercial scanning LiDAR that utilizes this technology.

Sweep is designed to be modular! As we continue to improve the capabilities of the sensor module, we'll be able to offer upgrades without the need to replace the entire scanner. 

Specifications

The scanning capabilities of the Sweep allow you to adjust the rotation speed on the fly so you can slow it down for more detail, or speed it up for fast reaction times.  

Sweep uses a laser that has been tested to be eye safe (even if you decide to stare at it straight on - not advised).  It operates in the infrared spectrum which is invisible to the human eye.

Communicating with Sweep is really simple! We're including our small adapter for those who want to connect to any computer using USB. If you want to connect Sweep to lower level controllers, just hook it up directly to UART. 

We designed Sweep to be very small and light! It fits right in the palm of your hand and weighs a tad less than most smart phones today. Sweep is also really quiet, something you may have never thought about until you've used one that makes annoying sounds as it spins. You won't be hearing this scanner. 

For more detailed info checkout the datasheet here:

What each Sweep Scanner includes

Scanse Visualizer

Our visualizer allows you to view the sensor data (like this room with someone walking around above), record and playback data, change settings, and update the firmware. It will be available on Linux, Windows, and OS X. 

ROS Support

We’ve already developed a ROS driver for Sweep as well as an example publisher node to start using Sweep in ROS right away.

SDK: python, javascript, C/C++

Using Sweep in your own project starts with the SDK. We're developing drivers for several major languages and will be creating example projects for platforms like Raspberry Pi, Arduino, and more. 

Example Projects / Drivers

These software projects and drivers are already in development and will be released as soon as they are complete.

Pixhawk autopilot driver: This driver will make available the angle and distance for the centroid of nearest object bodies within range. This uses a special mode with Sweep and does not require additional processing by the flight controller.

National Instruments roboRIO driver: This driver will provide the complete scan data on each complete rotation which can then be used to guide a robot.

Movement Tracker: This example application for the Raspberry Pi will allow you to track moving bodies within a space. Set threshold areas to activate or deactivate when entering or leaving them. Trigger an IFTTT recipe using the Maker Channel to do things like turn lights or security systems on/off.

Room Dimensions: This example application for the Raspberry Pi will output room measurements with centimeter accuracy.

Kickstarter Funding

We have three main goals for this kickstarter project:

  • Kick off production - pay for tooling / high volume component orders
  • Continue development of our visualizer application 
  • Develop more useful example projects like the ones mentioned above and more!

We are committed to delivering a high quality product. We have a beta tester community that has been giving valuable feedback on our development units. Once we get production units from our contract manufacturer, we will go through another round of development tests before shipping to our customers.  

We have a long standing relationship with our PCB manufacturer that has produced quality boards from the beginning and will continue to produce our boards for production.

The majority of our product will be made from high strength injection molded plastic. We have extensive experience designing injection molded components, and will be using a mold house that has produced high quality parts for us in the past.

Timeline

Read more…
3D Robotics

Design files for IRIS+ now open source

3689684633?profile=original

Good news for IRIS+ fans. We've released the CAD files as STLs, so you can 3D print any replacement parts you need for free, including improved versions of the legs that are 50% lighter and require less support when printing. 

3689684647?profile=original

Our friends at MyMiniFactory are hosting these and have prepared a great tutorial on how to use them:

3D Robotics have been strong adovcates of open source collaboration and their IRIS+ and MADE FOR SOLO projects are testimony to that. 

If that wasn't enough, in all their awesomeness they have decided to give back to the community by giving away the files for the IRIS+ for free!

Over the last week MyMiniFactory has been building the first ever 3D printed IRIS+, so as to document the process and highlight any issues along the way.

In light of this Kirby Downey has released an optimised version of the arms and legs which are up to 50% lighter and require less support - download here.

 

Follows MyMiniFactory's step by step guide:

 

1) Remove the bottom shell by taking out the screws

2) On this shell, remove the LED and USB devices and insert them on the 3D printed bottom shell

3) Remove the screws that hold the bottom plate, and remove the top shell

4) On the top shell, disconnect all the wires from the pixhawk remember the way they were connected and where they were going

5) Take out the pixhawk and all the components that are are glued or screwed to the plate and place them on the 3D printed top plate

6) On the bottom plate, remove the connections to the pixhawk and remove the screws that hold the arms of the drone

7) Remove the foam carefully from the bottom plate

8) Take out the screws that holds the board and put it back the 3D printed small plate

9) Remove the 3 clips that holds the wires in the center of the arm

10) Close to the motor, make two marks on each wire so you don’t mix them once they are cut.

11) Cut the wires, take out the 2 screws that hold the motor and insert it into the 3D printed arm.

12) Solder the wires (you can use heat shrink wire wrap to hold your soldered joint) and put the clips back.

13) Screw the arms to the plate and the shell

14) Take out all the components that are glued to the top shell and place them into the 3D printed shell

15) Glue the foam of top plate back on the small plate.

16) Connect all the wires to the pixhawk again.

17) Screw the 3D printed top shell and the piece for the gimbal at the bottom.

Read more…

Lone Star Drone Rodeo and Texas Big SAR!

3689684767?profile=originalWe are finally ready to push this bit of news out to the community at large, albeit a little close to the event.  We have a 1,400 acre ranch down here near Santo, TX where the land owner has put together multiple drone based events under the name Lone Star Drone Rodeo! 

There are three segments we will be sporting, a drone cage (for those new or wanting to combat each other), Drone Racing hosted by both the DallasFPV and the N.E. Dallas Speed Addicts for a MultiGP regional qualifier and finally a drone based Search and Rescue event hosted by the North Texas Drone User Group with dozens of missions designed to interface with existing professional ground based SAR groups.  We will also have a discounted course hosted by UAS Academy specifically designed and certified to teach SAR drone operators how to effectively plan and execute missions in a SAR environment. 

This event has been almost a year in the making and what we would love is for you to form a team and come on down to Texas!  If you are participating in the SAR portion the entry fee is waved!  You can also camp ($5.00/night) on site or we have a list of nearby places you can stay.  We will have policemen, firemen, company presidents, SAR personnel as well as every drone racer and drone SAR pilot in the area attending!  Come to see it or come to network!

If you are more of the video type, here is a story that aired on the event.  Sponsorship slots are still open, call Martin at 940-452-3004 for a sponsorship/vendor form, if you are a SAR group please contact us to participate at 980-333-2301 because the more the merrier!

Read more…
3D Robotics

3689684784?profile=original

If you saw Rafaello D'Andrea's amazing TED talk from a few weeks ago, you will have been impressed by how his team solved the problem of controlling VTOL aircraft in the vertical position with just two props (VTOL aircraft are notoriously prone to wind disturbance when lending in vertical mode). Now that technology is coming to market!

From IEEE Spectum:

Quadcopters and other helicopter-style drones can take off and land vertically with pinpoint precision, but they aren’t as fuel efficient or as fast as fixed-wing drones. On the other hand, fixed-wing aircraft normally require either catapults or relatively long runways to get up to speed before taking off. A spin-off company from the Autonomous Systems Lab at ETH Zurich is trying to provide the best of both worlds with its eponymous Wingtra drone.

The Wingtra takes off vertically (it’s held upright on the ground by fins projecting from the wings and tail), then levels out into horizontal flight. For landing, the general process is reversed, but with the assistance of a camera located in the tail. This camera allows the drone to spot a printed target placed on the ground. Once in sight, the Wingtra will autonomously descend to touch down on the target, within about 10 centimeters of bullseye, says Wingtra’s Leoplold Flechsenberger. 

The battery-powered Wingtra can fly for about an hour, during which time it can travel 60 kilometers. There’s no need for continuous control by the operator, as the Wingtra will follow its flight path autonomously. A removable module can carry different payloads: Those looking to inspect railway lines or survey crops for precision agriculture might choose to equip the drone with a high-resolution LIDAR or camera package, for example. Alternatively, an add-on freight module lets the Wingtra carry up to 0.5 kilograms, whichFlechsenberger says might prove invaluable in dispatching medical supplies to rural areas.

The drone was designed with simplicity in mind. There are just five primary components: a set of wings combined with the fuselage to form a single body, plus two propellers and two flaps. The drone doesn’t even have a forward-looking camera (although Flechsenberger says one may in added in later versions). The price has yet to be announced, but as the Wingtra is aimed at professional and institutional users, it’s likely to be considerably more than what one would expect for anything aimed at consumers or prosumers. The system is expected to be commercially available in 2017, says Flechsenberger (who adds that Wingtra is hiring to accommodate its rapid expansion). 

Read more…

IMG_3596.jpg?width=700

I'd like to introduce you our new frames .. 
we have launch our brand new carbon fibre hexacopter and octocopter. 


FC6-900 - hexacopter, carbon monocoque , 900mm diameter , pluggable arms, dust- and rain proofed, weight without battery 1800g. max battery inside carbon monocoque 6s - 10.000 mah. 
flighttime with max. take of weight 5kg. - around 30 min!

FC8-1200 - octocopter, ( also available as x8 ) carbon monocoque, 1200mm diameter, pluggable , dust- and rain proofed, weight without battery 2600g
max battery inside carbon monocoque : 2 x 6s - 10.000 mah 
flighttime with take of weight 8000g, around 20 min.


MADE IN GERMANY!

IMG_3599.jpg?width=700IMG_3600.jpg?width=700

IMG_3601.jpg?width=700

img_3052_1024.jpg?width=700

Read more…
3D Robotics

3689684452?profile=original3DR has just released an update to the Solo app on iOS and Android that adds a new GoPro Burst camera mode as well as improved FollowMe functionality (see below). This continues a monthly feature/performance update schedule that is adding a ton of new funtionality. Next month's software update will dramatically improve GPS performance and reduce lock time, along with adding the much requested "boat mode" (launch from a moving boat). 

And don't forget that the special 20% off discount for DIY Drones members only runs another two weeks. Enter "DIYD20OFF" at checkout to get a Solo + Gimbal for just $799. (That code also works on everything else in the 3DR store except for GoPro cameras and SiteScan)

Finally, if you're a developer you'll love the new DroneKit Python 2.0, which works with Solo or any other APM-based copter. Previously, Solo was running Dronekit 1.0, but it's now native 2.0 so can run any Dronekit Python apps right out of the box. And it's now officially part of the open source Dronecode software stack!

From the announcement:

Join us in welcoming yet another new weekly Solo® app release into the world!

This update unlocks “burst mode” on your GoPro® HERO® 4 and HERO 3+ Black cameras — the mode is accessible from the Solo app while you’re flying — and it also enhances the range and clarity of your FPV.

There’s also a new developer update! DroneKit Python 2.0 now makes it easier to develop for Solo. You don’t have to be a hard-core drone developer to tinker with Solo software; hobbyists and other interested people can get involved, even create third-party consumer software in the future. Learn more about DroneKit Python at the bottom of this post.

This new release is available now for download on both iOS and Android. Note that the app update does not require a Solo update. (***We also highly recommend turning on “auto-update” so your Solo app will pull these new releases automatically.***)

ABOUT BURST MODE

A still photo feature for GoPro. In “Burst Mode,” your GoPro HERO 4 can shoot up to 30 stills in one second (default). You can change both the number of photos (30, 10, 5, 3) and the length of time it takes to shoot them. For instance, shoot 30 photos in the span of one second, two seconds, three seconds or six seconds (5-photo and 3-photo bursts only available for a one-second lapse).

Burst is great for shooting action and fast-moving subjects. First, the number of shots and the fast shutter speed mean you can choose the best shot(s) from an array, where with a fast-moving subject it would be very difficult to capture a single perfect photo manually. Additionally you can use the whole series to illustrate a motion sequence.

Burst is particularly interesting for Solo. It’s not just your subject that moves — Solo moves as well. With burst, you can not only capture a subject’s motion sequence, but you can move Solo as you’re shooting a burst of photos, for some very cool dual perspective shifts and even parallax in a sequence of stills.

Challenge: Use burst while panning or yawing Solo to add an extra dynamic to the narrative of your subject’s motion.

Access burst mode in the GoPro settings menu of the Solo app.

Burst specs:

  • 30 photos/1 second (Default), 30 photos/2 seconds, 30 photos/3 seconds, 30 photos/6 seconds1
  • 10 photos/1 second, 10 photos/2 seconds, 10 photos/3 seconds
  • 5 photos/1 second
  • 3 photos/1 second

ABOUT DRONEKIT PYTHON 2.0

DroneKit-Python is an SDK for developers to create Python apps that communicate with vehicles over MAVLink. It provides developers with programming access to a vehicle’s telemetry, access to status information, along with enabling both mission management and direct control over vehicle movement and operations.

The SDK is designed for use in onboard companion computers, supporting advanced use cases like high-level path planning, computer vision, 3D modelling and more. You can also use this SDK to control drones from desktop computers and ground station apps, communicating easily over a higher-latency RF link.

Version 2 is essentially a ground-up rewrite, taking into consideration the major pain points from our library while developing for Solo: performance, ease of use, ease of development, extensibility and testing. DroneKit-Python 2.0 is designed to make the on-vehicle development process easier, more efficient and more robust all around. It now supports development on all copters.

Features:

  • Quick to get started: shortest example is just 3 lines of code
  • Embeddable as a Python library into any application
  • Multi-vehicle support in a single application
  • Create vehicle subclasses and add support for new MAVLink messages
  • Simplified state synchronization calls
  • Clean and comprehensive documentation and guides
  • Easy to debug and test with Software in the Loop
  • Extensive cross-platform tests (Windows, OS X, 

  • Forums: http://discuss.dronekit.io/
  • IM: https://gitter.im/dronekit/dronekit-python
  • and Linux)

Resources:

Read more…
3D Robotics

3689684699?profile=original

Very interesting new research from George Mason University on the risks to people of drone collision, based on wildlife strike data:

In December 2015, the Federal Aviation Administration (FAA) announced a new interim final rule that for the first time imposed regulation on the operation of unmanned aircraft systems (UAS) as model aircraft. In the name of a safe national airspace, the new regulations require operators of drones weighing more than 250g (0.55 pounds) to register with the agency.

Yet many drones weighing more than 250g are little more than toys. Do they really pose a risk to the airspace? To explore this question, we examine 25 years of data from the FAA’s wildlife strike database. Although aircraft collide with birds many thousands of times per year, only a tiny fraction of those collisions result in damage to the aircraft, much less human injuries or deaths. The most serious reported incidents typically involved flocks of large birds. Since the addition of UAS to the airspace is similar in many respects to an increase in the bird population, we conclude that the risk to the airspace caused by small drones (for example, weighing up to 2kg, or 4.41 pounds) flying in solitary formation is minimal.

Overview of the Data

US national airspace is home to an estimated 10 billion birds, some of which occasionally interfere with civil aviation. To track the risk this wildlife poses to human flight, the FAA has been collecting reports of aircraft collisions with wildlife in the National Wildlife Strike Database since 1990. Strike reporting is voluntary. When a wildlife strike occurs, airlines, airports, pilots, or other parties report the incident through an online portal, with data about the aircraft, the flight, the species of wildlife struck, and extent of damage caused.

Compared to the enormous population of birds, damaging bird strikes are rare. Since 1990, there has been a sevenfold increase in reported bird strikes owing both to growing bird populations and to the growing ease of reporting strikes online. But as figure 1 shows, strikes causing damage have actually declined from a peak of 764 in 2000, thanks to bird management efforts from airports. Specifically, airports have mitigated bird hazards by focusing on eliminating natural attractants of the large bird species that are responsible for the most serious incidents, like waste disposal areas and wetlands.

Figure 1. Reported Wildlife Strikes Causing Damage, 1990–2014

WEBbird-strikes-charts1.png

Source: Federal Aviation Administration, Wildlife Strike Database.

When large birds are ingested in jet engines, they may cause substantial damage, including crashes. While these birds do not number in the billions, they still maintain a significant presence. The US is home to nearly 1.9 million turkey vultures, for instance, and between 2 to 3 million snow geese enter the United States each winter. Contrary to sensational media headlines, the skies are crowded not by drones, but by fowl.

Figure 2 illustrates that while the FAA has recorded over 160,000 wildlife strikes since 1990, only 14,314 bird strike incidents have resulted in damage. Of these, 80 percent were caused by medium- to large-sized animals. On average, only 3 percent of reported small-bird strikes ever result in damage, compared to 39 percent of large-bird strikes. Given the voluntary nature of strike reporting, the true percentage of strikes causing damage is probably much lower, as strikes that do not cause damage can be either missed or underreported.

Figure 2. Reported Wildlife Strikes, 1990–2014

WEBbird-strikes-charts2.png

Source: Federal Aviation Administration, Wildlife Strike Database.

Injuries are even less common. Among the 398 people who have sustained injuries as a result of bird strikes, 100 stem from a single incident: the famous 2009 crash of US Airways Flight 1549 into the Hudson River. This spike can be seen in figure 3. Prototypically, the culprit was determined to be a gaggle of geese, an unknown number of which were sucked into both jet engines immediately following takeoff.

Figure 3. Casualties from Wildlife Strikes, 1990–2014

WEBbird-strikes-charts3.png

Source: Federal Aviation Administration, Wildlife Strike Database.

In total, there have been 238 wildlife strike incidents in which there were injuries or fatalities. To get an idea of how many of these affect commercial aviation, we can exclude incidents in which the operator is listed as “business,” “privately owned,” “government,” or “unknown” to narrow the total number of commercial incidents to 37. We should view these 37 incidents over more than 25 years in the context of approximately 27,000 commercial flights per day.

In more than 25 years of data, only 12 wildlife strike incidents resulted in fatalities. Out of these incidents, three of the aircraft were helicopters, one was a homebuilt aerobatic plane, one was an experimental aircraft, and one was a privately owned McDonnell Douglas A-4 Skyhawk, a Vietnam War–era fighter jet. One aircraft was a Cessna Citation jet, and four others were small Cessna or Piper propeller-driven aircraft. Out of the 12 incidents with fatalities, only one involved a commercial airline: In 2000, an Embraer EMB-120 operated by Atlantic Southeast Airlines hit a pair of white-tailed deer on its landing roll. The passenger in seat 3C suffered injuries and eventually died from an infection. Not a single one of the fatal incidents involved a bird that was reported as “small.”

Estimating the Probability of Casualties and Damage 

Although the number of reported bird strikes has increased substantially since 1990, the increase is probably due to the improved ease of reporting. Figure 4 shows over time both an increase in the number of reported wildlife strikes and a decrease in the proportion of reported incidents with reported damage. This is consistent with the hypothesis that in the early part of the observed period, reports were frequently not filed at all if there was no damage to the aircraft. For our econometric analysis of the probability of a strike causing damage or injury, we focus on the years 2009 and later to compensate for the effect of limited participation in reporting in earlier years.

Figure 4. The Relationship between Wildlife Strike Reporting and Damage, 1990–2014

WEBbird-strikes-charts4.png

Source: Federal Aviation Administration, Wildlife Strike Database.

We use probit regressions of casualty and damage reports on bird species weight for birds (and flying mammals) for collisions taking place in 2009 or later with a single animal to estimate the probability of casualty or damage conditional upon a strike with an animal of a certain weight. Figure 5 shows our estimate that damage to an aircraft will occur in around 20 percent of strikes with animals weighing around 2kg. And in figure 6, we further estimate that the probability of the incident resulting in passenger injury or death is about 0.2 percent for animals weighing around 2kg.

Figure 5. Probability of Damage by Bird Size, Single Collision

WEBbird-strikes-charts5.png

Note: This chart uses data from 2009–2015 only.

Source: Federal Aviation Administration, Wildlife Strike Database.

 

Figure 6. Probability of Injury or Death by Bird Size, Single Collision

WEBbird-strikes-charts6.png

Note: This chart uses data from 2009–2015 only.

Source: Federal Aviation Administration, Wildlife Strike Database.

 

 

Estimating the Probability of a Collision

Bird strikes provide an excellent parallel phenomenon for estimating the magnitude of damage a small UAS could cause by colliding with a manned aircraft. But as previously mentioned, without an estimate of UAS strike frequency, the magnitude of damage is insufficient to properly gauge risk. The size of the effect has to be multiplied by the chance of it actually occurring.

In 2014, there were 13,414 reported collisions with birds and flying mammals, counting incidents in which flocks of birds hit an aircraft as a single collision. As there are on the order of 10 billion birds in US airspace, this means that plausibly 1 bird in 1 million collides with an aircraft every year.

Even if we take UAS operators to be about as deliberate and skilled at avoiding aircraft as birds, we cannot similarly estimate that 1 UAS in 1 million UAS will collide with aircraft every year. Not only are UAS operators able to reason about human-piloted aircraft and airfield landing patterns better than birds are, UAS have very short battery lives and may sit idle for months at a time. In contrast, an observational study of bird behavior near wind turbines found the average bird spends roughly equal amounts of time flying as perching. Flight time is much more variable, however, with some migratory birds potentially flying as long as six months nonstop. 

FAA commonly refers to “acceptable risk levels” for general aviation in terms of fatalities per 100,000 flight hours. Using the aforementioned finding that birds spend roughly half their lives in flight, the fact that there were 13,414 bird strikes in 2014, and an estimate of 10 billion birds in US airspace, we estimate that there are 3.06x10−5 bird strikes (both damaging and not) per 100,000 bird flight hours. This risk level is comparable to the 5x10−5 fatality risk cited by the drone registration task force as acceptable for general aviation, without even adjusting for the probability of injury or fatality.

To date, a UAS has never collided with an aircraft in US airspace. Given that there are likely now more than 1 million UAS in US airspace, if they had equivalent flight hours to birds we might expect at least one UAS collision with an aircraft per year. However, taking into consideration human agency and the far more limited time most UAS spend in the air, the true UAS collision rate is likely orders of magnitude lower.

What Bird Strikes Reveal about UAS Risks to the Airspace

The FAA has based its rationale for a consumer UAS registry on a growing incidence of UAS sightings and “near misses.” As its docket argued, “Pilot reports of UAS sightings in 2015 are double the rate of 2014. Pilots have reported seeing drones at altitudes up to 10,000 feet, or as close as half-a-mile from the approach end of a runway. . . . The risk of unsafe operations will only increase as more UAS enter the national airspace.”

In a 2015 investigation, the Academy of Model Aeronautics (AMA) called the validity of these near miss reports into question. Of the 764 near miss incidents recorded by the FAA, the AMA found only 27, or 3.5 percent, were genuine UAS near misses. Instead, the FAA had been counting simple sightings as near misses—even when the operators were fully compliant with current UAS regulation. The FAA has also counted several cases where the pilot had explicitly reported that it was not a near miss, and more than a dozen cases where the flying object was officially unidentified. The AMA therefore accused the FAA of creating fuel for sensationalized and inaccurate media reports which, with the benefit of hindsight, helped build momentum for its rulemaking.

Our analysis has been based on actual bird strikes, not near misses or simple sightings. We find in general that small UAS under 2kg pose a negligible risk to the safety of the national airspace. We estimate that 6.12x10−6 collisions will cause damage to an aircraft for every 100,000 hours of 2kg UAS flight time. Or to put it another way, one damaging incident will occur no more than every 1.87 million years of 2kg UAS flight time. We further estimate that 6.12x10−8 collisions that cause an injury or fatality to passengers on board an aircraft will occur every 100,000 hours of 2kg UAS flight time, or once every 187 million years of operation. This appears to be an acceptable risk to the airspace.

Our analysis has some limitations. First, birds and UAS are composed of different materials, so it is possible that UAS-aircraft collisions are more likely to cause damage or casualties than bird-aircraft collisions. Although the FAA requires jet engines to undergo bird strike tests, it does not require them to undergo UAS strike tests, so it is not possible to empirically assess the additional degree of damage potentially caused by more rigid materials. Second, our assessment of the damage and casualties caused by birds has focused on incidents in which aircraft collide with individual birds, as opposed to flocks of birds. The rationale for this decision is that UAS do not typically fly in flocks, and therefore, collisions with individual birds provide a better point of comparison. However, if swarms of UAS were to become an increasingly common operational pattern, one would want to revisit our analysis to account for that fact.

Since the probability of any collision with any UAS is around 3.06x10−5 per 100,000 flight hours, countries that have even higher cutoffs for regulation than 2kg can be said to be acting responsibly. For example, the United Kingdom and Denmark have a 7kg threshold above which recreational UAS operators must inform their nearest air traffic controller or fly in an approved flying site. For registration, France recently moved to a 2kg threshold, while Canada still has a generous 35kg threshold.

Although UAS at the above thresholds are more likely to cause damage and injury than the 250g cutoff adopted by the FAA, we still estimate that the probability of a collision remains at an acceptable level.

Read more…

This is quick intro to FlytConsole, the web-based setup/configuration utility, bundled with FlytOS. FlytConsole is served by the onboard web-server, which is a part of FlytOS. So, you can start accessing/configuring your flight computer without downloading/installing any GCS application. Just point your web-browser to your flight computer, and you are good to go! It is built using RESTful APIs and web-socket connections.

FlytConsole offers a clean dashboard with all key parameters in one place. It provides access to all regular GCS features, such as, frame-selection, sensor calibration, RC calibration, gain-tuning, autopilot-parameters, waypoint navigation, mavlink inspector and so on. Some new features, such as, esc calibration and motor testing have been introduced (more are being added).

Why is FlytConsole interesting? Because it is very easily customisable and extensible (built using simple html and javascript)! Further, it eliminates the need for installation of any special GCS software on the client machine; and can be readily accessed from even a mobile device. Most importantly, FlytConsole serves as a template, allowing developers to reuse the code, to develop their own custom user-interface for their drone applications. Future commercial applications will all need their own custom interfaces (along with custom onboard/cloud apps). A single/common GCS will not make the cut. FlytOS makes it super-simple to build commercial drone applications (onboard, web/mobile, cloud), integrate a variety of payloads, leverage the power of ROS and OpenCV (libraries for collision avoidance, computer vision, SLAM, swarms), and expose custom user-interface over web/mobile.

While it may not look very polished yet, all the back-end features have been integrated and thoroughly tested. We are adding several other interesting features to FlytConsole, and are looking for more contributors to help us in this effort, esp. with UI/UX refinement. If you would like to contribute, do let us know! We will be happy to share the development plan.

FlytConsole is a sub-project of FlytOS project. The initial release is available for download (as part of FlytOS) at: http://flytbase.com/flytos/ ;

More sample applications (onboard and web/mobile) built for FlytOS are available here: https://github.com/flytbase/flytsamples

Documentation for FlytConsole is available here: http://docs.flytbase.com/docs/FlytPOD/GettingStarted/About_FlytConsole.html

Read more…
3D Robotics

ParaZero announces safety parachute for Solo

From the ParaZero press release:

TEL AVIV, Israel – March, 2016 – ParaZero, a startup that has developed a safety solution for all aerial systems such as UAVs and drones, publicly unveiled its technology today as governments around the world are increasingly focusing on regulating and ensuring the safety of the emerging commercial and private drone sector.

As companies such as Amazon and Google look to commercialize the use of drones for multiple purposes, and private consumers and hobbyists are enjoying more affordable drone models, the safety of both people and property has become a huge concern. Legislative bodies and civil aviation authorities around the world are currently debating the proper way to regulate this exponentially growing market, while simultaneously demanding increased safety features.

In this climate, there is a clear need to ensure that the increasing numbers of drones filling the skies don’t pose a danger to the people or property on the ground. ParaZero has developed its SafeAir system, that includes an automatic parachute recovery system for drones that will not only protect and prevent injury of people and assets on the ground, but will also allow drone operators to protect their investment in expensive drone hardware.

“It’s clear that drones are set to play a major role in our future, whether they are used as aerial cameras, rapid delivery systems, or for private enjoyment. In light of this, ensuring that these devices are operated safely and protecting individuals and property on the ground is paramount,” said Eden Attias, CEO of ParaZero. “Our system provides a reliable solution for the industry, just like an airbag, that acts automatically, whether there is a critical malfunction or a loss of power. Most importantly, our system works rapidly and at very low altitudes ensuring maximum effectiveness.”

The ParaZero’s SafeAir recovery system includes a patented pyrotechnic parachute launcher, independent triggering, as well as other safety solutions for payload protection. Altogether, these solutions provide multiple advantages over competing systems. These include:

  • Extremely Low Effective Altitude – ParaZero is using a customised pyrotechnic device that actively deploys the parachute to its full formation, in a fraction of a second. This technology protects aerial systems of all shapes and sizes, including all UAV, UAS, and drone platforms.
  • Automatic Triggering paired with Advanced Pyrotechnic Deployment – ParaZero leverages a highly reliable, complete stand-alone auto deployment system that does not rely on a drone’s systems and sensors. Thus, in case of a loss of power or control, breach flight envelope limits, penetration of GEO fencing, and other emergencies, the auto deployment system independently detects and automatically deploys the parachute.
  • Lightweight – ParaZero’s recovery systems are made from composite lightweight materials, making them the lightest systems available in the market.
  • Custom Design – Each system is custom made and embedded to fit the platform design, specs, and appearance of the aerial system. The safety solution can also be an independent add on, or dull integrated, according to the needs of the customers.

ParaZero has already partnered with leading manufacturers in the limited initial deployment of its system. Current users include Martin Jetpacks, DJI, as well as the Solo drone, produced by 3D Robotics. The company creates systems to meet the unique requirements of drone manufacturers, tailoring each system to the specific demands of each drone system.

Read more…

We are an Uruguayan company manufacturing drones for security and agro market. As 99% of problems are human error, we decided to fly our drones without human action ! The objective is quite simple : Help use of drones offering the simplest way to fly it.

Thank to DroneCode (and a lot of work...), we have designed a black box with 2 buttons : 1 to arm, 1 to fly mission. We put 1 more for Land if something goes wrong. LEDs help the user to decide to start the mission.

Usually a mission is :

  • take-off at 10 meters
  • wait for 10 seconds to be sure of GPS fix good quality (if not, Land button pressed) 
  • waypoints
  • last waypoint above landing point with 5 s delay
  • landing

Version 2 will be with 3G connection to send us logs after each flight. We will be able to monitor each flight and decide if the machine need maintenance.

Read more…
3D Robotics

Become a DIY Drones moderator!

3689684338?profile=original

One of the great things about this community is that it's very active but still keeps high standards of civility and a good signal-to-noise ratio. This doesn't happen by accident, but is rather due to a great cast of moderators who approve new members (keeping spammers out) and review all posts on the front page to ensure that they're high quality. 

You can be one of them!  All of the moderators are volunteers, and we all share the load the work, fitting in a few minutes when we can. With moderators around the world, that means pretty much 24/7 coverage, which is just what a global community needs. 

If you'd like to join our ranks of moderators, please PM me, comment below, or apply to join the Moderators Group. 

Guidelines and what the moderator job entails are below

These are the basic instructions for moderators:

Most of what you'll be doing is approving (or not) blog posts and otherwise keeping things running smoothly.

With blog posts, the key things to check before approving are:

  1. Does the post start with an image/video or at least have one very close to the top?
  2. Are videos embedded? (Not a link to a video elsewhere)
  3. Is the post informative, rather than asking a question or a request for help? (Those should be sent to the discussion forum).

Feel free to make modest edits (such as moving a photo to the top, or turning a video link into an embed) yourself. If the post should be in the discussion forum instead, paste the text into a Friend request to the author explaining that and delete the post. (Using a Friend request will hopefully take some of the sting out of having to reject their post ;-) )

When Moderating Comments:

Deletion is really the course of last resort, and tends to cause more trouble than it solves. Instead, we follow this escalation process: 

  • 1st course of action in case of TOS abuse: Gentle note in the comments asking people to play nice
  • 2nd: Edit the comment to remove offending piece and add: "[Moderator: Text edited to comply with site TOS]". It's nice to PM the member with an explanation, warning
  • 3rd: Lock comments. Also PM member with explanation/warning
  • 4th (only in cases of gross abuse): Delete comment. PM member
  • 5th (very rare, and only after multiple warnings): Ban member

Our Culture and Values:

Mark Harrison, one of our star moderators, articulated our culture and policies best with this post, which I'll just quote verbatim:

Here's my general feeling about a lot of things on this site; in fact, it's pretty much my general philosophy for large parts of my life:

        "It's more important to enable good things than prevent bad things"

For diydrones, this generally means:

--Be generous in accepting blog posts. We're not at a point where there are more submissions than can be confortably digested in a day. Likewise, the term "drone" is evolving at such a fast rate it's hard to pin down exactly what it means for everyone. So, I'm happy to lump in quadcopters, FPV, gimbals, RC, artistic aerial videos, electronics, radios... all kinds of stuff that meets my nebulous criterion of "generally interesting to the diy drone community."

Now of course it can be protested, "what if we're flooded by dozens or hundreds of posts on marginally related topic X?" And my response would be, "let's wait until that happens; we'll have tons more context and it will be easier to make a specific decision then than make some globally encompassing set of rules now. We may all even be a little bit smarter and a little bit wiser!"

-- Be generous in approving users. Lots of people aren't comfortable with revealing too much information about themselves, or may not have a particularly cogent reason for joining a site. I'm somewhat of an exception to this case... "Are you asking what I'm interested in? Let's talk about me, it's one of the most interesting topics we can discuss, don't you agree?" But for a lot of people, they may interested in the topic, but not interested in telling you why.

-- Feel free to make mistakes, and be nice when other people are making mistakes. Sometimes the most interesting things happen when things go awry. For better or worse, sometimes the most education things as well!

I think this is pretty much in agreement with how the site has been run historically. It's a site for amateurs, by amateurs (keeping in mind the defintion of "amateur"... from the French "lover of"), and as such has had a pretty wide-ranging scope of what's acceptable. That's served the site well, enabling it to be as relevant (or even more!) in 2013 as it was when it was founded.

Of course there are big exceptions to this "don't sweat the bad stuff" philosophy -- brain surgery, rocket launches, and skydiving come to mind -- but I think it's a useful guideline for a site such as ours.

 

More instructions:

Guidelines

When is a blog not a blog?

Read more…