Download Print this page

Ladybug True RMS Programming Manual

Generation ii sensors for use with lb5900 series power sensors

Advertisement

Quick Links

LB5900 Series USB PowerSensor+™
Programming Guide
Programming Guide For
LadyBug True RMS Generation II Sensors
FOR USE WITH LB5900 SERIES POWER SENSORS
Revision: NAV2Rev1
1
06/29/2015

Advertisement

loading
Need help?

Need help?

Do you have a question about the True RMS and is the answer not in the manual?

Questions and answers

Summary of Contents for Ladybug True RMS

  • Page 1 LB5900 Series USB PowerSensor+™ Programming Guide Programming Guide For LadyBug True RMS Generation II Sensors FOR USE WITH LB5900 SERIES POWER SENSORS Revision: NAV2Rev1 06/29/2015...
  • Page 2: Notices

    LB5900 Series USB PowerSensor+™ Programming Guide NOTICES © LadyBug Technologies LLC 2007-2015 This document contains information which is copyright protected. Do not duplicate without permission or as allowed by copyright laws. SAFETY A WARNING indicates a potential hazard that could completely damage the product. Do not continue until you fully understand the meaning.
  • Page 3: Table Of Contents

    Programming Guide TABLE OF CONTENTS NOTICES ..................................2 TABLE OF CONTENTS ..............................3 INTRODUCTION ................................6 LadyBug Generation Notice ............................6 Sensor Instruction Language ............................ 6 Sensor Hardware Interface ............................6 Zeroing and Calibration ............................. 6 Sensing Range ................................6 GET STARTED MEASUREMENTS ..........................
  • Page 4 LB5900 Series USB PowerSensor+™ Programming Guide CONFigure (Command) ..........................21 CONFigure:SCALar:POWer:AC (Command) ....................22 READ? ..................................23 READ[1]? ................................. 23 READ:POWer:AC? ............................23 FETCh? ................................... 24 FETCh? ................................24 FETCh:SCALar:POWer:AC? ........................... 24 MEASure? ................................26 MEASure? ................................ 26 MEASure:SCALar:POWer:AC? ........................26 CALIBRATION SUBSYSTEM COMMANDS ......................
  • Page 5 LB5900 Series USB PowerSensor+™ Programming Guide UNIT SUBSYSTEM ..............................67 MEMORY SUBSYSTEM COMMANDS ........................68 MEMory:CATalog Queries ............................68 MEMory:CATalog:STATe?..........................69 MEMory:FREE Queries ............................70 MEMory:FREE ..............................71 MEMory:FREE:STATe ............................. 72 MEMory:FREE:TABLe ............................. 73 MEMory:NSTates Query ............................74 MEMory:STATe Commands ........................... 75 MEMory:STATe:CATalog Query ........................
  • Page 6: Introduction

    LadyBug Generation II sensors including LB5900 series sensors utilize standard SCPI (Standard Commands for Programmable Instruments) instructions. The SCPI Standard is built on the foundation of IEEE-488.2, Standard Codes and Formats. LadyBug Generation II sensors conform to IEEE-488.2. SCPI syntax is ASCII text, and therefore can be attached to any computer test language, such as BASIC, C, or C++.
  • Page 7: Get Started Measurements

    LB5900 Series USB PowerSensor+™ Programming Guide Get Started Measurements Using MEASure? NOTE: We recommend that the user install the software power meter application provided and verify normal operation prior to testing and developing programmatic control. NOTE: Users should have a basic understanding of SCPI instructions prior to continuing A quick way to get started making power measurements with LB5900 series sensors is by using the MEASure? command.
  • Page 8: Measure Using Read

    LB5900 Series USB PowerSensor+™ Programming Guide Measure Using READ? This example sets up a measurement frequency then uses CONFigure, to set other parameters. CONFigure sets up the measurement, however the measurement is not started by CONFigure. READ? starts the measurement using the parameters set by CONFigure.
  • Page 9: Scpi Language Basics

    Low Level Commands. LadyBug Generation II sensors utilize a variety of Low Level commands as foundations for the SENSe, CALCulate and TRIGger systems to control measurements. Using Low Level Commands to directly setup the sensor assures that measurements will be made exactly as desired.
  • Page 10: Whitespace

    LB5900 Series USB PowerSensor+™ Programming Guide Bars (|) can be read as “or” and are used to separate alternative parameter options. Source List is used to specify the measurement channel. There is one therefore (@1) is used Whitespace Whitespace (tab or space) must be placed between command keywords and parameters. Scalar (Terminology) The term SCALar is used to specify a single dimensional argument.
  • Page 11: Scpi Data Types

    LB5900 Series USB PowerSensor+™ Programming Guide SCPI Data Types SCPI language defines different data formats for use in messages and responses. LB5900 power sensors are flexible listeners and can accept commands and parameters in various formats. LB5900 power sensors are precise talkers.
  • Page 12: String

    LB5900 Series USB PowerSensor+™ Programming Guide String Throughout this document, <string> is used to represent 7-bit ASCII characters. Revision: NAV2Rev1 06/29/2015...
  • Page 13: Ieee 488.2 Commands

    LB5900 Series USB PowerSensor+™ Programming Guide IEEE 488.2 Commands The LB5900 series sensors are SCPI compliant. This section contains information on the IEEE-488 Common Commands and USBTMC/USB488 Universal Command statements supported by the sensor. Along with programming language codes, they provide all management and data communication instructions for the sensor. The IEEE-488.2 Common Command descriptions are listed below.
  • Page 14: Idn

    LB5900 Series USB PowerSensor+™ Programming Guide *IDN? The *IDN? query allows the power sensor to identify itself. The string returned is: LadyBug Technologies LLC,LB59XXX,<serial number>,<firmware_version> where: • <serial number> uniquely identifies each LB5900 Series power sensor. • <firmware_version>represents the firmware version and revision.
  • Page 15: Rcl

    LB5900 Series USB PowerSensor+™ Programming Guide *RCL<NRf> The *RCL <NRf> (ReCaLl) command restores the state of the LB5900 series sensor from the specified save or recall register. A sensor setup must have been stored previously in the specified register. <NRf> must be between 1 and 10 or error 224 will be returned.
  • Page 16: Rst

    LB5900 Series USB PowerSensor+™ Programming Guide *RST The *RST (ReSeT) command places the sensor in a known state. Refer to “SYSTem:PRESet <character_data>” for information on reset values. Revision: NAV2Rev1 06/29/2015...
  • Page 17: Sav

    LB5900 Series USB PowerSensor+™ Programming Guide *SAV<NRf> The *SAV <NRf> (SAVe) command stores the current state of the sensor in the specified register. <NRf> must be between 1 and 10. Revision: NAV2Rev1 06/29/2015...
  • Page 18: Trg

    LB5900 Series USB PowerSensor+™ Programming Guide *TRG The *TRG (TRiGger) command triggers the LB5900 Series power sensor if it is the wait for trigger state. EXAMPLE *TRG Triggers the sensor if it is waiting for a trigger Error Messages If TRIGger[1]:SOURce is not set to BUS, error –211,"Trigger ignored" occurs. If the sensor is not in the wait-for-trigger state, error –211,"Trigger ignored"...
  • Page 19: Tst

    LB5900 Series USB PowerSensor+™ Programming Guide *TST? The *TST? (TeST) query causes the power sensor to perform a self-test. The test takes approximately 40 0 is returned if the test passes 1 is returned if the test fails Revision: NAV2Rev1 06/29/2015...
  • Page 20: Measurement Commands

    LB5900 Series USB PowerSensor+™ Programming Guide Measurement Commands High Level Measurement commands are used to acquire data. These four commands enable the user to configure and initiate measurements in a variety of ways. Note that LB5900 sensors themselves do not have windows and therefore do not utilize SCPI quarries relating to the four commands listed below return 1 for the window suffix.
  • Page 21: Configure

    LB5900 Series USB PowerSensor+™ Programming Guide CONFigure CONFigure? (Query) The CONFigure? Query returns the current configuration of the measurement as a quoted string in the following format: “<function> <expected_value>,<resolution>,<source list>” <expected_value> returns the expected value sent by the last CONFigure command or +20 dBm by default.
  • Page 22: Configure:scalar:power:ac (Command)

    LB5900 Series USB PowerSensor+™ Programming Guide CONFigure:SCALar:POWer:AC (Command) CONFigure[1][:SCALar][:POWer:AC][<expected_value>[,<resolution>[,<source list>]]] The command is used to set: The expected measurement power level. The measurement resolution. Syntax: CONF[1][:SCALar][:POWer:AC][<expected_value[,<resolution>[,<source_list>]]] Parameters Item Description & Default Values A numeric value for the expected power level. The units of Sensor dependent expected_value measurement are dBm and W.
  • Page 23: Read

    LB5900 Series USB PowerSensor+™ Programming Guide READ? READ[1]? Query is most commonly used with the CONFigure command to cause a new power measurement to be taken and the result returned to the output buffer. The result format is set by FORMat[:READing][:DATA]. The READ? query is equivalent to: INITiate FETCh?
  • Page 24: Fetch

    LB5900 Series USB PowerSensor+™ Programming Guide FETCh? FETCh? The FETCh? query calculates the measurement and returns the result. The result format is set by FORMat[:READing][:DATA]. Refer to FORMat Subsystem, for further information. The query returns a measurement result when it is valid. Under the following conditions, the measurement result is invalid: - When *RST is executed.
  • Page 25 LB5900 Series USB PowerSensor+™ Programming Guide Queries the measurement using the current sensor range and a resolution setting of 3. Associated Error Messages If the last measurement is not valid, error –230, "Data corrupt or stale" occurs. A measurement is valid after it has been initiated.
  • Page 26: Measure

    LB5900 Series USB PowerSensor+™ Programming Guide MEASure? MEASure? The MEASure[1]? query configures the LB5900 Series power sensor to perform a power measurement with the current measurement function, range and resolution then makes the measurement. The format of the result is set by FORMat[:READing][:DATA]. Refer to FORMat Subsystem,for further information. The MEASure? compound command is equivalent to: CONFigure READ?
  • Page 27: Calibration Subsystem Commands

    Programming Guide CALibration Subsystem Commands LadyBug’s patented No-Zero No-Cal system eliminates the need to zero or calibrate its sensors. High accuracy is assured for measurements from the sensors noise floor to its highest level power measurement. In order to provide support for replacement of competitive sensors that require calibration, LadyBug Generation II sensors support SCPI CAL instructions.
  • Page 28: Sense Subsystem Commands

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe Subsystem Commands The SENSe command subsystem directly affects settings used to make measurements. The high level command CONFigure uses the SENSe commands to prepare the LB5900 Series power sensor for making measurements making SENSe commands optional. At a lower level SENSe enables the user to change the following parameters: RANGe, FREQuency, LOSS, GAIN2 (channel offset), DCYCle (duty cycle), and AVERage without completely re-configuring the sensor.
  • Page 29 LB5900 Series USB PowerSensor+™ Programming Guide Error Messages If an averaging filter value is entered using [SENSe[1]:]AVERage:COUNt while [SENSe[1]:]MRATe is set to FAST, error –221, "Settings Conflict" occurs. However, the filter value is set but the [SENSe[1]:]AVERage:STATe command is not automatically set ON. Revision: NAV2Rev1 06/29/2015...
  • Page 30: Sense:average:count:auto

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:AVERage:COUNt:AUTO [SENSe[1]:]AVERage:COUNt:AUTO <boolean> enables and disables automatic averaging. When the auto-filter mode is enabled, the LB5900 Series power sensor automatically sets the number of readings averaged together to satisfy the averaging requirements for most power measurements. The number of readings averaged together depends on the resolution and the power level in which the sensor is currently operating.
  • Page 31 LB5900 Series USB PowerSensor+™ Programming Guide If SENSe[1]:AVERage:COUNt:AUTO is set to ON while SENSe[1]:MRATe is set to FAST or [SENSe[1]:]SPEed is set to 110, error –221, "Settings Conflict" occurs. However, automatic averaging is enabled but the SENSe[1]:AVERage:STATe command is not automatically set ON. Revision: NAV2Rev1 06/29/2015...
  • Page 32: Sense:average:state

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:AVERage:STATe [SENSe[1]:]AVERage[:STATe] <boolean> is used to enable and disable averaging. Reset Condition Enabled upon reset. Query [SENSe[1]:]AVERage[:STATe]? returns a 1 or 0 indicating averaging is enabled or disabled. 1 is returned when averaging is enabled 0 is returned when averaging is disabled Revision: NAV2Rev1 06/29/2015...
  • Page 33: Sense:frequency:cw:fixed

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:FREQuency:CW:FIXed [SENSe[1]:]FREQuency[:CW|:FIXed] <numeric_value> is used to enter a frequency. The frequency- dependent offset corrections are applied for the selected frequency. Parameters Item Description & Default Values A numeric value that specified the frequency, default units Hz.. Minimum 1 kHz MAX 1,000 GHz, DEF: 50MHz.
  • Page 34: Sense:mrate

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:MRATe [SENSe[1]:]MRATe <character_data> sets the measurement rate on the power sensor. When the measurement rate is set to FAST, the following couplings occur: Command Status OFF - Occurs on the measurement specified in the [SENSe[1]:]MRATe command.
  • Page 35: Sense:power:ac:range

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:POWer:AC:RANGe Note: Please refer to the note regarding sensing range in the introduction section of this document. [SENSe[1]:]POWer:AC:RANGe <numeric_value> selects one of two power ranges. If 0 is selected, the power sensor lower range is selected If 1 is selected, the power sensor upper range is selected Setting a range with this command automatically switches [SENSe[1]:]POWer:AC:RANGe:AUTO to OFF.
  • Page 36: Sense:power:ac:range:auto

    LB5900 Series USB PowerSensor+™ Programming Guide SENSe:POWer:AC:RANGe:AUTO Note: Please refer to the note regarding sensing range in the introduction section of this document. [SENSe[1]:]POWer:AC:RANGe:AUTO <boolean> In competitive sensors, this command enables and disables auto-ranging. When auto-ranging is ON, the LB5900 Series power sensor makes a full dynamic range measurement.
  • Page 37: Service Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide SERVice Subsystem The SERVice command subsystem is used to load information such as LB5900 Series power sensor board versions, hardware status and obtain information such as the serial number of the current sensor(s) being used. Revision: NAV2Rev1 06/29/2015...
  • Page 38: Service:sensor:radc

    LB5900 Series USB PowerSensor+™ Programming Guide SERVice:SENSor:RADC? SERVice:SENSor[1]:RADC? returns a new raw uncorrected measurement in volts, as a 32- bit signed integer. The returned raw measurement unit is float. Example SERV:SENS:RADC? This query returns a raw uncorrected measurement for the sensor. Revision: NAV2Rev1 06/29/2015...
  • Page 39: Service:sensor:snumber

    LB5900 Series USB PowerSensor+™ Programming Guide SERVice:SENSor:SNUMber? SERVice:SENSor[1]:SNUMber? is used to acquire the serial number of the power sensor in the form of MY12345678. Example SERV:SENS:SNUM? This query returns the serial number of the LB5900 Series power sensor in the form of MY12345678. Revision: NAV2Rev1 06/29/2015...
  • Page 40: Service:version:system

    LB5900 Series USB PowerSensor+™ Programming Guide SERVice:VERSion:SYSTem? SERVice:VERSion:SYSTem?<firmware_version> this query returns the sensor’s the firmware version. Return Format: <Major.Minor.Build YMD_HM cevCode> Example SERV:SNUM? Possible return 0.92.010i 20150624_1354 S Revision: NAV2Rev1 06/29/2015...
  • Page 41: Service:version:system:dfu

    LB5900 Series USB PowerSensor+™ Programming Guide SERVice:VERSion:SYSTem:DFU SERVice:VERSion:SYSTem:DFU causes the sensor to enter the firmware update mode. Example SERV:VERS:SYST:DFU The user must have LadyBug firmware update software. Revision: NAV2Rev1 06/29/2015...
  • Page 42: System Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide SYSTem Subsystem The SYStem command subsystem is used to: • Retrieve error numbers and messages from the LB5900 Series power sensor • Preset the sensor • Query the SCPI version SYSTem:ERRor? SYSTem:ERRor? returns error numbers and messages from the power sensor error queue. When an error is generated by the sensor, it stores an error number and corresponding message in the error queue.
  • Page 43: Error Message List

    LB5900 Series USB PowerSensor+™ Programming Guide Error Message List Invalid character An invalid character was found in the command string. You may have inserted a character such as #, $, or –101 % in the command header or within a parameter. For example, LIM:LOW O#.
  • Page 44 LB5900 Series USB PowerSensor+™ Programming Guide Suffix too long –134 A unit used contained more than 12 characters. For example, SENS:FREQ 2MHXYZXYZXYZXYZZYXZYX. Suffix not allowed –138 A unit was received following a numeric parameter which does not accept a unit. For example, INIT:CONT 0Hz.
  • Page 45 Out of memory the power sensor required more memory than was available to run an internal operation. Self-test Failed; –330 The –330,“Self-test Failed” errors indicate that you have a problem with the power sensor. Contact LadyBug Technologies for repair. –330 Self-test Failed;Measurement Channel Fault...
  • Page 46: System:help:headers

    LB5900 Series USB PowerSensor+™ Programming Guide SYSTem:HELP:HEADers? SYSTem:HELP:HEADers? This query returns a list of all SCPI commands supported by the sensor. Data is returned in IEEE 488.2 arbitrary block program data format as shown in the figure below. #xyyy..yddd....ddd<LF> # is the start of the block x is the number of digits y is the number of data bytes (d) in the block d is the data...
  • Page 47: Preset Values

    LB5900 Series USB PowerSensor+™ Programming Guide Preset Values Command Setting Comments “POW:AVER” CALC[1]:FEED[1] Select average measurement type CALC[1]:LIM:CLE:AUTO Clear limit data at INIT –90 dBm CALC[1]:LIM:LOW[:DATA] Lower limit CALC[1]:LIM:STAT Limits checking disabled CALC[1]:LIM:UPP[:DATA] +90 dBm Upper limit “(SENS1)” CALC[1]:MATH[:EXPR] Math expression FORM[:READ]:BORD normal Binary order...
  • Page 48 LB5900 Series USB PowerSensor+™ Programming Guide TRIG[:SEQ]:HYST 0 dB Fall/rise below/above TRIG:LEV TRIG[:SEQ]:LEV 0 dBm Power level TRIG[:SEQ]:SLOP Trigger event recognized on rising edge TRIG[:SEQ[1]]:COUN Trigger events for measurement cycle TRIG[:SEQ[1]]:DEL:AUTO Enable settling time delay TRIG[:SEQ[1]]:SOUR Trigger source set up UNIT:POW Power units Revision: NAV2Rev1...
  • Page 49: System:version

    LB5900 Series USB PowerSensor+™ Programming Guide SYSTem:VERSion SYSTem:VERSion? returns the version of SCPI used in the LB5900 Series power sensor. The response is in the form of XXXX.Y, where XXXX is the year and Y is the version number. Example SYST:VERS? Queries which version of SCPI is used in the sensor.
  • Page 50: System:time

    LB5900 Series USB PowerSensor+™ Programming Guide SYSTem:TIME SYSTem:TIME<time> Sets the real time clock. The sensor contains a real time clock with backup that maintains the clock for several hours. Note: If read when uninitialized, date is initialized to 2000,1,1 and time to 0,0,0 and error message -310, "System error;RTC Power Lost”...
  • Page 51: System:date

    LB5900 Series USB PowerSensor+™ Programming Guide SYSTem:DATE SYSTem:DATE<date> Sets the real time clock. The sensor contains a real time clock with backup that maintains the clock for several hours. Note: If read when uninitialized, date is initialized to 2000,1,1 and time to 0,0,0 and error message -310, "System error;RTC Power Lost”...
  • Page 52: Trigger Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger Subsystem The TRIGger subsystem is used to synchronize device actions with events. It includes the ABORt, INITiate, and TRIGger commands. These are all at the root level in the command hierarchy but they are detailed here because of their close functional relationship.
  • Page 53: Initiate:continous

    LB5900 Series USB PowerSensor+™ Programming Guide INITiate:CONTinous INITiate[1]:CONTinuous <boolean> sets the power sensor for either a single trigger cycle or continuous trigger cycles. A trigger cycle means that the power sensor exits the wait for trigger state and starts a measurement.
  • Page 54: Initiate:immediate

    LB5900 Series USB PowerSensor+™ Programming Guide INITiate:IMMEdiate INITiate[1][:IMMediate] sets the sensor in the wait for trigger state. When a trigger is received, the measurement is taken and the result placed in the power sensor’s memory. If TRIGger[1]:SOURce is set to IMMediate the measurement begins as soon as INITiate[1][:IMMediate] is executed.
  • Page 55: Initiate:continous:sequence

    LB5900 Series USB PowerSensor+™ Programming Guide INITiate:CONTinous:SEQuence INITiate[1]:CONTinuous:SEQuence[1] <boolean> sets the LB5900 Series power sensor for either a single trigger cycle or continuous trigger cycles. A trigger cycle means that the sensor exits the wait for trigger state and starts a measurement. If INITiate[1]:CONTinuous:SEQuence[1] <boolean>...
  • Page 56: Initiate:immediate:all

    LB5900 Series USB PowerSensor+™ Programming Guide INITiate:IMMediate:ALL INITiate[1][:IMMediate]:ALL This command initiates all trigger sequences. Example INIT:ALL This command initiates all trigger sequences. Error Messages If the sensor is not in the idle state or INITiate[1]:CONTinuous is ON, error –213,"INIT ignored" occurs. Revision: NAV2Rev1 06/29/2015...
  • Page 57: Initiate:immediate:sequence

    LB5900 Series USB PowerSensor+™ Programming Guide INITiate:IMMediate:SEQuence INITiate[1][:IMMediate]:SEQuence[1] This command sets the power sensor in the wait for trigger state. When a trigger is received, the measurement is taken and the result placed in the sensor’s memory. If TRIGger[1]:SOURce is set to IMMediate the measurement begins as soon as INITiate[1][:IMMediate] is executed.
  • Page 58: Trigger:delay:auto

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:DELay:AUTO TRIGger[1]:DELay:AUTO <boolean> is used to determine whether or not there is a settling-time delay before a measurement is made. When TRIGger[1]:DELay:AUTO <boolean> is set: ON, the LB5900 Series power sensor inserts a settling-time delay before taking the requested measurement.
  • Page 59: Trigger:immediate

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:IMMediate TRIGger[1][:IMMediate] causes a trigger to occur immediately, provided the sensor is in the wait for trigger state. When this command is executed, the measurement result is stored in the sensor memory. Use FETCh? to return the measurement. NOTE: This command performs the same function as INITiate[1]:[IMMediate].
  • Page 60: Trigger:source

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SOURce TRIGger[1]:SOURce BUS|INTernal[1]|EXTernal|HOLD|IMMediate (included for compatibility) configures the trigger system to respond to the specified source. This command selects the trigger source. Use the INITiate[1][:IMMediate] command to place the sensor in the wait for trigger state. NOTE: The preferred command is: TRIGger[:SEQuence[1]]:SOURce BUS|INTernal[1]|EXTernal|HOLD|IMMediate Parameters...
  • Page 61: Trigger:sequence:delay

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:DELay TRIGger[:SEQuence]:DELay <numeric_value> sets the delay between the recognition of a trigger event and the start of a measurement. Parameters Item Description & Default Range of Values The delay between the recognition of a trigger –0.150 to 0.15 sec event and the start of the measurement: •...
  • Page 62: Trigger:sequence:holdoff

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:HOLDoff TRIGger[:SEQuence]:HOLDoff <numeric_value> sets the trigger hold-off in seconds. Parameters Item Description & Default Range of Values The trigger hold-off in seconds. 1 μs to 400 ms • DEF: the default value is 1 μs •...
  • Page 63: Trigger:sequence:slope

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:SLOPe TRIGger[:SEQuence]:SLOPe <character_data> specifies whether a trigger event is recognized on the rising or falling edge of a signal. Parameters Item Description & Default Range of Values How a trigger event is recognized: • POSitive: a trigger event is recognized on the POSitive character_value rising edge of a signal...
  • Page 64: Trigger:sequence:count

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:COUNt TRIGger[:SEQuence[1]]:COUNt <numeric_value> controls the path of the trigger subsystem in the upward traverse of the wait for trigger state. COUNt loops through the event detection/measurement cycle are performed. That is, COUNt measurements are performed in response to COUNt trigger events. COUNt can be set to a value >1 only when: •...
  • Page 65: Trigger:sequence:immediate

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:IMMediate TRIGger[:SEQuence[1]]:IMMediate provides a one-time override of the normal process of the downward path through the wait for trigger state. It causes the immediate exit of the event detection layer if the trigger system is in this layer when the command is received. In other words, the sensor stops waiting for a trigger and takes a measurement ignoring any delay set by TRIG:DELay.
  • Page 66: Trigger:sequence:source

    LB5900 Series USB PowerSensor+™ Programming Guide TRIGger:SEQuence:SOURce TRIGger[:SEQuence[1]]:SOURce BUS|INTernal[1]|EXTernal|HOLD|IMMediate configures the trigger system to respond to the specified source. This command selects the trigger source. Use the INITiate[1][:IMMediate] command to place the sensor in the wait for trigger state. Parameters Item Description &...
  • Page 67: Unit Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide UNIT Subsystem The UNIT command subsystem sets power measurement units to dBm or Watts. The following command is described in this section: The UNIT[1]:POWer UNIT[1]:POWer <amplitude_unit> This command sets the power measurement units. The power measurement unit set by UNIT[1]:POWer is used for any command which accepts a numeric value in more than one unit.
  • Page 68: Memory Subsystem Commands

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory Subsystem Commands Note: Please refer to the note regarding Option MILin the introduction section of this document. The MEMory subsystem is used to read and edit various sensor functions including: Edit and review sensor save/recall registers. Edit and review sensor frequency-dependent offset tables.
  • Page 69: Memory:catalog:state

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:CATalog:STATe? MEMory:CATalog:STATe? is used to list the save/recall registers. The power sensor returns the data in the form of two numeric parameters and as many strings as there are save/recall registers. <numeric_value>,<numeric_value>{,<string>} The first numeric parameter indicates the amount of memory, in bytes, used for the storage of registers. The second parameter indicates the memory, in bytes, available for the storage of registers.
  • Page 70: Memory:free Queries

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:FREE Queries These queries are used to return information about the amount of free memory space available for frequency-dependent offset tables and save/recall registers. The following queries are described in this section: MEMory:FREE[:ALL]? MEMory:FREE:STATe? MEMory:FREE:TABLe? Revision: NAV2Rev1 06/29/2015...
  • Page 71: Memory:free

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:FREE MEMory:FREE[:ALL]? returns the amount of memory free for frequency-dependent offset tables, and save/recall registers. The format of the response is: <bytes_available>,<bytes_in_use> Revision: NAV2Rev1 06/29/2015...
  • Page 72: Memory:free:state

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:FREE:STATe MEMory:FREE:STATe? returns the amount of memory free for save/recall registers. The format of the response is: <bytes_available>,<bytes_in_use> Revision: NAV2Rev1 06/29/2015...
  • Page 73: Memory:free:table

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:FREE:TABLe MEMory:FREE:TABLe? returns the amount of memory free for frequency-dependent offset tables. The format of the response is: <bytes_available>,<bytes_in_use> Revision: NAV2Rev1 06/29/2015...
  • Page 74: Memory:nstates Query

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:NSTates Query MEMory:NSTates? returns the number of registers that are available for save/recall. Revision: NAV2Rev1 06/29/2015...
  • Page 75: Memory:state Commands

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:STATe Commands MEMory:STATe Commands are used to query and define register names. The following command and query are described in this section: MEMory:STATe:CATalog? MEMory:STATe:DEFine Revision: NAV2Rev1 06/29/2015...
  • Page 76: Memory:state:catalog Query

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:STATe:CATalog Query MEMory:STATe:CATalog? returns a list of the save/recall register names in ascending order of register number. The format of the response is: <string>,<string>,..,<string> Revision: NAV2Rev1 06/29/2015...
  • Page 77: Memory:state:define

    LB5900 Series USB PowerSensor+™ Programming Guide MEMory:STATe:DEFine MEMory:STATe:DEFine <“character_data”>,<numeric_value> is used to associate a name with a save/recall register number. Parameters Item Description & Default Values A to Z (uppercase) Details the register name. A maximum of 12 a to z (lowercase) character_data characters can be used.
  • Page 78: Calculate Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide CALCulate Subsystem The CALCulate subsystem performs post acquisition data processing. Functions in the SENSe subsystem are related to data acquisition, while the CALCulate subsystem operates on the data acquired by a SENSe function. The LB5900 Series power sensors contains an independent CALCulate Subsystem. CALCulate:FEED CALCulate[1]:FEED[1]<“string”>...
  • Page 79: Calculate:math Commands

    LB5900 Series USB PowerSensor+™ Programming Guide CALCulate:MATH Commands These commands define and carry out the following mathematical transformations on SENSe data for a single measurement. The following command and query are detailed in this section: CALCulate[1]:MATH[:EXPRession] <"string"> CALCulate[1]:MATH[:EXPRession]:CATalog? Revision: NAV2Rev1 06/29/2015...
  • Page 80: Calculate:math

    LB5900 Series USB PowerSensor+™ Programming Guide CALCulate:MATH CALCulate[1]:MATH[:EXPRession] <“string”> sets to a single measurement. Parameters Item Description & Default Range of Values “(SENS1)” Note: Quotes are A single string value detailing the measurement String type. The default is SENS1. mandatory. Example CALC:MATH "(SENS1)"...
  • Page 81: Calculate:math:catalog

    LB5900 Series USB PowerSensor+™ Programming Guide CALCulate:MATH:CATalog? CALCulate[1]:MATH[:EXPRession]:CATalog? Returns all of the defined expressions. The response is a list of comma separated strings. Each string contains an expression. For single measurement, the string is: "(SENS1)" Example CALC:MATH:CAT? This query lists all the defined math expressions. Revision: NAV2Rev1 06/29/2015...
  • Page 82: Output Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide OUTPut Subsystem The output subsystem controls the following two functions. The OUTPut subsystem is used to control the analog / digital output used for optional Recorder Out and optional Trigger out. OUTPut:RECorder:FEED (Recorder Out) OUTPut:RECorder[1]:FEED <data_handle>...
  • Page 83: Output:recorder:limit:lower (Recorder Out)

    LB5900 Series USB PowerSensor+™ Programming Guide OUTPut:RECorder:LIMit:LOWer (Recorder Out) OUTPut:RECorder[1]:LIMit:LOWer <numeric_value> sets the minimum scaling value for the recorder output. The units used are dependent on the units currently set for the CALC block specified in OUTPut:RECorder[1]:FEED <data_handle>. Parameters Item Description &...
  • Page 84: Output:recorder:limit:upper (Recorder Out)

    LB5900 Series USB PowerSensor+™ Programming Guide OUTPut:RECorder:LIMit:UPPer (Recorder Out) OUTPut:RECorder[1]:LIMit:UPPer <numeric_value> sets the maximum scaling value for the recorder output. The units used are dependent on the units currently set for the CALC block specified in OUTPut:RECorder[1]:FEED <data_handle>. Parameters Item Description &...
  • Page 85: Output:recorder:state (Recorder Out)

    LB5900 Series USB PowerSensor+™ Programming Guide OUTPut:RECorder:STATe (Recorder Out) OUTPut:RECorder[1]:STATe <boolean> sets the enabled sate for the recorder output. APP NOTE: OUTPut:TRIGger[:STATe], SERVice:BIST:VIDeo:STATe, and SERVice:BIST:TBASE:STATe commands override OUTPut:RECorder:STATe command. For example, if OUTPut:RECorder:STATe is ON and the command OUTPut:TRIGger[:STATe] ON is sent, this command overrides the recorder output state and sets it to OFF.
  • Page 86: Output:triggger:state (Trigger Out)

    LB5900 Series USB PowerSensor+™ Programming Guide OUTPut:TRIGgger:STATe (Trigger Out) OUTPut:TRIGger[:STATe] <boolean> sets the enabled sate for trigger output. APP NOTE: The OUTPut:RECorder:STATe, SERVice:BIST:VIDeo:STATe, and SERVice:BIST:TBASE:STATe commands override the OUTPut:TRIGger[:STATe] command. For example, if OUTPut:TRIGger[:STATe] is ON and the command OUTPut:RECorder:STATe ON is sent, this command overrides the trigger state and sets it to OFF.
  • Page 87: Unattended Operation Subsystem

    LB5900 Series USB PowerSensor+™ Programming Guide Unattended Operation Subsystem Unattended Operation (Operation UOP) allows the sensor make and store measurements autonomously. There are three modes of operation, Off, Basic and Reset. When UOP mode is set to off, the sensor functions as if the option were not installed.
  • Page 88: Uoperation Active

    LB5900 Series USB PowerSensor+™ Programming Guide UOPeration:ACTive UOPeration:ACTive<string> sets the state of UOPeration. There are 3 possible states: OFF, BAS, and RESET. Note: Queries or other communication activity made while UOPeration is active may interfere with storage timing. UOPeration:ACTive OFF This command turns off unattended operation.
  • Page 89 LB5900 Series USB PowerSensor+™ Programming Guide OFF – Unattend operation is off A string value representing the BASTIME – Operating in time triggered mode expected_value mode of unattended operation. FLUSHING – In the process of resetting Default condition is OFF Query Examples UOPeration:ACTive? This command returns “BASTIME”...
  • Page 90: Uoperation:bas:roen (Recorder Out)

    LB5900 Series USB PowerSensor+™ Programming Guide UOPeration:BAS:ROEN (Recorder Out) UOPeration:BAS:ROEN<bool> Enables and disables recorder output in basic unattended operation mode. A write sets the state of recorder out in basic unattended operation. When queried, the instruction returns the state of the recorder out during basic unattended operation. When active in unattended mode, recorder out settings supersede certain measurement settings.
  • Page 91: Uoperation:bas:rbac? (Query)

    LB5900 Series USB PowerSensor+™ Programming Guide UOPeration:BAS:RBAC? (Query) UOPeration:BAS:RBAC? [<number_start, number_count>] is the command used to return collected measurements. The command returns a string that is formatted for pasting into a spreadsheet. When no parameters are included, the query returns is a list of records; when record numbers are specified the specific records will be listed.
  • Page 92 LB5900 Series USB PowerSensor+™ Programming Guide Example #2 Check status In this example, there is some data available. This query (no parameters specified) lists the available data. Request: UOP:RBAC? Return: INDEX,DATE,TIME,POWER,FLAGS 1,6/22/2015,10:7:26.445,-inf,* 135,6/22/2015,10:7:44.165,-inf,* 61423750,measurements available Example #3 Return selected data In this example, using the known available date from example 2, some data to be returned is specified.