3070 / 79000 Board Test Systems: System Installation Manual (UNIX Version) November 2003

3070 / 79000 Board Test Systems
System Installation Manual (UNIX Version)

November 2003
Contents Agilent 3070 / 79000 System Installation (UNIX
Version)
E4000-90300 Rev. J 11/2003
1 UNIX System Installation Procedure

If You Need Help................................................................................................................... 1-1
Uncrating the System............................................................................................................. 1-1
Testhead IP Address Changes with B.03.80................................................................................ 1-3
Audience and Purpose ........................................................................................................... 1-3
What Does This Mean for Existing Systems Not at B.03.80?............................................... 1-3
How to Make IP Addresses Match ........................................................................................ 1-3
Implications for Custom Applications ................................................................................... 1-4
B.03.80 Update and Ignite Notes........................................................................................... 1-4
Preparation ................................................................................................................................... 1-5
Identifying the System ........................................................................................................... 1-5
Checking for Shipping Damage............................................................................................. 1-5
Verifying that the Shipment is Complete .............................................................................. 1-5
Verifying System Power........................................................................................................ 1-6
Verifying the Site Preparation ............................................................................................... 1-6
Installing Testhead Hardware ...................................................................................................... 1-7
Installing the Monitor, Keyboard, Mouse, Support Arms ..................................................... 1-7
Removing the Testhead Shipping Bolts............................................................................... 1-14
Stabilizing the Testhead....................................................................................................... 1-15
Installing the Strip Printer and Tray .................................................................................... 1-15
Installing the Footswitch...................................................................................................... 1-16
Connecting the Site LAN Cable to the Controller ............................................................... 1-16
Connecting the Compressed Air Supply to the Testhead .................................................... 1-16
Install the Probe and Probe Cradle ...................................................................................... 1-17
Installing the Fixture Pull-Down Label ............................................................................... 1-17
Installing the Serial Label .................................................................................................... 1-18
© Agilent Technologies 1998–2003 i

Table of Contents
Setting Up the Testhead Controller ........................................................................................... 1-19

Planning For the LAN Installation....................................................................................... 1-19
Turning on the PDU............................................................................................................. 1-21
Turning on the Monitor and Controller ............................................................................... 1-21
Setting up the Controller LAN and HP-UX Start-up........................................................... 1-21
Setting Up the Testhead ............................................................................................................. 1-23
Rotating the Testhead ......................................................................................................... 1-23
Cabling the Support Bay to the Testhead (307X System Only) .......................................... 1-23
Installing the Vacuum Manifold .......................................................................................... 1-27
Verifying the Testhead............................................................................................................... 1-28
Booting the Testhead ........................................................................................................... 1-28
Verifying the config File (Pre-Shipped Controllers Only) .................................................. 1-28
Running AutoAdjust All...................................................................................................... 1-29
Running Full Diagnostics .................................................................................................... 1-29
Setting Up and Verifying the Strip Printer .......................................................................... 1-29
Verifying the Vacuum Subsystem ....................................................................................... 1-30
Setting Up Other Hardware ....................................................................................................... 1-34
System Printer / Plotter ........................................................................................................ 1-34
Pay-Per-Use Button Adapter ............................................................................................... 1-34
PR PLUS.............................................................................................................................. 1-39
POTS (Plain Old Telephone Services) Bay......................................................................... 1-41
Instrument Rack ................................................................................................................... 1-41
Setting up the Testhead for Automation .............................................................................. 1-43
EFS Board Handler ............................................................................................................. 1-44
Completing the Installation........................................................................................................ 1-45
Reinstalling the Pod Covers................................................................................................. 1-45
Making a System Recovery Tape ........................................................................................ 1-45
Making a System Backup Tape ........................................................................................... 1-45
Turning System Administration Over to the Customer ....................................................... 1-45
Filling Out the System Support Log .................................................................................... 1-46
Installation Billing Information ........................................................................................... 1-46
© Agilent Technologies 1998–2003 Agilent 3070 / 79000 System Installation (UNIX Version) ii
Table of Contents
2 UNIX System Installation Reference

File System Changes With HP-UX 10.2X (B.03.XX) ................................................................ 2-2
Installing and Reviewing Codewords .......................................................................................... 2-4
The Configuration Files ............................................................................................................... 2-5
The System Config File ......................................................................................................... 2-5
The Standard Config File..................................................................................................... 2-14
The BT-BASIC Editor ............................................................................................................... 2-26
Starting the BT-BASIC Editor............................................................................................. 2-26
Using the BT-BASIC Editor................................................................................................ 2-27
Exiting the BT-BASIC Editor.............................................................................................. 2-28
HP-UX Quick Reference ........................................................................................................... 2-29
vi Editor Quick Reference ......................................................................................................... 2-32
Troubleshooting ......................................................................................................................... 2-35
Switch Settings .................................................................................................................... 2-35
Controller Start-Up Problems .............................................................................................. 2-42
Determining the IP Address................................................................................................. 2-42
Determining the Hardware Address .................................................................................... 2-42
Testhead LAN ..................................................................................................................... 2-42
Manually Setting the Local Time Zone & System Time..................................................... 2-49
Verify the Plan For the LAN Installation ............................................................................ 2-50
Set Up the LAN Software.................................................................................................... 2-50
Test the Network.................................................................................................................. 2-51
Miscellaneous ............................................................................................................................ 2-52
Rotating the Testhead Without PDU Power ........................................................................ 2-52
Moving the Controller to the Right Pod ............................................................................. 2-54
3 UNIX Device Files – C240 and Earlier

Rebuilding Device Files at B.03.81 or Later ............................................................................... 3-2
Process for Rebuilding Device Files...................................................................................... 3-2
Example for Recreating a Device File ................................................................................... 3-2
© Agilent Technologies 1998–2003 Agilent 3070 / 79000 System Installation (UNIX Version) iii
Table of Contents
712/60/100 Controller.................................................................................................................. 3-4

725/50 Controller ......................................................................................................................... 3-8
725/100 Controller ..................................................................................................................... 3-13
C110 Controller ......................................................................................................................... 3-18
B180L Controller ....................................................................................................................... 3-22
C240 Controller ......................................................................................................................... 3-26
4 UNIX Device Files – B2000 and Later

Rebuilding Device Files at B.03.81 or Later ............................................................................... 4-2
Process for Rebuilding Device Files...................................................................................... 4-2
Example for Recreating a Device File ................................................................................... 4-2
B2000 Controller ......................................................................................................................... 4-4
C3600 Controller ......................................................................................................................... 4-8
5 UNIX Controller Cabling Diagrams

712/60/100 Controller.................................................................................................................. 5-2
725/50 Controller ......................................................................................................................... 5-5
725/100 Controller ....................................................................................................................... 5-8
C110 Controller ......................................................................................................................... 5-11
B180L Controller ....................................................................................................................... 5-14
C240 Controller ......................................................................................................................... 5-17
B2000 Controller ....................................................................................................................... 5-20
C3600 Controller ....................................................................................................................... 5-23
© Agilent Technologies 1998–2003 Agilent 3070 / 79000 System Installation (UNIX Version) iv
1 UNIX System Installation Procedure
E4000-90300 Rev. J 11/2003
In this Chapter... ■ Testhead IP Address Changes with B.03.80, 1-3 If You Need Help
■ Preparation, 1-5 If you need help installing the system, contact Agilent’s
■ Installing Testhead Hardware, 1-7 Measurement Systems Knowledge Center (MSKC). In
the U.S. call 1.800.593.6635 with your MSKC support
■ Setting Up the Testhead Controller, 1-19 handle. Outside the U.S. call your local Agilent Service
■ Setting Up the Testhead, 1-23 Representative to access the MSKC. For help with
system administration or LAN problems, call MTD
■ Verifying the Testhead, 1-28
Customer Technical Support at 1.800.447.TEST.
■ Setting Up Other Hardware, 1-34
If you are installing a Test Server, refer to the Agilent
■ Completing the Installation, 1-45 3070 Series 3 / 79000 Family System Administration
Guide (E9900-90000) which is online. If the testhead
includes the optional Agilent Performance Port ACS
This chapter describes the installation of the Agilent (Actuator Control System) for switching compressed air
3070 Series 3 and 79000 board test systems with a to the test fixture, refer to the Agilent Performance Port
UNIX controller. If you are installing a system with a Manual (E3700-90000) for the ACS installation.
MS Windows (PC) controller, use the Agilent 3070
System Installation (WN Version) (E9970-90001). Uncrating the System
NOTE Uncrating the system is the responsibility of the Agilent

customer engineer. After removing the outer cardboard
This system should be installed only by an Agilent box from the system pallet, you will find instructions for
3070 / 79000 service-trained customer engineer uncrating the system attached to the pallet ramp. Use a
(CE) who is familiar with running the Diagnostic cordless electric drill with appropriate sockets and
software and troubleshooting the system. extensions to make the uncrating process go much
quicker.
Tools Needed for Installation

You will also need:
© Agilent Technologies 1998–2003 Agilent 3070 / 79000 System Installation (UNIX Version) 1-1
UNIX System Installation Procedure:
■ T20 Torx driver

■ Diagonal-cutters or scissors to cut straps
■ Utility knife to open boxes
■ BNC-to-dual banana coaxial cable (11001-60001)
— for Diagnostics
■ BNC(F)-to-BNC(F) (barrel) connector
(1250-0080) — for Diagnostics
■ 7/16-inch socket and ratchet — for support bay
uncrating
■ 9/16-inch socket and ratchet with 6-inch extension
— for support bay uncrating
■ Phillips screwdriver
■ 1/4-inch flat blade screwdriver
■ T10 Torx driver
■ 5-mm hex key wrench
■ 10-mm hex key wrench
UNIX System Installation Procedure: Testhead IP Address Changes with B.03.80
NOTE NOTE
Testhead IP This section contains important installation Those who use NIS or DNS for testhead IP
information. Read this before installing the address resolution should be aware that this
Address Changes system. method forces the system to look at local hosts
with B.03.80 first. If these users encounter problems, they
should ensure that the nsswitch.conf file is
Audience and Purpose configured correctly to support their NIS or DNS
Because of the Hewlett-Packard/Agilent Technologies networking implementation.
split, 3070 Board Test systems are no longer shipped
with testhead LAN IP addresses in the 15.3.112.* series. What Does This Mean for Existing Systems Not at
Beginning with systems shipped with B.03.80 software, B.03.80?
and systems updated or ignited with B.03.80 software,
the testhead’s IP addresses will be in the 10.3.112.* Using Local Hosts for Existing Systems
series.
If you have not changed your method of name
This should not cause any networking problems because resolution, and you are using local hosts, you are not
the systems are configured to use local hosts for affected by this change. You can run systems that have
testhead IP address resolution. This is accomplished by the new 10.3.112.* IP address in the same network as
creating a new /etc/nsswitch.conf file or modifying systems with the old 15.3.112.* address without any
an existing /etc/nsswitch.conf file to look at the conflicts.
local /etc/hosts file first when doing testhead IP
address resolution. Using a Nameserver for Existing Systems
If you are using a nameserver for name resolution, we
NOTE
recommend, but do not require, that all IP addresses
You should cycle power on the testhead after match. This means they should all use the 10.3.112.* IP
performing an update or ignite to B.03.80. address convention.
How to Make IP Addresses Match

Change all existing systems to the 10.3.112.* format.
This involves two steps:
UNIX System Installation Procedure: Testhead IP Address Changes with B.03.80
1 Change the IP addresses of each system using the

15.3.112.* format to the new 10.3.112.* format. # Example from /etc/bootptab
Modify the /etc/bootptab, /etc/rc.config.d/ module0:\
netconf, and /etc/hosts files (see B.03.80 ht=ether:\
Update and Ignite Notes below for examples). vm=rfc1048:\
ha=0060B0B215A5:\
2 Update the IP addresses on the nameserver itself. sm=255.255.248.0:\
ip=10.3.112.4
NOTE
Only 3070 testhead IP addresses in the 10.3.112.* # Example from /etc/rc.config.d/netconf
format are supported by Agilent. RARPD=0
IP_ADDRESS[1]=10.3.112.1
SUBNET_MASK[1]=255.255.248.0
Implications for Custom Applications INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=10.3.119.255
If there are any custom applications that are hard-coded LANCONFIG_ARGS[1]=”ether”
to look for a 15.3.112.* address, they must be modified DHCP_ENABLE[1]=0
to look for a 10.3.112.* address. An /etc/nsswitch.conf file will be added to ensure
that the /etc/hosts file is used first for name
B.03.80 Update and Ignite Notes resolution. If the /etc/nsswitch.conf file already
Because B.03.80 software configures the system with exists, it will be modified so that the /etc/hosts file is
testhead IP addresses in the 10.3.112.* series, you used first. An example follows:
should use caution if you use the practice of saving # Example from /etc/nsswitch.conf
critical files and then restoring the files after completing hosts: files [NOTFOUND=continue] dns
a software update or ignite.
If you use this practice, verify that the IP addresses of NOTE
the testhead and all modules in the /etc/bootptab, If you have addresses on your public LAN in the
/etc/rc.config.d/netconf, and /etc/hosts files 10.3.112.* range, and you experience address
are modified to map to the 10.3.112.* addresses. conflicts, contact your Agilent support
representative.
Here are some file examples:
# Example from /etc/hosts
10.3.112.4 module0
UNIX System Installation Procedure: Preparation
Preparation Identifying the System Checking for Shipping Damage

The Agilent 3070 / 79000 system is available with Inspect the system for damage. If you think there has
different types of testheads and controllers. Because of been damage, contact Agilent’s Manufacturing Test
these differences, there are slight variations in the Division, Order Administration (970.679.2261).
installation process.
■ The testhead may have 1-, 2-, or 4-module Verifying that the Shipment is Complete
capacity. Check the contents of all crates and boxes against the
■ The testhead may have one or two pods (only the order form from the customer. Many of the accessories
79000 has two pods; all other testheads have only and miscellaneous items like the strip printer, tape
a right pod) cartridges, licenses, and documentation are shipped in
separate boxes.
■ The testhead may include a VXI cardcage (79000
only). Also check the contents of all bags attached to the rear
of the testhead (you got this manual and a Site
■ The system may include a support bay. Preparation Manual from one of the bags).
■ The vector application rate may be 6, 12, or 20 Bag on the rear of the right pod:
megapatterns per second (MP/s).
■ Pod key
A label on the lower right corner of the testhead’s
cradle, when viewed from the rear, indicates the ■ Probe cradle
Common Testhead Product Number, which defines the ■ Certificates of Calibration
module capacity. Identifying 6-MP/s, 12-MP/s, or
20-MP/s is most efficiently done by reviewing the sales ■ Certificate of the Hardware Address for the
order or the paperwork sent with the system. System Card
■ System Data Sheet
■ Configuration printouts
UNIX System Installation Procedure: Preparation
Bags on the rear of the cradle: Verifying the Site Preparation

■ Vacuum fittings Review the customer’s completed Site Prep Checklist
■ Compressed air fitting from the Agilent 3070 / 79000 Site Preparation Manual.
Ask the customer for a copy of the System Plan
■ Installation kit (03066-69902) with various tools Drawing or have them select the appropriate layout
and parts (parts list included) from Chapter 3 of the Site Preparation Manual. Satisfy
yourself that preparations are complete before
Verifying System Power proceeding.
Use the Agilent 3070 / 79000 Family Site Preparation
Manual (03066-90114) to verify that the system has
been correctly wired to a reliable source of ac power. Do
not turn the system power on until instructed to do so.
NOTE
If you are installing a system that has been moved
from the customer’s original location, you may
need to reconfigure and rewire the system’s power
distribution unit (PDU) for a different mains
power. Refer to the Agilent PDU Upgrade and
Replacement Manual (E4030-90000).
UNIX System Installation Procedure: Installing Testhead Hardware
Installing Testhead Installing the Monitor, Keyboard, Mouse, If you are leaving them on the right side of the testhead,
Support Arms free them, unpack them, and extend the support arms to
Hardware the approximate positions in which they will be used.
The monitor, keyboard, mouse, and support arms may or Then proceed to Adjusting the Support Arms on
may not have already been installed from the factory, so page 1-13.
there are three possible scenarios for installing these
devices: Moving the Monitor, Keyboard, Mouse, Support Arms
■ Scenario A: If they are already installed and the If the customer wants the support arms on the left side
customer likes them on the right side of the of the testhead, move them as described below. The
testhead (the default side), all you have to do is monitor, keyboard and mouse are all connected with
un-secure them. Proceed to Un-securing the extension cables coiled inside the right pod so you can
Monitor, Keyboard, Mouse, Support Arms on move these devices to the left side of the testhead.
page 1-7.
1 Open the pod door (the key is in a bag attached to the
■ Scenario B: If they are already installed but the rear of the pod).
customer wants them on the left side of the
testhead instead of the right side, proceed to 2 Using a T20 Torx driver, remove 5 screws and
Un-securing the Monitor, Keyboard, Mouse, remove the right pod cover. Using a 5-millimeter hex
Support Arms on page 1-7 and then to Moving key wrench, remove two screws and remove the left
the Monitor, Keyboard, Mouse, Support Arms side cradle cover (if the testhead is a 79000 remove
on page 1-7. the left pod cover).
■ Scenario C: If they are not already installed, 3 Disconnect the monitor power supply’s power cord
proceed to Installing the Monitor, Keyboard, and the monitor, keyboard and mouse cables from
Mouse, Support Arms on page 1-9. their extension cables inside the right pod.
Un-securing the Monitor, Keyboard, Mouse,

Support Arms
If you are going to move the monitor, keyboard, mouse
and support arms to the left side of the testhead
(scenario B), don’t unpack them at this time. Just free
them from the testhead.
4 Using a 1/4-inch hex key wrench, remove two screws

