Ron,
 
I suppose there are some applications using 13.56 for data communication only
and not for power transfer and it looks for me that 302 291 with its 25dBuA/m
limit addresses that applications only.
RFID uses 13.56 for data and power transfer.
300 330-1 v1.7.1 addresses that in Table 5 specifying 60dBuA/m for 13.56 with
"NOTE 2: For RFID and EAS applications only."
 
If ETSI wonted to move 13.56 RFID from 300 330 to 302 291 than I suppose:
1. There would be something like NOTE 2 in 302 291-1 v1.1.1 (2005-07)
2. There wouldn't be that Note in 300 330-1 v1.7.1 (2010-02)
3. In the title of the 302 291 there wouldn't be "Data Communication
equipment" but "inductive loop systems" like in 300 330.
 
For me 'inductive loop systems' transfer data and power but 'data
communication equipment' transfer only data so it looks clear for me that 302
291 don't covers RFID applications with tags powering themselves from 13.56
field.
 
Best regards.
 
Piotr Galka
MicroMade
Poland
 
 

        ----- Original Message ----- 
        From: Ron Pickard <mailto:[email protected]>  
        To: Piotr Galka <mailto:[email protected]>  ; EMC-PSTC
<mailto:[email protected]>  
        Sent: Tuesday, October 04, 2011 9:52 PM
        Subject: Re: EN 300 330-1v1.7.1, RFID sidebands versus Spurious

        Piotr,
        For that frequency, you might instead want to look at EN 302291.
        
        Best regards,
        Sent from my DROID


        -----Original message-----
        

                From: Piotr Galka <[email protected]>
                To: EMC-PSTC <[email protected]>
                Sent: Tue, Oct 4, 2011 19:17:54 GMT+00:00
                Subject: EN 300 330-1v1.7.1, RFID sidebands versus Spurious
                
                
                I'm a designer who wants to understand measurements.
                 
                The device is 13,56MHz RFID short range (5cm) reader.
                Sidebands measurement:
                In 7.4.2 I read: "The transmitter shall be modulated with 
standard test
modulation...."
                Spurious emission measurement:
                In 7.5.3.1 I read: "The equipment under test shall be switched 
on with
normal modulation....."
                 
                Then according to Annex G the sidebands limit for 13,59MHz + 
900kHz and more
is -16dBuA/m and for spurious emission in the same frequency range the limit
is -3.5dBuA/m (7.5.3.2 Table 8).
                 
                Tell me please how to distinguish sideband from spurious (if 
both are
measured with modulation switched on) to know which limit to apply ?
                Do I have to look if the same is on the right and left of 13,56 
than
-16dBuA/m and if only on one sight then -3.5dBuA/m ?
                If it is to be done that way than what is the logic behind 
saying that for
example signal 16,56MHz is more danger for other devices if there is also the
same amplitude signal at 10,56MHz (limit -16dBuA/m) then if there is no signal
at 10,56MHz (limit -3.5dBuA/m) ?
                 
                In 6.5 I read: "there should preferably be a facility to 
operate the
transmitter in an unmodulated state", but I didn't found the measurement when
I will have to set my reader to work with unmodulated field.
                 
                What am I missing?
                 
                Best regards
                 
                Piotr Galka
                MicroMade
                Poland
                 
                -
                ----------------------------------------------------------------
                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]> 

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

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