A charger that buzzes is producing a mechanical response to an electrical drive: magnetic components and capacitors move slightly at the switching frequency or its harmonics, and a quiet room makes the result audible.

The useful questions are whether the noise indicates a fault, what conditions trigger it and how a product’s noise claim can be tested.

What makes a charger audible?

The main sources are transformer and inductor windings, which can move under magnetic forces, and ceramic capacitors, which can exhibit a piezoelectric response. The result varies with load, temperature and the switching scheme.

Because the drive changes with operating conditions, noise can be present in one mode and absent in another, which is why reports are sometimes inconsistent.

Switching frequency and burst mode

Light loads often push a charger into a burst or skip mode, where the switching pattern becomes intermittent. That changes the frequency content of the drive and can make an otherwise silent charger audible.

For a product, this is a control-loop design question rather than a component defect.

Transformer and inductor construction choices

Winding tension, core gap, potting and the mounting of the component all affect how much movement converts into sound. The specification can address each of those, which makes noise a controllable property rather than chance.

Potting and mechanical damping

Potting and conformal coating reduce movement, and mechanical damping at the mounting points prevents the housing from acting as a sounding board. Both are manufacturing choices with cost implications and both are verifiable.

When noise is normal and when it signals a fault

A low-level noise that varies with load is generally a characteristic rather than a fault. Noise accompanied by heat, a burning smell or intermittent charging is a different situation and should be treated as a defect.

Documentation that describes the first case and the second case separately reduces unnecessary returns.

Test conditions for a noise claim

A meaningful test defines the load, the distance and the ambient noise level, because a claim of silent operation is meaningless without them. Testing at several load points shows the behaviour across the range.

Handling customer complaints credibly

Where a noise claim is made, the response is to compare the unit against the specification and the sample. Where it exceeds the level defined in the sampling agreement, the batch is the relevant unit of investigation rather than the individual unit.

Specifying noise behaviour in a programme

Three items frame the specification: the acceptable noise level and the conditions for it, the construction requirements for magnetic components and capacitors, and the test method with its load points.

WECENT builds switching platforms with documented component selection, thermal design and protection behaviour, produced with 100% 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 audible noise 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.