Ckb-next: K57 RGB Wireless Keyboard

[Brainwasher06]

Hello,

Is it possible to add my keyboard in your software ? If you do it would be much appreciated =)

• If possible, try the latest code by building the software manually. ( i used ./quickinstall , dont know if it's what you mean)

Thank you for your work and your time.

Have a good day

Enter the name of your device here and attach the report generated above :
K57 RGB Wireless Keyboard
ckb-next-report-1573647243.gz

[tatokis]

It uses a completely new and redesigned protocol that we haven't looked into, and probably will not for a while. No one else has shown interest in implementing this protocol.

[87racer]

Just grabbed this keyboard and would be interested as well.

[kaijuagenda]

Recently bought one myself. shame there's no support yet.

[oppositionsecurity]

Recently returned 2 K57's actually. If you type 70+ WPM you will be sorely disappointed with the "selective n-key rollover". Very common 3 and 4 letter combinations will fail to type in rapid succession. As a side note the K95 is great, despite the cost, and is fully supported and allows for some cool effects using the top LEDs as notifications lights.

[kaijuagenda]

Recently returned 2 K57's actually. If you type 70+ WPM you will be sorely disappointed with the "selective n-key rollover". Very common 3 and 4 letter combinations will fail to type in rapid succession. As a side note the K95 is great, despite the cost, and is fully supported and allows for some cool effects using the top LEDs as notifications lights.

Not sure how well the measure holds up. I frequently break 90+ WPM on the K57 with no apparent issues, Nor can i replicate the problem you described. Either way I don't see the point of this response, unless the goal was to shill a more expensive peripheral.

[superjcvd]

I am interested too :)
So far the keyboard works fine in bluetooth.

• the sound control keys are working
• the RGB isn't working
• the macro keys are not working

[ThisNekoGuy]

I just got mine in the mail today, myself, it feels pretty great Lol
But yeah, it's unfortunate that there isn't support for it yet

[ethergary]

I'm also interested, most functionality works straight from the keyboard on the K57 out of the box for Linux, but it would be nice to be able to have full control over RGB and the macro keys like in this (very nice) software port for the other devices. I noticed that the K55 is supported which, other than wireless, appears virtually identical to the K57 at a glance as far as features and how it works (over USB at least, the wireless abilities not withstanding). I seem to figure with it plugged into USB should it communicate the same as the K55? And/or is it possible for testing purposes to 'fake' the K55 feature set in the ckb-next software to point to the K57 keyboard while plugged into USB within the software to test? I'm currently using Ubuntu 20.04 (POP OS style) which recognizes the keyboard just fine otherwise, but naturally not able to read as connected via ckb-next. I'm happy to go in and give it a go in the code, but some bread crumbs to point the way would be helpful. If it's my problem to figure out, no worries - I just like the keyboard and this software. And not particularly gifted at hardware driver programming.

[erdoking]

I am interested too! Really nice keyboard...

@ethergary : have a look here:
https://github.com/erdoking/ckb-next/commit/eb2e6bf8a26ea56aa46d8ec59119461f4a413509

I have played with the code a little bit and add detection for k57
It is detected but nothing is working ... Maybe a beginning ;)

While the compiled ckb-next is running the keyboard does not working.

[tatokis]

I have started work on implementing this for the ironclaw wireless.
I can look into this if you can provide the HID report descriptors of the device, in both wired and wireless mode using

sudo usbhid-dump -d 1b1c:xxxx

where xxxx is the device id (can be found using lsusb).

Additionally, I need wireshark captures of the device being plugged in with the corsair windows software running.
Start capture, plug device in, wait for a bit, stop capture.

Both wired and wireless, again, would be helpful.
All you need to do is install usbpcap when prompted while installing wireshark, and then find the appropriate capture device in wireshark itself.

[erdoking]

HID report:

Bus 001 Device 008: ID 1b1c:1b6e Corsair USB 2.0 Hub

usbhid-dump -d 1b1c:1b6e
001:008:002:DESCRIPTOR         1598253662.528718
 06 42 FF 09 02 A1 01 15 00 26 FF 00 75 08 95 40
 09 02 81 02 C0

