Discussions

Developer

2.0.54

Posted by Jason Short on November 29, 2011 at 10:51am

This version is bug fixes from 2.0.50-53 had some navigation bugs that manifested themselves in a bad way when flying in adverse condition. I would not recommend flying these in AP and I have deprecated the downloads on Wiki site.

 

If you downloaded 54 and it wouldn't fit on the 1280, I reposted it with some non-essential CLI test functions commented out. This is probably the last official release for the 1280. We just can't fit the code anymore. You will however be able to disable Logging and upload via Arduino to use 1280 boards with future releases.

 

As soon as Michael O. moves his Hex generator to the Stable branch, we can push out a hex. Thanks everyone for their patience!

Jason

 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • Developer
    Jason Short November 30, 2011 at 3:24pm

    I know this ride can be a little bumpy, but we're all in it together because it's so much fun. And we get to make things that are normally out of reach very accessible. In the end it's everyone's code and not someone else's.

    I like tinkering and spending my time on the code almost more than flying. That's the opposite for most folks, I understand. I also realize open source projects are not professionally run and some people don't like to see the sausage being made. That's why I think we need to keep a stable tag in the Mission planner and keep the bleeding edge stuff away from a $1000 hex a for example.

    Anyway, this is a community effort. If you would like to pitch in a help donate code, we can continue to improve and refine all aspects of the project from the sensors to the control laws to the high level features.

     

    Some key criteria I look at when adding code to the project:

    - ease of use

    - universality

    - style, readability, and copious code comments

    - Wiki documentation

    - test criteria

    - legacy issues/conflicts

     

    The best thing to do is to branch the main code, add in your ideas and test fly them, iterate the code. Then over-document them. 

     

    Areas for contribution include 

     

    Core Flight control - Stabilization and Acro modes.

    • Acro could really use some help by experience flyers. I simply don't fly acro mode.
    • I want to improve the reliability of Hexa and Octa's that loose a motor
    • Internal physics modeling of AC. We have a physics sim written in Python that could be the basics of a new control law. Someone could pick this up and create a self-tuning quad

     

    Advanced flight control

    • Altitude control - The new Baro sensor may be our savior. Physics Model would also help
    • Loiter algorithm - looking for experimentation and new ideas

     

    Auto-pilot

    • Things are turning out nicely here, documentation and usability and Mission planner integration are high on my list
    • Circle mode should be working, anyone try it?

     

    System 

    • Have you used and tested the ESC infield calibration? Love to hear feedback
    • In flight leveling - This hasn't had a serious look for months. Is it working well? Can it be improved? 

     

    If you have any interest in one of these areas or have another area to target for improvement (an not a new feature) please add it to this thread!

  • Gareth Rens November 30, 2011 at 1:21pm

    No no! Thank YOU! :))))))))))

This reply was deleted.

Activity