INITiate commands initialize the trigger system. This enables the trigger system to receive triggers.
SCPI command |
Description |
INITiate |
|
Completes one full trigger cycle |
|
Enables internal data log session |
|
Enables/disables continuous transient triggers |
Syntax |
INITiate[:IMMediate] |
Description |
The INITiate command is used to initialize the trigger system of the PSU. This command completes one full trigger cycle when the trigger source is an IMMediate and initiates the trigger subsystem when the trigger source is BUS.
For example, when the IMMediate is selected as a trigger source, an INITiate command immediately transfers the VOLTage:TRIGgered[:AMPLitude] and CURRent:TRIGgered[:AMPLitude] values to VOLTage[:LEVel][:IMMediate][:AMPLitude] and CURRent[:LEVel][:IMMediate][:AMPLitude] values. Any delay is ignored.
Execution of this command also affects bit 5 (Waiting for TRIGger) of the Operation Instrument Isummary register (see Section 3.3.2). |
Usage example |
Generate a trigger operation after 5 seconds: TRIG:SOUR BUS TRIG:DEL 5 INIT *TRG |
Errors |
-213,"Init ignored" 307,"List lengths are not equivalent" 308,"Cannot be changed while transient trigger is initiated" 309,"Cannot initiate while in fixed mode" |
Related Commands |
*TRG INSTrument:COUPle:TRIGger |
Syntax |
INITiate:DLOG {<filename>} |
||||||
Description |
The command starts the internal data logging session. All selected measurements defined with SENSe:DLOG:FUNCtion:CURRent and SENSe:DLOG:FUNCtion:VOLTage commands will be saved periodically in the specified filename. The data logging session will last until time specified with the SENSe:DLOG:TIME not expired or is interrupted prematurely (e.g. using the ABORt:DLOG or *RST command).
Data log file contains header and data section. The header is 28 bytes long and include the following information in little-endian format, i.e. the least significant byte (LSB) value is at the lowest address:
|
||||||
|
Position |
Name |
Description |
||||
|
0 – 7 |
FILE_ID |
Always contains 0x45 0x45 0x5a 0x2d 0x44 0x4c 0x4f 0x47 (i.e. EEZ-DLOG text in ASCII format) |
||||
|
8 – 9 |
VERSION |
File format version (e.g. 0x01 0x00) |
||||
|
10 – 11 |
FLAGS |
0 – jitter column not included 1 – jitter column included |
||||
|
12 – 15 |
COLUMNS |
Information about measured values that will be stored. A four bits per channel are used in the following manner (up to 8 channels can be supported): |
||||
|
|
|
Bit |
Output value |
|||
|
|
|
0 |
Channel 1 Voltage |
|||
|
|
|
1 |
Channel 1 Current |
|||
|
|
|
2 |
Channel 1 Power |
|||
|
|
|
3 |
Channel 1 Reserved for future use |
|||
|
|
|
4 |
Channel 2 Voltage |
|||
|
|
|
… |
|
|||
|
16 – 19 |
PERIOD |
Sampling frequency as specified with the SENSe:DLOG:PERiod command written as float (e.g. IEEE-754 32-bit floating point number in little-endian format) |
||||
|
20 – 23 |
DURATION |
Internal data logging duration as defined with the SENSe:DLOG:TIME command. If data logging is interrupted prematurely (e.g. using the ABORt:DLOG or *RST command) recorded duration can be calculated from the log file size:
(FILE_SIZE – HEADER_SIZE) / (1 + NUM_COLUMNS) * PERIOD |
||||
|
24 – 27 |
START_TIME |
Date and time when internal data logging session started written using the Unix time format. |
||||
|
The Log file data section contains multiple rows recorded with sampling frequency (every PERIOD) for the max. duration specified in DURATION field in the header. Number of recorded columns in each row depends of selected values for data logging as specify in COLUMNS and FLAGS fields in the header. For example:
|
||||||
|
Position |
Description |
|||||
|
0 – 3 |
Jitter (if Jitter flag is set in FLAG field) |
|||||
|
4 – 7 |
First value (e.g. output voltage on Channel 1) |
|||||
|
8 – 11 |
Second value (e.g. output current on Channel 2) |
|||||
|
… |
|
|||||
|
|
|
|||||
Parameters |
Name |
Type |
Range |
Default |
|||
|
<filename> |
Quoted string |
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters |
– |
|||
Usage example |
INIT:DLOG "test_log.dlog" |
||||||
Related Commands |
*RST ABORt:DLOG MMEMory:INFOrmation? SENSe:DLOG:FUNCtion:CURRent SENSe:DLOG:FUNCtion:VOLTage SENSe:DLOG:PERiod SENSe:DLOG:TIME |
Syntax |
INITiate:CONTinuous {<bool>} INITiate:CONTinuous? |
|||
Description |
This command is used to select whether the trigger system is continuously initiated or not. With CONTinuous set to OFF, the trigger system remain in the IDLE state until CONTinuous is set to ON or INITiate:IMMediate is received. Once CONTinuous is set to ON, the trigger system will be initiated and exit the IDLE state. On completion of each trigger cycle, with CONTinuous ON, the trigger system immediately commence another trigger cycle without entering the IDLE state. When INITiate:CONTinuous is set to OFF, the current trigger cycle will be completed before entering the IDLE state. The return to IDLE also occur as the result of an ABORt or *RST command.
The ABORt command force the trigger system to the IDLE state; however, the value of INITiate:CONTinuous is unaffected.
If INITiate:CONTinuous was set to ON prior to receiving ABORt, it remains ON and the trigger system immediately exit the IDLE state. |
|||
Parameters |
Name |
Type |
Range |
Default |
|
<bool> |
Boolean |
OFF|ON|0|1 |
OFF |
Return |
The query command returns 0 if continuous transients are disabled (OFF), and 1 if continuous transients are enabled (ON). |
|||
Usage example |
INIT:CONT ON |
|||
Related Commands |
*RST ABORt |