Skip to content

Drivers: add Holybro Pixhawk 6C USB ID (VID_3162 PID_0053) - #3735

Open
PROF0UND wants to merge 1 commit into
ArduPilot:masterfrom
PROF0UND:holybro-pixhawk6c-usb-id
Open

Drivers: add Holybro Pixhawk 6C USB ID (VID_3162 PID_0053)#3735
PROF0UND wants to merge 1 commit into
ArduPilot:masterfrom
PROF0UND:holybro-pixhawk6c-usb-id

Conversation

@PROF0UND

Copy link
Copy Markdown

The Holybro Pixhawk 6C uses VID 0x3162 PID 0x0053 as a composite USB device, presenting two interfaces:

  1. MI_00 for MAVLink and
  2. MI_02 for SLCAN.

This PID was not in Holybro.inf, causing the board to appear as a generic "USB Serial Device" in Windows rather than identifying itself.

This was confirmed on a physical Pixhawk 6C:

Get-PnpDevice -Class Ports | Select-Object FriendlyName, InstanceId, Status

shows

USB\VID_3162&PID_0053&MI_00 

and

USB\VID_3162&PID_0053&MI_02 

with status OK but no friendly name.

Related to #2095 (which added earlier Holybro PIDs but predates the 6C).

Pixhawk 6C uses VID 0x3162 PID 0x0053 as a composite USB device,
presenting MI_00 (MAVLink) and MI_02 (SLCAN) interfaces. Without
this entry the board shows as generic 'USB Serial Device' in Windows.

Closes: related to ArduPilot#2095
@robertlong13

Copy link
Copy Markdown
Collaborator

I can confirm that the VID/PID matches ArduPilot's hwedef for that board, and the .inf changes seem to be correct.

But Holybro.cat will need to be re-signed with Michael's cert. Which only @meee1 (and apparently @tridge ) can do.

@PROF0UND

Copy link
Copy Markdown
Author

oh no! Mission planner's connect dropdown shows a bunch of COM ports for me and I though this would be a nice fix for everyone. Hopefully gets signed!

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.

2 participants