APM Planner 2.0.13 released (was 2.0.12/11 released)

NOTE: Parameter settings was also broken. Next release we will also have 'beta' releases so we can avoid these simple mistakes getting into stable releases, and if you are so inclined, can help us test before release.

2.0.13 improves connectivity with bluetooth devices as well. :-) Thx for all the reports so far on these issues. You can always try the daily builds if you like to experiment see http://firmware.diydrones.com/Tools/APMPlanner/daily/

NOTE: auto tlogging was broken, so we have pushed a minor update to fix the issue. There are some other small changes as well, see the release notes for more info

Happy Independence Day for those in the US.

A new release of APM Planner 2.0.13 is available.

In this release we have

Upload to Droneshare
- You can now upload logs to Droneshare from the Graph View.
Support for APM Mission Planning commands
- All APM specific commands are supported. (excludes ROI, but you can add with Mission Other command)
Mission Elevation Display.
- You can now see the elevation profile and compare against the terrain based on the Google map data
Rework of serial port handling.
- New improvements in stability of serial port handling including bluetooth support.
Update improvements
Mission Editing performance issues (deleting 119 waypoints down from 10mins to 17secs)
Graph View now show mode changes with text for bin/tlog/log file formats.
Support for Ubuntu 14.04LTS (Trusty Tahir) builds (coming Monday, see preview here (It's identical except the version reports as 2.0.10) (Trusty Tahir builds are now ready see here)

and many many more fixes... download here http://ardupilot.com/downloads/?category=35

Enjoy

The AP2 Team

PS: Users will be notified automatically if you have installed a previous build of AP2.

Michael,

Thanks for your reply.

Ive managed to sort both PCs out.

After reinstalling 2.0.12 (still didn't work) and updating to 2.0.13 (still didn't work) I renamed com10 to com10a, ( as you had suggested to someone else), then it recognised com10 again and worked. Don't ask me what went wrong in the first place???, but its working at the moment.

My other PC was running windows8, so Bl@%%y Microsoft in there wisdom blocked the drivers as they wernt signed (I believe).They don't give you an option to install if you trust them.

I followed instructions on rebooting pc in XXXX mode and disabling signed drivers. It worked but now my pc is probably more vulnerable to attack than if Microsoft gave the option of accepting unsigned drivers without permanently changing your pc settings.

Next stage is learning the software and setting up the Quad.

Thanks Jason

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

Join diydrones

Comments

Developer

Bill Bonney October 6, 2014 at 12:13pm

@Itay Guy: First I would suggest posting here on ardupilot.com/forum

The QML folder is copied as part of the build of AP2, though which platform are you using. For windows you will need to install the touch.exe command for this work.

see https://github.com/diydrones/apm_planner/blob/master/README.md for instructions

Joystick support in AP2 uses a different mechanism that is supported in APM code. Hence it was commented out.
Itay Guy October 6, 2014 at 3:53am

Hi , two questions

1. how to copy the qml folder to the debug folder.

2. is there support for joystick ? I can see it in the MainWIndow.ui , but it seems to be disabled.

thanks

Itay
Developer

Bill Bonney July 31, 2014 at 1:13pm

Hi jason, if you can be more specific about the issues you are having, we can hopefully add some fixes. There's a newer version at http://firmware.diydrones.com/Tools/APMPlanner/daily/

With the next release we will also support beta upates, not just daily. So hopefully we can meet your requests sooner
Jason July 31, 2014 at 2:35am

Where is the 'write // save' button on APM 2.0.13

I couldn't change the settings.

I thought APM 2.0 was to replace Mission Planner.

Ive uninstalled APM2.0.13 and installed Mission Planner.

Cheers
Michael Carpenter July 16, 2014 at 7:10am

Glad you got it working! A bug is what went wrong :) One that has been located and squashed.

The driver signing issue is an issue, which will be solved soon since we should be able to use the same signed drivers that MissionPlanner uses.
Jason July 16, 2014 at 2:31am

Michael,

Thanks for your reply.

Ive managed to sort both PCs out.

After reinstalling 2.0.12 (still didn't work) and updating to 2.0.13 (still didn't work) I renamed com10 to com10a, ( as you had suggested to someone else), then it recognised com10 again and worked. Don't ask me what went wrong in the first place???, but its working at the moment.

My other PC was running windows8, so Bl@%%y Microsoft in there wisdom blocked the drivers as they wernt signed (I believe).They don't give you an option to install if you trust them.

I followed instructions on rebooting pc in XXXX mode and disabling signed drivers. It worked but now my pc is probably more vulnerable to attack than if Microsoft gave the option of accepting unsigned drivers without permanently changing your pc settings.

Next stage is learning the software and setting up the Quad.

Thanks Jason
Stephen Gloor July 15, 2014 at 10:18pm

It did not work on that version either. I am running it in a VM - all the networking is OK and I can see the linux PC from the server that is running the SITL and the ports are correct.
Aaron Curtis July 15, 2014 at 8:49pm

FYI I have 2.0.13 running on 14.04 as well and am running SITL with no trouble. Can you get SITL to work with 2.0.12?
Stephen Gloor July 15, 2014 at 8:46pm

I have installed it on Ubuntu 14.04. I cannot connect it to a UDP stream from SITL on port 14553. I have created a new connection and it says connected however it is not working.

I know the SITL output is working as I can connect on a PC running MP that is also being sent UDP packets.
Michael Carpenter July 15, 2014 at 6:26am

Alright, thanks! Fairly sure I know what's causing it, and I'll be sure it's fixed in the next daily build.

of 7

This reply was deleted.