What CE marking actually asks of a brushless motor

Plenty of teams treat CE marking as a box you tick near the end — send a unit to a lab, get a certificate, ship to Europe. Then they hit a wall at the worst possible time, weeks before launch, because the motor's switching noise is failing emissions and the fix means changing the controller they already tooled.

CE is not a test. It's a declaration you make that your product meets the relevant European directives, backed by evidence. The trick is knowing which directives are relevant, because for a brushless motor it's rarely just one, and the answer depends on how your motor is sold and used.

The directives that usually apply

EMC — Electromagnetic Compatibility

This is the one that catches BLDC products, almost without exception. A brushless motor is driven by a controller switching current at high frequency, and switching edges generate electromagnetic noise — both conducted back down the power lines and radiated into the air. EMC compliance means proving two things: your product doesn't emit more interference than allowed, and it keeps working when other equipment interferes with it. The emissions side is where motor-drive products most often fail first time.

Low Voltage Directive (LVD)

If your equipment operates between 50 and 1000 V AC or 75 and 1500 V DC, the LVD applies and covers electrical safety — shock protection, insulation, temperature rise, the things that stop a product hurting someone. Many battery-powered BLDC products sit below these thresholds and fall outside the LVD, but the moment you're on mains, or running a high-voltage pack, it's in scope. Don't assume; check your actual working voltages against the limits.

Machinery Directive

If your motor is part of machinery with moving parts that can cause injury, this can pull in a whole additional layer of risk assessment and safety requirements. A motor sold as a component is treated differently from a motor built into a finished machine, and "partly completed machinery" has its own route. This is the directive most often missed, because people think of their product as electronics, not machinery.

The expensive surprises in certification almost never come from the test itself. They come from discovering, late, that a directive you didn't plan for applies to you.

Component or product — it changes everything

Here's a distinction that trips people up. A bare motor sold to another manufacturer to build into their equipment is generally a component, and a component on its own often can't even carry a CE mark for some directives — it's the finished product that gets certified. But the moment your motor ships with its controller, a housing and a power input as something an end user plugs in and runs, you're likely placing a finished product on the market, and the full weight of the relevant directives lands on you.

So before anyone books a lab, the first question is: what exactly are you selling, and to whom? The same physical motor can have completely different obligations depending on the answer.

Where BLDC products actually fail

• Conducted emissions from the drive. The controller's switching dumps noise back onto the supply. Without proper filtering on the input, you fail conducted emissions — and bolting a filter on afterwards is always worse and more expensive than designing for it.
• Radiated emissions from cabling. The motor cables act as antennas for switching noise. Layout, shielding and cable choices made during design decide this, not anything you can fix at the lab.
• Insulation and clearances. On higher-voltage designs, creepage and clearance distances inside the motor and terminations have to meet the safety standard. Retrofitting spacing into a finished motor is often impossible.
• Temperature rise. Safety standards cap how hot accessible surfaces and windings are allowed to get. This ties straight back to your thermal design and the dyno data — another reason loaded testing earns its keep.

How to keep certification from becoming a crisis

The pattern that works is boring and effective: decide the target markets and the product definition up front, identify which directives that triggers, and design against the relevant harmonised standards from the start. Build in the EMC filtering, the clearances and the thermal margin while they're cheap to add — in the design — not after tooling.

Then do pre-compliance testing before the formal test. A rough EMC scan on an early prototype, even on simple gear, will flag an emissions problem while you can still solve it by changing the design. Walking into a full lab session blind is how you get an expensive fail and a schedule slip.

And remember CE is one market's regime. Selling into the US brings the FCC into the emissions picture; other regions have their own marks. The good news is that a product engineered to pass a rigorous EMC and safety standard is usually most of the way to the others — if you planned it that way from the beginning.

None of this is exotic, but it has to be threaded through the whole program rather than bolted on at the end. That's the part we manage for clients: deciding what applies, designing to clear it, and running the test-house relationship so the certificate is a formality, not a gamble.

This is general guidance, not regulatory advice — the binding requirements are in the directives and harmonised standards themselves, and your specific obligations depend on your product and market.