Table of Contents
Advertisement
Functional Verification Test
Test Procedure
Corrective Action
Chapter 2
The Functional Verification Test for the E8482A/B RF Multiplexer module
consists of sending the self-test command (
response. This test can be used at any time to verify that the device is
connected properly and is responding to basic commands. However, it does
not ensure module's switching operability.
1. Verify the RF multiplexer module is properly installed in the
mainframe and the mainframe has passed its power-on sequence test.
2. Verify that the computer is properly connected to the mainframe via
GPIB interface.
3. Send the
primary address is 09 and secondary address is 120/8 = 15) from
Agilent VISA Assistant application program.
4. A "+0" returned means no self-test failure, while any non-zero error
code returned indicates a self-test failure. See Table 2-2 below for the
description of self-test error codes.
NOTE
Test failures can be caused by improper cabling,improper selection of the
interface select code, primary, and/or secondary address setting. Verify
proper connection and address selection before troubleshooting. As
required, see Agilent E8482A/B Six/Three 1x4 RF Multiplexer Module
User's Manual for more information on module installation, address
selection, and the related SCPI commands.
An non-zero error code is returned when the module self-test fails. The
meaning of each code is given in Table 2-2. If a self-test failure occurs,
recycle power and repeat the self-test procedure as shown above. If the
problem reoccurs, the module requires to be repaired. Contact Agilent
Technologies for repair and service (see page 10).
a
Error
+0
+ss01
+ss02
+ss03
+ss05
+ss10
+ss11
a. ss = card number (with leading zero deleted, the typical is 1)
command to the RF multiplexer module (GPIB
*TST?
Table 2-2. Self-test Error Codes
Description (probable Causes)
Self-test passes.
Firmware error.
Bus error (problem communicating with the module).
Incorrect ID information in ID register.
Card data register incorrect (hardware and firmware with
different values).
Interrupt expected but not received.
Card busy time incorrect.
) and checking the
*TST?
Verification Tests
19
Advertisement
Table of Contents