that secure the support arm mount (T piece) post in
the right column (Figure 1-1).
Figure 1-1 Moving the support arms to the left side of the testhead
Top View of
Support Arm Mount
Monitor ('T' piece)
(Flat Panel Display)
Monitor Arm
(top and rear)
Keyboard Arm
(bottom and front) Riser under
Monitor Arm
Mouse Keyboard
'T' piece
Cables
Post Screw Holes
Use top and bottom for 307X or 317X,
middle and bottom for 327X or 79000
S3ARM1.WPG
'T' piece post inside column Left side
of testhead
5 Move the support arm mount (T piece) and assembly between the keyboard cable and the keyboard
to the left column. The T piece should protrude from extension cable. Route the bar code scanner cables
the side of the testhead, not the front of the testhead. through the support arm cable troughs.
12 Ensure that all cables are dressed properly, and use
CAUTION cable ties to secure the cables in place.
✸The assembly is awkward to move with the
devices attached, so unless you have help moving
13 Replace the pod or cradle side covers.
it, you should remove all devices from the support 14 Install the square plastic cap in the top of the right
arm trays before moving the support arm support arm column.
assembly.
15 Place the plastic keyboard overlay (E4000-84404) on
the keyboard.
6 Reinstall the two screws in the support arm post in 16 Proceed toAdjusting the Support Arms on
the left column. Position the support arm mount (T page 1-13.
piece) so it extends to the left or to the front from the
testhead. For 307X and 317X testheads, use the top Installing the Monitor, Keyboard, Mouse, Support Arms
and bottom screw holes; for 327X and 79000
testheads, use the middle and bottom screw holes. If the monitor, keyboard, mouse and support arms are
not already installed on the testhead, perform the
7 Switch the support arm locations on the T piece so following steps.
that the monitor support arm with the riser is in the
rear hole, farthest from the operator position. 1 Determine which side of the testhead the customer
wants the support arms located.
8 Replace the monitor, keyboard and mouse on the
support arm trays if you removed them. a If it’s the right side (the default), open the right
pod door (the key is in a bag attached to the rear of
9 Reroute the monitor, keyboard and mouse extension the pod).
cables from the right pod, across the rear cable
trough, to the left side of the testhead. b If it’s on the left side, remove the right pod cover,
but also remove the left side cradle cover (use a
10 Reconnect the cables to the extension cables in the 5-millimeter hex key wrench).
left side of the cradle (or the left pod if it is a 79000
testhead). 2 Unpack the support arms and the monitor and
keyboard trays (see Figure 1-2 on page 1-11 for the
11 If the system includes an optional bar code scanner, following steps).
connect the bar code scanner cable (8120-6751)
3 Insert the post of the support arm mount (T piece, blade screwdriver, tighten the two hold-down screws
E9900-10245) in the column. Position the support over the rear edge of the monitor base (Figure 20 on
arm mount so it extends to the right or left or to the page 1-12).
front from the testhead. Secure the post in the column
10 Unpack the keyboard and mouse and place them on
using a 1/4-inch hex key wrench and two each cap
the keyboard tray.
screws (3030-1044) and lock washers (2190-0963).
For 307X and 317X testheads, use the top and 11 Using diagonal cutters, cut the cable ties to free the
bottom screw holes; for 327X and 79000 testheads, cables in the right pod.
use the middle and bottom screw holes.
12 If the support arms are on the left side of the testhead,
4 Insert the extension (riser, E9900-10246) in the hole route the power cord and the keyboard and mouse
of the T piece that is farthest from the operator. extension cables through the cable trough across the
rear of the testhead cradle, and up the left side of the
5 Insert the monitor support arm (E9900-10250) in the
testhead to the support arms.
riser.
13 Route the cables through the cable troughs on the
6 Install the monitor tray (E9900-10260) on the
support arms. If the cable troughs are not
monitor support arm using a Phillips screwdriver and
pre-installed on the support arms, install them as
four flat-head screws (3030-0219, in the end of the
shown in Figure 1-2 on page 1-11 (note the lengths:
arm).
S=short, M=medium, L=long).
7 Insert the keyboard support arm (E9900-10248) in
the other hole in the T piece.
8 Install the keyboard tray (E9900-10247) on the
keyboard support arm using a Phillips screwdriver
and four flat-head screws (3030-0219, in the end of
the arm). Position the tray on the arm so that it is
centered front-to-back; this will help keep the tray
from tilting unexpectedly if you lean on the front
edge. If a bracket (E9900-10261) is provided, install
it between the tray and arm; otherwise choose a set of
holes in the tray for centering.
9 Unpack the monitor and mount it on the monitor tray.
Position the front edge of the monitor base under the
front edge of the monitor tray. Using a 1/4-inch flat
Figure 1-2 Installing the support arms
Arm Tension Top View

Adjustments Monitor
(1/4-inch hex) (Flat Panel Display)
Monitor Arm
Keyboard Arm on top
Riser under
Monitor Arm on bottom
L
M
Support Arm Mount Keyboard Mouse
('T' piece)
L M
S
Keyboard Tray
Cables Troughs Tilt Adjustment
Short, Medium, Long
Post Screw Holes
Use top and bottom for 307X or 317X,
middle and bottom for 327X or 79000
S3ARM2.WPG
Right Pod 'T' piece post inside column
14 Remove cover from the rear of the monitor (flat 15 Connect the monitor, keyboard, and mouse cables to
panel display) and connect the power cable and the extension cables.
signal cable (Figure 1-3 on page 1-12). Connect the
monitor power cord from the monitor power supply.
Replace the cover.
16 If the system includes an optional bar code scanner,

connect the bar code scanner cable (8120-6751)
between the keyboard cable and the keyboard
extension cable. Route the bar code scanner cables
through the cable troughs on the support arm.
17 Ensure that all cables are dressed properly, and use
cable ties to secure the cables in place.
18 Install the square plastic cap in the top of the unused
support arm column.
19 Place the plastic keyboard overlay (E4000-84404) on
the keyboard.
Figure 1-3 Mounting and cabling the monitor
Cover
Monitor hold-
down screws
FPDCABLE.WPG
20 Proceed to Adjusting the Support Arms on

page 1-13.
Adjusting the Support Arms

There are two types of support arm adjustments: vertical
and horizontal (see Figure 1-4 on page 1-14).
Using a 1/4-inch hex key wrench, adjust the monitor and
keyboard support arm vertical tension adjustments so
that it requires approximately equal force to move them
up or down. Move them to various positions as you
adjust them. Turning the adjustment clockwise makes it
easier to lower the arm, and counterclockwise makes it
easier to raise the arm (you may have to turn these
screws several turns; they are approximately 48 turns
stop-to-stop).
Also use the 1/16-inch hex key wrench to adjust the
joints in the support arms so they don’t move too freely
horizontally. The hex key wrench is in a bag with the
support arm screws on the keyboard tray box.
Figure 1-4 Ajusting the support arms
Arm Vertical Tension Monitor

Adjustments (Flat Panel Display)
(1/4-inch hex)
Keyboard Mouse
Keyboard Tray
Arm Horizontal Tilt Adjustment
Adjustments (knob)
(1/16-inch hex)
S3ARM3.WPG
Right Pod
Removing the Testhead Shipping Bolts brackets are under each side of the rear of the testhead
(see Figure 1-5 on page 1-15). These bolts hold the
Using a 5/16-inch hex key wrench (in the bag attached system in the zero-degree position during shipment.
to the rear of the testhead), remove the two shipping Screw the bolts into the threaded holes below the
bolts from the cradle. The shipping bolts and shipping shipping brackets to save them for future shipping use.
Stabilizing the Testhead 5 Locate the strip printer cable coiled under the rear of
the testhead cradle (Figure 1-5). Connect it to the
It is important to stabilize the testhead to keep it from strip printer.
moving around. This is especially true if the testhead is
in an automated production line. Using a 3/4-inch Figure 1-5 Locating the strip printer cable (NOTE: The
wrench (in the bag attached to the rear of the testhead), power cord will not be present on most
screw the testhead’s four leveling feet down to the floor systems)
(see Figure 1-6 on page 1-16). If you cannot get the
wrench on the hex nut on a leveling foot, remove the pod
cover to access the threaded screw shaft of the leveling Strip Printer Cable coiled under
foot and use a 1/4-inch wrench in the top of the foot to rear of testhead
screw it down enough to expose the 3/4-inch hex nut.
Bags of manuals
Installing the Strip Printer and Tray and parts
1 For a 3070 Series 3 system, unpack the strip printer

tray and install it in the left column of the testhead
(you may have to pry a plastic cover out of the top of
the column first). If you installed the monitor and
keyboard support arm on the left side of the testhead,
install the strip printer tray in the right column. The CABLES4A.WPG
79000 system does not include a strip printer tray.

Shipping Bolt and Bracket Rear Cable Trough
2 For a 3070 Series 3 system, unpack the strip printer
and place it on the strip printer tray. For a 79000
system, place the strip printer on top of either pod.
3 Refer to the manual accompanying the strip printer to
remove the shipping materials from inside the printer
and to install the paper and ribbon cassette.
4 Route the hooded-connector power cord (8120-1763)
through the hole in the rear of the pod cover (next to
the PDU) and plug the cable into one of the
un-switched outlets on the PDU. Plug the other end
into the strip printer.
Installing the Footswitch system printer and other LAN devices. The system
comes equipped to connect to a ThinLAN coaxial cable.
The BNC connector of an Agilent 28641B ThinLAN
NOTE
Transceiver protrudes from the rear of the controller
With software revision 3070 05.20p and later, the pod, where it is terminated with a BNC T and two
footswitch must be connected to the system. The 50-ohm loads.1
footswitch must be pressed to lock fixtures on the
testhead. If you do not want to connect the controller to the site
LAN at this time, leave the two 50-ohm loads on the
BNC T. If you want to connect to the site LAN, remove
Locate the footswitch and cable as shown in Figure 1-6. the loads and connect both ports of the BNC T to
Place the footswitch on the floor in front of the testhead. 50-ohm coaxial cables going to the site LAN. Keep the
insulator (1252-1650) over the BNC T.
Figure 1-6 Locating the footswitch and leveling foot
If you want to connect to an EtherTwist or other LAN,
remove the ThinLAN Transceiver, and connect to the
LAN ports on the rear of the controller as appropriate.
Connecting the Compressed Air Supply to the

Testhead
The system includes a male quick-disconnect air fitting
on the rear of the testhead for connecting the
compressed air supply. A female quick-disconnect
fitting is provided in a bag on the rear of the testhead. If
Footswitch Cable coiled Testhead Leveling Foot the customer’s existing compressed air hose has the
under front of testhead wrong fitting to mate with the testhead’s fitting, the
customer can remove the fitting from their air hose and
install the female fitting that is included with the system.
Connecting the Site LAN Cable to the Controller The air supply must be connected before you can test
and verify the system.
You do not have to connect the system to the customer’s
site LAN to complete the installation, but it is desirable
to do so to verify that you can communicate with a
1 Part numbers: BNC T (1250-0781); 50-ohm load (1250-0207).
Install the Probe and Probe Cradle Figure 1-7 Probe cradle (E9900-66400)
The probe cradle (Figure 1-7) is located on the left pod

cover of testhead as shipped from the factory. If the
customer wants the probe in a different location, an
extra strip of sticky-backed hook-and-loop fastener is
provided with the system so you can re-locate the probe
cradle.
WARNING
✸Do not place the probe cradle where it could

interfere with an overhanging test fixture, thereby
presenting a pinch hazard between the fixture and
the probe cradle.
Do not place the probe cradle where it could
interfere with testhead rotation.
1 Peel the backing paper off the hook-and-loop

fastener and affix the fastener where the customer
want is (see the Warning above). Installing the Fixture Pull-Down Label
2 Move the probe cradle to the new location: If you are installing the system in an English-speaking
a Rotate the cradle sideways to separate the country, skip this step and proceed to Setting Up the
fastener. Testhead Controller on page 1-19. If you are installing
the system in a non-English-speaking country, locate the
b Press the probe cradle firmly onto the packet of Fixture Pull-down Air Labels (E4000-84410).
hook-and-loop fastener you just installed. Choose the label that is of the correct language for your
Unpack the probe and insert it in the probe cradle. location and apply it over the English text that is
silk-screened on the rear of the testhead near the
compressed air connectors.
Installing the Serial Label

For customers who comply with the European
Community Machinery Directive, locate the serial label
(E9900-84303) and attach the label to the system as
explained in the instructions that accompany the label.
Figure 1-8 Serial label
Agilent Technologies
Manufacturing Test Div.
815 14th Street, SW
Loveland, CO. 80537 EXXXXA
TESTHEAD
USA S/N USXXXXXXXX
Made in USA of
Domestic and Foreign Parts
MFG:
9 2000 9 2002 9 2004
9 2001 9 2003 9 2005
UNIX System Installation Procedure: Setting Up the Testhead Controller
Setting Up the Planning For the LAN Installation at all, the first two items in the table are still necessary
for system set-up. In case of problems, see
Testhead Controller Before turning on the controller, fill out Table 1-1 Troubleshooting on page 2-35. Also he;pful is
below. You will need the assistance of the system’s Administering Agilent 3070 UNIX Systems (UNIX 10.X)
network administrator (or system manager). This is vital shipped both in paper and in the online documentation.
information you will need to set up the system for
networking. Some of the information may not be needed Be sure to read Testhead IP Address Changes with
depending on how your networking is implemented. B.03.80 on page 1-3.
Even if you don’t intend to put the system on a network
Table 1-1 LAN configuration information
Item Your Specific System Information Description

System Hostname The alphanumeric name by which your
system will be known on the network.
Internet (IP) Address Also called the IP address; obtain from
your network administrator.
Will you configure ❏ Yes DNS, also known as BIND, stands for
DNS? ❏ No Domain Name Service. If your network
uses DNS and has a DNS server, you will
configure DNS.
Will you configure NIS? ❏ Yes If your network uses NIS, you will
❏ No configure NIS.
If you answered NO to the two questions above, you do not need to fill out the information in the rest of the table
below.
Subnetwork Mask This number masks (ignores) information
that is not specific to your local network.
Get this number from your network
administrator.
Table 1-1 LAN configuration information (continued)
Item Your Specific System Information Description

Gateway Host Name Typically, the same hostname as the
system you are configuring. If you need to
go outside the subnet, this system would
like to know how to route outside the
subnet. If you do not have a designated
machine for this, use the name and IP
address of the system you are setting up.
Gateway IP Address Also called the IP address. Obtain this
number, specific to the gateway system,
from your network administrator.
Local Domain Name Your company’s domain name. Get this
number from your network administrator.
DNS Server Host Name Your local network’s DNS server. This is
the system on your network that resolves
local hostnames into IP addresses for
networking software.
DNS Server IP Address Also called the IP address. Obtain this
number, specific to the DNS server
system, from your network administrator.
NIS Domain Name
Turning on the PDU Setting up the Controller LAN and HP-UX Start-up
The Agilent E1135C PDU has two switches. During the boot process, the system will enter its
Start-up routine. It will ask you for the information that
1 Rotate the large, red, rotary switch1 to the On (1)
you recorded in Table 1-1 on page 1-19.
position. This switch should be left on at all times
unless someone is working inside the PDU. 1 Required Information — When you see:
2 Switch the green rocker switch to the On (1) position. Do you wish to continue?
This is the switch to use for switching testhead power
Click Yes, Continue. Again, you must have Table 1-1
on and off.
completed.
After switching both switches on, you should hear the
2 System Hostname — When you see:
testhead fans come on.
Hostname:____________
Turning on the Monitor and Controller Type the hostname (system name) and click OK. You
First, switch on the monitor (the power switch is located will be asked to confirm your answer.
on the right side of the monitor). Then open the right 3 Time Zone — Select your time zone and click OK.
pod door and switch on the computer. This sequencing You will be asked to confirm your answer.
is done so you will not miss any boot messages that
appear on the monitor. 4 <Region> Time Zone — Select your region time
zone and click OK.
DO NOT touch the keyboard. After several minutes,
you should see boot messages on the screen. In the Set 5 Confirm Date and Time — You will be asked to
System Parameters window, you should see: confirm the date and time.
Are you ready to link this system to a 6 Root Password — When you see:
network?
Do you want to set the root password at this time?
Click Yes and proceed to Setting up the Controller
LAN and HP-UX Start-up. Click No. The system administrator can assign the
root password later.
1 This Mains Disconnect Switch is for compliance with the European Community (EC) Machinery Directive. The ac mains for the system
is wired directly to this switch. It can be locked in the Off position where it disconnects the ac mains from the rest of the PDU.
7 Internet Address — When you see: If the messages ARE NOT OK, troubleshoot as
necessary; see Controller Start-Up Problems on
Internet Address:____________
page 2-42.
Get the address from the customer, type the IP
If the messages ARE OK, proceed to Setting Up the
address, and click OK. You will be asked to confirm
Testhead on page 1-23.
your answer. Do not use a dummy address.
8 Additional Network Parameters — When you see:
Do you want to configure these additional network
parameters?
Click No. After completing the system installation,
you should remind the customer’s system
administrator to configure DNS or NIS.
9 Configure Font Server — If you have X-terminals
logging into this system, you will want to configure
the font server, and you should click Yes. This will
use over 1 MB of disk space and run the font server
daemon. If no X-terminals will be logging into this
system, click No.
10 Unallocated Disk Space — This is an informational
dialog box letting you know your unallocated disk
space. Click Close.
11 System Parameters — This is an informational dialog
box letting you know your system parameters. Click
Close.
You will then see lots of HP-UX Start-up messages and
system test results.
After about one minute, you will see the CDE Login
Screen.
UNIX System Installation Procedure: Setting Up the Testhead
Setting Up the Rotating the Testhead Cabling the Support Bay to the Testhead (307X
Testhead System Only)
WARNING
If you are installing an Agilent 307X testhead with a
✸ Remove all objects, including the monitor/keyboard
support arms, from the rotation path of the
support bay, follow the procedures below. If you are
installing any other type of system, which has no
testhead. Should the testhead hit a support arm, support bay, skip this entire section and proceed to
damage could result. Booting the Testhead on page 1-28.
Open the right pod door and rotate the testhead by NOTE
pressing the rocker switch inside the pod. Rotate the This information also applies to installing an
testhead to the service position. The PDU must be E2197A xDSL/POTS Bay. If you are installing an
turned on in order to rotate the testhead. xDSL/POTs bay, also see POTS (Plain Old
Telephone Services) Bay on page 1-41.
NOTE
If power has not been connected to the testhead, In this section you will route the module umbilical
you can still rotate the testhead by plugging the cables directly through the door of their respective
testhead rotation motor into 110 volts or 220 volts modules (the cables no longer pass through a cable
ac power. See Rotating the Testhead Without clamp panel in the testhead). The umbilical cable
PDU Power on page 2-52. includes the DUT power supply cables, the triaxial
functional port cables, and the PDU branch control
wires.
In addition to the umbilical cables, you may also have to
route AccessPlus cables, GPIB cables, and power cords,
depending on what hardware is used in your system.
Refer to the following paragraphs and Figure 1-9 on
page 1-25 for the cable installation procedures.
Umbilical Cable with DUT Power Supply and Functional

Cables
1 Remove the module door locking bracket.
2 Locate the two access plates on a module door. Use a
T20 Torx driver to loosen the plate covering the
smaller hole and turn the plate around to expose the
hole. The smaller hole is for the umbilical cable; the
larger hole is for the AccessPlus cables.
3 With the module door open, connect the DUT power
supply connectors to the ASRU Card. Also be sure to
connect the ground wire to the ground lug on the side
wall of the module.
Figure 1-9 Cabling to the support bay (rear view)
Module Door Locking Bracket Vacuum Manifold
Support Bay
Module 0 Module 2
Module 1 Module 3
Module Umbilical
Cables
HP-IB Route the PDU Branch Control Cable Clamp Panel

Cable Black / White Wire Pair through Aux Aux Aux Aux Aux Aux
the cutout in the bottom panel.
SUP_BAY2.WPG
1 0 Aux Aux 2 3
4 Connect the white triaxial cable to the functional

ports as shown in Figure 1-10.
Figure 1-10 ASRU card connections (rear view)
Supplies 1-4
Supplies 5-6
Functional Ports
03066-66532 ASRU Card

White band
ASRU_CON.WPG Red band
PDU Branch Control Wires AccessPlus Cables

This applies only to 1-phase or 2-phase systems with a If the system includes AccessPlus cables, route them
PDU in the support bay. through the other (unused) hole in the module door (see
Figure 1-9 on page 1-25).
Every module umbilical cable has a black / white wire
pair, but only module umbilical cable going to the
GPIB Cable
bottom DUT supply has a wire pair that is connected to
the PDU. Note the module number on that module Connect the GPIB cable from the support bay to the
umbilical cable. GPIB connector on the GPIB card in the controller in
the controller bay pod of the testhead.
At the testhead end of the module umbilical, connect the
plug to J566, the PDU Branch Control connector.
Remove the bottom panel and route the wires through NOTE
the cutout in the panel (see Figure 1-9 on page 1-25). Do not connect the GPIB cable to the GPIB port
Coil and secure the branch control wires of the unused on the System Card.
umbilical cables.
Support Bay Power Cords

This applies only to 3-phase systems with no PDU in the
support bay.
Connect two power cords from the two power strips in
the rear of the support bay to the PDU in the testhead.
Route the power cords through the Auxiliary clamps in
the cable clamp panel in the rear of the support bay (see
Figure 1-9 on page 1-25).
Installing the Vacuum Manifold

