APM Roadmap
Folks,
The Dev Team is working on the APM hardware and software roadmap. Here are some highlights:
As I've mentioned before, the hardware roadmap (next 12 months) is to move to a 32-bit architecture along with the rest of the Arduino project. This will probably involve a single-board version of APM with an integrated GPS module. Long-term, we aim to make APM smaller, cheaper and more reliable. We'll announce more specifics when we're closer to a design. But rest assured that the current boards will remain the core of the project for a year or more and there is a lot of power still untapped in them, so we will continue to focus development on them.
There are also a bunch of other new boards coming soon, including an OSD designed to work with APM and possibly an open-source alternative to the Xbee modules.
On the software side, the priorities are also ease of use and more features. We're redesigning the Mission Planner to be one-stop dashboard for all setup needs. We'll be adding more commands to MAVLink, so you can script more complex missions. Real-time waypoint assignment with a click ("go here now") is coming. Joystick control from the HK GCS (no RC required) is very close to release. And there will be a lot more high-level photo/video controls, so you can "fly the camera", letting the aircraft figure out what to do.
On the overall system architecture side, we're adding ROS compatibility, so you can do multi-UAV swarming. We'll be integrating the PhoneDrone board for Android, so you can use an Anrdoid phone for high-level mission AI, such as tracking and following an object. And the Android interface can also allow long-distance wireless communications, far beyond the range of RC or Xbee.
That's a quick overview. What do you think? What else would you like to see?
The Dev Team is working on the APM hardware and software roadmap. Here are some highlights:
As I've mentioned before, the hardware roadmap (next 12 months) is to move to a 32-bit architecture along with the rest of the Arduino project. This will probably involve a single-board version of APM with an integrated GPS module. Long-term, we aim to make APM smaller, cheaper and more reliable. We'll announce more specifics when we're closer to a design. But rest assured that the current boards will remain the core of the project for a year or more and there is a lot of power still untapped in them, so we will continue to focus development on them.
There are also a bunch of other new boards coming soon, including an OSD designed to work with APM and possibly an open-source alternative to the Xbee modules.
On the software side, the priorities are also ease of use and more features. We're redesigning the Mission Planner to be one-stop dashboard for all setup needs. We'll be adding more commands to MAVLink, so you can script more complex missions. Real-time waypoint assignment with a click ("go here now") is coming. Joystick control from the HK GCS (no RC required) is very close to release. And there will be a lot more high-level photo/video controls, so you can "fly the camera", letting the aircraft figure out what to do.
On the overall system architecture side, we're adding ROS compatibility, so you can do multi-UAV swarming. We'll be integrating the PhoneDrone board for Android, so you can use an Anrdoid phone for high-level mission AI, such as tracking and following an object. And the Android interface can also allow long-distance wireless communications, far beyond the range of RC or Xbee.
That's a quick overview. What do you think? What else would you like to see?
Replies to This Discussion
-
DeveloperPermalink Reply by Doug Weibel on -
I have checked out the relay issue and found that the relay commands are working fine in the APM firmware. APM Planner has the fields for the set_relay command mislabeled, and I expect this is what caused people problems. It is the first field that should be used to specify if you want the relay on or off. I have notified Mike O of the issue.
-
-
Permalink Reply by Paul Feely on -
On the hardware roadmap, any interest in smaller form factor? - the stacking 'Ruby' http://www.uthere.com/products/ruby/ruby_for_your_aircraft.html form factor looks great for a skinny fuselage - an Arduino Nano style-ly APM would be great in my Merlin
-
-
3D RoboticsPermalink Reply by Chris Anderson on -
Absolutely. Future hardware will be that small or smaller. Current APM is bigger because it's a development board and people want to get access to all the I/O pins (not possible with closed source boards like Ruby). But many multi-chip functions can now be done with single chips.
-
-
Permalink Reply by Gary Southard on -
I agree with your goal of moving to a 32 bit processor. If you want my vote
I would like to see it be an STM32 ARM Cortex M3. I think the Arduino mega
form factor is perfect if you make it compatible with the current shield board.
Add more sensors to the current board. I am about to order the autopilot
mega and would prefer that the IMU remains compatible with any processor
upgrades.
-
- ‹ Previous
- 1
- 2
- Next ›
Social Networking
Top Content
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.A list of all T3 contests is here.
Groups
-
ArduCopter User Group
1283 members
-
Moderators
24 members
-
ArduCopter (traditional …
180 members
-
Queensland
4 members
-
Turkish Ardu Group
5 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
