ArduPilot / ArduPilot/MissionPlanner

Extend HW ID page to cover new MAVn_DEVID parameters

Open
#3,761 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

ArduPilot flight code PR https://github.com/ArduPilot/ardupilot/pull/29762 adds new MAVn_DEVID parameters to allow users to more easily figure out which MAVn_xxx parameters controls which serial port. It would be nice if the "HW ID" page's DevType showed a human readable string for the new parameter.

Image

The mapping from DevID to DevType is in the new parameter's description (see Values) but here it is again in any case:

```
// @Values: 0:Unknown
// @Values: 6:USB0
// @Values: 14:SERIAL1
// @Values: 22:SERIAL2
// @Values: 30:SERIAL3
// @Values: 38:SERIAL4
// @Values: 46:SERIAL5
// @Values: 54:SERIAL6
// @Values: 62:SERIAL7
// @Values: 70:SERIAL8
// @Values: 78:SERIAL9
// @Values: 174:NET_P1
// @Values: 182:NET_P2
// @Values: 190:NET_P3
// @Values: 198:NET_P4
// @Values: 334:CAN_D1_UC_S1
// @Values: 414:CAN_D2_UC_S1
// @Values: 494:SCR_SDEV1
// @Values: 502:SCR_SDEV2
```

Here is the equivalent MAVProxy PR https://github.com/ArduPilot/MAVProxy/pull/1736

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Mission Planner "HW ID" page and the existing DevID-to-DevType mapping, then compare its handling with the values listed in the issue. Use the referenced MAVProxy PR as supporting context. Done means the new MAVn_DEVID values display the corresponding human-readable strings on the HW ID page.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.