Developer

3689604406?profile=original

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.

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • That works! I just typed a V in the box and it showed COM15V in the planner. Then I clicked COM15 again, and Connect and that's all.

    Thank you Michael.

  • Alright so it's not properly detecting a single COM port. What happens if you type something in the com port box, then click the drop down and select COM15 again?

  • Thank you for your quick response!

    It does say: No Devices:3701784257?profile=original3701784203?profile=originalThe device manager shows no other COM port. Clicking gives:

    3701784157?profile=original

  • I assume that COM15 shows up in the upper right hand corner, and it doesn't say "No devices" ? Go into the connection by clicking on the com port or baud rate, and re-select the com port (or change it and select it again), if that fixes it then I'll file a bug report

  • I have the same problem using APM Planner 2.0.13. With MissionPlanner 1.3.7 all works well (COM15). The Devicemanager shows: Arduino Mega 2560 (COM15).

    Also the View Terminal button is not visible.

    Ardupilot 2.6

    Log:

    INFO 2014-07-15T13:50:06.687 QGCCore::initialize()
    INFO 2014-07-15T13:50:06.697 Current Build Info
    INFO 2014-07-15T13:50:06.697 Git Hash: 58f426825a3b8485c5dfe2959d0a68397805a983
    INFO 2014-07-15T13:50:06.697 Git Commit: 2.0.13
    INFO 2014-07-15T13:50:06.697 APPLICATION_NAME: "APM Planner"
    INFO 2014-07-15T13:50:06.697 APPLICATION_VERSION: "v2.0.13"
    INFO 2014-07-15T13:50:06.697 APP_PLATFORM: win
    INFO 2014-07-15T13:50:06.697 APP_TYPE: stable
    INFO 2014-07-15T13:50:06.767 Start Link Manager
    INFO 2014-07-15T13:50:06.767 "No Devices" 115200
    INFO 2014-07-15T13:50:06.787 UDP Created "UDP Link (port:14550)"
    INFO 2014-07-15T13:50:06.787 UDPLink::UDP connect
    INFO 2014-07-15T13:50:06.797 Start UAS Manager
    DEBUG 2014-07-15T13:50:06.807 Creating MainWindow
    INFO 2014-07-15T13:50:06.967 Creating SubMainWindow: SubMainWindow(0x668fb88)
    INFO 2014-07-15T13:50:06.967 setting objectName: "VIEW_MISSION"
    INFO 2014-07-15T13:50:07.007 Creating SubMainWindow: SubMainWindow(0x6759d18)
    INFO 2014-07-15T13:50:07.007 setting objectName: "VIEW_FLIGHT"
    INFO 2014-07-15T13:50:07.037 Creating SubMainWindow: SubMainWindow(0x679da88)
    INFO 2014-07-15T13:50:07.037 setting objectName: "VIEW_HARDWARE_CONFIG"
    DEBUG 2014-07-15T13:50:07.087 Requesting firmware: "stable" "apm"
    DEBUG 2014-07-15T13:50:08.167 "apm" Detected
    DEBUG 2014-07-15T13:50:08.297 fillPortsInfo
    INFO 2014-07-15T13:50:08.297 Inserting "COM15"
    INFO 2014-07-15T13:50:08.297 Changed Link to: "COM15"
    INFO 2014-07-15T13:50:09.017 Creating SubMainWindow: SubMainWindow(0x925f9a0)
    INFO 2014-07-15T13:50:09.017 setting objectName: "VIEW_SOFTWARE_CONFIG"
    DEBUG 2014-07-15T13:50:09.047 Disable Controls
    INFO 2014-07-15T13:50:09.497 Creating SubMainWindow: SubMainWindow(0x9738fd8)
    INFO 2014-07-15T13:50:09.497 setting objectName: "VIEW_ENGINEER"
    INFO 2014-07-15T13:50:09.537 Creating SubMainWindow: SubMainWindow(0x97cb988)
    INFO 2014-07-15T13:50:09.537 setting objectName: "VIEW_MAVLINK"
    INFO 2014-07-15T13:50:09.557 Creating SubMainWindow: SubMainWindow(0x97cf5e8)
    INFO 2014-07-15T13:50:09.557 setting objectName: "VIEW_SIMULATOR"
    INFO 2014-07-15T13:50:09.587 Creating SubMainWindow: SubMainWindow(0x97d0d08)
    INFO 2014-07-15T13:50:09.587 setting objectName: "VIEW_TERMINAL"
    DEBUG 2014-07-15T13:50:09.607 fillPortsInfo
    INFO 2014-07-15T13:50:09.607 Inserting "COM15"
    INFO 2014-07-15T13:50:09.607 Changed Link to: "COM15"
    DEBUG 2014-07-15T13:50:09.667 MODE: 0
    DEBUG 2014-07-15T13:50:09.667 "D|PREFLIGHT"
    DEBUG 2014-07-15T13:50:09.667 MODE: 80
    DEBUG 2014-07-15T13:50:09.667 "D|STABILIZED"
    DEBUG 2014-07-15T13:50:09.667 MODE: 64
    DEBUG 2014-07-15T13:50:09.667 "D|MANUAL"
    DEBUG 2014-07-15T13:50:09.667 MODE: 88
    DEBUG 2014-07-15T13:50:09.667 "D|VECTOR|STABILIZED"
    DEBUG 2014-07-15T13:50:09.667 MODE: 92
    DEBUG 2014-07-15T13:50:09.677 "D|AUTO|STABILIZED"
    DEBUG 2014-07-15T13:50:09.677 MODE: 66
    DEBUG 2014-07-15T13:50:09.677 "D|TEST"
    DEBUG 2014-07-15T13:50:09.817 QUrl( "file:///C:/Program Files (x86)/APMPlanner2/qml/PrimaryFlightDisplayQML.qml" )
    DEBUG 2014-07-15T13:50:09.887 QML Status: 1
    DEBUG 2014-07-15T13:50:09.897 QUrl( "file:///C:/Program Files (x86)/APMPlanner2/qml/PrimaryFlightDisplayQML.qml" )
    DEBUG 2014-07-15T13:50:09.947 QML Status: 1
    INFO 2014-07-15T13:50:09.957 UASActionsWidget creating UASActionsWidget(0x99d3658)
    DEBUG 2014-07-15T13:50:10.297 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:10.330 qmlBaseDir "C:/Program Files (x86)/APMPlanner2"
    DEBUG 2014-07-15T13:50:10.331 QUrl( "file:///C:/Program Files (x86)/APMPlanner2/qml/ApmToolBar.qml" )
    DEBUG 2014-07-15T13:50:10.371 QML Status: 1
    DEBUG 2014-07-15T13:50:10.372 APMToolBar: new Serial Link Created 1
    DEBUG 2014-07-15T13:50:10.373 APMToolBar setConnection: false
    DEBUG 2014-07-15T13:50:10.374 APMToolBar: updateLinkDisplay "No Devices" 115200 false
    DEBUG 2014-07-15T13:50:10.383 Loading widget: "PRIMARY_FLIGHT_DISPLAY_QML_DOCKWIDGET"
    DEBUG 2014-07-15T13:50:10.384 Loading widget: "UAS_INFO_INFOVIEW_DOCKWIDGET"
    DEBUG 2014-07-15T13:50:10.552 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.553 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.554 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.555 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.556 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.557 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.559 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.560 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:10.561 firmwareListFinished error: 0 "Unknown error"
    DEBUG 2014-07-15T13:50:15.466 "retrieve versionobject from server: http://firmware.diydrones.com/Tools/APMPlanner/apm_planner_version...."
    DEBUG 2014-07-15T13:50:15.701 Downloading: 2220 / 3074
    DEBUG 2014-07-15T13:50:15.703 Downloading: 3074 / 3074
    DEBUG 2014-07-15T13:50:15.705 AutoUpdateCheck::httpFinished()
    DEBUG 2014-07-15T13:50:15.709 Detected newVersion: ("2.0.13", "2.0.13", "") count: 2
    DEBUG 2014-07-15T13:50:15.711 Detected currentVersion: ("2.0.13", "2.0.13", "") count: 2
    DEBUG 2014-07-15T13:50:15.714 Verison Compare: " New Version 2.0.13 compared to Old Version 2.0.13"
    INFO 2014-07-15T13:50:15.716 no new update available
    DEBUG 2014-07-15T13:50:35.720 APMToolBar: showConnectionDialog for current serial link 1
    DEBUG 2014-07-15T13:50:36.725 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:37.739 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:38.753 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:39.766 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:40.781 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:41.795 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:42.810 SCW: Link is disconnected
    DEBUG 2014-07-15T13:50:43.801 QSerialPortPrivate::open() CreateFile: "\\.\No Devices"
    ERROR 2014-07-15T13:50:43.804 Error opening port "No such file or directory" trying again...
    DEBUG 2014-07-15T13:50:44.806 APMToolBar setConnection: false
    DEBUG 2014-07-15T13:50:44.809 APMToolBar: updateLinkDisplay "No Devices" 115200 false
    DEBUG 2014-07-15T13:50:44.811 QSerialPortPrivate::open() CreateFile: "\\.\No Devices"
    ERROR 2014-07-15T13:50:44.813 Error opening port "No such file or directory" trying again...
    DEBUG 2014-07-15T13:50:45.820 APMToolBar setConnection: false
    DEBUG 2014-07-15T13:50:45.823 APMToolBar: updateLinkDisplay "No Devices" 115200 false
    DEBUG 2014-07-15T13:50:45.825 QSerialPortPrivate::open() CreateFile: "\\.\No Devices"
    ERROR 2014-07-15T13:50:50.589 Error opening port "No such file or directory"
    DEBUG 2014-07-15T13:50:59.610 Delete Widget QRubberBand(0x4c54888, name = "qt_rubberband")
    DEBUG 2014-07-15T13:50:59.611 Delete Widget QMenuBar(0x6677be8, name = "menuBar")
    DEBUG 2014-07-15T13:50:59.612 Delete Widget QStackedWidget(0x6678c88)
    INFO 2014-07-15T13:50:59.614 Closing SubMainWindow: SubMainWindow(0x97d0d08, name = "VIEW_TERMINAL") "VIEW_TERMINAL"
    INFO 2014-07-15T13:50:59.619 Closing SubMainWindow: SubMainWindow(0x97cf5e8, name = "VIEW_SIMULATOR") "VIEW_SIMULATOR"
    INFO 2014-07-15T13:50:59.642 Closing SubMainWindow: SubMainWindow(0x97cb988, name = "VIEW_MAVLINK") "VIEW_MAVLINK"
    INFO 2014-07-15T13:50:59.645 Closing SubMainWindow: SubMainWindow(0x9738fd8, name = "VIEW_ENGINEER") "VIEW_ENGINEER"
    INFO 2014-07-15T13:50:59.648 Closing SubMainWindow: SubMainWindow(0x925f9a0, name = "VIEW_SOFTWARE_CONFIG") "VIEW_SOFTWARE_CONFIG"
    INFO 2014-07-15T13:50:59.671 Closing SubMainWindow: SubMainWindow(0x679da88, name = "VIEW_HARDWARE_CONFIG") "VIEW_HARDWARE_CONFIG"
    INFO 2014-07-15T13:50:59.707 Closing SubMainWindow: SubMainWindow(0x668fb88, name = "VIEW_MISSION") "VIEW_MISSION"
    INFO 2014-07-15T13:50:59.722 Closing SubMainWindow: SubMainWindow(0x6759d18, name = "VIEW_FLIGHT") "VIEW_FLIGHT"
    DEBUG 2014-07-15T13:50:59.748 Delete Widget QGCStatusBar(0x669c8f8, name = "QGC_STATUSBAR")
    DEBUG 2014-07-15T13:50:59.750 Delete DockWidget QDockWidget(0xa2b8190)
    DEBUG 2014-07-15T13:50:59.751 Destory APM Toolbar
    DEBUG 2014-07-15T13:50:59.760 save tlog dir to: "C:/Users/GW/apmplanner2/tlogs"
    INFO 2014-07-15T13:50:59.780 ~GAudioOutput()

  • Old versions can be found here: http://firmware.diydrones.com/Tools/APMPlanner/ That error means that the com port you are trying to connect to does not exist. When you go to the com port settings (by clicking on the port name or baud rate) the drop down box for the port name should automatically populate with available com port names. If you manually type in a name that does not exist, or attempt to connect without first selecting a com port it will likely be unable to connect.

    Can you post your logs please? They are located at c:\users\<username>\apmplanner2\log.txt

    AP2 installer should install the drivers automatically (As long as you have not un-checked them in the installer during the install process), but it may require you to unplug, and replug the device back in for it to be detected.

  • Gidday.

    I'm trying to set up a new Quad. All appears done but get an error saying [compass calibration not complete].

    This was with 2.0.12.

    Now after just updating to 2.0.13 I cannot even connect to the APM 2.6 board.

    it says

    Link Error

    Error opening port. no such file or directory.

    I've uninstalled and reinstalled APM2.0 Planner 2.0.13 a couple of times. I've dried to find 2.0.12 again on the net as It only happened after installing 2.0.13.

    Also my other PC also wont connect. It may be missing the drivers. I've tried downloading and updating the drivers MANY times, but it wont work.

    The first PC is windows 7. The other which has not worked at all is Winsdows 8

    Not having much luck with the software here.

    Any advice I can try.

    Cheers

  • Developer

    Ok, We fixed parameter changes and compass calibration (for one compass) works. builds available now

  • Thank you for the Trusty Tahr package!

  • Anyone having compass calibration issues?

This reply was deleted.