3070 / 79000 Board Test Systems - Keysight / 79000 Board Test Systems System Installation Manual ... This chapter describes the installation of the Agilent 3070 Series 3 and 79000

3070 / 79000 Board Test SystemsSystem Installation Manual (UNIX Version)

November 2003

© Agilent Technologies 1998�2003 i

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

1 UNIX System Installation ProcedureIf You Need Help................................................................................................................... 1-1Uncrating the System............................................................................................................. 1-1

Testhead IP Address Changes with B.03.80................................................................................ 1-3Audience and Purpose ........................................................................................................... 1-3What Does This Mean for Existing Systems Not at B.03.80?............................................... 1-3How to Make IP Addresses Match ........................................................................................ 1-3Implications for Custom Applications ................................................................................... 1-4B.03.80 Update and Ignite Notes........................................................................................... 1-4

Preparation ................................................................................................................................... 1-5Identifying the System........................................................................................................... 1-5Checking for Shipping Damage............................................................................................. 1-5Verifying that the Shipment is Complete .............................................................................. 1-5Verifying System Power........................................................................................................ 1-6Verifying the Site Preparation ............................................................................................... 1-6

Installing Testhead Hardware ...................................................................................................... 1-7Installing the Monitor, Keyboard, Mouse, Support Arms ..................................................... 1-7Removing the Testhead Shipping Bolts............................................................................... 1-14Stabilizing the Testhead....................................................................................................... 1-15Installing the Strip Printer and Tray .................................................................................... 1-15Installing the Footswitch...................................................................................................... 1-16Connecting the Site LAN Cable to the Controller ............................................................... 1-16Connecting the Compressed Air Supply to the Testhead .................................................... 1-16Install the Probe and Probe Cradle ...................................................................................... 1-17Installing the Fixture Pull-Down Label ............................................................................... 1-17Installing the Serial Label .................................................................................................... 1-18

© Agilent Technologies 1998�2003 Agilent 3070 / 79000 System Installation (UNIX Version) ii

Table of Contents

Setting Up the Testhead Controller ........................................................................................... 1-19Planning For the LAN Installation....................................................................................... 1-19Turning on the PDU............................................................................................................. 1-21Turning on the Monitor and Controller ............................................................................... 1-21Setting up the Controller LAN and HP-UX Start-up........................................................... 1-21

Setting Up the Testhead............................................................................................................. 1-23Rotating the Testhead ......................................................................................................... 1-23Cabling the Support Bay to the Testhead (307X System Only) .......................................... 1-23Installing the Vacuum Manifold .......................................................................................... 1-27

Verifying the Testhead............................................................................................................... 1-28Booting the Testhead ........................................................................................................... 1-28Verifying the config File (Pre-Shipped Controllers Only) .................................................. 1-28Running AutoAdjust All ...................................................................................................... 1-29Running Full Diagnostics .................................................................................................... 1-29Setting Up and Verifying the Strip Printer .......................................................................... 1-29Verifying the Vacuum Subsystem ....................................................................................... 1-30

Setting Up Other Hardware ....................................................................................................... 1-34System Printer / Plotter ........................................................................................................ 1-34Pay-Per-Use Button Adapter ............................................................................................... 1-34PR PLUS.............................................................................................................................. 1-39POTS (Plain Old Telephone Services) Bay......................................................................... 1-41Instrument Rack ................................................................................................................... 1-41Setting up the Testhead for Automation .............................................................................. 1-43EFS Board Handler ............................................................................................................. 1-44

Completing the Installation........................................................................................................ 1-45Reinstalling the Pod Covers................................................................................................. 1-45Making a System Recovery Tape ........................................................................................ 1-45Making a System Backup Tape ........................................................................................... 1-45Turning System Administration Over to the Customer ....................................................... 1-45Filling Out the System Support Log .................................................................................... 1-46Installation Billing Information ........................................................................................... 1-46

© Agilent Technologies 1998�2003 Agilent 3070 / 79000 System Installation (UNIX Version) iii

Table of Contents

2 UNIX System Installation ReferenceFile System Changes With HP-UX 10.2X (B.03.XX) ................................................................ 2-2Installing and Reviewing Codewords .......................................................................................... 2-4The Configuration Files ............................................................................................................... 2-5

The System Config File ......................................................................................................... 2-5The Standard Config File..................................................................................................... 2-14

The BT-BASIC Editor ............................................................................................................... 2-26Starting the BT-BASIC Editor............................................................................................. 2-26Using the BT-BASIC Editor................................................................................................ 2-27Exiting the BT-BASIC Editor.............................................................................................. 2-28

HP-UX Quick Reference ........................................................................................................... 2-29vi Editor Quick Reference ......................................................................................................... 2-32Troubleshooting ......................................................................................................................... 2-35

Switch Settings .................................................................................................................... 2-35Controller Start-Up Problems .............................................................................................. 2-42Determining the IP Address................................................................................................. 2-42Determining the Hardware Address .................................................................................... 2-42Testhead LAN ..................................................................................................................... 2-42Manually Setting the Local Time Zone & System Time..................................................... 2-49Verify the Plan For the LAN Installation ............................................................................ 2-50Set Up the LAN Software.................................................................................................... 2-50Test the Network.................................................................................................................. 2-51

Miscellaneous ............................................................................................................................ 2-52Rotating the Testhead Without PDU Power ........................................................................ 2-52Moving the Controller to the Right Pod ............................................................................. 2-54

3 UNIX Device Files � C240 and EarlierRebuilding Device Files at B.03.81 or Later ............................................................................... 3-2

Process for Rebuilding Device Files...................................................................................... 3-2Example for Recreating a Device File ................................................................................... 3-2

© Agilent Technologies 1998�2003 Agilent 3070 / 79000 System Installation (UNIX Version) iv

Table of Contents

712/60/100 Controller.................................................................................................................. 3-4725/50 Controller ......................................................................................................................... 3-8725/100 Controller ..................................................................................................................... 3-13C110 Controller ......................................................................................................................... 3-18B180L Controller ....................................................................................................................... 3-22C240 Controller ......................................................................................................................... 3-26

4 UNIX Device Files � B2000 and LaterRebuilding Device Files at B.03.81 or Later ............................................................................... 4-2

Process for Rebuilding Device Files...................................................................................... 4-2Example for Recreating a Device File ................................................................................... 4-2

B2000 Controller ......................................................................................................................... 4-4C3600 Controller ......................................................................................................................... 4-8

5 UNIX Controller Cabling Diagrams712/60/100 Controller.................................................................................................................. 5-2725/50 Controller ......................................................................................................................... 5-5725/100 Controller ....................................................................................................................... 5-8C110 Controller ......................................................................................................................... 5-11B180L Controller ....................................................................................................................... 5-14C240 Controller ......................................................................................................................... 5-17B2000 Controller ....................................................................................................................... 5-20C3600 Controller ....................................................................................................................... 5-23

© Agilent Technologies 1998�2003 Agilent 3070 / 79000 System Installation (UNIX Version) 1-1

1111 UNIX System Installation ProcedureE4000-90300 Rev. J 11/2003

In this Chapter... � Testhead IP Address Changes with B.03.80, 1-3

� Preparation, 1-5

� Installing Testhead Hardware, 1-7

� Setting Up the Testhead Controller, 1-19

� Setting Up the Testhead, 1-23

� Verifying the Testhead, 1-28

� Setting Up Other Hardware, 1-34

� Completing the Installation, 1-45

This chapter describes the installation of the Agilent 3070 Series 3 and 79000 board test systems with a UNIX controller. If you are installing a system with a MS Windows (PC) controller, use the Agilent 3070 System Installation (WN Version) (E9970-90001).

NOTEThis system should be installed only by an Agilent 3070 / 79000 service-trained customer engineer (CE) who is familiar with running the Diagnostic software and troubleshooting the system.

If You Need Help If you need help installing the system, contact Agilent�s Measurement Systems Knowledge Center (MSKC). In the U.S. call 1.800.593.6635 with your MSKC support handle. Outside the U.S. call your local Agilent Service Representative to access the MSKC. For help with system administration or LAN problems, call MTD Customer Technical Support at 1.800.447.TEST.

If you are installing a Test Server, refer to the Agilent 3070 Series 3 / 79000 Family System Administration Guide (E9900-90000) which is online. If the testhead includes the optional Agilent Performance Port ACS (Actuator Control System) for switching compressed air to the test fixture, refer to the Agilent Performance Port Manual (E3700-90000) for the ACS installation.

Uncrating the SystemUncrating the system is the responsibility of the Agilent customer engineer. After removing the outer cardboard box from the system pallet, you will find instructions for uncrating the system attached to the pallet ramp. Use a cordless electric drill with appropriate sockets and extensions to make the uncrating process go much quicker.

Tools Needed for InstallationYou will also need:


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

Testhead IP Address Changes with B.03.80

NOTEThis section contains important installation information. Read this before installing the system.

Audience and PurposeBecause of the Hewlett-Packard/Agilent Technologies split, 3070 Board Test systems are no longer shipped with testhead LAN IP addresses in the 15.3.112.* series.

Beginning with systems shipped with B.03.80 software, and systems updated or ignited with B.03.80 software, the testhead�s IP addresses will be in the 10.3.112.* series.

This should not cause any networking problems because the systems are configured to use local hosts for testhead IP address resolution. This is accomplished by creating a new /etc/nsswitch.conf file or modifying an existing /etc/nsswitch.conf file to look at the local /etc/hosts file first when doing testhead IP address resolution.

NOTEYou should cycle power on the testhead after performing an update or ignite to B.03.80.

NOTEThose who use NIS or DNS for testhead IP address resolution should be aware that this method forces the system to look at local hosts first. If these users encounter problems, they should ensure that the nsswitch.conf file is configured correctly to support their NIS or DNS networking implementation.

What Does This Mean for Existing Systems Not at B.03.80?

Using Local Hosts for Existing SystemsIf you have not changed your method of name resolution, and you are using local hosts, you are not affected by this change. You can run systems that have the new 10.3.112.* IP address in the same network as systems with the old 15.3.112.* address without any conflicts.

Using a Nameserver for Existing SystemsIf you are using a nameserver for name resolution, we recommend, but do not require, that all IP addresses match. This means they should all use the 10.3.112.* IP address convention.

How to Make IP Addresses MatchChange 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. Modify the /etc/bootptab, /etc/rc.config.d/netconf, and /etc/hosts files (see B.03.80 Update and Ignite Notes below for examples).

2 Update the IP addresses on the nameserver itself.

NOTEOnly 3070 testhead IP addresses in the 10.3.112.* format are supported by Agilent.

Implications for Custom ApplicationsIf there are any custom applications that are hard-coded to look for a 15.3.112.* address, they must be modified to look for a 10.3.112.* address.

B.03.80 Update and Ignite NotesBecause B.03.80 software configures the system with testhead IP addresses in the 10.3.112.* series, you should use caution if you use the practice of saving critical files and then restoring the files after completing a software update or ignite.

If you use this practice, verify that the IP addresses of the testhead and all modules in the /etc/bootptab, /etc/rc.config.d/netconf, and /etc/hosts files are modified to map to the 10.3.112.* addresses.

Here are some file examples:# Example from /etc/hosts10.3.112.4 module0

# Example from /etc/bootptabmodule0:\

ht=ether:\vm=rfc1048:\ha=0060B0B215A5:\sm=255.255.248.0:\ip=10.3.112.4

# Example from /etc/rc.config.d/netconfRARPD=0IP_ADDRESS[1]=10.3.112.1SUBNET_MASK[1]=255.255.248.0INTERFACE_NAME[1]=lan1BROADCAST_ADDRESS[1]=10.3.119.255LANCONFIG_ARGS[1]=”ether”DHCP_ENABLE[1]=0

An /etc/nsswitch.conf file will be added to ensure that the /etc/hosts file is used first for name resolution. If the /etc/nsswitch.conf file already exists, it will be modified so that the /etc/hosts file is used first. An example follows:# Example from /etc/nsswitch.confhosts: files [NOTFOUND=continue] dns

NOTEIf you have addresses on your public LAN in the 10.3.112.* range, and you experience address conflicts, contact your Agilent support representative.


UNIX System Installation Procedure: Preparation

Preparation Identifying the System The Agilent 3070 / 79000 system is available with different types of testheads and controllers. Because of these differences, there are slight variations in the installation process.

� The testhead may have 1-, 2-, or 4-module capacity.

� The testhead may have one or two pods (only the 79000 has two pods; all other testheads have only a right pod)

� The testhead may include a VXI cardcage (79000 only).

� The system may include a support bay.

� The vector application rate may be 6, 12, or 20 megapatterns per second (MP/s).

A label on the lower right corner of the testhead�s cradle, when viewed from the rear, indicates the Common Testhead Product Number, which defines the module capacity. Identifying 6-MP/s, 12-MP/s, or 20-MP/s is most efficiently done by reviewing the sales order or the paperwork sent with the system.

Checking for Shipping Damage Inspect the system for damage. If you think there has been damage, contact Agilent�s Manufacturing Test Division, Order Administration (970.679.2261).

Verifying that the Shipment is Complete Check the contents of all crates and boxes against the order form from the customer. Many of the accessories and miscellaneous items like the strip printer, tape cartridges, licenses, and documentation are shipped in separate boxes.

Also check the contents of all bags attached to the rear of the testhead (you got this manual and a Site Preparation Manual from one of the bags).

Bag on the rear of the right pod:

� Pod key

� Probe cradle

� Certificates of Calibration

� Certificate of the Hardware Address for the System Card

� System Data Sheet

� Configuration printouts


UNIX System Installation Procedure: Preparation

Bags on the rear of the cradle:

� Vacuum fittings

� Compressed air fitting

� Installation kit (03066-69902) with various tools and parts (parts list included)

Verifying System Power 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.

NOTEIf 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).

Verifying the Site Preparation Review the customer�s completed Site Prep Checklist from the Agilent 3070 / 79000 Site Preparation Manual. Ask the customer for a copy of the System Plan Drawing or have them select the appropriate layout from Chapter 3 of the Site Preparation Manual. Satisfy yourself that preparations are complete before proceeding.


UNIX System Installation Procedure: Installing Testhead Hardware

Installing Testhead Hardware

Installing the Monitor, Keyboard, Mouse, Support Arms The monitor, keyboard, mouse, and support arms may or may not have already been installed from the factory, so there are three possible scenarios for installing these devices:

� Scenario A: If they are already installed and the customer likes them on the right side of the testhead (the default side), all you have to do is un-secure them. Proceed to Un-securing the Monitor, Keyboard, Mouse, Support Arms on page 1-7.

� Scenario B: If they are already installed but the customer wants them on the left side of the testhead instead of the right side, proceed to Un-securing the Monitor, Keyboard, Mouse, Support Arms on page 1-7 and then to Moving the Monitor, Keyboard, Mouse, Support Arms on page 1-7.

� Scenario C: If they are not already installed, proceed to Installing the Monitor, Keyboard, Mouse, Support Arms on page 1-9.

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.

If you are leaving them on the right side of the testhead, free them, unpack them, and extend the support arms to the approximate positions in which they will be used. Then proceed to Adjusting the Support Arms on page 1-13.

Moving the Monitor, Keyboard, Mouse, Support Arms If the customer wants the support arms on the left side of the testhead, move them as described below. The monitor, keyboard and mouse are all connected with extension cables coiled inside the right pod so you can move these devices to the left side of the testhead.

1 Open the pod door (the key is in a bag attached to the rear of the pod).

2 Using a T20 Torx driver, remove 5 screws and remove the right pod cover. Using a 5-millimeter hex key wrench, remove two screws and remove the left side cradle cover (if the testhead is a 79000 remove the left pod cover).

3 Disconnect the monitor power supply�s power cord and the monitor, keyboard and mouse cables from their extension cables inside the right pod.



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

Monitor(Flat Panel Display)

S3ARM1.WPG

Top View of Support Arm Mount

('T' piece)

Monitor Arm(top and rear) Keyboard Arm

(bottom and front)

KeyboardMouse

Post Screw Holes Use top and bottom for 307X or 317X,middle and bottom for 327X or 79000

'T' piece post inside column

Cables

Left sideof testhead

Riser underMonitor Arm

'T' piece



