Unsolved

Closed

1 Rookie

 • 

26 Posts

735

February 28th, 2023 21:00

Area-51 R2, FXlight initialization problem after replacing motherboard

CEDBB29F-E994-45B2-AB83-E7F16D0539BF.jpegFA0A30FB-A480-4CF0-BD9A-6B75CA8234D5.jpeg

A4EB4F5D-0BC4-48D7-B006-5AD769B9D284.jpeg2EE1FEAA-DE4A-4889-8241-CF8C25191C38.jpeg

KakaoTalk_20230301_142210304.jpgKakaoTalk_20230301_142209935.jpgI recently upgraded my msi b550 motherboard and cpu (5800x3d) and visited this forum for an FXlight interlocking problem to get an answer and am using it well now. Once again, I want to thank everyone who helped me. However, there is one problem to worry about because it is not perfectly linked with fxlight.

For reference, I am using the area-51 r5 model case. I found and installed the command center suitable for me, and it runs very well even changing the color of the led through fxlight. However, if you turn off the power of the pc and turn it on again, all fxlight leds are initialized, and the leds of the area-51 case become dark. So, you have to go through the cumbersome fxlight integration process again.

Right now, the PC is not turned off and is in sleep mode. After putting the PC on standby in power saving mode and then returning, the fxlight lights up without any problems. So, if you want to use Windows in power saving mode and the Windows program is a little heavy, reboot your PC again. Then the window will be clean again. During the reboot of the pc, the fxlight led is maintained well. Well, I'm pretty satisfied with this one.

However, I am a little worried because I do not know what will happen because it is not perfect. I wrote a long article, but the really important question is, is it possible to create this state in which the fxlight led lights up immediately when the pc is turned off and then turned on again? It's like the state where the LED comes on right away when you turn on the power of the area-51 in its original state before replacing the motherboard.

If you have a solution for this, please discuss.

9 Legend

 • 

15.1K Posts

March 1st, 2023 09:00

Re: if you turn off the power of the pc and turn it on again, all fxlight leds are initialized, and the leds of the area-51 case become dark. So, you have to go through the cumbersome fxlight integration process again.

I think you need to save an AlienFx profile in AWCC.  I speak of this from using AWCC version for A51 R2 and R1.  R5 uses a different version of AWCC.

nice work that you accomplished to get the colorful led turned on. I suppose you got successful after connecting both USB1 and JFP1 cables btn motherboard and FIO.  Any thought in retrospect why your Windows dev manager had an error detecting USB device before when you powered on the FIO via 4 pin molex?  What was the mistake and which remedy did you apply to solve the issue? 

4 Operator

 • 

2.3K Posts

March 1st, 2023 17:00

FX color themes need to be saved in the Area-51 R5 also

ProfessorW00d_0-1677720494825.png

 

1 Rookie

 • 

42 Posts

April 10th, 2023 08:00

Any Idea how'd he manage to get all the FX Lights working? I'm just behind him with only the Power button Led working but no side or front panels lit. The Power Button Obeys and Remains to the custom colors in the updated AWCC 5.XXX. My MOLEX Cable if plugged in however gives me the Port Reset Error in device Manager and kills the powerbutton light

Stating he must have successfully 'Connecting USB1 and JFP1 cables' - Ive completed both Front Panel Cable Mod (hole poked) and installed the USB1 usb 2.0 cable and cant get any further. Suffered the same problems with the FIO Mini Board (AW EC device) in the Device Manager.

I'm pretty much stumped.

1 Rookie

 • 

26 Posts

April 10th, 2023 21:00

I connected the jfp jack before turning on the pc. After disconnecting all USB1 and Molex 4-pin power terminals, I turned on the PC. (Since the jfp terminal was disconnected, turn on the power by shorting the main board) Both side panels should be open at this time. After entering Windows, connect the jfp terminal, usb1, and Molex 4-pin terminal in order. There may be a notification that the wrong usb device is connected, but it is not a problem at all Perhaps the case front LED and the power button LED will light up Then it goes into power save mode Reattach both side panels after entering power save mode. After that, it returns to Windows from sleep mode. Both side panel LEDs should light up as well. Of course it's not a sure way, but I succeeded like this Now there is no problem with fxlight led control like before upgrade We wish you success

528F9BD6-7640-4F79-AB13-CDB68F2CE6DF.jpeg

 

9 Legend

 • 

15.1K Posts

April 11th, 2023 05:00

have you tried both usb 2.0 header on your msi Z790 edge ddr4 motherboard?

hopefully OP success experience may help you. “there will be light.”

https://download.msi.com/archive/mnu_exe/mb/MPGZ790EDGEWIFIDDR4.pdf

1 Rookie

 • 

42 Posts

April 11th, 2023 12:00

Yes tried both usb2.0 headers and created the required pinhole and confirmed pinouts for both cables on the motherboard and the FIO. My original post is here.

I'll attempt the above but rather odd that device manager will only be happy through a sequence of activations with the usb devices

9 Legend

 • 

15.1K Posts

April 12th, 2023 17:00

my experience with the R2 FIO (I do not have R5) is that the FIO is programmed by previous user using Dell motherboard and the settings were left in FIO after Dell board was removed.  On initial power up with new non-Dell board, some LED will light up depending on previous setting stored in FIO.  It is important not to have Windows kick in for that will often kill all LED except power button.  To put it simply the front and side LED use some USB 2.0 digital settings that were previously programmed for light on/off color.  when the board is just powered up there are default logical voltage on the 9 pin.  When Windows is booted it automatically resets all USB 2.0 logic level.   In my R2 with an old XPS motherboard, I instantly get all red led on power up during POST before boot, the red was programmed by me on previous boot using AWCC.  but this all red on state only lasts 2 sec then all off because pc quickly boots into Win 10.  After Win 10 it takes another 2 min for AWCC to kick in and retake control of LED.  and what makes Dell bloatware AWCC worse is that it is not reliable.  1/2 times AWCC does not launch or fails to take over LED from basic Windows.  thus all LED remain off.  I had to reboot to make it work.  it would then work for a few times but if I power off and unplug power for a few days, next time it does same thing.

try to experiment with case led without Windows.  I disconnect hdd sata cable. Power up front panel waterfall led constantly on.  side panels led are off.  But if either side panel is opened slightly using latch, then closed again, that instantly turned on led on both side panels.  Seems the opening/closing of side panel refreshes side led connection when Windows is absent.

October 7th, 2023 07:20

The only solution for my FIO r2 and to be able to reverse the color stored by the old user is to completely remove the power from the FIO board and the entire PC in general (turning off the power supply and holding down the power button for a correct discharge ) when I turn the PC back on, I manage to make all the LEDS light up including the side panels, (sometimes it is necessary to open and close a side cover during the post, but most of the time it is enough to just remove the electrical current) also The AWCC is functional and I was able to modify the lighting profile and store my last lighting configuration on the FIO board. The only uncomfortable thing is to repeat this process every time the PC is turned on.

(edited)

No Events found!

Top