The current code would set the vehicle to guided,
then arm, and if fixed wing, then switch to auto.
This small time it remained in guided, until QGC
received feedback of vehicle armed and changed to
auto, was enough to cause dangerous situations,
because when arming in guided mode, if the
vehicle is a tilt rotor vtol, it would arm the
rotors in forward flight position.
This commit changes the behaviour of start mission,
so if it is an Ardupilot fixed wing or VTOL it will
set auto mode, and then arm, which is the intended
way of dealing with this in Ardupilot
All I do here is ask qmake for the architecture and use it to download
the correct *.deb package. The rest of the changes is simply indentation.
I do not have an aarch64 linux so testing against Android NDK.
clang is slightly more picky with the unused 'this' captured by the
Airmap/services/*.cpp files
This adds regular expression support to the parameter search function. I
added the isValid condition to prevent the contains function to spam the
log with messages about invalid regular expressions.
User requested this feature here:
https://github.com/mavlink/qgroundcontrol/issues/10383
This passes the styleData.textColor property from the TableView to the
Text items used to populate the rows to ensure the proper color of the
text to match the alternating background colors of each row.
This fixes not being able to read the text on macOS where half of the
rows were black text on almost black background.
Fixes: #10449
- Allows operator to close/open the gripper using a button assigned
- Rename Gripper Grab/Release into Close/Open for clarity
- Add comments regarding Gripper functionality
Expose MAV_CMD_DO_GRIPPER Mission item to Mission planning GUI and
update the name shown to the user
This is used for the Package Delivery feature of PX4
Comm Links UI was not updating the enabled property of the Disconnect button after
being successfully disconnected, this is due to shared_ptr being automatically cleaned
up and no signal back to the UI on the change of the link state. Addition of signal
emission from qml disconnect method is a bandaid that works.
Without the patch the FTPManager is stuck when an EOF NAK is
received out of sequence in a burst transmission, e.g.
when the previous data packet is lost. With the EOF the
server will stop further transmissions but the client is
not waiting on anything.
Now the burst is restarted at the last received offset.
Closes: #10418
Ardupilot supports parameter download via a parameter file with
reduced size. This parameterfile is generated on the fly in
the vehicle with a size that dependes on block size of the ftp
transfer. I added the file to the MocklinkFTP. The file is the
original binary file from Arduplane 4.2 SITL simulation.
APM vehicles support a binary parameter download
via ftp which is much faster than the conventional
parameter download. This patch adds support for
downloading and parsing the parameterfile. The
parameters are injected in the factsystem. If the
ftp download does not work, the conventional
parameter download is used as fallback.
In the majority of failures the ftp manager only stops with
"Download failed". I added more detailed results available from
the transfer, e.g. "File not found".
The APM Vehicle responds with a fixed and wrong filesize in
the MAVFTP read request response. The reason is a dynamic
file creation on the vehicle. I add an option to ignore
the filesize indicated by the vehicle for a successfull transfer.
Ramon suggested to enable the ftp parameterdownload only
for APM vehicles. The ftp download only requests parameters
for component MAV_COMP_ID_AUTOPILOT1 for APM vehicles.
Ardupilot does not support the MAVLINK_MSG_ID_PROTOCOL_VERSION.
When this is attempted QGC assumes that Ardupilot does not support
the geofence and rally download. So this is skipped to make fence
and rally download work.
In #9440 the video streaming failed for some cameras and the
bunny example RTSP streaming movie. This worked in 4.0.6 and it
did not work anymore in 4.1.0. The same unstable behaviour is
observed in #10396.
The gstreamer rtsp source will
switch to tcp when no data is received via udp after 5 seconds.
The default timeout for the gstreamer video receiver is 2 seconds
resulting in a permanent teardown and restart until
eventually some data is received. As far as I understood the code
4.0.6 did not have a timeout which is in 4.1.0. I change the
timeout for RTSP to 8 seconds and leave it at 2 seconds for the
other streams. With 8 seconds timeout I can receive the bunny
example without problems.
Closes: #9440
PX4BuildBot
davidsastresas
Willian Galvani
Tim Nelson
Patrick José Pereira
Remek Zajac
Zdanek
olliw42
Don Gagne
DESKTOP-TG61LAS\Olli
Philipp Borgers
David Lechner
Bill Geyer
ThePeach-kr
Bill Geyer
Oleg Ziakun
Claudio Micheli
Friedrich Beckmann
Jacob Dahl
alexklimaj
WTPENGUIN
Beat Küng
Mathieu Mirmont