PX4 BuildBot
9f8325e8e0
Update submodule mavlink to latest Wed Jan 15 00:39:11 UTC 2025
...
- mavlink in PX4/Firmware (fd5b52d4c53f35a520646a6c4ec75588f6b87e0f): https://github.com/mavlink/mavlink/commit/5e3a42b8f3f53038f2779f9f69bd64767b913bb8
- mavlink current upstream: https://github.com/mavlink/mavlink/commit/619947d8bc29e80eecff18b0f4fecc42d9e171dd
- Changes: https://github.com/mavlink/mavlink/compare/5e3a42b8f3f53038f2779f9f69bd64767b913bb8...619947d8bc29e80eecff18b0f4fecc42d9e171dd
619947d8 2024-12-19 Hamish Willee - common.xml - PING fix (#2197 )
2f44ceff 2024-12-18 Julian Oes - common: use camera ID for CAMERA_IMAGE_CAPTURED (#2196 )
2025-01-14 21:45:04 -05:00
Matthias Grob
61961350f9
mavlink_receiver: don't publish out of range joystick input
...
Note that the MAVLink definition explicitly writes
"A value of INT16_MAX indicates that this axis is invalid."
which before this change was happily executed.
2024-12-19 17:59:41 +01:00
Matthias Grob
6241db74db
mavlink: stream RAW_RPM message for ONBOAR_LOW_BANDWIDTH
2024-12-19 07:30:25 +01:00
Matthias Grob
c463cc42d0
RPM: clean up message
2024-12-19 07:30:25 +01:00
Stefano Colli
0561f6c9fc
GZ: add gimbal simulation ( #23382 )
2024-12-18 12:15:03 +01:00
Julian Oes
98fde4cbac
gimbal: correctly set gimbal_device_id
...
When we use a gimbal connected via "RC", so PWM via the Aux channels, we
need to set the gimbal_device_id to 1 as per the protocol.
This was missing for GIMBAL_DEVICE_ATTITUDE_STATUS, so I added that, and
fixed the name of that variable while at it.
2024-12-18 07:51:40 +01:00
Beat Küng
aca5a70964
standard_modes: add vehicle-type specific standard modes
...
See https://mavlink.io/en/messages/development.html#MAV_STANDARD_MODE .
The only standard mode that is not set is MAV_STANDARD_MODE_SAFE_RECOVERY,
as PX4 uses RTL for that (with configuration parameters).
2024-12-18 07:12:36 +01:00
PX4 BuildBot
a751e900f5
Update submodule mavlink to latest Sat Dec 14 00:39:04 UTC 2024
...
- mavlink in PX4/Firmware (661ae0c0e3ac493ceddd13120e8ccb5bac47d887): https://github.com/mavlink/mavlink/commit/0e420102dbdd7e9f59617dd00c05a2470f22eef2
- mavlink current upstream: https://github.com/mavlink/mavlink/commit/5e3a42b8f3f53038f2779f9f69bd64767b913bb8
- Changes: https://github.com/mavlink/mavlink/compare/0e420102dbdd7e9f59617dd00c05a2470f22eef2...5e3a42b8f3f53038f2779f9f69bd64767b913bb8
5e3a42b8 2024-12-12 Hamish Willee - development: Remove parameter transaction proposal (#2169 )
25f4e9f0 2024-12-11 Hamish Willee - STANDARD_MODE_SAFE_RECOVERY + RTL merge (#2191 )
d5a8cb43 2024-12-11 Hamish Willee - Docs generate fix (#2194 )
35f70c4a 2024-12-05 Hamish Willee - Create index.md, dialects.md and make notes/warning work with vitepress (#2193 )
57c02856 2024-12-05 Hamish Willee - CAMERA_THERMAL_RANGE - no longer WIP (#2189 )
1ee2ebe1 2024-12-04 Hamish Willee - fetch_dialect_ardupilotmega.yml: Not fail if nothing to commit (#2181 )
1aa8c2d0 2024-12-04 Hamish Willee - ardupilotmega - remove_mav_cmd_external_estimate (#2187 )
49fa509a 2024-11-30 github-actions[bot] - ardupilotmega dialects from ArduPilot/mavlink: Fri Nov 29 23:49:36 UTC 2024 (#2185 )
75ebfc8f 2024-11-30 Hamish Willee - Update fetch_dialect_ardupilotmega.yml - fix copy error (#2184 )
8e97709d 2024-11-30 Hamish Willee - fetch_dialect_ardupilotmega.yml - add loweheiser (#2183 )
82b81aa8 2024-11-27 github-actions[bot] - ardupilotmega.xml from ArduPilot/mavlink: Wed Nov 27 04:13:16 UTC 2024 (#2178 )
5c421a33 2024-11-27 Hamish Willee - Speed uncertainty units /s (#2180 )
33f8a327 2024-11-24 David Sastre - Some modifications to multi-GCS protocol (#2179 )
9938f940 2024-11-21 Hamish Willee - fetch_dialect_ardupilotmega - create (#2177 )
a55d0ec5 2024-11-21 Hamish Willee - MAV_CMD_GROUP_START and _GROUP_END delete wip (#2176 )
1cf3c721 2024-11-21 Hamish Willee - dev: move FUEL_STATUS to common (#2170 )
7ecb8e33 2024-11-21 Hamish Willee - WIFI_NETWORK_SECURITY - wip removal (#2164 )
2024-12-13 20:57:48 -05:00
PX4 BuildBot
2f8460da91
Update submodule mavlink to latest Wed Nov 20 13:16:31 UTC 2024
...
- mavlink in PX4/Firmware (7e594e898b2281e7d3f6ef4057f1add829643058): https://github.com/mavlink/mavlink/commit/e221d46d4631a5b6f1e91040cb1fe4b6fa91ea43
- mavlink current upstream: https://github.com/mavlink/mavlink/commit/0e420102dbdd7e9f59617dd00c05a2470f22eef2
- Changes: https://github.com/mavlink/mavlink/compare/e221d46d4631a5b6f1e91040cb1fe4b6fa91ea43...0e420102dbdd7e9f59617dd00c05a2470f22eef2
0e420102 2024-11-20 David Sastre - development.xml: change OPERATOR_CONTROL id to 32100: (#2174 )
01e0cc2f 2024-11-14 Hamish Willee - SMART_BATTERY_INFO - revert and renumber BATTERY_INFO (#2173 )
2024-11-20 22:33:21 -05:00
Matthias Grob
3f83a8fa7a
mavlink: remove reference to COLLISION message I had missed
...
Should have been part of
b5d18c6131
2024-11-20 13:02:59 -05:00
Matthias Grob
b5d18c6131
Remove unused collision_report message
2024-11-12 21:18:57 -05:00
PX4 BuildBot
84ba95b496
Update submodule mavlink to latest Wed Nov 13 00:39:41 UTC 2024
...
- mavlink in PX4/Firmware (a793ddeac49e4251b329fc35f6e066c8d1d9b8f8): https://github.com/mavlink/mavlink/commit/b4add5292992cc43bd471b431b425338787982be
- mavlink current upstream: https://github.com/mavlink/mavlink/commit/e221d46d4631a5b6f1e91040cb1fe4b6fa91ea43
- Changes: https://github.com/mavlink/mavlink/compare/b4add5292992cc43bd471b431b425338787982be...e221d46d4631a5b6f1e91040cb1fe4b6fa91ea43
e221d46d 2024-11-06 benjinne - add rc_type_crsf (#2162 )
6ac99ca4 2024-11-06 Hamish Willee - Remove the imported headers for everything except common.xml (#2166 )
5f7fe504 2024-11-06 David Sastre - development.xml: First prototype for multi-GCS operation. (#2158 )
2024-11-12 21:17:32 -05:00
Julian Oes
d8be547b06
mavlink: drop acks early that aren't for us
...
This fixes an issue where we dropped acks that we should have sent out
just because the queue was clogged with acks that have nothing to do
with us and just happen to be sent to us. We should just ignore them and
not publish them to uORB.
2024-11-07 17:10:05 +13:00
Julian Oes
25e071e21d
mavlink: no acks for commands that aren't for us
...
We should not send out acks for commands that are not targetted at us.
This can confuse other MAVLink components and MAVLink commands just
don't scale that way, and it unnecessarily fills up our ack queue.
This was likely introduced to debug when MAVLink components were
implemented incorrectly sending commands to a wrong target.
The most we should do in this case is to print/log an info.
2024-11-07 17:10:05 +13:00
Peter Lichard
79bb30ce3d
fix(ftp): List empty directory ( #23638 )
2024-11-05 00:23:28 -09:00
Michael Schaeuble
22950a94ec
Override vehicle attitude send to gimbals when HIL mode is enabled
...
The simulated attitude can disturb the gimbal estimator and lead to strange behavior of the gimbal. So, since the hardware is not moving in HIL/SIH, we fake a static attitude towards the gimbal.
2024-10-30 15:25:05 +13:00
Marco Hauswirth
0c451552c7
EKF2: add validity flags to global pos message ( #23787 )
...
Co-authored-by: Mathieu Bresciani <brescianimathieu@gmail.com >
2024-10-23 10:19:04 +02:00
Hamish Willee
b390d5876a
AUTOPILOT.capabilities includes gimbal manager protocol bit ( #23692 )
...
* AUTOPILOT.capabilities includes gimbal manager protocol bit
Sets MAV_PROTOCOL_CAPABILITY_COMPONENT_IMPLEMENTS_GIMBAL_MANAGER bit in AUTOPILOT.capabilities
* mavlink: update submodule
* mavlink: only set gimbal flag if gimbal param set
We should probably only set the flag if the gimbal manager is actually
set up using the MNT_MODE_IN parameter.
* mavlink: make param optional
If the gimbal module is not built in we don't have the MNT_MODE_IN
param, so we need to deal with that.
* gazebo-classic: update submodule
---------
Co-authored-by: Julian Oes <julian@oes.ch >
2024-10-17 08:41:38 +11:00
Julian Oes
01888a3085
mavlink: fix SET_MESSAGE_INTERVAL parsing ( #23796 )
...
This fixes the SITL tests that fail in CI because we catch NAN as non
zero after cast to int. To fix this I've added the check whether they
are finite at all.
The checks for param5 and param6 would be a bit trickier because they
can be int or float, so I have omitted them for now.
2024-10-11 09:03:22 +13:00
Hamish Willee
da8827883f
Use target camera in image capture start/stop messages ( #23115 )
...
* Use target camera in image capture start/stop messages
* Add support for MAV_CMD_SET_CAMERA_SOURCE
* Add target ID for NAV_CMD_SET_CAMERA_MODE
* Run make format
2024-10-09 21:10:08 +13:00
Hamish Willee
66b9e60a49
MAV_CMD_SET_MESSAGE_INTERVAL reject non-zero values for unused params ( #23643 )
...
* MAV_CMD_SET_MESSAGE_INTERVAL reject non-zero values for unused params
* Remove data rate
* Replace rounding with addition of 0.5/0.5f
2024-10-09 21:08:49 +13:00
Konrad
daf604b361
mavlink_mission: handle concurrent mission count messages
2024-10-08 15:34:51 +02:00
Konrad
7ec4c1419c
mavlink_mission: only accept a mission request list on an ongoing transfer, when it is the same partner
2024-10-08 15:34:51 +02:00
Konrad
b51ad07ed0
mavlink_mission: do not send the mission count if a new mission is detected since a receiver can now check this by changing mission ids in the MISSION_CURRENT stream
2024-10-08 15:34:51 +02:00
Konrad
1c62dda057
mavlink_mission: make sure send mission item error ack is send to the right sysid/compid
2024-10-08 15:34:51 +02:00
Konrad
b1d52e20c6
mavlink_mission: guard incoming misison item to be from the current transfer partner
2024-10-08 15:34:51 +02:00
DanielH
ee19691d95
fix mission sysid for mission_ack
2024-10-08 15:34:51 +02:00
Matthias Grob
fd04ece6d4
geo: remove dependency on drv_hrt time driver
2024-10-07 14:24:18 +02:00
BazookaJoe1900
4d83badba1
fix files tags on the header comments ( #23564 )
2024-09-19 09:25:18 +03:00
Julian Oes
8f6ce4edbf
mavlink/lib: move open_drone_id helpers to mavlink
...
I could not extract the open_drone_id helpers to a separate lib because
it would require the mavlink headers while the mavlink library would
also depend on it, so it ended up being a circular dependency.
Instead, I'm now just using the headers from within the mavlink module
as well as from the uavcan driver.
2024-09-02 16:20:10 +12:00
Julian Oes
cd63cfed3a
remoteid: implement System as sent from GCS
...
This will send the System message if it is already being sent by a ground
station. Otherwise, it will assemble the message itself using the
takeoff/home location.
2024-09-02 16:20:10 +12:00
Julian Oes
7d1d398984
remoteid: add SelfID message
2024-09-02 16:20:10 +12:00
Julian Oes
04ea4f9b3a
uavcan: add OpenDroneID ArmStatus, operator ID
...
In order to have operator ID be sent by QGC, we need to forward
ArmStatus from the remote ID module (here on DroneCAN) to MAVLink.
2024-09-02 16:20:10 +12:00
Julian Oes
87a63e75be
mavlink: extract OpenDroneID function to lib
...
This extracts the function mapping from MAV_TYPE to MAV_ODID_UA_TYPE to
the library, so that it can be re-used later by the remote ID
implementation over DroneCAN.
Signed-off-by: Julian Oes <julian@oes.ch >
2024-09-02 16:20:10 +12:00
Jukka Laitinen
f67eb6989d
mavlink: Fix ESC_STATUS sending for batches > 1
...
The indexing was wrong for esc_status sending for ESCs 4->
Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae >
2024-08-26 15:06:55 -04:00
Jaeyoung Lim
e008ca24f1
Remove euler angles from attitude setpoint ( #23482 )
...
* Remove euler angles from attitude setpoint message
* Remove usage of euler angles in attitude setpoint messages
This commit removes the usage of euler angles in the vehicle_attitude_setpoint messages
* Fix standard vtol
2024-08-12 16:42:51 +02:00
Matthias Grob
af06bee8d0
update mavlink & adapt to pymavlink generator reporting failures by default
2024-08-12 16:26:56 +02:00
Matthias Grob
64056fc7bb
SYS_STATUS: fill correct attitude, horizontal position flags
2024-08-09 18:22:09 +02:00
Matthias Grob
fdfe43471e
mavlink_receiver: limit access through instances with gimbal mode
...
This adds explicit handling for the few things we want to allow through a MAVLink instance dedicated to a gimbal/(camera) payload as per the MAVLink gimbal mode configuration.
2024-08-09 10:13:44 -04:00
Matthias Grob
6cf0bf5e19
Support MAVLink extension MANUAL_CONTROL.aux
...
Note that in uORB we don't currently know if the aux fields are
specifically valid or not so we can also not set the corresponding
bits in the field.
2024-08-09 10:49:38 +02:00
Jacob Dahl
086c044f47
mavlink: log handler rewrite for improved efficiency ( #23421 )
2024-08-07 11:26:12 -04:00
Matthias Grob
ba579245fb
battery_status: remove unused smart battery mode
2024-07-30 14:37:11 +02:00
David Sidrane
54b20f1ff3
mavlink:Use CONFIG_BOARD_ROOT_PATH instead of string constant
2024-07-24 11:39:44 -04:00
Matthias Grob
f2bca92221
Fix duplicate newlines at the end of files
2024-07-19 14:33:36 +02:00
Daniel Agar
ca9948a84d
msgs/EstimatorStatus.msg rename mag_test_ratio -> hdg_test_ratio
...
- this is used for more than just mag
2024-07-18 16:39:18 +02:00
PX4 BuildBot
9bbfc8715e
Update submodule mavlink to latest Mon Jul 15 12:39:00 UTC 2024
...
- mavlink in PX4/Firmware (abcf9ca6f0aadc91b203342db689f07630ec0e3a): https://github.com/mavlink/mavlink/commit/da3223ff9380bfe8e496fab8df2cbb06d5f8d5c3
- mavlink current upstream: https://github.com/mavlink/mavlink/commit/d65952bacc02c4a5a1ed8249be73e6a66fa800ab
- Changes: https://github.com/mavlink/mavlink/compare/da3223ff9380bfe8e496fab8df2cbb06d5f8d5c3...d65952bacc02c4a5a1ed8249be73e6a66fa800ab
d65952ba 2024-07-05 Peter Barker - common.xml: correct description of GLOBAL_POSIITON_INT.relative_alt frame (#2131 )
5fc2ff8e 2024-06-26 Hamish Willee - Add multiplier field to docs, if present (#2125 )
a13d2317 2024-06-26 Roman Bapst - Added MAV_CMD_EXTERNAL_WIND_ESTIMATE to development (#2122 )
d8af87fd 2024-06-19 jokalode - Update common.xml (#2116 )
2024-07-15 11:18:19 -04:00
Silvan Fuhrer
33701aa3d5
BatteryStatus: remove voltage_filtered_a
...
Signed-off-by: Silvan Fuhrer <silvan@auterion.com >
2024-07-03 16:41:49 +02:00
Silvan Fuhrer
c2ae6a7e24
BatteryStatus: remove current_filtered_a
...
Signed-off-by: Silvan Fuhrer <silvan@auterion.com >
2024-07-03 16:41:49 +02:00
zhangteng0526
e03e0261a1
Fix buffer overflow in mavlink_receive.cpp
2024-07-03 08:11:32 +02:00
Matthias Grob
8cc7c99b59
mavlink: report generator error ( #23313 )
...
Without this flag the command silently succeeds even though the logs contains
an error. It's much more developer friendly to fail early in case of an error.
The log path is then also shown in the console output.
2024-06-24 10:00:03 +02:00