My rear fan in my desktop PC used to be detected in OpenRGB until about a week ago after I installed some firmware updates for my Asus ROG Strix Z690-A motherboard. All of my 4 fans and my cooler are from Corsair, and three of the fans are plugged into one Corsair Commander Core. The Core is still being detected by OpenRGB, but the rear fan is not anymore. If I recall correctly it is managed by a Corsair RGB header. Additionally, My GSkill RGB RAM works but it is now being detected as a generic ENE DRAM. If I try to rescan devices nothing changes. What should I do?

  • Steeltooth493@beehaw.orgOPEnglish
    1·
    10 months ago

    Both the Corsair Commander Core controller and the ASUS ROG motherboard are being detected in OpenRGB, but there is a 7th fan controller that is separate that is not being detected. That’s the one that is out.

    • CalcProgrammer1@lemmy.mlMEnglish
      1·
      10 months ago

      What kind of controller is it? Note that anything that connects to an ARGB header is NOT a controller, it’s a splitter or a hub and those are not detected in OpenRGB. An ARGB controller generates an ARGB signal from external software control while a splitter/hub just routes a signal from a different device.

      • Steeltooth493@beehaw.orgOPEnglish
        1·
        10 months ago

        I think that it’s a Corsair fan hub that I had connected to the Corsair Commander Core controller. Would OpenRGB be able to detect the fan if the hub is connected to the controller that way, even if it is not listed as a device? I’m beginning to suspect that the fan hub connection came loose somewhere, but I haven’t had an opportunity to check it out yet.

        • CalcProgrammer1@lemmy.mlMEnglish
          1·
          10 months ago

          The Corsair fan hub is basically a glorified wiring box, it is not a smart device and does not get detected in software. All the Corsair fan hub does is route the ARGB output signal of Fan 1 to the ARGB input of Fan 2 and so on for all connected fans. The number of LEDs needs to be entered manually.

          The ARGB protocol is just a string of LED data like RGBRGBRGBRGB… and it doesn’t know how many LEDs worth of data it should send out unless you enter this number by resizing the associated zone on the controller. The protocol is one-way meaning the controller has no feedback from the LEDs in the fan and thus has no idea if they actually receive the data or how many LEDs are actually connected.

          • Steeltooth493@beehaw.orgOPEnglish
            1·
            9 months ago

            Okay, so is it possible to use and plug two Corsair Commander Cores into each other and then have them both be detected by OpenRGB?

            • CalcProgrammer1@lemmy.mlMEnglish
              1·
              9 months ago

              You would plug them both into your motherboard, not into each other (unless that device has a built in USB hub then you could). It would show as two different devices and each one would have however many ARGB channels that you could use. I know Lighting Node Pro has 2 channels and same with Commander Pro but I’m not familiar with the Commander Core.

              • Steeltooth493@beehaw.orgOPEnglish
                1·
                9 months ago

                So I bought a Corsair Commander Core XT this weekend and I installed it today. It partly fixed it because my rear fan now lights up in white, but OpenRGB hasn’t been able to detect it yet. I haven’t been able to control the fan RGB and change the color as a result. I did not connect the Commander Cores up to each other yet. The Commander Core XT has an optional 3 pin RGB C header and one USB 2.0 headers that I did not connect up. Should I try connecting either of those from the XT to the other Commander Core?