Triggering infrastructure

[prasimix]

A triggering infrastructure will allow us to control various actives via SCPI commands remotely, locally or using digital input pin on the front panel (when TRIGger[:SEQuence]:SOURce PIN1, See also [SOURce:]DIGital:PIN<n>:FUNCtion and [SOURce:]DIGital:PIN<n>:POLarity). The following SCPI subsystems have to be supported:

• *TRG (see also *OPC, *WAI)
• ABORt
• INITiate
• TRIGger

[prasimix]

For TRIGger[:SEQuence]:SOURce KEY use encoder switch instead of button displayed on the TFT display. Change KEY to MANual

[prasimix]

POSitive and NEGative SLOPe seems that are exchanged. Also for better control a new command has to be added: TRIGger[:SEQuence]:TYPE {EDGE|LEVel} where EDGE is default.

[prasimix]

SLOPe polarity is now fixed.

[prasimix]

We need clarification regarding inital TRIGGered value for VOLTage and CURRent and when trigger is executed. For example if *RST is applied we have:

VOLT:TRIG?
nan

... and when triggered value is once set it is not clear does it persist to the next triggering event or not. This is important to know if we'd like to introduce OUTP:TRIG command since we have to know what will be set as new VOLT when next triggering event is happen. A hypothetical example:

VOLT:TRIG 12
TRIG:SOUR IMM
INIT
OUTP OFF
VOLT 3.3
VOLT:TRIG?
12.00
OUTP ON
INIT

If previous VOLT:TRIG value remains (instead of nan) then after next trigger INIT voltage will rise from 3.3 to 12 V that could be dangerous.

[prasimix]

Short version ABOR is not accepted.

[prasimix]

Fixed