Skip to content

[New Device] <SK64S>

Name of device:

Skyloong SK64S (Manufacturer jikedingzhi.com)

Link to manufacturer's product page:

Seller: https://aliexpress.com/item/1005001471570774.html?spm=a2g0o.productlist.0.0.68fa43162xQKEM&algo_pvid=da0ed4b7-b1bd-4879-86b4-70964a4cdff6&algo_expid=da0ed4b7-b1bd-4879-86b4-70964a4cdff6-0&btsid=0b0a050116144130397895001e154f&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

Manufacturer (Official Software): http://www.jikedingzhi.com/downloadlist?driverID=41

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

DeviceTypeUSB

S Version has Bluetooth

ID information:

Manufacturer: (Standard keyboards)

Description         Service DeviceID
-----------         ------- --------
HID Keyboard Device kbdhid  HID\VID_1EA7&PID_0907&MI_00\8&267B8D71&0&0000
HID Keyboard Device kbdhid  HID\VID_1EA7&PID_0907&MI_02&COL03\8&1AA062FD&0&0002

In Linux using lsusb it shows as:

Bus 003 Device 007: ID 1ea7:0907 SHARKOON Technologies GmbH Keyboard

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

Home page:

SK64S_Software1

LE File creator/editor (Animation and lighting):

SK64S_Software_AnimationCreator

Software revision and list of supported devices:

SK64S_SoftwareVersionInfo

Please attach device captures here:

GK64 and SK64 use the same software and probably have identical PCBs.

Unofficial driver version with support for linux (CLI): https://github.com/pixeltris/GK6X

GK64 firmware dump: https://github.com/wgwoods/gk64-python/

GK64 Captures by: @rgvxsthi issue: #421

1ea7_0907_ReportDescriptor.txt 1ea7_0907_DeviceDescriptor.txt

SK64 Captures:

Report Descriptor:xxxx_xxxx_ReportDescriptor.pcapng

Blue: BlueLEDs_Capture.pcapng

Green: GreenLEDs_Capture.pcapng

Red: RedLEDs_Capture.pcapng

Green to red change: Green-to-RedLEDs_Capture.pcapng

Rainbow: Rainbow_Capture.pcapng

Additional Info:

As @rgvxsthi reported a driver (For N-Key Rollover) was added in the Linux Kernel 5.13: Link to the commit

The manufacturer's website is currently down, including the official driver download page!

The manufacturer's website seems to be online again!

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 Joan Aluja Oraá