You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

USB-IDs-for-free.txt 6.6KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  1. Version 2009-08-22
  2. ===========================
  3. FREE USB-IDs FOR SHARED USE
  4. ===========================
  5. Objective Development has reserved a set of USB Product-IDs for use according
  6. to the guidelines outlined below. For more information about the concept of
  7. USB IDs please see the file USB-ID-FAQ.txt. Objective Development guarantees
  8. that the IDs listed below are not used by any USB compliant devices.
  9. ====================
  10. MECHANISM OF SHARING
  11. ====================
  12. From a technical point of view, two different devices can share the same USB
  13. Vendor- and Product-ID if they require the same driver on operating system
  14. level. We make use of this fact by assigning separate IDs for various device
  15. classes. On application layer, devices must be distinguished by their textual
  16. name or serial number. We offer separate sets of IDs for discrimination by
  17. textual name and for serial number.
  18. Examples for shared use of USB IDs are included with V-USB in the "examples"
  19. subdirectory.
  20. ======================================
  21. IDs FOR DISCRIMINATION BY TEXTUAL NAME
  22. ======================================
  23. If you use one of the IDs listed below, your device and host-side software
  24. must conform to these rules:
  25. (1) The USB device MUST provide a textual representation of the manufacturer
  26. and product identification. The manufacturer identification MUST be available
  27. at least in USB language 0x0409 (English/US).
  28. (2) The textual manufacturer identification MUST contain either an Internet
  29. domain name (e.g. "mycompany.com") registered and owned by you, or an e-mail
  30. address under your control (e.g. "myname@gmx.net"). You can embed the domain
  31. name or e-mail address in any string you like, e.g. "Objective Development
  32. http://www.obdev.at/vusb/".
  33. (3) You are responsible for retaining ownership of the domain or e-mail
  34. address for as long as any of your products are in use.
  35. (4) You may choose any string for the textual product identification, as long
  36. as this string is unique within the scope of your textual manufacturer
  37. identification.
  38. (5) Application side device look-up MUST be based on the textual manufacturer
  39. and product identification in addition to VID/PID matching. The driver
  40. matching MUST be a comparison of the entire strings, NOT a sub-string match.
  41. (6) For devices which implement a particular USB device class (e.g. HID), the
  42. operating system's default class driver MUST be used. If an operating system
  43. driver for Vendor Class devices is needed, this driver must be libusb or
  44. libusb-win32 (see http://libusb.org/ and
  45. http://libusb-win32.sourceforge.net/).
  46. Table if IDs for discrimination by textual name:
  47. PID dec (hex) | VID dec (hex) | Description of use
  48. ==============+===============+============================================
  49. 1500 (0x05dc) | 5824 (0x16c0) | For Vendor Class devices with libusb
  50. --------------+---------------+--------------------------------------------
  51. 1503 (0x05df) | 5824 (0x16c0) | For generic HID class devices (which are
  52. | | NOT mice, keyboards or joysticks)
  53. --------------+---------------+--------------------------------------------
  54. 1505 (0x05e1) | 5824 (0x16c0) | For CDC-ACM class devices (modems)
  55. --------------+---------------+--------------------------------------------
  56. 1508 (0x05e4) | 5824 (0x16c0) | For MIDI class devices
  57. --------------+---------------+--------------------------------------------
  58. Note that Windows caches the textual product- and vendor-description for
  59. mice, keyboards and joysticks. Name-bsed discrimination is therefore not
  60. recommended for these device classes.
  61. =======================================
  62. IDs FOR DISCRIMINATION BY SERIAL NUMBER
  63. =======================================
  64. If you use one of the IDs listed below, your device and host-side software
  65. must conform to these rules:
  66. (1) The USB device MUST provide a textual representation of the serial
  67. number. The serial number string MUST be available at least in USB language
  68. 0x0409 (English/US).
  69. (2) The serial number MUST start with either an Internet domain name (e.g.
  70. "mycompany.com") registered and owned by you, or an e-mail address under your
  71. control (e.g. "myname@gmx.net"), both terminated with a colon (":") character.
  72. You MAY append any string you like for further discrimination of your devices.
  73. (3) You are responsible for retaining ownership of the domain or e-mail
  74. address for as long as any of your products are in use.
  75. (5) Application side device look-up MUST be based on the serial number string
  76. in addition to VID/PID matching. The matching must start at the first
  77. character of the serial number string and include the colon character
  78. terminating your domain or e-mail address. It MAY stop anywhere after that.
  79. (6) For devices which implement a particular USB device class (e.g. HID), the
  80. operating system's default class driver MUST be used. If an operating system
  81. driver for Vendor Class devices is needed, this driver must be libusb or
  82. libusb-win32 (see http://libusb.org/ and
  83. http://libusb-win32.sourceforge.net/).
  84. Table if IDs for discrimination by serial number string:
  85. PID dec (hex) | VID dec (hex) | Description of use
  86. ===============+===============+===========================================
  87. 10200 (0x27d8) | 5824 (0x16c0) | For Vendor Class devices with libusb
  88. ---------------+---------------+-------------------------------------------
  89. 10201 (0x27d9) | 5824 (0x16c0) | For generic HID class devices (which are
  90. | | NOT mice, keyboards or joysticks)
  91. ---------------+---------------+-------------------------------------------
  92. 10202 (0x27da) | 5824 (0x16c0) | For USB Mice
  93. ---------------+---------------+-------------------------------------------
  94. 10203 (0x27db) | 5824 (0x16c0) | For USB Keyboards
  95. ---------------+---------------+-------------------------------------------
  96. 10204 (0x27db) | 5824 (0x16c0) | For USB Joysticks
  97. ---------------+---------------+-------------------------------------------
  98. 10205 (0x27dc) | 5824 (0x16c0) | For CDC-ACM class devices (modems)
  99. ---------------+---------------+-------------------------------------------
  100. 10206 (0x27dd) | 5824 (0x16c0) | For MIDI class devices
  101. ---------------+---------------+-------------------------------------------
  102. =================
  103. ORIGIN OF USB-IDs
  104. =================
  105. OBJECTIVE DEVELOPMENT Software GmbH has obtained all VID/PID pairs listed
  106. here from Wouter van Ooijen (see www.voti.nl) for exclusive disposition.
  107. Wouter van Ooijen has obtained the VID from the USB Implementers Forum, Inc.
  108. (see www.usb.org). The VID is registered for the company name "Van Ooijen
  109. Technische Informatica".
  110. ==========
  111. DISCLAIMER
  112. ==========
  113. OBJECTIVE DEVELOPMENT Software GmbH disclaims all liability for any
  114. problems which are caused by the shared use of these VID/PID pairs.