Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

[CaseySJ]

Things I notice:
1) You are credited in the driver! How cool.

I credited myself because I wrote it. Actually this is my third liquidctl driver. The three are:

• NZXT Smart Device V2 (which Jonas Malaco has since extended to support more V2 devices)
• Gigabyte RGB Fusion 2.0
• Asus Aura LED

2) if a kraken cooler or nzxt rgb device is installed, they are natively recognized by liquidctl. As such, when trying to control argb per the commands in your post, liquid fails with the following message:

'Error: too many devices, filter or select one (see: liquidctl --help)'

In this case, we can match to the device name and let liquidctl control asus alone instead of nzxt.
So Command becomes: 'liquidctl -m asus set argb2 color static 00ff00'

Exactly right! When there are multiple supported controllers, we must use the -m argument to distinguish between them.

3) While the command works to control the color on the selected port, the lights on the other ports go out.
So by default, all ports are set to rainbow. However, when running liquidctl on port 3 (argb3), the lights on the other two ports go out. Not sure this should happen. They should remain in the mode they were in until specifically programmed by the user. Just a suggestion.

This is one of the known issues when we use effect mode in which the controller does the work. The other mode is direct in which the software must continuously issue USB command codes to keep the lighting effects going. This mode is not supported.

However, it should definitely be possible to set two channels to static mode but with different colors. I'll re-check that shortly.

Otherwise, real cool that we can use python to extend liquidctl for Asus Aura. I can imagine a GUI wrapper around liquidctl (with buttons and color pickers and such) to control RGB. I just need to find the time to code it.

The OpenRGB GitHub project provides a GUI interface, but its implementation of Aura LED controller does not support the version we have on this motherboard. If you do create a GUI, that would be great.

Edit: another observation, once the aura led controller is programmed by liquidctl, the settings survive a reboot and even a soft power off. I didn't cold boot to see what happens.

It even survives sleep and wake, unlike the Gigabyte RGB Fusion 2.0 controller.

 

[dehjomz]

@CaseySJ

I discovered some additional dynamic color modes that are not in the driver:
0x10, takes_color=false
0x11, takes_color=false
0x12, takes_color=true
0x13, takes_color=false

Not sure what to name these.

 

[CaseySJ]

...
Will you make a table with the different colours we can try?
...

You can actually define any color you like using two bytes for red, two for green and two for blue:

RR GG BB

RR = 0x00 to 0xFF (0 to 255)
GG = 0x00 to 0xFF (0 to 255)
BB = 0x00 to 0xFF (0 to 255)

So the total color possibilities are 256 * 256 * 256 = 16,777,216

% liquidctl set sync color static RRGGBB

 

[CaseySJ]

@CaseySJ

I discovered some additional dynamic color modes that are not in the driver:
0x10, takes_color=false
0x11, takes_color=false
0x12, takes_color=true
0x13, takes_color=false

Awesome. Where/how did you find them? Do these modes have names?

 

[dehjomz]

Awesome. Where/how did you find them? Do these modes have names?

I don't know what they are named, I just modified the aura_led.py file.
Added a test mode.

_COLOR_MODES = {
mode.name: mode
for mode in [
_ColorMode('off', 0x00, takes_color=False),
_ColorMode('static', 0x01, takes_color=True),
_ColorMode('breathing', 0x02, takes_color=True),
_ColorMode('flashing', 0x03, takes_color=True),
_ColorMode('spectrum_cycle', 0x04, takes_color=False),
_ColorMode('rainbow', 0x05, takes_color=False),
_ColorMode('spectrum_cycle_breathing', 0x06, takes_color=False),
_ColorMode('chase_fade', 0x07, takes_color=True),
_ColorMode('spectrum_cycle_chase_fade', 0x08, takes_color=False),
_ColorMode('chase', 0x09, takes_color=True),
_ColorMode('spectrum_cycle_chase', 0x0a, takes_color=False),
_ColorMode('spectrum_cycle_wave', 0x0b, takes_color=False),
_ColorMode('chase_rainbow_pulse', 0x0c, takes_color=False),
_ColorMode('rainbow_flicker', 0x0d, takes_color=False),
_ColorMode('test', 0x13, takes_color=True),
]
}

Played around with the value of 'test' to see what if anything the controller did.

 

[ummario]

You can actually define any color you like using two bytes for red, two for green and two for blue:

RR GG BB

RR = 0x00 to 0xFF (0 to 255)
GG = 0x00 to 0xFF (0 to 255)
BB = 0x00 to 0xFF (0 to 255)

So the total color possibilities are 256 * 256 * 256 = 16,777,216

% liquidctl set sync color static RRGGBB

This is awesome!

For those who want to try different colour codes here's a good website to visualise the colours and get the HEX:

RGB Color Codes Chart

RGB color codes chart, RGB color picker, RGB color table.

www.rapidtables.com

I hope I don't brake any rule for posting a external website

 

[CaseySJ]

It works! You are a genius my friend!

The only side note Is that I'm getting different colours from the ones you wrote above and previous post (maybe a typo from you or something is wrong.) Here's what I get when I enter:

liquidctl set sync color static ff0000 - turns on blue (instead of red) edit: Turns on red
liquidctl set sync color static 00ff00 - turns on green (ok)
liquidctl set sync color static 0000ff - turns on Red (instead of blue) edit: Turns on blue
liquidctl set sync color static 00ffff - Turns on Yellow (instead of cyan) edit:Turns on cyan
liquidctl set sync color off - turns off
liquidctl set sync color rainbow - Turns on rainbow
liquidctl set sync color static ff00ff - turns on purple

Good Job!

Will you make a table with the different colours we can try?

EDIT - Only later noticed that you changed to new file. Now all colours are Ok!

Looking at your photos, may I ask how you have connected the (a) front intake fans and (b) bottom intake fans? For example:

• Are front intake fans connected to ARGB header #1
• Are bottom intake fans connected to ARGB header #2
• Are all fans daisy chained and connected to one ARGB header?

 

[ummario]

Looking at your photos, may I ask how you have connected the (a) front intake fans and (b) bottom intake fans? For example:

• Are front intake fans connected to ARGB header #1
• Are bottom intake fans connected to ARGB header #2
• Are all fans daisy chained and connected to one ARGB header?

They are daisy chained connected to the same header. Do you want me to try something different?

I was not sure where to connect, because my fan cables plug has 4 holes but one is covered. And the Aura RGB Header of this MB has 4 pins, so I could not connect this cable there.

I Have RGB fans connected to this port (addressable Gen 2 Header):

 

[CaseySJ]

They Daisy chained connected to the same header. Do you want me to try something different?

I was not sure where to connect, because my fan cables plug has 4 holes but one is covered. And the Aura RGB Header of this MB has 4 pins, so I could not connect this cable there.

I Have RGB fans connected to this port (addressable Gen 2 Header):

View attachment 541379

That is perfectly okay. If, however, you wanted to set different colors for the front and bottom fans, that could be done by connecting one set to one header, and another set to another header. Anyway, no big deal...

 

[ummario]

That is perfectly okay. If, however, you wanted to set different colors for the front and bottom fans, that could be done by connecting one set to one header, and another set to another header. Anyway, no big deal...

Yes, I thought the same. Anyway I prefer to have them all with same colour. Thanks