The MG362x1A trigger system is used to synchronize signal generator actions with software trigger commands. The MG362x1A follows the layered trigger model used in SCPI instruments. The following paragraphs describe operation and programming of the signal generator trigger system. The structure and components of the MG362x1A trigger model are shown in Figure: MG362x1A Trigger Model.

Turning power on, or sending *RST or :ABORt forces the trigger system into the idle state. The trigger system remains in the idle state until it is initiated. Trigger system initiation can happen on a continuous basis (:INITiate:CONTinuous ON) or on a demand basis (:INITiate:CONTinuous OFF). When the command :INITiate:CONTinuous is set to OFF, the trigger system is initiated by the :INITiate[:IMMediate] command. Note that *RST sets :INITiate:CONTinuous to OFF.

Once initiated, the trigger system enters an armed (wait for trigger) state. The trigger signal selected by the command :TRIGger[:SEQuence]:SOURce is examined until a TRUE condition is detected. The trigger signal selections are:

When a TRUE condition is detected, sweep generation of the selected sweep starts.

The command :TRIGger[:SEQuence][:IMMediate] provides a one-time override of the normal downward path in the trigger-event-detection state by forcing a TRUE trigger signal regardless of the setting for :TRIGger[:SEQuence]:SOURce.

Upon sweep completion, if :INITiate:CONTinuous is set OFF, the trigger system returns to the idle state. If :INITiate:CONTinuous is set to ON, the trigger system returns to the armed (wait for trigger) state.

Setting the command :INITiate:CONTinuous to ON and the command :TRIGger[:SEQuence]:SOURce to IMMediate, places the trigger system in an auto trigger mode. This causes continuous generation of the selected sweep.

The :ABORt command resets any sweep in progress and immediately returns the trigger system to the idle state. Unlike *RST, :ABORt does not change the settings programmed by other commands.