Fluke 190 Programmers Guide

REMOTE CONTROL AND

PROGRAMMING REFERENCE

for all FLUKE 190 family

of

ScopeMeter® test tools

© Fluke Corporation 1996, 2012

Revision 1a – December 2012

Copyright © 1996, 2012 Fluke Corporation or its subsidiaries.

Productnames and brandnames which appear in this document may be trademarks or registered trademarks of their respective owners.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2

TABLE OF CONTENTS

Table of Contents ................................................................................................................................................. 3

Introduction .......................................................................................................................................................... 5

INTRODUCTION TO PROGRAMMING ................................................................................................................... 7

Basic Programming Information ....................................................................................................................... 7

Commands structure ........................................................................................................................................ 7

Responses to receive from the ScopeMeter .................................................................................................... 8

Acknowledge .................................................................................................................................................... 8

Command and Response Terminators (Message Terminators) ...................................................................... 9

Typical program sequence - An example ......................................................................................................... 9

COMMAND REFERENCE...................................................................................................................................... 11

Conventions .................................................................................................................................................... 11

AS AUTO SETUP ..................................................................................................................................... 13

AT ARM TRIGGER ................................................................................................................................... 14

CM CLEAR MEMORY ............................................................................................................................... 16

DS DEFAULT SETUP ................................................................................................................................ 17

GD GET DOWN........................................................................................................................................ 18

GL GO TO LOCAL .................................................................................................................................... 19

GR GO TO REMOTE ................................................................................................................................ 19

HO HOLD ........................................................................................................................................ 21

ID IDENTIFICATION ................................................................................................................................ 22

IS INSTRUMENT STATUS ....................................................................................................................... 23

PC PROGRAM COMMUNICATIONS (not used in 190-series-II) ............................................................. 25

PS PROGRAM SETUP .............................................................................................................................. 26

QM QUERY MEASUREMENT .................................................................................................................... 29

QP QUERY PRINT .................................................................................................................................... 34

QS QUERY SETUP.................................................................................................................................... 40

QW QUERY WAVEFORM .......................................................................................................................... 41

RD READ DATE ........................................................................................................................................ 43

RI RESET INSTRUMENT ......................................................................................................................... 44

RP REPLAY ........................................................................................................................................ 46

RS RECALL SETUP ................................................................................................................................... 48

RT READ TIME ........................................................................................................................................ 50

SO SWITCH ON ....................................................................................................................................... 51

SS SAVE SETUP ...................................................................................................................................... 52

ST STATUS QUERY ................................................................................................................................. 53

TA TRIGGER ACQUISITION ..................................................................................................................... 55

WD WRITE DATE ...................................................................................................................................... 56

WT WRITE TIME ...................................................................................................................................... 57

Appendix A ASCII Codes ..................................................................................................................... 58

Appendix B
Appendix C
Appendix D
Appendix E
Appendix F
Appendix G

Installing the interface cable and drivers........................................................................ 60

Installing USB-drivers for 190-series-II............................................................................ 61

Acknowledge Data .......................................................................................................... 64

Status Data ...................................................................................................................... 65

Waveform Data ............................................................................................................... 66

Program Example for Query Waveform ......................................................................... 70

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 3

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 4

INTRODUCTION

When using ScopeMeter® testtools, the desire to store any measurement results on the PC, for reference
purposes or for documenting the tests made is rather obvious. For that purpose, Fluke offers a dedicated
software package: FlukeView ScopeMeter for Windows (or ‘SW90W’). It allows the user to store test results,
be it voltage readings or complete scope screen images, or long-time recordings of successive measurements
over time, or even to make a spectral analysis and see what frequency components are contained within a
signal. FlukeView offers all this in a readily available software package, at an affordable price, with user
interface in either English, French or German language, to run on a Windows PC.

FlukeView offers the possibility to store complete instrument settings on the PC, as a file, for sharing those
with co-workers or for re-using them at a later point in time. And the package even includes a possibility to
remotely control the ScopeMeter testtool via a ‘virtual instrument’ seen on the PC-screen, where the mouse
can be used to press keys just like you would on the real instrument; leave your ScopeMeter is a testtroom
and control it remotely, while staying in a more safe environment yourself.

