Windows 10: What report descriptor usages are required for HID UPSes?

Discus and support What report descriptor usages are required for HID UPSes? in Windows 10 Software and Apps to solve the problem; I'm developing an HID power device UPS and having trouble getting it to work on Windows - it does get recognized, but shows 0% charge.The report... Discussion in 'Windows 10 Software and Apps' started by Antonlya, Jun 25, 2023.

  1. Antonlya Win User

    What report descriptor usages are required for HID UPSes?


    I'm developing an HID power device UPS and having trouble getting it to work on Windows - it does get recognized, but shows 0% charge.The report generated by `powercfg /energy` suggests that the battery capacity is unknown, even though my reports contain this data. I would like to ask: under which paths does Windows look for the battery capacity? Is there any recommended report descriptor structure for Windows?Any help would be appreciated. Thanks.

    :)
     
    Antonlya, Jun 25, 2023
    #1

  2. Problem with Joystick HID descriptor readout

    I bought a used Joystick (Speedlink Phantom Hawk), which I can't return. The Z-Rotation Axis (twist axis) has a weird offset and doesn't read out the full Motion, it is centred at readout 180, and only uses about 20-30% of the IRL range. I tried everything conventional, and everything driver related, nothing helped (Windows driver, Speedlink Joystick Driver, and alternative drivers).

    From Hours of trying to fix this Problem, I got to figure out what exactly is not working correctly, however I couldn't find a way to solve it.

    Using "Free Device Monitoring Studio" I am able to read out the HID descriptor and the Values send by the Joystick.

    The Problem is, that the Joystick has 2 Z-Axis readouts, the first one is the actual Z-Rotation Axis with its full range, the second Z-Axis is the thrust Slider, and the Rz-Axis is again the Z-Rotation, but only part of the Range with the weird offset.

    The actual Z-Axis gives values between 35-230 over the full twist range.

    So it's not a faulty sensor.

    The Question now is, is there a way to get it working again, either by editing the HID descriptor, or by making it that Windows reads the actual Z-Axis instead of the false Rz-Axis?

    One readout of sent packages looks like this:

    Report ID:-1

    X[0..255]/[0..255]: 128

    Y[0..255]/[0..255]: 125

    Z[0..255]/[0..255]: 146 <--- actual twist Axis

    Z[0..255]/[0..255]: 127

    Rz[0..255]/[0..255]: 174 <----fake/false twist Axis.

    Hat Switch[0x0..0x7]/[0x0..0x13b]: 0xf

    BUTTON1 pressed: 0

    BUTTON2 pressed: 0

    BUTTON3 pressed: 0

    BUTTON4 pressed: 0

    BUTTON5 pressed: 0

    BUTTON6 pressed: 0

    BUTTON7 pressed: 0

    BUTTON8 pressed: 0

    BUTTON9 pressed: 0

    BUTTON10 pressed: 0

    BUTTON11 pressed: 0

    BUTTON12 pressed: 0

    Unknown: 0

    Unknown: 0

    Unknown: 0

    Unknown: 0

    Unknown: 0

    Unknown: 0

    Unknown: 1

    Unknown: 0

    The HID Descriptor reads out this:

    05 01 09 04 A1 01 09 00 A1 02 09 30 15 00 25 FF

    35 00 45 FF 65 00 55 00 75 08 95 01 81 02 09 31

    81 02 09 32 81 02 09 32 81 02 09 35 81 02 09 39

    25 07 46 3B 01 65 14 75 04 81 42 05 09 19 01 29

    0C 25 01 45 01 65 00 75 01 95 0C 81 02 95 08 81

    03 C1 00 06 00 FF 09 00 A1 02 09 02 25 FF 45 FF

    75 08 95 07 91 02 C1 00 C1 00

    Which when Parsed gives this:

    0x05, 0x01, // Usage Page (Generic Desktop Ctrls)

    0x09, 0x04, // Usage (Joystick)

    0xA1, 0x01, // Collection (Application)

    0x09, 0x00, // Usage (Undefined)

    0xA1, 0x02, // Collection (Logical)

    0x09, 0x30, // Usage (X)

    0x15, 0x00, // Logical Minimum (0)

    0x25, 0xFF, // Logical Maximum (-1)

    0x35, 0x00, // Physical Minimum (0)

    0x45, 0xFF, // Physical Maximum (-1)

    0x65, 0x00, // Unit (None)

    0x55, 0x00, // Unit Exponent (0)

    0x75, 0x08, // Report Size (8)

    0x95, 0x01, // Report Count (1)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x09, 0x31, // Usage (Y)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x09, 0x32, // Usage (Z)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x09, 0x32, // Usage (Z)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x09, 0x35, // Usage (Rz)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x09, 0x39, // Usage (Hat switch)

    0x25, 0x07, // Logical Maximum (7)

    0x46, 0x3B, 0x01, // Physical Maximum (315)

    0x65, 0x14, // Unit (System: English Rotation, Length: Centimeter)

    0x75, 0x04, // Report Size (4)

    0x81, 0x42, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,Null State)

    0x05, 0x09, // Usage Page (Button)

    0x19, 0x01, // Usage Minimum (0x01)

    0x29, 0x0C, // Usage Maximum (0x0C)

    0x25, 0x01, // Logical Maximum (1)

    0x45, 0x01, // Physical Maximum (1)

    0x65, 0x00, // Unit (None)

    0x75, 0x01, // Report Size (1)

    0x95, 0x0C, // Report Count (12)

    0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0x95, 0x08, // Report Count (8)

    0x81, 0x03, // Input (Const,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)

    0xC1, 0x00, // End Collection

    0x06, 0x00, 0xFF, // Usage Page (Vendor Defined 0xFF00)

    0x09, 0x00, // Usage (0x00)

    0xA1, 0x02, // Collection (Logical)

    0x09, 0x02, // Usage (0x02)

    0x25, 0xFF, // Logical Maximum (-1)

    0x45, 0xFF, // Physical Maximum (-1)

    0x75, 0x08, // Report Size (8)

    0x95, 0x07, // Report Count (7)

    0x91, 0x02, // Output (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile)

    0xC1, 0x00, // End Collection

    0xC1, 0x00, // End Collection



    // 106 bytes
     
    Garip Coban, Jun 25, 2023
    #2
  3. EdTittel Win User
    a request for device descriptor request failed

    Maybe it's time to step back from the current efforts, and start over. I suggest you read over this excellent tutorial and try all of its steps: [Solved] Unknown USB Device (Device Descriptor Request Failed) for Windows 10 - Driver Easy. The one that may provide you with some easy relief is the one where you uninstall the device whose descriptor is failing, reboot, and see what happens when device enumeration recurs during boot-up. If you're lucky, it will fix itself.
    HTH,
    --Ed--
     
    EdTittel, Jun 25, 2023
    #3
  4. What report descriptor usages are required for HID UPSes?

    I2C HID Device (This device cannot start. (Code 10) A request for the HID descriptor failed.)

    Hi, For some time I've been experiencing some touchpad-related problems, it stopped working multitouch/multi-finger touch after a time of use, but after the restart, the touchpad started working again, but the issue was still happening. So I decided to take a look in the drivers and found I2C HID Device (This device cannot start. (Code 10) A request for the HID descriptor failed.) with yellow markings, then started disabling, enabling and Uninstalling HID device from device manager and restarted, still it did not work, then, I have taken support from Dell executives and they took online sessions and it worked. but after four or five days it started again I tried everything they(Dell online support Executive) suggested to me. Now I don't know what to do. I just wanted to use a functional touchpad, now. I installed and updated all the drivers, and windows update is up to date, but still no use My machine is a Dell Inspiron 15 7591 2 in 1.
     
    zarmin ahsan, Jun 25, 2023
    #4