Install the vacuum manifold on the rear of the testhead,
on the vacuum ports, as shown in Figure 1-9 on
page 1-25.
UNIX System Installation Procedure: Verifying the Testhead
Verifying the Booting the Testhead are two conditions that will require you to verify the
config files:
Testhead Log in as service1.
■ If the testhead controller was pre-shipped to the
Boot the testhead using the Testhead Functs and customer ahead of the testhead.
Testhead Power On function keys. Watch the LEDs on
the System Card during the boot process for problems ■ If the customer wants the testhead cards installed
and review the screen for boot error messages.1 in a certain configuration that is different from the
way in which they were shipped from the factory.
Booting takes about two minutes. The testhead LAN has
been configured with the correct hardware addresses at The official system config file (/var/hp3070/
the factory. If any error messages appear, see diagnostics/th1/config) and the standard config file
Troubleshooting on page 2-35. (/var/hp3070/standard/config) were set up and
compiled at the factory. Codewords for all software
NOTE products ordered with the system were also set up at the
factory.
The first time the system is booted with the new
controller, there will be several Warning - Standard If the controller was shipped before the testhead, the
calibration tables not loaded for Module X Slot X config files will not be set up for your testhead. You will
messages. These warning messages are normal; need to set up and compile the config files and enter the
they are generated because there are no valid codewords for your system. The config files will not
AutoAdjust tables in the /var/hp3070/ compile unless the codewords are correct.
diagnostics/th1/cal_B subdirectory. These If you want to verify that the config files are correct,
messages will go away when you run AutoAdjust compare the system configuration printout (in the bag
later. attached to the rear of the testhead) to the official
system config file. From a service1 login, press F2
(Shell) to invoke an HP-UX shell window. At the shell
Verifying the config File (Pre-Shipped Controllers
prompt ($) type:
Only)
more config
Normally, you can skip this section and proceed to
Ask the customer’s system administrator if there is a
Running AutoAdjust All on page 1-29. However, there
plan for card location. If a card configuration plan
1 See the 3070 / 79000 Repair I Manual (E4000-90160), Chapter 1A, "How to Power-up and Boot the Testhead."
exists, and it differs from the actual1 system Setting Up and Verifying the Strip Printer
configuration shipped from the factory, change the
location of the cards to match the plan. Note any change If you have not already done so, remove the shipping
in card locations and edit the official system config file material from the printer and install the paper roll and
accordingly; see The Configuration Files on page 2-5. print ribbon cassette in the printer according to the
instructions with the printer. Then verify the printer as
Running AutoAdjust All follows:
1 Run the printer’s self-test according to the manual
NOTE that came with the printer to verify that it prints well.
Allow the testhead to warm up for 30 minutes 2 Verify communication with the printer: Log in as
before running AutoAdjust. If the testhead user1.
temperature is not allowed to stabilize, you may
3 Open a BT-BASIC window and type:
get Diagnostics failures later.
report is /dev/rpr1
report "This is a test"
After the testhead has warmed up for at least
30 minutes, run AutoAdjust All (press function key F6 The printer should print the message This is a
in the AutoAdjust menu). Verify that there are no errors. test.
4 Exit the system: click on the Exit icon in the low right
Running Full Diagnostics corner of the screen and then click on the Yes button.
Put a pin verification fixture on the testhead, enable
manual intervention,2 and run Full Diagnostics. Verify
that there are no errors.
1 The Actual Config function key (F4) polls the cards in the testhead to identify their type.
2 From the Service Package - Level 1 menu, select Config and then DGN Config. Change Manual Intervention to Yes (press Next Value). Do
not press Save Config as that will make this permanent. Press Exit to run manual intervention this one time only. Refer to the 3070 / 79000
Repair I Manual, Chapter 2, for more information.
1 Look at the vacuum hardware on the testhead and

NOTE note the following:
If the testhead is being used with convention
■ How many solenoids are being used to control
vacuum fixtures, proceed to Verifying the
vacuum
Vacuum Subsystem on page 1-30. If the testhead
is being used in an automation environment, ■ Which Auxiliary ports are being used to control
proceed to Setting up the Testhead for which solenoids
Automation on page 1-43.
■ Which solenoids have hoses to which vacuum
ports (if external solenoids are used)
Verifying the Vacuum Subsystem 2 With the testhead booted, look at the system config
file (/var/hp3070/diagnostics/th1/ config) and verify
The Agilent 3070 Series 3 testheads may or may not
that the relay <r> controls vacuum <m>
have internal vacuum solenoids (valves); they are
statement(s) agrees with the hardware:
optional. All 327X (one-module) and 79000 testheads
always have at least one internal vacuum solenoid; two ■ r = 1 for Aux 1; 2 for Aux 2; 3 for Aux 3, 4 for
solenoids are optional in these testheads. Aux 4; 5 for Aux 5
It is the customer’s responsibility to connect the vacuum ■ m = the module vacuum port(s) connected (can be
solenoid control wires to the System Card unless the 0; 1; 2; 3; 0,1; 2,3; 0-3)
system was purchased with internal solenoids, in which
3 From a BT-BASIC window, take control of the
case the solenoids are wired in the factory. The internal
testhead; type:
vacuum system and wiring are shown in see Figure 1-11
on page 1-32. testhead is 1
To verify the operation of the vacuum subsystem, 4 Execute a vacuum well... statement; type:
perform the steps below. If a vacuum source and vacuum well a is <m>
solenoids are connected, you can turn vacuum on and
off and listen for the sound of the air at the testhead’s The vacuum well is normally defined in the testplan.
vacuum ports. If a vacuum source and solenoids are not For this test, use a. Ensure that <m> = a valid module
connected, you can use a voltmeter to verify that 24 volt vacuum port noted in step 2.
dc can be switched to all terminal pairs of the Auxiliary
connector (J3) on the System Card (Figure 1-11 on
page 1-32).
The vacuum ports are where the vacuum manifold or

— if the vacuum manifold is not used — the external
vacuum hoses are connected. The vacuum outlets
are where the vacuum connects to the test fixture on
top of the testhead. Agilent 317X, 327X and 79000
testheads have only two vacuum ports. On the 327X
and 79000 testheads, ports 2 and 3 are reversed from
the orientation shown in Figure 1-11.
Figure 1-11 Internal vacuum solenoids in a 4-module series 3 testhead
80-PSI Regulator Vacuum Valve

System Card 03066-67911 E3770-67900
Relay 1 +_ 1
2
Port1 Port3
Relay 2 +_ 3
4 Port0 Port2
Relay 3 +_ 5
6
Relay 4 +
+ 1
7
_
2
_
+ 3
_
4
+ 5
8
_
6
+ 7
_
8
Relay 5 + 9
+
_
9
10
0ut
_
11
In
12
10
Remote 11
Shutdown 12
Air Lines E9900-63200
Jumper 4-Module Manifold
E9946A Vacuum components shown above the dotted line
Vacuum components below the dotted line are customer

supplied
Vacuum
Source
Pressure Gage
Manual Cut-off Valve 2-inch Vacuum Hose vac4_S3new.wpg
5 Verify that you can switch vacuum on and off; type:

faon
faoff
If the vacuum control doesn’t work, check:1

■ 24 volts dc present on the Auxiliary port when it is
switched on2
■ Defective solenoid
■ Vacuum source not turned on
■ Compressed air supply not turned on (air-piloted
solenoids only)
If you have other optional hardware to install, find it in
the Table of Contents of Chapter 2 under "Setting Up
Other Hardware," which will direct you to the
appropriate installation instructions. If you do not have
any optional hardware to install, proceed to Completing
the Installation on page 1-45.
1 For additional troubleshooting information, see Chapter 1G, "Troubleshooting Fixture Pull-down and Vacuum," in the 3070 Repair I
Manual (E4000-90160).
2 If the supply is defective or overloaded, it may have folded back when the port relay was closed.
UNIX System Installation Procedure: Setting Up Other Hardware
Setting Up Other System Printer / Plotter

Hardware To install a LAN-based system printer or plotter, use
SAM. The customer’s system administrator or LAN
manager will provide the device’s name and IP address.
Pay-Per-Use Button Adapter

If you are installing a Pay-Per-Use system, and you have
moved the controller from its default location, you must
reinstall the button hardware in the same pod as the
controller. Mount the button adapter on the bottom
hinge of the controller pod as shown in Figure 1-12.
Connect the shielded RJ-45 cable (8120-6773) with a
DB-9 adapter (E9970-63200) to port 1 on the E3788
SCSI-MUX box.
Figure 1-12 Pay-Per-Use button adapter hardware in the left pod
Right Pod, cover removed

Dual Button
Holder with
cable 1st PPU Button
1252-8421
2nd PPU Button
PPU DB9
Button Digi MUX Box
Adapter Port 1
0960-2134
8120-6773 Cable
RJ45-DB9
Adapter
E9970-63201
Installing and Removing Test Credit Buttons botton holder. Save the packaging material until you are
certain that the button is working correctly.
Agilent E3995A test credit button(s) will need to be
installed as shown in Figure 1-13. One 50k test credit To remove a test credit button, grasp the button by its
button is included with the Pay-Per-Use system. It is flange and pull it straight out of the button holder. To
packaged in a 3-inch by 1.5-inch box inside a plastic bag remove the button holder cable from the button adapter,
containing installation instructions. Agilent test credit deflect one of the retaining latches with your fingernail,
buttons may be inserted while the system is running. To a pen, or similar instrument. The button connector will
insert a button, grasp it with the flange or labeled side pop up for removal.
up. Push the button firmly into one of the ports of the
Figure 1-13 Installing Pay-Per-Use buttons
Dual Buttons Holder PPU Buttons

with cable
PPU1HH.WPG
Insert Button Connector

Rel ease
Button Adapter
Verifying the Test Credit Buttons

From a service1 login, run a report1 that tests the test
credit buttons: Move the mouse pointer out of all
windows, click and hold the right mouse button, drag
the mouse pointer down to highlight the Test Credit Data,
then select Pay-Per-Use Utilities. A report, shown in
Figure 1-14, will be displayed in a new window. Verify
that the button label and the button balance are correct
for the number of buttons installed.2 Buttons are
identified by the button label number on the button.
1 From the HP-UX shell, type /opt/hp3070/bin/ppb_report.

2 The E3994A 10k Test Credit Button may also be used and would indicate 10,000 credits.
Figure 1-14 Pay-Per-Use report
PR PLUS Editing the /etc/inittab File for the Terminal
This procedure describes how to enable Agilent PR 1 Log in as root.

PLUS paperless repair software on the Agilent 3070 / 2 Edit the /etc/inittab file as follows:
79000 controller (with software revision B.03.00 or
later) and setup the hardware. For more information Find the commented line that corresponds to the port
about PR PLUS, see the 3070 Series 3 / 79000 Family to which you connected the terminal, and
System Administration Guide (E9900-90000) un-comment it by removing the # character from the
beginning of the line. For example, if the terminal is
Connecting the Terminal connected to port 4, un-comment:
Connect the terminal to a port on the E3788 SCSI-MUX #tm4:234:respawn:/usr/sbin/getty -h ttym04

H # scsi port box, 4th port 9600 baud
box (from the controller). Use a 4-meter RJ-45 cable
(8120-6773) and a DCE adapter (E4000-62106) to 3 Re-save the file.
connect to the terminal cable. While any of the eight
4 Re-initialize the init process to read the
ports on the MUX box can be used, ports 4 through 8 are
/etc/inittab file; type:
the primary ports for terminals; ports 1 through three are
primarily used for other devices. Remove the controller /sbin/init q
pod cover to access the MUX box. The terminal should now display a login prompt.
Configuring the Terminal Installing the PR PLUS Codeword
■ 8-bit characters You must install the PR PLUS codeword on every
■ No parity system running PR PLUS software. A separate license
and codeword is required for each system. Concerning a
■ XON/XOFF PR PLUS system:
■ 9600 baud ■ Boards will be homed on that system (their
■ Block mode OFF databases are stored there)
■ PR PLUS terminals are connected to that system
■ Either the prplus program or the prsetup
program will be run from that system
1 Log in as root and run preupdate; type:
/var/adm/sw/products/HP307X/HP3070SU/preupdate
2 Enter the codeword exactly as it appears on the Running the alarm Daemon
license.
The alarm daemon must be running on each PR PLUS
system that is used to home boards. This daemon is
Setting up the 8-User HP-UX License
automatically started during system boot.
The PR PLUS license includes an 8-user license.
To see whether the alarm daemon is running, type:
Because the standard 3070 / 79000 software is setup
with a 2-user license, you must setup the 8-user license ps -fu hp3070
to allow simultaneous access at the attached terminals This command also verifies that the translogd
and system console. With a 2-user license the console program is running. If either daemon is not running, you
acts as one user, and the network, if attached, acts as the can manually start the alarm daemon. It must be run
second. Although any attached terminal on a 2-user with the proper values set for environment variables
system may show a login prompt, no login attempt will PATH and NLSPATH. From root, type:
succeed as long as someone is logged in at the console.
env
To set up the 8-user license, you must reload software. NLSPATH=/opt/hp3070/lib/nls/american/%N.cat \
Follow the directions in the Agilent B.03.0X Software PATH=$PATH:/usr/hp3070/bin \
Reloading Procedure (E9900-96000) that came with the nice alarm
system. After alarm is running on all PR PLUS systems, verify
the flow of log data among networked systems by
Setting Up PR PLUS running the Network Verify function in the prsetup
Unless you are already familiar with the prsetup program. The expected results are described in the
program, you will need to read the online PR PLUS online documentation.
documentation.1 From the console window, type:
su - prsetup
Although you can do a Network Verify function (as

described in the online documentation), no results will
be seen until the alarm daemon is running on each
PR PLUS system. Proceed to Running the alarm
Daemon below.
1 Click on the arrow above the Bookshelf icon. Then click on Agilent 3070 Online Manuals. From the Bookshelf menu, click on
Information Management and then Agilent PR PLUS. See "Using the Setup Program" in the table of contents.
POTS (Plain Old Telephone Services) Bay
To install a POTS bay, refer to the E2197A xDSL and
E1085A POTS Bay Installation and Upgrade Manual
(E1085-90000).
CAUTION
✸When adding a POTS bay to the system, the GPIB

cables must be connected as shown in Figure
1-15 on page 1-42. If they are not connected
correctly, the system may experience GPIB
timeout errors.
Instrument Rack
Connect the GPIB cables to the instrument rack as
shown in Figure 1-15 on page 1-42. The DUT power
supplies must be the farthest items from the controller,1
and the GPIB cabling must form a continuous loop. In
the case of the 79000 testhead, the VXI mainframe in
the testhead must be between the controller and the
DUT power supplies.
1 The DUT supplies handshake faster than most other devices on the bus. If they are cabled directly to the controller, the glitches they
generate can cause GPIB timeout errors.
Figure 1-15 Connecting the GPIB cables to a POTS bay or instrument rack
POTS Bay or
Instrument Rack Controller External Instruments
in the Support Bay or
VXI
Testhead
Mainframe
Instrument 1 DUT Supplies in the
Support Bay or
Instrument 2 NO Testhead
POTS Bay or
Instrument Rack Controller External Instruments
in the Support Bay or
Testhead
VXI
Mainframe
Instrument 2 NO Support Bay or
Testhead
POTS Bay or
External Instruments
Instrument Rack Controller in the Support Bay or
Testhead
VXI
Mainframe
Instrument 2
Support Bay or
Testhead
YES - 3070
POTS Bay or
E1421B VXI
Instrument Rack Controller Mainframe
Face down
6634A/B VXI Mainframe and
VXI Middle DUT Supplies in the
Mainframe 6634A/B Testhead
Instrument 1 Outside
6624A
Instrument 2
YES - 79000
79K-HPIB.WPG
Setting up the Testhead for Automation Figure 1-16 Connecting the EMO cable
If the testhead is being used in an automation

environment in which a piece of automation equipment System Card
is being installed on top of the testhead, do the
following: J3
1 Shut down the testhead.

2 Rotate the testhead to the horizontal position and
install the shipping bolts in the rear of the testhead to
keep it from being rotated (see Figure 1-5 on
page 1-15).
3 Screw the testhead leveling feet down to the floor to
stabilize the testhead and keep it from moving on the
floor (see Figure 1-6 on page 1-16). Also install 6 Remove the jumper from terminals 11 and 12 on the
floor brackets to keep the testhead stable. If you don’t plug and connect the Emergency Shutdown (EMO)
have a floor bracket kit, order Agilent 44990-63221. switch on the automa-tion equipment to pins 11 and
Installation instructions accompany the kit. 12 on the plug. Then reinstall the plug on the System
4 Using a 5-millimeter hex key wrench, remove the Card.
safety shroud from around the testhead’s pin field.
WARNING
5 After installing the automation equipment on the
testhead, reach under the testhead and disconnect
the plug from the Auxiliary connector (J3) on the
✸ DO NOT operate the system without an EMO
switch properly wired and accessible to the
System Card (Figure 1-16). operator. Failure to provide EMO capability may
result in death or serious bodily injury.
7 Boot the testhead. When the testhead is booted, press

the EMO switch on the automation equipment to
verify that it is functioning properly.
EFS Board Handler
NOTE
Be sure testhead diagnostics runs without failure
before installing the board handler. You cannot
rotate the testhead to the service position with the
board handler installed.
If this system has an Agilent 44990A EFS Board

Handler, use the information in Chapter 8 of the Agilent
44990A EFS Board Handler Manual (44990-90004) to
install it. Connect the board handler to port 2 of the
E3488 SCSI-MUX box. Use an RJ-45 cable
(8120-6773) and a DB-9 connector adapter
(E9970-63200). The connector adapter is in the spare
parts kit that comes with the board handler.
UNIX System Installation Procedure: Completing the Installation
Completing the Reinstalling the Pod Covers Turning System Administration Over to the
Installation If any pod or cradle covers are still off the system, Customer
reinstall them now. ■ Inform the customer that Agilent shipped the
software without a root password, and that they
Making a System Recovery Tape should use the passwd statement to create a root
password.
A recovery tape allows you to boot the controller after a
catastrophic fault, such as when you can no longer boot ■ Tell the system administrator about the
from your disk. To make a recovery tape, refer to contributed software. A disclaimer of any
Administering Agilent 3070 UNIX Systems warranties, expressed or implied, is displayed
(E9900-90000). while un-compressing contributed software. If the
system administrator desires to un-compress
CAUTION contributed software, log in as root and type:
✸Using the system recovery tape will re-initialize

your disk drive, and therefore, all existing data
cd /opt/hp3070/contrib/bin
sh Convert
will be lost. Documentation files are un-compressed in the
/opt/hp3070/contrib/doc subdirectory.
Making a System Backup Tape ■ Remind the system administrator that DNS or NIS
need to be setup (see Additional Network
To make a backup tape, refer to Administering Agilent Parameters — When you see: on page 1-22).
3070 UNIX Systems (E9900-90000). This is the customer’s responsibility.
UNIX System Installation Procedure: Completing the Installation
Filling Out the System Support Log

Introduce the customer to the Agilent 3070 / 79000
System Support Log (03066-90150) now.
1 Place your business card in Chapter 1, and suggest
that other Agilent representatives’ cards belong
there too.
2 Place the customer’s Agilent 3070 / 79000 software
licenses in Chapter 2.
3 Discuss the Preventive Maintenance information in
UNIX System Installation Reference on page 2-1,
with the customer.
4 Fill out the Installation and Configuration Records to
reflect the system. If you fixed a problem that you
feel warrants a Maintenance Record, fill one out now.
Installation Billing Information

You may charge up to eight hours to Agilent’s
Electronic Manufacturing Test Division (EMTD/0900)
for installing the system. Please charge actual time not
to exceed eight hours. Do not include repair time on the
installation repair order; complete a separate repair
order for any warranty repair associated with the
installation.
2 UNIX System Installation Reference
E4000-90300 Rev. J 11/2003
In this Chapter... ■ File System Changes With HP-UX 10.2X (B.03.XX), 2-2
■ Installing and Reviewing Codewords, 2-4
■ The Configuration Files, 2-5
■ The BT-BASIC Editor, 2-26
■ HP-UX Quick Reference, 2-29
■ vi Editor Quick Reference, 2-32
■ Troubleshooting, 2-35
■ Miscellaneous, 2-52
This chapter contains reference information that may be