FlukeView ScopeMeter software is readily available as a commercial package, for applications on a Windows
PC (Win-XP or later). When in doubt about purchasing the package, a trial version is available as a demo
package (meaning: no storage nor printing capabilities included). For virtually all ScopeMeter users,
FlukeView ScopeMeter is the perfect tool to get all tasks mentioned above covered – quickly and
conveniently.

Nevertheless, in some situations end-users of ScopeMeter testtools want to write test protocols themselves,
for instance for educational purposes, or want to use ScopeMeters in a larger system-set-up in which
FlukeView can’t be easily included or can’t provide the functionality that the user is looking for. For that
reason, we have written the document at hand.

This document contains remote control and programming information for all models of the different series of
the Fluke 190-series ScopeMeter® testtools. Previous editions of the document dealt with the ‘original 190­series’ (instruments that can be recognized by three digit typenumbers without any letters included, e.g.
‘Fluke-199’), and later on was extended to also cover the 190B and 190C series (e.g. ‘Fluke-196C’). This
edition now is created as an update to extend the description and to support the newer ‘Fluke 190-series-II’
instruments as well (model numbers like ‘Fluke-190-204’ or ‘Fluke-190-502’).

The first edition was written around the PM9080 Optically Insulated RS232 Adapter/Cable, which was the
only interface cable available at that point in time. At a later stage, the OC4USB was introduced, which
includes an RS-232 to USB converter, and which behaves just like the PM9080, yet it uses the electrical
interface of the USB-port to establish the physical connection to the (notebook-)PC. From PC-side, however,
this interface is seen through a virtual RS-232-port, also known as a COM-port, and command handling is
exactly the same as when using the PM9080.

The Fluke-190-series-II has a similar kind of interface/converter built into the instrument mainframe. If you
look at the testtool body, you may see a USB-connector on the side of the instrument (in case you can’t find
it: open the plastic cover on the left-hand side of the testtool, closest to the on/off switch). An optical
interface inside the ScopeMeter housing provides the hardware link between that USB-port and the other
internal electronics, while ensuring full electrical insulation, needed to use the testtool as a double insulated
instrument in CAT III 1000 V applications. As a result of this interface, and seen from the PC-side, also the
190-series-II ScopeMeter testtools are controlled through a virtual RS-232 port (a.k.a. ‘a COM-port’).

Details about making the interconnection between PC and instrument using PM9080 or the OC4USB may be
found in Appendix B of this document.

Drivers for the interface cables for the 190, 190B and 190C series were included on the CD-ROM that is or
was found with the instrument.
Details about installing the dedicated USB-drivers for the 190-series-II testtools can be found as Appendix C
of this document.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 5

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 6

INTRODUCTION TO PROGRAMMING

SS 8

Basic Programming Information

Before trying to remotely control any ScopeMeter tetstool, a communication link needs to be established
between PC and ScopeMeter. Next, the software interface needs to be established. Refer to Appendix B and
C for details. Once you have installed the interface and drivers, you can control the ScopeMeter® from the
computer with simple communication facilities, such as GWBASIC, QuickBASIC or QBASIC, programming
languages from Microsoft® Corporation.

All examples given in this manual are in the QBASIC language but will also run in QuickBASIC.

QuickBASIC, as a compiler, allows you to make executable files of programs, so you can start such programs
directly from DOS. For reading and interpreting this manual, knowledge of these programming languages is
assumed. QBASIC was supplied with Microsoft MS-DOS 5.0 and higher and with Windows 95, 98, and NT.
With newer Windows operating systems, QBasic is no longer included as a standard, but it is available as
freeware instead, e.g. through ‘quickbasic.sourceforge.net’.
The benefit of presenting the program examples as QBASIC files is in transparency, the easy ‘readability’ even
for programming engineers who are accustomed to work in other, newer programming languages.

Features of the syntax and protocol used with ScopeMeters are as follows:

• Easy input format with a ‘forgiving’ syntax: all commands consist of two characters that can be either
in UPPER or lower case. Parameters, that sometimes follow the command, may be separated from it
by one or more separation characters.

• Strict and consistent output format:

o alpha character responses are always in UPPERCASE.

o Parameters are always separated by a comma ("," = ASCII 44, see Appendix A).

