Difference between revisions of "Simucube product USB interface documentation"
From Granite Devices Knowledge Wiki
[checked revision] | [checked revision] |
m (Mtakala moved page Simucube product USB interface to Simucube product USB interface documentation) |
(→Simucube product USB interface detection) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 10: | Line 10: | ||
==Simucube product USB interface detection== | ==Simucube product USB interface detection== | ||
* USB Vendor ID: 0x16d0 | * USB Vendor ID: 0x16d0 | ||
− | * USB Product IDs and Windows | + | * USB Product IDs and Windows guidProduct ID list: |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Line 16: | Line 16: | ||
! USB Product ID | ! USB Product ID | ||
! guiProduct ID | ! guiProduct ID | ||
+ | ! Visible name in Windows | ||
+ | ! Notes | ||
|- | |- | ||
| Simucube 1 | | Simucube 1 | ||
| 0x0d5a | | 0x0d5a | ||
| {0D5A16D0-0000-0000-0000-504944564944} | | {0D5A16D0-0000-0000-0000-504944564944} | ||
+ | | SimuCUBE | ||
|- | |- | ||
| Simucube 2 Sport | | Simucube 2 Sport | ||
| 0x0d61 | | 0x0d61 | ||
| {0D6116D0-0000-0000-0000-504944564944} | | {0D6116D0-0000-0000-0000-504944564944} | ||
+ | | Simucube 2 Sport | ||
|- | |- | ||
| Simucube 2 Pro | | Simucube 2 Pro | ||
| 0x0d60 | | 0x0d60 | ||
| {0D6016D0-0000-0000-0000-504944564944} | | {0D6016D0-0000-0000-0000-504944564944} | ||
+ | | Simucube 2 Pro | ||
|- | |- | ||
| Simucube 2 Ultimate | | Simucube 2 Ultimate | ||
| 0x0d5f | | 0x0d5f | ||
| {0D5F16D0-0000-0000-0000-504944564944} | | {0D5F16D0-0000-0000-0000-504944564944} | ||
+ | | Simucube 2 Ultimate | ||
+ | |- | ||
+ | | Simucube Link Hub | ||
+ | | 0x0d66 | ||
+ | | {0D6616D0-0000-0000-0000-504944564944} | ||
+ | | SC-Link | ||
+ | | Used by Simucube ActivePedal | ||
|} | |} | ||
− | Note, that the first part of the guiProduct ID is in hexadecimal, and can be used to identify the device in game application's detection code. | + | Note, that the first part of the guiProduct ID is in hexadecimal, and can be used to identify the device in game application's detection code. See: https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ee416610(v=vs.85)?redirectedfrom=MSDN |
+ | Good tool to investigate available DirectInput devices on the system is the DiTool, available from https://sourceforge.net/projects/x360ce/files/ditool.zip/download | ||
[[Category:Force_feedback_system]] | [[Category:Force_feedback_system]] | ||
[[Category:Simucube_2]] | [[Category:Simucube_2]] | ||
[[Category:Technology]] | [[Category:Technology]] |
Latest revision as of 17:58, 1 February 2023
Simucube product USB axis description and support requirements[edit | edit source]
- Wheel axis: X axis, Unsigned 16 bit field, 0-65535 value
- Y axis: Unsigned 16 bit field. This axis will idle at center position. However, users can map external pedal or handbrake to this axis.
- Do not utilize product X and Y axises for in-game menu browsing!
- Pedal/handbrake axises: 6 additional axises, unsigned 16 bit values.
- These can be set by users to inteface with Simucube-compatible pedals or handbrakes, or with (upcoming) analog axises (clutch paddles) from Simucube Wireless Wheels
- Buttons: There are 128 buttons.
- All buttons can be used by Simucube 1 physical interface, and when combined with a Simucube wireless wheel, support for all 128 buttons is required for optimal user experience.
Simucube product USB interface detection[edit | edit source]
- USB Vendor ID: 0x16d0
- USB Product IDs and Windows guidProduct ID list:
Product name | USB Product ID | guiProduct ID | Visible name in Windows | Notes |
---|---|---|---|---|
Simucube 1 | 0x0d5a | {0D5A16D0-0000-0000-0000-504944564944} | SimuCUBE | |
Simucube 2 Sport | 0x0d61 | {0D6116D0-0000-0000-0000-504944564944} | Simucube 2 Sport | |
Simucube 2 Pro | 0x0d60 | {0D6016D0-0000-0000-0000-504944564944} | Simucube 2 Pro | |
Simucube 2 Ultimate | 0x0d5f | {0D5F16D0-0000-0000-0000-504944564944} | Simucube 2 Ultimate | |
Simucube Link Hub | 0x0d66 | {0D6616D0-0000-0000-0000-504944564944} | SC-Link | Used by Simucube ActivePedal |
Note, that the first part of the guiProduct ID is in hexadecimal, and can be used to identify the device in game application's detection code. See: https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ee416610(v=vs.85)?redirectedfrom=MSDN Good tool to investigate available DirectInput devices on the system is the DiTool, available from https://sourceforge.net/projects/x360ce/files/ditool.zip/download