Shop our Airplanes Products Drone Products Sales
Thread Tools
Dec 03, 2016, 07:54 AM
Registered User
mpjf01's Avatar
I've been using it on a hex frame for 3 years with an original Revo. I bought a HK version recently and flashed that with it and it also flew OK. I didn't persist as I wanted to see if I could get Librepilot to run on that board, still haven't succeeded with GPS modes.
Sign up now
to remove ads between posts
Dec 03, 2016, 04:37 PM
Registered User
Do you know if in this version the autotune for PID is working?
Dec 05, 2016, 01:01 AM
Registered User
Quote:
Originally Posted by mpjf01
if I could get Librepilot to run on that board, still haven't succeeded with GPS modes.
Open/libre-Pilot software is died as I see. That code is a best sample of overkill-engineering that I ever seen. But their boards are really good and very cheap.
Dec 05, 2016, 01:02 AM
Registered User
Quote:
Originally Posted by anbello
in this version
What "this version" do you mean?
Dec 05, 2016, 03:24 AM
Registered User
Quote:
Originally Posted by night_ghost
What "this version" do you mean?
I mean the old version from scenkov linked in you first post.
Dec 05, 2016, 05:35 AM
Registered User
All code uploaded to Github

There is latest.zip in a root folder, it contains the latest binaries so anyone can test it.

That binaries are compiled to run on "bare metal" - without bootloader so should be flashed via ST-link or boot0 DFU, there are helper scripts in libraries/AP_HAL_REVOMINI/support
Dec 05, 2016, 05:39 AM
Registered User
Quote:
Originally Posted by anbello
I mean the old version from scenkov linked in you first post.
Unfortunately, this version is completely outdated and does not contain all the most "tasty" features introduced in 3.3 and particularly 3.4
Dec 05, 2016, 07:10 PM
Registered User
mpjf01's Avatar
Quote:
Originally Posted by night_ghost
All code uploaded to Github

There is latest.zip in a root folder, it contains the latest binaries so anyone can test it.

That binaries are compiled to run on "bare metal" - without bootloader so should be flashed via ST-link or boot0 DFU, there are helper scripts in libraries/AP_HAL_REVOMINI/support
I'd love to try it. Does "without bootloader" mean that it cannot be flashed in the normal way? If so I have no clue what to do.
Dec 05, 2016, 10:19 PM
Registered User
Quote:
Originally Posted by mpjf01
Does "without bootloader" mean that it cannot be flashed in the normal way?
What way is "normal"? Revolution board has built in SWD port so the simplest way to flash/debug is a st-link. Or set "Boot" jumper and connect to USB - board will boot up in DFU mode.
Dec 06, 2016, 12:29 AM
Registered User
mpjf01's Avatar
For me at least the "normal way" is to use the LibrePilot GCS and the USB port as described in the original instructions (it was Open Pilot then).
Dec 06, 2016, 01:26 AM
Registered User
Quote:
Originally Posted by mpjf01
For me at least the "normal way" is to use the LibrePilot GCS and the USB port as described in the original instructions (it was Open Pilot then).
There are situations with a range of devices in this hobby where the 'normal' bootloader doesn't work or needs to be bypassed. It is rarely a complicated procedure but sometimes requires specialised hardware. I've had to do it several times, often just to install a user friendly bootloader, but not with this FC. Even a Taranis can be forced into DFU mode to solve firmware problems.

Google gave several promising results for flashing this FC, using alternative methods. An example below:

https://librepilot.atlassian.net/wik...oard+using+DFU
Dec 06, 2016, 04:24 AM
Registered User
Quote:
Originally Posted by mpjf01
For me at least the "normal way" is to use the LibrePilot GCS and the USB port as described in the original instructions (it was Open Pilot then).
In this case we CHANGE firmware from one infrastructure to absolutely different one, so that neither Librepilot instruction nor Ardupilot instruction will not help us.

Why? Firmware should be placed to different address than OpenPilot bootloader can.

if ever this HAL will be accepted to the mainline then will be a way to flash bootloader via OpenPilot tool and then reflash the board by MP.