helpful while installing an Agilent 3070 / 79000 board
test system.
UNIX System Installation Reference: File System Changes With HP-UX 10.2X (B.03.XX)
File System When HP-UX went to revision 10.2X at 3070 / 79000 Two changes that affect key directories are:
revision B.03.00 (3070 Series 3), many files, directories
Changes With and commands (or scripts) changed location in the file /hp3070 became /var/hp3070
HP-UX 10.2X system. Some commands also changed in functionality. /usr/hp3070 became /opt/hp3070
These changes affect the hp3070 directory where the
(B.03.XX) diagnostic and configuration files are located and many
directories related to networking. Table 2-1 is a list of files, directories and commands
that are important for installation and configuration:
Table 2-1 Comparison of file systems
Pre-HP-UX 10.2X Post-HP-UX 10.2X

/hp3070/diagnostics/th1/config /var/hp3070/diagnostics/th1/config
/hp3070/diagnostics/th1/cal_B /var/hp3070/diagnostics/th1/cal_B
/hp3070/diagnostics/th1/config.pvi /var/hp3070/diagnostics/th1/config.pvi
/hp3070/standard/config /var/hp3070/standard/config
/hp3070/lib/.enable /var/hp3070/lib/.enable
/dev (no change)
/etc/bootptab (no change)
/etc/checklist /etc/fstab
/etc/csh.login (no change)
/etc/dmesg /usr/sbin/dmesg
/etc/exports (no change)
/etc/hosts (no change)
/etc/ifconfig /usr/sbin/ifconfig
/etc/inetd.conf (no change)
UNIX System Installation Reference: File System Changes With HP-UX 10.2X (B.03.XX)
Table 2-1 Comparison of file systems (continued)
Pre-HP-UX 10.2X Post-HP-UX 10.2X

/etc/inittab (no change)
/etc/lanscan /usr/sbin/lanscan
/etc/netlinkrc /etc/rc.config.d/netconf
/etc/profile (no change)
/etc/services (no change)
/etc/set_parms /sbin/set_parms
/etc/shutdown /sbin/shutdown
/etc/telinit /sbin/init
/usr/adm/rc.log /etc/rc.log
/usr/adm/inetd.sec (no change)
/usr/hp3070/bin /opt/hp3070/bin
/usr/hp3070/bin/ppb_report /opt/hp3070/bin/ppb_report
/usr/hp3070/contrib/bin /opt/hp3070/contrib/bin
/usr/hp3070/contrib/doc /opt/hp3070/contrib/doc
/usr/hp3070/lib/nls/american/%N.cat /opt/hp3070/lib/nls/american/%N.cat
/usr/lib/tztab (no change)
/usr/lib/uucp/uugetty (no change)
/usr/pil/defaults/hwconfig.cf /etc/opt/sicl/hwconfig.cf
UNIX System Installation Reference: Installing and Reviewing Codewords
Installing and 1 Log in as root and run preupdate; type:

Reviewing /opt/hp3070/etc/HP3070SU/preupdate
Codewords 2 Enter all codewords from the software licenses

shipped with the system.
3 To verify the codewords, type:
/opt/hp3070/bin/codeword -l (-el, not -one)
4 Log out when you have entered all the codewords.
NOTE
Incorrectly entered codewords, blank lines or
spaces before or after a codeword may cause
errors when compiling the config files. User and
Operator logins may not boot if the
/var/hp3070/lib/.enable file contains invalid
information. Codeword order does not make any
difference.
After installing or changing codewords, you must

compile both the system config file (/var/hp3070/
diagnostics/th1/config) and the standard config file
(/var/hp3070/standard/config).
Codeword information is stored in the system config
object file by the compiler. This does several things: It
confirms that the hardware and enable statements are
compatible, it constrains the development environment
to the appropriate features, and at run time it verifies
that the testhead has the resources required by the test.
UNIX System Installation Reference: The Configuration Files
The Configuration Two types of configuration files are discussed in this

section. They are informally called the system config
Files file and the standard config file:1
system config file: /var/hp3070/diagnostics/th1/config

standard config file: /var/hp3070/standard/config
The System Config File

The system config file informs the system software
what hardware to expect in the testhead. Usually this file
will match the actual system hardware. One reason for
changing this file to represent something other than the
actual system hardware is to facilitate certain methods
of system troubleshooting.
1 Actually, there are two more config files. The standard config file mentioned above is used as a template for creating board config files
which are used in board test development. A fourth config file is the hwconfig.cf file that sets up communication with GPIB devices
(see page 2-36).
The testhead name Statement ControlXT/XTP Cards in the testhead, which are on the
testhead LAN (see page 2-43).
The testhead name statement in the system config file
identifies the block in the /etc/bootptab file that For an Agilent 3070 Series 3 / 79000 testhead with
contains the hardware addresses (ha) and internet B.03.00 or later software, the testhead name statement
protocol addresses (ip) for the System Card and any in the system config and /etc/bootptab files must
look like this:
testhead name "testhead1" "module3" "module2" "module1" "module0"
testhead1 represents the System Card, and module<n> relay 1 controls vacuum 2,3
represents the ControlXT/XTP Card in each module. relay 2 controls vacuum 0,1
Include only the modules that are present. If the testhead For testheads with the Agilent E9945A two-module
does not have ControlXT/XTP Cards, then no internal vacuum system, the default statements are:
module<n> keywords are needed.
relay 1 controls vacuum 3
Because the System Card and ControlXT/XTP Card IP relay 2 controls vacuum 2
addresses are local to each system, their IP addresses are For testheads with the Agilent E9946A four-module
identical in all systems. However, the hardware address
internal vacuum system, the default statements are:
(ha) of each card is unique.
The board Handler, line frequency and relay Statements relay 2 controls vacuum 2
Edit the system config file to make it match the system. relay 4 controls vacuum 0
board handlerComment1 (!) this for now There is nothing special about the defaults except that
each matches a configuration shown in the site
line frequency 60Un-comment either 50 or 60 (Hz)
preparation manual. Review the Agilent 3070 / 79000
The relay <x> controls vacuum <y> statements also Family Site Preparation Manual (03066-90114) to see a
need to match the actual hardware configuration after drawing of this default vacuum hookup. Modify the
the customer decides how to implement vacuum control. relay statements so they will work with your customer’s
For testheads without internal vacuum valves, the hardware.
default statements are:
1 Commented means that the comment character, an exclamation mark (!), has been placed at the beginning of the line. Un-commented
means the ! has been deleted from the beginning of the line.
For example, to turn on all four vacuum ports with a cards 2, 3, 4, 5 hybrid advanced
single relay, you might use this statement in the system cards 2 to 5 hybrid advanced
cards 2, 4, 7 to 11 hybrid advanced
configuration file:
relay 1 controls vacuum 0,1,2,3 Table 2-2 includes footnotes with rules or limitations
that apply to certain configurations of cards. One rule
The cards <keywords> Statements that applies to all HybridPlus Pin Cards is that you can
mix single-density and double-density cards in the same
You can use the Official system configuration file module.
printout shipped with the system as a model if you need
to customize the system configuration file. Table 2-2 Table 2-2 spans three pages: the first page covers the
cross-references the diagnostic name and part number to Access, Analog, ASRU, Channel, and Control Cards;
cards <keywords> statements in the configuration the second page covers Hybrid Cards; and the third page
files. covers Serial Test Cards.
The cards <keywords> statements can be delimited by

commas (,); a range can be separated by the word to.
Valid examples are:
Table 2-2 Diagnostics name to card type cross reference
Diagnostics Config Name cards <keywords> Statement in the system config file Pattern App Part Number
(in the Config screen) (see the Notes at the end of the table) Rate of the Card
Access access 6/12/20 MP/s E1061-66501
Analog analog 6/12/20 MP/s E1172-66524
E1121-66526
Ana_DD analog double density 6/12/20 MP/s E4000-66542
Ana_DD2 analog double density 6/12/20 MP/s E4000-66551
ASRU asru 6/12 MP/s 03066-66530
ASRU_B asru b revision 1
6/12/20 MP/s 03066-66531
ASRU_C asru c revision 6/12/20 MP/s 03066-66532
Table 2-2 Diagnostics name to card type cross reference (continued)
Channel channel 6/12 MP/s 03066-66560
Chan_HA channel high accuracy 20 MP/s 03066-66562
Ctl_Std control standard 2
6 MP/s E1038-66515
Ctl_Adv control advanced 2
12 MP/s 03066-66510
Ctl_Pls control plus <x> 2,3
6/12/20 MP/s 03066-66511
Ctl_Xt control xt 2
6/12/20 MP/s E4000-66512
Ctl_Xtp control xtp 2
6/12/20 MP/s E9900-66504
Hyb_Std hybrid standard 6 MP/s E1046-66522
H_PpuStd hybrid standard 4 6/12 MP/s E4045-66527
H_StdDD hybrid standard double density 5,6
6 MP/s E4000-66540
H_StdDD2 hybrid standard double density 5,6
6 MP/s E4000-66550
H_PpuDD hybrid standard double density 4,5,6
6/12/20 MP/s E4000-66546
HPpuDD2 hybrid standard double density 4,5,6
6/12/20 MP/s E4000-66550
Hyb_Adv hybrid advanced 5,6
12 MP/s 03066-66520
Hyb_B hybrid advanced b revision 5,6
12 MP/s 03066-66521
H_AdvDD hybrid advanced double density 5,6,7
12 MP/s E4000-66544
HAdvDD2 hybrid advanced double density 5,6,7
12 MP/s E4000-66550
Hyb_HA hybrid high accuracy 5
20 MP/s 03066-66523
H_HA_DD hybrid high accuracy double density 5,6,7
20 MP/s E4000-66545
Table 2-2 Diagnostics name to card type cross reference (continued)
HHADD2 hybrid high accuracy double density 5,6,7
20 MP/s E4000-66550
HStd_32 hybrid standard double density 32 5 6 MP/s E9900-66502
HAdv_32 hybrid advanced double density 32 5
12 MP/s E9900-66502
H_HA_32 hybrid high accuracy double density 32 5 20 MP/s E9900-66502
HPpu_32 hybrid high accuracy double density 32 5 20 MP/s E9900-66502
Serial serial 8,9
6/12/20 MP/s E1085-66502
Serial serial with cables 8,9
6/12/20 MP/s E1085-66502
with
E1093-61601
STC_B serial b revision 8,9,10
6/12/20 MP/s E1085-66502
STC_B serial b revision with cables 8,9,10
6/12/20 MP/s E1085-66502
with
E1093-61601
1. Agilent 3072 Process Test Systems must list asru in both the system and standard config files. When used in a 6- or
12-MP/s system, an asru b revision card should be listed as asru in the config files.
2. You cannot mix Control Cards in any combination in the testhead except control xt and control xtp. control stan-
dard and control advanced do not work with B.03.xx or later software.
3. <x> is the card’s memory in MB. It can be no value, 4 or 16; the default (no value) is 4 MB.
4. The card ID identifies Pay-Per-Use Hybrid Cards, causing the Diagnostics Config Name to indicate Ppu.
The <speed> of a PPU card depends on the card and the system in which it is installed. In a Series II PPU system, the
<speed> is “standard” unless the customer chooses the Pay-Per-Hertz option in which it is “advanced.” In a Series 3 PPU
system, the <speed> is “high accuracy” unless there are single-density PPU cards in the system in which case the <speed>
is “advanced” (single-density PPU cards cannot be “high accuracy,” and all cards in a system must be the same speed).
5. If the keyword 32 appears at the end of the hybrid... statement, the system interprets it as a Hybrid32 Card
(E9900-66502) instead of a HybridPlus Card. If Hybrid32 Cards are present, the Control Cards must be control xt/xtp.
6. You can mix hybrid advanced and hybrid advanced b revision cards in a testhead. You cannot mix hybrid
standard, hybrid advanced, or hybrid high accuracy cards in any combination in a testhead.
7. If any hybrid ... double density card is used in a testhead, all Control Cards must be control plus or conrol
xt/xtp.
8. If an STC or STC Plus Card is used in a testhead, all Control Cards must be control plus or control XT/XTP.
9. If you have any form of serial keyword in the Config file, you MUST also have serial ports statements defined in the
/var/hp3070/diagnostics/th1/config file for each STC/STC Plus Card. Also verify that the serial test codeword is
in the /var/hp3070/bin/.enable file.
10. The serial b revision card requires software revision B.03.20 or greater. You cannot mix serial (STC, E1089A) and
serial b revision (STC Plus, E1089B) Cards in the testhead. The STC and STC Plus Cards use the same card
(E1085-66502), but the PM and STS modules are different. You cannot mix TTL PMs or STSs from STC and STC Plus Cards
on the same STC or STC Plus Card; see the Agilent 3070 / 79000 Telecom Theory & Repair Manual (03066-90100) for more
information.
NOTE
Serial = STC Card (E1089A)
STC_B = STC Plus Card (E1089B)
serial means that the STC Card DOES NOT
have external cables connected.
serial with cables means that the STC Card
does have external cables connected.
The supplies <keywords> Statements There are four types of DUT power supplies allowed in
the system as shown in Table 2-3. The Agilent 6634A
NOTE can only be used with ASRU revision C cards,
03066-66532, on the high-voltage ports (ports 5 and 6).
Numbering of the supplies in the supplies
<keywords> statements is arbitrary. The software
will accept any mapping of supply numbers to
modules. Ask the customer whether they plan to
share board test fixtures with other systems. If
they plan to do so, ask the customer whether they
have modified the default power supply setting. If
so, reconcile the supplies numbering with
existing systems.
Table 2-3 DUT power supplies
Product No. Model No. Description

44940A 6624A 4 outputs:2 @ 0–7 V, 0–5 A or 0–20 V, 0–2 A and
2 @ 0–20 V, 0–2 A or 0–50 V, 0–0.8 A
44941A 6621A 2 outputs: 0–7 V, 0–10 A and 0–20 V, 0–4 A
E4034A 6634A 1 output:1–100 V, 0–1 A
E3784A 6642A 1 output:0–20 V, 0–10 A
Table 2-4 on page 2-12 shows a valid default power For 307X systems, with a support bay, if you need to
supply mapping for each module, and the proper syntax determine which DUT power supply is wired to which
for each type of power supply. The commented (!) module, the DUT/ASRU (E4000-61602) cables are
statements illustrate that you cannot assign a power labeled on both ends with the module numbers to which
supply number (1 through 24) more than once in a they are routed. 317X systems use cable numbers
testhead, and you cannot assign a channel number (1 E4000-61606 and E1170-61607.
through 6) more than once in a module.
Factory defaults have been established for common

configurations.
Table 2-4 Default Power Supply Mapping (Rear view of testhead)
Module 0 Module 2
supplies hp6624 13 to 16 asru channels 1 to 4 ! supplies hp6624 5 to 8 asru channels 1 to 4

! supplies hp6621 13 to 14 asru channels 1 to 4 supplies hp6621 5 to 6 asru channels 1 to 4
! supplies hp6624 23 to 24 asru channels 5 to 6 ! supplies hp6624 19 to 20 asru channels 5 to 6
supplies hp6621 23 asru channels 5 to 6 ! supplies hp6621 19 asru channels 5 to 6
! supplies hp6634 23 asru channels 5 supplies hp6634 19 asru channels 5
! supplies hp6634 24 asru channels 6 supplies hp6634 20 asru channels 6
! supplies hp6642 23 asru channels 5 to 6 ! supplies hp6642 19 asru channels 5 to 6
Module 1 Module 3
supplies hp6624 9 to 12 asru channels 1 to 4 supplies hp6624 1 to 4 asru channels 1 to 4

! supplies hp6621 9 to 10 asru channels 1 to 4 ! supplies hp6621 1 to 2 asru channels 1 to 4
! supplies hp6624 21 to 22 asru channels 5 to 6 supplies hp6624 17 to 18 asru channels 5 to 6
supplies hp6634 21 asru channels 5 ! supplies hp6634 17 asru channels 5
supplies hp6634 22 asru channels 6 ! supplies hp6634 18 asru channels 6
If the power supplies are functional, a DUT supply’s

GPIB address can be determined by tracing the cabling
to determine which supply is connected to the module,
then reading the GPIB address from the front panel of
the supply. Factory default DUT power supply GPIB
addresses and /dev files are shown on page 2-13. The
customer has the flexibility to modify this addressing,
and if they have done so, they will need to inform the
CE of the address for a replacement supply.
The DUT Power Supply GPIB Addresses and Device Files To change the GPIB address, press ADDR (beside the
display), enter the desired address on the ENTRY keypad,
Power Supply Connection GPIB Device File and then press ENTER on the ENTRY keypad.
Address
Module 0, asru channels 1-4 22 /dev/ps0
Module 0, asru channel 5 or 5-6 26 /dev/ps4
Module 0, asru channel 6 27 /dev/ps5
NOTE
If a power supply is split between two modules,
the default GPIB address (and device file) is the
one for the lower numbered module.
Editing and Compiling the System Config File The Standard Config File
If the system config file as shipped from the factory is The standard config file (/var/hp3070/standard/
NOT acceptable,1 or you have moved cards in the config) is the master of the configuration files used to
testhead, edit the system config file: develop board tests. Programmers can modify a copy
1 Log in as service1.2 called board config for each board test developed. The
copy will be in each board’s subdirectory.
2 Open a BT-BASIC window.3
3 Type: get "config" (Return)
4 Edit the file to match the desired system
configuration. Use the configuration printout shipped
with the system as a model.
5 Type: re-save (Return)
If you have added a codeword(s) or changed the system
config file, you must compile the system config file;
type:
compile config; testhead (Return)
When the system config file has compiled without
errors, exit to the Service Package - Level 1 by
typing exit on the BT-BASIC command line.
1 If the /var/hp3070/diagnostics/th1/config file is missing or corrupted, one of the sys.config.* templates can be
copied from the /var/hp3070/diagnostics directory and edited to match the actual system configuration. Selected statements
from the system config file can then be copied to the standard config file as shown in Copying Statements from the System Config
File on page 2-22.
2 You may also go to the HP-UX shell from service1 and type vi config, but there is no syntax checking when editing with vi as
there is in BT-BASIC.
3 See The BT-BASIC Editor on page 2-26.
Syntax Differences from the System Config File The following statements1 can (or for some
configurations, must) be used in standard config and
Some of the syntax for the standard config file (copied
board config files:
to board config files) is different from that of the system
config file. However, the cards <keywords> syntax is ■ target
the same for the system confign file and the standard
■ enable
config file. The following statements must not be used
in the /var/hp3070/standard/config file or board ■ module
config file:
■ end module
■ testhead name "testhead1" "module3"
"module2" "module1" "module0" ■ cards
■ line frequency ■ supplies
■ board handler ■ ports
■ relay <x> controls vacuum <y>
■ connect
■ bank
■ end bank ■ control <x>
■ probe connect statements allow programmers to name and
■ debug port define the use of external ports. Usually these can
remain as-shipped until the customer decides how to use
■ control <x>
these ports.
1 See the 3070 Family Users’ Manual - Quick Reference Guide for definitions and conventions of these statements.
The target <keywords> Statements hp3070 advanced. The default target <keywords>
statements (Table 2-5), included in the standard config
NOTE file shipped with the system, match the full capability of
the system. Because it is more explicit and does not
The target <keywords> statement should be the
cause any problems, the target hp3070 advanced
first un-commented statement in the file and must
statement is included in the standard config file shipped
be before the cards <keywords> statements.
from the factory with 12-MP/s systems.
A target <keywords> statement is needed in each

