Corsair RMi, HXi, AXi PSU Statistics - CyanLabs's fork

Followers

This topic contains 323 posts with an estimated read time of 154 minutes. A summary containing the most significant posts is available with an estimated read time of 1 minute.

View summary

Reply to this topic

Prev
1
2
3
4
5
6
7
8
9
10
11
Next
Page 6 of 13

July 20, 20213 yr

Yes, my bad, now I can see the PR on github.

Quote

Replies 322
Views 58.1k
Created 5 yr5 yr
Last Reply Apr 17Apr 17

Popular Days

Posted Images

July 21, 20213 yr

hi, Im adding a new image so you can update the github one.

Quote

3 months later...

October 22, 20213 yr

Hello all, curious the status of this plugin.

Noticed my AX1500i isn't being recognized. Anyone else have an AX1500i working?

Quote

2 months later...

January 15, 20223 yr

I am having problems with this plugin. Everything seems to work except home assistant cant reach the status.php page. And if I open in a new incognito mode the

http://10.0.0.40/plugins/corsairpsu/status.php

page it redirects me to /login. I think this is the problem. There is no basic auth popup just a redirect to the unraid login. did anoyne else run into this?

If I login to unraid and open the status page I get the JSON response properly

Edited January 15, 20223 yr by BoKKeR

Quote

January 15, 20223 yr

Author

1 hour ago, BoKKeR said:
I am having problems with this plugin. Everything seems to work except home assistant cant reach the status.php page. And if I open in a new incognito mode the
http://10.0.0.40/plugins/corsairpsu/status.php
page it redirects me to /login. I think this is the problem. There is no basic auth popup just a redirect to the unraid login. did anoyne else run into this?

If I login to unraid and open the status page I get the JSON response properly

Yes because unraid removed basic auth and now uses a form auth, this is mentioned a few times in this thread.

Quote

2 weeks later...

January 23, 20223 yr

Can we get an update on the progress für ax1600i for example? Is there even someone investigating rn?

Quote

January 23, 20223 yr

Author

There is no update, nothing is being worked on, this uses a completely different protocol so isn't supported. someone would have to make a binary (cli application) that interfaces with the AX1600i

Quote

5 weeks later...

February 22, 20223 yr

Hello all,

I'm a happy user of this plugin, and got a HXi series psu because of it.
But I have some trouble with getting the data into Home Assistant Core dashboard.
I have figured out how to edit the configuration.yaml and the sensor entities show up, but the data is unavailable. (HX750i and unRAID 6.9.2)

I'm new to home assistant, but I think the problem is the basic authentication?

Quote

4 weeks later...

March 19, 20223 yr

On 1/22/2020 at 6:54 AM, Fma965 said:

Please can you provide some screenshots, info on your usb devices etc.

Same boat here, AX1500i. Unraid 6.10.0-rc3

root@CRYZEN:~# lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0b05:1984 ASUSTek Computer, Inc. USB Audio
Bus 005 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 1b1c:1c02 Corsair Corsair Link TM USB Dongle
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
root@CRYZEN:~#

