Quiet or Noisy? How to Test Power Adapter Acoustics
Power adapter acoustic noise should be evaluated against a defined sound metric and test setup in the operating states that matter to the end product. Agree whether acceptance covers overall sound level, a tonal whistle or both, then record the load, microphone geometry and background conditions. A result from one configuration cannot establish that an adapter will be inaudible in every installation.
For an OEM team, the useful starting point is the product’s use. A bedside device, a quiet office terminal and equipment in a machinery room create different acoustic expectations. Describe that use to the supplier before asking it to meet a requirement called “low noise.”
What does “quiet” mean for this product?

Write the acoustic requirement around what the user should experience and how the team will evaluate it. If a distinct whistle is the complaint, retain that information when defining the test. If the concern is total sound from the complete device, identify whether the adapter will be measured separately, as part of the device, or both.
ISO 7779:2018 describes airborne-noise measurement for information technology and telecommunications equipment. Its framework distinguishes A-weighted sound power from emission sound pressure at specified positions and includes assessment of prominent discrete tones. Ask the test laboratory which method and quantity fit your product; the standard’s scope does not supply a universal pass value for adapters.
The related ECMA-74 framework also treats prominent tones and references methods for other audible characteristics. An overall number therefore needs a clear description of what it measures. A tonal assessment answers a different acceptance question from an overall sound-level result.
Agree the method, edition and acceptance criteria before evaluating samples. Record who sets the limit and whether it applies to the adapter alone or the complete product. Keep product sound requirements distinct from any separate assessment of workplace noise exposure.
Electrical noise belongs in a different record. The site’s ripple and noise measurement guide addresses voltage measurements. Those results do not report the airborne sound a user hears, even when an engineer investigates a relationship between electrical activity and acoustic behavior.
Which operating states belong in the acoustic test?

The diagram brings several operating states to the same acoustic observation point. Use it as a planning model: change the relevant device state while keeping the agreed measurement conditions identifiable. It does not show measured sound levels.
Build the state list from the device’s actual use. Include the modes where a complaint could occur, such as standby, normal operation or a transition between functions. Add no-load operation if that is a relevant state for the adapter. Ask the supplier which other conditions its design review suggests evaluating.
There is a physical reason to look beyond one load setting. In Murata’s laptop battery-line examples, operating mode changes the audible behavior of ceramic capacitors and the circuit board. These examples support checking meaningful modes; they do not identify the cause of a sound from a particular sealed adapter.
Texas Instruments describes another specific mechanism in its UCC28880/UCC28881 application note: on/off controller activity can enter the audible band. TI also calls for evaluation that accounts for temperature and component/device variation. The discussion concerns those offline buck controllers, so its design remedies should not be applied indiscriminately to other adapters.
For each selected state, identify how the device reaches it and how long the observation should cover. If the sound appears only during a transition, ask for that transition to be documented. A steady-state result alone would leave that part of your request unanswered.
How should the measurement conditions be recorded?

Two acoustic reports are easier to compare when they describe the same measurement conditions. Ask the laboratory to identify the method used, the configuration tested and any restrictions on interpretation. Avoid specifying an arbitrary microphone distance copied from another product’s report.
Murata’s published evaluation uses an operating specimen inside an anechoic box, with sound-pressure measurement and frequency analysis. That is a manufacturer example of controlling the acoustic observation. The appropriate facilities and method for your finished product should be established with the laboratory.
Use the following fields to organize that discussion. They are proposed report fields, not a substitute for the selected standard’s full procedure.
| Record field | What the report should make clear |
|---|---|
| Specimen identity | Adapter model, revision, cable and connected device or defined load |
| Acoustic quantity | Sound power or sound pressure, weighting and any tonal assessment |
| Method and setup | Method edition, microphone positions, orientation and support arrangement |
| Environment | Background conditions and how the method addresses them |
| Operating state | Input condition, load or device mode, and relevant temperature condition |
| Observation | Measurement interval, transitions examined and any limitations |
Background conditions need particular attention when the sound is faint. Ask the laboratory whether the available setup can distinguish the specimen’s emission sufficiently for the agreed decision. An unexplained low reading should prompt a review of the method’s limitations before it becomes a supplier acceptance claim.
Retain the actual configuration. A note such as “adapter tested” gives the next engineer little help if the cable, supporting surface or connected load cannot be identified. Photographs and a clear setup description can make the record easier to reproduce, without turning an illustrative photograph into proof of a result.
What evidence should support sample acceptance?

Review the result against the requirement that was agreed for the sample. Check that the report uses the intended metric, covers the requested operating states and identifies the adapter revision. If acceptance includes a tonal criterion, confirm that the report addresses it rather than relying solely on an overall value.
Treat an unexplained sound observation as a question for supplier investigation. Provide the operating state and the conditions under which the sound occurred. A recording may help describe the complaint, but it should not replace the agreed measurement evidence unless the acceptance plan explicitly makes that recording method suitable for the decision.
Ask the supplier to document any change it proposes in response. Identify the revised sample and agree which acoustic evaluations need to be repeated. Keep the broader power adapter qualification test plan connected to that decision so the acoustic review does not lose track of the approved product configuration.
A useful acceptance record states the requirement, the evidence reviewed, the decision and any remaining condition. If the report covers only the adapter on a laboratory bench, preserve that scope in the approval. Complete-device evidence may still be needed where the customer’s requirement concerns the installed product.
Send the supplier your operating-state list, installation description and the acoustic question you need answered. Agree the measurement method and acceptance criteria before the next sample comparison, then request results tied to that exact configuration.