board config file, unless the target system is target
Table 2-5 Factory default target <keywords> statements
Pattern Application Rate target <keyword> Statement

6-MP/s Systems target hp3073 standard
12-MP/s Systems target hp3070 advanced
20-MP/s Systems target high accuracy
With Agilent 3X79CT Telecom test systems, the default statements need to be modified per Table 2-6 on
target <keywords> statement is not correct unless the page 2-16.
customer also ordered an In-Circuit Upgrade. If the
customer did not order the In-circuit Upgrade with their
telecom test system, the target <keywords>
Table 2-6 Functional testhead target <keywords> statements
Product Description target <keywords> Statement

6-MP/s Functional Testhead target hp3073 standard functional
12-MP/s Functional Testhead target hp3070 advanced functional
20-MP/s Functional Testhead target high accuracy functional
With an Agilent 3X72 Process Test system, the default Process Test System default target <keywords>
target <keywords> is correct. See Table 2-7 for the statements.
Table 2-7 3X72 process test system default target <keyword> statements
Product Description target <keywords> Statement

3172U Unpowered Test (1 module) target unpowered
3072U Unpowered Test (3 modules) target unpowered
3172P Powered Test (1 module) target unpowered
3072P Powered Test (3 modules) target unpowered
3X72 Test Development Center Software and Licenses target unpowered
The enable <keywords> Statements If the system is target hp3070 advanced or target
high accuracy, the features listed below are implied
NOTE and do not need enable <keywords> statements.
The enable <keywords> statements should be If the system is target hp3073 standard, however, it
after the target <keywords> statement and must does not include these features. If the customer ordered
be outside of a module block. these products, you must add the appropriate codewords
and enable <keywords> statements for these features:
enable <keywords> statements are used in ■ SimPlate Express Fixture Software

combination with codewords to selectively enable ■ Combo/Incircuit Test Upgrade
software functionality. Commented enable
<keywords> statements for appropriate products for ■ Combinational/Functional Test Upgrade
each system are included in the default standard config See Product-specific enable <keywords> statements
file. The programmer will un-comment the correct on page 2-18 and Standard feature enable
enable <keywords> statements which correspond to <keywords> statements on page 2-19.
product numbers purchased or supplied as standard
software when they edit the board config file.
Table 2-8 Product-specific enable <keywords> statements
Product Description enable <keywords> Statement in /var/hp3070/standard/config

Simplate Express Fixturing Upgrade enable express fixturing
Serial Test enable serial test
In-Circuit Test enable incircuit test
6-MP/s Combinational Test enable combo test
Throughput Multiplier enable throughput multiplier
Panel Test enable paneltest
Interconnect Plus enable advanced boundary scan
TestJet enable testjet
Powered Test Upgrade enable powered testing
Connect Check enable connect check
Polarity Check enable polarity check
Multiple Board Versions enable multiple board versions
DriveThru enable drivethru
Magic Test enable magic
Flash70 enable flash70
Flash In-system Programming enable flash isp
PLD In-system Programming enable pld isp
Silicon Nails enable silicon nails
Table 2-9 Standard feature enable <keywords> statements
Functional Description enable <keywords> Statement in /var/hp3070/standard/config

Enables B.01.xx software to function with the controller enable software revision b
hardware. It causes software to develop tests that are
NOT compatible with pre-B.01.00 software developed
on the HP 9000 Series 300. The enable software
revision b statement is invalid in the series 300
environment.
On systems with double-density pin cards, allows the enable all high accuracy resources
second column to be used as drivers and receivers.
Enables the 3070 software to utilize the Agilent E4032A enable gr fixture interface
GenRad Universal Fixture Interface. The default GR (followed by GR multiplexing option 2:16 or 2:8
multiplexing option is 2:16 if a multiplexing option is not or 4:16)
entered.
Enables the 3070 software to utilize the Agilent E4031A enable hp3065 fixture interface
3065 Universal Fixture Interface.
Enables a given testhead resource to go to multiple PC enable dual well shared wiring
boards on multiple vacuum well fixture.
Enables interoperability between UNIX® and MS enable common delimiter
Windows®.
Editing the Standard Config File

The standard config file should be edited to contain the
full capability of the system the customer purchased. A
copy of the standard config file is used by board test
programmers as the description of the system hardware
used for resource allocation during test development.
This copy is called the board config file and is
required in each board subdirectory. The board config
file might describe this system, another system, or a
subset of this (or another) system. It is the responsibility
of the programmer to edit the board config file, but the
standard config file should contain all of the capability
of the system as a beginning point.
The Default Standard Config File

The default standard config file has the correct target
<keywords> statement with the possible exception of
Agilent 3079CT Telecom system. Commented1 enable
<keywords> statements for appropriate products for
each 3070 / 79000 system are included. Summarized
directions, shown below, for copying selected
statements from the system config file are included in
the standard config file. See Copying Statements from
the System Config File on page 2-22 for detailed
directions.
1 Commented means that the comment character, an exclamation mark (!), has been placed at the beginning of the line. Un-commented
means the ! has been deleted from the beginning of the line.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! During TESTHEAD CONTROLLER installation:
!
! Copy the statements:cards 1 asru . . .
!.
!.
!.
! supplies . . .
! ports . . .
!
! from the '/var/hp3070/diagnostic/th1/config' file
! to the blank spaces below for module <number>.
!
! Do NOT include 'end module', 'probe', 'debug port',
! 'bank <number>, or 'end bank' statements.
!
! For TEST DEVELOPMENT STATIONS copy the above statements from the
! '/var/hp3070/diagnostics/th1/config' file on the Testhead Controller.
!
! See the "HP 3070 Series II Family Installation" manual for more information.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Copying Statements from the System Config File file to the standard config file, as shown in Figure 2-1.
This ensures the programmer has the full capability of
The desired end result of the following procedure is to
the system in the standard config file
copy the cards ..., serial ports ..., supplies
(/var/hp3070/standard/config).
... and ports ... statements from the system config
Figure 2-1 Copying configuration information
The following procedure uses the mouse to copy text config file. This method is suggested to eliminate typing
from the system config file into a temporary buffer and errors and to save time.
then output the contents of the buffer into the standard
Move the second window to the lower right corner of the

NOTE display. To do this, place the mouse pointer on the top
If you are configuring a test server, log in to the bar of this window; then click and hold down the left
appropriate testhead controller and copy the mouse button. Drag the window to the lower right
appropriate statements from the system config file corner of the display to uncover the first window.
(/var/hp3070/diagnostics/th1/config). Release the button.
7 On the command line of the second BT-BASIC
One method to do this using BT-BASIC1 follows: window, type:
1 Log in as service1. get /var/hp3070/diagnostics/th1/config

Return
2 Open a BT-BASIC window. To open a BT-BASIC
window, move the mouse pointer out of all windows; 8 Press F1 to move the cursor into the workspace to
then click and hold down the right mouse button. permit editing.
Drag the pointer to highlight the New BASIC Window 9 Locate the first (or next) module <number> that
selection, then release the button. contains un-commented cards 1 ... statements
3 On the command line type: using the arrow keys or the Prev and Next keys. Scroll
the text up until you can see the end module
msi /var/hp3070/standard Return statement.
4 On the command line, type: 10 Place your mouse pointer on the left margin in front
copy config over config.temp Return of the first cards ... statement and click the left
mouse button. Hold the mouse button down and
This makes a backup copy of the config file in the highlight the text, by dragging the mouse pointer
event you have a problem with this procedure. over it, to include the ports ...2 statement. Release
5 On the command line, type: the button.
get /var/hp3070/standard/config Return You now have the cards 1 ..., serial ports
..., supplies ..., and ports ... statements
6 Open another BT-BASIC window. stored in a temporary buffer.
1 You may also use the HP-UX shell from service1 and vi to display and edit appropriate statements.
2 3072U Unpowered Process test systems will not have supplies ... or ports ... statements. Copy to the last statement before
the end module statement.
15 If you have a control plus 4 card, delete the

NOTE number after the plus. The standard config file will
Do NOT include probe, debug port, bank, or not compile if the number (amount of RAM) is
end bank statements. These statements are not included in the statement.
valid in the standard config file (/var/hp3070/
standard/config). NOTE
Do not delete the ! Specify instrument ...
11 Move the mouse pointer to the window containing through ! connect ... which were in the
the standard config file. Click on any border with the original file. These statements can be used by the
left mouse button to bring this window into the programmer to specify external instrumentation.
foreground.
12 Press F1 to enter the workspace. Then move the 16 Repeat steps 10 through 16 for each module
cursor immediately below the module <number> <number> that contains un-commented cards
statement that corresponds to the module <number> statements in the system config file.
statements you have stored in the buffer from the
17 When all of the correct statements have been copied
system config file.
to the standard config file, and appropriate
statements have been un-commented, re-save the
NOTE standard config file. To re-save, press F1 to return to
Failure to place the cursor immediately below the the command line, then type re-save and press
module statement can result in corruption of the Return.
file by over-writing existing statements. The
18 When all of the correct statements have been copied
blank space is 20 lines long and the copied
to the standard config file, exit the system config file.
statements may be up to 20 lines. If necessary,
To exit, press F1 to return to the command line, then
retrieve your backup copy and repeat steps 11-16.
type exit and press Return. Since no changes were
made in the system config file, you should not need
13 Click the right mouse button. The text from the to re-compile this file. However, you may wish to
buffer will be inserted into the standard config file. re-compile to verify that nothing was inadvertently
changed.
14 Un-comment the module <number> and end module
statements in the standard config file; use the delete Proceed to Compiling the Standard Config File on
character key to remove the comment (!) character. page 2-25.
Compiling the Standard Config File

If you have modified the standard config file or added
one or more codewords to the file, compile the standard
config file by entering:1
compile /var/hp3070/standard/config Return
Exit the BT-BASIC window. This will return you to the
Service Package - Level 1 menu.
1 From the HP-UX prompt, to compile, type: qcomp /var/hp3070/standard/config
UNIX System Installation Reference: The BT-BASIC Editor
The BT-BASIC Users in the HP-UX group /var/hp3070 can use the
BT-BASIC editor. The editor has command line input
Editor and a workspace, as shown in Figure 2-2.
Figure 2-2 BT-BASIC editor screen
BT-BASIC
Status: xxx lines in workspace
command line configuration xxxx
Workspace
BASIC
edit
Starting the BT-BASIC Editor When logged in as user1 through user4, you can start
BT-BASIC by clicking on the upward-pointing triangle
When logged in as service1, you can create a above the Agilent 3070 icon using the left mouse button.
BT-BASIC window by moving the mouse pointer out of A menu of Agilent 3070 programs will be displayed.
all windows, then clicking and holding down the right Click left on the BT-BASIC icon. To minimize the
mouse button. Drag the mouse pointer down to highlight Agilent 3070 Programs menu, click on the
the New BASIC Window selection, then release the downward-pointing triangle at the bottom of the menu.
button.
When you initially enter a BT-BASIC window, the switch to the workspace by pressing F1. In the
cursor will be on the command line. From the command workspace, you can edit a file’s contents. The cursor
line, you can enter and execute BT-BASIC commands. control keys, Insert Char, Delete Char, and arrow keys
See Table 2-10 on page 2-27 for BT-BASIC statements move the cursor in the workspace. You can switch back
commonly used during the editing of configuration files. to the Command line by pressing F1.
Using the BT-BASIC Editor Command Line Statements
To edit an existing file, first you will need to execute See Table 2-10.
get "<filename>". To create a new filename, you need
to switch to the workspace to permit editing. You can
Table 2-10 Commonly used BT-BASIC statements1
BT-BASIC Statement Statement Function

get "<filename>" retrieve an existing file
save "<filename>" create a new file
re-save
save an existing file
compile "<filename>"
compile "<filename>";testhead compile a file
findn "<string expression>" compile a testhead file
exit find the next occurrence of a string expression
quit a BASIC window
1. For a more complete list of BT-BASIC statements, see the 3070 Family Users’ Manual Quick Reference Guide A-K section
"Statements Organized by Task." See configuration-related statements beneath heading subsections "Configuration" and
"File Manipulation."
BT-BASIC Editor Syntax Checking

When you get "<filename>" a file, the editor will
determine what syntax checking rules apply based on
the type of file you are editing. For installations, you
will be editing config files, and the system will be using
configuration syntax rules. The editor will not allow
lines with line-specific syntax errors. Multi-line
problems like missing end module statements will not
be detected until the file is compiled.
Exiting the BT-BASIC Editor

You can exit a BT-BASIC window by typing exit on
the command line. Normally, after editing a file, you
should re-save the file. If you edited a file and did not
save the changes, the program will ask for confirmation
that you are intentionally not saving your changes.
To log out after logging in as user1 to user4, click on
the Exit icon in the lower right corner of the screen, then
click on the Yes button in the message box. This method
does not work for service1; log out from service1
using the Logout function key.
UNIX System Installation Reference: HP-UX Quick Reference
HP-UX Quick Type commands as they are shown in the second column. Follow each command with Return.
Italics specifies directory, file or other task-specific text.
Reference Keyboard keys are in bold.
For additional information type man command_name
using the commands shown in the second column.
Include pathnames with filenames if you are working
with different directories.
To Do This... Type This...

Working with Directories:
Show current working directory pwd
Change directory cd pathname
Change to home directory cd
Create a directory mkdir directory_name
Remove an (empty) directory rmdir directory_name
Display permissions for a directory ll -d directory_name
Change permissions for file or directory chmod octal# filename
Owner Group Others (See man page)

rwx rwx rwx

Working with Files:
List files and directories in current directory ls
List all files or directories, including hidden (dot) files ls -a
lsf
List files, and show directories with /
ll filename
Display permissions for a file
vi filename
Create or edit a file
more filename (q to quit) (v to vi)
Display file contents
cp -p file1 file2
Copy a file with permissions and owners
mv old_file new_file
Move a file to a new filename
cat file1 >> file2
Append file1 onto the end of file2
rm filename
Remove a file
lp filename
Print a file
Finding and Organizing:
Find file(s) beginning with x in the current and sub-directories. find . -name 'x*' -print
Find all occurrences of word in all files in the current directory grep word *
date
Display date and time
man command_name
Find HP-UX command manual page hostname
Find name of current host system uname -a
Find current HP-UX system information version
Find Agilent 3070 Software Revision (as user1 or service1)
env
(As root path is /opt/hp3070/bin)
Find environment info. including PATH

System Operations:
Clear screen clear
Log out exit or CTRL d Return
Change to Korn shell ksh
Edit your command line (in Korn shell set for vi) ESC (use vi commands)
Recall previous command line (with vi editor) ESC k (back) or j (forward)
Execute previous command line Return (when line is displayed)
ps -ef
List current process status and PID’s
kill PID (Process ID Number from list)
Kill (terminate) a process
passwd
Create or change a password
command < infile
Redirect input from a file to a command
command1 | command2
Connect two processes with a pipe
Network Operations:
Invoke ftp and connect to remote_hostname ftp remote_hostname
Copy a file using ftp from remote_hostname get remote_file
Copy a file using ftp from the local current directory to current directory on put local_file
the remote_hostname
Exit ftp bye
Log in on a remote system rlogin remote_hostname
UNIX System Installation Reference: vi Editor Quick Reference
vi Editor Quick Type commands as they are shown in the second column. Follow colon (:) and search (/) commands with Return
Italics specifies directory, file or other task-specific text. as indicated.
Reference Keyboard keys are in bold.
To Do This ... Type This in Command Mode

Getting Started with vi:
Create or edit a file (from HP-UX shell) vi filename
Make sure you’re in command mode ESC
Show if you are in command or insert mode :set showmode Return
Find out what file you are in CTRL g
Moving Within a File:
Move the cursor left or right h or l or arrow keys
Move the cursor up or down k or j or arrow keys
Cursor to end of line $
Cursor to beginning of line 0 (Zero) or ^
Cursor to end of file G
Cursor to beginning of file 1G (one G)
Inserting Text:
Insert text at the cursor position i
Insert (Append) text after the cursor position a
Backspace to overwrite previous character (in Insert Mode) CTRL h or Backspace

r (character)
Replace single character
R
Replace until ESC is pressed

Deleting text:
Delete characters at cursor x
Delete word (cursor at beginning of word) dw
dd
Delete the entire line at the cursor position
D
Delete from cursor to end of the current line dG
Delete from cursor to end of the file
Moving Text:
Join lines of text J
Copy a line into a buffer yy
p
Put copied or deleted text line from buffer after cursor line
:r filename Return
Read in another file after cursor line
Searching Text:
Search for words /words Return
Repeat the previous search for words n (forward search) or N (backward search)
Saving and printing Files:

Save file in same filename :w Return
Save file to a new filename :w new_filename Return
Exit from file without saving changes :q!
Overwrite another existing file with this file :w! or wq! Return
Save and exit from the vi editor :wq Return
Print another file from within a file :!lp filename Return

Repairing Mistakes:
Undo the previous action u
Restore a line to its previous state U
p
Restore (put) last delete
:e! Return
Restore current file to last saved text, disregarding changes
u (repeat to toggle)
Compare changes before and after an action
vi -r filename
Recover a file after a system interruption (from HP-UX shell)
UNIX System Installation Reference: Troubleshooting
Troubleshooting Switch Settings is available. Its Address must be set to 0100. Set the
switches as shown in Figure 2-3 on page 2-35.
This section is provided for troubleshooting purposes
only. If the computer boots and functions properly, An Agilent 10834A GPIB extender is mounted on the
disregard this section. If the computer does not function E2071C card to prevent kinking the cables which are
properly, use this section to verify that switches and attached to the card. You must remove the extender
jumpers have been set correctly. Not all I/O cards have before removing the card from the controller.
switches or jumpers, so only those that do are mentioned
in this section. Figure 2-3 E2071C card switches
E2071C GPIB Card Switches
NOTE
The E2071C GPIB card (E2073-66501) is an
instrument GPIB card, not a high-speed HP-IB
card. Therefore, it cannot be used to control disk
or tape drives.
The E2071C card was used in the 3070 Series II
system. The Series 3 / 79000 system uses the
Agilent 0960-1010 (TAMS) GPIB Card which
has no switches.
To add a second GPIB card to the controller, you must

do two things: (1) set the card’s address switches and (2)
modify the ...hwconfig.cf file. The switch settings
are explained below; the GPIB software configuration is
explained on the next page.
One E2071C GPIB card must be installed in slot 1. Its
Address must be set to 0000. A second optional Agilent
E2071C GPIB card may be installed in slot 2 if that slot
GPIB Software Configuration While logged in as root, run iosetup; type:

In order to communicate with GPIB devices, a /opt/sicl/bin/iosetup
hwconfig.cf file must be setup.1 This file has two
Follow the instructions on the screen. This program will
different paths depending on the software revision: modify the hwconfig.cf file. If a kernel rebuild is
necessary, this program will do it for you. The . . .
/etc/opt/sicl/hwconfig.cf B.03.XX hwconfig.cf file should include one or more of the
/usr/pil/etc/hwconfig.cf B.02.XX following lines:
7 hpib e2071 1 21 0b0000 1 3 1st HP E2071C GPIB Card

8 hpib4 e2071 2 21 0b0100 1 10 2nd HP E2071C GPIB Card
# Custom TULIP Driver
7 custom t60488 1 21 SYSCON DMATRM TAMS GPIB Card
1 There is also a golden copy of the file which you should retain as a backup copy:
/opt/sicl/defaults/hwconfig.cf B.03.XX
/usr/pil/defaults/hwconfig.cf B.02.XX
SEU-4470 RS-232 Card Switches and Jumpers
CAUTION
✸Damage to the SEU-4470 RS-232 card or

