Area-51 R5, i9 13900ks upgrade and LGA1700 motherboard options

Hmmm.. interesting and great help to the community with this windows port of AlienFX-LED-tester.

I have a device that shows up in Device Manager when the Molex is unplugged - STL32 Bootloader.. I assume this is a subsysytem of the AW-ELC device?

With aid of the illustration Could you kindly confirm eaxctly how the HDD connections were jumped? And whether at your FPL header end or cable end at the FIO Board?

---

I have a device that shows up in Device Manager when the Molex is unplugged - STL32 Bootloader.. I assume this is a subsysytem of the AW-ELC device?

 

---

I do not have that AW-ELC.  I pulled the molex on project case and the only thing that happened is the LED's around the case turned off.  The Alienware head was the only thing left on.  I did not see anything show up on my device manager.

---

With aid of the illustration Could you kindly confirm eaxctly how the HDD connections were jumped? And whether at your FPL header end or cable end at the FIO Board?

"p

---

I bought this this kit of jumpers to replace an old Dell front panel set of LED's and switches that worked fine. 

The following is the MSI FP pinout for my project motherboard

I am not using the "5 pins" but I plan to connect the HDD LED to an led somewhere so I can see disk traffic.  This R4 case has no reset button nor disk activity light.

When I refer to the above header, I mean the header on the MSI motherboard.  I have not removed the panel cable from that case PCB as the case I bought came with all cables (but no power supply)

When I got the jumper kit in I first mod'ed the USB extension cable to allow it to fit between the Panel cable and the front panel connector.  When windows booted all the LED lights turned off.  This was unexpected but I read about the problem here.  At least the extension cable got the connector close enough to the header to make it easy to test different wiring.

I removed the extension cable from the above motherboard header and attached a single jumper "pair" between 6 & 8 and the extension cable sockets correspond to 6 & 8.  This normally is power on / off

Pressing the power switch did not turn on the system so I assume power is needed.

I then attached another jumper "pair" between 2 & 4 above and the corresponding 2 & 4 sockets on the extension.  This allowed the Alien head button to power up the system but all the LEDs turned off as before. I then unplugged the 6 & 8  at the cable externsion and plugged them into where the HDD activity cable would go.  This worked:  The power switch turns on /off the system and the LED lights do not turn off when the system boots

To PCB is just the extension cable that connects to that short "Panel" cable at the PCB.

Where those two pair of jumpers connect

A51 R1 has an MIO board = 187C:0513 = 'Gaming Desktop'

A51 R2 R3 R4 have FIO board H6HK9 = 187C:0526 = '?'

• I purchased H6HK9 to test w/ retail MSI x99 board, will know more soon
• 'Gaming Desktop' & 'AW-ELC' show up in Settings > Devices > BluTooth + Other

A51 R5 R6 R7 have FIO 3FFYN = 187C:0550 = 'AW-ELC'

____________________

In my R1 I had no luck getting R5 3FFYN to work w/ my MSI x99 retail board, in fact I couldn't get CmndCntr 5.5.xxx versions to launch, at all, while my R5 N4R4N factory image restored HDD (using the recovery partition) loads w/ CmndCntr 5.1.14.0, but even as I boot that up into my x99 retail board, nothing works yet

What I'm about to say has no use for non-R1 51s, but CmndCntr 4.8.23 DID work on my R1 MIO board, & that was interesting because it is the final & last CmndCntr version for the R4 (final CmndCntr4.0, not 5.0 etc), which we know uses the same H6HK9 FIO board as the R2

4.8.23 INCLUDES the AlienFXTester.exe > it detected my MIO but did NOT detect the R5 FIO

What DID work is when I plugged FIO board into the USB3.0 port using the 3.0 = 2.0 adaptor

DVCMNGR > I get a HIT in HID Devices --> USB\VID_187C&PID_0550\00.01

• Clearly, 187C:0550 is the R5 R6 R7 FIO board & it shows as USB in the Registry along with my 0513 MIO board

• I just can't get 0550 to list as an AFX Capable Device in the REGISTRY

Below is the Factory Restored HDD Registry, it shows 187C:0550 as AFX Capable

I'm interested if anyone can install a CmndCntr version, have working LED case lights that can change color & back etc), and have their FIO board listed as an AFX Capable Device in their Registry ... it MAY be, someone manually changes the registry by using say the factory screenshot values above, FORCE the FIO board to be recognized in those cases where it is not

