The Wooting config is based around a USH HID Generic interface. The base of this report is from the AVR ASF (http://ww1.microchip.com/downloads/en/appnotes/doc8499.pdf). If I remember correctly there are some slight changes, but nothing to major.

With this generic interface you can basically read and write bytes however you want it. The PC (host) will always initiate the configuration.

The Report In and Out are set as 128 bytes. The feature report size is 8 bytes.

There are two main parts in the protocol:

1. Commands
2. Reports

Direct access to raw analog values from an analog keyboard for game and application developers.

This project will allow you to build your own DLL and customize the source code. Looking to directly get started with the DLL? Check out the downloads and guides in our developer portal

The main goal of Wooting is to make analog keyboards an industry standard, with the analog SDK being the main driver. If you just look at Wooting keyboards in itself it would make sense to combine them into one. One system that can control everything. But this way we set ourselves up for a problem.

The peripheral market right now already has many RGB systems. Most closed and some starting to open up a bit. Even though the RGB systems have many flaws and are not compatible at all, companies have already decided on their systems.

Now imagine you’re a company deciding if you want to adopt this new analog thing: would you want there to be a RGB part in it that competes with your own system? That’s why we decided to keep it split. The analog SDK should be it’s own pure thing that is just focussed on one thing, making analog keyboards standard in the industry. The RGB SDK is just a cool separate Wooting thing.