Commander Mini will not control fans based on temp sensors.

[red-ray]

After stopping, it shows Channel IDs of 1F 00 00 00 00 00 00 00 instead of 05 00 00 00 01 00 00 00 on the Link Devices page of SIV.

 

AFAIK this indicates the CLCC firmware has crashed.

 

When adding CLCC support to SIV I found the CLCC firmware is fragile (to say the least) and this is what happened with I "upset it".

 

This may be triggered by the SATA +12 volts power connection being poor and recommend you use a dedicated cable from the PSU just for the CLCC.

[Bob Pilette]

Got my 3rd Commander Mini from Corsair. This one's USB went to 1F in a couple of seconds after I power cycled it every time until I unplugged my AX1500I from it.

 

Now that I have it working, It runs the fans at full speed if I set them to custom in SIV. Custom seems to work in CL4 when I switch the programs. SIV did keep the custom curves I set.

 

I am downloading the latest SIV beta and as soon as that is installed I am going to try to shut down and cold boot the system.

 

If I get the fans to behave in SIV then I'll try the AX1500I in the first port again. If that doesn't work Ill try other ports.

 

I pulled the other minis out of the case so I can't check those at the moment. SIV says the firmware on this one is 1.1.06. Is that the latest POS firmware that Corsair has?

[red-ray]

This one's USB went to 1F in a couple of seconds after I power cycled it every time until I unplugged my AX1500I from it.

1. I recall seeing this if you have the CLCC and a slow USB device connected to the same USB hub. Post [uSB Bus] so I can see the topology.
   
2. Post [Link Fans] so I can see what you have configured.
   
3. My AX1500i is connected to CLCC port 4.
   
4. V1.1.06 is still the latest CLCC firmware as of CL 4.6.0.86.

[Bob Pilette]

Mini Commander was on its own hub by itself until I got pissed and tried using the AX1500i's own USB connection. Of course now SIV will not pick up the AX1500i but CL4 (I tried both programs separately, CL4 is not allowed to startup with windows) does while on its own USB header.I did try it on all CLCC ports including 4 with varying random firmware crash times. CLCC is also on its own SATA Power cable by itself from the power supply on the nearest connector.

 

Current USB Bus:

 

[uSB Bus] <- SIV64X - System Information Viewer V5.18 Beta-04 MONSTER7::Bob

 

Connection Vendor and Device Description Version mA Device Type Device Information

 

[Hub 0 Ports 5] Standard USB OHCI Host Controller V1 Root Hub 500 Powered Hub Individual Switching and Protection

[Port 0.3] Logitech Unifying USB Receiver Keyboard V2.00 Full 98 HID Keyboard Logitech USB Receiver

Logitech Unifying USB Receiver Mouse HID Mouse Instance 1

Logitech Unifying USB Receiver Control Human 0.0 Instance 2

[Port 0.4] Logitech Unifying USB Receiver Keyboard V2.00 Full 98 HID Keyboard Logitech USB Receiver

Logitech Unifying USB Receiver Mouse HID Mouse Instance 1

Logitech Unifying USB Receiver Control Human 0.0 Instance 2

 

[Hub 1 Ports 5] Standard USB EHCI Host Controller V2 Root Hub 500 Powered Hub Ganged Switching Global Protection

[Port 1.2] Canon IJ Scanner V2.00 High 2 Canon MX920 series (10AD55)

Canon IJ Scanner Printer (2) Instance 1

Canon IJ Scanner Printer (2) Instance 2

[Port 1.5] Alcor Micro Multi Flash Reader V2.00 High 100 Bulk SCSI Disk Generic Flash Card Reader/Writer (058F63666438)

 

[Hub 2 Ports 5] Standard USB OHCI Host Controller V1 Root Hub 500 Powered Hub Individual Switching and Protection

[Port 2.1] Micro Chip Technology MCP2200 USB-to-Serial Port V2.00 Full 100 Comms Ctrl 2.1 Microchip Technology Inc. MCP2200 USB Serial Port Emulator (0001850422)

[Port 2.2] Cambridge Silicon Windigo BTM01C2AC Bluetooth Adapter V2.00 Full (31)Connected CSR BlueCore Device

[Port 2.3] American Power Conversion USB UPS V2.00 Full 2 Human 0.0 APC Smart-UPS C 1500 FW:UPS 02.2 / ID=1000 (AS1239217735)

 

[Hub 3 Ports 5] Standard USB EHCI Host Controller V2 Root Hub 500 Powered Hub Ganged Switching Global Protection

 

[Hub 4 Ports 2] Standard USB OHCI Host Controller V1 Root Hub 500 Powered Hub Individual Switching and Protection

 

