Now, isn't that the crux of the problem. Lots of folks like you Brian, Gamer Nexus, etc. commenting on what should happen, how things are supposed to work, and what appropriate behavior is yet do not know anything about what the design requirements are. For instance Brian_B is going on about OPP and how it handles shorts. It does not. OPP is not even a required protection under the ATX12v or EPS design guide so it may be implemented however a manufacturer wishes. What does control shorts is the SCP which is defined in the design guides. I have have a nifty little button on the load tester to test the protection that drops the resistance to below 0.1 Ohm. OPP? Well yes a test for that too, but it has a slew rate defined by the load tester NOT a specification.
Not when there are design parameters required because it is impossible to design for every instance when there are no rules to play by.
Literally impossible to design out idiots. There is no way to design a unit for every failure or overload mode. That is why there is a design guide that establishes what unit has to do in order to be compliant. "Overload safety" is not a defined thing in this case. Again, it goes to people are commenting on what they don't know about. OCP does exist....and the spec calls for 240VA per rail with a defined slew rate. Now, I will let you figure out exactly how many power supplies are not spec compliant for OCP that you guys love and have no problem with.
Well, hold on just a moment.
I may not be familiar with the specifics of the standards that apply to power supplies, but I have been in product development my entire career.
You start with a set of user requirements. Those generally include a bunch of safety precautions. There is a risk management process designed to uncover additional risks that had not previously been considered. These are also added to the requirements.
In any industry the established standards are a bare minimum, not what you design to as a target.
In my industry minimum electrical safety standards are set by IEC 60601-1. That doesn't mean anyone designs to the standard and then washes their hands of everything else. As part of the user needs process they look at their own returns and failures and determine what kind of problems they have had in the past, and they add in their own internal design requirements to mitigate them.
Standards are nothing but bare minimums, and you know what they say about people who do nothing but the bare minimum?
Gigabytre can complain about how they are testing all they want, but there is a reason these two 750 and 850 watt Gigabyte units are failing spectacularly in testing, and others aren't. Maybe they weren't conservative enough in setting their design targets. Maybe they made a mistake in a calculation that didn't get caught. Maybe they made a mistake in trusting a sub-contractor they shouldn't have. I don't know the details, but the truth is their power supplies are a problem, and others are not.
I don't want to point fingers enough. You spend long enough in any industry and even the best company has a screw-up. That is inevitable. The difference between the good and the bad - however - is how they behave when things go wrong. Thus far Gigabyte is not off to a good start.
Blaming a standard, or a lack thereof is a cop-out. As a designer of any product, you are supposed to know your customer, know their usage scenario and design to match. You design your product for it's actual use condition to the users need, and mitigate the risks the user is likely to see. The standards are just bare minimums. You never rely on standards to ensure you have a good product.
You develop your user needs, you design to those needs, and then you test to make sure you have met those needs. It is your responsiblity to determine what the needs are, and make sure you have designed a product that works, standards or none.