Resetting the Instrument | Simple measurement procedure (MEASure)
Measurement procedure with flexibility (READ) | Most flexible measurement procedure (INITiate and FETCh)
Measurement using software triggers | Multipoint measurement with specified trigger count
Waveform data retrieval function

Measurement using software triggers

To start the measurement using a software trigger, set the trigger source to BUS. After sending INIT, the KFM2150 enters the trigger-wait status (WTG). Send a software trigger (*TRG command or the IEEE488.1 get message) to start the measurement.

If the trigger count is set to 1, the KFM2150 enters the IDLE state after one measurement is completed.

If the trigger count is set to 2 or more, the KFM2150 enters the WTG status again after one measurement is completed. Then, send the next software trigger.

To check whether the KFM2150 has entered the WTG status, read the SEQ1 bit (for impedance measurement) or the SEQ2 bit (for voltage or current measurement) of the STAT:OPER:TRIG register.


[Status check]
STAT:OPER:TRIG? 'Return to [Status check] if the SEQ1 bit is not set.
(Read the response)
*TRG 'Send a software trigger.
If the number of triggers that have been sent is less than four, return to [Status check].
*OPC? 'When the measurement is complete, 1 is retrieved.
(Read the response)
FETC:IMP? 'Query the impedance data (magnitude) that has been measured.
(Read the response)
FETC:IMP:RES? 'Query the resistance data.
FETC:IMP:REAC? 'Query the reactance data.
FETC:IMP:PHAS? 'Query the phase data.
(Read the response)

When all measurements specified by trigger count are complete, FETC[:<meter_fn>]? can be used to retrieve the data. The response is the result obtained by averaging the specified trigger counts of data. If ARR is specified explicitly as in FETC:ARR:RES?, all the data can be retrieved in comma separated format. If the trigger count is set to 1, the same data is returned for SCAL and ARR.

If the trigger source is set to BUS, READ[:<meter_fn>]? cannot be used to instruct a measurement start. This is because there is no way to send a software trigger after sending READ[:<meter_fn>]? without canceling it. The measurement started with READ can be aborted only with ABOR, *RST, and *RCL or the IEEE488.1 sdc and dcl messages.

If the trigger source is set to BUS, do not send *OPC? when the number of sent triggers has not reached the trigger count. If you do, a deadlock will occur between the software trigger transmission and *OPC, and no response will be provided for *OPC. Sending a software trigger to continue the measurement will abort *OPC?.