Measurement Computing Personal488 rev.3.0 For DOS & Windows 3.Xi - Manual (Page 66)

II. SOFTWARE GUIDES - 8. Driver488/DRV 8D. Getting Started
Personal488 User’s Manual, Rev. 3.0 II-51
Keyboard Controller Program
The program KBC.EXE is a utility program that allows you to enter Driver488/DRV commands from
the keyboard and see what effect they have. When KBC is run, it displays an IEEE> prompt and waits
for a command to be entered from the keyboard. When the key is pressed, KBC sends the
command to Driver488/DRV and displays any response or error messages that occur. This allows you
to test the various Driver488/DRV commands and their effects on your instruments without having to
write a program. A dialog with
KBC might be:
First, we can use the HELLO command to display the Driver488/DRV revision identification:
IEEE> HELLO
Driver488 Revision X.X ©199X IOtech, Inc.
Then check the Driver488/DRV status:
IEEE> STATUS
CS21 1 I000 000 T0 C0 P0 OK
The following indicators describe each component of the Driver488/DRV status:
Next, take a reading from IEEE 488 bus device 16 :
IEEE> ENTER 16
NDCV=035.679E-3
Now, list the commands that have been executed so far and re-execute the ENTER command:
IEEE> .L
3 HELLO
2 STATUS
1 ENTER 16
IEEE .1
IEEE> ENTER 16
NDCV+032.340E-3
Notice that the .L and .1 commands are not Driver488/DRV commands. Instead, they are supplied by
the KBC program. The .L command is used to show a list of the previously entered commands. KBC
keeps the last 20 commands in this list. Any of these commands can be reentered by typing a period
followed by the number of that command. For example, the
.1 command reenters the last command
that was entered. The user may then edit this command, or may just press re-executing the
command.
Indicator Driver488/DRV Status
C It is in the Controller state.
S It is the System Controller.
21 The value of its IEEE 488 bus address.
1 An Address Change has occurred.
I It is idle (neither a talker nor a listener).
0 There is no ByteIn available.
0 It is not ready to send a ByteOut .
0 Service Request ( SRQ ) is not asserted.
000 There is no outstanding error.
T0 It has not received a bus device TRIGGER command (only applicable in the Peripheral
mode).
C0 It has not received a CLEAR command (only applicable in the Peripheral mode).
P0 No CONTINUE transfer is in progress.
OK The error message is “OK”.