5 Move the support arm mount (T piece) and assembly to the left column. The T piece should protrude from the side of the testhead, not the front of the testhead.

CAUTION

✸The assembly is awkward to move with the devices attached, so unless you have help moving it, you should remove all devices from the support arm trays before moving the support arm assembly.

6 Reinstall the two screws in the support arm post in the left column. Position the support arm mount (T piece) so it extends to the left or to the front from the testhead. For 307X and 317X testheads, use the top and bottom screw holes; for 327X and 79000 testheads, use the middle and bottom screw holes.

7 Switch the support arm locations on the T piece so that the monitor support arm with the riser is in the rear hole, farthest from the operator position.

8 Replace the monitor, keyboard and mouse on the support arm trays if you removed them.

9 Reroute the monitor, keyboard and mouse extension cables from the right pod, across the rear cable trough, to the left side of the testhead.

10 Reconnect the cables to the extension cables in the left side of the cradle (or the left pod if it is a 79000 testhead).

11 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 support arm cable troughs.

12 Ensure that all cables are dressed properly, and use cable ties to secure the cables in place.

13 Replace the pod or cradle side covers.

14 Install the square plastic cap in the top of the right support arm column.

15 Place the plastic keyboard overlay (E4000-84404) on the keyboard.

16 Proceed toAdjusting the Support Arms on page 1-13.

Installing the Monitor, Keyboard, Mouse, Support Arms If the monitor, keyboard, mouse and support arms are not already installed on the testhead, perform the following steps.

1 Determine which side of the testhead the customer wants the support arms located.

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 the pod).

b If it�s on the left side, remove the right pod cover, but also remove the left side cradle cover (use a 5-millimeter hex key wrench).

2 Unpack the support arms and the monitor and keyboard trays (see Figure 1-2 on page 1-11 for the following steps).



3 Insert the post of the support arm mount (T piece, E9900-10245) in the column. Position the support arm mount so it extends to the right or left or to the front from the testhead. Secure the post in the column using a 1/4-inch hex key wrench and two each cap screws (3030-1044) and lock washers (2190-0963). For 307X and 317X testheads, use the top and bottom screw holes; for 327X and 79000 testheads, use the middle and bottom screw holes.

4 Insert the extension (riser, E9900-10246) in the hole of the T piece that is farthest from the operator.

5 Insert the monitor support arm (E9900-10250) in the riser.

6 Install the monitor tray (E9900-10260) on the monitor support arm using a Phillips screwdriver and four flat-head screws (3030-0219, in the end of the arm).

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

blade screwdriver, tighten the two hold-down screws over the rear edge of the monitor base (Figure 20 on page 1-12).

10 Unpack the keyboard and mouse and place them on the keyboard tray.

11 Using diagonal cutters, cut the cable ties to free the cables in the right pod.

12 If the support arms are on the left side of the testhead, route the power cord and the keyboard and mouse extension cables through the cable trough across the rear of the testhead cradle, and up the left side of the testhead to the support arms.

13 Route the cables through the cable troughs on the support arms. If the cable troughs are not pre-installed on the support arms, install them as shown in Figure 1-2 on page 1-11 (note the lengths: S=short, M=medium, L=long).



Figure 1-2 Installing the support arms

14 Remove cover from the rear of the monitor (flat panel display) and connect the power cable and signal cable (Figure 1-3 on page 1-12). Connect the monitor power cord from the monitor power supply. Replace the cover.

15 Connect the monitor, keyboard, and mouse cables to the extension cables.


S3ARM2.WPG

Arm TensionAdjustments(1/4-inch hex)

Top View

Monitor Armon topKeyboard Arm

on bottom

Keyboard Mouse

Keyboard TrayTilt Adjustment

'T' piece post inside column

Cables TroughsShort, Medium, Long

Support Arm Mount('T' piece)

Right Pod

Riser underMonitor Arm

Post Screw Holes Use top and bottom for 307X or 317X,middle and bottom for 327X or 79000

S

L

L

M

M



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

20 Proceed to Adjusting the Support Arms on page 1-13.

Monitor hold-down screws

FPDCABLE.WPG

Cover



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

Removing the Testhead Shipping Bolts Using a 5/16-inch hex key wrench (in the bag attached to the rear of the testhead), remove the two shipping bolts from the cradle. The shipping bolts and shipping

brackets are under each side of the rear of the testhead (see Figure 1-5 on page 1-15). These bolts hold the system in the zero-degree position during shipment. Screw the bolts into the threaded holes below the shipping brackets to save them for future shipping use.


S3ARM3.WPG

Arm Vertical TensionAdjustments

(1/4-inch hex)

Keyboard Mouse

Keyboard TrayTilt Adjustment

(knob)

Right Pod

Arm HorizontalAdjustments

(1/16-inch hex)



Stabilizing the Testhead It is important to stabilize the testhead to keep it from moving around. This is especially true if the testhead is in an automated production line. Using a 3/4-inch wrench (in the bag attached to the rear of the testhead), screw the testhead�s four leveling feet down to the floor (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 foot and use a 1/4-inch wrench in the top of the foot to screw it down enough to expose the 3/4-inch hex nut.

Installing the Strip Printer and Tray 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 79000 system does not include a strip printer tray.

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.

5 Locate the strip printer cable coiled under the rear of the testhead cradle (Figure 1-5). Connect it to the strip printer.

Figure 1-5 Locating the strip printer cable (NOTE: The power cord will not be present on most systems)

Strip Printer Cable coiled underrear of testhead

CABLES4A.WPG

Rear Cable Trough

Bags of manualsand parts

Shipping Bolt and Bracket



Installing the Footswitch

NOTEWith software revision 3070 05.20p and later, the footswitch must be connected to the system. The footswitch must be pressed to lock fixtures on the testhead.

Locate the footswitch and cable as shown in Figure 1-6. Place the footswitch on the floor in front of the testhead.

Figure 1-6 Locating the footswitch and leveling foot

Connecting the Site LAN Cable to the Controller 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

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 Transceiver protrudes from the rear of the controller pod, where it is terminated with a BNC T and two 50-ohm loads.1

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 the loads and connect both ports of the BNC T to 50-ohm coaxial cables going to the site LAN. Keep the insulator (1252-1650) over the BNC T.

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 the customer�s existing compressed air hose has the 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. The air supply must be connected before you can test and verify the system.

Footswitch Cable coiledunder front of testhead

Testhead Leveling Foot

1 Part numbers: BNC T (1250-0781); 50-ohm load (1250-0207).



Install the Probe and Probe CradleThe 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).

2 Move the probe cradle to the new location:

a Rotate the cradle sideways to separate the fastener.

b Press the probe cradle firmly onto the hook-and-loop fastener you just installed.

Unpack the probe and insert it in the probe cradle.

Figure 1-7 Probe cradle (E9900-66400)

Installing the Fixture Pull-Down Label If you are installing the system in an English-speaking country, skip this step and proceed to Setting Up the Testhead Controller on page 1-19. If you are installing the system in a non-English-speaking country, locate the packet of Fixture Pull-down Air Labels (E4000-84410). Choose the label that is of the correct language for your 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 TechnologiesManufacturing Test Div.815 14th Street, SWLoveland, CO. 80537USA

MFG:9 2000 9 2002 9 20049 2001 9 2003 9 2005

EXXXXATESTHEAD

S/N USXXXXXXXX

Made in USA ofDomestic and Foreign Parts


UNIX System Installation Procedure: Setting Up the Testhead Controller

Setting Up the Testhead Controller

Planning For the LAN Installation Before turning on the controller, fill out Table 1-1 below. You will need the assistance of the system�s network administrator (or system manager). This is vital information you will need to set up the system for networking. Some of the information may not be needed depending on how your networking is implemented. Even if you don�t intend to put the system on a network

at all, the first two items in the table are still necessary for system set-up. In case of problems, see Troubleshooting on page 2-35. Also he;pful is Administering Agilent 3070 UNIX Systems (UNIX 10.X) shipped both in paper and in the online documentation.

Be sure to read Testhead IP Address Changes with B.03.80 on page 1-3.

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 DNS?

❏ Yes❏ No

DNS, also known as BIND, stands for Domain Name Service. If your network uses DNS and has a DNS server, you will configure DNS.

Will you configure NIS? ❏ Yes❏ No

If your network uses NIS, you will 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.



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

Table 1-1 LAN configuration information (continued)

Item Your Specific System Information Description



Turning on the PDU The Agilent E1135C PDU has two switches.

1 Rotate the large, red, rotary switch1 to the On (1) position. This switch should be left on at all times unless someone is working inside the PDU.

2 Switch the green rocker switch to the On (1) position. This is the switch to use for switching testhead power on and off.

After switching both switches on, you should hear the testhead fans come on.

Turning on the Monitor and Controller First, switch on the monitor (the power switch is located on the right side of the monitor). Then open the right pod door and switch on the computer. This sequencing is done so you will not miss any boot messages that appear on the monitor.

DO NOT touch the keyboard. After several minutes, you should see boot messages on the screen. In the SetSystem Parameters window, you should see:Are you ready to link this system to anetwork?

Click Yes and proceed to Setting up the Controller LAN and HP-UX Start-up.

Setting up the Controller LAN and HP-UX Start-up During the boot process, the system will enter its Start-up routine. It will ask you for the information that you recorded in Table 1-1 on page 1-19.

1 Required Information � When you see:

Do you wish to continue?

Click Yes, Continue. Again, you must have Table 1-1 completed.

2 System Hostname � When you see:

Hostname:____________

Type the hostname (system name) and click OK. You will be asked to confirm your answer.

3 Time Zone � Select your time zone and click OK. You will be asked to confirm your answer.

4 <Region> Time Zone � Select your region time zone and click OK.

5 Confirm Date and Time � You will be asked to confirm the date and time.

6 Root Password � When you see:

Do you want to set the root password at this time?

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:

Internet Address:____________

Get the address from the customer, type the IP address, and click OK. You will be asked to confirm 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.

If the messages ARE NOT OK, troubleshoot as necessary; see Controller Start-Up Problems on page 2-42.

If the messages ARE OK, proceed to Setting Up the Testhead on page 1-23.


UNIX System Installation Procedure: Setting Up the Testhead

Setting Up the Testhead

Rotating the Testhead

WARNING

✸Remove all objects, including the monitor/keyboard support arms, from the rotation path of the testhead. Should the testhead hit a support arm, damage could result.

Open the right pod door and rotate the testhead by pressing the rocker switch inside the pod. Rotate the testhead to the service position. The PDU must be turned on in order to rotate the testhead.

NOTEIf power has not been connected to the testhead, you can still rotate the testhead by plugging the testhead rotation motor into 110 volts or 220 volts ac power. See Rotating the Testhead Without PDU Power on page 2-52.

Cabling the Support Bay to the Testhead (307X System Only) If you are installing an Agilent 307X testhead with a support bay, follow the procedures below. If you are installing any other type of system, which has no support bay, skip this entire section and proceed to Booting the Testhead on page 1-28.

NOTEThis information also applies to installing an E2197A xDSL/POTS Bay. If you are installing an xDSL/POTs bay, also see POTS (Plain Old Telephone Services) Bay on page 1-41.

In this section you will route the module umbilical cables directly through the door of their respective modules (the cables no longer pass through a cable clamp panel in the testhead). The umbilical cable 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 2

Module 3

Module 0

Module 1

Support Bay

SUP_BAY2.WPG

HP-IBCable

Route the PDU Branch ControlBlack / White Wire Pair throughthe cutout in the bottom panel.

1 0 2 3Aux Aux

Aux Aux Aux Aux Aux AuxCable Clamp Panel

Module UmbilicalCables

Module Door Locking Bracket Vacuum Manifold



4 Connect the white triaxial cable to the functional ports as shown in Figure 1-10.

Figure 1-10 ASRU card connections (rear view)

PDU Branch Control Wires This applies only to 1-phase or 2-phase systems with a PDU in the support bay.

Every module umbilical cable has a black / white wire pair, but only module umbilical cable going to the bottom DUT supply has a wire pair that is connected to the PDU. Note the module number on that module umbilical cable.

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 the cutout in the panel (see Figure 1-9 on page 1-25). Coil and secure the branch control wires of the unused umbilical cables.

AccessPlus Cables If the system includes AccessPlus cables, route them through the other (unused) hole in the module door (see Figure 1-9 on page 1-25).

GPIB Cable Connect the GPIB cable from the support bay to the GPIB connector on the GPIB card in the controller in the controller bay pod of the testhead.

NOTEDo not connect the GPIB cable to the GPIB port on the System Card.

Supplies 1-4Supplies 5-6

Functional Ports

Red band

03066-66532 ASRU CardWhite band

ASRU_CON.WPG



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 Testhead

Booting the Testhead Log in as service1.

Boot the testhead using the Testhead Functs and Testhead Power On function keys. Watch the LEDs on the System Card during the boot process for problems and review the screen for boot error messages.1

Booting takes about two minutes. The testhead LAN has been configured with the correct hardware addresses at the factory. If any error messages appear, see Troubleshooting on page 2-35.

NOTEThe first time the system is booted with the new controller, there will be several Warning - Standard calibration tables not loaded for Module X Slot X messages. These warning messages are normal; they are generated because there are no valid AutoAdjust tables in the /var/hp3070/diagnostics/th1/cal_B subdirectory. These messages will go away when you run AutoAdjust later.

Verifying the config File (Pre-Shipped Controllers Only) Normally, you can skip this section and proceed to Running AutoAdjust All on page 1-29. However, there

are two conditions that will require you to verify the config files:

� If the testhead controller was pre-shipped to the customer ahead of the testhead.

� If the customer wants the testhead cards installed in a certain configuration that is different from the way in which they were shipped from the factory.

The official system config file (/var/hp3070/diagnostics/th1/config) and the standard config file (/var/hp3070/standard/config) were set up and compiled at the factory. Codewords for all software products ordered with the system were also set up at the factory.

If the controller was shipped before the testhead, the config files will not be set up for your testhead. You will need to set up and compile the config files and enter the codewords for your system. The config files will not compile unless the codewords are correct.

