This update modifies the CMakeLists.txt files in both the AutoPilotPlugins directory and within the APM subdirectory, adding APMRemoteSupportComponent to the list of components included in the project's build. This change is necessary to ensure that the new APMremoteSupportComponent is compiled when the project is built.
This fixes a bug introduced in b62a533 which, when a joystick was disabled
and uncalibrated, caused unbounded recursive calls to Joystick::startPolling.
This fixes a number of issues with the way joysticks were handled
in a multi vehicle context. I reworked the way vehicle determine
to enable and capture the joystick input, as well as seperating
setJoystickEnable from saveJoystick to seperate runtime and saved
state.
The list of serial ports that ended up in the UI was from
QSerialPortInfo::availablePorts(), however the list available
to be used is a filtered list from QGCSerialPortInfo::availablePorts()
Changed so that the UI pulls the filtered list, and no ports present
which dont actually work.
QGCSerialPortInfo skips over serial ports which are not the first in any
composite device. However this is how some internal NMEA GPS's present.
So if the description contains 'NMEA', dont skip them.
This new host is different to the standard mavlink forwarding
one because it is meant to get disconnected when QGC closes
so the users don't leave by mistake the connection to the
support servers opened
This commit adds support for setting home clicking on map.
It is shown as another action in the submenu when we click
over the map with an active vehicle online.
As per mavlink specs, this command must use AMSL altitude,
so we need to first query terrain altitude, and when received
send the command.
Several checks have been implemented, and in case terrain
altitude is not shown at the selected location a popup will
appear indicating there are no terrain data for the specified location
There was a bug scaling rc rssi from rc_channels mavlink
message where it was scaled to 0-100 from 0-255, and this
was wrong because 255 is meant to be invalid, and AP uses
0-254 anyway. We must leave 255 as it is so the frontend
can understand if we don't have data.
Also, in RCRSSIIndicator, we don't show the indicator anymore
if data is not valid, there is no point
Beat Küng
Don Gagne
Don Gagne
PX4BuildBot
Jacob Dahl
Sergii Lisovenko
James Mare
Junwoo Hwang
davidsastresas
Matt Skelton