3D Robotics

APM 2.0 beta released!

3689393223?profile=originalI'm delighted to announce the release of the first public beta of ArduPilot Mega 2.0. This is a significant upgrade to APM 1.02, and now delivers on full 2-way in-air communications, including real-time mission planning and autopilot control.

 

[UPDATE:Arduino-free code uploading added to features]

 

New features/changes include:

  • --Full support for the MAVlink protocol, which is now APM's default communications method.
  • --Auto-detection of GPS modules. No more requirement to tell APM what GPS module you're using--it will figure it out and configure the module appropriately!
  • 3689393150?profile=original--2-way telemetry.  Dozens of commands can now be sent from the Ground Station to the UAV while it's in the air. (see example from HK GCS at right)
  • --2-way Mission Planning. You can script and change missions in real time while the UAV is flying!
  • --Supports APM boards with the ATMega2560 chip, which has twice as much memory as the current board. The DIY Drones store will begin selling these new boards when the final version of APM 2.0 is released.
  • --Mission Planner now uploads firmware and checks for new versions online. No need for Arduino (unless you want it)!
  • --Magnetometer fully supported.
  • --Current sensor fully supported
  • --Support for the latest HK Ground Control Station and QGroundControl ground stations.
  • --Mission Planning and configuration can now be done wirelessly. No need to use USB if you don't want to.
  • --No more fiddling with a configuration file in Arduino! The software comes ready to go, right out of the box
  • --New command-line tests allow you to check failsafe operation, Xbees, radio inputs and more.
  • --New versions of HK GCS and the Mission Planner operate in MAVLink mode, allowing for wireless operation and compatibility with other MAVLink devices, including those running the Robot Operating System (ROS)

---------------------------------------------------------------------------------------------

Huge props to the whole development team: Doug Weibel (project leader), Michael Smith, Jason Short, James Goppert, Michael Oborne (mission planner), Paul Mather (GCS), Lorenz Meier (MAVLink integration), Randy Mackay, Ryan Beall, Darren Corley, Joe Holdsworth, and countless others who have contributed with flight testing and bug catching!

 

Remember that this is an initial beta release, so there may be bugs and undocumented bits. After the beta-testing period (usually about six weeks) we'll release APM 2.0 final version, and retire APM 1.02.

 

Loading the code automatically:

 

Just download the Mission Planner and select "Upload Firmware" from the Tools section of the menu. Make sure APM is plugged into your USB port and you've selected the right port from the Mission Planner menu. Click on "Update Check" and the program will search online for the latest version of the code and load it to APM.

 

If you want to do a simulation with Xplane, follow the instructions below. That will soon be a firmware option with the Mission Planner, too.

 

Loading manually (Optional)

[UPDATE: Ignore this section if you don't want to fiddle with the code. Arduino is no longer required to load the code!]

 

Download the zip file, unzip it to your desktop. You will have two folders inside your APM 2.0 folder, as shown:

 

3689393014?profile=original

Make sure you're using the latest Arduino (0022). Set your Arduino Sketchbook location to the APM 2.0 folder, as shown below. You must exit Arduino and restart it for this to take effect. Within Arduino, open up the ArduPilotMega.pde file within the ArduPilotMega folder, and that will open all the other files. Before you compile, don't forget to select the right board (Arduino Mega 1280 or Arduino Mega 2560)

 

3689393238?profile=original3689393027?profile=original

(Note: in the final version of APM 2.0, you will not have to use the Arduino IDE at all: the Mission Planner will load the firmware for you and check for more recent versions. The Arduino IDE will just be available in case you want to modify or inspect the code. UPDATE: this is now live)

--------------------------------------

 

Additional instructions:

--If you're doing flight simulation with Xplane, instructions for doing it with APM 2.0 are here.

--Make sure you're using the latest Mission Planner and HK GCS. In the Mission Planner, make sure you select APM 2.x modes (MAVLink), shown at right.

 

Known issues:

1) Mission Planner won't write waypoints on Port 0 in HIL mode. Instead, write the waypoints via your Xbee (port 3); remember to change the Mission Planner baud rate to 57k when using the Xbee port.
2) Uploading mission commands is still not fully documented. We'll get to that this week
3) There may be some issues with datalogs not recording. We're looking into it.

