Remote command syntax, Command syntax for medtester, Command syntax for computer – Fluke Biomedical Cufflink User Manual

Page 78: Command parameters

Advertising
background image

Cufflink

Operators Manual

3-4

Remote Command Syntax

A computer or a medTester with medCheck can be used to control the Analyzer. For both

controllers, start remote commands with a command verb and add optional parameters

(values that further define the remote command).
Remote commands are not case sensitive; either upper or lower case letters can be used

anywhere in the command, and the Analyzer understands it. The differences in syntax for

each controller are explained below (n represents the parameter value).

Command Syntax for medTester

When the Analyzer is controlled with a medTester, separate the command verb from the

parameter list with a colon and separate each parameter with a semicolon. Do not put

spaces anywhere in the command line. The syntax is:
CommandVerb:parameter=n;parameter=n
Example: makearm:hr=60,envshift=50

Command Syntax for Computer

When the Analyzer is controlled with a computer, separate the command verb from the

parameter list with a space or a colon. Separate the parameters with a comma or

semicolon. The syntax is:
CommandVerb parameter=n,parameter--r-
Example: makearm hr=60,envshift=50
or
CommandVerb:parameter=n;parameter=n
Example: makearm:hr=60;envshift=50

Command Parameters

Command parameters are values specified to further define remote commands. For

example, different heart rates can be specified for the makearm command.
If no command parameters are specified, the Analyzer uses current values. Current values

are either the default values or the values used in a previous command.
Parameters for each command are described in the Command Descriptions section later

in this chapter.

Default Values

Default values are reassigned to all remote commands each time the Analyzer is powered

up. The Analyzer uses default values for the first command given to it if no parameters

have been specified. For example, the command makearm has no parameters defining it,

so the Analyzer uses default values. However, if "malcearm:hr=30" were specified as a

parameter that sets the heart rate at 30 BPM, the Analyzer would use that value instead of

the 80 BPM default value.

Advertising