Service pulse commands have reserved names and typically used for internal purposes of spectrometer. Pulse engine treated them in a special way. The syntax of pulse commands definitions is the same with ordinary commands. Defining of service pulse commands is not obligatory. Including of the definitions into configuration file causing pulse engine to incorporate corresponding action into full pulse sequence. Using of service pulse command in the pulse program (except detect) is not welcomed.

Full pulse sequence consists of pulse sequence produced from PPL and number of service sequences produced by service pulse commands (see Fig.1). Pulse, reptime and eos sequences are repeated according to amount of repetitions specified. Eor sequence finishing the full sequence.

Fig.1. Full pulse sequence.

Name

Description

scope

Scope trigger. Generate trigger synchronously with the chosen pulse of the pulse sequence.. All channels of this command have to be of up or down type. Length have to be specified. Part of sequence.

detect

Acquisition trigger. All channels of this command have to be of up or down type. Length have to be specified. Part of sequence.

reptime

Command to be executed to specify sequence repetition time. See also reptype key in CFP file overview. Channels can be of arbitrary type. If no pulses needed channel type 'space' have to be specified. The length of pulse is calculated as a difference between repetition time and lengths of pulse sequence and eos sequence.

bos

Begin of sequence command. Appears before the sequence. All channels of this command have to be of up, down or space type. Length have to be specified.

eos

End of sequence command. Depending on the eos key (see Pulse Configuration) can appear before or after reptime pulse. All channels of this command have to be of up, down or space type. Length have to be specified.

eor

End of run command. Appears after all repetitions are done and finishing a full pulse sequence. All channels of this command have to be of up or down type.