In message <D038C885075E4234912D119506A574CB@christopher>, dated Sat, 16
Jun 2012, Chris Wells <[email protected]> writes:
I have a 24VDC powered device that needs to meet CISPR 11. We planned
to recommend a particular class B power supply with this device.
However the noise from our device appears to be pushing through the
power supply and limiting the combo to class A. The problem area is in
the 5-30 MHz. range.
Strictly, if you are not supplying the power supply, just recommending
it, then to the letter of the EMC Directive you are not responsible for
its emissions, even when connected to your product. But I think many
people would say that was cheating.
If your DC input is pushing out enough hash to cause the power supply's
emissions to be too high, I think you do have to quieten the DC input,
regardless of what any standard says. Standards can't necessarily
explicitly cover every possible situation.
--
OOO - Own Opinions Only. Try www.jmwa.demon.co.uk and www.isce.org.uk
Instead of saying that the government is doing too little, too late or too
much, too early, say they've got is exactly right, thus throwing them into
total confusion.
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK
-
----------------------------------------------------------------
This message is from the IEEE Product Safety Engineering Society emc-pstc discussion
list. To post a message to the list, send your e-mail to <[email protected]>
All emc-pstc postings are archived and searchable on the web at:
http://www.ieee-pses.org/emc-pstc.html
Attachments are not permitted but the IEEE PSES Online Communities site at
http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used
formats), large files, etc.
Website: http://www.ieee-pses.org/
Instructions: http://listserv.ieee.org/request/user-guide.html
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <[email protected]>
Mike Cantwell <[email protected]>
For policy questions, send mail to:
Jim Bacher: <[email protected]>
David Heald: <[email protected]>
