VKB-SIM

Hello all,
I'm currently working on writing up a configuration library and configuration app for Linux (and potentially other platforms). Currently, all of the work is being done through disassembling and debugging vkbdevcfg, but I was wondering if there is any documentation available on the protocol used for communicating between vkb hardware (njoy32) and the vkbdevcfg software. Any other efforts in reverse engineering would be helpful.

The protocols are not public, but with a non-disclosure agreement (NDA) everything is possible.
Problem #1 - some complexity of data interpretation.
For example, most button functions are encoded in two bytes. The encoder takes 4 bytes in the classic notation and 8 bytes in the new one.
See an example of the current data interpretation for the encoder

This will require a detailed description of the structures and their interpretation.
But there is a problem - I have not yet finished a simple description of all the functionality for the help center. It is unrealistic to allocate time for such specific tasks.

Are you ready to deal with this on your own?


Problem #2
This can change at any time - without announcement, because these are internal functions of the configurator and firmware of the device

I'll be happy to work on it alone and in private if need be, however I would prefer the protocol be made public. I'll also be happy to work on the project alone. I've already reversed part of the data encoding algorithm used for sending certain commands such as reading CPUID, setting hardware calibration modes, and resetting the controller to defaults, but I've yet to figure out the profile system or the more advanced configs. Regardless of if the project is public or private, my main focus is getting configuration software working on linux, and I'd be happy to maintain a linux version privately with compatibility with the windows version.

Just on this, if there's anywhere we could speak privately to figure out the terms for a linux port, I'd like to work on that soon.
Thanks.

This is very interesting - I was actually thinking about doing something similar once I get more familiar with the devices (only just received by first ones).

It is nice to see that VKB is open to support such efforts.

@damiiuwu - If you'd like some help with that, I have some experience in UI programming.

In any case, keep us updated if there is any progress.