[New Device] Ducky Zero 6108

Hi,

I've recently changed from a Ducky ONE 2 RGB TKL to a Ducky Zero 6108 and was wondering if this could also be added to the OpenRGB software.

From the Hardware ID's listed in the application this is what i've got for the device,

[3233:0021 U=0006 P=0x0001 I=0] Ducky - Ducky Zero 6108 [3233:0021 U=0080 P=0x0001 I=0] Ducky - Ducky Zero 6108 [3233:0021 U=0001 P=0x000C I=0] Ducky - Ducky Zero 6108 [3233:0017 U=0006 P=0x0001 I=0] Ducky - Ducky Zero 6108 2.4GHz [3233:0017 U=0006 P=0x0001 I=1] Ducky - Ducky Zero 6108 2.4GHz [3233:0017 U=0080 P=0x0001 I=1] Ducky - Ducky Zero 6108 2.4GHz [3233:0017 U=0001 P=0x000C I=1] Ducky - Ducky Zero 6108 2.4GHz [3233:0017 U=0092 P=0xFF1C I=1] Ducky - Ducky Zero 6108 2.4GHz [3233:0017 U=0002 P=0x0001 I=1] Ducky - Ducky Zero 6108 2.4GHz

Let me know if this is possible!

Name of device:

Ducky Zero 6108

Link to manufacturer's product page:

https://www.duckychannel.com.tw/en/DuckyZero6108

Please select what type of device/interface the device uses:

~"DeviceType::Keyboard" DeviceTypeUSB

ID information: USB\VID_3233&PID_0021&MI_01\7&2F0607CA&0&0001

Please attach screenshots of the device's official control application here:

image

Please attach device captures here:

https://gitlab.com/OpenRGBDevelopers/OpenRGB-Wiki/-/blob/stable/Device-Documentation/Ducky-Keyboards.md

The link has an example of the other ducky keyboards being picked up via different USB VID and USB PID to my current keyboard. If USB VID: 3233 and USB PID: 0021 was also a value added to this document, my keyboard might work with the software, though i don't know how to do this.

https://gitlab.com/Dr_No/OpenRGB/-/tree/stable/Controllers/DuckyKeyboardController?ref_type=heads

only suggestion is editing the "DuckyKeyboardController.h" file linked to include my keyboard, i downloaded a zip file and tried to check this but i don't understand enough about github to freely edit and make changes to items to try get a test app working.

Checklist for Step2

  • Name of device
  • A link to the vendors product page has been included
  • The transport bus has been identified and the appropriate label added to the issue.
  • The device ID's have been included for USB or PCI
  • Screenshots of the OEM Application are included
  • There is either, appropriate code examples linked or suitable device captures attached
Edited by Robert Meekings