Creator Z16 - No compatible keyboard found

[hey-kzn]

Hi everyone ! Thanks for the tools ! but the install & test give me this " no compatible keyboard found ", i tried other tools for control rgb and same issue.

What can i do for fix that ? :(

[Gibtnix]

Well, one thing you could try is to modify the IDs according to your keyboard: sudo msiklm list to extract the IDs, thereafter change the IDs in the open_keyboard() function. Thereafter, the test option should at least find the keyboard, otherwise the IDs are wrong. If this works, you can test any of the commands. Currently, two different command structures are used, depending on the arguments (cf. Readme for full information about this), you could try both. If both do not work, your keyboard is likely to not be supported at all because it needs a different command structure that needs to be known to support your keyboard.

[hey-kzn]

Ok thanks for the response, i tried your solutions but still give me the same message.

[Gibtnix]

If you change the IDs accordingly, at least sudo msiklm test should find your keyboard. If you changed the IDs in msiklm.c and the command does not find your keyboard, the IDs are not correct. Also be careful in not mixing hex/decimal numbers which of course can change the results.

[hey-kzn]

I tried but the same issue : "no compatible keyboard found" with IDs hex, i dont know what can i do for fix that

[Gibtnix]

The used IDs are incorrect if this message appears. The command sudo msiklm test only initializes the device corresponding to the IDs, so if you read them out with sudo msiklm list before and replace the read IDs with the ones in msiklm.c, recompiling and retesting has to work. Maybe delete the 0x prefix, but if you use your IDs, sudo msiklm test has to work. Of course. whether the commands work is a different story...

[brokencog]

Just to clarify for @Akouniakov the "msiklm list" returns the vendor/product ID's in decimal value which does not need the 0x hexidecimal.

My question is about the "command structures" you mentioned. I don't see any explanation in the README, could you help me understand this? I'm trying to figure out why the keyboard LEDs aren't being adjusted.

The only debugging I've done is output the result from hid_send_feature_report(), which results in 0x08 ... which is the number of bytes written to the device?

It could likely be this model isn't supported, I have an MSI GE76 which has the SteelSeries info of:

Device: SteelSeries KLC
    Device Vendor ID:        4152
    Device Product ID:       4410
    Device Serial Number:    (null)
    Device Manufacturer:     SteelSeries
    Device Path:             3-9:1.0
    Device Interface Number: 0
    Device Release Number:   258

Device: SteelSeries KLC
    Device Vendor ID:        4152
    Device Product ID:       4410
    Device Serial Number:    (null)
    Device Manufacturer:     SteelSeries
    Device Path:             3-9:1.1
    Device Interface Number: 1
    Device Release Number:   258

Device: SteelSeries ALC
    Device Vendor ID:        4152
    Device Product ID:       4414
    Device Serial Number:    (null)
    Device Manufacturer:     SteelSeries
    Device Path:             3-10:1.0
    Device Interface Number: 0
    Device Release Number:   256

Device: SteelSeries ALC
    Device Vendor ID:        4152
    Device Product ID:       4414
    Device Serial Number:    (null)
    Device Manufacturer:     SteelSeries
    Device Path:             3-10:1.1
    Device Interface Number: 1
    Device Release Number:   256

[Gibtnix]

The details regarding the command structure, in particular with the different ways how the command is created is explained in the usability section in the Readme. The different command structure is triggered by explicitly setting the intensity, i.e. sudo msiklm green is different to sudo msiklm green high. For details please refer to the Readme.

[brokencog]

oh. I thought you meant the readme explains something about how it functions ... okay, yes, I see adding the intensity as a third option. Do you happen to know of any additional HID libraries which might help make it work with this hardware?

…

-daniel

On Wed, Apr 6, 2022 at 12:36 PM Gibtnix ***@***.***> wrote: The details regarding the command structure, in particular with the different ways how the command is created is explained in the usability section in the Readme. The different command structure is triggered by explicitly setting the intensity, i.e. sudo msiklm green is different to sudo msiklm green high. For details please refer to the Readme. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGCULF5N6ZZ7WMZKPAWXKTVDXRUZANCNFSM5RQSI6VA> . You are receiving this because you commented.Message ID: ***@***.***>

[Gibtnix]

I think it is not about the correct library but instead the correct command structure. The correct command structures are not documented somewhere. I guess if you build the right command, it will work.
About the existing two options, there is not really much to explain more. The details you find in the code.

[brokencog]

Well, if "blue high" is a valid 'command structure's, then I understand that this. The issue is further along than that. The hid_send_report() ... Sorry not at the computer,don't recall the full name ... Returns 8, the number of bytes written to the keyboard. Yet nothing happens with the LED s.

…

On Wed, Apr 6, 2022, 12:52 PM Gibtnix ***@***.***> wrote: I think it is not about the correct library but instead the correct command structure. The correct command structures are not documented somewhere. I guess if you build the right command, it will work. About the existing two options, there is not really much to explain more. The details you find in the code. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGCULEDG5QWOH2XLABDUI3VDXTO5ANCNFSM5RQSI6VA> . You are receiving this because you commented.Message ID: ***@***.***>

[Gibtnix]

Try sudo msiklm blue and sudo msiklm blue high. If both do not work, your keyboard is most likely not supported.

[brokencog]

Not supported. But since the windows code functions, it's about getting the bits correct, hence my question about other HID libs ... I'll keep looking into it if I get it to work I'll let you know. Thanks again.

…

On Wed, Apr 6, 2022, 1:18 PM Gibtnix ***@***.***> wrote: Try sudo msiklm blue and sudo msiklm blue high. If both do not work, your keyboard is most likely not supported. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGCULAZIK2ZZQP4KGL662LVDXWRVANCNFSM5RQSI6VA> . You are receiving this because you commented.Message ID: ***@***.***>

[Gibtnix]

You're welcome