I think I'm saying that when my FIO is seen as an HID Device aka USB\VID_187C&PID_0550\00.01 I'd need to direct the registry to it, 'fake it' as an AFX Capable Device but my issue is I can not get the 5.5.xxx CmndCntrs to even launch correctly to test with

This was a long way of asking anyone w/a retail board in their R2-R7 (& AFTER the CmndCntr installed) does your older 0526 or newer 0550 FIO board appear in the Registry in the column shown in pic above?, & then it goes like this right? -->

• it is not listed and my case lights work vs they do not work ever
• it is listed and my case lights work vs they still do not work ever

We'd like, I assume, for the FIO board to be listed as both an AFX Capable Device in the Registry & at the SAME time listed as say AW-ELC in the Settings > Devices portion of Windows

I made some progress on the lights, sort of.

If I connect the PWR LED to the PWR LED (instead of the HDD) then the system boots with no lights but unaccountably, I can uninstall the USB error device and when I re-install the device is enabled and the PCB is accessible as

idVendor:  0x187C
idProduct: 0x0526

I was then able to run the the awcc APP, the old from 2017 (bios description was R4 to allow the install).

Of course, nothing shows up on the LED panels.  However, I configured a morphing theme, saved it, then shut down and reconnected the PWR LED to the HDD LED like was needed to get the lights to work.  Unfortunately, when I rebooted the theme did not show up.  In fact nothing showed up which was worse then the theme not working.  I tried the AWCC app, the awcc "test" app, nothing could be done to get the lights to work again.  I then remembered that  VS2022 app I discovered on github erased** all themes  when it starts.  After running it the lights are back working. again.  By "back working" I mean they are blue after powering up  and stay blue.  I will look more into this.  If a morphing theme cannot be run possibly I can just change the color to something besides blue.  This project, getting the alien lights to work probably needs to be on another thread.

** The themes in the document folder are not erased.  The PCB is reset causing the loaded theme to be removed.

I was able to change the colors by changing "unknown" to Area51R4 in registry "Alienware AlienFX"

The morph did not work, the colors stayed the same even though the preview indicated morphing.

Going to document a lot of this here:
https://github.com/JStateson/AlienLedTest

This is amazing information thanks for it

Regarded https://fifamobileapk.com/ 

(Chiming in 2day w/ a load of nuthin)

12.12.20 I took the below screengrab showing ALL current CmndCntr versions (lol) listed on the R4/R5 support page. We see R4's final 4.8.23 then the move to newer CmndCntr 5.0 versions for R4 & R5, none of which are available for download on Dellware.com anymore (only the newest CmndCntr 5.5 versions)

The screengrab was saved by me in the event I ever moved into R4/R5 territory, I just didn't think they'd all be pulled off the site like this. I'd wondered if someone like HALOS w/ an R5 might have better luck w/ an older 5.0 version than w/the newer 5.5 versions > he only has to get lucky once & only google can reveal where they are

As for Joe, based on your very 1st post here a few pages back, are u saying u have two A51 R4 cases?, one w/ the HJ5Y7 alienboard & another w/ a retail MSI Raider? If so, u have access to OEM Registry & DvcMngr data, should parts of these issues be related to one or both areas

Q: is / are your FIO board(s) part# H6HK9 (seen in the older R2)

Q: did your latest post above claim success in having & changing colors by using 4.8.23? I don't see the side panels lit up

Q: on your MSI Raider, did you launch 4.8.23's AlienFXTester.exe & was your FIO board detected? If u have a working R4 alienboard, what'd FXTester say about its FIO board, detected? 

____________________

FYI: Aurora R1-R4 & A51 R1-R7

Warning: here, when I install a CmndCntr version not meant for my AlienFX MIO board, I DISCONNECT its USB cable 1st - install the software, restart PC, put PC to sleep, then reconnect the USB cable, wake from sleep & start to use the software. That's because newer versions of CmndCntr may try to firmware flash / update my MIO board, which I do not want to happen. YOU may heed this advice at your discretion (disconnect MIO or FIO USB cable B4 u install CmndCntr, reconnect afterwards)

In my recent post, scroll 1/2 way down p.1 to Section 2A: Install AWCC & then Section 2B: Fix AWCC After Install, where post-install of the CmndCntr as u launch into AFX & there's an error there that is solved w/a few mouse clicks & a trip into Registry Editor as below > change 'unsupported' model to your desktop name / version (as Joe said he had to do), re-launch AFX & regain control of your lights