If you want to verify that the config files are correct, compare the system configuration printout (in the bag 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 prompt ($) type:more config

Ask the customer�s system administrator if there is a 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 configuration shipped from the factory, change the location of the cards to match the plan. Note any change in card locations and edit the official system config file accordingly; see The Configuration Files on page 2-5.

Running AutoAdjust All

NOTEAllow the testhead to warm up for 30 minutes before running AutoAdjust. If the testhead temperature is not allowed to stabilize, you may get Diagnostics failures later.

After the testhead has warmed up for at least 30 minutes, run AutoAdjust All (press function key F6 in the AutoAdjust menu). Verify that there are no errors.

Running Full Diagnostics Put a pin verification fixture on the testhead, enable manual intervention,2 and run Full Diagnostics. Verify that there are no errors.

Setting Up and Verifying the Strip Printer If you have not already done so, remove the shipping material from the printer and install the paper roll and print ribbon cassette in the printer according to the instructions with the printer. Then verify the printer as follows:

1 Run the printer�s self-test according to the manual that came with the printer to verify that it prints well.

2 Verify communication with the printer: Log in as user1.

3 Open a BT-BASIC window and type:report is /dev/rpr1

report "This is a test"

The printer should print the message This is a

test.

4 Exit the system: click on the Exit icon in the low right corner of the screen and then click on the Yes button.

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 / 79000Repair I Manual, Chapter 2, for more information.



NOTEIf the testhead is being used with convention vacuum fixtures, proceed to Verifying the Vacuum Subsystem on page 1-30. If the testhead is being used in an automation environment, proceed to Setting up the Testhead for Automation on page 1-43.

Verifying the Vacuum Subsystem The Agilent 3070 Series 3 testheads may or may not have internal vacuum solenoids (valves); they are optional. All 327X (one-module) and 79000 testheads always have at least one internal vacuum solenoid; two solenoids are optional in these testheads.

It is the customer�s responsibility to connect the vacuum solenoid control wires to the System Card unless the system was purchased with internal solenoids, in which case the solenoids are wired in the factory. The internal vacuum system and wiring are shown in see Figure 1-11 on page 1-32.

To verify the operation of the vacuum subsystem, perform the steps below. If a vacuum source and solenoids are connected, you can turn vacuum on and off and listen for the sound of the air at the testhead�s vacuum ports. If a vacuum source and solenoids are not connected, you can use a voltmeter to verify that 24 volt dc can be switched to all terminal pairs of the Auxiliary connector (J3) on the System Card (Figure 1-11 on page 1-32).

1 Look at the vacuum hardware on the testhead and note the following:

� How many solenoids are being used to control vacuum

� Which Auxiliary ports are being used to control which solenoids

� Which solenoids have hoses to which vacuum ports (if external solenoids are used)

2 With the testhead booted, look at the system config file (/var/hp3070/diagnostics/th1/ config) and verify that the relay <r> controls vacuum <m> statement(s) agrees with the hardware:

� r = 1 for Aux 1; 2 for Aux 2; 3 for Aux 3, 4 for Aux 4; 5 for Aux 5

� m = the module vacuum port(s) connected (can be 0; 1; 2; 3; 0,1; 2,3; 0-3)

3 From a BT-BASIC window, take control of the testhead; type:testhead is 1

4 Execute a vacuum well... statement; type:vacuum well a is <m>

The vacuum well is normally defined in the testplan. For this test, use a. Ensure that <m> = a valid module vacuum port noted in step 2.



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

E9946A Vacuum components shown above the dotted line Vacuum components below the dotted line are customersupplied

VacuumSource

Pressure Gage

Port3

In0ut

+_

+_

+_

+_

+_

1

2

3

4

5

6

7

8

9

10

11

12

RemoteShutdownJumper

+_

+_

+_

+_

+_

1

2

3

4

5

6

7

8

9

10

11

12

Relay 2

Relay 1

Relay 3

Relay 4

Relay 5

80-PSI Regulator03066-67911

Air Lines

Port2

Port1

Port0

Vacuum ValveE3770-67900

E9900-632004-Module Manifold

System Card

2-inch Vacuum HoseManual Cut-off Valve 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 Hardware

System Printer / Plotter 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

PPU DB9ButtonAdapter0960-2134

Dual ButtonHolder withcable1252-8421

Digi MUX BoxPort 1

8120-6773 CableRJ45-DB9AdapterE9970-63201

1st PPU Button2nd PPU Button

Right Pod, cover removed



Installing and Removing Test Credit Buttons Agilent E3995A test credit button(s) will need to be installed as shown in Figure 1-13. One 50k test credit button is included with the Pay-Per-Use system. It is packaged in a 3-inch by 1.5-inch box inside a plastic bag containing installation instructions. Agilent test credit buttons may be inserted while the system is running. To insert a button, grasp it with the flange or labeled side up. Push the button firmly into one of the ports of the

botton holder. Save the packaging material until you are certain that the button is working correctly.

To remove a test credit button, grasp the button by its flange and pull it straight out of the button holder. To remove the button holder cable from the button adapter, deflect one of the retaining latches with your fingernail, a pen, or similar instrument. The button connector will pop up for removal.

Figure 1-13 Installing Pay-Per-Use buttons

PPU1HH.WPG

InsertRelease

PPU ButtonsDual Buttons Holder with cable

Button Connector

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


UNIX System Installation Procedure: Setting Up Other HardwarePR PLUS This procedure describes how to enable Agilent PR PLUS paperless repair software on the Agilent 3070 / 79000 controller (with software revision B.03.00 or later) and setup the hardware. For more information about PR PLUS, see the 3070 Series 3 / 79000 Family System Administration Guide (E9900-90000)

Connecting the Terminal Connect the terminal to a port on the E3788 SCSI-MUX box (from the controller). Use a 4-meter RJ-45 cable (8120-6773) and a DCE adapter (E4000-62106) to connect to the terminal cable. While any of the eight ports on the MUX box can be used, ports 4 through 8 are the primary ports for terminals; ports 1 through three are primarily used for other devices. Remove the controller pod cover to access the MUX box.

Configuring the Terminal � 8-bit characters

� No parity

� XON/XOFF

� 9600 baud

� Block mode OFF

Editing the /etc/inittab File for the Terminal 1 Log in as root.

2 Edit the /etc/inittab file as follows:

Find the commented line that corresponds to the port to which you connected the terminal, and un-comment it by removing the # character from the beginning of the line. For example, if the terminal is connected to port 4, un-comment:#tm4:234:respawn:/usr/sbin/getty -h ttym04H # scsi port box, 4th port 9600 baud

3 Re-save the file.

4 Re-initialize the init process to read the /etc/inittab file; type:/sbin/init q

The terminal should now display a login prompt.

Installing the PR PLUS Codeword You must install the PR PLUS codeword on every system running PR PLUS software. A separate license and codeword is required for each system. Concerning a PR PLUS system:

� Boards will be homed on that system (their 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 license.

Setting up the 8-User HP-UX License The PR PLUS license includes an 8-user license. Because the standard 3070 / 79000 software is setup with a 2-user license, you must setup the 8-user license to allow simultaneous access at the attached terminals and system console. With a 2-user license the console acts as one user, and the network, if attached, acts as the second. Although any attached terminal on a 2-user system may show a login prompt, no login attempt will succeed as long as someone is logged in at the console.

To set up the 8-user license, you must reload software. Follow the directions in the Agilent B.03.0X Software Reloading Procedure (E9900-96000) that came with the system.

Setting Up PR PLUS Unless you are already familiar with the prsetup program, you will need to read the online PR PLUS 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.

Running the alarm Daemon The alarm daemon must be running on each PR PLUS system that is used to home boards. This daemon is automatically started during system boot.

To see whether the alarm daemon is running, type:ps -fu hp3070

This command also verifies that the translogd program is running. If either daemon is not running, you can manually start the alarm daemon. It must be run with the proper values set for environment variables PATH and NLSPATH. From root, type:envNLSPATH=/opt/hp3070/lib/nls/american/%N.cat \PATH=$PATH:/usr/hp3070/bin \nice alarm

After alarm is running on all PR PLUS systems, verify the flow of log data among networked systems by running the Network Verify function in the prsetup program. The expected results are described in the online documentation.

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.


UNIX System Installation Procedure: Setting Up Other HardwarePOTS (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

79K-HPIB.WPG

Instrument Rack Controller


Instrument 1

Instrument 2

VXIMainframe


YES - 3070

POTS Bay or

POTS Bay or

POTS Bay or

NO

NO

External Instrumentsin the Support Bay orTesthead

DUT Supplies in theSupport Bay orTesthead





Instrument 1

Instrument 2

VXIMainframe

Instrument 1

Instrument 2

VXIMainframe

Instrument 1

Instrument 2

VXIMainframe

Instrument 1

Instrument 2

VXIMainframe

Instrument Rack ControllerPOTS Bay or

E1421B VXIMainframe

YES - 79000

Face down6634A/B

Middle6634A/B

Outside6624A

VXI Mainframe andDUT Supplies in theTesthead



Setting up the Testhead for Automation If the testhead is being used in an automation environment in which a piece of automation equipment is being installed on top of the testhead, do the following:

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 floor brackets to keep the testhead stable. If you don�t have a floor bracket kit, order Agilent 44990-63221. Installation instructions accompany the kit.

4 Using a 5-millimeter hex key wrench, remove the safety shroud from around the testhead�s pin field.

5 After installing the automation equipment on the testhead, reach under the testhead and disconnect the plug from the Auxiliary connector (J3) on the System Card (Figure 1-16).

Figure 1-16 Connecting the EMO cable

6 Remove the jumper from terminals 11 and 12 on the plug and connect the Emergency Shutdown (EMO) switch on the automa-tion equipment to pins 11 and 12 on the plug. Then reinstall the plug on the System Card.

WARNING

✸DO NOT operate the system without an EMO switch properly wired and accessible to the 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.

J3

System Card



EFS Board Handler

NOTEBe 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 Installation

Reinstalling the Pod Covers If any pod or cradle covers are still off the system, reinstall them now.

Making a System Recovery Tape A recovery tape allows you to boot the controller after a catastrophic fault, such as when you can no longer boot from your disk. To make a recovery tape, refer to Administering Agilent 3070 UNIX Systems (E9900-90000).

CAUTION

✸Using the system recovery tape will re-initialize your disk drive, and therefore, all existing data will be lost.

Making a System Backup Tape To make a backup tape, refer to Administering Agilent 3070 UNIX Systems (E9900-90000).

Turning System Administration Over to the Customer

� Inform the customer that Agilent shipped the software without a root password, and that they should use the passwd statement to create a root password.

� Tell the system administrator about the contributed software. A disclaimer of any warranties, expressed or implied, is displayed while un-compressing contributed software. If the system administrator desires to un-compress contributed software, log in as root and type:cd /opt/hp3070/contrib/binsh Convert

Documentation files are un-compressed in the /opt/hp3070/contrib/doc subdirectory.

� Remind the system administrator that DNS or NIS need to be setup (see Additional Network Parameters � When you see: on page 1-22). 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.


2222 UNIX System Installation ReferenceE4000-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 Changes With HP-UX 10.2X (B.03.XX)

When HP-UX went to revision 10.2X at 3070 / 79000 revision B.03.00 (3070 Series 3), many files, directories and commands (or scripts) changed location in the file system. Some commands also changed in functionality. These changes affect the hp3070 directory where the diagnostic and configuration files are located and many directories related to networking.

Two changes that affect key directories are:

Table 2-1 is a list of files, directories and commands that are important for installation and configuration:

/hp3070 became /var/hp3070

/usr/hp3070 became /opt/hp3070

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)

/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

Table 2-1 Comparison of file systems (continued)

Pre-HP-UX 10.2X Post-HP-UX 10.2X


UNIX System Installation Reference: Installing and Reviewing Codewords

Installing and Reviewing Codewords

1 Log in as root and run preupdate; type:

/opt/hp3070/etc/HP3070SU/preupdate

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.

NOTEIncorrectly 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 Files

Two types of configuration files are discussed in this section. They are informally called the system config file and the standard config file:1

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).

system config file: /var/hp3070/diagnostics/th1/config

standard config file: /var/hp3070/standard/config



The testhead name Statement The testhead name statement in the system config file identifies the block in the /etc/bootptab file that contains the hardware addresses (ha) and internet protocol addresses (ip) for the System Card and any

ControlXT/XTP Cards in the testhead, which are on the testhead LAN (see page 2-43).

For an Agilent 3070 Series 3 / 79000 testhead with B.03.00 or later software, the testhead name statement in the system config and /etc/bootptab files must look like this:

testhead1 represents the System Card, and module<n> represents the ControlXT/XTP Card in each module. Include only the modules that are present. If the testhead does not have ControlXT/XTP Cards, then no module<n> keywords are needed.

Because the System Card and ControlXT/XTP Card IP addresses are local to each system, their IP addresses are identical in all systems. However, the hardware address (ha) of each card is unique.

The board Handler, line frequency and relay Statements Edit the system config file to make it match the system.

board handlerComment1 (!) this for nowline frequency 60Un-comment either 50 or 60 (Hz)

The relay <x> controls vacuum <y> statements also need to match the actual hardware configuration after the customer decides how to implement vacuum control. For testheads without internal vacuum valves, the default statements are:

relay 1 controls vacuum 2,3relay 2 controls vacuum 0,1

For testheads with the Agilent E9945A two-module internal vacuum system, the default statements are:

relay 1 controls vacuum 3relay 2 controls vacuum 2

For testheads with the Agilent E9946A four-module internal vacuum system, the default statements are:

relay 1 controls vacuum 3relay 2 controls vacuum 2relay 3 controls vacuum 1relay 4 controls vacuum 0

There is nothing special about the defaults except that each matches a configuration shown in the site preparation manual. Review the Agilent 3070 / 79000 Family Site Preparation Manual (03066-90114) to see a drawing of this default vacuum hookup. Modify the relay statements so they will work with your customer�s hardware.

testhead name "testhead1" "module3" "module2" "module1" "module0"

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 single relay, you might use this statement in the system configuration file:

relay 1 controls vacuum 0,1,2,3

The cards <keywords> Statements You can use the Official system configuration file printout shipped with the system as a model if you need to customize the system configuration file. Table 2-2 cross-references the diagnostic name and part number to cards <keywords> statements in the configuration files.

The cards <keywords> statements can be delimited by commas (,); a range can be separated by the word to. Valid examples are:

cards 2, 3, 4, 5 hybrid advancedcards 2 to 5 hybrid advancedcards 2, 4, 7 to 11 hybrid advanced

Table 2-2 includes footnotes with rules or limitations that apply to certain configurations of cards. One rule that applies to all HybridPlus Pin Cards is that you can mix single-density and double-density cards in the same module.

Table 2-2 spans three pages: the first page covers the Access, Analog, ASRU, Channel, and Control Cards; the second page covers Hybrid Cards; and the third page covers Serial Test Cards.

Table 2-2 Diagnostics name to card type cross reference

Diagnostics Config Name (in the Config screen)

cards <keywords> Statement in the system config file(see the Notes at the end of the table)

Pattern App Rate

Part Number of the Card

Access access 6/12/20 MP/s E1061-66501

Analog analog 6/12/20 MP/s E1172-66524E1121-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



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)



Pattern App Rate




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-66502with 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.

Table 2-2 Diagnostics name to card type cross reference (continued)



Pattern App Rate




NOTESerial = 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.

6. You can mix hybrid advanced and hybrid advanced b revision cards in a testhead. You cannot mix hybridstandard, 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 conrolxt/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.



The supplies <keywords> Statements

NOTENumbering 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.

There are four types of DUT power supplies allowed in the system as shown in Table 2-3. The Agilent 6634A can only be used with ASRU revision C cards, 03066-66532, on the high-voltage ports (ports 5 and 6).

Table 2-4 on page 2-12 shows a valid default power supply mapping for each module, and the proper syntax for each type of power supply. The commented (!) statements illustrate that you cannot assign a power supply number (1 through 24) more than once in a testhead, and you cannot assign a channel number (1 through 6) more than once in a module.

For 307X systems, with a support bay, if you need to determine which DUT power supply is wired to which module, the DUT/ASRU (E4000-61602) cables are labeled on both ends with the module numbers to which they are routed. 317X systems use cable numbers E4000-61606 and E1170-61607.

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



Factory defaults have been established for common configurations.

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.

Table 2-4 Default Power Supply Mapping (Rear view of testhead)

Module 0

supplies hp6624 13 to 16 asru channels 1 to 4! supplies hp6621 13 to 14 asru channels 1 to 4! supplies hp6624 23 to 24 asru channels 5 to 6supplies hp6621 23 asru channels 5 to 6! supplies hp6634 23 asru channels 5! supplies hp6634 24 asru channels 6! supplies hp6642 23 asru channels 5 to 6

Module 2

! supplies hp6624 5 to 8 asru channels 1 to 4supplies hp6621 5 to 6 asru channels 1 to 4! supplies hp6624 19 to 20 asru channels 5 to 6! supplies hp6621 19 asru channels 5 to 6supplies hp6634 19 asru channels 5supplies hp6634 20 asru channels 6! supplies hp6642 19 asru channels 5 to 6

Module 1

supplies hp6624 9 to 12 asru channels 1 to 4! supplies hp6621 9 to 10 asru channels 1 to 4! supplies hp6624 21 to 22 asru channels 5 to 6! supplies hp6621 21 asru channels 5 to 6supplies hp6634 21 asru channels 5supplies hp6634 22 asru channels 6! supplies hp6642 21 asru channels 5 to 6

Module 3

supplies hp6624 1 to 4 asru channels 1 to 4! supplies hp6621 1 to 2 asru channels 1 to 4supplies hp6624 17 to 18 asru channels 5 to 6! supplies hp6621 17 asru channels 5 to 6! supplies hp6634 17 asru channels 5! supplies hp6634 18 asru channels 6! supplies hp6642 17 asru channels 5 to 6



The DUT Power Supply GPIB Addresses and Device Files

NOTEIf a power supply is split between two modules, the default GPIB address (and device file) is the one for the lower numbered module.

To change the GPIB address, press ADDR (beside the display), enter the desired address on the ENTRY keypad, and then press ENTER on the ENTRY keypad.Power Supply Connection GPIB

AddressDevice File

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









Editing and Compiling the System Config File If the system config file as shipped from the factory is NOT acceptable,1 or you have moved cards in the testhead, edit the system config file:

1 Log in as service1.2

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.

