Skip to content

docs: add vendor ID allocation table #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alexcekay wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs: add vendor ID allocation table #81

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8306968
docs: add vendor ID allocation table
alexcekay May 28, 2026
cac45cb
added review feedback
alexcekay Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,37 @@ For service types, the following should be used:
- [100, 200) Reserved for future use
- [200, 256) Vendor-specific service types

Vendor message ID allocations
------------------------------

To request a block, open a PR adding a row to this table.
Companies are generally allocated a block of 20 IDs.

| Range | Namespace | Owner | Type |
|-----------------|---------------------|-----------|---------|
| 20000 - 20019 | ardupilot.* | ArduPilot | Project |
| 20020 - 20039 | com.volz.* | Volz | Company |
| 20050 - 20069 | com.hobbywing.* | HobbyWing | Company |
| 20070 - 20089 | com.tmotor.* | T-Motor | Company |
| 20110 - 20129 | com.himark.* | Himark | Company |
| 20200 - 20219 | com.hex.* | Hex | Company |
Comment thread
alexcekay marked this conversation as resolved.
| 20300 - 20319 | com.xacti.* | Xacti | Company |
| 20720 - 20799 | ardupilot.* | ArduPilot | Project |
| 20800 - 20899 | px4.* | PX4 | Project |

@tridge tridge Jun 15, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this actually exist?

@alexcekay alexcekay Jun 16, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please clarify? If you mean if there are px4 messages yet, the answer is no.

This is a reserved allocation which we would like to use similar to the ardupilot* range. The idea is to use them for project-specific messages. The first example I'd put into this space is #80. The change proposed there doesn't seem too useful for ArduPilot but is useful in the context of PX4. My plan is to open PRs for messages like this and, if they turn out not to be useful for ArduPilot, move them into this range instead.

| 20900 - 20919 | com.auterion.* | Auterion | Company |

Legacy allocations (IDs outside the blocks above, predating this table):

| IDs in use | Namespace |
|------------------------------|---------------------|
| 1033, 1035, 1038, 1039, 1332 | com.tmotor.* |
| 2018, 2019 | com.himark.* |
| 20009 | mppt.* |
| 20013 | com.hobbywing.* |
| 20030 - 20035 | dronecan.remoteid.* |
| 20100 | com.hobbywing.* |
| 20300 | cuav.* |
| 20402, 20407, 20554 | com.xacti.* |
| 21910 | ardupilot.* |

* [**DroneCAN website**](http://dronecan.org)