Hello! My English is poor.
I bought a Redragon K580 Vata keyboard (not Pro) for SignalRGB. The device support section listed this model, not the Pro. The program recognizes it, but it doesn’t work properly. The keys stick when pressed! Any keys. Also, in various places, different colors are constantly flashing that aren’t present in the backlight preset. If I select the Redragon K557 Kala V2 in the settings, the keys behave normally, but the backlighting doesn’t work correctly. Or maybe I need special firmware?
Try connecting it to a USB 3.0 port.
These keyboards use a generic protocol, and this issue is related to USB bandwidth. Different models can have different chips, and some may be more sensitive than others, causing issues like this.
Unfortunately, it didn’t help. Is it possible to identify the chip only by disassembling the keyboard? Or can I manually edit the EVision_Keyboard_Controller.js plugin?
It probably has different Device IDs and a slightly different layout. I’d report the bug using the bug icon in the app (upper-right corner) or through this link so that the support team can follow up.
Fingers crossed the dev team can fix it with a little extra info. 
Thanks! I’ll try contacting support through SignalRGB.
I took the keyboard apart to check the microcontroller markings. It’s a Vision VS11K33A, but there’s no information online about the microcontroller it uses!
When I submit a bug report, the program closes and restarts. Is this supposed to happen? Or maybe the bug report wasn’t sent?
The form closes, but the app shouldn’t crash. Might need to send it as an email to [email protected]
I solved the problem myself. Support never responded. Since I’m not a professional but an amateur, it took me about 7 hours to find a solution. I can say one thing: “Redragon not only replaced a fairly good Sonic microcontroller with a cheap VS11K33A (I couldn’t find the real microcontroller behind it online), but also a very weak one!”
It chokes on a 56-bit packet stream (hence the loops and flashes of unwanted colors), so by trial and error, 24-bit proved to be the most stable.
To fix these errors, you need to:
Go to %localappdata%\VortxEngine
Then go to app-2.5.хх\Signal-x64\Plugins\EVision
Open EVision_Keyboard_Controlle.js in a text editor (Notepad++) and find the line “const bytesToSend = 56;” change the value from 56 to 24 and restart the SignalRGB program.
Now the keyboard should work correctly.
Good luck everyone!
Addition (working on bugs):
Find the line “calculateChecksum(packet, index, bytesToSend = 56”). Change 56 to 24.
If the keys sometimes flicker when the color is static, then:
- Find the line “device.write(packet, 64);” underneath it will be “device.pause(1);” Change 1 to 10.
- If that doesn’t help, reduce the FPS to 30. To do this, at the very top, under the line “import DeviceDiscovery from “@SignalRGBSignalRGBSignalRGBSignalRGB/DeviceDiscovery”;”, add the line “export function FPS() { return 30; }”
I’ll provide this information to the devs and see what can be done! Thanks for all the extra information you provided!!
I ran a few more tests and eventually settled on the following:24bit packet - this indeed turned out to be optimal. The backlight works with a 56bit packet. But the microcontroller can’t process keystrokes correctly. Apparently, 120 LEDs and keystrokes are too much for it.device.pause(1); - 10 was too much, 2 is enough. I don’t know if the engine can handle non-integer numbers, like 1.5
export function FPS() { return 30; } - If the backlight is static and has no FPS limit, the various keys flicker periodically. I think 30 or 60 would be distinguishable to the naked eye.With these changes, everything works smoothly for me, including the backlighting at the edges!
Glad to hear you were able to figure it out, and sorry you didn’t receive a response from our support team.
We’ve been working through all tickets, so it’s possible your message didn’t reach us or was filtered as spam. To help us check, could you share the email subject or ticket number so we can look into it?
Hello! I submitted an issue report in the program. At first, the program closed after I sent it. But then it seemed to send it, and the program didn’t close. Unfortunately, I don’t remember the exact title. Then I contacted the tech-support channel on Discord. I attached a video for clarity and a photo of the controller. But unfortunately, they didn’t respond either.
If the ticket submission was successful, you should get a confirmation email. If for some reason it didn’t go through, you can send an email to [email protected] to create a ticket over email.
I talked to the team and mentioned the fix, and the team is working to see what might be done on the plugin side. The issue is that the manufacturer usually uses boards that accept the higher bit rate and it’s not always clear what’s in use by the manufacturer 
There was no confirmation email, which means the bug report wasn’t sent.
I’ll still send the letter as you suggested. Maybe the problem isn’t the package size? And will they require any information from me?
I fully support you, as I mentioned above. Redragon loves doing this. I bought this keyboard because of the support and the ability to flash QMK, but it was a total failure! I don’t think it’s even worth waiting for now 
We usually check the device console for us to know more how the device is configured. Have you sent us a bug report yet so we can look into this further?