The Standard Config File The standard config file (/var/hp3070/standard/config) is the master of the configuration files used to develop board tests. Programmers can modify a copy called board config for each board test developed. The copy will be in each board�s subdirectory.

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 asthere is in BT-BASIC.

3 See The BT-BASIC Editor on page 2-26.



Syntax Differences from the System Config File Some of the syntax for the standard config file (copied to board config files) is different from that of the system config file. However, the cards <keywords> syntax is the same for the system confign file and the standard config file. The following statements must not be used in the /var/hp3070/standard/config file or board config file:

� testhead name "testhead1" "module3""module2" "module1" "module0"

� line frequency

� board handler

� relay <x> controls vacuum <y>

� bank

� end bank

� probe

� debug port

� control <x>

The following statements1 can (or for some configurations, must) be used in standard config and board config files:

� target

� enable

� module

� end module

� cards

� supplies

� ports

� connect

� control <x>

connect statements allow programmers to name and define the use of external ports. Usually these can remain as-shipped until the customer decides how to use these ports.

1 See the 3070 Family Users� Manual - Quick Reference Guide for definitions and conventions of these statements.



The target <keywords> Statements

NOTEThe target <keywords> statement should be the first un-commented statement in the file and must be before the cards <keywords> statements.

A target <keywords> statement is needed in each board config file, unless the target system is target

hp3070 advanced. The default target <keywords> statements (Table 2-5), included in the standard config file shipped with the system, match the full capability of the system. Because it is more explicit and does not cause any problems, the target hp3070 advanced statement is included in the standard config file shipped from the factory with 12-MP/s systems.

With Agilent 3X79CT Telecom test systems, the default target <keywords> statement is not correct unless the 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>

statements need to be modified per Table 2-6 on page 2-16.

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

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 target <keywords> is correct. See Table 2-7 for the

Process Test System default target <keywords> statements.

The enable <keywords> Statements

NOTEThe enable <keywords> statements should be after the target <keywords> statement and must be outside of a module block.

enable <keywords> statements are used in combination with codewords to selectively enable software functionality. Commented enable<keywords> statements for appropriate products for each system are included in the default standard config file. The programmer will un-comment the correct enable <keywords> statements which correspond to product numbers purchased or supplied as standard software when they edit the board config file.

If the system is target hp3070 advanced or targethigh accuracy, the features listed below are implied and do not need enable <keywords> statements.

If the system is target hp3073 standard, however, it does not include these features. If the customer ordered these products, you must add the appropriate codewords and enable <keywords> statements for these features:

� SimPlate Express Fixture Software

� Combo/Incircuit Test Upgrade

� Combinational/Functional Test Upgrade

See Product-specific enable <keywords> statements on page 2-18 and Standard feature enable <keywords> statements on page 2-19.

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



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 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.

enable software revision b

On systems with double-density pin cards, allows the second column to be used as drivers and receivers.

enable all high accuracy resources

Enables the 3070 software to utilize the Agilent E4032A GenRad Universal Fixture Interface. The default GR multiplexing option is 2:16 if a multiplexing option is not entered.

enable gr fixture interface

(followed by GR multiplexing option 2:16 or 2:8or 4:16)

Enables the 3070 software to utilize the Agilent E4031A 3065 Universal Fixture Interface.

enable hp3065 fixture interface

Enables a given testhead resource to go to multiple PC boards on multiple vacuum well fixture.

enable dual well shared wiring

Enables interoperability between UNIX® and MS Windows®.

enable common delimiter



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 The desired end result of the following procedure is to copy the cards ..., serial ports ..., supplies... and ports ... statements from the system config

file to the standard config file, as shown in Figure 2-1. This ensures the programmer has the full capability of the system in the standard config file (/var/hp3070/standard/config).

Figure 2-1 Copying configuration information

The following procedure uses the mouse to copy text from the system config file into a temporary buffer and then output the contents of the buffer into the standard

config file. This method is suggested to eliminate typing errors and to save time.



NOTEIf you are configuring a test server, log in to the appropriate testhead controller and copy the appropriate statements from the system config file (/var/hp3070/diagnostics/th1/config).

One method to do this using BT-BASIC1 follows:

1 Log in as service1.

2 Open a BT-BASIC window. To open a BT-BASIC window, move the mouse pointer out of all windows; then click and hold down the right mouse button. Drag the pointer to highlight the New BASIC Window selection, then release the button.

3 On the command line type:

msi /var/hp3070/standard Return4 On the command line, type:

copy config over config.temp ReturnThis makes a backup copy of the config file in the event you have a problem with this procedure.

5 On the command line, type:

get /var/hp3070/standard/config Return6 Open another BT-BASIC window.

Move the second window to the lower right corner of the display. To do this, place the mouse pointer on the top bar of this window; then click and hold down the left mouse button. Drag the window to the lower right corner of the display to uncover the first window. Release the button.

7 On the command line of the second BT-BASIC window, type:

get /var/hp3070/diagnostics/th1/config Return

8 Press F1 to move the cursor into the workspace to permit editing.

9 Locate the first (or next) module <number> that contains un-commented cards 1 ... statements using the arrow keys or the Prev and Next keys. Scroll the text up until you can see the end module statement.

10 Place your mouse pointer on the left margin in front of the first cards ... statement and click the left mouse button. Hold the mouse button down and highlight the text, by dragging the mouse pointer over it, to include the ports ...2 statement. Release the button.

You now have the cards 1 ..., serial ports

..., supplies ..., and ports ... statements 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.



NOTEDo NOT include probe, debug port, bank, or end bank statements. These statements are not valid in the standard config file (/var/hp3070/standard/config).

11 Move the mouse pointer to the window containing the standard config file. Click on any border with the left mouse button to bring this window into the foreground.

12 Press F1 to enter the workspace. Then move the cursor immediately below the module <number> statement that corresponds to the module <number> statements you have stored in the buffer from the system config file.

NOTEFailure to place the cursor immediately below the module statement can result in corruption of the file by over-writing existing statements. The blank space is 20 lines long and the copied statements may be up to 20 lines. If necessary, retrieve your backup copy and repeat steps 11-16.

13 Click the right mouse button. The text from the buffer will be inserted into the standard config file.

14 Un-comment the module <number> and end module statements in the standard config file; use the delete character key to remove the comment (!) character.

15 If you have a control plus 4 card, delete the number after the plus. The standard config file will not compile if the number (amount of RAM) is included in the statement.

NOTEDo not delete the ! Specify instrument ... through ! connect ... which were in the original file. These statements can be used by the programmer to specify external instrumentation.

16 Repeat steps 10 through 16 for each module<number> that contains un-commented cards statements in the system config file.

17 When all of the correct statements have been copied to the standard config file, and appropriate statements have been un-commented, re-save the standard config file. To re-save, press F1 to return to the command line, then type re-save and press Return.

18 When all of the correct statements have been copied to the standard config file, exit the system config file. To exit, press F1 to return to the command line, then type exit and press Return. Since no changes were made in the system config file, you should not need to re-compile this file. However, you may wish to re-compile to verify that nothing was inadvertently changed.

Proceed to Compiling the Standard Config File on 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 ReturnExit 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 Editor

Users in the HP-UX group /var/hp3070 can use the BT-BASIC editor. The editor has command line input and a workspace, as shown in Figure 2-2.

Figure 2-2 BT-BASIC editor screen

Starting the BT-BASIC Editor When logged in as service1, you can create a BT-BASIC window by moving the mouse pointer out of all windows, then clicking and holding down the right mouse button. Drag the mouse pointer down to highlight the New BASIC Window selection, then release the button.

When logged in as user1 through user4, you can start BT-BASIC by clicking on the upward-pointing triangle above the Agilent 3070 icon using the left mouse button. A menu of Agilent 3070 programs will be displayed. Click left on the BT-BASIC icon. To minimize the Agilent 3070 Programs menu, click on the downward-pointing triangle at the bottom of the menu.

configuration xxxxStatus: xxx lines in workspace

edit

BT-BASIC

BASIC

command line

Workspace



When you initially enter a BT-BASIC window, the cursor will be on the command line. From the command line, you can enter and execute BT-BASIC commands. See Table 2-10 on page 2-27 for BT-BASIC statements commonly used during the editing of configuration files.

Using the BT-BASIC Editor To edit an existing file, first you will need to execute get "<filename>". To create a new filename, you need to switch to the workspace to permit editing. You can

switch to the workspace by pressing F1. In the workspace, you can edit a file�s contents. The cursor control keys, Insert Char, Delete Char, and arrow keys move the cursor in the workspace. You can switch back to the Command line by pressing F1.

Command Line Statements See Table 2-10.

Table 2-10 Commonly used BT-BASIC statements1

BT-BASIC Statement Statement Functionget "<filename>"

save "<filename>"

re-save

compile "<filename>"

compile "<filename>";testhead

findn "<string expression>"

exit

retrieve an existing filecreate a new filesave an existing filecompile a filecompile a testhead filefind the next occurrence of a string expressionquit 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 Reference

Type commands as they are shown in the second column. Italics specifies directory, file or other task-specific text. Keyboard keys are in bold.

Include pathnames with filenames if you are working with different directories.

Follow each command with Return.

For additional information type man command_name using the commands shown in the second column.

To Do This... Type This...

Working with Directories:Show current working directoryChange directoryChange to home directoryCreate a directoryRemove an (empty) directoryDisplay permissions for a directoryChange permissions for file or directory

Owner Group Othersrwx rwx rwx

pwd

cd pathnamecd

mkdir directory_namermdir directory_namell -d directory_namechmod octal# filename

(See man page)



Working with Files:List files and directories in current directoryList all files or directories, including hidden (dot) filesList files, and show directories with /Display permissions for a fileCreate or edit a fileDisplay file contentsCopy a file with permissions and ownersMove a file to a new filenameAppend file1 onto the end of file2Remove a filePrint a file

ls

ls -a

lsf

ll filenamevi filenamemore filename (q to quit) (v to vi)cp -p file1 file2

mv old_file new_file

cat file1 >> file2

rm filenamelp filename

Finding and Organizing:Find file(s) beginning with x in the current and sub-directories.Find all occurrences of word in all files in the current directoryDisplay date and timeFind HP-UX command manual pageFind name of current host systemFind current HP-UX system informationFind Agilent 3070 Software Revision (as user1 or service1) (As root path is /opt/hp3070/bin)Find environment info. including PATH

find . -name 'x*' -print

grep word *

date

man command_name

hostname

uname -a

version

env




System Operations:Clear screenLog outChange to Korn shellEdit your command line (in Korn shell set for vi)Recall previous command line (with vi editor)Execute previous command lineList current process status and PID�sKill (terminate) a processCreate or change a passwordRedirect input from a file to a commandConnect two processes with a pipe

clear

exit or CTRL d Returnksh

ESC (use vi commands)ESC k (back) or j (forward)Return (when line is displayed)ps -ef

kill PID (Process ID Number from list)passwd

command < infilecommand1 | command2

Network Operations:Invoke ftp and connect to remote_hostnameCopy a file using ftp from remote_hostnameCopy a file using ftp from the local current directory to current directory on the remote_hostnameExit ftpLog in on a remote system

ftp remote_hostnameget remote_file put local_file

bye

rlogin remote_hostname



UNIX System Installation Reference: vi Editor Quick Reference

vi Editor Quick Reference

Type commands as they are shown in the second column. Italics specifies directory, file or other task-specific text. Keyboard keys are in bold.

Follow colon (:) and search (/) commands with Return as indicated.

To Do This ... Type This in Command Mode

Getting Started with vi:Create or edit a file (from HP-UX shell)Make sure you�re in command modeShow if you are in command or insert modeFind out what file you are in

vi filenameESC:set showmode ReturnCTRL g

Moving Within a File:Move the cursor left or rightMove the cursor up or downCursor to end of lineCursor to beginning of lineCursor to end of fileCursor to beginning of file

h or l or arrow keysk or j or arrow keys$

0 (Zero) or ^G

1G (one G)

Inserting Text:Insert text at the cursor positionInsert (Append) text after the cursor positionBackspace to overwrite previous character (in Insert Mode)Replace single characterReplace until ESC is pressed

i

a

CTRL h or Backspacer (character)R



Deleting text:Delete characters at cursorDelete word (cursor at beginning of word)Delete the entire line at the cursor positionDelete from cursor to end of the current lineDelete from cursor to end of the file

x

dw

dd

D

dG

Moving Text:Join lines of textCopy a line into a bufferPut copied or deleted text line from buffer after cursor lineRead in another file after cursor line

J

yy

p

:r filename Return

Searching Text:Search for wordsRepeat the previous search for words

/words Returnn (forward search) or N (backward search)

Saving and printing Files:Save file in same filenameSave file to a new filenameExit from file without saving changesOverwrite another existing file with this fileSave and exit from the vi editorPrint another file from within a file

:w Return:w new_filename Return:q!

:w! or wq! Return:wq Return:!lp filename Return




Repairing Mistakes:Undo the previous actionRestore a line to its previous stateRestore (put) last deleteRestore current file to last saved text, disregarding changesCompare changes before and after an actionRecover a file after a system interruption (from HP-UX shell)

u

U

p

:e! Returnu (repeat to toggle)vi -r filename



UNIX System Installation Reference: Troubleshooting

Troubleshooting Switch Settings This section is provided for troubleshooting purposes only. If the computer boots and functions properly, disregard this section. If the computer does not function properly, use this section to verify that switches and jumpers have been set correctly. Not all I/O cards have switches or jumpers, so only those that do are mentioned in this section.

E2071C GPIB Card Switches

NOTEThe 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

is available. Its Address must be set to 0100. Set the switches as shown in Figure 2-3 on page 2-35.

An Agilent 10834A GPIB extender is mounted on the E2071C card to prevent kinking the cables which are attached to the card. You must remove the extender before removing the card from the controller.

Figure 2-3 E2071C card switches



GPIB Software Configuration In order to communicate with GPIB devices, a hwconfig.cf file must be setup.1 This file has two different paths depending on the software revision:

While logged in as root, run iosetup; type:/opt/sicl/bin/iosetup

Follow the instructions on the screen. This program will modify the hwconfig.cf file. If a kernel rebuild is necessary, this program will do it for you. The . . .

hwconfig.cf file should include one or more of the following lines:

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

/etc/opt/sicl/hwconfig.cf B.03.XX/usr/pil/etc/hwconfig.cf B.02.XX

7 hpib e2071 1 21 0b0000 1 3 1st HP E2071C GPIB Card8 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



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.

NOTEThe 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

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.

EnableSQE Test

28641BThinLAN Transceiver

Disable



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

The 28685B EtherTwist Transceiver is a medium attachment unit (MAU) that connects directly to the AUI port on an IEEE 802.3 or Ethernet network device such as a hub, bridge, or router, or a network adapter card in a PC or workstation.

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.

Set the Link Beat switch to Enabled if the transceiver is used in a 10Base-T network. Set the Link Beat switch to Disabled if the transceiver is used in a network that is not compatible with 10Base-T (e.g., Agilent StarLAN 10).

Set the Loopback Test switch to Disabled for normal use. Set the Loopback Test switch to Enabled only for troubleshooting.

SQE TestLink Beat

Loopback TestLong Cable

Enable Disable

28685BEtherTwist Transceiver



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 1 To troubleshoot any start-up problem, log in as root.

No password is required on an initial installation.

2 When you see the HP CDE1 screen, click left on the terminal icon to open a window.

3 Move the cursor into the console terminal window. Check the contents of the /usr/adm/rc.log for error messages; type: cd /usr/admReturnmore rc.logReturndmesgReturn

4 When finished, log out.

NOTEThe most common cause of failure is improper termination of the LAN ports. Both the built-in LAN AUI port and the plug-in LAN card port must be properly terminated. For additional troubleshooting information see General LAN Information on page 2-42.

Determining the IP Address To determine the IP address, executemore /etc/hosts | grep <SYSTEM_NAME> or /etc/ifconfig lan0. The IP address follows the word inet.

Determining the Hardware Address To determine the hardware address2 and the status of the LAN, execute /etc/lanscan. The hardware address is the second field, lan0 is the external LAN, and lan1 is the testhead LAN to the System Card.

Testhead LAN

NOTEA testhead LAN troubleshooting procedure can be found in the file /etc/newconfig/hp3070/README.LAN.htm. Launch Netscape and open this file.