So the best way to find BOOT jumper and flash via DFU - this requires no additional hardware than USB cable.

PS. Jumper does not have to be soldered - enough to short it with thin wire and then connect the USB cable to USB Extension. It is more convenient than connect to the board, and you can invite an assistant
Dec 06, 2016, 07:39 AM
Registered User
For those using Linux, in this script from night_ghost the right parameters for dfu-util
https://github.com/night-ghost/ardup.../UPLOAD-DFU.sh
Dec 06, 2016, 10:58 PM
Registered User
for Windows users - just rename .sh to .bat

UPD. and correct path to binaries
Last edited by night_ghost; Dec 07, 2016 at 02:50 AM.
Dec 08, 2016, 05:03 AM
Registered User
I flashed the bin in latest.zip on my revomini with dfu-util all OK.

When I re-plug the USB I see this with dmesg:
Code:
[ 9241.731871] usb 9-2: new full-speed USB device number 40 using uhci_hcd
[ 9241.913933] usb 9-2: New USB device found, idVendor=26ac, idProduct=0011
[ 9241.913940] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9241.913944] usb 9-2: Product: 3DR Virtual COM
[ 9241.913948] usb 9-2: Manufacturer: RevoMini
[ 9241.913951] usb 9-2: SerialNumber: 00000000050C
[ 9241.916995] cdc_acm 9-2:1.0: ttyACM0: USB ACM device
But when I try to connect apmplanner2 on /dev/ttyACM0 I get no param and the following:
Code:
[20161208 11:00:22.137 DEBUG] - APMToolBar: CONNECT SELECTED
[20161208 11:00:22.137 DEBUG] - APMToolBar: connectMAV  QObject(0x0) with sLink 1
[20161208 11:00:22.138 DEBUG] - SerialConnection::connect()
[20161208 11:00:22.138 ERROR] - serial connection: error  0
[20161208 11:00:22.143 DEBUG] - APMToolBar setConnection: true
[20161208 11:00:22.143 DEBUG] - APM Tool BAR QML: connected
[20161208 11:00:22.145 DEBUG] - APMToolBar: updateLinkDisplay "ttyACM0" : "115200"  connected: true
[20161208 11:00:22.146 DEBUG] - APMToolBar: DISCONNECT unselected
[20161208 11:00:22.290 WARN ] - QObject::connect: No such signal SerialConnection::disconnected(QObject*)
[20161208 11:00:22.291 INFO ] - ArduPilotMegaMAV APM Connected
[20161208 11:00:22.292 DEBUG] - LinkManger::startLogging() "/home/andrea/apmplanner2/tlogs/quadcopter//2016-12-08 11-00-22.tlog"
[20161208 11:00:22.293 DEBUG] - Start MAVLink logging "/home/andrea/apmplanner2/tlogs/quadcopter//2016-12-08 11-00-22.tlog"
[20161208 11:00:22.378 DEBUG] - ATTEMPTING TO LOAD CSV
[20161208 11:00:22.378 DEBUG] - AUTOPILOT: "ARDUPILOTMEGA"
[20161208 11:00:22.378 DEBUG] - FILENAME:  "/usr/bin/ardupilotmega/parameter_tooltips/tooltips.txt"
[20161208 11:00:22.380 DEBUG] - src/uas/UAS.cc 2160 LOADING PARAM LIST
[20161208 11:00:22.396 DEBUG] - Loading widget: "PRIMARY_FLIGHT_DISPLAY_QML_DOCKWIDGET"
[20161208 11:00:22.396 DEBUG] - Loading widget: "UAS_INFO_INFOVIEW_DOCKWIDGET"
[20161208 11:00:22.396 DEBUG] - Loading widget: "UNMANNED_SYSTEM_CONTROL_DOCKWIDGET"
[20161208 11:00:22.409 DEBUG] - MODE: 0
[20161208 11:00:22.410 DEBUG] - "D|PREFLIGHT"
[20161208 11:00:22.410 DEBUG] - MODE: 80
[20161208 11:00:22.410 DEBUG] - "D|STABILIZED"
[20161208 11:00:22.410 DEBUG] - MODE: 64
[20161208 11:00:22.411 DEBUG] - "D|MANUAL"
[20161208 11:00:22.411 DEBUG] - MODE: 88
[20161208 11:00:22.411 DEBUG] - "D|VECTOR|STABILIZED"
[20161208 11:00:22.412 DEBUG] - MODE: 92
[20161208 11:00:22.412 DEBUG] - "D|AUTO|STABILIZED"
[20161208 11:00:22.412 DEBUG] - MODE: 66
[20161208 11:00:22.412 DEBUG] - "D|TEST"
[20161208 11:00:22.486 DEBUG] - addUAS "MAV 001"
[20161208 11:00:22.487 INFO ] - QGCMapTool::activeUASSet
[20161208 11:00:22.487 INFO ] - QGCMapTool::activeUASSet
[20161208 11:00:22.488 DEBUG] - AHC: uasConnected()
[20161208 11:00:22.489 DEBUG] - toggleButtonsShown true
[20161208 11:00:22.489 DEBUG] - Multirotor
[20161208 11:00:22.527 INFO ] - QGCMapTool::activeUASSet
[20161208 11:00:22.530 INFO ] - UASActionWidget::activeUASSet
[20161208 11:00:22.530 INFO ] - Arming State Changed:  DISARM
[20161208 11:00:22.531 INFO ] - updateWaypointList: 
[20161208 11:00:22.531 INFO ] - UASActionWidget: set for Copter
[20161208 11:00:22.544 DEBUG] - APMToolBar::ActiveUASSet  ArduPilotMegaMAV(0xa6552c8)
[20161208 11:00:22.545 DEBUG] - APMToolBar::ActiveUASSet  ArduPilotMegaMAV(0xa6552c8)
[20161208 11:00:22.545 DEBUG] - activeUASSet "MAV 001"
[20161208 11:00:22.545 DEBUG] - UPDATE WP LIST IN 2D MAP CALLED FOR UAS 1
[20161208 11:00:22.550 DEBUG] - HBD: Heartbeat started
[20161208 11:00:22.550 DEBUG] - UAS: new system_status 4
[20161208 11:00:22.550 DEBUG] - UAS: new base mode  81
[20161208 11:00:22.550 DEBUG] - MODE: 81
[20161208 11:00:22.550 DEBUG] - "D|STABILIZED"
[20161208 11:00:22.551 DEBUG] - UAS: new custom mode  0
[20161208 11:00:22.551 DEBUG] - APM: getCustomModeText()
[20161208 11:00:22.551 DEBUG] - plotTextArrow: 0  to  "MODE"
[20161208 11:00:22.551 DEBUG] - APMToolBar::mode: "Stabilize"
[20161208 11:00:22.552 DEBUG] - APM: getCustomModeText()
[20161208 11:00:22.552 DEBUG] - APM say: "Mode changed to Stabilize for system 1"
[20161208 11:00:22.552 INFO ] - "/home/andrea/apmplanner2/tmp_audio/mode_changed_to_stabilize_for_system_1.wav"  file exist, playing this file
[20161208 11:00:24.005 DEBUG] - HBD: Heartbeat stopped
[20161208 11:00:27.011 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:28.003 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:29.003 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:30.003 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:31.003 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:32.003 DEBUG] - QGCParamWidget: No parameters, re-requesting from MAV
[20161208 11:00:32.003 DEBUG] - src/uas/UAS.cc 2160 LOADING PARAM LIST
[20161208 11:00:32.004 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:33.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:33.003 INFO ] - "/home/andrea/apmplanner2/tmp_audio/link_lost_to_system_1.wav"  file exist, playing this file
[20161208 11:00:34.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:35.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:36.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:37.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:38.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:39.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:40.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:41.002 DEBUG] - ApmSoftwareConfig::populateTimerTick() - No Param names from param manager. Sleeping for one second...
[20161208 11:00:42.002 DEBUG] - QGCParamWidget: No parameters, re-requesting from MAV