A charger that trips a breaker when it is plugged in is usually behaving exactly as its input circuit dictates. The cause is inrush current: a brief, high current as the input capacitors charge.

Understanding the mechanism explains why some installations tolerate it and others do not, and what the design can do about it.

Why does inrush current happen at plug-in?

At the instant of connection, the input capacitors are discharged and behave almost as a short circuit until they charge. The current that flows in that first fraction of a cycle can be many times the steady-state value.

The magnitude depends on the circuit design and on the point in the mains cycle at which the connection is made, which is why the same charger can trip protection once and not the next time.

NTC thermistors, relays and active limiting

Three approaches reduce inrush: a thermistor whose resistance falls as it warms, a relay that bypasses a limiting resistor after startup, and an active circuit that controls the charging of the input capacitance.

Each trades cost, complexity and efficiency differently, and the choice follows the product’s power level and its expected installation.

Peak current versus breaker and fuse curves

Protection devices respond according to their time-current curves, so a short high-current pulse may pass while a longer one trips. That is why inrush interacts with the protection type rather than only with its rating.

For installation planning, the relevant question is the protection device’s response at the pulse duration, not its steady-state rating alone.

Multiple chargers on one strip

Several chargers connected to one strip can draw inrush collectively if they are energised together, particularly where the strip is switched at the wall. Spreading connection times, or using a strip with sequencing, reduces the aggregate pulse.

Surge events and what protects the charger

Inrush is a startup phenomenon, while surge is an external event. The charger’s input protection addresses voltage transients, and its specification should state what it tolerates without failure.

That distinction matters in venues with poor power quality, where the charger may be blamed for damage caused upstream.

Test method and what to record

A practical test records the peak current and its duration at a defined input voltage, with the measurement method stated. Repeating the test over several connection points in the mains cycle gives a distribution rather than a single number.

That record is what answers an installation complaint with evidence.

Field complaints that trace back to inrush

Two complaints recur: a breaker that trips when a charger is plugged in, and a charger that appears to fail on first use when the protection has actually operated. Both are resolved by understanding the input circuit rather than by replacing the product.

Specifying input behaviour for a product line

The specification should state the peak inrush current and its duration, the limiting method used, the protection the product provides against surges and the test conditions.

WECENT builds switching platforms with over-voltage, over-current, over-temperature and short-circuit protection, tested through functional testing, hi-pot pressure testing and load aging at the quality control gates; documentation is available under NDA through the OEM/ODM programme, and the range is listed in the product catalogue.

Programmes in this area are decided by documentation as much as by hardware. The practical discipline is to keep one file per model containing the specification, the test and inspection records and the market documents, and to review it whenever the bill of materials or the production site changes. WECENT produces per-batch inspection records at its quality control gates and provides model-level specifications and certification planning through its OEM/ODM programme, with the platform range listed in the product catalogue.

For inrush and surge design, the same file answers most questions that arise during qualification, audit or listing review: which standard applies, which model was tested, and which batch the shipped units came from. Reference documents for the relevant requirements are published by the standards and regulatory bodies, including the official text and the related requirement, with the equivalent market rule and https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15 applying where the product is sold into those markets.

Two further habits keep the file usable over time. The first is to record the review date and the reviewer against each document, so that an outdated report is visible rather than assumed current. The second is to keep the commercial documents – quotation, agreed specification and packaging artwork – in the same folder as the technical evidence, because a question about a shipped unit usually requires both.

A further point concerns the production reality behind the paperwork. Claims that survive scrutiny are the ones a factory can reproduce batch after batch, which means the specification, the test method and the acceptance criteria have to travel together with the order. Where they do not, the same product can be built to two different understandings of the same document.

Finally, buyers should decide in advance what evidence they will need if a question arises later, and request it at the sampling stage rather than after the shipment. Requesting records retrospectively is possible, but it is slower and it removes the opportunity to correct a specification before tooling. WECENT supports programmes with model-level specifications and per-batch inspection records produced at its quality control gates, available under NDA through its OEM/ODM programme, with the platform range listed in its product catalogue catalogue.

Reference standards for this topic

Where a programme needs the primary documents, the relevant references for this topic are published by the standards bodies and regulators: USB-IF: USB Power Delivery, ISTA: transit test protocols.