Test Development Tools

Transcription

1 Contents Test Development Tools 1 Agilent IPG Test Consultant In this chapter Objectives Prerequisites Starting IPG Test Consultant Quitting IPG Test Consultant Features of IPG Test Consultant The Main Form Setting the Test Regeneration Behavior Selecting the Working Directory Selecting the Fixture Format Accessing Features in the Menu Bar Developing a Board Test Agilent Board Consultant In this chapter Objectives Prerequisites Starting Agilent Board Consultant Quitting Board Consultant Features of Board Consultant Features of the Main Form Menu Options Agilent Technologies 2001 Test Development Tools i

2 Table of Contents The Flowchart The Graphical Display The Forms Using Board Consultant Using On-Item Help Using the Flowchart Shortcuts in the Menu Bar Using the Graphical Display Using the Forms Board Consultant and Multi-Board Panels About Verification Checks The Board Graphics Viewer BT-BASIC Statements for Board Graphics Viewer Using the Board Graphics Viewer The Testability Report The BT-BASIC Environment In this chapter Objectives Prerequisites Using BT-BASIC in a Window The Command Area The Work Area Clearing the Screen Editing & File Manipulation Operating Modes & Error Checking The Softkeys Agilent Technologies 2001 Test Development Tools ii

3 Table of Contents 4 Agilent Pushbutton Debug In this chapter Objectives Prerequisites Features of Agilent Pushbutton Debug Board-Level Versus Device-Level Debug Starting Pushbutton Debug at the Board Level Board-Level Debug Device-Level Debug AutoAnalog Debug Miscellaneous Topics Subsequent Runs Are Faster Using Vacuum Fixtures with Agilent Pushbutton Debug Customizing the Macros Menu The Plot Generator In this chapter Objectives About The Plot Generator About the Plots The Board_XY Plot The Probe Plot The Inserts Plot The Alignment Plot The Wires Plot Things to do Before Using the Plot Generator Running the Plot Generator Agilent Technologies 2001 Test Development Tools iii

4 Table of Contents Using Plotters with the Plot Generator The Steps Required to Draw a Plot Orientation of the Plots Pen Colors and Types Plot Sizing and Scaling Which Plotters Are Supported? Usage Notes Viewing Plot Files About Spoolers Plot Files for the Top Plate Advisory Messages The Part Description Editor In this chapter Objectives Prerequisites Descriptions of the Menus, Tasks, and Forms The Menu Bar The Initialization Form Device Entry Forms Descriptions of the Device Entry Forms Capacitor Entry Form Connector Entry Form Diode Entry Form FET Entry Form Fuse Entry Form Inductor Entry Form Jumper/Strap Entry Form Pin Library Entry Form Agilent Technologies 2001 Test Development Tools iv

5 Table of Contents Potentiometer Entry Form Resistor Entry Form Switch Entry Form Transistor Entry Form Zener Entry Form CAMCAD Professional 8 Agilent Fixture Consultant In this chapter Objectives Prerequisites Introduction Getting Started Starting Agilent Fixture Consultant Quitting Fixture Consultant Fixture Graphics BT-BASIC Statements for Fixture Graphics Using Fixture Graphics Board Test Grader, Test Coverage, & Coverage Analyst In this chapter Objectives Board Test Grader Overview Test Types Limitations Grading Methods Agilent Technologies 2001 Test Development Tools v

6 Table of Contents Running Board Test Grader Prerequisites for Pre-B Board Tests Running Board Test Grader in Pushbutton Debug Running Board Test Grader in a BT-BASIC Window Re-running Board Test Grader Troubleshooting Example Testplan Creating a.discharge File Board Test Grader Files Data Files Report Files config.bdg testplan.bdg Test Coverage Running Test Coverage Interpreting the Test Coverage Report Coverage Analyst Starting Coverage Analyst Quitting Coverage Analyst Agilent Conversion Tool In this chapter Objectives Prerequisites Required Tools and Materials Practicing a Conversion Running the Conversion Tool Start the Conversion Tool Agilent Technologies 2001 Test Development Tools vi

7 Table of Contents Package Transfer Extract Make Interoperable Prepare for ECO View Log Troubleshooting Problems General Startup Package Transfer Extract What the Conversion Tool Does Relevant Differences Between UNIX and MS Windows Operating Systems Post-Conversion File Cleanup Source Controller Destination Controller Test Consultant Backup Files UNIX and MS Windows Interoperability In this chapter Objectives Prerequisites Interoperability Definition Enabling Interoperability Use of the Agilent Conversion Tool Engineering Change Orders (ECOs) Agilent Technologies 2001 Test Development Tools vii

8 Table of Contents Make Interoperable Function Prepare for ECO Function Copying Board Directories Compatible Objects UNIX and MS Windows Interoperability Matrix The Common Delimiter Character The Enable Common Delimiter Statement UNIX & MS Windows Servers Interoperability Use Models Operator Use Case Developer Use Case ECO Use Case Development Model without Conversion Agilent Technologies 2001 Test Development Tools viii

9 1 Agilent IPG Test Consultant In this chapter... Features of IPG Test Consultant, 1-3 Developing a Board Test, 1-22 Objectives After reading this chapter, you will be able to describe the appearance and features of Agilent IPG Test Consultant, which is the main user interface through which test developers interact with the test system. Among IPG Test Consultant s features include the following: Step-by-step guidance through the test generation and fixture generation processes. Access to other test system features, such as BT-BASIC, Board Consultant, Fixture Consultant, and the shell environment. Convenient mouse- or keyboard-driven forms (where appropriate). Online help. NOTE Detailed information about this software package is provided by online help. This chapter provides only the information needed to understand and begin using the software package. Prerequisites You must be familiar with features of the user interface such as the mouse, windows, menus, online help, and the terminology associated with them. NOTE See Chapter 1, Using a Workstation in Board Test Fundamentals for more information on the user interface. See Chapter 1, Test and Fixture Development in Test and Fixture Development for a description of the test generation process. See Chapter 6, Completing and Debugging Tests in Test and Fixture Development for a description of the fixture generation process. Agilent Technologies 2001, 2004 Test Development Tools 1-1

10 Chapter 1: Agilent IPG Test Consultant Starting IPG Test Consultant Start IPG Test Consultant in one of the following ways: Click the 3070 Programs icon on the Front Panel, then click IPG Test Consultant. Right-click the desktop background to display the Work menu. Click IPG Test Consultant. Type test consultant on the BT-BASIC command line. Press softkey F6 test consult within a BT-BASIC session. Use the mouse to drag a board directory from File Manager and drop it on the PG Test Consultant icon in the 3070 Programs menu.the 3070 Programs menu can be accessed on the Front Panel. Quitting IPG Test Consultant Exit IPG Test Consultant by selecting File > Exit from the menu bar. Agilent Technologies 2001, 2004 Test Development Tools 1-2

11 Chapter 1: Agilent IPG Test Consultant Features of IPG Test Consultant This section describes the main features of the IPG Test Consultant. The Main Form The Main Form displays when you start IPG Test Consultant. Tasks you can perform within the Main Form: Setting the Test Regeneration Behavior. When you are running with an existing board test, you can instruct IPG to regenerate only those files that have changed. Selecting the Working Directory. The working directory is a board directory that contains all the files associated with your board test. Within the board directory are subdirectories which contain device tests, fixture files, and other test files. Selecting the Fixture Format Specify whether you are testing more than one board per fixture. Accessing Features in the Menu Bar Activate IPG Test Consultant s features by selecting items from the menu bar. Each of these actions is individually described below. Setting the Test Regeneration Behavior The test regeneration behavior affects the way IPG regenerates tests when you are running incrementally and updating the test during debug or because of a Production Change Order (PCO). Regardless of its value, the chosen setting has no effect on the generation procedures for new board tests. See Table 1-1 for a description of the menu choices. Table 1-1 Test regneration behavior choices Menu Item Comprehensive Regeneration Comprehensive Regeneration; Clear Permanent Description IPG regenerates all tests that are changed, or affected by a change, except for those tests that are marked permanent in the testorder file. Same as Comprehensive Regeneration except that IPG also updates permanent tests that have been changed or affected by a change. In addition, IPG removes the permanent keyword from those tests entries in the testorder file. Agilent Technologies 2001, 2004 Test Development Tools 1-3

12 Chapter 1: Agilent IPG Test Consultant Table 1-1 Test regneration behavior choices (continued) Menu Item Limited Regeneration Limited Regeneration; Clear Permanent Description IPG regenerates only tests that are directly affected by a change, except for those tests that are marked permanent in the testorder file. Same as Limited Regeneration except that IPG also updates permanent tests that are directly affected by a change. In addition, IPG removes the permanent keyword from those tests entries in the testorder file. Selecting the Working Directory The working directory is the directory in which you either create a test for a new board or modify the test for an existing board. The name of the currently selected working directory appears in the data entry field under Selected Directory. 1 Choose a working directory. Click on the data entry field under Selected Directory and type the name of a directory. When the working directory is correct, press Return or move the mouse cursor out of the field and click on another item to use the new value. Use the mouse to choose a directory from the directory listing that appears along the left side of the menu, which is denoted Selected Directory Contents. The list shows the files and directories that appear under the current directory. 2 Build a path to a board directory Click the mouse's left button on a directory in the list. Your choice is appended to the name of the current directory. Then the next level in the directory structure appears in the window. In a similar fashion, you can append however many entries are needed to reach the desired directory. Directories in the list are terminated with a /, while files are not. Also, the buttons in which directory names and file names appear have a different color so you can distinguish one from the other. Agilent Technologies 2001, 2004 Test Development Tools 1-4

13 Chapter 1: Agilent IPG Test Consultant 3 Specify a relative path to a directory. Use the mouse to specify a relative path to a directory: Click.. / to move up one level in the hierarchy (to the parent of the current directory). Click. / to redisplay the current directory. NOTE If you do not know how to specify relative pathnames with./ and../, see Chapter 3, The File System in Board Test Fundamentals. 4 Scroll to see entire list. If there are more directories listed than can fit inside the window, use the mouse to move the scroll bar vertically to see the entire list. Selecting the Fixture Format The option menu to the right of the Fixture Format label displays the Agilent IPG Test Consultant menu, which lets you specify whether you are testing more than one board per fixture. See Table 1-2. Table 1-2 Menu Item Single Board Per Fixture Multiple Boards Per Fixture Fixture menu choices Description 1 Click a menu item (see Table 1-2). To exit this menu without making any changes, click somewhere outside the option menu, for example in the backdrop area. 2 Specify the fixture directory. The fixture is used to test only one board on a fixture. NOTE: Do not use this format. For multiple boards use PanelTest. See Agilent PanelTest in the Optional Board Test Applications Manual. For a more detailed description of specifying paths with the mouse, see Selecting the Working Directory on page Copy the path to the display area. When the path is correct, click on Set Fixture Directory to copy the path to the display area under Fixture Directory. Agilent Technologies 2001, 2004 Test Development Tools 1-5

14 Chapter 1: Agilent IPG Test Consultant 4 Specify board directories to be associated with the fixture directory. You can either use the mouse to select directories from the list or directly type them into the data entry field under Selected Directory. 5 Append the new board directory. After you have specified or built the path to a board directory, click on Add Board to append the new board directory to the list under Board Directories. 6 Remove board directories if necessary. Remove a board directory from the list, by selecting its name under Board Directories and then clicking Remove Board. Accessing Features in the Menu Bar The list below shows the hierarchy of items beneath the menu bar in IPG Test Consultant s main form (which, for simplicity, does not show the Help option). File Menu Exit Actions Menu Enter Board Data Develop Board Test Add A Test Edit Menu View/Edit Board Files (>) View Summary/Details Files (>) View/Edit Test Files (>) View/Edit Board Configuration View/Edit Fixture Files (>) View/Edit Other File Management Menu Clean Up Board Directory Archive Board Directory Restore Board Directory Copy/Move Board Directory Programs Menu Run BT-BASIC Run Agilent Board Consultant Run Test Cell Manager Run Korn shell Run Pushbutton Q-STATS Run Agilent Boundary-Scan Run Agilent Advanced Boundary-Scan Run Setup Test Editor Run Part Description Editor Run Agilent TestJet Keepouts Generation Run Agilent TestJet Drill File Generation Run Agilent Fixture Consultant Agilent Technologies 2001, 2004 Test Development Tools 1-6

15 Chapter 1: Agilent IPG Test Consultant NOTE Most of the items in the Edit menu cascade to display submenus, as indicated by an arrow (>) to the right of them. The items and features available from the menu bar are individually described next. File Menu The File menu contains the exit command. Actions Menu The Actions menu provides access to the main features of IPG Test Consultant and to other software tools. It also lets you add new tests. The Actions menu contains the options shown in Table 1-3. Table 1-3 Actions menu options Menu Item Enter Board Data Develop Board Test Add A Test Description Starts Agilent Board Consultant, which is a software tool that aids test developers in providing correct data before running IPG Test Consultant. Begins the sequence of steps required to generate a board test. If you select this option, IPG Test Consultant displays the Dependencies Calculation Menu. Add a new test to an existing testorder file. If you select this option, IPG Test Consultant opens a new BT-BASIC window and loads the testorder file into the workspace. The following two sections describe features that display when selecting menu options: Dependencies Calculation Form on page 1-7 Develop Board Test Form on page 1-9 Dependencies Calculation Form The Dependenceis Calculation form appears when you click Actions > Develop Board Test. The Dependencies Calculation form lets you select where to begin calculating dependencies. Dependencies calculations are used to decide which steps in the test Agilent Technologies 2001, 2004 Test Development Tools 1-7

16 Chapter 1: Agilent IPG Test Consultant and fixture development process need to be done. If you are an experienced test developer, you can save time by skipping the full dependencies calculations that would otherwise be done each time you use IPG Test Consultant. Although this form's options include the full series of steps in the test development process listed under Begin Dependencies Calculation At, only two options are selectable here. These options are presented in Table Select an option from the Dependencies Calculation form. Table 1-4 Dependencies calculation options Menu Item Compile config File Generate Test Requirements Files Description This is the usual starting point for calculating dependencies. Choosing this option causes dependencies calculations to start near the beginning of the Develop Board Test process. If you are a beginner or not sure why you would want to skip dependencies calculations, select this item. Choosing this option as your starting point lets you ignore the steps prior to Generate Test Requirements Files. This option can be useful if you are: Debugging and the only changes are to the source files for tests. Manually running portions of the fixture generation process, such as board placement. Doing some steps without having libraries available. Select this option only if you are confident that it is the correct choice! 2 Make a selection from the Actions menu. Actions menu options are provided in Table 1-5, below. Agilent Technologies 2001, 2004 Test Development Tools 1-8

17 Chapter 1: Agilent IPG Test Consultant Table 1-5 Actions menu options Menu Item Begin Interactive Development Begin Batch Development Description Displays the Develop Board Test form, which guides you through the normal sequence of steps required to generate a board test and the associated fixture reports and files. Calculates dependencies from whichever starting point was chosen, does all the steps in the test development process without user intervention, verifies the dependencies, and then returns to the main form. 3 Exit the form. To exit the Dependencies Calculation form and return to the main form without taking any action, click File > Cancel. Develop Board Test Form The Develop Board Test form appears immediately after the Dependencies Calculation form if you choose Begin Interactive Development. This form guides you through the normal sequence of steps required to generate a board test and the associated fixture reports and files. Under Single Step Execution there are a list of steps, including those presented in Table 1-6. Table 1-6 Single step execution options Menu Item Compile config File Compile Library Tests Compile board File Description Compile a configuration file that describes the hardware in your system's testhead. Compile tests in the library directories. Compile the board file. Agilent Technologies 2001, 2004 Test Development Tools 1-9

18 Chapter 1: Agilent IPG Test Consultant Table 1-6 Single step execution options (continued) Menu Item Compile and Plot board_xy File Generate Initial Fixture Files Generate Tests Using IPG Generate testplan Create Custom Tests Generate Test Requirements Files Generate Final Fixture Files and Reports Generate Test Object Files Recalculate Dependencies Description Compile the board_xy file. Also run the Plot Generator program. Run the fixture generation software. Also lets you run the Fixture Consultant software so you can change the board placement, select probes, or reserve brcs for custom applications Run the IPG software. Run the Testplan Generator (TPG) software, which generates the testplan. Manually create custom tests which IPG does not automatically generate. Extract the hardware resource requirements for the test. Run the fixture generation software and the Plot Generator program. Also lets you run the Fixture Consultant software so you can make wiring changes, such as modifying the wiring for fixture electronics. Compile the device tests to generate the executable (object) files. Verify that the steps were correctly completed. As IPG Test Consultant runs, it moves through the sequence of steps required to develop your board test. Whenever it stops with a step selected (highlighted), you have the option of specifying what happens next. Or, you can manually examine a different step by clicking on it. Only the highlighted step can be executed (Do) or skipped. There are two ways to use the Develop Board Test form, Multiple Step and Single Step. Each provides a different path through the series of steps. Multiple Step is the more automatic of the two paths. Each step has an option menu to its left, under Multiple Step Control. If you click Execute All Steps to Stop Mark Agilent Technologies 2001, 2004 Test Development Tools 1-10

19 Chapter 1: Agilent IPG Test Consultant in the Actions menu, IPG Test Consultant automatically executes the sequence of steps according to how these options are defined. Initially, the value of each option is determined by IPG Test Consultant. Overriding a default action lets you control IPG Test Consultant's progress through the test development process. Unless an option's value is stippled or grayed-out, you can specify the desired action for a step. NOTE A Mark menu appears in the menu bar for the Develop Board Test form. This menu contains two options that let you quickly change all the options for multiple step control, which are Mark all steps: SKIP and Mark all steps: DO. The actions allowed by the option menus can vary slightly according to what is required. Steps whose actions end with a question mark for example, Do? have not been evaluated yet (and, thus, IPG Test Consultant does not know if they need to be done). After they have been evaluated, the question mark disappears. If IPG Test Consultant evaluates the step and determines that it is unnecessary, the step is ignored and marked Not Required. Some of the possible actions are presented in Table 1-7. Table 1-7 Possible actions from the Develop Board Test form, Multiple Step path Menu Item Do/Do? Skip/Skip? START & Do Description Do this step. Then mark it as Done and go to the next step. Update the date and time stamp on all files associated with it but take no action. Then mark it as Skipped and go to the next step. (The updated date/time stamp marks the files as deliberately skipped instead of out-of-date.) Indicates the current starting point that is, the first step that IPG Test Consultant needs to do. After this step has been done, the next step that needs execution is marked START & Do. You cannot change which step is marked START & Do. Agilent Technologies 2001, 2004 Test Development Tools 1-11

20 Chapter 1: Agilent IPG Test Consultant Table 1-7 Possible actions from the Develop Board Test form, Multiple Step path Menu Item START & Skip Do & STOP/Do? & STOP Skip & STOP/Skip? & STOP Not Required Description Indicates the current starting point, but deliberately skips the step. Do this step and stop. Skip this step and stop. Indicates that a step is not required and cannot be done. When the actions are set up as desired, click Execute All Steps to Stop Mark in the Actions menu to do them. This executes the sequence of steps until a step is encountered whose option contains the word STOP. The other path is called Single Step because it lets you proceed one step at a time through the sequence of steps. Each step has an option menu associated with it. The values of the options represent actions you may want to take for that step. After you have selected the option menu, click on your choice of action. Each time a step is completed, the next step to be done is selected automatically. The actions allowed by the option menus can vary slightly according to what is required. Among the possible actions are shown in Table 1-8. Table 1-8 Possible actions from the Develop Board Test form, Single Step path Menu Item Do This Step Redo This Step Skip This Step Description Executes the current step, which may consist of several substeps. (Click Expand This Step to view the components that comprise a step.) Repeats a step that has already been done. Only the last step executed can be redone. Ignores the step but update the date and time stamp for files associated with this step. (The updated date/time stamp marks the files as deliberately skipped instead of out-of-date.) Agilent Technologies 2001, 2004 Test Development Tools 1-12

21 Chapter 1: Agilent IPG Test Consultant Table 1-8 Possible actions from the Develop Board Test form, Single Step path Menu Item Expand This Step Expanded Information Not Evaluated Why Why Information Not Evaluated Modify List of Tests to be Generated Run Fixture Consultant Description Shows the statements used to perform the selected task. Appears when the dependencies required for Expand This Step have not been evaluated. Clicking on this step does nothing. Displays a message explaining why the selected step is necessary. Appears when the dependencies required for Why have not been evaluated. Clicking on this step does nothing. Appears when you choose Generate Tests Using IPG under Single Step Execution. This item displays an additional form that lets you specify which tests IPG regenerates. Appears when you choose either the initial or final fixturing steps. This item runs Fixture Consultant so you can interactively make changes to the fixture. If an action is inappropriate, you see an error message explaining why the action was not allowed. Be aware that you can use a combination of the Multiple Step and Single Step features. For example, you can use Multiple Step to execute a sequence of steps until a STOP action is encountered, and then begin using Single Step. To exit the Develop Board Test form and return to the main form without taking any action, click Cancel in the File menu. Choose the Modify List of Tests to be Generated option. The resulting form lets you specify which tests IPG should regenerate, which tests it should not regenerate, and which tests should be marked permanent in the testorder file and not regenerated. You can move tests from one list to another by clicking on them and then clicking on the arrow corresponding to the action you wish to take. If you wish to manually add a test to the list, click Add A Test and supply the name of the new test. When you have finished, click Save followed by Close to record your choices and exit this form. If you change your mind, click Close without clicking Save. Agilent Technologies 2001, 2004 Test Development Tools 1-13

22 Chapter 1: Agilent IPG Test Consultant Edit Menu The Edit menu provides a path to additional menus in which you can examine or edit the source files for an existing board, which reside in the working directory you chose in the Main Form. 1 Select an item from a sub-menu. Selecting an item from a sub-menu opens a BT-BASIC window and changes to the operating mode appropriate for the task, such as analog or digital. If a required file or directory does not exist, the BT-BASIC status line displays an error and the BT-BASIC command line displays the command that caused the error. 2 Edit the file. If you need to edit the file, you can use the convenient editing features available within the BT-BASIC environment. 3 Exit. a On the BT-BASIC command line, type: exit b Press Return. View/Edit Board Files Menu Choosing View/Edit Board Files in the Edit menu lets you examine or modify the board or board_xy files. Both View/Edit options open a new BT-BASIC window and then load the named file into the workspace for viewing or editing. View Summary/Details Files Menu Choosing Edit, then View Summary/Details Files lets you examine the summary file produced by IPG Test Consultant or any of the summary or details files produced by IPG or by the fixturing software. All the options in this menu open a new BT-BASIC window and then load a file into the workspace for viewing or editing. View Test Consultant Summary loads the summary file, and the other options load the named file. The summary file lists the actions taken during the latest run of the Develop Board Test feature in IPG Test Consultant. View/Edit Test Files Menu Choosing Edit, then View/Edit Test Files lets you examine or modify many files (including files for device tests) produced during the test generation process. Many of the options in this menu open a new BT-BASIC window and then load the named file into Agilent Technologies 2001, 2004 Test Development Tools 1-14

23 Chapter 1: Agilent IPG Test Consultant the workspace for viewing or editing. The exceptions to this are presented in Table 1-9. Table 1-9 View/Edit Test Files menu options Menu Item View/Edit testorder File View/Edit testmain File View/Edit testplan File View/Edit Digital Tests View/Edit Functional Tests View/Edit Backtrace Files View/Edit States Files View/Edit shorts Files View/Edit opens Files View/Edit Analog Tests Description Opens a new BT-BASIC window and gets the testorder file. Opens a new BT-BASIC window and gets the testmain file. Opens a new BT-BASIC window and gets the testplan file. Opens a new BT-BASIC window in digital mode and move to the digital directory for the selected board. Opens a new BT-BASIC window in digital mode and move to the functional directory for the selected board. Opens a new BT-BASIC window in backtrace mode and move to the functional directory for the selected board. Opens a new BT-BASIC window in states mode and move to the functional directory for the selected board. Opens a new BT-BASIC window and gets the shorts file. Opens a new BT-BASIC window and gets the opens file. Opens a new BT-BASIC window in analog mode and move to the analog directory for the selected board. Agilent Technologies 2001, 2004 Test Development Tools 1-15

24 Chapter 1: Agilent IPG Test Consultant Table 1-9 View/Edit Test Files menu options (continued) Menu Item View/Edit Powered Analog Tests View/Edit Mixed Signal Tests Description Opens a new BT-BASIC window in analog mode and move to the analog directory for the selected board. Opens a new BT-BASIC window in basic mode and move to the mixed directory for the selected board. View/Edit CAD Files Menu Choosing Edit,then View/Edit CAD Files lets you examine or modify the cad.data, cad.format, or board_xy files. These files are related because the CAD files are used to produce the board_xy file, which describes the physical characteristics of a circuit board. All the options in this menu open a new BT-BASIC window and then load the named file into the workspace for viewing or editing. View/Edit Board Configuration Choosing this item in the Edit menu opens a new BT-BASIC window and then loads the config file into the workspace for viewing or editing. View/Edit Fixture Files Menu Choosing View/Edit Fixture Files in the Edit menu lets you examine or modify the files associated with fixturing. (Regardless of what the menu option says, you always have the ability to modify these files. However, we recommend that you modify only those files with a View/Edit option.) All of the options in this menu open a new BT-BASIC window and then load the named file into the workspace for viewing or editing. View/Edit Other File Choosing this option in the Edit menu starts BT-BASIC, which is useful for viewing or editing miscellaneous files for which no View/Edit option exists in the menus listed above. Management Menu The Management menu displays menu options used to manipulate the files in a board directory. Agilent Technologies 2001, 2004 Test Development Tools 1-16

25 Chapter 1: Agilent IPG Test Consultant Your choices here are presented in Table Table 1-10 Management menu options Menu Item Clean Up Board Directory Archive Board Directory Restore Board Directory Copy/Move Board Directory Description Lets you manage a board directory by removing unwanted files or directories. Lets you copy the contents of a board directory to magnetic tape. Lets you restore the contents of a board directory stored on magnetic tape by the Archive Board Directory feature. Lets you copy or move a board directory and its contents. Each of these is individually described below. Clean Up Board Directory Form If you select Clean Up Board Directory in the Management menu, the appropriate form appears. This form is used to remove unwanted files, including backup files, from a directory. You can also use this to change the working directory. See Selecting the Working Directory on page 1-4 for more information. If there are more files or directories listed than can fit inside the window, use the mouse to move the scroll bar vertically to see the entire list. Do any of the following to mark (highlight) the files or directories you wish to clean up: Click on individual files (or on a directory). Select all backup files in the current directory by clicking Mark All Backup Files. 4 Mark files and/or directories. Clicking the Mark menu in the menu bar provides the shortcuts shown in Table 1-11 when selecting items to delete. Agilent Technologies 2001, 2004 Test Development Tools 1-17

26 Chapter 1: Agilent IPG Test Consultant Select all numbered backup files other than the most recent backup file by clicking Mark All Backups, then.1~. Table 1-11 Mark menu shortcuts Shortcut Mark All Backup Files Mark All Backups, then 1~ Unmark All Selections Description Select all backup files. (By convention, the names of backup files end with a tilde [~], or with a period, a number, and a tilde; for example, file~ or file.4~.) Select all numbered backup files except the most recent one; that is, select all numbered backup files whose number is greater than 1. (When numbered backups are used, the name of each backup file is followed by a period, a unique number from 1 to 9, and a tilde to identify the file.) Un-select all marked files/directories. As you mark files (or directories), they are highlighted. If you change your mind, you can unmark a selection by clicking on it a second time. 5 Delete the marked items. a After you have marked the appropriate choices, click Actions, then Delete Marked Selections. b When you are asked to confirm the action, click OK to do the action and return to the main form. 6 Exit the form. To exit this form without taking any action, click File, then Cancel. Archive Board Directory Query Box If you select Board Management > Archive Board Directory, the query box appears. This option lets you save the entire contents of a board directory to a tape cartridge for archival storage. 1 Insert a tape in the tape drive. Wait for the busy light to turn off. 2 Click OK. The contents of the working directory you chose in the main menu are archived to the tape. 3 Exit. Agilent Technologies 2001, 2004 Test Development Tools 1-18

27 Chapter 1: Agilent IPG Test Consultant To exit this query box without taking any action, click Cancel. Restore Board Directory Query Box If you select Board Management > Restore Board Directory, the query box appears. This item lets you restore the contents of a board directory from magnetic tape. Perform the following tasks to accomplish this. 1 Insert the backup tape in the tape drive. Wait for the busy light to turn off. 2 Click OK. The tape's contents are restored to the working directory you chose in the main menu. This option lets you copy an existing board directory (stored on a tape cartridge) into a new directory. CAUTION Files restored from the backup tape overwrite existing files of the same name in the working directory. 3 Exit. To exit this query box without taking any action, click Cancel. Copy/Move Board Directory Form If you select Management, then Copy/Move Board Directory, a form appears that lets you copy or move the entire contents of a board directory to a different directory. NOTE A move is equivalent to copy followed by delete; the source is copied to the destination and then the source is deleted. 1 Toggle the label above the directory listing. The label above the directory listing is either From Directory Contents or To Directory Contents to indicate which directory listing is being shown. To toggle this label between From... and To..., select Actions, then Toggle FROM/TO Listing. 2 Specify a source directory. The name of the source directory, which is the directory to be copied or moved, appears under From Directory. Edit the data entry field or use the mouse to select a directory from the list. Agilent Technologies 2001, 2004 Test Development Tools 1-19

28 Chapter 1: Agilent IPG Test Consultant 3 Specify a destination directory. The name of the destination directory, which is the location to which the source directory is copied or moved, appears under To Directory. The destination directory must exist and be empty; otherwise, you will receive an error message. Edit the data entry field or use the mouse to select a directory from the list. 5 Exit. To exit this form without taking any action, click File > Cancel. Programs Menu This menu lets you run other test system functions without exiting IPG Test Consultant. This menu contains the items presented in Table Move (or copy) the directory. Click either Copy Directory or Move Directory (in the Actions menu) to perform the indicated action. Table 1-12 Programs menu options Menu Item Run BT-BASIC Run Agilent Board Consultant Run Test Cell Manager Run Korn shell Description Start a BT-BASIC session in a new window. Run Board Consultant, which aids test developers in providing correct board data before running IPG Test Consultant. Start the Test Cell Manager program, which provides a shell around the BT-BASIC environment that prevents test operators from directly interacting with the programming environment. (See Chapter 4, Program Management and Miscellaneous Statements in Board Test Fundamentals for more information about the Test Cell Manager.) Open an Korn shell in a new window. Run Pushbutton Q-STATS Run Pushbutton Q-STATS, the quality management software on the Agilent Technologies 2001, 2004 Test Development Tools 1-20