I documented what I did in an MS word document here
 https://github.com/JStateson/AlienLedTest/blob/main/R4-case-lights.docx

I have an original Dell R4 system with the older motherboard that cannot use the newer CPU chips. I am going to give it to one of my kids after I swap CPUs. I bought a used Area51 (probably r4 case) on ebay and an MSI Raider x299 used motherboard fully loaded.  I have not been able to get the AWCC 4.8.23 app to directly control the LEDs using the Raider.  The best I could do was to preview what  it looks like, then save the theme and reboot after making a minor cable change.  All of the LEDs can be programmed individually but I was not able to get morphing to work.  I could add a digital I/O board or USB DIO adapter to eliminate the cable change requirement, but it is not worth the effort since I cannot get morphing to work.  It is also a PITA to have to power off to get the LEDs to turn on.

 l have a newer AWCC but all it does is control the LEDs on my alienware mouse and keyboard.  It does not see the Area51 case LEDs.

Other project waiting on my liquid cooler:  I plan on delidding the i9-7900x as it runs too hot and putting it in the Raider system.   The i7-7820x will go into the original R4 for my son to use.

Question:  Has anyone ever got the AWCC app and the Area51 LEDs to fully work with non-dell motherboard?

Joe's qwestion stands to the R2-R7 community: who can confirm working case LEDs on a retail mthrbrd

@ Joe ... the reason above I ask R2 owners to chime in, & asked u your FIO board part#'s, is that R2 R3 R4 should all share the same H6HK9 FIO board & if so, success w/ a retail board on R2 SHOULD = success on R3 R4 (I see in your GitHub doc u have H6HK9)

When the old AlienOwners Forum was alive & well, an owner maybe in 2019-2020 who had success w/ an MSI retail board (working case lights) started a 'DataBase' where he asked all past-present-future swappers to chime in w/ their mthrbrd brand/make/model/socket etc & whether no lights, some lights, or all lights worked & yes, the DataBase started to grow w/a small # of 100% successes, almost all were MSI boards inside of R2 cases at the time (because R3-R7 already had new enough hardware not to feel the need to upgrade yet) & that info is now lost  ... HERE on this forum & the older now-locked (read-only) forum were hits & misses mostly by R2 owners. SOME users post onto uTube about their swap & they will or can be asked what happened w/the lights (none/some/all etc). The CONSENSUS at the time was that if u want working lights buy an MSI (& sometimes after power-up u had to remove the side panels off 1st then reattach for the sides to light up as a side effect of the swap), which is why this month is troubling the # of MSI failures across many sockets/chipsets, in fact all posters in this thread have MSI boards w/this issue. WE WANT this issue relegated to the newer R5 R6 R7 3FFYN FIO board & NOT be an issue for R2 R3 R4 so we can at least say well, the Aliens were sick of owner swaps & pulled off their final trick & just shut those final versions down (or had u jumping through ridiculous hoops to get some lights on etc)

Also, your unknown Triad case has a rear service tag &/or express service code u can run through Dell/support to find out what model it is: enter service tag > the new page IDs your model > clik View Product Specs for original as-shipped eqwipment (the front DVD slot means it is not the Chassis2.0 revision on R5 R6 R7, while your H6HK9 FIO board makes it an R2 R3 or R4 case, just go check)

As for better kooling, u can try the 120x48mm Threadripper TFGHM or HR6V4 alienkooler if u swap off the TR4 retention ring & apply your Intel 2066 ring if that's what u have now

Not all, denigration biased systems are ATi.

http://cryphosnegative.blogspot.com/ 

l just noticed that I am not getting the voltage measurements as shown below

Using a voltmeter at the H6HK9 PCB I find the following measurements with Fluke VM and power up Area-51 R4 all OEM.

Hey. MSI retail, MSI R1-R7 alienboard's & your R2 R3 R4 H6HK9 (+R5 R6 R7 3FFYN) FIO yellow Front Panel header all share this MSI pinout

I see you were given a 9-wire harness? You have no Reset Switch, so pins/wires 5/7 are not relevant, while pin #9 'Reserved' doesnt seem relevant either

We might ask why the yellow front panel header is relevant at all to 'none some or all' lights on or off = a mystery

I don't know, I can't fully test because I have an R1 case & just the raw H6HK9 + 3FFYN boards + a 5pin R1 LED strip that approximates a side panel LED, I don't have the matching front top LOGO board (I bought it, I was told it was bunk & issued a refund)