root@CRYZEN:/sys/bus/usb/drivers# ls -al
total 0
drwxr-xr-x 8 root root 0 Mar 19 04:13 ./
drwxr-xr-x 4 root root 0 Mar 19 04:13 ../
drwxr-xr-x 2 root root 0 Mar 19 04:13 hub/
drwxr-xr-x 2 root root 0 Mar 19 04:13 synaptics_usb/
drwxr-xr-x 2 root root 0 Mar 19 04:13 usb/
drwxr-xr-x 2 root root 0 Mar 19 04:13 usb-storage/
drwxr-xr-x 2 root root 0 Mar 19 04:13 usbfs/
drwxr-xr-x 2 root root 0 Mar 19 04:13 usbhid/
root@CRYZEN:/sys/bus/usb/drivers# cd hub/
root@CRYZEN:/sys/bus/usb/drivers/hub# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
lrwxrwxrwx 1 root root 0 Mar 19 09:08 1-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:01.0/0000:23:00.0/usb1/1-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 10-0:1.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb10/10-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 2-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:01.0/0000:23:00.0/usb2/2-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 3-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb3/3-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 3-5:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb3/3-5/3-5:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 4-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb4/4-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 5-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/5-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 5-1:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/5-1/5-1:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 6-0:1.0 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb6/6-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 7-0:1.0 -> ../../../../devices/pci0000:20/0000:20:08.1/0000:33:00.3/usb7/7-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 8-0:1.0 -> ../../../../devices/pci0000:20/0000:20:08.1/0000:33:00.3/usb8/8-0:1.0/
lrwxrwxrwx 1 root root 0 Mar 19 09:08 9-0:1.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb9/9-0:1.0/
--w------- 1 root root 4096 Mar 19 09:08 bind
lrwxrwxrwx 1 root root 0 Mar 19 09:08 module -> ../../../../module/usbcore/
-rw-r--r-- 1 root root 4096 Mar 19 09:08 new_id
-rw-r--r-- 1 root root 4096 Mar 19 09:08 remove_id
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:08 unbind
root@CRYZEN:/sys/bus/usb/drivers/hub# cd ../synaptics_usb/
root@CRYZEN:/sys/bus/usb/drivers/synaptics_usb# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
--w------- 1 root root 4096 Mar 19 09:11 bind
-rw-r--r-- 1 root root 4096 Mar 19 09:11 new_id
-rw-r--r-- 1 root root 4096 Mar 19 09:11 remove_id
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:11 unbind
root@CRYZEN:/sys/bus/usb/drivers/synaptics_usb# cd ../usb
root@CRYZEN:/sys/bus/usb/drivers/usb# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
lrwxrwxrwx 1 root root 0 Mar 19 09:11 10-1 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb10/10-1/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 3-5 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb3/3-5/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 3-5.1 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb3/3-5/3-5.1/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 5-1 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/5-1/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 5-6 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/5-6/
--w------- 1 root root 4096 Mar 19 09:11 bind
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:11 unbind
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb1 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:01.0/0000:23:00.0/usb1/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb10 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb10/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb2 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:01.0/0000:23:00.0/usb2/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb3 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb3/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb4 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.1/usb4/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb5 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb6 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb6/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb7 -> ../../../../devices/pci0000:20/0000:20:08.1/0000:33:00.3/usb7/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb8 -> ../../../../devices/pci0000:20/0000:20:08.1/0000:33:00.3/usb8/
lrwxrwxrwx 1 root root 0 Mar 19 09:11 usb9 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb9/
root@CRYZEN:/sys/bus/usb/drivers/usb# cd ../usb-storage/
root@CRYZEN:/sys/bus/usb/drivers/usb-storage# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
lrwxrwxrwx 1 root root 0 Mar 19 09:12 10-1:1.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb10/10-1/10-1:1.0/
--w------- 1 root root 4096 Mar 19 09:12 bind
lrwxrwxrwx 1 root root 0 Mar 19 09:12 module -> ../../../../module/usb_storage/
-rw-r--r-- 1 root root 4096 Mar 19 09:12 new_id
-rw-r--r-- 1 root root 4096 Mar 19 09:12 remove_id
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:12 unbind
root@CRYZEN:/sys/bus/usb/drivers/usb-storage# cd ../usbfs/
root@CRYZEN:/sys/bus/usb/drivers/usbfs# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
--w------- 1 root root 4096 Mar 19 09:13 bind
lrwxrwxrwx 1 root root 0 Mar 19 09:13 module -> ../../../../module/usbcore/
-rw-r--r-- 1 root root 4096 Mar 19 09:13 new_id
-rw-r--r-- 1 root root 4096 Mar 19 09:13 remove_id
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:13 unbind
root@CRYZEN:/sys/bus/usb/drivers/usbfs# cd ../usbhid/
root@CRYZEN:/sys/bus/usb/drivers/usbhid# ls -al
total 0
drwxr-xr-x 2 root root 0 Mar 19 04:13 ./
drwxr-xr-x 8 root root 0 Mar 19 04:13 ../
lrwxrwxrwx 1 root root 0 Mar 19 09:13 5-6:1.7 -> ../../../../devices/pci0000:20/0000:20:01.1/0000:21:00.0/0000:22:08.0/0000:2a:00.3/usb5/5-6/5-6:1.7/
--w------- 1 root root 4096 Mar 19 09:13 bind
lrwxrwxrwx 1 root root 0 Mar 19 09:13 module -> ../../../../module/usbhid/
-rw-r--r-- 1 root root 4096 Mar 19 09:13 new_id
-rw-r--r-- 1 root root 4096 Mar 19 09:13 remove_id
--w------- 1 root root 4096 Mar 19 04:13 uevent
--w------- 1 root root 4096 Mar 19 09:13 unbind
root@CRYZEN:/sys/bus/usb/drivers/usbhid# ^C
root@CRYZEN:/sys/bus/usb/drivers/usbhid#

Quote

2 months later...

June 18, 20223 yr

Author

This has been mentioned multiple times but i'll mention it again.

1. Unraid now uses form auth not basic auth therefore the direct access to the json wont work

