M
Hi Everyone,
I've got a small problem here... The person who drafted the system-requirements document for our device went and listed just about every EMC standard there is. Specifically, the document states:
"The system shall conform to EMC standards FCC Part 15, Directive 89/336/EEC*, IEC 60601-1-2, ICES 003, EN6100-3-2, EN61000-3-3...."
(* I believe this Directive has since been superceded by 2004/108/EC, correct?)
...anyway, it goes on and on...
The point is, though, that now that design is complete we now have to demonstrate compliance to these original requirements laid out.
So my question is, is there a simple way to demonstrate conformity to all these EMC standards? I presume that there's a ton of overlap amonst them...in which case a single battery of tests might suffice (wishful thinking)?
...Of course, this document IS under our control, and we could always revise the original requirements to make it more feasable to verify? ...but in this case, I wouldn't know what to include and what not to.
I think the intent of the person who wrote the original system requirements was to cover all bases, so that the device would conform to as many country-specific requirements as possible. But it seems to me that this requirement statement is totally overkill, and quite infeasable to verify...
Any advice here?
Thanks in advance,
MM.
I've got a small problem here... The person who drafted the system-requirements document for our device went and listed just about every EMC standard there is. Specifically, the document states:
"The system shall conform to EMC standards FCC Part 15, Directive 89/336/EEC*, IEC 60601-1-2, ICES 003, EN6100-3-2, EN61000-3-3...."
(* I believe this Directive has since been superceded by 2004/108/EC, correct?)
...anyway, it goes on and on...
The point is, though, that now that design is complete we now have to demonstrate compliance to these original requirements laid out.
So my question is, is there a simple way to demonstrate conformity to all these EMC standards? I presume that there's a ton of overlap amonst them...in which case a single battery of tests might suffice (wishful thinking)?
...Of course, this document IS under our control, and we could always revise the original requirements to make it more feasable to verify? ...but in this case, I wouldn't know what to include and what not to.
I think the intent of the person who wrote the original system requirements was to cover all bases, so that the device would conform to as many country-specific requirements as possible. But it seems to me that this requirement statement is totally overkill, and quite infeasable to verify...
Any advice here?
Thanks in advance,
MM.