General LAN Information Every device on the network must have three things which identify it: a hardware address, an IP address, and a system name.

The hardware address is a 12-digit hexadecimal number, assigned by the manufacturer of the device, and coded into the device.

The IP (internet protocol) address is assigned by the LAN system administrator. It takes the form xx.xx.xx.xx and is used by the high-level LAN software. Changing hardware does not affect the IP address.

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 administrator. It is usually a name like hpmtle which has built-in company name and location coding that is meaningful to the customer. An alias can also be assigned. It is usually a verbal name like system1. Both the system name and the alias are mapped to the IP address. You can get the system name most easily by typing uname -n at the HP-UX prompt.

System Card / Control Card LAN Information On 3070 Series 3 / 79000 systems (with B.03.00 or later software), the System Card and the ControlXT/XTP Cards communicate via LAN. Because the System Card and ControlXT/XTP Card IP addresses are local to each system, their assigned addresses are the same from one system to the next. However, their hardware addresses (ha)1 are unique in each system.

The hardware address of the System Card is printed on its sheet-metal panel. The last four digits of the ControlXT/XTP Card�s hardware address are printed on one of its ROMs; it�s the last line (hexadecimal number) on the label. See the examples in the bootptab file on page 2-44.

If you change or swap a ControlXT/XTP Card,2 you 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

(SAM). It will automatically update the /etc/bootptab file. To use SAM, perform the following steps:

1 Log in as a user or superuser.

2 Click on the File Cabinet icon in the Common Desktop Environment (CDE) menu.

3 From the Application Manager screen, select (double-click) System_Admin.

4 Select Sam (it takes several seconds for the System Administration Manager to run). If you logged in as a user, you will have to enter the superuser password.

5 Select Networking and Communications.

6 Select Bootable Devices.

7 Select Fixed-Address Devices Booting From this Server. This will open a new window that displays the System Card and Control Cards in the testhead.

8 To edit the hardware address of a particular card, double-click it. After editing the appropriate field, click OK. (You can also select Actions and Modify to modify a card, or Actions and Remove to remove a card.)

9 Exit the window and then exit SAM.

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:

This file is the database for the BOOTP daemon. An entry in this file maps the hardware addresses of the system hardware to their IP address and system name.

Verify that the appropriate blocks are in this file as shown below. The last four digits of the hardware address (ha) are taken from the System Card or Control Card:

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)


vm=rfc1048:\




/etc/hosts file:

This file must contain the following lines:

NOTEIf 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.


vm=rfc1048:\



vm=rfc1048:\


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



/etc/rc.config.d/netconf file:

This file configures your networking parameters. It sets up some things that the /etc/netlinkrc file used to as 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:

Below the section on the public lan, there�s a section on routing.

HOSTNAME="<the correct systemhostname>"

OPERATING_SYSTEM=HP-UX

LOOPBACK_ADDRESS=127.0.0.1 (Make sure this line exists!!)

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; thiswill often work.)

(<x.x.x.x> may be variable based on the site requirements.)

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

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



Below this section, you�ll find a section on the private (testhead) lan. These addresses should be the same on every testhead that you install.

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.

/etc/services file:

Check this file and verify that the bootps and bootpc entries are correct:

/etc/inetd.conf file:

Check this file and verify that the bootps entry is not commented:

/usr/adm/inetd.sec file:

Check this file and see if there is a bootps entry; there need not be one. If there is none, then there are no

security lockouts. If there is one for bootps, it must allow an IP address of 0.0.0.0 as in the following example:

ROUTE_ARGS[0]=""

RARPD=0

IP_ADDRESS[1]=10.3.112.1

SUBNET_MASK[1]=255.255.248.0

INTERFACE_NAME[1]=lan1

BROADCAST_ADDRESS[1]=10.3.119.255

LANCONFIG_ARGS[1]="ether"

DHCP_ENABLE[1]=0

bootpc 67/udp

bootpc 68/udp

bootps dgram udp wait root /etc/bootpd bootpd

bootps allow <IP Address >.* <IP address range> 0.0.0.0



/var/hp3070/diagnostics/th1/config file:

Verify that it includes the following line:

/dev directory:

Verify that the /dev directory contains the following device files:

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

work, check the /etc/bootptab file, the LAN cable, and the System Card.

testhead name "testhead1" "module0" "module1" "module2" "module3"

52 0x430000 /dev/lan1

52 0x430000 /dev/ieee1

52 0x430001 /dev/ether1

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, clickGeneral, double-click System_Admin, and double-click HaltSystem or RebootSystem. Do not use SingleUserMode.



LAN Hardware Information The LAN ports on the controller must be terminated properly. If they are not, the HP-UX Start Networking start-up process will fail during boot and you may have LAN communication problems. This applies to both the built-in LAN AUI port and the LAN port in slot 3.

The LAN AUI port must be terminated with a LAN transceiver. The Agilent 28641B ThinLAN Transceiver is shipped with the controller, but the Agilent 28685B EtherTwist Transceiver or another transceiver may also be used. The transceiver, in turn, must be terminated with a BNC "T" connector (Agilent 1250-0781) and either two LAN cables or two 50-ohm loads (Agilent 1250-0207).

The LAN port in slot 3 must also be terminated with a "T" connector and either two 50-ohm loads or one 50-ohm load and a cable (Agilent 8120-5371) to the System Card assembly in the testhead.

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.

NOTEThe factory has connected the testhead to the LAN with a minimal /etc/hosts file. The factory has also configured the /etc/bootptab file to communicate with the Agilent 3X7X system card testhead LAN and no additional interaction should be needed.

Manually Setting the Local Time Zone & System Time As root, using vi, you can change the time zone variable (TZ) in these files:

� etc/profile

� /etc/csh.login

You can identify the local time zone in the file /usr/lib/tztab. Shut down the system and correct the system time when prompted.



Verify the Plan For the LAN Installation Before you set up the LAN, be sure you have determined all of the information in Table 2-1, "LAN Configuration Information," in Chapter 2. Use the plan that the customer gave you and consult with the customer system administrator and LAN manager. To complete final testing and customization of the LAN, you will need the assistance of the customer system administrator or LAN manager.

CAUTION

✸Do NOT use the sample dummy IP address (10.11.13.10) as the IP address for any 3070 / 79000 system. You MUST use a unique IP address supplied by the customer system administrator or LAN manager.

Set Up the LAN Software

Verify the System Name Log in as root. Review the /etc/rec.config.d/netconf file and find the line that contains the HOSTNAME variable. You can do this by typing:more /etc/rec.config.d/netconf

The name must match the name in the customer�s LAN plan as the correct name for this system. If it is not correct, you can correct the system name by re-running the script /etc/set_parms.1

Check the LAN Hardware 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 Using the information in Planning For the LAN Installation on page 1-19, edit the /etc/hosts file to describe all the systems in the LAN plan. The first three

fields should be entered in the order shown below; the alias is optional. You can enter a remark after a # symbol.

For example, using the sample dummy values:

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 ConcernsThe 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.

IP Address System Name alias comment10.3.112.1 testhead dan # First Agilent 3070 system


UNIX System Installation Reference: Miscellaneous

Miscellaneous Rotating the Testhead Without PDU Power

NOTEThis applies to Series II only, not Series III.

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.

NOTERepeated rotating of the testhead when connected to 120 volts ac may cause the thermal cutout to open due to excessive heating. Aiding the motor may be necessary to rotate a fully-loaded testhead when connected to 120 volts ac.

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 panelmounting screws.



Figure 2-8 Location of outlets for the rotating motor

LH2.WPG

Bank 2Bank 1

Testhead Motor Power317X 2-module testheadwith Bank 2 loaded

Testhead Motor Power307X 4-module testhead or317X 2-module testheadwith Bank 1 loaded



Moving the Controller to the Right Pod

NOTEThis is an optional procedure and applies to Agilent 3070 Series II systems only. It need not be done if the customer just wants the monitor and keyboard moved (extension cables allow this), but only if the customer insists on moving the controller itself.

NOTEThe C110 and controller can only be moved to the right pod in testheads shipped after November 1996. With older testheads the rotation switch will physically interfere with the controller. In the newer testheads the switch was relocated slightly to provide clearance for 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.

5 Remove the controller, optional RS-232 MUX box (with power pack), and LAN transceiver, and set them aside.

6 Remove the bottom foam, tear off the perforated end piece, turn it over, and place it in the right pod. Push the middle section of foam down to expose a cut-out for the controller.