2. PSU's that are not supported use a completely different protocol, if a CLI exists for slackware/linux that reads the data maybe i'll consider adding it

Quote

June 18, 20223 yr

I was going to reply back with https://forums.unraid.net/topic/86715-corsair-rmi-hxi-axi-psu-statistics-cyanlabss-fork/#comment-806215, but then noticed that you actually wrote that.

As a side note though, should any plugin implement hacks in the plugin itself etc to bypass security on the server that plugin would be rather instantly blacklisted. Mods / scripts in the forum to do that are however acceptable.

Quote

June 18, 20223 yr

Author

I've been out of the loop for a while, does unraid provide a bearer token auth method yet... you know like every single other appliance ever!

sidenote, if you want PSU stats in Home Assistant use the NetData docker container works great. (assuming your PSU is supported)

image.png.66229df3481524ecb86f99b1593cc8b9.png

Quote

June 18, 20223 yr

Author

22 minutes ago, Squid said:

I was going to reply back with https://forums.unraid.net/topic/86715-corsair-rmi-hxi-axi-psu-statistics-cyanlabss-fork/#comment-806215, but then noticed that you actually wrote that.

Also, as a side note that code doesn't work any more, last time i tested this code did.

It also technically doesn't have any security implications as all it does is disables auth on that page

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

# Add Un-Authenticated access to Unraid 6.10-RC1+ for Status.php (Corsair Plugin)
while [ ! -f /var/run/nginx.pid ]
do
  sleep 2 # or less like 0.2
done

echo -e "# Fma965 Un-Authenticated Access\nlocation ~ /plugins\/corsairpsu\/status.php {\nallow all;\ninclude fastcgi_params;\n}\n\n# End Fma965 Un-Authenticated Access\n\n$(cat /etc/nginx/conf.d/locations.conf)" > /etc/nginx/conf.d/locations.conf;
nginx -s reload
# End Nginx Basic Auth Patch

Quote

2 months later...

September 8, 20222 yr

Hi,

i bought a HX 1000i it is visible in systemdevices:

Bus 001 Device 002 Port 1-1 ID 1b1c:1c1e Corsair HX1000i Power Supply

But there are no values in the plugin on the dashboard.

In the plugin settings everythings on default.

can anyone help me........,please?

Quote

1 month later...

October 10, 20222 yr

The rest api could be deployed as a container so home assistant can access the data. If anyone else is interested I might fix it over the coming weekend.

Edited October 10, 20222 yr by BoKKeR

Quote

October 12, 20222 yr

On 10/10/2022 at 3:28 AM, BoKKeR said:

The rest api could be deployed as a container so home assistant can access the data. If anyone else is interested I might fix it over the coming weekend.

yes please

Quote

3 weeks later...

October 28, 20222 yr

On 10/12/2022 at 3:56 AM, Poncho's Vault said:

yes please

I have looked at it. The easy way is by getting rid of the plugin thus there would be no integration in unraid, The docker container would work as an API for home assistant only. There might be a way to rewrite the plugin to listen for the port of the docker container, but it all feels like too much work for such a niche feature.

Quote

October 28, 20222 yr

Author

9 minutes ago, BoKKeR said:

I have looked at it. The easy way is by getting rid of the plugin thus there would be no integration in unraid, The docker container would work as an API for home assistant only. There might be a way to rewrite the plugin to listen for the port of the docker container, but it all feels like too much work for such a niche feature.

This would be pointless, netdata docker container already detects the PSUs, this plugin is purely for the integration in the dashboard at this point

There is a super easy way though, plugin write to a text file, docker container read the text file, output to HA but again not really needed since netdata can do what you want.

Edited October 28, 20222 yr by Fma965

Quote

1 month later...

December 18, 20222 yr

On 9/8/2022 at 9:41 AM, chico11 said:

Hi,

i bought a HX 1000i it is visible in systemdevices:

Bus 001 Device 002 Port 1-1 ID 1b1c:1c1e Corsair HX1000i Power Supply

But there are no values in the plugin on the dashboard.

In the plugin settings everythings on default.

can anyone help me........,please?

I have the exact same issue. HX1000i not showing up on the dashboard.

system devices: Bus 001 Device 003 Port 1-10ID 1b1c:1c1e Corsair HX1000i Power Supply.

Anyone know how to get it working? What makes it work for some but not others?

Edit: Might be worth noting that I have the 2021 model of the HX1000i. Perhaps the device ID needs to be added to the plugin in order to work?

Edited December 19, 20222 yr by Olitrolli
Extra info

Quote

December 21, 20222 yr

On 12/18/2022 at 9:27 PM, Olitrolli said:

I have the exact same issue. HX1000i not showing up on the dashboard.