computer may result if cables are disconnected or
connected while power is applied. Shut down the
computer and turn off its power before connecting
or removing cables.
To prevent damage to computer cards from
electrostatic discharge (ESD), use a grounded
wrist strap and proper ESD handling techniques
when removing, adjusting and reinstalling
computer cards.
The SEU-4470 card was used in the Agilent 3070
Series II system. The Series 3 / 79000 system does
not use this card, but uses the Agilent E3788
SCSI-to-RS-232 MUX box instead.
A Danford/SBE SEU-4470 card (0950-2619 exchange)

can be installed in slot 2 of the C110 controller.
Set the switches and jumpers as shown in Figure 2-4 on
page 2-38.
NOTE
The SEU-4470 RS-232 card is not a
Hewlett-Packard product, so SAM cannot create a
device file for it. The SEU-4470 is not supported
under HP-UX 10.2.
Figure 2-4 SEU-4470 card switches and jumpers
28641B ThinLAN Transceiver Switches

Set the switches on the 28641B ThinLAN Transceiver
as shown in Figure 2-5.
Figure 2-5 28641B ThinLAN transceiver switches
28641B
ThinLAN Transceiver
Enable Disable
SQE Test
The 28641B ThinLAN Transceiver is used to connect an

IEEE 802.3 or Ethernet network device to a ThinLAN
coaxial network.
Set the SQE Test switch to Enabled for connection to an
AUI port on a LAN card or another device expecting
SQE signals. Set the SQE Test switch to Disabled for
connection to a hub or repeater’s AUI port.
28685B EtherTwist Transceiver Switches

Set the switches on the 28685B EtherTwist Transceiver
as shown in Figure 2-6.
Figure 2-6 Agilent 28685B EtherTwist transceiver switches
SQE Test
Link Beat
Loopback Test
Long Cable
Enable Disable
28685B
EtherTwist Transceiver
The 28685B EtherTwist Transceiver is a medium Set the Link Beat switch to Enabled if the transceiver is
attachment unit (MAU) that connects directly to the used in a 10Base-T network. Set the Link Beat switch to
AUI port on an IEEE 802.3 or Ethernet network device Disabled if the transceiver is used in a network that is not
such as a hub, bridge, or router, or a network adapter compatible with 10Base-T (e.g., Agilent StarLAN 10).
card in a PC or workstation.
Set the Loopback Test switch to Disabled for normal use.
Set the SQE Test switch to Enabled for connection to an Set the Loopback Test switch to Enabled only for
AUI port on a LAN card or another device expecting troubleshooting.
SQE signals. Set the SQE Test switch to Disabled for
connection to a hub or repeater’s AUI port.
The Long Cable switch allows the transceiver to be used

with twisted-pair cables over 100 meters in length. Set
the Long Cable switch to Enabled if using high-grade,
low-crosstalk twisted-pair cable. Set the Long Cable
switch to Disabled if not using high-grade twisted-pair
cable.
E3788 SCSI-MUX Box Switches

Set the SCSI ID switches on the rear of the box as shown
in Figure 2-7.
Figure 2-7 E3788 SCSI-MUX box SCSI ID switches
SCSI SCSI ID Switches
E3788SW.WPG
Controller Start-Up Problems Determining the Hardware Address

1 To troubleshoot any start-up problem, log in as root. To determine the hardware address2 and the status of the
No password is required on an initial installation. LAN, execute /etc/lanscan. The hardware address is
the second field, lan0 is the external LAN, and lan1 is
2 When you see the HP CDE1 screen, click left on the
the testhead LAN to the System Card.
terminal icon to open a window.
3 Move the cursor into the console terminal window. Testhead LAN
Check the contents of the /usr/adm/rc.log for
error messages; type:
NOTE
cd /usr/admReturn
A testhead LAN troubleshooting procedure can be
more rc.logReturn
dmesgReturn found in the file /etc/newconfig/hp3070/
README.LAN.htm. Launch Netscape and open
4 When finished, log out. this file.
NOTE
General LAN Information
The most common cause of failure is improper
termination of the LAN ports. Both the built-in Every device on the network must have three things
LAN AUI port and the plug-in LAN card port which identify it: a hardware address, an IP address, and
must be properly terminated. For additional a system name.
troubleshooting information see General LAN The hardware address is a 12-digit hexadecimal number,
Information on page 2-42. assigned by the manufacturer of the device, and coded
into the device.
Determining the IP Address The IP (internet protocol) address is assigned by the
LAN system administrator. It takes the form
To determine the IP address, execute xx.xx.xx.xx and is used by the high-level LAN
more /etc/hosts | grep <SYSTEM_NAME> or
software. Changing hardware does not affect the IP
/etc/ifconfig lan0. The IP address follows the
address.
word inet.
1 Common Desktop Environment.

2 The hardware address is also called a Link Level Address, LANIC ID, MAC Address, or Station Address.
The system name is also assigned by the LAN system (SAM). It will automatically update the /etc/bootptab
administrator. It is usually a name like hpmtle which file. To use SAM, perform the following steps:
has built-in company name and location coding that is
1 Log in as a user or superuser.
meaningful to the customer. An alias can also be
assigned. It is usually a verbal name like system1. Both 2 Click on the File Cabinet icon in the Common
the system name and the alias are mapped to the IP Desktop Environment (CDE) menu.
address. You can get the system name most easily by
3 From the Application Manager screen, select
typing uname -n at the HP-UX prompt.
(double-click) System_Admin.
System Card / Control Card LAN Information 4 Select Sam (it takes several seconds for the System
Administration Manager to run). If you logged in as a
On 3070 Series 3 / 79000 systems (with B.03.00 or later
user, you will have to enter the superuser password.
software), the System Card and the ControlXT/XTP
Cards communicate via LAN. Because the System Card 5 Select Networking and Communications.
and ControlXT/XTP Card IP addresses are local to each
6 Select Bootable Devices.
system, their assigned addresses are the same from one
system to the next. However, their hardware addresses 7 Select Fixed-Address Devices Booting From this
(ha)1 are unique in each system. Server. This will open a new window that displays
the System Card and Control Cards in the testhead.
The hardware address of the System Card is printed on
its sheet-metal panel. The last four digits of the 8 To edit the hardware address of a particular card,
ControlXT/XTP Card’s hardware address are printed on double-click it. After editing the appropriate field,
one of its ROMs; it’s the last line (hexadecimal number) click OK. (You can also select Actions and Modify to
on the label. See the examples in the bootptab file on modify a card, or Actions and Remove to remove a
page 2-44. card.)
If you change or swap a ControlXT/XTP Card,2 you 9 Exit the window and then exit SAM.
must change its hardware address in the system
software.
To change system software for a new hardware address,
use the HP-UX System Administration Manager
1 The hardware address is also called a Link Level Address, LANIC ID, MAC Address, or Station Address.
2 When swapping the System Card, you must remove the ROM from the old card and install it on the new card, so DO NOT change the
hardware address of the System Card.
/etc/bootptab file: Verify that the appropriate blocks are in this file as
shown below. The last four digits of the hardware
This file is the database for the BOOTP daemon. An
address (ha) are taken from the System Card or Control
entry in this file maps the hardware addresses of the
Card:
system hardware to their IP address and system name.
test:\
ba:\
bf=C2300B:\
hd=/usr/lib/X11/700X/bin:\
hn:\
ht=ether:\
vm=rfc1048:\
ha=080009000000:\
ip=192.30.103.01
testhead1:\ (System Card block)
ht=ether:\
vm=rfc1048:\
ha=08000945xxxx:\ (Hardware address of the System Card)
ip=10.3.112.2 (IP address; there is no :\ after the last line in an entry)
module0:\ (Module 0 block)
ht=ether:\
vm=rfc1048:\
ha=0060b0b2xxxx:\ (Hardware address of ControlXT/XTP, last 4 digits)
ip=10.3.112.4 (IP address)
ht=ether:\
vm=rfc1048:\

ht=ether:\
vm=rfc1048:\
ht=ether:\
vm=rfc1048:\
/etc/hosts file:
This file must contain the following lines:
10.3.112.2 testhead1 (LAN port to System Card)

10.3.112.7 module3 (Include modules as appropriate)
10.3.112.6 module2
10.3.112.5 module1
10.3.112.4 module0
NOTE
If your customer is using a nameserver instead of
the hosts file, the nameserver must have these
entries. (The hosts file will not be used.) Use
nslookup testhead1 to verify that the
nameserver knows about the testhead.
/etc/rc.config.d/netconf file: OPERATING_SYSTEM=HP-UX
This file configures your networking parameters. It sets LOOPBACK_ADDRESS=127.0.0.1 (Make sure this
up some things that the /etc/netlinkrc file used to as line exists!!)
well as some additional things. Check the following
things (in order in the default file): There is a section on setting up your public lan — the
one that talks to the factory network:
HOSTNAME="<the correct system
hostname>"
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=<x.x.x.x> (<x.x.x.x> should be the IP address for the machine.)
SUBNET_MASK[0]=<x.x.x.x>
(HP’s default is 255.255.248.0; this (<x.x.x.x> may be variable based on the site requirements.)
will often work.)
BROADCAST_ADDRESS[0]=<x.x.x.x> (Write out the IP address and the subnet mask in binary, invert
the subnet mask (bit by bit), and do a binary OR on the two
numbers. Then convert the numbers back to decimal. This will
give you the correct broadcast address. It will have the same
format as an IP address or mask.)
LANCONFIG_ARGS[0]="ether"
DHCP_ENABLE[0]=0
Below the section on the public lan, there’s a section on

routing.
ROUTE_DESTINATION[0]=default
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]=<x.x.x.x> (If the customer has a router defined, use that IP address. If
not, you can use the IP address that you used for lan 0.)
ROUTE_COUNT[0]=0
ROUTE_ARGS[0]=""
Below this section, you’ll find a section on the private /etc/services file:
(testhead) lan. These addresses should be the same on
Check this file and verify that the bootps and bootpc
every testhead that you install.
entries are correct:
RARPD=0
bootpc 67/udp
IP_ADDRESS[1]=10.3.112.1
bootpc 68/udp
SUBNET_MASK[1]=255.255.248.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=10.3.119.255 /etc/inetd.conf file:
LANCONFIG_ARGS[1]="ether"
DHCP_ENABLE[1]=0
Check this file and verify that the bootps entry is not
commented:
There are some additional parameters in the file as well.

These are usually not used. Most of the time, you are
best off if you leave them at their default values.
bootps dgram udp wait root /etc/bootpd bootpd
/usr/adm/inetd.sec file: security lockouts. If there is one for bootps, it must

allow an IP address of 0.0.0.0 as in the following
Check this file and see if there is a bootps entry; there
example:
need not be one. If there is none, then there are no
bootps allow <IP Address >.* <IP address range> 0.0.0.0
/var/hp3070/diagnostics/th1/config file:
Verify that it includes the following line:
testhead name "testhead1" "module0" "module1" "module2" "module3"
/dev directory: work, check the /etc/bootptab file, the LAN cable,
and the System Card.
Verify that the /dev directory contains the following
device files:
52 0x430000 /dev/lan1
52 0x430000 /dev/ieee1
52 0x430001 /dev/ether1
If you modify the /etc/rc.config.d/netconf or

/etc/inetd.conf files,1 reboot the controller2 to
reread the files. If the customer’s LAN uses
nameservers, the testhead’s IP address (10.3.112.2) and
system name (testhead1) must be known by all name
servers.
To verify communication to the testhead, you can use
the ping command. From the testhead controller, type
/etc/ping 10.3.112.1 -n 10. This verifies
communication with the LAN card; if it doesn’t work,
check the /etc/netlinkrc file and the LAN card. Type
/etc/ping 10.3.112.2 -n 10 to verify
communication with the System Card; if it doesn’t
1 If you edit the etc/inetd.conf file, you can run /etc/indtd -c to reread the /etc/inetd.conf file. Also a daemon runs
about every five minutes which rereads the /etc/inetd.conf file.
2 DO NOT use the HP-UX shutdown command in the CDE environment. To halt or reboot the controller, raise the Toolbox menu, click
General, double-click System_Admin, and double-click HaltSystem or RebootSystem. Do not use SingleUserMode.
LAN Hardware Information

NOTE
The LAN ports on the controller must be terminated
The factory has connected the testhead to the
properly. If they are not, the HP-UX Start Networking
LAN with a minimal /etc/hosts file. The
start-up process will fail during boot and you may have
factory has also configured the /etc/bootptab
LAN communication problems. This applies to both the
file to communicate with the Agilent 3X7X
built-in LAN AUI port and the LAN port in slot 3.
system card testhead LAN and no additional
The LAN AUI port must be terminated with a LAN interaction should be needed.
transceiver. The Agilent 28641B ThinLAN Transceiver
is shipped with the controller, but the Agilent 28685B
EtherTwist Transceiver or another transceiver may also Manually Setting the Local Time Zone &
be used. The transceiver, in turn, must be terminated System Time
with a BNC "T" connector (Agilent 1250-0781) and
either two LAN cables or two 50-ohm loads (Agilent As root, using vi, you can change the time zone
1250-0207). variable (TZ) in these files:
■ etc/profile
The LAN port in slot 3 must also be terminated with a
"T" connector and either two 50-ohm loads or one ■ /etc/csh.login
50-ohm load and a cable (Agilent 8120-5371) to the You can identify the local time zone in the file
System Card assembly in the testhead. /usr/lib/tztab. Shut down the system and correct the
system time when prompted.
CAUTION
✸Do NOT attempt to use SAM to set up the

testhead LAN. It will render the /etc/netlinkrc
so it will no longer function. See the Installation
Reference Section "Troubleshooting the Testhead
LAN" for the correct setup of the
/etc/netlinkrc file.
Verify the Plan For the LAN Installation Set Up the LAN Software
Before you set up the LAN, be sure you have
Verify the System Name
determined all of the information in Table 2-1, "LAN
Configuration Information," in Chapter 2. Use the plan Log in as root. Review the
that the customer gave you and consult with the /etc/rec.config.d/netconf file and find the line that
customer system administrator and LAN manager. To contains the HOSTNAME variable. You can do this by
complete final testing and customization of the LAN, typing:
you will need the assistance of the customer system more /etc/rec.config.d/netconf
administrator or LAN manager.
The name must match the name in the customer’s LAN
CAUTION plan as the correct name for this system. If it is not
correct, you can correct the system name by re-running
✸Do NOT use the sample dummy IP address
(10.11.13.10) as the IP address for any 3070 /
the script /etc/set_parms.1
79000 system. You MUST use a unique IP Check the LAN Hardware
address supplied by the customer system
administrator or LAN manager. Type dmesg to print the last boot message. This will
display the last boot message. Look for LAN diagnostic
information. Troubleshoot as necessary.
A common cause of failure is improper termination of
the LAN ports and this does not indicate any error in the
boot message. Both the built-in LAN AUI port and the
plug-in LAN card port must be properly terminated.
1 You may also use vi to edit and resave the /etc/rec.config.d/netconf file.
Edit the /etc/hosts File fields should be entered in the order shown below; the
alias is optional. You can enter a remark after a #
Using the information in Planning For the LAN
symbol.
Installation on page 1-19, edit the /etc/hosts file to
describe all the systems in the LAN plan. The first three For example, using the sample dummy values:
IP Address System Name alias comment

10.3.112.1 testhead dan # First Agilent 3070 system
Test the Network

From a root login, execute landiag. Use ping
<System Name> to verify connection to each of the
systems listed in the /etc/hosts file. Press Break or
Ctrl-C to stop the ping.
Manually Mount the File System

Have the customer’s system administrator manually
mount all file systems that will be automatically
mounted later. Verify the mount by accessing the
manually mounted file systems and have the customer’s
system administrator troubleshoot if necessary.
Advanced Networking Concerns

The customer’s system administrator or LAN manager
may want to mount other file systems on this system, or
mount this file system on another system. The
/etc/checklist file is read during boot and is used to
mount file systems. The /etc/exports file must be
created on this system if its file system is to be made
available for other systems to mount. Work with the
customer system administrator to customize the LAN.
UNIX System Installation Reference: Miscellaneous
NOTE
Miscellaneous Rotating the Testhead Without PDU Power Repeated rotating of the testhead when connected
to 120 volts ac may cause the thermal cutout to
NOTE open due to excessive heating. Aiding the motor
may be necessary to rotate a fully-loaded testhead
This applies to Series II only, not Series III. when connected to 120 volts ac.
The testhead rotation motor is a 240-volt ac motor with

a thermal cutout. The power cord to the motor is labeled
Testhead Motor Power and is plugged into the outlet
nearest the front lower corner of the testhead, as shown
in Figure 2-8 on page 2-53. 307X four-module systems
and 317X left-to-right systems have the Testhead Motor
Power plugged into the 200–240 volt outlet box in the
right lower front of the system in the right-most outlet.
317X two-module systems have the Testhead Motor
Power plugged into the outlet box behind the modules.1
Lower the rear cover2 onto the base of the system to
gain access to the outlets inside the testhead. To rotate
the testhead without system power, unplug the motor
from the testhead outlet and connect it to a standard
Agilent power cord. Connect the standard Agilent
power cord to 200–240 volts ac if possible. If not, plug
it into 120 volt ac and push on the testhead to help the
motor rotate the testhead. Push the switch inside the
testhead pod to activate the testhead rotation motor.
1 DUT power supplies are set at the factory to 100-120 volts to allow the supplies to meet low line conditions in all countries. Therefore,
the outlet behind the DUT supplies is wired for 100-120 volts.
2 You may have to lay down on the floor at the rear of the system and use a stubby flat blade screwdriver (or a coin) to loosen the rear panel
mounting screws.
Figure 2-8 Location of outlets for the rotating motor
Bank 2
Bank 1
Testhead Motor Power Testhead Motor Power LH2.WPG

317X 2-module testhead 307X 4-module testhead or
with Bank 2 loaded 317X 2-module testhead
with Bank 1 loaded
Moving the Controller to the Right Pod 5 Remove the controller, optional RS-232 MUX box
(with power pack), and LAN transceiver, and set
them aside.
NOTE
This is an optional procedure and applies to 6 Remove the bottom foam, tear off the perforated end
Agilent 3070 Series II systems only. It need not piece, turn it over, and place it in the right pod. Push
be done if the customer just wants the monitor and the middle section of foam down to expose a cut-out
keyboard moved (extension cables allow this), but for the controller.
only if the customer insists on moving the 7 Place the optional RS-232 MUX box (with power
controller itself. pack) in the foam with the ports to the rear. Use cable
ties to secure the optional MUX power pack to the
support structure. Install the LAN transceiver. Place
NOTE the controller in the bottom foam. Do not turn the
controller over, but keep it in the same orientation
The C110 and controller can only be moved to the
that it was in in the other pod. Use cable ties to secure
right pod in testheads shipped after November
the devices inside the pod.
1996. With older testheads the rotation switch will
physically interfere with the controller. In the 8 Replace the foam on top of the controller. Ensure that
newer testheads the switch was relocated slightly the thicker side of the foam is toward the testhead.
to provide clearance for the controller.
9 Reconnect all cables to the controller.
The controller must be shut down and turned off. See

Example 2-9 on page 2-55 for the following steps.
1 Using a T20 Torx driver, remove both pod covers
(5 screws in each cover).
2 Remove the foam from the top of the controller and
set it aside.
3 Disconnect all cables from the controller and
optional RS-232 MUX box (with power pack),
noting where to reconnect them later.
4 Reroute the cables to the right pod.
Figure 2-9 Moving the controller to the right pod
Keep the thick side of the

foam between the computer
and the testhead.
Attach the power pack
to the beam using
cable ties
Left Pod
Keep the MUX box Right Pod

