Skip to content

mavproxy: allow 32 bit MAVLink system IDs - #1704

Open
tridge wants to merge 2 commits into
ArduPilot:masterfrom
tridge:pr-mavlink2.1
Open

mavproxy: allow 32 bit MAVLink system IDs#1704
tridge wants to merge 2 commits into
ArduPilot:masterfrom
tridge:pr-mavlink2.1

Conversation

@tridge

@tridge tridge commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Lift the source_system and target_system setting ranges for MAVLink2.1 32 bit system IDs. The wire handling comes from pymavlink; targets in the extended TARGETTED header are overlaid onto decoded messages by pymavlink so vehicle switching and forwarding work unchanged.

Requires ArduPilot/pymavlink#1229

tridge added 2 commits July 28, 2026 06:27
Lift the source_system and target_system setting ranges for MAVLink2.1
32 bit system IDs. The wire handling comes from pymavlink; targets in
the extended TARGETTED header are overlaid onto decoded messages by
pymavlink so vehicle switching and forwarding work unchanged.
the mission file has an 8 bit target_system field, so packing a target
over 255 raised struct.error and aborted the upload for waypoints,
fence and rally. The autopilot ignores that field when loading the
file, so write zero as we do for other raw payload structs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant