Jump to content

Stavos914

Members
  • Posts

    15
  • Joined

Reputation

10 Good
  1. I just connected a mini USB cable directly to the motherboard I/O instead of using the internal USB cable. I could not find any other solution to this fix. I'm lucky in that I have an open air case where I can do this without having to run a USB cable out of my case in order to do that. Anyone else would have to run a mini USB cable from the node pro inside the case, to the outside of the case in order to connect to the motherboard I/O USB port. I have updated the node pro firmware through the iCue program with no luck. There just seems to be a compatibility issue with the node pros and some motherboards, or some BIOS setting that nobody seems to know of. Kinda sucks but they do look cool once you get them working the right way.
  2. No, you are replacing that cable with a mini USB cable like this https://smile.amazon.com/AmazonBasics-USB-2-0-Cable-Male/dp/B00NH13S44/ref=sr_1_2_sspa?crid=FR4F5DOI0YDK&keywords=mini+usb+cable&qid=1562084403&s=gateway&sprefix=mini+usb+%2Caps%2C146&sr=8-2-spons&psc=1 This cable would go from your node to the back of your motherboard where you have your mouse, keyboard, and audio connected instead of using the cable with multiple pins that came with the fans.
  3. There is no adapter needed. It is just running a mini USB cable from the node to a USB port on the MB. Search your old electronics drawer for one.
  4. Yes, just connecting to the I/O USB port solved this for me. As you can see from the thread overall, I could not find any other way to fix this issue. Still don't know if it is due to a bad cable that Corsair provided, bad MB USB port, bad BIOS settings, or a combination. I am more than happy with this fix since nobody else was able to offer a better way to fix this.
  5. I can confidently say that hooking up the NoPro to the I/O USB port fixed the issue for me. I could care less about not using the MB USB port at this point. This is an acceptable fix for me!
  6. HOLY. ****! I should have listened to you earlier dude. I just plugged the NoPro to the I/O with a normal mini USB cable and that seems to have fixed the issue. I've already tried it three times with the fan lights coming back on every time. I'll keep shutting it down every so often to confirm, and turn it off for the night to see if they come back on in the morning, but I think this has been the issue all along. I don't know if this is a bad cable or a bad port yet though (or compatibility issue?). You folks might understand the specs required much better than I can. Is the cable provided by Corsair compatible with my USB port on my MB? Thanks again, and very sorry I didn't try all the suggestions you gave me right away. I guess I still tried them all but this one was way late, haha!
  7. I have Windows Fast Startup disabled and I have Fast Boot turned off in the BIOS as well. I have this and XHCI hand off enabled per a previous forum post I found that also showed me how to reset the NoPro.
  8. I am overclocked currently. I suppose it could be messing it up, but why does it work when I reset the node? If it is the overclocking, I would just live with it since I prefer being OC'ed. The lights don't even turn back on anymore when I restart a second time before logging in, as I described in my original post, so something has changed somehow. The only way to make the node activate now, if I shut down, is to disconnect the USB and power cable from the node then re-plug them back in. This turns the node back on without fail so far, as if nothing had changed. I have just been leaving my computer on all the time now so I don't have to deal with all this crap. The weird part is that I have no problem putting my PC through a restart and logging in. The fan lights stay on while going through a restart, with what I can only describe as the "standby" lighting pattern, which consists of each fan being lit up one by one with the "color wave" lighting pattern. Once I log in, the color pattern goes back to the settings I have set up. It is only when I actually shut down the machine that things just go to ****. If anyone knows why there is this discrepancy between shutting down and restarting, please let me know. I've given up trying to solve this issue but I'm always up for suggestions. I'm still pretty bummed that there is no solution to this problem.
  9. DevBiker, I've disabled Legacy USB Support. I'll let you know if that has any effect. I tried leaving the computer on all night and day so I did't have to worry about the lights going out and it seemed to be going fine, until I checked back on it just recently and saw that the screen was black, the computer still running, the fan lights looked like they were doing their standby lighting effect (what they do when I do a real restart until I log back in). Could not do anything but hard reset. No idea what that was, but when I did that, the fan lights refused to turn on, no matter how many times I shut down before I logged in. I had to disconnect the NoPro cables, press and hold the reset button on the NoPro, and reconnect the cables. Lights are back on now. However, my Vengeance RAM is not being recognized on the iCue program anymore, but they still light up, so whatever. Welcome to my hell... Gizmo, I'm not sure how to turn Hardware Lighting on or off. There is not an option to turn that on or off, its just there. I did turn on the second channel and turned it off again but I'm not sure if that does anything. Additionally, I would not have this option if the NoPro in iCue is not being detected, which is my main issue when the lights don't turn on.
  10. I checked the BIOS and "Enable Legacy USB Support" is enabled. Well thanks for trying at least. Ill keep an eye on this an see if anyone else offers suggestions. Ill get around to submitting a ticket later.
  11. Thanks for the quick response! I hope you're able to see my system specs, by the way. I filled it out on my profile. Let me know if you don't see them. I do have Windows Fast Startup disabled and I do have Fast Boot turned off in the BIOS as well. I have this and XHCI hand off enabled per a previous forum post I found that also showed me how to reset the NoPro. Then I ask you this, because you definitely know more about computer BIOS settings than I do, can you think of a BIOS setting that changes after a second bootup from Shutdown state? Because I can look at the MB handbook BIOS settings, but they are almost gibberish to me lol. I have an Asus Maximus VIII Formula, by the way.
  12. I should note that when the lights do not come on, the NoPro is not visible in the iCue program, even though I see it on USBDeview as disabled. When the lights are on, it is visible. It is directly connected to the motherboard. Its going into an 1112 USB port. I do not have any splitters between the NoPro and the MB. Can it be a bad port if one time it works and the next it doesn't? Is this the right port to plug this into? I did swap where the SATA power cables of the fan splitter and the NoPro connected so that the fan splitter was closest to the power supply (they are connected to the same sata cable, as well as my HDD). That seemed to have worse results. The lights just were not turning on at all after a restart when I did that. I flipped them back so that the NoPro was closer to the PS and the lights turned on as they did before. Do you think I should have a dedicated SATA power cable just for the NoPro? If they don't turn on and I don't restart it before logging in, I can usually disconnect the USB and sata cable from the NoPro and reset it in some way. Either by pressing and holding the reset button on the NoPro or just unplug and replug the mini USB going into the NoPro and the sata cable connecting to the power supply cable. I really don't like doing this because I have to take the back panel of my case off every time. When I see it enabled on USBDeview, I can disable and enable it all I want. Can it be some RegEdit settings? I'll try connecting the mini USB to the I/O soon. I just don't know what to do at this point. I'm at my limit with this crap. I have never experienced hardware this dodgy before in my life. What can be stopping the NoPro from initializing SOMETIMES!? Thanks
  13. Hi DevBiker, All it took was for me to shut the PC down and start it back up for the lights to not turn on. It does look a USB initialization problem. I have downloaded USBDeView and can confirm that the Node is not enabled. I see it on the list but does not have a green light next to it. What can I do with this info? I should also ask, can this be a bad Node PRO? Should I get a replacement? Thanks for the response.
  14. I bought the LL 120 fan kit with the Lighting Node PRO about a month ago. I have not seen such a glitchy set of hardware in my life. I have had so many issues with the node not turning the fan LED's on. This seems to happen after I shut down the computer for a little while (shutdown at night, turn on the next morning or evening). I have tried all the suggestions I have found to make it better. I have gone into the BIOS and turned Fast Boot off and turned XHCI Hand-off on. I have disconnected the power cables and pressed the reset button on the node until the fans came back on. These were the early struggles. It used to be a crapshoot. Sometimes the lights did turn on on the first startup try, and sometimes they didn't. That is not the case now, and I do not know what has changed. I now seem to be at a constant point where, after the PC has been shutdown over night, I turn on the PC and the fan lights do not turn on. I then re-shutdown, before I log in to my Microsoft account, then restart my PC. This causes the fan lights to turn on. So yes, I am at the point where I have to turn on my PC, then right after, turn my PC back off so that I can turn it back on so the fan lights work. Does this sound as ridiculous as I think it is? Does anybody know why this happens!? Please help if you think you know why I am having this issue. I would like to have the fan lights come on after the first time I start my PC. I am currently using the iCue software to control my lighting node, keyboard, and RAM. It is so disappointing to have this issue considering how cool the lighting effects are with these fans, something I have seen over and over again regarding issues with these fan kits.
×
×
  • Create New...