The DroidPlanner team, led by Arthur Benemann, is pleased to announce the next version of its Android-based UI. DroidPlanner 2.0 offers a completely redesigned interface for controlling 3DR multirotors over Mavlink. The UI/UX has been rethought with an emphasis on simplified workflows, glanceable information, and reliability for the most common user actions.
DroidPlanner 2.0 centers around two screens: Telemetry and Planning. The telemetry screen allows users to quickly assess the state of the aircraft and perform quick actions, like loiter and land. The planning screen allows users to create missions on the fly, as well as edit them easily in the field. Other features, particularly those different from the original DroidPlanner, are listed below. The DroidPlanner 2.0 UI was specifically targeted at multirotors, but full plane support and all the features of the original DroidPlanner are coming soon!
Features:
- Completely redesigned graphical user interface
- Specifically designed for 3DR multirotors and Iris
- New telemetry screen showing quick glanceable info: HUD, battery, RSSI, distance
- Easy to use Home, Land, and Loiter buttons
- New guided mode with changeable altitude
- Quick mode switching
- New planning screen for quick mission generation
- Easy and powerful mission editing tools
- Basic radio TX setup
- Preflight checklist
Coming soon:
- Survey tools in the mission planning screen
- FollowMe 2.0 with advanced control options
- New flight tuning screens
- Improved radio configuration
The app is still in a beta release, bugs can be reported on Github.
For additional support check out the DroidPlanner forum.
If you like the app consider making a donation to support the development.
Comments
the links are working now? thanks.....
dennis
@Dennis Okeefe: Make sure you join the G+ community first: https://plus.google.com/u/0/communities/109498440846585781402
I just checked and all links are valid.
the links don't work?
dennis
For otheres browsing by older stuff ultrojo question was anwsered in the forum: http://ardupilot.com/forum/viewforum.php?f=15
@yudi irawan: That's a know problem, but thanks for reporting.
The issue is that the more advanced waypoint types aren't implemented, and don't get sent to the copter. When arming DP request's your copter it's mission, and that's what you are seeing.
That's why we call this a beta :) It'll be fixed in a new release.
When I arming my quad, the region of interest waypoint was disappear, and also the takeoff and land waypoint. Is it right way?
This is after arming
Wow Arthur, hasn't it come such a long way since me emailing you about USB compatibility hehe.
I am very happy to see that the blogs you and i made have turned this into the most popular choice, your work has paid off!
hi
sory if my question out of topic a bit.
after i changes parameters for minimosd extra, i cannot connection to droidplanner using may tab failed.
but if connect the radio telemtry via mission planner PC is ok.
anything wrong with minimosdextra setting conflict with droidplanner on my tab?
this setting i change according to minimosd extra.
SERIAL3_BAUD, 57 (telemetry output at 57600)
SR3_EXT_STAT, 2 ( 2hz for waypoints, GPS raw, fence data, current waypoint, etc)
SR3_EXTRA1, 5 ( 5hz for attitude and simulation state)
SR3_EXTRA2, 2 ( 2hz for VFR_Hud data )
SR3_EXTRA3, 3 ( 3hz for AHRS, Hardware Status, Wind )
SR3_POSITION, 2 ( 2hz for location data )
SR3_RAW_SENS, 2 ( 2hz for raw imu sensor data )
SR3_RC_CHAN, 5 ( 5hz for radio input or radio output data )
If you fly copter than you also need to set SR0 also:
SR0_EXT_STAT, 2
SR0_EXTRA1, 5
SR0_EXTRA2, 2
SR0_EXTRA3, 3
SR0_POSITION, 2
SR0_RAW_SENS, 2
SR0_RC_CHAN, 5
thanks
Thanks Arthur. I thought I had but apparently had not.
@Barrett Floyd: It's active, just make sure you join the Google+ beta community first.
-
5
-
6
-
7
-
8
-
9
of 11 Next