See FCC 784748 D01 Labeling Part 15 &18 Guidelines v07.
"Guidelines for Labelling and User Information for Devices Subject to
Part 15 and Part 18"

I think the pertinent part you seek is related to Certification:

If the device is subject to Certification:
(1) Section 2.925 contains information on identification of the
equipment; 
(2) include a label bearing an FCC Identifier (FCC ID) (Section 2.926)
and 
(3) include the appropriate compliance statement in Section 15.19(a). 

If the device is considered too small and therefore it is impractical
(smaller than the palm of the hand) to display the
compliance statement, then the statement may be placed in the user
manual or product
packaging. However, the device must still be labelled with the FCC ID.
If the device is
unquestionably too small for the FCC ID to be readable (smaller than 4-6
points), the FCC ID
may be placed in the user manual. However, it must be determined that
the device itself is too
small - the label area allocated to the FCC ID may not be reduced
because of over crowded
identification of other product and regulatory information.

-Bob Sykes


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Gartman,
Richard
Sent: Monday, January 17, 2011 2:44 PM
To: [email protected]
Subject: FCC and IC Grantee Code marking

Our engineering group has developed a small 802.11 b/g client (just a
little bigger than a blue tooth head set. It is an external plug-in
device allowing another product to be Wi-Fi accessible). Since there is
not a lot of surface area on the product, can the FCC and IC markings be
left off the product and only placed in the manual? If it has to be on
the product what is the minimum size of the lettering?

Thank you for your opinions.
W. Richard Gartman, MS, CSP
Product Stewardship Manager
Texas Instruments, Education Technology
7800 Banner Drive, Dallas, Tx 75251
Office: 972-917-1636               Email: [email protected]
Fax: 972-917-0668   URL: www.education.ti.com 
www.education.ti.com/us/productstewardship

-
----------------------------------------------------------------
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://product-compliance.oc.ieee.org/
Graphics (in well-used formats), large files, etc. can be posted to that
URL.

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


Please be advised that this email may contain confidential 
information.  If you are not the intended recipient, please notify us 
by email by replying to the sender and delete this message.  The 
sender disclaims that the content of this email constitutes an offer 
to enter into, or the acceptance of, any agreement; provided that the 
foregoing does not invalidate the binding effect of any digital or 
other electronic reproduction of a manual signature that is included 
in any attachment.

-
----------------------------------------------------------------
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://product-compliance.oc.ieee.org/
Graphics (in well-used formats), large files, etc. can be posted to that URL.

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