The amplitude of signal source may not need calibration because you calibrate
the field at the end with calibrated probes.
You should at least check or get the signal generator calibrated if your
verification procedure is not checking (characterizing) the modulation.
EN 61000-4-3 gives some hints about amplitude modulation but the other
modulation types can be difficult to measure (Pulse, burst, phase etc.)
OOO (Own opinions only)
Best regards,
Deniz Demirci
National Technical Systems (NTS Canada)
Phone: 403-568-6605 ext 244
fax: 403-568-6970
email:[email protected]
web: http://www.ntscorp.com/about/locations
From: [email protected] [mailto:[email protected]] On Behalf Of Ken Javor
Sent: Tuesday, August 10, 2010 7:05 AM
To: Wendy Nya; Untitled
Subject: Re: Calibration supplier for signal generator with pulse modulation
Why would the signal source need calibration? Normally, it is the signal
measurement devices that require calibration. Further, this signal source
likely requires some amplification in order to provide the required signal
for EMI testing, so that it is the amplified output which must be measured,
not the signal generator itself.
Ken Javor
Phone: (256) 650-5261
> From: Wendy Nya <[email protected]>
> Date: Tue, 10 Aug 2010 01:23:29 -0700 (PDT)
> To: <[email protected]>
> Subject: Calibration supplier for signal generator with pulse modulation
>
> Dear All,
>
> I am looking for a calibration supplier that can provide accredited service
> for
> AR SG6000. It hasĀ built-in pulse modulation option (for Radiated Immunity
> use).
>
> By the way - Is anyone using this model? It seems to be OEM from Agilent (it
> came in an agilent box) but the equipment is marked AR
> and works with Agilent N5181A driver. Agilent is saying that it is not able
to
> provide accredited calibration service for this model.
>
> Thanks & Regards,
> Wendy Nya
>
>
>
>
> -
> ----------------------------------------------------------------
> 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]>