7 Place the optional RS-232 MUX box (with power 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 the controller in the bottom foam. Do not turn the controller over, but keep it in the same orientation that it was in in the other pod. Use cable ties to secure the devices inside the pod.

8 Replace the foam on top of the controller. Ensure that the thicker side of the foam is toward the testhead.

9 Reconnect all cables to the controller.



Figure 2-9 Moving the controller to the right pod

Left Pod

Right Pod

Keep the thick side of thefoam between the computerand the testhead.

Turn the bottom foam overand push down the cut-outmiddle section.

Attach the power packto the beam usingcable ties

Keep the MUX boxbetween the computerand the testhead,ports to the rear.

C110FOAM.WPG

PDU


3333 UNIX Device Files � C240 and EarlierE4000-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



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 Files at B.03.81 or Later

Starting at software revision B.03.81, device driver major numbers are dynamically assigned. This section describes the supported method for rebuilding device files at B.03.81 and later.

The minor numbers for the device files have not changed. Use the minor numbers that are in the following tables.

Process for Rebuilding Device Files� Use Table 3-1 on page 3-3 to locate the driver for

the device file.

� Use the lsdev command to determine the correct major number associated with the driver (see Example for Recreating a Device File).

Example for Recreating a Device FileThis example recreates the device file /dev/ttyjb1. You must be root to execute this procedure.

1 Locate the device file in Table 3-1 on page 3-3. This device file is associated with the sts driver.

2 Execute the /usr/sbin/lsdev -d <driver> command (the <driver> argument is case-sensitive):# /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

matches the following tables is a coincidence; the major number may not always be 137.

4 Remove the device file:# rm /dev/ttyjb1

5 Use the mknod command to rebuild the device file. Use the major number 137 that is associated with the sts driver:# mknod /dev/ttyjb1 c 137 0x011000

6 Set the correct permissions. The permissions have not changed; use the same permissions that are in the following tables:# chmod 666 /dev/ttyjb1# chown root:other /dev/ttyjb1

NOTEAn asterisk (*) in the name of a driver or device file indicates that it can be replaced by any combination of letters or numbers. For example, the btlan* driver in Table 3-1 refers to all btlan drivers (btlan0, btlan1, etc).

Character Block Driver Class137 -1 sts comm


UNIX Device Files � C240 and Earlier: Rebuilding Device Files at B.03.81 or Later

NOTEWith 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 Filesasio0 Serial Port Interface cua0p0, cul0p0, mux0, mux1, rpr1, tty0p0, tty1p0, ttyd0p0btlan*lan2

LAN Interface (C240, B180L, B2000)LAN Interface (C110, 725, 712)

ether*, ieee*, lan*

CentIfSCentIf

Parallel Port Interface c*t0d0_lp, lp

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

(C240, B180L, B2000)t60488*


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 Usedcrw-rw-rw- root other sts 0x001070 acs Performance Port ACScrw-rw-rw- root other sts 0x001020 bcr Bar code readercrw-rw-rw- bin bin beep 0x000000 beepcrw-rw-rw- lp bin CentIf 0x010002 c1t0d0_lpcrw--w--w- root sys cn 0x000000 console-r--r--r-- root hp3070 108 countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x001030 cuash04 Modemcrw-rw-rw- root other sts 0x001040 cuash05 Modemcrw-rw-rw- root other sts 0x001050 cuash06 Modemcrw-rw-rw- root other sts 0x001060 cuash07 Modemcrw-rw-rw- root other sts 0x001070 cuash08 Modemcrw-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 DMMcrw-rw-rw- bin bin lan2 0x000001 ether0 System LANcrw-rw-rw- root other lan2 0x0c0000 gpio1 GPIO to testhead-r--r--r-- root hp3070 107 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x001010 hp44990 EFS Board Handler-r--r--r-- root hp3070 107 hp79000slot0 79000 VXIcrw-rw-rw- root other sts 0x001010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x001020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x001030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- bin bin lan2 0x000000 lan0prw-rw-rw- root root 0 logcrw------- lp bin CentIf 0x020002 lpcrw------- bin bin asio0 0x000080 mux0crw-rw-rw- bin bin mm 0x000002 null



crw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0-r--r--r-- root hp3070 108 ps0 GPIO DUT power supply 0-r--r--r-- root hp3070 108 ps1 GPIO DUT power supply 1-r--r--r-- root hp3070 107 ps10 GPIO DUT power supply 10-r--r--r-- root hp3070 107 ps11 GPIO DUT power supply 11-r--r--r-- root hp3070 108 ps2 GPIO DUT power supply 2crw-rw-rw- bin bin ps2 0x000000 ps2_0crw-rw-rw- bin bin ps2 0x000010 ps2_1crw-rw-rw- bin bin ps2 0x000003 ps2kbdcrw-rw-rw- bin bin ps2 0x000001 ps2mouse-r--r--r-- root hp3070 108 ps3 GPIO DUT power supply 3-r--r--r-- root hp3070 108 ps4 GPIO DUT power supply 4-r--r--r-- root hp3070 108 ps5 GPIO DUT power supply 5-r--r--r-- root hp3070 108 ps6 GPIO DUT power supply 6-r--r--r-- root hp3070 108 ps7 GPIO DUT power supply 7-r--r--r-- root hp3070 107 ps8 GPIO DUT power supply 8-r--r--r-- root hp3070 107 ps9 GPIO DUT power supply 9crw-rw-rw- root other beep 0x208000 rhilcrw-rw-rw- root other asio0 0x000004 rpr1 Strip printer-r--r--r-- root hp3070 107 scope Oscilloscope-r--r--r-- root hp3070 108 synthcrw--w--w- bin bin asio0 0x000000 tty0p0 Modem devicecrw------- root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0crw-rw-rw- root other sts 0x001030 ttyds04crw-rw-rw- root other sts 0x001040 ttyds05crw-rw-rw- root other sts 0x001050 ttyds06crw-rw-rw- root other sts 0x001060 ttyds07crw-rw-rw- root other sts 0x001070 ttyds08crw-rw-rw- root other sts 0x001030 ttydsh04crw-rw-rw- root other sts 0x001040 ttydsh05crw-rw-rw- root other sts 0x001050 ttydsh06crw-rw-rw- root other sts 0x001060 ttydsh07

Table 3-2 Device files on the 712/60/100 Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos. Filename Function Where Used



crw-rw-rw- root other sts 0x001070 ttydsh08crw-rw-rw- root other sts 0x001000 ttyjb1 Button adaptercrw-rw-rw- root other sts 0x001000 ttym01 Terminal MUX 1 Port 1crw-rw-rw- root other sts 0x001010 ttym02 Terminal MUX 1 Port 2crw-rw-rw- root other sts 0x001020 ttym03 Terminal MUX 1 Port 3crw-rw-rw- root other sts 0x001030 ttym04 Terminal MUX 1 Port 4crw-rw-rw- root other sts 0x001040 ttym05 Terminal MUX 1 Port 5crw-rw-rw- root other sts 0x001050 ttym06 Terminal MUX 1 Port 6crw-rw-rw- root other sts 0x001060 ttym07 Terminal MUX 1 Port 7crw-rw-rw- root other sts 0x001070 ttym08 Terminal MUX 1 Port 8crw-rw-rw- root other sts 0x001030 tycuas04crw-rw-rw- root other sts 0x001040 tycuas05crw-rw-rw- root other sts 0x001050 tycuas06crw-rw-rw- root other sts 0x001060 tycuas07crw-rw-rw- root other sts 0x001070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x003000 0mcrw-rw-rw- bin bin stape 0x003080 0mbcrw-rw-rw- bin bin stape 0x003040 0mncrw-rw-rw- bin bin stape 0x0030c0 0mnbcrw-rw-rw- bin bin stape 0x003000 c0t3d0BESTcrw-rw-rw- bin bin stape 0x003080 c0t3d0BESTbcrw-rw-rw- bin bin stape 0x003040 c0t3d0BESTncrw-rw-rw- bin bin stape 0x0030c0 c0t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2




brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5brw-r----- root sys lv 0x000006 lvol6crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5crw-r----- root sys lv 0x000006 rlvol6



UNIX Device Files � C240 and Earlier: 725/50 Controller

725/50 ControllerTable 3-3 Device files on the 725/50 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos. Filename Function Where Usedcrw-rw-rw- root other sts 0x001070 acs Performance Port ACScrw-rw-rw- root other sts 0x001020 bcr Bar code readercrw--w--w- user1 hp3070 cn 0x000000 consolecrw-rw-rw- root other hpib 0x070e00 counter Countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x001030 cuash04 Modemcrw-rw-rw- root other sts 0x001040 cuash05 Modemcrw-rw-rw- root other sts 0x001050 cuash06 Modemcrw-rw-rw- root other sts 0x001060 cuash07 Modemcrw-rw-rw- root other sts 0x001070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- bin bin lan2 0x000001 ether0 System LANcrw-rw-rw- bin bin lan2 0x010001 ether1 EISA LANcrw-rw-rw- root other hil 0x000020 footpedal Footswitchcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- bin bin hil 0x000010 hil1 HP-HIL device



crw-rw-rw- bin bin hil 0x000020 hil2 HP-HIL devicecrw-rw-rw- bin bin hil 0x000030 hil3 HP-HIL devicecrw-rw-rw- bin bin hil 0x000040 hil4 HP-HIL devicecrw-rw-rw- bin bin hil 0x000050 hil5 HP-HIL devicecrw-rw-rw- bin bin hil 0x000060 hil6 HP-HIL devicecrw-rw-rw- bin bin hil 0x000070 hil7 HP-HIL devicecrw-rw-rw- bin bin hil 0x000010 hil_0.1crw-rw-rw- bin bin hil 0x000020 hil_0.2crw-rw-rw- bin bin hil 0x000030 hil_0.3crw-rw-rw- bin bin hil 0x000050 hil_0.5crw-rw-rw- bin bin hil 0x000060 hil_0.6crw-rw-rw- bin bin hil 0x000070 hil_0.7crw-rw-rw- bin bin hil 0x000080 hilkbd HP-HIL keyboard crw-rw-rw- bin bin hil 0x000080 hilkbd_0crw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x001010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-r--r-- root root lan2 0x430000 ieee1crw-rw-rw- root other sts 0x001010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x001020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x001030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- bin bin lan2 0x000000 lan0 Customer�s site LANcrw-rw-rw- bin bin lan2 0x010000 lan1 Testhead LANcrw------ bin bin asio0 0x000080 mux0crw------ bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2

Table 3-3 Device files on the 725/50 Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos. Filename Function Where Used



crw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- bin bin hil 0x000000 rhilcrw-rw-rw- bin bin hil 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 E1199A Strip Printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw--w--w- bin bin cn 0x000000 sysconcrw--w--w- bin bin cn 0x000000 systtycrw------ root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem devicecrw-rw-rw- root other sts 0x001030 ttyds04crw-rw-rw- root other sts 0x001040 ttyds05crw-rw-rw- root other sts 0x001050 ttyds06crw-rw-rw- root other sts 0x001060 ttyds07crw-rw-rw- root other sts 0x001070 ttyds08crw-rw-rw- root other sts 0x001030 ttydsh04crw-rw-rw- root other sts 0x001040 ttydsh05crw-rw-rw- root other sts 0x001050 ttydsh06crw-rw-rw- root other sts 0x001060 ttydsh07crw-rw-rw- root other sts 0x001070 ttydsh08crw-rw-rw- root other sts 0x001000 ttyjb1 Button Adapter crw-rw-rw- root other sts 0x001000 ttym01 terminal mux 1 port 1crw-rw-rw- root other sts 0x001010 ttym02 terminal mux 1 port 2




crw-rw-rw- root other sts 0x001020 ttym03 terminal mux 1 port 3crw-rw-rw- root other sts 0x001030 ttym04 terminal mux 1 port 4crw-rw-rw- root other sts 0x001040 ttym05 terminal mux 2 port 1crw-rw-rw- root other sts 0x001050 ttym06 terminal mux 2 port 2crw-rw-rw- root other sts 0x001060 ttym07 terminal mux 2 port 3crw-rw-rw- root other sts 0x001070 ttym08 terminal mux 2 port 4crw-rw-rw- root other sts 0x001030 tycuas04crw-rw-rw- root other sts 0x001040 tycuas05crw-rw-rw- root other sts 0x001050 tycuas06crw-rw-rw- root other sts 0x001060 tycuas07crw-rw-rw- root other sts 0x001070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x003000 0mcrw-rw-rw- bin bin stape 0x003080 0mbcrw-rw-rw- bin bin stape 0x003040 0mncrw-rw-rw- bin bin stape 0x0030c0 0mnbcrw-rw-rw- bin bin stape 0x003000 c0t3d0BESTcrw-rw-rw- bin bin stape 0x003080 c0t3d0BESTbcrw-rw-rw- bin bin stape 0x003040 c0t3d0BESTncrw-rw-rw- bin bin stape 0x0030c0 c0t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupcrw-r----- root sys lv 0x000001 lvol1crw-r----- root sys lv 0x000002 lvol2crw-r----- root sys lv 0x000003 lvol3crw-r----- root sys lv 0x000004 lvol4crw-r----- root sys lv 0x000005 lvol5crw-r----- root sys lv 0x000006 lvol6




crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5crw-r----- root sys lv 0x000006 rlvol6




725/100 ControllerTable 3-4 Device files on the 725/100 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos. Filename Function Where Usedcrw-rw-rw- root other sts 0x001070 acs Performance Port ACScrw-rw-rw- root other sts 0x001020 bcr Bar code readercrw--w--w- user1 hp3070 cn 0x000000 consolecrw-rw-rw- root other hpib 0x070e00 counter Countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x001030 cuash04 Modemcrw-rw-rw- root other sts 0x001040 cuash05 Modemcrw-rw-rw- root other sts 0x001050 cuash06 Modemcrw-rw-rw- root other sts 0x001060 cuash07 Modemcrw-rw-rw- root other sts 0x001070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- bin bin lan2 0x000001 ether0 System LANcrw-rw-rw- bin bin lan2 0x010001 ether1 EISA LANcrw-rw-rw- root other hil 0x000020 footpedal Footswitchcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- bin bin hil 0x000010 hil1 HP-HIL device



crw-rw-rw- bin bin hil 0x000020 hil2 HP-HIL devicecrw-rw-rw- bin bin hil 0x000030 hil3 HP-HIL devicecrw-rw-rw- bin bin hil 0x000040 hil4 HP-HIL devicecrw-rw-rw- bin bin hil 0x000050 hil5 HP-HIL devicecrw-rw-rw- bin bin hil 0x000060 hil6 HP-HIL devicecrw-rw-rw- bin bin hil 0x000070 hil7 HP-HIL devicecrw-rw-rw- bin bin hil 0x000010 hil_0.1crw-rw-rw- bin bin hil 0x000020 hil_0.2crw-rw-rw- bin bin hil 0x000030 hil_0.3crw-rw-rw- bin bin hil 0x000050 hil_0.5crw-rw-rw- bin bin hil 0x000060 hil_0.6crw-rw-rw- bin bin hil 0x000070 hil_0.7crw-rw-rw- bin bin hil 0x000080 hilkbd HP-HIL keyboard crw-rw-rw- bin bin hil 0x000080 hilkbd_0crw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x001010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-r--r-- root root lan2 0x430000 ieee1crw-rw-rw- root other sts 0x001010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x001020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x001030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- bin bin lan2 0x000000 lan0 Customer�s site LANcrw-rw-rw- bin bin lan2 0x010000 lan1 Testhead LANcrw------ bin bin asio0 0x000080 mux0crw------ bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2




crw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- bin bin hil 0x000000 rhilcrw-rw-rw- bin bin hil 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 E1199A Strip Printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw--w--w- bin bin cn 0x000000 sysconcrw--w--w- bin bin cn 0x000000 systtycrw------ root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem devicecrw-rw-rw- root other sts 0x001030 ttyds04crw-rw-rw- root other sts 0x001040 ttyds05crw-rw-rw- root other sts 0x001050 ttyds06crw-rw-rw- root other sts 0x001060 ttyds07crw-rw-rw- root other sts 0x001070 ttyds08crw-rw-rw- root other sts 0x001030 ttydsh04crw-rw-rw- root other sts 0x001040 ttydsh05crw-rw-rw- root other sts 0x001050 ttydsh06crw-rw-rw- root other sts 0x001060 ttydsh07crw-rw-rw- root other sts 0x001070 ttydsh08crw-rw-rw- root other sts 0x001000 ttyjb1 Button Adapter crw-rw-rw- root other sts 0x001000 ttym01 terminal mux 1 port 1crw-rw-rw- root other sts 0x001010 ttym02 terminal mux 1 port 2




crw-rw-rw- root other sts 0x001020 ttym03 terminal mux 1 port 3crw-rw-rw- root other sts 0x001030 ttym04 terminal mux 1 port 4crw-rw-rw- root other sts 0x001040 ttym05 terminal mux 2 port 1crw-rw-rw- root other sts 0x001050 ttym06 terminal mux 2 port 2crw-rw-rw- root other sts 0x001060 ttym07 terminal mux 2 port 3crw-rw-rw- root other sts 0x001070 ttym08 terminal mux 2 port 4crw-rw-rw- root other sts 0x001030 tycuas04crw-rw-rw- root other sts 0x001040 tycuas05crw-rw-rw- root other sts 0x001050 tycuas06crw-rw-rw- root other sts 0x001060 tycuas07crw-rw-rw- root other sts 0x001070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x004000 c0t4d0brw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x003000 0mcrw-rw-rw- bin bin stape 0x003080 0mbcrw-rw-rw- bin bin stape 0x003040 0mncrw-rw-rw- bin bin stape 0x0030c0 0mnbcrw-rw-rw- bin bin stape 0x003000 c0t3d0BESTcrw-rw-rw- bin bin stape 0x003080 c0t3d0BESTbcrw-rw-rw- bin bin stape 0x003040 c0t3d0BESTncrw-rw-rw- bin bin stape 0x0030c0 c0t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x027000 c2t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupcrw-r----- root sys lv 0x000001 lvol1crw-r----- root sys lv 0x000002 lvol2crw-r----- root sys lv 0x000003 lvol3crw-r----- root sys lv 0x000004 lvol4




crw-r----- root sys lv 0x000005 lvol5crw-r----- root sys lv 0x000006 lvol6crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5



UNIX Device Files � C240 and Earlier: C110 Controller

C110 ControllerTable 3-5 Device files on the C110 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos Filename Function Where Usedcrw-rw-rw- root other sts 0x011070 acs Performance Port ACScrw-rw-rw- root other sts 0x011020 bcr EFS bar code reader MUX port 3crw-rw-rw- bin bin beep 0x000000 beep crw-rw-rw- lp bin CentIf 0x020002 c2t0d0_lpcrw--w--w- root sys cn 0x000000 console crw-rw-rw- root other hpib 0x070e00 countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x011030 cuash04 Modemcrw-rw-rw- root other sts 0x011040 cuash05 Modemcrw-rw-rw- root other sts 0x011050 cuash06 Modemcrw-rw-rw- root other sts 0x011060 cuash07 Modemcrw-rw-rw- root other sts 0x011070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- bin bin lan2 0x000001 ether0 System LANcrw-rw-rw- bin bin lan2 0x010001 ether1crw-rw-rw root other sts 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- bin bin hil 0x000010 hil1 HP-HIL devicecrw-rw-rw- bin bin hil 0x000020 hil2 HP-HIL devicecrw-rw-rw- bin bin hil 0x000030 hil3 HP-HIL devicecrw-rw-rw- bin bin hil 0x000040 hil4 HP-HIL devicecrw-rw-rw- bin bin hil 0x000050 hil5 HP-HIL devicecrw-rw-rw- bin bin hil 0x000060 hil6 HP-HIL devicecrw-rw-rw- bin bin hil 0x000070 hil7 HP-HIL devicecrw-rw-rw- bin bin hil 0x000010 hil_0.1 crw-rw-rw- bin bin hil 0x000020 hil_0.2 crw-rw-rw- bin bin hil 0x000030 hil_0.3



crw-rw-rw- bin bin hil 0x000040 hil_0.4 crw-rw-rw- bin bin hil 0x000050 hil_0.5 crw-rw-rw- bin bin hil 0x000060 hil_0.6 crw-rw-rw- bin bin hil 0x000070 hil_0.7crw-rw-rw- bin bin hil 0x000080 hilkbd HP-HIL keyboardcrw-rw-rw bin bin hil 0x000080 hilkbd_0crw-rw-rw- root other hpib 0x070800 hp3488 EFS 3488A switch/control boxcrw-rw-rw- root other sts 0x011010 hp44990 EFS Board Handler MUX port 2crw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-r--r-- root root lan2 0x430000 ieee1crw-rw-rw- root other sts 0x011010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x011020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x011030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- bin bin lan2 0x000000 lan0 Customer�s site LANcrw-rw-rw- bin bin lan2 0x010000 lan1 Testhead LANcrw------- lp bin CentIf 0x020002 lpcrw------- bin bin asio0 0x000080 mux0crw------- bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 null crw-rw-rw- bin bin framebuf 0x000001 ocrt crw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2crw-rw-rw- bin bin ps2 0x000000 ps2_0 crw-rw-rw- bin bin ps2 0x000010 ps2_1 crw-rw-rw- bin bin ps2 0x000003 ps2kbdcrw-rw-rw- bin bin ps2 0x000001 ps2mouse Mousecrw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5

Table 3-5 Device files on the C110 Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos Filename Function Where Used



crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- root other sflop 0x501000 rhil crw-rw-rw- bin bin hil 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 Strip Printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw--w--w- root bin asio0 0x000000 tty0p0crw--w--w- bin bin asio0 0x010000 tty1p0crw------- root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem (standard)crw-rw-rw- root other sts 0x011030 ttyds04 Modem MUX port 4crw-rw-rw- root other sts 0x011040 ttyds05 Modem MUX port 5crw-rw-rw- root other sts 0x011050 ttyds06 Modem MUX port 6crw-rw-rw- root other sts 0x011060 ttyds07 Modem MUX port 7crw-rw-rw- root other sts 0x011070 ttyds08 Modem MUX port 8crw-rw-rw- root other sts 0x011030 ttydsh04 Modem MUX port 4crw-rw-rw- root other sts 0x011040 ttydsh05 Modem MUX port 5crw-rw-rw- root other sts 0x011050 ttydsh06 Modem MUX port 6crw-rw-rw- root other sts 0x011060 ttydsh07 Modem MUX port 7crw-rw-rw- root other sts 0x011070 ttydsh08 Modem MUX port 8crw-rw-rw- root other sts 0x011000 ttyjb1 PPU button adapter MUX port 1crw-rw-rw- root other sts 0x011000 ttym01 Terminal MUX port 1crw-rw-rw- root other sts 0x011010 ttym02 Terminal MUX port 2crw-rw-rw- root other sts 0x011020 ttym03 Terminal MUX port 3crw--w--w- root tty sts 0x011030 ttym04 Terminal MUX port 4crw-rw-rw- root other sts 0x011040 ttym05 Terminal MUX port 5crw-rw-rw- root other sts 0x011050 ttym06 Terminal MUX port 6crw-rw-rw- root other sts 0x011060 ttym07 Terminal MUX port 7crw-rw-rw- root other sts 0x011070 ttym08 Terminal MUX port 8crw-rw-rw- root other sts 0x011030 tycuas04 Modem MUX port 4crw-rw-rw- root other sts 0x011040 tycuas05 Modem MUX port 5crw-rw-rw- root other sts 0x011050 tycuas06 Modem MUX port 6




crw-rw-rw- root other sts 0x011060 tycuas07 Modem MUX port 7crw-rw-rw- root other sts 0x011070 tycuas08 Modem MUX port 8

/dev/dskbrw-r----- bin sys sdisk 0x004000 c0t4d0brw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0brw-r----- bin sys sdisk 0x015000 c1t5d0/dev/rmtcrw-rw-rw- bin bin stape 0x013001 0mcrw-rw-rw- bin bin stape 0x013081 0mbcrw-rw-rw- bin bin stape 0x013041 0mncrw-rw-rw- bin bin stape 0x0130c1 0mnbcrw-rw-rw- bin bin stape 0x013000 c1t3d0BESTcrw-rw-rw- bin bin stape 0x013080 c1t3d0BESTbcrw-rw-rw- bin bin stape 0x013040 c1t3d0BESTncrw-rw-rw- bin bin stape 0x0130c0 c1t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x017000 c1t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5



UNIX Device Files � C240 and Earlier: B180L Controller

B180L ControllerTable 3-6 Device files on the B180L Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos Filename Function Where Usedcrw-rw-rw- root other sts 0x011070 acs Performance Port ACScrw-rw-rw- root other sts 0x011020 bcr EFS bar code reader, MUX port 3crw-rw-rw- bin bin beep 0x000000 beep crw-rw-rw- lp bin CentIf 0x020002 c2t0d0_lpcrw-rw-rw- root other hpib 0x070e00 counter Countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x011030 cuash04 Modemcrw-rw-rw- root other sts 0x011040 cuash05 Modemcrw-rw-rw- root other sts 0x011050 cuash06 Modemcrw-rw-rw- root other sts 0x011060 cuash07 Modemcrw-rw-rw- root other sts 0x011070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- root root btlan3 0x000001 ether0 System LANcrw-r--r-- root root 0x430001 ether1 EISA LANcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x011010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-r--r-- root root 0x430000 ieee1crw-rw-rw- root other sts 0x011010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x011020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x011030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- root root btlan3 0x000000 lan0 Customer�s site LANcrw-r--r-- root root 0x430000 lan1 Testhead LANcrw------- lp bin CentIf 0x020002 lp



crw------- bin bin asio0 0x000080 mux0crw------- bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2crw-rw-rw- bin bin ps2 0x000000 ps2_0crw-rw-rw- bin bin ps2 0x000010 ps2_1crw-rw-rw- bin bin ps2 0x000003 ps2kbdcrw-rw-rw- bin bin ps2 0x000001 ps2mouse Mousecrw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- root other beep 0x000000 rhilcrw-rw-rw- root other beep 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 Strip printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw-rw-rw- bin bin t60488 0x000000 t60488.0crw-rw-rw- bin bin t60488 0x010000 t60488.1crw-rw-rw- bin bin t60488 0x020000 t60488.2crw-rw-rw- bin bin t60488 0x030000 t60488.3crw-rw-rw- bin bin t60488 0x040000 t60488.4crw-rw-rw- bin bin t60488 0x050000 t60488.5crw-rw-rw- bin bin t60488 0x060000 t60488.6crw-rw-rw- bin bin t60488 0x070000 t60488.7

Table 3-6 Device files on the B180L Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos Filename Function Where Used



crw--w--w- bin bin asio0 0x000000 tty0p0crw--w--w- bin bin asio0 0x010000 tty1p0crw------- root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem devicecrw-rw-rw- root other sts 0x011030 ttyds04crw-rw-rw- root other sts 0x011040 ttyds05crw-rw-rw- root other sts 0x011050 ttyds06crw-rw-rw- root other sts 0x011060 ttyds07crw-rw-rw- root other sts 0x011070 ttyds08crw-rw-rw- root other sts 0x011030 ttydsh04crw-rw-rw- root other sts 0x011040 ttydsh05crw-rw-rw- root other sts 0x011050 ttydsh06crw-rw-rw- root other sts 0x011060 ttydsh07crw-rw-rw- root other sts 0x011070 ttydsh08crw-rw-rw- root other sts 0x011000 ttyjb1 Button adaptercrw-rw-rw- root other sts 0x011000 ttym01 Terminal MUX 1 Port 1crw-rw-rw- root other sts 0x011010 ttym02 Terminal MUX 1 Port 2crw-rw-rw- root other sts 0x011020 ttym03 Terminal MUX 1 Port 3crw-rw-rw- root other sts 0x011030 ttym04 Terminal MUX 1 Port 4crw-rw-rw- root other sts 0x011040 ttym05 Terminal MUX 1 Port 5crw-rw-rw- root other sts 0x011050 ttym06 Terminal MUX 1 Port 6crw-rw-rw- root other sts 0x011060 ttym07 Terminal MUX 1 Port 7crw-rw-rw- root other sts 0x011070 ttym08 Terminal MUX 1 Port 8crw-rw-rw- root other sts 0x011030 tycuas04crw-rw-rw- root other sts 0x011040 tycuas05crw-rw-rw- root other sts 0x011050 tycuas06crw-rw-rw- root other sts 0x011060 tycuas07crw-rw-rw- root other sts 0x011070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x013001 0mcrw-rw-rw- bin bin stape 0x013081 0mb




crw-rw-rw- bin bin stape 0x013041 0mncrw-rw-rw- bin bin stape 0x0130c1 0mnbcrw-rw-rw- bin bin stape 0x013000 c1t3d0BESTcrw-rw-rw- bin bin stape 0x013080 c1t3d0BESTbcrw-rw-rw- bin bin stape 0x013040 c1t3d0BESTncrw-rw-rw- bin bin stape 0x0130c0 c1t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x017000 c1t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5




C240 ControllerTable 3-7 Device files on the C240 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos Filename Function where Usedcrw-rw-rw- root other sts 0x011070 acs Performance Port ACScrw-rw-rw- root other sts 0x011020 bcr Bar code readercrw-rw-rw- bin bin beep 0x000000 beep crw-rw-rw- lp bin CentIf 0x010002 c2t0d0_lpcrw--w--w- root sys cn 0x000000 consolecrw-rw-rw- root other hpib 0x070e00 countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other sts 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x011030 cuash04 Modemcrw-rw-rw- root other sts 0x011040 cuash05 Modemcrw-rw-rw- root other sts 0x011050 cuash06 Modemcrw-rw-rw- root other sts 0x011060 cuash07 Modemcrw-rw-rw- root other sts 0x011070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- root root btlan3 0x000001 ether0 System LANcrw-r--r-- root root btlan3 0x430001 ether1 EISA LANcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x011010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-r--r-- root root 0x430000 ieee1crw-rw-rw- root other sts 0x011010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x011020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x011030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- root root btlan3 0x000000 lan0 Customer�s site LANcrw-r--r-- root root 0x430000 lan1 Testhead LAN



crw------- lp bin CentIf 0x020002 lpcrw------- bin bin asio0 0x000080 mux0crw------- bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT powe supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT powe supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT powe supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT powe supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT powe supply 2crw-rw-rw- bin bin ps2 0x000000 ps2_0crw-rw-rw- bin bin ps2 0x000010 ps2_1crw-rw-rw- bin bin ps2 0x000003 ps2kbdcrw-rw-rw- bin bin ps2 0x000001 ps2mousecrw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT powe supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT powe supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT powe supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT powe supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT powe supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT powe supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT powe supply 9crw-rw-rw- root other beep 0x000000 rhilcrw-rw-rw- root other beep 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 Strip printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw-rw-rw- bin bin t60488 0x000000 t60488.0crw-rw-rw- bin bin t60488 0x010000 t60488.1crw-rw-rw- bin bin t60488 0x020000 t60488.2crw-rw-rw- bin bin t60488 0x030000 t60488.3crw-rw-rw- bin bin t60488 0x040000 t60488.4crw-rw-rw- bin bin t60488 0x050000 t60488.5crw-rw-rw- bin bin t60488 0x060000 t60488.6

Table 3-7 Device files on the C240 Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos Filename Function where Used



crw-rw-rw- bin bin t60488 0x070000 t60488.7crw--w--w- bin bin asio0 0x000000 tty0p0 Modem devicecrw--w--w- bin bin asio0 0x010000 tty1p0crw------- root sys cn 0x000001 ttyconfcrw--w--w- uucp other asio0 0x000002 ttyd0p0crw-rw-rw- root other sts 0x011030 ttyds04crw-rw-rw- root other sts 0x011040 ttyds05crw-rw-rw- root other sts 0x011050 ttyds06crw-rw-rw- root other sts 0x011060 ttyds07crw-rw-rw- root other sts 0x011070 ttyds08crw-rw-rw- root other sts 0x011030 ttydsh04crw-rw-rw- root other sts 0x011040 ttydsh05crw-rw-rw- root other sts 0x011050 ttydsh06crw-rw-rw- root other sts 0x011060 ttydsh07crw-rw-rw- root other sts 0x011070 ttydsh08crw-rw-rw- root other sts 0x011000 ttyjb1 Button adaptercrw-rw-rw- root other sts 0x011000 ttym01 Terminal MUX 1 Port 1crw-rw-rw- root other sts 0x011010 ttym02 Terminal MUX 1 Port 2crw-rw-rw- root other sts 0x011020 ttym03 Terminal MUX 1 Port 3crw-rw-rw- root other sts 0x011030 ttym04 Terminal MUX 1 Port 4crw-rw-rw- root other sts 0x011040 ttym05 Terminal MUX 1 Port 5crw-rw-rw- root other sts 0x011050 ttym06 Terminal MUX 1 Port 6crw-rw-rw- root other sts 0x011060 ttym07 Terminal MUX 1 Port 7crw-rw-rw- root other sts 0x011070 ttym08 Terminal MUX 1 Port 8crw-rw-rw- root other sts 0x011030 tycuas04crw-rw-rw- root other sts 0x011040 tycuas05crw-rw-rw- root other sts 0x011050 tycuas06crw-rw-rw- root other sts 0x011060 tycuas07crw-rw-rw- root other sts 0x011070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x005000 c0t5d0brw-r----- bin sys sdisk 0x006000 c0t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x013001 0m




crw-rw-rw- bin bin stape 0x013081 0mbcrw-rw-rw- bin bin stape 0x013041 0mncrw-rw-rw- bin bin stape 0x0130c1 0mnbcrw-rw-rw- bin bin stape 0x013000 c1t3d0BESTcrw-rw-rw- bin bin stape 0x013080 c1t3d0BESTbcrw-rw-rw- bin bin stape 0x013040 c1t3d0BESTncrw-rw-rw- bin bin stape 0x0130c0 c1t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x017000 c1t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5



4444 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



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 Files at B.03.81 or Later

Starting at software revision B.03.81, device driver major numbers are dynamically assigned. This section describes the supported method for rebuilding device files at B.03.81 and later.

The minor numbers for the device files have not changed. Use the minor numbers that are in the following tables.

Process for Rebuilding Device Files� Use Table 4-1 on page 4-3 to locate the driver for

the device file.

� Use the lsdev command to determine the correct major number associated with the driver (see Example for Recreating a Device File).

Example for Recreating a Device FileThis example recreates the device file /dev/ttyjb1. You must be root to execute this procedure.

1 Locate the device file in Table 4-1 on page 4-3. This device file is associated with the sts driver.

2 Execute the /usr/sbin/lsdev -d <driver> command (the <driver> argument is case-sensitive):# /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

matches the following tables is a coincidence; the major number may not always be 137.

4 Remove the device file:# rm /dev/ttyjb1

5 Use the mknod command to rebuild the device file. Use the major number 137 that is associated with the sts driver:# mknod /dev/ttyjb1 c 137 0x011000

6 Set the correct permissions. The permissions have not changed; use the same permissions that are in the following tables:# chmod 666 /dev/ttyjb1# chown root:other /dev/ttyjb1

NOTEAn asterisk (*) in the name of a driver or device file indicates that it can be replaced by any combination of letters or numbers. For example, the btlan* driver in Table 4-1 refers to all btlan drivers (btlan0, btlan1, etc).

Character Block Driver Class137 -1 sts comm


UNIX Device Files � B2000 and Later: Rebuilding Device Files at B.03.81 or Later

NOTEWith 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 Filesasio0 Serial Port Interface cua0p0, cul0p0, mux0, mux1, rpr1, tty0p0, tty1p0, ttyd0p0btlan*lan2

LAN Interface (C240, B180L, B2000)LAN Interface (C110, 725, 712)

ether*, ieee*, lan*

CentIfSCentIf

Parallel Port Interface c*t0d0_lp, lp

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

(C240, B180L, B2000)t60488*


UNIX Device Files � B2000 and Later: B2000 Controller

B2000 ControllerTable 4-2 Device files on the B2000 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos Filename Function Where Usedcrw-rw-rw- root other sts 0x031070 acs Performance Port ACScrw-rw-rw- root other sts 0x031020 bcr EFS bar code reader, MUX port 3crw-rw-rw- bin bin beep 0x000000 beep crw-rw-rw- lp bin SCentIf 0x010002 c1t0d0_lpcrw-rw-rw- root other hpib 0x070e00 counter Countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x031030 cuash04 Modemcrw-rw-rw- root other sts 0x031040 cuash05 Modemcrw-rw-rw- root other sts 0x031050 cuash06 Modemcrw-rw-rw- root other sts 0x031060 cuash07 Modemcrw-rw-rw- root other sts 0x031070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- root root btlan3 0x000001 ether0 System LANcrw-r--r-- root root 0x430001 ether1 EISA LANcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x031010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-rw-rw- bin bin hub 0x000000 hubcrw-r--r-- root root 0x430000 ieee1crw-rw-rw- root other sts 0x031010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x031020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x031030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- root root btlan3 0x000000 lan0 Customer�s site LANcrw-r--r-- root root 0x430000 lan1 Testhead LAN



crw------- lp bin SCentIf 0x020002 lpcrw------- bin bin asio0 0x000080 mux0crw------- bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2crw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- root other beep 0x000000 rhilcrw-rw-rw- root other beep 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 Strip printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw-rw-rw- bin bin t60488 0x000000 t60488.0crw-rw-rw- bin bin t60488 0x010000 t60488.1crw-rw-rw- bin bin t60488 0x020000 t60488.2crw-rw-rw- bin bin t60488 0x030000 t60488.3crw-rw-rw- bin bin t60488 0x040000 t60488.4crw-rw-rw- bin bin t60488 0x050000 t60488.5crw-rw-rw- bin bin t60488 0x060000 t60488.6crw-rw-rw- bin bin t60488 0x070000 t60488.7crw--w--w- bin bin asio0 0x000000 tty0p0crw--w--w- bin bin asio0 0x010000 tty1p0crw------- root sys cn 0x000001 ttyconf

Table 4-2 Device files on the B2000 Controller (B.03.XX / HP-UX 10.X) (continued)Permissions Owner Group Driver Minor Nos Filename Function Where Used



crw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem devicecrw-rw-rw- root other sts 0x031030 ttyds04crw-rw-rw- root other sts 0x031040 ttyds05crw-rw-rw- root other sts 0x031050 ttyds06crw-rw-rw- root other sts 0x031060 ttyds07crw-rw-rw- root other sts 0x031070 ttyds08crw-rw-rw- root other sts 0x031030 ttydsh04crw-rw-rw- root other sts 0x031040 ttydsh05crw-rw-rw- root other sts 0x031050 ttydsh06crw-rw-rw- root other sts 0x031060 ttydsh07crw-rw-rw- root other sts 0x031070 ttydsh08crw-rw-rw- root other sts 0x031000 ttyjb1 Button adaptercrw-rw-rw- root other sts 0x031000 ttym01 Terminal MUX 1 Port 1crw-rw-rw- root other sts 0x031010 ttym02 Terminal MUX 1 Port 2crw-rw-rw- root other sts 0x031020 ttym03 Terminal MUX 1 Port 3crw-rw-rw- root other sts 0x031030 ttym04 Terminal MUX 1 Port 4crw-rw-rw- root other sts 0x031040 ttym05 Terminal MUX 1 Port 5crw-rw-rw- root other sts 0x031050 ttym06 Terminal MUX 1 Port 6crw-rw-rw- root other sts 0x031060 ttym07 Terminal MUX 1 Port 7crw-rw-rw- root other sts 0x031070 ttym08 Terminal MUX 1 Port 8crw-rw-rw- root other sts 0x031030 tycuas04crw-rw-rw- root other sts 0x031040 tycuas05crw-rw-rw- root other sts 0x031050 tycuas06crw-rw-rw- root other sts 0x031060 tycuas07crw-rw-rw- root other sts 0x0311070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x000000 c0t0d0brw-r----- bin sys sdisk 0x026000 c2t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x033000 0mcrw-rw-rw- bin bin stape 0x033080 0mbcrw-rw-rw- bin bin stape 0x033040 0mncrw-rw-rw- bin bin stape 0x0330c0 0mnbcrw-rw-rw- bin bin stape 0x033000 c3t3d0BEST




crw-rw-rw- bin bin stape 0x033080 c3t3d0BESTbcrw-rw-rw- bin bin stape 0x033040 c3t3d0BESTncrw-rw-rw- bin bin stape 0x0330c0 c3t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x027000 c2t7d0crw-r----- bin sys sctl 0x037000 c3t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5brw-r----- root sys lv 0x000006 lvol6crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5crw-r----- root sys lv 0x000006 rlvol6



UNIX Device Files � B2000 and Later: C3600 Controller

C3600 ControllerTable 4-3 Device files on the C3600 Controller (B.03.XX / HP-UX 10.X)Permissions Owner Group Driver Minor Nos Filename Function Where Usedcrw-rw-rw- root other sts 0x031070 acs Performance Port ACScrw-rw-rw- root other sts 0x031020 bcr EFS bar code reader, MUX port 3crw-rw-rw- bin bin beep 0x000000 beep crw-rw-rw- lp bin SCentIf 0x010002 c1t0d0_lpcrw-rw-rw- root other hpib 0x070e00 counter Countercrw-rw-rw- bin bin framebuf 0x000000 crtcrw-rw-rw- bin bin framebuf 0x000000 crt0crw-rw-rw- root other asio0 0x000001 cua0p0 Modemcrw-rw-rw- root other sts 0x031030 cuash04 Modemcrw-rw-rw- root other sts 0x031040 cuash05 Modemcrw-rw-rw- root other sts 0x031050 cuash06 Modemcrw-rw-rw- root other sts 0x031060 cuash07 Modemcrw-rw-rw- root other sts 0x031070 cuash08 Modemcrw-rw-rw- root other asio0 0x000001 cul0p0 Modemcrw-rw-rw- root other hpib 0x070a00 dmm Functional DMMcrw-rw-rw- root other hpib 0x070b00 dmm_ref Calibration DMMcrw-rw-rw- root root btlan3 0x000001 ether0 System LANcrw-r--r-- root root 0x430001 ether1 EISA LANcrw-rw-rw- root other 0x0c0000 gpio1 GPIO to testheadcrw-rw-rw- root other hpib 0x070800 hp3488 Board handler switch/controlcrw-rw-rw- root other sts 0x031010 hp44990 EFS Board Handlercrw-rw-rw- root other hpib 0x070880 hp79000slot0 79000 VXIcrw-rw-rw- root other hpib 0x071f00 hpib1crw-rw-rw- bin bin hub 0x000000 hubcrw-r--r-- root root 0x430000 ieee1crw-rw-rw- root other sts 0x031010 JOT_PLC JOT Board Handlercrw-rw-rw- root other sts 0x031020 JOT_BCR_P0 JOT Bar Code Readercrw-rw-rw- root other sts 0x031030 JOT_BCR_P1 JOT Bar Code Readercrw-rw-rw- root root btlan3 0x000000 lan0 Customer�s site LANcrw-r--r-- root root 0x430000 lan1 Testhead LAN



crw------- lp bin SCentIf 0x020002 lpcrw------- bin bin asio0 0x000080 mux0crw------- bin bin asio0 0x010080 mux1crw-rw-rw- bin bin mm 0x000002 nullcrw-rw-rw- bin bin framebuf 0x000001 ocrtcrw-rw-rw- bin bin framebuf 0x000001 ocrt0crw-rw-rw- root other hpib 0x071600 ps0 GPIB DUT power supply 0crw-rw-rw- root other hpib 0x071700 ps1 GPIB DUT power supply 1crw-rw-rw- root other hpib 0x070300 ps10 GPIB DUT power supply 10crw-rw-rw- root other hpib 0x070400 ps11 GPIB DUT power supply 11crw-rw-rw- root other hpib 0x071800 ps2 GPIB DUT power supply 2crw-rw-rw- root other hpib 0x071900 ps3 GPIB DUT power supply 3crw-rw-rw- root other hpib 0x071a00 ps4 GPIB DUT power supply 4crw-rw-rw- root other hpib 0x071b00 ps5 GPIB DUT power supply 5crw-rw-rw- root other hpib 0x071c00 ps6 GPIB DUT power supply 6crw-rw-rw- root other hpib 0x071d00 ps7 GPIB DUT power supply 7crw-rw-rw- root other hpib 0x070100 ps8 GPIB DUT power supply 8crw-rw-rw- root other hpib 0x070200 ps9 GPIB DUT power supply 9crw-rw-rw- root other beep 0x000000 rhilcrw-rw-rw- root other beep 0x000000 rhil_0crw-rw-rw- root other asio0 0x010004 rpr1 Strip printercrw-rw-rw- root other hpib 0x070700 scope Oscilloscopecrw-rw-rw- root other hpib 0x071100 synthcrw-rw-rw- bin bin t60488 0x000000 t60488.0crw-rw-rw- bin bin t60488 0x010000 t60488.1crw-rw-rw- bin bin t60488 0x020000 t60488.2crw-rw-rw- bin bin t60488 0x030000 t60488.3crw-rw-rw- bin bin t60488 0x040000 t60488.4crw-rw-rw- bin bin t60488 0x050000 t60488.5crw-rw-rw- bin bin t60488 0x060000 t60488.6crw-rw-rw- bin bin t60488 0x070000 t60488.7crw--w--w- bin bin asio0 0x000000 tty0p0crw--w--w- bin bin asio0 0x010000 tty1p0crw------- root sys cn 0x000001 ttyconf




crw--w--w- uucp other asio0 0x000002 ttyd0p0 Modem devicecrw-rw-rw- root other sts 0x031030 ttyds04crw-rw-rw- root other sts 0x031040 ttyds05crw-rw-rw- root other sts 0x031050 ttyds06crw-rw-rw- root other sts 0x031060 ttyds07crw-rw-rw- root other sts 0x031070 ttyds08crw-rw-rw- root other sts 0x031030 ttydsh04crw-rw-rw- root other sts 0x031040 ttydsh05crw-rw-rw- root other sts 0x031050 ttydsh06crw-rw-rw- root other sts 0x031060 ttydsh07crw-rw-rw- root other sts 0x031070 ttydsh08crw-rw-rw- root other sts 0x031000 ttyjb1 Button adaptercrw-rw-rw- root other sts 0x031000 ttym01 Terminal MUX 1 Port 1crw-rw-rw- root other sts 0x031010 ttym02 Terminal MUX 1 Port 2crw-rw-rw- root other sts 0x031020 ttym03 Terminal MUX 1 Port 3crw-rw-rw- root other sts 0x031030 ttym04 Terminal MUX 1 Port 4crw-rw-rw- root other sts 0x031040 ttym05 Terminal MUX 1 Port 5crw-rw-rw- root other sts 0x031050 ttym06 Terminal MUX 1 Port 6crw-rw-rw- root other sts 0x031060 ttym07 Terminal MUX 1 Port 7crw-rw-rw- root other sts 0x031070 ttym08 Terminal MUX 1 Port 8crw-rw-rw- root other sts 0x031030 tycuas04crw-rw-rw- root other sts 0x031040 tycuas05crw-rw-rw- root other sts 0x031050 tycuas06crw-rw-rw- root other sts 0x031060 tycuas07crw-rw-rw- root other sts 0x0311070 tycuas08/dev/dskbrw-r----- bin sys sdisk 0x000000 c0t0d0brw-r----- bin sys sdisk 0x026000 c2t6d0/dev/rmtcrw-rw-rw- bin bin stape 0x033000 0mcrw-rw-rw- bin bin stape 0x033080 0mbcrw-rw-rw- bin bin stape 0x033040 0mncrw-rw-rw- bin bin stape 0x0330c0 0mnbcrw-rw-rw- bin bin stape 0x033000 c3t3d0BEST




crw-rw-rw- bin bin stape 0x033080 c3t3d0BESTbcrw-rw-rw- bin bin stape 0x033040 c3t3d0BESTncrw-rw-rw- bin bin stape 0x0330c0 c3t3d0BESTnbcrw-r--r-- bin bin stape 0xfffffe stape_config/dev/rscsicrw-r----- bin sys sctl 0x007000 c0t7d0crw-r----- bin sys sctl 0x027000 c2t7d0crw-r----- bin sys sctl 0x037000 c3t7d0/dev/vg00crw-r----- root sys lv 0x000000 groupbrw-r----- root sys lv 0x000001 lvol1brw-r----- root sys lv 0x000002 lvol2brw-r----- root sys lv 0x000003 lvol3brw-r----- root sys lv 0x000004 lvol4brw-r----- root sys lv 0x000005 lvol5brw-r----- root sys lv 0x000006 lvol6crw-r----- root sys lv 0x000001 rlvol1crw-r----- root sys lv 0x000002 rlvol2crw-r----- root sys lv 0x000003 rlvol3crw-r----- root sys lv 0x000004 rlvol4crw-r----- root sys lv 0x000005 rlvol5crw-r----- root sys lv 0x000006 rlvol6



5555 UNIX Controller Cabling DiagramsE4000-90300 Rev. J 11/2003

In this Chapter... � 712/60/100 Controller, 5-2




� B180L Controller, 5-14


� B2000 Controller, 5-20



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 Controller

See Figure 5-1 on page 5-4.

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.



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

Table 5-1 712/60/100 Controller cables and devices � Series II (continued)



Figure 5-1 712/60/100 Controller details � Series II (See Table 5-1 on page 5-2)

712-1.WPG

712 Controller

Modem

Footswitch

Mod 3 Mod 2 Mod 1 Mod 0

Mouse

BCS

Keyboard

Monitor

To Site LAN

Load"T" &

Load"T" &

A B C D E F

Testhead - Control Cards

DUT P.S.A A A A

34

8

03066-66581

LAN/HP-IB

Load"T" &

DUT P.S.

DUT P.S.

DDS Drive

StripPrinter

1J

G

7

B

CD

12

E

3

47

H

F L

I

85

10

11

R

6

7

7

S

2

K

Series IISystem Card

P P

18

MTerminals

9

NMN


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)




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.