between the computer
and the testhead,
ports to the rear. PDU
Turn the bottom foam over
and push down the cut-out
middle section. C110FOAM.WPG
3 UNIX Device Files – C240 and Earlier
E4000-90300 Rev. G 11/2001
In this Chapter... ■ Rebuilding Device Files at B.03.81 or Later, 3-2
■ 712/60/100 Controller, 3-4
■ 725/50 Controller, 3-8
■ 725/100 Controller, 3-13
■ C110 Controller, 3-18
■ B180L Controller, 3-22

test system.
The included tables list some of the device files, also
called special files, present in the 3070 / 79000 file
system. Standard ptyxx and ttyxx files are not listed in
order to limit the length of the list.
UNIX Device Files – C240 and Earlier: Rebuilding Device Files at B.03.81 or Later
Rebuilding Device Starting at software revision B.03.81, device driver matches the following tables is a coincidence; the
major numbers are dynamically assigned. This section major number may not always be 137.
Files at B.03.81 or describes the supported method for rebuilding device
Later files at B.03.81 and later. Character Block Driver Class
137 -1 sts comm
The minor numbers for the device files have not
changed. Use the minor numbers that are in the 4 Remove the device file:
following tables.
# rm /dev/ttyjb1
Process for Rebuilding Device Files 5 Use the mknod command to rebuild the device file.
Use the major number 137 that is associated with the
■ Use Table 3-1 on page 3-3 to locate the driver for sts driver:
the device file.
# mknod /dev/ttyjb1 c 137 0x011000
■ Use the lsdev command to determine the correct
major number associated with the driver (see 6 Set the correct permissions. The permissions have
Example for Recreating a Device File). not changed; use the same permissions that are in the
following tables:
Example for Recreating a Device File # chmod 666 /dev/ttyjb1
# chown root:other /dev/ttyjb1
This example recreates the device file /dev/ttyjb1.
You must be root to execute this procedure.
NOTE
1 Locate the device file in Table 3-1 on page 3-3. This An asterisk (*) in the name of a driver or device
device file is associated with the sts driver. file indicates that it can be replaced by any
2 Execute the /usr/sbin/lsdev -d <driver> combination of letters or numbers. For example,
command (the <driver> argument is case-sensitive): the btlan* driver in Table 3-1 refers to all btlan
drivers (btlan0, btlan1, etc).
# /usr/sbin/lsdev -d sts
3 Use the Character column to determine the major

number. In this example the major number for the
sts driver and the associated device file
/dev/ttyjb1 is 137. The fact that the major number
UNIX Device Files – C240 and Earlier: Rebuilding Device Files at B.03.81 or Later
NOTE
With dynamic assignment, the major number for a
particular device file may be different on each
type of supported controller. It may also be
different between similar controllers if the
hardware attached to the controllers is different.
Table 3-1 Device Files

Driver Function Device Files
asio0 Serial Port Interface cua0p0, cul0p0, mux0, mux1, rpr1, tty0p0, tty1p0, ttyd0p0
btlan* LAN Interface (C240, B180L, B2000) ether*, ieee*, lan*
lan2 LAN Interface (C110, 725, 712)
CentIf Parallel Port Interface c*t0d0_lp, lp
SCentIf
hpib HP HP-IB Card Interface counter, dmm, dmm_ref, hp3488, hp79000slot0, hpib1, ps0, ps1,
ps10, ps11, ps2, ps3, ps4, ps5, ps6, ps7, ps8, ps9, scope, synth
lv Logical Volumes /dev/vg*/group, /dev/vg*/lvol*, /dev/vg*/rlvol*
sdisk SCSI Interface (e.g., extra disks) /dev/dsk/c*t*d*, /dev/rdsk/c*t*d*
sts SCSI MUX Box (E3788) Interface acs, bcr, cuash*, hp44990, ttyds*, ttyjb1, ttym*, tycuas*
t60488 TAMS Card Interface t60488*
(C240, B180L, B2000)
UNIX Device Files – C240 and Earlier: 712/60/100 Controller
712/60/100
Controller Table 3-2 Device files on the 712/60/100 Controller (B.03.XX / HP-UX 10.X)
Permissions Owner Group Driver Minor Nos. Filename Function Where Used
crw-rw-rw- root other sts 0x001070 acs Performance Port ACS
crw-rw-rw- root other sts 0x001020 bcr Bar code reader
crw-rw-rw- bin bin beep 0x000000 beep
crw-rw-rw- lp bin CentIf 0x010002 c1t0d0_lp
crw--w--w- root sys cn 0x000000 console
-r--r--r-- root hp3070 108 counter
crw-rw-rw- bin bin framebuf 0x000000 crt
crw-rw-rw- bin bin framebuf 0x000000 crt0
crw-rw-rw- root other asio0 0x000001 cua0p0 Modem
crw-rw-rw- root other sts 0x001030 cuash04 Modem
crw-rw-rw- root other asio0 0x000001 cul0p0 Modem
-r--r--r-- root hp3070 108 dmm Functional DMM
-r--r--r-- root hp3070 108 dmm_ref Calibration DMM
crw-rw-rw- bin bin lan2 0x000001 ether0 System LAN
crw-rw-rw- root other lan2 0x0c0000 gpio1 GPIO to testhead
-r--r--r-- root hp3070 107 hp3488 Board handler switch/control
crw-rw-rw- root other sts 0x001010 hp44990 EFS Board Handler
-r--r--r-- root hp3070 107 hp79000slot0 79000 VXI
crw-rw-rw- root other sts 0x001010 JOT_PLC JOT Board Handler
crw-rw-rw- root other sts 0x001020 JOT_BCR_P0 JOT Bar Code Reader
crw-rw-rw- bin bin lan2 0x000000 lan0
prw-rw-rw- root root 0 log
crw------- lp bin CentIf 0x020002 lp
crw------- bin bin asio0 0x000080 mux0
crw-rw-rw- bin bin mm 0x000002 null
Table 3-2 Device files on the 712/60/100 Controller (B.03.XX / HP-UX 10.X) (continued)
crw-rw-rw- bin bin framebuf 0x000001 ocrt
crw-rw-rw- bin bin framebuf 0x000001 ocrt0
-r--r--r-- root hp3070 108 ps0 GPIO DUT power supply 0
crw-rw-rw- bin bin ps2 0x000000 ps2_0
crw-rw-rw- bin bin ps2 0x000003 ps2kbd
crw-rw-rw- bin bin ps2 0x000001 ps2mouse
crw-rw-rw- root other beep 0x208000 rhil
crw-rw-rw- root other asio0 0x000004 rpr1 Strip printer
-r--r--r-- root hp3070 107 scope Oscilloscope
-r--r--r-- root hp3070 108 synth
crw--w--w- bin bin asio0 0x000000 tty0p0 Modem device
crw------- root sys cn 0x000001 ttyconf
crw--w--w- uucp other asio0 0x000002 ttyd0p0
crw-rw-rw- root other sts 0x001030 ttyds04
crw-rw-rw- root other sts 0x001030 ttydsh04
crw-rw-rw- root other sts 0x001000 ttyjb1 Button adapter
crw-rw-rw- root other sts 0x001000 ttym01 Terminal MUX 1 Port 1
crw-rw-rw- root other sts 0x001030 tycuas04
/dev/dsk
brw-r----- bin sys sdisk 0x005000 c0t5d0
/dev/rmt
crw-rw-rw- bin bin stape 0x003000 0m
crw-rw-rw- bin bin stape 0x003080 0mb
crw-rw-rw- bin bin stape 0x003040 0mn
crw-rw-rw- bin bin stape 0x0030c0 0mnb
crw-rw-rw- bin bin stape 0x003000 c0t3d0BEST
crw-rw-rw- bin bin stape 0x003080 c0t3d0BESTb
crw-rw-rw- bin bin stape 0x003040 c0t3d0BESTn
crw-rw-rw- bin bin stape 0x0030c0 c0t3d0BESTnb
crw-r--r-- bin bin stape 0xfffffe stape_config
/dev/rscsi
crw-r----- bin sys sctl 0x007000 c0t7d0
/dev/vg00
crw-r----- root sys lv 0x000000 group
brw-r----- root sys lv 0x000001 lvol1
crw-r----- root sys lv 0x000001 rlvol1
UNIX Device Files – C240 and Earlier: 725/50 Controller
725/50 Controller
Table 3-3 Device files on the 725/50 Controller (B.03.XX / HP-UX 10.X)
crw--w--w- user1 hp3070 cn 0x000000 console
crw-rw-rw- root other hpib 0x070e00 counter Counter
crw-rw-rw- root other hpib 0x070a00 dmm Functional DMM
crw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMM
crw-rw-rw- bin bin lan2 0x010001 ether1 EISA LAN
crw-rw-rw- root other hil 0x000020 footpedal Footswitch
crw-rw-rw- root other 0x0c0000 gpio1 GPIO to testhead
crw-rw-rw- bin bin hil 0x000010 hil1 HP-HIL device
Table 3-3 Device files on the 725/50 Controller (B.03.XX / HP-UX 10.X) (continued)
crw-rw-rw- bin bin hil 0x000010 hil_0.1
crw-rw-rw- bin bin hil 0x000080 hilkbd HP-HIL keyboard
crw-rw-rw- bin bin hil 0x000080 hilkbd_0
crw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/control
crw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXI
crw-rw-rw- root other hpib 0x071f00 hpib1
crw-r--r-- root root lan2 0x430000 ieee1
crw-rw-rw- bin bin lan2 0x000000 lan0 Customer’s site LAN
crw-rw-rw- bin bin lan2 0x010000 lan1 Testhead LAN
crw------ bin bin asio0 0x000080 mux0
crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0
crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4
crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5
crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6
crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7
crw-rw-rw- bin bin hil 0x000000 rhil
crw-rw-rw- bin bin hil 0x000000 rhil_0
crw-rw-rw- root other asio0 0x010004 rpr1 E1199A Strip Printer
crw-rw-rw- root other hpib 0x070700 scope Oscilloscope
crw-rw-rw- root other hpib 0x071100 synth
crw--w--w- bin bin cn 0x000000 syscon
crw--w--w- bin bin cn 0x000000 systty
crw------ root sys cn 0x000001 ttyconf
crw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem device
crw-rw-rw- root other sts 0x001000 ttyjb1 Button Adapter
crw-rw-rw- root other sts 0x001000 ttym01 terminal mux 1 port 1
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
crw-r----- root sys lv 0x000001 lvol1
725/100 Controller
Table 3-4 Device files on the 725/100 Controller (B.03.XX / HP-UX 10.X)
crw--w--w- user1 hp3070 cn 0x000000 console
crw-rw-rw- bin bin lan2 0x010001 ether1 EISA LAN
crw-rw-rw- root other hil 0x000020 footpedal Footswitch
crw-rw-rw- bin bin hil 0x000080 hilkbd_0
crw-rw-rw- bin bin hil 0x000000 rhil
crw-rw-rw- root other asio0 0x010004 rpr1 E1199A Strip Printer
crw--w--w- bin bin cn 0x000000 syscon
crw--w--w- bin bin cn 0x000000 systty
crw------ root sys cn 0x000001 ttyconf
crw-rw-rw- root other sts 0x001000 ttyjb1 Button Adapter
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
UNIX Device Files – C240 and Earlier: C110 Controller
C110 Controller
Table 3-5 Device files on the C110 Controller (B.03.XX / HP-UX 10.X)
Permissions Owner Group Driver Minor Nos Filename Function Where Used
crw-rw-rw- root other sts 0x011020 bcr EFS bar code reader MUX port 3
crw-rw-rw- root other hpib 0x070e00 counter
crw-rw-rw- bin bin lan2 0x010001 ether1
crw-rw-rw root other sts 0x0c0000 gpio1 GPIO to testhead
Table 3-5 Device files on the C110 Controller (B.03.XX / HP-UX 10.X) (continued)
crw-rw-rw bin bin hil 0x000080 hilkbd_0
crw-rw-rw- root other hpib 0x070800 hp3488 EFS 3488A switch/control box
crw-rw-rw- root other sts 0x011010 hp44990 EFS Board Handler MUX port 2
crw-rw-rw- bin bin ps2 0x000001 ps2mouse Mouse
crw-rw-rw- root other sflop 0x501000 rhil
crw-rw-rw- root other asio0 0x010004 rpr1 Strip Printer
crw--w--w- root bin asio0 0x000000 tty0p0
crw--w--w- bin bin asio0 0x010000 tty1p0
crw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem (standard)
crw-rw-rw- root other sts 0x011030 ttyds04 Modem MUX port 4
crw-rw-rw- root other sts 0x011030 ttydsh04 Modem MUX port 4
crw-rw-rw- root other sts 0x011000 ttyjb1 PPU button adapter MUX port 1
crw-rw-rw- root other sts 0x011000 ttym01 Terminal MUX port 1
crw--w--w- root tty sts 0x011030 ttym04 Terminal MUX port 4
crw-rw-rw- root other sts 0x011030 tycuas04 Modem MUX port 4
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
UNIX Device Files – C240 and Earlier: B180L Controller
B180L Controller
Table 3-6 Device files on the B180L Controller (B.03.XX / HP-UX 10.X)
crw-rw-rw- root other sts 0x011020 bcr EFS bar code reader, MUX port 3
crw-rw-rw- root root btlan3 0x000001 ether0 System LAN
crw-r--r-- root root 0x430001 ether1 EISA LAN
crw-r--r-- root root 0x430000 ieee1
crw-rw-rw- root root btlan3 0x000000 lan0 Customer’s site LAN
crw-r--r-- root root 0x430000 lan1 Testhead LAN
Table 3-6 Device files on the B180L Controller (B.03.XX / HP-UX 10.X) (continued)
crw-rw-rw- bin bin ps2 0x000001 ps2mouse Mouse
crw-rw-rw- root other beep 0x000000 rhil_0
crw-rw-rw- bin bin t60488 0x000000 t60488.0
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
C240 Controller
Permissions Owner Group Driver Minor Nos Filename Function where Used
crw-rw-rw- root other hpib 0x070e00 counter
crw-rw-rw- root other sts 0x000001 cua0p0 Modem
crw-r--r-- root root btlan3 0x430001 ether1 EISA LAN
crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT powe supply 0
crw-rw-rw- bin bin ps2 0x000001 ps2mouse
crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT powe supply 4
crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT powe supply 5
crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT powe supply 6
crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT powe supply 7
crw--w--w- bin bin asio0 0x000000 tty0p0 Modem device
crw--w--w- uucp other asio0 0x000002 ttyd0p0
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
4 UNIX Device Files – B2000 and Later
E4000-90300 Rev. G 11/2001
In this Chapter... ■ Rebuilding Device Files at B.03.81 or Later, 4-2
■ B2000 Controller, 4-4

test system.
The included tables list some of the device files, also
called special files, present in the 3070 / 79000 file
system. Standard ptyxx and ttyxx files are not listed in
order to limit the length of the list.
UNIX Device Files – B2000 and Later: Rebuilding Device Files at B.03.81 or Later
Rebuilding Device Starting at software revision B.03.81, device driver matches the following tables is a coincidence; the
major numbers are dynamically assigned. This section major number may not always be 137.
Files at B.03.81 or describes the supported method for rebuilding device
Later files at B.03.81 and later. Character Block Driver Class
137 -1 sts comm
The minor numbers for the device files have not
changed. Use the minor numbers that are in the 4 Remove the device file:
following tables.
# rm /dev/ttyjb1
Process for Rebuilding Device Files 5 Use the mknod command to rebuild the device file.
Use the major number 137 that is associated with the
■ Use Table 4-1 on page 4-3 to locate the driver for sts driver:
the device file.
# mknod /dev/ttyjb1 c 137 0x011000
■ Use the lsdev command to determine the correct
major number associated with the driver (see 6 Set the correct permissions. The permissions have
Example for Recreating a Device File). not changed; use the same permissions that are in the
following tables:
Example for Recreating a Device File # chmod 666 /dev/ttyjb1
# chown root:other /dev/ttyjb1
This example recreates the device file /dev/ttyjb1.
You must be root to execute this procedure.
NOTE
1 Locate the device file in Table 4-1 on page 4-3. This An asterisk (*) in the name of a driver or device
device file is associated with the sts driver. file indicates that it can be replaced by any
2 Execute the /usr/sbin/lsdev -d <driver> combination of letters or numbers. For example,
command (the <driver> argument is case-sensitive): the btlan* driver in Table 4-1 refers to all btlan
drivers (btlan0, btlan1, etc).
# /usr/sbin/lsdev -d sts
3 Use the Character column to determine the major

number. In this example the major number for the
sts driver and the associated device file
/dev/ttyjb1 is 137. The fact that the major number
UNIX Device Files – B2000 and Later: Rebuilding Device Files at B.03.81 or Later
NOTE
With dynamic assignment, the major number for a
particular device file may be different on each
type of supported controller. It may also be
different between similar controllers if the
hardware attached to the controllers is different.
Table 4-1 Device Files

Driver Function Device Files
asio0 Serial Port Interface cua0p0, cul0p0, mux0, mux1, rpr1, tty0p0, tty1p0, ttyd0p0
btlan* LAN Interface (C240, B180L, B2000) ether*, ieee*, lan*
lan2 LAN Interface (C110, 725, 712)
CentIf Parallel Port Interface c*t0d0_lp, lp
SCentIf
hpib HP HP-IB Card Interface counter, dmm, dmm_ref, hp3488, hp79000slot0, hpib1, ps0, ps1,
ps10, ps11, ps2, ps3, ps4, ps5, ps6, ps7, ps8, ps9, scope, synth
lv Logical Volumes /dev/vg*/group, /dev/vg*/lvol*, /dev/vg*/rlvol*
sdisk SCSI Interface (e.g., extra disks) /dev/dsk/c*t*d*, /dev/rdsk/c*t*d*
sts SCSI MUX Box (E3788) Interface acs, bcr, cuash*, hp44990, ttyds*, ttyjb1, ttym*, tycuas*
t60488 TAMS Card Interface t60488*
(C240, B180L, B2000)
UNIX Device Files – B2000 and Later: B2000 Controller
B2000 Controller
Table 4-2 Device files on the B2000 Controller (B.03.XX / HP-UX 10.X)
crw-rw-rw- lp bin SCentIf 0x010002 c1t0d0_lp
crw-rw-rw- bin bin hub 0x000000 hub
Table 4-2 Device files on the B2000 Controller (B.03.XX / HP-UX 10.X) (continued)
crw------- lp bin SCentIf 0x020002 lp
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
UNIX Device Files – B2000 and Later: C3600 Controller
C3600 Controller
crw-rw-rw- lp bin SCentIf 0x010002 c1t0d0_lp
crw-rw-rw- bin bin hub 0x000000 hub
crw------- lp bin SCentIf 0x020002 lp
/dev/dsk
/dev/rmt
/dev/rscsi
/dev/vg00
5 UNIX Controller Cabling Diagrams
E4000-90300 Rev. J 11/2003
In this Chapter... ■ 712/60/100 Controller, 5-2
■ B180L Controller, 5-14
■ B2000 Controller, 5-20

test system.
The included cabling diagrams show how all system
components and peripherals are connected to the
controllers. Each diagram has an accompanying table
that lists the part numbers of cables, connector adapters,
and devices. For more controller cabling information
see Chapter 1 in the Agilent 3070 / 79000 Repair
Manual (E4000-90160).
UNIX Controller Cabling Diagrams: 712/60/100 Controller
712/60/100 See Figure 5-1 on page 5-4.

Controller Table 5-1 712/60/100 Controller cables and devices — Series II
Cables Part No Description

