Corsair HX1000i ATX3.1 incorrect Input voltage displayed

[ralf474]

Hello. I have a Corsair HX1000i ATX3.0 (CP-9020259-EU) PSU that I bought more than a year ago where the Input voltage is correct.


Recently I got a Corsair HX1000i ATX3.1 (CP-9020259-EU) PSU and it says 115V, it's plugged in the same wall socket at the other PSU. I did restart, shutdown, unplug-replug, try different wall socket, reinstall Hwinfo, but nothing helped.

 

[Martin]

The PSU reports this value. Maybe check for a 110/230V switch on the PSU?

 

[ralf474]

The PSU reports this value. Maybe check for a 110/230V switch on the PSU?

There's no switch on it. https://hwbusters.com/psus/corsair-hx1000i-review/
I checked iCue too, but I can't find the Input voltage anywhere.

 

[red-ray]

There are two variants of the HX1000i, the original with a PID of 1C07 (HID\VID_1B1C&PID_1C07) which does report 230 volts when it should and a later model with a PID of 1C1E (HID\VID_1B1C&PID_1C1E). With the later model it looks like Corsair have messed up and and they incorrectly report 115 rather than 230 volts as my SIV utility also reported 115 on 2025-03-12 for one in Germany with the V0.3.02 firmware. I wonder if there is a firmware update to fix this, if not you should ask Corsair for one.

 

[ralf474]

There are two variants of the HX1000i, the original with a PID of 1C07 (HID\VID_1B1C&PID_1C07) which does report 230 volts when it should and a later model with a PID of 1C1E (HID\VID_1B1C&PID_1C1E). With the later model it looks like Corsair have messed up and and they incorrectly report 115 rather than 230 volts as my SIV utility also reported 115 on 2025-03-12 for one in Germany with the V0.3.02 firmware. I wonder if there is a firmware update to fix this, if not you should ask Corsair for one.

View attachment 12471

Thank you. There are three variants(4 if we count the original blue). The ATX 2.52 without 12VHPWR cable, ATX3.0 with H+ cable and ATX3.1 with H++ cable.

 

[red-ray]

There are three variants

OK and given your two report the same V0.3.2 firmware version I suspect the firmware version from the hardware is not correct. I mentioned this issue to the owner in Germany and he said that iPOO also reports 115 Volts for his and has reported the issue to Corsair. I wonder if Corsair will fix this.