29 Chapter 1: Agilent IPG Test Consultant Table 1-12 Programs menu options (continued) Menu Item Run Agilent Boundary-Scan Run Agilent Advanced Boundary-Scan Run Setup Test Editor Run Part Description Editor Run Agilent TestJet Keepouts Generation Run Agilent TestJet Drill File Generation Run Agilent Fixture Consultant Description Run the Boundary-Scan software, which is a software package that supports the testing of digital devices that comply with IEEE Standard Run the optional InterconnectPlus software. Run Setup Test Editor, a software tool that helps you develop VCL setup-only tests for custom digital devices. Run the Part Description Editor, which is used to create or modify part description libraries. Run software that generates keepout areas that are the precise size and shape for Agilent TestJet probes, which ensures that the fewest possible resources are blocked. Generate drill file information for Agilent TestJet probes, which is not generated by the fixture generation software. Run Fixture Consultant, which is a software package that lets you graphically examine and modify fixturing information. Agilent Technologies 2001, 2004 Test Development Tools 1-21

30 Chapter 1: Agilent IPG Test Consultant Developing a Board Test Figure 1-1 on page 1-23 shows a simplified diagram of how IPG Test Consultant develops a board test, and where each action occurs. Although they are not shown in Figure 1-1 on page 1-23, you can access IPG Test Consultant's other features as needed from the menu bar in the Main Form. For example, you can use the Edit menu to view or edit data files, the Management menu to manage board directories, or the Programs menu to run other software packages without exiting the IPG Test Consultant. 1 Specify board directory(s). Specify the directory in which the data for that board is located. 2 Enter the board data. If you have already entered the data for your board, you can skip this step. If not, run Board Consultant to enter board data. 3 Decide on a development process. You must decide whether to work interactively or to let IPG Test Consultant develop the board test without intervention. a Choosing interactive development lets you monitor and control the steps as they happen. Depending upon how you prefer to work, you can use Multiple Step, Single Step, or a combination of the two. b If you choose batch development, you are prompted only when necessary. For example, you are advised if there is an action you must take before IPG Test Consultant can continue. Choosing the Begin Interactive Development or Begin Batch Development actions causes IPG Test Consultant to calculate dependencies. This updates the program's knowledge of your board test and lets it decide what must be done. Agilent Technologies 2001, 2004 Test Development Tools 1-22

31 Chapter 1: Agilent IPG Test Consultant Figure 1-1 IPG Test Consultant develops a board test Begin Set test regeneration behavior, specify fixture format (main form) Choose board directory (main form) Choose fixture directory (main form) Enter board data (Action menu in main form) Develop board test (Action menu in main form) Begin interactive development (Action menu in Dependencies Calculation form) Begin batch development (Action menu in Dependencies Calculation form) Calculate dependencies Calculate dependencies Multiple step (Develop Board Test form) Single step (Develop Board Test form) End Agilent Technologies 2001, 2004 Test Development Tools 1-23

32 Chapter 1: Agilent IPG Test Consultant Agilent Technologies 2001, 2004 Test Development Tools 1-24

33 2 Agilent Board Consultant In this chapter... Features of Board Consultant, 2-3 Using Board Consultant, 2-24 The Board Graphics Viewer, 2-31 The Testability Report, 2-34 Objectives When you finish reading this chapter, you should be able to describe the appearance and features of Board Consultant, which is a software tool that aids you in providing correct data before you run IPG Test Consultant. Board Consultant can greatly reduce the amount of time you spend regenerating board tests and fixturing information by helping you identify errors and testability problems with board data. Among Agilent Board Consultant s features are the following: A step-by-step flowchart that guides you through the process of data entry and verification. Graphical representation of board data, which makes it easier to identify problems early in the test development process. Convenient mouse- or keyboard-driven forms for entering and verifying data. The ability to generate a Testability Report for use by you and those who design your circuit boards. Extensive online help. NOTE Detailed information about this software package is provided via online help, which includes on-item help that provides information about any feature that appears on the screen. Because extensive online help is available, this chapter provides only the information needed to understand and begin using the software package. Prerequisites See Chapter 3, Creating Board Information in Test & Fixture Development for information about using Board Consultant to develop board tests. If you are not already familiar with features of the user interface, see Chapter 1, Using a Workstation in Board Test Fundamentals. Agilent Technologies 2001 Test Development Tools 2-1

34 Chapter 2: Agilent Board Consultant Starting Agilent Board Consultant You can do any of the following to run Board Consultant: Click the arrow above the Agilent 3070 icon on the front panel to display the subpanel menu. Then, click the Board Consultant icon. Right-click the desktop background to display the Work menu and click Board Consultant. Type board consultant on the BT-BASIC command line. Select Actions, then Enter Board Data in IPG Test Consultant. Select Programs, then Run Board Consultant in IPG Test Consultant. Quitting Board Consultant Exit Board Consultant by selecting File, then Exit from the menu bar. Agilent Technologies 2001 Test Development Tools 2-2

35 Chapter 2: Agilent Board Consultant Features of Board Consultant The following topics describe the major features of Board Consultant. The Main Form appears when you start Board Consultant (see Figure 2-1 on page 2-4). It consists of two major parts: a flowchart of tasks (on the left of the form), and a graphical representation of the board. Agilent Technologies 2001 Test Development Tools 2-3

36 Chapter 2: Agilent Board Consultant Figure 2-1 Main Form in Board Consultant Agilent Technologies 2001 Test Development Tools 2-4

37 Chapter 2: Agilent Board Consultant Features of the Main Form The Main Form in Board Consultant contains the following: a flowchart, a Detailed View and Overview to graphically display the board, control buttons, a menu bar, an area for notes and status messages, and some miscellaneous features. The flowchart and graphical display are described in The Flowchart on page 2-8 and The Graphical Display on page 2-14 respectively. The other items are described next. Menu Bar The menu bar at the top of the form provides access to the following menus: Table 2-1 Menu File Tasks Compile Verify Search Menu bar options Description Lets you work with the files that store board information. You can load existing board information, create information for a new board, and save board information. You can also exit Board Consultant from this menu. Lets you display the X-Y locations on your board and display forms to examine or enter data that describes the physical and electrical characteristics of your board. This option also lets you display the paths to libraries. The Tasks menu provides an alternative method to display the forms that are organized into groups for sequential access via the blocks in the flowchart. Lets you compile out-of-date library or Agilent SAFEGUARD files, the board file, the board_xy file, or the config file. Performs verification to confirm the integrity of your data. Lets you search for a device or a node on your board. If the search finds a match, it can: Display a form that lets you examine or modify the data for that item. Highlight that item in the graphical display. Agilent Technologies 2001 Test Development Tools 2-5

38 Chapter 2: Agilent Board Consultant Table 2-1 Menu Options Help Menu bar options (continued) Description Displays a form that enables you to highlight locations in the graphical display. Provides an overview that describes how to use on-item help. Table 2-2 Miscellaneous features in the Main Form Feature Board Directory Status Line Notes area View / Edit Physical Board Data Tasks Description The name of your working directory, the directory that contains the board and board_xy files for your board, appears in the title bar at the top of the form. The status message displays information about the task being processed by Board Consultant. The status is Ready when Board Consultant is waiting for you to do something. Note that the button to the left of the Status label changes color to show the current status: green means ready and yellow means busy. An area that displays supplemental information about the current task. Lists the tasks associated with this block in the flowchart. Click the mouse's left button on the appropriate pushbuttons to invoke the necessary form or information for that task. If there are too many tasks to view on the screen at one time, you can use the scroll bar to move through the list. Agilent Technologies 2001 Test Development Tools 2-6

39 Chapter 2: Agilent Board Consultant Menu Options The main menu contains the following: File Save Board Information Create New Board... Load Existing Board... Print... Exit Tasks View / Edit Panel Data (>) View / Edit Physical Board Data (>) View / Edit Board Description Data (>) View / Edit Test System Data (>) View / Edit Library Paths Compile Compile config File Compile Modified Libraries Compile Modified Safeguard Files Compile board File Compile board_xy File Generate X-Y Plot Verify Verify Fixture Type Verify Configuration Size Run Agilent Access Consultant Show Devices Using Agilent Polarity Check * Show Devices Using Agilent TestJet * Verify Agilent TestJet & Agilent Polarity Check Probe Types (Keepouts/Outlines) Verify Node Probing Access Verify Power Node Probing Access Verify Ground Node Probing Access Show Missing Libraries Verify Disable Methods Exist Verify Disabling Nodes Usable Verify Tied Nodes Data Verify Boundary-Scan Chains Show Devices in Library Directory Show Library for Device Designator Show Library for Part Number Show IPG Device Summary Verify IPG Device Disable Results Verify Safeguard Inhibit Results Generate Testability Report Search For Device... For Node... Version Set Version... Create New Version (>) Add/Cancel New Version Delete Version Agilent Technologies 2001 Test Development Tools 2-7

40 Chapter 2: Agilent Board Consultant Options Highlight Location Data * These items appear only if your system has the Agilent TestJet option installed. The Flowchart The Flowchart provides access to other forms for entering, examining, or modifying the data for your board. It guides you through the actions needed to enter data for your board and to develop library tests. The blocks in the flowchart are associated with related data entry tasks or actions. When you select a block, a list of possible tasks appears below the flowchart in the Task area or the action on the label is initiated. You can click on any Task to display its data entry form for viewing and editing. Figure 2-2 Flowchart Agilent Technologies 2001 Test Development Tools 2-8

41 Chapter 2: Agilent Board Consultant The Hierarchy of Blocks and Actions Each block in the flowchart has one or more actions associated with it. When you click a block, one of two things happens: The software initiates the action indicated on the label. If more than one action is possible, a list of tasks appears in the Task area below the flowchart. To select a task, click the pushbutton associated with that task. When you select a task, Board Consultant displays the appropriate form, verifies the integrity of the board information, or begins compiling a file. Table 2-3 describes a reference list of blocks and actions. In many cases, the action corresponds to an item that appears below the flowchart, in the list of actions for the current block. Use Table 2-3 to understand the flowchart s overall structure, or to find a specific action when you are not sure which block that action is associated with. Table 2-3 Block List of blocks and actions in the Flowchart form Action(s) Create New Board Translate CAD Data Load Existing Board View/Edit Panel Data Board Type View/Edit Physical Board Data Invokes a Board Specification Form Display CAD Translation Instructions Invokes a Board Directory Selection Form Enter Boards On Panel Enter Panel Outline Enter Panel Tooling Holes Enter Panel Keepout Areas Displays the Board Selection Form Enter Board Outline Enter Board Tooling Holes Agilent Technologies 2001 Test Development Tools 2-9

42 Chapter 2: Agilent Board Consultant Table 2-3 Block List of blocks and actions in the Flowchart form (continued) Action(s) View/Edit Board Description Enter Capacitor Enter Connector Enter Diode Enter FET Enter Fuse Enter Inductor Enter Jumper/Strap Enter Node Library Enter Pin Library Enter Potentiometer Enter Resistor Enter Switch Enter Transistor Enter Zener Enter Node Enter Internal Devices Agilent Technologies 2001 Test Development Tools 2-10

43 Chapter 2: Agilent Board Consultant Table 2-3 Block List of blocks and actions in the Flowchart form (continued) Action(s) View/Edit Test System Data Enter Power Node Data Enter Fixed Node Data Enter Board-level Disables/Conditions Enter IPG Global Options Enter Family Options Enter Fixture Options Enter GP Relay Connections Enter Board Keepout Areas Enter Groups Enter Extra Probing Locations Agilent Technologies 2001 Test Development Tools 2-11

44 Chapter 2: Agilent Board Consultant Table 2-3 Block List of blocks and actions in the Flowchart form (continued) Action(s) Compile/Verify (below View/Edit Test System Data) View/Edit Library Data Display config File Instructions Compile config File Verify Fixture Type Verify Configuration Size Run Access Consultant Show Devices Using Polarity Check * Show Devices Using Agilent TestJet * Verify Bottom-Side Keepouts for Agilent TestJet and Polarity Check * Show Devices Using Connect Check Verify Node Probing Access Verify Power Node Probing Access Verify Ground Node Probing Access * These items appear only if you have the Agilent TestJet option installed. Enter Library Paths Display Device Library Instructions Display Part Library Instructions Display Safeguard File Instructions Agilent Technologies 2001 Test Development Tools 2-12

45 Chapter 2: Agilent Board Consultant Table 2-3 Block List of blocks and actions in the Flowchart form (continued) Action(s) Compile/Verify (below View/Edit Library Data) Final Compile/Verify Testability Report Save Board Files Compile Modified Libraries Compile Modified Safeguard Files Verify Missing Libraries Verify Disable Methods Exist Verify Disable Nodes Usable Verify Tied Nodes Data Verify Boundary-Scan Chains Show Boundary-Scan Chains Show Devices in Library Directory Show Library For Device Designator Show Library For Part Number Save Board Files Compile board File Compile board_xy File Generate X-Y Plot Show IPG Device Summary Verify IPG Device Disable Results Verify Safeguard Inhibit Results Generate the testability report Agilent Technologies 2001 Test Development Tools 2-13

46 Chapter 2: Agilent Board Consultant The Graphical Display Board Consultant provides a graphical display to help you visualize the characteristics of your board, such as X-Y locations and device outlines. The Detailed View and Overview make it easy to identify components, device pins and nodes on the screen. The flowchart provides access to the various forms that you can use to examine or modify board data. Board Consultant requires board X-Y data to display the board graphically. The graphical display contains two views of the board (an overview and a detailed view), feature and viewing controls, and information areas. Agilent Technologies 2001 Test Development Tools 2-14

47 Chapter 2: Agilent Board Consultant Figure 2-3 Board Consultant graphical display Agilent Technologies 2001 Test Development Tools 2-15

48 Chapter 2: Agilent Board Consultant The main features of the graphical display are: Overview: A full view of the entire board and its features. Unlike the Detailed View, the Overview always shows the entire board. A red outline in the Overview shows which region of the board is being displayed in the Detailed View. The area inside this outline is called the Viewport. If you have the optional PanelTest feature installed on your system, you can also view an entire panel to see where boards are located on it. Detailed View: A variable-magnification view of the board and its features. This area always shows the part of the board that is outlined in red in the Overview. Devices with no X-Y data: A list of devices that exist in your board data but do not have physical locations on the board as it is displayed. One example of this is a surface mount device whose electrical characteristics are defined in the board data but that does not use physical X-Y locations on the board. Only devices for which there is no X-Y location data appear in this list. When partial X-Y data is present, the device appears in the graphics windows and not here. If the full list is too long to fit on the screen at one time, a scroll bar appears along the right side. You can use the scroll bar to move through the list. Feature Controls: A group of pushbuttons that controls which features are shown in the Detailed View (you cannot control the appearance of the Overview). When lit, the colors of the buttons correspond to the colors of their respective items on the screen. The options here are: Outlines: Controls whether the physical outline of the board is displayed. Tooling Holes: Controls whether tooling holes are displayed. X-Y Locations: Controls whether X-Y locations are displayed for the top, bottom, or both sides of the board. Device Outlines: Controls whether device outlines are displayed for the top, bottom, or both sides of the board. Keepout Areas: Controls whether keepout areas are displayed for the top, bottom, or both sides of the board. View Controls: A group of pushbuttons that controls the Detailed View. The options here are: Show Panel View: Alternates between the panel view and the board view when data is being entered for a multi-board panel. (This item is usable only when the optional PanelTest feature is installed on your test system.) Agilent Technologies 2001 Test Development Tools 2-16

49 Chapter 2: Agilent Board Consultant Full View: Shows the entire board in the Detailed View. This is a larger version of the view shown in the Overview. Redraw: Refreshes or updates the Detailed View as needed. Previous View: Returns the Detailed View to the magnification and position prior to the last change in view. Zoom In/Zoom Out: Increases or decreases the magnification of the Detailed View in discrete steps. Be aware that it is possible to zoom in or out too far and see only a black screen. If you suspect this has happened, check the Overview window to see where the viewport is located. Zoom To Highlights: Automatically zooms to items that are highlighted in the Detailed View. Clear Highlighting: Removes the highlighting from any items that are highlighted in the Detailed View. View: Controls the side from which you view the board, which can be the top or the bottom. The top is typically the side on which components are located. If you compare your board with the view in the graphical display, it should be apparent which side is which. This option simply changes the perspective from which you view the board; it does not affect which features are displayed (X-Y locations, device outlines, keepout areas) or how those features are displayed (top, bottom, both). Cursor: The cursor location and its units of measure appear on the same line as View. The cursor location is continuously updated as you move the mouse inside either the Overview or the Detailed View. The Status and Notes areas are shared with the flowchart and serve the same functions as before. The Forms NOTE In the following material, the layout of some of the forms may differ slightly from the same forms as they appear on the screen; however, the functions have not changed. Board Consultant provides many forms to describe your board characteristics. You can use these forms to: View or edit data that describes the physical board, such as the X-Y locations on a board. Agilent Technologies 2001 Test Development Tools 2-17

50 Chapter 2: Agilent Board Consultant View or edit data that describes the electrical characteristics of the board, such as information about devices and nodes. View or edit test system data, which is global information such as power nodes, definitions of logic families, fixturing options, and GP relay connections. You can access the following forms in Board Consultant: Panel Definition Board Outline Board Tooling Holes Device Entry Node Entry Internal Device Entry Library Paths Power Node Options Fixed Node Option Board-Level Disable/Condition IPG Global Options Family Options Fixture Options GP Relay Connections Keepout Areas Group Pins Entry Extra Probing Locations Displaying Forms Many forms in Board Consultant share common characteristics such as menus, data entry fields, and buttons. The Device Entry Form provides an example of the features you may encounter when using forms. To display this form, select Tasks > View/Edit Board Description Data, then select Device Data and any device type. This form contains menus, data entry fields, and buttons that let you specify device information, add a device, delete a device, or close the form. Several display options are available from the Options menu. These options allow you to vary the content and appearance of a device entry form, which consists of separate sections or panels. You can save space on the screen by displaying only a portion of the entire form. You can choose the following display options: Maximize/Normalize: Resizes the device entry form so that all of the displayed features are visible without scrolling. Show/Hide Values: Show or hide features that describe a device's value, such as its nominal value and tolerances. Show/Hide Connections: Show or hide features that describe how the pins on a device are connected and accessed. Agilent Technologies 2001 Test Development Tools 2-18

51 Chapter 2: Agilent Board Consultant Show/Hide Test Options: Show or hide features that describe general testing options for a device, such as testability, tolerance multiplier, and remote sensing. When you choose to hide an option, the information does appear in the device entry form. When you choose to include or show an option, an additional panel for that option is inserted into the form, as Figure 2-4 shows. Figure 2-4 Device Entry forms can include optional panels Each of these panels contains additional data entry fields or controls used to describe a device. You can show all options and have all three panels appear in the device entry form, as Figure 2-4 illustrates. Be aware that different kinds of devices may use variations on these panels. For example, Values may not apply to one kind of device, while another kind of device may have several different Test Options. Agilent Technologies 2001 Test Development Tools 2-19

52 Chapter 2: Agilent Board Consultant The width of a device entry form varies depending upon whether it is maximized or normalized. You may need to scroll its fields when its size is normalized. Many of the panels use a horizontal scroll bar to scroll a group of data entry fields that do not fully appear on the screen when the form is normalized. You can horizontally expand a device entry form by maximizing it. This is done with the Maximize option in the Options menu invoked from the menu bar. Maximizing removes the need to scroll horizontally. Figure 2-5 on page 2-21 shows a Device Entry Form that is maximized with all possible options visible. Because the full version of a form can occupy considerably more space on the screen than its smaller variations, you can save space on the screen by hiding features you are not currently using. Agilent Technologies 2001 Test Development Tools 2-20

53 Chapter 2: Agilent Board Consultant Figure 2-5 Maximized Device Entry form Shortcuts When Using the Forms Besides the standard keys used by most of the software packages on your test system, such as Tab and Shift-Tab to move from item to item, the forms in Board Agilent Technologies 2001 Test Development Tools 2-21

54 Chapter 2: Agilent Board Consultant Consultant provide additional shortcuts you may find useful. NOTE For an overview of the user interface and more information about using the keyboard, see Chapter 1, Using a Workstation in Board Test Fundamentals. For example, you also can use the Shift-left/Shift-right arrow keys to move from item to item in Board Consultant s forms. Some forms, such as the one in Figure 2-6, contain a list area in which each row contains related data entry fields. Figure 2-6 Shortcuts in a list area You can use the following shortcuts inside a list area: Pressing home-up (white arrow) moves the typing cursor to the beginning (upper left corner) of the list area. Pressing home-down (Shift/white arrow) Agilent Technologies 2001 Test Development Tools 2-22

55 Chapter 2: Agilent Board Consultant moves the typing cursor to the end (lower right corner) of the list area. The up/down arrow keys move the cursor vertically from row to row. When the list is too long to fit on the screen, these keys scroll the list. The Insert line key inserts a blank line, while the Delete line key removes the current line and its contents. You can use Return to add a new row to the end of a list (when you need to enter more items than there are rows of data entry fields). Use the Insert line key if you need to add a new row between existing rows. Agilent Technologies 2001 Test Development Tools 2-23

56 Chapter 2: Agilent Board Consultant Using Board Consultant The next few topics further describe some of the features introduced earlier at an overview level. Using On-Item Help Board Consultant provides on-item help for features that appear on the screen. Pressing and holding the middle button on a three-button mouse (or simultaneously pressing and holding both buttons on a two-button mouse) changes the mouse cursor to a question mark. When you place the question mark on an item and release the button, help appears for that item. ADVICE To save time when invoking on-item help, you can click the middle button on an item and not wait for the question mark to appear. The question mark is simply an aid whose distinctive shape identifies on-item help. Using the Flowchart Each block in the flowchart represents a step you potentially need to do when entering or verifying the data for your board. Beginning at Start, you must either click on Create New Board and specify the name of a new board directory or click Load Existing Board and specify the name of a board directory that already contains board information. You can save much work entering data if you have CAD data that can be translated to provide board information. If you do have CAD data, click Translate CAD Data to receive instructions about how to use it. After these initial steps, there are two distinct paths in the process of entering board information. One path, which is located at the left side of the flowchart, lets you enter a physical and electrical description of the board, plus global information needed by the test system. The other path, which is located at the right side of the flowchart, lets you develop library tests for use in your board test. The two parallel paths converge near the bottom of the flowchart, where the descriptive board information and the library tests combine to become the information to develop a complete board test. Shortcuts in the Menu Bar Because the flowchart is an easy-to-use visual guide through the data entry process, it is the appropriate tool for many test developers. But if you know exactly what you need to do, you can use items in the menu bar to go directly to a desired task. The menu bar is an alternate way for you to use all the forms that are organized into Agilent Technologies 2001 Test Development Tools 2-24

57 Chapter 2: Agilent Board Consultant groups for sequential access via the blocks in the flowchart. For example, when you click View/Edit Board Description in the flowchart, you are presented with a list of tasks associated with entering data for different kinds of devices or entering data for nodes. But if you invoke Tasks, then View/Edit Board Description Data, you are presented with a submenu that provides similar functions. Use whichever method you prefer, the flowchart or the menu bar, or a combination of the two. Depending upon your individual work habits and degree of experience with developing board tests, you may find one way easier or more convenient than the other. Using the Graphical Display Much of Board Consultant's usefulness is in its graphical display. Because it lets you view the physical characteristics of a board, the graphical display lets you visually verify the integrity of board information. The Overview always displays the entire board and identifies which region of the board you are examining in the Detailed View (see Figure 2-3 on page 2-15). When a board is displayed, the Overview area contains a red box called the viewport. The viewport shows the region of the overall board displayed in the Detailed View. For information on the options available, see The Graphical Display on page Select which side of the board to view. 2 Vary the magnification. 3 Examine sections of the board. 4 Identify items, such as devices or the pins on devices. 5 Display data entry forms. 6 Find an item on the board. 7 Highlight board locations. 1 Select which side of the board to view. Use the View option to select the top or bottom view of the board. 2 Vary the magnification. Use the view controls to vary the magnification of the Detailed View. Press and hold the right button while dragging the mouse cursor across the area you want to magnify. When you release the button, the area you specified is magnified. Click Previous View in the view controls to return to the original display. Agilent Technologies 2001 Test Development Tools 2-25

58 Chapter 2: Agilent Board Consultant 3 Examine sections of the board. Move the mouse cursor into the viewport, press and hold the mouse s left button, and you can drag the viewport around inside the Overview. This lets you quickly examine different sections of your board in the Detailed View area. 4 Identify items, such as devices or the pins on devices. a Turn on Device Outlines. b Point the mouse cursor to an item, and then click the mouse's left button. The mouse cursor momentarily changes to a pointing hand, and then the identity of the item appears in the Notes area. The amount of detail provided by this feature depends upon how you point to an item. For example, pointing to the middle of a device identifies that device. But pointing to a specific pin on a device identifies the device, the pin number, and the node to which the pin is connected. In a similar fashion, pointing to other items on a board may simply identify the X-Y location of the item and the node to which it is connected. As you might expect, the accuracy of this feature is affected by the magnification in the Detailed View. The larger an item appears, the easier it becomes to point precisely to it. (You hear a beep if you point to an item and miss. Simply try again.). 5 Display data entry forms. Click the mouse's right button on an item to select it and automatically invoke its data entry form. 6 Find an item on the board. When you need to find an item on your board but do not know its location, use the Search menu in the menu bar. a Choose whether you want to find a device or a node. This invokes the Search Specification form, as Figure 2-7 on page 2-27 shows. Agilent Technologies 2001 Test Development Tools 2-26

59 Chapter 2: Agilent Board Consultant Figure 2-7 Using the Search Specification form If you are searching for a device and the device type initially shown in the Search Specification form is incorrect, click Device Type to specify another type. Then choose a device from the list that appears. Alternately, you can click the data entry fields and directly type your choices for Device Type and Designator. 7 Highlight board locations. a Select Options > Highlight Location Data. b Select an item in the list of devices or nodes. c Click either of the following: Highlight Device or Highlight Locations to find the item and have it highlighted in the Detailed View. Show Data for Device or Show Data for Node to find the item and automatically invoke the correct form for examining or modifying the data for that item. The Highlight Control form shown in Figure 2-8 on page 2-28 appears. b Choose all the locations whose attributes match the criteria you specify by clicking the control buttons. c After you have specified the options, click Highlight to highlight the matching locations. Be aware that this highlighting occurs only when the appropriate features are enabled in the features controls. For example, if a location whose fixture access is top (as specified in the Device Entry form for that device) matches the criteria in the Highlight Control form but X-Y locations for the top of the board are not enabled, the location is not highlighted. d Click Clear Highlights in the view controls area as needed to clear the existing highlighting. Agilent Technologies 2001 Test Development Tools 2-27

60 Chapter 2: Agilent Board Consultant Figure 2-8 The Highlight Control form NOTE As you use the forms to enter board information, remember to periodically save work in progress. This reduces the possibility of losing work because of a power failure or other problem. Board Consultant and Multi-Board Panels If you have the optional PanelTest feature installed on your test system, Board Consultant can help you work with multi-board panels. Both the flowchart and the graphical display change slightly to accommodate panels. When panels are being used, Board Type: <panel> appears between the View and Cursor labels on the line immediately above the graphical Detailed Display window. Using the Forms Unless you specifically invoke them from the menu bar, the forms in Board Consultant appear automatically as needed. For example, when you click a block in the flowchart and then choose an action from the list that appears, the form that appears is appropriate for the task. 1 Select a board for data entry. a Select Board Type from the flow chart. The Board Selection Form appears. b Select the individual boards for data entry. The selected board is displayed graphically, assuming X-Y data is available. The Board Type block is grayed-out if panels are not being used. Agilent Technologies 2001 Test Development Tools 2-28

61 Chapter 2: Agilent Board Consultant 2 Display the panel/display a board. The graphical display has a button at the top of the view controls that enables you toggle between displaying the whole panel and displaying a selected board. The button is labeled Show Board View if a panel is currently being displayed, or Show Panel View if a single board is being displayed. This button is grayed-out when panels are not being used. sequence and combined into a single file, they become the Testability Report (described later). Figure 2-9 A verification check 3 Identify a specific board on a panel. Click on the outline of that board in the Detailed View. This fills the selected board with a hatching pattern and identifies it in the Notes area. 4 Display the board view. Click the mouse s right button on the outline of the board in the Detailed View. About Verification Checks Most of the options under the Verify menu in the menu bar invoke checks that verify the correctness of your board information. Figure 2-9 shows an example of a typical verification check. This check compares the resources available on the test system against the resources needed to test the board. When all of the verification checks are executed in To print the results of verification checks: 1 Select File, then Print. The dialog box in Figure 2-10 on page 2-30 appears. Agilent Technologies 2001 Test Development Tools 2-29

62 Chapter 2: Agilent Board Consultant Figure 2-10 Printing results of a verification check 2 Complete information in the Print Dialog box and click OK. a Check either: Print the results of a verification check to a file. Print a list of features that are highlighted in the graphical display to a file. b Type the filename in the text box. Specify lp as the file name to print directly to your line printer. Agilent Technologies 2001 Test Development Tools 2-30

