Measurement Operations & Settings Triggering - The TRIGger Subsystem
172 Agilent 8163A/B, 8164A/B & 8166A/B Mainframes, Fifth Edition
Table 9 Generating Output Triggers from Power Measure ments
Hardware
Triggering
Trigger Rearming Software Triggering Data Acquisition Functions
sens:func:stat
trig:outp trig:outp:rearm init:imm init:con t MINMax LOGGing|STABility
DISabled - An output trigger will never be generated.
AVGover ON An output trigger is generated for ever y new power measurement when th e aver-
aging time period finishes.
Applies for all subsequen t
data acquisition functions.
MEASure ON An output trigger is generated for every new power mea surement when the aver-
aging time period begins.
Applies for all subsequen t
data
acquisition functions.
AVGover OFF An output trigger is generated when the averaging
time period of the first power measureme nt finish-
es. A further hardware output trigger cannot be
generated until you send trig:outp:rearm.
An output trigger is generat-
ed for every new power mea-
surement when the
averaging time period finish-
es. Applies for all subsequent
data acquisition functions.
MEASure OFF An output trigger is generated when the averaging
time peri od of th e first p ower m easurem ent be gins.
A further hardware output trigger cannot be gener-
ated until you send trig:outp:rearm.
An output trigger is generat-
ed for every new power mea-
surement when the
averaging time period begins.
Applies for all subsequen t
data acquisition functions.
command: :TRIGger
syntax: :TRIGger<wsp>NODEA|1|NODEB|2
description: Generates a hardware trigger.
parameters: 1 or NODEA:
2 or NODEB:
Is identical to a trigger at the Inp ut Trigger Connector.
Generates trigger at the Output Trigger Connector.
NOTE A hardware trigger cannot be effective in the DISabled triggering mode but can be
effective in DEFault, PASSthrough or LOOPback triggering modes, see “:TRIGger:CONFiguration” on page 177 for information on triggering modes.
NOTE “:TRIGger” on page 179 describes the :TRIGg er command for advanced users using
“:TRIGger:CONFiguration:EXTended” on page 179.
response: none
example: trig 1