Pendulum CNT-90 Programmer's Handbook

Pendulum CNT-90 Programmer's Handbook

Timer / counter / analyzer, frequency calibrator / analyzer, microwave counter / analyzer
Hide thumbs Also See for CNT-90:
Table of Contents

Advertisement

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CNT-90 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Pendulum CNT-90

  • Page 2 4031 600 90201 May 2017 - Tenth Edition © 2017 Pendulum Instruments / Altaria Services...
  • Page 3: General Information

    GENERAL INFORMATION About this Manual This manual contains directions for use that apply to the Timer/Counter/Analyzers CNT-90 and CNT-91, the Frequency Calibrator/Analyzer CNT-91R, and the Microwave Counter/Analyzer CNT-90XL. In order to simplify the references, the instruments are further referred to throughout this manual as the '9X', whenever the information applies to all types.
  • Page 4 This page is intentionally left blank.
  • Page 5: Table Of Contents

    Table of Contents GENERAL INFORMATION ... . . III Order of Execution....5-4 MEASurement Function .
  • Page 6 :CALCulate :AVERage :COUNt : Input Subsystems ... . . 8-45 CURRent? ..... . 8-13 :INPut«[1]|2»...
  • Page 7 :MEASure: ARRay: FREQuency: :TOTalize :GATE ....8-102 BTBack? ..... . . 8-74 Source Subsystem .
  • Page 8 *LMC? ......8-133 *LRN? ......8-134 *OPC .
  • Page 9: Getting Started

    Chapter 1 Getting Started...
  • Page 10: Finding Your Way Through This Manual

    Getting Started Finding Your Way Through This Manual You should use this Programmer's The “Programmer’s Reference” Sec- Handbook together with the User's tion of this manual contains: Manual. That manual contains speci- – Chapter 5, Instrument Model, ex- fications for the counter and explana- plains how the instrument looks tions possibilities...
  • Page 11: Manual Conventions

    Getting Started Alternative Expressions Giving Manual Different Result: Conventions Alternative expressions giving different results are separated by |. For example, On|Off means that the function may be Syntax Specification Form switched on or off. This manual uses the EBNF (Extended Backus-Naur Form) notation for describ- Grouping: «...
  • Page 12: Setting Up The Instrument

    Getting Started used if the command is only four charac- Setting Up the ters. Instrument – If the last character in the command is a digit, then this digit is appended to the shortform. Setting the GPIB Address Examples: The address of the counter is set to 10 ®...
  • Page 13: Interface Functions

    Getting Started – Basic talker. Interface Functions – No talker only. – It can send out a status byte as response to What can I do with the Bus? a serial poll from the controller. All the capabilities of the interface for the –...
  • Page 14: Using The Usb Interface

    4-11. ers. Instruments connected to the USB bus are identified with: Using the USB Vendor ID: 0x14EB for Pendulum Instru- ments. Interface Model ID: 0x0090 for the '90' and serial number of the instrument. The counter is equipped with a USB full...
  • Page 15: Default Settings

    Chapter 2 Default Settings...
  • Page 16: Default Settings (After * Rst)

    Default Settings Default settings PARAMETER VALUE/ SETTING (after * RST) Mathematics Mathematics State PARAMETER VALUE/ Constants K=M=1, SETTING Inputs A & B Limits Trigger Level AUTO Limit State Impedance 1 MW Limit Mode RANGE Manual Attenuator Lower Limit Coupling Upper Limit Trigger Slope Burst Filter...
  • Page 17: Introduction To Scpi

    Chapter 3 Introduction to SCPI...
  • Page 18: What Is Scpi

    This chapter is an overview of SCPI and shows how SCPI is used in Pendulum Frequency Counters and Timer/Counters. Figure 3-1 Vertical SCPI is based on IEEE-488.2 to which it This means that all instruments of the owes much of its structure and syntax.
  • Page 19 Introduction to SCPI A programmer with SCPI experience, Management and however, will understand the meaning Maintenance of Programs and reasons of a SCPI program, because SCPI simplifies maintenance and man- of his knowledge of the standard. agement of the programs. Today changes Changes, extensions, and additions are and additions in a good working program much easier to make in an existing appli-...
  • Page 20: How Does Scpi Work In The Instrument

    Introduction to SCPI Message Exchange Control How does SCPI protocol Work in the Another important function is the Mes- Instrument? sage Exchange Control, defined by IEEE 488.2. The Message Exchange Control protocol specifies the interactions The functions inside an instrument that between the several functional elements control the operation provide SCPI com- that exist between the GPIB functions...
  • Page 21 Introduction to SCPI message. When the controller violates this State Purpose rule, the device will report a query error IDLE Wait for messages (interrupted action). READ Read and execute mes- – The instrument sends only one response sages message for each query message. If the QUERY Store responses to be query message resulted in more than one...
  • Page 22 Introduction to SCPI Remote Local Protocol Definitions Remote Operation When an instrument operates in remote, all local controls, except the local key, are disabled. Local Operation An instrument operates in local when it is not in remote mode as defined above. Local Lockout In addition to the remote state, an instru- ment can be set to remote with ‘local...
  • Page 23: Program And Response Messages

    Introduction to SCPI Program and Response Messages The communication between the system One or more program message units controller and the SCPI instruments con- (commands) may be sent within a simple nected to the GPIB takes place through program message, see Fig. 3-6. Program and Response Messages.
  • Page 24 Introduction to SCPI Most controller programming languages root level keyword, representing the send these terminators automatically, but highest hierarchical level in the command allow changing it. So make sure the ter- tree. minator is as above. keywords following represent Example of a terminated program mes- subnodes under the root node.
  • Page 25 Introduction to SCPI Notation Habit in Command Syntax To clarify the difference between the forms, the shortform in a syntax specifi- < R e s p o n s M e s s a g e U n i t > cation is shown in upper case letters and the remaining part of the longform in Fig 3-9...
  • Page 26: Command Tree

    Introduction to SCPI Example: Command Tree SEND® ARM:STARt:SLOPe8NEG Command Trees like the one below are Where: ARM is the root node and SLOPe is used to document the SCPI command set the leaf node. in this manual. The keyword (mnemonic) Each colon in the command header on the root level of the command tree is moves the current path down one level...
  • Page 27: Parameters

    Introduction to SCPI The instrument always allows MINimum This is the command where: and MAXimum as a data element in com- ARM:STARt is the header path and mands, where the parameter is a numeric :SLOPe is the first leaf node and DE- value.
  • Page 28 Introduction to SCPI Example Other Data Types SEND® :SYST:TOUT8ON or Other data types that can be used for pa- :SYST:TOUT81 rameters are the following: This switches timeout monitoring on. – String data: Always enclosed between sin- A query, for instance :SYSTem:TOUT?, gle or double quotes, for example will return 1 or 0;...
  • Page 29: Macros

    Introduction to SCPI within the language (like BASIC) we rec- Macros ommend that you use block data instead, and use single quotes as string identifiers A macro is a single command, that repre- within the macro. sents one or several other commands, de- When using string data for the pending on your definition.
  • Page 30 Introduction to SCPI Macros with Arguments Enabling and Disabling Macros You can pass arguments (variable param- eters) with the macro. Insert a dollar sign *EMC Enable Macro Command ($) followed by a single digit in the range 1 to 9 where you want to insert the pa- When you want to execute a counter rameter.
  • Page 31 Introduction to SCPI Retrieve a Macro *GMC? Get Macro Contents Query This query gives a response containing the definition of the macro you specified when sending the query. Example using the above defined macro: SEND® *GMC?8‘LIMITMON’ READ¬ #292:CALC:STAT ON;:CALC:LIM:STAT ON; :CALC:LIM:LOW:DATA $1;STAT8ON;...
  • Page 32: Status Reporting System

    Introduction to SCPI You can select some conditions in the Status Reporting counter that should be reported in the Sta- System tus Byte Register. You can also select if some bits in the Status Byte should gen- erate a Service Request (SRQ). Introduction (An SRQ is the instrument’s way to call the controller for help.)
  • Page 33: Error Reporting

    Introduction to SCPI 0, “No error” Error Reporting When errors occur and you do not read these errors, the Error Queue may over- The counter will place a detected error in flow. Then the instrument will overwrite its Error Queue. This queue is a FIFO the last error in the queue with the fol- (First-In First-Out) buffer.
  • Page 34 Introduction to SCPI Execution Error This error shows that the instrument has received a valid program message which it cannot execute because of some device specific conditions. Device-specific Error This error shows that the instrument could not properly complete some device specific operations.
  • Page 35: Initialization And Resetting

    Introduction to SCPI The device-clear commands will not do Initialization and the following: Resetting – Change the instrument settings or stored data in the instrument. Reset Strategy – Interrupt or affect any device operation in progress. There are three levels of initialization: –...
  • Page 36 Introduction to SCPI The *RST Command Use this command to reset a device. It initializes the device-specific functions in the Counter. The following happens when you use the *RST command: – You set the Counter-specific functions to a known default state. The *RST condition for each command is given in the com- mand reference chapters.
  • Page 37: Programming Examples

    Chapter 4 Programming Examples...
  • Page 38: Introduction

    Programming Examples Introduction The program examples in this chapter are written in standard 'C' extended with a dedicated library National AT-GPIB/TNT controller board. The programs can be run on PCs using Windows later operating systems. Even if you use other platforms for your applications, you can benefit from study- ing the examples.
  • Page 39: Individual Mesurements (Ex. #1)

    Programming Examples Individual Mesurements (Ex. #1) Sample program to perform individual measurements on the '9X'. Written for National AT-GPIB/TNT for Windows NT and later. Sample program to perform individual measurements on the '9X'. Written for National AT-GPIB/TNT for Windows NT and later. #include <windows.h>...
  • Page 40 Programming Examples // Setup for pulse width measurement ibwrite(counter, “CONF:PWID (@1)”); // Some settings... ibwrite(counter, “AVER:STAT OFF;:ACQ:APER MIN”); ibwrite(counter, “INP:LEV:AUTO OFF; :INP:LEV 0"); ibwrite(counter, ”FORMAT:TINF ON;:FORMAT ASCII"); // Check that setup was OK, all commands correctly spelled ibwrite(counter, “syst:err?”); ibrd(counter, buf, 100L); buf[ibcnt]=0;...
  • Page 41: Block Measurements (Ex. #2)

    Programming Examples Block Measurements (Ex. #2) Sample program to perform fast measurements on the '9X' using block measurements. Written for National AT-GPIB/TNT for Windows NT and later. ** Sample program to perform fast measurements on the '9X' ** using block measurements ** Written for National AT-GPIB/TNT for Windows NT and later #include <windows.h>...
  • Page 42 Programming Examples // Reset counter to known state ibwrite(counter, “*rst;*cls”); // Setup for period measurement ibwrite(counter, “FUNC ‘PER 1’”); // Some settings... ibwrite(counter, “INP:LEV:AUTO OFF;:INP:LEV 0;COUP DC”); ibwrite(counter, “TRIG:COUNT 1000;:ARM:COUNT 1"); ibwrite(counter, ”DISP:ENAB ON"); ibwrite(counter, “FORMAT ASCII;:FORMAT:TINF OFF”); ibwrite(counter, “*ESE 1;*SRE 32"); // On the safe side: Check that setup was OK, all commands correctly spelled etc ibwrite(counter, ”syst:err?");...
  • Page 43 Programming Examples printf (“Block measurement: %d samples/s\n”, 10000 * 1000 / (Stop - Start)); do { ibwrite(counter, “syst:err?”); ibrd(counter, buf, 100L); buf[ibcnt]=0; printf(“End error: %s\n”, buf); } while (atoi(buf)!=0); ibonl(counter, 0); /******************** * Support functions * ********************/ void ibwrite(int counter, const char *string) { ibwrt(counter, (char*) string, strlen(string));...
  • Page 44: Fast Measurements (Ex. #3)

    Programming Examples Fast Measurements (Ex. #3) Sample program to perform fast measurements on the '9X' using GET, DISP:ENAB OFF and FORMAT REAL. Written for National AT-GPIB/TNT for Windows NT and later. ** Sample program to perform fast measurements on the '9X' ** using GET, DISP:ENAB OFF and FORMAT REAL ** Written for National AT-GPIB/TNT for Windows NT and later #include <windows.h>...
  • Page 45 Programming Examples ibwrite(counter, “*idn?”); ibrd(counter, buf, 100L); buf[ibcnt]=0; printf(“Counter identification string: %s\n”, buf); printf(“Setup\n”); if ((counter = ibdev(0, address, 0, T3s, 1, 0)) < 0) { printf(“Could not connect to counter”); exit(1); // Reset counter to known state ibwrite(counter, “*rst;*cls”); ibwrite(counter, “*ESE 0;...
  • Page 46 Programming Examples ibrd(counter, reading, 29L); for (j=0; j<8; j++) { Result.c[j] = reading[3+j]; if (i%50 == 0) printf(“Result %d: %e\n”, i, Result.d); Stop = clock(); printf (“Total time %d ms (%f samples /s)\n”, Stop- Start, (double)1000.0/(Stop-Start)*1000); ibwrite(counter, “DISP:ENAB ON”); do { ibwrite(counter, “syst:err?”);...
  • Page 47: Usb Communication (Ex. #4)

    // Begin by initializing the system Status = viOpenDefaultRM(&defaultRM); if (Status < VI_SUCCESS) { printf (“Failed to initialise NI-VISA system.\n”); return -1; // Look for something made by Pendulum Status = viFindRsrc(defaultRM, “USB?*INSTR{VI_ATTR_MANF_ID==0x14EB}”, &fList, &numInstrs, Desc); if (Status < VI_SUCCESS) { printf (“No matching instruments found.\n”);...
  • Page 48 Programming Examples Status = viWrite(Instr, “*IDN?\n”, 6, &RetCount); Status = viRead(Instr, Buffer, MAX_CNT, &RetCount); Buffer[RetCount]=0; printf(“%s\n”,Buffer); Status = viWrite(Instr, “INIT:CONT OFF;:func ‘per’\n”, 25, &RetCount); while( i++<10){ Status = viWrite(Instr, “init;fetc?\n”, 11, &RetCount); if (Status != VI_SUCCESS) { printf(“Write: status = %x, i = %d\n”, Status, i); /* Close down the system */ Status = viClose(Instr);...
  • Page 49: Continuous Measurements (Ex. #5)

    Programming Examples Continuous Measurements (Ex. #5) #include <windows.h> #include <stdio.h> #include <conio.h> #include <stdlib.h> #include <float.h> #include <math.h> #include <assert.h> #include "visa.h" // Write a null terminated string (ie, no binary data) to the // instrument. unsigned WriteDevice(ViSession Instr, const char *Str, int Line) ViStatus Status;...
  • Page 50: Error Code

    Programming Examples return((unsigned)Status); #define WriteDev(Str) WriteDevice(Instr, Str, __LINE__) #define ReadDev(Buf, BufLength, pActualLength) ReadDevice(Instr, Buf, BufLength, pActualLength, __LINE__) ViSession defaultRM, Instr; void Quit() (void)viClose(Instr); (void)viClose(defaultRM); _exit(0); void QuitMsg(char *Str) fprintf(stderr, Str); Quit(); void ReportAndQuit() char Buf[100]; ViUInt32 ReadLength; int Error; // Break the measurement. (void)WriteDev("abort");...
  • Page 51 Programming Examples (void)WriteDev("syst:pres"); (void)viClose(Instr); (void)viClose(defaultRM); _exit(0); // command line arguments struct CmdArgs bool bUSB; // GPIB if false unsigned int nAddr; // GPIB address. Not used for USB double Pacing; char Func[64]; // measurement function bool bPeriod; // is Meas Func one of Period functions // or one of Freq functions double RefVal, Delta;// reference value and acceptable error // (used to check meas results)
  • Page 52 Programming Examples static int const nMeasFuncs = sizeof(StrMeasFuncs) / sizeof(StrMeasFuncs[0]); // defaults static int const DefAddr = 10; static double const DefPacing = 100e-6; // s static int const DefMeasFunc = 2; static double const DefRefFreq = 10e6; // Hz static double const DefDelta = 10e5;...
  • Page 53 Programming Examples break; // this is not pacing. fallthrough to next arg nArg++; case 3: // meas func // copy Meas Func int n = strlen(s); if ( n >= sizeof(pArgs->Func) / sizeof(pArgs->Func[0]) ) // func is too long bError = true; break;...
  • Page 54 Programming Examples fprintf(stderr, "Usage:\n" "%s USB|GPIB[:<Address>] [<Pacing>] [<Meas Func>] [<Ref Freq>] [<Delta>]\n\n" "Parameters description:\n" " USB|GPIB - selects particular bus interface,\n" " <Address> - (optional) instrument's GPIB address\n" " (%d if omitted)\n" " <Pacing> - (optional) pacing time between measurements\n" "...
  • Page 55 Programming Examples return (_isnan(Val) || Val < Args.RefVal - Args.Delta || Val > Args.RefVal + Args.Delta); // check for keypress and exit if any inline void CheckUserCancel() if ( kbhit() ) if ( 0 == getch() ) getch(); QuitMsg("\nCancelled by the user...\n"); // Create a buffer that should fit 10000 samples in FORMat // PACKed.
  • Page 56 Programming Examples // Find the instrument if ( Args.bUSB ) // Look on USB for something made by Pendulum with model // code 0x0091. // For this sample program we'll just pick the first // found, if any. sprintf(Command, "USB?*INSTR{VI_ATTR_MANF_ID==0x14EB &&...
  • Page 57 Programming Examples sprintf(Command, "CONF:%s", Args.Func); if (WriteDev(Command) != VI_SUCCESS) Quit(); // Do a measurement to check if all is set up OK. if (WriteDev("inp:lev:auto off;:inp:lev 0;:form:bord swap") != VI_SUCCESS) Quit(); if (WriteDev("form asc;:form:tinf on") != VI_SUCCESS) Quit(); if (WriteDev("read?") != VI_SUCCESS) Quit(); if (ReadDev(Buffer, BUFSIZE, &ReadLength) != VI_SUCCESS) Quit();...
  • Page 58 Programming Examples // Fetch the measurement results as it goes. Count = 0; while (true) CheckUserCancel(); // The 'max' parameter means fetch as many samples as is // currently available for fetching (but no more than // the upper limit, which by default is 10000). if (WriteDev("fetc:arr? max") != VI_SUCCESS) Quit();...
  • Page 59 Programming Examples for (i=0; i<Samples; i++) { Val = *((double*)pBuf); pBuf += 8; if (i == 0 && _isnan(Val)) { // Invalid value response. printf("The instrument is apparently no longer measuring.\n"); Failed = true; break; TSVal = *((__int64*)pBuf); pBuf += 8; // Do something with the fetched result.
  • Page 60 Programming Examples if (Failed) { break; ReportAndQuit(); return(0); 4-24 Error Code...
  • Page 61: Instrument Model

    Chapter 5 Instrument Model...
  • Page 62: Introduction

    Instrument Model An instrument may use a combination of Introduction the above functions. The counters belong to the signal acquisition category, and The figure below shows how the instru- only that category is described in this ment functions are categorized. This in- manual.
  • Page 63: Measurement Function Block

    Instrument Model SENSe Measurement The SENSe block converts the signals Function Block into internal data that can be processed by the CALCulate block. The SENSe com- The measurement function block converts mands control various characteristics of the input signals into an internal data for- the measurement and acquisition process.
  • Page 64: Other Subsystems

    Instrument Model SYSTem Other Subsystems This subsystem controls some system pa- rameters like timeout. In addition to the major functions (sub- systems), there are several other subsys- TEST tems in the instrument model. This subsystem tests the hardware and The different blocks have the following software of the counter and reports er- functions.
  • Page 65: Measurement Function

    Instrument Model the instrument you are using. See Figure MEASurement 5-3. Function MEASure? This is the most simple command to use, In addition to the subsystems of the in- but it does not offer much flexibility. The strument model, which control the instru- MEASure? query lets the counter config- ment functions, SCPI has signal-oriented ure itself for an optimal measurement,...
  • Page 66 Instrument Model READ? starts the acquisition and returns the result. This sequence does the same as the MEA- Sure command, but now it is possible to insert commands between CONFigure and READ? to adjust the setting of a par- ticular function (called fine tuning). For instance, you can set an input attenuator at a required value.
  • Page 67: Using The Subsystems

    Chapter 6 Using the Subsystems...
  • Page 68: Introduction

    Using the Subsystems Introduction Although SCPI is intended to be self ex- planatory, we feel that some hints and tips on how to use the different subsys- tems may be useful. This chapter does not explain each and every command, but only those for which we believe extra ex- planations are necessary.
  • Page 69: Calculate Subsystem

    Using the Subsystems Calculate Subsystem The calculate subsystem processes the Limit Monitoring measuring results. Here you can recalcu- Limit monitoring makes it is possible to late the result using mathematics, make get a service request when the measure- statistics and set upper and lower limits ment value falls below a lower limit or for the measurement result.
  • Page 70: Configure Function

    Using the Subsystems Configure Function The CONFigure command sets up the counter to make the same measurements as the MEASure query, but without initi- ating the measurement and fetching the result. Use configure when you want to change any parameters before making the measurement.
  • Page 71: Format Subsystem

    Using the Subsystems Format Subsystem Time Stamp An overview of the different output for- mats gained studying Readout Format Chapter 8, Command Reference. See the following subdivisions with page When :FORMat:TINFormation is set to references: ON, the readout will consist of two val- ues instead of one for :FETCh:SCALar?, P.
  • Page 72: Input Subsystems

    Using the Subsystems Input Subsystems Figure 6-1 Summary of Model ‘9X’ input amplifier settings. 6-6 Input Subsystems...
  • Page 73: Measurement Function

    Using the Subsystems Measurement Function The Measure function group has a differ- details about the signal you are going to ent level of compatibility and flexibility measure, for example: than other commands. The parameters SEND® MEASure:FREQ?8208MHz,1 used with commands from the Measure group describe the signal you are going to Where: 20 MHz is the expected value, measure.
  • Page 74 Using the Subsystems Example: 20E6 is the expected signal value 1 is the required resolution SEND® CONFigure:FREQ82E6,1 SEND® INPut:IMPedance81E6 2E6 is the expected value 1 is the required resolution (1Hz) Sets input impedance to 1 MW SEND® INPut:IMPedance850 SEND® INITiate Sets input impedance to 50 W Starts measurement SEND®...
  • Page 75: Sense Command Subsystems

    Using the Subsystems Sense Command Subsystems Depending on application, you can select Prescaling different input channels and input charac- For all measuring functions except time teristics. interval, rise/fall time, phase and time stamping, the maximum input A or B fre- Switchbox quency is 300 MHz.
  • Page 76: Status Subsystem

    Using the Subsystems Status Subsystem Introduction – The Questionable Data Register reports when the output data from the counter may Status reporting is a method to let the not be trusted. controller know what the counter is do- – The Device Register 0 reports when the ing.
  • Page 77 Using the Subsystems Example: Note that all event registers and the status byte record positive events. That is when The counter answers 40 when you ask for a condition changes from inactive to ac- the contents of the Standard Event Status tive, the bit in the event register is set Register.
  • Page 78: Status Byte Register

    Using the Subsystems – – Bit 3 is also true, showing that a device You set all bits true in 8-bit registers by dependent error has occurred. programming them to 255 (Service Re- quest Enable and Standard Event Enable.) Use the same technique when you pro- gram the enable registers.
  • Page 79 Using the Subsystems one or more data bytes. When the queue request, it may regularly test the is empty, the queue status bit is set false. SRQ-line, it may regularly make serial poll or *STB?, or the controller may not Status of the Output Queue (MAV) react at all.
  • Page 80 Using the Subsystems SRQ is true. If you read the status byte us- Using the Serial Poll (IEEE-488.1 de- ing *STB?, bit 6 represents MSS. MSS re- fined). mains true until all event registers are – Response: cleared and all queues are empty. Bit 6: RQS message, shows that the –...
  • Page 81 Using the Subsystems You can also clear all event registers with measurement cycle, for instance “Mea- the *CLS (Clear Status) command. surement stopped”. Although it is possible to read the Status Condition Registers condition registers directly, we recommend that you use SRQ Two of the status register structures also when monitoring the measure- have condition registers: The Status Op-...
  • Page 82 Using the Subsystems example, to call for the attention of the Standard Status Registers controller by generating a service request. These registers are called the standard status data structure because they are mandatory in all instruments that fulfill the IEEE 488.2 standard. Standard Event Status Register Bit 7 (weight 128) —...
  • Page 83 Using the Subsystems Bit 5 (weight 32) — Command Error has completed all previously started ac- tions. (CME) Shows that the instrument has detected a Summary, Standard Event command error. This means that it has re- Status Reporting ceived data that violates the syntax rules *ESE <bit mask>...
  • Page 84 Using the Subsystems SCPI-defined Status Registers The counter has two 16-bit SCPI-defined status structures: The operation status register and the questionable data regis- ter. These are 16 bits wide, while the sta- tus byte and the standard status groups are 8 bits wide. Standard Event Register Questionable Data Register Condition Register...
  • Page 85 Using the Subsystems Bit 4 (weight 16) — Measurement Operation Status Group Started (MST) This group reports the status of the coun- ter measurement cycle. This bit shows that the counter is measur- ing. It is set when the measurement or se- quence of measurements starts.
  • Page 86 Using the Subsystems Bit 10 (weight 1024) — Timeout for Questionable Data/Signal Measurement (TIO) Status Group The counter sets this bit true when it This group reports when the output data abandons the measurement because the from the counter may not be trusted. internal timeout has elapsed, or no signal has been detected.
  • Page 87 Using the Subsystems Device-defined Status Structure The counter has one device-defined status status byte. Its purpose is to report when structure called the Device Register 0. It the measuring result has exceeded pre- summarizes this structure in bit 0 of the programmed limits.
  • Page 88 Using the Subsystems *SRE 1 You set the limits with the following commands in the calculate subsystem. Enable SRQ when a limit is exceeded. :CALCulate:LIMit:UPPer and :STAT:DREG0? :CALCulate:LIMit:LOWer Reading and clearing the event register of Device Register structure 0. Bit Definition –...
  • Page 89: Trigger/Arming Subsystem

    Using the Subsystems Trigger/Arming Subsystem The ARM-TRIG Trigger The SCPI TRIGger subsystem enables syn- chronization of instrument actions with Configuration specified internal or external events. The gives a typical trigger configuration, the following list gives some examples. ARM-TRIG model. The configuration contains two event-detection layers: the Instrument Action ‘Wait for ARM’...
  • Page 90 Using the Subsystems This trigger configuration is sufficient for most instruments. More complex instru- IDLE *RST state ments, such as the '9X', have more ARM ABORt layers. INIT[:IMM] or The ‘Wait for TRIG’ event-detection INIT:CONT ON? layer is always the last to be crossed be- fore instrument actions can take place.
  • Page 91 Using the Subsystems layer). This delay can be programmed by Triggering using the <layer>:DELay command. *TRG Trigger Command Backward Traversing an The trigger command has the same func- Event-detection Layer tion as the Group Execute Trigger com- The number of times a layer event has to mand GET, defined by IEEE 488.1.
  • Page 92 Using the Subsystems Select Source Arming Start Layer 2 Event IMMediate <layer> detection (bus trig) :SOURce <layer>:IMMediate Event detection layer Layer loop <layer>:COUNt counter = 0 Completed No. of layer loop counts? Select Source Select Characteristics EXTernal4 IM M e d ia te <layer>...
  • Page 93: Error Messages

    Chapter 7 Error Messages...
  • Page 94 Error Messages empty, Read the Error/Event Queue :SYSTem:ERRor? query will return: You read the error queue with the :SYS- 0, “No error” Tem:ERRor? query. When errors occur and you do not read Example: these errors, the Error Queue may over- SEND®...
  • Page 95 Error Messages Command Errors Error Error Description Description/Explanation/Examples Number GET not allowed A Group Execute Trigger was received within a pro- –105 gram message (see IEEE-488.2, 7.7). Parameter not al- More parameters were received than expected for –108 the header; for example, the *EMC common com- lowed mand accepts only one parameter, so receiving *EMC0,,1 is not allowed.
  • Page 96 Error Messages Command Errors Error Error Description Description/Explanation/Examples Number Exponent too large The magnitude of the exponent was larger than –123 32000 (see IEEE-488.2, 7.7.2.4.1). Too many digits The mantissa of a decimal numeric data element con- –124 tained more than 255 digits excluding leading zeros (see IEEE-488.2, 7.7.2.4.1).
  • Page 97 Error Messages Command Errors Error Error Description Description/Explanation/Examples Number String data not al- A string data element was encountered but was not al- –158 lowed lowed at this point in parsing. Block data error This error as well as errors –161 through –169 is –160 generated when parsing a block data element.
  • Page 98 Error Messages Command Errors Error Error Description Description/Explanation/Examples Number Invalid expression The expression data element was invalid (see –171 data IEEE-488.2, 7.7.7.2); for example, unmatched pa- rentheses or an illegal character were used. Invalid expression A mnemonic data element in the expression was not data;...
  • Page 99 Error Messages Execution errors Error Error Description description/explanation/examples Number Execution error This is the generic syntax error for devices that can- –200 not detect more specific errors. This code indicates only that an Execution Error as defined in IEEE-488.2, 11.5.1.1.5 has occurred. Trigger error –210 Indicates that a GET, *TRG, or triggering signal was...
  • Page 100 Error Messages Execution errors Error Error Description description/explanation/examples Number Data out of range Indicates that a legal program data element was –222 parsed but could not be executed because the inter- preted value was outside the legal range as defined by the counter (see IEEE-488.2, 11.5.1.1.5.).
  • Page 101 Error Messages Execution errors Error Error Description description/explanation/examples Number Hardware missing Indicates that a legal program command or query –241 could not be executed because of missing counter Hardware missing; hardware; for example, an option was not installed. (prescaler)" Definition of what constitutes missing hardware is com- pletely device specific.
  • Page 102 Error Messages Execution errors Error Error Description description/explanation/examples Number Indicates that the macro label defined in the *DMC Illegal macro label –273 command was a legal string syntax, but could not be accepted by the counter (see IEEE-488.2, 10.7.3 and 10.7.6.2);...
  • Page 103 Error Messages Standardized Device specific errors Error Error Description description/explanation/examples Number Device specific error This code indicates only that a Device-Dependent –300 Error as defined in IEEE-488.2, 11.5.1.1.6 has oc- curred. Contact your local service center. Memory error Indicates that an error was detected in the counter’s –311 memory.
  • Page 104 Error Messages Query errors Error Error Description description/explanation/examples Number Query error This code indicates only that a Query Error as de- –400 fined in IEEE-488.2, 11.5.1.1.7 and 6.3 has oc- curred. Query Indicates that a condition causing an INTER- –410 INTERRUPTED RUPTED Query error occurred (see IEEE-488.2, 6.3.2.3);...
  • Page 105 Error Messages Device specific errors Error Error Description description/explanation/examples Number Device operation A floating-point error occurred during a counter op- (1)100 gave floating-point eration. underflow Device operation A floating-point error occurred during a counter op- (1)101 gave floating-point eration. overflow Device operation A floating-point error occurred during a counter op- (1)102...
  • Page 106 Error Messages Device specific errors Error Error Description description/explanation/examples Number Measurement bro- A new bus command caused a running measure- (1)160 ken off ment to be broken off. Instrument set to An internal setting inconsistency caused the instru- (1)170 default ment to go to default setting.
  • Page 107 Error Messages Device specific errors Error Error Description description/explanation/examples Number Parser error Generic error in the parser. (1)220 Illegal parser call The parser was called when it should not be active. (1)221 Unrecognized input A character not in the valid IEEE488.2 character set (1)222 character was part of a command.
  • Page 108 Error Messages This page is intentionally left blank. 7-16 Error Code...
  • Page 109: Command Reference

    Chapter 8 Command Reference...
  • Page 110 This page is intentionally left blank. 8-2 Command Reference...
  • Page 111: Abort

    Abort :ABORt Command Reference 8-3...
  • Page 112: Abort

    :ABORt Abort Measurement The ABORt command terminates a measurement. The trigger subsystem state is set to “idle-state”. The command does not invalidate already finished results when breaking an array measurement. This means that you can fetch a partial result af- ter an abort.
  • Page 113: Arming Subsystem

    Arming Subsystem :ARM [ :STARt | :SEQuence [ 1 ] ] :LAYer2 :[ IMMediate ] BUS | IMMediate :SOURce [ :LAYer [ 1 ] ] <Numeric value> | MIN | MAX | INF * :COUNt <Numeric value> | MIN | MAX :DELay POSitive | NEGative :SLOPe...
  • Page 114: Arm :Count

    :ARM :COUNt 8 <Numeric value>|MIN|MAX|INFinity * No. of Measurements on each Bus arm This count variable controls the upward exit of the “wait-for-bus-arm” state (:ARM:STARt:LAY1). The counter loops the trigger subsystem downwards COUNt number of times before it exits to the idle state. This means that a COUNt No.
  • Page 115: Arm :Delay

    :ARM :DELay 8 <Numeric value> | MIN | MAX Delay after External Start Arming This command sets a delay between the pulse on the selected arming input and the time when the counter starts measuring. Range: 20 ns to 2 s, 10 ns resolution. Parameters: –9 <Numeric value>...
  • Page 116: Arm :Layer2 :Source

    :ARM :LAYer2 :SOURce 8 «BUS | IMMediate» Bus Arming On/Off Switches between Bus and Immediate mode for the “wait-for-bus-arm” function, (layer 2). GET and *TRG triggers the counter if Bus is selected as source. If the counter receives GET/ *TRG when not in “wait-for-bus-arm” state, it ignores the trigger and generates an error.
  • Page 117: Arm :Source

    :ARM :SOURce 8 «EXTernal1 | EXTernal2 | EXTernal4 | IMMediate» External Start Arming Source Selects START arming input or switches off the start arming function. When switched off the DELay is inactive. Parameters: EXTernal1 is input A EXTernal2 is input B EXTernal4 is input E IMMediate is Start arming OFF Note: For the Totalize function in the CNT-91, IMM means manual start-stop using...
  • Page 118: Arm :Stop :Source

    :ARM :STOP :SOURce 8 «EXTernal1 | EXTernal2 | EXTernal4 | TIMer | IMMediate» External Stop Arming Source Selects STOP arming input or switches off the STOP arming function. The CNT-91 has also a programmable timer that is accessible in Totalize mode. Parameters: EXTernal1 is input A EXTernal2 is input B...
  • Page 119: Calculate Subsystem

    Calculate Subsystem :CALCulate 8 ON|OFF :STATe :DATA? :IMMediate :MATH 8 (<Numeric expression>) [:EXPRession] 8 ON|OFF :STATe :AVERage 8 ON|OFF [:STATe] 8 MIN|MAX|MEAN|SDEViation|ADEViation * :TYPE 8 <Numeric value>|MIN|MAX :COUNt :CURRent? :LIMit 8 ON|OFF [:STATe] :FAIL? :CLEar [:IMMediate] 8 ON|OFF :AUTO :FCOunt [:TOTal]? :LOWer? :TOTal?
  • Page 120: Calculate :Average :Count

    :CALCulate :AVERage :ALL? The Main Calculated Statistics Parameters Returns mean value, standard deviation, min and max value from the current sta- tistics sampling. <mean value>, <standard deviation>, <min value>, <max value>¿ Returned format: :CALCulate :AVERage :COUNt 8 < No. of samples> Sample Size for Statistics Sets the number of samples to use in statistics sampling.
  • Page 121: Calculate :Average :State

    :CALCulate :AVERage :COUNt :CURRent? Number of Statistics Samples Gathered Returns the number of samples currently gathered in the current statistics sam- pling. <No. of samples>¿ Returned format: :CALCulate :AVERage :STATe 8 < Boolean > Enable Statistics Switches On/Off the statistical function. Note that the CALCulate subsystem is au- tomatically enabled when the statistical functions are switched on.
  • Page 122: Calculate :Average :Type

    :CALCulate :AVERage :TYPE 8 «MAX|MIN|MEAN|SDEViation|ADEViation» Statistical Type Selects the statistical function to be performed. You must use :CALC:DATA? to read the result of statistical operations. :READ?, :FETC? will only send the results that the statistical operation is based on. Parameters: MAX returns the max.
  • Page 123: Calculate :Immediate

    :CALCulate :IMMediate Recalculate Data This event causes the calculate subsystem to reprocess the statistical function on the sense data without reacquiring the data. Query returns this reprocessed data. <Decimal data>¿ Returned format: Where: <Decimal data> is the recalculated data. Example: SEND®...
  • Page 124: Calculate :Limit :Clear

    :CALCulate :LIMit :CLEar Clear Limit Failure Count The command resets the counter that reports its result over the :CALCulate:LIMit:FCOunt? query command. :CALCulate :LIMit :CLEar :AUTO 8 <Boolean> Automatic Reset of Limit Failure Count The command activates (ON) or deactivates (OFF) automatic reset by :INIT of the counter that reports its result over the :CALCulate:LIMit:FCOunt? query command.
  • Page 125: Calculate :Limit :Fail

    :CALCulate :LIMit :FAIL? Limit Fail Returns a 1 if the limit testing has failed (the measurement result has passed the limit), and a 0 if the limit testing has passed. The following events reset the fail flag: – Power-on – *RST A:CALC:LIM:STAT8OFF ®...
  • Page 126: Calculate :Limit :Fcount

    :CALCulate :LIMit :FCOunt? Number of Limit Failure Counts The command returns the total number of times the set lower and upper limits have been passed since the counter was last reset by :CALC:LIM:CLEAR or auto- matically by :INIT if :CALC:LIM:CLEAR:AUTO ON has been activated. In other words, the returned value is the sum of the values returned by :CALCu- late:LIMit:FCOunt:LOWer? and :CALCulate:LIMit:FCOunt:UPPer? <...
  • Page 127: Calculate :Limit :Pcount

    :CALCulate :LIMit :PCOunt? Number of Pass Counts The command returns the number of measurement results between the set lower and upper limits since the counter was last reset by :CALC:LIM:CLEAR or auto- matically by :INIT if :CALC:LIM:CLEAR:AUTO ON has been activated.. <...
  • Page 128: Calculate :Limit :Lower :State

    :CALCulate :LIMit :LOWer :STATe 8 <Boolean> Check Against Lower Limit Selects if the measured value should be checked against the lower limit. <Boolean> = ( 1/ON | 0/OFF ) Parameters 1| 0 ¿ Returned format: *RST condition: Complies with standards: SCPI 1991.0 confirmed.
  • Page 129: Calculate :Limit :Upper :State

    :CALCulate :LIMit :UPPer :STATe 8 <Boolean> Check Against Upper Limit Selects if the measured value should be checked against the upper limit. <Boolean> = ( 1/ON | 0/OFF ) Parameters 1| 0 ¿ Returned format: *RST condition: Complies with standards: SCPI 1991.0, confirmed.
  • Page 130: Calculate :Math :State

    :CALCulate :MATH :STATe 8 <Boolean> Enable Mathematics Switches on/off the mathematical function. Note that the CALCulate subsystem is automatically enabled when MATH operations are switched on. This means that other enabled calculate sub-blocks are indirectly switched on. Switching off mathe- matics, however, does not switch off the CALCulate subsystem.
  • Page 131: Calculate :Totalize :Type

    :CALCulate :TOTalize :TYPE CNT-91 8 APLUSB|AMINUSB|ADIVB Select Postprocessing for Totalize If both counting registers (primary and secondary channel) are being used, you can manipulate the measurement results before presentation by selecting one of three postprocessing formulas that operate directly on the raw data. Parameters APLUSB selects the expression A + B to add the results in the two registers.
  • Page 132 This page is intentionally left blank. 8-24 Command Reference...
  • Page 133: Calibration Subsystem

    Calibration Subsystem :CALibration :INTerpolator 8 <Boolean> :AUTO Command Reference 8-25...
  • Page 134: Calibration :Interpolator :Auto

    :CALibration :INTerpolator :AUTO 8 <Boolean> Calibration of Interpolator The '9X' is a reciprocal counter that uses an interpolating technique to increase the resolution. In time measurements, for example, interpolation increases the resolu- tion from 10 ns to 0.1 ns. The counter calibrates the interpolators automatically once for every measurement when this command is ON.
  • Page 135: Configure Function

    Configure Function Set up Instrument for Measurement :CONFigure 8 <Parameters>,(<Channels>)] [:SCALar]<Measuring Function> 8 (<Array Size>)[,<Parameters>,(<Channels>)] :ARRay<Measuring Function> The array size for :MEASure and :CONFigure, and the channels, are expression data that must be in parentheses ( ). Measuring Function, Parameters and Channels are explained on page 8-54. The counter uses the default Parameters and Channels when you omit them in the command.
  • Page 136: Configure :

    :CONFigure :<Measuring Function> [8 <parameters>[,(<channels>)]] Configure the counter for a single measurement Use the configure command instead of the measure query when you want to change other settings, for instance, the input settings before making the measure- ment and fetching the result. The :CONFigure command controls the settings of the Input, Sense and Trigger sub- systems in the counter in order to make the best possible measurement.
  • Page 137: Configure :Array :

    To make the measurements and fetch the seven measurement results: SEND® :READ:ARR? 8 7 READ¬ 5.23421E-3,5.12311E-3,5.87526E-3, 8 5.50345E-3,5.33901E-3,5.25501E-3, 8 5.03571E-3 Array Size Function Interpolator Calibration ON Interpolator Calibration OFF Freq, Per & CNT-90 CNT-91 CNT-90 CNT-91 most other 375 k 1.9 M 750 k 3.8 M...
  • Page 138: Configure :Totalize [:Continuous]

    :CONFigure :TOTalize [:CONTinuous] CNT-91 [8 (@«1|2»)][,(@«1|2»)] Totalize Manually This is a count/totalize function controlled from the GPIB interface using the com- mand SENS:TOT:GATE8ON|OFF. The counter counts up for each event on the primary input channel. The same ap- plies to the secondary channel if it has been activated. The result is one or two val- ues depending on the presence of the secondary channel.
  • Page 139: Display Subsystem

    Display Subsystem :DISPlay 8 ON OFF :ENABle 8-31 Command Reference...
  • Page 140: Display :Enable

    :DISPlay :ENABle 8 < Boolean > Display State Turns On/Off the updating of the entire display section. This can be used for secu- rity reasons or to improve the GPIB speed, since the display does not need to be updated. <Boolean>...
  • Page 141: Fetch Function

    Fetch Function :FETCh [:SCALar]? 8 <Array Size>|MAX * :ARRay? * CNT-91 only Command Reference 8-33...
  • Page 142: Fetch

    :FETCh? Fetch One Result The fetch query retrieves one measuring result from the measurement result buffer of the counter without making new measurements. Fetch does not work unless a measurement has been made by the :INITiate, :MEASure?, or :READ? com- mands.
  • Page 143: Fetch :Array

    :FETCh :ARRay? 8 <fetch array size>|MAX * Fetch an Array of Results :FETCh:ARRay? query differs from the :FETCh? query by fetching several mea- suring results at once. An array of measurements must first be made by the commands. :INITiate, :MEASure:ARRay? or :CONFigure:ARRay;:READ? If the array size is set to a positive value, the first measurement made is the first result to be fetched.
  • Page 144 GPIB MODE FORMAT NATIVE COMPATIBLE ASCii <LF> 9.91E37 REAL #18<Binary NaN> #18<9.91E37 in binary format> PACKED #18<Binary NaN> #18<9.91E37 in binary format> NaN = Not a Number, a standardized bit pattern indicating that the transferred data is not a valid result. FORMAT ASCii REAL...
  • Page 145: Format Subsystem

    Format Subsystem :FORMat 8 ASCii | REAL | PACKed [:DATA] 8 NORMal | SWAPped :BORDer 8 <Numeric value> * :SMAX 8 <Boolean> :TINFormation[:STATe] * CNT-91 only Command Reference 8-37...
  • Page 146: Format

    :FORMat 8 ASCii|REAL|PACKed Response Data Type Sets the format in which the result will be sent on the bus. Parameters: ASCii: The length will be automatically controlled by the resolution of each measurement re- sult. REAL: The length parameter is ignored; the output is always in 8-byte format. PACKed: See REAL.
  • Page 147: Format :Smax

    :FORMat :SMAX CNT-91 8 <Numeric value> Upper Limit for Array Size Sets or queries the upper limit for :FETCh:ARRay? MAX command in number of samples. The command is intended for use with any controllers or application pro- grams that cannot read large amounts of data, when the functionality of the :FETCh:ARRay? MAX command is still interesting.
  • Page 148: Format :Tinformation

    :FORMat :TINFormation 8 Boolean Timestamping On/Off This command turns on/off the time stamping of measurements. Time stamping is always done at the start of a measurement with full measurement resolution, and is saved in the measurement buffer together with the measurement result. The setting of this command will affect the output format of the MEASure, READ and FETCh queries.
  • Page 149: Hard Copy

    Hard Copy :HCOPy :SDUMp :DATA? 8-41 Command Reference...
  • Page 150: Hcopy :Sdump :Data

    :HCOPy :SDUMp :DATA? Screen Dump Return block data containing screen dump in Windows BMP format. Returned Format: #43942<Binary BMP Data> The '4' means that the following four digits (3942) tell how many data bytes will succeed. The proper screen data is preceded by a 62-byte header, which means that 3942 - 62 = 3880 bytes carry the pixel information.
  • Page 151: Initiate Subsystem

    Initiate Subsystem :INITiate [:IMMediate ] 8 ON | OFF :CONTinuous Command Reference 8-43...
  • Page 152: Initiate

    :INITiate Initiate Measurement The :INITiate command initiates a measurement. Executing an :INITiate command changes the counter’s trigger subsystem state from “idle-state” to “wait-for-bus-arm-state” (see Figure 6-11). The trigger subsystem will continue to the other states, depending on programming. With the *RST setting, the trigger subsystem will bypass all its states and make a measurement, then return to idle state.
  • Page 153: Input Subsystems

    Input Subsystems INPUT A :INPut[1] 8 <Numeric value>|MIN|MAX (1|10) :ATTenuation 8 AC|DC :COUPling 8 <Numeric value>|MIN|MAX :IMPedance [:EVENt] 8 <Numeric value>|MIN|MAX :LEVel 8 ON|OFF|ONCE :AUTO 8 <Numeric value> :RELative 8 POS|NEG :SLOPe :FILTer [:LPASs] 8 ON|OFF [:STATe] 8 ON|OFF :DIGital 8 <Numeric value>|MIN|MAX :FREQuency INPUT B...
  • Page 154: Input«[1]|2» :Attenuation

    :INPut«[1]|2» :ATTenuation 8 «<Numeric value>|MAX|MIN» Attenuation Attenuates the input signal by 1 or 10. The attenuation is automatically set if the in- put level is set to AUTO. Parameters: <Numeric values> £ 5, and MIN gives attenuation 1. <Numeric values> > 5, and MAX gives attenuation 10. Returned format: 1.00000000000E+000|1.00000000000E+001 ¿...
  • Page 155: Input«[1]|2» :Filter

    :INPut«[1]|2» :FILTer 8 <Boolean> Analog Low Pass Filter Switches on or off the analog low pass filter on input 1 (A) and/or input 2 (B). It has a cutoff frequency of 100 kHz. Parameters: <Boolean> is «1 | ON» | «0 | OFF» 1|0¿...
  • Page 156: Frequency

    :INPut«[1]|2» :FILTer :DIGital :FREQuency 8<Numeric value>|MIN|MAX Set the Digital Low Pass Filter Cutoff Frequency Any frequency between 1 Hz and 50 MHz can be entered. The filter is activated by the command: :INPut«[1]|2»:FILTer:DIGital8ON|OFF Parameters: <Numeric value> is a value between 1 and 50 * 10 MIN means 1 Hz MAX means 50 MHz <Numeric value>¿...
  • Page 157: Input«[1]|2» :Level

    :INPut«[1]|2» :LEVel 8 «<Decimal data>|MAX|MIN» Fixed Trigger Level Input A and input B can be individually set to autotrigger or to fixed trigger levels of between –5 V and +5 V in steps of 2.5 mV. If the attenuator is set to 10X, the range is –50 V and +50 V in 25 mV steps.
  • Page 158: Input«[1]|2» :Level :Relative

    In this way you can benefit from the automatic trigger level adjustment without sac- rificing measurement speed. From the bus, input A and input B are always set to autotrigger individually. Parameters: <Boolean> = ( 1/ON | 0/OFF | ONCE) Example for Input A (1) SEND®...
  • Page 159: Input«[1]|2» :Slope

    :INPut«[1]|2» :SLOPe 8 «POS|NEG» Trigger Slope Selects if the counter should trigger on a positive or a negative transition. Selecting negative slope is useful for Time Interval measurements. The slope is fixed for Pos/Neg Pulse Width/Duty Factor and Rise/Fall Time. Arming slope is not affected by this command.
  • Page 160 This page is intentionally left blank. 8-52 Command Reference...
  • Page 161: Measurement Function

    Measurement Function Set up the Instrument, Perform Measurement, and Read Data :MEASure [:SCALar]<Measuring Function>? [<Parameters>][,(<Channels>)] 8 (<Array Size>)[,<Parameters>][,(<Channels>)] :ARRay<Measuring Function>? 8 [<N>] :MEMory? :MEMory<N>? The array size for :MEASure and :CONFigure, and the channels, are expression data that must be within parentheses ( ). The question mark at the end of the commands is only valid for :MEASure, where a result is expected.
  • Page 162 :MEASure|:CONFigure [:SCALar] [:VOLTage] :FREQuency [:CW]? [ _ [<exp. value>[,<resol.>],][(@1|@2|@3|@4|@6)]] :BTBack? * [ _ [<exp. value>[,<resol.>],][(@1|@2)]] :BURSt? [ _ [<exp. value>[,<resol.>],][(@1|@2|@3)]] :POWer[:AC]? ** [ _ (@3)] :PRF? [ _ [<exp. value>[,<resol.>],][(@1|@2|@3)]] :RATio? [ _ [<exp. value>[,<resol.>],][(@1|@2|@3),(@1|@2|@3)]] :NCYCles? [ _ (@1|@2|@3)] :PDUTycycle|:DCYCle?[ _ [<reference>,][(@1|@2)]] :NDUTycycle? [ _ [<reference>,][(@1|@2)]] :MAXimum?
  • Page 163 :ARRay [:VOLTage] :FREQuency [:CW]? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2|@3|@4|@6)]] :BTBack? * _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2)]] :BURSt? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2|@3)]] :POWer[:AC]? ** _ (<Size>)[,(@3)] :PRF? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2|@3)]] :RATio? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2|@3),(@1|@2|@3)]] :NCYCles? _ (<Size>)[,(@1|@2|@3)] :PDUTycycle|:DCYCle? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2)]] :NDUTycycle? _ (<Size>)[,[<exp. value>[,<resol.>],][(@1|@2)]] :MAXimum? _ (<Size>)[,(@1|@2)] :MINimum? _ (<Size>)[,(@1|@2)]...
  • Page 164: Measure :

    :MEASure :<Measuring Function>? [8 [<parameters>][ ,(<channels>)]] Make one measurement The measure query makes a complete measurement, including configuration and readout of data. Use measure when you can accept the generic measurement without fine tuning. When a CONFigure command or MEASure? query is issued, all counter settings are set to the *RST settings., except those specified as <parameters>...
  • Page 165: Measure :Array :

    :MEASure :ARRay :<Measuring Function>? 8 (<array size>)[,[<parameters>] [,(<channels>)]] Make an array of measurements The :MEASure:ARRay query differs from the :MEASure query in that it performs the number of measurements you decide in the <array size> and sends all the measuring results in one string to the controller. The array size for :MEASure and :CONFigure, and the channels, are expression data that must be in parentheses ( ).
  • Page 166: Measure :Memory

    :MEASure :MEMory<N>? Memory Recall, Measure and Fetch Result Use this command when you want to measure several parameters fast. :MEAS:MEM1? recalls the contents of memory 1 and reads out the result, :MEAS:MEM2? recalls the contents of memory two and reads out the result etc. The equivalent command sequence is *RCL1;READ? The allowed range for <N>...
  • Page 167: Explanations Of The Measuring Functions

    EXPLANATIONS OF THE MEASURING FUNCTIONS This sub-chapter explains the various measurements that can be done with :MEASure and :CONFigure;:READ?. Only the queries for single measurements using the measure command are given here, but all of the information is also valid for the :CONFigure command and for both scalar (single) and array measurements.
  • Page 168: Measure :Frequency

    :MEASure :FREQuency? [8 [<expected value>[,<resolution>]] [,<(@«1|2|3|4|6»)>]] Frequency Traditional frequency measurements. The counter uses the <expected value> and <resolution> to calculate the Measurement Time (:SENSe:ACQuisition:APER- ture). Example: SEND® :MEAS:FREQ? 8 (@3) READ¬ 1.78112526833E+009 This example measures the frequency at input C. The channel is expression data and it must be in parentheses ( ).
  • Page 169: Measure :Frequency :Burst

    (@1) means input A (@2) means input B (@3) means input C (RF input, option for CNT-90, standard for CNT-90XL) (@4) means input E (Rear panel arming input) If you omit the channel, the instrument measures on input A (@1).
  • Page 170: Measure :Frequency :Prf

    :MEASure :FREQuency :PRF? [8 [<exp. val.>[,<res.>]][,<(@«1|2|3|4»)>]] Pulse Repetition Frequency Measures the PRF (Pulse Repetition Frequency) of a burst signal.The burst dura- tion must be less than 50% of the pulse repetition frequency (PRF). It is better to set up the measurement with the [:SENS]:FUNC “:FREQ:PRF” command when measuring pulse repetition frequency.
  • Page 171: Measure :Frequency :Ratio

    :MEASure :FREQuency :RATio? [8 [<expected value> [,<resolution>]][,<(@«1|2|3»)>,<(@«1|2|3»)>]] Frequency Ratio Frequency ratio measurements between two inputs. Example: SEND® :MEAS:FREQ:RAT? 8 (@1),(@3) READ¬ 2.345625764333E+000 This example measures the ratio between input A and input C. The channel is expression data and must be within parentheses ( ). <expected value>...
  • Page 172: Measure «:Pdutycycle | :Dcycle

    :MEASure «:PDUTycycle | :DCYCle»? [8 [<threshold>] [,(@«1|2»)]] Positive duty cycle: Duty Factor Traditional duty cycle measurement is performed. That is, the ratio between the on time and the off time of the input pulse is measured. Parameters <threshold> parameter sets the trigger levels in volts. If omitted, the auto trigger level is set to 50 percent of the signal.
  • Page 173: Measure [:Volt] :Maximum

    :MEASure [:VOLT] :MAXimum? [ 8 («@1|@2»)] Positive Peak Voltage This command measures the positive peak voltage with the input DC coupled. Parameters: («@1|@2») is the measurement channel (@1) means input A (@2) means input B Complies with standards: SCPI 1991.0, confirmed. :MEASure [:VOLT] :MINimum? [ 8 («@1|@2»)] Negative Peak Voltage...
  • Page 174: Measure [:Volt] :Ptpeak

    :MEASure [:VOLT] :PTPeak? [8 (@«1|2»)]. Peak-to-Peak Voltage This command measures the peak-to-peak voltage on either main input channel. Parameters: (@«1|2») is the measurement channel (@1) means input A (@2) means input B Complies with standards: SCPI 1991.0, confirmed. :MEASure [:VOLT] :RATio? [8(@1|@2),(@1|@2)] Peak-to-Peak Voltage Ratio in dB This command measures the peak-to-peak voltage ratio in dB between the se-...
  • Page 175: Measure [:Volt] :Pslewrate

    :MEASure [:VOLT] :PSLEwrate? [8(@1|@2)] Positive Slew Rate This command measures the positive slew rate in V/s on either main input channel. Parameters: (@«1|2») is the measurement channel (@1) means input A (@2) means input B :MEASure [:VOLT] :NSLEwrate? [8(@1|@2)] Negative Slew Rate This command measures the negative slew rate in V/s on either main input chan- nel.
  • Page 176: Measure :Period

    :MEASure :PERiod? [8 [<expected value> [,<resolution>]][,<(@«1|2|3»)>]] Period A traditional period time measurement is performed on a single period. Measuring time set by the :ACQ:APER command does not affect the measurement. The <expected value> and <resolution> are used to calculate the Measurement Time ([:SENSe]:ACQuisition:APERture).
  • Page 177: Measure :Phase

    :MEASure :PHASe? [8 [<expected value>[,<resolution>]] [,(@«1|2»),(@«1|2»)]] Phase A traditional PHASe measurement is performed. Parameters: <expected value> and <resolution> are ignored by the counter The first (@«1|2») is the start channel and the second (@«1|2») is the stop channel (@1) means input A (@2) means input B If you omit the channel, the instrument measures between input A and input B.
  • Page 178: Measure «:Fall :Time | :Ftim

    :MEASure «:FALL :TIME | :FTIM»? [8 [<lower threshold> [,<upper threshold>[,<expected value>[,<resolution>]]]] [,(@1|@2)]] Fall Time The transition time from 90% to 10% of the signal amplitude is measured. The measurement is always a single measurement and the Auto-trigger is always on, setting the trigger levels to 90% and 10 % of the amplitude. If you need an av- erage transition time measurement, or other trigger levels, use the :SENSe sub- system and manually set trigger levels instead.
  • Page 179: Measure :Pwidth

    :MEASure :PWIDth? [8 [<threshold>] [,<(@«1|2»)>]] Positive Pulse Width A positive pulse width measurement is performed. This is always a single measurement. If you need an average pulse width mea- surement, use the :SENSe subsystem instead. Parameters <threshold> parameter sets the trigger levels in volts. If omitted, the auto trigger level is set to 50 percent of the signal.
  • Page 180: Measure :Array :Ststamp

    :MEASure :ARRay :STSTamp? CNT-91 8(<array size>)[,(@1)|(@2)] Single Time Stamp A time stamp (TS) is taken of the trigger level crossing on the selected input chan- nel. The commands :MEAS and :CONF automatically invoke :FORM:TINF ON to get the time stamp data, but when :FUNC is used instead, you should normally let it be preceded by the :FORMat:TINFormation ON command explicitly.
  • Page 181: Measure :Array :Tstamp

    :MEASure :ARRay :TSTAmp? 8(<array size>)[,(@1)|(@2)] Time Stamp Time stamps are taken of all positive and negative trigger level crossings of the se- lected input channel. The commands :MEAS and :CONF automatically invoke :FORMat:TINFormation ON to get the time stamp data, but when :FUNC is used instead, you should normally let it be preceded by the :FORMat:TINFormation ON command explicitly.
  • Page 182: Btback

    :MEASure: ARRay: FREQuency: BTBack? CNT-91 8(<array size>)[,(@1)|(@2)] Frequency Back-to-Back STATISTICS This is the inverse function of Period Back-to-Back. See below. In mode measurement time is used for pacing the time stamps. The pacing parameter is not used in this case. Thus a series of consecutive frequency average measure- ments without dead time can be made in order to fulfil the requirements for correct calculation of Allan variance or deviation.
  • Page 183: Measure: Array: Tierror

    :MEASure: ARRay: TIError? CNT-91 8 (array size)[,[<exp value>[,<resol>],][(@1|(@2)]] Time Interval Error (TIE) This command automatically performs TIE measurements on clock signals from a predefined collection of system frequencies. See list on page 8-100. TIE is defined as positive and increasing if the measured frequency exceeds the reference frequency.
  • Page 184 This page is intentionally left blank. 8-76 Command Reference...
  • Page 185: Memory Subsystem

    Memory Subsystem :MEMory :DATA :RECord 8 [<Dataset Number>] :COUNt? 8 <Dataset Number> :DELete 8 <Dataset Number> :FETCh? 8 <Dataset Number>,<Number of Samples>|MAX :ARRay? 8 <Dataset Number> :STARt 8 [<Dataset Number>] :NAME? 8 <Dataset Number>[,<Label>] :SAVE 8 <Dataset Number> :SETTings? :DELete 8 ‘<Macro name>’...
  • Page 186: Memory :Data :Record :Count

    :MEMory :DATA :RECord :COUNt? 8 [<Dataset Number>] Number of Samples in Dataset If the optional <Dataset Number> parameter is specified, the command returns the number of samples in the corresponding FLASH memory position 0-7. If no parameter is specified, a comma-separated list is returned, containing the number of samples in each of the eight FLASH memory positions 0-7.
  • Page 187: Array

    :MEMory :DATA :RECord :FETCh? 8 <Dataset Number> Fetch Sample in Dataset The command fetches one sample from the FLASH memory position with the num- ber (0-7) given in the command parameter <Dataset Number>. Set the start position with the command :MEMory:DATA:RECord:FETCh:STARt. :MEMory :DATA :RECord :FETCh :ARRay? 8 <Dataset Number>,<Number of Samples>|MAXimum Fetch Array of Samples in Dataset...
  • Page 188: Start

    :MEMory :DATA :RECord :FETCh :STARt 8 <Dataset Number> Set Start Position for Dataset Fetch The data pointer is set to the first sample in the Dataset entered as a number (0-7) in the command parameter <Dataset Number>. :MEMory :DATA :RECord :NAME? 8 [<Dataset Number>] Get Name of Dataset If the optional <Dataset Number>...
  • Page 189: Memory :Data :Record :Save

    :MEMory :DATA :RECord :SAVE 8 <Dataset Number>[,<Label>] Save Measurement Data Array to Internal FLASH Memory One of the eight (0-7) memory positions must be entered, but you can also enter an optional name (max 6 characters) for easier recognition. A default name will be assigned automatically if you omit the <Label> parameter. It represents the abbreviated measurement function and the channel.
  • Page 190: Memory :Free :Macro

    :MEMory :DELete :MACRo 8 ‘<Macro name>’ Delete one Macro This command removes an individual MACRo Parameters ‘<Macro name>’ is the name of the macro you want to delete. <Macro name> is String data that must be surrounded by quotation marks. See also: *PMC, if you want to delete all macros.
  • Page 191: Memory :Nstates

    :MEMory :NSTates? Memory States The Number of States query (only) requests the number of *SAV/ *RCL instrument setting memory states available in the counter. The counter responds with a value that is one greater than the maximum that can be sent as a parameter to the *SAV and *RCL commands.
  • Page 192 This page is intentionally left blank. 8-84 Command Reference...
  • Page 193: Output Subsystem

    Output Subsystem Control the pulse output (CNT-91 only) :OUTPut 8 NORMal | INVerted * :POLarity 8 PULSe | GATE | ALARm | OFF :TYPE * Only for ALARM, “high” is NORMAL See SOURCE Subsystem on page 8-103 for time parameter setting commands. Command Reference 8-85...
  • Page 194: Output :Polarity

    :OUTPut :POLarity CNT-91 8 NORMal | INVerted Output Polarity The command controls the polarity of the pulse output, but only if it is configured as an alarm circuit. See also the command :OUTPut:TYPE. Parameters NORMal means that the output level is high when the alarm has been activated. INVerted means that the output level is low when the alarm has been activated.
  • Page 195: Read Function

    Read Function Perform Measurement and Read Data :READ [:SCALar]? 8 <Array Size>|MAX :ARRay? Command Reference 8-87...
  • Page 196: Read

    :READ? Read one Result The read function performs new measurements and reads out a measuring result without reprogramming the counter. Using the :READ? query in conjunction with the :CONFigure command gives you a measure capability where you can fine tune the measurement.
  • Page 197: Read :Array

    :READ :ARRay? 8 «<array size for FETCh>|MAX» Read an array of results The :READ:ARRay? query differs from the :READ? query by reading out several results at once after making the number of measurements previously set up by :CONFigure:ARRay 8 or 8 :MEASure:ARRAy?. The :READ:ARRay? query is identical to: :ABORt;:INITiate;:FETCh:ARRay?_<array size for FETCh>...
  • Page 198 This page is intentionally left blank. 8-90 Command Reference...
  • Page 199: Sense Command Subsystem

    Sense Command Subsystem Sense Subsystem Command Tree [:SENSe] :ACQuisition 8 <meas time> | MIN | MAX :APERture :HOFF 8 ON | OFF [:STATe] 8 TIME :MODE 8 <numeric value> | MIN | MAX :TIME 8 ONCE :AUTO :FREQuency :BURSt 8 <numeric value> | MIN | MAX :APERture :STARt 8 <numeric value>...
  • Page 200: Acquisition :Aperture

    :ACQuisition :APERture 8 «<Decimal value > | MIN | MAX» Set the Measurement Time Sets the gate time for one measurement. <decimal value> is 20 ns to 1000 s. Parameters: MIN gives 20 ns and MAX gives 1000 s. ¿ Returned format: <Decimal value >...
  • Page 201: Acquisition :Hoff :Time

    :ACQuisition :HOFF :TIME 8 «<Decimal value> | MIN | MAX» Hold Off Time Sets the Hold Off time value. Parameters: <Decimal data> = a number between 20E–9 and 2.0 Returned format: <Decimal value>¿ *RST condition: 200 ms :AUTO 8 ONCE | PRESet Autoset from the Bus Performs the same task as the front panel button AUTO SET.
  • Page 202: Frequency :Burst :Prescaler

    :FREQuency :BURSt :APERture 8 «<Numeric value>|MIN|MAX» Burst Measuring Time Sets the time length within a burst during which the burst frequency is measured. <Numeric value> = a number between 20 ns and 2 s. Parameters: <Numeric value>¿ Returned format: 200 ms *RST condition: :FREQuency :BURSt :PREScaler [:STATe] 8 <Boolean>...
  • Page 203: Frequency :Burst :Sync :Period

    :FREQuency :BURSt :STARt :DELay 8 «<Numeric value>|MIN|MAX» Burst Start Delay Sets the burst start delay, i.e. the time length between the burst start and the actual start of the burst measuring time. This parameter is used for controlling the point of time when a measurement sample is taken.
  • Page 204: Frequency :Power :Unit

    :FREQuency :POWer :UNIT CNT-90XL 8 DBM|W Input C Measurement Unit Selects dBm or W as the basic measurement unit to be displayed or read out. DBM | W Parameters: The reference level 0 dBm is 1 mW in 50 W. Increasing the level by 3 dB means doubling the power.
  • Page 205: Function

    :FREQuency :REGRession 8 ON|OFF|AUTO Smart Frequency Despite its name, this command also applies to Period Average. By means of continuous time stamping and linear regression analysis, the resolu- tion compared to a “normal” reciprocal counter is improved by one or two digits for measuring times between 200 ms and 100 s.
  • Page 206 Functions and Channels 8 ‘ 1 | 2 | 3 | 4 | 6 ‘ ] :FREQuency [ :CW ] 8 ‘ 1 | 2 | 3 , 1 | 2 | 3 ‘ ] :FREQuency [ :CW ] :RATio 8 ‘...
  • Page 207: Hf :Acquisition [:State]

    :HF :ACQuisition [:STATe] CNT-90XL 8 <Boolean> Input C Acquisition ON/OFF Switches the automatic acquisition system ON or OFF. ON means Automatic Ac- quisition, OFF means Manual Acquisition. When the instrument is switched from remote to local operation, Automatic Acquisition mode is entered, irrespective of the previous remote setting.
  • Page 208: Roscillator :Source

    :ROSCillator :SOURce 8 «INT|EXT|AUTO» Select Reference Oscillator Selects the signal from the external reference input as timebase instead of the in- ternal timebase oscillator. If the parameter is set to the default value AUTO, external reference will be used, if present. <INT|EXT|AUTO>¿...
  • Page 209: Tinterval :Auto

    :TIError :FREQuency CNT-91 8 <Numeric value> Set Basic TIE Frequency An arbitrary frequency in the range 1 Hz to 100 MHz can be entered (increment = 1 Hz). Subsequent TIE measurements are made by continuous timestamping of the input signal and the internal/external timebase clock. Observations of Wander, for instance, can easily be made by means of this command and the function :MEASure:ARRay:TIError? in conjunction with the built-in statistics/graphics fa- cilities.
  • Page 210: Totalize :Gate

    :TOTalize :GATE CNT-91 8 ON | OFF Control the GATE in Totalize Manual Mode Open/closes the gate for :CONFigure:TOTalize[:CONTinuous]. Before opening the gate with this command, the counter must be in the ‘contin- uously initiated’ state (:INIT:CONT 8 ON), or else the totalizing will not start. <Boolean>...
  • Page 211: Source Subsystem

    Source Subsystem Set Time Parameters for Pulse Output (CNT-91 only) :SOURce :PULSe 8 <Numeric value> :PERiod 8 <Numeric value> :WIDTh Command Reference 8-103...
  • Page 212: Source :Pulse :Period

    :SOURce :PULSe :PERiod CNT-91 8 <Numeric value> Set Pulse Period The pulse generator time parameters are activated when the output type is config- ured to PULSe using the :OUTPut command. See page 8-85. <Numeric value> = a number between 20 * 10 and 2 s in 10 ns increments.
  • Page 213: Status Subsystem

    Status Subsystem :STATus :DREGister0 8 <bit mask> :ENABle [:EVENt]? :OPERation :CONDition? 8 <bit mask> :ENABle [:EVENt]? :QUEStionable :CONDition? 8 <bit mask> :ENABle [:EVENt]? :PRESet Related Common Commands: *CLS 8 <bit mask> *ESE *ESR? 8 <bit mask> *PSC 8 <bit mask> *SRE *STB? Command Reference 8-105...
  • Page 214: Status :Dregister0

    :STATus :DREGister0? Read Device Status Event Register This query reads out the contents of the Device Event Register. Reading the De- vice Event Register clears the register. See Figure 6-10. Returned format: <dec.data> = the sum (between 0 and 6) of all bits that are true. See table below: Bit No.
  • Page 215: Status :Operation :Condition

    :STATus :OPERation :CONDition? Read Operation Status Condition Register Reads out the contents of the operation status condition register. This register re- flects the state of the measurement process. See table below. Returned Format: <Decimal data> = the sum (between 0 and 368) of all bits that are true. See table below: Bit No.
  • Page 216: Status :Operation :Enable

    :STATus :OPERation :ENABle 8 <Decimal data> Enable Operation Status Reporting Sets the enable bits of the operation status enable register. This enable register contains a mask value for the bits to be enabled in the operation status event reg- ister. A bit that is set true in the enable register enables the corresponding bit in the status register.
  • Page 217: Status: Operation

    :STATus: OPERation? Read Operation Status, Event Reads out the contents of the operation event status register. Reading the Opera- tion Event Register clears the register. See figure on page 8-107. <Decimal data>¿ Returned Format: <dec.data> = the sum (between 0 and 368) of all bits that are true. See table on page 8-108. Complies with standards: SCPI 1991.0, confirmed.
  • Page 218: Status :Questionable :Condition

    :STATus :QUEStionable :CONDition? Read Questionable Data/Signal Condition Register Reads out the contents of the status questionable condition register. Returned Format: <dec.data> = the sum (between 0 and 17920) of all bits that are true. See table below: Bit No. Weight Condition 16384 Unexpected parameter...
  • Page 219: Status :Questionable :Enable

    :STATus :QUEStionable :ENABle 8 <Decimal data> Enable Questionable Data/Signal Status Reporting Sets the enable bits of the status questionable enable register. This enable register contains a mask value for the bits to be enabled in the status questionable event register. A bit that is set true in the enable register enables the corresponding bit in the status register.
  • Page 220 This page is intentionally left blank. 8-112 Command Reference...
  • Page 221: System Subsystem

    System Subsystem :SYSTem :COMMunicate :GPIB 8 <Numeric value> | MIN | MAX :ADDRess :ERRor? :INSTrument :TBASe :LOCK? 8 NATive | COMPatible :LANGuage :PRESet 8 <Block data> :SET 8 ON :TALKonly :TEMPerature? :TOUT 8 ON | OFF [:STATe] 8 ON | OFF :AUTO 8 <timeout value>...
  • Page 222: System :Error

    :SYSTem :COMMunicate :GPIB :ADDRess 8 «<Numeric value>|MAX|MIN» [,«<Numeric value>|MAX|MIN»] Set GPIB Address This command sets the GPIB address. It is valid until a new address is set, either by sending a new bus command or via the front panel USER OPT menu. Parameters: <Numeric value>...
  • Page 223: System :Language

    :SYSTem: INSTRument: TBASe: LOCK? CNT-91R Check Rubidium Oscillator Status Query command returning the status of the rubidium oscillator control loop. <Numeric value>¿ Returned format:> A “1” means “locked” A “0” means “unlocked”. :SYSTem :LANGuage 8 NATive | COMPatible Select GPIB Mode The user can select between two command sets, where native exploits the full capability of the instrument, and compatible facilitates portability to test systems using the Agilent counters 53131 and 53132.
  • Page 224: System :Set

    :SYSTem :PRESet Preset This command recalls the same default settings that are entered when you press USER OPT ® Save/Recall ® Recall Setup ® Default. These are not exactly the same settings as after * RST: :SYST:PRES gives 200 ms Measurement Time :SYST:PRES activates :INIT:CONT ON *RST gives 10 ms Measurement Time *RST activates :INIT:CONT OFF...
  • Page 225: System :Temperature

    :SYSTem :TALKonly CNT-91 8 ON Enter Talk Only Mode The main purpose is to transfer streaming data fast in monitoring systems without predefined limits for time or number of samples. It is a non-reversible command, i.e. you can only return to normal bus mode by sending IFC or pressing the CAN- CEL button on the front panel.
  • Page 226: System :Tout :Auto

    :SYSTem :TOUT 8 <Boolean> Timeout On/Off This command switches the timeout on or off. When timeout is enabled, the mea- surement attempt will be abandoned when the time set with :SYST:TOUT:TIME has elapsed. Depending on GPIB mode and output format, a special response message will be sent to the controller instead of a measurement result, and the timeout bit in the STATus QUEStionable register will be set.
  • Page 227: System :Unprotect

    :SYSTem :TOUT :TIME 8 «<Numeric value>|MIN|MAX» Timeout, Set This command sets the timeout in seconds with a resolution of 10 ms. The 10 ms timer ticks start to be counted after EITHER a measurement INIT (if Arming is not selected) OR an external arming event (if Arming is selected). The counting stops at the stop trigger of the measurement.
  • Page 228 This page is intentionally left blank. 8-120 Command Reference...
  • Page 229: Test Subsystem

    Test Subsystem :TEST 8 RAM | ROM | LOGic | DISPlay | ALL :SELect Related common command: *TST Command Reference 8-121...
  • Page 230: Test :Select

    :TEST :SELect 8 «RAM | ROM | LOGic | DISPlay | ALL» Select Self-tests Selects which internal self-tests shall be used when self-test is requested by the *TST command. Returned format: «RAM | ROM | LOGic | DISPlay | ALL»¿ *RST condition: 8-122 Command Reference...
  • Page 231: Trigger Subsystem

    Trigger Subsystem :TRIGger [ :STARt | :SEQuence [ 1 ] ] [ :LAYer [ 1 ] ] 8 <Numeric value> | MIN | MAX :COUNt :SOURCE :TIMER Related common command: *TRG Command Reference 8-123...
  • Page 232: Trigger :Count

    :TRIGger :COUNt 8 «<Numeric value> | MIN | MAX» No. of Triggerings on each Ext Arm start Sets how many measurements the instrument should make for each ARM:STARt condition, (block arming). These measurements are done without any additional arming conditions before the measurement.
  • Page 233: Trigger: Timer

    :TRIGger: TIMer 8<Numeric value> | MIN | MAX Set Pacing Time This command sets the sample rate, for instance in conjunction with the statistics functions. Parameters: <Numeric value> is a time length between 2 ms and 500 s, entered in seconds. MIN means 2 ms.
  • Page 234 This page is intentionally left blank. 8-126 Command Reference...
  • Page 235: Common Commands

    Common Commands *CLS 8 <Arbitrary block program data> *DDT 8 <Macro label> , <Program messages> *DMC 8 <Decimal data> *EMC 8 <Decimal data> *ESE *ESR? 8 <Macro label> *GMC? *IDN? *LMC? *LRN? *OPC *OPC? *OPT? *PMC 8 <Decimal data> *PSC 8 <Arbitrary block program data>...
  • Page 236: Cls

    *CLS Clear Status Command The *CLS common command clears the status data structures by clearing all event registers and the error queue. It does not clear enable registers and transition fil- ters. It clears any pending *WAI, *OPC, and *OPC?. Example: ®...
  • Page 237: Dmc

    *DMC 8 <Macro label> , <Program messages> Define Macro Allows you to assign a sequence of one or more program message units to a macro label. The sequence is executed when the macro label is received as a command or query. Twenty-five macros can be defined at the same time, and each macro can contain an average of 40 characters.
  • Page 238: Emc

    *EMC 8<Decimal data> Enable Macros This command enables and disables expansion and execution of macros. If mac- ros are disabled, the instrument will not recognize a macro although it is defined in the instrument. (The Enable Macro command takes a long time to execute.) Parameters: <Decimal data>...
  • Page 239: Ese

    *ESE 8<Decimal data> Standard Event Status Enable Sets the enable bits of the standard event enable register. This enable register contains a mask value for the bits to be enabled in the standard event status regis- ter. A bit that is set true in the enable register enables the corresponding bit in the status register.
  • Page 240: Esr

    *ESR? Event Status Register Reads out the contents of the standard event status register. Reading the Standard Event Status Register clears the register. Returned Format: <dec.data> = the sum (between 0 and 255) of all bits that are true. See table on page 8-131. Complies with standards: IEEE 488.2 1987.
  • Page 241: Idn

    *IDN? Identification query Reads out the manufacturer, model, serial number, and firmware level in an ASCii response data element. The query must be the last query in a program message. Response is <Manufacturer> , <Model> , <Serial Number>, <Firmware Level>. Example: SEND ®*IDN? READ¬...
  • Page 242: Lrn

    *LRN? Learn Device Setup Learn Device Setup Query. Causes a response message that can be sent to the in- strument to return it to the state it was in when the *LRN? query was made. Returned Format: :SYST:SET_<Block data>¿ Where: <Block data>...
  • Page 243: Opt

    |Rubidium <Prescaler option> = 0|Option 10|Option 13|Option 14|Option 14B <Microwave converter> = 27GHz|40GHz|46GHz|60GHz <Reserved> = 0 until further notice Notes: CNT-90/91(R) only CNT-90XL only CNT-90/91 only CNT-90/91 & CNT-90XL CNT-91R only Complies with standards: IEEE 488.2 1987. Command Reference 8-135...
  • Page 244: Pmc

    *PMC Purge Macros Removes all macro definitions. *PMC Example: See also: :MEMory:DELete:MACRo 8 ‘<Macro-name>’ if you want to remove a single macro. Complies with standards: IEEE 488.2 1987. *PSC 8 <Decimal data> Power-on Status Clear Enables/disables automatic power-on clearing. The status registers listed below are cleared when the power-on status clear flag is 1.
  • Page 245: Pud

    *PUD 8 Arbitrary block program data> Protected User Data Protected user data. This is a data area in which the user may write any data up to 64 characters. The data can always be read, but you can only write data after un- protecting the data area.
  • Page 246: Rmc

    *RMC 8 ‘<Macro name>’ Delete one Macro This command removes an individual MACRo. Parameters: ‘<Macro name>’ is the name of the macro you want to delete. <Macro name> is String data that must be surrounded by quotation marks. See also: *PMC, if you want to delete all macros.
  • Page 247: Sav

    *SAV _<Decimal data> Save Saves the current settings of the instrument in an internal nonvolatile memory. Nineteen memory locations are available. Switching the power off and on does not change the settings stored in the registers. Note that memory positions 1 to 10 can be protected from the front panel USER OPT menu.
  • Page 248: Sre

    *SRE 8 <Decimal data> Service Request Enable The Service Request Enable command sets the service request enable register bits. This enable register contains a mask value for the bits to be enabled in the status byte register. A bit that is set true in the enable register enables the corre- sponding bit in the status byte register to generate a Service Request.
  • Page 249: Stb

    *STB? Status Byte Query Reads out the value of the Status Byte. Bit 6 reports the Master Summary Status bit (MSS), not the Request Service (RQS). The MSS is set if the instrument has one or more reasons for requesting service. Returned Format: <Integer>...
  • Page 250: Tst

    *TST? Self Test The self-test query causes an internal self-test and generates a response indicat- ing whether or not the device completed the self-test without any detected errors. <Integer>¿ Returned Format: Where: <Integer> = a number indicating errors according to the table below. <Integer>...
  • Page 251: Index

    Chapter 9 Index...
  • Page 252 Index Levels selected by· · · · · · · · · · · · 8-50 Power on clearing · · · · · · · · · · · 8-136 1 Mohm · · · · · · · · · · · · · · · · · · · · · · 8-48 Speed ·...
  • Page 253 Calibration · · · · · · · · · · · · · 8-119, 8-137 *RCL · · · · · · · · · · · · · · · · · · · · · 8-137 Subsystem· · · · · · · · · · · · · · · · · · 8-25 *RMC ·...
  • Page 254 :CALCulate:LIMit:CLEar · · · · · · · 8-16 :DISPlay:ENABle· · · · · · · · · · · · · 8-32 :CALCulate:LIMit:CLEar:AUTO· · 8-16 :FETCh:ARRay? · · · · · · · · · · · · · 8-34 :CALCulate:LIMit:FAIL ·...
  • Page 255 :MEASure:FREQuency:POWer? 8-61 :MEMory:FREE:MACRo? · · · · · · 8-82 :MEASure:FREQuency:PRF · · · · 8-62 :MEMory:NSTates? · · · · · · · · · · · 8-83 :MEASure:FREQuency:RATio· · · 8-63 :OUTPut:POLarity · · · · · · · · · · · · 8-86 :MEASure:FREQuency:RATio?·...
  • Page 256: Device Status Register

    :SYSTem:PRESet · · · · · · · · · · · 8-116 :SYSTem:SET · · · · · · · · · · · · · · 8-116 :SYSTem:TALKonly · · · · · · · · · · 8-117 Data :SYSTem:TEMPerature? ·...
  • Page 257 DREG0 · · · · · · · · · · · · · · · · · · · · · 8-141 Execution Duration Control · · · · · · · · · · · · · · · · · · · · · · 3-4 See Pulse width Error ·...
  • Page 258 Get Macro · · · · · · · · · · · · · · · · · · · 8-132 Internal reference · · · · · · · · · · · · · 8-100 GPIB Address · · · · · · · · · · · · 1-4, 8-114 Interpolators Group Execute Trigger ·...
  • Page 259 Trigger · · · · · · · · · · · · · · · · · · · · 8-141 Measurement Function· · · · · · · · · · 8-53 Measurement Time· · · · · · · · · · · · · 8-92 Macro ·...
  • Page 260 Limits · · · · · · · · · · · · · · · · · · 6-3, 8-15 Overflow · · · · · · · · · · · · · · · · · · · · · 6-20 Monitor of low limit ·...
  • Page 261 Message terminator · · · · · · · · · · · 3-9 Messages · · · · · · · · · · · · · · · · · · · 3-7 Result QUE · · · · · · · · · · · · · · · · · · · · · · · 8-140 Fetch one ·...
  • Page 262: Standard Event Status

    Set Basic TIE Frequency · · · · · · · 8-101 Clear · · · · · · · · · · · · · · · · · · · · · 8-128 Settings Clear data structures· · · · · · · · · · 3-20 Reading ·...
  • Page 263 Summary Trigger Level Measurement commands · · · · · · · 6-8 Automatic · · · · · · · · · · · · · · · · · · 8-49 Of input amplifier settings · · · · · · · 6-6 Fixed ·...
  • Page 264 Wait-to-continue · · · · · · · · · · · · · · 8-142 WFA-bit · · · · · · · · · · · · · · · · · · · · · · 6-19 WFT-bit ·...

This manual is also suitable for:

Cnt-90xlCnt-91rCnt-91

Table of Contents