Thema:

What report descriptor usages are required for HID UPSes?

Loading...
  1. What report descriptor usages are required for HID UPSes? - Similar Threads - report descriptor usages

  2. I2C HID Device - This device cannot start. Code 10 A request for the HID descriptor failed.

    in Windows 10 Gaming
    I2C HID Device - This device cannot start. Code 10 A request for the HID descriptor failed.: So i'm attempting to fix an HP Pavilion x360 14-dh2034nr with issues related to the touchpad. There's a yellow triangle next to the driver and nothing I do seems to fix it.I have already reinstalled windows while keeping all my files, attempted to find the newest driver for...
  3. What report descriptor usages are required for HID UPSes?

    in Windows 10 Gaming
    What report descriptor usages are required for HID UPSes?: I'm developing an HID power device UPS and having trouble getting it to work on Windows - it does get recognized, but shows 0% charge.The report generated by `powercfg /energy` suggests that the battery capacity is unknown, even though my reports contain this data. I would...
  4. Problem with Joystick HID descriptor readout

    in Windows 10 Gaming
    Problem with Joystick HID descriptor readout: I bought a used Joystick Speedlink Phantom Hawk, which I can't return. The Z-Rotation Axis twist axis has a weird offset and doesn't read out the full Motion, it is centred at readout 180, and only uses about 20-30% of the IRL range. I tried everything conventional, and...
  5. Problem with Joystick HID descriptor readout

    in Windows 10 Software and Apps
    Problem with Joystick HID descriptor readout: I bought a used Joystick Speedlink Phantom Hawk, which I can't return. The Z-Rotation Axis twist axis has a weird offset and doesn't read out the full Motion, it is centred at readout 180, and only uses about 20-30% of the IRL range. I tried everything conventional, and...
  6. Problem with Joystick HID descriptor readout

    in Windows 10 Drivers and Hardware
    Problem with Joystick HID descriptor readout: I bought a used Joystick Speedlink Phantom Hawk, which I can't return. The Z-Rotation Axis twist axis has a weird offset and doesn't read out the full Motion, it is centred at readout 180, and only uses about 20-30% of the IRL range. I tried everything conventional, and...
  7. I2C HID Device. Code 10: A request for the HID descriptor failed.

    in Windows 10 Drivers and Hardware
    I2C HID Device. Code 10: A request for the HID descriptor failed.: I2C HID Cihazı. Kod 10: HID tanımlayıcı için bir istek başarısız oldu. https://answers.microsoft.com/en-us/windows/forum/all/i2c-hid-device-code-10-a-request-for-the-hid/f9866d9b-596a-4fa2-b895-41584d35cf64
  8. 12C HID Device will not start Code 10 A request for the HID descriptor failed.

    in Windows 10 Drivers and Hardware
    12C HID Device will not start Code 10 A request for the HID descriptor failed.: I've tried just about every fix on the internet to try and resolve this issue for a non-functioning touchpad. In Device Manager there is only an option for Mouse with no mention of Touchpad. Anyone out there with a solution or is there some ugly secret?...
  9. I2C HID Device. Code 10: A request for the HID descriptor failed.

    in Windows 10 Drivers and Hardware
    I2C HID Device. Code 10: A request for the HID descriptor failed.: Hi, I have a Huawei Matebook D from 2017. For one year periodically the driver for the HID I2C device failed. Sometimes like magic, it comes back to work again. It always affects the touchpad accessory functions and gestures and usually, I fix this functionality with a USB...
  10. I2C HID Device. Code 10: A request for the HID descriptor failed.

    in Windows 10 Drivers and Hardware
    I2C HID Device. Code 10: A request for the HID descriptor failed.: Hi, I have a Huawei Matebook from 2017. For one year periodically the driver for HID I2c device failed. Sometimes like magic, it comes back to work again. It always affects the touchpad accessory functions and gestures and usually, I fix this functionality with a USB mouse....