[Hub 5 Ports 4] Standard USB OHCI Host Controller V1 Root Hub 500 Powered Hub Individual Switching and Protection

[Port 5.3] Corsair Integrated USB Bridge V2.0.0 V2.00 Full 100 Human 0.0 Corsair Memory, Inc. Integrated USB Bridge

[Port 5.4] Corsair Link AX1500i USB Dongle V1.00 (1C02) V1.10 Full 100 Silicon Labs Corsair Link TM USB Dongle (0001)

 

[Hub 6 Ports 4] Standard USB EHCI Host Controller V2 Root Hub 500 Powered Hub Ganged Switching Global Protection

 

[Hub 7 Ports 4] Etron USB XHCI Host Controller V3 Root Hub 900 Powered Hub Ganged Switching Global Protection

 

[Hub 8 Ports 4] Etron USB XHCI Host Controller V3 Root Hub 900 Powered Hub Ganged Switching Global Protection

 

[_][_]Total of 18 USB entities, 9 Root Hubs, 0 Rate Hubs, 0 Ext Hubs and 9 Devices Device names from C:\Program Files\siv\USBDEVS.txt Date 2017-03-17 Version 174 (48,147)

 

[ OK ] [ Copy] [Windows] [Machine] [Link Status][Link Devices][uSB Bus][uSB Disks][ SPD ][HID Bus] [ SMART] [Volumes] [PCI Bus]

 

So CLCC was on Hub 5 alone until the AX1500i was added. Any way to recognize the AX1500i USB along with the CLCC in SIV? Both show up in Link Devices but only the CLCC is showing a device in Link Limits. I updated the AX1500i and my N*** H**+ in Limits but I guess Limits is only for estimating.

[red-ray]

Any way to recognize the AX1500i USB along with the CLCC in SIV?

 

I updated the AX1500i and my N*** H**+ in Limits but I guess Limits is only for estimating.

 

Your post is harder to read that it should be. Try again, use numbers lists and post .PNG images .

 

My AX1500i is connected via a CLCC and SIV reports both.

 

I was pondering adding NZXT HUE+ support, but when the LNP came out I got that instead as it's a sensible HID device unlike the NZXT HUE+. I have no plan to waste money on a NZXT HUE+ just to add support to SIV.

 

[Bob Pilette]

Sorry about that, tried the insert image and didn't feel like hosting the image somewhere. I'm an old salt computer user/tech/engineer who can remember mainframes, mini computers, and all the forms of micro computers so interfaces are not always intuitive for me.

 

Here is the image:

 

SIV does not report the AX1500i if the AX1500i is on its own USB header. Unfortunately, with the latest replacement CLCCs I have this is the only workaround right now. I wonder what corsair changed or what it is about my Gigabyte V2.0 USB headers? Do you happen to know what Corsair is using for internal communication (USB,I2C or some other serial since it is 4 wire)? I'm going to crack open my CLCC with the dead fan port and report what I find.

 

Here is my Link Devices too if it will help:

 

I had a problem with missing cables on my first Hue+ so I got an open box Hue+ to get things going. NZXT finally got some replacements in so I have another Hu+ on the way. So I am going to end up with the HUE+ I have now with 8 LED strips and a HUE with 4 LED strips (if the replacement has everything).

 