system devices: Bus 001 Device 003 Port 1-10ID 1b1c:1c1e Corsair HX1000i Power Supply.

Anyone know how to get it working? What makes it work for some but not others?

Edit: Might be worth noting that I have the 2021 model of the HX1000i. Perhaps the device ID needs to be added to the plugin in order to work?

The same issue - new HX1000i model 2022. Recognised as "Bus 003 Device 002 Port 3-2 ID 1b1c:1c1e Corsair HX1000i Power Supply" but no data in the plugin.

Quote

1 month later...

January 24, 20232 yr

Author

Guys you can all keep reporting the issues with certain PSU's but if the underlying binary, CorsairRMI and cpsumoncli don't detect it then it's not going to work

Run these commands via SSH/Terminal

/usr/local/bin/corsairmi

/usr/local/bin/cpsumon/cpsumoncli TTYNumber

If they give response then i can probably update the plugin, otherwise it will need a new binary

Edited January 24, 20232 yr by Fma965

Quote

January 26, 20232 yr

On 1/24/2023 at 9:35 PM, Fma965 said:
Guys you can all keep reporting the issues with certain PSU's but if the underlying binary, CorsairRMI and cpsumoncli don't detect it then it's not going to work

Run these commands via SSH/Terminal
/usr/local/bin/corsairmi
OR
/usr/local/bin/cpsumon/cpsumoncli TTYNumber
If they give response then i can probably update the plugin, otherwise it will need a new binary

Thanks for the looking into this!

Here is the output from running the commands in the terminal:

root@Tower:~# /usr/local/bin/corsairmi
No compatible devices found.
root@Tower:~# /usr/local/bin/cpsumon/cpsumoncli TTYNumber
Corsair AXi Series PSU Monitor
(c) 2014 Andras Kovacs - [email protected]
-------------------------------------------

Serial port (TTYNumber) open error.

As mentioned above, I have the new version of the HX1000i --> https://www.corsair.com/us/en/Categories/Products/Power-Supply-Units/HXi-Series-Fully-Modular-ATX-Power-Supplies/p/CP-9020214-NA

It shows up as:

system devices: Bus 001 Device 003 Port 1-10ID 1b1c:1c1e Corsair HX1000i Power Supply.

Thanks!

Quote

January 26, 20232 yr

Author

10 minutes ago, Olitrolli said:
Thanks for the looking into this!

Here is the output from running the commands in the terminal:
root@Tower:~# /usr/local/bin/corsairmi
No compatible devices found.
root@Tower:~# /usr/local/bin/cpsumon/cpsumoncli TTYNumber
Corsair AXi Series PSU Monitor
(c) 2014 Andras Kovacs - [email protected]
-------------------------------------------

Serial port (TTYNumber) open error.
As mentioned above, I have the new version of the HX1000i --> https://www.corsair.com/us/en/Categories/Products/Power-Supply-Units/HXi-Series-Fully-Modular-ATX-Power-Supplies/p/CP-9020214-NA

It shows up as:

system devices: Bus 001 Device 003 Port 1-10ID 1b1c:1c1e Corsair HX1000i Power Supply.

Thanks!

Thanks, to clarify you need to replace TTYNumber with the corresponding port for the PSU, not just type TTYNumber
/dev/tty...

In addition https://github.com/ka87/cpsumon has not been updated for 7 years
and https://github.com/notaz/corsairmi also not been updated in like 5 years

Edited January 26, 20232 yr by Fma965

Quote

January 27, 20232 yr

On 1/26/2023 at 10:07 AM, Fma965 said:

Thanks, to clarify you need to replace TTYNumber with the corresponding port for the PSU, not just type TTYNumber
/dev/tty...

In addition https://github.com/ka87/cpsumon has not been updated for 7 years
and https://github.com/notaz/corsairmi also not been updated in like 5 years

Sorry for being an absolute noob at this but where do I see which port is used by the PSU?

Really appreciate the help here.

Quote

1 month later...

February 28, 20232 yr

Can we please add HX1500i? Following is the device id information:

Bus 001 Device 014 Port 1-10.4.2 ID 1b1c:1c1f Corsair HX1500i Power Supply

Quote

Prev
1
2
3
4
5
6
7
8
9
10
11
Next
Page 6 of 13

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Followers

Go to topic listing

Replies 322
Views 58.1k
Created 5 yr5 yr
Last Reply Apr 17Apr 17

Corsair RMi, HXi, AXi PSU Statistics - CyanLabs's fork

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

chico11

giganode

giganode

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

chico11

giganode

giganode

Posted Images

Account

Navigation

Search