53200A Manual
53200A Manual
User’s Guide
Notices U.S. Government Rights Warranty
The Software is “commercial computer THE MATERIAL CONTAINED IN THIS
Copyright Notice software,” as defined by Federal Acqui- DOCUMENT IS PROVIDED “AS IS,”
sition Regulation (“FAR”) 2.101. Pursu- AND IS SUBJECT TO BEING
© Keysight Technologies 2011–2020 ant to FAR 12.212 and 27.405-3 and CHANGED, WITHOUT NOTICE, IN
No part of this manual may be repro- Department of Defense FAR Supple- FUTURE EDITIONS. FURTHER, TO THE
duced in any form or by any means ment (“DFARS”) 227.7202, the U.S. MAXIMUM EXTENT PERMITTED BY
(including electronic storage and government acquires commercial com- APPLICABLE LAW, KEYSIGHT DIS-
retrieval or translation into a foreign puter software under the same terms CLAIMS ALL WARRANTIES, EITHER
language) without prior agreement and by which the software is customarily EXPRESS OR IMPLIED, WITH REGARD
written consent from Keysight Technol- provided to the public. Accordingly, TO THIS MANUAL AND ANY INFORMA-
ogies as governed by United States and Keysight provides the Software to U.S. TION CONTAINED HEREIN, INCLUD-
international copyright laws. government customers under its stan- ING BUT NOT LIMITED TO THE
dard commercial license, which is IMPLIED WARRANTIES OF MER-
Trademarks embodied in its End User License CHANTABILITY AND FITNESS FOR A
Microsoft and Windows are U.S. Agreement (EULA), a copy of which can PARTICULAR PURPOSE. KEYSIGHT
registered trademarks of Microsoft be found at http://www.keysight.com/ SHALL NOT BE LIABLE FOR ERRORS
Corporation. find/sweula. The license set forth in the OR FOR INCIDENTAL OR CONSE-
EULA represents the exclusive authority QUENTIAL DAMAGES IN CONNECTION
Manual Part Number by which the U.S. government may use, WITH THE FURNISHING, USE, OR
modify, distribute, or disclose the Soft- PERFORMANCE OF THIS DOCUMENT
53220-90001 ware. The EULA and the license set OR OF ANY INFORMATION CON-
forth therein, does not require or per- TAINED HEREIN. SHOULD KEYSIGHT
Edition mit, among other things, that Keysight: AND THE USER HAVE A SEPARATE
Edition 3, April 30, 2020 (1) Furnish technical information WRITTEN AGREEMENT WITH WAR-
related to commercial computer soft- RANTY TERMS COVERING THE MATE-
Printed in: ware or commercial computer software RIAL IN THIS DOCUMENT THAT
Printed in Malaysia documentation that is not customarily CONFLICT WITH THESE TERMS, THE
provided to the public; or (2) Relinquish WARRANTY TERMS IN THE SEPARATE
Published by: to, or otherwise provide, the govern- AGREEMENT SHALL CONTROL.
ment rights in excess of these rights
Keysight Technologies
customarily provided to the public to Safety Information
Bayan Lepas Free Industrial Zone,
use, modify, reproduce, release, per-
11900 Penang, Malaysia
form, display, or disclose commercial CAUTION
Technology Licenses computer software or commercial com-
puter software documentation. No A CAUTION notice denotes a hazard. It
The hardware and/or software additional government requirements calls attention to an operating proce-
described in this document are fur- beyond those set forth in the EULA dure, practice, or the like that, if not
nished under a license and may be shall apply, except to the extent that correctly performed or adhered to,
used or copied only in accordance with those terms, rights, or licenses are
the terms of such license. could result in damage to the product
explicitly required from all providers of or loss of important data. Do not pro-
commercial computer software pursu-
Declaration of Conformity ant to the FAR and the DFARS and are
ceed beyond a CAUTION notice until
Declarations of Conformity for this set forth specifically in writing else- the indicated conditions are fully
product and for other Keysight prod- where in the EULA. Keysight shall be understood and met.
ucts may be downloaded from the under no obligation to update, revise or
Web. Go to http://www.keysight.com/ otherwise modify the Software. With
go/conformity. You can then search by respect to any technical data as WARNING
product number to find the latest Dec- defined by FAR 2.101, pursuant to FAR
laration of Conformity. 12.211 and 27.404.2 and DFARS A WARNING notice denotes a hazard. It
227.7102, the U.S. government calls attention to an operating proce-
acquires no greater than Limited Rights dure, practice, or the like that, if not
as defined in FAR 27.401 or DFAR correctly performed or adhered to,
227.7103-5 (c), as applicable in any could result in personal injury or death.
technical data. Do not proceed beyond a WARNING
notice until the indicated conditions are
fully understood and met.
Certification
Keysight Technologies certifies that this product met its published specifications
at time of shipment from the factory. Keysight Technologies further certifies that
its calibration measurements are traceable to the United States National Institute
of Standards and Technology, to the extent allowed by the Institute's calibration
facility, and to the calibration facilities of other International Standards
Organization members.
Exclusive Remedies
The remedies provided herein are the customer's sole and exclusive remedies.
Keysight Technologies shall not be liable for any direct, indirect, special,
incidental, or consequential damages, whether based on contract, tort, or any
other legal theory.
Safety Symbols
The following symbols on the instrument and in the documentation indicate
precautions which must be taken to maintain safe operation of the instrument.
General
Do not use this product in any manner not specified by the manufacturer. The
protective features of this product may be impaired if it is used in a manner not
specified in the operation instructions.
Fuses
The Keysight 53220A/53230A is provided with an internal line fuse appropriate for
the line voltages listed on the instrument. This fuse is not user accessible.
In case of damage
Instruments that appear damaged or defective should be made inoperative and
secured against unintended operation until they can be repaired by qualified
service personnel.
Protection limits
The Keysight 53220A/53230A 350 MHz Universal Frequency Counter/Timer
provides protection circuitry to prevent damage to the instrument and to protect
against the danger of electric shock, provided the Protection Limits are not
exceeded and the instrument is properly grounded. To ensure safe operation of
the instrument, do not exceed the Protection Limits defined on the front panel:
Channel / Setup
Product Options 201/202 add parallel Channel 1 and Channel 2 inputs to the
WARNING rear panel of the instrument. Signals on the center conductor of either
panel’s channel BNCs are also present on the corresponding center
conductor of the BNC on the opposite panel.
Battery operation
When operating the 53220A or 53230A under battery power (Option 300), failure
to observe the following warnings may result in damage to the instrument,
electric shock, and serious personal injury:
Under battery power, the instrument chassis may float to the potential of the
WARNING measured signal supplied by the user.
Product category:
With reference to the equipment types in the WEEE directive Annex 1, this
instrument is classified as a “Monitoring and Control Instrument” product.
The affixed product label is as shown below.
Software Updates/Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Exclusive Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Lithium Battery Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Before applying power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ground the instrument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Do not operate in an explosive atmosphere . . . . . . . . . . . . . . . . . . . . 6
Do not operate near flammable liquids . . . . . . . . . . . . . . . . . . . . . . . . 7
Do not remove the instrument cover . . . . . . . . . . . . . . . . . . . . . . . . .7
Do not modify the instrument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
In case of damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Cleaning the instrument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Protection limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing the instrument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Battery operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Waste Electrical and Electronic Equipment (WEEE) Directive . . . . . . .10
Product category: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Sales and Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
8 Instrument Status
Keysight 53220A/53230A Status System . . . . . . . . . . . . . . . . . . . . . .279
Questionable Data Register Group . . . . . . . . . . . . . . . . . . . . . . . . .279
Standard Operation Register Group . . . . . . . . . . . . . . . . . . . . . . . .280
Standard Event Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
Status Byte Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282
A 53220A/53230A
Error Messages
Index
Welcome. This user’s guide contains configuration and operating information for
the Keysight 53220A/53230A 350 MHz Universal Frequency Counter/Timer.
The 53220A/53230A is a 2U, 1/2-module width LXI Class C instrument. The 2U,
1/2-module width references refer to the 53220A/53230A’s physical size relative
to standard EIA rack cabinet dimensions. LXI, an acronym for LAN eXtensions for
Instrumentation, is an instrumentation standard for devices that use the Ethernet
(LAN) as their primary remote communications interface.
21
1 Preparation for Use
N10149
Ext Ref In Gate In/Out Opt 010 UOCXO
Opt 106/115
Opt 300 Battery
Opt 150 sw
IECS / NMB-001
(53230A Only)
Line
100-240V, 50-60 Hz
100-127V, 400 Hz
Int Ref Out Trig In USB LAN 90VA Max Intertek
ISM 1-A
C D
Front panel
The shaded areas of the front panel represent keys that perform similar functions.
These areas are briefly described below.
A. Measure keys - display soft key menus from which the measurement function
is selected. Auto Scale senses the input signal (greater than 100 Hz) on input
channel 1, 2, or 3 and automatically sets the range and input threshold required to
make the selected measurement. Counter measurements are covered in
Chapter 3.
B. View keys - select how measurement data is displayed on the front panel.
Display configuration is covered later in this chapter. Graphics, math, and data
logging are covered in Chapter 6.
C. System keys - provide instrument-wide configuration which includes setting
the counter preset state and access to utility functions and to the counter’s
built-in help system. For measurement configuration involving numeric entry,
Shift changes the key definitions to the numbers at the lower left of the keys.
D. Channel keys - select the input channel and displays the soft key menu used to
configure the input signal path. Note that Figure 1-1 includes Channel 3 Option
106/115. Signal path configuration is covered in Chapter 4.
E. Gate and Trigger keys - select the gating and triggering soft key menus used
to control the measurement. Gating and triggering are covered in Chapter 5.
F. Soft keys - are the menus from which the counter is configured. The menus and
soft keys themselves are defined by the “functional” keys described above.
G. Power/Stand by button - switches the instrument between ‘on’ and ‘off’, or
between ‘on’ and ‘standby’.
Standby power (when enabled) is provided by the line voltage or Battery Option
300 and is used to maintain the temperature of the oven-controlled crystal
oscillator (OCXO) - Option 010. See “Applying Power” in this chapter for more
information.
H. USB ‘Host’ Port - available for transferring measurement data and instrument
configurations between the counter and a USB storage device. The front panel
port is for information transfer only. The rear panel USB port is used for
instrument (I/O) control. Data flow is covered in Chapter 7.
Rear panel
The 53230A rear panel shown in Figure 1-1 includes product Option 201 (parallel
rear panel inputs) and GPIB interface Option 400. The rear panel terminals are
briefly described below.
A. Parallel Rear Panel Inputs - product Options 201 and 202 add parallel inputs
on the rear panel. Note that these ARE NOT separate inputs. Signals on the center
conductor of either panel’s channel BNCs are ALSO present on the opposite
panel’s center conductor. Signal path configuration is covered in Chapter 4.
B. Ext Ref In - is the connector for providing an external reference oscillator
signal. Valid external refererence oscillator (time base) frequencies are 1, 5, and
10 MHz.
Int Ref Out - is the connector for accessing the counter’s internal 10 MHz
reference oscillator. The oscillator signal is a 0.5 Vrms (into 50 Ω) sine wave.
Reference oscillator usage and configuration are covered in Chapter 3.
C. Gate In/Out - is an input for external gate signals, and an output for routing the
counter’s internal gate to other devices. Additional information on this connector
is covered in the section “Enabling Gate Signals on the ‘Gate in/Out’ BNC” in
Chapter 5.
Trig In - is the connector for supplying an external trigger signal to the counter.
Triggering is covered in Chapter 5.
D. USB and LAN - are the standard input/output (I/O) ports. Configuration of
these ports and the GPIB interface is covered in Chapter 2.
Display
The layout of the 53220A/53230A display is shown in Figure 1-2.
Main Measurement
Main Measurement Display
Secondary Measurements
Data Entry Area
Materials included
The following accessories are shipped standard with the 53220A/53230A counter:
1 Power cord
2 USB cable
3 Keysight I/O Libraries Suite CD-ROM
4 Keysight 53210A/53220A/53230A Product Reference CD-ROM
Additionally, your instrument may have shipped with one or more of the following
options installed.
Each of the product options listed in Table 1-1 is available after the original
NOTE purchase of the instrument. Refer to the 53210A/53220A/53230A Service Guide
(p/n 53220-90010) for installation instructions for each of these options.
No manuals?
There are three printed manuals available with the 53220A/53230A:
– Keysight 53220A/53230A Quick Start Tutorial (p/n 53220-90005)
– Keysight 53220A/53230A User’s Guide (p/n 53220-90001)
– Keysight 53210A/53220A/53230A Service Guide (p/n 53220-90010)
53220A/53230A Option 0B0 (delete printed manuals) is the default product
documentation option. If Option 0B0 was ordered, only the Quick Start Tutorial
and 53210A/53220A/53230A Product Reference CD-ROM are shipped with the
instrument. All manuals are available on the CD. To obtain printed manuals from
Keysight, contact your Keysight representative.
Use care when moving the counter from cold to warm conditions as condensation
may develop. Ensure that any condensation has evaporated and that the counter
has thermally stabilized before turning on the instrument.
Electrical requirements
The electrical (power) requirements of the 53220A/53230A are summarized
below.
Line voltage and frequency are sensed at power on and no input power
adjustments (e.g. fuse changes, line voltage selection) are required.
Applying Power
Connect the power cord and press the “on/standby” button on the front panel
( ). During the power-on sequence the counter performs an auto-calibration
and self-test which includes:
If the 53220A/53230A does not turn on when the on/standby button is pressed,
NOTE verify AC power is available to the instrument and that the power cord is
securely connected. If the instrument still does not turn on, the cooling fan is not
audible, or if the front panel display is off when power is applied, return the unit
to Keysight for repair.
Standby power
The power modes of the 53220A/53230A counter are ‘on’ ‘off’, and ‘standby’. In
standby mode with the instrument connected to line voltage, standby power is
supplied to maintain the temperature within the ultra high-stability oven
controlled crystal oscillator (Option 010).
Battery Option 300 itself supplies standby power for the OCXO when the 53220A/
53230A is not connected to line voltage.
Refer to Chapter 3, "Standby power to the reference oscillator (Option 010)" for
information on enabling/disabling standby power.
Battery operation
Under battery power, the instrument chassis may float to the potential of the
measured signal supplied by the user.
With Battery Option 300 installed and enabled, the 53220A/53230A counter can
be operated using battery power for up to three hours.
Removing AC power when the battery is enabled switches the counter to battery
power automatically with no interruption of operation. Similarly, there is no
interruption in the transition back to line power, provided line power is
connected before the battery is d isabled.
Reading the battery level Pressing the Battery Level soft key or sending the
command:
SYSTem:BATTery:LEVel?
reads the battery charge (in percent) relative to a fully charged (100%) battery.
Battery in use The presence and status (enabled or disabled) of the battery is
indicated by a battery icon in the upper-right corner of the display (Figure 1-2).
Remotely, the instrument can be queried as to whether it is currently using AC
power or battery power with the command:
SYSTem:BATTery:STATus?
The command returns AC if the instrument is using line power, or BATT if using the
internal battery.
Battery care
When the battery is enabled and the instrument is not connected to AC power,
the battery discharges at 30% of full capacity per day. When the battery is
d isabled and AC power is not connected, the battery discharges at 10% of full
capacity per month.
When storing the instrument without AC power applied, do not allow the battery
to discharge below 10%. The following equation can be used to determine
instrument storage time without AC power - and still enable the instrument to be
fully recharged:
months battery disabled * 10% + days battery enabled * 30% = 90%
A fully discharged battery may need to be replaced if it has not been recharged for
six to 18 months.
Instrument help is available by pressing and holding any front panel key or
softkey. Pressing the Help key enables you to select additional help topics
including front panel measurement examples.
Utility Functions
Utility functions enable you to configure features of the instrument indirectly
related to measurement selection and configuration. These functions include:
– d isplay configuration - display control and numeric data formatting
– user interaction - localized language selection, audible indicators
– reference settings - time/date, measurement time out, time base,
auto-leveling, 53100 series emulation, NISPOM security
Display configuration
Measurements can be displayed in numerical or graphical form using the
following keys.
With AutoDigits On, the number of digits displayed is automatically set based on
gate time, measurement mode (AUTO, CONTinuous, RECiprocal - Chapter 3),
and resolution enhancement. When Off, the number of digits is set with the rotary
knob or [Shift]ed numeric keys. See Chapter 5, "Resolution and gate time" for
more information when AutoDigits On is set.
When Graph is selected, the data is displayed in a trend chart or histogram. Trend
charts and histograms are covered in Chapter 6.
Numeric Format
The format (radix, decimal group separator) of numeric data that appears in the
main measurement display (Figure 1-2) is set using the following keys.
The format also applies to numeric readings within trend charts, histograms, limit
testing, etc.
Radix The decimal separator (radix point) between the integer and fractional
parts of the reading can be a decimal point (.) or comma (,).
Digit group separator A digit group separator between every three digits on
either side of the decimal separator (radix) allows easier viewing of the displayed
reading. The separator can be one of the following:
None - there is no space between digits (e.g. 10.967342515 MHz)
Space - a space is inserted between every three digits
(e.g. 10.967 342 515 MHz)
On - a comma (,) or decimal point (.) is inserted between every three digits
depending on the decimal separator (radix) selected:
decimal point radix: 10.967,342,515 MHz
comma radix: 10,967.342.515 MHz
Screen control
Screen control is available through the keys shown below.
The display screen can be turned off to increase reading throughput and its screen
saver mode can be used to conserve power. Screen brightness can be adjusted
for optimal viewing in different environments.
Note that pressing any key with the display turned off, turns the display back on.
Screen capture
For documentation of product testing or as a convenience in gathering data, the
contents of the counter display can be captured and saved.
The keys related to this feature are shown below.
The content captured is the display state at the time the [Utility] key is pressed.
The file format is selectable as either bmp ( bitmap file format) or png (portable
network graphics (bitmap) format). Files may be store in internal flash memory or
to an external USB device.
See Chapter 7 for information on selecting paths and creating file names.
User interaction
The features described in this section are related to the user’s physical interaction
with the instrument.
Beeper Setting
Reference settings
Reference settings are counter settings that apply to all counter measurements.
The date and time settings for the counter’s real-time clock are set using the
commands:
SYSTem:DATE <year>,<month>,<day>
SYSTem:DATE? (query form)
SYSTem:TIME <hour>,<minute>,<second>
SYSTem:TIME? (query form)
The date and time range values are:
year: 2000‐2099 hour: 0‐23
month: 1‐12 minute: 0‐59
day: 1‐31 second: 0‐59.999
The real-time clock is battery-backed and retains the date and time when power
is off. There is no automatic setting of, or automatic return to the current date and
time.
Time base
53220A and 53230A measurements are based on a reference oscillator - also
referred to as an internal/external clock or time base. A valid reference oscillator
signal must be present for measurements to occur.
Refer to Reference Oscillator Configuration in Chapter 3 for detailed information
on selecting and configuring the reference oscillator source.
Auto level
The threshold level is the trigger (input) level at which the counter begins the
measurement. Auto-level is the automatic setting of this threshold based on the
positive and negative peaks of the input signal.
The minimum frequency at which auto-leveling can occur is set as shown.
Measurements
Chapter 3 Math and Graphs
Chapter 6
2 53220A/53230A Software
Installation and Interface
Configuration
Software Requirements 48
Using the Counter Web-Enabled Interface 49
Installing the Keysight IO Libraries 54
Firmware and Driver Updates 69
47
2 53220A/53230A Software Installation and Interface Configuration
Software Requirements
The environments available to program the 53220A/53230A are dependent upon
the IO libraries and drivers installed. The IO software included with the 53220A/
53230A is contained on the following CD:
– Keysight Automation-Ready CD: Keysight IO Libraries Suite
The IVI-C and IVI-COM drivers for the instrument can be found on the web at:
www.keysight.com/find/53220A or www.keysight.com/find/53230A
Table 2-1 summarizes the environments, IO driver recommendations, and the
location (media) where specific drivers and libraries can be found.
This section describes the Web pages and windows primarily used to program
NOTE the 53220A/53230A. Refer to “Help with this Page” associated with each Web
page for additional information on functions or pages not covered in this
manual.
Browser configuration
In some network configurations a proxy server may prevent access to the
instrument (i.e. “page cannot be displayed”) after the IP address is entered. In this
situation, the proxy must be configured from the browser such that the proxy is
not used for (IP) addresses within the range of those that can be assigned to the
53220A/53230A.
Although no additional libraries or drivers are required to use the Web interface,
NOTE the interface is also accessible from Keysight Connection Expert (KCE). See
“Opening the Web interface from Keysight Connection Expert” for more
information.
Web interface pages other than the ‘Welcome Page’ may be password
NOTE protected. When shipped from the factory no password is set; however, an ‘Enter
Password’ dialog box may appear. Click on the dialog box to continue.
If the page is password protected and the password is unknown, pressing
[Utility], (I/O Config), (LAN Reset) on the front panel clears the password.
Any command in the counter’s SCPI command set can be sent to the instrument.
Query commands which include ‘?’ in the syntax return data and can be sent by
selecting Send & Read after the command is entered. Commands which do not
return data are sent using Send Command.
The Keysight IO Libraries and utilities are often updated to include additional
NOTE features and improve usability. The figures used in this chapter represent the
latest version of the IO Libraries available at the time of printing. While you may
have a different version, the process of configuring and adding instruments to an
interface remains basically the same.
If the IO libraries installation does not start automatically, select Start > Run from
the Windows start menu and type <drive>:\autorun\auto.exe where
<drive> is the designator of the CD drive.
After the IO libraries have been installed, close the installation wizard. If
applicable, continue with instrument driver installation as described below.
Otherwise, continue with the ”Adding Instruments to the PC Interface” section of
this chapter.
The figures used in this chapter represent the latest version of the IO Libraries
NOTE available at the time of printing. While you may have a different version, the
process of configuring and adding instruments remains basically the same.
Once the IP address is known, start the Connection Expert utility by clicking the
‘Keysight IO Control’ icon and selecting “Keysight Connection Expert” from the
pop up menu as shown in Figure 2-3.
To search the network for the counter, click and select LAN Instrument
located on the Connection Expert tool bar. After selecting LAN Instrument,
Connection Expert performs an automatic find (Auto Find) of all instruments on
the same subnet as the computer.
Select the counter from the list and then click ‘OK’. Communication paths to the
instruments are verified and the instruments are added to the configured
interface. Instruments added to the LAN in this manner are subsequently
programmed using VXI-11 protocol.
Using the sockets protocol For higher performance, instruments added to the
LAN configuration can also use the Sockets protocol. To use this connection,
select LAN instrument from the (Figure 2-4). Next, select Enter Address. In
this window, enter the instrument’s host name or IP address and under Set
Protocol, select Socket (Figure 2-5). Note that an instrument can have both
VXI-11 and Sockets connections in the configuration.
Host names
The 53220A/53230A has a default host name. The format of the host name is:
A‐53220A‐nnnnn (Keysight 53220A)
A‐53230A‐nnnnn (Keysight 53230A)
where ‘nnnnn’ are the last five digits of the instrument’s serial number.
The instrument host name is reported by Connection Expert for network servers
that support Dynamic Domain Name Service (DNS). For network servers that do
not support Dynamic DNS, only the IP address is reported.
The first time the 53220A/53230A is connected to the PC via the USB cable, a
NOTE “hardware wizard” utility within the PC may start and prompt you for installation
software for the product. There is no installation software for the USB interface
other than the libraries on the Keysight Automation-Ready CD that ships with
the 53220A/53230A. Continue through the “wizard” application without
searching for software and using the default selections.
Figure 2-6 Setting a VISA alias for the USB address string.
To add instruments to the GPIB interface, click and select GPIB Instrument
on the Connection Expert tool bar (Figure 2-4). In the Add a GPIB Instrument
window that appears (Figure 2-7), select the counter’s GPIB address (note:
factory-set address = 3) and select OK.
Connection Expert will attempt to establish a communication path to the
instrument. If the counter is at the address specified, the instrument will be added
to the list of GPIB-configured instruments.
The counter’s GPIB address can be read from the front panel as shown below.
Using Interactive IO
The Connection Expert ‘Interactive IO’ utility provides another method (Table 2-1)
of sending commands to the 53220A/53230A. Interactive IO is accessible from
any of the PC’s IO interfaces, and allows you to send any command in the
53220A/53230A SCPI command set to the instrument. You can also choose from
a menu of IEEE-488 Common commands (e.g. *IDN?, *RST, *TST?).
Firmware updates are available from the LAN interface only. Note the IP address
NOTE before starting the utility.
3 Enter the counter’s IP address or host name (Figure 2-10). Select ‘Update’ to
start the update process.
The firmware update takes a few moments to complete. The 53220A/53230A will
reboot once the update is complete.
Following a firmware update, Keysight Connection Expert (if running) may report
NOTE that the 53220A/53230A configuration has changed. This is represented by a
yellow triangle and an exclamation point (!) next to the updated instrument.
Select the instrument name, select ‘Change Properties’, and then select either ‘Test
Connection’ or ‘Identify Instrument’ to update Connection Expert.
3 53220A/53230A
Measurements
Counter Measurement Summary 76
Reference Oscillator Configuration 78
Setting the Measurement Mode 83
Setting the Measurement Time Out 86
SCPI Syntax Conventions 87
The MEASure and CONFigure Commands 89
Frequency and Period Measurements 93
Time Interval Measurements 102
Totalizing Measurements 119
Burst Pulse Measurements 124
75
3 53220A/53230A Measurements
Freq CONFigure:FREQuency
Frequency 53220A/53230A 1,2,3
Period MEASure:FREQuency?
Freq CONFigure:FREQuency:RATio
Frequency ratio 53220A/53230A 1,2,3
Period MEASure:FREQuency:RATio?
Freq CONFigure:PERiod
Period 53220A/53230A 1,2,3
Period MEASure:PERiod?
Freq CONFigure:SPERiod
SPeriod 53220A/53230A 1,2
Period MEASure:SPERiod?
Freq CONFigure:FREQuency:BURSt 3
Burst carrier frequency 53230A
Period MEASure:FREQuency:BURSt? (Opt. 150)
Freq CONFigure:FREQuency:PRF 3
Pulse repetition frequency 53230A
Period MEASure:FREQuency:PRF? (Opt. 150)
Freq CONFigure:FREQuency:PRI 3
Pulse repetition interval 53230A
Period MEASure:FREQuency:PRI? (Opt. 150)
CONFigure:TINTerval
Time interval Time 53220A/53230A 1,2
Interval MEASure:TINTerval?
CONFigure:RTIMe
Rise time Time 53220A/53230A 1,2
Interval MEASure:RTIMe?
CONFigure:FTIMe
Fall time Time 53220A/53230A 1,2
Interval MEASure:FTIMe?
CONFigure:NDUTycycle
Negative duty cycle Time 53220A/53230A 1,2
Interval MEASure:NDUTycycle?
CONFigure:PDUTycycle
Positive duty cycle Time 53220A/53230A 1,2
Interval MEASure:PDUTycycle?
CONFigure:NWIDth
Negative pulse width Time 53220A/53230A 1,2
Interval MEASure:NWIDth?
CONFigure:PWIDth
Positive pulse width Time 53220A/53230A 1,2
Interval MEASure:PWIDth?
CONFigure:PHASe
Phase Time 53220A/53230A 1,2
Interval MEASure:PHASe?
CONFigure:TOTalize:CONTinuous
Totalize (continuous) Totalize 53220A/53230A 1,2
CONFigure:TOTalize:TIMed
Totalize (timed) Totalize 53220A/53230A 1,2
MEASure:TOTalize:TIMed?
Freq CONFigure:ARRay:TSTamp
Time stamp Period 53230A 1,2,3
MEASure:ARRay:TSTamp?
The reference oscillator (time base) is either the counter’s internal oscillator or the
internal oscillator tuned to an external reference. The source commands are:
[SENSe:]ROSCillator:SOURce {INTernal|EXTernal}
[SENSe:]ROSCillator:SOURce? (query form)
[SENSe:]ROSCillator:SOURce:AUTO {OFF|ON}
[SENSe:]ROSCillator:SOURce:AUTO? (query form)
The status of the external reference (time base) is also monitored by the counter’s
Questionable Data register. The register can be queried with the command:
STATus:QUEStionable:EVENt?
A value of +1024 (bit 10) indicates an invalid frequency (time base) error. Reading
the register clears all bits in the register. See Chapter 8 for information on the
counter’s status system.
There are three measurement modes available for making frequency, frequency
ratio, and average period measurements. The measurement mode is set using the
command:
[SENSe:]FREQuency:MODE {AUTO|RECiprocal|CONTinuous}
[SENSe:]FREQuency:MODE? (query form)
AUTO - configures the counter to make resolution-enhanced measurements when
possible, or reciprocal measurements otherwise depending on input signal
conditions. Channel 3 wide mode burst frequency measurements (PRF/PRI) are
made using resolution-enhanced (AUTO) mode only.
RECiprocal - configures the counter for reciprocal-only measurements. In
Reciprocal mode, the period of the input signal is measured and all frequency
readings are derived from (are the reciprocal of) the period measurement.
RECiprocal mode is not available on optional channel 3.
CONTinuous - configures the counter for continuous, resolution-enhanced,
gap-free measurements. These measurements are used by the counter's Allan
Deviation feature when estimating stability.
In CONTinuous mode a trigger count of ‘1’ is the only value allowed, and all
samples (readings) per trigger are taken within a single (hardware) gate open/
gate close sequence and computed back-to-back. There is no lag (dead time)
between readings that otherwise occurs with the per-sample gate open/gate
close sequence of the AUTO and RECiprocal modes.
1 2 3 4 5
start stop ...
edges required for reading subsequent readings based on number
determined by gate time of edges for first reading
Gate time/edge count The specified (or default) gate time and the input signal
frequency determine the number of edges required to produce the first reading in
the sample count. All subsequent readings in the count are based on the same
number of edges used for the first reading. Gate time is per reading.
Start/stop edge The edge that ends the gate time of the previous reading is the
same edge which starts the gate time (edge count) for the next reading. Because
the same edge is used as a start/stop edge, there is no gap/lag/dead time
between readings in CONTinous mode.
Input signal stability The stability of the input signal frequency during the
measurement can impact the counter's observable continuous (gap-free)
characteristic. As previously mentioned, all readings in the current reading count
are based on the number of edges required to complete the first reading which in
turn, are based on the specified or default gate time. If during measurements
before the sample count is reached the input frequency changes, the counter will
modulate the gate time of subsequent readings according to the frequency. The
edge count per reading as originally determined remains fixed and the readings
gap-free.
CONTinuous mode is available on channels 1 and 2 and optional channel 3 of the
53230A only, and only for frequency and average-period measurements.
Following a reset (*RST) or instrument preset (SYSTem:PREset or Preset key), the
measurement mode is set to AUTO. CONFigure and MEASure do not change the
mode.
Same subsystem For commands that share the same subsystem, multiple
commands can also be sent in a single string. The first command references the
root node, and subsequent commands separated by semicolons, are referenced to
the same level as the previous command. As an example, the command sequence
representing the CALCulate2 subsystem:
CALC2:TRAN:HIST:STAT ON
CALC2:TRAN:HIST:POIN 15
CALC2:TRAN:HIST:RANG:AUTO ON
CALC2:TRAN:HIST:RANGe:AUTO:COUNt 300
can be sent in a string as:
CALC2:TRAN:HIST:STAT ON;POIN 15;RANG:AUTO ON;AUTO:COUN 300
Using MEASure
Measurements using commands from the MEASure subsystem are made as the
command is executed, and are based on parameters specified within the syntax.
The results are sent to the instrument’s output buffer.
For example, the MEASure command:
MEAS:FREQ? 60.0, 1e‐3, (@1)
takes a single measurement with five digit (1 mHz) resolution of an expected
60 Hz signal on channel 1. All other counter parameters (input configuration,
trigger sources, etc.), are set to values predefined for the given MEASure
command, or remain unchanged from previously programmed values.
Because the measurement is taken immediately, changes to the counter
configuration are limited to the parameters within the command.
Using CONFigure
Measurements using commands from the CONFigure subsystem allow the use of
low-level commands to change counter parameters before the measurement is
taken. For example, assume the following configuration is required:
– frequency measurement
– external trigger - positive slope
– trigger count = 2
– sample count (readings per trigger) = 5
– gate time = 5 ms
The MEASure:FREQuency? command cannot be used since it immediately
triggers a measurement after setting the trigger source to ‘internal’, the trigger
count to ‘1’, and the sample count to ‘1’. The gate time is set to 0.1 seconds.
Using CONFigure and the appropriate low-level commands, the configuration can
be changed before the measurement is initiated (the abbreviated form of the SCPI
commands are shown):
//configure counter for frequency measurements
//change parameter values from those set by CONFigure
CONF:FREQ 1.0E6, (@2)
TRIG:SOUR EXT
TRIG:SLOP POS
TRIG:COUN 2
SAMP:COUN 5
SENS:FREQ:GATE:TIME 0.005
SENS:FREQ:GATE:SOUR TIME
INIT
Using CONFigure?
The following command:
CONFigure?
returns the measurement function configured by the last CONFigure or MEASure?
command sent to the instrument. Sending CONFigure? after power is cycled
generates a settings conflict error until CONFigure or MEASure? is sent.
For example:
CONF:FREQ 1.0E6, (@2)
CONF?
returns (including quotes):
"FREQ +1.00000000000000E+006,+1.00000000000000E‐004,(@2)"
which includes the function, expected value, (calculated) resolution, and channel.
If a channel number is not specified in the CONFigure or MEASure command, no
channel is included in the return string.
Frequency
90
tr tf
10 + width
- width
frequency
Notes
1 See Chapter 5 for information on triggering and number of readings per
trigger (sample count).
Frequency ratio
A frequency ratio measurement is the measurement of two signals in which one
signal generally serves as a reference (Figure 3-3). The signals can be different
wave shapes and applied to any 2-channel combination on the counter.
numerator channel
f1
denominator channel
f2
Notes
1 The digits of resolution in the above ratio measurements is set by the
resolution parameter (1.0E‐6, 1.0E‐9). In effect, the exponent corresponds
to the number of digits. See Frequency measurements in Chapter 5 for
information on the relationship between gate time and reading resolution.
2 See Chapter 4 for additional information on counter threshold levels and on
configuring the input signal path.
Period
90
tr tf
10 + width
- width
period
Notes
1 See Chapter 5 for information on triggering and number of readings per
trigger (sample count).
2 See Chapter 4 for additional information on counter threshold levels and on
configuring the input signal path.
Time stamp
Time stamp measurements record events (edges) as they occur on the counter
input channels. An example of time stamp measurements between the edges of
an input waveform is shown in Figure 3-5. (Time stamp measurements are
available with the 53230A only.)
scale factor = 2
Notes
1 In the example, 200 time stamp readings are taken at a 1 MHz rate and stored
in the counter’s reading memory. The readings are then stored on a USB drive
connected to the counter’s front panel “host” port as comma-separated values
(CSV), in one measurement per line ASCII format.
2 The data returned with time stamp measurements include a scale factor
followed by the time stamp values (in seconds) themselves. The scale factor,
which is the number of input cycles per time stamp, increases as the frequency
of the input signal becomes greater than the time stamp rate specified. Time
stamp values will either be the signal period itself (scale factor = 1 for input
frequencies < the time stamp rate), or the signal period multiplied by the scale
factor.
For example, a 10 MHz input signal and a 1 MHz time stamp rate might have a
scale factor of 11. The data for this measurement would be represented as:
1.10000000E+01 (scale factor: 11 cycles per time stamp)
1.10077637E‐06 (1st time stamp = signal period x scale factor)
1.09963867E‐06 (2nd time stamp = signal period x scale factor)
1.10005859E‐06 .
1.09999023E‐06 .
1.09988770E‐06 .
1.10017578E‐06 .
Dividing a time stamp value by the scale factor returns the input signal period
(e.g. 1.10077637E‐06 / 11 = 1.00070579E‐7).
3 See Chapter 4 for additional information on counter threshold levels and on
configuring the input signal path.
4 See Chapter 7 for information on data flow, reading memory, and on creating
data files.
Time interval
tim e interval
Ch. 1
C h. 2
tw o channel
Measurements taken without changing at least one of these settings could result
in values of approximately 0 seconds, as the measurement starts and stops on the
same edge (slope) at approximately the same time.
Notes
1 Auto-level is enabled on both channels to specify relative threshold levels of
10% of the peak-to-peak signal level. The measurement starts on a positive
(rising) edge on channel 1, and stops on a positive edge on channel 2.
2 A gate stop hold off is specified to select the desired rising edge on channel 2
and, therefore, the interval to be measured.
3 See Chapter 4 for information on input threshold levels and slope, and
Chapter 5 for advanced gating information.
1V
4 Vp-p
//configure a time interval measurement on ch.1. Use
//defaults as set by CONFigure except for those set as //shown
*RST // reset to start from known state
CONF:TINT (@1)
INP:COUP AC // set AC coupling
INP:IMP 50 // set input impedance to 50 ohm
INP:LEV1 1.0 // set start threshold to 1V
INP:LEV2 1.0 // set stop threshold to 1V
INP:SLOP1 POS // set start slope to positive (rising)
INP:SLOP2 NEG // set stop slope to negative (falling)
READ? // initiate counter and take reading
Notes
1 Input coupling and impedance are set to assure the intended start and stop
trigger thresholds as the thresholds are specified as absolute values. The
measurement starts on the positive (rising) edge on channel 1, and stops on
the negative (falling) edge.
An example of rise and fall times on an input signal are shown in Figure 3-8.
90
tr tf
10 + width
- width
frequency
The commands used to make rise and fall time measurements are:
MEASure:RTIMe? [{<lower_ref>|MINimum|MAXimum|DEFault}
[,{<upper_ref>|MINimum|MAXimum|DEFault}]] [,<channel>]
CONFigure:RTIMe [{<lower_ref>|MINimum|MAXimum|DEFault}
[,{<upper_ref>|MINimum|MAXimum| DEFault}]] [,<channel>]
MEASure:FTIMe? [{<lower_ref>|MINimum|MAXimum|DEFault}
[,{<upper_ref>|MINimum|MAXimum|DEFault}]] [,<channel>]
CONFigure:FTIMe [{<lower_ref>|MINimum|MAXimum|DEFault}
[,{<upper_ref>|MINimum|MAXimum| DEFault}]] [,<channel>]
– lower_ref and upper_ref specify the input signal reference level, either in
terms of percent of peak-to-peak voltage, or in absolute voltage. To specify
rise or fall time percentage levels from 10% to 90%, use a numeric value with
no suffix or with the suffix PCT (e.g. 30 or 30 PCT).
To specify rise or fall time levels in absolute voltage within the ranges:
5.125V range: -5.125V to +5.125V
51.25V range: -51.25V to +51.25V
use a numeric value with the V or MV (millivolt) suffix: 100 MV or .1V (spaces
allowed).
If either lower_ref or upper_ref is omitted or specified in percent, auto-leveling
is enabled. If specified in absolute voltage, auto-leveling is disabled
– channel is counter channel 1 or 2 specified as (@1) or (@2).
READ?
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// using MEASure? ‐ measure fall time using 15% and 65%
// references
*RST // reset to start from known state
MEAS:FTIM? 15PCT, 65PCT, (@2)
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// using CONFigure ‐ measure fall time on the wave segment // from
+1.25V to ‐1.4V
*RST // reset to start from known state
CONF:FTIM ‐1.4V, 1.25V, (@1)
INP:COUP DC // set DC coupling
INP:IMP 50 // set input impedance to 50 ohm
READ?
Notes
1 Lower and upper references can be specified as percentages or as absolute
levels in either the CONFigure or MEASure? command. For either rise time or
fall time measurements, the lower reference is specified first.
2 Absolute references are relative to the amplitude of the signal and must take
into consideration the counter’s input coupling and impedance settings.
3 See Chapter 4 for information on configuring the input signal path which
includes coupling and impedance.
Pulse width
An example of positive and negative pulse widths are shown in Figure 3-9.
90
tr tf
10 + width
- width
frequency
The commands used to make positive and negative pulse width measurements
are:
MEASure:PWIDth? [{<reference>|MINimum|MAXimum|DEFault}] [,<channel>]
CONFigure:PWIDth [{<reference>|MINimum|MAXimum|DEFault}] [,<channel>]
MEASure:NWIDth? [{<reference>|MINimum|MAXimum|DEFault}] [,<channel>]
CONFigure:NWIDth [{<reference>|MINimum|MAXimum|DEFault}] [,<channel>]
– reference specifies the threshold level where the width measurement begins.
For positive width measurements, the level at which the signal passes through
the threshold in the positive (rising) direction and again in the negative (falling
direction) defines the positive width. Similarly, the level at which the signal
passes through the threshold in the negative (falling) direction and again in the
positive (rising) direction defines the negative width.
To specify a threshold level from 10% to 90% of the peak-to-peak input voltage,
use a numeric value with no suffix or with the suffix PCT (e.g. 30 or 30 PCT).
To specify a threshold level in absolute voltage within the ranges:
5.125V range: -5.125V to +5.125V
51.25V range: -51.25V to +51.25V
use a numeric value with the V or MV (millivolt) suffix: 100 MV or .1V (spaces
allowed).
If reference is omitted or specified in percent, auto-leveling is enabled. If
specified in absolute voltage, auto-leveling is disabled
– channel is counter channel 1 or 2 specified as (@1) or (@2).
INP:COUP DC // set DC coupling
INP:IMP 50 // set input impedance to 50 ohm
READ?
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// using CONFigure ‐ measure negative width at ‐500 mV
// reference
*RST // reset to start from known state
CONF:NWID ‐500 MV, (@1)
INP:COUP DC // set DC coupling
INP:IMP 50 // set input impedance to 50 ohm
READ?
Notes
1 The reference (threshold) can be specified as a percentage of the peak-to-peak
amplitude or as an absolute level in either the CONFigure or MEASure?
command.
2 Absolute references are relative to the amplitude of the signal and must take
into consideration the counter’s input coupling and impedance settings.
3 See Chapter 4 for information on configuring the input signal path which
includes coupling and impedance.
Duty cycle
Positive and negative duty cycle measurements are the ratio of the positive or
negative widths to the period of the signal (Figure 3-10).
period
20%
+ duty cycle
50%
- duty cycle
80%
The commands used to make positive and negative duty cycle measurements are:
MEASure:PDUTycycle? [{<reference>|MINimum|MAXimum| DEFault}]
[,<channel>]
CONFigure:PDUTycycle [{<reference>|MINimum|MAXimum| DEFault}]
[,<channel>]
MEASure:NDUTycycle? [{<reference>|MINimum|MAXimum| DEFault}]
[,<channel>]
CONFigure:NDUTycycle [{<reference>|MINimum|MAXimum| DEFault}]
[,<channel>]
– reference specifies the threshold level where the duty cycle measurement
begins. For positive duty cycle measurements, the level at which the signal
passes through the threshold in the positive (rising) direction and again in the
negative (falling direction) defines the positive duty cycle. Similarly, the level at
which the signal passes through the threshold in the negative (falling) direction
and again in the positive (rising) direction defines the negative duty cycle.
To specify a threshold level from 10% to 90% of the peak-to-peak input voltage,
use a numeric value with no suffix or with the suffix PCT (e.g. 30 or 30 PCT).
To specify a threshold level in absolute voltage within the ranges:
5.125V range: -5.125V to +5.125V
51.25V range: -51.25V to +51.25V
use a numeric value with the V or MV (millivolt) suffix: 100 MV or .1V (spaces
allowed).
If reference is omitted or specified in percent, auto-leveling is enabled. If
specified in absolute voltage, auto-leveling is disabled
– channel is counter channel 1 or 2 specified as (@1) or (@2).
*RST // reset to start from known state
CONF:PDUT ‐1.0V, (@1)
INP:COUP DC // set DC coupling
INP:IMP 50 // set input impedance to 50 ohm
READ?
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// using CONFigure ‐ measure the negative duty cycle at a // 50% (0V)
reference
*RST // reset to start from known state
CONF:NDUT 50 PCT, (@1)
TRIG:SOUR EXT // set an external trigger source
INIT
Notes
1 The reference (threshold) can be specified as a percentage of the peak-to-peak
amplitude or as an absolute level in either the CONFigure or MEASure?
command.
2 Absolute references are relative to the amplitude of the signal and must take
into consideration the counter’s input coupling and impedance settings.
3 The measured duty cycle is a decimal representation of the ratio. For example,
a 5% duty cycle reading might appear in the counter output buffer as:
+5.105095730909666E‐002
The same reading would appear in the display as: 5.1 Pct.
4 See Chapter 4 for information on configuring the input signal path and
Chapter 5 for information on Triggering.
Phase
phase
Notes
1 If the phase format is CENTered, a typical phase measurement for signals 270°
out of phase for example, could be ‐9.10799485574691E+001. If the format
was POSitive, the phase difference measured might typically be
+2.68904450044343E+002.
2 Phase measurements represent the signal phase of the first channel relative to
the second channel in the pair. For example, if the phase format is CENTered
and the signal on channel 2 is delayed for a period equivalent to 90°, the
measurement will be 90° for the channel pair (@1),(@2). If under the same
signal conditions the channel pair were specified as (@2),(@1), the
measurement would be -90 degrees.
Single-period
Notes
1 For period-averaging measurements rather than single-period measurements,
use the MEASure:PERiod? or CONFigure:PERiod commands.
2 Setting an absolute threshold level disables the counter’s auto-level function.
CONFigure and MEASure enable auto-leveling at 50% (0V).
3 See Chapter 4 for information on input signal conditioning, including threshold
level and sensitivity.
Totalizing Measurements
The 53220A/53230A measurements covered in this section include gated and
continuous totalizing measurements.
Gated
Gated (timed) totalizing measurements count events (edges) that occur on the
channel over a specified period.
The relationship of the gate to the period input events are totalized is shown in
Figure 3-12.
input
...
events
Notes
1 In the program above (using CONFigure), the input signal on channel 1 whose
events (edges) are totalized is also applied to channel 2 as the gate signal.
Totalizing the positive edges begins on the same edge that opens the gate. A
gate stop hold off is set to extend the gate. For totalize measurements, the
holdoff starts when the gate opens. Setting a hold off of 1 second in effect,
sets a 1 second gate time. If the gate stop was not held off, the gate would
close after 1 event.
2 See Chapter 5 for additional information on triggering and gating.
Continuous
Continuous totalizing measurements count events (edges) that occur on the input
channel.
Similar to gated (timed) totalizing measurements, continuous measurements
begin when the measurement gate is opened (Figure 3-12). Rather than totalizing
for a specified gate time, continuous totalizing continues indefinitely until the
measurement is aborted, or cleared and restarted from the front panel.
The command used to make continuous totalizing measurements is:
CONFigure:TOTalize:CONTinuous [<channel>]
– channel is counter channel 1 or 2, specified as (@1) or (@2). (There is no
equivalent MEASure? command for continuous totalizing measurements.)
The command:
[SENSe:]TOTalize:DATA?
can be used during continuous totalizing or with long gate times to read the
current count.
Sending the command:
ABORt
aborts the measurement.
Notes
1 Pressing Clear Count on the front panel will not clear or abort continuous
measurements started from the LAN, USB, or GPIB interface. Pressing the
Back/Local key, however, will clear the count when the instrument transfers
from remote to local mode.
2 Continuous totalizing must be aborted (stopped) before the count can be
retrieved from the output buffer using the FETCh?, DATA:LAST?,
DATA:REMove?, or R? command (Chapter 7).
3 The ABORt command sent from the remote interface or changing the counter
function from the front panel stops continuous totalizing.
PRI / PRF
- 6 dB
p-p
amplitude
Carrier frequency
The commands used to measure the carrier frequency of a burst pulse are:
MEASure:FREQuency:BURSt? [<channel>]
CONFigure:FREQuency:BURSt [<channel>]
Notes
1 See Burst measurement detector threshold in Chapter 4 for information on
setting the threshold for pulse measurements.
2 See Burst carrier frequency measurements in Chapter 5 for information on
narrow pulse mode and on automatic and manual gate control for carrier
measurements.
The commands used to measure the pulse repetition interval (PRI) and pulse
repetition frequency (PRF) (Figure 3-13) of a burst signal are:
MEASure:FREQuency:PRI? [{<expected> | MINimum | MAXimum | DEFault}
[,{<resolution> | MINimum | MAXimum | DEFault}]] [,<channel>]
CONFigure:FREQuency:PRI [{<expected> | MINimum | MAXimum | DEFault}
[,{<resolution> | MINimum | MAXimum | DEFault}]] [,<channel>]
- expected is the expected interval. resolution is the desired measurement
resolution in seconds. The parameter ranges are:
expected: 100 ns to 1.0s (default = 0.001s)
resolution: 1.0E-15 * expected to 1.0E-5 * expected
(default resolution corresponds to a 0.1s gate time)
– channel is counter channel 3 specified as (@3).
MEASure:FREQuency:PRF? [{<expected> | MINimum | MAXimum | DEFault}
[,{<resolution> | MINimum | MAXimum | DEFault}]] [,<channel>]
CONFigure:FREQuency:PRF [{<expected> | MINimum | MAXimum | DEFault}
[,{<resolution> | MINimum | MAXimum | DEFault}]] [,<channel>]
– expected is the expected repetition frequency. resolution is the desired
measurement resolution in hertz. The parameter ranges are:
expected: 1 Hz - 10 MHz (default = 1 kHz)
resolution: 1.0E-15 * expected to 1.0E-5 * expected
(default resolution corresponds to a 0.1s gate time)
– channel is counter channel 3 specified as (@3).
// measure an expected 1 kHz pulse repetition frequency
// with 6‐digit (mHz) resolution
*RST // reset to start from known state
MEAS:FREQ:PRF? 1E3, .001, (@3)
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// measure the pulse repetition frequency using CONFigure, // set the
detector threshold to ‐6 dB
*RST // reset to start from known state
CONF:FREQ:PRI 1E3, .001, (@3)
INP3:BURS:LEV ‐6 // set a detector threshold of ‐6 dB
READ?
Notes
1 See Measurement Gate in Chapter 5 for information on digits of resolution
based on expected value and resolution parameter settings.
2 See Burst measurement detector threshold in Chapter 4 for information on
setting the threshold for pulse measurements.
The commands used to measure the positive (on) width and negative (off) width
of a burst pulse (Figure 3-13) are:
MEASure:PWIDth:BURSt? [<channel>]
CONFigure:PWIDth:BURSt [<channel>]
MEASure:NWIDth:BURSt? [<channel>]
CONFigure:NWIDth:BURSt [<channel>]
– channel is counter channel 3 specified as (@3).
// measure the positive (on) width using CONFigure, set
// a ‐12 dB detector threshold
*RST // reset to start from known state
CONF:PWID:BURS (@3)
INP3:BURS:LEV ‐12 // set a detector threshold of ‐12 dB
READ?
‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
// measure the negative (off) width of the burst signal
*RST // reset to start from known state MEAS:NWID:BURS?
(@3)
// measure the negative (off) width using CONFigure, set
// a ‐12 dB detector threshold
*RST // reset to start from known state
CONF:NWID:BURS (@3)
INP3:BURS:LEV ‐12 // set a detector threshold of ‐12 dB
READ?
Notes
1 See Burst measurement detector threshold in Chapter 4 for information on
threshold settings and its relationship to positive and negative width
measurements.
4 53220A/53230A Input
Signal Conditioning
Channel Characteristics 132
Signal Conditioning Path 133
Measuring Input Signal Levels and Signal Strength 152
This chapter contains information on configuring the input channels relative to the
characteristics of the input signal expected. Configuration includes the channel’s
impedance, range/probe factor, coupling, filtering, and threshold level/sensitivity
settings.
131
4 53220A/53230A Input Signal Conditioning
Channel Characteristics
There are two, plus an optional third input channel on the 53220A/53230A
counter. Product Option 201 adds parallel (additional) rear panel access to
channels 1 and 2. Product Options 106 and 115 add a 6 GHz or 15 GHz third
channel. Option 202 places third channel Option 106 / 115 on the front panel and
Option 203 places the third channel option on the rear panel.
If parallel channel 1 and channel 2 inputs are present on the rear panel (Option
NOTE 201), all input specifications apply to the rear terminals only, and are relative to
50W input impedance. Performance of the front panel inputs in this instance is
not specified. Also, when calibrating the instrument, the rear panel input
terminals are used.
Auto DC Coupling
Input
Cal Protection
Buffer
1M W AC Coupling
50W
Input
INPut{1|2}:COU Pling Selectable
100 kHz
IN Put{1|2}:IM Pedance Low-Pass Filter
IN Put{1|2}:PROTection? Range
IN Put{1|2}:PROTection:C LEar Selection
INPut{1|2}:FILTer
IN Put{1|2}:R ANG e
IN Put{1|2}:PROB e
Threshold Level
trigger / gating
and Sensitivity
IN Put{1|2}:LEVel{1|2}
SYSTem :ALEVel:FREQuency
IN Put{1|2}:LEVel:AU TO
IN Put{1|2}:LEVel{1|2}:RELative
IN Put3:BUR St:LEVel
IN Put{1|2}:NR EJect
IN Put{1|2}:SLO Pe{1|2}
Impedance 1 MΩ
Range (1:1 probe) 5V
Range (10:1) probe 50 V
Probe factor 1:1
Coupling AC
Low pass filter Off
Auto-level Enabled
Level (absolute) 0.0 V
Level (relative) 50%
Pulse Envelope (channel 3) -6 dB
Noise Rejection Disabled
Slope Positive
Input impedance
Using probes If using a 1:1 or 10:1 probe, the input impedance of the counter
should be set to match the compatibility (e.g. 50 Ω, 1 MΩ, high Z) of the probe.
See “Setting the probe factor” for more information.
Following a reset (*RST) or front panel preset (Preset), the impedance is set to
1 MΩ. CONFigure and MEASure do not change the input impedance setting.
Impedance example
//period measurement of expected 10 MHz signal,
//maximum resolution, use channel 1
CONF:FREQ 0.1E6,MAX,(@1)
INP:IMP 1.0E6 //set impedance to 1 Mohm
Input protection
The maximum input voltage (including any DC offset) allowed with 50 Ω input
impedance is ±5.125 Vp. If the input voltage exceeds ~ ± 10.0 Vp, the input
protection relay opens - changing the input impedance to 1 MΩ.. (The display and
Impedance softkey will still indicate a 50 Ω setting however.)
With the relay open, the corresponding channel key flashes until the input voltage
is removed or red uced below the damage threshold and the key is pressed. This
sets the impedance back to 50 Ω.
To programmatically determine if the protection relay has been opened, the
command:
INPut[{1|2}]:PROTection?
queries the relay state (0 = relay closed, 1 = relay open). With the input voltage
removed or red uced below the damage threshold, the protection relay is reset
(closed) with the command:
INPut[{1|2}]:PROTection:CLEar
setting the input impedance back to 50 Ω.
Voltage overload bit The opening of the input protection relay corresponds to
the ‘Voltage Overload’ bit (bit 0) being set in the counter’s Questionable Condition
and Questionable Event registers. The bit in the Condition register is cleared by
the INPut:PROTection:CLEar command or by changing the input impedance to
1 MΩ. The bit in the Event register is cleared by reading the register. See
Chapter 8, "Instrument Status" for more information.
Input range
The signal operating ranges (input ranges) of the 53220A/53230A counter are
±5.0 V, ±50 V,and ±500 V and are dependent on the probe factor. The range is set
using the command:
INPut[{1|2}]:RANGe {<range>|MINimum|MAXimum|DEFault}
INPut[{1|2}]:RANGe? [{MINimum|MAXimum|DEFault}](query form)
When a 1:1 probe factor is selected (see “Setting the probe factor”), the available
ranges are 5.0 V and 50.0 V. When a 10:1 probe factor is selected the available
ranges are 50.0 V and 500.0 V.
CONFigure and MEASure do not change the input range setting. Following a reset
(*RST) or a front panel preset (Preset), the range is set to 5.0 V.
Range example
//period measurement of expected 10 MHz signal,
//maximum resolution, use channel 1
CONF:PER 0.1E‐6,MAX,(@1)
INP:IMP 1E6 //set impedance to 1 Mohm
INP:RANG 50 //set 50V range
For better access to test points on the device under test (DUT), Keysight
recommends its N2870A, N2873A, and N2874A Passive Probes for use with the
53220A/53230A counter. The 35 MHz (BW) N2870A 1:1 probe and the 500 MHz
N2873A and 1.5 GHz N2874A 10:1 probes are popular accessories commonly
used with Keysight oscilloscopes.
When using probes with the counter, specifying a probe factor references and
displays threshold levels and p-p levels relative to actual levels on the DUT,
rather than to the level at the channel input. The probe factor is set with the
command:
INPut[{1|2}]:PROBe {<factor>|MINimum|MAXimum|DEFault}
INPut[{1|2}]:PROBe? [{MINimum|MAXimum|DEFault}]
(query form)
Probe factor settings are 1 for a 1:1 probe (N2870A), and 10 for a 10:1 probe
(N2873A or N2874A). When set to 1, the counter ranges are 5 V and 50 V. When
set to 10, the counter ranges are 50 V and 500 V.
Probe input compatibility The input compatibility of the N2870A and N2873A
probes is 1 MΩ respectively. The compatibility of the N2874A is 50 Ω. Each is
compatible with the counter’s 20 pF input capacitance. When using a probe, the
counter input impedance should be set accordingly (1MΩ, 50 Ω).
CONFigure and MEASure do not change the probe factor setting. Following a
reset (*RST) or an instrument preset (SYSTem:PRESet or Preset key), the probe
factor is set to 1.
Input coupling
AC coupling removes the signal’s DC content and centers the signal at 0 V. The
measurable frequency range (channels 1 and 2) with AC coupling is:
– AC = 10 Hz - 350 MHz
– DC = 1 mHz - 350 MHz
DC coupling extends the frequency range across the full bandwidth of the
instrument (1 mHz - 350 MHz). CONFigure and MEASure do not change the
coupling setting. Following a reset (*RST) or front panel preset (Preset), the
coupling is set to AC.
When selecting AC or DC coupling, the amplitude of the input signal must also be
considered. DC coupling is applicable for most measurements, especially those
requiring a specific trigger level. Rather than reducing the signal amplitude by
changing the counter range, AC coupling can be used to bring the signal in
contact with the hysteresis window defined by the trigger level. This is
represented in Figure 4-2 (also see “Threshold level and sensitivity”).
trigger point
programmed trigger level
reset point
VU VU
}
VC
} VC
VL VL
0V 0V
Hysteresis window
DC coupling AC coupling
Coupling example
//period measurement of expected 10 MHz signal,
//maximum resolution, use channel 1
CONF:PER 0.1E‐6,MAX,(@1)
INP:COUP AC //set AC coupling
For measurement applications of 100 kHz or less, a 100 kHz low-pass filter can be
enabled within the signal path to eliminate noise introduced by higher-frequency
components of the input signal.
The bandwidth filter is switched into the signal path using the command:
INPut[{1|2}]:FILTer[:LPASs][:STATe] {OFF|ON}
INPut[{1|2}]:FILTer[:LPASs][:STATe]? (query form)
On - enables the filter. OFF - disables the filter.
Figure 4-3 shows the effects on the instrument’s measurable frequency range
when the filter is enabled.
DC AC
The threshold level is the trigger (input) level at which the counter begins the
signal count (i.e. measurement). This level is the center of the hysteresis band -
the band which represents counter sensitivity. For a count to occur, the signal
must cross the upper and lower limits of the band in opposite directions
(polarities). Figure 4-4 identifies these characteristics and conditions of the input
signal. The dynamic range of the input signal is indicated on the front panel.
INPut{1|2}:LEVel{1|2}
SYSTem:ALEVel:FREQuency
INPut{1|2}:LEVel{1|2}:AUTO
INPut{1|2}:LEVel{1|2}:RELative
INPut3:BURSt:LEVel
INPut{1|2}:NREJect
trigger point
threshold level
VU
signal operating range
VC Hysteresis band
dynamic range
(p-p sensitivity)
VL
reset point
The input threshold level can be specified as an absolute value. An absolute level
is set with the command:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute] {<volts>|MINimum|
MAXimum|DEFault}
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]? [{MINimum|MAXimum|
DEFault}] (query form)
Using auto-level
Automatic setting of the input threshold level is based on the positive and
negative peaks of the input signal. Auto-level is enabled with the command:
INPut[{1|2}]:LEVel[{1|2}]:AUTO {OFF|ON|ONCE}
INPut[{1|2}]:LEVel[{1|2}]:AUTO? (query form)
OFF disables auto-leveling; ON enables auto-leveling. Auto-level ONCE
immediately sets an auto-level and then disables auto-leveling.
100%
(Vmax:)
100%
(Vmax:)
0%
(Vmin:)
0V
0%
(Vmin:)
DC coupling AC coupling
For example, a 3 Vpp input signal with a 2 VDC offset and DC coupling would
have a Vmax: value of 3.5V and a Vmin value of 0.5V (Vmax, Vmin, and Vpp are
viewable on the front panel). With AC coupling, Vmax and Vmin would be ±1.5V
respectively.
If a 30% relative threshold is specified for the DC-coupled signal described above,
the corresponding (absolute) value is 1.4 V. The same relative threshold for an
AC-coupled signal has an absolute value of -0.6 V.
The absolute value of any relative threshold level can be queried using:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]?
or computed as:
Vmin + (% threshold x Vpp)
level w/DC coupling: 0.5 + (0.30 x 3) = 1.4 V
level w/AC coupling: ‐1.5 + (0.30 x 3) = ‐0.6 V
Auto-leveling is available for two input frequency ranges: 50 Hz to < 10 kHz and
frequencies > 10 kHz. The auto-level period is shorter for frequencies >10 kHz
when an (auto-level) frequency range is set from the front panel or specified by
the command:
SYSTem:ALEVel:FREQuency {<frequency>|MINimum|MAXimum| DEFault}
SYSTem:ALEVel:FREQuency? [{MINimum|MAXimum|DEFault}]
(query form)
The frequency parameter values are:
Frequencies Frequencies
Interface
> 10 kHz 50 Hz to < 10 kHz
Front Panel Fast Slow
10.0E3 50.0
SCPI
Maximum MINimum
A frequency setting of 10 kHz decreases the auto-level period for all frequencies
>10 kHz. A frequency setting of 50 Hz provides auto-leveling for frequencies
down to 50 Hz. The frequency selected should be based on the lowest expected
frequency in the measurement.
The auto-level frequency is a system setting which applies to all counter
channels, and should be noted when making two-channel measurements.
The default setting is 50 Hz. The value is stored in non-volatile memory and does
not change when power is cycled or following a reset (*RST) or a front panel
preset (Preset). CONFigure and MEASure enable auto-level and set a relative
threshold of 50%, but do not change the auto-level frequency.
All 53230A burst measurements are relative to the pulse width. The ‘on’ portion of
the pulse width is established by a -6 dB and -12 dB detector threshold.
Figure 4-6 is an example of the thresholds relative to the peak amplitude of the
burst signal.
PRI / PRF
-6 dB (on) -6 dB (off)
- 6 dB
- 12 dB
p-p
amplitude
- 12 dB (on) - 12 dB (off)
The detector threshold and, therefore, the ‘on’ portion of the pulse width must be
considered when making burst measurements such as positive (on) width and
negative (off) width. This threshold is set with the command:
INPut3:BURSt:LEVel {<dB>|MINimum|MAXimum|DEFault}
INPut3:BURSt:LEVel? [{MINimum|MAXimum|DEFault}]
(query form)
The dB levels are -6 and -12, and are nominal (i.e. non-specified) values.
CONFigure and MEASure do not change the detector threshold setting. Following
a reset (*RST) or front panel preset (Preset), the threshold is set to -6 dB.
This command and burst measurement capability are only available on the
53230A counter with channel 3 Option 106 or 115 (6 GHz or 15 GHz microwave
input) and Pulse Microwave Measurement Option 150.
Threshold sensitivity (Figure 4-4) to the input signal is a function of the amount of
noise rejection or hysteresis. Noise rejection (the hysteresis band) at the counter
input is increased or decreased with the command:
INPut[{1|2}]:NREJection {OFF|ON}
INPut[{1|2}]:NREJection? (query form)
ON enables noise rejection, thus increasing hysteresis and decreasing sensitivity by
50%. This setting should be used when noise is present in the signal environment.
However, if the threshold level is close to a peak amplitude (positive or negative),
a count will not occur if the signal does not cross both hysteresis levels due to the
increased hysteresis band. OFF disables noise rejection which decreases
hysteresis and increases sensitivity.
CONFigure and MEASure do not change the noise rejection setting. Following a
reset (*RST) or instrument preset (Preset), noise rejection is disabled (off).
Noise rejection from bandwidth limiting For input signals up to 100 kHz,
reducing the counter’s bandwidth from 350 MHz to 100 kHz (see “Bandwidth
limiting (low-pass) filter”) also provides noise rejection. Additional noise rejection
for frequencies in this range is then obtained through INPut:NREJection ON.
Time interval errors Using noise rejection with time interval measurements
results in time interval errors due to errors in setting the threshold level and the
effects of hysteresis on the trigger and reset points (Figure 4-4). These errors are
dependent on the input signal slew rate at each trigger point.
Threshold slope
The slope (edge) of the input signal on which the threshold level occurs is
specified with the command:
INPut[{1|2}]:SLOPe[{1|2}] {POSitive|NEGative}
INPut[{1|2}]:SLOPe{1|2}]? (query form)
POSitive - the trigger point occurs on the positive (rising) edge. The reset point
occurs on the negative (falling) edge (Figure 4-4).
NEGative - the trigger point occurs on the negative edge, with the reset point
occurring on the positive edge.
The slope setting does not apply to pulse width, duty cycle, or rise/fall time
measurements (i.e. measurements with pre-defined slopes).
For single-channel time interval measurements, SLOPe/SLOPe1 sets the edge for
the start event and SLOPe2 sets the edge for the stop event.
CONFigure and MEASure do not change the slope setting. Following a reset
(*RST) or instrument preset (Preset), the positive (rising) slope is selected.
The relative signal strength on channel 3 Option 106 or 115 (6 GHz or 15 GHz
microwave input) is displayed on the counter and can also be measured with the
command:
INPut3:STRength?
The colors and the relative strengths returned by the command indicate the
following:
155
5 Triggering and Gating
Settings Summary
Table 5-1 is a summary of power-on/reset settings for the trigger and gating
parameters covered in this section.
Measurement
Gate Stop Enabled Complete
gate
Gate Start Enabled opens
Making measurement
Auto Gate
Input events received are ignored Gate enabled
Extension
The SCPI commands and parameters listed throughout this chapter are provided
NOTE as a guide to how the counter is operated programmatically. The commands are
described in detail in the ‘Programmer’s Reference’ section of the Keysight
53210A/53220A/53230A Product Reference CD.
System Trigger
ABORt
*RST Idle state
SAMPle:COUNt
Sample Count
INITiate:IMMediate
READ? Wait-for-trigger state Yes
MEASure?
No triggers received
=
TRIGger:COUNt?
trigger received
Yes
Triggered state
No # readings
=
SAMPle:COUNt?
SENSe:FREQuency:GATE:SOURce
TIME
SENSe:TOTalize:GATE:SOURce Gate Source
SENSe:TINTerval:GATE:SOURce IMMediate
EXTernal
EXTernal
SENSe:FREQuency:GATE:TIME
SENSe:GATE:EXTernal:SOURce External Gate Source SENSe:TOTalize:GATE:TIME
SENSe:TINTerval:GATE:SOURce IMMediate
BNC
INPut[1] | INPut2 *
(measurement complete)
(delay disabled)
SENSe:GATE:STARt:DELay:EVENts
(input channel)
SENSe:GATE:STARt:DELay:TIME (for all EXTernal Sources)
Gate stop source does not apply to rise/fall auto gate extension
time, duty cycle, pulse width, phase, and
single-period measurements (frequency and period measurements)
System Trigger
The counter operates in one of three states depending on the status of the system
trigger: idle, wait for trigger, and triggered.
Idle state
Counter configuration generally occurs while the instrument is in the idle state
(Figure 5-3). This includes configuration of the system trigger.
As shown, the counter is placed in the idle state by either of the following the
commands:
ABORt - aborts a measurement in progress.
*RST - resets the counter to its factory default values.
The counter also returns to the idle state after the total number of measurements
determined by the TRIGger:COUNt and SAMPle:COUNt settings are complete
(i.e. # of measurements = TRIGger:COUNt x SAMPle:COUNt).
ABORt
*R S T
Idle state
return to idle state w h en
(# rea ding s = T R IG g er:C O U N t x S A M P le:C O U N t)
T R IG ge r:S LO P e T rigg er S lo pe
S A M P le :C O U N t S am ple C ount
The system trigger is configured using the commands within the TRIGger and
SAMPle subsystems. Figure 5-3 show the sequence in which the commands are
commonly used.
The system trigger source which starts the trigger/gate cycle is set with the
command:
TRIGger:SOURce {IMMediate|EXTernal|BUS}
TRIGger:SOURce? (query form)
– trigger source IMMediate sets a continuous trigger signal. By default,
CONFigure sets the trigger source to IMMEDiate.
– trigger source EXTernal sets the trigger source to an external trigger applied
to the rear panel ‘Trig In’ BNC connector.
– trigger source BUS causes the instrument to be triggered by the *TRG
command received over an IO interface.
When the system trigger source is set to EXTernal, the triggering slope (edge) of
the signal is set with the command:
TRIGger:SLOPe {POSitive|NEGative}
TRIGger:SLOPe? (query form)
– trigger slope POSitive selects the signal’s rising edge, and trigger slope
NEGative selects the signal’s falling edge. The signal is applied to the
‘Trig In’ BNC. By default, CONFigure sets the trigger slope to NEGative.
The delay between receipt of the internal or external system trigger signal and the
start of the first measurement (Figure 5-1) is set with the command:
TRIGger:DELay {<time>|MINimum|MAXimum|DEFault}
TRIGger:DELay? [{MINimum|MAXimum|DEFault}] (query form)
– specifies the delay in seconds. Delays between subsequent measurements (i.e.
multiple readings per trigger - see SAMPle:COUNt) are set with the
SENSe:GATE:STARt:DELay commands. CONFigure and MEASure set a
default delay of 0.0 s.
The number of system triggers the counter will receive before returning to the idle
state from the wait-for-trigger state is set with the command:
TRIGger:COUNt {<count>|MINimum|MAXImum|DEFault}
TRIGger:COUNt? [{MINimum|MAXimum|DEFault}] (query form)
The trigger count range is 1 to 1,000,000. CONFigure and MEASure set a default
trigger count of ‘1’.
Sample count
The count range is 1 to 1,000,000. CONFigure and MEASure set a default sample
count of ‘1’.
Reading memory can store up to 1,000,000 readings. If the product of the trigger
count and the sample count is greater than 1,000,000 readings, data must be
read from reading memory fast enough to prevent memory overflow. If memory
does overflow, new readings will overwrite the first (oldest) readings stored. The
most recent readings are always preserved. See Chapter 8, "Instrument Status"
for information on monitoring reading memory count.
The trigger count and sample count are ignored when making continuous
NOTE totalize measurements. The trigger count is also ignored when making
continuous, gap-free frequency or period measurements. Only one trigger is
accepted when using these functions. See the ‘Programmer’s Reference’ section
of the Keysight 53210A/53220A/53230A Product Reference CD for more
information.
INITiate:IMMediate
READ?
W ait-for-trigger state
Yes
MEASure?
No triggers received
=
TRIGger:COUNt?
trigger received
Yes
Triggered state
No # readings
=
SAMPle:COUNt?
Initiating example
//configure for frequency, set system trigger parameters
CONF:FREQ 5E6,0.1,(@2)
TRIG:SOUR EXT // trigger source external
TRIG:SLOP POS // external trigger slope ‐ positive
TRIG:DEL 1 // 1s delay after trigger received
TRIG:COUN 2 // accept 2 system triggers
SAMP:COUN 100 // take 100 readings per system trigger
INIT // initiate the counter ‐ wait for trigger state
FETc? // retrieve measurements from reading memory
READ?
– equivalent to executing INITiate:IMMediate directly followed by FETCh?.
With READ?, readings are displayed, stored in reading memory, and
instantaneously read into the output buffer (see Chapter 7, "Formats and Data
Flow" for more information).
READ? example
//configure for frequency, set system trigger parameters
CONF:FREQ 5E6,0.1,(@2)
TRIG:SOUR EXT // trigger source external
TRIG:SLOP POS // external trigger slope ‐ positive
TRIG:DEL 1 // 1s delay after trigger received
TRIG:COUN 2 // accept 2 system triggers
SAMP:COUN 100 // take 100 readings per system trigger
READ? //initiate the counter ‐ fetch readings from memory
Once initiated, a valid trigger signal and a satisfied delay period (if specified)
moves the counter to the triggered state and the beginning of the gate cycle. The
counter remains in the triggered state until the sample count (readings per
trigger) is reached. The counter then returns to the wait-for-trigger state until the
next system trigger is received. The counter returns to the idle state once the
product of the trigger count x sample count is reached.
Measurement Gate
Control of the measurement gate allows you to select the duration of the
measurement. The gating sequence of the trigger/gate cycle begins after a
system trigger signal is received, and is repeated for each measurement specified
in the sample count.
The gate sequence occurs while the counter is in the triggered state
NOTE (Figure 5-2). Although shown in the figure after the counter is initiated, gate
configuration like system trigger configuration, occurs while counter is in the
idle state.
Gate set up
The counter’s gate source determines the path through the gate cycle and the
related parameters that must be considered. A gate source is required for all
frequency, totalizing, and time interval measurements.
Although selection of the gate source is shown at the beginning of the cycle
(Figure 5-2 and Figure 5-5), programmatically it should occur after all other gate
parameters have been set. This prevents potential “settings conflict” errors
between the SENSe subsystem commands, and is illustrated in the examples and
program segments that use these commands.
SENSe:FREQuency:GATE:SOURce TIME
SENSe:TOTalize:GATE:SOURce Gate Source
SENSe:TINTerval:GATE:SOURce IMMediate
EXTernal
INPut[1] | INPut2 *
* not available with time interval
Gate Start (open)
ADVanced
SENSe:FREQuency:GATE:TIME
SENSe:TOTalize:GATE:TIME
SENSe:TINTerval:GATE:SOURce IMMediate
(measurement complete)
(for all EXTernal Sources)
SENSe:FREQuency:GATE:POLarity
SENSe:TOTalize:GATE:POLarity
SENSe:TINTerval:GATE:POLarity
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]
Typical counter measurements and most applications use an internal signal as the
gate source to control the gate for a specified (or default) period of time.
For applications requiring synchronization with external events or requiring more
precise gate control, an external gate or advanced gating is used. External gate
signals are applied to the counter’s rear panel ‘Gate In/Out’ BNC or to the channel
1 or channel 2 input.
Frequency measurements
For frequency and period measurements the command used to set/change the
gate source is:
[SENSe:]FREQuency:GATE:SOURce {TIME|EXTernal|INPut[1]| INPut2|ADVanced}
[SENSe:]FREQuency:GATE:SOURce? (query form)
– gate source TIME is used to achieve a desired resolution in number of d igits. It
uses an internal gate signal and is the default gate source. It enables the gate
to remain open for a specified period while the input signal is measured. The
longer the gate time, the greater the resolution.
Table 5-2 shows the digits of resolution achieved with the 53230A and 53220A for
a given gate time. The table also includes formulas for estimating digits as a
function of gate time or expected values, and gate times as a function of digits.
1 sec up to 12* 10
gate time = (10^d igits) * Tss
10 sec up to 13* 11
100 sec up to 14* 12
1000 sec up to 15* 13
* Resolution Enhanced
Querying the gate time The gate time set by the expected value and resolution
parameters can be determined after execution of the CONFigure or
MEASure command.
For example, assume a measurement requiring 10-digit (mHz) resolution of a
5 MHz signal is required. Because digits of resolution is approximately equal to
Log10 (expected value) ‐ Log10 (resolution), this measurement could be
configured as:
MEAS:FREQ? 5e6, 5E‐4, (@1) // expected freq, resolution
A typical measurement using this configuration might return:
+4.99998458333282E+006
With the counter display registering:
4.999 984 583 3MHz (11 digits ‐ resolution enhanced)
Gate sources EXTernal, INPut[1], and INPut2 are external sources. EXTernal
is the counter’s rear panel ‘Gate In/Out’ BNC, and INPut[1]/ INPut2
(represented by softkeys Chan 1 and Chan 2) are the counter’s channel 1 and
channel 2 inputs.
When using any external gate source the polarity of the gate signal and therefore,
the duration of the gate, is set or changed with the command:
[SENSe:]FREQuency:GATE:POLarity {POSitive|NEGative}
[SENSe:]FREQuency:GATE:POLarity? (query form)
POSitive starts the measurement on a positive edge on the Gate In/Out BNC or
channel 1/channel 2 input, and stops the measurement on the next negative
edge. NEGative starts the measurement on a negative edge on the Gate In/Out
BNC or channel 1/channel 2 input, and stops the measurement on the next
positive edge.
CONFigure and MEASure do not change the polarity setting. Following a reset
(*RST) or instrument preset (SYSTem:PRESet or Preset key), the negative edge is
selected.
To set the polarity of the external gate signal:
// select the gate polarity and source
CONF:PER
SENS:FREQ:GATE:POL POS // set polarity
SENS:FREQ:GATE:SOUR EXT // set source
For external sources INPut[1] and INPut2 (Chan 1 and Chan 2 softkeys), a fixed
input threshold voltage must be specified in addition to the gate signal polarity.
This is done using the command:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]{<volts>|MINimum|
MAXimum|DEFault}
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]?[{MINimum|MAXimum|DEFault}]
(query form)
The specified edge (polarity) of the gate signal crossing the threshold opens the
gate. The opposite edge (polarity) of the signal crossing the threshold closes the
gate. (More information on the INPut subsystem can be found in CChapter 4,
"53220A/53230A Input Signal Conditioning".)
When using external sources INPut[1] and INPut2, the channel selected as the
gate source cannot be the same channel on which the measured signal is applied.
That is, the gate source channel cannot be involved in the measurement.
To set the polarity and level for an external gate source:
// select the gate polarity, source, and threshold level
CONF:FREQ
SENS:FREQ:GATE:POL POS // set polarity
SENS:FREQ:GATE:SOUR INP // set source ‐ channel 1
INP:LEV 4 // set threshold ‐ 4V
Totalizing
When using the external gate sources, the polarity of the gate signal and
therefore, the duration of the gate, is set or changed with the command:
[SENSe:]TOTalize:GATE:POLarity {POSitive|NEGative}
[SENSe:]TOTalize:GATE:POLarity? (query form)
POSitive starts totalizing on a positive edge on the Gate In/Out BNC or channel
1/channel 2 input, and stops totalizing on the next negative edge. NEGative
starts totalizing on a negative edge on the Gate In/Out BNC or channel 1/channel
2 input, and stops totalizing on the next positive edge.
CONFigure and MEASure do not change the polarity setting. Following a reset
(*RST) or instrument preset (SYSTem:PRESet or Preset key), the negative edge is
selected.
To set the polarity of the external gate signal:
// select the gate polarity and source
CONF:TOT:TIM
SENS:TOT:GATE:POL POS // set polarity
SENS:TOT:GATE:SOUR EXT // set source
For external sources INPut[1] and INPut2 (Chan 1 and Chan 2 softkeys), a fixed
input threshold voltage must be specified in addition to the gate signal polarity.
These parameters are set with the commands:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]{<volts>|MINimum|
MAXimum|DEFault}
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]?[{MINimum|MAXimum|DEFault}]
(query form)
The specified edge (polarity) of the gate signal crossing the threshold opens the
gate. The opposite edge (polarity) of the signal crossing the threshold closes the
gate.
When using sources INPut[1] and INPut2, the channel selected as the gate
source cannot be the same channel on which input events are totalized. That is,
the gate source channel cannot be involved with the measurement.
To set the polarity and level when using an input channel as the gate source:
// select the gate polarity, source, and threshold level
CONF:TOT:TIM
SENS:TOT:GATE:POL POS // set polarity
SENS:TOT:GATE:SOUR INP1 // set source ‐ channel 1
INP1:LEV 4 // set threshold ‐ 4V
Continuous totalizing
Reading the current count During continuous or timed totalizing with long
gate times, the current count can be read with the command:
[SENSe:]TOTalize:DATA?
For example:
CONF:TOT:CONT // configure continuous totalizing
INIT // start measurement
SENS:TOT:DATA? // query current count
ABOR // terminate measurements
For time interval measurements, the command used to set/change the gate
source is:
[SENSe:]TINTerval:GATE:SOURce {IMMediate|EXTernal| ADVanced}
[SENSe:]TINTerval:GATE:SOURce? (query form)
– gate source IMMediate uses an internal gate signal which starts the
measurement on the first event (edge/level) defined by the INPut subsystem,
and ends on the next (stop) event defined. The CONFigure commands set the
time interval gate source to IMMediate.
– gate source EXTernal is the counter’s rear panel ‘Gate In/Out’ BNC. Using an
external gate, the measurement begins on the first start event after the
external gate is received. The measurement ends following the stop event. The
start and stop events (edge/level) are defined by the INPut subsystem.
When using an external gate source, the polarity of the gate signal is changed
with the command:
[SENSe:]TINTerval:GATE:POLarity {POSitive|NEGative}
[SENSe:]TINterval:GATE:POLarity? (query form)
POSitive enables a time interval measurement following a positive edge on the
Gate In/Out BNC. NEGative enables a time interval measurement following a
negative edge on the Gate In/Out BNC. For either edge, the measurement begins
on the first start event after the (gate) edge.
Following a reset (*RST) or instrument preset (SYSTem:PRESet or Preset key), the
negative edge (polarity) is selected.
SENS:TINT:GATE:POL POS // set gate signal polarity
SENS:TINT:GATE:SOUR EXT // external gate source
For timing and synchronization with other instruments gate signals from sources
Time (internal), IMMediate (internal), and INPut[1]/INPut2
(Chan 1 and Chan 2 softkeys) can be routed to the rear panel ‘Gate In/ Out’
connector and assigned a polarity using the commands:
OUTPut[:STATe] {OFF|ON}
OUTPut[:STATe]? (query form)
OUTPut:POLarity {NORMal | INVerted}
OUTPut:POLarity? (query form)
ON enables “Gate Out” - gate signals are routed to the rear panel BNC. OFF
disables “Gate Out” - the BNC is an external (“Gate In”) source. Therefore,
OUTPut:STATe OFF must be set when the gate source is EXTernal.
NORMal - the polarity of the gate signal output from the "Gate Out" BNC is a
rising (positive) edge. INVerted - the gate signal polarity is a falling (negative)
edge.
‘on’
time
- 6 dB
p-p
amplitude
For carrier frequency measurements with ‘on durations’ (Figure 5-6) less than 10
μs, narrow pulse mode must be set using the command:
[SENSe:]FREQuency:BURSt:GATE:NARRow {OFF|ON}
[SENSe:]FREQuency:BURSt:GATE:NARRow? (query form)
ON - enables narrow pulse mode for ‘on durations’ less than 10 μs. Automatic gate
set up (SENSe:FREQuency:BURSt:GATE:AUTO ON) is al ways used when narrow
mode is enabled.
OFF - disables narrow pulse mode. For ‘on durations’ greater than 20 μs, narrow
pulse mode must be disabled.
Following a reset (*RST) or instrument preset (SYSTem:PRESet or Preset key),
narrow pulse mode is disabled.
Gate control for measuring the carrier frequency can occur automatically during
the measurement or be controlled manually as shown in Figure 5-7.
SENSe:FREQuency:BURSt:GATE:NARRow
OFF
53230A Opt. 150 Narrow Pulse Mode
ON
ON
SENSe:FREQuency:BURSt:GATE:AUTO Gate Control
OFF
Automatic Gate Control
Manual Gate Control
SENSe:FREQuency:GATE:SOURce
SENSe:TOTalize:GATE:SOURce Gate Source
SENSe:TINTerval:GATE:SOURce
ADVanced
* not available with tim e interval
IM M ediate
SENSe:GATE:STARt:SOURce Gate Start Source (internal)
EXTernal
SENSe:GATE:STARt:DELay:TIM E
The specific command which sets the gate start (open) source is:
[SENSe:]GATE:STARt:SOURce {IMMediate|EXTernal}
[SENSe:]GATE:STARt:SOURce? (query form)
– gate source IMMediate starts (opens) the measurement gate immediately
after a system trigger is received and following any programmed system
trigger and gate start delay.
– gate source EXTernal sets the gate source to be specified by the command:
[SENSe:]GATE:EXTernal:SOURce {BNC|INPut[1]|INPut2}
[SENSe:]GATE:EXTernal:SOURce? (query form)
– gate source BNC is the counter’s rear panel ‘Gate In/Out’ BNC.
– gate source INPut[1] and INPut2 (represented by softkeys Chan 1 and
Chan 2) are the counter’s channel 1 and channel 2 inputs. These sources are
not available for time interval, pulse wid th, d uty cycle, rise/fall time, or
phase measurements.
OUTput:STATe OFF must be set when using gate source BNC. See “Enabling
NOTE gate signals on the ‘gate in/out’ BNC” for more information and for information
on using gate signals to synchronize other instruments.
When using the external gate sources listed, the polarity of the start gate signal is
set (changed) with the command:
[SENSe:]GATE:STARt:SLOPe {POSitive|NEGative}
[SENSe:]:GATE:START:SLOPe? (query form)
POSitive starts (opens) the gate on a positive edge on the Gate In/Out BNC or
channel 1/channel 2 input. NEGative starts the measurement on a negative edge
on the Gate In/Out BNC or channel 1/channel 2 input. The gate is stopped
(closed) based on the corresponding stop gate settings.
Following a reset (*RST) or instrument preset (SYSTem:PRESet or Preset key), a
negative slope is selected.
For external sources INPut[1] and INPut2 (Chan 1 and Chan 2 softkeys), a fixed
input threshold voltage must also be specified in addition to the gate signal slope.
This is done using the command:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]{<volts>|MINimum|
MAXimum|DEFault}
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]?[{MINimum|MAXimum|DEFault}]
(query form)
The specified edge (slope) of the gate signal crossing the threshold starts the
gate. (More information on the INPut subsystem can be found in Chapter 4,
"53220A/53230A Input Signal Conditioning")
When using external sources INPut[1] and INPut2, the channel selected as the
gate source cannot be the same channel on which the measured signal is applied.
That is, the gate start source channel cannot be involved in the measurement.
When using either an internal (immediate) or external signal to start (open) the
gate, a delay from when the signal is received to when the gate is started (opened)
can be specified. The delay source and its parameters are set with the commands:
[SENSe:]GATE:STARt:DELay:SOURce {IMMediate|EVENts|TIME}
[SENSe:]GATE:STARt:DELay:SOURce? (query form)
– delay source IMMediate disables the delay settings and no gate delay occurs.
CONFigure and MEASure do not change the delay source setting. Following a
reset (*RST) or instrument preset (SYSTem:PRESet or Preset key), delay source
IMMediate is selected.
– delay source EVENts delays the gate start (open) until a specified number of
events (edges) as configured by the INPut subsystem occur on the input
channel. For two-channel time interval measurements, delay events are
counted on the ‘start’ channel. For frequency ratio measurements, delay
events are counted on the ‘denominator’ channel.
The number of events is specified with the command:
[SENSe:]GATE:STARt:DELay:EVENts {<count>|MINimum|MAXimum|DEFault}
[SENSe:]GATE:STARt:DELay:EVENts? (query form)
– delay source TIME delays the gate start (open) for a period set by the
command:
[SENSe:]GATE:STARt:DELay:TIME {<time>|MINimum|MAXimum|DEFault}
[SENSe:]GATE:STARt:DELay:TIME? (query form)
Advanced gate control - gate stop hold off and gate stop
Advanced gate control also includes (optionally) enabling a gate stop hold off and
setting the gate stop (close) parameters. Figure 5-9 repeats the gate stop hold off
and gate stop sections of the full trigger/gate cycle shown in Figure 5-2.
SENSe:GATE:STOP:HOLDoff:SOURce
IMMediate
SENSe:GATE:STOP:SOURce Gate Stop Source
(internal)
EXTernal
Figure 5-9 Gate stop hold off and gate stop sequence.
The gate stop holdoff source and its parameters are set with the commands:
[SENSe:]GATE:STOP:HOLDoff:SOURce {IMMediate|EVENts|TIME}
[SENSe:]GATE:STOP:HOLDoff:SOURce? (query form)
– holdoff source IMMediate disables the hold off settings and no gate holdoff
occurs. The gate closes immediately after the gate stop parameters are
satisfied.
CONFigure and MEASure do not change the hold off source setting. Following a
reset (*RST) or instrument preset (SYSTem:PRESet or Preset key), hold off source
IMMediate is selected (disabled).
– hold off source EVENts holds off the gate stop (close) until a specified number
of events (edges) as configured by the INPut subsystem occur on the input
channel. For two-channel time interval measurements, hold off events are
counted on the ‘stop’ channel. For frequency ratio measurements, hold off
events are counted on the ‘denominator’ channel.
The number of events is specified with the command:
[SENSe:]GATE:STOP:HOLDoff:EVENts {<count>|MINimum|MAXimum|DEFault}
[SENSe:]GATE:STOP:HOLDoff:EVENts? (query form)
– holdoff source TIME holds off the gate stop (close) for a period set by the
command:
[SENSe:]GATE:STOP:HOLDoff:TIME {<time>|MINimum|MAXimum|
INFinity|DEFault}
[SENSe:]GATE:STOP:HOLDoff:TIME? (query form)
Note for frequency, frequency ratio, average period, PRF, and PRI measurements,
the minimum gate stop (close) holdoff time is 100 usec for the 53220A, or 1 usec
for the 53230A.
INFinity or +9.9E+37 is accepted only for the TOTalize measurement function.
When selected, the gate remains open until an ABORt or *RST command or a
device clear is received.
The gate stop source determines when the measurement gate is closed following
the stop hold off.
Setting a gate stop source does not apply to rise/fall time, duty cycle, pulse
NOTE wid th, phase, and single period measurements. These measurements complete
automatically on the next appropriate edge on the input channel.
The specific command which sets the gate stop source is:
[SENSe:]GATE:STOP:SOURce {IMMediate|EXTernal}
[SENSe:]GATE:STOP:SOURce? (query form)
– gate source IMMediate stops (closes) the measurement gate immediately
following any gate stop hold off.
– gate source EXTernal sets the gate stop source to be specified by the
command:
[SENSe:]GATE:EXTernal:SOURce {EXTernal|INPut[1]|INPut2}
[SENSe:]GATE:EXTernal:SOURce? (query form)
– gate source EXTernal is the counter’s rear panel ‘Gate In/Out’ BNC.
CONFigure and MEASure do not change the gate stop source setting. Following
a reset (*RST) or instrument preset (SYSTem:PRESet or Preset key), gate stop
source EXTernal is selected.
When using the external gate sources listed above, the polarity of the stop gate
signal is set (changed) with the command:
[SENSe:]GATE:STOP:SLOPe {POSitive|NEGative}
[SENSe:]:GATE:STOP:SLOPe? (query form)
POSitive stops (closes) the gate on a positive edge on the Gate In/Out BNC or
channel 1/channel 2 input. NEGative stops the measurement on a negative edge
on the Gate In/Out BNC or channel 1/channel 2 input.
CONFigure and MEASure do not change the slope setting. Following a reset
(*RST) or instrument preset (SYSTem:PRESet or Preset key), a positive slope is
selected.
For external sources INPut[1] and INPut2 (Chan 1 and Chan 2 softkeys), a fixed
input threshold voltage must also be specified in addition to the gate signal slope.
This is done using the command:
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]{<volts>|MINimum|
MAXimum|DEFault}
INPut[{1|2}]:LEVel[{1|2}][:ABSolute]?[{MINimum|MAXimum|DEFault}]
(query form)
The specified edge (slope) of the gate signal crossing the threshold stops the gate.
(More information on the INPut subsystem can be found in Chapter 4, "53220A/
53230A Input Signal Conditioning".)
When using external sources INPut[1] and INPut2, the channel selected as the
gate source cannot be the same channel on which the measured signal is applied.
That is, the gate start source channel cannot be involved in the measurement.
6 53220A/53230A Math,
Graphing, and
Data Logging
Math Functions 204
Histograms 222
Trend Charts 234
Data Logging 241
Graphics Functions and Reading Memory 246
The Keysight 53220A/53230A counter features math operations that allow you to
scale readings, test limits, and statistically analyze data. Its graphics functions
compute and display histograms and trend charts of real time measurement data.
This chapter provides information on how these features are used through the
SCPI CALCulate subsystem and with the front panel Math, Graph, and Data Log
keys.
203
6 53220A/53230A Math, Graphing, and Data Logging
Math Functions
The 53220A/53230A counter math functions include smoothing, null/scale,
statistics, and limit checking. Figure 6-1 is a description of how the functions are
enabled.
The math functions are enabled at two levels: 1) the CALCulate[1] subsystem as
a whole is enabled, and 2) the individual math operation is enabled. Math
operations begin once the measurements are started either by
INITiate:IMMediate or READ?, or as soon as the operation is selected from the
front panel (with internal triggering). Readings are processed real time and
displayed, stored in reading memory, and sent to the output buffer (they are not
post-processed from reading memory).
The number of readings processed for a given trigger cycle (Chapter 5:
“Triggering and Gating”) is determined by the trigger count (TRIGger:COUNt) and
the number of readings per trigger (SAMPle:COUNt). The default trigger count
and sample count set by each command is ‘1’. Each time the counter is initiated
reading memory is cleared and a new set of math-processed data is generated.
From the front panel, readings are processed continually if the trigger source
remains at its default INTernal setting.
The math and graphics functions covered in this chapter are enabled individually
(Figure 6-1). However, multiple operations may be enabled at the same time and
performed on the same set of readings.
The SCPI commands and parameters listed throughout this chapter are provided
NOTE as a guide to how the counter is operated programmatically. The commands are
described in detail in the ‘Programmer’s Reference’ section of the Keysight
53210A/53220A/53230A Product Reference CD.
CALCulate1:AVERage:STATe ON
CALCulate1:AVERage
(statistics)
CALCulate1:SCALe: STATe ON
CALCulate1:SMOothing:STATe ON CALCulate1:LIMit:STATe ON
INITiate:IMMediate
CALCulate1:SMOothing CALCulate1:SCALe CALCulate1:LIMit reading memory
(moving average) (scaling and offset) (limit checking)
measurement CALCulate2:TRANsform:HISTogram:STATe ON
data CALCulate1:STATe ON
CALCulate2:TRANsform:HISTogram
(histograms)
READ?
output
buffer
readings initiated by READ? are sent to reading memory and to the output buffer
Smoothing data
The filter is reset if the measurement function or channel is changed, if another set
of readings is initiated, or if a measurement is outside the range corresponding to
the number of readings specified (SLOW, MEDium, FAST).
After the filter is reset, the reading is the average of all readings up to the
specified response (10, 50, 100). At that point, the reading is the moving average
of the last 10, 50, or 100 measurements. Equal weighting is applied to all
measurements in the average.
A reset (*RST) or instrument preset (SYSTem:PRESet) sets the response to FAST.
Smoothing example
//frequency measurement of expected 1 kHz signal ‐ ch 1
//reduce noise on 5,000 readings
CONF:FREQ 1E3,(@1)
SAMP:COUN 5000 // take 5000 reading
CALC:STAT ON // enable CALCulate1 subsystem
CALC:SMO:STAT ON // enable moving average filter
CALC:SMO:RESP SLOW // average 100 readings
INIT
Scaling functions
When scaling is enabled statistical analysis, limit checking, histograms, and trend
charts use scaled data. Figure 6-2 shows the display with scaling functions
enabled.
CALCulate1:SCALe:UNIT:STATe ON
CALCulate1:STATe ON CALCulate1:SCALe:UNIT
CALCulate1:SCALe:STATe ON
CALCulate1:SCALe:FUNCtion
The NULL, PCT, PPM, and PPB scaling functions require a reference value. For PCT,
PPM, and PPB the value cannot be ‘0’.The reference can be obtained automatically
or specified directly with the commands:
CALCulate[1]:SCALe:REFerence:AUTO {OFF|ON}
CALCulate[1]:SCALe:REFerence:AUTO? (query form)
CALCulate[1]:SCALe:REFerence {<reference>|MINimum|MAXimum| DEFault}
CALCulate[1]:SCALe:REFerence? [{MINimum|MAXimum|DEFault}]
(query form)
ON - automatically selects the first measurement as the reference for all
subsequent readings in the reading count (trigger count x sample count). OFF
disables automatic selection and requires the reference to be specified directly.
Following a reset (*RST) or instrument preset (SYSTem:PRESet), automatic
reference selection is enabled (ON).
<reference> - specifies the reference value directly. The reference is used for all
readings in the reading count.
Following a reset (*RST) or instrument preset (SYSTem:PRESet), a reference value
of 0.0 is set and automatic reference is enabled.
From the front panel, pressing Get New Reference takes a reference measurement
on the first trigger received after the key is pressed. A reference can be entered
manually by selecting Ref Value and using the knob or SHIFTed numeric keys.
Reference example
//determine the percentage difference of 100 frequency
//measurements to a reference value of 50000.000
CONF:FREQ 50E3,(@1)
SAMP:COUN 100 // take 100 readings
CALC:STAT ON // enable CALCulate1 subsystem
CALC:SCAL:STAT ON // enable scaling
CALC:SCAL:FUNC PCT // select scale function (PCT)
CALC:SCAL:REF 50.000E3 // set reference value
INIT
Inverting the reading (1/x) Each reading as it is taken can be inverted prior to
its use in the Mx-B equation which thus becomes M/x-B. Inversion is enabled with
the command:
CALCulate[1]:SCALe:INVert {OFF|ON}
CALCulate[1]:SCALe:INVert? (query form)
ON - inverts the reading. OFF disables reading inversion.
Following a reset (*RST) or instrument preset (SYSTem:PRESet) reading inversion
is disabled.
When Invert x is enabled (On) the front panel reading units (Hz, sec) are turned
NOTE off. See “Assigning reading units” if displayed units are required.
For ease in identifying readings from the front panel, a user-defined “units string”
can be assigned to any scale function. The user string replaces the
instrument-assigned measurement units (Hz, pct, ppm, ...). The unit prefix (μ, m,
k, M) remains.
The units string is displayed on the counter and defined using the commands:
CALCulate[1]:SCALe:UNIT:STATe {OFF|ON}
CALCulate[1]:SCALe:UNIT:STATe? (query form)
CALCulate[1]:SCALe:UNIT "<units>"
CALCulate[1]:SCALe:UNIT? (query form)
ON - displays user-defined units on the front panel. OFF - turns off the
user-defined units.
units are one to four characters. Double quotes enclosing the string are
included in the command. The assigned units appear in the counter d isplay only.
Following a reset (*RST) or instrument preset (SYSTem:PRESet) user-defined
units are disabled.
From the front panel, units are entered by pressing the User Units softkey, enabling
the units (On), and using the rotary knob and arrows to enter and select the
character position.
Scaling example
The following example is a typical sequence of scaling commands from the SCPI
CALCulate[1] subsystem.
//Scale 500 readings (M/x‐B) and assign reading units
CONF:FREQ (@1) // frequency measurement
SAMP:COUN 500 // 500 readings/trigger
SENS:FREQ:GATE:TIME .010 // set minimum gate time
CALC:STAT ON // enable CALCulate1 subsystem
CALC:SCAL:STAT ON // enable scaling operation
CALC:SCAL:FUNC SCAL // set scaling function = Mx‐B
CALC:SCAL:INV ON // invert readings (M/x‐B)
CALC:SCAL:GAIN 100 // set gain (M)
CALC:SCAL:OFFS 0 // set offset (B)
CALC:SCAL:UNIT:STAT ON // enable user‐defined units
CALC:SCAL:UNIT "sec" // assign units to readings
INIT // initiate readings
For an input frequency of 1 MHz, the counter should display readings of
approximately +100.00... usec.
Statistics
Statistical calculations are performed continually on readings as they are taken, or
until the total reading count (TRIGger:COUNt x SAMPle:COUNt) is reached. The
commands used to generate statistical data are covered in this section.
As mentioned, multiple operations can be enabled at the same time. Figure 6-3 is
an example with statistics and limit checking enabled.
CALCulate1:STATe ON CALCulate1:AVERage:STATe ON
CALCulate1:AVERage CLEar
Figure 6-3 Counter display with limit testing and statistics enabled.
Enabling statistics
Before statistical calculations are performed they must be enabled using the
command:
CALCulate[1]:AVERage:STATe {OFF|ON}
CALCulate[1]:AVERage[:STATe]? (query form)
ON - enables statistical calculations on the readings as they occur. Statistical data
includes: mean, standard deviation, Allan deviation, maximum value, minimum
value, and average peak-to-peak value.
OFF - disables statistics computation.
Following a reset (*RST) or instrument preset (SYSTem:PRESet), statistical
computations are disabled.
Reading count
Statistical calculations start when Math and the Statistics function are enabled. The
number of readings on which a given set of statistics are based is shown as the
Count value (Figure 6-3). The count can also be queried with the command:
CALCulate[1]:AVERage:COUNt:CURRent?
The count can be read at any time after the measurements have been initiated (i.e.
INITiate:IMMediate, READ?, MEASure?).
Following a reset (*RST) or instrument preset (SYSTem:PRESet), the count is set
to ‘1’.
CALCulate[1]:AVERage:PTPeak?
– returns the average peak-to-peak value (average maximum value - average
minimum value) of all readings in the reading count.
Allan deviation
Allan deviation which is used to estimate stability, is selectable from the front
panel (Figure 6-3) or can be enabled with the command:
CALCulate[1]:AVERage:ADEViation?
Allan deviation is used for frequency and period measurements only, and requires
continuous (gap-free) measurements (SENSe:FREQuency:MODE CONTinuous) for
highest accuracy. Continuous mode is available with the 53230A only.
Allan deviation is also available with the 53220A; however, the 53220A does not
support continuous (gap free) measurements.
Standard deviation
Standard deviation is available with both counters using the command:
CALCulate[1]:AVERage:SDEViation?
The CALCulate1 subsystem and statistics must also be enabled before the
standard deviation can be determined.
Clearing/resetting statistics
The current set of reading statistics is clear by any of the following:
– enabling statistical functions - CALCulate[1]:AVERage[:STATe] ON
– a new measurement cycle - INITiate:IMMediate, READ?, MEASure?
– sending a new SCPI command or changing a current SCPI parameter
– a reset or instrument preset - *RST, SYSTem:PRESet
These steps also clear all read ings in reading memory. To clear statistics without
clearing reading memory, the following command is used:
CALCulate[1]:AVERage:CLEar[:IMMediate]
Limit checking
Limit checking enables counter measurements to be compared on a
reading-by-reading basis to a lower limit and upper limit.
Limits that are exceeded are reported in the counter’s Questionable Data register
(bits 11 and 12). Register definitions and are contained in Chapter 8.
When enabled, limit checking appears on the counter display as shown in
Figure 6-4.
CALCulate1:STATe ON
CALCulate1:LIMit:STATe ON
CALCulate1:LIMit:UPPer CALCulate1:LIMit:CLEar
CALCulate1:LIMit:LOWer
is used to read the Questionable Data register. A value of +2048 (bit 11) indicates
a reading below the lower limit. A value of +4096 (bit 12) indicates a reading
above the upper limit. Reading the register also clears all bits in the register (see
“Clearing limit conditions).
Histograms
The distribution for a given set of counter measurements (except continuous
totalize and time stamp measurements) can be represented graphically using
the 53220A/53230A histogram feature. The following example (Figure 6-5)
represents the basic format of a counter histogram.
count LR UR
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note that histograms and math functions (e.g. statistics, scaling, limits, etc.) can
be used simultaneously with the same measurement data.
Viewing histograms
At power-on or when the front panel Preset key is pressed, numeric data is
displayed. Remotely, histograms can be displayed by changing the display mode
using the command:
DISPlay[:WINDow]:MODE {NUMeric|HISTogram|TCHart}
DISPlay[:WINDow]:MODE? (query form)
The Graph key followed by the Histogram softkey enables and automatically starts
histograms from the front panel. Histograms can also be turned off from the
softkey menu.
Remotely, a reset (*RST) or instrument preset (SYSTem:PRESet) does not change
the display mode.
Histograms correspond to readings in reading memory - starting at the time the
histogram is enabled and ending when the product of the trigger count
(TRIGger:COUNt) and sample count (SAMPle:COUNt) is reached. If triggering is
continuous (i.e. internal), the histogram continually updates from the point it was
enabled.
Figure 6-6 describes the information provided in a typical histogram window.
Bin indices
position window - for marker, zoom,
and pan adjustment the decimal
position (i.e. 1000's, 100's, 10's, 1's)
highlighted by the arrow keys sets
the amount of movement (coarse –
fine) for each tick of the rotary knob.
Histogram configuration
Histograms are configured using the softkeys and commands shown in
Figure 6-7.
CALCulate2:TRANsform:HISTogram:STATe ON
CALCulate2:TRANsform:HISTogram:COUNt?
CALCulate2:TRANsform:HISTogram:CLEar
CALCulate2:TRANsform:HISTogram:POINts
CALCulate2:TRANsform:HISTogram:RANGe:AUTO
CALCulate2:TRANsform:HISTogram:RANGe:AUTO:COUNt
CALCulate2:TRANsform:HISTogram:RANGe:LOWer
CALCulate2:TRANsform:HISTogram:RANGe:UPPer
Number of bins
Bin representation
The softkey:
corresponds to the bin with the largest number of entries and is expressed as an
exact count (Count), or the bin’s percentage (%) of the total reading count. This
setting is only available from the front panel.
The lower and upper ranges of the histogram are specified directly with the
commands:
CALCulate2:TRANsform:HISTogram:RANGe:LOWer
{<value>|MINimum|MAXimum|DEFault}
CALCulate2:TRANsform:HISTogram:RANGe:LOWer?
[{MINimum|MAXimum|DEFault} (query form)
CALCulate2:TRANsform:HISTogram:RANGe:UPPer
{<value>|MINimum|MAXimum|DEFault}
CALCulate2:TRANsform:HISTogram:RANGe:UPPer?
[{MINimum|MAXimum|DEFault}] (query form)
value - directly specifies the histogram lower and upper range values. The value
ranges are:
‐1.0E+15 to ‐1.0E‐15, 0.0, 1.0E‐15 to 1.0E+15
The default lower and upper ranges and the ranges set following a reset (*RST) or
instrument preset (SYSTem:PRESet) are 0.0.
When setting the ranges, both a lower range and an upper range must be
specified. Any of the following steps will prevent a “settings conflict” error (e.g.
lower range greater than upper range) due to the order in which ranges are set:
– setting the upper range first
– setting both ranges on the same line programmatically
– enabling the histogram after the ranges are set
– setting the ranges automatically
With AutoRange Off, the Set to Min/Max softkey is another method for setting the
histogram bin ranges (lower and upper). Depending on the instrument state, Set to
Min/Max will set the ranges as follows:
– When ‘Statistics’ (under the Math key) are enabled, the minimum and
maximum values from the reading statistics are used.
– If readings are in progress and ‘Statistics’ are off, the instrument will select a
minimum and a maximum value from (up to) the last 10,000 readings taken.
– If no previous readings are available, a minimum bin range of 0 and a
maximum bin range of 1 000 000 000.0 are set.
Alternately, lower and upper range values can be set automatically based on a
minimum value and maximum value obtained from the first ‘n’ number of readings
taken.
Automatic range selection is enabled with the commands:
CALCulate2:TRANsform:HISTogram:RANGe:AUTO {OFF|ON}
CALCulate2:TRANsform:HISTogram:RANGe:AUTO? (query form)
ON - enables automatic selection of the histogram lower and upper range values.
OFF - disables automatic selection.
Following a reset (*RST) or instrument preset (SYSTem:PRESet) automatic range
selection is enabled.
The number of readings from which the minimum and maximum range values are
selected (ON) is set with the command:
CALCulate2:TRANsform:HISTogram:RANGe:AUTO:COUNt
{<value>|MINimum|MAXimum|DEFault}
CALCulate2:TRANsform:HISTogram:RANGe:AUTO:COUNt?
[{MINimum|MAXimum|DEFault}] (query form)
value - specifies the first ‘n’ number of readings from which lower and upper
range values are obtained. 10 to 1,000 readings can be specified.
The default number and the number set following a reset (*RST) or instrument
preset (SYSTem:PRESet) is 100.
The data from which the current histogram is created is cleared by any of the
following:
– pressing the Reset Histogram softkey
– enabling/disabling or changing any part of the histogram
– number of bins, lower or upper range
– a new measurement cycle - INITiate:IMMediate, READ?, MEASure
– sending a new SCPI command or changing a current SCPI parameter
Saving readings
The readings used to create the histogram can be saved to internal flash memory
or to an external USB memory device as comma-separated values (CSV) in one
measurement per line ASCII format.
Selecting Save Read ings opens the Export action window from which a path and file
name can be selected or created. The number of readings exported is the total
number in reading memory at the time Export Read ings is pressed - which may not
be the total reading count (TRIGger:COUNt x SAMPle:COUNt).
Exporting readings clears read ing memory and re-starts the histogram on the
next trigger received.
For marker, zoom, and pan adjustment the decimal position (i.e. 100's, 10's, 1's)
NOTE highlighted by the arrow keys sets the amount of movement (coarse or fine) for
each tick of the rotary knob.
The ‘Marker’ softkeys allow you to position markers on individual bins within the
histogram, and if desired, lock the relative distance between the markers. When
locked together, moving either Marker1 or Marker2 with the front panel knob or
using [Shift] followed by a bin number, also moves the other marker while
maintaining the distance between the two. The data corresponding to the marker
positions is shown above the histogram window.
Zoom determines the number of bins displayed by increasing the resolution at the
center region of the histogram. Each time the zoom is adjusted, the X Min and
X Max indices (Figure 6-6) are changed to show the current bin range.
Pan scans the histogram (left or right) once a zoom percentage has been set. By
moving the Pan window, regions of interest can be brought into view; and Zoom
used again to expand the region. Pan, used interchangeably with Zoom in this
manner, maintains the zoom percentage.
Show All restores the histogram window to the total number of bins specified -
including the outer bins, and resets the zoom and pan.
Trend Charts
Reading trends for a given number of counter measurements (except continuous
totalize) or timestamps can be represented within a 53220A/53230A trend chart,
also known as a run chart.
Figure 6-8 shows the components of a typical counter trend chart.
Function
Y Max: maximum reading value within display span Channel
Y Min: minimum reading value within display span Current reading count
Span: (Y Max – Y Min) (memory)
reading indices
Clearing the trend chart clears reading memory and restarts the reading count on
the next trigger received.
Saving readings
The readings represented by the trend chart can be saved to internal flash
memory or to an external USB memory device as comma-separated values (CSV)
in one measurement per line ASCII format.
Selecting Save Read ings opens the Export action window from which a path and file
name can be selected or created. The number of readings exported is the number
of readings in memory (Figure 6-8) at the time Export Read ings is pressed - which
may not be the total reading count (TRIGger:COUNt x SAMPle:COUNt).
Exporting readings clears read ing memory and re-starts the trend chart on the
next trigger received.
For marker, zoom, and pan adjustment the decimal position (i.e. 1000's, 100's,
NOTE 10's, 1's) highlighted by the arrow keys sets the amount of movement (coarse or
fine) for each tick of the rotary knob.
Reading decimation
The trend window displays a maximum of 100 readings. When greater than 100
readings are displayed, the readings are decimated - grouped together and
represented by decimation points. The number of readings in a decimation group
is the reading count/100.
Figure 6-10 is a trend chart of 100,000 readings in which the readings have been
decimated.
position window
indicates decimation
and relative max & min
values within the group
When a marker is moved to a decimation point, the number of the first reading in
the corresponding group is displayed. This number should be noted if it is
necessary to view individual readings within a group.
Data Logging
The data logging feature of the 53220A/53230A counter allows you to log and
analyze up to 1,000,000 readings. Data logging is enabled and configured from
the front panel only, and is available with all counter measurements except
continuous totalizing.
Logged readings ARE NOT saved to internal flash memory or external USB
NOTE memory until the logging duration is complete. If power is lost and if battery
Option 300 is not enabled or it also loses power before logging is complete, all
data will be lost.
Figure 6-11 shows the keys and and windows associated with the data logger
application.
Logged readings saved in internal flash memory or in external USB memory are
comma-separated values (CSV) in one measurement per line ASCII format. A
default path and file name (Internal\DataLog) is used if one is not specified.
The drive (Internal or External) is selected using the browse feature and the
file name is specified using the rotary knob and arrow keys to select or change
characters.
Pressing [Done] saves the path and file name and returns to the application menu.
Data logging will not start if an invalid path/file is specified.
In terms of Time, the data logging duration is specified in hh.mm.ss format. The
value is set using the rotary knob and arrow keys, or using the [Shift]ed numeric
keys. By highlighting specific digits in the time window, greater resolution (i.e.
minutes and seconds) of the logging time can be specified.
The maximum data logging period is 99.00.00. The reading limit, however, is
1,000,000 readings which may occur before the time duration is reached.
In terms of Read ings, data logging continues until the specified number of
readings are complete. The reading count is set using the rotary knob and arrow
keys, or using the [Shift]ed numeric keys. A maximum of 1,000,000 readings can
be specified.
For the Time Stamp measurement function, only read ing duration is available.
When required, a delay can be set between the time the Run key is pressed, and
the start of data logging. The start delay is specified in hh.mm.ss format and is set
using the rotary knob and arrow keys, or using the [Shift]ed numeric keys. By
highlighting specific digits in the delay window, greater resolution (i.e. minutes
and seconds) of the delay time can be specified.
The maximum delay setting is 99:00:00.
Pressing the Run softkey enables data logging. Data logging begins following any
specified start delay when a valid path/file exists. A default path and file name of:
Internal\DataLog
is used when the data logger application is started. Select Yes to overwrite the file
and begin.
Viewing readings
A trend chart is populated as readings are logged. After data logging completes,
the readings are stored in the file specified. Pressing View Resul ts when logging is
stopped and the readings are saved, or when logging is complete, displays a trend
chart of the saved readings.
Pressing View Resul ts after logging Time Stamp measurements will display
“Graphics not supported for this function”.
Figure 6-12 is an example of a trend chart as readings are logged. (Figure 6-8 and
Figure 6-10 contain more information on the trend chart window.)
Function
Channel
Current Reading Count
(memory)
Trend Window
(100 points)
reading indices
time or number of readings
remaining
When logging is complete, the Marker, Pan, and Zoom softkeys can be used review
the data. Note that pressing the Graph key followed by the Trend Chart softkey does
not retain the data in the display.
If greater than 100 readings are logged the readings are decimated - grouped
together and represented by decimation points (see “Trend Charts” and “Reading
decimation”).
reading memory
(record)
.. (record)
.
Reset Histogram:
Reset Stats: - clears current histogram (record)
- clears current set of statistics (record) .. - does not clear reading memory, does not abort readings
- does not clear reading memory, does not abort readings
– clears count and new set of statistics re-start on next
. – clears count and new histogram re-starts on next reading
after reset
reading after reset
(record) (record)
..
.
(memory)
247
7 Formats and Data Flow
Format ASCII is set following an instrument reset (*RST) or front panel preset
(PRESet). A line feed (LF) and End-Or-Identify (EOI) follow the last reading in both
formats.
Specifying a format
Data formats can be specified during counter configuration as shown in the
following segment:
CONF:FREQ 1.0E6
FORM REAL, 64
SAMP:COUN 5
INIT
FETC?
In this segment, measurements initiated by INIT are stored in reading memory.
When FETC?(ed) from memory to the output buffer the readings are converted to
REAL format.
Data flow
The flow of measurement data within the counter is summarized in Figure 7-1.
MMEMory:DOWNoad:DATA
Keysight 53220A/53230A Counter
calibration
state storage
constants LAN
FETCh?
R? GPIB
volatile reading memory output
(1M readings) buffer
MMEMory:STORe:DATA DATA:REMove?
USB
DATA:LAST?
MMEMory:DOWNoad:DATA
MMEMory:UPLoad?
Reading locations include the front panel, read ing memory (volatile), output
buffer, internal flash memory (non-volatile), and external USB memory.
The commands which determine data flow are listed in Table 7-2 and are
described in the following paragraphs.
Reading Memory
DATA:REMove? Specified count Yes Yes
Output Buffer
Reading Memory
DATA:LAST? 1 No Yes
Output Buffer
Reading Memory
MMEMORY:STORe:DATA Internal Flash All No No
External USB
Reading memory
In addition to being displayed, all counter readings are stored in the counter’s
volatile read ing memory (Figure 7-1). Memory capacity is 1,000,000 readings.
Reading memory has the following attributes:
1 reading memory is cleared after a function change, during execution of the
READ?, INITiate:IMMediate, or MEASure? command, after cycling power,
or following an instrument reset (*RST) or preset (SYSTem:PRESet).
2 all readings are stored in an internal counter format - the programmed format
(FORMat subsystem) is set when readings are transferred to the output buffer.
3 if read ing memory overflows the first (oldest) readings are overwritten and the
‘Reading Mem Ovfl’ bit (14) in the Questionable Data Register is set. The most
recent measurements are retained.
Output buffer
Data is available to the PC over the LAN, USB, and GPIB interfaces once it is in the
output buffer (Figure 7-1). The following section explains how readings are
transferred from memory to the buffer. If during a transfer the output buffer fills,
command execution is paused until readings are removed by the PC - creating
room in the buffer. No readings are lost.
READ? example
// frequency meas of 500 kHz signal with uHz resolution
CONF:FREQ 500E3, 1E‐6, (@1) // configure counter
TRIG:COUN 1 // set trigger count
SAMP:COUN 10 // take 10 readings
READ? // read readings when complete
FETCh? example
// frequency meas of 500 kHz signal with uHz resolution
CONF:FREQ 500E3, 1E‐6, (@1) // configure counter
TRIG:COUN 1 // set trigger count
SAMP:COUN 10 // take 10 readings
INIT:IMM // initiate counter to start rdgs
FETC? // fetch rdgs from memory when complete
R? example
// frequency meas of 500 kHz signal with uHz resolution
CONF:FREQ 500E3, 1E‐6, (@1) // configure counter
TRIG:COUN 2 // set trigger count
SAMP:COUN 2500 // set readings/trigger
INIT:IMM // initiate counter to start readings
wait 2500 seconds
R? 2500 // read and remove first 2500 readings
wait 2500 seconds
R? // read and remove all remaining readings
DATA:REMove? example
// frequency meas of 500 kHz signal with uHz resolution
CONF:FREQ 500E3, 1E‐6, (@1) // configure counter
TRIG:COUN 2 // set trigger count
SAMP:COUN 2500 // set readings/trigger
INIT:IMM // initiate counter to start readings
DATA:REM? 2500,WAIT // wait for‐read first 2500 readings
DATA:REM? 2500,WAIT // wait for‐read last 2500 readings
DATA:LAST? - returns the last reading taken and includes read ing units (Hz,
s). The reading is not deleted from memory and the command can be sent before
the total reading count (TRIGger:COUNt x SAMPle:COUNt) is reached.
DATA:LAST? example
//frequency meas of 500 kHz signal with uHz resolution
CONF:FREQ 500E3, 1E‐6, (@1) // configure counter
TRIG:COUN 1 // set trigger count
SAMP:COUN 100 // take 100 readings )
INIT:IMM // initiate counter to start rdgs
wait 20 seconds
DATA:LAST? // retrieve reading (with units) 20s after start
FETC? // fetch all rdgs from memory when complete
A typical response showing a subset of the data is:
+4.999962418998650E+005 HZ
...+4.999962370997962E+005,+4.999962418998650E+005,+4.999962407190446E+
005,+4.999962443559675E+005,...
– when count number of readings have entered reading memory, bit 12 (Rdg
Mem Threshold) in the Standard Operation Register is set to ‘1’. By monitoring
this bit, readings can be transferred from memory to the output buffer once a
given number of measurements have occurred.
Once the threshold is reached, the number of readings in memory must drop
below the threshold level in order to detect when the threshold is reached again.
Path is Internal
USB:\ INT:\
Path is External
root directory
fil
e
folder
Figure 7-2 Folders and files within internal memory and USB storage.
Creating folders and files in flash memory and on the USB drive
Folders and files are created in instrument memory and on a USB drive as
described in the following sections.
Creating folders
When specifying a folder name the current folder is referenced. If a current folder
(MMEM:CDIR) has not been specified and a drive name (INT or USB) is not
included, the default drive ‘INT:’ is referenced. For example:
MMEM:MDIR “dut_2”
creates the folder ‘dut_2’ on the root drive INT.
Following a reset (*RST) or instrument preset (SYSTem:PRESet), the counter
resets the current folder to the root directory on the internal flash file system
("INT:\") .
The combination of folder and file name cannot exceed 240 characters, and
cannot contain the characters \ / : * ? “ < > |. Preference files have a .prf
extension.
User preferences include settings such as:
– display brightness, radix, separator, and screen saver state
– Help language selected
– state recall and select settings
– reference oscillator source, external reference frequency, standby setting
– auto-level minimum frequency
– battery state (enabled, disabled)
– beeper setting
– measurement time out
– 531xx SCPI compatibility language setting
When loading a preferences file that specifies a static IP address for LAN, be
careful that this does not result in two instruments with the same IP address on
your LAN. This could result in LAN configuration errors on both instruments.
User preferences cannot be stored or loaded (retrieved) using the front panel.
Verifying a recalled state Before a state is recalled, its storage location can be
queried to determine if a valid state exists of if the location is empty.
MEMory:STATe:VALid? {0|1|2|3|4}
queries the specified state location. If ‘0’ is returned the location is empty. If ‘1’ is
returned a valid state exists. For example:
//verify a valid state is stored in location 3; 0 = no state //saved, 1
= valid state in location 3
MEM:STAT:VAL? 3
//enable automatic recall at power‐on
MEMory:STATe:RECall:AUTO {ON|OFF}
MEMory:STATe:RECall:AUTO? (query form)
//select the state location or file recalled at power‐on
MEMory:STATe:RECall:SELect {0|1|2|3|4|<file>}
MEMory:STATe:RECall:SELect? (query form)
If automatic recall is enabled and a state location or file name is not selected, the
counter will power-on in the state it was in when last turned off (location 0).
Following are examples of a state recalled from a numbered state location and
from a state file in internal flash memory.
// configure counter
*SAV 2 // save state in location 2
MEM:STAT:REC:AUTO ON // enable state recall at power‐on
MEM:STAT:REC:SEL 2 // recall state in loc. 2 at power‐on
// when power is cycled, state in location 2 is recalled
and
MMEM:MDIR “INT:\SETUP_A” // create folder in INT memory
//configure counter
// store state in file
MMEM:STOR:STAT “INT:\SETUP_A\test_A.sta”
MEM:STAT:REC:AUTO ON // enable state recall at power‐on
MEM:STAT:REC:SEL “test_A.sta” // recall file at power‐on
//when power is cycled, state test_A.sta is recalled
A specific power-on state can be selected from the front panel as follows:
1 From the Store/Recall menu, select User Def using the ‘Power On’ soft key.
2 Press User Def File to view the file system. Select the desired state to be set at
power-on by selecting the desired folder and file name. Remember that
instrument state locations 0-4 are identified by file name (e.g. STATE_3.sta).
For states saved in other files (locations), specify the appropriate file with the
.sta extension.
Selecting Last using the ‘Power On’ soft key will recall the instrument state at the
time the counter was last turned off (state location 0). With Factory selected, the
counter will power-up in its factory-set state.
Deleting folders
Folders are deleted (removed) using the command:
MMEMory:RDIRectory “<folder>”
When deleting a folder from an I/O interface, the folder must be empty
(containing no sub-folders or files). The folder designated as the current folder
(MMEMory:CDIRectory) cannot be deleted. From the front panel, un-empty
folders can be deleted (as prompted) as can the (SCPI designated) current folder.
Deleting files
Data and state files located on the instrument’s internal flash drive or on a USB
memory device (Figure 7-2) are deleted using the command:
MMEMory:DELete <“file”>
The file format is “[drive:path]<file_name>”. drive is either INT (internal flash
memory) or USB (external memory device). If the file deleted is not in the specified
current directory, path is an absolute folder path beginning with ‘\’ and starting at
the root folder. The file name must include the file extension. For example:
\\ delete data file data1.csv in USB folder dut_1
MMEM:DEL “USB:\dut_1\data1.csv”
State files saved in state locations 0 - 4 can also be deleted with the commands:
MEMory:STATe:DELete {0|1|2|3|4}
MEMory:STATe:DELete:ALL
//delete the contents of state location 2
MEM:STAT:DEL 2
//delete the contents of all numeric state locations
MEM:STAT:DEL:ALL
Folders and Files are deleted using the front panel as follows:
1 After pressing the ‘Manage Files’ softkey, press the ‘Action’ softkey and select
‘Delete’. (The action should be selected first.)
2 Press the ‘Browse’ softkey and use the front panel knob to highlight the drive,
folder, or file, and then press ‘Select’. Press ‘Browse’ again to view (and select)
the contents within a folder.
3 When folder or file appears in within the Path: or File: window, press ‘Perform
Delete’.
The destination folder in the copy or move command must currently exist. The
folder is not created during the copy or move.
The following examples show different locations to which files may be copied:
//copy file from folder to root of USB drive
MMEM:COPY "INT:\dut_1\state1.sta" , "USB:\"
//move file from folder to root of USB drive
MMEM:MOVE "INT:\dut_1\state1.sta" , "USB:\"
//copy file from INT folder to existing USB folder
MMEM:COPY "INT:\dut_1\state1.sta" , "USB:\duts"
//copy file from folder to existing folder ‐ new file name
MMEM:COPY "INT:\dut_1\state1.sta" , "USB:\duts\s1.sta"
//rename file from state1.sta to state2.sta
MMEM:MOVE "INT:\dut_1\state1.sta" , "INT:\dut_1\state2.sta"
Folder catalogs
A catalog of all sub-folders and files, or separate catalogs of data (.csv and .dat)
and state (.sta) files per folder can be obtained using the following commands.
In addition to the list of files, the commands also provide the total amount of
memory used and the total amount of memory available (free) on the specified
drive.
MMEMory:CATalog[:ALL]? [<“folder”>]
MMEMory:CATalog:DATA? [<“folder”>]
MMEMory:CATalog:STATe? [<“folder”>]
The folder parameter format is drive:path. drive is either INT (internal flash
memory) or USB (external memory device). path is an absolute path and folder
name beginning with \. If a folder is not specified, the contents of the specified
current folder (MMEMory:CDIRectory) or the contents of the drive’s root directory
are returned.
The format of the data returned is:
<total memory used>, <total memory free>, <“file listing”>
“file listing” with quotes (““) included is further separated into:
“<file name>, <file type>, <file size>”
Memory used, memory free, and file size are given in bytes. Examples of what the
individual CATalog commands might return for a folder on an external USB
memory device containing a sub-folder plus a .csv data file, a .dat data file, and a
state file are given as follows:
MMEMory:CATalog[:ALL]?
253657088,519798784,"data1.csv,ASC,12500","state1.sta,STAT,860","data2.
dat,BIN,1600","dut_a,FOLD,0"
MMEMory:CATalog:DATA?
253657088,519798784,"data1.csv,ASC,12500","data2.dat,BIN,1600"
MMEMory:CATalog:STATe?
253657088,519798784,"state1.sta,STAT,860"
8 Instrument Status
Keysight 53220A/53230A Status System 279
This chapter covers the status registers used to monitor conditions within the
53220A/53230A counter.
277
8 Instrument Status
Condition Register
The Condition Register within the Questionable Data Register Group monitors
current conditions that may impact the integrity of the counter measurements.
The Condition Register is read with the command:
STATus:QUEStionable:CONDition?
Reading the register does not clear the bit(s) in the register. The bit is cleared
when the condition is removed.
Event Register
The Event Register within the Questionable Data Register Group also monitors
conditions that may impact the integrity of the counter measurements.
The Event Register is read with the command:
STATus:QUEStionable[:EVENt]?
Unlike the Condition Register, the bits in the Event Register remain set following
the condition that occurred. The bits are cleared by reading the register.
Enable Register
The Enable register specifies which bits in the Event register can generate a
summary bit which is subsequently used to generate a service request.
Bits within the Event Register are enabled with the command:
STATus:QUEStionable:ENABle <enable>
STATus:QUEStionable:ENABle? (query form)
– enable: decimal value corresponding to the binary-weighted sum of the bits
in the register. For example, to enable the bit monitoring possible time base
errors: STAT:QUES:ENAB 1024.
Condition Register
The Condition Register within the Standard Operation Register Group monitors
current conditions regarding the operational state of the instrument. The
Condition Register is read with the command:
STATus:OPERation:CONDition?
Reading the register does not clear the bit(s) in the register. The bit is cleared
when the condition is removed.
Event Register
The Event Register within the Standard Operation Register Group also monitors
the instrument state. The Event Register is read with the command:
STATus:OPERation[:EVENt]?
Unlike the Condition Register, the bits in the Event Register remain set following
the state that occurred. The bits are cleared by reading the register.
Enable Register
The Standard Operation Register Group Enable Register specifies which bits in the
Event register can generate a summary bit which is subsequently used to
generate a service request.
Bits within the (operational) event register are enabled with the command:
STATus:OPERation:ENABle <enable>
STATus:OPERation:ENABle? (query form)
– enable: decimal value corresponding to the binary-weighted sum of the bits
in the register. For example, to enable the bit monitoring low (critical) battery
charge: STAT:OPER:ENAB 4.
A 53220A/53230A
Error Messages
Appendix A contains a description of the error messages associated with the
53220A/53230A counter.
285
A 53220A/53230A Error Messages
File name error; The combination of the directory path and file name is greater than 239
‐257
path too long characters.
File name error; The folder name specified in the memory operation is the name of an
‐257
not a folder name existing file.
File name error; The file name specified in the memory operation is the name of an
‐257
path is a folder name existing folder.
File name error; The name specified when creating a file or folder already exists in
‐257
file or folder already exists internal flash memory or on the USB device.
File name error;
‐257 The “..” convention cannot be used to indicate the parent folder.
relative path not allowed
File name error; The folder presently specified as the default/current folder
‐257
folder is default folder (MMEMory:CDIRectory) cannot be deleted.
File name error;
‐257 The folder or file operation specified does not include a valid path name.
path name missing
File name error; The drive name is missing or is invalid in the path specified. Valid drive
‐257 drive name missing or names are INT (internal flash memory) and USB (external USB memory
not recognized device).
File name error;
‐257 The file uploaded to the counter is greater than 1 GByte.
file too large
When deleting a folder from an I/O (remote) interface, the folder must
File name error;
‐257 be empty - no sub-folders or files. Un-empty folders CAN be deleted
folder not empty from the front panel.
File name error; Depending on the memory operation and file type, valid file extensions
‐257
unknown file extension are .csv, .dat, .sta, and .prf.
Calibration memory lost;
The instrument’s calibration data has been erased following a
‐313 due to firmware revision instrument firmware update. Recalibration of the instrument is required.
change
Save/recall memory lost; The instrument state saved by the *SAV? command in non-volatile
‐314
memory corruption detected (flash) memory has been lost.
Save/recall memory lost;
The instrument state saved by the *SAV? command in non-volatile
‐314 due to firmware revision (flash) memory has been lost due to a firmware update.
change
Configuration memory lost; User-preference settings such as I/O settings, the reference oscillator
‐315
memory corruption detected setting, measurement time out setting,... have been lost.
Configuration memory lost; User-preference settings such as I/O settings, the reference oscillator
‐315 due to firmware revision setting, measurement time out setting,... have been lost due to a
change firmware update.
Channel 3 power changed The measurement could not be completed due to a change (too low or
+317
during measurement too high) in input signal power.
Channel 3 input is not a
+318 The measurement function selected requires/ expects a pulsed signal.
pulsed signal
Channel 3 frequency shift The FM tolerance of the input signal frequency exceeded ±50% during
+319
detected during measurement the current measurement gate.
Printed in Malaysia
53220-90001
www.keysight.com