Now that I know how to capture your windows and upload them here I can probably be more helpful in testing SIV if you ever want to add the HUE+ to SIV. For now I just use CAM if I want to change the LEDs or if I shut off the power supply and make sure it is closed and exited otherwise (if it doesn't crash first).

 

Well maybe I still need to learn to insert images inline. :p:

[red-ray]

Here is my Link Devices too if it will help:

 

I had a problem with missing cables on my first Hue+ so I got an open box Hue+ to get things going. NZXT finally got some replacements in so I have another Hu+ on the way. So I am going to end up with the HUE+ I have now with 8 LED strips and a HUE with 4 LED strips (if the replacement has everything).

 

I guess the Micro Chip Technology MCP2200 USB-to-Serial Port is the NZXT HUE+, is it?

 

Assuming so then it's exactly the same silly COM port device as the NZXT GRID+ V2 which SIV does support. Given this the I/O would be trivial to add, but we need to deduce the packet contents and protocol semantics as I did for the LNP. There are two options:

1. You do this and provide me with a protocol specification.
   
2. I am provided with a NZXT HUE+ and I deduce it.

The easy option is you get an LNP which is a far more sensible HID device, see http://forum.corsair.com/forums/showthread.php?p=892386

[red-ray]

 

SIV does not report the AX1500i if the AX1500i is on its own USB header.

To C-Link connect AXi PSUs I recommend a CL Mini (CLCC) which is what I use (H100i and H80i also work) as SIV does not as yet support the Corsair Link™ USB Dongle.

 

You do not need to tell me what I specify.

 

1. Unfortunately, with the latest replacement CLCCs I have this is the only workaround right now.
   
2. I wonder what corsair changed or what it is about my Gigabyte V2.0 USB headers?
   
3. Do you happen to know what Corsair is using for internal communication (USB,I2C or some other serial since it is 4 wire)?
   
4. I'm going to crack open my CLCC with the dead fan port and report what I find.

When I ask you to use numbered lists it would be good use them rather than me having to number them.

1. If hardware/firmware is faulty SIV can't be expected to work.
   
2. I have no idea, ask Corsair what they changed. If the CLCC SATA power connection poor you get issues.
   
3. The CLCC C-Link ports are basically I2C.
   
4. Good Luck.

[Bob Pilette]

0.4 Yes, the Hue+ has the same silly com port as the Grid+ V2.

 

0.5 Correction. I only got replacement cables for my now second hue and found it had a dead USB port. Got it as is/used so I am not going to pursue getting it replaced.

 

0.6 So I would now like to help you get the protocol specification for the Hue+. I imagine it is similar to the Grid+ v2 but I don't have one of those since it only has one PWM port. I am not exactly sure what you want or how to get the info, so let me know and I will be glad to help since I already have invested in it.

 

0.9 My bad, I missed the post about the USB Dongle.

 

1. We will see about that. I may have to fix the one I have with the dead fan port since it does work with the AX1500i.

 

2. I have double checked the SATA power connector many times plus put it on its own dedicated cable.

 

3. I2C Figured as much. I've done a lot with serial comms between playing with early MB environmental control and power chairs.

 

4. Oooo I am such a bad boy. To be fair, I used to program 6502/6800/68000 assembly and machine. And I was into Amigas as well.

 

4.1 Progress so far: keywords: ColdFire+, MCF51JU128VLH, 68000 Subset, Software Shhh, Firmware 1.1.6, S19, SRecord, & Decoder.

 

4.2 Next (Done): keywords: Printed readable Decoded and addressed Firmware (all 185 pages), Obtained pertinent manuals.

 

4.3 After that: keywords: Human disassembly (may take a while). Note: No dissasembler/decompiler program available due to instruction set & data sizes.

 

4.4 Dissasembled code will not be published due to copyrights. I would be glad to discuss fair use with a Corsair official especially if they indicate a contract breach from CoolIt documented by a lawyer. I will consider providing programming insights, code fixes in loadable format only (use at your own risk and unsupported probably) (version format depending on Corsair's cooperation). Note: all this will be done only under fair use.

 

4.5 If and only if, I end up with only my code and publicly published code, then I will publish under a freely redistributal license (with a use at your own risk disclaimer) unless Corsair can provide a way that insures proper updating of their product like should have been done in the first place. Note: There is a free code size limited version IDS (Integrated Development Studio) that is available if a releasable source code would fit it.

 

4.6 No promises, but I am retired and disabled so time is on my side and I am disgusted as everyone else around here and the CLCC is the only useable multi PWM fan controller in town unfortunately.

 

4.7 I am not looking for renumeration (money) because it would affect some of my disability income. However, I would not turn down help getting anything that might help from Corsair or anyone else.

 

5. We can only hope that computer environmental monitoring & control improves with time (yea, I got a beef with Gigabyte too). Don't even get me started about BIOSes.

 

Bob

[Bob Pilette]

For those who are interested, I have heavily edited my previous post.

 

Bob

[red-ray]

I am not exactly sure what you want or how to get the info, so let me know and I will be glad to help since I already have invested in it.

 

Basically the sequence of bytes you need to send to get/set the display mode and colours. I guess the COM port speed, but I suspect it's the same as GRID+.

 

I suspect the basic GRID+ and HUE+ low level I/O will be the same. BTW all six of the GRID+ controllers 3-pin voltage :(:.

 

What I did with the LNP was to get CL4 to change things and then used http://www.usblyzer.com/ to see that was in the data packets, see http://forum.corsair.com/forums/showthread.php?p=892386.

 

For GRID+ I found some code on-line, as I recall https://www.reddit.com/r/NZXT/comments/4izk9n/the_nzxt_grid_v2_now_works_on_linux/, maybe I would get all the info from https://github.com/kusti8/hue-plus.

 

I would need HUE+ here to make SIV control it otherwise it would take forever and a day and I would loose interest.