o Responses always end with the carriage return code (ASCII 13). Because the carriage return

code is a non-visible character (visible neither on screen nor on a print-out), this character
is represented as <cr> in the command syntax.

• Synchronization between input and output: after receipt of each command, the ScopeMeter returns
an acknowledge character followed by the carriage return code (ASCII 13). This indicates that the
command has been successfully received and executed. The computer program must always read
this acknowledge response before sending the next command to the ScopeMeter testtool. See
below and Appendix D for details.

Commands structure

All remote commands for the ScopeMeter consist of a header, made up of two letters (‘alpha characters’),
which are sometimes followed by additional parameters. Example:

RI

Some of the commands are followed by one or more parameters to give the ScopeMeter more information.
Example:

This is the Reset Instrument command. It resets the ScopeMeter.

This is the Save Setup command. It saves the present acquisition settings in memory.
The SS header is followed by a separator (space), then followed by the parameter "8" to
indicate where to store the settings. The meaning of this parameter is described in
Chapter 3 COMMAND REFERENCE.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 7

Some commands require several parameters. Example:

WT 9,50,30

This is the Write Time command. This command requires three parameters. The
parameters are separated by a comma, which is called the Program Data Separator.
You may use only one comma between the parameters.

Also refer to the section ‘Data Separators’.

A code at the end of each command tells the ScopeMeter that the command is ended. This is the carriage
return code (ASCII 13) and is called the Program Message Terminator. This code is needed to indicate to the
ScopeMeter that the command is completed so it can start executing the command.

Also refer to the section ‘Command and Response Terminators’.

Responses to receive from the ScopeMeter

After each command sent to the ScopeMeter, there is an automatic response coming back from it, indicated
as < acknowledge> which you MUST input (receive and handle), to let the computer know whether or not the
previous command has been successfully executed.

Refer to the ‘Acknowledge’ section below.

There are several commands that ask the ScopeMeter for response data. Such commands are called Queries.
Example:

ID

This is the IDentification query which asks for the model number and the software
version of the ScopeMeter.
When the ScopeMeter receives a query it sends the < acknowledge> reply, just as it does
after every command received, but now it is followed by the requested response data.

The format of the response data depends upon which query was sent. When a response consists of different
response data portions, these are separated by commas (ASCII character 44).

Also refer to the section ‘Data Separators’, below.

All response data, < acknowledge> as well as following (requested) response data, is terminated by the
carriage return code (<cr> = ASCII 13).

Also refer to the section ‘Command and Response Terminators’.

Acknowledge

After receiving a command, the ScopeMeter automatically returns the <acknowledge> response to let the
computer know whether or not the received command has been successfully executed. This response is a
one-digit number followed by <cr> as response terminator.

• If <acknowledge> is 0, it indicates that the ScopeMeter has successfully executed the command.

• If the command was a query, the <acknowledge><cr> response is immediately followed by the

requested response data, terminated by <cr>.

• If <acknowledge> is 1 or higher, this indicates that the ScopeMeter testtool has not executed the
command successfully. In that case, and if the command was a query, the <acknowledge><cr>
response is NOT followed by any further response data.

There can be several reasons for a non-zero <acknowledge> response. For more details, refer to Appendix D.

In case of an error you can obtain more detailed status information by using the ST (STATUS) query.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 8

Notes:

1. You MUST ALWAYS input <acknowledge> (that is: make the PC accept this acknowledgement), even
when the original command was not a query.

2. Throughout this manual, the <acknowledge> may be written in full (as was just done), or as <ackn>.

Data Separators

Data Separators are used between parameters sent to the ScopeMeter and between values and strings
received from the ScopeMeter.
Comma (",") is used as program data separator as well as response data separator:

- Program Data Separator

Name Character ASCII value

(Decimal)

Comma , 44 Single comma allowed

- Response Data Separator

Comma , 44

Comments

Command and Response Terminators (Message Terminators)

- Command (Program Message) Terminators

A code is needed at the end of each command to tell the ScopeMeter that the command is ended, and that
the instrument can start executing the command. This code is called the Program Message Terminator. The
code needed for the ScopeMeter is carriage return (ASCII code 13 decimal).

Notes:

1. The carriage return code is a non-visible ASCII character. Therefore this code is represented as <cr> in
the Command Syntax and Response Syntax lines given for each command.

2. The QBASIC programming language, which is used for all program examples, automatically adds a

carriage return to the end of the command output. (In the QBASIC language, this is the PRINT #....

statement.)

Once <cr> is recognized by the ScopeMeter, the entered command is executed. After EACH command, the
ScopeMeter returns <ackn><cr> to the computer to signal the end of the command processing (also see the
section ‘Acknowledge’.)

- Response (Message) Terminators

The response from the ScopeMeter ends with a carriage return (ASCII 13). This is indicated as <cr> in the
Response Syntax for each command.

Typical program sequence - An example

A typical program sequence consists of the following user actions:

1. Set the communication parameters for the RS232 port of the computer to match the ScopeMeter
settings (not needed for 190-series II).

2. Send a command or query to the ScopeMeter.

3. Read (input) the acknowledge response from the ScopeMeter.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 9

If the response value is zero, go to step 4.

If the response value is not zero, the ScopeMeter didn’t execute the previous command. Read the
error message from the following acknowledge subroutine, recover the error, and repeat the
command or query (this is not shown in the following program example.)

4. If a query was sent to the ScopeMeter, read the response.

5. The sequence of steps 2, 3, and 4 may be repeated for different commands or queries.

6. Close the communication channel.

The following program example gives this in more detail:

‘Example of a typical program sequence:
‘***************** Beginning of example program ****************
OPEN "COM1:1200,N,8,1,CS,DS,RB2048" FOR RANDOM AS #1
‘This QBASIC program line sets the parameters for the
‘RS232 port (COM1 on the Computer) to match the
‘ScopeMeter power-on default settings. It also opens a
‘communication channel (assigned #1) for input or output
‘through the COM1 port. Your ScopeMeter must be connected
‘to this port. "RB2048" sets the size of the computer
‘receive buffer to 2048 bytes to prevent buffer overflow
‘during communication with the ScopeMeter.
PRINT #1, "ID" ‘Outputs the IDENTITY command (query) to the ScopeMeter.
GOSUB Acknowledge ‘This subroutine inputs the acknowledge response from
‘the ScopeMeter and displays an error message if the
‘acknowledge value is non-zero.
INPUT #1, Response$ ‘This inputs the response data from the IDENTITY query.
PRINT Response$ ‘Displays the queried data.
CLOSE #1 ‘This closes the communication channel.
END ‘This ends the program.
‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.
Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT "Error "; ACK; ": ";
SELECT CASE ACK
CASE 1
PRINT "Syntax Error"
CASE 2
PRINT "Execution Error"
CASE 3
PRINT "Synchronization Error"
CASE 4
PRINT "Communication Error"
CASE IS < 1
PRINT "Unknown Acknowledge"
CASE IS > 4
PRINT "Unknown Acknowledge"
END SELECT
PRINT "Program aborted."
END
END IF
RETURN
‘****************** End of example program *****************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 0

COMMAND REFERENCE

Conventions

Page layout used for each command

XY Header

Each command description starts with a header for quickly finding the command.

This header includes the two-character command indicator (i.c. ‘XY’) used for the command
syntax, and includes the full command name (i.c. ‘HEADER’). Note: for the sake of this example,
the command indicator differs from the command name, where usually one is an abbreviation of
the other.

Purpose: Explains what the command does or what it is used for.

Command

Syntax:

Response

Syntax:

Note: Further notes relating to the command, or giving reference to associated

Example: This is an example QBASIC program which shows how you can use the

‘***************** Beginning of example program *****************
‘
‘
‘******************** End of example program ********************

Use an MS-DOS Editor and copy the complete example program between the two lines to a file name with
the .BAS extension. Start QBASIC and open this file from the FILE menu. Longer programs may include page
breaks. Pay attention to remove those prior to running the program, or make them proceed by the ‘ (=remark)
character to prevent the QBASIC interpreter from interpreting them as an incorrect statement.

Shows the syntax for the command. Parameters are separated by commas.
Commands are terminated by <cr> (carriage return).

Shows the format of the response from the ScopeMeter. Responses are
terminated by <cr> (carriage return). Each Response Syntax starts with the
<ackn> response, followed by the query response if the syntax relates to a
query.

commands.

command. The example may also include some other commands to show
the relation with those commands.
The following two comment lines (which start with an ‘ ) successively
indicate the beginning and the end of an example program.

Note: some editors may not recognize the quote (‘) symbol as the start of a REMARK-line. In such case,
replace the quote-symbols by a REM-text.

When you have connected the ScopeMeter, you can start the program from the RUN menu.

You may want to refer to the Table of Contents on page 3 for an overview of all available commands, for an
easier reference.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 1

Syntax conventions

The Command Syntax and the Response Syntax may contain the following meta symbols and data elements:

UPPERCASE These characters are part of the syntax. For commands, lower case is also allowed.

<...> An expression between these brackets is a code, such as <cr> (carriage return)

that can not be expressed in a printable character, or it is a parameter that is
further specified.
Do not actually include these brackets in the command!

[...] The item between these brackets is optional.

This means that you may omit it from the command, or the ScopeMeter may omit
this from a response.
Do not actually include these brackets in the command!

| This is a separator between selectable items. This means, that you must choose to

use only one of the listed items (exclusive or).

{.....} Specifies an element that may be repeated zero or more times.

(…...) Grouping of multiple elements.

<binary_character> = 0 to 255

<digit> = 0 to 9

<sign> = + or  [this is: positive or negative]

<decimal_number> = <digit>{<digit>}

<float> = <mantissa><exponent>

<mantissa> = <signed_integer>

<exponent> = <signed_byte>

<signed_integer> = <binary_character><binary_character>

Two bytes representing a signed integer value. The first byte is the most
significant and contains the sign bit (bit 7).

<signed_long> = four <binary_character>‘s

<unsigned_integer> = <binary_character><binary_character>

Two bytes representing an unsigned integer value. The first byte is the most
significant.

<unsigned_long> = four <binary_character>‘s

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 2

AS AUTO SETUP

Purpose: Switches on the AUTO-ranging mode of the ScopeMeter, which will allow it to

automatically adept the actual instrument settings to the input signals applied.

Command Syntax:

Response Syntax:

AS<cr>

<ackn><cr>

Notes:

• You may select elements of the setup not to modified by the AUTO SET
procedure, by going through the USER OPTIONS menu of the ScopeMeter.

• The instrument will send the <ackn> as soon as the Autoranging mode has been
activated. This doesn’t indicate that a stable or the most suitable display of the
applied input signal would have been arrived at. Depending on a series of
variables, achieving a stable display may take up to 10 seconds. Reaching such
stability is not signaled to the PC, though. Once AURTORANGING is active,
settings may also change in case the signal changes.

Example: Example: The following example program sends an AUTO SETUP command to the

ScopeMeter. Connect a repetitive signal on INPUT A to see the effect of AUTO
SETUP.

‘***************** Beginning of example program *****************
CLS ‘Clears the PC screen.
OPEN "COM1:1200,N,8,1,CS,DS,RB2048" FOR RANDOM AS #1
PRINT #1, "AS" ‘Sends AUTO SETUP command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT "Error "; ACK; ": ";
SELECT CASE ACK
CASE 1
PRINT "Syntax Error"
CASE 2
PRINT "Execution Error"
CASE 3
PRINT "Synchronization Error"
CASE 4
PRINT "Communication Error"
CASE IS < 1
PRINT "Unknown Acknowledge"
CASE IS > 4
PRINT "Unknown Acknowledge"
END SELECT
PRINT "Program aborted."
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 3

AT ARM TRIGGER

Purpose: Resets and arms the trigger system for a new acquisition. This command can also be

used for single shot acquisitions. When the AT command is given while an
acquisition is in progress, this acquisition is aborted and the trigger system is
rearmed. The command can also be used to go from other mdoes (e.g. from Replay
mode) to ‘live’ acquisition mode.

Command Syntax:

Response Syntax:

AT<cr>

<ackn><cr>

Notes:

• Also see the example program for the IS command, which uses the AT command
for a single shot application.

• The <ackn> is sent only once the ScopeMeter has completed rearming the
acquisition system

Example: The following example program (see next page) arms the trigger system of the

ScopeMeter using the AT command. This means that after this command the
ScopeMeter starts an acquisition as soon as a trigger is generated by the actual
signal (thus: when signal exceeds the trigger level) or from a TA (Trigger Acquisition)
command.

After the AT (Arm Trigger) command it is assumed that the signal amplitude is
sufficient to actually trigger the acquisition. If not, you can use the TA (TRIGGER
ACQUISITION) command to force the acquisition to start. This is not useful, however,
if you want the acquisition to be actually started by a signal transition, for
synchronization purposes.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 4

‘***************** Beginning of example program *****************
OPEN "COM1:1200,N,8,1,CS,DS,RB2048" FOR RANDOM AS #1
PRINT #1, "AT" ‘Sends the ARM TRIGGER command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
CLOSE #1
END
‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.
Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT "Error "; ACK; ": ";
SELECT CASE ACK
CASE 1
PRINT "Syntax Error"
CASE 2
PRINT "Execution Error"
CASE 3
PRINT "Synchronization Error"
CASE 4
PRINT "Communication Error"
CASE IS < 1
PRINT "Unknown Acknowledge"
CASE IS > 4
PRINT "Unknown Acknowledge"
END SELECT
PRINT "Program aborted."
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 5

CM CLEAR MEMORY

Purpose: Clears all saved setups, waveforms, and screens from internal memory.

Command Syntax:

Response Syntax:

Note: Reciving the <ackn> confirms that the action has been completed. Depending on

Example: See below

‘***************** Beginning of example program *****************
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
PRINT #1,”CM” ‘Sends the Clear Memory command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

CM<cr>

<ackn><cr>

memory size of the instrument at hand, this may take several seconds.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 6

DS DEFAULT SETUP

Purpose: Resets the ScopeMeter to the factory-default settings, just like these were at the

moment of original delivery, except for the RS232 communication settings such as
baud rate (so as to keep the communications alive).

Command Syntax:

Response Syntax:

DS<cr>

<ackn><cr>

Notes:

• Wait for at least 2 seconds after the <ackn> reply has been received, so as to let
the ScopeMeter settle itself, before you send the next command.

• A Master Reset (refer to the Users Manual) performs the same, but also resets
the RS232 communication settings to the default values.

• Refer to AS (= Auto Setup) for a command that gives an automatic adaptation of
settings to match the applied input signals.

Example: See below

‘***************** Beginning of example program *****************
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
CLS
PRINT #1, “DS” ‘Sends DEFAULT SETUP command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
SLEEP 2 ‘Delay (2 sec.) necessary after “DS”.
PRINT #1, “ID” ‘Sends the IDENTIFICATION query.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
INPUT #1, ID$ ‘Inputs identity data from ScopeMeter.
PRINT ID$ ‘Displays identity data.
CLOSE #1
END
‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.
Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 7

GD GET DOWN

Purpose: Switches off the instrument’s power system.

Command Syntax:

Response Syntax:

GD<cr>

<ackn><cr>

Notes:

• If external power (mains adapter) is supplied, you can use the SO command to
switch the instrument on again.

• If no external power is connected, the instrument can only be switched on
manually by pressing the ON/OFF key.

Example: See below

‘***************** Beginning of example program *****************
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
CLS
PRINT #1, “GD” ‘Sends the GET DOWN command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
PRINT “The GET DOWN command switched the ScopeMeter off.”
PRINT “Press any key on the PC keyboard to switch “
PRINT “the ScopeMeter on again.”
SLEEP
PRINT #1, “SO” ‘Sends the SWITCH ON command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 8

GL GO TO LOCAL

Purpose: Switches on the ‘local operation mode’, this is: enable the keypad for local (manual)

control.

Command Syntax:

Response Syntax:

Note: Also refer to the GR (Go to Remote) command.

GL<cr>

<ackn><cr>

Example:

The following example (see next page) uses the GR (GO TO REMOTE) command to
set the ScopeMeter in the REMOTE state so that the keypad is disabled. Next, the GL
(GO TO LOCAL) command is sent to activate the keypad and provide manual (local)
operation of the ScopeMeter testtool again.

GR GO TO REMOTE

Purpose: Sets the ScopeMeter in the remote operation mode which disables local (keypad

controlled) operation.

Command Syntax:

Response Syntax:

Notes: You can use the following methods to return to the local operation mode so as to

GR<cr>

<ackn><cr>

enable manual (local) operation again:

1. Sending the GL (GO TO LOCAL) command.

2. Switching off the instrument (through on/off key on the front panel or
through GD command), then switching on again (through SO command or
locally, using on/off key on front panel).

Example: The following example (see next page) uses the GR (GO TO REMOTE) command to

set the ScopeMeter in the REMOTE state so that the keypad is disabled. Next, the GL
(GO TO LOCAL) command is sent to activate the keypad and provide manual (local)
operation of the ScopeMeter testtool again.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 1 9

‘***************** Beginning of example program *****************
CLS ‘Clears the PC screen.
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
PRINT #1, “GR” ‘Sends GO TO REMOTE command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
PRINT “All ScopeMeter keys (except the Power ON/OFF key)
PRINT “are now disabled by the GR (GO TO REMOTE) command.”
PRINT “Check this.”
PRINT
PRINT “Press any key on the PC keyboard to continue.”
SLEEP
PRINT
PRINT #1, “GL” ‘Sends GO TO LOCAL command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
PRINT “The ScopeMeter keys are now enabled again by the “
PRINT “GL (GO TO LOCAL) command.”
PRINT “Check this.”
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 0

HO HOLD

Purpose: Sets the ScopeMeter in the Hold mode. In more detail: the ScopeMeter stops

sampling the input channels and stops calculating new measurement results.
Bringing the instrument to Hold-mode makes it ‘freeze’ the display.

Command Syntax:

Response Syntax:

Example: The following example program uses the HO command to stop the signal acquisition

‘***************** Beginning of example program *****************
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
CLS
PRINT #1, “HO” ‘Sends the HOLD command.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
PRINT “The HOLD command has put the ScopeMeter in HOLD.”
PRINT “Check on the ScopeMeter screen.”
PRINT “Press any key on the PC keyboard to continue and”
PRINT “enable acquisition again.”
SLEEP
PRINT #1, “AT” ‘Sends the ARM TRIGGER command to
‘enable acquisition again.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

HO<cr>

<ackn><cr>

and freeze the information on screen; next it uses the AT (ARM TRIGGER) command
to enable a new acquisition of applied input signal(s) again.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 1

ID IDENTIFICATION

Purpose: Makes the ScopeMeter send its model identification data to the PC.

Command Syntax:

Response Syntax:

Example: The following example program queries the identity data of the ScopeMeter and

‘***************** Beginning of example program *****************
CLS ‘Clears the PC screen.
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
PRINT #1, “ID” ‘Sends IDENTIFICATION query.
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter.
INPUT #1, IDENT$ ‘Inputs the queried data.
PRINT IDENT$ ‘Displays queried data.
CLOSE #1
END

‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT "Unknown Acknowledge"
END SELECT
PRINT "Program aborted."
END
END IF
RETURN
‘******************** End of example program ********************

ID<cr>

<ackn><cr>[<identity><cr>]

where,
<identity> is an ASCII string containing the following data elements:
<model_number>;<software_version>;<creation_date>;<languages>

displays this data on the PC screen.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 2

IS INSTRUMENT STATUS

0

1

2

5

6

7

8

9

10

11

12

13

14

15

Purpose: Queries the contents of the ScopeMeter’s status register. The returned value

reflects the present operational status of the testtool itself (see note).
Status is indicated by a 16-bit word, presented as an integer value, where each bit
signals the logical status of an individual parameter (so: represented as 1 or 0). See
table below for details.

Command Syntax:

Note: Not to be confused with the ST-command (Status Query), which provides status

Response Syntax:

<status>

Bit Value Status Description

3
4 16 Remote

1024 Pre Calibration valid
2048 Replay buffer full
4096 Triggered

8192 Instrument On
16384 Instrument Reset occurred
32768 Next <status> field available. Not used to date (hence always 0)

Example program – See next page.

IS<cr>

information about the CPL-interface (e.g. ‘Illegal Command’ or ‘Checksum Error’).

<ackn><cr>[<status><cr>]

where,
<status> = integer value 0 to 65535 (see below)

1 Maintenance mode
2 Charging
4 Recording
8 AutoRanging

32 Battery Connected

64 Power Adapter (external power) applied
128 Calibration necessary
256 Instrument in HOLD mode
512 Pre Calibration busy

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 3

‘***************** Beginning of example program *****************

CLS ‘Clears the PC screen
OPEN “COM1:1200,N,8,1,CS,DS,RB2048” FOR RANDOM AS #1
PRINT #1, “IS” ‘Sends the INSTRUMENT STATUS query
GOSUB Acknowledge ‘Input acknowledge from ScopeMeter
INPUT #1, Status$ ‘Input Instrument Status
StV = VAL(Status$) ‘Decimal value of Instrument Status
PRINT “Instrument Status : “; StV
IF (StV AND 1) = 1 THEN PRINT “ ScopeMeter in Maintenance mode.”
IF (StV AND 2) = 2 THEN PRINT “ ScopeMeter charging.”
IF (StV AND 4) = 4 THEN PRINT “ ScopeMeter recording.”
IF (StV AND 8) = 8 THEN PRINT “ AutoRanging active”
IF (StV AND 16) = 16 THEN PRINT “ ScopeMeter remote.”
IF (StV AND 32) = 32 THEN PRINT “ Battery connected.”
IF (StV AND 64) = 64 THEN PRINT “ Power Adapter connected.”
IF (StV AND 128) = 128 THEN PRINT “ Calibration necessary.”
IF (StV AND 256) = 256 THEN PRINT “ ScopeMeter in HOLD.”
IF (StV AND 512) = 512 THEN PRINT “ Pre-calibration busy.”
IF (StV AND 1024) = 1024 THEN PRINT “ Pre-calibration valid.”
IF (StV AND 2048) = 2048 THEN PRINT “ Replay-buffer full.”
IF (StV AND 4096) = 4096 THEN PRINT “ ScopeMeter triggered.”
IF (StV AND 8192) = 8192 THEN PRINT “ ScopeMeter On.”
ELSE
PRINT “ ScopeMeter Off.”
END IF
IF (StV AND 16384) = 16384 THEN PRINT “ Reset Instrument occurred.”
END
‘******************* Acknowledge subroutine *********************
‘Use this subroutine after each command or query sent to the
‘ScopeMeter. This routine inputs the acknowledge response from
‘the ScopeMeter. If the response is non-zero, the previous
‘command was not correct or was not correctly received by
‘the ScopeMeter. Then an error message is displayed and
‘the program is aborted.

Acknowledge:
INPUT #1, ACK ‘Reads acknowledge from ScopeMeter.
IF ACK <> 0 THEN
PRINT “Error “; ACK; “: “;
SELECT CASE ACK
CASE 1
PRINT “Syntax Error”
CASE 2
PRINT “Execution Error”
CASE 3
PRINT “Synchronization Error”
CASE 4
PRINT “Communication Error”
CASE IS < 1
PRINT “Unknown Acknowledge”
CASE IS > 4
PRINT “Unknown Acknowledge”
END SELECT
PRINT “Program aborted.”
END
END IF
RETURN
‘******************** End of example program ********************

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 4

PC PROGRAM COMMUNICATIONS

Purpose: Programs the baud rate for RS232 communications (not used with 190-series-II).

Command Syntax:

PC <baudrate>

where,
<baudrate> = 1200 | 2400 | 4800 | 9600 | 19200
38400 (Fluke 19xC)
57600 (Fluke 19xC, PM9080/101 or OC4USB required)

The default baudrate is 1200 . This is set at power-on or after an RI (Reset
Instrument) command.

(not used in 190-series-II)

Response Syntax:

Example: See an example for this command under the QP (QUERY PRINT) command

Notes:

• The Fluke 19x/19xC instruments support 1 stopbit, 8 databits and software
handshake (a.k.a. “X-on X-off protocol”). Hardware handshaking is not supported.

• The 190-series-II has a USB interface. No baudrate setting is required, nor
supported. If the PC command is used nevertheless (with proper parameters),
this will be accepted and ignored and a positive <ackn> given.

<ackn><cr>

description.

R e mo te C on tr o l a n d Pr og r am m i ng Re f e re nc e f or th e F L UK E 19 0 f a mi ly of S c o pe Me t er ® t es t t oo ls

p a ge 2 5