4) The manual still describes the 1.02 software. We'll change that to 2.0 during the beta test period, so by the time we release the final of 2.0 the manual is fully updated.

5) This has been mostly tested with 900 Mhz Xbee modules and the XstreamBee adapter, which work great. However, there is an issue with the 2.4 Ghz Xbee modules, which have a slightly different hardware configuration that conflicts with that adapter when sending data upstream. A short term workaround is to solder a jumper from the adapter's CTS to V+ pin. The next version of these adapter boards will include a more graceful fix.

 

If you find any bugs, please file a report in the Issue Tracker. The dev team will not be responding to bug reports filed in blog comments

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • My concern was actually the microcontroller ATMEGA2560 alone, so that let us take my case, I already have two APM boards based on ATMEGA1280 and would certainly like to by two microcontrollers ATMEGA2560 so that I can replace in both the boards. 

  • 3D Robotics
    Rana, thanks for catching that listing error. I think that random price really means that they're actually not selling it yet. Once we offer APM2560 boards, they will be sold with the regular Arduino Mega 2560 bootloader (Optiboot)
  • Chris, I recently observed that "ArduPilot - Arduino Compatible UAV Controller w/ ATMega2560 "New Ge..." is there with a typo web mistake, showing price of $999,999.99, pl. get it corrected.

     

    In one of my recent comments on page #2 in this very blog, I put a query stating that "may existing users of APM order programmed ATMEGA2560 from DIYStore, so that they can replace of their own ?"

     

    So, it is possible for the existing users to get the ATMEGA2560 programmed with Arduino bootloader from DIY Store ?

     

     

     

  • Thank you everyone, I won't worry about it then. For the record, I am using a JR 12X with a 7 channel Spektrum AR7000 receiver.

    The "check before you fly" is a good reminder - applies to non autopilot flight also, just one more step to check the active modes in addition to the manual mode.

    Our field (www.wimac.ca) is closed right now (dirt road + melting snow + cars = mud), but the word is it might open on Sunday afternoon if for no other reason that it is supposed to be the first nice weekend day for the past month or so and the indoor flying just isn't the same. Hope to try it then.
  • Chris, you're right, we have to test everytime the plane on the ground before the takeoff. I do this always but this afternoon when I tested "stabilize" I was focused to check the movement of the surfaces and not on the direction... :-(
  • 3D Robotics
    Doug is the authority here; I didn't notice it in my testing but I've got so many planes with so many configurations that its hard to keep track. As always you should test the plane on the ground in auto mode before taking off. I often find I need to flip a DIP switch because of a config change. Taking off without such a ground test is a recipe for disaster, which is why we make such a big deal about it in the manual.
  • Doug, Andrew, today I had the same problem with my Futaba 10CH. I was at 30mt height, I switched to Auto and the plane (at full power) dived vertically! Wow... what a surprise! In a second I recovered it but there was a lot of adrenaline in the air :-). I reset the EEPROM and I compiled again the 2.0 code but the only way to solve the problem was to work on the dip switch...
  • Developer
    Actually Andrew it is expected for at least some radios.  I would have said all radios is Chris hadn't spoken up otherwise...  And it was intentional.   There was some code in 1.0X which was "backwards" from all the documentation.  That got corrected, and resulted in the switch positions changing.
  • I did a "reset"/"Y" then a radio setup (moving the sticks to the corners) after loading the code in both instances. The 2.0 code was loaded both via the Mission Planner and via the Arduino IDE by rebuilding the code from the zip file download with the same result. I will retry the 1.02 with an unmodified zip file download.
  • 3D Robotics
    Andrew: no, that is not expected. It doesn't do that with ours. Did you re-do the radio config when you upgraded? You should reset the EEPROM and re-configure everything.
This reply was deleted.