Hi Dennis

I think what we see often are intentional radiators that are also  
computer peripherals eg WiFi USB dongles.  These would need DoC logo  
or separate certification per 15.101, yes?

best regards

Tom

On Apr 1, 2009, at 3:49 PM, Dennis Ward wrote:

> Of course, having said that someone will probably pull out of the  
> hat the
> one instance where some obscure intentional radiator was DoC.   
> Never say
> never
>
> Dennis Ward
> Director of Engineering
> American TCB
> Certification Resource for the Wireless Industry www.atcb.com
> 703-847-4700 fax 703-847-6888
> direct - 703-880-4841
>
>
> -----Original Message-----
> From: Dennis Ward [mailto:[email protected]]
> Sent: Wednesday, April 01, 2009 3:36 PM
> To: 'Gartman, Richard'; 'Reginald Henry'; '[email protected]'
> Subject: RE: FCC ** LOGO vs Verification Label RequirementT***
>
> HI Richard
> I do not think that is indicated in my response. Intentional  
> radiators are
> certified and not DoC'd. There are a couple rare instances where  
> certain
> intentional radiators may be verified, but they are never DoC'd. In  
> other
> words DoC does not apply to intentional radiators.   In the mention  
> of a
> receiver there is an instance where a standalone receiver could be  
> DoC'd.
> However, when the receiver is part of the transceiver (transmitter and
> receiver in one unit) and the transmitter portion is certified, the  
> receiver
> is only verified. DoC basically applies to only unintentional  
> radiators but
> does not apply to verified devices. 15.101 gives the list of what  
> can and
> cannot be DoC'd
>  Hope this clears it up a little.
>
> Dennis Ward
> Director of Engineering
> American TCB
> Certification Resource for the Wireless Industry www.atcb.com
> 703-847-4700 fax 703-847-6888
> direct - 703-880-4841
>
>
> -----Original Message-----
> From: Gartman, Richard [mailto:[email protected]]
> Sent: Wednesday, April 01, 2009 2:34 PM
> To: Dennis Ward; 'Reginald Henry'; [email protected]
> Subject: RE: FCC ** LOGO vs Verification Label RequirementT***
>
> Dennis,
> As I read your description, the FCC logo is for use only on  
> intentional
> radiators, such as wireless access points or clients, which require  
> FCC
> certification.
> Is this correct?
>
> 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
> Please consider the environment before printing this email. There  
> is only
> one earth - don't waste it.
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of  
> Dennis Ward
> Sent: Wednesday, April 01, 2009 4:10 PM
> To: 'Reginald Henry'; [email protected]
> Subject: RE: FCC ** LOGO vs Verification Label RequirementT***
>
> By FCC logo I take it that you mean the DoC logo.  If so, the DoC  
> logo only
> applies under certain situations and is not for general use.   
> Typically the
> FCC LOGO only applies and can only be used in those instances where  
> the
> device can be certified or DoC'd.  The devices that can use the DoC  
> logo are
> found in CFR 47 15.101 and include such things as Class B computer
> peripheral device (class A cannot use the DoC logo), CB receivers,
> Superregenerative receivers, all other receivers subject to part 15
> (receiver that tune between 30-960MHz only and which are not  
> verified as
> part of a transceiver the transmitter of which is certified), TV  
> interface
> devices, cable system terminal device, CPU boards and internal power
> supplies used in Class B personal computers, Class B personal  
> computers
> assembled using authorized boards and power supplies.
>
> No other device is supposed to or should use the DoC logo.
>
> Too many times, because of misinformation etc, companies try to put  
> the DoC
> logo on digital devices that are not subject to certification or  
> DoC and
> Class A computers or other type devices.  For an exact definition  
> of what
> can and cannot have the DoC logo you should refer to CFR47 15.101,  
> Subpart J
> of part 2 namely 2.906.
>
> It should also be noted that testing for DoC must be done not only  
> by an
> accredited lab but ONLY by an accredited lab having an MRA with the  
> US or on
> US soil.
>
> Thanks
>
> Dennis Ward
> Director of Engineering
> American TCB
> Certification Resource for the Wireless Industry www.atcb.com
> 703-847-4700 fax 703-847-6888
> direct - 703-880-4841
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of  
> Reginald
> Henry
> Sent: Wednesday, April 01, 2009 1:39 PM
> To: [email protected]
> Subject: FCC ** LOGO vs Verification Label RequirementT***
>
>
> All,
>
> Every few years I am asked this question.
>
> When should the FCC Logo be applied to a product vs. the FCC  
> Statement .
>
> As I recall if the product is...
>
> 1) Meant for commercial use
> 2) An unintentional radiator
> 3) tested to be verified ( results of tests NOT maintained by the  
> FCC )
>    by an independent lab to meet the FCC requirements
>
> IF ALL ABOVE IT TRUE THEN... the FCC statement (should be applied  
> to the
> product and the manual.
>
>
> PLEASE GIVE ME YOUR INPUT ON THIS ?
>
>
> Best Regards,
> Reg Henry
> Reginald Henry
> Electrical Engineer
> Tel: (631) 952-2288    Ext: 310
> Tel: (800) 645-9116    Ext: 310
> Web:  <http://www.vicon-cctv.com/>
>
>
>
>
> CONFIDENTIALITY NOTICE: This transmission may contain information  
> that is
> privileged, confidential and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you  
> are hereby
> notified that any disclosure, copying, distribution, or use of the
> information contained herein (including any reliance thereof) is
> strictly prohibited. If you receive this transmission in error, please
> immediately contact the sender and destroy the material in it's
> entirety,whether in electronic or hard copy format. The views  
> expressed in
> this
> communication may not necessarily be the views held by the company.
> Thank you.
>
> -
> ----------------------------------------------------------------
> 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.ieeecommunities.org/emc-pstc
> 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]>
>
> -
> ----------------------------------------------------------------
> 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.ieeecommunities.org/emc-pstc
> 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]>
>
> -
> ----------------------------------------------------------------
> 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.ieeecommunities.org/emc-pstc
> 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]>

-

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.ieeecommunities.org/emc-pstc
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