Now i have a time for this because my Quadrocopter, Camera mount and Plane waiting for stabilisation ;)
Now i have a time for this because my Quadrocopter, Camera mount and Plane waiting for stabilisation ;)
Hi,
This is my experimental quadrorotor. In this flight I'm trying the stable mode with the accelerometer.
ARM 7 32bit LPC2103 a 60Mhz ( Coridium ARMmite PRO )
ITG-3200 Triple-Axis Digital-Output Gyro, 16bit, digitally-programmable low-pass filter
BMA180 Triple Axis Accelerometer, 14Bit, Programmable integrated digital filters
ESC: PWM at 495Hz
R/C RECEIVER: PPM composite signal, 8 Channel
Greetings, Danilo
Autonomous Helicopter from M W on Vimeo.
Introduction
Open Source Hardware (OSHW) is a term for tangible artifacts -- machines, devices, or other physical things -- whose design has been released to the public in such a way that anyone can make, modify,
distribute, and use those things. This definition is intended to help
provide guidelines for the development and evaluation of licenses for
Open Source Hardware.
It is important to note that hardware is different from software in that physical resources must always be committed for the creation of physical goods. Accordingly, persons or companies producing items
("products") under an OSHW license have an obligation not to imply that
such products are manufactured, sold, warrantied, or otherwise
sanctioned by the original designer and also not to make use of any
trademarks owned by the original designer.
The distribution terms of Open Source Hardware must comply with the following criteria:
1. Documentation
The hardware must be released with documentation including design files, and must allow modification and distribution of the design files. Where documentation is not furnished with the physical product,
there must be a well-publicized means of obtaining this documentation
for no more than a reasonable reproduction cost preferably, downloading
via the Internet without charge. The documentation must include design
files in the preferred form for which a hardware developer would modify
the design. Deliberately obfuscated design files are not allowed.
Intermediate forms analogous to compiled computer code -- such as
printer-ready copper artwork from a CAD program -- are not allowed as
substitutes.
2. Necessary Software
If the hardware requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the documentation requirement must also include at least one of the
following: The necessary software, released under an OSI-approved open
source license, or other sufficient documentation such that it could
reasonably be considered straightforward to write open source software
that allows the device to operate properly and fulfill its essential
functions.
3. Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original hardware. The license must allow for the manufacture, sale,
distribution, and use of products created from the design files or
derivatives of the design files.
4. Free redistribution
The license shall not restrict any party from selling or giving away the project documentation as a component of an aggregate distribution containing designs from several different sources. The
license shall not require a royalty or other fee for such sale. The
license shall not require any royalty or fee related to the sale of
derived works.
5. Attribution
The license may require derived works to provide attribution to the original designer when distributing design files, manufactured products, and/or derivatives thereof. The license may also require
derived works to carry a different name or version number from the
original design.
6. No Discrimination Against Persons or Groups
The license must not discriminate against any person or group of persons.
7. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used
in nuclear research.
8. Distribution of License
The rights attached to the hardware must apply to all to whom the product or documentation is redistributed without the need for execution of an additional license by those parties.
9. License Must Not Be Specific to a Product
The rights attached to the hardware must not depend on the hardware being part of a particular larger product. If the hardware is extracted from that product and used or distributed within the terms of
the hardware license, all parties to whom the hardware is redistributed
should have the same rights as those that are granted in conjunction
with the original distribution.
10. License Must Not Restrict Other Hardware or Software
The license must not place restrictions on other hardware or software that may be distributed or used with the licensed hardware. For example, the license must not insist that all other hardware sold at
the same time be open source, nor that only open source software be used
in conjunction with the hardware.
11. License Must Be Technology-Neutral
No provision of the license may be predicated on any individual technology or style of interface.
Afterword
The signatories of this Open Source Hardware definition recognize that the open source movement represents only one way of sharing information. We encourage and support all forms of openness and
collaboration, whether or not they fit this definition.
It was exciting for me to see Jasons Sim working in 3D, so I thought I would share a pic
>> With the minor modification shown below which adjusts the climbrates
// guess the climb rate
// --------------------
if(pitch_sensor >= 0){
climb_rate = (pitch_sensor * (CLIMBRATE_UP/100) * (long)dTnav) / 90000L;
}else{
climb_rate = (pitch_sensor * (CLIMBRATE_DOWN/100) * (long)dTnav) / 90000L;
}
current_loc.alt += climb_rate;
Heres a photo I took last week at the Waddington UAS symposium
Quite a difference, was that one the original plan????
Lots of announcements coming out in time for Farnborough.
We don't cover military UAVs here, but I'll make an exception on design grounds for this one. Just look at it!
From BoingBoing:
"British empire presents new kite to Lord Vader
Britain's Ministry of Defense announced this unmanned fighter jet today, the Tiranus. Named for the Celtic god of bad-assery, it looks markedly more sinister than America's one, itself revealed in May. There's something about that blue-gray hangar ... it reminds me of something.
Photo: Sienar Fleet Systems.
If you've been looking for a way to control your robotic project over a WiFi, then you might want to take a look at the Remote Control Over IP (RCOIP) project by Mike McCauley. He uses a lot of complicated words, but it's basically a communication protocol to do RC-style control over an Internet connection.
Of course, you can't connect directly to a traditional RC device using your laptop, so you will need to substitute your radio receiver for an Arduino with a WiFi shield, and put the RCKit library on it. For the controller end, you could use another Arduino or a computer. He's also got a (nonfree) iPhone control app, which allows you to control your creation using a simulated touchscreen RC controller.
There are probably a bunch of different protocols that people use for this, such as Open Sound Controller- do you have a favorite?"
Boeing on Monday unveiled a potential new eye in the sky, this one powered by hydrogen fuel.
The Phantom Eye, an unmanned aerial vehicle from the company's Phantom Works division, is expected to make its first flight early next year. Boeing is pitching the demonstrator UAV as a "first of its kind" aircraft that "could open up a whole new market in collecting data and communications."
A decade into the 21st century, surveillance drones are nothing new considering the now long-running successes of aircraft such as the Predator and the Global Hawk. What sets the Phantom Eye apart is the hydrogen propulsion system. Although hydrogen has been bandied about for some time as an alternative energy source, it has yet to progress much beyond the novelty stage.
http://news.cnet.com/8301-11386_3-20010294-76.html?tag=newsEditorsPicksArea.0
Tested the autolaunch function this weekend.
Launch altitude was set to 25 meters so it went almost instantly to WP1 after launch.
Next time I will try a higher launch altitude.
This was the last flight of the day the lipo was empty as can been seen at the end of the video the plane could not hold altitude.