Table 5-2 725/50 Controller cables and devices � Series II (continued)



Figure 5-2 725/50 Controller details � Series II (See Table 5-2 on page 5-5)

725 1 WPG

Modem

StripPrinter

Footswitch


DUT P.S.

LinePrinter

MouseBCR

Keyboard

Monitor

To Site LAN

Load"T" &

Load"T" &

A B C D E F

PPU Button Adapter

Board Handler BCRBoard Handler


Load"T" &

DUT P.S.

DUT P.S.

A A A A

8

B

1Adapter2

34

F

8G

H

I

K

6

L5 7

7M

J8

N

N

N

D

EC

9

03066-66581

O

P

725/50Controller




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 adapterNot 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)



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

Table 5-3 725/100 Controller cables and devices � Series II (continued)



Figure 5-3 725/100 Controller details � Series II (See Table 5-3 on page 5-8)

725-2.WPG

Modem

StripPrinter

Footswitch


DUT P.S.

LinePrinter

Mouse

BC

KeyboardMonitor

To Site LAN

Load"T" &

Load"T" &

A B C D E F

PPU Button Adapter



Load"T" &

DUT P.S.

DUT P.S.

A A A A

8

B

1Adapter2

34

F

8G

H

I

K

6 L5

7 10

M

J8

N

