Administering Agilent 3070 Systems MS Windows® NT® and 2000® January 2004
Contents Administering Agilent 3070 Systems (MS Windows NT and 2000) 1 Introduction About This Manual ................................................................................................................ 1-1 Who Should Use This Manual............................................................................................... 1-1 Summary of System Administration Tasks ................................................................................. 1-2 How Many Administrators are Necessary? .
Table of Contents Booting a 3070 Controller ..................................................................................................... 2-2 Logging In.............................................................................................................................. 2-3 Booting the Testhead ............................................................................................................. 2-3 Shutting Down the System ............................................................
Table of Contents Configuring a Network Adapter Card (Local Area Connection) .............................................. 3-18 4 Backing Up and Restoring System Software Introduction............................................................................................................................ 4-1 Objectives .............................................................................................................................. 4-1 Prerequisites.........................................
Table of Contents Disaster Recovery Procedure............................................................................................... 4-20 How to Restore a System From a Full Backup Tape........................................................... 4-22 Restoring a 3070 System from the System Recovery DVD ...................................................... 4-28 Introduction..........................................................................................................................
Table of Contents Introduction............................................................................................................................ 6-2 The $AGILENT3070_ROOT Environment Variable ........................................................... 6-2 $AGILENT3070_ROOT on UNIX............................................................................................. 6-2 $AGILENT3070_ROOT on MS Windows.................................................................................
Table of Contents Client.................................................................................................................................... 7-10 Server ................................................................................................................................... 7-10 Client/Server ........................................................................................................................ 7-10 The MS Windows Controller as Server .............................
Table of Contents BT-BASIC Quick-Reference ..................................................................................................... 8-17 NT Korn Shell Quick Reference................................................................................................ 8-18 vi and viw Editor Quick Reference............................................................................................ 8-21 Codewords .........................................................................................
Table of Contents Introduction.......................................................................................................................... 8-40 Location of Device Files...................................................................................................... 8-40 If a DUT Power Supply is Replaced.................................................................................... 8-40 DUT Power Supply Device Files.....................................................................
1 In this Chapter... Introduction ■ Summary of System Administration Tasks, 1-2 ■ 3070 Software Overview, 1-3 ■ 3070 Hardware Overview, 1-8 You should also have a basic working knowledge of MS Windows® NT or 2000 operating systems and experience in system administration. About This Manual Welcome to Administering Agilent 3070 Systems (MS Windows NT and 2000) This manual contains information for administering 3070 board test systems running on MS Windows® 2000 Professional and NT operating systems.
Chapter 1: Introduction Summary of System Administration Tasks How Many Administrators are Necessary? Responsibilities Ideally, a system should have one system administrator and a backup. It could be necessary to have one system administrator per shift. The system administrator’s responsibilities include managing system installation, setup, configuration, networking, and security. Avoid maintenance conflicts by keeping as few system administrators as necessary.
Chapter 1: Introduction 3070 Software Overview This section contains: ■ Introduction, 1-3 ■ Capabilities of the MS Windows® 2000 Professional Operating System, 1-3 ■ The Agilent 3070 Directory Structure, 1-4 ■ Advantages of a LAN, 1-5 ■ 3070 Program Software, 1-5 computer systems, and peripheral devices over a network. ■ Multi-tasking – Several programs, processes, and tasks can be performed at the same time.
Chapter 1: Introduction The Agilent 3070 Directory Structure Table 1-1 describes the Agilent 3070 directories located under the . Table 1-1 © Agilent Technologies 2001–2003 Agilent3070 directories Directory: Directory Contents or Use autofile System autofiles bin 3070 system executable programs boards Location for customer board directories.
Chapter 1: Introduction Table 1-1 Agilent3070 directories (continued) Directory: Directory Contents or Use standard Standard 3070 templates used throughout the system. tmp Where 3070 software stores temporary files/logs. util Utility files $NUTCROOT\usr\lib\X11\ app-defaults\3070 The directory containing X resource files for X applications. $NUTCROOT is a system variable set during installation of the NutCracker runtime environment. It contains the MKS Toolkit and Korn shell.
Chapter 1: Introduction additional test-oriented statements. BT-BASIC testplans are used to control and manipulate the board test system and to run tests on the circuit boards. ■ Analog Test Language (ATL) is a set of special statements used to make in-circuit measurements on analog devices. ■ Vector Control Language (VCL) is a set of statements used to write tests for individual digital devices (in-circuit testing).
Chapter 1: Introduction © Agilent Technologies 2001–2003 Table 1-2 Standard 3070 Programs (continued) Program Use Boundary-Scan Graphical interface for testing digital devices that comply with IEEE Standard 1149.1. Conversion Tool Tool for converting board test programs and directories for cross-platform compatibility between HP-UX and MS Windows operating systems. Korn Shell Shell environment for executing UNIX commands on MS Windows operating systems.
Chapter 1: Introduction 3070 Hardware Overview This section provides an overview of 3070 test system hardware. A complete test system includes a testhead and a testhead controller. Testhead The testhead contains hardware required to execute board tests. Testhead Controller The testhead controller is a computer that controls the testhead. It is located in a testhead pod.
2 In this Chapter...
Chapter 2: Starting and Shutting Down the System Starting the System This section describes how to start and boot a 3070 MS Windows® controller and testhead. ■ Booting a 3070 Controller, 2-2 ■ Logging In, 2-3 ■ Booting the Testhead, 2-3 Booting a 3070 Controller 1 Turn on the video display and any other peripherals. 2 Turn on power to the controller. Prerequisites 3 Allow the controller to boot.
Chapter 2: Starting and Shutting Down the System Logging In Several types of logins exist for the 3070. Some logins can be created or changed by the system administrator (see Adding a User Account in Chapter 5) and some are for specialized use and cannot be changed. Logins that cannot be changed include: — For standard operator use.
Chapter 2: Starting and Shutting Down the System Shutting Down the System This section contains: ■ Introduction, 2-4 ■ Unboot the Testhead, 2-4 ■ Shut Down the Controller, 2-4 ■ Disconnecting Power to the Controller, 2-4 Shut Down the Controller CAUTION shut down the computer before turning off ✸ Always the power. It is not safe to turn off the power until Windows displays the following message: It is now safe to turn off your computer.
3 In this Chapter...
Chapter 3: Setting Up and Configuring New Systems Preparing to Set Up a System Setting up a system involves establishing a computer name, user account, and both Administrator and user passwords. Use the Windows 2000 Setup Wizard to set up your system. If you plan to connect your computer to a network, you must configure the appropriate Local Area Connections in Network and Dial-up Connections before connecting to your network.
Chapter 3: Setting Up and Configuring New Systems Information for Windows 2000 Setup The first time you start your system, the Windows 2000 Setup Wizard requests information to set up your computer. Table 3-1 summarizes the information you may need to complete the Setup Wizard. Table 3-1 Setup Information Information Description Product Key A 25-character key that uniquely identifies your copy of Windows 2000 Professional.
Chapter 3: Setting Up and Configuring New Systems © Agilent Technologies 2002, 2003 Administering Agilent 3070 Systems (MS Windows NT and 2000) 3-4
Chapter 3: Setting Up and Configuring New Systems Setting Up Windows 2000 Professional Follow the procedure in Table 3-2 to setup your Controller for Windows® 2000 Professional. Table 3-2 Setup Windows® 2000 Professional Task Step 1 Verify: • All cable connections to the controller. 2 Turn on power to the controller. 3 Complete the Windows 2000 Setup Wizard tasks.
Chapter 3: Setting Up and Configuring New Systems Additional Setup Tasks The tasks in Table 3-3 should be completed before the system is ready for users. Table 3-3 Additional setup tasks Task Step 1 Enter codewords to enable optional software features if necessary: Agilent 3070 test development systems support standard and optional software features that are licensed with Software Certificates. Optional software features are enabled by entering unique codewords found on Software Certificates.
Chapter 3: Setting Up and Configuring New Systems Table 3-3 Additional setup tasks Task Step 2 Create a system recovery tape. It is very important to make a full back up tape that can be used to recover your system in case of a disaster such as a disk crash. For instructions, see Making a Full Backup Tape on page 4-9. Re-establish the bootptab and system config files from backup files. If these files were not backed up, contact your Agilent systems engineer.
Chapter 3: Setting Up and Configuring New Systems Gathering Network Configuration Information Table 3-4 Use this section to gather the information needed to configure your computer for a LAN. Gather the Network Configuration Information Complete the information in Table 3-4 with the assistance of the network administrator or LAN manager.
Chapter 3: Setting Up and Configuring New Systems Table 3-4 Windows NT LAN configuration information (continued) Task (Network Parameter) Write System Information Here Description 5 IP Address IP Address: The IP address for this workstation. . . Subnet Mask: . . . Default Gateway: . . . . IP address of the system that is used to route network traffic to other networks.
Chapter 3: Setting Up and Configuring New Systems Table 3-4 Windows NT LAN configuration information (continued) Task (Network Parameter) Write System Information Here Description 10 DNS ■ DNS Service Search Order . . . . . . 11 DNS ■ IP Addresses (in order) of DNS servers that this system uses for resolving host names. Ordered domain suffix list used when searching for a host.
Chapter 3: Setting Up and Configuring New Systems Table 3-4 Windows NT LAN configuration information (continued) Task (Network Parameter) Write System Information Here Description 15 WINS Address ■ Scope ID 16 Will Other Network Protocols Be Configured? [ ] AppleTalk Protocol This list is not exhaustive; other protocols can be configured. Use this space to document other network protocol information.
Chapter 3: Setting Up and Configuring New Systems Network Components © Agilent Technologies 2002, 2003 Making a network requires the following basic hardware, software, and connections: ■ Network interface cards (NICs), or adapter cards - used to connect a computer to a file servers or workstations. ■ Cables - used to connect the nodes on a LAN. ■ Physical topology - the physical location of all computers on the network and the cabling system that connects them.
Chapter 3: Setting Up and Configuring New Systems Agilent Software License Activation Codeword and License Management Agilent will begin issuing license keys to replace the current codeword scheme for new 3070 features starting with software release 05.20p. At present, only new features will require the license key. This is the first step in a process that will eventually replace all Agilent 3070 codewords with license keys in future software releases.
Chapter 3: Setting Up and Configuring New Systems Figure 3-1 Software License Activation Process Flow Diagram © Agilent Technologies 2002, 2003 Administering Agilent 3070 Systems (MS Windows NT and 2000) 3-14
Chapter 3: Setting Up and Configuring New Systems Redeeming your Software License To redeem your software license, perform these steps: 1 Acquire the target controller or test development system’s hardware (MAC) address. a Login to the 3070 controller or test development system as administrator. This must be the system where you intend to activate the license, b Open a korn shell window and type lmhostid -ether. Hit Return, c This command will return the hardware or MAC address for the targeted system.
Chapter 3: Setting Up and Configuring New Systems e Follow the instructions listed below the certification number. Where it says Enter Node ID, type the 12-character hardware (MAC) address for the target system which you recorded in Step 1c. f Enter the Agilent serial number from your controller (if the controller was not supplied by Agilent, use the controller manufacturer's serial number g In the space provided, enter an email address where you can retrieve the license file.
Chapter 3: Setting Up and Configuring New Systems NOTE Software License Activation Troubleshooting If for some reason you can no longer use the license key after activation, use the following recovery process. Loss of the software key may be due to: ■ ■ hardware modification or replacement including controller, hard drive, LAN card, etc. inadvertent license file deletion, 1 Locate your software entitlement certificate and reconfirm your license activation key.
Chapter 3: Setting Up and Configuring New Systems Configuring a Network Adapter Card (Local Area Connection) A 3070 MS Windows® system includes two network adapter cards: a 3Com Etherlink XL 10/100 PCI and a Realtek RTL8139(A)-based Fast Ethernet Adapter. Agilent configures the Local Area Connection for the 3Com Etherlink XL 10/100 PCI to connect only to the testhead. Never change these settings. Table 3-5 describes how to configure a network adapter card (Local Area Connection 2).
Chapter 3: Setting Up and Configuring New Systems Table 3-5 Configuring and Connecting a Local Area Connection (continued) Task Step 3 Verify that the list of Components checked are used by this connection: includes: • • • • Client for Microsoft Networks File and Printer Sharing for Microsoft Networks NetBEUI Protocol (optional) Internet Protocol (TCP/IP) NOTE The Internet Protocol (TCP/IP) is required by the testhead controller. 4 Specify IP Addresses.
Chapter 3: Setting Up and Configuring New Systems Table 3-5 Configuring and Connecting a Local Area Connection (continued) Task Step 6 Add or edit configuration information. Click Advanced to add or edit: ADVICE Contact your IT department for configuration information and assistance. © Agilent Technologies 2002, 2003 • • • • • IP addresses Gateways DNS server addresses WINS addresses or to specify security options. 7 Accept the configuration. • Click OK. 8 Connect the LAN cable.
Chapter 3: Setting Up and Configuring New Systems Table 3-5 Configuring and Connecting a Local Area Connection (continued) Task Step 9 Run the Network Identification Wizard. a Right-click My Computer, then click Properties. b Click the Network Identification tab in the System Properties dialog box, then click Network ID. c Enter the appropriate information in the Network Identification Wizard. This wizard identifies your computer to the network.
4 In this Chapter... Backing Up and Restoring System Software ■ Planning a Backup Strategy, 4-3 Introduction ■ Preparing for Disaster Recovery, 4-4 ■ Creating Boot Recovery Diskettes, 4-6 ■ Making a Full Backup Tape, 4-9 ■ Restoring Selected Data from a Backup Tape, 4-14 A disaster recovery plan, and backup disks and tape(s) are necessary to protect your system and data against hardware failures, corrupted data, or accidental deletion of files.
Chapter 4: Backing Up and Restoring System Software Required Tools and Materials © Agilent Technologies 2001–2003 ■ TapeWare software with Disaster Recovery. ■ An HP SureStore DAT 24 tape drive or compatible DDS storage device. ■ Four (4) blank 3.5” diskettes and 24Gb blank tape (Included with the system.
Chapter 4: Backing Up and Restoring System Software Planning a Backup Strategy Data is sometimes lost when a user accidentally deletes or overwrites a file, or misuses a command. Also, a power failure or hard disk crash can result in lost or corrupted data. Data can be restored if you use effective backup procedures. One of the most important responsibilities of the system administrator is to implement an effective backup strategy.
Chapter 4: Backing Up and Restoring System Software Preparing for Disaster Recovery If you have an Industrial PC, seeDisaster Recovery for an Industrial PC Controller If your system fails, it is important to be prepared for disaster recovery. To recover your 3070 operating system, application software, and files, you need: ■ A DDS tape drive connected to your 3070 controller. ■ TapeWare software with Disaster Recovery.
Chapter 4: Backing Up and Restoring System Software Disaster Recovery for an Industrial PC Controller This information applies to 3070 systems with Industrial PC (IPC) controllers with DVD drives. Backup vs. Disaster Recovery Backup is the copying of files (board directories) to a removable media or network. Disaster recovery is the process of restoring the system to operational readiness after a major catastrophe like a hard disk failure.
Chapter 4: Backing Up and Restoring System Software Creating Boot Recovery Diskettes Introduction ■ Your 3070 system includes a set of blank diskettes that should be used at the initial system setup to create boot disk Disaster Recovery diskettes. ■ Disaster Recovery Wizard - a TapeWare application. ■ At least four blank formatted 3.5” floppy diskettes, depending on your system configuration. When to Create Boot Recovery Diskettes.
Chapter 4: Backing Up and Restoring System Software How to Create Boot Recovery Diskettes Table 4-1 describes how to create a set of boot Recovery Diskettes. Table 4-1 How to create boot Recovery Diskettes Task Step 1 Log on as Windows Administrator. a Press Ctrl-Alt-Del to log on. b The default User Name is Administrator. Click OK. No password is necessary when you receive your 3070 system. After you establish an Administrator account, you must enter the password. 2 Start TapeWare.
Chapter 4: Backing Up and Restoring System Software Table 4-1 How to create boot Recovery Diskettes (continued) Task Step 5 Label each boot Recovery Diskettes. Include: • • • • A disk name and number (example: boot disk Recovery Diskette 1 of 4) The date created. The operating system revision. The computer system name. 6 Write protect each boot Recovery Diskette and store in a secure location.
Chapter 4: Backing Up and Restoring System Software Making a Full Backup Tape Overview Your 3070 system includes an HP SureStore DAT 24 tape device and TapeWare software for performing data backups. This section describes how to perform full data backups using the TapeWare Wizard and a system compatible DDS tape drive. A full backup tape can be used to recover your operating system, application software, and data files.
Chapter 4: Backing Up and Restoring System Software How to Make a Full Backup Tape Table 4-2 describes how to make a full backup tape using the TapeWare Wizard, which may be used for disaster recovery or restoring selected data. Table 4-2 How to make a full backup tape Task Step 1 Log on as Windows Administrator. a Press Ctrl-Alt-Del to log on. b The default User Name is Administrator. Click OK. No password is necessary when you receive your 3070 system.
Chapter 4: Backing Up and Restoring System Software Table 4-2 © Agilent Technologies 2001–2003 How to make a full backup tape (continued) Task Step 5 Select a backup tape device. a Insert a blank DDS tape into a tape device that is connected to your system. b Select a backup tape device in the Wizard - Where window, then click Next. TapeWare will copy selected data to the tape in the selected device.
Chapter 4: Backing Up and Restoring System Software Table 4-2 How to make a full backup tape (continued) Task Step 6 Select the type of backup to perform. • Click Full in the Wizard - How to Backup window, then click Next. 7 Select how data will be written to tape. • Select Overwrite all tapes that are accessible in the Wizard - How to Write window. NOTE The default option is Append to any tapes that are accessible.
Chapter 4: Backing Up and Restoring System Software Table 4-2 How to make a full backup tape (continued) Task Step 8 Choose a data verification option. • Select a verification option in the Wizard - How to Verify window. Full verify is recommended for a full backup. Then click Next. Options include: No verify - Do not verify data. Full verify - Verify data on tape matches exactly data on hard drive. Quick verify - Verify data on tape is readable.
Chapter 4: Backing Up and Restoring System Software Restoring Selected Data from a Backup Tape This section describes the procedures for restoring selected data from a backup tape using TapeWare’s Restore Specific Wizard. Use this wizard to selectively restore data from individual drives, folders, or files. For instructions on restoring an entire system, see Restoring a 3070 System from a Full Backup Tape on page 4-19.
Chapter 4: Backing Up and Restoring System Software Table 4-3 © Agilent Technologies 2001–2003 How to recover specific data from a backup tape (continued) Task Step 4 Start the Restore Specific program and name the job. a Select the TapeWare Wizard tab and click Restore Specific. b Type a job name, then click Next.
Chapter 4: Backing Up and Restoring System Software Table 4-3 How to recover specific data from a backup tape (continued) Task Step 5 Select what to restore. • Select the computer, drives, folders, or files that you want to restore in the Wizard-What to Restore window. Click in the checkboxes next to the device or folder names you want to select. Then click Next. You can expand or collapse devices and folders to view the structure.
Chapter 4: Backing Up and Restoring System Software Table 4-3 How to recover specific data from a backup tape (continued) Task Step 6 Choose a tape device from which to restore data. a Select the device or folder name that represents a tape device connected to your system. If necessary, expand or collapse devices and folders until you can view and select the desired device. b Click Next.
Chapter 4: Backing Up and Restoring System Software Table 4-3 How to recover specific data from a backup tape (continued) Task Step 7 Specify when to run the restore job. a Click Now, if you want to run the job immediately. Click Save job, but don’t run it now to save the job to a file. Click Later if you want to schedule the job to run later, and follow the onscreen instructions to specify when the job should run. b Click Finish.
Chapter 4: Backing Up and Restoring System Software NOTE Restoring a 3070 System from a Full Backup Tape Introduction When you received your system you should have made recovery media by following the procedures in sections Creating Boot Recovery Diskettes on page 4-6 and Making a Full Backup Tape on page 4-9. If you did not do so, contact your Agilent board test representative. For instructions on restoring selected data, see Restoring Selected Data from a Backup Tape on page 4-14.
Chapter 4: Backing Up and Restoring System Software Required Tools and Materials To restore your system after a system failure or disk crash, you will need: The boot Recovery Diskettes enable you to boot your system and run TapeWare’s disaster recovery program, Recover.exe. This option should be used only as an emergency measure because it: ■ TapeWare software with Disaster Recovery. ■ removes all the files from the hard drive. ■ An HP SureStore DAT 24 tape drive or system compatible tape device.
Chapter 4: Backing Up and Restoring System Software You can use TapeWare to recover a boot disk or to recover all disk volumes and partitions. Table 4-4 describes the disaster recovery options you can select Table 4-4 © Agilent Technologies 2001–2003 when you boot your system from the boot Recovery Diskettes. You must use both the boot recovery diskettes and a full backup tape to restore your system.
Chapter 4: Backing Up and Restoring System Software How to Restore a System From a Full Backup Tape Table 4-5 describes how to restore a 3070 system from boot recovery diskettes and a full backup tape. NOTE Use only a complete and recent full backup tape as a disaster recovery tape. You can make other types of backups, such as Incremental, Differential, or Snapshot. These types of backups can be used to a recover a partial system or individual files, but cannot be used to restore an entire system.
Chapter 4: Backing Up and Restoring System Software Table 4-5 How to restore a system from a disaster using boot recovery diskettes and full backup tape Task Step 1 Boot from Recovery Diskette 1 and begin TapeWare Disaster Recovery (Phase 2) a Insert Recovery Diskette 1 in your floppy drive. b From the Start menu, choose Shutdown, select Restart and Click Yes. Recovery Diskette 1 contains Recover.exe, the TapeWare application that initiates the Disaster Recovery process.
Chapter 4: Backing Up and Restoring System Software Table 4-5 How to restore a system from a disaster using boot recovery diskettes and full backup tape (continued) Task Step 3 Choose a recovery option. Available options include: ■ Recover Boot Disk ■ Recover Entire System ■ Exit from Disaster Recovery WARNING this option to recover all hard disks on your system. ✸ Use NOTE: All data on the drives to be recovered will be overwritten.
Chapter 4: Backing Up and Restoring System Software Table 4-5 How to restore a system from a disaster using boot recovery diskettes and full backup tape (continued) Task Step 4 Overwrite existing partitions on the hard disk drive. a Press F10 to overwrite existing partitions, or WARNING ✸ This option overwrites all disk volumes and partitions with the data from the disaster recovery tape or backup tape. Press ESC to return to the main menu without recovering the system or its volumes.
Chapter 4: Backing Up and Restoring System Software Table 4-5 How to restore a system from a disaster using boot recovery diskettes and full backup tape (continued) Task Step 5 Insert the remaining Recovery Diskettes when prompted. NOTE Your system may automatically reboot several times after the restart process. NOTE After completing these steps, it takes approximately 30 minutes to one hour to restore your system. a Insert Recovery Diskette 2, then press F10.
Chapter 4: Backing Up and Restoring System Software Table 4-5 Task How to restore a system from a disaster using boot recovery diskettes and full backup tape (continued) Step f If your backup data spans multiple tapes, click Yes in the Do you have any more tapes that you would like TapeWare to restore to your system? window and insert additional backup tapes. Otherwise, click No. g Click Restart in the Recovery Complete window to restart your system.
Chapter 4: Backing Up and Restoring System Software CAUTION Restoring a 3070 System from the System Recovery DVD Introduction This procedure describes how to install system recovery software on your Agilent 3070 system controller (MS Windows®* system only). from the System Recovery DVD will ✸ Restoration format the C: drive and reload it to a factory default state. You will not be able to boot the testhead because certain files which are unique to your system are not restored by this process.
Chapter 4: Backing Up and Restoring System Software System Recovery Procedure 5 In the IO Config window, click OK. 6 Load the System Recovery DVD in your DVD-ROM drive. 6 In the Restart message window, click OK. 7 Restart the computer. If necessary, press the reset button on the front of the computer. 8 At the Agilent 3070: prompt, type restore system. 7 Restart the computer: click Start > Shutdown > select Restart > click OK. This concludes the recovery procedure.
5 In this chapter... Administration Tasks ■ Overview of Administration Tasks, 5-2 Prerequisites ■ Maintaining the File System, 5-3 Before you begin using this chapter, you should already: ■ Creating User Accounts, 5-4 ■ About User Accounts, 5-5 ■ User Rights, 5-6 ■ Adding a User Account, 5-6 ■ Adding a Group Account, 5-7 ■ Administering Datalogging, 5-10 ■ Installing Patches, 5-11 ■ Know how to administer an MS Windows® Workstation.
Chapter 5: Adminstration Tasks Overview of Administration Tasks This chapter describes system administration tasks as they relate to the 3070 applications. It does not describe general MS Windows® system administration. For information on any other MS Windows® administration tasks, refer to the MS Windows® documentation shipped with the system, both on line and hardcopy.
Chapter 5: Adminstration Tasks Maintaining the File System Required Tools and Materials ■ To accomplish the tasks in this section, you will need: ■ ■ Windows 2000 System Tools, such Disk Defragmenter and Disk Cleanup. • C:\temp • D:\temp ■ Administrative Tools for other file management tasks. • From the Start menu, point to Programs > Accessories > System Tools > Disk Cleanup.
Chapter 5: Adminstration Tasks Creating User Accounts Authorized users gain access to an 3070 system by supplying a valid user name (login name) and (optionally) a password. File access permissions and group permissions determine who can access a given file on MS Windows® systems. Required Tools and Materials To accomplish the tasks in this chapter, you will need: ■ Standard MS Windows® administration tools.
Chapter 5: Adminstration Tasks Table 5-2 3070 users User Name Definition and Permissions operator oil The operator account, member of the Agilent3070Operators group. This user can run BT-BASIC in operator mode, or you can create a localizable operator interface (oil). See the 3070 Online Help System for more information. user A generic user account, member of the Agilent3070Users group. service3070 Member of the Agilent3070Users group. Use this account to run DGN and troubleshoot the testhead.
Chapter 5: Adminstration Tasks User Rights User rights define the actions a user can perform on a computer. Rights can be assigned to both users and groups. By carefully planning and assigning user and group rights, you can provide secure access to files. Adding a User Account a Click Start > Settings > Control Panel > System > Advanced > Environment Variables... 1 Login as Administrator. 2 Click Start > Settings > Control Panel > Administrative Tools > Computer Management.
Chapter 5: Adminstration Tasks Adding a Group Account 2 Click Start > Programs > Administrative Tools (Common) > User Manager > User > New User. 3 Enter the Username:, Full Name:, Description:, Password:, and Confirm Password: of the and click OK. To add a group account, login as Administrator and: 1 Click Start > Settings > Control Panel > Administrative Tools > Computer Management. 4 In the User Manager window, click > User > Properties > Profile.
Chapter 5: Adminstration Tasks Make sure the user belongs to one or more of these groups to ensure proper access and security to 3070 features, applications, and files. 1 Copy the operator’s policy file to the Primary Domain Controller (PDC), which is the computer that authenticates user logins: ■ We recommend all users have a password for added system security. Copy: ■ The $AGILENT3070_ROOT system variable is set in system properties, so you do not need to set it for each user account.
Chapter 5: Adminstration Tasks 4 Transfer the operator account from the 3070 controller to the PDC: a View the Agilent3070Operators group information on the 3070. b Replicate this group account on the PDC. c View the operator user account information on the 3070. d Replicate this user account on the PDC. e Remove the operator user account information from the 3070. 5 Optional: Enable replication on all domain controllers so that the Ntconfig.
Chapter 5: Adminstration Tasks Administering Datalogging This section describes several datalogging tasks. Datalogging is described in Information Management, Chapter 2; see “Structure of the Datalogging Files.” Occasionally, the datalogging process may require your attention. If a 3070 system fails to log data, do the following: ■ ■ Verify that the translogd process, which automatically transfers log data from source queues to destination queues, is running.
Chapter 5: Adminstration Tasks Installing Patches If you receive notification of a patch release for 3070 software, you will also receive instructions on how to download and install the patch. When you install the patch software, it will find the current software, verify that all patch prerequisites are met, and load the patch. This will typically happen with no interaction required. CAUTION not install any Microsoft® Service Pack unless ✸Do specifically recommended by Agilent.
6 In this Chapter... Understanding the File System ■ The Root Directory Environment Variable, 6-2 ■ The .hp3070 File, 6-7 ■ Installing Software Packages, 6-11 3070 Reference 3070 User and Service manuals are located on 3070 system controllers and on factory-supplied updates.
Chapter 6: Understanding the File System The Root Directory Environment Variable This section contains: All subdirectories under /opt/hp3070/../.. will exist on UNIX systems for the forseeable future. ■ Introduction, 6-2 ■ The $AGILENT3070_ROOT Environment Variable, 6-2 NOTE ■ $AGILENT3070_ROOT on UNIX, 6-2 ■ $AGILENT3070_ROOT on MS Windows, 6-5 /opt/hp3070 is replaced by $AGILENT3070_ROOT on all MS Windows systems.
Chapter 6: Understanding the File System New File Path Usage in a UNIX terminal Window Table 6-1 illustrates new path equivalents using the system config file when working in a UNIX terminal window. Table 6-1 New file path usage in a UNIX shell window Before Software Release 3070 04.00 pa At and After Software Release 3070 04.
Chapter 6: Understanding the File System Table 6-2 File path usage in a BT-BASIC window Pre 3070 Software Release 3070 04.00pa 3070 Software Release 3070 05.00p At and After 3070 Software Release 3070 04.
Chapter 6: Understanding the File System $AGILENT3070_ROOT on MS Windows On MS Windows systems, the factory default value of $AGILENT3070_ROOT is C:/Agilent3070 Identify the Value of $AGILENT3070_ROOT To identify the value of $AGILENT3070_ROOT on a MS Windows system, at a shell window prompt enter: ■ Table 6-3 echo $AGILENT3070_ROOT File Path Usage in a MS Windows Korn Shell Window When working in a Korn shell window, follow the UNIX syntax by: ■ Using $variable (instead of %variable%).
Chapter 6: Understanding the File System New File Path Usage in a MS-DOS Command Prompt Window When working in a Command Prompt window: ■ Use %variable% (instead of $variable). Table 6-4 ■ Use \ (backslash) instead of / (forward slash). Table 6-4 on page 6-6 illustrates new path equivalents using the dev directory when working in a Command Prompt window. New file path usage in a MS-DOS Command Prompt window Pre 3070 Software Release 3070 04.00pa At and After 3070 Software Release3070 04.
Chapter 6: Understanding the File System The .hp3070 File The system first searches the current working directory for a .hp3070 file. If one is not found, the user’s home directory is searched. This method allows a .hp3070 file for each board. The .hp3070 file can affect system behavior in many ways. Table 6-5 Some Descriptions of .hp3070 File Keywords Some descriptions of .hp3070 file keywords are given in Table 6-5. This is not a complete description of this file.
Chapter 6: Understanding the File System Table 6-5 Some descriptions of .hp3070 file keywords (continued) keyword Description .ProgramAction The value of this option determines whether a new window is automatically opened when some commands are executed (such as execute – see Syntax Reference. .ProgramAction can be either window (a new window is automatically opened) or nowindow (a new window is not automatically opened). For example, .ProgramAction: nowindow Debug.
Chapter 6: Understanding the File System Table 6-5 Some descriptions of .hp3070 file keywords (continued) keyword Description Operator.Footswitch This option lets you specify whether the foot switch on the Agilent 3070 is enabled. Specify Yes to have the foot switch enabled, or No to have it disabled. For example, Operator.footswitch: Yes The majority of the .hp3070 file contains definitions for the operator keypad, which are invoked by an operator statement if the Operator.
Chapter 6: Understanding the File System Standard.Label7: Standard.Label8: Standard.Command1: Standard.Command2: Standard.Command3: Standard.Command4: Standard.Command5: Standard.Command6: Standard.Command7: Standard.Command8: stop exit CHAR_START CHAR_YES CHAR_NO CHAR_NULL CHAR_FAON CHAR_FAOFF CHAR_STOP CHAR_EXIT This example defines the keypad boxes which are arranged in eight columns.
Chapter 6: Understanding the File System Installing Software Packages Introduction The factory routinely releases new software packages that improve and add capabilities. Some software packages depend on a previous software package being installed. Always notify system users when a new software package is installed. Install a Software Package Installation instructions accompany software packages. Follow the instructions carefully.
7 In this Chapter...
Chapter 7: Additional Information for Networking Introduction A network is a collection of computers that communicate with each other using a set of agreed upon protocols. 3070 Networking Facilities 3070s contain networking software for: ■ LANs (local area networks). ■ Internet services. ■ File sharing. Additional facilities include software to enable: ■ remote log ons. ■ file transfers. ■ remote execution. ■ network printer servers. ■ a full range of Internet services.
Chapter 7: Additional Information for Networking Testhead IP Addresses This section contains: ■ 3070 System IP Addresses, 7-3 ■ Implications for Custom Applications, 7-3 All 3070 MS Windows systems are configured with Agilent IP addresses in the 10.3.112.XX series. To avoid network conflicts, including the inability to boot a testhead, all 3070 systems on the same network must share the same IP address series.
Chapter 7: Additional Information for Networking c Select your country and click go d Scroll down to Technical & Professional Services © Agilent Technologies 2001–2002 Administering Agilent 3070 Systems (MS Windows NT and 2000) 7-4
Chapter 7: Additional Information for Networking The Private LAN This section contains: ■ 3070 Private LAN IP Addresses, 7-5 3070 Private LAN IP Addresses Your 3070 MS Windows system includes two network adapter cards for connecting to local area networks. (LANs). The first network adapter card is configured and reserved for the private LAN. It is represented as Local Area Connection in Network and Dial-up Table 7-1 © Agilent Technologies 2001–2002 Connections.
Chapter 7: Additional Information for Networking Figure 7-1 © Agilent Technologies 2001–2002 3070 Private LAN IP Addresses Administering Agilent 3070 Systems (MS Windows NT and 2000) 7-6
Chapter 7: Additional Information for Networking The Public LAN This section contains: ■ Introduction, 7-7 ■ A User-Access Example, 7-7 Figure 7-2 LAN cable and coupler Introduction Local Area Connection 2 is the public LAN interface used for connecting to your site network. This LAN interface can be connected to your network with an RJ45 cable that is compatible with 10Base-T or 100Base-T. A 3070 MS Windows system includes an RJ45 LAN cable located at the base of the controller.
Chapter 7: Additional Information for Networking Figure 7-3 User-access example for UNIX and MS Windows test development systems and testheads MS WINDOWS Single-user (No Concurrent Access) access to MS Windows Test Development Workstation Direct OR Single-user (No Concurrent Access) access to MS Windows Testhead OR Via Networked MS Windows Direct MS Windows Testhead Controller MS Windows Test Development Workstation HUB or Switch, etc.
Chapter 7: Additional Information for Networking Bridges, Routers, and Gateways Bridges, routers, and gateways are used to connect multiple segments of a network into a unified, larger network. Typically, you will not have to worry about these devices. If installing systems onto an existing network, you may have to configure the 3070 to take advantage of the facilities that your network provides.
Chapter 7: Additional Information for Networking Clients and Servers Network A network is a group of computers that are connected and used for sharing resources such as files, software, and peripheral devices. Hosts and Nodes Each computer or device on the network is host (also known as a node). A host can be a client, server, or both. In most cases, each host functions as both a client and a server. Client A client is a computer or program that requests the services of another computer or program.
Chapter 7: Additional Information for Networking Domain Names A domain name is a unique combination of a hostname and a network domain name. A hostname is a unique name assigned to node within the network domain to which the node is connected. It is not valid to have two nodes with the same name in the same domain. TCP/IP protocols provide a number of mechanisms for mapping domain names to IP addresses.
Chapter 7: Additional Information for Networking Network Services A 3070 MS Windows system comes bundled with a variety of basic and advanced network services. The primary network services available on the 3070 are described in Table 7-2. These services may require configuration. Table 7-2 Network services Network Service Description FTP Transfer files to and from a computer running an FTP server service. To start FTP: a From the Start menu, click Run b Type ftp, then click OK.
Chapter 7: Additional Information for Networking Useful Commands The commands inTable 7-3 can be executed in a Command Prompt window. In Windows 2000, the Command Prompt replaces the MS-DOS prompt. More detailed information on these and others commands is available in Windows 2000 Professional Help. Table 7-3 © Agilent Technologies 2001–2002 To Execute a Command in a Command Prompt Window 1 Point to Start > Programs > Accessories and click Command Prompt. 2 Type the command at the C:\> prompt.
8 In this Chapter...
Chapter 8: Reference Logging-On as service3070 The service3070 logon allows system configuration and testing. Display the Logon Status from a Current Login 1 Press the keyboard keys at the same time. 2 If logged-on as service3070, click Cancel. Otherwise, click Logoff.... Logon as service3070 1 Click Start > Shut Down....
Chapter 8: Reference The Root Directory Environment Variable This section contains: ■ Introduction, 8-3 ■ Determine the Value of the Root Directory Environment Variable, 8-3 Determine the Value of the Root Directory Environment Variable ■ Use of the Root Directory Environment Variable in a BT-BASIC Window, 8-3 1 Open a Korn shell window: ■ Use of the Root Directory Environment Variable in a Korn Shell Window, 8-4 ■ Use of the Root Directory Environment Variable in a MS-DOS Command Prompt Window
Chapter 8: Reference Table 8-1 New file path usage in a BT-BASIC window Pre 3070 Software Release 3070 04.00pa 3070 Software Release 3070 05.00p At and After 3070 Software Release 3070 04.
Chapter 8: Reference Table 8-2 New file path usage in a Korn shell window Pre 3070 Software Release 3070 04.00pa At and After 3070 Software Release 3070 04.00pa D:\Agilent3070\diagnostics\th1 $AGILENT3070_ROOT\diagnostics\th1 \opt\hp3070\help\C\SERVICE $AGILENT3070_ROOT\Documentation\SERVICE Use of the Root Directory Environment Variable in a MS-DOS Command Prompt Window In a MS-DOS Command Prompt window: ■ Use %% (instead of $).
Chapter 8: Reference Directory Descriptions Table 8-4 lists descriptions of some 3070 MS Windows system directories. Table 8-4 © Agilent Technologies 2001–2002 Descriptions of various 3070 MS Windows system directories $AGILENT3070_ROOT\ The directory beneath which the vast majority of the 3070 system software resides. $AGILENT3070_ROOT\autofile The directory that contains all the autofiles for the system.
Chapter 8: Reference Table 8-4 © Agilent Technologies 2001–2002 Descriptions of various 3070 MS Windows system directories (continued) $AGILENT3070_ROOT\tmp A directory that is used by the 3070 software for storing temporary files and logs. $AGILENT3070_ROOT\util A directory that is used for storing a few utility files.
Chapter 8: Reference Editing Files This section contains: ■ Forward-Slashes versus Back-Slashes in Command Lines Containing File Paths, 8-8 ■ Use BT-BASIC, 8-8 ■ How to Edit the System Config File to Match the Testhead Configuration, 8-9 ■ How to Resolve the Standard Config File from the System Config File, 8-10 Forward-Slashes versus Back-Slashes in Command Lines Containing File Paths A general rule for commands using a path to a directory or file is to use a forward-slash (/) for commands tied t
Chapter 8: Reference Open BT-BASIC Save in BT-BASIC • Double-click the desktop BT-BASIC icon OR 1 Press F1 on the keyboard, if necessary, to toggle to the command line. Click Start > Programs > Agilent 3070 > BT-BASIC. BT-BASIC will open with the cursor on the command line. re-save Open a File in BT-BASIC Exit BT-BASIC • From the command line, enter: 1 Press F1 on the keyboard, if necessary, to toggle to the command line.
Chapter 8: Reference Table 8-5 Edit the system config file to match the testhead configuration Task Step 1 Open the system config file in a BT-BASIC window. a Open a BT-BASIC window by double-clicking the desktop icon. b From the BT-BASIC command line, enter: get btgetenv$ ("AGILENT3070_ROOT") & "/diagnostics/th1/config" 2 Arrange or modify statements to reflect the actual testhead configuration. Do this as required. 3 Save and exit the system config file.
Chapter 8: Reference No changes to the system config file are made. Table 8-6 Resolve the standard config file from the system config file Task Step 1 Make a backup copy of the standard config file: a Open a BT-BASIC window by double-clicking the desktop icon. b At the prompt, type: msi btgetenv$ ("AGILENT3070_ROOT") & "/standard" c copy "config" over "config.
Chapter 8: Reference Table 8-6 Resolve the standard config file from the system config file (continued) Task Step 5 Copy the appropriate statements from the system config file to the clipboard buffer: In the BT-BASIC window containing the system config file: a Press F1 on the keyboard to enter the workspace. b Locate the module that contains un-commented cards 1 ... statements using the arrow keys or the Prev and Next keys. c Scroll the text up until the end module statement is visible.
Chapter 8: Reference Table 8-6 Resolve the standard config file from the system config file (continued) Task 6 Paste the copied text in the standard config file: Step CAUTION ✸Do not delete the ! Specify instrument ... through ! connect ... statements. a Activate the window containing the standard config file by clicking on the window border. b Press F1 on the keyboard to enter the workspace.
Chapter 8: Reference Table 8-6 Resolve the standard config file from the system config file (continued) Task Step 8 Save , then exit the standard config file: a In the window containing the standard config file, press F1 to return to the command line. b Enter: 1) re-save 2) exit 9 Exit the system config file without saving it: a In the window containing the system config file, press F1 to return to the command line. b Enter: exit 10 Compile the standard config file.
Chapter 8: Reference Figure 8-1 Copying configuration information $AGILENT3070_ROOT/standard/config BT-BASIC Status: xxx lines in workspace configuration xxxx ! CONFIGURATION FOR DEVELOPING BOARD TESTS ! target . . . enable . . . module . . BT-BASIC Status: xxx lines in workspace ! Specify instrument end module command configuration xxxx ! relay 1 controls vacuum . . . bank . . module . . cards 1 . . . ports . . ., . . . end module module . . cards 1 asru . . . ports . . ., . . .
Chapter 8: Reference MS Windows Quick-Reference See Table 8-7 for a MS Windows quick-reference. Table 8-7 MS Windows quick-reference To Do This... Enter This... • Kill processes and applications • Monitor CPU and memory usage Open the MS Windows Task Manager: a Hold down the keys at the same time (or right-click on the toolbar). b Click Task Manager...
Chapter 8: Reference NOTE BT-BASIC Quick-Reference Table 8-8 lists some commonly used BT-BASIC statements. Additional BT-BASIC information is given in Editing Files on page 8-8. For a more complete list of BT-BASIC statements, see the Agilent 3070 Family Users' Manual Quick Reference Guide available in the online User manuals or on paper as part number E9900-13602.
Chapter 8: Reference NOTE NT Korn Shell Quick Reference Although the operating system is MS Windows, a number of 3070 UNIX commands are valid in the Korn shell. If uncertain whether to use forward-slashes or back-slashes, see Forward-Slashes versus Back-Slashes in Command Lines Containing File Paths on page 8-8. See Table 8-9 for a Korn shell quick reference. Keyboard keys are in { }.
Chapter 8: Reference Table 8-9 Korn shell quick reference (continued) To Do This . . . Enter This . . .
Chapter 8: Reference Table 8-9 Korn shell quick reference (continued) To Do This . . . Enter This . . .
Chapter 8: Reference NOTE vi and viw Editor Quick Reference See Table 8-10 for a vi and viw editor quick reference. Keyboard keys are in { }. If uncertain whether to use forward-slashes or back-slashes, see Forward-Slashes versus Back-Slashes in Command Lines Containing File Paths on page 8-8. Table 8-10 vi and viw editor quick reference To Do This . . . Enter This in Command Mode . . .
Chapter 8: Reference Table 8-10 vi and viw editor quick reference (continued) To Do This . . . Enter This in Command Mode . . .
Chapter 8: Reference Table 8-10 vi and viw editor quick reference (continued) To Do This . . . Enter This in Command Mode . . .
Chapter 8: Reference Table 8-10 vi and viw editor quick reference (continued) To Do This . . . Enter This in Command Mode . . .
Chapter 8: Reference Codewords Codewords are pre-installed at the factory and normally do not require adjustment. Compile the Two Config Files CAUTION Introduction The capabilities of a 3070 system are based on the codewords installed. Codeword information is used by the system config file compiler and allows confirmation that the hardware and the supported software features are compatible.
Chapter 8: Reference System Config File Specifics The path to the system config file is: The "Official" and "Actual" System Config Files $AGILENT3070_ROOT/diagnostics/th1/config It must match the actual testhead card configuration. The "official" system config file is the system config file as when the system was shipped. It will be necessary to edit the system config file if the testhead cards or locations of the testhead cards have changed.
Chapter 8: Reference Descriptions of Some Statements in the System Config File The testhead name Statement The testhead name statement in the system config file identifies, via the hosts file, the block in the bootptab file that contains the hardware and internet protocol addresses for the System Card and ControlXT Card.
Chapter 8: Reference NOTE Single-density Hybrid Pin Cards cannot be used. The supplies Statements Numbering of the supplies in the supplies statements is arbitrary. The software will accept any mapping of supply numbers to modules. If the customer plans to share board test fixtures with other systems, it is possible they may have modified the default power supply setting. If so, reconcile the supplies numbering with existing systems.
Chapter 8: Reference Standard Config File Specifics This section contains: ■ Introduction, 8-29 ■ The Board Config File, 8-29 ■ Standard Config File Syntax Similarities to and Differences from the System Config File, 8-29 ■ Statements Allowed in the Standard, System, and Board Config Files, 8-30 ■ Statements Not Allowed in either the Standard or Board Config Files, but Are Allowed in the System Config File, 8-30 ■ Descriptions of Some Statements in the Standard Config File, 8-30 Introduction T
Chapter 8: Reference Statements Allowed in the Standard, System, and Board Config Files Descriptions of Some Statements in the Standard Config File • • • • • • The target Statements target enable module end module access ports boards wired in parallel • • • • • cards supplies ports boards connect A target statement is needed in each board config file. See Table 8-11 for factory default target statements.
Chapter 8: Reference Table 8-11 Factory default target statements Pattern Application Rate target Statement 6 MP/s (megapatterns-per-second) target hp3073 standard 12 MP/s target hp3070 advanced 20 MP/s target high accuracy See Table 8-12 for 3X72 process test system default target statements.
Chapter 8: Reference CAUTION NOTE ✸the enable statements should exist after target statements, and must be Codewords must be installed to enable optional software features. For more information, see Codewords on page 8-25. outside of a module block. The programmer will un-comment the correct enable statements which correspond to standard or optional software features as the board config file is developed.
Chapter 8: Reference Table 8-13 Some enable statements in the standard config file enable © Agilent Technologies 2001–2002 Functional Description: drivethru Enables the testing of digital devices through series resistors using Agilent TestJet technology. Use the Agilent Drive Thru Test in combination with the Agilent Access Consultant to identify and selectively remove nonessential probing locations.
Chapter 8: Reference Table 8-13 Some enable statements in the standard config file enable © Agilent Technologies 2001–2002 Functional Description: testjet Enables the TestJet testing technique on your board. This option is automatically enabled on the Agilent 3072 system. throughput multiplier Allows testing up to four boards simultaneously (one per module), which increases board throughput. It can only be used with the paneltest option.
Chapter 8: Reference Compiling the System and Standard Config Files For changes to the system config file and the standard config file to be enabled, they must be compiled. NOTE If codewords have been modified in any way, both the system config and the standard config files must be compiled. To compile the config files: 1 Login as service3070 (default password is service) 2 Open BT-BASIC. 3 Compile the system config file.
Chapter 8: Reference NOTE The bootptab File This section contains: ■ Hardware Addresses, 8-36 ■ IP Addresses, 8-37 Hardware Addresses Each control card has a unique hardware address. If a control card in the testhead is changed, the bootptab file must be edited to reflect a changed hardware address. CAUTION ✸ Changes made to the bootptab file MUST be done through the Bootp Server program.
Chapter 8: Reference 5 If a ControlXT Card was removed, delete its hardware address: 10.3.112.6 for module 2 10.3.112.7 for module 3 a Pull down the Hardware Address menu and select the address of the card you removed. • Merit dump file = This is a comment; enter the module number (e.g., module 2). b Click Delete. • Subnet mask = 255.255.255.0 6 Add the hardware address of the ControlXT Card you are installing: a Click New. b Enter the hardware address of the ControlXT Card.
Chapter 8: Reference The hosts File The path to the hosts file is: • $SystemRoot/system32/drivers/etc/hosts NOTE $SystemRoot is an environment variable that is usually set to: c:/winnt The hosts file must include these IP addresses: 10.3.112.2 testhead1 (System Card) 10.3.112.7 module3 10.3.112.6 module2 10.3.112.5 module1 10.3.112.4 module0 Example 8-1 on page 8-39 shows a sample hosts file.
Chapter 8: Reference Example 8-1 # # # # # # # # # # # # # # # # A sample hosts file This is a sample HOSTS file used by Microsoft TCP/IP for MS Windows. This file contains the mappings of IP addresses to host names. Each entry should be kept on an individual line. The IP address should be placed in the first column followed by the corresponding host name. The IP address and the host name should be separated by at least one space.
Chapter 8: Reference Device Files This section contains: ■ Introduction, 8-40 ■ Location of Device Files, 8-40 ■ If a DUT Power Supply is Replaced, 8-40 ■ DUT Power Supply Device Files, 8-41 Introduction Management of devices on MS Windows controllers are very different than on UNIX controllers. On MS Windows controllers, most devices are managed invisibly by the operating system.
Chapter 8: Reference DUT Power Supply Device Files See Table 8-18 on page 8-49 for DUT power supply GPIB addresses and device files.
Chapter 8: Reference Vacuum Control Location of Vacuum Control Statements These are contained in the system config file: $AGILENT3070_ROOT/diagnostics/th1/config Vacuum Control Specifics The relay controls vacuum statements need to match the actual hardware configuration after the customer decides how to implement vacuum control. There is nothing special about the defaults except that each matches a configuration shown in the site preparation manual.
Chapter 8: Reference CAUTION Rotating the Testhead all objects, including the monitor / ✸Remove keyboard support arms, from the rotational path of the testhead. During rotation, should the testhead hit anything, damage could result. CAUTION the shipping bolts before attempting to ✸Remove rotate the testhead. Otherwise, damage can result. 1 Open the pod door. 2 Press and hold the testhead rotation switch inside the pod until the testhead rotates to the desired position.
Chapter 8: Reference NOTE Testhead Cards See Table 8-15 for available testhead cards with diagnostics names, cards statements, pattern applications rates and part numbers. If Replacing the ControlXT Card ■ The ROM from the old card must be removed and installed on the new card. ■ Its hardware address in the system software must be changed. DO NOT change the hardware address of the System Card. System Card / Control Card LAN Information See Testhead LAN and Serial Port MUX on page 8-59.
Chapter 8: Reference Table 8-15 For MS Windows systems – supported testhead cards with diagnostics names, cards statements, pattern applications rates and part numbers (continued) H_StdDD2 hybrid standard double density 6 E4000-66550 H_PpuDD hybrid standard double density 6 E4000-66546 HPpuDD2 hybrid standard double density 6 E4000-66550 H_AdvDD hybrid advanced double density 12 E4000-66544 HAdvDD2 hybrid advanced double density 12 E4000-66550 H_HA_DD hybrid high accuracy do
Chapter 8: Reference Table 8-15 For MS Windows systems – supported testhead cards with diagnostics names, cards statements, pattern applications rates and part numbers (continued) © Agilent Technologies 2001–2002 STC_B serial b revision 6/12/20 E1085-66502 STC_B serial b revision with cables 6/12/20 E1085-66502 with E1093-61601 Administering Agilent 3070 Systems (MS Windows NT and 2000) 8-46
Chapter 8: Reference DUT Power Supplies Voltage Ranges DUT Power Supplies Allowed DUT power supplies are set at the factory to one of two configurations: See Table 8-16 for the DUT power supplies allowed. • Option 220 for line voltages of 200–220 volts. • Option 240 for line voltages of 230–240 volts. Table 8-16 DUT power supplies allowed 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.
Chapter 8: Reference Table 8-17 Default DUT power supply mappings for each module (rear view of testhead) (continued) ! supplies hp6624 23 to 24 asru channels 5 to 6 supplies hp6621 23 asru channels 5 to 6 ! supplies hp6624 19 to 20 asru channels 5 to 6 ! supplies hp6621 19 asru channels 5 to 6 ! supplies hp6634 23 asru channels 5 supplies hp6634 19 asru channels 5 ! supplies hp6634 24 asru channels 6 supplies hp6634 20 asru channels 6 ! supplies hp6642 23 asru channels 5 to 6 ! supplies hp6642 19 a
Chapter 8: Reference GPIB Addresses and Device Files If the DUT power supplies are functional, a supply’s GPIB address can be determined by tracing the cabling to determine which supply is connected to the module. If the supply has a front panel and is accessible, the GPIB address can be read from the front panel of the supply. on page 8-40 for more information about DUT power supply GPIB addresses. NOTE The customer has the flexibility to modify the DUT power supply GPIB addressing.
Chapter 8: Reference Table 8-18 DUT power supply GPIB addresses and device files (continued) © Agilent Technologies 2001–2002 Module 3, asru channel 5 or 5-6 3 $AGILENT3070_ROOT/dev/ps10 Module 3, asru channel 6 4 $AGILENT3070_ROOT/dev/ps11 Administering Agilent 3070 Systems (MS Windows NT and 2000) 8-50
Chapter 8: Reference To Change DUT Power Supply GPIB Addresses For 307X systems only where the power supplies are mounted in a support bay: • Open the support bay and find the correct power supply. Systems without support bays have the power supplies mounted in the testhead: • Panels must be removed from the testhead in order to access the front panel of the power supplies.
Chapter 8: Reference Controller Cables and Devices There are two supported MS Windows testhead controllers: For the Kayak XU700, use Figure 8-2 on page 8-53 with Table 8-19 on page 8-54. For the Visualize P600, use Figure 8-3 on page 8-56 with Table 8-20 on page 8-57.
Chapter 8: Reference Figure 8-2 Kayak XU700 cabling diagram Optional Bar Code Scanner Keyboard 3 G 7, K N 6 A Mouse M Optional Modem L 2 1 E Digi MUX for Optional Serial Devices B 5 Strip Printer 8 Not Used C D © Agilent Technologies 2001–2002 F Optional Parallel Printer Administering Agilent 3070 Systems (MS Windows NT and 2000) Private LAN GPIB Optional SCSI Optional Site LAN I J Video 4 Monitor Power Supply O 8-53
Chapter 8: Reference Table 8-19 Kayak XU700 cables and devices Cables Figure 8-2 Reference Part Number Description A E4000-61628 Control Cable 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 03066-61629 Strip Printer Cable, RS-232, DB9(f) to DB25(m) cross-conn.
Chapter 8: Reference Table 8-19 Kayak XU700 cables and devices (continued) N E4000-61629 LAN Cable, SMB to SMB for ControlXT Cards O 8120-1763 2 ea.
Chapter 8: Reference Figure 8-3 Visualize P600C cabling diagram 7 K Mouse 3 Keyboard Serial B To Strip Printer Serial A To Optional External Modem To Mouse G Bar Code Scanner (Opt) Mod 3 Mod 2 Mod 1 DUT P.S. (Opt) Mod 0 6 N E M Power Supply These connectors not used DUT P.S. (Opt) A Strip Printer To Optional Parallel Printer To Keyboard Testhead - ControlXT Cards F 4 O Video Monitor DUT P.S.
Chapter 8: Reference Table 8-20 Visualize P600C cables and devices Cables Figure 8-3 Reference Part Number Description A E4000-61628 Control Cable 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 03066-61629 Strip Printer Cable, RS-232, DB9(f) to DB25(m) cross-conn.
Chapter 8: Reference Table 8-20 Visualize P600C cables and devices (continued) N E4000-61629 LAN Cable, SMB to SMB for ControlXT Cards O 8120-1763 2 ea.
Chapter 8: Reference Testhead LAN and Serial Port MUX Testhead LAN IP Address The testhead LAN IP address is 10.3.112.10 with a subnet mask of 255.255.255.0 System Card / Control Card LAN Information The System Card and the ControlXT Cards communicate via a private LAN. Because the System Card and ControlXT 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) are unique in each system.
Chapter 8: Reference Table 8-21 Connector box MUX assignments © Agilent Technologies 2001–2002 Serial Port Reserved For 1 Pay-Per-Use (PPU) 2 JOT Board Handler 3—4 JOT Bar Code Readers 5—8 Other EIA-232 Devices Administering Agilent 3070 Systems (MS Windows NT and 2000) 8-60
Numerics Index A B C D E F G H I K L M N O P Q R S T U V W X Y Z Symbols A $AGILENT3070_ROOT, 8-3 $AGILENT3070_ROOT Environment Variable, 6-2 $AGILENT3070_ROOT on MS Windows, 6-5 Adding a group account, 5-7 Adding a user account, 5-6 additional system setup tasks, 3-6 Administering Agilent 3070 MS Windows Systems, 8-1 Administering Datalogging, 5-10 administration tasks, 1-2 Administrators How many are necessary?, 1-2 Agilent Software License Activation, 3-13 Flow Diagram, 3-14
Index Numerics © Agilent Technologies 2001–2002 A B C D E F G H I J K L M N O P Q R S T U V W X Y B C backing up the system creating a backup strategy, 4-3 back-slash, 8-8 Backup Strategy planning, 4-3 Backup tape making, 4-9, 4-10 restoring from, 4-14 board configuration file, 8-29 Boot disks creating, 4-6 Boot Recovery Diskettes creating, 4-7 when to create, 4-6 Booting a 3070 Controller, 2-2 Booting the Testhead, 2-3 bootptab file, 8-36, 8-37 Bridges, Routers, and Gateways, 7
Index Numerics A B C D E F G H I J K tools and material, 4-6 D Determine the Value of the Root Directory Environment Variable, 8-3 device files, 8-40 Device Files in $AGILENT3070_ROOT/dev, 8-40 directories, 8-6 directory structure, 1-4 Disaster recovery making a full backup tape, 4-10 options, 4-20 preparing for, 4-4 Disconnecting power, 2-4 Display the Logon Status from a Current Login, 8-2 domain, 5-8 Domain Names, 7-11 domain, with operator user, 5-8 DUT power supplies, 8-47, 8-48 DUT Power
Index Numerics A B C D E F G H I J adding, 5-7 Group accounts, 5-5 groups, 5-4 H hardware address, 8-36 Hardware Addresses, 8-36 Help, 5-3 Hosts and Nodes, 7-10 hosts file, 8-38, 8-39 How to Restore a System From a Full Backup Tape, 4-22 I incremental backup, 4-3 Install codewords, 8-25 Installing Patches, 5-11 installing patches, 5-11 IP Address, 8-37 IP address, 8-59 IP Addresses, 8-37 K Kayak XU700 cables and devices, 8-54 © Agilent Technologies 2001–2002 Administering Agilent 3070 System
Index Numerics A B C D E F G H I K L M N O P Q R S T MS Windows systems – supported testhead cards, 8-44 prerequisites, 5-1 N Q Network, 7-10 Network Components, 3-12 Network configuration information gathering, 3-8 Network services, 7-12 new software, 5-11 NT Korn Shell Quick Reference, 8-18 NUTCROOT alias, 1-5 quality reporting software, 1-6 O objectives, 4-1, 5-1 oil (User account), 5-5 oil login, 2-3 Open a File in BT-BASIC, 8-9 operator (User account), 5-5, 5-8 operator loggin
Index Numerics A B C D E F G H I J setup wizard tasks, 3-3 Shut Down the Controller Controller shut down, 2-4 Shutting Down the System, 2-4 Site Preparation documentation, 8-1 software overview, 1-3 Windows 2000 operating system capabilities, 1-3 standard config file, 8-10, 8-29 standard config file syntax, 8-29 Statements in the System Config File, 8-27 std3070 (User account), 5-5 Subnet mask, 8-37 supplies Statements, 8-28 system preparing to set up, 3-2 System Administration tasks, 1-2 System
Index Numerics A B C D E F G H I J K Understanding the file system File system understanding, 6-1 Use of the Root Directory Environment Variable, 8-3 Use of the Root Directory Environment Variable in a Korn Shell Window, 8-4 Useful commands, 7-13 User (User account), 5-5 User account, 5-4 3070, 5-5 about, 5-5 adding, 5-6 calibrate, 5-5 groups, 5-4 operator, 5-5, 5-8 service3070, 5-5 std3070, 5-5 user, 5-5 User Rights, 5-6 User-Access Example, 7-7 Users, 5-4, 8-17 access permissions, 5-4 controll
E9970-90000 Rev.
