Thank you, everyone!
Regards,Stephen
On Wednesday, February 15, 2017 8:37 AM, Bill Stumpf <bstu...@dlsemc.com>
wrote:
#yiv1807988800 #yiv1807988800 -- _filtered #yiv1807988800 {panose-1:2 4 5 3 5
4 6 3 2 4;} _filtered #yiv1807988800 {font-family:Calibri;panose-1:2 15 5 2 2 2
4 3 2 4;} _filtered #yiv1807988800 {font-family:Verdana;panose-1:2 11 6 4 3 5 4
4 2 4;}#yiv1807988800 #yiv1807988800 p.yiv1807988800MsoNormal, #yiv1807988800
li.yiv1807988800MsoNormal, #yiv1807988800 div.yiv1807988800MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1807988800 a:link,
#yiv1807988800 span.yiv1807988800MsoHyperlink
{color:blue;text-decoration:underline;}#yiv1807988800 a:visited, #yiv1807988800
span.yiv1807988800MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv1807988800 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv1807988800
span.yiv1807988800EmailStyle18 {color:#1F497D;}#yiv1807988800
span.yiv1807988800EmailStyle19
{color:#000066;font-weight:normal;font-style:normal;text-decoration:none
none;}#yiv1807988800 .yiv1807988800MsoChpDefault {font-size:10.0pt;} _filtered
#yiv1807988800 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv1807988800
div.yiv1807988800WordSection1 {}#yiv1807988800 The latest chatter I gathered on
this topic is that the FCC considers collocated as "in the same enclosure".
Indications are that any reference to <20cm being considered collocated has
been set aside. Bill From: Michael Derby [mailto:micha...@acbcert.com]
Sent: Wednesday, February 15, 2017 2:18 AM
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: Re: [PSES] Co-located modules Hi Stephen, One thing to remember
is that “must not be co-located” really just means “must not be co-located
without some additional effort” For example, co-locating two modules and
then calculating the new combined RF Exposure MPE value to verify that the
product still meets the requirements, would be acceptable. It does not
necessarily mean a C2PC is needed, for example. I think you’re right that 20
cm is ‘good guidance’ with regard to RF Exposure. But if your modules are
20.5cm apart, you might still want to consider the overall compliance of that
final product… and a co-located MPE calculation is not too hard. Thanks,
Michael. From: Stephen Whalen [mailto:scwha...@bellsouth.net]
Sent: 14 February 2017 23:34
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: [PSES] Co-located modules All, For a module that has "must not be
co-located" restriction on FCC grant. What is the minimum separation distance
allowed for another transmitter? I recall 20cm but can't find where it is
documented. Regards, Stephen -
---------------------------------------------------------------- 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 <emc-p...@ieee.org> 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 athttp://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://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the
list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to:
Jim Bacher <j.bac...@ieee.org>
David Heald <dhe...@gmail.com> -
---------------------------------------------------------------- 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 <emc-p...@ieee.org> 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://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the
list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to:
Jim Bacher <j.bac...@ieee.org>
David Heald <dhe...@gmail.com> -
----------------------------------------------------------------
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
<emc-p...@ieee.org>All emc-pstc postings are archived and searchable on the web
at:http://www.ieee-pses.org/emc-pstc.htmlAttachments 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://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.htmlFor help, send mail to the
list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>For policy questions, send mail to:
Jim Bacher <j.bac...@ieee.org>
David Heald <dhe...@gmail.com>
-
----------------------------------------------------------------
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
<emc-p...@ieee.org>
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://www.ieee-pses.org/list.html (including how to unsubscribe)
List rules: http://www.ieee-pses.org/listrules.html
For help, send mail to the list administrators:
Scott Douglas <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>
For policy questions, send mail to:
Jim Bacher: <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>