N

N

D

EC

9

03066-66581

O

P

725/100Controller

11

R



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




1 44902-60000 Footswitch





6 A4490A Monitor

7 A2839B Mouse

8 1250-0781 BNC 'T'



9 A2840B Keyboard



Table 5-4 C110 Controller cables and devices � Series II (continued)



Figure 5-4 C110 Controller details � Series II (See Table 5-4 on page 5-11)

C110-1.WPG

Modem

StripPrinter

Footswitch


DUT P.S.

Mouse

BCS

KeyboardMonitor

To Site LAN

Load"T" &

Load"T" &

A B C D E F

PPU Button Adapter



DUT P.S.

DUT P.S.

A A A A

8

B

1Adapter 2

34

8

I

J6

K5

79

L

8

D

E

C

03066-66581

P

R

C110Controller

S


G

18 11

MTerminals

1 HP-IB2 Empty3 LAN4 Graph

H

10

S

K

N

F

MN


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)



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) or8120-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

Table 5-5 B180L Controller cables and devices � Series 3 / 79000 (continued)



Figure 5-5 B180L Controller details � Series 3 / 79000 (See Table 5-5 on page 5-14)

B180L-1.WPG

Modem

StripPrinter

Footswitch


DUT P.S.

Mouse

BCS

KeyboardMonitor

To Site LAN

Load"T" &

A B C D E F

PPU Button Adapter


Testhead - ControlXT Cards

DUT P.S.

DUT P.S.A

B

1

2

34

7

L

6

I5

8

D

E

C

03066-66581

K P

Series II/3 / 79000System Card

G

1810

MTerminals H

9

P

N

F

MN

ParallelPrinter

B180L

7

11

S

8

Hub

T

R

J

P.S.U

7



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)





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

Table 5-6 C240 Controller cables and devices � Series 3 / 79000



Figure 5-6 C240 Controller details � Series 3 / 79000 (See Table 5-6 on page 5-17)

C240-1.W PG

Modem

StripPrinter

Footswitch


DUT P.S.

Mouse

BCS

KeyboardMonitor

To Site LAN

Load"T" &

A B C D E F

PPU Button Adapter



DUT P.S.

DUT P.S.A

B1

2

34

7

L I5

8

D

E

03066-66581

K


G

1810

MTerminals H

9

N

F

MN

ParallelPrinter

C240

7S

8

T

P

6P.S.

U

C

11Hub

7

R

J


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 E9970-63200E4000-62106E4000-62105

RJ-45 Cable, shielded, 4-meter plus:DB-9 adapter for PPU button adapterDB-25 adapter for board handlerDCE 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





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

Table 5-7 B2000 controller (A5983A) cables and devices � Series 3 / 79000 UNIX (continued)



Figure 5-7 B2000 controller details � Series 3 / 79000 UNIX (See Table 5-7 on page 5-20)

B2000.WPG

StripPrinter

Footswitch

LinePrinter

Mouse KeyboardMonitor

B

1

2

L

4

6

D

P

B2000 Controller


A B C D E F


A

03066-66581


7S

T

2 3 41

To Site LAN

BCR

C

11

Hub7

R

H5

V

(UNIX)

DATDATP.S.

DUT P.S.

DUT P.S.

DUT P.S.

E

DUT P.S.

1

8

10

M

9

PPU Button AdapterBoard HandlerBoard Handler BCR

Terminals

PK

1

2

F

N

1

2

USB

3

Port 1reservedfor UPS



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-6773E9970-63200E4000-62106E4000-62105

RJ-45 Cable, shielded, 4-meter plus:DB-9 adapter for PPU button adapterDB-25 adapter for board handlerDCE 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





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 1250-02071250-20761252-1650

BNC T50-ohm BNC Load/Termination50-ohm SMB Load/TerminationHook & 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

Table 5-8 C3600 controller cables and devices � Series 3 / 79000 (continued)



Figure 5-8 C3600 controller details � Series 3 / 79000 UNIX (See Table 5-8 on page 5-23)

C3600.WPG

StripPrinter

Footswitch

LinePrinter

Mouse KeyboardMonitor

B

1

2

L

4

6

D

P

C3600 Controller


A B C D E F

Testhead - ControlXT/XTP Cards

A

03066-66581


7S

T

2 3 41

To Site LAN

BCR

C

11

Hub7

R

H5

V

(UNIX)

DATDATP.S.

DUT P.S.

DUT P.S.

DUT P.S.

E

DUT P.S.

1

8

10

M

9

PPU Button AdapterBoard HandlerBoard Handler BCR

Terminals

P

K1

2N

1

2

USB

3

5 6

F

Port 1reservedfor UPS

Wide SCSI

Printed in Singapore11/2003

E4000-90300 Rev. J

Documents

3070 / 79000 Board Test Systems - Keysight / 79000 Board Test Systems System Installation Manual ... This chapter describes the installation of the Agilent 3070 Series 3 and 79000