001:008:001:DESCRIPTOR         1598253662.529510
 06 42 FF 09 01 A1 01 15 00 26 FF 00 75 08 95 40
 09 01 81 02 95 40 09 01 91 02 C0

001:008:000:DESCRIPTOR         1598253662.531037
 05 01 09 06 A1 01 85 01 05 08 95 03 75 01 19 01
 29 03 15 00 25 01 91 02 95 05 91 03 05 07 75 01
 19 E0 29 E7 95 08 81 02 19 00 29 67 95 68 81 02
 19 87 29 8E 95 08 81 02 C0 05 0C 09 01 A1 01 85
 02 95 01 75 10 15 00 26 FF 03 19 00 2A FF 03 81
 00 C0

Bus 001 Device 011: ID 1b1c:1b62 Corsair CORSAIR K57 RGB Wireless Dongle

001:011:003:DESCRIPTOR         1598253890.755936
 05 0C 09 01 A1 01 85 02 95 01 75 10 15 00 26 FF
 03 19 00 2A FF 03 81 00 C0

001:011:002:DESCRIPTOR         1598253890.756411
 06 42 FF 09 02 A1 01 15 00 26 FF 00 75 08 95 40
 09 02 81 02 C0

001:011:001:DESCRIPTOR         1598253890.756867
 06 42 FF 09 01 A1 01 15 00 26 FF 00 75 08 95 40
 09 01 81 02 95 40 09 01 91 02 C0

001:011:000:DESCRIPTOR         1598253890.757430
 05 01 09 06 A1 01 85 01 05 08 95 03 75 01 19 01
 29 03 15 00 25 01 91 02 95 05 91 03 05 07 75 01
 19 E0 29 E7 95 08 81 02 19 00 29 67 95 68 81 02
 19 87 29 8E 95 08 81 02 C0

I need to install the corsair windows software first ;) havn't start windows 10 for month ...

[erdoking]

usb_corsair_k57.zip

I have created the captures - thank you very much for your engagement :)

1.) disconnected all USB devices
2.) stop iCUE
3.) start wireshark
3.) plugin keyboard (wired OR wireless)
4.) start iCUE
5.) activate some effects
6.) Repeat

On wireless we cant do the same things like on wired! maybe different protocols?
On wireless we cant program each key color different for example...

[tatokis]

A bit late, but excellent.
It helped me reverse quite a bit of the protocol. You can load bragishark in wireshark and have a look if you wish.

Before I add the device to ckb, can you please make another capture, both with CUE off and on, simply pressing some keys and noting down which keys they are.
For example: Close CUE, start capture, type press "qwerty", stop capture.
And then also repeat with CUE running.

[tatokis]

Oh, and also, what layout is your keyboard? @erdoking (European/American/etc)

[erdoking]

usb_corsair_k57_qwertz.zip
I updated to iCUE 3.33.246
My keyboard layout is European (qwertz)

I pressed the keys:
qwertz left up right botton and G1-G6

G6 open the windows menu if cue not running

At the moment i have no idea how to load bragishark ... but i found it out ;)

[bvcelari]

I got one of this Keyboards too, Is there anyway I can help? it's a pitty I cannot use ckb-next

[magni08]

Also interested and willing to assist.

Using qwerty layout on a manjaro distro.

[DrajonsAreEpic]

I have a K57 and would love to be able to use use ckb-next. Willing to help, but don't have any practical coding abilities. Using a QWERTY layout on Pop!OS.

[pmsobrado]

Any updates on this? I just got a K57 myself and I'm willing to help by any means possible. I have Windows and Ubuntu 18.04.

[nmartin-cs]

Found this project after picking up a K57. CKB daemon running is systemd (Arch). Got most everything working using udev; few things I'd like to fix. Personally I could care less about the led lights ;)
@tatokis I'd like to take a look at this protocol. You mentioned it is different than the earlier models? Can you point me at it? Sorry if you mentioned this before TL;TD