The LOGO board outputs Alienhead Pwr LED (as Pwr On LED 2/4) + the Front Waterfall (Front Panel) Lights pair ... it must do that as an electrical command from the FIO's LOGO port header. IT MAKES SENSE to me if someone said that the Alienhead power on button always turns on (as a product of the JFP1 2/4 Power LED pins, pic above). That Alienhead should light up as JFP1relays Power LED pins +/_ to the LOGO board ... if it does light up, great, if it does not, FOOEY ON THEM

HDD (Activity) LED pins 1/3: these alienboards may have their own onboard mthrbrd HDD LED tell-tale that sparkles w/activity through the rear I/O trim plate, which can explain why the JFP1 HDD LED pins do not output anything

Ok, so in JFP1 diagram, Pwr On + HDD LED explained. Power On-Off Switch 6/8 should work ... so that covers JFP1... how or even why it all relates to Lights on or off in the TRIAD case is a mystery to me

It also makes sense to me that the Front Panel waterfall &/or side panels will not light up, so long as the FIO board is an 'Unknown USB device' & won't show as an HID device as it should

HERE, not u guys out there w/ an R2-R7 TRIAD case, but HERE, I can't test this out using just an FIO board + an LED strip, I'm stuck. MY LED strip ALWAYS lights up with simple Molex 4pin powa, I CAN NOT CHANGE THE COLOR though, because my R2 R3 R4 FIO & R5 R6 R7 FIO will not co-operate w/my retail MSI x99 board. AlienF/X will not work, AlienFXTester.exe does not see them, I just get errors in DEVCMNGR

Top is a success / bottom is a miss; either way, AlienFX app won't work

For H6HK9 I got zip (unknown device) through my USB2.0 headers, but I used the USB3.0 -to- 2.0 adaptor, I got a HIT in DVCMNGR HID DEVICES & in Windows (setting up A-51), but, within 2seconds it went away in HID & became a 'hidden device', like it turns on in HID then turns right off & disapears as a device, ugh

I had zero control over it in AlienF/X & AlienFXTester, nothing showed in the Registry or DVCMNGR

All I have is a single 5pin led STRIP here, I can't replicate the song & dance others do with the full TRIAD case, like taking off a side panel & putting it back on, or jumping 'pins', the routine that has to happen. Besides, AlienFX HAS NO EFFECT, I can't change colors, at least on my eqwivalent of the 5pin side panel LED. If no board is detected, it follows that AlienFX app won't work

I have XJKKD R2 alienboard here in my R1, the KnightFury, so my H6HK9 FIO should work. I JUST bought a new R1, she arrives 2mrrw by FedEx, &, I can not now get to my R2 board, I ran out of space! I have x6 R1 cases & live/dead alien body parts box'd n strewn in my room, I can't move anymore. Like a HOARD. I'll be working w/ my new girl-alien all week. The BEST I could hope for here is to see how the R2 alienboard reacts in DVCMNGR to the H6HK9 FIO, either as an HID device, a USB device, or both, then, what? Take the data & values over to my retail x99 board? BRUTE FORCE the Registry? If I did, would DVCMNGR stop it? Dunno ... give me time

I should've done this a few weeks ago w/ 3FFYN paired to R5 board, now I've run out of testing room. Will report back when I know sumthin

I realize our conversations are made difficult by each of us using our own terms & language to describe what's happening. I've tried to be describe what I saw here. I CAN NOT duplicate what happens in the TRIAD case w/a working set of side panels, logoboard, front panel lights etc. I tried to gain full control &  of the R2 R3 R4 & R5 R6 R7 FIO boards & neither work for reasons I can't explain yet, hah

What I'm saying Joe, is my FIO board outputs an LED color on the FIO red 5pin header, at all times so long as 4pin powa is applied. I can't 'jump' pins & do other things here, simply because the AlienFX app refuses to work to even change a color, so I can't know what your voltage readings mean, but someone WITH your TRIAD case might

Joe, if you have an R4 w/ HJ5Y7 alienboard, you can side-by-side faster than I can what the DVCMNGR & Registry have to say, & what they do. I'm out of this project til next weekend, giving my new girl a splendid makeover, good luck there

Thanks for sharing. Very useful information. Refer this source . 

I loved this content. Thanks for creating it. I’m a big supporter of your stuff.

setup quán cafe

I have read a lot of articles on this topic but This article is really a good article

nhượng quyền cafe