Area-51 FX light does not turn on after replacing msi motherboard

it is an interesting question.  most people asked how to put a non-Dell board in A51 R2 case which is triad 1.0.  you have a R5 case which is triad 2.0 and it has no slot loading odd at front panel.  the MIO of R5 looks like this

you are certainly missing the USB wire from #3 of MIO to new non-Dell motherboard.  hence there is no talk between the MIO and new board.  therefore AlienFx would not work.

NB: the stock Dell R5 board uses proprietary 10 pin header for FIO and USB1.  After you replace the board you may continue to use the Dell proprietary cables if they are long enough to reach new board FIO and USB2.0 header.  make sure the 10 pin connector is connected in correct orientation on new board 9 pin header.

If cables are not long enough you need to acquire your own FIO cable and USB2.0 cable.  Once both cables are connected, and MIO powered by 4 pin molex, use R5 registry key hack to install AWCC (or you can continue to use prior HDD w OS installed for R5 board).  go inside AWCC folder to find AlienFxtester.exe to test all LED.

Re: If I directly connect leftover usb2.0 9 pin to msi motherboard usb2.0 9 pin cable, all lights turn off.  

this may be expected if Windows is initially launched from HDD.  to have all LED on continuously as a test, remove HDD from pc so it powers on but can not find OS.  In my R2, all LEDs on for 1-2 sec right after power on, then all off as pc boots into Windows, then it launches AWCC, which can take up to 2 min or longer if using slower mechanical hdd, then all LEDs on again (but sometimes remains all off because of intermittent AWCC runtime bug).

thank you very much for your answer

I tried again with what you told me, and it seems that something else is wrong.

I connected USB1 (2.0-9PIN) on the small board that was missing yesterday,

but Windows doesn't recognize it.

                                                              (I'm a Korean)        

Literally, "Unknown USB Device (Port Reset Failed)"

I thought it might be a bad cable, so I connected it by alternating other cables, but it's the same phenomenon

My guess is that the small motherboard (model name: MS-4440) is causing this phenomenon due to a recognition error. The motherboard seems to be an OEM product from MSI. I'm trying to find out how to download and install the corresponding driver here. I think it could be solved by recognizing this little motherboard guy. And thank you so much again for your reply. If you have any information about this, please share.

this is a little known territory as most of the successful install have been done in triad1.0 case, but certainly very interesting.

I think the principle behind a successful pairing of new motherboard and Dell FIO daughter-board is the same for R2 and R5 case.  You need a usb2.0 cable and JFP cable to connect the two boards.  FIO needs to have molex 4 pin power.

R5 uses these Dell proprietary cables

afaik there is no driver to download to have motherboard recognize FIO.

You are correct . . . the Molex 4-pin on the MIO board is connected directly to the PSU. The other connector you have circled in the lower photo is an 8-pin EPS supplemental power for the PCIe slots. Let me know if I can help with any other photos or additional information.

Are the red marked Molex 4-pin power lines connected to each other?

If that's right...

I thought the Molex power line was connected directly to the power, but I may have made a mistake.

I honestly do not know exactly how FIO interacts with non-Dell mobo to control various led. I remember I had trouble (a lot of trouble) at beginning w a R2 case and non-Dell board.  I got the front led default blue color before connecting any cable to FIO (the case was bought without any Dell cable). But after I connected some cable, I lost all led, which was very discouraging.  But then one day I got it.
Rather than studying how the FIO should appear properly in Windows dev mgr, a quicker way is to use AlienFXtester.exe which is a small utility app inside AWCC folder.  You want to see this screen which means FIO is detected.

Oh~! I wasn't the only one who couldn't recognize the usb I was honestly giving up, but your words give me hope again.

Your answer is very deep.

thank you I'm just guessing myself... FIO power when booting Windows 10 turned off, and the USB device is connected Because there is a device manager It may be accepted as a recognition error.

So, after work, I use usb1 and jfp After disconnecting the cable jack and booting When entering the window, the FIO power After being put in, I plan to connect usb1 and jfp cable jack.

Or through the bios menu FIO power can be continuously input.

It's going to be important to make it I hope you can remember I wish, that's how desperate it is thank you

Make sure it lights up feeling that something is going well received

But that feeling didn't last long When you turn off your PC and turn it on again Everything will be initialized.

LED light is not continuous When restarting Windows or in sleep mode, the LED stays on. However, if I turn off the PC and turn it back on, everything is reset.Now, even the USB device (FIO board) is not recognized well.

I have uninstalled and reinstalled windows several times in this process.

As I continued to work on this, I discovered something. If you remove the Molex 4-pin power terminal of the FIO board (literally without giving power) and connect the usb1 jack, it is recognized very well as the correct device in Device Manager.

Just plug in the Molex terminal and turn on the power. If given, it will be recognized as a wrong device in Device Manager from then on.

And awcc only for r2 Even when the usb device is recognized correctly, the fxlight part cannot be entered.

The fan control part or the overclocking part is well entered. Even fxlight test.exe has never recognized the FIO board.

However, only the latest version of awcc was able to enter fxlight and change the color.

Is there any solution for this part? My goal is to make the device manager's usb device recognized normally once the FIO power is connected. And next time, I want to see a scene where the FIO board is normally recognized in fxlight test.exe Any advice on this issue? gradually loses power

You have already made big progress.  I agree AWCC is not prefect. I think you have to save a profile of LED (all red or all blue or whatever) in AlienFxeditor.exe, another stand alone app inside AWCC folder.  Then next time after restart it will remember the saved color pattern.  For me I just pick one color I like then be done w it.  I do not really change it often at all.  You should completely remove old AWCC for R2 and install AWCC for R5.  Best way is to do clean OS install then one clean AWCC install. Do it right the first time.

I am considering upgrade to my R4 board after reading a discussion here

However, I would like to have the Thermal Controller app work  That app is in the 2017 "Control Center"
 and is not in any of the recent AWCCs

Does the r2 have a Thermal Sensor app?  If so, does it work on your new board?

@CityFire 

what was your final outcome there? lights? LEDs? Lit up like a UFO ??? Christmas tree? Yes No Maybe?

Report back at your leisure, ty

ProTip: always bring the resolution by posting a pic or more of your mthrbrd swap success

Meme: pictures or it didn't happen