| layout | title | permalink |
|---|---|---|
page |
Frequently Asked Questions |
/faq/ |
Please read our howto guide.
Is this supported by the USB-IF?
No, pid.codes is in no way supported, endorsed by, or associated with USB-IF.
pid.codes and the people behind it have never signed an agreement with USB-IF not to reassign or redistribute PID codes. The VID we were gifted was procured from USB-IF by a company that has since ceased trading, and they did so before USB-IF's terms prohibited sublicense or transferring of VIDs or PIDs.
It is our belief that USB-IF has no legitimate right to prohibit this activity, and that their actions are limited to 'revoking' the original VID, a fairly meaningless pronouncement since they can never reassign it to anyone else. Nevertheless, we hope they will not do so, and will instead choose to work with us to make creating and distributing USB devices more accessible for hobbyists, makers, and small businesses.
No, absolutely not. The domain name registration is our only cost besides our time, and we paid for that out of our own pockets. We accept no income from users or advertisers.
Operating systems use VID and PID codes to uniquely identify a device, which helps determine what drivers to load and how to interact with it.
Yes, absolutely. You need to have created a repository for your source code somewhere, with your work so far. If it's plain that you're not yet at the point of needing a unique PID, we might suggest you use a testing PID. If you've got several unreleased projects, we might ask for justification before handing out another PID.
We'd really rather you didn't do this, but we won't try and 'take away' your PID. Once it's assigned to you, it's yours until the heat death of the universe. However, don't expect any more PIDs from us in future!
PIDs are allocated in the order pull requests are submitted. If the first pull request is rejected for whatever reason, the PID will go to a subsequent requester.
Email us at [email protected].