A E1170-61604 Control Cable
B 8120-3445 GPIB Cable, 1-meter
C 8120-3446 GPIB Cable, 2-meter
D 8120-3543 LAN Cable, BNC to BNC, 72-in.
E 8120-1838 LAN Cable, BNC to BNC, 12-in.
F A2263-62045 A4014A LAN/RS-232 Breakout Cable
G 24542M Modem Cable, RS-232, DB9(f) to DB25(m) cross-conn., 5-m
H 03066-61629 Strip Printer Cable, RS-232, DB9(f) to DB25(m) cross-conn., 5-m
I 8120-6751 Bar Code Scanner Cable
J 8120-6713 Footswitch Extender Cable, RJ11
K C2300-60005 Monitor Cable
L 03066-61640 Video Extension Cable, 10 ft.
M 8120-6773 RJ-45 Cable, shielded, 4-meter plus E4000-62106 DB-25 adapter
N 8120-6773 RJ-45 Cable, shielded, 4-meter plus E4000-62105 DCE adapter
P 8120-6794 Keyboard / Mouse Extension cable
R 8121-1045 SCSI DDS Drive Cable
S 8120-6730 LAN AUI Extension Cable, 3-ft.
Table 5-1 712/60/100 Controller cables and devices — Series II (continued)
Devices Part No Description

1 44902-60000 Footswitch with Cable
2 E4000-62102 Footswitch Adapter
3 28641B ThinLAN Transceiver
4 0510-1611 Hook & Loop Fastener
5 0950-2946 Bar Code Scanner Wedge (optional) (p/o E3786A)
6 A4032A 17-inch Monitor
7 1250-0781 BNC 'T'
1250-0207 50-ohm Load/Termination
1252-1650 Hook & Loop Insulator (protects 'T' from accidental grounding)
8 A4030D Keyboard and mouse
9 E4000-37900 SCSI/RS-232 w/E4000-37911 pwr sup, SCSI-2 cable (p/o E3788A)
10 A2656A DDS Drive with power supply
11 A1658-62016 SCSI Terminator
12 E2050A LAN/GPIB Gateway with power supply
Figure 5-1 712/60/100 Controller details — Series II (See Table 5-1 on page 5-2)
Testhead - Control Cards
Mod 3 Mod 2 Mod 1 Mod 0
A A A A
DUT P.S.
Series II
DUT P.S.
System Card
03066-66581
Modem
ABCDE F
B 1
J 2
DUT P.S. 7
Footswitch
"T" &
C
Load G
7 D
712 Controller To Site LAN
LAN/HP-IB 12 S
3
4 7
E
F L "T" &
R Load
P P 10
3 K DDS Drive
4
"T" & 7
Load Monitor 11
H Mouse 8
6 8 1
Strip I 9
Printer BCS 5
8 M
Terminals M
Keyboard N
712-1.WPG N
UNIX Controller Cabling Diagrams: 725/50 Controller
725/50 Controller See Figure 5-2 on page 5-7.
Table 5-2 725/50 Controller cables and devices — Series II

B 8120-6713 Footswitch Extender Cable, RJ111
C 8120-5371 LAN Cable, BNC to BNC, 5-meter
D 8120-3447 GPIB Cable, 4-meter
E 8120-3445 GPIB Cable, 1-meter
F 8120-6730 LAN AUI Extension Cable, BNC to BNC, 1-meter
I A4251-62001 Monitor Cable
J Line Printer Cable (supplied by customer)
K Keyboard Cable (with keyboard)
L 46083-61601 Bar Code Reader Cable
M Mouse Cable (with mouse)
N E4000-61613 SEU-CRJC MUX Cable and 92224M adapter
Not supported on HP-UX 10.2; see (10) and (M) on C110 controller
O 03066-61640 Video Extension Cable, 10 ft.
P Footswitch Cable (with footswitch)
Table 5-2 725/50 Controller cables and devices — Series II (continued)

1 44902-60000 Footswitch1
5 E1016A Bar Code Reader
6 A4251A Monitor
7 A2205B Keyboard and Mouse
8 1250-0781 BNC 'T'
9 50759B Modem (supplied by the local Agilent field office)
1. Prior to software rev. B.02.00, the footswitch was connected to an Agilent 46094A Quad Box for the Series I system.
Figure 5-2 725/50 Controller details — Series II (See Table 5-2 on page 5-5)

A A A A
DUT P.S.
Series II
System Card
03066-66581
DUT P.S.
8
ABCDE F
"T" & E
Load
C DUT P.S.
B D
Footswitch
P 2 Adapter
1
N
725/50 PPU Button Adapter
To Site LAN Controller N
Board Handler BCR
Board Handler
N
"T" & 8
O Load J Line
"T" & 3 Printer
F
Load 4
8
G I 6
Monitor
9 Modem 5 7
L M
H K BCR Mouse
7
Strip
Printer Keyboard
725 1 WPG
725/100 Controller See Figure 5-3 on page 5-10.
Table 5-3 725/100 Controller cables and devices — Series II

D 8120-3447 GPIB Cable, 4-meter (with Agilent 10834A GPIB Conn. Extender)
I A2300-60005 Monitor Cable
J Line Printer Cable (supplied by customer)
K Keyboard Cable (with keyboard)
L 8120-6751 Bar Code Scanner Cable
M Mouse Cable (with mouse)
N E4000-61613 SEU-CRJC MUX Cable and 92224M adapter
Not supported on HP-UX 10.2; see (10) and (M) on C110 controller
O 03066-61640 Video Extension Cable, 10 ft.
P Footswitch Cable (with footswitch)
Table 5-3 725/100 Controller cables and devices — Series II (continued)
R A4022-62003 Keyboard Adapter Module Cable

1 44902-60000 Footswitch
6 A4032A Monitor
7 A2839A Mouse
8 1250-0781 BNC 'T'
9 50759B Modem (supplied by the local Agilent field office)
10 A2840A Keyboard
11 A4022-62005 Keyboard Adapter Module
Figure 5-3 725/100 Controller details — Series II (See Table 5-3 on page 5-8)

A A A A
DUT P.S.
Series II
System Card
03066-66581
DUT P.S.
8
ABCDE F
"T" & E
Load
C DUT P.S.
B D
Footswitch
P 2 Adapter
1
N
725/100 PPU Button Adapter
To Site LAN Controller N
Board Handler BCR
Board Handler
N
"T" & 8
Load J Line
"T" & 3 O R Printer
F
Load 4
8 I
G
11 5
9 Modem 6 L
M BC
H K
Monitor
Strip Mouse 7 Keyboard
10
Printer
725-2.WPG
UNIX Controller Cabling Diagrams: C110 Controller
C110 Controller See Figure 5-4 on page 5-13.
Table 5-4 C110 Controller cables and devices — Series II

D 8120-3447 GPIB Cable, 4-meter (with Agilent 10834A GPIB Conn. Extender)
I D2800-80006 Monitor Cable, 15-pin VGA (C2300-60005 can also be used)
J Keyboard Cable (with keyboard)
K 8120-6751 Bar Code Scanner Cable
L Mouse Cable (with mouse)
P 03066-61640 Video Extension Cable, 10 ft.
R Footswitch Cable (with footswitch)
S 8120-6794 Keyboard / Mouse Extension cable
Table 5-4 C110 Controller cables and devices — Series II (continued)

1 44902-60000 Footswitch
6 A4490A Monitor
7 A2839B Mouse
8 1250-0781 BNC 'T'
9 A2840B Keyboard
Figure 5-4 C110 Controller details — Series II (See Table 5-4 on page 5-11)

A A A A
DUT P.S.
Series II
System Card
03066-66581
DUT P.S.
ABCDE F
"T" & E
Load 8
D DUT P.S.
R B
Footswitch C
Adapter 2
1
1 HP-IB Modem
C110 2 Empty
3 LAN 8 G
Controller 4 Graph
To Site LAN
8 10 1 11
"T" &
H
F Load
P S 3
S 8
M PPU Button Adapter 4
Terminals I
M Board Handler Strip
N N Board Handler BCR Printer 5
K
L BCS
6 J K
Monitor
Mouse 7 Keyboard 9
C110-1.WPG
UNIX Controller Cabling Diagrams: B180L Controller
B180L Controller See Figure 5-5 on page 5-16.
Table 5-5 B180L Controller cables and devices — Series 3 / 79000

B 8120-6713 Footswitch Extension Cable, RJ-11
C 8120-8728 LAN Cable, RJ-45 to RJ-45
D E9927-61607 4-meter GPIB Cable (for TAMS 70488-10 card)
E 8120-3445 1-meter GPIB Cable
F 8120-6730 LAN AUI Extension Cable, AUI to BNC, 1-meter
J 8120-6861 Video Adapter Cable
K 03066-61640 Video Extension Cable (1 for 327X / 79000, 2 for 307X / 317X)
L D2800-80006 Video Cable
P 8120-6794 Keyboard / Mouse Extension Cable
R 8120-5371 6-meter LAN Cable, BNC to BNC (for 307X and 317X) or . . .
8120-3543 2-meter LAN Cable, BNC to BNC (for 327X and 79000)
Table 5-5 B180L Controller cables and devices — Series 3 / 79000 (continued)
S E4000-61630 LAN Cable, BNC to SMB for ControlXT/XTP Cards

T E4000-61629 LAN Cable, SMB to SMB for ControlXT/XTP Cards
U 2 ea. 8120-1763 (327X and 79000) or
8120-1763 + 8120-4188 (307X and 317X)
power cords
6 E9900-69301 NEC MultiSync LCD Flat Panel Display
7 1250-0781 BNC 'T'
1250-0207 50-ohm BNC Load/Termination
1250-2076 50-ohm SMB Load/Termination
8 A4030E Keyboard and Mouse
11 E9900-68700 J3128A AdvanceStack 10Base-T Hub-8E with 0950-3612 power supply
Figure 5-5 B180L Controller details — Series 3 / 79000 (See Table 5-5 on page 5-14)
Testhead - ControlXT Cards
T 7
S
A DUT P.S.
Series II/3 / 79000

System Card DUT P.S.
03066-66581
ABCDE F E
DUT P.S.
R 11
1
Hub D
C
Footswitch B 7
2 Modem
G
B180L
Parallel
Printer
To Site LAN
10
8 9 1 J F
3
7
4
K P P "T" & Load
M PPU Button Adapter
Terminals L H Strip
M Board Handler
N N Board Handler BCR
Printer
5
I
P.S. BCS
U 6 Monitor
Mouse 8 Keyboard
8
B180L-1.WPG
C240 Controller See Figure 5-6 on page 5-19.
Table 5-6 C240 Controller cables and devices — Series 3 / 79000

D E9927-61607 4-meter GPIB Cable (to TAMS card)
F 8120-6730 LAN AUI Extension Cable, AUI to BNC, 1-meter
J 8120-6861 Video Adapter Cable
R 8120-5371 6-meter LAN Cable, BNC to BNC (for 307X and 327X) or . . .
8120-3543 2-meter LAN Cable, BNC to BNC (for 327X and 79000)
Table 5-6 C240 Controller cables and devices — Series 3 / 79000

U 2 ea. 8120-1763 (327X and 79000) or 8120-1763 + 8120-4188 (307X and 317X)
power cords
6 E9900-69301 NEC MultiSync LCD Flat Panel Display
7 1250-0781 BNC 'T'
8 A4030E Keyboard and Mouse
11 E9900-68700 J3128A AdvanceStack 10Base-T Hub-8E with 0950-3612 power supply
Figure 5-6 C240 Controller details — Series 3 / 79000 (See Table 5-6 on page 5-17)

T 7
S
A DUT P.S.
Series II/3 / 79000

System Card DUT P.S.
03066-66581
AB CDE F E
DUT P.S.
R 11
1
Hub D
B C
Footswitch 7
2 G Modem
C240 To Site LAN

J F
3
7
10 4
8 9 1 K
"T" & Load
Parallel
P Printer
M PPU Button Adapter
Terminals H Strip
M Board Handler
N N Board Handler BCR
Printer
5
L I
P.S. BCS
U 6 Monitor
Mouse 8 8
C240-1.W PG
Keyboard
UNIX Controller Cabling Diagrams: B2000 Controller
B2000 Controller See Figure 5-7 on page 5-22.
Table 5-7 B2000 controller (A5983A) cables and devices — Series 3 / 79000 UNIX

D E9927-61607 4-meter GPIB Cable (for TAMS 70488-10 card)
F 8120-6773 LAN Cable (pod/bulkhead connector = 8121-0572)
G not used
I 0960-2151 Bar Code Scanner Cable (including scanner)
M 8120-6773 RJ-45 Cable, shielded, 4-meter plus:
E9970-63200 DB-9 adapter for PPU button adapter
E4000-62106 DB-25 adapter for board handler
E4000-62105 DCE adapter for board handler bar code reader
N 1150-7834 Y-mouse WHYM-0008 Keyboard and Mouse Adapter for USB
R 8120-3543 2-meter LAN Cable, BNC to BNC
Table 5-7 B2000 controller (A5983A) cables and devices — Series 3 / 79000 UNIX (continued)

U 2 ea. 8120-1763 (327X and 79000) or 8120-1763 + 8120-4188 (307X and 317X)
V 8121-1045 SCSI cable supplied with E3788 SCSI-MUX box
3 8121-0572 Pod/bulkhead connector
4 E9900-69302 NEC MultiSync 1525M LCD Flat Panel Display
5 A4030G/ABA Keyboard kit
6 Mouse
7 1250-0781 BNC T
7 1250-0207 50-ohm BNC Load/Termination
7 1250-2076 50-ohm SMB Load/Termination
7 1252-1650 Hook & Loop Insulator (protects T from accidental grounding)
9 E4000-37900 E3788 SCSI-MUX box with E4000-37911 power supply
11 E9900-68700 1150-7852 10Base-T Ethernet Hub with 0950-3612 power supply
Figure 5-7 B2000 controller details — Series 3 / 79000 UNIX (See Table 5-7 on page 5-20)
Footswitch 1
T 7 A DUT P.S.
S
2
Series II/3 / 79000 DUT P.S.
System Card
B
03066-66581
DUT P.S.
AB C DE F
E
R DUT P.S.
D
DAT V
P.S. DAT M
1 PPU Button Adapter
Board Handler
B2000 Controller 9 Board Handler BCR
(UNIX)
Terminals
10
1 8
USB
11 Line
1 2 3 4 2
Hub Printer
7 C L F
K 3 To Site LAN
2 P
N
4
BCR
H 1 P
Port 1 6 5
Monitor Strip reserved
Printer for UPS Mouse Keyboard
B2000.WPG
C3600 Controller See Figure 5-8 on page 5-25. .
Table 5-8 C3600 controller cables and devices — Series 3 / 79000

C 8120-8728 LAN Cable, 1-meter, RJ-45 to RJ-45
D 8120-3447 4-meter GPIB Cable
F 8120-6773 LAN Cable (pod/bulkhead connector = 8121-0572)
G not used
I Bar Code Scanner Cable
M 8120-6773 RJ-45 Cable, shielded, 4-meter plus:
E9970-63200 DB-9 adapter for PPU button adapter
E4000-62106 DB-25 adapter for board handler
E4000-62105 DCE adapter for board handler bar code reader
N 1150-7834 Y-mouse WHYM-0008 Keyboard and Mouse Adapter for USB
R 8120-3543 2-meter LAN Cable, BNC to BNC
Table 5-8 C3600 controller cables and devices — Series 3 / 79000 (continued)

U 2 ea. 8120-1763 (327X and 79000) or 8120-1763 + 8120-4188 (307X and 317X)
V 8121-1045 SCSI cable supplied with E3788 SCSI-MUX box
3 8121-0572 Pod/bulkhead connector
4 E9900-69302 NEC MultiSync 1525M LCD Flat Panel Display
5 A4030G/ABA Keyboard kit
6 Mouse
7 1250-0781 BNC T
1252-1650 Hook & Loop Insulator (protects T from accidental grounding)
9 E4000-37900 E3788 SCSI-MUX box with E4000-37911 power supply
11 E9900-68700 1150-7852 10Base-T Ethernet Hub with 0950-3612 power supply
Figure 5-8 C3600 controller details — Series 3 / 79000 UNIX (See Table 5-8 on page 5-23)
Testhead - ControlXT/XTP Cards
Footswitch 1
T 7 A DUT P.S.
S
2
Series II/3 / 79000 DUT P.S.
System Card
B
03066-66581
DUT P.S.
AB C DE F
E
R DUT P.S.
D
DAT V
P.S. DAT M
1 PPU Button Adapter
Board Handler
C3600 Controller 9 Board Handler BCR
(UNIX)
Terminals
10
1 8
USB
11 Line
1 2 3 4 5 6 2 Wide SCSI
Hub Printer
7 C
L F
3 To Site LAN
2 P
N
4 K BCR
H 1 P
Port 1 6 5
Monitor Strip reserved
Printer for UPS Mouse Keyboard
C3600.WPG
E4000-90300 Rev. J Printed in Singapore
11/2003

3070 / 79000 Board Test Systems: System Installation Manual (UNIX Version) November 2003

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3070 / 79000 Board Test Systems: System Installation Manual (UNIX Version) November 2003

Enviado por

Direitos autorais:

Formatos disponíveis

3070 / 79000 Board Test Systems

System Installation Manual (UNIX Version)

1 UNIX System Installation Procedure

© Agilent Technologies 1998–2003 i

Setting Up the Testhead Controller ........................................................................................... 1-19

2 UNIX System Installation Reference

3 UNIX Device Files – C240 and Earlier

712/60/100 Controller.................................................................................................................. 3-4

4 UNIX Device Files – B2000 and Later

5 UNIX Controller Cabling Diagrams

NOTE Uncrating the system is the responsibility of the Agilent

Tools Needed for Installation

■ T20 Torx driver

How to Make IP Addresses Match

1 Change the IP addresses of each system using the

Preparation Identifying the System Checking for Shipping Damage

Bags on the rear of the cradle: Verifying the Site Preparation

Un-securing the Monitor, Keyboard, Mouse,

4 Using a 1/4-inch hex key wrench, remove two screws

Figure 1-2 Installing the support arms

Arm Tension Top View

16 If the system includes an optional bar code scanner,

Figure 1-3 Mounting and cabling the monitor

20 Proceed to Adjusting the Support Arms on

Adjusting the Support Arms

Figure 1-4 Ajusting the support arms

Arm Vertical Tension Monitor

1 For a 3070 Series 3 system, unpack the strip printer

79000 system does not include a strip printer tray.

Connecting the Compressed Air Supply to the

The probe cradle (Figure 1-7) is located on the left pod

✸Do not place the probe cradle where it could

1 Peel the backing paper off the hook-and-loop

Installing the Serial Label

Figure 1-8 Serial label

Table 1-1 LAN configuration information

Item Your Specific System Information Description

Table 1-1 LAN configuration information (continued)

Item Your Specific System Information Description

Umbilical Cable with DUT Power Supply and Functional

Figure 1-9 Cabling to the support bay (rear view)

Module Door Locking Bracket Vacuum Manifold

HP-IB Route the PDU Branch Control Cable Clamp Panel

4 Connect the white triaxial cable to the functional

Figure 1-10 ASRU card connections (rear view)

03066-66532 ASRU Card

ASRU_CON.WPG Red band

PDU Branch Control Wires AccessPlus Cables

Support Bay Power Cords

Installing the Vacuum Manifold

1 Look at the vacuum hardware on the testhead and

The vacuum ports are where the vacuum manifold or

Figure 1-11 Internal vacuum solenoids in a 4-module series 3 testhead

80-PSI Regulator Vacuum Valve

Vacuum components below the dotted line are customer

Manual Cut-off Valve 2-inch Vacuum Hose vac4_S3new.wpg

5 Verify that you can switch vacuum on and off; type:

If the vacuum control doesn’t work, check:1

Setting Up Other System Printer / Plotter

Pay-Per-Use Button Adapter

Figure 1-12 Pay-Per-Use button adapter hardware in the left pod

Right Pod, cover removed

Figure 1-13 Installing Pay-Per-Use buttons