Initialization and Color Packets for Alienware Monitors AW2518H, AW3418HW, and AW3418DW

[Th4nato5]

Not sure if this has been mentioned yet, but Alienware Monitors send out the following packets for the below respective monitors during initialization and color setting:

• AW2518H:

1. Initialization Packet: 95000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2. Color Setting Packet: 9248050004XXRRGGBBffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

XX in the Color Setting Packet changes based on the LED ID being set. AW2518H has the following LED locations and the respective LED IDs:

1. Backside: 01

RR, GG, BB represents the hex number of the RGB values (0 to 255).

Vendor ID: 0x0424
Product ID: 0x274c

• AW3418DW:

1. Initialization Packet: 95000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2. Color Setting Packet: 9248050004XXRRGGBBffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

XX in the Color Setting Packet changes based on the LED ID being set. AW3418DW has the following LED locations and the respective LED IDs:

1. Upper Left Backside: 01
2. Stand Backside: 02
3. Middle Bottom: 04
4. Power Button: 08

RR, GG, BB represents the hex number of the RGB values (0 to 255).

Vendor ID: 0x0424
Product ID: 0x274a

• AW3418HW:

1. Initialization Packet: 95000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2. Color Setting Packet: 9248050004XXRRGGBBffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

XX in the Color Setting Packet changes based on the LED ID being set. AW3418HW has the following LED locations and the respective LED IDs:

1. Upper Left Backside: 01
2. Stand Backside: 02
3. Middle Bottom: 04
4. Power Button: 08

RR, GG, BB represents the hex number of the RGB values (0 to 255).

Vendor ID: 0x0424
Product ID: 0x274b

[T-Troll]

Yep, it's APIv6 pattern.

By the way, LightID is a mask, so you can set many lights at one command (f.e. using 0x6 as an ID will set 2 lights).

Normally, APIv6 have a checksum at the end of color set package (depending on command type - you only set color, but pulse and morph are also available), and also have a brightness into each command.

Seems like this is a new, simplified API. I can support it, but need more info from you to fully implement it:

1. Is command length still 64, as before?
2. Is command code 0x48, not 0x84?
3. What is ReportID for this monitor (zero byte into USBPcap package interseption)?
4. What is the command to switch lights to pulse/morph?
5. What is the command to switch brightness?

(this is mine APIv6 description for your reference)

// V6, monitors
		//const byte systemStatus[3]{0x93,0x37,0x0e};
		//[3] - some command, can be 06 and 0e
		//reply: 94 37 (command) XX.....XX - status
		const byte COMMV6_systemReset[]{ 4, 0x95,0,0,0 };
		//const byte colorReset[11]{ 0x92,0x37,0x07,0x00,0x51,0x84,0xd0,0x03,0x64,0x55,0x59 };
		const byte COMMV6_colorSet[]{2, 0x92,0x37 };
		//[3] - command length (a - color, b - pulse, f - morph, 7 - timing),
		//[6] - command (87 - color, 88 - Pulse, 8c - morph/breath, 84 - timing?),
		//[8] - command type - 4 - color, 1 - morph, 2 - pulse, 3 - timing?
		//[9] - light mask,
		// 3,84 - [10] - Brightness, [11] - ???, [12] - checksum
		// 4,87 - [10,11,12] - RGB, [13] - Brightness (0..64), [14] - checksum
		// 2,88 - [10,11,12] - RGB, [13] - Brightness (0..64), [14] - Tempo?, [15] - checksum
		// 1,8c - [10,11,12] - RGB, [13,14,15] - RGB2, [16] - brightness, [17,18] - tempo, [19] - checksum