/Virpil-Communicator

A small library for communicating with Virpil Devices

Primary LanguageC#GNU General Public License v3.0GPL-3.0

Virpil Communicator

Nuget .NET 5 CI build GitHub Discord

This package allows you to talk to Virpil HID devices. It's fairly feature limited at this moment and is currently designed for firmware version 20210102.

Usage/Examples

// 0x825B is the PID of Virpil Control Panel #2
var controlPanel2 = new DeviceCommunicator(0x825B);

// set LED #1 on the panel to #FFFFFF (white)
controlPanel2.SendCommand(BoardType.OnBoard, 1, LedPower.Full, LedPower.Full, LedPower.Full);

Packet structure

This document is probably accurate enough for firmware 20210102. I make no guarantee any of this data will hold true for any other firmware version.

The data fragment for setting an LED (and perhaps other things, too) is 38 bytes in length. A sample payload might look something like the following:

02 66 05 00 00 80 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 f0

This data should be written as a Feature.

Understanding the bytes

00: 02

I'm not sure what this is for, but it's at the start of every data fragment

01: 66

For our purposes, this is the type of board you're communicating with. Possible values are:

  • 64: default : used to set all leds back to their default settings that were set with the profile
  • 65: add-board : I'm not sure what this is for
  • 66: on-board : used when the led you want to modify is on the device you're communicating with
  • 67: slave-board : used when the led you want to modify is on a slave device of the device you're communicating with

02: 05

This is the id of the command you are running. You can view these commands in the VPC_LED_Control tool, but I'll list them here too.

  • 00: used to set all leds back to default
  • 01-04: used for setting add-board leds 1-4
  • 05-24: used for setting on-board leds 1-20
  • 25-44: used for setting slave-board leds 1-20

05: 80

Defines the [color](#The Color Byte) the LED should be set to.

NOTE! the position of this byte varies depending on the led being modified. For example, if you were modifying LED 2 this would be in slot 06, if you were modifying LED 15 this would be in slot 19, etc.

25: f0

Not really sure what this one does either, but it seems to close out every data fragment.

The Color Byte

Since color is sent over a single byte, we effectively get 6-bit (2-2-2) color (note the colors at that link are slightly different from the ones you'll see on your hardware, as your hardware uses 25/50/100% instead of 33/67/100%). A sample color might look something like this:

1010 1100

and is structured as

10bb ggrr

This means that each channel has just 4 states - off [00], and 3 intensities of on (25% [01], 50% [10], and 100% [11]) - for a total of 64 possible colors. In this example, we have 0 red, 100% green, and 50% blue - producing a lovely Irish Stream color.

Examples

Set LEDs to default colors

0000   02 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0010   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020   00 00 00 00 00 f0

Set on-board LED 3 to bright magenta

0000   02 66 07 00 00 00 00 b3 00 00 00 00 00 00 00 00
0010   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0020   00 00 00 00 00 f0

Set slave-board LED 14 to dark cyan

0000   02 67 26 00 00 00 00 00 00 00 00 00 00 00 00 00
0010   00 00 94 00 00 00 00 00 00 00 00 00 00 00 00 00
0020   00 00 00 00 00 f0

Acknowledgements