Jump to content
Corsair Community

Search the Community

Showing results for tags 'lighting node usb issue'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CORSAIR COMMS DEPARTMENT
    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
  • COMMUNITY DISCUSSIONS
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
  • TECHNICAL SUPPORT & CUSTOMER SERVICE
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
  • PRODUCT DISCUSSIONS
    • CORSAIR iCUE
    • Build Hardware
    • Gaming Peripherals
    • Audio Devices
    • Battlestation Hardware: Ambient Lighting, Furniture, etc.
    • CORSAIR Pre-Built Systems
    • CORSAIR Technologies Q&A
  • Alternative Languages
    • Deutscher Support (German Support)
    • French Support
    • Spanish Support
  • LEGACY TOPICS
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service

Categories

  • System Build Inspiration
  • Memory
  • Cases
  • iCUE CONTROLLERS
  • Maximizing Performance
  • Peripherals
  • Storage
  • Liquid Cooling
  • Gaming Mice
  • News and Events
  • How-tos and DIY
  • USB Drives
  • Extreme OC Mods
  • Gaming Keyboards
  • Power Supply Units
  • Gaming Headsets
  • Uncategorized

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

Found 5 results

  1. Hi, I am quite confused by this issue. I just ported over my system from a smaller case and decided to add RGB in the process for fun. I have a STRAFE keyboard and it is successfully detected by the iCue software. I am able to modify colours, etc. from there. From what I can tell in the device logs, the commander pro and the lighting node CORE are successfully being detected by my computer (As in I check the HID that iCue is attempting to use with the HID of the devices that I can see in device manager and they match) but the logs are showing that iCue is failing to connect to them (or at least that is how I am understanding what the iCue logs are telling me). I have 3 SP120 fans and they are spinning and the RGB is lit but they are not showing up in iCue either. I will post the logs below so that hopefully they can give more context. Any help would be greatly appreciated! (Sorry if I posted this in the wrong spot, this is my first time on this forum.) 2020-12-26T15:46:35 W cue.devices.layout: Invalid HW layout 2020-12-26T15:46:35 C cue.manifest: Cannot find "" layout for "STRAFE RGB" 2020-12-26T15:46:35 C cue.devices: Unknown command in NxpPhysicalHidDevice: AbstractCommand::SetDpiBrightnessLevel 2020-12-26T15:46:35 C cue.devices: Unknown command in NxpPhysicalHidDevice: AbstractCommand::GetBacklightEnabled 2020-12-26T15:46:35 C cue.devices: Unknown command in NxpPhysicalHidDevice: AbstractCommand::GetLightingMode 2020-12-26T15:46:35 I cue.sys_info.win: Info: prop=Size class=Win32_DiskDrive returned=false 2020-12-26T15:46:35 W cue.devices.layout: Invalid HW layout 2020-12-26T15:46:35 C cue.manifest: Cannot find "" layout for "STRAFE RGB" 2020-12-26T15:46:35 I cue.lightings.direct_player: Started lighting worker in 0x980 2020-12-26T15:46:35 I cue.devices: Device insertion processing complete for STRAFE RGB (vid=1b1c, pid=1b20) 2020-12-26T15:46:35 I cue.dev.conn_proxy: Device does not support multiple connection types 2020-12-26T15:46:35 I cue.profiles.mappings_actualizer: Use volume wheel workaround for "STRAFE RGB" 2020-12-26T15:46:35 I cue.sys_info.win: Info: prop=Caption class=Win32_PnpEntity returned=false 2020-12-26T15:46:35 I cue.sys_info.win: Info: prop=DeviceID class=Win32_PnpEntity returned=false 2020-12-26T15:46:35 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2020-12-26T15:46:35 I cue.firmware.index: "STRAFE RGB" firmware update, expected version: 3.8 same version found, on device: bootloader: 0.14 firmware: 3.8 2020-12-26T15:46:36 I cue.sys_info.win: Info: prop=Name class=Win32_PnpEntity returned=false 2020-12-26T15:46:36 I cue.sys_info.win: Info: prop=Manufacturer class=Win32_PnpEntity returned=false 2020-12-26T15:46:36 I cue.sys_info.win: Info: prop=Service class=Win32_PnpEntity returned=false 2020-12-26T15:46:36 I cue.sdk.device_watcher: Start prepare WorkingStateState 2020-12-26T15:46:36 I cue.sdk.device_watcher: Finish prepare WorkingStateState 2020-12-26T15:46:36 C cue.devices: Unknown command in NxpPhysicalHidDevice: AbstractCommand::GetSensors 2020-12-26T15:46:36 I cue.lib.datacollection.engine.mixpanelengine: Data was written to mixpanel successfully, queryId: "" 2020-12-26T15:46:50 I cue.core.init_ui: Starting UI. 2020-12-26T15:46:50 W Broken filename passed to function 2020-12-26T15:46:52 W qrc:/qml/ui/MainWindow.qml:85: TypeError: Cannot read property 'borderlessWindowController' of null 2020-12-26T15:46:52 W qrc:/qml/ui/MainWindow.qml:86: TypeError: Cannot read property 'borderlessWindowController' of null 2020-12-26T15:46:52 W MainWindow_QMLTYPE_875(0x2c252600) must be a top level window. 2020-12-26T15:46:52 W MainWindow_QMLTYPE_875(0x2c252600) must be a top level window. 2020-12-26T15:46:52 W Model size of -1 is less than 0 2020-12-26T15:46:52 W libpng warning: iCCP: known incorrect sRGB profile 2020-12-26T15:46:52 W libpng warning: iCCP: known incorrect sRGB profile 2020-12-26T15:46:52 W libpng warning: iCCP: known incorrect sRGB profile 2020-12-26T15:46:52 W qrc:/qml/ui/HeadsetControls.qml:79:4: QML RowLayout: Cannot anchor to an item that isn't a parent or sibling. 2020-12-26T15:46:52 W qrc:/qml/ui/TouchscreenElementsInfo.qml:89:2: QML ColumnLayout: Possible anchor loop detected on vertical anchor. 2020-12-26T15:46:52 W Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. 2020-12-26T15:46:52 W libpng warning: iCCP: known incorrect sRGB profile 2020-12-26T15:46:52 W libpng warning: iCCP: known incorrect sRGB profile 2020-12-26T15:46:52 W qrc:/qml/help/HintManager.qml:132: TypeError: Cannot read property 'parent' of null 2020-12-26T15:46:52 W qrc:/qml/help/HintManager.qml:132: TypeError: Cannot read property 'parent' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:132: TypeError: Cannot read property 'parent' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:132: TypeError: Cannot read property 'parent' of null 2020-12-26T15:46:53 W qrc:/qml/ui/HeadsetControls.qml:387: ReferenceError: surround is not defined 2020-12-26T15:46:53 W qrc:/qml/ui/HeadsetControls.qml:377: ReferenceError: surround is not defined 2020-12-26T15:46:53 W qrc:/qml/collection/AccordionItem.qml:154: TypeError: Cannot read property 'containsMouse' of undefined 2020-12-26T15:46:53 W qrc:/qml/collection/AccordionItem.qml:163: TypeError: Cannot read property 'containsMouse' of undefined 2020-12-26T15:46:53 W qrc:/qml/ui/accordion/DialControlAccordionItem.qml:178: TypeError: Cannot read property 'y' of null 2020-12-26T15:46:53 W qrc:/qml/ui/accordion/ButtonsLibraryAccordionItem.qml:373:6: Unable to assign [undefined] to QStringList 2020-12-26T15:46:53 W qrc:/qml/ui/assignment/AssignmentView.qml:738: TypeError: Cannot read property 'width' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:348: TypeError: Cannot read property 'arrowSide' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:356: TypeError: Cannot read property 'arrowSide' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:364: TypeError: Cannot read property 'arrowSide' of null 2020-12-26T15:46:53 W qrc:/qml/help/HintManager.qml:372: TypeError: Cannot read property 'arrowSide' of null 2020-12-26T15:47:39 I cue.dev.hidenumerator: Found device VID 6940 PID 3088 Usage Page 132 Usage 82 2020-12-26T15:47:39 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:47:39 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:47:39 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:47:39 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:47:39 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:47:39 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:47:39 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:47:39 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c10\\6&25281d2f&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "82")("hid-usagepage", "132")("model-name", "Commander PRO")("usb-pid", "3088")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:47:39 I cue.devices: Device vid=1b1c pid=c10 ignored by HidDeviceEnumerator 2020-12-26T15:48:02 I cue.devices: Device vid=1b1c pid=c1a ignored by HidDeviceEnumerator 2020-12-26T15:48:02 I cue.dev.hidenumerator: Found device VID 6940 PID 3098 Usage Page 65472 Usage 1 2020-12-26T15:48:02 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:48:02 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:48:02 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:48:02 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:48:02 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:48:02 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:48:02 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) not found. 2020-12-26T15:48:02 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1a\\7&1d7eb924&4&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65472")("model-name", "CORSAIR Lighting Node CORE")("usb-pid", "3098")("usb-vid", "6940")("vendor", "Corsair")) 2020-12-26T15:48:11 I cue.devices.nxp: Buffer apply for Blue failed. request timed out for STRAFE RGB 2020-12-26T15:48:11 I cue.devices.nxp: Buffer write, 1. failed. request timed out for STRAFE RGB 2020-12-26T15:48:11 I cue.devices.nxp: Buffer write, 1. failed. request timed out for STRAFE RGB 2020-12-26T15:48:11 I cue.devices.nxp: Buffer write, 1. failed. request timed out for STRAFE RGB 2020-12-26T15:48:20 I cue.devices.nxp: Buffer write, 1. failed. request timed out for STRAFE RGB 2020-12-26T15:48:50 W qrc:/qml/collection/ColorPicker.qml:42: TypeError: Cannot call method 'updateCurrentColor' of null 2020-12-26T15:48:50 W qrc:/qml/collection/ColorPicker.qml:48: TypeError: Cannot call method 'updateCurrentColor' of null 2020-12-26T15:48:51 W Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. 2020-12-26T15:48:51 W qrc:/qml/ui/settings/DeviceSettings.qml:239:7: Unable to assign [undefined] to double 2020-12-26T15:48:51 W qrc:/qml/delegate/TabViewTabDelegate.qml:21: TypeError: Cannot read property 'top' of null 2020-12-26T15:48:54 I cue.clinkclient: Error connecting to service: 2 2020-12-26T15:48:54 W cue.sensors.system_info: Failed to get device list. code = 5 "Failed to send device list request"
  2. This is my first post here as I've started to run into a couple of issues with iCue over the past week. I've been running it for roughly 8 months now, and after changing the configurations of my fans/LEDs strips multiple times, my build is done, but now my Lighting Node Pro is not being detected as of yesterday and after trying to repair/uninstall iCue today now my Commander Pro is not being detected either. When Repairing it says "An installation package for the product cannot be found. Try installing using a valid copy of the installation package '28.70_release.msi'." I downloaded this directly from the Corsair website today. This is not the first time I've had trouble with this. Updating to the newest 3.28.70 it took me a couple of tries, as before I knew there was an update I tried to uninstall because I thought there was a bug or error. The Dashboard no longer displayed my "System Info". So after failing the uninstalls normally and doing some light research I found out I could download the newest update from the website and repair iCue, I simply tried to do an uninstall so I could have a fresh install and this failed locking me out from updating/repairing/uninstalling, so I reset my PC, then tried to repair, which worked. New 3.28.70 running. My K70, ST100, Vengeance RGB, Lighting Node Pro and Commander Pro were all there, with the new update, but still no "System Info+" available in the Dashboard still. Unrelated to my iCue problems I reinstalled my CPU cooler, dusted out my case, etc. Put my PC back together to make sure everything is right, all 6 of my LL120's light up, and my 4 ambient strips too, everything is running until I got to iCue and seen that my LNP was not being detected, its plugged into my Commander Pro and I only have 1 USB 2.0 header on my mobo. The LNP was detected when I unplugged my Commander Pro from that header and put in the LNP. I tried both ports on the Commander Pro and tried both orientations, far left and far right as it can fit in both ways. Now today trying to do a fresh install/repair, my Commander Pro is not being detected and I'm receiving that error message. Any help would be appreciated. Sorry for the long write up.
  3. So recent got The LL120 RGB seris fan kit with teh lighting node pro. Im having alot of trouble with the computer not seeing the node pro. I have one usb 2.0 header on my Asus crosshair v hero. If i plug it directly into the header the computer will see it and i can customzie it. but i bought a usb 2.0 header splitter as i need to have the front case usb and also the Corsair h100i v2 plugged in. When plugged into the splitter the usb and the aio get seen but not light node pro. Any ideas or suggestion would be helpful
  4. PREVIOUSLY READ POSTS (I won't let @DevBiker down): https://forum.corsair.com/v3/showthread.php?p=940351&p=940351 https://forum.corsair.com/v3/showthread.php?t=178995 Prerequisites: Turn off fast startup in BIOS?: YES Turn off fast startup in WINDOWS?: YES DISABLE HXCI in BIOS? YES Does USBDeView show NoPRO connected with a green dot? YES NoPro Firmware wipe? YES Complete iCUE reinstall? YES Relevant Information: MOBO: ROG Crosshair Hero VI (ONE usb 2.0 header) Windows Version: 10 Home, Build 1909 iCUE Software Version: 3.23.66 Corsair Products: H115i PRO Lighting Node PRO x3 LL120 RGB (connected to NoPRO) As previously stated, my current MOBO only has ONE USB2.0 internal header. Because of this, I need to use a USB2.0 Extender (That is the one I purchased). The H115i PRO IS detected by iCUE when either directly connected to the MOBO or the extender. The NoPRO on the other hand is detected by USBDeView when either directly connected to the MOBO or the extender, but fails to be detected by the iCUE software when connected to the extender. I'm at the point of believing that this is an oversight in iCUE software... Any more information/operations that you all would like me to try, I would gladly give a shot.
  5. I just bought the Lighting Node PRO and after I connected all the cables and boot up my system I noticed no light:wtfman: then after long troubleshooting I figured out if I power on my system and turning it off again then i have to open the case unplug the USB cable from the Node and then plug it back in and then power my system on again then the lights works:confused: I've tested both my USB 2.0 connection on my motherboard I get the same issue, I have tested with other devices working without problems so the port seems to be working without any issues. I have to do this every day because I'm cutting the power to the whole set up every time I'm going to bed. Does anyone have any idea what the issue can be? --------------UPDATE----------------- here is a small update on my issue I bought the commander Pro because I need it for a future project in my build and because I was tired of the issue with the usb on the Lighting Node PRO and I thought if it was not working I can return it because then it must be something with my motherboard, but now my issue it's gone, so I think it must be the Lighting Node PRO itself that is the issue. I'm still waiting on response from Corsair support just to hear what they have to say on the issue, I also updated the support ticket with the new information.
×
×
  • Create New...