Hi All,
  A question came to me that I can't readily answer.  Would a commercially
available FPGA engineering development board be excluded from the EU EMC
Directive?
The board would be an enclosure-less development kit akin to a PC
motherboard, but designed for use in FPGA engineering development
applications (i.e. not for general consumer use).

I've scoured the ec.europa.eu provided "Guide for the EMC Directive
2004/108/EC (8th February 2010)", with particular attention paid
to sections 1.1.2(.x), 1.1.5, and 1.2.

Taking this document at face value, I am inclined to believe that this
device is a non-excluded apparatus under the scope of the EMC directive.
However, this doesn't sit well with my understanding of the intent of the
directive.

Has anyone received concrete direction for engineering development
apparatuses that they would be willing to share and/or point to?  (side
note - I expected apparati, but apparently that's not the plural form)

Thanks in advance, and Best Regards,
-Dave Heald



Note the best information about the device suggest that it is not subject
to any more specific EMC content containing directive such as R&TTE,
Medical Device, Marine, etc...

-
----------------------------------------------------------------
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]>

Reply via email to