63 Chapter 2: Agilent Board Consultant The Board Graphics Viewer If desired, you can use BT-BASIC to programmatically invoke a read-only version (which does not have a Save Board Information option in its File menu) of the graphical display separately from the rest of Board Consultant. When used by itself, this feature is called the Board Graphics Viewer. You can use it interactively like the graphical portion of Board Consultant or you can manipulate the graphics from a testplan, which is useful when you need to draw attention to features on a board. The Board Graphics Viewer lets you view and selectively highlight any of the following: A specific board or all boards on a multi-board panel. A specific device or a pin on a device. All locations on a specific node. The board graphics viewer is already integrated into your system s backtracing and autolearn features. Thus, if the Board Graphics Viewer is in use when backtrace or autolearn are invoked, they automatically can make use of the graphics (see Using the Board Graphics Viewer on page 2-33). Other potential uses for the Board Graphics Viewer include: Helping test operators locate a specific device. For example, suppose your testplan requires that a potentiometer be adjusted. You can use the Board Graphics Viewer to display the potentiometer and highlight it, which helps production operators find the correct potentiometer when making the adjustment (see Using the Board Graphics Viewer on page 2-33 for an example of this). Helping test developers locate manual probing locations while debugging a board test. Helping repair operators locate devices and physical locations during repair operations. BT-BASIC Statements for Board Graphics Viewer A set of BT-BASIC statements lets you invoke the graphical display from the BT-BASIC command line or from a board test. Table 2-4 on page 2-32 lists the BT-BASIC statements associated with the Board Graphics Viewer. NOTE For more information about these statements, refer to the Syntax Reference. Agilent Technologies 2001 Test Development Tools 2-31

64 Chapter 2: Agilent Board Consultant Table 2-4 BT-BASIC statements Term board graphics board graphics display board board graphics display panel board graphics end board graphics highlight board board graphics highlight clear board graphics highlight device board graphics highlight nodes select boards on panel Definition Invokes a read-only version of the Board Graphics Viewer used to graphically display features on boards. Switches the Board Graphics Viewer from viewing a multi-board panel to viewing a single board on the panel. Switches the Board Graphics Viewer from a board view to a panel view (if the board is on a multi-board panel). Terminates the Board Graphics Viewer used to graphically display features on boards. Switches the Board Graphics Viewer to a panel view (if it is not already there) and causes it to highlight a specified board. Selectively clears highlighting provided by the Board Graphics Viewer. Causes the Board Graphics Viewer to highlight a specified device or pin on a device (device.pin) in a color that denotes the device's status as active, fail, or pass. Causes the Board Graphics Viewer to highlight all locations on a specified node. The highlighting can be in a color that denotes the node's status as active, fail, or pass. Lets you use the Board Graphics Viewer to choose which boards should be tested on a multi-board panel. Agilent Technologies 2001 Test Development Tools 2-32

65 Chapter 2: Agilent Board Consultant Using the Board Graphics Viewer A simple example of using the Board Graphics Viewer to draw attention to a device might look like this: Example 2-1! Beginning of the testplan board graphics! Invoke Board Graphics Viewer wait for start board graphics highlight clear all! Remove any previous highlighting sub Preshorts board graphics highlight device "rpot201"! Draw attention to pot. test "analog/rpot201"! Adjust & test the pot subend......! End of the testplan Because support for the Board Graphics Viewer is built-in, the only statement you must add to make it work with a testplan for backtrace or autolearn is: board graphics on Agilent Technologies 2001 Test Development Tools 2-33

66 Chapter 2: Agilent Board Consultant The Testability Report Board Consultant generates a testability report that contains information about the testability of your board, such as probing access and pins that are tied high or low. It also includes information about the test for your board, such as missing libraries, device disable problems, and safeguard problems. to provide information about the testability of the board to the design department. NOTE See Chapter 3, Creating Board Information in Test & Fixture Development for details about the testability report. You can generate a testability report any time during test development; the report includes information generated from the files that are available when the report is generated. We recommend that you generate and examine the report before leaving Board Consultant and again before leaving IPG Test Consultant later in the test development process. To generate the testability report, select the Testability Report block on the flowchart. The report is placed in a file called testability.rpt. Use the list source statement to copy the testability.rpt file to the printer to generate a copy that you can examine. You can use the testability report to correct any problems in your board test before continuing. You can also use the report Agilent Technologies 2001 Test Development Tools 2-34

67 3 The BT-BASIC Environment In this chapter... Using BT-BASIC in a Window, 3-2 Objectives When you finish reading this chapter, you should be able to describe the appearance and features of the BT-BASIC environment in which test developers work when using BT-BASIC to develop a board test. Prerequisites Before you begin using this chapter, you should already know how to use BT-BASIC. NOTE If you need more information, see BT-BASIC Programming. Agilent Technologies 2001, 2003 Test Development Tools /2003

68 Chapter 3: The BT-BASIC Environment Using BT-BASIC in a Window Figure 3-1 shows a window with BT-BASIC running. Figure 3-1 BT-BASIC running inside a window Agilent Technologies 2001, 2003 Test Development Tools 3-2

69 Chapter 3: The BT-BASIC Environment A BT-BASIC window is formatted into two parts: The Command Area The Work Area The Command Area The top part of a BT-BASIC window is the command area. The first line, Status, is used by the system to display messages describing system status and any error information. The next line is the command line, which is used to execute statements, run programs, and so on. For example, here is how you can use the print statement to print something to the screen. 1 Press the command/edit softkey, F1. 2 On the command line, type: print "This is a number -- ";69 3 Press Return or the execute softkey, F4. The message (the part in quotes) and the number are printed in the lower part of the screen. The maximum length of the command line is 2048 characters. If the command line is too long to fit in a single row on the screen, only 80 characters of it are visible at a time. The Work Area The lower part of a BT-BASIC window is called the work area because you write text or programs in it. The results of operations, such as the printing you executed above, are also sent to the work area unless you specify another place, such as a printer. The current mode of operation, with the process identification number (this number uniquely identifies your operating session), is shown at the top right of the work area. Opening a window into BT-BASIC sets the mode to basic, which indicates that the system is ready to accept a BT-BASIC program. The blocks of inverse video at the bottom of the work area show the functions of the softkeys, F1 through F8. Also, the letters IC (insert character) appear near the bottom of the window if the keyboard is in the insert mode (Ins char key). The actual workspace available to you is very much larger than just the twenty or so lines in the BT-BASIC window; the workspace is as large as the available memory in the controller. The work area of the BT-BASIC window acts as a window into the workspace in memory. So if you are writing a report and have filled the screen, the top lines simply roll up and disappear as you add more lines at the bottom. But they are not lost from the workspace. You can roll the workspace down (using the up-arrow key) and view Agilent Technologies 2001, 2003 Test Development Tools 3-3

70 Chapter 3: The BT-BASIC Environment those lines through your window (the work area of the screen) whenever you wish. The maximum length of a single line in the workspace is 2048 characters. If a line is too long to fit in a single row on the screen, it wraps around and occupies additional rows. Using the various editing keys and statements described in this chapter, you can access and edit any part of the contents of the workspace. To edit a program already in a file, for example, simply use the get or load statements to bring the file into the workspace. It can then be edited or run as desired. Clearing the Screen Occasionally you need to clear the screen before sending a new message to it. To do this from within a program, include the following program line: printer is * print using "@" This program line defines the workstation s window as the print device and sends it a page eject. The page eject empties the work area while leaving the command area intact. The same commands can be executed manually from the command line when no program is running. However, the results are different from when they are executed from within a program. When the commands are executed from the command line, the window (work area) clears, but when the cursor is moved to the work area (with the command/edit softkey) the original contents of the work area reappear. Or, you can use the Clear display key if something has been printed to the screen. For example, if the screen is the print device (printer is *) and you execute a cat statement on the command line, a list of files appears in the work area. Pressing the Clear display key erases both the list of files and the cat statement that appears on the command line. The Clear display key redraws the screen when the contents of the workspace (such as a file) are being displayed. Editing & File Manipulation The editing statements are used to prepare text, files, and programs on the workstation. The file manipulation statements provide a link between the system workspace and the file structure. Agilent Technologies 2001, 2003 Test Development Tools 3-4

71 Chapter 3: The BT-BASIC Environment CAUTION You should not use an HP-UX editor, such as vi, to edit board test files on your test system. Board test files include a header that contains information used by the board test software. The BT-BASIC editor prevents you from altering or removing this header information, but other editors do not. If this header information is not properly maintained, your test system may not function correctly. Editing Statements The editing statements are used with the workstation s editing keys and softkeys to enhance the workstation s editing capability. None of these statements are programmable. They can be executed only from the workstation command line. Table 3-1 contains a list and a brief description of the editing statements. Table 3-1 Term change changem changen delete duplicate edit fetch Editing statements Definition (change all) Replaces all occurrences of an existing string with a new string, throughout the workspace. Not case sensitive. (change marked) Replaces all occurrences of an existing string with a new string, throughout the area defined by the mark softkey. Not case sensitive. (change next) Replaces the next occurrence of an existing string with a new string. Not case sensitive. Deletes the marked lines in the workspace. Duplicates the marked lines in the workspace. Inserts duplication immediately above the line where the cursor is positioned. Positions the cursor at the beginning of the specified line. Copies a specified line from the workspace into the workstation command line. Agilent Technologies 2001, 2003 Test Development Tools 3-5

72 Chapter 3: The BT-BASIC Environment Table 3-1 Term find findm findn list listm listn move number scratch Editing statements (continued) Definition (find first) Finds the first occurrence of a given string within the entire workspace. Not case sensitive. (find marked) Locates the first occurrence of a given string within the marked area of the workspace. Not case sensitive. (find next) Locates the next occurrence of a given string within the workspace. Not case sensitive. (list all) Lists the entire workspace to the default output device. (list marked) Lists the marked portion of the workspace to the default output device. (list to end) Lists, to the default output device, all lines from the current line to the end of the workspace. Moves the marked segment of workspace to immediately above the current line. Returns information to the user about the current line number and cursor position. Clears the workspace only. Erases any text, program, or variables currently stored there. File Manipulation Statements File manipulation statements provide a link between the workspace and the file system. Except for the compile statement, these statements are used to store the contents of the workspace into files and to bring the contents of files back into the workspace. The statements operate only on source files. These statements are described in Table 3-2. Two sets of statements perform identical functions. The two sets are: get, save, and re-save load, store, and re-store Both sets are included in BT-BASIC as a convenience to test developers from other systems, who may be used to either set. Feel free to use whichever you prefer, or mix them. Agilent Technologies 2001, 2003 Test Development Tools 3-6

73 Chapter 3: The BT-BASIC Environment Table 3-2 File manipulation statements Term compile merge get and load re-save and re-store save and store Definition Used to compile object code from source files. Lets you merge all or part of one or more files into another file. Clears the workspace and copies the contents of a disk file into it. The file is checked for correct syntax. The statement can be executed only from the workstation command line; it is not programmable. Same as save or store, except writes to an existing file. The statement can be used to write to a device, such as a printer. Creates a new file on the disk and stores the contents of the workspace in it. Records the current mode in the file. NOTE For complete descriptions of the statements, refer to the Syntax Reference. Operating Modes & Error Checking There are several operating modes, each of which has its own syntax and is associated with a specific task. Usually, the accuracy of the syntax is automatically checked whenever that mode is selected. Most modes are selected by executing a statement that includes the name of the mode. For example, to select text mode you would type text on the command line and press Return. (Also, files that have a mode associated with them automatically invoke the required mode when they are retrieved into the workspace with a get or load statement.) Depending upon which mode is selected, one of several things happens when you change modes: The workspace is cleared and the mode name appears in the information line of the BT-BASIC window. From here, you can change modes at any time by executing the appropriate statement on the Agilent Technologies 2001, 2003 Test Development Tools 3-7

74 Chapter 3: The BT-BASIC Environment command line. The modes that do this are shown in Table 3-3. A separate software package is invoked, which looks different from the BT-BASIC window in which it was invoked. When you exit the new mode, the BT-BASIC window returns. The modes that do this are described in Table 3-4. The new mode takes effect but no immediate change occurs in the BT-BASIC window. The modes that do this are described in Table 3-5. Table 3-3 Modes -- workspace is cleared and mode name is displayed Mode analog backtrace Description Lets you create or edit analog in-circuit tests. Lets you create, edit, or compile backtrace files. basic Lets you interactively type and execute BT-BASIC statements, and create, edit, or run BT-BASIC programs. configuration digital part pins Lets you create or edit a configuration file that defines the hardware resources available for use by Agilent IPG. Lets you type Vector Control Language (VCL) statements, and create or edit VCL test programs, which are used to test digital devices. Note that VCL programs are run in basic mode; see the test statement for details. Lets you create or edit a part description library file, which is written in PDL (Part Description Language). Lets you create or edit a pins file that contains CHEK-POINT information. safeguard Lets you create or edit Agilent SAFEGUARD files in the digital libraries. These files contain the safety information required to minimize possible damage to devices resulting from their being overdriven during digital testing. Agilent Technologies 2001, 2003 Test Development Tools 3-8

75 Chapter 3: The BT-BASIC Environment Table 3-3 Mode shorts states testorder text wirelist Modes -- workspace is cleared and mode name is displayed (continued) Description Lets you create or edit the shorts test file generated by IPG. This file lists the nodes that are to be tested for opens or shorts. Lets you create or edit the states file, which contains the node state data for digital functional tests. Lets you edit the testorder file, which determines the order in which tests execute on your system. Lets you type any text (syntax checking is turned off), which is useful for writing reports. Lets you create or edit the fixture wiring list file for a test. Table 3-4 Modes -- invokes a separate software package Mode board consultant debug partforms Description Invokes Board Consultant, which is a software tool used to enter and verify the accuracy of data during the test development process. Lets you debug analog and digital tests. (When debugging an analog test or when using the Agilent Pushbutton Debug environment to debug analog or digital tests; see Chapter 6, Debugging Digital Tests in Test Methods: Digital) Invokes the Part Description Editor, which you can use to create or edit part description libraries. Agilent Technologies 2001, 2003 Test Development Tools 3-9

76 Chapter 3: The BT-BASIC Environment Table 3-5 Mode autolearn Modes -- the new mode takes effect but no immediate change occurs in the BT-BASIC window Description Lets you execute autolearn statements for a specified test. NOTE AUTOLEARN is not supported in MS Windows systems. debug Lets you debug analog and digital tests.(when debugging a digital test but not using the Pushbutton Debug environment; see Chapter 6, Debugging Digital Tests in Test Methods: Digital) In general, you need not be concerned with how a particular mode looks. But you should be aware of what the mode does and when to use it. Deciding which mode to select usually depends on where you are in the test generation process and on the requirements for the PC board to be tested. For example, if you need to add a new digital test to the library you execute digital and then you can type VCL statements. In most cases, selecting a mode turns on the appropriate syntax checking for that mode. With syntax checking on, the system monitors what you type to ensure that it is consistent with the current mode and that it contains no errors. If an error is detected, the system rejects what you have just typed and returns a message identifying the error. You can then erase or correct the error immediately, rather than having to find and correct it at a later time. The following are not automatically syntax checked: board_xy: There is no syntax checking until the board_xy file is compiled. To check the syntax before compilation, you can execute a check boardxy statement. text: There is no syntax checking because text mode lets you type anything you wish. You can use text mode to write and save programs, then check the syntax later. Agilent Technologies 2001, 2003 Test Development Tools 3-10

77 Chapter 3: The BT-BASIC Environment What is Error Checking? Many programming and data entry errors are automatically detected and produce warning messages. The two types of error checking that take place are as follows: Line Level Error Checking: Errors are detected when the line is entered. Runtime Error Checking: Errors are not detected until the program is run. Line Level Error Checking At the line level, syntax checking occurs when the you press Return after typing a line of characters in any mode except text mode. The check is made for lines in the workspace or on the command line. If a language error occurs, a beep sounds and an error message identifies the error. The error message appears on the status line. Language errors include misspelled keywords, missing parameters, incorrect punctuation, etc. If the statement contains a logical error, such as the wrong variable being named, the error cannot be found by a line-level syntax check, because the statement itself still makes sense. But if the wrong type of variable is specified, such as a numeric variable when the syntax requires a string variable, then that error can be detected by a syntax check. Anything in quotation marks is a string and is not syntax checked. For the more experienced test developer, it is important to note that the image specifications are not syntax checked at the line-level; take extra care when typing the specifications. They are checked at runtime. There are two reasons for this. First, the specifications can be stored in strings, in which case the system has no way of determining (until run time) that they are image specifications. Second, the specifications must be matched with the list of items to be input or output by the (one or more) I/O statements invoking those image specifications. Because those lists can include variables and expressions, checking for mismatches can be only a runtime task. Runtime Error Checking Runtime error checking occurs while the program is running. Again, error messages are generated identifying the type of error found. This type of checking ensures that the program as a whole makes sense, and that statements are not misplaced or missing. Programs and files that must be compiled are checked at the line-level and are also checked for general sense when they are compiled. Because the error checking feature in this system is very thorough, it helps you write programs correctly and saves you time. Remember that syntax checking cannot find logical errors; the types of errors that cause the program to return incorrect results or to run in some unexpected way. Agilent Technologies 2001, 2003 Test Development Tools 3-11

78 Chapter 3: The BT-BASIC Environment Failure messages associated with testing PC boards, a component is measured and fails to meet specifications, are not related to the error checking described here. The Softkeys The softkeys are in the top row of the keyboard and are identified as keys F1 through F8. These keys are called soft because their definitions can change with the task you are doing or if you redefine them. If a task uses softkeys, the current definitions of those keys appear at the bottom of the window they affect. If more than one window containing softkeys is present on the screen, the softkeys affect only the active window (the window that contains the mouse cursor). The standard softkeys are immediate-execute keys. Its function is executed immediately upon pressing the key, and does not have to be followed by a Return. Table 3-6 on page 3-12 contains a list and brief description of the standard softkey definitions that appear in basic mode (changing to another mode can change the softkey definitions) when you log in. The softkeys are used interactively for manipulating information on the workstation screen. You also can use the mouse to press softkeys when they are displayed on the screen. Simply place the mouse cursor on the softkey and click the mouse s left button. Redefining the Softkeys Softkey definitions can be changed to suit your needs. The statements in Table 3-7 on page 3-13 are used to manipulate softkey definitions. Table 3-6 Softkeys Softkey F1 command/edit F2 recall plus F3 recall minus Description If the cursor is in the work area, this key moves it to the command line. Or, if the cursor is in the command line, this key moves it to the last known position in the work area, or to the top of the work area if the last position is not known. Recalls, one by one, the commands (statements) now in the command stack. As commands are executed in the command line, they are added to the stack if they are not already there. Older commands drop off as new commands are added. The stack can hold up to 20 lines. Agilent Technologies 2001, 2003 Test Development Tools 3-12

79 Chapter 3: The BT-BASIC Environment Table 3-6 Softkeys (continued) Softkey F4 execute F5 mark F8 store line Description Executes the command now in the command line; the Return key can perform the same function. Also used to confirm that you really want to exit BT-BASIC if the workspace has been edited. Defines (marks) a group of lines in the workspace to be operated on as a block. This key changes its definition each time it is pressed, switching from mark to second mark to remove marks. To define a block, move the cursor to the start of the block and press mark. Then move the cursor to the end of the block and press second mark. The block is ready to edit. After editing, press remove marks. Copies a line from the command line into the work area. The new line is inserted at the current position of the cursor, and it overwrites any previous line. Table 3-7 Softkey manipulation statements (continued) Table 3-7 Statement softkey softkey clear softkeys clear softkeys Softkey manipulation statements Definition Changes a softkey definition. Selects the default softkey definition for a single softkey. Globally selects the default softkey definitions for all softkeys. Activates a redefined softkey. Statement softkeys on & off softkeys to & over Definition Switches between default and modified softkeys. Stores modified softkey definitions. Agilent Technologies 2001, 2003 Test Development Tools 3-13

80 4 Agilent Pushbutton Debug In this chapter... Features of Agilent Pushbutton Debug, 4-4 Miscellaneous Topics, 4-21 Objectives When you finish reading this chapter, you should be able to describe the appearance and features of Agilent Pushbutton Debug. Pushbutton Debug is a software package that: Simplifies your use of the test system's debug features by freeing you from having to remember their exact syntax. Provides macros, which act as typing aids that simplify and speed up the process of debugging. Lets you debug tests in any order. Includes a feature called AutoAnalog Debug that automatically debugs tests for resistors, capacitors, FETs, and inductors (except for tests in which the device is adjustable). This can greatly reduce the time it takes to get a new test debugged and into production. Prerequisites Some aspects of Pushbutton Debug are primarily a user interface that aids your use of the debug features that already exist on your test system. Because much of your interaction with Pushbutton debug simply passes standard debug statements to the BT-BASIC environment, this chapter assumes you already have a good working knowledge of debug. If this is not true, see the following: Analog debug is described in Chapter 5, Debugging Analog Tests in Test Methods: Analog. Digital debug is described in Chapter 6, Debugging Digital Tests in Test Methods: Digital. Agilent TestJet debug is described in Chapter 2, Agilent TestJet and Agilent Vectorless Test EP in Optional Board Test Applications. Serial debug is described in the Agilent 307XCT Serial Functional Test documentation. Agilent Technologies 2001 Test Development Tools 4-1

81 Chapter 4: Agilent Pushbutton Debug NOTE Detailed information about this software package is provided via online help, which includes on-item help that lets you point to a feature on the screen and then describes that feature to you. Because extensive online help is available, this chapter provides only the information needed to understand and begin using the software package. Figure 4-1 on page 4-3 shows an example of how Pushbutton Debug appears on the screen. Here, it is being used with the graphical debug window, which is a logic analyzer-like display that shows the timing associated with a test. This environment lets you quickly examine or modify the source file for a test and then see the results. Agilent Technologies 2001 Test Development Tools 4-2

82 Chapter 4: Agilent Pushbutton Debug Figure 4-1 Typical session with Pushbutton Debug Agilent Technologies 2001 Test Development Tools 4-3

83 Chapter 4: Agilent Pushbutton Debug Features of Agilent Pushbutton Debug The following topics describe the major features of Pushbutton Debug. Board-Level Versus Device-Level Debug Figure 4-2 The two levels of Pushbutton Debug Board-level debug Testplan Pushbutton Debug lets you debug your board tests at either of two levels: Repair Tickets Board-level debug: Sets up the testhead for debug, execute sections of the test, and collect a list of tests that fail. Device-level debug: Choose specific tests from the list of failures and then collect data and debug them. Figure 4-2 shows a conceptual diagram of the two levels of debugging. Board-level debugging begins with the testplan, which either contains or calls the tests used to test the board. After using Pushbutton Debug to load the testplan and generate repair tickets for failing tests, you can debug the individual tests in a mode called Device-level debug. Pins Pre-Shorts Shorts Analog Digital Serial TestJet Polarity Check Device-level debug Individual tests Pushbutton Debug is primarily a syntax builder that lets you interact quickly with the standard debug environment on the Agilent 3070 family of board test system. Choosing items from Pushbutton Debug s menus creates the needed syntax and then automatically sends it to the BT-BASIC environment for execution. Agilent Technologies 2001 Test Development Tools 4-4

84 Chapter 4: Agilent Pushbutton Debug Starting Pushbutton Debug at the Board Level Pushbutton Debug helps you identify and debug failing tests. You can use any of the following methods to start Pushbutton at the board level. Click the 3070 icon on the Front Panel and click the Pushbutton Debug icon. Use the msi statement to move to the correct board directory and type the following on the BT-BASIC command line: load board debug board Use the mouse to drag a board directory from File Manager and drop it on the Pushbutton Debug icon in the 3070 Programs panel. NOTE See Chapter 6, Debugging Digital Tests in Test Methods: Digital for more information. When you have finished using Pushbutton Debug, select File, then Exit from the menu bar. Board-Level Debug Start Pushbutton Debug at the board level. This is the starting point for debugging at the board level. Features of Board-Level Debug Table 4-1 on page 4-5 describes the features available for board-level debug. Table 4-1 Features of board-level debug Feature Menu Bar List of Failing Tests Description Provides access to several levels of menus and options through which you interact with Pushbutton Debug. Displays a list of tests that failed during a board test. Select items from this list and debug them with Pushbutton Debug. Agilent Technologies 2001 Test Development Tools 4-5

