Ralph,

ANSI C63.4 also has the procedure:  Section 4.1.2 and Annex E.

In short, it's a verification of the LISN impedance and insertion loss 
characteristics.  Typically this requires a network analyzer to perform the 
verification. 

Also,  if you use AC line filters on the line side of the LISN those should be 
part of the LISN impedance characterization (no AC mains connected naturally).

Regards,

Dave Spencer
EMC Engineer
Xerox Corp. 


From: [email protected] [mailto:[email protected]] On Behalf Of Ralph McDiarmid
Sent: Tuesday, January 27, 2009 12:41 PM
To: [email protected]
Subject: RE: Calibration Standards for LISN

I don't have a copy of CISPR 16 to reference and so I am curious about how one 
calibrates an AMN? (or an antenna for that matter).  I can see characterizing 
the AMN so that its transducer factor versus frequency is known and can be then 
used to calculate a uV level.


Ralph McDiarmid, AScT 
Compliance Engineering Group 
Xantrex Technology Inc



From: [email protected] [mailto:[email protected]] On Behalf Of John Woodgate
Sent: Tuesday, January 27, 2009 5:22 AM
To: [email protected]
Subject: Re: Calibration Standards for LISN

In message 
<[email protected]>, dated 
Tue, 27 Jan 2009, Grace Lin <[email protected]> writes:

>For LISN calibration, what are the calibration standards that I should 
>fill in in the questionaire requested by a calibration lab?  Are ANSI 
>C63.4, CISPR 15, and CISPR 22 appropriate?  These are three test 
>standards I use most.

No, LISN calibration is in CISPR 16-1-2, where they are called 
Artificial Mains Networks (AMNs). See clause 4 and Annex A.

It is a good move to get your LISNs calibrated. Recent experience at a 
test house showed significant differences between supposedly good LISNs.
-- 
OOO - Own Opinions Only. Try www.jmwa.demon.co.uk and www.isce.org.uk
Things can always get better. But that's not the only option.
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK

-

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