Blogs

Developer

Arducopter Beta update.

Posted by Jason Short on May 9, 2011 at 10:46am

3689405810?profile=original

Found some good bugs already. An issue with auto trimming being activated due to unusual Radio configurations fixed. Mavlink support is now up to par with APM. and A compass bug in the library squashed.

 

I revved the firmware's EERPOM fingerprint. You must redo the setup completely. (except ESC calibration.)

 

Thanks for the feedback!

Jason

E-mail me when people leave their comments –
Follow

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

Join diydrones

Comments

  • Developer
    Jason Short May 9, 2011 at 2:53pm
    Give us a moment to sort this Mavlink issue. We had trouble with users not getting XBEE access to Mavlink and the fix seems to have made it incompatible.
    Use the CLI, and follow the guidelines in the quick start section of the wiki.
  • Russell B. Sutton May 9, 2011 at 2:50pm
    Although I can only connect to the CLI I did notice that now when you " show "  settings the compass mag offset appears and it not  00.000,  00.0000,  00.0000. 
  • Vincent Mees May 9, 2011 at 2:14pm

    Uploaded the new code with mission planner.

    Uploads without problem.

    Setup goes smooth.

    But when checking sensors there is no connection.

    Then I switch to xbee and use 57600. Still no connection

     

    When I do the same procedure with arduino, a keep having the same problem.

     

    With the firts beta, everything worked with USB.

  • Taylor Cox May 9, 2011 at 2:13pm
    Yes, I have the same issue with mavlink not connecting....Something popped up and set something about testing the firewall...and I didn't save the command so I can't turn it back on...does anyone have the command for the command prompt that the missionplanner displayed??
  • Chris Starke May 9, 2011 at 1:45pm

    just uploaded the new code and now mavlink wont connect

  • Magellan May 9, 2011 at 1:17pm

    @Jason

    Way to roll out the fix to the problem I had just 20 hours ago.

    Someone mentioned putting a firmware version number in the Mission Planner upload dialog. That could be really useful as I can tell that your hard work is going to result in several revisions in the near future.

     

  • Developer
    Jason Short May 9, 2011 at 12:38pm

    The Mission planner auto generates the hex code from the SVN, so you should be good.

     

  • Taylor Cox May 9, 2011 at 12:30pm
    So we can load the code through the missionplanner and the code will contain the new fixes correct? Or should we be using arduino to upload the new code with the fixes?
  • Darren May 9, 2011 at 12:22pm
    is it ok to use APM planner firmware upload, will it update with your changes today?
  • Ritchie May 9, 2011 at 11:43am
    I think Jason should get a gold plated flyswatter gold plated for his efforts :)
This reply was deleted.