85 Chapter 4: Agilent Pushbutton Debug Table 4-1 Feature Repair Ticket Area Message Area Select button List button Break Command Features of board-level debug (continued) Description An area in which the repair tickets for failing tests appear here. You can also use this area as a general-purpose editor with any text file. The results from using macros can also appear here. Editing Tips: Because the Tab key can be used to move from item to item in this form, you must use CTRL-Tab to move from tab stop to tab stop when editing in the repair ticket area. To move to the beginning of the file, press and hold the CTRL key and then press the home-up key (the white arrow key in the keyboard's Cursor Control Group of keys). To move to the end of the file, press and hold the Extend char key and then press the home-up key. When you use the Insert char key to switch between overtype and insert mode, the letters IC (Insert Character) appear at the upper right corner of the form, just below the Help label in the menu bar. Displays status messages or error messages while using Pushbutton Debug. The label directly above this area reads Board Level Debug or Device Level Debug to indicate which of the two debug modes is currently enabled. The actual debug statements appear in this area as they are sent to the BT-BASIC environment. Chooses the highlighted test as the one to debug. Not used for board-level debug. Sends a break or interrupt to the BT-BASIC environment from which Pushbutton Debug was invoked. This is useful for interrupting debug operations, such as stopping a recycle to fail. The File Menu Use the File menu to create a new file, open an existing file, save or rename a file, or exit Pushbutton Debug. The options available at this menu are presented in Table 4-2. Agilent Technologies 2001 Test Development Tools 4-6

86 Chapter 4: Agilent Pushbutton Debug Table 4-2 Menu Item Open New Save Save as Unlink Exit File menu options Description Opens an existing file for editing. The file is loaded into the repair ticket area, which you can use as a general-purpose editor for text files. Clears the repair ticket area. If you select this option while editing an existing file, you are given the option of saving the existing file before creating a new file. Saves the current contents of the repair ticket area. Saves the current contents of the repair ticket area, but saves it under a different name than the original file from which it was loaded. You are prompted for a new name. Unlinks or removes a file, or unlinks the name from the file if it has multiple links. This is useful with multi-board panels, where the name of a single source file may be linked to many tests. Exits Pushbutton Debug and return to the BT-BASIC session from which Pushbutton Debug was invoked. The Debug Menu Options from the Debug menu, presented in Table 4-3, are used to debug individual tests and recompile tests with or without debug. Agilent Technologies 2001 Test Development Tools 4-7

87 Chapter 4: Agilent Pushbutton Debug Table 4-3 Debug menu options Menu Item Debug Next Test Debug Selected Test Debug Test Debug Current Test Debug Board Debug Version Debug Status Compile Selected Test Compile Selected Test; Debug Compile Test Mark Permanent Description Debugs the next test in the list of failing tests. If no test is selected, the first test in the list is debugged. Executes whichever test is currently selected (highlighted) in the list of failing tests. Lets you enter the name of a specific test to debug and, optionally, specify parameters for the test. Returns to the last test debugged during this session. Returns you to board-level debug if you are in device-level debug. Specifies which version of the board will be tested. Sends status information about the current debug session to whichever device is selected by a printer is statement. Compiles the source files associated with whichever test is selected in the list of failing tests. Compiles the source files associated with whichever test is selected in the list of failing tests and creates a debug object used to provide Pushbutton Debug with more information about the test. Lets you enter the name of a specific test to compile and, optionally, specify compilation options. Marks the test as permanent in the file testorder so that IPG does not alter the test. Agilent Technologies 2001 Test Development Tools 4-8

88 Chapter 4: Agilent Pushbutton Debug The Edit Menu The Edit menu, shown in Table 4-4, lets you interact with the contents of the repair ticket area. Table 4-4 Edit menu options Menu Item Cut Copy Paste Find String Go To Line Duplicate A Line Description Deletes the selected (highlighted) text and places it in a buffer. Copies the selected text and places it in a buffer. Inserts previously stored text (from a Cut or a Copy operation) from a buffer into the repair ticket area at the current location of the typing cursor. Searches for specific text in the repair ticket area. Moves the typing cursor to the specified line. Copies the line on which the typing cursor is currently located. The Macros Menu Selecting Macros from the menu bar invokes the Macros menu, which lets you use macros. Macros are stored commands or groups of commands that you can quickly execute as needed. Think of a macro as a stored sequence of events that can be played back simply by selecting the corresponding item from a menu. Besides providing you with a predefined set of starter macros, Pushbutton Debug lets you create your own macros. Or, you can easily customize the macros that we provide. See Customizing the Macros Menu on page 4-21 for details. Agilent Technologies 2001 Test Development Tools 4-9

89 Chapter 4: Agilent Pushbutton Debug The default options at the first level of the Macros menu are listed in Table 4-5 Table 4-5 Macros menu options Menu Item Setup Macros Testplan Macros Test Grader Macros Description Invokes a list of setup macros, which are used to set up the testhead, load the testplan, and do other steps required to execute a section of the testplan. These macros set up the test environment so you can execute and debug tests. Invokes a list of testplan macros, which are used to execute a section of the testplan and retrieve failing tests and repair tickets. A list of failing tests is automatically placed under Failing Tests: in the main form and the repair ticket is placed in the repair ticket area. Invokes a list of Board Test Grader and Test Coverage macros, which are used to generate a report of the quality of the board test and test coverage. The Board Test Grader and Test Coverage are explained in Chapter 9, Board Test Grader, Test Coverage, & Coverage Analyst. Selecting Macros followed by any of these options invokes a submenu. Macro menus can be customized and their contents may vary, thus the submenu may vary as well. If you choose Setup Macros, Testplan Macros, or Test Grader Macros, the appropriate menu will appear and will reflect any custom macros you use. NOTE See Chapter 9, Board Test Grader, Test Coverage, & Coverage Analyst for a description of the Board Test Grader. Device-Level Debug The next several topics describe the appearance and features of the debug features available at the device level, which is where individual tests are debugged. Agilent Technologies 2001 Test Development Tools 4-10

90 Chapter 4: Agilent Pushbutton Debug CHEK-POINT and Shorts Debug at the Device Level You can debug a shorts test at the device level. Table 4-6 describes the features provided to debug CHEK-POINT (pins) and shorts tests. Table 4-6 Feature Menu Bar Features of CHEK-POINT and Shorts Debug at the device level Description The menu bar near the top of the main form provides access to several levels of menus and options through which you interact with Pushbutton Debug. Test source display and edit area Message Area An area where statements in the test source are displayed for the test being debugged. Unlike board-level debug, this area cannot be used as a general-purpose editor in device-level debug. The mode indicator near the upper right corner always shows the current mode, which is shorts here. Editing Tips: Because the Tab key can be used to move from item to item in this form, you must use CTRL-Tab to move from tab stop to tab stop when editing in the test source display and edit area. To move to the beginning of the file, press and hold the CTRL key and then press the home-up key (the white arrow key in the keyboard s Cursor Control Group of keys). To move to the end of the file, press and hold the Extend char key and then press the home-up key. When you use the Insert char key to switch between overtype and insert mode, the letters IC (Insert Character) appear at the upper right corner of the form, just below the Help label in the menu bar. An area in which status messages or error messages appear while you use Pushbutton Debug. The label directly above this area reads Board Level Debug or Device Level Debug to indicate which of the two debug modes is currently enabled. As you use Pushbutton Debug, you can watch the Message Area and see the actual debug statements that are sent to the BT-BASIC environment. Agilent Technologies 2001 Test Development Tools 4-11

91 Chapter 4: Agilent Pushbutton Debug Table 4-6 Feature Break Command Features of CHEK-POINT and Shorts Debug at the device level (continued) Description Sends a break or interrupt to the BT-BASIC environment from which Pushbutton Debug was invoked. This is useful for interrupting debug operations, such as stopping a recycle to fail. Notice that besides the overall changes to the appearance of the form when switching from board-level to device-level debug, there are new items in the menu bar. The contents of the menu bar change as needed to provide selections appropriate for the kind of debugging being done. Analog Debug at the Device Level You can use Pushbutton Debug to debug an analog in-circuit test at the device level. Besides the features already described for CHEK-POINT, and shorts, and for Agilent TestJet debug which is described in the next section, this form includes the Compile and Go button, which lets you quickly compile changes made in the Test source display and edit area and then rerun the changed test. Agilent TestJet Debug at the Device Level You can debug an Agilent TestJet test at the device level. TestJet debug macros include: TestJet Close Adjust-With Board TestJet Close Adjust-Without Board TestJet Close Adjust-Calculate Results TestJet Missing Adjust-Loaded TestJet Missing Adjust-Blank TestJet Missing Adjust-Calculate Results Faon Faoff NOTE See Chapter 2, Agilent TestJet and Agilent Vectorless Test EP in Optional Board Test Applications for a description of these macros and how to use them. Agilent Polarity Check Debug at the Device Level You can debug an Agilent Polarity Check test at the device level. To get to the appropriate screen, enter polarity as the name of the test in the Debug/Debug Test dialog box. Agilent Technologies 2001 Test Development Tools 4-12

92 Chapter 4: Agilent Pushbutton Debug Digital Debug at the Device Level You can debug a digital in-circuit test at the device level. Digital device-level debug has the following unique features: Table 4-7 Feature Features of Digital Debug at the device level Description Test source display and edit area List area Select button List button This area provides additional features in digital debug. Notice that an arrow appears to the left of this area. When you use the graphical waveform display, the position of the arrow cross-references the graphical display with the test source. As you move through the graphical display, this arrow moves to show which section of the test source corresponds to the resultant waveform. This arrow changes to a question mark if you have modified the test source and Pushbutton Debug cannot accurately correlate the changed source statements with the results in the graphical waveform display (which is generated from object code that has not been changed). However, the question mark does show an approximate correlation between the two unless you have made extensive changes to the test source. An area in which a list of devices, VCL groups, pins, nodes, or internal nodes appears. You select items to work on from this list. A shortcut that lets you quickly select or unselect every item in the list area. Lets you choose what to display in the List area. You can display devices, VCL groups, pins, nodes, or internal nodes. Agilent Technologies 2001 Test Development Tools 4-13

93 Chapter 4: Agilent Pushbutton Debug Table 4-7 Feature Features of Digital Debug at the device level (continued) Description Graphic Edit Mode Vector Mapping Controls and shows the status of your interaction with the List area or the graphical debug window. As you execute debug statements, those statements act upon items that affect a specific test. For example, debug statements affect things like devices, groups, pins, nodes, timing, driver and receiver thresholds, and more. It is up to you to specify which of these many items a debug statement affects. The Graphic Edit Mode pushbutton provides a quick way for you to select which item to use in a debug operation. Clicking in the graphical debug window or clicking this pushbutton directly causes this pushbutton to light. When the pushbutton is lit you can select an item by clicking on it in the graphical debug window. For example, suppose you want to change the receiver high value on a specific pin during a specific vector. If that pin and vector are displayed in the graphical debug window, you can simply click on it to indicate your preference and then select Set Reference Receive High from the menu bar. When the Graphic Edit Mode pushbutton is unlit, you use the List area to select items for debug operations. An error message appears if you attempt to execute a debug statement without selecting an item from either the List area or the graphical debug window. Invokes an option menu that lets you use the Test source display and edit area to view either the definition section or the execution section of the test. Serial Debug at the Device Level You can debug a serial test at the device level. The features provided by device-level debug for serial tests are similar to those described for the other kinds of device-level debug, except that serial debug s list area lists processes instead of tests. Structure of Device-Level Debug The menus and options beneath the menu bar are organized into a hierarchy. Although analog debug, digital debug, shorts debug, and serial debug have menu items in common, options in some submenus vary with the mode. Agilent Technologies 2001 Test Development Tools 4-14

94 Chapter 4: Agilent Pushbutton Debug The Mode Menu Selecting Mode from the menu bar invokes the Mode menu, which is a pull-down menu. When appropriate, this menu lets you change from one kind of program source to another; for example, you can switch between analog and digital sources when debugging a mixed test that uses both. At other times this menu simply shows which mode is being used, and you cannot interact with it. Table 4-8 Option Analog Digital Serial Mode menu options Description Lets you work with analog in-circuit or analog functional tests. Lets you work with digital in-circuit or digital functional tests. Lets you work with serial, digital tests that consist of statements from the Serial Test Language (STL). You cannot select inappropriate items from this menu. For example, if a test is exclusively digital, the Analog and Serial items are automatically stippled or grayed-out to keep you from using them. Agilent Technologies 2001 Test Development Tools 4-15

95 Chapter 4: Agilent Pushbutton Debug The Execute Menu The Execute menu lets you choose how vectors are executed and specify options for safeguard and the learn feature. The options in the Execute menu are presented in Table 4-9. These options vary with the debug mode. Table 4-9 Execute Menu options Menu Item Execute To End Execute To Fail Execute To Vector... Recycle To End Recycle To Fail Recycle To Fail; Halt Recycle To Vector... Test Cont Safeguard None Safeguard All Description Executes the test currently being debugged. The test is executed once to the end, regardless of failures. Executes the test currently being debugged. The test is executed once, either until the first failure occurs or, if the test does not fail, to the end of the test. Lets you specify the number of an individual vector to execute. Repeatedly executes the test currently being debugged, regardless of failures. Repeatedly executes the test currently being debugged until a break is received. If a failure occurs, the test restarts immediately. Repeatedly executes the test currently being debugged until a break is received. If a failure occurs, test execution halts. Lets you specify the number of an individual vector to recycle. Continues a test after the test has been stopped by a halt or a pause statement. Turns off all SAFEGUARD controls. Turns on all SAFEGUARD controls. Agilent Technologies 2001 Test Development Tools 4-16

96 Chapter 4: Agilent Pushbutton Debug Table 4-9 Menu Item Learn On Learn Off Execute Menu options (continued) Description Turns on the learn feature, which is used to learn and store data from a known good (golden) board. Turns off the learn feature. The Display Menu Selecting Display from the menu bar invokes the Display menu, which is a pull-down menu that lets you choose what to display in the graphical debug window, control how that information is displayed, and work with files that contain the results of display operations. The options in the Display menu are (these options vary with the debug mode): Table 4-10 Display menu options Menu Item Display Define Display Control File I/O Description Lets you choose the kind of information that appears in the graphical debug window. You can execute a test and then display failures, actual results, expected results, or other information. Lets you control how information is displayed in the graphical debug window. For example, you can refresh or update the display, add or remove markers, adjust the scale of the display, etc. Lets you save or recall the results of displays. The Set Menu Selecting Set from the menu bar invokes the Set menu, which is a pull-down menu. Its submenus, presented in Table 4-11, let you specify parameters for the drivers and receivers used in digital testing. Agilent Technologies 2001 Test Development Tools 4-17

97 Chapter 4: Agilent Pushbutton Debug Table 4-11 Set menu options Menu Item Set Load Set Offset Set Reference Set Slew Rate Set State Set Terminators Description Invokes a submenu that lets you define the pull-up or pull-down loads for receiver pins. Invokes a submenu that lets you define the offsets on drivers, receivers, or on the probe. Invokes a submenu that lets you change the high and low reference voltages for drivers and receivers on pins and nodes. Invokes a submenu that lets you change the slew rate on one or more drivers. Invokes a submenu that lets you set drivers and receivers to a low, high, or high-impedance state. Invokes a submenu that lets you use the diode-clamp terminators in the receiver circuits on HybridPlus Cards to enhance the quality of high-speed signals. The Util Menu Selecting Util from the menu bar invokes the Util menu, which is a pull-down menu. Options at that menu are presented in Table This menu lets you work with debug adjustments and backpatches, control the timing-related features of debug, and add or remove drivers, receivers, debug sync signals, and vectors. Agilent Technologies 2001 Test Development Tools 4-18

98 Chapter 4: Agilent Pushbutton Debug Table 4-12 Util menu options Menu Item Administration Timing Add/Remove Description Invokes a submenu that lets you print or remove control adjustments to test parameters made during debugging, simulate fault conditions on one or more nodes, and work with backpatches. Use Diagnose Faults for board test transportability. Diagnose Faults automatically analyzes a failing test by varying several test parameters (attempting to make the test pass) and then generates a report detailing possible changes to correct the failure. Invokes a submenu that lets you control features of debug that are related to timing, such as set the vector cycle time, set the period of the DUT clock, and select which edge of the external clock is used to synchronize the test timing. Lets you add or remove drivers, receivers, debug sync signals, and vectors. Also lets you display all homingloop machine vectors including the piped vectors for each pass through the homingloop. The Ports Menu Selecting Ports from the menu bar invokes the Ports menu, which is a pull-down menu. This menu lets you connect one of the three debug ports sync, clock, or data to one of several resources. The options in the Ports menu create dbconnect statements whose actions correspond to the menu items. AutoAnalog Debug AutoAnalog Debug automatically debugs tests for resistors, capacitors, FETs, and inductors (except for tests in which the device is adjustable), which greatly reduces the time it takes to get a new test debugged and into production. You can start AutoAnalog Debug by selecting either of two options from Pushbutton Debug s Macros menu -- Setup Macros or Testplan Macros. Notice that both menu items for AutoAnalog Debug appear after the items that run the pins, preshorts, and shorts tests. This means that those tests are run automatically when you start AutoAnalog Debug, and you do not need to run them by themselves. Agilent Technologies 2001 Test Development Tools 4-19

99 Chapter 4: Agilent Pushbutton Debug The menu items that invoke AutoAnalog Debug are: Menu Item AutoAnalog Debug Calculate Test Limits... Description Invokes the default operating mode, which automatically debugs all applicable tests for the board. Invokes a dialog box that prompts you for the name of a file that contains a list of tests whose limits should be recalculated. This lets you selectively choose which tests have their limits recalculated. the operator to manually engage or disengage the fixture as needed. For more information about editing macros, see Customizing the Macros Menu on page After AutoAnalog Debug has finished, it presents a list of any failing tests it was unable to debug automatically. You can use the features described earlier in this chapter to manually debug the remaining tests at the board level in Pushbutton Debug. When using Pushbutton Debug s AutoAnalog Debug feature with a non-vacuum fixture, you must edit the following macro files in directory: <board_directory>/debug/board/aadebug_macros: "ExtraMeas" "Final" "InitTest" "PreTest" Remove the vacuum actuations commands, faon and faoff. Then you can use an input statement to prompt Agilent Technologies 2001 Test Development Tools 4-20

100 Chapter 4: Agilent Pushbutton Debug Miscellaneous Topics Subsequent Runs Are Faster As you use Pushbutton Debug you notice that some features execute slowly the first time you use them. In particular, there is a delay when using on-item help or debugging an item the first time. This is because some software features are created as needed each time you use Pushbutton Debug. Once they have been created, they are quickly available for subsequent use in the same session. You can minimize this effect during device-level debug by creating a list of devices in the list area and then using the Debug Next Test option in the Debug menu. This is much faster than repeatedly selecting only a single device each time for debugging. Using Vacuum Fixtures with Agilent Pushbutton Debug When using a vacuum fixture, you must be sure your testplan contains a vacuum well statement that refers to your specific vacuum configuration. You can find the vacuum well statement in the Initialize_Board_Constants section of the testplan file for your board, as the following example shows. sub Initialize_Board_Constants global Board$, Board_Rev$ Board$ = "my_board2" Board_Rev$ = ""!'vacuum well' stmt goes here if req d vacuum well a is 2,3 subend If the default vacuum configuration is not correct, load the testplan into the BT-BASIC workspace and modify it. Customizing the Macros Menu You can easily customize the Macros menu and the list(s) of macros invoked from it. The macro directory structure begins with a directory named debug beneath your board directory. Beneath directory debug are subdirectories, each of which is named for the level of macros it contains, as presented in Table Table 4-13 Macros Macro analog board connectcheck Description Contains macro files used for device-level analog debug. Contains macro files used for all board-level debug. Contains macro files used for all board-level Connect Check test debug. Agilent Technologies 2001 Test Development Tools 4-21

101 Chapter 4: Agilent Pushbutton Debug Table 4-13 Macros (continued) Macro digital polcheck serial shorts testjet Description Contains macro files used for device-level digital debug. Contains macros files used for device-level debugging of Polarity Check tests. Contains macros files used for device-level debugging of serial tests. Contains macros files used for device-level debugging of shorts tests. Contains macros files used for device-level debugging of TestJet tests. The above example shows how the macro files for board-level debug are organized, but a similar structure provides macros beneath directories analog, connectcheck, digital, polchk, shorts, serial, and testjet. Directory board contains a file named menu and one or more subdirectories. File menu defines the first level of items that appears when you invoke Macros from the menu bar. This file contains two entries per item, which are: The names of subdirectories, which appear as items in the menu. Because file names cannot contain spaces, the underscore character (_) is used to connect words when menu items are longer than one word. The underscore is automatically removed when the file name is displayed as a menu item. A letter that uniquely identifies the mnemonic shortcut for that item in the menu. In the example, menu contains definitions for two items in the menu at the first level: Setup Macros and Testplan Macros. When the menu appears, the S in Setup Macros is underlined to identify it as the mnemonic shortcut for that item. The T in Testplan Macros is similarly underlined. Definitions for the second level of menu items reside beneath subdirectories Setup_Macros and Testplan_Macros. Subdirectory Setup_Macros contains files for the corresponding menu item of the same name. Again, there is a file named menu that defines what items appear in the menu at this level. The example includes Testhead Power On, whose mnemonic shortcut is O, and Custom, whose shortcut keystroke is C. Also beneath directory Setup_Macros are files containing one or more programming statements to be executed by the macros. The name of each file must match that of its corresponding item in file menu at this level. For example, menu item Testhead Is 1 executes the contents of file Testhead_Is_1. Agilent Technologies 2001 Test Development Tools 4-22

102 Chapter 4: Agilent Pushbutton Debug In the example, file Testhead_Is_1, which corresponds to item Testhead Is 1 in the menu, executes a single statement: testhead is 1. In contrast, file Custom contains several statements that are executed when item Custom is invoked from the menu. Under directory AADebug_Macros are files containing macros used by Pushbutton Debug s AutoAnalog Debug feature. Be aware that for board-level debug your test system does not support more than two levels of menus beneath Macros in the menu bar. Device-level macros can contain only one level. You can use the BT-BASIC editor to examine or modify these files. If you like, you can add custom entries at either level of the menu. For example, you could add another group of items in the menu with Setup Macros and Testplan Macros. Or, you could define additional items in the existing menus. NOTE As with other standard files on your test system, the default macro files reside in directory $AGILENT3070_ROOT/standard. They are automatically copied to your board directory during testplan generation. Thus, modifying the standard files changes the macro defaults on your system. NOTE With Agilent 3070 software revision pa, an environment variable was created so that files can be easily transferred between UNIX and MS Windows controllers, which have different file systems. The environment variable, $AGILENT3070_ROOT, replaces the upper path names on both systems.for example, the $AGILENT3070_ROOT factory default value is /var/hp3070. In this document, only path names using the environment variable are used. If you must use actual path names, refer to older versions of the documentation. Please see The Root Directory Environment Variable in Administering Agilent 3070 UNIX Systems for further information. Menu items appear in the order in which you define them in the files. Be sure to supply a unique mnemonic shortcut for each item, and place that shortcut on the line following the menu item. Leaving a blank line between entries in any of these files causes a horizontal bar to appear as a separator between items. This is useful when arranging items into groups of similar items. Agilent Technologies 2001 Test Development Tools 4-23

103 5 The Plot Generator In this chapter... About The Plot Generator, 5-2 About the Plots, 5-3 Things to do Before Using the Plot Generator, 5-6 Running the Plot Generator, 5-7 piece of clear plastic or Mylar and then comparing the plot against the blank PC board. If the plots reveal a problem, then you can fix it (and verify the fix) at the earliest (and least expensive) point in the fixturing process. Using Plotters with the Plot Generator, 5-8 Usage Notes, 5-10 Objectives When you finish reading this chapter, you should understand the Plot Generator program, referred to in this documentation as Plot Generator. The Plot Generator helps you develop a test fixture by modeling the fixture on paper before you actually build it. After you have built the fixture, the plots can be used as aids in debugging. The Plot Generator is especially useful in verifying that fixturing data is correct before you build a fixture. For example, the plots generated by the Plot Generator can show whether or not the board is correctly oriented on the fixture. Or, you can verify that probes appear in the correct locations by generating a full-sized plot on a Agilent Technologies 2001 Test Development Tools 5-1

104 Chapter 5: The Plot Generator About The Plot Generator The Plot Generator produces plot files from data contained in the board_xy.o and fixture.o files. You then draw a plot by copying a plot file to a plotter (if you do not have a plotter, see Viewing Plot Files on page 5-10). The information shown in the plots generated by the Plot Generator includes the following: Locations of personality pins and probes (devices and vias) on the fixture s top and bottom plates. Placement of the circuit board(s) on the fixture. Locations of the critical and functional interconnecting wires in a fixture. Location of all alternate and extra probes (both for nodes and for device pins). Location of tooling holes. Locations of keepout areas on the board, which are areas where probes and personality pins are not allowed. Locations of keepout areas on the fixture. Plots resulting from the Plot Generator work with a variety of plotters. For a list of plotters supported by the Plot Generator see Which Plotters Are Supported? on page 5-9. See your System Administrator to find out which of these devices is installed on your test system. Agilent Technologies 2001 Test Development Tools 5-2

105 Chapter 5: The Plot Generator About the Plots The various kinds of plots produced by the Plot Generator are: The Board_XY Plot The Probe Plot The Inserts Plot The Alignment Plot The Wires Plot The Board_XY Plot The Board_XY Plot is generated from data contained in the board_xy.o file. It shows the following information: The outline of a printed circuit board. The location of all alternate and extra probes (both for nodes and for device pins). Normal probes and extra probes are both labeled as GOOD in the plot. The location of tooling holes. The location of keepout areas on the board, which are areas where probes and personality pins are not allowed. The plot is stored in a file named board_xy.p in the local board directory. Plots use the following colors: Green: mandatory locations. Blue: preferred and critical locations. Black: good and unreliable locations. Red: locations where probes cannot appear (such as NO PROBE and NO ACCESS). Red outline: keepout areas. NOTE Locations that cannot be manually probed during backtracing (NO MANUAL) are drawn in the appropriate color for the location. If top probes are allowed, a second file board_xytop.p is generated for the top plate of an Express Cassette fixture. This file is also stored in the local board directory. The Probe Plot The Probe Plot is generated from data contained in the fixture.o file. It shows the locations of all probes and personality pins, including alternates. The plot is stored in a file named probes.p in the fixture directory. The diameter of the probes approximates the required clearance each probe needs from other probes. If probe clearances are reduced by making changes to the fixture component files, then the diameters may overlap. This is because the diameters drawn using plot generator are Agilent Technologies 2001 Test Development Tools 5-3

106 Chapter 5: The Plot Generator based on standard clearances while the spacing of the probes are based on the new modified clearances. This overlap will provide visual feedback on the any changes made to the fixture component files. A Probe Plot uses the following colors and symbols: Black octagons: probes for devices. Blue octagons: probes for vias. Black plus signs (+): alternate probes for devices. Blue plus signs (+): alternate probes for vias. Green octagons: transfer probes. Green plus signs (+): drilled transfer probes. Red octagons: inserted pins. Red plus signs (+): drilled pins. Small, red squares: override pins. Red outline: keepout areas. If top probes are allowed, a second file (probestop.p) is generated for the top plate of an Express Cassette fixture. This file is also stored in the fixture directory. A plot generated from the probestop.p file does not show personality pins. The Inserts Plot The Inserts Plot is generated from data contained in the fixture.o file. It shows the locations of probes, and identifies their attributes (such as 50MIL, TRANSFERS, etc.). The plot is always shown from the probe side, which means the view is from the bottom for the top plate, and from the top for the bottom plate. The plot is stored in a file named inserts.p in the fixture directory. The Inserts Plot uses the following colors: Red: long and transfer probes. Black: 100 mil and 100 mil lightweight probes. Blue: 75 mil and 75 mil lightweight probes. Green: 50 mil probes are drawn in green. If top probes are allowed, a second file insertstop.p is generated for the top plate of an Express Cassette fixture. This file is also stored in the fixture directory. The Alignment Plot The Alignment Plot is generated from data contained in the fixture.o file. It shows the positions of personality pins with respect to the fixture alignment plate. Rectangles indicate the area into which a pin must flex in order to make contact. Agilent Technologies 2001 Test Development Tools 5-4

107 Chapter 5: The Plot Generator The plot is stored in a file named alignment.p in the fixture directory. Two sizes of rectangles can be shown in the Alignment Plot. Small rectangles denote the tapered holes in the alignment plate that are used for regular pins. The large rectangles denote areas that can be probed on the small printed circuit boards that are part of transfer mechanisms for offset personality pins. Because the top plate does not have personality pins, there is no Alignment Plot for the top plate. If top probes are allowed, a second file (wirestop.p) is generated for the top plate of an Express Cassette fixture. This file is also stored in the fixture directory. The Wires Plot The Wires Plot is generated from data contained in the fixture.o file. It shows the locations of all wires on critical and functional nodes with respect to the fixture plate. The plot is stored in a file named wires.p in the fixture directory. The plot uses the following colors: Red: wires on critical nodes. Blue: wires on functional nodes. Red wire: a wire on a node that is both critical and functional. Red outline: keepout areas. Agilent Technologies 2001 Test Development Tools 5-5

108 Chapter 5: The Plot Generator Things to do Before Using the Plot Generator Because plot files are produced from data contained in the board.o, board_xy.o and fixture.o files, these files must exist before you run the Plot Generator program. NOTE In order for these.o files to exist, the source files from which they are derived must either exist or you must follow the test development process to create them. If you run the Plot Generator from IPG Test Consultant, the necessary files are available when they are needed. But if you decide to manually run the Plot Generator from BT-BASIC (with the generate plot statement), keep the following in mind: If you intend to generate a Board_XY Plot, be sure that the board.o and board_xy.o files exist and that they are in the board directory. If these files do not exist, use the compile statement to create them. If you intend to generate any plot other than the Board_XY Plot, be sure that a fixture.o file exists and that it is in the fixture directory. If this file does not exist, use the compile statement to create it. Agilent Technologies 2001 Test Development Tools 5-6

109 Chapter 5: The Plot Generator Running the Plot Generator You can run the Plot Generator in either of two ways: Automatically from IPG Test Consultant. When you use IPG Test Consultant, there are two places where the Plot Generator is automatically run. One is after the board_xy file has been compiled (a Board_XY Plot is produced), and the other is after the fixture tooling software has been run (a Probe Plot and a Wires Plot are produced). Manually from BT-BASIC. Executing a generate plot statement on the BT-BASIC command line runs the Plot Generator. Optional parameters let you specify which type of plot to generate and which type of plotter to use; for details, see the description of the generate plot statement in Syntax Reference. finished, you can either draw a hard copy of the files immediately or do some other task and plot them later. To produce a hard copy of the plot files, use the copy over statement to copy them to a plotter. For example, you could send a plot file to the plotter like this: copy "wirestop.p" over plotter Be aware that each time you run the Plot Generator, existing plot files are overwritten by the newer versions. Unlike some other files on your test system, plot files are not automatically backed up. NOTE Because having IPG Test Consultant automatically run the Plot Generator produces only three of the five possible types of plots, running the Plot Generator from BT-BASIC provides additional functionality. As the Plot Generator runs, status messages appear on screen to inform you of the its progress (see Advisory Messages on page 5-10). When the Plot Generator has Agilent Technologies 2001 Test Development Tools 5-7

110 Chapter 5: The Plot Generator Using Plotters with the Plot Generator The following topics describe a few things you need to know about how the Plot Generator works with plotters. The Steps Required to Draw a Plot In general, here are the steps you should follow when drawing plots produced by the Plot Generator: 1 Load the paper. Insert paper into the plotter and verify that there are no errors. 2 Make sure the plotter is on-line. The plotter must be ready to receive data. 3 Turn on the rotate function. If this is required, see Orientation of the Plots. 4 Copy a plot file to the plotter. Use the copy over statement. 5 Reset the rotation. Set the rotation to normal after you have finished using the Plot Generator (or between plots if some of the plots do not require rotation). Orientation of the Plots When drawing a plot, the Plot Generator assumes the X-axis is the longer of the two axes on the paper. If this is not the case, use the front-panel controls on your plotter to rotate the plot before copying plot files to it. ADVICE This is easy to determine; if the combination of plotter and paper size you are using defaults to having the Y-axis as the longer axis, plots are cut off. Also be aware that which axis is the longer on a given plotter may vary with the paper size. Be aware that if your board_xy file contains a PLACEMENT keyword to specify rotation of the board, plots derived from it are already rotated. NOTE See Chapter 3, Creating Board Information in Test & Fixture Development for a description of board placement. Pen Colors and Types The Plot Generator supports the use of four pens, which should be installed as follows: Agilent Technologies 2001 Test Development Tools 5-8

111 Chapter 5: The Plot Generator pen 1 is black pen 2 is red pen 3 is green pen 4 is blue Unless you follow this definition when installing the pens, any references to specific colors in this chapter are incorrect. Be sure to use a plotter pen that is appropriate for the media being drawn upon. For details, refer to the documentation that came with your plotter. Plot Sizing and Scaling If no plot size or scale is specified, the Plot Generator defaults to paper size D and 100% scale (full-size). When the drawings are full-sized, it is easy to place them on top of a blank PC board for comparison purposes. Because the plots are drawn centered, you can use smaller paper if the full-sized plot fits on the paper. If the full-sized plot does not fit on the paper, the edges of the drawing are cut off. Which Plotters Are Supported? You can use an HP 7550 plotter, any HP 757X-series plotter, HP 758X-series plotter, or HP 759X-series plotter. These are connected to the LAN using JetDirect cards. ADVICE You probably want to have your System Administrator or an Agilent Technologies support person set up the plotter(s). ADVICE If producing accurate plots is important to you, be sure to have your plotter calibrated (as often as required) before using it with the Plot Generator. Even if your plotter is accurately calibrated, you can expect to see minor variations between the size of a plot and the size of the actual board or fixture. Agilent Technologies 2001 Test Development Tools 5-9

112 Chapter 5: The Plot Generator Usage Notes Viewing Plot Files If you do not have a plotter connected to your system, you can use a program called hpglviewer to display plot files on your workstation s screen. This method is not quite as useful as drawing full-sized plots on Mylar, but it does let you preview your fixture before building it. NOTE hpglviewer is a user-contributed program; see Chapter 4, Program Management and Miscellaneous Statements in Board Test Fundamentals. About Spoolers When you use the copy over statement to copy a plot file to a plotter, the file is sent to the standard spooling system on your system. If desired, you can run the Plot Generator on several networked systems and have the plots all plotted on a common, shared plotter anywhere in the network. This approach can be very cost-effective because it lets several systems share a color plotter that is only used occasionally. In order to use a remote plotter via networking, the appropriate spooling scripts must be installed by your System Administrator. NOTE See the LP Spooler topics in Chapter 8 of the System Administration Tasks documentation for details. Plot Files for the Top Plate Be aware that plot files for the top plate are automatically deleted if they are no longer needed. For example, the Plot Generator produces plots for both the bottom plate and the top plate if the value of the Top Probes Allowed option was ON when the data for a board was entered in Agilent Board Consultant. If you later set Top Probes Allowed to OFF and rerun the Plot Generator, an advisory message appears on the screen to inform you that any plot files for the top plate have been deleted. Advisory Messages As the Plot Generator runs, it may report minor discrepancies in the input data being processed, such as: No tooling information was found. This is acceptable, but plots do not show tooling holes. An advisory message such as this may reveal a problem, or you may decide that it is normal for this specific board. If it indicates a problem, you have the opportunity to correct the data before going further. Agilent Technologies 2001 Test Development Tools 5-10

113 Chapter 5: The Plot Generator Another advisory message you may see when running the Plot Generator is: Probe or alternate locations found on the other node. These locations are plotted. This means that when you ran the fixture generation software in incremental mode to minimize fixturing changes, one or more existing (from a previous run of the fixture generation software) probe locations were marked as unused (OTHER). When the Plot Generator processes data that contains probes marked OTHER, the plot shows probes or alternate locations that do not actually exist (unless you have already built the fixture). Agilent Technologies 2001 Test Development Tools 5-11

114 6 The Part Description Editor In this chapter... Descriptions of the Menus, Tasks, and Forms, 6-2 Descriptions of the Device Entry Forms, 6-8 Objectives When you finish reading this chapter, you should be able to describe the appearance and features of the Part Description Editor. Although you can manually write PDL (Part Description Language) files (in part mode), the Part Description Editor provides an easier way by allowing use of predefined forms to enter information for new libraries or maintain/modify the information in existing library entries. The Part Description Editor is a graphical user interface for creating or modifying a part description library. It provides features similar to those in other software packages that use windows, such as pull-down menus, use of the mouse, and online help. You should be familiar with this editor before you enter descriptions of new parts or modify existing descriptions. Prerequisites You must: Understand part description libraries and why you may want to use them. See Chapter 3, Creating Board Information in Test & Fixture Development. Understand the syntax of PDL. See Chapter 8, Part Description Language in Data Formats. Be familiar with features of the user interface. See Chapter 1, Using a Workstation in Board Test Fundamentals for more information. Agilent Technologies 2001 Test Development Tools 6-1

115 Chapter 6: The Part Description Editor Descriptions of the Menus, Tasks, and Forms Near the top of each form that appears in the Part Description Editor is a menu bar from which you can select menus and forms for doing tasks. The menus, tasks, and device entry forms available from the menu bar are organized into a general hierarchy, presented in Figure 6-1. (Online help is also available from the menu bar.) Agilent Technologies 2001 Test Development Tools 6-2

116 Chapter 6: The Part Description Editor Figure 6-1 Overview of tasks, menus, and forms in the Part Description Editor Menu Bar Device Entry Forms File Task Resistor New Open Save Save As Exit Initialization Device Entry Resistor Capacitor Inductor Potentiometer Diode Zener Transistor FET Capacitor Inductor Potentiometer Diode Zener Transistor FET Connector Connector Fuse Fuse Jumper/Strap Switch Pin Library Jumper/Strap Switch Library Device Agilent Technologies 2001 Test Development Tools 6-3

117 Chapter 6: The Part Description Editor These menus, tasks, and forms are described below. Table 6-1 File menu options (continued) The Menu Bar The options in the Part Description Editor form s menu bar include the following: File: Invokes the File Menu, used to manipulate files or exit the Part Description Editor. Task: Invokes the Task Menu, used to choose which task to do with the Part Description Editor. Help: Invokes the Help Menu for the Part Description Editor. The File Menu Create a new file, open an existing file, save a file, or exit the Part Description Editor. Menu Item Save Save as Exit The Task Menu The Task Menu invokes a cascading submenu of device entry forms or return to the Initialization Form. Table 6-2 Description Saves the file you are currently editing. Saves the file you are currently editing, but saves it under a different name. You are prompted for a new name. Exits the Part Description Editor. Task menu options Table 6-1 File menu options Menu Item Description Menu Item New Open Description Clears the Part Description Library for creating a new part description library. If you select this option while editing an existing file, you are given the option of saving the existing file before creating a new file. Opens an existing part description library file for editing. Initialization Device Entry Returns you to the Initialization Form, which is where you begin working on a part description library. Invokes a submenu of device entry forms. The cascaded submenu contains a list of the forms used to enter descriptions of individual devices in a part description library. Select an option from this menu to invoke the needed form. Agilent Technologies 2001 Test Development Tools 6-4

118 Chapter 6: The Part Description Editor ADVICE You can quickly switch between a device entry form and the Initialization Form by clicking on Prev Task or Next Task, as appropriate. The Initialization Form The Initialization Form appears whenever you invoke the Part Description Editor. It is the starting point for all tasks within the Part Description Editor. The Initialization Form includes the text boxes and data entry fields presented in Table 6-3. Table 6-3 Initialization form text boxes and data entry fields Text Box/ Data Entry Field Path to Part Description Library Initial Comments List of Unused (noconnect) External Pins Number of Internal Nodes Internal Nodes Description This text field shows the pathname of the current part description library file. If a part description library contains comments at the beginning, those comments appear here. Use this text box to add comments to a new part description library file or edit the comments in an existing file. If an external pin on a part description library device is not used, the pin is present but it does not make an internal connection to anything, it is listed here. Items in the list can be separated from one another by either commas or spaces. This text box shows how many (if any) internal nodes a part description library contains. If a part description library contains internal nodes, the names of those nodes appears here. Internal nodes are nodes that are connected internally but cannot be accessed externally via the fixture. Agilent Technologies 2001 Test Development Tools 6-5

119 Chapter 6: The Part Description Editor Table 6-3 Initialization form text boxes and data entry fields (continued) Text Box/ Data Entry Field No Manual Probe Access List of Devices in Part Description Description If this box is highlighted, the internal node listed to its left below Internal Nodes cannot be probed manually. This box contains buttons that list the designators (such as r1, c1) of devices included in the current part description library. Device Entry Forms After specifying global information in the Initialization Form, use the individual device entry forms to enter descriptive information about the devices in a part description library. Listed in alphabetical order, these forms include the following: Capacitor Entry Form Connector Entry Form Diode Entry Form FET Entry Form Fuse Entry Form Inductor Entry Form Jumper/Strap Entry Form Pin Library Entry Form Potentiometer Entry Form Resistor Entry Form Switch Entry Form Transistor Entry Form Zener Entry Form Figure 6-2 on page 6-7 shows a typical device entry form. Use the form in Figure 6-2 on page 6-7 (and similar forms for other kinds of devices) to specify the characteristics of a device within a part description library. Besides specifying the part s electrical characteristics, you also must specify how its pins are connected. Each device entry form is individually described in the following sections. Agilent Technologies 2001 Test Development Tools 6-6

120 Chapter 6: The Part Description Editor Figure 6-2 Entering a description of a typical device Agilent Technologies 2001 Test Development Tools 6-7

121 Chapter 6: The Part Description Editor Descriptions of the Device Entry Forms The following topics provide full descriptions of the Part Description Editor forms used to enter devices in part description libraries. Once you are familiar with these forms, you probably do not need to refer to these descriptions again. Table 6-4 Capacitor entry form data entry fields Capacitor Entry Form Use the Capacitor Entry Form to enter a description of a capacitor that appears in a part description library. The data entry fields in this form are shown in Table 6-4. Data Entry Field Description Designator A unique name that identifies a specific capacitor; for example, c1. Value Tolerances (+/-) Connections: Pin 1 Connections: Pin 2 Part Number Failure Message Replaceable The nominal value of the capacitor in farads (F), microfarads (uf), or picofarads (pf). The plus and minus tolerances expressed as percentages of the capacitor value. Both are positive numbers. The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor's part number or your internal part number, for the capacitor. A part number is used for reference purposes only. An optional message associated with the capacitor. Can be Yes or No. No denotes the capacitor as non-replaceable; the capacitor is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Agilent Technologies 2001 Test Development Tools 6-8

122 Chapter 6: The Part Description Editor Table 6-4 Capacitor entry form data entry fields (continued) Data Entry Field Type Testable Description Can be Fixed or Variable. Can be Yes or No. No instructs Agilent IPG not to write a test for the capacitor. Connector Entry Form Use the Connector Entry Form to enter a description of a connector that appears in a part description library. Connectors are not testable; enter them in part description libraries for documentation purposes. The data entry fields in this form are shown in Table 6-5 Table 6-5 Connector entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific connector; for example, j1. Number of Connections Pins Connections Part Number Failure Message Replaceable The total number of pins on the connector that are externally accessible. Enter a value and press Return; the appropriate number of rows appear beneath Pins and Connections. A number associated with a pin on the connector. The external pin or internal node to which each pin on the connector is connected. An optional part number, such as the vendor's part number or your internal part number, for the connector. A part number is used for reference purposes only. An optional message associated with the connector. Can be Yes or No. No denotes the connector as non-replaceable; i.e., the connector is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Agilent Technologies 2001 Test Development Tools 6-9

123 Chapter 6: The Part Description Editor Diode Entry Form Use the Diode Entry Form to enter a description of a diode that appears in a part description library. The data entry fields in this form are shown in Table 6-6. Table 6-6 Diode entry form data entry fields Data Entry Field Designator Forward Bias Test Limits: High Forward Bias Test Limits: Low Connections: Anode Connections: Cathode Part Number Failure Message Replaceable Testable Description A unique name that identifies a specific diode; for example, cr1. Specifies the upper test limit for the voltage drop across the diode when it is forward biased. Specifies the lower test limit for the voltage drop across the diode when it is forward biased. The external pin or internal node to which the anode of this device is connected. The external pin or internal node to which the cathode of this device is connected. An optional part number, such as the vendor s part number or your internal part number, for the diode. A part number is used for reference purposes only. An optional message associated with the diode. Can be Yes or No. No denotes the diode as non-replaceable; the diode is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the diode. Agilent Technologies 2001 Test Development Tools 6-10

124 Chapter 6: The Part Description Editor FET Entry Form Use the FET Entry Form to enter a description of a field-effect transistor that appears in a part description library. The data entry fields in this form are shown in Table 6-7 Table 6-7 FET entry form data entry fields Data Entry Field Designator On Description A unique name that identifies a field-effect transistor; for example, qf1. Resistance: High Specifies the high test limit for the channel resistance (R on ). On Resistance: Low Specifies the low test limit for the channel resistance (R on ). Type Connections: Source Connections: Gate Connections: Drain Part Number Failure Msg Replaceable Testable Can be N-Channel or P-Channel. The external pin or internal node to which this device s source is connected. The external pin or internal node to which this device s gate is connected. The external pin or internal node to which this device s drain is connected. An optional part number, such as the vendor s part number or your internal part number, for the FET. A part number is used for reference purposes only. An optional message associated with the FET. Can be Yes or No. No denotes the FET as non-replaceable; the FET is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the FET. Agilent Technologies 2001 Test Development Tools 6-11

125 Chapter 6: The Part Description Editor Fuse Entry Form Use the Fuse Entry Form to enter a description of a fuse that appears in a part description library. The data entry fields in this form are shown in Table 6-8. Table 6-8 Fuse entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific fuse; for example, f1. Max Current Connections: Pin 1 Connections: Pin 2 Part Number Failure Message Replaceable Testable The maximum permissible current through the fuse in amps. The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor s part number or your internal part number, for the fuse. A part number is used for reference purposes only. An optional message associated with the fuse. Can be Yes or No. No denotes the fuse as non-replaceable; the fuse is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the fuse. Agilent Technologies 2001 Test Development Tools 6-12

126 Chapter 6: The Part Description Editor Inductor Entry Form Use the Inductor Entry Form to enter a description of an inductor that appears in a part description library. The data entry fields in this form are shown in Table 6-9. Table 6-9 Inductor entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific inductor; for example, l1. Value Tolerances (+/-) Series Resistance Connections: Pin 1 Connections: Pin 2 Part Number Failure Message Replaceable The nominal value of the inductor in henries (H), millihenries (mh), or microhenries (uh). The plus and minus tolerances expressed as percentages of the inductor value. Both are positive numbers. The series resistance of the inductor in ohms, kilohms (k ohms), or megohms (M ohms). The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor's part number or your internal part number, for the inductor. A part number is used for reference purposes only. An optional message associated with the inductor. Can be Yes or No. No denotes the inductor as non-replaceable; the inductor is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Agilent Technologies 2001 Test Development Tools 6-13

127 Chapter 6: The Part Description Editor Table 6-9 Inductor entry form data entry fields (continued) Data Entry Field Type Testable Description Can be Fixed or Variable. Can be Yes or No. No instructs IPG not to write a test for the inductor. Jumper/Strap Entry Form Use the Jumper/Strap Entry Form to enter a description of a jumper or a strap that appears in a part description library. The data entry fields in this form are shown in Table Table 6-10 Jumper/Strap entry form data entry fields Data Entry Field Designator Connections: Pin 1 Connections: Pin 2 Part Number Failure Message Replaceable Description A unique name that identifies a specific jumper or strap; for example, jp1. The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor s part number or your internal part number, for the jumper or strap. A part number is used for reference purposes only. An optional message associated with the jumper or strap. Can be Yes or No. No denotes the jumper/strap as non-replaceable; the jumper/strap is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Agilent Technologies 2001 Test Development Tools 6-14

128 Chapter 6: The Part Description Editor Table 6-10 Jumper/Strap entry form data entry fields (continued) Data Entry Field Type Testable Description Can be Open or Closed to denote the state of the jumper or strap when it is tested. If you test the jumper or strap without setting it to the proper state specified will cause it to fail the test! Can be Yes or No. No instructs IPG not to write a test for the jumper or strap. Pin Library Entry Form Use the Pin Library Entry Form to enter a description of a pin-oriented library device that appears in a part description library. (Because the nodes on a board are not referenced in a library test, it does not make sense to describe a node-oriented test in a part description library.) The library device whose description you enter here can be analog, digital, mixed, or even another part description library. The data entry fields in this form are shown in Table Table 6-11 Pin Library entry form data entry fields Data Entry Field Designator Number of Connections Pins Connections Description A unique name that identifies a specific pin library device. The total number of pins on the library device that are externally accessible. After you enter a value in this field and press Return, the appropriate number of rows appear beneath Pins and Connections. A number associated with a pin on a library device. The external pin or internal node to which a pin on the library device is connected. Agilent Technologies 2001 Test Development Tools 6-15

129 Chapter 6: The Part Description Editor Table 6-11 Pin Library entry form data entry fields (continued) Data Entry Field Part Number Failure Message Replaceable Safeguard Testable Testability Standard Description A part number, such as the vendor's part number or your internal part number, for the library device. An optional message associated with the library device. Can be Yes or No. No denotes the library device as non-replaceable; the library device is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the library device. Library test expected. Potentiometer Entry Form Use the Potentiometer Entry Form to enter a description of a potentiometer that appears in a part description library. The data entry fields in this form areshown in Table 6-12 Table 6-12 Potentiometer data entry fields Data Entry Field Description Designator A unique name that identifies a specific potentiometer; for example, p1. Value The nominal value of the potentiometer in ohms, kilohms (k ohms), or megohms (M ohms). Agilent Technologies 2001 Test Development Tools 6-16

130 Chapter 6: The Part Description Editor Table 6-12 Potentiometer data entry fields (continued) Data Entry Field Tolerances (+/-) Connections: Pin 1 Connections: Wiper Connections: Pin 2 Part Number Failure Message Replaceable Testable Description The plus and minus tolerances expressed as percentages of the potentiometer s value. Both are positive numbers. The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which this device s wiper is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor s part number or your internal part number, for the potentiometer. A part number is used for reference purposes only. An optional message associated with the potentiometer. Can be Yes or No. No denotes the potentiometer as non-replaceable; the potentiometer is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the potentiometer. Resistor Entry Form Use the Resistor Entry Form to enter a description of a resistor that appears in a part description library. The data entry fields in this form are shown in Table Agilent Technologies 2001 Test Development Tools 6-17

131 Chapter 6: The Part Description Editor Table 6-13 Resistor entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific resistor; for example, r1. Value Tolerances (+/-) Connections: Pin 1 Connections: Pin 2 Part Number Failure Message Replaceable Type Testable The nominal value of the resistor in ohms, kilohms (k ohms), or megohms (M ohms). The plus and minus tolerances expressed as percentages of the resistor value. Both are positive numbers. The external pin or internal node to which the arbitrarily chosen Pin 1 of this device is connected. The external pin or internal node to which the arbitrarily chosen Pin 2 of this device is connected. An optional part number, such as the vendor s part number or your internal part number, for the resistor. A part number is used for reference purposes only. An optional message associated with the resistor. Can be Yes or No. No denotes the resistor as non-replaceable; the resistor is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Fixed or Variable. Can be Yes or No. No instructs IPG not to write a test for the resistor. Agilent Technologies 2001 Test Development Tools 6-18

132 Chapter 6: The Part Description Editor Switch Entry Form Use the Switch Entry Form to enter a description of a switch that appears in a part description library. The data entry fields in this form are shown in Table Table 6-14 Switch entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific switch; for example, s1. Number of Connections Pins Connections Open/Closed Part Number Failure Message The total number of pins on the switch that are externally accessible. After you enter a value in this field and press Return, the appropriate number of rows appear beneath Pins and Connections. A number associated with a pin on the switch. The external pin or internal node to which a pin on the switch is connected. Click a box marked Open to select (highlight) it if the contact listed below Connections in the same row is connected to Common when the switch is tested. If you highlight this box, the Open label changes to Closed. If you test the switch without setting it to the state specified here, it does not pass the test! An optional part number, such as the vendor s part number or your internal part number, for the switch. A part number is used for reference purposes only. An optional message associated with the switch. Agilent Technologies 2001 Test Development Tools 6-19

133 Chapter 6: The Part Description Editor Table 6-14 Switch entry form data entry fields (continued) Data Entry Field Replaceable Testable Description Can be Yes or No. No denotes the switch as non-replaceable; the switch is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the switch. Transistor Entry Form Use the Transistor Entry Form to enter a description of a bipolar transistor that appears in a part description library. The data entry fields in this form are shown in Table Table 6-15 Transistor entry form data entry fields Data Entry Field Description Designator A unique name that identifies a specific bipolar transistor; for example, q1. Beta Test Limits: High Beta Test Limits: Low Type Connections: Emitter Connections: Base Connections: Collector Part Number The upper test limit specified as a DC beta value. The lower test limit specified as a DC beta value. Can be NPN or PNP to denote whether the transistor is an NPN or a PNP device. The external pin or internal node to which this device s emitter is connected. The external pin or internal node to which this device s base is connected. The external pin or internal node to which this device s collector is connected. An optional part number, such as the vendor s part number or your internal part number, for the transistor. A part number is used for reference purposes only. Agilent Technologies 2001 Test Development Tools 6-20

134 Chapter 6: The Part Description Editor Table 6-15 Transistor entry form data entry fields (continued) Data Entry Field Failure Message Replaceable Testable Description An optional message associated with the transistor. Can be Yes or No. No denotes the transistor as non-replaceable; the transistor is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the transistor. Zener Entry Form Use the Zener Entry Form to enter a description of a Zener diode that appears in a part description library. The data entry fields in this form are shown in Table Table 6-16 Zener entry form data entry fields Data Entry Field Designator Value Tolerances (+/-) Connections: Anode Connections: Cathode Part Number Description A unique name that identifies a specific Zener diode; for example, ds1. The nominal value of the Zener diode. The plus and minus tolerances expressed as percentages of the Zener value. Both are positive numbers. The external pin or internal node to which this device s anode is connected. The external pin or internal node to which this device s cathode is connected. An optional part number, such as the vendor's part number or your internal part number, for the Zener diode. A part number is used for reference purposes only. Agilent Technologies 2001 Test Development Tools 6-21

135 Chapter 6: The Part Description Editor Table 6-16 Zener entry form data entry fields (continued) Data Entry Field Failure Msg Replaceable Testable Description An optional message associated with the Zener diode. Can be Yes or No. No denotes the Zener diode as non-replaceable; the Zener diode is a child device inside a parent device and cannot be individually replaced. Selecting No means you will be told to replace the parent of a failing device. Can be Yes or No. No instructs IPG not to write a test for the Zener diode. Agilent Technologies 2001 Test Development Tools 6-22

136 7 CAMCAD Professional CAMCAD Professional is one of the fastest and most accurate CAD translation tools on the market. It offers a product that is easy to use while providing higher value at a lower cost than the leading competitor. Fast - CAMCAD Professional has been tested and proven to import and export a 19-megabyte file four times faster than the leading competitor. Easy to use - CAMCAD Professional is more intuitive and requires a shorter learning curve for first-time CAD translators. Accurate - CAMCAD Professional is optimized for all Agilent Automated X-ray Inspection (AXI), In-circuit Inspection (ICT), and Automated Optical Inspection (AOI) products. Best Value - CAMCAD Professional offers a complete tool set for a lower cost, as well as, additional options not available from the leading competitor. NOTE For more information about CAMCAD Professional, see igent_test/camcad/demo.asp. Agilent Technologies 2002 Test Development Tools 7-1

137 8 Agilent Fixture Consultant In this chapter... Introduction, 8-2 Getting Started, 8-3 Fixture Graphics, 8-4 Objectives When you finish reading this chapter, you should be able to: Start Agilent Fixture Consultant Start Agilent Fixture Graphics Describe their general features (you can find detailed information about Fixture Consultant in online help). easy because many of the features of the graphical display and the forms are similar. NOTE Because extensive online help is available, this chapter provides only the information needed to understand and begin using the software package. If you are not already familiar with features of the user interface such as the mouse, windows, menus, online help, and the terminology associated with them see Chapter 1, Using a Workstation in Board Test Fundamentals for more information. Prerequisites This chapter provides a reference description of Fixture Consultant. See Chapter 1, Test and Fixture Development in Test & Fixture Development for information about using Fixture Consultant during board test development. If you are familiar with using Agilent Board Consultant, using Fixture Consultant is Agilent Technologies 2001 Test Development Tools 8-1

138 Chapter 8: Agilent Fixture Consultant Introduction Fixture Consultant is a software tool that aids you in customizing your board test fixture. Fixture Consultant can greatly reduce the amount of time spent verifying and regenerating fixturing information in the test development process. It helps you identify and correct problems before building or modifying the test fixture. With Fixture Consultant, you can: Graphically represent the board on the test fixture. Thus, you can visualize the board s actual location on the fixture, identify blocked resources, and examine wiring information. Control board placement by rotating and moving the board s position in the graphical view. Change probe locations, unblock testhead resources, and customize the wiring of fixture elements. Use the convenient mouse- or keyboard-driven forms to enter wiring, brc, and probe attributes. Add fixture electronics. If you need to customize your fixture, such as connecting a load resistor to nodes on the board, you can add fixture nodes and specify wiring connections to them. This information is later listed in the fixturing reports so the fixture builder can correctly wire the circuit. Access extensive online help. Agilent Technologies 2001 Test Development Tools 8-2

139 Chapter 8: Agilent Fixture Consultant Getting Started Starting Agilent Fixture Consultant To start Fixture Consultant, either: Click the 3070 Programs icon on the Front Panel, then click the Fixture Consultant icon. Right-mouse click in the desktop background to display the Work menu and click Fixture Consultant from the menu options. Type fixture consultant on the BT-BASIC command line. Choose the Run Fixture Consultant option from the Programs menu in IPG Test Consultant. While running IPG Test Consultant s test development steps interactively, you can run Fixture Consultant at the Generate Initial Fixture Files and Generate Final Fixture Files and Reports steps. Quitting Fixture Consultant You can exit Fixture Consultant by selecting File, then Exit from the menu bar of Fixture Consultant s main graphical display. Agilent Technologies 2001 Test Development Tools 8-3

140 Chapter 8: Agilent Fixture Consultant Fixture Graphics If desired, you can use BT-BASIC to programmatically invoke a read-only version (which does not allow saving changes) of Fixture Consultant. When used by itself, this feature is called Fixture Graphics. The capability to change nodes, probes, pins and wires is also disabled. Fixture Graphics lets you view and selectively highlight any of the following: Nodes Devices Pins Probes Keepouts BRCs Alternates BT-BASIC Statements for Fixture Graphics Entering fixture graphics from a BT-BASIC window or within the testplan lets you invoke the graphical display. Table 8-1 lists the BT-BASIC statements associated with Fixture Graphics. Table 8-1 BT-BASIC statements Term fixture graphics fixture graphics end Definition Invokes a read-only version of Fixture Consultant used to graphically display features of the fixture. Terminates Fixture Graphics. Using Fixture Graphics An example of using Fixture Graphics within a testplan might look like Example 8-1. Agilent Technologies 2001 Test Development Tools 8-4

141 Chapter 8: Agilent Fixture Consultant Example 8-1! Beginning of the testplan fixture graphics sub Preshorts subend fixture graphics end... Agilent Technologies 2001 Test Development Tools 8-5

142 9 Board Test Grader, Test Coverage, & Coverage Analyst In this chapter... Board Test Grader Overview, 9-2 Running Board Test Grader, 9-5 information on Coverage Analyst, see Coverage Analyst on page Troubleshooting, 9-9 Board Test Grader Files, 9-13 Test Coverage, 9-23 Coverage Analyst, 9-29 Objectives When you finish reading this chapter, you should know how to use: Board Test Grader, which detects and reports in-circuit and functional tests that are unstable or marginal, allowing you to modify and repair them. Test Coverage, which helps you determine how completely your board is tested. It reports any untested devices. For information on Test Coverage, see Test Coverage on page Coverage Analyst, which helps you investigate the coverage result and determine the best use of your time to improve coverage and understand why a certain coverage value was created. For Agilent Technologies 2001 Test Development Tools 9-1

143 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Board Test Grader Overview Run Board Test Grader after you have completed and debugged your tests. Board Test Grader uses one known-good board to run its grading routines. The utility relies upon statistical analysis and multiple test executions to determine marginal tests. Board Test Grader results are written to report files that you can print to your local printer. Each test category creates its own report file. A summary report file summarizes the results of all of the categories. You can use the reports to keep a permanent record of your board test performance (for comparison with future tests, for fixture and test maintenance). You also can use these reports as acceptance criteria for releasing or accepting a board development project. Test Types The Board Test Grader evaluates the following types of 3070 tests: Pins Shorts Preshorts Analog in-circuit tests Digital in-circuit tests Digital functional tests Analog functional tests Limitations Board Test Grader: Does not support tests with variables in Basic (common on mixed tests, especially Agilent TestJet Tests). Does not support Agilent Polarity Check tests. Always requires a.discharge test, even if one wasn t written automatically. Grading Methods For each of these test types, at least one of the following grading methods determines the quality and stability of your tests: Vacuum Off (all test types). The tests are run with the vacuum off. Any test that passes is flagged in the report as failing. This method simulates the test's ability to find missing components. Agilent Technologies 2001 Test Development Tools 9-2

144 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst CAUTION The Vacuum Off grading process of Board Test Grader may generate false results for tests utilizing 4-6 wire measurements implemented with 4-6 probes, specifically multiple probes for the I and B busses. Board Test Grader incorrectly identifies the device as untested. Quality Preshorts and Analog tests: Preshorts and analog in-circuit tests are executed a specified number of times (default is 10 times). Tests are analyzed for their measured value and its closeness to the programmed threshold. Other analog tests are evaluated for their mean value and coefficient of producibility. Tests whose values fall out of a specified range are flagged as marginal. Any test that fails is flagged as failing. The mean of the measurements should fall into the center section of the test limits; the default is 66.67% (+/- 2 standard deviation). This test represents a hypothesis test. 95% of all measurements should fall within +/- 2 standard deviation if they are generated from the test with the mean centered between the two limits. Therefore, any mean outside the +/- 2 standard deviation limit has only a 5% probability of stemming from the test. This suggests further examination of the test is necessary. The coefficient of producibility is calculated from the equation: cp = mean - closer limit 3*standard deviation and should exceed the specified value (default is 10; you can change the default in config.bdg). Shorts test: The shorts evaluation generates four new shorts files. The original thresholds and settling delays are modified both up and down by a specified percentage (default is 10%) to simulate testhead-to-testhead variation. The tests are flagged as failures if they do not pass. Pins, digital, functional tests: The tests are run repeatedly for a specified number of times (default is 10 times). Tests are flagged as failures if they do not pass all repetitions. Power Supply Sensitivity (all powered tests) The digital in-circuit, digital functional, and analog functional tests are executed with lower and higher power supply voltages (default is +/- Agilent Technologies 2001 Test Development Tools 9-3

145 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst 5%) to simulate a test's sensitivity to power supply variation. The tests are flagged as failing if they do not pass all repetitions (default number of repetitions is 1). Speed Sensitivity (all powered tests) The digital in-circuit, digital functional, and analog functional tests are run with slower and faster vector cycle, receive delay (default is +/- 10%) and event times (except for sync-to-clock tests, which are not tested). The tests are flagged as failing if they do not pass all repetitions (default number of repetitions is 1). Logic Level Sensitivity (all powered tests) The digital in-circuit, digital functional, and analog functional tests are run with modified logic levels to simulate marginal tests (default is +/- 10%): Drive high is decreased. Drive low is increased. Receive high is increased. Receive low is decreased. The tests are flagged as failing if they do not pass all repetitions (default number of repetitions is 1). Fault Coverage (all powered tests) The digital in-circuit, digital functional, and analog functional tests are run with drivers and receivers in modified states to determine the pin fault coverage of the VCL/PCF tests. The four cases tested are drive level stuck high, drive level stuck low, driver floating, and receiver disconnected. A report on the pin fault coverage of the tests is generated. Agilent Technologies 2001 Test Development Tools 9-4

146 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Running Board Test Grader Refer to your preferred method of running Board Test Grader: Running Board Test Grader in Pushbutton Debug. Running Board Test Grader in a BT-BASIC Window on page 9-7. Re-running Board Test Grader on page 9-8. Prerequisites for Pre-B Board Tests Before you use Board Test Grader on a pre-b board directory, you must follow these steps: 1 Update the debug macros. Execute the following statement in the board directory before you run Pushbutton Debug: generate debug macros If you have custom macros in your local board directory, executing this statement may overwrite them. You may want to back up your custom macros, then apply the customizations to the new macros. 2 Update the testplan file. In the testplan file, move the vacuum well statement into the Initialize_Board_Constants subroutine. For example: sub Initialize_Board_Constants global Board$,Board_Rev$ Board$ = "roy" Board_rev$ = ""!vacuum well stmt goes here (if req d) vacuum well a is 2,3 subend Running Board Test Grader in Pushbutton Debug To run Board Test Grader from Pushbutton Debug: 1 Start Board Test Grader. a Click Macros in the Pushbutton Debug menu bar. b Click Test Grader Macros. Board Test Grader macro commands are Generate Test Coverage Report, Create Grading Config, Create Grading Testplan, and Grade Tests. Agilent Technologies 2001 Test Development Tools 9-5

147 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst NOTE The first macro, Generate Test Coverage Report, is a separate program from Board Test Grader and is described in Test Coverage on page Create a config.bdg file. Click on Create Grading Config. 3 Modify the config.bdg file. If you do not edit config.bdg, default values are used and all tests and grading methods are run. If you do not want a test type to run, you must specify test type = False. For example, if you want to test every test type except digital quality test, you would change the variable associated with digital quality test to False: Digital_Quality_Test = True changes to: Digital_Quality_Test = False When Board Test Grader runs, it omits the digital quality test commands in testplan.bdg. It also does not create a report file associated with digital quality tests. The comments in config.bdg help you edit the file. A listing of the default config.bdg file is shown in config.bdg on page Generate the Board Test Grader testplan. Click on Create Grading Testplan. The testplan is created from your original testplan and the config.bdg file. It contains the BT-BASIC commands to grade your in-circuit and functional tests. NOTE Do not edit config.bdg after testplan.bdg is created. If you need to edit config.bdg, create a new testplan.bdg. 5 Run the Board Test Grader testplan. Click on Grade Tests. This grades the tests specified in config.bdg and creates the grading reports in the /<board_directory>/bdg_data directory. 6 Print the report files. Agilent Technologies 2001 Test Development Tools 9-6

148 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Running Board Test Grader in a BT-BASIC Window This section describes how to run Board Test Grader in a BT-BASIC window. 1 msi to the local board directory. 2 Create a config.bdg file. Enter: grade tests; configuration 3 Modify the config.bdg file. If you do not want a test type to run, you must specify test type = False. For example, if you want to test every test type except digital quality test, you would change the variable associated with digital quality test to False: Digital_Quality_Test = True changes to: Digital_Quality_Test = False When Board Test Grader runs, it omits the digital quality test commands in testplan.bdg. It also does not create a report file associated with digital quality tests. The comments in config.bdg help you edit the file. A listing of the default config.bdg file is shown in config.bdg on page Generate the Board Test Grader testplan. Enter: grade tests; testplan The testplan is created from your original testplan and the config.bdg file. It contains the BT-BASIC commands to grade your in-circuit and functional tests. NOTE Do not edit config.bdg after testplan.bdg is created. If you need to edit config.bdg, create a new testplan.bdg. 5 Run the Board Test Grader testplan. Enter: get testplan.bdg run This grades the tests specified in config.bdg. Agilent Technologies 2001 Test Development Tools 9-7

149 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst 6 Generate the reports. Enter: grade tests; report This creates the grading reports in the /<board_directory>/bdg_data directory. 7 Print the report files. Re-running Board Test Grader If you made modifications to the files, you do not need to recreate them before running Board Test Grader again. Instead: If you modified config.bdg to reflect the tests you want to run or to change test parameters, start at Generate the Board Test Grader testplan. If you modified testplan.bdg to fix test problems, start at step 5, Run the Board Test Grader testplan. Agilent Technologies 2001 Test Development Tools 9-8

150 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Troubleshooting Board Test Grader requires that all test subroutines found in your original testplan (including preshorts, shorts, analog tests, digital tests, digital functional tests, and analog functional tests) meet the following requirements. If the requirements are not met, Board Test Grader might not function properly. (In testplan.bdg, the commands that might cause the following problems are flagged with comments. If necessary, modify testplan.bdg to allow the tests to be graded.) If you are having problems running Board Test Grader, make sure your test environment meets the following requirements. Subroutines may not depend upon other subroutines. No subroutines (except Characterize and Setup_Power_Supplies) can depend on setups in other subroutines. For example, closing a GP relay in preshorts and expecting it to be closed in analog tests is not allowed. Subroutines must be re-executable. The subroutines are run multiple times. A subroutine must be structured so it can run independently of all other subroutines. Individual tests must be re-executable. Each test is run multiple times. A test must be structured so it can run independently of all other tests and subroutines. For example, setting up an external instrument before a specific test might prevent the test from running multiple times. If you have problems with Board Test Grader because of the these requirements, consider rewriting your original testplan to meet these requirements. The files must be in the appropriate format and location. Board Test Grader operates on the assumption that the original testplan and other board directory files are present and are of Agilent 3070 standard format. If this is not the case, Board Test Grader may not function properly. Board Test Grader requires the presence of a.discharge file. This file is required even if the original board development did not require one. If your board directory does not have a.discharge file, see Creating a.discharge File on page Wait statements might be necessary. If the vacuum release time is greater than approximately 2 seconds, consider adding wait statements in testplan.bdg. This allows the fixture to completely finish before the next test begins. The wait can be added to the individual test subroutines in testplan or to the Vacuum_Cycle subroutine. Agilent Technologies 2001 Test Development Tools 9-9

151 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Example Testplan Example 9-1 shows a testplan in an inappropriate format: Example 9-1 sub Digital_Tests test "U1" gpconnect "Node1" to "Node2" test "U2" subend sub Analog_Functional_Tests test "U3" output "Source" ; "Send 1kHz, 0dbm, analog signal to codec)" setup Synchronization to T1 stream! ignore how it's done test "U4" (check bits 9-16 within a 193 bit stream) test "1_second_monostable" subend This testplan has a number of problems: Digital_Tests cannot be executed multiple times. The first time U1 runs with the GP relay open, the second time with the relay closed. The subroutine Analog_Functional_tests depends on Digital_Tests (closing the relay). U4 cannot be run multiple times: the first time it tests bits 9-16, the second time The monostable test cannot be re-run immediately because it requires a one second wait between tests. The following changes in Example 9-2 make the testplan gradable: Agilent Technologies 2001 Test Development Tools 9-10

152 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Example 9-2 sub Digital_Tests gpdisconnect "Node1" from "Node2" test "U1" gpconnect "Node1" to "Node2" test "U2" subend sub Analog_Functional_Tests gpconnect "Node1" to "Node2" test "U3" output "Source" ; "Send 1kHz, 0dbm, analog signal to codec)" test "U4_new" (synchronize and check bits 9-16) test "1_second_monostable_wait 1 second in test" subend Creating a.discharge File 1 Create a dummy file. In a BT-BASIC window, change the operating mode to analog. 2 Create the.discharge file. In the workspace, type:! This file is req d by Board Grader disconnect all 3 Save the file. Save the file as.discharge. 4 Compile the.discharge file. 5 Get the wirelist file. You may need to execute a list object wirelist.o over wirelist first. Agilent Technologies 2001 Test Development Tools 9-11

153 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst 6 Add the.discharge field. Add the.discharge field after any general purpose relay or <Other Node> entries. It should appear before any specific nodes are entered. For example: test analog ".discharge" end test 7 Re-save and compile wirelist file. Agilent Technologies 2001 Test Development Tools 9-12

154 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Board Test Grader Files Data Files The data files, listed in Table 9-1, contain information from running testplan.bdg. Most of the data files (with the exception of *_ver_fau.dat) use standard or customized logging commands. Report Files The report files, listed in Table 9-2 on page 9-14, show the number of successful or unsuccessful runs for each test. The Summary Report (summary.rpt) shows which tests require further examination. Examine it before you look at individual report files. Table 9-1 Data files File pins.dat pre_sho.dat sho.dat ana_inc_vac_off.dat ana_inc_qua.dat dig_inc_vac_off.dat dig_inc_qua.dat dig_inc_pow_sup.dat dig_inc_spe.dat dig_inc_ver_fau.dat dig_fun_vac_off.dat Data Pins data Preshorts data Shorts data Analog incircuit vacuum off data Analog incircuit quality data Digital incircuit vacuum off daa Digital incircuit quality data Digital incircuit power supply sensitivity data Digital incircuit speed sensitivity data Digital incircuit verify faults data Digital functional vacuum off data Agilent Technologies 2001 Test Development Tools 9-13

155 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Table 9-1 Data files (continued) File dig_fun_qua.dat dig_fun_pow_sup.dat dig_fun_spe.dat dig_fun_ver_fau.dat ana_fun_vac_off.dat ana_fun_qua.dat ana_fun_pow_sup.dat ana_fun_spe.dat ana_fun_ver_fau.dat Data Digital functional quality data Digital functional power supply sensitivity data Digital functional speed sensitivity data Digital functional verify faults data Analog functional vacuum off data Analog functional quality data Analog functional power supply sensitivity data Analog functional speed sensitivity data Analog functional verify faults data Table 9-2 Report files File pins.rpt pre_sho.rpt sho.rpt ana_inc_vac_off.rpt Data Pins report Preshorts report Shorts report Analog incircuit vacuum off report Agilent Technologies 2001 Test Development Tools 9-14

156 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Table 9-2 Report files (continued) File ana_inc_qua.rpt dig_inc_vac_off.rpt dig_inc_qua.rpt dig_inc_pow_sup.rpt dig_inc_spe.rpt dig_inc_log_lev.rpt dig_inc_fau_cov.rpt dig_fun_vac_off.rpt dig_fun_qua.rpt dig_fun_pow_sup.rpt dig_fun_spe.rpt dig_fun_log_lev.rpt dig_fun_fau_cov.rpt ana_fun_vac_off.rpt ana_fun_qua.rpt ana_fun_pow_sup.rpt ana_fun_spe.rpt Data Analog incircuit quality report Digital incircuit vacuum off report Digital incircuit quality report Digital incircuit power supply sensitivity report Digital incircuit speed sensitivity report Digital incircuit logic level sensitivity report Digital incircuit fault coverage report Digital functional vacuum off report Digital functional quality report Digital functional power supply sensitivity report Digital functional speed sensitivity report Digital functional logic level sensitivity report Digital functional fault coverage report Analog functional vacuum off report Analog functional quality report Analog functional power supply sensitivity report Analog functional speed sensitivity report Agilent Technologies 2001 Test Development Tools 9-15

157 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Table 9-2 Report files (continued) File ana_fun_log_lev.rpt ana_fun_fau_cov.rpt summary.rpt Data Analog functional logic level sensitivity report Analog functional fault coverage report Summary report config.bdg Example 9-3 shows the default config.bdg file. Example 9-3 Data_Dir = bdg_data Cycle_Vacuum = False Board_Serial_Number = Board1 Board_Path =./ Testplan = testplan Testhead = th1 # Name of the directory where BDG puts # data and report files. # Cycle vacuum between test loops: # True or False # Serial Number of the board. This # string is printed on the reports. # Directory containing the board files. # BDG changes directory into this # directory. # Name of the testplan file. BDG uses # this file to generate testplan_bdg. # Name of the testhead. BDG prints this # string on the reports. Agilent Technologies 2001 Test Development Tools 9-16

158 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Sub_Characterize = Characterize # Name of the Characterize # subroutine. Fn_Pins = fnpinsfailed # Name of the Pins # function. Sub_Pre_Shorts = Pre_Shorts # Name of the Pre_shorts # subroutine. Sub_Shorts = Shorts # Name of the Shorts # subroutine. Sub_Analog_Incircuit = Analog_Tests # Name of the Analog # Incircuit subroutine. Sub_Setup_Power_Supplies = Setup_Power_Supplies # Name of the subroutine # to set up the power Sub_Digital_Incircuit = Digital_Tests # Name of the Digital # Incircuit subroutine. Sub_Digital_Functional = Functional_Tests # Name of the Digital # Functional subroutine. Sub_Analog_Functional = Analog_Functional_Tests # Name of the Analog # Functional subroutine. # These commands apply to Pins tests: Pins_Test = True # Run test: True or False. Pins_Executions = 10 # Number of runs of the test. # These commands apply to the Pre-Shorts tests: Pre_Shorts_Test = True # Run test: True or False. Pre_Shorts_Executions = 10 # Number of runs of the test. Pre_Shorts_Report_CPK < # Value of CPK (coefficient of # producibility) used to flag # a test in the report. Pre_Shorts_Report_Mean_Not_Centered=66.67% # The mean a test must be # centered within this value, # or a flag is set in the # report. Pre_Shorts_Report_Closed_Margin = 2.00 # The test threshold - largest # measurement must exceed this # value or a flag is set in # the report. Agilent Technologies 2001 Test Development Tools 9-17

159 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Pre_Shorts_Report_Open_Margin = # The smallest measurement - # test threshold must exceed # this value or a flag is set # in the report. # These commands apply to the Shorts tests: Shorts_Test = True # Run test: True or False. Shorts_Executions = 10 # Number of runs of the test Shorts_Positive_Threshold_Variation = 10.00% # Positive variation of the # threshold. Shorts_Negative_Threshold_Variation = 10.00% # Negative variation of the # threshold. Shorts_Positive_Settling_Delay_Variation = 10% # Positive variation of the Shorts_Negative_Settling_Delay_Variation = 10% # The following commands consist of three parts: # The first part denotes the test subroutine: # Analog Incircuit # Digital Incircuit # Digital Functional # Analog Functional. # The second part denotes the type of test: # Vacuum off # Quality # Power Supply Sensitivity # Speed Sensitivity # Logic Level Sensitivity # Fault Coverage. # settling delay. # Negative variation of the # settling delay. # The third part denotes the test parameters: # _Test Run the Test: True or False. # _Executions Number of times to run the test # _Report CPK Value of CPK used to flag a test in the report # _Mean_Not_Centered The mean a test must be centered within this Agilent Technologies 2001 Test Development Tools 9-18

160 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst # value, or a flag is set in the report. # _Positive_Variation Change in the test parameter by increasing the value. # _Negative_Variation Change in the test parameter by decreasing the value. # These commands apply to the Analog Incircuit tests: Analog_Incircuit_Vacuum_Off_Test = True Analog_Incircuit_Quality_Executions = 10 Analog_Incircuit_Quality_Report_CPK < Analog_Incircuit_Quality_Report_Mean_Not_Centered = 66.67% # These commands apply to the Digital Incircuit tests: Digital_Incircuit_Vacuum_Off_Test = True Digital_Incircuit_Quality_Test = True Digital_Incircuit_Quality_Executions = 10 Digital_Incircuit_Quality_Report_CPK < Digital_Incircuit_Quality_Report_Mean_Not_Centered = 66.67% Digital_Incircuit_Power_Supply_Sensitivity_Test = True Digital_Incircuit_Power_Supply_Sensitivity_Executions = 1 Digital_Incircuit_Power_Supply_Sensitivity_Positive_Variation = 5.00% Digital_Incircuit_Power_Supply_Sensitivity_Negative_Variation = 5.00% Digital_Incircuit_Speed_Sensitivity_Test = True Digital_Incircuit_Speed_Sensitivity_Executions = 1 Digital_Incircuit_Speed_Sensitivity_Positive_Variation = 10.00% Digital_Incircuit_Speed_Sensitivity_Negative_Variation = 10.00% Digital_Incircuit_Logic_Level_Sensitivity_Test = True Digital_Incircuit_Logic_Level_Sensitivity_Executions = 1 Digital_Incircuit_Fault_Coverage_Test = True Digital_Incircuit_Fault_Coverage_Executions = 1 # These commands apply to the Digital Functional tests: Digital_Functional_Vacuum_Off_Test = True Digital_Functional_Quality_Test = True Digital_Functional_Quality_Executions = 10 Digital_Functional_Quality_Report_CPK < Digital_Functional_Quality_Report_Mean_Not_Centered = 66.67% Digital_Functional_Power_Supply_Sensitivity_Test = True Digital_Functional_Power_Supply_Sensitivity_Executions = 1 Agilent Technologies 2001 Test Development Tools 9-19

161 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Digital_Functional_Power_Supply_Sensitivity_Positive_Variation = 5.00% Digital_Functional_Power_Supply_Sensitivity_Negative_Variation = 5.00% Digital_Functional_Speed_Sensitivity_Test = True Digital_Functional_Speed_Sensitivity_Executions = 1 Digital_Functional_Speed_Sensitivity_Positive_Variation = 10.00% Digital_Functional_Speed_Sensitivity_Negative_Variation = 10.00% Digital_Functional_Logic_Level_Sensitivity_Test = True Digital_Functional_Logic_Level_Sensitivity_Executions = 1 Digital_Functional_Fault_Coverage_Test = True Digital_Functional_Fault_Coverage_Executions = 1 # These commands apply to the Analog Functional tests: Analog_Functional_Vacuum_Off_Test = True Analog_Functional_Quality_Test = True Analog_Functional_Quality_Executions = 10 Analog_Functional_Quality_Report_CPK < Analog_Functional_Quality_Report_Mean_Not_Centered = 66.67% Analog_Functional_Power_Supply_Sensitivity_Test = True Analog_Functional_Power_Supply_Sensitivity_Executions = 1 Analog_Functional_Power_Supply_Sensitivity_Positive_Variation = 5.00% Analog_Functional_Power_Supply_Sensitivity_Negative_Variation = 5.00% Analog_Functional_Speed_Sensitivity_Test = True Analog_Functional_Speed_Sensitivity_Executions = 1 Analog_Functional_Speed_Sensitivity_Positive_Variation = 10.00% Analog_Functional_Speed_Sensitivity_Negative_Variation = 10.00% Analog_Functional_Logic_Level_Sensitivity_Test = True Analog_Functional_Logic_Level_Sensitivity_Executions = 1 Analog_Functional_Fault_Coverage_Test = True Analog_Functional_Fault_Coverage_Executions = 1 Agilent Technologies 2001 Test Development Tools 9-20

162 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst testplan.bdg The testplan.bdg file consists of three parts: testmain.bdg. The subroutine call Get_BDG_specifications. This subroutine contains some of the test parameters from the configuration file. The programmer can change these parameters to eliminate tests that have been run successfully. Information from the original testplan. This includes the vacuum well information and all test subroutines. The basic functionality of testmain_bdg is shown in Example 9-4. Example 9-4 call Initialize! initialize variables call Get_BDG_specifications! obtain the test parameters load board testhead is 1 unpowered call Vacuum_well! execute the vacuum well is... call Characterize! learn the small capacitors call Tests! execute all tests The subroutines in testmain_bdg are shown in Example 9-5. Agilent Technologies 2001 Test Development Tools 9-21

163 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Example 9-5 sub Fatal sub Sys_Err sub The_End sub Power_Supply_Failure sub Initialize sub Tests sub Pins_bdg sub Pre_Shorts_bdg sub Shorts_bdg sub Analog_Incircuit sub Test_bdg sub Test sub Prt sub Vacuum sub Vacuum_cycle sub Powered sub Start_log sub Start_report sub End_report sub Start_print sub End_print! call The_End without a system error! call The_End with a system error! print error information, cleanup and stop! call Fatal with the appropriate message! set global variables! call all test subroutines! execute all pins tests! execute all pre_shorts tests! execute all shorts tests! execute all analog incircuit tests! execute all digital incircuit, digital! functional, and analog functional tests! execute one digital incircuit, digital! functional, or analog functional test! print a message to the CRT! control the vacuum! cycle vacuum! execute powered or unpowered! set up data logging! set up the report file! close the report file and copy it to! another file! set up the print file! close the print file and copy it to! another file Agilent Technologies 2001 Test Development Tools 9-22

164 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Test Coverage The Test Coverage report primarily: Measures the actual device test coverage percentage. Describes untested devices. Use Test Coverage after the test is developed for your board and after your fixture is built. You can use it during the test debug phase or anytime later, including after a board is in production. It does not alter any standard files, but simply creates a report. Running Test Coverage Test Coverage requires a complete board directory with all files (including device test objects) and a testplan that functions correctly. You should run Test Coverage from an Pushbutton Debug window. NOTE The first time you run Test Coverage on a board directory, execute the following statement in the board directory before you run Pushbutton Debug: generate debug macros This statement updates the macros in your local board directory. Running Test Coverage on a Standard Testplan To run Test Coverage on a standard testplan: 1 Place your fixture on the testhead. Make sure it is locked. (It is not necessary to have a board on the fixture, because no vacuum is applied.) 2 msi to your board directory. 3 Start Pushbutton Debug. Execute: load board debug board 4 Generate a Test Coverage Report. a From the main menu, click Macros. b Click Test Grader Macros. c Click Generate Test Coverage Report. NOTE To run Test Coverage in a BT-BASIC window, see the syntax and options for the verify device coverage statement in the Syntax Reference. Agilent Technologies 2001 Test Development Tools 9-23

165 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst The Generate Test Coverage Report macro performs the following actions: 1 Creates a new testplan called testplan.cov. The existing testplan file is copied to the file testplan.cov, then is modified to allow testplan.cov to run the tests that measure test coverage accuracy. The modifications: Run all of the device tests (except pins and shorts) without ever applying vacuum or power to the board. Prevent testplan.cov from exiting early due to any test failing. The changes made differ slightly for a panelized vs. standard board. Every line in testplan.cov that is altered is marked with the comment! COVERAGE. 2 Executes the testplan.cov file while reporting all failures to the testcoverage_fail.dat file. For panelized boards, you must specify (via the standard operator interface) which board or boards should be considered in the coverage report. Any number of boards is acceptable by the test coverage tool. However, if more than one board is selected, all devices on these boards are reported within the same report; they are not separated by individual board numbers. Therefore, we recommend you select a single board for a report, then repeat the process for as many other boards as desired. If an error (or break) occurs, the testplan.cov file detects this and prevents a new report from being completed. An error message reminds you that you cannot simply edit testplan.cov that is in the BT-BASIC window. Instead, you must edit the testplan file. (See Running Test Coverage on a Custom Testplan on page 9-25.) 3 Creates the report file, testcoverage.rpt. This is created by comparing devices that failed (in the testcoverage_fail.dat file) to the board topology in board.o. For panelized boards, only the devices on the board(s) selected are considered (as explained in step 2). Any device that has failed is considered tested. (See Interpreting the Test Coverage Report on page 9-26.) 4 Removes the intermediate files testplan.cov and testcoverage_fail.dat. This prevents the directory from becoming cluttered with temporary files. Test Coverage does not alter any standard files in the board directory. You can set up the standard backup options (none, unnumbered, or numbered) in the.hp3070 file using the TestCoverage.BackupLevel: resource if desired. This allows you to automatically back up the testcoverage.rpt file. Agilent Technologies 2001 Test Development Tools 9-24

166 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Running Test Coverage on a Custom Testplan Under normal circumstances, the Generate Test Coverage Report macro performs the steps listed in the previous section and creates a complete testcoverage.rpt report file. However, if a testplan has been heavily customized, the macro may have problems performing the steps successfully. You must make changes to your customized testplan file to allow the macro to run all device tests, then rerun the macro. In some cases, when the macro executes the testplan.cov file an error can occur that prevents all tests from being run and logged in the testcoverage_fail.dat file. In other cases no error occurs, but the report generated is not complete or correct (for example, some test sections may have been skipped, which is not obvious upon a quick inspection). For these reasons, we recommend you perform the following tasks whenever you run this macro for the first time on a board. These tasks change the macro so it does not unlink the failure data file. Then, by examining this file, you can identify which tests have been run. Follow these steps to run Test Coverage on a custom testplan: 1 Generate a Test Coverage Report. a From the main menu, click Macros. b Click Test Grader Macros. c Click Generate Test Coverage Report. 2 Remove all unlink statements. Because you have already run the macro, it is available on the BT_BASIC command line (you may have to break it first if it is running, or use the recall minus key if it is not visible). In the set of commands, delete all unlink statements so that testplan.cov and testcoverage_fail.dat files are not removed. (There is more than one unlink per file. Make sure you remove them all.) 3 Execute the modified macro. Use the execute key, or press Return. This generates a new testplan.cov from the testplan file and runs it. 4 Examine the testcoverage_fail.dat file. If no errors occurred and the testcoverage.rpt report was generated, you can look in this report and in the testcoverage_fail.dat file to see which type of tests were run. Agilent Technologies 2001 Test Development Tools 9-25

167 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst If an error occurred, then you may or may not have a testcoverage_fail.dat to examine. In this case, the BT-BASIC window should indicate the line number within the testplan.cov file on which the error occurred. When fixing errors, remember that they must be made to the original testplan, not to testplan.cov. 5 Make a backup copy of testplan. You use this to restore the original testplan after you are finished running the Test Grader. 6 Edit the testplan file. To correct the execution problems: Look at testplan.cov, testcoverage.rpt, and testcoverage_fail.dat (when present) to determine how you should edit the testplan file. Do not comment out any test statements (except pins and shorts) or the report may not be accurate for these devices. 7 Repeat step 3 through step 6 until you generate a good testcoverage.rpt file. 8 Keep track of the changes you made to the testplan file. When you run Test Coverage in the future, you always want to use the most current testplan. Therefore, we recommend you do not just save a copy of the edited testplan (from step 6), as it may not be up to date the next time you run Test Coverage. For example, if you comment out a test in the new testplan, your old edited testplan does not reflect this. Rather, we recommend you make a note (perhaps in the original testplan) of the lines that need to be edited for Test Coverage. The testplan.cov file contains the Doing_Test_Coverage variable. This variable is set to 1 in testplan.cov. This lets you put branches in your testplan based on this variable (for example, if Doing_Test_Coverage then...). Any variable not set to a value defaults to 0, so your testplan works correctly for normal production board testing. Interpreting the Test Coverage Report The report file testcoverage.rpt is located in the local board directory. It contains a single-page summary section followed by a details section. All devices that are marked as replaceable are considered in the report, except testpoints (defined as single pin connectors marked NT no test in board.o). The replaceable attribute in board.o for a device normally is only a concern for Part Description devices. For example, a resistor pack device may be marked replaceable but each individual resistor tested Agilent Technologies 2001 Test Development Tools 9-26

168 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst may be marked non-replaceable, so only the replaceable devices are considered. Lists of these devices not considered are found at the end of the Details section. Again, for panelized boards, only the board number(s) selected to be tested are considered. The definitions in Table 9-3 help you understand how Device Test Coverage percentages are calculated: Table 9-3 Device test coverage definitions Term Bypass capacitor Parallel tested only devices Tested device Definition Any capacitor with both pins connected to power supply nodes. When devices are tested in parallel: The base device reported as failing is counted as tested. All other devices reported as being in parallel are called parallel tested only and are not counted as tested (unless they fail from a separate test). Any device for which a failure with the exact same name as the device is reported from either a normal test or an Agilent TestJet test (at least one pin is reported as open). If a non-replaceable device is reported as failing, then the failure information for the REPLACE DEVICE: part name is used (assuming it is replaceable). NOTE Agilent Polarity Check failures do not count as tested or untested. In addition, Boundary Scan tests, open jumpers, and switches are counted as untested. Summary Section This section provides fast facts about your board, including the: Device test coverage percentage: Both without and with bypass capacitors. This is the bottom line number. Agilent Technologies 2001 Test Development Tools 9-27

169 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Coverage by device type: For each device type, it lists total devices, untested (or parallel tested only) devices, and percentage tested. This section highlights problems by device type and also itemizes so that all the data is available for report customization. Test coverage summary: A breakdown of untested or tested devices, listed in order of what needs the most attention. Details Section This section provides detailed information about devices in the following categories: Untested devices (no coverage at all; this does not include parallel tested only devices). Lists all untested devices by device type, and the first of the following explanations encountered (if any): Either one or both of: bypass cap with node names listed; indicates it is a bypass capacitor. NT in board indicates it is marked No Test in the board.o topology (for Part Description Library devices it must also have sub-devices (also referred to as children) to be listed. COMMENTED indicates device test statement was found to be commented in the testplan. Also printed is any comment found at the end of the line in the testplan. NOTE: the first test statement encountered is used (except if it is in the characterize subroutine). NO FAIL indicates device test statement was found uncommented in the testplan (yet the device did not fail). Also printed is any comment found at the end of the line in the testplan. NOTE: the first test statement encountered is used (except if it is in the characterize subroutine). NULLTEST in testorder indicates the device was marked nulltest in the testorder file. NT in board only for Part Description Library devices that do not have sub devices (children) and were not listed above. Devices tested in parallel only (except bypass capacitors). Lists devices that do not have their own stand-alone test, but are only reported in parallel with another device. This list does not include bypass capacitors. The failing device name it is in parallel with is also listed. Bypass capacitors tested in parallel only. Lists bypass capacitors tested in parallel only, along with both node names and the failing device name with which it is in parallel. Devices tested by Agilent TestJet only. Lists connectors and pin libraries that are only tested by Agilent TestJet. Agilent Technologies 2001 Test Development Tools 9-28

170 Chapter 9: Board Test Grader, Test Coverage, & Coverage Analyst Coverage Analyst Run Coverage Analyst any time after test generation through the release or delivery of the board test directory into production. Key times to consider running Coverage Analyst would be directly after initial test generation, after test debug prior to running Board Test Grader, and after running Board Test Grader. Coverage Analyst helps you determine how completely your board is tested. It can utilize and report on the data generated by the Board Test Grader process. This process does not require a known-good board, fixture or testhead. Starting Coverage Analyst Click the arrow above the Agilent 3070 icon on the front panel to display the subpanel menu. Then, click the Coverage Analyst icon. Quitting Coverage Analyst Exit Coverage Analyst by selecting Action, then Exit from the menu bar. Exit the generated report by selecting File, then Exit from the menu bar of your browser. NOTE For more information on Coverage Analyst, see the Agilent 3070 Test Program Coverage Analyst Software Documentation which can be accessed from the Help menu of the Coverage Analyst GUI. Agilent Technologies 2001 Test Development Tools 9-29

171 10 Agilent Conversion Tool In this chapter... Running the Conversion Tool, 10-4 Troubleshooting Problems, What the Conversion Tool Does, Post-Conversion File Cleanup, The Agilent Conversion Tool is used to convert the ASCII (American Standard Code for Information Exchange) text files in a board directory for cross-platform compatibility between UNIX and MS Windows operating systems. Text files contained in the boards directory are merged into a single compressed file. The executable files are regenerated by IPG Test Consultant. NOTE The default location for the board directory is $AGILENT3070_ROOT/boards/<BoardName>. The board directory may not be in the default location on your controller. Change the directory path as required where /boards/<boardname> is used in this document. The Conversion Tool is also used to transfer board directories between 3070 controllers with same or different operating systems: UNIX to MS Windows MS Windows to UNIX MS Windows to MS Windows (when board directories are in different path locations on different controllers) See the Advice on page for why UNIX to UNIX transfers are not recommended.) Some post-processing editing will be required if: Libraries are not contained within (local to) the board directory. Other files outside the board directory or $AGILENT3070_ROOT/standard directory are required. Non-standard peripherals not defined in MS Windows have been used in UNIX files or vice versa. Agilent Technologies 2002 Test Development Tools 10-1

172 Chapter 10: Agilent Conversion Tool If post-processing is not needed, Running the Conversion Tool is the only section of this document you will need to read. NOTE VisTA (Visual Test Advisor) functional testplans cannot be converted using the Conversion Tool. An error message will result if you attempt to convert a VisTA board directory. NOTE Resolving issues related to board directory conversion requires 3070 user training and an understanding of the functionality of IPG Test Consultant. It may also require an understanding of the board being converted as well as any customization which has occurred during board development. NOTE For simplicity, the terms directory or subdirectory are used for both UNIX and MS Windows in this chapter. Folder and subfolder could have been used. Objectives When you finish reading this chapter, you should be able to perform the following tasks: Convert a board directory from an UNIX controller to an MS Windows controller. Convert a board directory from an MS Windows controller to an UNIX controller. Move a board directory between MS Windows controllers when the board directories are on different drive letters or paths (for example C:\ to D:\). Locate and resolve issues resulting from differences between UNIX and MS Windows operating systems and 3070 software directory structures. Prerequisites Before you begin using this chapter, you should: Have a board directory that contains a testplan, tests, and appropriate files that have been compiled on software revision pa or later. Be able to run IPG Test Consultant and fix errors. For more information, see Chapter 1, Agilent IPG Test Consultant.. Agilent Technologies 2002 Test Development Tools 10-2

173 Chapter 10: Agilent Conversion Tool Know the locations of board directories on both operating systems. Have enough disk space: Three times the board directory size on the source controller and four times the board directory size on the destination controller. Disk space requirements are verified before execution of the Conversion Tool. Know the remote logins, controller names or IP addresses and passwords of both the source and destination controllers to transfer files to or from your controller via FTP. Required Tools and Materials To accomplish the tasks in this chapter, you will need: A 3070 board test system with a testhead with pa software (UNIX or MS Windows) A functional board directory compiled using pa software (UNIX or MS Windows) Run IPG Test Consultant to completion on the $AGILENT3070_ROOT/boards/class_bd. It will pass IPG Test Consultant after it compiles the libraries, etc. NOTE $AGILENT3070_ROOT/standard/tutorial /class_bd directory will NOT pass IPG Test Consultant until moved to the correct location and IPG Test Consultant is run. You may use IPG Test Consultant, Management, Copy/Move Board Directory, then modify the permissions, if needed. For more information, see Chapter 1, Management Menu. Practicing a Conversion If you want to practice a conversion of the class_bd directory documented in this chapter, you can copy the class_bd with subdirectories from: $AGILENT3070_ROOT/standard/tutorial/class_bd to $AGILENT3070_ROOT/boards/class_bd Agilent Technologies 2002 Test Development Tools 10-3

174 Chapter 10: Agilent Conversion Tool Running the Conversion Tool NOTE Software revision p or newer must be installed and the source board directory must pass IPG Test Consultant before running the Agilent Conversion Tool. The Conversion Tool main screen has the same file menu and buttons in both UNIX and MS Windows; therefore, only one version (UNIX) is shown in this document except where appropriate. The Conversion Tool consists of these functions: Package: Merges and compresses all of the boards/<boardname> directories text files into a single <BoardName>.cvt file that can be copied to another controller and extracted. Transfer: Used to transfer files using FTP (file transfer protocol) to another ftp server-enabled controller. Extract: Extracts (uncompresses) a packaged <BoardName>.cvt file in a platform-dependent manner. Make Interoperable: This function is a combination of Package and Extract. The Make Interoperable function makes a copy of the board directory, takes the runtime test objects and makes them interoperable. It deletes the objects, makes modifications, and recompiles the source files.. This operation is much quicker on MS Windows as the files are modified directly. It also adds the enable common delimiter statement to the board config file. Prepare for ECO: Takes an interoperable board directory, flips the source text files, and modifies the raw files in preparation for an ECO. View Log: Used to view resulting log files or other text files. Abort: Aborts the Package or Extract process before it has completed. For more details what the Conversion Tool is doing, see a summary of the differences between the two operating systems described in the section Relevant Differences Between UNIX and MS Windows Operating Systems on page NOTE The Conversion Tool operates in a copy of the board directory. It does NOT modify an existing board directory during Package, Make Interoperable, or Prepare for ECO. During Extract, if a board directory of the same name exists, it can replace the board directory after prompting the user for approval. Agilent Technologies 2002 Test Development Tools 10-4

175 Chapter 10: Agilent Conversion Tool ADVICE To streamline board directory conversion, you may want to use the IPG Test Consultant Management, Clean Up Board Directory, Mark to remove unneeded backup files. NOTE Binary files are not packaged or converted. (<filename>.o, etc.) They are recreated during the Extract process. Click the Conversion Tool icon on the MS Windows desktop. Click Start, Programs, Agilent3070, Conversion Tool In a BT-BASIC Window, type execute ctool.ksh & (Not case sensitive and is run in the background) In a Korn Shell window, type ctool.ksh & (Not case sensitive and is run in the background) The Agilent Conversion Tool main screen, shown in Figure 10-1 on page 10-6, will start. Start the Conversion Tool In the UNIX environment, there are several ways to start the Conversion Tool: From a user1 login, on the Agilent3070 Programs popup list, click Agilent Conversion Tool. In a BT-BASIC Window, type execute ctool.ksh & (Case sensitive and is run in the background) In Shell Window, type ctool.ksh & (Case sensitive and is run in the background) In the MS Windows environment, there are also several ways to start the Conversion Tool: Agilent Technologies 2002 Test Development Tools 10-5

176 Chapter 10: Agilent Conversion Tool Figure 10-1 Agilent Conversion Tool Main Screen Agilent Technologies 2002 Test Development Tools 10-6

177 Chapter 10: Agilent Conversion Tool Package Locate the Board Directory 1 Select the package function from the File menu, Package, or by clicking the Package button. The package process defaults to the $AGILENT3070_ROOT/boards directory. The Package screen, shown in Figure 10-2 on page 10-9, will appear. The factory default location for board directories is: UNIX: /var/hp3070/boards MS Windows: C:/Agilent3070/boards As described in Navigation on page 10-8, you can use this screen to locate../boards/<boardname> directories. In this example, the <BoardName> in the boards directory is class_bd. This is a board directory used for training in the Agilent 3070 training class. A backup directory called <BoardName>.migration_backup/<BoardName> is created by the Conversion Tool. NOTE There is not a Conversion Tool batch mode available because IPG Test Consultant should be run during the conversion process and IPG Test Consultant is not a batch mode tool. NOTE In the testplan file, user modifications to the testplan are preserved. Path names and file names are modified to be operating system specific NOTE Do NOT run the Conversion Tool against a copy of your board directory with a different board name. For example, don t copy <BoardName> to <NewBoardName>. The board name of the /boards/<boardname> is referenced in the fixture/fixture file and is used during IPG Test Consultant program execution. If a fixture.o exists, IPG Test consultant does not compile the /fixture/fixture file and create a new fixture.o file. The Conversion Tool will use the $AGILENT3070_ROOT environment variable when converting board directories. Agilent Technologies 2002 Test Development Tools 10-7

178 Chapter 10: Agilent Conversion Tool Navigation Select the board directory containing the <BoardName> you want to package. Notice the navigation buttons at the top of the Package screen. Their operation is similar to the MS Windows file manager. Their functions are: Look in: Lists the subdirectories to the root. Allows you to navigate to any mounted volumes in UNIX and any drive letters, mapped or physical, in MS Windows. Up One Level - Goes up one subdirectory level Home - Goes to Home Directory. This may be on a different drive or mounted volume. New Folder - Creates a new subdirectory in the current directory called New Folder in MS Windows and NewFolder in UNIX. List - Not functional Details - Not functional NOTE Do NOT select anything except a directory which contains board files and directories. If you do, a Warning message will result which says This does not appear to be a valid board directory, continue? Normally, click Cancel. Any directory can be packaged, but if the board directory does not compile with IPG Test Consultant, Extract results will also not compile. 2 Select the <BoardName> subdirectory. Click Package. The Run IPG Test Consultant dialog box shown in Figure 10-3 will be displayed. To rename this folder in UNIX use the mv NewFolder <BoardName> command and in MS Windows use the File Manager Rename command. NOTE Spaces in file or directory names in board directories are not allowed. Agilent Technologies 2002 Test Development Tools 10-8

179 Chapter 10: Agilent Conversion Tool Figure 10-2 Select the boards/<boardname> subdirectory Agilent Technologies 2002 Test Development Tools 10-9

180 Chapter 10: Agilent Conversion Tool Figure 10-3 Run IPG Test Consultant? which describes how to run the Conversion Tool without running IPG Test Consultant during packaging. No - Do Not Run IPG Test Consultant If you are confident that the board directory will pass IPG Test Consultant, click No. If you click No, a second dialog box indicating that there may be IPG Test Consultant regeneration problems, and the board may not build correctly on the destination system will appear as shown in Figure Check Board Directory Status? Even if you have run IPG Test Consultant using software revision pa, it is recommended that you allow IPG Test Consultant to do a check of the../boards/<boardname> status before the packaging. Yes - Run IPG Test Consultant Figure 10-4 Are you sure you don t want to run IPG Test Consultant? If you click Yes, a subdirectory in the board directory <BoardName>.migration_backup/<BoardName> will be created and a copy of the <BoardName> will be copied into it. Copying large board directories and files can take several minutes. Be patient. Packaging will begin and Agilent IPG Test Consultant screens will be displayed. If you clicked Yes, go to How to Run IPG Test Consultant on page Skip the following section, Select Yes to continue or No to stop the Conversion Tool. If you select Yes: A temporary subdirectory in the board directory migration_directory will be created and a copy of the <BoardName> will be copied into it. Agilent Technologies 2002 Test Development Tools 10-10

181 Chapter 10: Agilent Conversion Tool Because packaging a large board directory and files can take several minutes, a dialog box indicating the need for patience will appear. The dialog box will go away when copying is complete. A progress dialog box will appear. While the progress bar is displayed, you can Abort. If you abort packaging, you must start packaging from the beginning. When packaging is complete, the <BoardName>.cvt file will be written in the directory one level up from the../<boardname> being packaged. In the default file structure, this will be the /boards directory. If a <BoardName>.cvt file with the same name exists, you will need to approve removing and replacing it. If you say No, packaging will stop. You will need to remove the previous <BoardName>.cvt file manually. When packaging is complete, the location and board name dialog box will be displayed as shown in Figure The Conversion Tool will also display information about the package process, and show when the board packaging was completed, with a time stamp, as shown in Figure 10-6 on page Figure 10-5 Packaged board file location and name Agilent Technologies 2002 Test Development Tools 10-11

182 . Chapter 10: Agilent Conversion Tool Figure 10-6 Package complete screen Packaging without running IPG Test Consultant is complete; go to Transfer on page How to Run IPG Test Consultant When running the Conversion Tool, it will be interactive. You will need to navigate in IPG Test Agilent Technologies 2002 Test Development Tools 10-12

183 Chapter 10: Agilent Conversion Tool Consultant to the directory where the../<boardname> resides. See Chapter 1, Agilent IPG Test Consultant, for navigation information. NOTE Package will always run against a copy of the boards/<boardname> directory. Because the directory name for the board is referenced by IPG Test Consultant, an interim directory is created called: <BoardName>.migration_backup Contained in the <BoardName>.migration_backup directory will be the <BoardName> subdirectory. 3 IPG Test Consultant will check the status of the board directory. You may have to bring the IPG Test Consultant screen to the front to view the IPG Test Consultant Messages screen. Verify the board directory doesn t have errors. As shown in Figure 10-9 on page 10-16, the result should be: *** NO ACTIONS WERE PERFORMED BY IPG TEST CONSULTANT *** 4 Close Agilent IPG Test Consultant by selecting File, Exit. Go to step 5 page Select the $AGILENT3070_ROOT/boards /<BoardName>.migration_backup/<BoardName> directory, as shown in Figure 10-7 on page For the class_bd example, select /var/hp3070/boards/class_bd.migration_back up/class_bd/ Select Actions, Develop Board Test. 2 Do a Comprehensive Regeneration as shown in Figure 10-8 on page Select Actions, Begin Batch Development. Agilent Technologies 2002 Test Development Tools 10-13

184 Chapter 10: Agilent Conversion Tool Figure 10-7 IPG Test Consultant - Develop Board Test Agilent Technologies 2002 Test Development Tools 10-14

185 Chapter 10: Agilent Conversion Tool Figure 10-8 IPG Test Consultant - Batch Development Agilent Technologies 2002 Test Development Tools 10-15

186 Chapter 10: Agilent Conversion Tool Figure 10-9 IPG Test Consultant - Packaging a board without errors Agilent Technologies 2002 Test Development Tools 10-16

187 Chapter 10: Agilent Conversion Tool 5 If IPG Test Consultant returned errors or performed any compiles, the package result probably has problems as described in Figure You can review the results of the packaging process in the <BoardName>_package.log file. See View Log on page 10-34, for more information on how to review the <BoardName>_package.log file. Figure Package Results - continue or fix errors? If there are IPG Test Consultant compiles or other errors, it is strongly recommended that IPG Test Consultant be run again on the original board directory. Click No. Then fix the problems before running Package again. If there were no compiles or other errors, click Yes; packaging will begin. Several dialog boxes will appear: Because copying large board directories and files can take several minutes, a dialog box indicating the need for patience will appear. The dialog box will go away when copying is complete. A progress dialog box will appear. While the Progress bar is displayed, you can Abort. If you abort Packaging, you must start Packaging from the beginning. When Packaging is complete, the <BoardName>.cvt file will be written in the directory one level up from the /<BoardName> directory being packaged. When the default directory paths are used, this will be the /boards directory. Agilent Technologies 2002 Test Development Tools 10-17

188 Chapter 10: Agilent Conversion Tool If a <BoardName>.cvt file with the same name exists, you will need to approve removing and replacing it. If you say No, packaging will stop. You will need to remove the previous <BoardName>.cvt file. When packaging is complete, the location and board name dialog box will be displayed, as shown in Figure The Agilent Conversion Tool will also display information about the package process, and show when the board packaging was completed, with a time stamp, as shown in Figure 10-6 on page described in Relevant Differences Between UNIX and MS Windows Operating Systems on page Figure Package board location and name The <BoardName>.cvt file is a compressed file containing all of the../<boardname> directories text files. It has the same contents whether created from an UNIX or an MS Windows operating system. The Extract function will make the operating systemdependent changes required to address the differences Agilent Technologies 2002 Test Development Tools 10-18

189 Chapter 10: Agilent Conversion Tool Transfer Transfer is used to transfer <BoardName>.cvt files to another 3070 controller with the FTP Server enabled. NOTE You can Extract the <BoardName>.cvt file in the board directory on the originating system, but it will overwrite the existing /<BoardName> directory. If you choose to do that, you may want to make a backup of the boards/<boardname> files and directories in another location. A warning message is displayed before the original board directory is removed. ADVICE Using the Conversion Tool can be especially useful for transferring files between MS Windows controllers where the 3070 software is on different hard drives or board directory paths. If a development controller has the MS Windows pa or later software on one drive C:/Agilent3070 and a production system has it on another drive, for example D:/Agilent3070, the Extract function has the capability of determining where the 3070 software is loaded, using the $AGILENT3070_ROOT environment variable, and extracting correct file paths. The compressed <BoardName>.cvt file can be transferred to another UNIX or MS Windows 2000 controller and extracted (uncompressed) on that system. FTP server functionality is enabled on the MS Windows 2000 controllers as configured from Agilent. FTP, in UNIX or MS Windows, requires a password on the destination system. Anonymous FTP is not enabled on either UNIX or MS Windows 2000, as configured from the factory. Agilent Technologies 2002 Test Development Tools 10-19

190 Chapter 10: Agilent Conversion Tool Transfer Files to a Controller with the FTP Server Enabled (UNIX or Windows 2000) To transfer a file: 1 Select File, Transfer or click Transfer. 2 Navigate to the board directory. 3 Highlight the desired <BoardName>.cvt file, as shown in Figure Figure Select the <BoardName>.cvt file for transfer Agilent Technologies 2002 Test Development Tools 10-20

191 Chapter 10: Agilent Conversion Tool 4 Click FTP. The FTP dialog box, shown in Figure on page 10-21, will be displayed. a Fill in the User Name, and User Password. Passwords must be established on the destination controller. b Fill in the FTP Host field. If the FTP Host in a different domain, the domain name will be required. The FTP Host IP address may be used. c Fill in the FTP Host path. The environment variable will not work with FTP. d Select either the: Default UNIX Path Default Windows path or enter your board directory path. The default UNIX path is /var/hp3070/boards/ and the default Windows path is /Agilent3070/boards/. Click Help for more path information. e Click Put File. Figure FTP login dialog box 5 When the data transfer is complete, the FTP session will log out of the destination controller. An error message will be displayed if transfer errors occur. If transfer errors occur, contact your system administrator. Agilent Technologies 2002 Test Development Tools 10-21

192 Chapter 10: Agilent Conversion Tool Transfer Files to a Controller without the FTP Server Enabled CAUTION <BoardName>.cvt files must be transferred in binary (not ASCII) format. If you transfer the <BoardName>.cvt file using another method other than the Conversion Tool Transfer, and the Extract on the destination controller fails because of a checksum error or a tar error occurs, try another transfer method. MS Windows controllers without the FTP server enabled have command line file transfer protocol (ftp) as part of their operating system software. FTP is also included as part of the Korn Shell software in the pa or later software. MS Windows systems without the FTP server enabled can use FTP get to move files from and FTP put to move files to an UNIX system. For more information, in Windows Explorer, select Help, Help Topics, type ftp and click ftp utility. Alternatives for moving files from UNIX to MS Windows without FTP the server enabled include: Using the FTP get command on the destination MS Windows machine to pull the file from the UNIX controller. Using a 3rd party software package on the MS Windows machine (Reflection FTP, Hummingbird software, etc.). With MS Windows 2000, FTP can be enabled. Creating a DAT tape on the UNIX machine and restoring it on the MS Windows machine or vice versa. A DAT tape drive is included on the MS Windows controller in a 3070 testhead. Alternatives for moving files between MS Windows controllers without the FTP server enabled include: Using the FTP put command on the source machine to an interim UNIX machine, then using the FTP get command on the destination MS Windows machine to pull the file. Using network file sharing, i.e., Windows Explorer, Tools, Map Network Drive. Using hardware solutions including DAT tape, zip disks, CDs, etc. Sending files as a mail file attachment (verify that the file size is acceptable) ADVICE <BoardName>.cvt files can be very large. Choose how to transfer them carefully and always use binary format. Agilent Technologies 2002 Test Development Tools 10-22

193 Chapter 10: Agilent Conversion Tool Extract The <BoardName>.cvt file created by the Package program is operating system-independent. That is the reason the program may be used to transfer files bidirectionally between UNIX and MS Windows, as between MS Windows Systems, as well as between UNIX systems. The Extract function on the destination system makes the changes needed to resolve the differences described in the section Relevant Differences Between UNIX and MS Windows Operating Systems. CAUTION If you have renamed the <BoardName>.cvt file or changed the name during the FTP process the Extract will fail. An example of renaming a file is class_bd.cvt vs. Class_bd.cvt. This is because the compressed file preserves the actual <BoardName> including uppercase and lowercase. NOTE Successful automated conversion assumes that default locations for various elements, files, and directories have been adhered to by board development programmers. If modifications to these elements have occurred, converting the files will require more manual intervention. The Conversion Tool compiles in two stages: 1 Compiles that are designed to preserve existing board and fixture data. These compiles are always done and any errors from these compiles will appear in the Conversion Tool window, shown in Figure on page NOTE Any compile errors that occur during the 1st stage will adversely affect 2nd stage compiles. If a BT-BASIC window doesn't close that indicates a compile error; fix the problem before continuing. 2 When the step 1 compiles are done, IPG Test Consultant is started and will handle all of the other compiling. IPG Test Consultant will report errors from the compiles it is responsible for. Agilent Technologies 2002 Test Development Tools 10-23

194 Chapter 10: Agilent Conversion Tool NOTE All Extract compiles MUST run correctly, or have the errors corrected during the Extract, for the board directory conversion to be successful. NOTE In the testplan file, user modifications to the testplan are preserved. Path names and file names are modified to be operating system specific Run Extract 1 Click Extract on the Agilent 3070 Conversion Tool main screen, shown in Figure 10-1 on page Select the desired <BoardName>.cvt, as shown in Figure on page 10-25, on the destination system. As described in the section Navigation on page 10-8, you can use the select screen to locate and select packaged <BoardName>.cvt files. The file named <BoardName>.cvt should have been placed in the board directory, one level above the <BoardName> directory to be extracted. For example, the class_bd.cvt file, when extracted will create a subdirectory called class_bd in the /boards subdirectory. Agilent Technologies 2002 Test Development Tools 10-24

195 Chapter 10: Agilent Conversion Tool Figure Select the <BoardName>.cvt file Agilent Technologies 2002 Test Development Tools 10-25

196 Chapter 10: Agilent Conversion Tool 3 Click Extract. Because uncompressing large board directories and files can take several minutes, a dialog box indicating the need for patience will appear. The dialog box will go away when uncompressing is complete. A progress dialog box will appear. While the Progress bar is displayed, you can Abort. If you abort the Extract, you must restart the Extract function from the beginning. If a non-supported board is found in the../boards/<boardname>/config file, a Warning message shown in Figure is displayed. See Cards in the Testhead, Chapter 3, System Configuration, or Chapter 5, Configuration Reference for additional information about required hardware configurations for UNIX and MS Windows 3070 systems. NOTE The required boards need to be installed or the config file corrected to match existing required hardware. Figure ControlXT Card Warning 4 The Agilent IPG Test Consultant main screen, shown in Figure on page will be displayed. Navigate to the directory where your board files reside, normally boards/<boardname>. Select Actions, Develop Board Test. 5 The IPG Test Consultant Comprehensive Regeneration screen, shown in Figure on page will be displayed. Verify that you are in the correct directory. Select Actions, Begin Batch Development. If you desire, you may select Begin Interactive Development and go through each section. An IPG Test Consultant Message window will display the results of IPG Test Consultant, while sending information to the summary file in the boards/<boardname> directory. Agilent Technologies 2002 Test Development Tools 10-26

197 Chapter 10: Agilent Conversion Tool CAUTION If a BT-BASIC Windows does not close during the Extract process, an error has been found during one of the compiles that may cause the board directory conversion to fail. Using BT-BASIC, locate and fix the error(s) before continuing the Extract Figure Restore the testorder file When IPG Test Consultant is complete, a message ========Ending test generation=========== will be the last message. You may have to move the IPG Test Consultant screen to see it. 6 Close IPG Test Consultant by selecting File, Exit. 7 The user will be prompted to restore the original testorder file, as shown in Figure on page The programmer may have modified the default testorder on the source system, and the modified testorder should be preserved. The original testorder has been modified by Conversion Tool; all tests are marked permanent. You will almost always want to restore the original. Select Yes. If you select No, there is a testorder.bak file that you can mv or rename to restore the original test order. 8 When Extract is complete, the location and board name dialog box will be displayed, as shown in Figure Select OK. When Extract is complete, the <BoardName> directory will be written in the directory one level down from the subdirectory where the <BoardName>.cvt is located. The default location is the /boards subdirectory. The Agilent Conversion Tool will also display information about the Extract process, and show when the board directory extraction was completed, with a time stamp, as shown in Figure on page Agilent Technologies 2002 Test Development Tools 10-27

198 Chapter 10: Agilent Conversion Tool Figure Extracted (converted) board location and name 9 A file named conversion.log will be created in the <BoardName> subdirectory. For example, the../boards/class_bd directory, when converted, will have a file called conversion.log. 10 Go to View Log on page Agilent Technologies 2002 Test Development Tools 10-28

199 Chapter 10: Agilent Conversion Tool Figure Extract - Develop Board Test Agilent Technologies 2002 Test Development Tools 10-29

200 Chapter 10: Agilent Conversion Tool Figure Extract - Begin Batch Development Agilent Technologies 2002 Test Development Tools 10-30

201 Chapter 10: Agilent Conversion Tool Figure Extract results screen Agilent Technologies 2002 Test Development Tools 10-31

202 Chapter 10: Agilent Conversion Tool Make Interoperable To make a board directory interoperable, 1 Select the Make Interoperable function from the Interoperability menu. 2 Browse and highlight the board directory. Select the Interop function key. 3 You will be prompted to check the board directory status with IPG Test Consultant. Select YES as recommended (shown in Figure 9-21.) 4 A copy of the board directory will be created with the file name <board_name>_interop. If you select NO, jump to Step 6. If you select NO and the Make Interoperable function has errors, you must use IPG Test Consultant to proceed. 5 Use IPG Test Consultant to confirm that the copied board directory is developed without errors. 6 Use IPG Test Consultant to complete the operation by confirming board development and recompiling the objects. When finished, you will see the Note in Figure 9-22 stating that conversion is complete. The note will indicate the location of the interoperable board directory with the file extension <board_name>_interop. Figure Step 3: Check board directory status?. Figure Conversion Complete Note with file path Agilent Technologies 2002 Test Development Tools 10-32

203 Chapter 10: Agilent Conversion Tool Prepare for ECO The Prepare for ECO function takes an interoperable board directory and: flips the source text files, and modifies the raw files in preparation for an ECO. NOTE The board directory must be interoperable in order to perform the Prepare for ECO function. To use Prepare for ECO: 1 Select the Prepare for ECO function from the File menu, Interoperability. 2 Browse to an interoperable board directory and double click on it. Select the board you wish to prepare. 3 Select the Prepare function key. This will create a new board directory with the file extension <board_name>_eco. 4 The Agilent Conversion Tool window will show the status of the preparation. The status will complete with an indication that the board has been prepared successfully. Agilent Technologies 2002 Test Development Tools 10-33

204 Chapter 10: Agilent Conversion Tool View Log The View Log button may be used to view text files on the system. Multiple files may be opened simultaneously. Select the desired file, as shown in Figure on page Two *.log files are created by the Conversion Tool. <BoardName>_package.log one level above the board directory. conversion.log in the <BoardName> directory. The conversion.log has all of the information from the <BoardName>_package.log plus the information from the Extract process appended at the end. 2 To view the <BoardName>.cvt file, select Files of type: (.cvt) one level above the board directory. 3 To view other file types, select Files of type: All Files (*.*) in the <BoardName> directory. Of particular interest to understanding the conversion results are: summary and summary~ (a summary and summary backup of the IPG Test Consultant actions). testplan (UNIX and MS Windows) and testplan.diff (on UNIX) NOTE It is recommend that all other text files be reviewed using BT-BASIC. NOTE <BoardName>.cvt files created on MS Windows controllers are ASCII text, and can be opened and searched for troubleshooting purposes in a text editor. <BoardName>.cvt files created on UNIX are compressed TAR files and will need to be uncompressed before they can be used for troubleshooting purposes. Agilent Technologies 2002 Test Development Tools 10-34

205 Chapter 10: Agilent Conversion Tool Figure View Log Agilent Technologies 2002 Test Development Tools 10-35

206 Chapter 10: Agilent Conversion Tool NOTE The Text Editor opened by View Log is operating system-dependent. UNIX: Text Editor MS Windows: Notepad As shown in Figure on page 10-37, the conversion.log contains a listing of the directories which were extracted, and the binary (*.o, etc.) files which were not converted. These binary files are recreated during IPG Test Consultant execution on the destination system. There is also information about: Symbolic links Illegal file names Duplicate file names that would be caused by MS Windows (testorder and Testorder is legal on UX, but will cause overwriting of files on MS Windows). Non-default paths. For example, /user/home/<hpuxuser> Changes to file names with the old path names commented (!) above the new path names Agilent Technologies 2002 Test Development Tools 10-36

207 Chapter 10: Agilent Conversion Tool Figure View log: (UNIX Text Editor) Agilent Technologies 2002 Test Development Tools 10-37

208 Chapter 10: Agilent Conversion Tool Troubleshooting Problems The Agilent Conversion Tool, ctool.ksh, uses a Perl script to convert the ASCII (American Standard Code for Information Exchange) text files in the../boards/<boardname> directory for cross-platform compatibility. NOTE IPG Test Consultant using pa or later software must run correctly on the source system as a first step in troubleshooting. If the source file is not correct, the converted file will not function correctly. NOTE VisTA (Visual Test Advisor) functional testplans cannot be converted using the Conversion Tool. An error message will result if you attempt to convert a VisTA board directory. General NOTE Successful automated conversion assumes that default locations for various elements, files, and directories have been adhered to by board development programmers. If modifications to these elements have occurred, converting the files will require more manual intervention. NOTE Resolving issues related to boards/<boardname> conversion requires 3070 user training and an understanding of the functionality of IPG Test Consultant. It may also require an understanding of the board being converted, as well as any customization which has occurred during board development. Review the Relevant Differences Between UNIX and MS Windows Operating Systems on page 10-43, and keep them in mind as problems are addressed. Because of the complexity of some boards, and the flexibility of the Agilent 3070 software, not all conversion problems can be addressed by the Conversion Tool software. Agilent Technologies 2002 Test Development Tools 10-38

209 Chapter 10: Agilent Conversion Tool NOTE <BoardName>.cvt files created on MS Windows controllers are ASCII text, and can be opened and searched for troubleshooting purposes in a text editor. <BoardName>.cvt files created on UNIX are compressed TAR files and will need to be uncompressed before they can be used for troubleshooting purposes. CAUTION Do NOT attempt to edit <BoardName>.cvt files and re-extract. Verify that duplicate file names, except for case (capitalization) in the UNIX system, are not causing problems. Try Extract first and if there are errors, examine the conversion logs. As a last resort, look through the board directory looking for file, file1, file2, etc.. You might also try opening the <BoardName>.cvt file on the destination system using a text editor and doing a wild card search for file names ending in *1*, *2*, etc. to locate potential name changes. You may also be able to determine from the file name or directory you are viewing which other files need modified. On the original UNIX system, change the source system file names to have unique file names without using case sensitivity, and verify that IPG Test Consultant compiles files correctly. Search for /dev/* files in the <BoardName>.cvt file that have meaning in UNIX, but are not applicable to MS Windows. Resolve them by pointing to a standard peripherals on the MS Windows controller. Startup Scripts not found during ctool.ksh and IPG Test Consultant execution will display an Error dialog box showing the file name and expected path, as shown in Figure on page They can occur in two situations: During startup when the Conversion Tool looks for IPG Test Consultant, Perl and migrate.pl. If they are not found and the user cannot find the files the Conversion Tool exits. Locate the file either on the 3070 MS Windows CD, or on the UNIX system, and put it in the location displayed in the dialog box. Agilent Technologies 2002 Test Development Tools 10-39

210 Chapter 10: Agilent Conversion Tool You may try reinstalling the software, or you can call your Agilent service and support representative. Figure Startup - missing files Transfer Confirm login, password, hostname or IP address, and path on the destination system. Verify that FTP works correctly from the Korn Shell or Unix Shell window using command line FTP commands. Verify that the FTP server is enabled on the destination MS Windows 2000 controller. See you System Administrator. Extract Package Watch for errors in package complete screen, shown in Figure 10-6 on page 10-12). Fix the source of the errors. Review the../boards/<boardname> /_package.log on the source system, looking for errors or path names that may give clues to problem. Review the../boards/<boardname> /conversion.log on the destination system, looking for errors or path names that may give clues to problem. Carefully review the IPG Test Consultant errors in the summary file. They errors may give a clue about the source of problems. If a compiler message indicates it cannot find files, then Confirm the location of the libraries in the boards/<boardname> under Library Options exists and the path is correct. Agilent Technologies 2002 Test Development Tools 10-40

211 Chapter 10: Agilent Conversion Tool Confirm that the missing files were on the SOURCE system and they are in the expected location, including: wirelist or wirelist.o If there is a wirelist.o but no wirelist, try the following command in BT-BASIC: list object wirelist.o over wirelist fixture/fixture or fixture/fixture.o If there is a fixture.o but no fixture, try the following command in BT-BASIC: list object fixture.o over fixture config board testorder testplan Library paths The make_local_lib program may be used to move external library files into the boards subdirectory. This contrib utility searches the library paths defined in the board file and copies the library sources and objects to a local directory called library. Its location is: UNIX: /opt/hp3070/contrib/bin/make_local_lib MS Windows: c:/agilent3070/contrib/bin/make_local_lib.exe NOTE Contrib programs are used at the customers own risk. Agilent assumes no liability for their use. necessary libraries and any other necessary files Verify paths to custom libraries outside the boards/<boardname> subdirectory are hard coded properly in the appropriate files. The libraries in the board directory and $AGILENT3070_ROOT/standard directory should work without problems. Agilent Technologies 2002 Test Development Tools 10-41

212 Chapter 10: Agilent Conversion Tool What the Conversion Tool Does NOTE VisTA (Visual Test Advisor) functional testplans cannot be converted using the Conversion Tool. An error message will result if you attempt to convert a VisTA board directory. NOTE If IPG Test Consultant has compile problems during the packaging or extraction process, *.o files may not be created, and the board testplan may not execute properly. Each board directory must be converted individually. NOTE If a board directory has not run through IPG Test Consultant with software revision pa or later, it may not convert correctly. Run IPG Test Consultant on the source system board directory before attempting conversion. NOTE Attempting batch mode processing of multiple board files, including running IPG Test Consultant will cause problems. NOTE Successful automated conversion assumes that default locations for various elements, files, custom libraries, and directories have been used by board development programmers. If modifications to these elements have occurred, converting the files will require more manual intervention. Agilent Technologies 2002 Test Development Tools 10-42

213 Chapter 10: Agilent Conversion Tool Relevant Differences Between UNIX and MS Windows Operating Systems The operating system where the packaged file is extracted determines the characteristics of the boards/<boardname> files. Several differences between the operating systems make the Conversion Tool necessary. Each of these differences is explained in more detail in the following sections. Differences include: Board Directory Paths File Names Device Driver Methods (Peripherals) Board Directory Paths On UNIX the paths cannot be changed during the software installation. On MS Windows, the path can be changed during software installation. In UNIX and MS Windows, the installation path is stored in the environment variable $AGILENT3070_ROOT. Environment Variable Beginning with 3070 software revision 04.00pa, the environment variable $AGILENT3070_ROOT is used to enhance portability between UNIX, MS Windows, and between MS Windows systems with the software on different drives. For more information about environment variables, see the Administering Agilent 3070 Systems (Unix), The Root Directory Environment Variable. The default values of the $AGILENT3070_ROOT on factory software loads are: UNIX: AGILENT3070_ROOT = /var/hp3070 MS Windows: AGILENT3070_ROOT = C:/Agilent3070 On UNIX controllers /hp3070 is aliased to /var/hp3070, so they are the same path. The software that was in /opt/... in UNIX, on MS Windows, when using the default MS Windows setup, is directly under the <value in $AGILENT3070_ROOT>. When users load the 3070 software on the MS Windows OS, the user may change the directory path where the software is installed during the installation process. That user selected, non-default directory path, is stored in the $AGILENT3070_ROOT environment variable. That makes using the environment variable in source files, not hard coding path, critical to having portable board directories. Agilent Technologies 2002 Test Development Tools 10-43

214 Chapter 10: Agilent Conversion Tool The Conversion Tool comments the original line containing /var/hp3070 and /hp3070 and replaces it with a line containing the environment variable $AGILENT3070_ROOT in text files under the boards directory. An exception is the BT-BASIC testplans, described below. Program Language and Hard Coded Paths BT-BASIC testplans use the environment variable with the btgetenv$ ( AGILENT3070_ROOT ) & /PathName statement. This allows testplans created on an MS Windows controller or an UNIX controller, which have been converted, to normally run without modification on either operating system. Text source files created using program languages other than BT-BASIC may require editing before running IPG Test Consultant if files external to the board directory are needed by the program. Library files which are in default locations are converted without problems. These program languages are: VCL (Vector Control Language) ATL (Analog Test Language) STL (Serial Test Language) ITL (InterconnectPlus Test Language) BSDL (Boundary-Scan Description Language) As part of program development in VCL, ATL, STL, ITL and BDSL languages, hard coded path names may have been used in the source files. NOTE Normally the needed subdirectories are immediately below the board directory and are converted correctly; however, this programming practice may not have been followed by all board programmers. If so, you will need to hard code these paths after conversion or move the external files into the board directory. If non-standard paths are detected by the Conversion Tool, the file name, the line number and path will be in the conversion.log. After conversion, search for!ctool in the board directory to locate occurrences of non-standard paths. Where non-standard hardcoded paths exist, such as in the setup.avi and setup.avi+pvi files, example paths for both UNIX and MS Windows may be in the /standard/... /... example files. Syntax examples where paths may be hard coded can be located by searching for file id, file name or directory name in the online User manuals. Agilent Technologies 2002 Test Development Tools 10-44

215 Chapter 10: Agilent Conversion Tool Front-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 to a 3070 application, and use a back-slash (\) for MS Windows operating system-related commands. If a command line containing a file path fails to execute, it may be because the slash used is of the wrong type. Reversing the slash(es) may resolve the issue. This is because: Many Korn shell commands are used in this Windows NT environment, and require front-slashes (/) in command lines containing file paths. In Windows NT, when opening a file from the Start, Run... menu, both front-slashes (/) and back-slashes (\) are recognized. A command may be performed in or with some relationship to the MS-DOS environment, which can require back-slashes in command lines containing file paths. File Names Uppercase / Lowercase Sensitivity File names and path names in UNIX are case-sensitive. For example, files or directories class_bd and Class_Bd are different files or directories in UNIX. When transferred to MS Windows, they would overwrite one another, with the contents being the last one copied or moved. MS Windows preserves the uppercase and lowercase (capitalization) letters in file and directory names, both in names created in and transferred to MS Windows, but does not use the uppercase/lower case letters. It may be useful to understand which case (capitalization) a file name or directory name occurs first in a file. Both Korn Shell and Command Prompt windows will display the uppercase/lowercase letters. NOTE To view the case (capitalization) on the MS Windows system use the Korn Shell (Start, Programs, Agilent3070, Korn Shell). The Command Prompt (MS DOS) window will also display the case but its use is not recommended. The Conversion Tool treats identically spelled file names as follows: UNIX first occurrence of class_bd = MS Windows class_bd UNIX 2nd occurrence of Class_BD = MS Windows Class_BD1. Agilent Technologies 2002 Test Development Tools 10-45

216 Chapter 10: Agilent Conversion Tool UNIX 3rd occurrence of Class_bd = MS Windows Class_bd2 CAUTION Each file is treated by itself, as if other files did not contain the same unique name differentiated only by case. File names usage in files in the same /<BoardName> subdirectory may not occur in the same order, therefore causing unexpected errors. ADVICE Unique file and directory names should be created on the UNIX system, excluding case sensitivity, and any files that reference the unique names modified. IPG Test Consultant should be run on the UNIX system prior to running the Conversion Tool. Colon (:) and (%) Character UNIX allows the : (colon) character in file and directory path names. It is an illegal character in a file or path name in MS Windows. The following programs in UNIX use the : (colon) character as a part of there program generation process: PanelTest and Throughput Multiplier (Uses 1:r3, 2:r3, etc. to differentiate which module is being used to test the DUT. See Chapter 1, Multiple-Board Tests & Fixtures, for more details. Libraries defined as part descriptions use : (colon) in the device file name. (See Chapter 7, Flash OBP Programming Steps, for examples. When the Conversion Tool packages a board directory illegal file names are renamed with the _@_ (underscore(at)underscore) character string. During Extract, the destination operating system determines what character replaces the _@_ characters as follows: In the <BoardName>.cvt file 2:r3 becomes 2_@_r3. During extract: UNIX: 2:r3 MS Windows: 2%r3 If you have created file names containing a % sign, this may cause some confusion, but will compile on either system. For example: UNIX original file name = /var/hp3070/boards/test:%failure After moving it back to UNIX this would become $AGILENT3070_ROOT/boards/Test::failure After conversion to MS Windows this name would become $AGILENT3070_ROOT/boards/Test%%failure. Agilent Technologies 2002 Test Development Tools 10-46

217 Chapter 10: Agilent Conversion Tool ADVICE It is recommend that file names or path names containing % signs, or : (colon) not be used in either the UNIX or MS Windows environment. Spaces and Underscores File names containing spaces must not be used in either the UNIX or MS Windows environment. They may result in an error message during ITG Test Consultant execution, and will generate an error message when the Conversion Tool detects them. File names with _ (underscore) are valid in both operating systems. For example, class_bd is valid. $AGILENT3070_ROOT/dev/ directory for compatibility reasons. GPIB Devices GPIB device communication is managed by the NutCracker, Enterprise UNIX Development on Windows Software (TM). Some, but not all, of the GPIB devices which were supported in UNIX are available in the pa Windows software release. These GPIB devices, which are shown in Table 10-1 on page 10-48, are in different directory locations on the MS Windows controller. Device Driver Methods (Peripherals) Communication with peripherals (printers, plotters, power supplies, test equipment, etc.) is not the same for UNIX and MS Windows. However, the software used by the 3070 on the MS Windows system emulates the UNIX environment for GPIB devices, greatly simplifying cross-platform peripherals communication. See BT-BASIC Programming, Chapter 5, Addressing the Bus And Bus Devices, for more information about addressing GPIB devices. In MS Windows most devices are managed by the operating system using device drivers. Several devices, (mostly GPIB) have been duplicated in the Agilent Technologies 2002 Test Development Tools 10-47

218 Chapter 10: Agilent Conversion Tool.. Table 10-1 GPIB device names and locations File Name (/dev/...) UNIX MS Windows counter /dev/counter $AGILENT3070_ROOT/dev/counter dmm /dev/dmm $AGILENT3070_ROOT/dev/dmm dmm_ref /dev/dmm_ref $AGILENT3070_ROOT/dev/dmm_ref gpio1 /dev/gpio1 $AGILENT3070_ROOT/dev/gpio1 hpib1 /dev/hpib1 $AGILENT3070_ROOT/dev/hpib1 hp3488 /dev/hp3488 $AGILENT3070_ROOT/dev/hp3488 null /dev/null $AGILENT3070_ROOT/dev/null ps0 /dev/ps0 $AGILENT3070_ROOT/dev/ps0 ps1 /dev/ps1 $AGILENT3070_ROOT/dev/ps1 ps10 /dev/ps10 $AGILENT3070_ROOT/dev/ps10 ps11 /dev/ps11 $AGILENT3070_ROOT/dev/ps11 ps2 /dev/ps2 $AGILENT3070_ROOT/dev/ps2 ps3 /dev/ps3 $AGILENT3070_ROOT/dev/ps3 ps4 /dev/ps4 $AGILENT3070_ROOT/dev/ps4 ps5 /dev/ps5 $AGILENT3070_ROOT/dev/ps5 ps6 /dev/ps6 $AGILENT3070_ROOT/dev/ps6 Agilent Technologies 2002 Test Development Tools 10-48

219 Chapter 10: Agilent Conversion Tool Table 10-1 GPIB device names and locations (continued) File Name (/dev/...) UNIX MS Windows ps7 /dev/ps7 $AGILENT3070_ROOT/dev/ps7 ps8 /dev/ps8 $AGILENT3070_ROOT/dev/ps8 ps9 /dev/ps9 $AGILENT3070_ROOT/dev/ps9 scope /dev/scope $AGILENT3070_ROOT/dev/scope synth /dev/synth $AGILENT3070_ROOT/dev/synth Agilent Technologies 2002 Test Development Tools 10-49

220 Chapter 10: Agilent Conversion Tool Serial Ports (RS232) On the MS Windows system several RS232 devices which translated within 3070 applications are managed by the NutCracker, Enterprise UNIX Development on Windows Software (TM). The stty option available on UNIX is not supported on MS Windows. Instead, use the BT-BASIC control statements. See BT-BASIC Programming, Chapter 6, RS-232 for more information. These devices do not appear on the $AGILENT3070_ROOT/dev listing but are managed by the MS Windows operating system. The COM serial ports in the MS Windows operating system are also mapped to /dev files as follows: /dev/com/n where n is the COM port number. /dev/com1 and /dev/com2 do not appear in the /dev directory, but are managed by the MS Windows operating system. NOTE The strip printer (rpr1), because it is used in nearly every testplan, is converted by the Conversion Tool. The other input/output devices may require modifications to the testplan. Table 10-2 Input/Output Devices Device type UNIX MS Windows (transparent to user) strip printer /dev/rpr1 /dev/com/2 Serial MUX Box JOT /dev/ttym(xx) where xx is the box and the port /dev/jot_plc /dev/jot_bcr_p0 /dev/jot_bcr_p1 /dev/com/3..10 /dev/com/4 /dev/com/5 /dev/com/6 bar code reader /dev/bcr /dev/com/n (where n is assigned by the user) Agilent Technologies 2002 Test Development Tools 10-50

221 Chapter 10: Agilent Conversion Tool Table 10-2 Input/Output Devices (continued) Device type UNIX MS Windows (transparent to user) tape drive /dev/rmt/0m /dev/rmt0 null /dev/null /dev/null tty /dev/tty /dev/tty console /dev/console /dev/console lp /dev/lp /dev/lp Because the RS232 MUX is a different product on UNIX and MS Windows controllers, the pinouts on the RJ45 connectors on the MS Windows and UNIX serial mux boards are not wired the same. If you are using serial devices, you must change the RJ45 to DB9 or RJ45 to DB25 adapter to match the appropriate RS232 MUX. Table 10-3 RS232 MUX adapters Cable adapter type UNIX Adapter Part Number MS Windows Adapter Part Number RJ45 -> DB9M E E RJ45 -> DB25M E E RJ45 -> DB25F E Not available Agilent Technologies 2002 Test Development Tools 10-51

222 Chapter 10: Agilent Conversion Tool Post-Conversion File Cleanup After the conversion is complete, when the board directory on the destination controller 3070 system is testing Devices Under Test (DUTs), there are several files that can be removed to recover disk space. Source Controller If the source controller is a development controller, the user may choose to keep the board directory for future Engineering Change Order board development. If you are going to keep the <BoardName> directory, you can remove: <BoardName>.cvt <BoardName> package.log /migration_directory(x) if it exists. If problems have occurred, there may be multiple copies as designated by the (x). If no future development for this board directory is going to be done on the source machine, delete: <BoardName> original board directory Destination Controller Files that can be removed include: <BoardName>.cvt /<BoardName>/conversion.log /boards/<boardname>_compress.tar.z(x) if it exists /<BoardName>/tmp_migration_board if it exists Test Consultant Backup Files On both the source and destination controller there are files ending in ~, which are backup files. If disk space is needed, consider whether the backup files are still required. For more information, see Chapter 1, Management Menu. Agilent Technologies 2002 Test Development Tools 10-52

223 11 UNIX and MS Windows Interoperability In this chapter... Interoperability Definition, 11-2 Enabling Interoperability, 11-2 Use of the Agilent Conversion Tool, 11-4 Make Interoperable Function, 11-5 Prepare for ECO Function, 11-5 Copying Board Directories, 11-5 Compatible Objects, 11-6 UNIX and MS Windows Interoperability Matrix, 11-7 The Common Delimiter Character, 11-9 The Enable Common Delimiter Statement, 11-9 UNIX & MS Windows Servers, Interoperability Use Models, Objectives After reading this chapter, you should be able to: Develop interoperable runtime tests for both UNIX and MS Windows platforms, How to use the common delimiter (%), How to use the enable common delimiter statement in the board config file, When to use the Agilent Conversion Tool for interoperability, How to process Engineering Change Orders (ECOs) for interoperability between UNIX and MS Windows test systems. Prerequisites You must be familiar with Agilent 3070 board test development processes before developing interoperable tests. Test and Fixture Development Agilent Conversion Tool Agilent Technologies 2002, 2003 Test Development Tools /2003

224 Chapter 11: UNIX and MS Windows Interoperability Interoperability Definition Interoperability is defined as the ability to run a board on either a MS Windows or UNIX controlled testhead without concern for the system on which it was developed. Specifically it is the ability to run developed tests on testheads running either UNIX or MS Windows operating systems. NOTE Since Interoperability is a new feature, interoperable tests are not backward compatible with software revisions prior to p. Board tests developed on software revision p or newer will not run on testheads using older software revisions. ADVICE Target the desired operating system before beginning test development. If developing on UNIX with the potential for tests to run on MS Windows, test development should be completed after enabling interoperability. Enabling Interoperability Before beginning board test development, reference Table 11-1 on page 11-3 to help you decide how and when to develop for interoperability Beginning with software release p, MS Windows test development is always interoperable. If developing on UNIX, you may choose to develop for interoperability. If you choose not to develop for interoperability on UNIX, runtime tests will only run on UNIX. One exception is if your boards are not panelized and do not have part libraries - these will run on MS Windows without conversion. If the decision is made to not develop for interoperability, the Agilent Conversion Tool can be utilized to make the tests interoperable. Agilent Technologies 2002, 2003 Test Development Tools 11-2

225 Chapter 11: UNIX and MS Windows Interoperability Table Test Development Decision Matrix I have a board from: I am Targeting: How I get there UNIX software releases B through p UNIX at software release p or later MS Windows pre-software release p MS Windows at software release p or later UNIX only Interoperable on UNIX and MS Windows Interoperable on UNIX or MS Windows Interoperable on UNIX or MS Windows Interoperable on UNIX or MS Windows Upgrade to or later. The enable common delimiter statement in board config file is optional. Do not use it if you intend to use the board on pre- B release systems. Update to or newer. Use Make Interoperable command in Agilent Conversion Tool. Add enable common delimiter statement to board config file Upgrade to or later. Use Make Interoperable command in Agilent Conversion Tool. All MS Windows systems will be interoperable. Add enable common delimiter statement in board config file to allow development, e.g. ECOs, on UNIX systems; the Prepare for ECO function will also be needed then. Agilent Technologies 2002, 2003 Test Development Tools 11-3

226 Chapter 11: UNIX and MS Windows Interoperability Use of the Agilent Conversion Tool Beginning with software release and newer, board test development on UNIX and MS Windows (testhead runtime objects) is interoperable and will run on testheads with either operating system. Use of the Agilent Conversion Tool is unnecessary. Use of the Agilent Conversion Tool is required to convert objects and text files (non testhead runtime) for: moving board test development files to the other operating system, or Engineering Change Orders (ECOs) to board tests running on testheads using an operating system other than the operating system used for board test development. Non testhead runtime objects include: controller processing, testability reporting, all board test related text files, some data accessing coverage. ADVICE When making a UNIX board interoperable, use the Make Interoperable feature in the Agilent Conversion Tool. Do not attempt conversion manually. You may miss files that require conversion. Engineering Change Orders (ECOs) Test development and ECOs for a given board on either operating system is made simpler with the Agilent Conversion Tool. Utilize the Agilent Conversion Tool to convert the board tests before performing the ECO. See Chapter 5, Performing an ECO NOTE The Agilent Conversion Tool is required for an ECO if the board was developed on an operating system different than the one utilized to complete the ECO. NOTE VISTA communications test software is not supported by the Agilent Conversion Tool Agilent Technologies 2002, 2003 Test Development Tools 11-4

227 Chapter 11: UNIX and MS Windows Interoperability ADVICE Do not edit board test files with shell editors such as vi. These and other text editors do not update the file's header information such as the time-stamp. Only use BT-BASIC to edit the board test files. Make Interoperable Function The Agilent Conversion Tool has two new commands - Make Interoperable and Prepare for ECO. The Make Interoperable function is a combination of Package and Extract. The Make Interoperable function makes a copy of the board directory, takes the runtime test objects and makes them interoperable. It deletes the objects, makes modifications, and recompiles the source files.. This operation is much quicker on MS Windows as the files are modified directly. It also adds the enable common delimiter statement to the board config file. Prepare for ECO Function The Agilent Conversion Tool recognizes that interoperable board runtime objects are compatible between UNIX and MS Windows platforms. The Conversion Tool will not package a board that is interoperable. Source files have different end-of-line characters on the MS Windows platform and UNIX systems. In order to do test development, the source file end-of-line characters must match the development system format. The Prepare for ECO function takes an interoperable board directory, changes the source text file end-of-line characters as needed, and modifies the raw files in preparation for an ECO. This operation is to be done on the platform on which the ECO is to be performed. For additional information on file conversion, please see Chapter 10, Agilent Conversion Tool. Copying Board Directories ADVICE When you copy a board directory from UNIX to MS Windows and vice versa, the board text files need to be converted using the Prepare for ECO function. Otherwise, IPG Test Consultant will generate errors. When using FTP to transfer board directories, only use binary format. If the board directory is not packaged and you utilize smart or ascii ftp, the board object files will be corrupted. Agilent Technologies 2002, 2003 Test Development Tools 11-5

228 Chapter 11: UNIX and MS Windows Interoperability Compatible Objects Runtime object files that will be modified for interoperability include: board.o, board_xy.o, config.o, pins.o, testjet.o, connectcheck.o, safeguard.o, shorts.o, wirelist.o, fixture.o, all test library objects, and all testhead objects (analog, digital...) These objects will be revised to the latest 3070 software revision. NOTE Beginning with software, it is no longer possible to generate test objects that will run on Series I systems using revision A software (A.xx.xx). The or newer software will be able to read objects from revision A software and convert them to the current revision. This change is equivalent to the enable software revision b statement always being included in the config file. Another comment regarding board.o, IPG Test Consultant has a built-in feature that detects when libraries have been moved. In the LIBRARY OPTIONS section a developed board pointing to a library path: C:/Agilent3070/library/ttl or $AGILENT3070_ROOT/library/ttl at compilation time, will have the complete path (resolved path if it included an environment variable) stored in the DEVICES section of the board.o. Regardless of what the library paths were in the former operating system, IPG Test Consultant is looking at the absolute path stored in board.o. If the board file has platform independent library paths (using $AGILENT3070_ROOT or another environment variable) and the system library objects exist, then the board will compile. However, you can indicate IPG Test Agilent Technologies 2002, 2003 Test Development Tools 11-6

229 Chapter 11: UNIX and MS Windows Interoperability Consultant to skip all the steps which will then only update the time stamp in each file to keep everything consistent. UNIX and MS Windows Interoperability Matrix The following matrix illustrates interoperability across platforms with various board files from 3070 software versions. Please see the Interoperability Matrix in Figure 11-1 on page Agilent Technologies 2002, 2003 Test Development Tools 11-7

230 Chapter 11: UNIX and MS Windows Interoperability Figure 11-1 UNIX and MS Windows Interoperability Matrix Platform UNIX WN 3070 SW version part libraries or panel test (: or %) Common Delimiter % Board Directory From: pre pre without with without with without with functionality not applicable functionality unavailable functionality not applicable enabled (%) not enabled (:) functionality not applicable functionality unavailable Board to run on: without with without with without with without with Current UNIX model N/A NOT SUPPORTED N/A N/A Board Conversion required - objects not interoperable. N/A pre N/A Current UNIX model N/A NOT SUPPORTED NOT SUPPORTED N/A Board Conversion required - objects not interoperable. UNIX No conversion. Objects up-revved. Current UNIX model N/A Current UNIX model N/A N/A UNIX cannot read WN objects. Conversion required N/A Agilent Technologies 2002, 2003 Test Development Tools N/A No conversion. Objects up-revved. Current UNIX model N/A No conversion. UNIX reads "%"s. No conversion. UNIX reads ":"s. Board Conversion required - objects not interoperable. N/A NOT SUPPORTED N/A N/A N/A Board Conversion required - objects not interoperable. No conversion. WN reads UNIX objects and uprevs them. N/A N/A Board Conversion required - objects not interoperable. N/A Interoperable N/A NOT SUPPORTED NOT SUPPORTED N/A Current WN model N/A UNIX cannot read WN objects. Conversion required functionality NOT without N/A Interoperable N/A not applicable SUPPORTED NOT with enabled (%) N/A SUPPORTED N/A Configuration not applicable Enable common delimiter means I want interoperability with enabled A board with part libraries or panel test and 'enable common delimiter' (in board config) - uses % with not enableda board with part libraries or panel test and no 'enable common delimiter' (in board config) - uses : (on UNIX only) common delimiter is enabled/disabled at development time - not runtime N/A N/A Objects up-revved and reformatted silently N/A Current WN model N/A NOT SUPPORTED N/A Interoperable N/A pre Interoperable Objects are interoperable except ":"; requires conversion. N/A Objects up-revved and reformatted silently N/A Current WN model N/A NOT SUPPORTED WN N/A Current WN model

231 Chapter 11: UNIX and MS Windows Interoperability The Common Delimiter Character NOTE Interoperability is determined at test development and not at run time. Agilent 3070 software has used the colon (:) and the percent symbol (%) as the delimiter character for panelized boards and parent/child device notation in the part description library on UNIX and MS Windows systems respectively. Beginning with the Agilent p software release, interoperability between UNIX and MS Windows unifies these delimiter characters to a common delimiter - the percent symbol (%). The Enable Common Delimiter Statement NOTE In order to develop interoperable boards, you must utilize a new enable command in the board config file. The enable common delimiter statement allows tests developed on either operating system to use the percent symbol (%) as the delimiter. The percent symbol is recognized on both UNIX and MS Windows operating systems at software release p. UNIX test development software before release p uses the colon (:) as the delimiter. The colon is forbidden in MS Windows file names. If developing or running interoperable board tests, the enable common delimiter statement must be included in the board config file. Example 10-1 shows the use of the enable common delimiter statement in the board config file. See Chapter E, enable (CONFIGURATION) in Syntax Reference for additional information. Example 11-1 Add the enable common delimiter statement to the board config file target hp3073 standard enable express fixturing enable testjet enable paneltest enable common delimiter... If the enable common delimiter statement appears in the board config file, the Agilent Conversion Tool recognizes this and will not perform the package operation on the board files. Agilent Technologies 2002, 2003 Test Development Tools 11-9

232 Chapter 11: UNIX and MS Windows Interoperability UNIX & MS Windows Servers If a server is used to distribute the same board test files to UNIX and MS Windows test systems, a common-platform file sharing server/client must be utilized. NOTE Agilent 3070 software, UNIX, and MS Windows operating systems do not include a common platform file sharing solution. Boards located on a UNIX server can be accessed by MS Windows systems if the SMB/CIFS (Server Message Block/Common Internet File System) protocol is enabled on the UNIX server. This will allow the MS Windows system to access board files from a UNIX server/client. Likewise, a NFS (Network File System) server must be enabled on a MS Windows server so that UNIX systems may mount to the PC to access the board files over a network. For additional information, see Chapter 7, Network Services in Administering Agilent 3070 UNIX Systems. Agilent Technologies 2002, 2003 Test Development Tools 11-10

233 Chapter 11: UNIX and MS Windows Interoperability Interoperability Use Models Operator Use Case The runtime system can utilize either UNIX or MS Windows operating systems. 1 Login as operator to a UNIX or MS Windows test system with p software. 2 Load an interoperable board testplan, 3 Run the testplan. Please refer to the Operator Use Case Diagram Developer Use Case 1 Login to a UNIX or MS Windows test system with p software. 2 Develop the board and testplan. 3 Debug the testplan. 4 Load the board and run the testplan. Please refer to the Developer Use Case Diagram ECO Use Case 1 Login to a UNIX or MS Windows test system with p software. 2 Load a board developed on either a UNIX or MS Windows test system using B or newer software. 3 Utilize the Agilent Conversion Tool to make the board interoperable and prepare if for ECO. 4 Go to the <board_name>_eco directory and perform the ECO modifications. 5 Debug the testplan. Load the board on either a UNIX or MS Windows test system and run the testplan. Please refer to the ECO Use Case Development Model without Conversion This describes the process of choosing a platform and completing all development on that platform with or newer software. Runtime can be achieved on either UNIX or MS Windows without any conversion. 1 Login to the chosen development platform. 2 Develop the board and testplan. 3 Debug the testplan. 4 Load the board and run on any runtime system. Please refer to the Development Model without Conversion Agilent Technologies 2002, 2003 Test Development Tools 11-11

234 Chapter 11: UNIX and MS Windows Interoperability Figure 11-2 Operator Use Case Diagram Agilent Technologies 2002, 2003 Test Development Tools 11-12

235 Chapter 11: UNIX and MS Windows Interoperability Figure 11-3 Developer Use Case Diagram Agilent Technologies 2002, 2003 Test Development Tools 11-13

236 Chapter 11: UNIX and MS Windows Interoperability Figure 11-4 ECO Use Case Agilent Technologies 2002, 2003 Test Development Tools 11-14