BTW [Link Devices] shows the PnP IDs as does the Corsair HX1000i Power Supply (#0) tooltip.

 

[jonnyGURU]

Thanks for the heads up. Oversight on my part. I'll look into it now.

EDIT: Someone flipped a register in the firmware. 115V mains reports 230V. 230V mains reports 115V.

 

[jonnyGURU]

Thank you. There are three variants(4 if we count the original blue). The ATX 2.52 without 12VHPWR cable, ATX3.0 with H+ cable and ATX3.1 with H++ cable.

You are somewhat correct, but red-ray is also correct. There are technically only two variants. Just because the cable selection changes, doesn't mean it gets a new PID or even a new RPS part number, for that matter.

Also, there is no such thing as a H++ cable. The PCIe 5.1 spec only changed the connector on the GPU. We just started stamping "H++" on the connector because people were still confused about how a male H+ connector plugged into a female H++ connector. You'll note that the 75 level and CP part numbers are the same. Only the artwork on the box changed.

 

[ralf474]

Thanks for the heads up. Oversight on my part. I'll look into it now.

EDIT: Someone flipped a register in the firmware. 115V mains reports 230V. 230V mains reports 115V.

Can your avarage user update the firmware? Or does one need to send it back?

You are somewhat correct, but red-ray is also correct. There are technically only two variants. Just because the cable selection changes, doesn't mean it gets a new PID or even a new RPS part number, for that matter.

Also, there is no such thing as a H++ cable. The PCIe 5.1 spec only changed the connector on the GPU. We just started stamping "H++" on the connector because people were still confused about how a male H+ connector plugged into a female H++ connector. You'll note that the 75 level and CP part numbers are the same. Only the artwork on the box changed.

Well technically yes, there shouldn't be any difference. From my sample of one, my 3.0 H+ cable is 3 dimple that's split on top and bottom, the 3.1 H++ cable is the spring version that's open only at the bottom. The premium individually sleeved 12V-2X6 cable from corsair.com says 12VHPWR(just like on der8auer video) on the label and has H+ stamp with spring design.

Not sure if you guys updated from dimple to spring or it just comes from a different supplier and it's lottery.

 

[red-ray]

Someone flipped a register in the firmware. 115V mains reports 230V. 230V mains reports 115V.

Thank you for the information, but this does not make total sense as looking at #post-48602 the both PSUs report the same V0.03.02 firmware version with one reporting 115 and the other 230.

My guess is that "Someone" also failed to update the firmware version, did they please?
Is/will there be a firmware update to fix this or will owners need to RMA the PSUs?

Note from the HX1000i Power Supply I can tell these are both PID 1C1E as PID 1C07 will report as HX1000i C-Link Adapter.

 

[bibi]

Hello. I have a Corsair HX1000i ATX3.0 (CP-9020259-EU) PSU that I bought more than a year ago where the Input voltage is correct.

I am the german SIV user. I can see the wrong voltage on ICue to, see Eingangsspannung 115V. The same CP-9020259-EU from Amazon

 

[jonnyGURU]

Well technically yes, there shouldn't be any difference. From my sample of one, my 3.0 H+ cable is 3 dimple that's split on top and bottom, the 3.1 H++ cable is the spring version that's open only at the bottom. The premium individually sleeved 12V-2X6 cable from corsair.com says 12VHPWR(just like on der8auer video) on the label and has H+ stamp with spring design.

Not sure if you guys updated from dimple to spring or it just comes from a different supplier and it's lottery.

My point was that the box and cable kit doesn't make the PSU itself different. That's all.

As for the dimple vs. spring: CWT was never authorized to change the terminal. They did so without telling us and now we are trying to get them to change back to the dimples.

The spring terminals have been problematic. Their lack of movement causes misalignment of terminals while mating. This, in turn, wears out the "split" causing the terminal to open up and release its tension on the male terminal within the female connector. Furthermore, copper makes for a terrible spring material. It's too soft. Since the dimples, on the other hand, are embossed into the metal, the likelihood of malleation is reduced.

Thank you for the information, but this does not make total sense as looking at #post-48602 the both PSUs report the same V0.03.02 firmware version with one reporting 115 and the other 230.

My guess is that "Someone" also failed to update the firmware version, did they please?
Is/will there be a firmware update to fix this or will owners need to RMA the PSUs?

Note from the HX1000i Power Supply I can tell these are both PID 1C1E as PID 1C07 will report as HX1000i C-Link Adapter.

Not sure what they were doing in the firmware in the first place. There were no changes requested, yet someone went in, changed something, flipped the input voltage values and then didn't give the firmware a new revision! Again: CWT doing shit without people telling them to do it.

 

[jonnyGURU]

Can your avarage user update the firmware? Or does one need to send it back?

Unfortunately, it cannot be updated by the end user. Not sure how important it is to the end user, but I suppose you could send it back if it bothers you. Just give me some time to give the support team a heads up.

 

[red-ray]

There were no changes requested, yet someone went in, changed something, flipped the input voltage values and then didn't give the firmware a new revision!

Thank you for the clarification, if they had updated the firmware revision I could have done a workaround. Please ensure the fixed firmware does have a updated revision/version.

What's the issue with end users not being able to update the firmware? I have a DediProg SF100, could that do it?

 

[jonnyGURU]

Thank you for the clarification, if they had updated the firmware revision I could have done a workaround. Please ensure the fixed firmware does have a updated revision/version.

What's the issue with end users not being able to update the firmware? I have a DediProg SF100, could that do it?

Same reason as always. If you brick the firmware of a keyboard, you can use another keyboard. If you brick the firmware on the PSU, your whole PSU is down for the count.

 

[ralf474]

My point was that the box and cable kit doesn't make the PSU itself different. That's all.

As for the dimple vs. spring: CWT was never authorized to change the terminal. They did so without telling us and now we are trying to get them to change back to the dimples.

The spring terminals have been problematic. Their lack of movement causes misalignment of terminals while mating. This, in turn, wears out the "split" causing the terminal to open up and release its tension on the male terminal within the female connector. Furthermore, copper makes for a terrible spring material. It's too soft. Since the dimples, on the other hand, are embossed into the metal, the likelihood of malleation is reduced.

Not sure what they were doing in the firmware in the first place. There were no changes requested, yet someone went in, changed something, flipped the input voltage values and then didn't give the firmware a new revision! Again: CWT doing shit without people telling them to do it.

I hate to mention him, but JayZ showed that dimple could suffer more damage after multiple insertion. Well it's not like I have any choice or chance getting a dimple individually sleeved cable, since Corsair.com doesn't sell them, maybe alza.cz has some old stock?

Unfortunately, it cannot be updated by the end user. Not sure how important it is to the end user, but I suppose you could send it back if it bothers you. Just give me some time to give the support team a heads up.

Thanks. That's a shame. It would bother me very much on my main rig, but fortunately the 115V is just for testbench and the new replacement would still read 115V, wouldn't it?

 

[Martin]

BTW, reporting 115V for VIN can result in some mess when calculating power consumption. Corsair uses certain formulas (estimates) to calculate either PIN from POUT or vice-versa and they depend on whether the PSU is 110V or 230V.

 

[jonnyGURU]

I hate to mention him, but JayZ showed that dimple could suffer more damage after multiple insertion. Well it's not like I have any choice or chance getting a dimple individually sleeved cable, since Corsair.com doesn't sell them, maybe alza.cz has some old stock?

I am familiar with Jayz and his testing is very unscientific. He made a lot of assumptions. And he is wrong. He correlated the play in the terminals to "wear and tear", when, in fact, the play in the terminals are there by design. Fun fact! The reason he saw better conductivity the more he plugged in and unplugged the connector? The tin plating is scraping off exposing bare copper. That's why.

He let me down a long time ago when he told everyone that using pigtails hurt your benchmark scores. He ran the straight cables first, then the pigtails and the score was lower. Of course, anyone that tests a barrage of benchmarks over and over again without a complete cool down period, the scores will get worse and worse over time until you let the GPU and CPU completely cool off. Yet... here we are.

 

[jonnyGURU]

BTW, reporting 115V for VIN can result in some mess when calculating power consumption. Corsair uses certain formulas (estimates) to calculate either PIN from POUT or vice-versa and they depend on whether the PSU is 110V or 230V.

Correct. As 230V has an overall higher efficiency.

 

[red-ray]

Same reason as always. If you brick the firmware of a keyboard, you can use another keyboard. If you brick the firmware on the PSU, your whole PSU is down for the count.

That's true when using a program the update firmware, but not when using a flash hardware programmer such as the DediProg SF100.

I suspect I have just spotted another firmware bug, the Product Name is CORSAIR when I suspect it should be HX1000i given what my RM850i reports.