Thanks to all for the quick education!

Now, follow up question: RED. Seems to me that this does use RF to communicate, 
so it seems to fall into scope of RED. Agree? Disagree?

thanks,

Mike


> Re: [PSES] NFC (near field communication): FCC Approach?On October 20, 2018 
> at 2:40 AM Michael Derby <[email protected]> wrote:
> 
> 
>     I agree with Michael that this needs to be tested and authorised 
> (certified) to FCC 15.225.
> 
>      
> 
>      
> 
>     Another Michael.
> 
>      
> 
>      
> 
>      
> 
>      
> 
>     From: Heckrotte, Michael [mailto:[email protected]]
>     Sent: 20 October 2018 04:00
>     To: [email protected]
>     Subject: Re: [PSES] NFC (near field communication): FCC Approach?
> 
>      
> 
>     Digital devices that have a power consumption not exceeding 6 nW are 
> exempt from specific technical standards per FCC Rules 15.103(f).
> 
>      
> 
>     There are no such exemptions for intentional radiators. See FCC Rules 
> 15.225 for radiated emission limits applicable to radio devices operating on 
> 13.56 MHz.
> 
>      
> 
>      
> 
>     Best Regards,
> 
>     Mike
> 
>      
> 
>     From: Ken Javor <[email protected] 
> mailto:[email protected] >
>     Sent: Friday, October 19, 2018 5:54 PM
>     To: [email protected] mailto:[email protected]
>     Subject: Re: [PSES] NFC (near field communication): FCC Approach?
> 
>      
> 
>     I don’t know what the FCC rules are on something like this – others on 
> this forum are much better informed on that topic - but if the ERP is 0 dBm 
> (1 mW), then at three meters away the field intensity would be 58 mV/m, or 95 
> dBuV/m.  Now this is at 13.56 MHz, where there is no FCC RE limit. But the 
> FCC Class B three meter limit at 30 MHz is something like 40 dBuV/m (someone 
> jump in if I got this wrong) so that means the third harmonic must be 55 dB 
> down from the fundamental.  That is certainly doable, but I wouldn’t take it 
> for granted without some sort of verification.
> 
>     Ken Javor
>     Phone: (256) 650-5261
> 
> 
> 
>     ---------------------------------------------
> 
>     From: MIKE SHERMAN <[email protected] mailto:[email protected] >
>     Reply-To: MIKE SHERMAN <[email protected] 
> mailto:[email protected] >
>     Date: Fri, 19 Oct 2018 17:22:50 -0500
>     To: <[email protected] mailto:[email protected] >
>     Subject: [PSES] NFC (near field communication): FCC Approach?
> 
>     Esteemed fellow listers --
> 
> 
> 
>     I'm looking at a very low power, intermittent NFC card reader/writer. 
> Alkaline battery operated device. NFC is only energized for 10 seconds at a 
> time on demand, and range to read/write is less than 1 cm from the surface of 
> the device.
> 
> 
> 
>     I'm not an EE, but my simplified thought process is: "I can barely get 
> this to couple magnetically with a card sitting on its surface. How could I 
> possibly interfere with broadcast services or other equipment?"
> 
> 
> 
>     So, oh wise ones, from your experience what actions with respect to FCC 
> are reasonable to do? For example, radiated emissions testing seems to me 
> like a total waste of time and money.
> 
> 
> 
>     More technical details: maximum input power to the NFC chip is 17 mW. 
> Chip is coupled to a flat 30mm x 40mm "NFC Ferrite Antenna (13.56 MHz)" that 
> my EE describes as "zero gain." We're rating RF output as 0 mW (i.e., 
> rounding off, it's a lot closer to 0 mW than to 1 mW).
> 
> 
> 
>     Looking forward once again to interesting wisdom from this group.
> 
> 
> 
>     Mike Sherman
> 
>     Graco Inc.
>      -
>     ----------------------------------------------------------------
> 
>     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] mailto:[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://www.ieee-pses.org/list.html (including how to 
> unsubscribe) <http://www.ieee-pses.org/list.html> 
> http://www.ieee-pses.org/list.html
>     List rules:     http://www.ieee-pses.org/listrules.html
> 
>     For help, send mail to the list administrators:
>     Scott Douglas <[email protected] mailto:[email protected] >
>     Mike Cantwell <[email protected] mailto:[email protected] >
> 
>     For policy questions, send mail to:
>     Jim Bacher  <[email protected] mailto:[email protected] >
>     David Heald <[email protected] mailto:[email protected] >
> 
>     -
>     ----------------------------------------------------------------
> 
>     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] mailto:[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://www.ieee-pses.org/list.html (including how to 
> unsubscribe) http://www.ieee-pses.org/list.html
>     List rules: http://www.ieee-pses.org/listrules.html
> 
>     For help, send mail to the list administrators:
>     Scott Douglas <[email protected] mailto:[email protected] >
>     Mike Cantwell <[email protected] mailto:[email protected] >
> 
>     For policy questions, send mail to:
>     Jim Bacher <[email protected] mailto:[email protected] >
>     David Heald <[email protected] mailto:[email protected] >
> 
> 
>     This e-mail may contain privileged or confidential information. If you 
> are not the intended recipient: (1) you may not disclose, use, distribute, 
> copy or rely upon this message or attachment(s); and (2) please notify the 
> sender by reply e-mail, and then delete this message and its attachment(s). 
> Underwriters Laboratories Inc. and its affiliates disclaim all liability for 
> any errors, omissions, corruption or virus in this message or any attachments.
> 
>     -
>     ----------------------------------------------------------------
> 
>     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] mailto:[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://www.ieee-pses.org/list.html (including how to 
> unsubscribe) http://www.ieee-pses.org/list.html
>     List rules: http://www.ieee-pses.org/listrules.html
> 
>     For help, send mail to the list administrators:
>     Scott Douglas <[email protected] mailto:[email protected] >
>     Mike Cantwell <[email protected] mailto:[email protected] >
> 
>     For policy questions, send mail to:
>     Jim Bacher <[email protected] mailto:[email protected] >
>     David Heald <[email protected] mailto:[email protected] >
> 


 

> -
>     ----------------------------------------------------------------
> 
>     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] mailto:[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://www.ieee-pses.org/list.html (including how to 
> unsubscribe) http://www.ieee-pses.org/list.html
>     List rules: http://www.ieee-pses.org/listrules.html
> 
>     For help, send mail to the list administrators:
>     Scott Douglas <[email protected] mailto:[email protected] >
>     Mike Cantwell <[email protected] mailto:[email protected] >
> 
>     For policy questions, send mail to:
>     Jim Bacher <[email protected] mailto:[email protected] >
>     David Heald <[email protected] mailto:[email protected] >
> 


 

-
----------------------------------------------------------------
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://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 <[email protected]>
Mike Cantwell <[email protected]>

For policy questions, send mail to:
Jim Bacher:  <[email protected]>
David Heald: <[email protected]>

Reply via email to