MIN and MAX

Parameters in Coupled

Commands

Command couplings can often result in “ Settings conflict” errors when the program executes. When a coupled command is executed, the command setting is evaluated by the digitizer processor. If the setting causes an illegal digitizer configuration, a "Settings conflict" error occurs. The error message lists the conflicting settings, and then reports the values set by the digitizer processor.

The "Comments" section of each command entry indicates if a command is coupled, and if it is, what the coupling constraints are.

When MINimum or MAXimum is a command parameter in a group of coupled commands, that command should be the last command executed. Unlike other parameters that are set when an end-of-line indication is received, MIN and MAX are evaluated by the digitizer processor when the command is parsed. Thus, the value of MIN or MAX is based on the values of the other (coupled) commands at that time. For example, if the following commands are sent:

ARM:COUN 1

TRIG:COUN MAX

ARM:COUN 128

Executable When Initiated Commands

A “ Settings conflict” error will occur when ARM:COUN 128 is executed because the trigger count value set by TRIG:COUN MAX (524,288) is based upon the ARM:COUN 1 setting. For an arm count of 128, the maximum trigger count allowed is 4,096. Because of these types of interactions, MIN and MAX are not recommended for specifying a parameter value.

In the "Comments" section of each command listing is the item

"Executable when initiated: Yes/No". This identifies the command as being executable when the digitizer is in the INITiated state as the result of one of the following commands:

INITiate:IMMediate

VINStrument:CONFigure:VME:MEMory:INITiate

VINStrument:CONFigure:LBUS:MEMory:INITiate

Chapter 4

Command Reference 183

Page 183
Image 183
HP E1429A manual Executable When Initiated Commands, MIN and MAX Parameters in Coupled Commands, Armcoun Trigcoun MAX