Doridian

I am looking more and more through Corsair's nightmare of a software. Well, the Lighting Node has it's entirely own protocol it seems. Sadly I don't own one so I can't test too much :(

Good news everyone: I have swapped CorsairLink++ over to the cross-platform HidSharp library! (It is also faster than HidLibrary)

red-ray is the maker of SIV. Not CL++. That would be me. I will try swapping to a more cross-platform library if I can get it wrapped up nicely in a .NET DLL. If you know of any existing wrappers, go ahead and poke me with them!

I just wish I could convince someone at Corsair to hand me the firmware source code so I can fix the bugs in there as well, because disassembling it is hard and I am not too experienced in reverse-engineering firmware.

I also added this Mutex to my app already.

Finally got most things to work (missing LEDs and the huge Mains power sensor block as well as control): As we can also deduct from this: The temperature sensor breakage and PSU sensor breakage are a fault of the hardware or firmware (on the Commander Mini).

I have now managed to find out the protocols for AFP and the PSUs. I will try and document it once I have gotten fully through it.

I have done some coding and got to this: https://github.com/Doridian/CorsairLinkPlusPlus This can communicate with the Commander Mini (or other USB things), enumerate devices connected to it etc. However, my problem now is: The AX1200i and AirFlow Pro. They reply totally weird. Both of them give me a 0x00 ID on register 0x00 (ID). One gives me all 0xFF bytes on 0x02 (name), the other 00 00 fe 58 00 00 00 00. The one giving me all 0xFF on 0x02 (name) also gives me all 0xFF on 0x01 (version) and fan count, the other all 0x00.