Agilent Technologies E1476A User Manual page 37

 ',0 $ >@
 287387   &/26( #   
 287387   567
 287387   67$7 23(5 (1$% 
 287387   6&$1 # 
 287387   ,1,7
 :+,/( 127 %,7 632//   
 35,17 :$,7,1* )25 6&$1 &203/(7(
 (1' :+,/(
 287387   67$7 23(5"
 (17(5   $
 35,17 67$7 23(5 (9(17 %,7 
 (1'
Exercise 4: Check for
System Errors
36 Getting Started
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com
$
RUN the program. You should hear channel relays opening and closing,
especially when a large channel list is scanned.
You can add the following lines to the program in Exercise 3 to verify that
no system errors were generated. It is always a good idea to check if your
program causes the instrument to report any errors during program
development (such as command strings that are invalid and cause an error
to be sent to the instrument's error queue). You can read the instrument's
error queue by inserting the following four program lines (all errors are read
until the error queue is "+0, No errors").
 5(3($7
 287387   6<67 (55"
 (17(5   $$
A$ gets the
 35,17 $$
 817,/ $ 
See "Using Interrupts With Error Checking" in Chapter 2 for detecting errors
with interrupts. For example, inserting the following (incorrect) program line:
 287387   75,* 6285& %86
will cause an error to be sent to the error queue because 75,* 6285& %86
is an incorrect command header (must be 75,* 6285 %86). The instrument
still functions using the default value 75,* ,00HGLDWH. To know that an error
was reported and your instrument is doing what you intended it to do, you
must read the error register with a 6<67HP (55RU" command.
You can insert this program segment at different places in your program to
see where the error is generated when debugging your program if it cannot
be determined from the error message or by examining the program lines.
In this case, the error is returned as  8QGHILQHG KHDGHU which means
the command header was incorrectly specified. This error is generated by
the instrument driver while trying to parse the command (the error -113 is
documented in the command module manual).
!Dimension array to hold data entered
!Close all channels
!Open all channels by resetting module
!Enable bit 8 of status operation event register
!Scan all channels
!Initiate the scan using the default
!Serial poll bit 7 of the status byte until it is high
!Query the status operation event register
!Bit 8 reported high (status byte bit 7 was high)
!Print response to the
STAT:OPER
!A gets the error number,
!error message
TRIG[:IMM]
query
Chapter 1