Test Development Tools - Abcelectroniquenotes-application.abcelectronique.com/018/18-26773.pdf ·...

© Agilent T i

Con

............................................ 1-1

............................................ 1-1

............................................ 1-1

............................................ 1-2

............................................ 1-2

............................................ 1-3

............................................ 1-3

............................................ 1-3

............................................ 1-4

............................................ 1-5

............................................ 1-6

.......................................... 1-22

............................................ 2-1

............................................ 2-1

............................................ 2-1

............................................ 2-2

............................................ 2-2

............................................ 2-3

............................................ 2-5

............................................ 2-7

echnologies 2001 Test Development Tools

tents Test Development Tools

1 Agilent IPG Test ConsultantIn 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 .................................................................

2 Agilent Board ConsultantIn this chapter...................................................................................

Objectives ..................................................................................Prerequisites...............................................................................Starting Agilent Board Consultant............................................Quitting Board Consultant .........................................................

Features of Board Consultant ..........................................................Features of the Main Form.........................................................Menu Options ............................................................................

© Agilent T ii

Table of C

............................................ 2-8

.......................................... 2-14

.......................................... 2-17

.......................................... 2-24

.......................................... 2-24

.......................................... 2-24

.......................................... 2-24

.......................................... 2-25

.......................................... 2-28

.......................................... 2-28

.......................................... 2-29

.......................................... 2-31

.......................................... 2-31

.......................................... 2-33

.......................................... 2-34

............................................ 3-1

............................................ 3-1

............................................ 3-1

............................................ 3-2

............................................ 3-3

............................................ 3-3

............................................ 3-4

............................................ 3-4

............................................ 3-7

.......................................... 3-12


ontents

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

3 The BT-BASIC EnvironmentIn 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 T iii

Table of C

............................................ 4-1

............................................ 4-1

............................................ 4-1

............................................ 4-4

............................................ 4-4

............................................ 4-5

............................................ 4-5

.......................................... 4-10

.......................................... 4-19

.......................................... 4-21

.......................................... 4-21

.......................................... 4-21

.......................................... 4-21

............................................ 5-1

............................................ 5-1

............................................ 5-2

............................................ 5-3

............................................ 5-3

............................................ 5-3

............................................ 5-4

............................................ 5-4

............................................ 5-5

............................................ 5-6

............................................ 5-7


ontents

4 Agilent Pushbutton DebugIn this chapter...................................................................................


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

5 The Plot GeneratorIn 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 T iv

Table of C

............................................ 5-8

............................................ 5-8

............................................ 5-8

............................................ 5-8

............................................ 5-9

............................................ 5-9

.......................................... 5-10

.......................................... 5-10

.......................................... 5-10

.......................................... 5-10

.......................................... 5-10

............................................ 6-1

............................................ 6-1

............................................ 6-1

............................................ 6-2

............................................ 6-4

............................................ 6-5

............................................ 6-6

............................................ 6-8

............................................ 6-8

............................................ 6-9

.......................................... 6-10

.......................................... 6-11

.......................................... 6-12

.......................................... 6-13

.......................................... 6-14

.......................................... 6-15


ontents

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

6 The Part Description EditorIn this chapter...................................................................................


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 T v

Table of C

.......................................... 6-16

.......................................... 6-17

.......................................... 6-19

.......................................... 6-20

.......................................... 6-21

............................................ 8-1

............................................ 8-1

............................................ 8-1

............................................ 8-2

............................................ 8-3

............................................ 8-3

............................................ 8-3

............................................ 8-4

............................................ 8-4

............................................ 8-4

............................................ 9-1

............................................ 9-1

............................................ 9-2

............................................ 9-2

............................................ 9-2

............................................ 9-2


ontents

Potentiometer Entry Form .........................................................Resistor Entry Form...................................................................Switch Entry Form.....................................................................Transistor Entry Form................................................................Zener Entry Form.......................................................................

7 CAMCAD Professional

8 Agilent Fixture ConsultantIn this chapter...................................................................................


Introduction......................................................................................Getting Started .................................................................................

Starting Agilent Fixture Consultant ..........................................Quitting Fixture Consultant .......................................................

Fixture Graphics ..............................................................................BT-BASIC Statements for Fixture Graphics .............................Using Fixture Graphics ..............................................................

9 Board Test Grader, Test Coverage, & Coverage AnalystIn this chapter...................................................................................

Objectives ..................................................................................Board Test Grader Overview...........................................................

Test Types..................................................................................Limitations .................................................................................Grading Methods .......................................................................

© Agilent T vi

Table of C

............................................ 9-5

............................................ 9-5

............................................ 9-5

............................................ 9-7

............................................ 9-8

............................................ 9-9

.......................................... 9-10

.......................................... 9-11

.......................................... 9-13

.......................................... 9-13

.......................................... 9-13

.......................................... 9-16

.......................................... 9-21

.......................................... 9-23

.......................................... 9-23

.......................................... 9-26

.......................................... 9-29

.......................................... 9-29

.......................................... 9-29

.......................................... 10-1

.......................................... 10-2

.......................................... 10-2

.......................................... 10-3

.......................................... 10-3

.......................................... 10-4

.......................................... 10-5


ontents

Running Board Test Grader .............................................................Prerequisites for Pre-B.01.50 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 ........................................................

10 Agilent Conversion ToolIn this chapter...................................................................................

Objectives ..................................................................................Prerequisites...............................................................................Required Tools and Materials....................................................Practicing a Conversion .............................................................

Running the Conversion Tool..........................................................Start the Conversion Tool ..........................................................

© Agilent T vii

Table of C

.......................................... 10-7

........................................ 10-19

........................................ 10-23

........................................ 10-32

........................................ 10-33

........................................ 10-34

........................................ 10-38

........................................ 10-38

........................................ 10-39

........................................ 10-40

........................................ 10-40

........................................ 10-40

........................................ 10-42ting Systems .................. 10-43........................................ 10-52........................................ 10-52........................................ 10-52........................................ 10-52

.......................................... 11-1

.......................................... 11-1

.......................................... 11-1

.......................................... 11-2

.......................................... 11-2

.......................................... 11-4

.......................................... 11-4


ontents

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 Opera

Post-Conversion File Cleanup .........................................................Source Controller .......................................................................Destination Controller................................................................Test Consultant Backup Files ....................................................

11 UNIX and MS Windows InteroperabilityIn this chapter...................................................................................

Objectives ..................................................................................Prerequisites...............................................................................Interoperability Definition .........................................................Enabling Interoperability ...........................................................

Use of the Agilent Conversion Tool ................................................Engineering Change Orders (ECOs)..........................................

© Agilent T viii

Table of C

.......................................... 11-5

.......................................... 11-5

.......................................... 11-5

.......................................... 11-6

.......................................... 11-7

.......................................... 11-9

.......................................... 11-9

........................................ 11-10

........................................ 11-11

........................................ 11-11

........................................ 11-11

........................................ 11-11

........................................ 11-11


ontents

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 T 1-1

In this led information about this software package vided by online help. This chapter provides he information needed to understand and using the software package.

tesust be familiar with features of the user

ace � such as the mouse, windows, menus, help, and the terminology associated with

hapter 1, Using a Workstation in Board undamentals for more information on the nterface.

hapter 1, Test and Fixture Development in nd Fixture Development for a description of st generation process.

hapter 6, Completing and Debugging Tests t and Fixture Development for a description fixture generation process.

echnologies 2001, 2004 Test Development Tools

1111 Agilent IPG Test Consultant

chapter... � Features of IPG Test Consultant, 1-3

� Developing a Board Test, 1-22

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

NOTEDetaiis proonly tbegin

Prerequisi� You m

interfonlinethem.

NOTESee CTest Fuser i

See CTest athe te

See Cin Tesof the

© Agilent T 1-2

Chapter 1


: Agilent IPG Test Consultant

Starting IPG Test ConsultantStart 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 ConsultantExit IPG Test Consultant by selecting File > Exit from the menu bar.

© Agilent T 1-3

Chapter 1

FeaturTest C

ting the Fixture Format Specify whether re testing more than one board per fixture.

sing Features in the Menu Bar Activate est Consultant�s features by selecting items the menu bar.

se actions is individually described below.

Test Regeneration Behavioreneration behavior affects the way IPG tests when you are running incrementally g the test during debug or because of a Change Order (PCO). Regardless of its hosen setting has no effect on the generation for new board tests. See Table 1-1 for a of the menu choices.

r affected by a change, except for those tests er file.

cept that IPG also updates permanent tests nge. In addition, IPG removes the permanent order file.



es of IPG onsultant

This section describes the main features of the IPG Test Consultant.

The Main FormThe 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.

� Selecyou a

� AccesIPG Tfrom

Each of the

Setting theThe test regregeneratesand updatinProduction value, the cprocedures description

Table 1-1 Test regneration behavior choices

Menu Item Description

Comprehensive Regeneration

IPG regenerates all tests that are changed, othat are marked permanent in the testord

Comprehensive Regeneration; Clear Permanent

Same as Comprehensive Regeneration exthat have been changed or affected by a chakeyword from those tests� entries in the test

© Agilent T 1-4

Chapter 1

hows the files and directories that appear current directory.

path to a board directory

mouse's left button on a directory in the list.

ice is appended to the name of the current . Then the next level in the directory appears in the window. In a similar fashion, append however many entries are needed to desired directory.

ies in the list are terminated with a /, while not. Also, the buttons in which directory d file names appear have a different color so

distinguish one from the other.

ffected by a change, except for those tests that ile.

IPG also updates permanent tests that are removes the permanent keyword from those



Selecting the Working DirectoryThe 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 sunder the

2 Build a

Click the

Your chodirectorystructureyou can reach the

Directorfiles are names anyou can

Limited Regeneration IPG regenerates only tests that are directly aare marked permanent in the testorder f

Limited Regeneration; Clear Permanent

Same as Limited Regeneration except that directly affected by a change. In addition, IPGtests� entries in the testorder file.

Table 1-1 Test regneration behavior choices (continued)


© Agilent T 1-5

Chapter 1

enu item (see Table 1-2).

is menu without making any changes, click ere outside the option menu, for example in drop area.

the fixture directory.

re detailed description of specifying paths mouse, see Selecting the Working y on page 1-4.

e path to the display area.

e path is correct, click on Set Fixture to copy the path to the display area under irectory.

Fixture menu choices

Description

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



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.

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

1 Click a m

To exit thsomewhthe back

2 Specify

For a mowith the Director

3 Copy th

When thDirectoryFixture D

Table 1-2

Menu Item

Single BoarPer Fixture

Multiple Boards PerFixture

© Agilent T 1-6

Chapter 1

enuew/Edit Board Files (>)ew Summary/Details Files (>)ew/Edit Test Files (>)ew/Edit Board Configurationew/Edit Fixture Files (>)ew/Edit Other Filegement Menu

ean Up Board Directory chive Board Directory store Board Directory py/Move Board Directory ams Menun BT-BASICn Agilent Board Consultantn Test Cell Managern Korn shelln Pushbutton Q-STATSn Agilent Boundary-Scann Agilent Advanced Boundary-Scann Setup Test Editorn Part Description Editorn Agilent TestJet Keepouts Generationn Agilent TestJet Drill File Generationn Agilent Fixture 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 BarThe 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 M� Vi� Vi� Vi� Vi� Vi� Vi

� Mana� Cl� Ar� Re� Co

� Progr� Ru� Ru� Ru� Ru� Ru� Ru� Ru� Ru� Ru� Ru� Ru� Ru

© Agilent T 1-7

Chapter 1

nu contains the exit command.

us menu provides access to the main features Consultant and to other software tools. It add new tests.

s menu contains the options shown in Table

es Calculation Formenceis Calculation form appears when you s > Develop Board Test. encies Calculation form lets you select

gin calculating dependencies. Dependencies are used to decide which steps in the test

tool that aids test developers in providing

a board test. If you select this option, IPG Test enu.

lect this option, IPG Test Consultant opens a nto the workspace.



NOTEMost 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 MenuThe File me

Actions MenThe Actionof IPG Testalso lets you

The Action1-3.

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

DependenciThe Dependclick ActionThe Dependwhere to becalculations

Table 1-3 Actions menu options


Enter Board Data Starts Agilent Board Consultant, which is a softwarecorrect data before running IPG Test Consultant.

Develop Board Test Begins the sequence of steps required to generate Consultant displays the Dependencies Calculation M

Add A Test Add a new test to an existing testorder file. If you senew BT-BASIC window and loads the testorder file i

© Agilent T 1-8

Chapter 1

this form's options include the full series of he test development process listed under ependencies Calculation At, only two re selectable here. These options are

d in Table 1-4.

ndencies. Choosing this option causes ning of the Develop Board Test process. If you skip dependencies calculations, select this

u ignore the steps prior to Generate Test ou are:urce files for tests.tion process, such as board placement.ilable. the correct choice!



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.

1 Select an option from the Dependencies Calculation form.

Althoughsteps in tBegin Doptions apresente

2 Make a selection from the Actions menu.

Actions menu options are provided in Table 1-5, below.

Table 1-4 Dependencies calculation options


Compile config File This is the usual starting point for calculating depedependencies calculations to start near the beginare a beginner or not sure why you would want toitem.

Generate Test Requirements Files

Choosing this option as your starting point lets yoRequirements Files. This option can be useful if y� Debugging and the only changes are to the so� Manually running portions of the fixture genera� Doing some steps without having libraries avaSelect this option only if you are confident that it is

© Agilent T 1-9

Chapter 1

ard Test Formp Board Test form appears immediately after encies Calculation form if you choose Begin evelopment. This form guides you through

sequence of steps required to generate a nd the associated fixture reports and files.

le Step Execution there are a list of steps, ose presented in Table 1-6.

h guides you through the normal sequence of the associated fixture reports and files.

arting point was chosen, does all the steps in intervention, verifies the dependencies, and

es the hardware in your system's testhead.



3 Exit the form.

To exit the Dependencies Calculation form and return to the main form without taking any action, click File > Cancel.

Develop BoThe Develothe DependInteractive Dthe normal board test a

Under Singincluding th

Table 1-5 Actions menu options


Begin Interactive Development

Displays the Develop Board Test form, whicsteps required to generate a board test and

Begin Batch Development Calculates dependencies from whichever stthe test development process without user then returns to the main form.

Table 1-6 Single step execution options


Compile config File Compile a configuration file that describ

Compile Library Tests Compile tests in the library directories.

Compile board File Compile the board file.

© Agilent T 1-10

Chapter 1

o ways to use the Develop Board Test form, p and Single Step. Each provides a different

h the series of steps.

ep is the more automatic of the two paths. as an option menu to its left, under Multiple l. If you click Execute All Steps to Stop Mark

Plot Generator program.

o lets you run the Fixture Consultant software t, select probes, or reserve brcs for custom

are, which generates the testplan.

does not automatically generate.

ents for the test.

the Plot Generator program. Also lets you run an make wiring changes, such as modifying

executable (object) files.

pleted.



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 twMultiple Stepath throug

Multiple StEach step hStep Contro

Compile and Plot board_xy File Compile the board_xy file. Also run the

Generate Initial Fixture Files Run the fixture generation software. Alsso you can change the board placemenapplications

Generate Tests Using IPG Run the IPG software.

Generate testplan Run the Testplan Generator (TPG) softw

Create Custom Tests Manually create custom tests which IPG

Generate Test Requirements Files

Extract the hardware resource requirem

Generate Final Fixture Files and Reports

Run the fixture generation software andthe Fixture Consultant software so you cthe wiring for fixture electronics.

Generate Test Object Files Compile the device tests to generate the

Recalculate Dependencies Verify that the steps were correctly com

Table 1-6 Single step execution options (continued)


© Agilent T 1-11

Chapter 1

allowed by the option menus can vary ording to what is required. Steps whose with a question mark � for example, Do? been evaluated yet (and, thus, IPG Test does not know if they need to be done). After een evaluated, the question mark disappears. Consultant evaluates the step and determines ecessary, the step is ignored and marked d.

possible actions are presented in Table 1-7.

ath

o the next step.

ssociated with it but take no action. Then mark updated date/time stamp marks the files as

, the first step that IPG Test Consultant needs t step that needs execution is marked START

rked START & Do.



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.

NOTEA 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 actionsslightly accactions end� have notConsultant they have bIf IPG Test that it is unnNot Require

Some of the

Table 1-7 Possible actions from the Develop Board Test form, Multiple Step p


Do/Do? Do this step. Then mark it as Done and go t

Skip/Skip? Update the date and time stamp on all files ait as Skipped and go to the next step. (Thedeliberately skipped instead of out-of-date.)

START & Do Indicates the current starting point � that isto do. After this step has been done, the nex& Do. You cannot change which step is ma

© Agilent T 1-12

Chapter 1

on your choice of action. Each time a step is the next step to be done is selected ly.

allowed by the option menus can vary ording to what is required. Among the ions are shown in Table 1-8.

erately skips the step.

not be done.

ath

th

several substeps. (Click Expand This Step to

the last step executed can be redone.

mp for files associated with this step. (The erately skipped instead of out-of-date.)



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, clickcompleted, automatical

The actionsslightly accpossible act

START & Skip Indicates the current starting point, but delib

Do & STOP/Do? & STOP Do this step and stop.

Skip & STOP/Skip? & STOP Skip this step and stop.

Not Required Indicates that a step is not required and can

Table 1-7 Possible actions from the Develop Board Test form, Multiple Step p


Table 1-8 Possible actions from the Develop Board Test form, Single Step pa


Do This Step Executes the current step, which may consist of view the components that comprise a step.)

Redo This Step Repeats a step that has already been done. Only

Skip This Step Ignores the step but update the date and time staupdated date/time stamp marks the files as delib

© Agilent T 1-13

Chapter 1

nerate, which tests it should not regenerate, ests should be marked permanent in the file and not regenerated. You can move tests t to another by clicking on them and then the arrow corresponding to the action you . If you wish to manually add a test to the

dd A Test and supply the name of the new

ave finished, click Save followed by Close ur choices and exit this form. If you change click Close without clicking Save.

ted task.

pand This Step have not been evaluated.

step is necessary.

y have not been evaluated. Clicking on this

g IPG under Single Step Execution. This item hich tests IPG regenerates.

l fixturing steps. This item runs Fixture s to the fixture.

th



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 regeand which ttestorder from one lisclicking on wish to takelist, click Atest.

When you hto record yoyour mind,

Expand This Step Shows the statements used to perform the selec

Expanded Information Not Evaluated

Appears when the dependencies required for ExClicking on this step does nothing.

Why Displays a message explaining why the selected

Why Information Not Evaluated

Appears when the dependencies required for Whstep does nothing.

Modify List of Tests to be Generated

Appears when you choose Generate Tests Usindisplays an additional form that lets you specify w

Run Fixture Consultant

Appears when you choose either the initial or finaConsultant so you can interactively make change

Table 1-8 Possible actions from the Develop Board Test form, Single Step pa


© Agilent T 1-14

Chapter 1

ard Files Menuiew/Edit Board Files in the Edit menu lets you modify the board or board_xy files.

dit options open a new BT-BASIC window d the named file into the workspace for

editing.

ary/Details Files Menudit, then View Summary/Details Files lets you summary file produced by IPG Test

or any of the summary or details files IPG or by the fixturing software.

ons in this menu open a new BT-BASIC then load a file into the workspace for

editing. View Test Consultant Summary loads file, and the other options load the named mmary file lists the actions taken during the the Develop Board Test feature in IPG Test

st Files Menudit, then View/Edit Test Files lets you modify many files (including files for device ced during the test generation process.

options in this menu open a new window and then load the named file into



Edit MenuThe 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 BoChoosing Vexamine or

Both View/Eand then loaviewing or

View SummChoosing Eexamine theConsultant produced by

All the optiwindow andviewing or the summaryfile. The sulatest run ofConsultant.

View/Edit TeChoosing Eexamine or tests) produ

Many of theBT-BASIC

© Agilent T 1-15

Chapter 1

order file.

main file.

plan file.

nd move to the digital directory for the selected

nd move to the functional directory for the

e and move to the functional directory for

nd move to the functional directory for the

rts file.

ns file.

and move to the analog directory for the



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


View/Edit �testorder� File

Opens a new BT-BASIC window and gets the test

View/Edit �testmain� File

Opens a new BT-BASIC window and gets the test

View/Edit �testplan� File Opens a new BT-BASIC window and gets the test

View/Edit Digital Tests Opens a new BT-BASIC window in digital mode aboard.

View/Edit Functional Tests

Opens a new BT-BASIC window in digital mode aselected board.

View/Edit Backtrace Files

Opens a new BT-BASIC window in backtrace modthe selected board.

View/Edit States Files Opens a new BT-BASIC window in states mode aselected board.

View/Edit �shorts� Files Opens a new BT-BASIC window and gets the sho

View/Edit �opens� Files Opens a new BT-BASIC window and gets the ope

View/Edit Analog Tests

Opens a new BT-BASIC window in analog mode selected board.

© Agilent T 1-16

Chapter 1

have the ability to modify these files. e recommend that you modify only those View/Edit option.)

ptions in this menu open a new BT-BASIC then load the named file into the workspace or editing.

her Fileis option in the Edit menu starts BT-BASIC, ful for viewing or editing miscellaneous

ich no View/Edit option exists in the menus .

t Menuement menu displays menu options used to the files in a board directory.

and move to the analog directory for the

d move to the mixed directory for the selected



View/Edit CAD Files MenuChoosing 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 ConfigurationChoosing 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 MenuChoosing 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 alwaysHowever, wfiles with a

All of the owindow andfor viewing

View/Edit OtChoosing thwhich is usefiles for whlisted above

ManagemenThe Managmanipulate

View/Edit Powered Analog Tests

Opens a new BT-BASIC window in analog mode selected board.

View/Edit Mixed Signal Tests

Opens a new BT-BASIC window in basic mode anboard.

Table 1-9 View/Edit Test Files menu options (continued)


© Agilent T 1-17

Chapter 1

re more files or directories listed than can fit e window, use the mouse to move the scroll cally to see the entire list.

f the following to mark (highlight) the files ories you wish to clean up:

on individual files (or on a directory).

t all backup files in the current directory by ng Mark All Backup Files.

ng unwanted files or directories.

ry to magnetic tape.

tory stored on magnetic tape by the Archive

its contents.



Your choices here are presented in Table 1-10.

Each of these is individually described below.

Clean Up Board Directory FormIf 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.

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.

If there ainside thbar verti

Do any oor direct

� Click

� Selecclicki

Table 1-10 Management menu options


Clean Up Board Directory Lets you manage a board directory by removi

Archive Board Directory Lets you copy the contents of a board directo

Restore Board Directory Lets you restore the contents of a board direcBoard Directory feature.

Copy/Move Board Directory Lets you copy or move a board directory and

© Agilent T 1-18

Chapter 1

e marked items.

you have marked the appropriate choices, Actions, then Delete Marked Selections.

you are asked to confirm the action, click do the action and return to the main form.

form.

is form without taking any action, click File, cel.

rd Directory Query Boxt Board Management > Archive Board e query box appears. This option lets you ire contents of a board directory to a tape r archival storage.

tape in the tape drive.

the busy light to turn off.

.

ents of the working directory you chose in menu are archived to the tape.



� Select all numbered backup files other than the most recent backup file by clicking Mark All Backups, then .1~.

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 th

a Afterclick

b WhenOK to

6 Exit the

To exit ththen Can

Archive BoaIf you selecDirectory, thsave the entcartridge fo

1 Insert a

Wait for

2 Click OK

The contthe main

3 Exit.

Table 1-11 Mark menu shortcuts

Shortcut Description

Mark All Backup Files

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

Mark All Backups, then 1~

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

Unmark All Selections

Un-select all marked files/directories.

© Agilent T 1-19

Chapter 1

Board Directory Formt Management, then Copy/Move Board form appears that lets you copy or move the nts of a board directory to a different

ve is equivalent to copy followed by delete; urce is copied to the destination and then the e is deleted.

he label above the directory listing.

l above the directory listing is either From y Contents or To Directory Contents to which directory listing is being shown.

e this label between From . . . and To . . ., tions, then Toggle FROM/TO Listing.

a source directory.

e of the source directory, which is the to be copied or moved, appears under From

y.

data entry field or use the mouse to select a from the list.



To exit this query box without taking any action, click Cancel.

Restore Board Directory Query BoxIf 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 If you selecDirectory, aentire contedirectory.

NOTEA mothe sosourc

1 Toggle t

The labeDirectorindicate

To togglselect Ac

2 Specify

The namdirectoryDirector

Edit the directory

© Agilent T 1-20

Chapter 1

is form without taking any action, click File .

enuets you run other test system functions ting IPG Test Consultant.

ontains the items presented in Table 1-12.

pers in providing correct board data before

rovides a shell around the BT-BASIC directly interacting with the programming agement and Miscellaneous Statements

tion about the Test Cell Manager.)

ement software on the 3070.



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.

4 Move (or copy) the directory.

Click either Copy Directory or Move Directory (in the Actions menu) to perform the indicated action.

5 Exit.

To exit th> Cancel

Programs MThis menu lwithout exi

This menu c

Table 1-12 Programs menu options


Run BT-BASIC Start a BT-BASIC session in a new window.

Run Agilent Board Consultant

Run Board Consultant, which aids test develorunning IPG Test Consultant.

Run Test Cell Manager Start the Test Cell Manager program, which penvironment that prevents test operators fromenvironment. (See Chapter 4, Program Manin Board Test Fundamentals for more informa

Run Korn shell Open an Korn shell in a new window.

Run Pushbutton Q-STATS Run Pushbutton Q-STATS, the quality manag

© Agilent T 1-21

Chapter 1

software package that supports the testing of d 1149.1-1990

lps you develop VCL setup-only tests for

to create or modify part description libraries.

at are the precise size and shape for Agilent t possible resources are blocked.

et probes, which is not generated by the fixture

ackage that lets you graphically examine and



Run Agilent Boundary-Scan Run the Boundary-Scan software, which is a digital devices that comply with IEEE Standar

Run Agilent Advanced Boundary-Scan

Run the optional InterconnectPlus software.

Run Setup Test Editor Run Setup Test Editor, a software tool that hecustom digital devices.

Run Part Description Editor Run the Part Description Editor, which is used

Run Agilent TestJet Keepouts Generation

Run software that generates keepout areas thTestJet probes, which ensures that the fewes

Run Agilent TestJet Drill File Generation

Generate drill file information for Agilent TestJgeneration software.

Run Agilent Fixture Consultant

Run Fixture Consultant, which is a software pmodify fixturing information.

Table 1-12 Programs menu options (continued)


© Agilent T 1-22

Chapter 1

DeveloTest

nding upon how you prefer to work, you can ultiple Step, Single Step, or a combination two.

choose batch development, you are pted only when necessary. For example, you vised if there is an action you must take

e IPG Test Consultant can continue.

g the Begin Interactive Development or Begin velopment actions causes IPG Test nt to calculate dependencies. This updates ram's knowledge of your board test and lets what must be done.



ping a Board 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.

Depeuse Mof the

b If youpromare adbefor

ChoosinBatch DeConsultathe progit decide

© Agilent T 1-23

Chapter 1

e directory (main form)

elopment (Action menu inies Calculation form)

late dependencies



Figure 1-1 IPG Test Consultant develops a board test

Set test regeneration behavior, specifyfixture format (main form)

Begin

Choose board directory (main form) Choose fixtur

Enter board data (Action menu inmain form)

Develop board test (Action menu inmain form)

Begin interactive development (Actionmenu in Dependencies Calculation form)

Begin batch devDependenc

CalcuCalculate dependencies

Multiple step (DevelopBoard Test form)

Single step (DevelopBoard Test form)

End

© Agilent T 1-24

Chapter 1



© Agilent T 2-1

In this enient mouse- or keyboard-driven forms for ng and verifying data.

bility to generate a Testability Report for use u and those who design your circuit boards.

sive online help.

led information about this software package vided via online help, which includes m help that provides information about any e that appears on the screen. Because sive online help is available, this chapter des only the information needed to stand and begin using the software package.

tesr 3, Creating Board Information in Test & elopment for information about using Board to develop board tests.

ot already familiar with features of the user e Chapter 1, Using a Workstation in Board entals.


2222 Agilent Board Consultant

chapter... � Features of Board Consultant, 2-3

� Using Board Consultant, 2-24

� The Board Graphics Viewer, 2-31

� The Testability Report, 2-34

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

� Conventeri

� The aby yo

� Exten

NOTEDetaiis proon-itefeaturextenproviunder

PrerequisiSee ChapteFixture DevConsultant

If you are ninterface, seTest Fundam

© Agilent T 2-2

Chapter 2


: Agilent Board Consultant

Starting Agilent Board ConsultantYou 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 ConsultantExit Board Consultant by selecting File, then Exit from the menu bar.

© Agilent T 2-3

Chapter 2

FeaturConsu



es of Board ltant

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 T 2-4

Chapter 2



Figure 2-1 Main Form in Board Consultant

© Agilent T 2-5

Chapter 2

a for notes and status messages, and miscellaneous features.

art and graphical display are described in art on page 2-8 and The Graphical

page 2-14 respectively. The other items are ext.

ar at the top of the form provides access to g menus:

load existing board information, create n also exit Board Consultant from this menu.

ms to examine or enter data that describes the also lets you display the paths to libraries.rms that are organized into groups for

s, the board file, the board_xy file, or the

ch finds a match, it can:at item.



Features of the Main FormThe 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 are� some

The flowchThe FlowchDisplay on described n

Menu BarThe menu bthe followin

Table 2-1 Menu bar options

Menu Description

File Lets you work with the files that store board information. You caninformation for a new board, and save board information. You ca

Tasks Lets you display the X-Y locations on your board and display forphysical and electrical characteristics of your board. This option The Tasks menu provides an alternative method to display the fosequential access via the blocks in the flowchart.

Compile Lets you compile out-of-date library or Agilent SAFEGUARD fileconfig file.

Verify Performs verification to confirm the integrity of your data.

Search Lets you search for a device or a node on your board. If the sear� Display a form that lets you examine or modify the data for th� Highlight that item in the graphical display.

© Agilent T 2-6

Chapter 2

phical display.

contains the board and board_xy files for rm.

sk being processed by Board Consultant. The you to do something.ges color to show the current status: green

the current task.

art. Click the mouse's left button on the or information for that task.

ne time, you can use the scroll bar to move



Options Displays a form that enables you to highlight locations in the gra

Help Provides an overview that describes how to use on-item help.

Table 2-1 Menu bar options (continued)

Menu Description

Table 2-2 Miscellaneous features in the Main Form

Feature Description

Board Directory The name of your working directory, the directory thatyour board, appears in the title bar at the top of the fo

Status Line The status message displays information about the tastatus is Ready when Board Consultant is waiting for Note that the button to the left of the Status label chanmeans ready and yellow means busy.

Notes area An area that displays supplemental information about

View / Edit Physical Board Data Tasks

Lists the tasks associated with this block in the flowchappropriate pushbuttons to invoke the necessary formIf there are too many tasks to view on the screen at othrough the list.

© Agilent T 2-7

Chapter 2

rify Agilent TestJet & Agilent Polarity eck Probe Types (Keepouts/Outlines)rify Node Probing Accessrify Power Node Probing Accessrify Ground Node Probing Accessow Missing Librariesrify Disable Methods Existrify Disabling Nodes Usablerify Tied Nodes Datarify Boundary-Scan Chainsow Devices in Library Directoryow Library for Device Designatorow Library for Part Numberow IPG Device Summaryrify IPG Device Disable Resultsrify Safeguard Inhibit Resultsnerate Testability Reporthr Device . . .r Node . . .n

t Version . . .eate New Version (>)d/Cancel New Versionlete Version



Menu OptionsThe 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 *

� VeCh

� Ve� Ve� Ve� Sh� Ve� Ve� Ve� Ve� Sh� Sh� Sh� Sh� Ve� Ve� Ge

� Searc� Fo� Fo

� Versio� Se� Cr� Ad� De

© Agilent T 2-8

Chapter 2

Flowchart



� Options� Highlight Location Data

* These items appear only if your system has the Agilent TestJet option installed.

The FlowchartThe 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

© Agilent T 2-9

Chapter 2

task, click the pushbutton associated with hen you select a task, Board Consultant appropriate form, verifies the integrity of formation, or begins compiling a file.

escribes a reference list of blocks and any cases, the action corresponds to an

pears below the flowchart, in the list of the current block. Use Table 2-3 to the flowchart�s overall structure, or to find a ion when you are not sure which block that ociated with.

ation Form

Instructions

ry Selection Form

sas

ction Form

s



The Hierarchy of Blocks and ActionsEach 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 that task. Wdisplays thethe board in

Table 2-3 dactions. In mitem that apactions for understand specific actaction is ass

Table 2-3 List of blocks and actions in the Flowchart form

Block Action(s)

Create New Board Invokes a Board Specific

Translate CAD Data Display CAD Translation

Load Existing Board Invokes a Board Directo

View/Edit Panel Data Enter Boards On PanelEnter Panel OutlineEnter Panel Tooling HoleEnter Panel Keepout Are

Board Type Displays the Board Sele

View/Edit Physical Board Data Enter Board OutlineEnter Board Tooling Hole

© Agilent T 2-10

Chapter 2



View/Edit Board Description Enter CapacitorEnter ConnectorEnter DiodeEnter FETEnter FuseEnter InductorEnter Jumper/StrapEnter Node LibraryEnter Pin LibraryEnter PotentiometerEnter ResistorEnter SwitchEnter TransistorEnter ZenerEnter NodeEnter Internal Devices

Table 2-3 List of blocks and actions in the Flowchart form (continued)

Block Action(s)

© Agilent T 2-11

Chapter 2

es/Conditionss

tionsas

tions



View/Edit Test System Data Enter Power Node DataEnter Fixed Node DataEnter Board-level DisablEnter IPG Global OptionEnter Family OptionsEnter Fixture OptionsEnter GP Relay ConnecEnter Board Keepout AreEnter GroupsEnter Extra Probing Loca


Block Action(s)

© Agilent T 2-12

Chapter 2

tructions

larity Check *ilent TestJet *outs for Agilent TestJet and Polarity Check *nnect Checkessing Accessing Access

ly if you have the Agilent TestJet option

structionsuctionsstructions



Compile/Verify (below View/Edit Test System Data) Display config File InsCompile config FileVerify Fixture TypeVerify Configuration SizeRun Access ConsultantShow Devices Using PoShow Devices Using AgVerify Bottom-Side KeepShow Devices Using CoVerify Node Probing AccVerify Power Node ProbVerify Ground Node Prob* These items appear oninstalled.

View/Edit Library Data Enter Library PathsDisplay Device Library InDisplay Part Library InstrDisplay Safeguard File In


Block Action(s)

© Agilent T 2-13

Chapter 2

esard Files

xistable

hainshains Directory Designatorumber

aryle Results

esults

eport



Compile/Verify (below View/Edit Library Data) Save Board FilesCompile Modified LibrariCompile Modified SafeguVerify Missing LibrariesVerify Disable Methods EVerify Disable Nodes UsVerify Tied Nodes DataVerify Boundary-Scan CShow Boundary-Scan CShow Devices in LibraryShow Library For DeviceShow Library For Part N

Final Compile/Verify Save Board FilesCompile board FileCompile board_xy FileGenerate X-Y PlotShow IPG Device SummVerify IPG Device DisabVerify Safeguard Inhibit R

Testability Report Generate the testability r


Block Action(s)

© Agilent T 2-14

Chapter 2



The Graphical DisplayBoard 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 T 2-15

Chapter 2



Figure 2-3 Board Consultant graphical display

© Agilent T 2-16

Chapter 2

re Controls: A group of pushbuttons that ls which features are shown in the Detailed

(you cannot control the appearance of the iew). When lit, the colors of the buttons pond to the colors of their respective items screen. The options here are:

tlines: Controls whether the physical tline of the board is displayed.

oling Holes: Controls whether tooling holes displayed.

Y Locations: Controls whether X-Y ations are displayed for the top, bottom, or th sides of the board.

vice Outlines: Controls whether device tlines are displayed for the top, bottom, or th sides of the board.

epout Areas: Controls whether keepout as are displayed for the top, bottom, or both es of the board.

Controls: A group of pushbuttons that ls the Detailed View. The options here are:

ow Panel View: Alternates between the nel view and the board view when data is ing entered for a multi-board panel. (This m is usable only when the optional PanelTest ture is installed on your test system.)



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.

� FeatucontroViewOvervcorreson the

� Ouou

� Toare

� X-locbo

� Deoubo

� Kearesid

� Viewcontro

� Shpabeitefea

© Agilent T 2-17

Chapter 2

ption simply changes the perspective from you view the board; it does not affect which es are displayed (X-Y locations, device es, keepout areas) or how those features are yed (top, bottom, both).

or: The cursor location and its units of re appear on the same line as View. The

r location is continuously updated as you the mouse inside either the Overview or the led View.

nd Notes areas are shared with the flowchart e same functions as before.

following material, the layout of some of rms may differ slightly from the same forms y appear on the screen; however, the ons have not changed.

ultant provides many forms to describe your cteristics. You can use these forms to:

or edit data that describes the physical , such as the X-Y locations on a board.



� 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 owhichfeaturoutlindispla

� CursmeasucursomoveDetai

The Status aand serve th

The Forms

NOTEIn thethe foas thefuncti

Board Consboard chara

� Viewboard

© Agilent T 2-18

Chapter 2

ormss in Board Consultant share common ics such as menus, data entry fields, and e Device Entry Form provides an example of you may encounter when using forms. To form, select Tasks > View/Edit Board Data, then select Device Data and any device

ontains menus, data entry fields, and buttons specify device information, add a device, ice, or close the form.

lay options are available from the Options e options allow you to vary the content and of a device entry form, which consists of tions or panels. You can save space on the

isplaying only a portion of the entire form.

ose the following display options:

mize/Normalize: Resizes the device entry so that all of the displayed features are e without scrolling.

/Hide Values: Show or hide features that ibe a device's value, such as its nominal and tolerances.

/Hide Connections: Show or hide features escribe how the pins on a device are cted and accessed.



� 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 FMany formcharacteristbuttons. Ththe featuresdisplay thisDescriptiontype.

This form cthat let you delete a dev

Several dispmenu. Thesappearanceseparate secscreen by d

You can cho

� Maxiform visibl

� Showdescrvalue

� Showthat dconne

© Agilent T 2-19

Chapter 2

hoose to hide an option, the information in the device entry form. When you choose r show an option, an additional panel for that erted into the form, as Figure 2-4 shows.

at different kinds of devices may use n these panels. For example, Values may not kind of device, while another kind of

have several different Test Options.



� 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 cdoes appearto include ooption is ins

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 thvariations oapply to onedevice may

© Agilent T 2-20

Chapter 2



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 T 2-21

Chapter 2

your test system, such as Tab and Shift-Tab m item to item, the forms in Board



Figure 2-5 Maximized Device Entry form

Shortcuts When Using the FormsBesides the standard keys used by most of the software

packages onto move fro

© Agilent T 2-22

Chapter 2

e, you also can use the Shift-left/Shift-right to move from item to item in Board s forms.

, such as the one in Figure 2-6, contain a list h each row contains related data entry

ing home-up (white arrow) moves the typing r to the beginning (upper left corner) of the ea. Pressing home-down (Shift/white arrow)



Consultant provide additional shortcuts you may find useful.

NOTEFor an overview of the user interface and more information about using the keyboard, see Chapter 1, Using a Workstation in Board Test Fundamentals.

For examplarrow keys Consultant�

Some formsarea in whicfields.

Figure 2-6 Shortcuts in a list area

You can use the following shortcuts inside a list area: � Presscursolist ar

© Agilent T 2-23

Chapter 2



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 T 2-24

Chapter 2

UsingConsu

name of a board directory that already ard information.

e much work entering data if you have CAD n be translated to provide board information. ve CAD data, click Translate CAD Data to

ructions about how to use it.

initial steps, there are two distinct paths in of entering board information. One path, ated at the left side of the flowchart, lets you ical and electrical description of the board, information needed by the test system. The which is located at the right side of the ets you develop library tests for use in your

rallel paths converge near the bottom of the here the descriptive board information and

ests combine to become the information to omplete board test.

in the Menu Bar flowchart is an easy-to-use visual guide data entry process, it is the appropriate tool st developers. But if you know exactly what do, you can use items in the menu bar to go desired task. The menu bar is an alternate to use all the forms that are organized into



Board ltant

The next few topics further describe some of the features introduced earlier at an overview level.

Using On-Item HelpBoard 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.

ADVICETo 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 FlowchartEach 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 contains bo

You can savdata that caIf you do hareceive inst

After these the process which is locenter a physplus global other path, flowchart, lboard test.

The two paflowchart, wthe library tdevelop a c

Shortcuts Because thethrough thefor many teyou need todirectly to away for you

© Agilent T 2-25

Chapter 2

formation on the options available, see The Display on page 2-14.

hich side of the board to view.

magnification.

e sections of the board.

items, such as devices or the pins on

data entry forms.

item on the board.

t board locations.

hich side of the board to view.

iew option to select the top or bottom view ard.

magnification.

e view controls to vary the magnification of etailed View.

and hold the right button while dragging the e cursor across the area you want to magnify. you release the button, the area you ied is magnified.

Previous View in the view controls to return original display.



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 DisplayMuch 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 inGraphical

1 Select w

2 Vary the

3 Examin

4 Identifydevices.

5 Display

6 Find an

7 Highligh

1 Select w

Use the Vof the bo

2 Vary the

� Use ththe D

� PressmousWhenspecif

� Clickto the

© Agilent T 2-26

Chapter 2

on of the item and the node to which it is cted.

u might expect, the accuracy of this feature cted by the magnification in the Detailed The larger an item appears, the easier it es to point precisely to it. (You hear a beep

point to an item and miss. Simply try .).

data entry forms.

mouse's right button on an item to select it matically invoke its data entry form.

item on the board.

u need to find an item on your board but do its location, use the Search menu in the

r.

se whether you want to find a device or a This invokes the Search Specification form, ure 2-7 on page 2-27 shows.



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

locaticonne

As yois affeView.becomif youagain

5 Display

Click theand auto

6 Find an

When yonot knowmenu ba

a Choonode.as Fig

© Agilent T 2-27

Chapter 2

e searching for a device and the device type shown in the Search Specification form is , click Device Type to specify another type. ose a device from the list that appears.

ly, you can click the data entry fields and type your choices for Device Type and or.

t board locations.

t Options > Highlight Location Data.

ighlight Control form shown in Figure 2-8 ge 2-28 appears.

se all the locations whose attributes match iteria you specify by clicking the control s.

you have specified the options, click ght to highlight the matching locations.

e that this highlighting occurs only when the ate features are enabled in the features For example, if a location whose fixture top (as specified in the Device Entry form evice) matches the criteria in the Highlight orm but X-Y locations for the top of the

e not enabled, the location is not highlighted.

Clear Highlights in the view controls area as d to clear the existing highlighting.



Figure 2-7 Using the Search Specification form

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.

If you arinitially incorrectThen cho

Alternatedirectly Designat

7 Highligh

a Selec

The Hon pa

b Choothe crbutton

c AfterHighli

Be awarappropricontrols.access isfor that dControl fboard ar

d Clickneede

© Agilent T 2-28

Chapter 2

u use the forms to enter board information, ber to periodically save work in progress.

educes the possibility of losing work se of a power failure or other problem.

sultant and Multi-Board Panels the optional PanelTest feature installed on stem, Board Consultant can help you work oard panels. Both the flowchart and the splay change slightly to accommodate en panels are being used, Board Type:

pears between the View and Cursor labels mmediately above the graphical Detailed dow.

board for data entry.

t Board Type from the flow chart.

oard Selection Form appears.

t the individual boards for data entry.

elected board is displayed graphically, ing X-Y data is available. The Board Type

is grayed-out if panels are not being used.



Figure 2-8 The Highlight Control form

Using the FormsUnless 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.

NOTEAs yorememThis rbecau

Board ConIf you haveyour test sywith multi-bgraphical dipanels. Wh<panel> apon the line iDisplay win

1 Select a

a Selec

The B

b Selec

The sassumblock

© Agilent T 2-29

Chapter 2

d combined into a single file, they become ity Report (described later).

A verification check

results of verification checks:

le, then Print.

og box in Figure 2-10 on page 2-30 appears.



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.

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

sequence anthe Testabil

Figure 2-9

To print the

1 Select Fi

The dial

© Agilent T 2-30

Chapter 2



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 T 2-31

Chapter 2

The BoViewe

ng test operators locate a specific device.

ample, suppose your testplan requires that a tiometer be adjusted. You can use the Board ics Viewer to display the potentiometer and ght it, which helps production operators find rrect potentiometer when making the

tment (see Using the Board Graphics er on page 2-33 for an example of this).

ng test developers locate manual probing ons while debugging a board test.

ng repair operators locate devices and cal locations during repair operations.

Statements for Board Graphics Viewer-BASIC statements lets you invoke the splay from the BT-BASIC command line or d test. Table 2-4 on page 2-32 lists the statements associated with the Board iewer.

ore information about these statements, to the Syntax Reference.



ard Graphics r

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:

� Helpi

For expotenGraphhighlithe coadjusView

� Helpilocati

� Helpiphysi

BT-BASICA set of BTgraphical difrom a boarBT-BASICGraphics V

NOTEFor mrefer

© Agilent T 2-32

Chapter 2

ics Viewer used to graphically display features

ing a multi-board panel to viewing a single

rd view to a panel view (if the board is on a

graphically display features on boards.

view (if it is not already there) and causes it to

oard Graphics Viewer.

a specified device or pin on a device e's status as active, fail, or pass.

all locations on a specified node. The ode's status as active, fail, or pass.

ose which boards should be tested on a



Table 2-4 BT-BASIC statements

Term Definition

board graphics Invokes a read-only version of the Board Graphon boards.

board graphics display board

Switches the Board Graphics Viewer from viewboard on the panel.

board graphics display panel

Switches the Board Graphics Viewer from a boamulti-board panel).

board graphics end Terminates the Board Graphics Viewer used to

board graphics highlight board

Switches the Board Graphics Viewer to a panelhighlight a specified board.

board graphics highlight clear

Selectively clears highlighting provided by the B

board graphics highlight device

Causes the Board Graphics Viewer to highlight (device.pin) in a color that denotes the devic

board graphics highlight nodes

Causes the Board Graphics Viewer to highlight highlighting can be in a color that denotes the n

select boards on panel Lets you use the Board Graphics Viewer to chomulti-board panel.

© Agilent T 2-33

Chapter 2

highlighting.

tion to pot.



Using the Board Graphics ViewerA 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 startboard graphics highlight clear all! Remove any previous

. . .

. . .sub Preshorts

. . .

. . .board graphics highlight device "rpot201"! Draw attentest "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 T 2-34

Chapter 2

The TeRepor

nformation about the testability of the board n department.



stability t

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.

NOTESee 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

to provide ito the desig

© Agilent T 3-1

In this

echnologies 2001, 2003 Test Development Tools 06/2003

3333 The BT-BASIC Environment

chapter... � Using BT-BASIC in a Window, 3-2

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

PrerequisitesBefore you begin using this chapter, you should already know how to use BT-BASIC.

NOTEIf you need more information, see BT-BASIC Programming.

© Agilent T 3-2

Chapter 3

Usinga Wind


: The BT-BASIC Environment

BT-BASIC in ow

Figure 3-1 shows a window with BT-BASIC running.

Figure 3-1 BT-BASIC running inside a window

© Agilent T 3-3

Chapter 3

Areaart of a BT-BASIC window is called the ecause you write text or programs in it. The erations, such as the printing you executed lso sent to the work area unless you specify e, such as a printer.

mode of operation, with the process n number (this number uniquely identifies ing session), is shown at the top right of the

pening a window into BT-BASIC sets the ic, which indicates that the system is ready

BT-BASIC program.

of inverse video at the bottom of the work he functions of the softkeys, F1 through F8. tters IC (insert character) appear near the e window if the keyboard is in the insert

har key).

orkspace available to you is very much just the twenty or so lines in the BT-BASIC e workspace is as large as the available the controller. The work area of the window acts as a window into the n memory. So if you are writing a report and

the screen, the top lines simply roll up and s you add more lines at the bottom. But they from the workspace. You can roll the down (using the up-arrow key) and view



A BT-BASIC window is formatted into two parts:

� The Command Area � The Work Area

The Command AreaThe 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 The lower pwork area bresults of opabove, are aanother plac

The currentidentificatioyour operatwork area. Omode to basto accept a

The blocks area show tAlso, the lebottom of thmode (Ins cThe actual wlarger than window; thmemory in BT-BASIC workspace ihave filled disappear aare not lost workspace

© Agilent T 3-4

Chapter 3

, but when the cursor is moved to the work he command/edit softkey) the original the work area reappear.

use the Clear display key if something has to the screen. For example, if the screen is

vice (printer is *) and you execute a cat n the command line, a list of files appears in a. Pressing the Clear display key erases both

les and the cat statement that appears on the ne. The Clear display key redraws the screen ntents of the workspace (such as a file) are yed.

ile Manipulation statements are used to prepare text, files, s on the workstation. The file manipulation rovide a link between the system workspace structure.



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 ScreenOccasionally 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) clearsarea (with tcontents of

Or, you canbeen printedthe print destatement othe work arethe list of ficommand liwhen the cobeing displa

Editing & FThe editingand programstatements pand the file

© Agilent T 3-5

Chapter 3

ements statements are used with the workstation�s and softkeys to enhance the workstation�s bility. None of these statements are ble. They can be executed only from the command line.

ontains a list and a brief description of the ments.

new string, throughout the workspace. Not

ith a new string, throughout the area defined

with a new string. Not case sensitive.

immediately above the line where the cursor is

ommand line.



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 StatThe editingediting keysediting capaprogrammaworkstation

Table 3-1 cediting state

Table 3-1 Editing statements

Term Definition

change (change all) Replaces all occurrences of an existing string with acase sensitive.

changem (change marked) Replaces all occurrences of an existing string wby the mark softkey. Not case sensitive.

changen (change next) Replaces the next occurrence of an existing string

delete Deletes the marked lines in the workspace.

duplicate Duplicates the marked lines in the workspace. Inserts duplicationpositioned.

edit Positions the cursor at the beginning of the specified line.

fetch Copies a specified line from the workspace into the workstation c

© Agilent T 3-6

Chapter 3

ave, and re-save

store, and re-store

e included in BT-BASIC as a convenience lopers from other systems, who may be used . Feel free to use whichever you prefer, or

ntire workspace. Not case sensitive.

the marked area of the workspace. Not case

e workspace. Not case sensitive.

fault output device.

urrent line to the end of the workspace.

the current line.

d cursor position.

s currently stored there.



File Manipulation StatementsFile 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, s

� load,

Both sets arto test deveto either setmix them.

find (find first) Finds the first occurrence of a given string within the e

findm (find marked) Locates the first occurrence of a given string withinsensitive.

findn (find next) Locates the next occurrence of a given string within th

list (list all) Lists the entire workspace to the default output device.

listm (list marked) Lists the marked portion of the workspace to the de

listn (list to end) Lists, to the default output device, all lines from the c

move Moves the marked segment of workspace to immediately above

number Returns information to the user about the current line number an

scratch Clears the workspace only. Erases any text, program, or variable

Table 3-1 Editing statements (continued)

Term Definition

© Agilent T 3-7

Chapter 3

text on the command line and press Return. that have a mode associated with them ly invoke the required mode when they are to the workspace with a get or load

upon which mode is selected, one of several ens when you change modes:

orkspace is cleared and the mode name rs in the information line of the BT-BASIC w. From here, you can change modes at any y executing the appropriate statement on the

er file.

ile into it. The file is checked for correct syntax. n command line; it is not programmable.

le. The statement can be used to write to a

the workspace in it. Records the current mode



NOTEFor complete descriptions of the statements, refer to the Syntax Reference.

Operating Modes & Error CheckingThere 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 (Also, files automaticalretrieved instatement.)

Depending things happ

� The wappeawindotime b

Table 3-2 File manipulation statements

Term Definition

compile Used to compile object code from source files.

merge Lets you merge all or part of one or more files into anoth

get and load Clears the workspace and copies the contents of a disk fThe statement can be executed only from the workstatio

re-save and re-store

Same as save or store, except writes to an existing fidevice, such as a printer.

save and store Creates a new file on the disk and stores the contents ofin the file.

© Agilent T 3-8

Chapter 3

, the BT-BASIC window returns. The modes o this are described in Table 3-4.

ew mode takes effect but no immediate e occurs in the BT-BASIC window. The s that do this are described in Table 3-5.

ts, and create, edit, or run BT-BASIC

rdware resources available for use by Agilent

nd create or edit VCL test programs, which are in basic mode; see the test statement for

written in PDL (Part Description Language).

information.

ital libraries. These files contain the safety resulting from their being overdriven during



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

modethat d

� The nchangmode

Table 3-3 Modes -- workspace is cleared and mode name is displayed

Mode Description

analog Lets you create or edit analog in-circuit tests.

backtrace Lets you create, edit, or compile backtrace files.

basic Lets you interactively type and execute BT-BASIC statemenprograms.

configuration Lets you create or edit a configuration file that defines the haIPG.

digital Lets you type Vector Control Language (VCL) statements, aused to test digital devices. Note that VCL programs are rundetails.

part Lets you create or edit a part description library file, which is

pins Lets you create or edit a pins file that contains CHEK-POINT

safeguard Lets you create or edit Agilent SAFEGUARD files in the diginformation required to minimize possible damage to devicesdigital testing.

© Agilent T 3-9

Chapter 3

This file lists the nodes that are to be tested for

e state data for digital functional tests.

which tests execute on your system.

is useful for writing reports.

inued)

to enter and verify the accuracy of data during

ng an analog test or when using the Agilent al tests; see Chapter 6, Debugging Digital

o create or edit part description libraries.



shorts Lets you create or edit the shorts test file generated by IPG. opens or shorts.

states Lets you create or edit the states file, which contains the nod

testorder Lets you edit the testorder file, which determines the order in

text Lets you type any text (syntax checking is turned off), which

wirelist Lets you create or edit the fixture wiring list file for a test.

Table 3-3 Modes -- workspace is cleared and mode name is displayed (cont

Mode Description

Table 3-4 Modes -- invokes a separate software package

Mode Description

board consultant Invokes Board Consultant, which is a software tool usedthe test development process.

debug Lets you debug analog and digital tests. (When debuggiPushbutton Debug environment to debug analog or digitTests in Test Methods: Digital)

partforms Invokes the Part Description Editor, which you can use t

© Agilent T 3-10

Chapter 3

u can then erase or correct the error , rather than having to find and correct it at

ng are not automatically syntax checked:

_xy: There is no syntax checking until the _xy file is compiled. To check the syntax

e compilation, you can execute a checkxy statement.

There is no syntax checking because text lets you type anything you wish. You can xt mode to write and save programs, then the syntax later.

urs in the BT-BASIC window

t.

systems.

digital test but not using the Pushbutton Debug 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. Yoimmediatelya later time.

The followi

� boardboard

beforboard

� text: modeuse techeck

Table 3-5 Modes -- the new mode takes effect but no immediate change occ

Mode Description

autolearn Lets you execute autolearn statements for a specified tes

NOTEAUTOLEARN is not supported in MS Windows

debug Lets you debug analog and digital tests.(When debugging a environment; see Chapter 6, Debugging Digital Tests in

© Agilent T 3-11

Chapter 3

e experienced test developer, it is important the image specifications are not syntax he line-level; take extra care when typing ations. They are checked at runtime. There ons for this. First, the specifications can be ings, in which case the system has no way of (until run time) that they are image ns. Second, the specifications must be th the list of items to be input or output by more) I/O statements invoking those image ns. Because those lists can include variables ions, checking for mismatches can be only a .

or Checkingor checking occurs while the program is ain, error messages are generated the type of error found. This type of sures that the program as a whole makes hat statements are not misplaced or missing.

d files that must be compiled are checked at el and are also checked for general sense re compiled.

error checking feature in this system is very helps you write programs correctly and me. Remember that syntax checking cannot errors; the types of errors that cause the return incorrect results or to run in some way.



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 CheckingAt 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 morto note that checked at tthe specificare two reasstored in strdeterminingspecificatiomatched withe (one or specificatioand expressruntime task

Runtime ErrRuntime errrunning. Agidentifying checking ensense, and t

Programs anthe line-levwhen they a

Because thethorough, itsaves you tifind logicalprogram to unexpected

© Agilent T 3-12

Chapter 3

n page 3-12 contains a list and brief of the standard softkey definitions that sic mode (changing to another mode can

softkey definitions) when you log in. The used interactively for manipulating on the workstation screen.

n use the mouse to press softkeys when they d on the screen. Simply place the mouse e softkey and click the mouse�s left button.

he Softkeysinitions can be changed to suit your needs. nts in Table 3-7 on page 3-13 are used to softkey definitions.

to the command line. Or, if the cursor is in the position in the work area, or to the top of the

now in the command stack. As commands are the stack if they are not already there. Older . The stack can hold up to 20 lines.



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 SoftkeysThe 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 odescription appear in bachange the softkeys areinformation

You also caare displayecursor on th

Redefining tSoftkey defThe statememanipulate

Table 3-6 Softkeys

Softkey Description

F1 command/edit If the cursor is in the work area, this key moves it command line, this key moves it to the last knownwork area if the last position is not known.

F2 recall plusF3 recall minus

Recalls, one by one, the commands (statements) executed in the command line, they are added to commands drop off as new commands are added

© Agilent T 3-13

Chapter 3

; the Return key can perform the same to exit BT-BASIC if the workspace has been

to be operated on as a block. This key changes mark to second mark to remove marks.

he block and press mark. Then move the ark. The block is ready to edit. After editing,

area. The new line is inserted at the current us line.

n & off Switches between default and modified softkeys.

& over Stores modified softkey definitions.

Softkey manipulation statements (continued)

Definition



F4 execute Executes the command now in the command linefunction. Also used to confirm that you really wantedited.

F5 mark Defines (marks) a group of lines in the workspace its definition each time it is pressed, switching fromTo define a block, move the cursor to the start of tcursor to the end of the block and press second mpress remove marks.

F8 store line Copies a line from the command line into the workposition of the cursor, and it overwrites any previo

Table 3-6 Softkeys (continued)

Softkey Description

Table 3-7 Softkey manipulation statements

Statement Definition

softkey Changes a softkey definition.

softkey clear Selects the default softkey definition for a single softkey.

softkeys clear Globally selects the default softkey definitions for all softkeys.

softkeys Activates a redefined softkey.

softkeys o

softkeys to

Table 3-7

Statement

© Agilent T 4-1

In this tests of Pushbutton Debug are primarily a user at aids your use of the debug features that t on your test system. Because much of your with Pushbutton debug simply passes bug statements to the BT-BASIC t, this chapter assumes you already have a ng knowledge of debug. If this is not true, wing:

g debug is described in Chapter 5, gging Analog Tests in Test Methods: g.

l debug is described in Chapter 6, gging Digital Tests in Test Methods: l.

nt TestJet debug is described in Chapter 2, nt TestJet and Agilent Vectorless Test EP tional Board Test Applications.

debug is described in the Agilent 307XCT l Functional Test documentation.


4444 Agilent Pushbutton Debug

chapter... � Features of Agilent Pushbutton Debug, 4-4

� Miscellaneous Topics, 4-21

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

PrerequisiSome aspecinterface thalready exisinteraction standard deenvironmengood workisee the follo

� AnaloDebuAnalo

� DigitaDebuDigita

� AgileAgilein Op

� SerialSeria

© Agilent T 4-2

Chapter 4


: Agilent Pushbutton Debug

NOTEDetailed 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 T 4-3

Chapter 4



Figure 4-1 Typical session with Pushbutton Debug

© Agilent T 4-4

Chapter 4

FeaturPushb

The two levels of Pushbutton Debug

Debug is primarily a syntax builder that lets quickly with the standard debug t on the Agilent 3070 family of board test osing items from Pushbutton Debug�s es the needed syntax and then automatically he BT-BASIC environment for execution.

Board-level debug

Device-level debug

Testplan

Repair Tickets

PinsPre-ShortsShortsAnalogDigitalSerialTestJetPolarity Check

Individual tests



es of Agilent utton Debug

The following topics describe the major features of Pushbutton Debug.

Board-Level Versus Device-Level DebugPushbutton Debug lets you debug your board tests at either of two levels:

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

Figure 4-2

Pushbutton you interactenvironmensystem. Chomenus creatsends it to t

© Agilent T 4-5

Chapter 4

hapter 6, Debugging Digital Tests in Test Methods: Digital for more information.

ave finished using Pushbutton Debug, select it from the menu bar.

el Debugutton Debug at the board level. This is the nt for debugging at the board level.

Board-Level Debugn page 4-5 describes the features available vel debug.

h which you interact with Pushbutton Debug.

ms from this list and debug them with



Starting Pushbutton Debug at the Board LevelPushbutton 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.

NOTESee C

When you hFile, then Ex

Board-LevStart Pushbstarting poi

Features of Table 4-1 ofor board-le

Table 4-1 Features of board-level debug

Feature Description

Menu Bar Provides access to several levels of menus and options throug

List of Failing Tests

Displays a list of tests that failed during a board test. Select itePushbutton Debug.

© Agilent T 4-6

Chapter 4

available at this menu are presented in

. You can also use this area as a g macros can also appear here. tem to item in this form, you must use e repair ticket area.ey and then press the home-up key (the white move to the end of the file, press and hold the

and insert mode, the letters IC (Insert low the Help label in the menu bar.

button Debug. The label directly above this ate which of the two debug modes is currently

ent to the BT-BASIC environment.

which Pushbutton Debug was invoked. This is cycle to fail.



The File MenuUse the File menu to create a new file, open an existing file, save or rename a file, or exit Pushbutton Debug.

The optionsTable 4-2.

Repair Ticket Area

An area in which the repair tickets for failing tests appear heregeneral-purpose editor with any text file. The results from usinEditing Tips: Because the Tab key can be used to move from iCTRL-Tab to move from tab stop to tab stop when editing in thTo move to the beginning of the file, press and hold the CTRL karrow key in the keyboard's Cursor Control Group of keys). ToExtend char key and then press the home-up key.When you use the Insert char key to switch between overtypeCharacter) appear at the upper right corner of the form, just be

Message Area

Displays status messages or error messages while using Pusharea reads Board Level Debug or Device Level Debug to indicenabled.The actual debug statements appear in this area as they are s

Select button

Chooses the highlighted test as the one to debug.

List button Not used for board-level debug.

Break Command

Sends a break or interrupt to the BT-BASIC environment fromuseful for interrupting debug operations, such as stopping a re

Table 4-1 Features of board-level debug (continued)

Feature Description

© Agilent T 4-7

Chapter 4

air ticket area, which you can use as a

ing an existing file, you are given the option of

it under a different name than the original file

has multiple links. This is useful with y be linked to many tests.

rom which Pushbutton Debug was invoked.



The Debug MenuOptions from the Debug menu, presented in Table 4-3, are used to debug individual tests and recompile tests with or without debug.

Table 4-2 File menu options


Open Opens an existing file for editing. The file is loaded into the repgeneral-purpose editor for text files.

New Clears the repair ticket area. If you select this option while editsaving the existing file before creating a new file.

Save Saves the current contents of the repair ticket area.

Save as Saves the current contents of the repair ticket area, but saves from which it was loaded. You are prompted for a new name.

Unlink Unlinks or removes a file, or unlinks the name from the file if itmulti-board panels, where the name of a single source file ma

Exit Exits Pushbutton Debug and return to the BT-BASIC session f

© Agilent T 4-8

Chapter 4

test is selected, the first test in the list is

lighted) in the list of failing tests.

and, optionally, specify parameters for the test.

on.

ice-level debug.

session to whichever device is selected by a

er test is selected in the list of failing tests.

er test is selected in the list of failing tests and Debug with more information about the test.

ile and, optionally, specify compilation options.

er so that IPG does not alter the test.



Table 4-3 Debug menu options


Debug Next Test Debugs the next test in the list of failing tests. If nodebugged.

Debug Selected Test Executes whichever test is currently selected (high

Debug Test Lets you enter the name of a specific test to debug

Debug Current Test Returns to the last test debugged during this sessi

Debug Board Returns you to board-level debug if you are in dev

Debug Version Specifies which version of the board will be tested.

Debug Status Sends status information about the current debug printer is statement.

Compile Selected Test Compiles the source files associated with whichev

Compile Selected Test; Debug

Compiles the source files associated with whichevcreates a debug object used to provide Pushbutton

Compile Test Lets you enter the name of a specific test to comp

Mark Permanent Marks the test as permanent in the file testord

© Agilent T 4-9

Chapter 4

you can easily customize the macros that we e Customizing the Macros Menu on or details.

buffer.

ration) from a buffer into the repair ticket area

ocated.



The Edit MenuThe Edit menu, shown in Table 4-4, lets you interact with the contents of the repair ticket area.

The Macros MenuSelecting 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,provide. Sepage 4-21 f

Table 4-4 Edit menu options


Cut Deletes the selected (highlighted) text and places it in a

Copy Copies the selected text and places it in a buffer.

Paste Inserts previously stored text (from a Cut or a Copy opeat the current location of the typing cursor.

Find String Searches for specific text in the repair ticket area.

Go To Line Moves the typing cursor to the specified line.

Duplicate A Line Copies the line on which the typing cursor is currently l

© Agilent T 4-10

Chapter 4

hapter 9, Board Test Grader, Test rage, & Coverage Analyst for a description Board Test Grader.

vel Debugveral topics describe the appearance and he debug features available at the device is where individual tests are debugged.

e testhead, load the testplan, and do other macros set up the test environment so you can

te a section of the testplan and retrieve failing ly placed under Failing Tests: in the main form

cros, which are used to generate a report of Test Grader and Test Coverage are explained Coverage Analyst.



The default options at the first level of the Macros menu are listed in Table 4-5

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.

NOTESee CCoveof the

Device-LeThe next sefeatures of tlevel, which

Table 4-5 Macros menu options


Setup Macros Invokes a list of setup macros, which are used to set up thsteps required to execute a section of the testplan. These execute and debug tests.

Testplan Macros Invokes a list of testplan macros, which are used to executests and repair tickets. A list of failing tests is automaticaland the repair ticket is placed in the repair ticket area.

Test Grader Macros

Invokes a list of Board Test Grader and Test Coverage mathe quality of the board test and test coverage. The Boardin Chapter 9, Board Test Grader, Test Coverage, &

© Agilent T 4-11

Chapter 4

to several levels of menus and options through

or the test being debugged. Unlike board-level r in device-level debug. The mode indicator which is shorts here.

item to item in this form, you must use the test source display and edit area.L key and then press the home-up key (the eys). To move to the end of the file, press and

pe and insert mode, the letters IC (Insert below the Help label in the menu bar.

r while you use Pushbutton Debug. The label Level Debug to indicate which of the two debug

Area and see the actual debug statements that



CHEK-POINT and Shorts Debug at the Device LevelYou 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 Features of CHEK-POINT and Shorts Debug at the device level

Feature Description

Menu Bar The menu bar near the top of the main form provides accesswhich you interact with Pushbutton Debug.

Test source display and edit area

An area where statements in the test source are displayed fdebug, this area cannot be used as a general-purpose editonear the upper right corner always shows the current mode,Editing Tips: Because the Tab key can be used to move fromCTRL-Tab to move from tab stop to tab stop when editing inTo move to the beginning of the file, press and hold the CTRwhite arrow key in the keyboard�s Cursor Control Group of khold the Extend char key and then press the home-up key.When you use the Insert char key to switch between overtyCharacter) appear at the upper right corner of the form, just

Message Area An area in which status messages or error messages appeadirectly above this area reads Board Level Debug or Device modes is currently enabled.As you use Pushbutton Debug, you can watch the Message are sent to the BT-BASIC environment.

© Agilent T 4-12

Chapter 4

t Missing Adjust-Blank

t Missing Adjust-Calculate Results

hapter 2, Agilent TestJet and Agilent rless Test EP in Optional Board Test cations for a description of these macros and o use them.

arity Check Debug at the Device Levelug an Agilent Polarity Check test at the

l. To get to the appropriate screen, enter s the name of the test in the Debug/Debug box.

m which Pushbutton Debug was invoked. This a recycle to fail.f the form when switching from board-level to e contents of the menu bar change as needed eing done.

ontinued)



Analog Debug at the Device LevelYou 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 LevelYou 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

� TestJe

� TestJe

� Faon

� Faoff

NOTESee CVectoApplihow t

Agilent PolYou can debdevice levepolarity aTest dialog

Break Command

Sends a break or interrupt to the BT-BASIC environment frois useful for interrupting debug operations, such as stoppingNotice that besides the overall changes to the appearance odevice-level debug, there are new items in the menu bar. Thto provide selections appropriate for the kind of debugging b

Table 4-6 Features of CHEK-POINT and Shorts Debug at the device level (c

Feature Description

© Agilent T 4-13

Chapter 4

that an arrow appears to the left of this area. the arrow cross-references the graphical al display, this arrow moves to show which rm.e test source and Pushbutton Debug cannot sults in the graphical waveform display (which wever, the question mark does show an

de extensive changes to the test source.

r internal nodes appears. You select items to

the list area.

lay devices, VCL groups, pins, nodes, or



Digital Debug at the Device LevelYou can debug a digital in-circuit test at the device level. Digital device-level debug has the following unique features:

Table 4-7 Features of Digital Debug at the device level

Feature Description

Test source display and edit area

This area provides additional features in digital debug. NoticeWhen you use the graphical waveform display, the position ofdisplay with the test source. As you move through the graphicsection of the test source corresponds to the resultant wavefoThis arrow changes to a question mark if you have modified thaccurately correlate the changed source statements with the reis generated from object code that has not been changed). Hoapproximate correlation between the two unless you have ma

List area An area in which a list of devices, VCL groups, pins, nodes, owork on from this list.

Select button A shortcut that lets you quickly select or unselect every item in

List button Lets you choose what to display in the List area. You can dispinternal nodes.

© Agilent T 4-14

Chapter 4

Device-Level Debugand options beneath the menu bar are to a hierarchy. Although analog debug, g, shorts debug, and serial debug have menu mon, options in some submenus vary with

area or the graphical debug window. items that affect a specific test. For example, es, timing, driver and receiver thresholds, and bug statement affects.ou to select which item to use in a debug his pushbutton directly causes this pushbutton licking on it in the graphical debug window. For on a specific pin during a specific vector. If that ou can simply click on it to indicate your the menu bar.

List area to select items for debug operations. statement without selecting an item from either

lay and edit area to view either the definition



Serial Debug at the Device LevelYou 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 ofThe menus organized indigital debuitems in comthe mode.

Graphic Edit Mode

Controls and shows the status of your interaction with the ListAs you execute debug statements, those statements act upondebug statements affect things like devices, groups, pins, nodmore. It is up to you to specify which of these many items a deThe Graphic Edit Mode pushbutton provides a quick way for yoperation. Clicking in the graphical debug window or clicking tto light. When the pushbutton is lit you can select an item by cexample, suppose you want to change the receiver high valuepin and vector are displayed in the graphical debug window, ypreference and then select Set Reference Receive High fromWhen the Graphic Edit Mode pushbutton is unlit, you use the An error message appears if you attempt to execute a debug the List area or the graphical debug window.

Vector Mapping

Invokes an option menu that lets you use the Test source dispsection or the execution section of the test.

Table 4-7 Features of Digital Debug at the device level (continued)

Feature Description

© Agilent T 4-15

Chapter 4



The Mode MenuSelecting 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.

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.

Table 4-8 Mode menu options

Option Description

Analog Lets you work with analog in-circuit or analog functional tests.

Digital Lets you work with digital in-circuit or digital functional tests.

Serial Lets you work with serial, digital tests that consist of statements from the Serial Test Language (STL).

© Agilent T 4-16

Chapter 4

test is executed once to the end, regardless of

est is executed once, either until the first failure test.

r to execute.

gged, regardless of failures.

gged until a break is received. If a failure

gged until a break is received. If a failure

r to recycle.

y a halt or a pause statement.



The Execute MenuThe 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


Execute To End Executes the test currently being debugged. The failures.

Execute To Fail Executes the test currently being debugged. The toccurs or, if the test does not fail, to the end of the

Execute To Vector . . . Lets you specify the number of an individual vecto

Recycle To End Repeatedly executes the test currently being debu

Recycle To Fail Repeatedly executes the test currently being debuoccurs, the test restarts immediately.

Recycle To Fail; Halt Repeatedly executes the test currently being debuoccurs, test execution halts.

Recycle To Vector . . . Lets you specify the number of an individual vecto

Test Cont Continues a test after the test has been stopped b

Safeguard None Turns off all SAFEGUARD controls.

Safeguard All Turns on all SAFEGUARD controls.

© Agilent T 4-17

Chapter 4

that information is displayed, and work at contain the results of display operations.

in the Display menu are (these options vary ug mode):

let you specify parameters for the drivers rs used in digital testing.

and store data from a known good (golden)

the graphical debug window. You can execute d results, or other information.

aphical debug window. For example, you can adjust the scale of the display, etc.



The Display MenuSelecting 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 howwith files th

The optionswith the deb

The Set MenuSelecting Set from the menu bar invokes the Set menu, which is a pull-down menu. Its submenus, presented in

Table 4-11,and receive

Learn On Turns on the learn feature, which is used to learn board.

Learn Off Turns off the learn feature.

Table 4-9 Execute Menu options (continued)


Table 4-10 Display menu options


Display Define Lets you choose the kind of information that appears ina test and then display failures, actual results, expecte

Display Control Lets you control how information is displayed in the grrefresh or update the display, add or remove markers,

File I/O Lets you save or recall the results of displays.

© Agilent T 4-18

Chapter 4

down loads for receiver pins.

ers, receivers, or on the probe.

reference voltages for drivers and receivers on

one or more drivers.

to a low, high, or high-impedance state.

inators in the receiver circuits on HybridPlus



The Util MenuSelecting Util from the menu bar invokes the Util menu, which is a pull-down menu. Options at that menu are presented in Table 4-12. 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.

Table 4-11 Set menu options


Set Load Invokes a submenu that lets you define the pull-up or pull-

Set Offset Invokes a submenu that lets you define the offsets on driv

Set Reference Invokes a submenu that lets you change the high and low pins and nodes.

Set Slew Rate Invokes a submenu that lets you change the slew rate on

Set State Invokes a submenu that lets you set drivers and receivers

Set Terminators Invokes a submenu that lets you use the diode-clamp termCards to enhance the quality of high-speed signals.

© Agilent T 4-19

Chapter 4

ch the device is adjustable), which greatly time it takes to get a new test debugged and tion.

rt AutoAnalog Debug by selecting either of from Pushbutton Debug�s Macros menu -- s or Testplan Macros.

both menu items for AutoAnalog Debug the items that run the pins, preshorts, and This means that those tests are run ly when you start AutoAnalog Debug, and need to run them by themselves.

l adjustments to test parameters made during es, and work with backpatches. Use Diagnose tomatically analyzes a failing test by varying ss) and then generates a report detailing

ug that are related to timing, such as set the elect which edge of the external clock is used

ignals, and vectors. Also lets you display all for each pass through the homingloop.



The Ports MenuSelecting 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 DebugAutoAnalog Debug automatically debugs tests for resistors, capacitors, FETs, and inductors (except for

tests in whireduces theinto produc

You can statwo optionsSetup MacroNotice that appear aftershorts tests.automaticalyou do not

Table 4-12 Util menu options


Administration Invokes a submenu that lets you print or remove controdebugging, simulate fault conditions on one or more nodFaults for board test transportability. Diagnose Faults auseveral test parameters (attempting to make the test papossible changes to correct the failure.

Timing Invokes a submenu that lets you control features of debvector cycle time, set the period of the DUT clock, and sto synchronize the test timing.

Add/Remove Lets you add or remove drivers, receivers, debug sync shomingloop machine vectors including the piped vectors

© Agilent T 4-20

Chapter 4

to manually engage or disengage the fixture

formation about editing macros, see g the Macros Menu on page 4-21.



The menu items that invoke AutoAnalog Debug are:

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

the operatoras needed.

For more inCustomizin


AutoAnalog Debug

Invokes the default operating mode, which automatically debugs all applicable tests for the board.

Calculate Test Limits . . .

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.

© Agilent T 4-21

Chapter 4

MisceTopics

_Rev$ = ""m well' stmt goes here if req’dm well a is 2,3

lt vacuum configuration is not correct, load into the BT-BASIC workspace and modify

ng the Macros Menuily customize the Macros menu and the cros invoked from it.

directory structure begins with a directory g beneath your board directory. Beneath bug are subdirectories, each of which is he level of macros it contains, as presented 3.

Macros

Description

Contains macro files used for device-level analog debug.

Contains macro files used for all board-level debug.

ck Contains macro files used for all board-level Connect Check test debug.



llaneous Subsequent Runs Are FasterAs 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 DebugWhen 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_Constantsglobal Board$, Board_Rev$

Board$ = "my_board2"

Board!'vacuu

vacuusubend

If the defauthe testplanit.

CustomiziYou can easlist(s) of ma

The macro named debudirectory denamed for tin Table 4-1

Table 4-13

Macro

analog

board

connectche

© Agilent T 4-22

Chapter 4

se file names cannot contain spaces, the score character (_) is used to connect words menu items are longer than one word. The score is automatically removed when the file is displayed as a menu item.

er that uniquely identifies the mnemonic ut for that item in the menu.

ple, menu contains definitions for two items at the first level: Setup Macros and Testplan en the menu appears, the S in Setup Macros d to identify it as the mnemonic shortcut for he T in Testplan Macros is similarly

for the second level of menu items reside directories Setup_Macros and acros. Subdirectory Setup_Macros s for the corresponding menu item of the Again, there is a file named menu that t items appear in the menu at this level. The ludes Testhead Power On, whose mnemonic , and Custom, whose shortcut keystroke is

h directory Setup_Macros are files ne or more programming statements to be the macros. The name of each file must f its corresponding item in file menu at this

xample, menu item Testhead Is 1 executes of file Testhead_Is_1.



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.

Becauunderwhenundername

� A lettshortc

In the examin the menuMacros. Whis underlinethat item. Tunderlined.

Definitions beneath subTestplan_M

contains filesame name.defines whaexample incshortcut is OC.

Also beneatcontaining oexecuted bymatch that olevel. For ethe contents

digital Contains macro files used for device-level digital debug.

polcheck Contains macros files used for device-level debugging of Polarity Check tests.

serial Contains macros files used for device-level debugging of serial tests.

shorts Contains macros files used for device-level debugging of shorts tests.

testjet Contains macros files used for device-level debugging of TestJet tests.

Table 4-13 Macros (continued)

Macro Description

© Agilent T 4-23

Chapter 4

Agilent 3070 software revision 3070 pa, an environment variable was created so les can be easily transferred between ® and MS Windows® controllers, which

different file systems. The environment le, $AGILENT3070_ROOT, replaces the upper ames on both systems.For example, the ENT3070_ROOT factory default value is p3070. In this document, only path names the environment variable are used. If you use actual path names, refer to older versions documentation. Please see The Root tory Environment Variable in nistering Agilent 3070 UNIX Systems for r information.

appear in the order in which you define files. Be sure to supply a unique mnemonic each item, and place that shortcut on the line e menu item.

lank line between entries in any of these a horizontal bar to appear as a separator ms. This is useful when arranging items into milar items.



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.

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

NOTEWith 04.00that fiUNIXhave variabpath n$AGIL

/var/husingmust of theDirecAdmifurthe

Menu itemsthem in the shortcut forfollowing th

Leaving a bfiles causesbetween itegroups of si

© Agilent T 5-1

In this ar plastic or Mylar and then comparing the the blank PC board. If the plots reveal a en you can fix it (and verify the fix) at the least expensive) point in the fixturing


5555 The Plot Generator

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

� Using Plotters with the Plot Generator, 5-8

� Usage Notes, 5-10

ObjectivesWhen 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

piece of cleplot againstproblem, thearliest (andprocess.

© Agilent T 5-2

Chapter 5

AboutGener


: The Plot Generator

The Plot ator

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 T 5-3

Chapter 5

About : good and unreliable locations.

locations where probes cannot appear (such PROBE and NO ACCESS).

utline: keepout areas.

ions that cannot be manually probed during racing (NO MANUAL) are drawn in the priate color for the location.

s are allowed, a second file � p.p � is generated for the top plate of an

ssette fixture. This file is also stored in the directory.

Plotlot is generated from data contained in the file. It shows the locations of all probes and pins, including alternates. The plot is stored ed probes.p in the fixture directory.

er of the probes approximates the required ch probe needs from other probes. If probe re reduced by making changes to the fixture files, then the diameters may overlap. This is diameters drawn using plot generator are



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

� Red: as NO

� Red o

NOTELocatbacktappro

If top probeboard_xyto

Express Calocal board

The ProbeThe Probe Pfixture.o personality in a file nam

The diametclearance eaclearances acomponent because the

© Agilent T 5-4

Chapter 5

s PlotPlot is generated from data contained in the file. It shows the locations of probes, and eir attributes (such as 50MIL, TRANSFERS, lot is always shown from the probe side, s the view is from the bottom for the top om the top for the bottom plate.

stored in a file named inserts.p in the rectory.

Plot uses the following colors:

long and transfer probes.

: 100 mil and 100 mil lightweight probes.

75 mil and 75 mil lightweight probes.

: 50 mil probes are drawn in green.

s are allowed, a second file � .p � is generated for the top plate of an

ssette fixture. This file is also stored in the rectory.

ent Plotent Plot is generated from data contained in .o file. It shows the positions of personality spect to the fixture alignment plate. indicate the area into which a pin must flex

ake contact.



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 InsertThe Inserts fixture.o identifies thetc.). The pwhich meanplate, and fr

The plot is fixture di

The Inserts

� Red:

� Black

� Blue:

� Green

If top probeinsertstop

Express Cafixture di

The AlignmThe Alignmthe fixturepins with reRectangles in order to m

© Agilent T 5-5

Chapter 5

s are allowed, a second file (wirestop.p) for the top plate of an Express Cassette

s file is also stored in the fixture directory.



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.

The Wires PlotThe 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.

If top probeis generatedfixture. Thi

© Agilent T 5-6

Chapter 5

ThingsUsingGener



to do Before the Plot ator

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.

NOTEIn 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 T 5-7

Chapter 5

RunniGener

u can either draw a hard copy of the files or do some other task and plot them later.

a hard copy of the plot files, use the copyent to copy them to a plotter. For example,

end a plot file to the plotter like this:irestop.p" over plotter

at each time you run the Plot Generator, t files are overwritten by the newer versions. e other files on your test system, plot files matically backed up.



ng the Plot ator

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 generateplot statement in Syntax Reference.

NOTEBecause 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

finished, yoimmediately

To produceover statemyou could s

copy "w

Be aware thexisting ploUnlike somare not auto

© Agilent T 5-8

Chapter 5

Usingthe Plo

n of the Plotsing a plot, the Plot Generator assumes the e longer of the two axes on the paper. If this se, use the front-panel controls on your tate the plot before copying plot files to it.

Es easy to determine; if the combination of r and paper size you are using defaults to g the Y-axis as the longer axis, plots are cut lso be aware that which axis is the longer on n plotter may vary with the paper size.

at if your board_xy file contains a keyword to specify rotation of the board, d from it are already rotated.

hapter 3, Creating Board Information in Fixture Development for a description of

placement.

s and Typesnerator supports the use of four pens, which stalled as follows:



Plotters with t 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 PlotIn 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).

OrientatioWhen drawX-axis is this not the caplotter to ro

ADVICThis iplottehavinoff. Aa give

Be aware thPLACEMENT plots derive

NOTESee CTest &board

Pen ColorThe Plot Geshould be in

© Agilent T 5-9

Chapter 5

plots are drawn centered, you can use er if the full-sized plot fits on the paper. If d plot does not fit on the paper, the edges of are cut off.

tters Are Supported? an HP 7550 plotter, any HP 757X-series

758X-series plotter, or HP 759X-series se are connected to the LAN using JetDirect

Erobably want to have your System nistrator or an Agilent Technologies support n set up the plotter(s).



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

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

Because thesmaller papthe full-sizethe drawing

Which PloYou can useplotter, HP plotter. Thecards.

ADVICYou pAdmiperso

© Agilent T 5-10

Chapter 5

Usage e LP Spooler topics in Chapter 8 of the Administration Tasks documentation for

s.

for the Top Plateat plot files for the top plate are ly deleted if they are no longer needed. For e Plot Generator produces plots for both the e and the top plate if the value of the Topowed option was ON when the data for a ntered in Agilent Board Consultant. If you Probes Allowed to OFF and rerun the Plot

n advisory message appears on the screen to that any plot files for the top plate have been

essagesGenerator runs, it may report minor es in the input data being processed, such as:

information was found. This is acceptable, not show tooling holes.

message such as this may reveal a problem, decide that it is normal for this specific ndicates a problem, you have the to correct the data before going further.



Notes Viewing Plot FilesIf 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.

NOTEhpglviewer is a user-contributed program; see Chapter 4, Program Management and Miscellaneous Statements in Board Test Fundamentals.

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

NOTESee thSystemdetail

Plot Files Be aware thautomaticalexample, thbottom platProbes All

board was elater set TopGenerator, ainform you deleted.

Advisory MAs the Plot discrepanci

No tooling but plots do

An advisoryor you mayboard. If it iopportunity

© Agilent T 5-11

Chapter 5



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 T 6-1

In this tes

rstand part description libraries and why you ant to use them. See Chapter 3, Creating

d Information in Test & Fixture opment.

rstand the syntax of PDL. See Chapter 8, Description Language in Data Formats.

miliar with features of the user interface. See ter 1, Using a Workstation in Board Test amentals for more information.


6666 The Part Description Editor

chapter... � Descriptions of the Menus, Tasks, and Forms, 6-2

� Descriptions of the Device Entry Forms, 6-8

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

PrerequisiYou must:

� Undemay wBoarDevel

� UndePart

� Be faChapFund

© Agilent T 6-2

Chapter 6

DescrMenusForms


: The Part Description Editor

iptions of the , Tasks, and

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 T 6-3

Chapter 6

tor

Device Entry FormsResistor

Capacitor

Inductor

Switch

Transistor

Zener

FET

Connector

Potentiometer

Diode

Fuse

Jumper/Strap

Library Device



Figure 6-1 Overview of tasks, menus, and forms in the Part Description Edi

Menu Bar

File

Initialization Device Entry

Task

NewOpenSaveSave AsExit

ResistorCapacitorInductorPotentiometerDiodeZenerTransistorFETConnectorFuseJumper/StrapSwitchPin Library

© Agilent T 6-4

Chapter 6

nuenu invokes a cascading submenu of device or return to the Initialization Form.

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

Description

Returns you to the Initialization Form, which is where you begin working on a part description library.

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

File menu options (continued)

Description



These menus, tasks, and forms are described below.

The Menu BarThe 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 MenuCreate a new file, open an existing file, save a file, or exit the Part Description Editor.

The Task MeThe Task Mentry forms

Table 6-1 File menu options

Menu Item

Description

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

Open Opens an existing part description library file for editing.

Save

Save as

Exit

Table 6-2

Menu Item

Initialization

Device Entr

Table 6-1

Menu Item

© Agilent T 6-5

Chapter 6

zation Formation Form appears whenever you invoke cription Editor. It is the starting point for all the Part Description Editor.

ation Form includes the text boxes and data presented in Table 6-3.

nt part description library file.

t the beginning, those comments appear here. t description library file or edit the comments in

vice is not used, the pin is present but it does s listed here. Items in the list can be separated

nodes a part description library contains.

es, the names of those nodes appears here. ernally but cannot be accessed externally via



ADVICEYou can quickly switch between a device entry form and the Initialization Form by clicking on Prev Task or Next Task, as appropriate.

The InitialiThe Initializthe Part Destasks within

The Initializentry fields

Table 6-3 Initialization form text boxes and data entry fields

Text Box/ Data Entry Field Description

Path to Part Description Library

This text field shows the pathname of the curre

Initial Comments If a part description library contains comments aUse this text box to add comments to a new paran existing file.

List of Unused (noconnect) External Pins

If an external pin on a part description library denot make an internal connection to anything, it ifrom one another by either commas or spaces.

Number of Internal Nodes This text box shows how many (if any) internal

Internal Nodes If a part description library contains internal nodInternal nodes are nodes that are connected intthe fixture.

© Agilent T 6-6

Chapter 6

on page 6-7 shows a typical device entry

in Figure 6-2 on page 6-7 (and similar ther kinds of devices) to specify the ics of a device within a part description ides specifying the part�s electrical ics, you also must specify how its pins are

entry form is individually described in the ections.

to its left below Internal Nodes cannot be

rs (such as r1, c1) of devices included in the



Device Entry FormsAfter 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 form.

Use the formforms for ocharacteristlibrary. Bescharacteristconnected.

Each devicefollowing s

No Manual Probe Access If this box is highlighted, the internal node listedprobed manually.

List of Devices in Part Description

This box contains buttons that list the designatocurrent part description library.

Table 6-3 Initialization form text boxes and data entry fields (continued)

Text Box/ Data Entry Field Description

© Agilent T 6-7

Chapter 6



Figure 6-2 Entering a description of a typical device

© Agilent T 6-8

Chapter 6

DescrDevice

Entry Formacitor Entry Form to enter a description of a at appears in a part description library. The ields in this form are shown in Table 6-4.

or; for example, c1.

, microfarads (uF), or picofarads (pF).

rcentages of the capacitor value. Both are

rbitrarily chosen Pin 1 of this device is


art number or your internal part number, for the urposes only.

itor.

non-replaceable; the capacitor is a child device y replaced. Selecting No means you will be told



iptions of the 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.

Capacitor Use the Capcapacitor thdata entry f

Table 6-4 Capacitor entry form data entry fields

Data Entry Field Description

Designator A unique name that identifies a specific capacit

Value The nominal value of the capacitor in farads (F)

Tolerances (+/-) The plus and minus tolerances expressed as pepositive numbers.

Connections: Pin 1 The external pin or internal node to which the aconnected.


Part Number An optional part number, such as the vendor's pcapacitor. A part number is used for reference p

Failure Message An optional message associated with the capac

Replaceable Can be Yes or No. No denotes the capacitor as inside a parent device and cannot be individuallto replace the parent of a failing device.

© Agilent T 6-9

Chapter 6

are not testable; enter them in part libraries for documentation purposes.

try fields in this form are shown in Table 6-5

to write a test for the capacitor.

for example, j1.

externally accessible. Enter a value and press neath Pins and Connections.

on the connector is connected.

number or your internal part number, for the poses only.

r.

n-replaceable; i.e., the connector is a child ually replaced. Selecting No means you will be



Connector Entry FormUse the Connector Entry Form to enter a description of a connector that appears in a part description library.

Connectorsdescription

The data en

Type Can be Fixed or Variable.

Testable Can be Yes or No. No instructs Agilent IPG not

Table 6-4 Capacitor entry form data entry fields (continued)


Table 6-5 Connector entry form data entry fields


Designator A unique name that identifies a specific connector;

Number of Connections The total number of pins on the connector that areReturn; the appropriate number of rows appear be

Pins A number associated with a pin on the connector.

Connections The external pin or internal node to which each pin

Part Number An optional part number, such as the vendor's partconnector. A part number is used for reference pur

Failure Message An optional message associated with the connecto

Replaceable Can be Yes or No. No denotes the connector as nodevice inside a parent device and cannot be individtold to replace the parent of a failing device.

© Agilent T 6-10

Chapter 6

or example, cr1.

p across the diode when it is forward biased.

across the diode when it is forward biased.

node of this device is connected.

athode of this device is connected.

art number or your internal part number, for the oses only.

.

-replaceable; the diode is a child device inside ced. Selecting No means you will be told to

a test for the diode.



Diode Entry FormUse 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


Designator A unique name that identifies a specific diode; f

Forward Bias Test Limits: High

Specifies the upper test limit for the voltage dro

Forward Bias Test Limits: Low

Specifies the lower test limit for the voltage drop

Connections: Anode The external pin or internal node to which the a

Connections: Cathode The external pin or internal node to which the c

Part Number An optional part number, such as the vendor�s pdiode. A part number is used for reference purp

Failure Message An optional message associated with the diode

Replaceable Can be Yes or No. No denotes the diode as nona parent device and cannot be individually replareplace the parent of a failing device.

Testable Can be Yes or No. No instructs IPG not to write

© Agilent T 6-11

Chapter 6

data entry fields in this form are shown in

istor; for example, qf1.

tance (Ron).

tance (Ron).

evice�s source is connected.

evice�s gate is connected.

evice�s drain is connected.

art number or your internal part number, for the ses only.

replaceable; the FET is a child device inside a ed. Selecting No means you will be told to

a test for the FET.



FET Entry FormUse the FET Entry Form to enter a description of a field-effect transistor that appears in a part description

library. TheTable 6-7

Table 6-7 FET entry form data entry fields


Designator On A unique name that identifies a field-effect trans

Resistance: High Specifies the high test limit for the channel resis

On Resistance: Low Specifies the low test limit for the channel resis

Type Can be N-Channel or P-Channel.

Connections: Source The external pin or internal node to which this d

Connections: Gate The external pin or internal node to which this d

Connections: Drain The external pin or internal node to which this d

Part Number An optional part number, such as the vendor�s pFET. A part number is used for reference purpo

Failure Msg An optional message associated with the FET.

Replaceable Can be Yes or No. No denotes the FET as non-parent device and cannot be individually replacreplace the parent of a failing device.


© Agilent T 6-12

Chapter 6

r example, f1.

use in amps.



art number or your internal part number, for the ses only.

replaceable; the fuse is a child device inside a ed. Selecting No means you will be told to

a test for the fuse.



Fuse Entry FormUse 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


Designator A unique name that identifies a specific fuse; fo

Max Current The maximum permissible current through the f



Part Number An optional part number, such as the vendor�s pfuse. A part number is used for reference purpo

Failure Message An optional message associated with the fuse.

Replaceable Can be Yes or No. No denotes the fuse as non-parent device and cannot be individually replacreplace the parent of a failing device.


© Agilent T 6-13

Chapter 6

r; for example, l1.

), millihenries (mH), or microhenries (uH).

rcentages of the inductor value. Both are

ilohms (k ohms), or megohms (M ohms).



art number or your internal part number, for the rposes only.

tor.

on-replaceable; the inductor is a child device y replaced. Selecting No means you will be told



Inductor Entry FormUse 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


Designator A unique name that identifies a specific inducto

Value The nominal value of the inductor in henries (H


Series Resistance The series resistance of the inductor in ohms, k



Part Number An optional part number, such as the vendor's pinductor. A part number is used for reference pu

Failure Message An optional message associated with the induc

Replaceable Can be Yes or No. No denotes the inductor as ninside a parent device and cannot be individuallto replace the parent of a failing device.

© Agilent T 6-14

Chapter 6


a test for the inductor.

or strap; for example, jp1.



art number or your internal part number, for the ence purposes only.

r or strap.

as non-replaceable; the jumper/strap is a child ividually replaced. Selecting No means you will



Jumper/Strap Entry FormUse the Jumper/Strap Entry Form to enter a description of a jumper or a strap that appears in a part description

library. TheTable 6-10.



Table 6-9 Inductor entry form data entry fields (continued)


Table 6-10 Jumper/Strap entry form data entry fields


Designator A unique name that identifies a specific jumper



Part Number An optional part number, such as the vendor�s pjumper or strap. A part number is used for refer

Failure Message An optional message associated with the jumpe

Replaceable Can be Yes or No. No denotes the jumper/strapdevice inside a parent device and cannot be indbe told to replace the parent of a failing device.

© Agilent T 6-15

Chapter 6

analog, digital, mixed, or even another part library.

try fields in this form are shown in Table

he jumper or strap when it is tested.to the proper state specified will cause it to fail

a test for the jumper or strap.

ry device.

at are externally accessible. After you enter a iate number of rows appear beneath Pins and

ice.

on the library device is connected.



Pin Library Entry FormUse 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 bedescription

The data en6-11.

Type Can be Open or Closed to denote the state of tIf you test the jumper or strap without setting it the test!


Table 6-10 Jumper/Strap entry form data entry fields (continued)


Table 6-11 Pin Library entry form data entry fields


Designator A unique name that identifies a specific pin libra

Number of Connections The total number of pins on the library device thvalue in this field and press Return, the approprConnections.

Pins A number associated with a pin on a library dev

Connections The external pin or internal node to which a pin

© Agilent T 6-16

Chapter 6

data entry fields in this form areshown in

er or your internal part number, for the library

device.

e as non-replaceable; the library device is a be individually replaced. Selecting No means device.

a test for the library device.

meter; for example, p1.

, kilohms (k ohms), or megohms (M ohms).



Potentiometer Entry FormUse the Potentiometer Entry Form to enter a description of a potentiometer that appears in a part description

library. TheTable 6-12

Part Number A part number, such as the vendor's part numbdevice.

Failure Message An optional message associated with the library

Replaceable Can be Yes or No. No denotes the library devicchild device inside a parent device and cannot you will be told to replace the parent of a failing

Safeguard


Testability Standard 1149.1

Library test expected.

Table 6-11 Pin Library entry form data entry fields (continued)


Table 6-12 Potentiometer data entry fields


Designator A unique name that identifies a specific potentio

Value The nominal value of the potentiometer in ohms

© Agilent T 6-17

Chapter 6

rcentages of the potentiometer�s value. Both


evice�s wiper is connected.


art number or your internal part number, for the nce purposes only.

tiometer.

er as non-replaceable; the potentiometer is a be individually replaced. Selecting No means device.

a test for the potentiometer.



Resistor Entry FormUse 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 6-13.

Tolerances (+/-) The plus and minus tolerances expressed as peare positive numbers.


Connections: Wiper The external pin or internal node to which this d


Part Number An optional part number, such as the vendor�s ppotentiometer. A part number is used for refere

Failure Message An optional message associated with the poten

Replaceable Can be Yes or No. No denotes the potentiometchild device inside a parent device and cannot you will be told to replace the parent of a failing


Table 6-12 Potentiometer data entry fields (continued)


© Agilent T 6-18

Chapter 6

; for example, r1.

ms (k ohms), or megohms (M ohms).

rcentages of the resistor value. Both are



art number or your internal part number, for the rposes only.

or.

on-replaceable; the resistor is a child device y replaced. Selecting No means you will be told

a test for the resistor.



Table 6-13 Resistor entry form data entry fields


Designator A unique name that identifies a specific resistor

Value The nominal value of the resistor in ohms, kiloh




Part Number An optional part number, such as the vendor�s presistor. A part number is used for reference pu

Failure Message An optional message associated with the resist

Replaceable Can be Yes or No. No denotes the resistor as ninside a parent device and cannot be individuallto replace the parent of a failing device.



© Agilent T 6-19

Chapter 6

for example, s1.

xternally accessible. After you enter a value in ber of rows appear beneath Pins and

on the switch is connected.

if the contact listed below Connections in the witch is tested. If you highlight this box, the

te specified here, it does not pass the test!

art number or your internal part number, for the poses only.

.



Switch Entry FormUse 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 6-14.

Table 6-14 Switch entry form data entry fields


Designator A unique name that identifies a specific switch;

Number of Connections The total number of pins on the switch that are ethis field and press Return, the appropriate numConnections.

Pins A number associated with a pin on the switch.

Connections The external pin or internal node to which a pin

Open/Closed Click a box marked Open to select (highlight) itsame row is connected to Common when the sOpen label changes to Closed.If you test the switch without setting it to the sta

Part Number An optional part number, such as the vendor�s pswitch. A part number is used for reference pur

Failure Message An optional message associated with the switch

© Agilent T 6-20

Chapter 6


n-replaceable; the switch is a child device y replaced. Selecting No means you will be told

a test for the switch.

transistor; for example, q1.

e.

e.

sistor is an NPN or a PNP device.

evice�s emitter is connected.

evice�s base is connected.

evice�s collector is connected.

art number or your internal part number, for the urposes only.



Transistor Entry FormUse the Transistor Entry Form to enter a description of a bipolar transistor that appears in a part description

library. TheTable 6-15.

Replaceable Can be Yes or No. No denotes the switch as noinside a parent device and cannot be individuallto replace the parent of a failing device.


Table 6-14 Switch entry form data entry fields (continued)


Table 6-15 Transistor entry form data entry fields


Designator A unique name that identifies a specific bipolar

Beta Test Limits: High The upper test limit specified as a DC beta valu

Beta Test Limits: Low The lower test limit specified as a DC beta valu

Type Can be NPN or PNP to denote whether the tran

Connections: Emitter The external pin or internal node to which this d

Connections: Base The external pin or internal node to which this d

Connections: Collector The external pin or internal node to which this d

Part Number An optional part number, such as the vendor�s ptransistor. A part number is used for reference p

© Agilent T 6-21

Chapter 6

try fields in this form are shown in Table

stor.

non-replaceable; the transistor is a child device y replaced. Selecting No means you will be told

a test for the transistor.

iode; for example, ds1.

rcentages of the Zener value. Both are positive

evice�s anode is connected.

evice�s cathode is connected.

s part number or your internal part number, for rence purposes only.



Zener Entry FormUse the Zener Entry Form to enter a description of a Zener diode that appears in a part description library.

The data en6-16.

Failure Message An optional message associated with the transi

Replaceable Can be Yes or No. No denotes the transistor as inside a parent device and cannot be individuallto replace the parent of a failing device.


Table 6-15 Transistor entry form data entry fields (continued)


Table 6-16 Zener entry form data entry fields


Designator A unique name that identifies a specific Zener d

Value The nominal value of the Zener diode.

Tolerances (+/-) The plus and minus tolerances expressed as penumbers.

Connections: Anode The external pin or internal node to which this d

Connections: Cathode The external pin or internal node to which this d

Part Number An optional part number, �such as the vendor'the Zener diode. A part number is used for refe

© Agilent T 6-22

Chapter 6

diode.

as non-replaceable; the Zener diode is a child ividually replaced. Selecting No means you will

a test for the Zener diode.



Failure Msg An optional message associated with the Zener

Replaceable Can be Yes or No. No denotes the Zener diodedevice inside a parent device and cannot be indbe told to replace the parent of a failing device.


Table 6-16 Zener entry form data entry fields (continued)


© Agilent Technologies 2002 Test Development Tools 7-1

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

NOTEFor more information about CAMCAD Professional, see http://www.ate.agilent.com/emt/products/intelligent_test/CAMCAD/demo.asp.

http://www.ate.agilent.com/emt/products/intelligent_test/CAMCAD/demo.asp

© Agilent T 8-1

In this e many of the features of the graphical the forms are similar.

se extensive online help is available, this er provides only the information needed to stand and begin using the software package.

are not already familiar with features of the nterface � such as the mouse, windows, s, online help, and the terminology iated with them � see Chapter 1, Using a station in Board Test Fundamentals for information.


8888 Agilent Fixture Consultant

chapter... � Introduction, 8-2

� Getting Started, 8-3

� Fixture Graphics, 8-4

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

PrerequisitesThis 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

easy becausdisplay and

NOTEBecauchaptunder

If youuser imenuassocWorkmore

© Agilent T 8-2

Chapter 8

Introd s extensive online help.


: Agilent Fixture Consultant

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

� Acces

© Agilent T 8-3

Chapter 8

Gettin



g Started Starting Agilent Fixture ConsultantTo 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 ConsultantYou can exit Fixture Consultant by selecting File, then Exit from the menu bar of Fixture Consultant�s main graphical display.

© Agilent T 8-4

Chapter 8

Fixtur souts

ates

Statements for Fixture Graphicsxture graphics from a BT-BASIC within the testplan lets you invoke the splay. Table 8-1 lists the BT-BASIC ssociated with Fixture Graphics.

nt used to graphically display features of the



e 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

� Probe� Keep� BRCs� Altern

BT-BASICEntering fiwindow or graphical distatements a

Table 8-1 BT-BASIC statements

Using Fixture GraphicsAn example of using Fixture Graphics within a testplan might look like Example 8-1.

Term Definition

fixture graphics Invokes a read-only version of Fixture Consultafixture.

fixture graphics end Terminates Fixture Graphics.

© Agilent T 8-5

Chapter 8



Example 8-1

! Beginning of the testplan. . .. . .

fixture graphics. . .. . .

sub Preshorts. . .. . .. . .

subend

fixture graphics end. . .

© Agilent T 9-1

, & Coverage Analyst

In this ation on Coverage Analyst, see Coverage st on page 9-29.


9999 Board Test Grader, Test Coverage

chapter... � Board Test Grader Overview, 9-2

� Running Board Test Grader, 9-5

� Troubleshooting, 9-9

� Board Test Grader Files, 9-13

� Test Coverage, 9-23

� Coverage Analyst, 9-29

ObjectivesWhen 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 9-23.

� 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

informAnaly

© Agilent T 9-2

Chapter 9

BoardOverv

sGrader:

not support tests with variables in Basic on on mixed tests, especially Agilent

t Tests).

not support Agilent Polarity Check tests.

ys requires a .discharge test, even if one t written automatically.

ethodsthese test types, at least one of the following thods determines the quality and your tests:

m Off (all test types).

sts are run with the vacuum off. Any test asses is flagged in the report as failing. This d simulates the test's ability to find missing

onents.


: Board Test Grader, Test Coverage, & Coverage Analyst

Test Grader iew

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

LimitationBoard Test

� Does (commTestJe

� Does

� Alwawasn�

Grading MFor each of grading mestability of

� Vacuu

The tethat pmethocomp

© Agilent T 9-3

Chapter 9

tered between the two limits. Therefore, y mean outside the +/- 2 standard deviation it has only a 5% probability of stemming m the test. This suggests further amination of the test is necessary. The efficient of producibility is calculated from equation:

d should exceed the specified value (default 10; you can change the default in nfig.bdg).

orts test: The shorts evaluation generates r new shorts files. The original thresholds

d settling delays are modified both up and wn by a specified percentage (default is %) to simulate testhead-to-testhead riation. The tests are flagged as failures if y do not pass.

s, digital, functional tests: The tests are run eatedly for a specified number of times fault is 10 times). Tests are flagged as lures if they do not pass all repetitions.

r Supply Sensitivity (all powered tests)

igital in-circuit, digital functional, and g functional tests are executed with lower igher power supply voltages (default is +/-

cp = mean - closer limit3*standard deviation



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

cenanlimfroexcothe

anis co

Shfouando10vathe

Pinrep(defai

� Powe

The danaloand h

© Agilent T 9-4

Chapter 9

igital in-circuit, digital functional, and g functional tests are run with drivers and ers in modified states to determine the pin overage of the VCL/PCF tests. The four

tested are drive level stuck high, drive level low, driver floating, and receiver nnected. A report on the pin fault coverage tests is generated.



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 danaloreceivfault ccasesstuckdiscoof the

© Agilent T 9-5

Chapter 9

RunniGrade

the testplan file.

stplan file, move the vacuum well t into the Initialize_Board_Constants e.

ple:tialize_Board_ConstantsBoard$,Board_Rev$

$ = "roy"_rev$ = ""

um well stmt goes here (if req’d)m well a is 2,3

oard Test Grader in Pushbutton Debugd Test Grader from Pushbutton Debug:

ard Test Grader.

Macros in the Pushbutton Debug menu bar.

Test Grader Macros.

st Grader macro commands are Generate erage Report, Create Grading Config, Create Testplan, and Grade Tests.



ng Board Test r

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.01.50 Board TestsBefore you use Board Test Grader on a pre-B.01.50 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

In the testatemensubroutin

For examsub Iniglobal

BoardBoard

!vacuvacuu

subend

Running BTo run Boar

1 Start Bo

a Click

b Click

Board TeTest CovGrading

© Agilent T 9-6

Chapter 9

omments in config.bdg help you edit the listing of the default config.bdg file is

n in config.bdg on page 9-16.

e the Board Test Grader testplan.

Create Grading Testplan.

lan is created from your original testplan onfig.bdg file. It contains the BT-BASIC ds to grade your in-circuit and functional

t edit config.bdg after testplan.bdg is d. If you need to edit config.bdg, create a estplan.bdg.

Board Test Grader testplan.

Grade Tests.

des the tests specified in config.bdg and he grading reports in the _directory>/bdg_data directory.

e report files.



NOTEThe first macro, Generate Test Coverage Report, is a separate program from Board Test Grader and is described in Test Coverage on page 9-23.

2 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 cfile. Ashow

4 Generat

Click on

The testpand the ccommantests.

NOTEDo nocreatenew t

5 Run the

Click on

This gracreates t/<board

6 Print th

© Agilent T 9-7

Chapter 9

omments in config.bdg help you edit the listing of the default config.bdg file is

n in config.bdg on page 9-16.

e the Board Test Grader testplan.

tests; testplan

lan is created from your original testplan onfig.bdg file. It contains the BT-BASIC ds to grade your in-circuit and functional

t edit config.bdg after testplan.bdg is d. If you need to edit config.bdg, create a estplan.bdg.

Board Test Grader testplan.

testplan.bdg’ | run

des the tests specified in config.bdg.



Running Board Test Grader in a BT-BASIC WindowThis 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 cfile. Ashow

4 Generat

Enter:grade

The testpand the ccommantests.

NOTEDo nocreatenew t

5 Run the

Enter:get ’

This gra

© Agilent T 9-8

Chapter 9



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 GraderIf 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 T 9-9

Chapter 9

Troub nd subroutines. For example, setting up an al instrument before a specific test might

nt the test from running multiple times.

problems with Board Test Grader because of quirements, consider rewriting your original

eet these requirements.

iles must be in the appropriate format ocation. Test Grader operates on the assumption that iginal testplan and other board directory re present and are of Agilent 3070 standard t. If this is not the case, Board Test Grader ot function properly.

d Test Grader requires the presence of a harge file.ile is required even if the original board opment did not require one. If your board ory does not have a .discharge file, see ing a .discharge File on page 9-11.

statements might be necessary. vacuum release time is greater than ximately 2 seconds, consider adding wait ents in testplan.bdg. This allows the

e to completely finish before the next test s. The wait can be added to the individual broutines in testplan or to the m_Cycle subroutine.



leshooting 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 aexternpreve

If you have the these retestplan to m

� The fand lBoardthe orfiles aformamay n

� Boar.disc

This fdeveldirectCreat

� Wait If theapprostatemfixturbegintest suVacuu

© Agilent T 9-10

Chapter 9

dec)"one

onostable test cannot be re-run immediately se it requires a one second wait between

ng changes in Example 9-2 make the dable:



Example TestplanExample 9-1 shows a testplan in an inappropriate format:

Example 9-1

sub Digital_Teststest "U1"gpconnect "Node1" to "Node2"test "U2"

subend

sub Analog_Functional_Teststest "U3"

output "Source" ; "Send 1kHz, 0dbm, analog signal to cosetup Synchronization to T1 stream ! ignore how it's dtest "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 17-24.

� The mbecautests.

The followitestplan gra

© Agilent T 9-11

Chapter 9

codec)"

file.

file as .discharge.

the .discharge file.

wirelist file.

need to execute a list object wirelist.o elist first.



Example 9-2

sub Digital_Testsgpdisconnect "Node1" from "Node2"test "U1"gpconnect "Node1" to "Node2"test "U2"

subend

sub Analog_Functional_Testsgpconnect "Node1" to "Node2"test "U3"

output "Source" ; "Send 1kHz, 0dbm, analog signal totest "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 Graderdisconnect all

3 Save the

Save the

4 Compile

5 Get the

You mayover wir

© Agilent T 9-12

Chapter 9



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 T 9-13

Chapter 9

BoardFiles

siles, listed in Table 9-2 on page 9-14, show

of successful or unsuccessful runs for each mmary Report (summary.rpt) shows which further examination. Examine it before you

vidual report files.



Test Grader Data FilesThe 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 FileThe report fthe numbertest. The Sutests requirelook at indi

Table 9-1 Data files

File Data

pins.dat Pins data

pre_sho.dat Preshorts data

sho.dat Shorts data

ana_inc_vac_off.dat Analog incircuit vacuum off data

ana_inc_qua.dat Analog incircuit quality data

dig_inc_vac_off.dat Digital incircuit vacuum off daa

dig_inc_qua.dat Digital incircuit quality data

dig_inc_pow_sup.dat Digital incircuit power supply sensitivity data

dig_inc_spe.dat Digital incircuit speed sensitivity data

dig_inc_ver_fau.dat Digital incircuit verify faults data

dig_fun_vac_off.dat Digital functional vacuum off data

© Agilent T 9-14

Chapter 9

ta

ata



dig_fun_qua.dat Digital functional quality data

dig_fun_pow_sup.dat Digital functional power supply sensitivity da

dig_fun_spe.dat Digital functional speed sensitivity data

dig_fun_ver_fau.dat Digital functional verify faults data

ana_fun_vac_off.dat Analog functional vacuum off data

ana_fun_qua.dat Analog functional quality data

ana_fun_pow_sup.dat Analog functional power supply sensitivity d

ana_fun_spe.dat Analog functional speed sensitivity data

ana_fun_ver_fau.dat Analog functional verify faults data

Table 9-1 Data files (continued)

File Data

Table 9-2 Report files

File Data

pins.rpt Pins report

pre_sho.rpt Preshorts report

sho.rpt Shorts report

ana_inc_vac_off.rpt Analog incircuit vacuum off report

© Agilent T 9-15

Chapter 9

rt

port

t

eport



ana_inc_qua.rpt Analog incircuit quality report

dig_inc_vac_off.rpt Digital incircuit vacuum off report

dig_inc_qua.rpt Digital incircuit quality report

dig_inc_pow_sup.rpt Digital incircuit power supply sensitivity repo

dig_inc_spe.rpt Digital incircuit speed sensitivity report

dig_inc_log_lev.rpt Digital incircuit logic level sensitivity report

dig_inc_fau_cov.rpt Digital incircuit fault coverage report

dig_fun_vac_off.rpt Digital functional vacuum off report

dig_fun_qua.rpt Digital functional quality report

dig_fun_pow_sup.rpt Digital functional power supply sensitivity re

dig_fun_spe.rpt Digital functional speed sensitivity report

dig_fun_log_lev.rpt Digital functional logic level sensitivity repor

dig_fun_fau_cov.rpt Digital functional fault coverage report

ana_fun_vac_off.rpt Analog functional vacuum off report

ana_fun_qua.rpt Analog functional quality report

ana_fun_pow_sup.rpt Analog functional power supply sensitivity r

ana_fun_spe.rpt Analog functional speed sensitivity report

Table 9-2 Report files (continued)

File Data

© Agilent T 9-16

Chapter 9

ere BDG puts

t loops:

rd. Thisreports.board files.

to this

e. BDG usesstplan_bdg.G prints this

rt



config.bdgExample 9-3 shows the default config.bdg file.

Example 9-3

Data_Dir = bdg_data # Name of the directory wh# data and report files.

Cycle_Vacuum = False # Cycle vacuum between tes# True or False

Board_Serial_Number = Board1 # Serial Number of the boa# string is printed on the

Board_Path = ./ # Directory containing the# BDG changes directory in# directory.

Testplan = testplan # Name of the testplan fil# this file to generate te

Testhead = th1 # Name of the testhead. BD# string on the reports.

ana_fun_log_lev.rpt Analog functional logic level sensitivity repo

ana_fun_fau_cov.rpt Analog functional fault coverage report

summary.rpt Summary report

Table 9-2 Report files (continued)

File Data

© Agilent T 9-17

Chapter 9

the Characterizene.the Pins.the Pre_shortsne.the Shortsne.the Analogubroutine. Sub_Setup_Power_Supplies

p the powerthe Digitalt subroutine.the Digitalal subroutine.the Analogal subroutine.

True or False. Pins_Executions = 10

Pre-Shorts tests:e_Shorts_Executions = 10e_Shorts_Report_CPK < 10.00PK (coefficient ofbility) used to flagin the report.a test must be

d within this value,ag is set in the

threshold - largestment must exceed thisr a flag is set inort.



Sub_Characterize = Characterize # Name of# subrouti

Fn_Pins = fnPinsfailed # Name of# function

Sub_Pre_Shorts = Pre_Shorts # Name of# subrouti

Sub_Shorts = Shorts # Name of# subrouti

Sub_Analog_Incircuit = Analog_Tests # Name of# Incircuit s

= Setup_Power_Supplies # Name of the subroutine# to set u

Sub_Digital_Incircuit = Digital_Tests # Name of# Incircui

Sub_Digital_Functional = Functional_Tests # Name of# Function

Sub_Analog_Functional = Analog_Functional_Tests # Name of# Function

# These commands apply to Pins tests:Pins_Test = True # Run test:# Number of runs of the test.

# These commands apply to thePre_Shorts_Test = True # Run test: True or False. Pr

# Number of runs of the test. Pr# Value of C

# produci# a test

Pre_Shorts_Report_Mean_Not_Centered=66.67% # The mean# centere# or a fl# report.

Pre_Shorts_Report_Closed_Margin = 2.00 # The test# measure# value o# the rep

© Agilent T 9-18

Chapter 9

lest measurement -reshold must exceedlue or a flag is setreport.

: True or False.f runs of the testvariation of the

ld.variation of the

ld.variation of the

g delay.variation of the

g delay.

in the reportwithin this



Pre_Shorts_Report_Open_Margin = 100.00 # The smal# test th# this va# in the

# These commands apply to the Shorts tests:Shorts_Test = True # Run testShorts_Executions = 10 # Number oShorts_Positive_Threshold_Variation = 10.00% # Positive

# threshoShorts_Negative_Threshold_Variation = 10.00% # Negative

# threshoShorts_Positive_Settling_Delay_Variation = 10% # Positive

# settlinShorts_Negative_Settling_Delay_Variation = 10% # Negative

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

# 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# _Mean_Not_Centered The mean a test must be centered

© Agilent T 9-19

Chapter 9

port.ncreasing the value.ecreasing the value.

og_Incircuit_Vacuum_Off_Test = True

%

ion = 5.00%ion = 5.00%

0.00%0.00%

7%



# value, or a flag is set in the re# _Positive_Variation Change in the test parameter by i# _Negative_Variation Change in the test parameter by d

# These commands apply to the Analog Incircuit tests: AnalAnalog_Incircuit_Quality_Executions = 10Analog_Incircuit_Quality_Report_CPK < 10.00Analog_Incircuit_Quality_Report_Mean_Not_Centered = 66.67%

# These commands apply to the Digital Incircuit tests:Digital_Incircuit_Vacuum_Off_Test = TrueDigital_Incircuit_Quality_Test = TrueDigital_Incircuit_Quality_Executions = 10Digital_Incircuit_Quality_Report_CPK < 10.00Digital_Incircuit_Quality_Report_Mean_Not_Centered = 66.67Digital_Incircuit_Power_Supply_Sensitivity_Test = TrueDigital_Incircuit_Power_Supply_Sensitivity_Executions = 1Digital_Incircuit_Power_Supply_Sensitivity_Positive_VariatDigital_Incircuit_Power_Supply_Sensitivity_Negative_VariatDigital_Incircuit_Speed_Sensitivity_Test = TrueDigital_Incircuit_Speed_Sensitivity_Executions = 1Digital_Incircuit_Speed_Sensitivity_Positive_Variation = 1Digital_Incircuit_Speed_Sensitivity_Negative_Variation = 1Digital_Incircuit_Logic_Level_Sensitivity_Test = TrueDigital_Incircuit_Logic_Level_Sensitivity_Executions = 1Digital_Incircuit_Fault_Coverage_Test = TrueDigital_Incircuit_Fault_Coverage_Executions = 1

# These commands apply to the Digital Functional tests:Digital_Functional_Vacuum_Off_Test = TrueDigital_Functional_Quality_Test = TrueDigital_Functional_Quality_Executions = 10Digital_Functional_Quality_Report_CPK < 10.00Digital_Functional_Quality_Report_Mean_Not_Centered = 66.6Digital_Functional_Power_Supply_Sensitivity_Test = TrueDigital_Functional_Power_Supply_Sensitivity_Executions = 1

© Agilent T 9-20

Chapter 9

tion = 5.00%tion = 5.00%

10.00%10.00%

%

ion = 5.00%ion = 5.00%

0.00%0.00%



Digital_Functional_Power_Supply_Sensitivity_Positive_VariaDigital_Functional_Power_Supply_Sensitivity_Negative_VariaDigital_Functional_Speed_Sensitivity_Test = TrueDigital_Functional_Speed_Sensitivity_Executions = 1Digital_Functional_Speed_Sensitivity_Positive_Variation =Digital_Functional_Speed_Sensitivity_Negative_Variation =Digital_Functional_Logic_Level_Sensitivity_Test = TrueDigital_Functional_Logic_Level_Sensitivity_Executions = 1Digital_Functional_Fault_Coverage_Test = TrueDigital_Functional_Fault_Coverage_Executions = 1

# These commands apply to the Analog Functional tests:Analog_Functional_Vacuum_Off_Test = TrueAnalog_Functional_Quality_Test = TrueAnalog_Functional_Quality_Executions = 10Analog_Functional_Quality_Report_CPK < 10.00Analog_Functional_Quality_Report_Mean_Not_Centered = 66.67Analog_Functional_Power_Supply_Sensitivity_Test = TrueAnalog_Functional_Power_Supply_Sensitivity_Executions = 1Analog_Functional_Power_Supply_Sensitivity_Positive_VariatAnalog_Functional_Power_Supply_Sensitivity_Negative_VariatAnalog_Functional_Speed_Sensitivity_Test = TrueAnalog_Functional_Speed_Sensitivity_Executions = 1Analog_Functional_Speed_Sensitivity_Positive_Variation = 1Analog_Functional_Speed_Sensitivity_Negative_Variation = 1Analog_Functional_Logic_Level_Sensitivity_Test = TrueAnalog_Functional_Logic_Level_Sensitivity_Executions = 1Analog_Functional_Fault_Coverage_Test = TrueAnalog_Functional_Fault_Coverage_Executions = 1

© Agilent T 9-21

Chapter 9

ation from the original testplan. This es the vacuum well information and all test

utines.

nctionality of testmain_bdg is shown in -4.

...



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

� Informincludsubro

The basic fuExample 9

Example 9-4

call Initialize ! initialize variablescall Get_BDG_specifications ! obtain the test parametersload boardtesthead is 1unpoweredcall Vacuum_well ! execute the vacuum well iscall Characterize ! learn the small capacitorscall Tests ! execute all tests

The subroutines in testmain_bdg are shown in Example 9-5.

© Agilent T 9-22

Chapter 9

em errorerroreanup and stopiate message

s

t testsit, digitaltional testsit, digitalional test

d

opy it to

py it to



Example 9-5

sub Fatal ! call The_End without a systsub Sys_Err ! call The_End with a systemsub The_End ! print error information, clsub Power_Supply_Failure ! call Fatal with the approprsub Initialize ! set global variablessub Tests ! call all test subroutinessub Pins_bdg ! execute all pins testssub Pre_Shorts_bdg ! execute all pre_shorts testsub Shorts_bdg ! execute all shorts testssub Analog_Incircuit ! execute all analog incircuisub Test_bdg ! execute all digital incircu

! functional, and analog funcsub Test ! execute one digital incircu

! functional, or analog functsub Prt ! print a message to the CRTsub Vacuum ! control the vacuumsub Vacuum_cycle ! cycle vacuumsub Powered ! execute powered or unpoweresub Start_log ! set up data loggingsub Start_report ! set up the report filesub End_report ! close the report file and c

! another filesub Start_print ! set up the print filesub End_print ! close the print file and co

! another file

© Agilent T 9-23

Chapter 9

Test C t Coverage on a Standard Testplan Coverage on a standard testplan:

ur fixture on the testhead.

re it is locked. (It is not necessary to have a the fixture, because no vacuum is applied.)

our board directory.

shbutton Debug.

ad boardbug board

e a Test Coverage Report.

the main menu, click Macros.

Test Grader Macros.

Generate Test Coverage Report.

Test Coverage in a BT-BASIC window, see ntax and options for the verify device

age statement in the Syntax Reference.



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

NOTEThe 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 TesTo run Test

1 Place yo

Make suboard on

2 msi to y

3 Start Pu

Execute:lode

4 Generat

a From

b Click

c Click

NOTETo runthe sycover

© Agilent T 9-24

Chapter 9

ard for a report, then repeat the process for other boards as desired.

r (or break) occurs, the testplan.cov file his and prevents a new report from being d. An error message reminds you that you

imply edit testplan.cov that is in the IC window. Instead, you must edit the n file. (See Running Test Coverage on a Testplan on page 9-25.)

he report file, testcoverage.rpt.

reated by comparing devices that failed (in coverage_fail.dat file) to the board in board.o. For panelized boards, only the n the board(s) selected are considered (as

d in step 2). Any device that has failed is ed tested. (See Interpreting the Test e Report on page 9-26.)

s the intermediate files testplan.cov and erage_fail.dat.

vents the directory from becoming cluttered porary files.

ge does not alter any standard files in the tory. You can set up the standard backup ne, unnumbered, or numbered) in the e using the TestCoverage.BackupLevel: esired. This allows you to automatically

testcoverage.rpt file.



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 boas many

If an errodetects tcompletecannot sBT-BAStestpla

Custom

3 Creates t

This is cthe testtopologydevices oexplaineconsiderCoverag

4 Removetestcov

This prewith tem

Test Coveraboard direcoptions (no.hp3070 filresource if dback up the

© Agilent T 9-25

Chapter 9

e a Test Coverage Report.

the main menu, click Macros.

Test Grader Macros.

Generate Test Coverage Report.

all unlink statements.

you have already run the macro, it is on the BT_BASIC command line (you may reak it first if it is running, or use the recall y if it is not visible).

t of commands, delete all unlink statements stplan.cov and testcoverage_fail.dat

not removed. (There is more than one unlink Make sure you remove them all.)

the modified macro.

xecute key, or press Return. This generates stplan.cov from the testplan file and

e the testcoverage_fail.dat file.

rs occurred and the testcoverage.rpt as generated, you can look in this report and stcoverage_fail.dat file to see which ests were run.



Running Test Coverage on a Custom TestplanUnder 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 Generat

a From

b Click

c Click

2 Remove

Becauseavailablehave to bminus ke

In the seso that tefiles are per file.

3 Execute

Use the ea new teruns it.

4 Examin

If no erroreport win the tetype of t

© Agilent T 9-26

Chapter 9

e, we recommend you do not just save a he edited testplan (from step 6), as it may to date the next time you run Test

e. For example, if you comment out a test in testplan, your old edited testplan does ct this. Rather, we recommend you make a haps in the original testplan) of the lines to be edited for Test Coverage.

plan.cov file contains the est_Coverage variable. This variable is set stplan.cov. This lets you put branches in tplan based on this variable (for example, g_Test_Coverage then ...). Any not set to a value defaults to 0, so your n works correctly for normal production ting.

g the Test Coverage Reportile testcoverage.rpt is located in the directory. It contains a single-page summary wed by a details section.

that are marked as replaceable are in the report, except testpoints (defined as onnectors marked NT � no test � in he replaceable attribute in board.o for a ally is only a concern for Part Description

r example, a resistor pack device may be laceable but each individual resistor tested



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.

Thereforcopy of tnot be upCoveragthe new not reflenote (perthat need

The testDoing_T

to 1 in teyour tesif Doin

variable testpla

board tes

InterpretinThe report flocal board section follo

All devicesconsidered single pin cboard.o). Tdevice normdevices. Fomarked rep

© Agilent T 9-27

Chapter 9

anelized boards, only the board number(s) be tested are considered.

ons in Table 9-3 help you understand how Coverage percentages are calculated:

ection provides fast facts about your board, e:

e test coverage percentage: Both without ith bypass capacitors. This is the bottom line er.

upply nodes.

as tested.re called parallel tested only and are not rate test).

name as the device is reported from either a pin is reported as open).

then the failure information for the it is replaceable).



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 pselected to

The definitiDevice Test

NOTEAgilent Polarity Check failures do not count as tested or untested. In addition, Boundary Scan tests, open jumpers, and switches are counted as untested.

Summary SThis sectionincluding th

� Devicand wnumb

Table 9-3 Device test coverage definitions

Term Definition

Bypass capacitor Any capacitor with both pins connected to power s

Parallel tested only devices

When devices are tested in parallel:� The base device reported as failing is counted� All other devices reported as being in parallel a

counted as tested (unless they fail from a sepa

Tested device Any device for which a failure with the exact samenormal test or an Agilent TestJet test (at least oneIf a non-replaceable device is reported as failing, REPLACE DEVICE: part name is used (assuming

© Agilent T 9-28

Chapter 9

e in the testplan. NOTE: the first test tement encountered is used (except if it is in characterize subroutine).

FAIL indicates device test statement was nd uncommented in the testplan (yet the

vice did not fail). Also printed is any mment found at the end of the line in the tplan. NOTE: the first test statement countered is used (except if it is in the aracterize subroutine).

LLTEST in testorder indicates the device s marked nulltest in the testorder file.

in board only for Part Description Library vices that do not have sub devices (children) d were not listed above.

es tested in parallel only (except bypass itors). Lists devices that do not have their tand-alone test, but are only reported in el with another device. This list does not e bypass capacitors. The failing device

it is in parallel with is also listed.

ss capacitors tested in parallel only. Lists s capacitors tested in parallel only, along oth node names and the failing device name hich it is in parallel.

es tested by Agilent TestJet only. Lists ctors and pin libraries that are only tested by nt TestJet.



� 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 SectionThis 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

linstathe

� NO

foudecotesench

� NU

wa

� NT

dean

� Deviccapacown sparallincludname

� Bypabypaswith bwith w

� DevicconneAgile

© Agilent T 9-29

Chapter 9

Cover ore information on Coverage Analyst, see ilent 3070 Test Program Coverage Analyst

are Documentation which can be accessed the Help menu of the Coverage Analyst



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

NOTEFor mthe AgSoftwfrom GUI.

© Agilent T 10-1

In this sion Tool is also used to transfer board etween 3070 controllers with same or

erating systems:

to MS Windows

indows to UNIX

indows to MS Windows (when board ories are in different path locations on ent controllers) See the Advice on page for why UNIX to UNIX transfers are not mended.)

processing editing will be required if:

ries are not contained within (local to) the directory.

files outside the board directory or ENT3070_ROOT/standard directory are ed.

tandard peripherals not defined in MS ows have been used in UNIX files or vice .


10101010 Agilent Conversion Tool

chapter... � Running the Conversion Tool, 10-4

� Troubleshooting Problems, 10-38

� What the Conversion Tool Does, 10-42

� Post-Conversion File Cleanup, 10-52

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.

NOTEThe 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 Converdirectories bdifferent op

� UNIX

� MS W

� MS Wdirectdiffer10-19recom

Some post-

� Libraboard

� Other$AGIL

requir

� Non-sWindversa

© Agilent T 10-2

Chapter 1

inish reading this chapter, you should be orm the following tasks:

ert a board directory from an UNIX ller to an MS Windows controller.

ert a board directory from an MS Windows ller to an UNIX controller.

a board directory between MS Windows llers when the board directories are on

ent drive letters or paths (for example C:\ to

e and resolve issues resulting from ences between UNIX and MS Windows ting systems and 3070 software directory ures.

tesbegin using this chapter, you should:

a board directory that contains a testplan, and appropriate files that have been iled on software revision 3070 04.00pa or

le to run IPG Test Consultant and fix errors. ore information, see Chapter 1, Agilent IPG onsultant..


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

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

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

NOTEFor simplicity, the terms �directory� or �subdirectory� are used for both UNIX and MS Windows in this chapter. �Folder� and �subfolder� could have been used.

ObjectivesWhen you fable to perf

� Convcontro

� Convcontro

� MovecontrodifferD:\).

� Locatdifferoperastruct

PrerequisiBefore you

� Havetests, complater.

� Be abFor mTest C

© Agilent T 10-3

Chapter 1

st Consultant to completion on the 70_ROOT/boards/class_bd. It will pass nsultant after it compiles the libraries, etc.

ENT3070_ROOT/standard/tutorial

s_bd directory will NOT pass IPG Test ltant until moved to the correct location and est Consultant is run. You may use IPG Test ltant, Management, Copy/Move Board

tory, then modify the permissions, if needed. ore information, see Chapter 1, gement Menu.



� 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 MaterialsTo accomplish the tasks in this chapter, you will need:

� A 3070 board test system with a testhead with 3070 04.00pa software (UNIX or MS Windows)

� A functional board directory compiled using 3070 04.00pa software (UNIX or MS Windows)

Practicing a ConversionIf 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

Run IPG Te$AGILENT30

IPG Test Co

NOTE$AGIL

/clas

ConsuIPG TConsuDirecFor mMana

© Agilent T 10-4

Chapter 1

RunniConve

files are modified directly. It also adds the e common delimiter statement to the config file.re for ECO: Takes an interoperable board ory, flips the source text files, and modifies w files in preparation for an ECO.og: Used to view resulting log files or other les.: Aborts the Package or Extract process e it has completed.

tails what the Conversion Tool is doing, see of the differences between the two operating cribed in the section Relevant Differences NIX and MS Windows Operating Systems 43.

onversion Tool operates in a copy of the directory. It does NOT modify an existing directory during Package, Make operable, or Prepare for ECO. During ct, if a board directory of the same name , it can replace the board directory after pting the user for approval.



ng the rsion Tool

NOTESoftware revision 3070 04.00p 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 theenabl

board� Prepa

directthe ra

� View Ltext fi

� Abortbefor

For more dea summary systems desBetween Uon page 10-

NOTEThe CboardboardInterExtraexistsprom

© Agilent T 10-5

Chapter 1

the Conversion Tool icon on the MS ows desktop.

Start, Programs, Agilent3070, Conversion

T-BASIC Window, type executel.ksh &” (Not case sensitive and is run in ckground)

orn Shell window, type ctool.ksh & (Not ensitive and is run in the background)

t Conversion Tool main screen, shown in on page 10-6, will start.



ADVICETo streamline board directory conversion, you may want to use the IPG Test Consultant Management, Clean Up Board Directory, Mark to remove unneeded backup files.

NOTEBinary files are not packaged or converted. (<filename>.o, etc.) They are recreated during the Extract process.

Start the Conversion ToolIn 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:

� ClickWind

� ClickTool

� In a B“ctoo

the ba

� In a Kcase s

The AgilenFigure 10-1

© Agilent T 10-7

Chapter 1

Packa is not a Conversion Tool batch mode ble because IPG Test Consultant should be ring the conversion process and IPG Test ltant is not a batch mode tool.

testplan file, user modifications to the an are preserved. Path names and file names odified to be operating system specific

OT run the Conversion Tool against a copy r board directory with a different board

. For example, don�t copy <BoardName> to

oardName>. The board name of the ds/<BoardName> is referenced in the re/fixture file and is used during IPG onsultant program execution. If a re.o exists, IPG Test consultant does not

ile the /fixture/fixture file and create a ixture.o file.

sion Tool will use the $AGILENT3070_ROOT t variable when converting board



ge Locate the Board Directory1 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.

NOTEThereavailarun duConsu

NOTEIn thetestplare m

NOTEDo Nof youname<NewB

/boarfixtu

Test Cfixtu

compnew f

The Converenvironmendirectories.

© Agilent T 10-8

Chapter 1

ist - Not functional

etails - Not functional

OT select anything except a directory which ins board files and directories. If you do, a ing message will result which says Thisnot appear to be a valid board

tory, continue? Normally, click Cancel.

ctory can be packaged, but if the board does not compile with IPG Test Consultant, esults will also not compile.

e <BoardName> subdirectory. Click Package. IPG Test Consultant dialog box shown in 0-3 will be displayed.



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.

To rename this folder in UNIX use the mv

NewFolder <BoardName> command and in MS Windows use the File Manager Rename command.

NOTESpaces in file or directory names in board directories are not allowed.

� L

� D

NOTEDo NcontaWarndoes

direc

Any diredirectoryExtract r

2 Select thThe RunFigure 1

© Agilent T 10-10

Chapter 1

ibes how to run the Conversion Tool without Test Consultant during packaging.

un IPG Test Consultant

onfident that the board directory will pass nsultant, click No.

No, a second dialog box indicating that there Test Consultant regeneration problems, and ay not build correctly on the destination appear as shown in Figure 10-4.

Are you sure you don�t want to run IPG Test Consultant?

o continue or No to stop the Conversion select Yes:

y subdirectory in the board directory directory will be created and a copy of ame> will be copied into it.



Figure 10-3 Run IPG Test Consultant?

Check Board Directory Status?Even if you have run IPG Test Consultant using software revision 3070 04.00pa, 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

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 10-12. Skip the following section,

which descrrunning IPG

No - Do Not R

If you are cIPG Test Co

If you clickmay be IPGthe board msystem will

Figure 10-4

Select Yes tTool. If you

A temporarmigration_

the <BoardN

© Agilent T 10-11

Chapter 1

Packaged board file location and name



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 10-5. 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 10-12.

Figure 10-5

© Agilent T 10-12

Chapter 1

PG Test Consultant

ng the Conversion Tool, it will be You will need to navigate in IPG Test



Figure 10-6 Package complete screen.

Packaging without running IPG Test Consultant is complete; go to Transfer on page 10-19.

How to Run I

When runniinteractive.

© Agilent T 10-13

Chapter 1

Consultant will check the status of the ectory. You may have to bring the IPG Test nt screen to the front to view the IPG Test nt Messages screen.

e board directory doesn�t have errors. As Figure 10-9 on page 10-16, the result e:

ACTIONS WERE PERFORMED BY IPG ONSULTANT ***

ilent IPG Test Consultant by selecting File,

p 5 page 10-17.



Consultant to the directory where the ../<BoardName>resides. See Chapter 1, Agilent IPG Test Consultant, for navigation information.

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

1 Select the $AGILENT3070_ROOT/boards/<BoardName>.migration_backup/<BoardName>

directory, as shown in Figure 10-7 on page 10-14.

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

Select Actions, Begin Batch Development.

3 IPG Testboard dirConsultaConsulta

Verify thshown inshould b

*** NO TEST C

4 Close AgExit. Go to ste

© Agilent T 10-17

Chapter 1

age 10-34, for more information on how to e <BoardName>_package.log file.

will appear. The dialog box will go away ng is complete.

dialog box will appear. While the Progress yed, you can Abort. If you abort Packaging, art Packaging from the beginning.

aging is complete, the <BoardName>.cvt ritten in the directory one level up from the e> directory being packaged. When the

ctory paths are used, this will be the /boards



5 If IPG Test Consultant returned errors or performed any compiles, the package result probably has problems as described in Figure 10-10.

You can review the results of the packaging process in the <BoardName>_package.log file. See View

Log on preview th

Figure 10-10 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 patiencewhen copyi

A progress bar is displayou must st

When Packfile will be w/<BoardNam

default diredirectory.

© Agilent T 10-18

Chapter 1

Relevant Differences Between UNIX and ws Operating Systems on page 10-43.



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 10-11. 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 10-12.

Figure 10-11 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 system- dependent changes required to address the differences

described inMS Windo

© Agilent T 10-19

Chapter 1

TransfE the Conversion Tool can be especially l for transferring files between MS Windows llers where the 3070 software is on different rives or board directory paths.

ment controller has the MS Windows 3070 ater software on one drive C:/Agilent3070 ction system has it on another drive, for /Agilent3070, the Extract function has the f determining where the 3070 software is g the $AGILENT3070_ROOT environment d extracting correct file paths.



er Transfer is used to transfer <BoardName>.cvt files to another 3070 controller with the FTP Server enabled.

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

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.

ADVICUsingusefucontrohard d

If a develop04.00pa or land a produexample D:capability oloaded, usinvariable, an

© Agilent T 10-20

Chapter 1

to the board directory.

t the desired <BoardName>.cvt file, as Figure 10-12.



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

3 Highlighshown in

Figure 10-12 Select the <BoardName>.cvt file for transfer

© Agilent T 10-21

Chapter 1

FTP login dialog box

e data transfer is complete, the FTP session out of the destination controller.

message will be displayed if transfer errors transfer errors occur, contact your system rator.



4 Click FTP. The FTP dialog box, shown in Figure 10-13 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 10-13

5 When thwill log

An erroroccur. Ifadminist

© Agilent T 10-22

Chapter 1

a 3rd party software package on the MS ows machine (Reflection FTP, Hummingbird are, etc.). With MS Windows 2000, FTP can abled.

ing a DAT tape on the UNIX machine and ing it on the MS Windows machine or vice . A DAT tape drive is included on the MS ows controller in a 3070 testhead.

s for moving files between MS Windows without the FTP server enabled include:

the FTP put command on the source ine to an interim UNIX machine, then using P get command on the destination MS

ows machine to pull the file.

network file sharing, i.e., Windows rer, Tools, Map Network Drive.

hardware solutions including DAT tape, zip CDs, etc.

ng files as a mail file attachment (verify that e size is acceptable)

EdName>.cvt files can be very large. Choose

o transfer them carefully and always use format.



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 3070 04.00pa 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.

� UsingWindsoftwbe en

� CreatrestorversaWind

Alternativecontrollers

� Usingmachthe FTWind

� UsingExplo

� Usingdisks,

� Sendithe fil

ADVIC<Boar

how tbinary

© Agilent T 10-23

Chapter 1

Extrac ssful automated conversion assumes that lt locations for various elements, files, and ories have been adhered to by board opment programmers. If modifications to elements have occurred, converting the files equire more manual intervention.

sion Tool compiles in two stages:

s that are designed to preserve existing board re data. These compiles are always done and rs from these compiles will appear in the ion Tool window, shown in Figure 10-20 on 31.

ompile errors that occur during the 1st stage dversely affect 2nd stage compiles.

T-BASIC window doesn't close that tes a compile error; fix the problem before uing.

e step 1 compiles are done, IPG Test ant is started and will handle all of the other g. IPG Test Consultant will report errors compiles it is responsible for.



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

NOTESuccedefaudirectdevelthese will r

The Conver

1 Compileand fixtuany erroConverspage 10-

NOTEAny cwill a

If a Bindicacontin

2 When thConsultcompilinfrom the

© Agilent T 10-24

Chapter 1



NOTEAll Extract compiles MUST run correctly, or have the errors corrected during the Extract, for the board directory conversion to be successful.

NOTEIn the testplan file, user modifications to the testplan are preserved. Path names and file names are modified to be operating system specific

Run Extract1 Click Extract on the Agilent 3070 Conversion Tool

main screen, shown in Figure 10-1 on page 10-6.

2 Select the desired <BoardName>.cvt, as shown in Figure 10-14 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 T 10-26

Chapter 1

ControlXT Card Warning

ent IPG Test Consultant main screen, shown e 10-18 on page 10-29 will be displayed.

to the directory where your board files ormally boards/<BoardName>. Select Develop Board Test. Test Consultant Comprehensive ation screen, shown in Figure 10-19 on 30 will be displayed.

at you are in the correct directory.

tions, Begin Batch Development. If you ou may select Begin Interactive Development rough each section.

Test Consultant Message window will he results of IPG Test Consultant, while information to the summary file in the <BoardName> directory.



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

NOTEThe required boards need to be installed or the config file corrected to match existing required hardware.

Figure 10-15

4 The Agilin Figur

Navigatereside, nActions,

5 The IPGRegenerpage 10-

Verify th

Select Acdesire, yand go th

An IPG display tsending boards/

© Agilent T 10-27

Chapter 1

Restore the testorder file

tract is complete, the location and board log box will be displayed, as shown in 0-17. Select OK.

tract is complete, the <BoardName> will be written in the directory one level m the subdirectory where the ame>.cvt is located. The default location is rds subdirectory.

lent Conversion Tool will also display ion about the Extract process, and show board directory extraction was completed, e stamp, as shown in Figure 10-20 on

31.



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

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 10-16 on page 10-27.

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.

Figure 10-16

8 When Exname diaFigure 1

When Exdirectorydown fro<BoardN

the /boa

The Agiinformatwhen thewith a timpage 10-

© Agilent T 10-28

Chapter 1



Figure 10-17 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 10-34.

© Agilent T 10-32

Chapter 1

Make Step 3: Check board directory status?.

Conversion Complete Note with file path



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 10-21

Figure 10-22

© Agilent T 10-33

Chapter 1

Prepa



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

NOTEThe 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 T 10-34

Chapter 1

View L other file types, select Files of type: All

*.*) in the <BoardName> directory. Of r interest to understanding the conversion re:

and summary~ (a summary and summary f the IPG Test Consultant actions).

n (UNIX and MS Windows) and n.diff (on UNIX)

ecommend that all other text files be ed using BT-BASIC.



og 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 10-23 on page 10-35.

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

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.

3 To view Files (

particularesults a

summary

backup o

testpla

testpla

NOTEIt is rreview

© Agilent T 10-36

Chapter 1



NOTEThe Text Editor opened by View Log is operating system-dependent.

UNIX: Text Editor

MS Windows: Notepad

As shown in Figure 10-24 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 T 10-38

Chapter 1

TroubProble

ssful automated conversion assumes that lt locations for various elements, files, and ories have been adhered to by board opment programmers. If modifications to elements have occurred, converting the files equire more manual intervention.

ving issues related to boards/<BoardName>rsion requires 3070 user training and an standing of the functionality of IPG Test ltant. It may also require an understanding board being converted, as well as any mization which has occurred during board opment.

w the Relevant Differences Between and MS Windows Operating Systems on

10-43, and keep them in mind as problems dressed. Because of the complexity of some s, and the flexibility of the Agilent 3070 are, not all conversion problems can be ssed by the Conversion Tool software.



leshooting ms

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.

NOTEIPG Test Consultant using 3070 04.00pa 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.


NOTESuccedefaudirectdevelthese will r

NOTEResolconveunderConsuof thecustodevel

General� Revie

UNIXpageare adboardsoftwaddre

© Agilent T 10-39

Chapter 1

ectory you are viewing which other files modified.

e original UNIX system, change the source file names to have unique file names

ut using case sensitivity, and verify that IPG onsultant compiles files correctly.

h for /dev/* files in the <BoardName>.cvt at have meaning in UNIX, but are not able to MS Windows. Resolve them by ng to a standard peripherals on the MS ows controller.

ts not found during cTool.ksh and IPG Test ltant execution will display an Error dialog

howing the file name and expected path, as n in Figure 10-25 on page 10-40. They can in two situations:

ring startup when the Conversion Tool looks IPG Test Consultant, Perl and migrate.pl.

they are not found and the user cannot find files the Conversion Tool exits.

e the file either on the 3070 MS Windows r on the UNIX system, and put it in the on displayed in the dialog box.



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 dirneed

On thsystemwithoTest C

� Searcfile thapplicpointiWind

Startup� Scrip

Consubox sshowoccur

� DuforIf the

LocatCD, olocati

© Agilent T 10-40

Chapter 1

rm login, password, hostname or IP address, ath on the destination system.

that FTP works correctly from the Korn or Unix Shell window using command line ommands.

that the FTP server is enabled on the ation MS Windows 2000 controller. See you m Administrator.

w the ../boards/<BoardName>ersion.log on the destination system, g for errors or path names that may give to problem.

ully review the IPG Test Consultant errors in mmary file. They errors may give a clue

the source of problems.

r message indicates it cannot find files, then

rm the location of the libraries in the s/<BoardName> under �Library Options� and the path is correct.



You may try reinstalling the software, or you can call your Agilent service and support representative.

Figure 10-25 Startup - missing files

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.

Transfer� Confi

and p

� VerifyShell FTP c

� VerifydestinSyste

Extract� Revie

/conv

lookinclues

� Carefthe suabout

If a compile

� Confiboard

exists

© Agilent T 10-41

Chapter 1

socal_lib program may be used to move

rary files into the boards subdirectory. This ty searches the library paths defined in the nd copies the library sources and objects to a ry called library. Its location is:

t/hp3070/contrib/bin/make_local_lib

s: 3070/contrib/bin/make_local_lib.exe

ib programs are used at the customers own gilent assumes no liability for their use.



� 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

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

Library pathThe make_lexternal libcontrib utiliboard file alocal directo

UNIX: /op

MS Windowc:/Agilent

NOTEContrrisk. A

© Agilent T 10-42

Chapter 1

What tConveDoes

Test Consultant has compile problems g the packaging or extraction process, *.o

ay not be created, and the board testplan ot execute properly. Each board directory

be converted individually.

pting batch mode processing of multiple files, including running IPG Test Consultant ause problems.



he rsion Tool


NOTEIf a board directory has not run through IPG Test Consultant with software revision 3070 04.00pa or later, it may not convert correctly. Run IPG Test Consultant on the source system board directory before attempting conversion.

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

NOTEIf IPGdurinfiles mmay nmust

NOTEAttemboardwill c

© Agilent T 10-43

Chapter 1

Variable

ith 3070 software revision 04.00pa, the t variable $AGILENT3070_ROOT is used to rtability between UNIX, MS Windows, and Windows systems with the software on

ives.

formation about environment variables, see stering Agilent 3070 Systems (Unix), The tory Environment Variable.

values of the $AGILENT3070_ROOT on ware loads are:

: AGILENT3070_ROOT = /var/hp3070

indows: AGILENT3070_ROOT = gilent3070

ontrollers /hp3070 is aliased to 0, so they are the same path.

e that was in /opt/... in UNIX, on MS hen using the default MS Windows setup, is er the <value in $AGILENT3070_ROOT>.

load the 3070 software on the MS Windows r may change the directory path where the installed during the installation process. That d, non-default directory path, is stored in the 3070_ROOT environment variable. That the environment variable in source files,

ding path, critical to having portable board



Relevant Differences Between UNIX and MS Windows Operating SystemsThe 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 PathsOn 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

Beginning wenvironmenenhance pobetween MSdifferent dr

For more inthe AdminiRoot Direc

The defaultfactory soft

� UNIX

� MS WC:/A

On UNIX c/var/hp307

The softwarWindows, wdirectly und

When usersOS, the usesoftware is user selecte$AGILENTmakes usingnot hard codirectories.

© Agilent T 10-44

Chapter 1

ally the needed subdirectories are diately below the board directory and are rted correctly; however, this programming ce may not have been followed by all board ammers.

you will need to hard code these paths after rsion or move the external files into the directory.

ard paths are detected by the Conversion e name, the line number and path will be in ion.log.

rsion, search for �!cTool� in the board locate occurrences of non-standard paths.

standard hardcoded paths exist, such as in vi and setup.avi+pvi files, example paths IX and MS Windows may be in the... /... example files.

ples where paths may be hard coded can be earching for file id, file name or directory online User manuals.



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.

NOTENormimmeconvepractiprogr

If so, conveboard

If non-standTool, the filthe convers

After convedirectory to

Where non-the setup.afor both UN/standard/

Syntax examlocated by sname in the

© Agilent T 10-45

Chapter 1

re different files or directories in UNIX. ferred to MS Windows, they would ne another, with the contents being the last or moved.

s preserves the uppercase and lowercase on) letters in file and directory names, both eated in and transferred to MS Windows, but the uppercase/lower case letters.

seful to understand which case on) a file name or directory name occurs . Both Korn Shell and Command Prompt

ill display the uppercase/lowercase letters.

w the case (capitalization) on the MS ows system use the Korn Shell (Start, ams, Agilent3070, Korn Shell). The

and Prompt (MS DOS) window will also y the case but its use is not recommended.

sion Tool treats identically spelled file llows:

first occurrence of class_bd = MS ows class_bd

2nd occurrence of Class_BD = MS ows Class_BD1.



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 aWhen transoverwrite oone copied

MS Window(capitalizatiin names crdoes not use

It may be u(capitalizatifirst in a filewindows w

NOTETo vieWindProgrCommdispla

The Convernames as fo

� UNIXWind

UNIXWind

© Agilent T 10-46

Chapter 1

o test the DUT. See Chapter 1, iple-Board Tests & Fixtures, for more s.

ries defined as part descriptions use : (colon) device file name. (See Chapter 7, Flash Programming Steps, for examples.

onversion Tool packages a board directory ames are renamed with the _@_ (at)underscore) character string. During destination operating system determines ter replaces the _@_ characters as follows:

<BoardName>.cvt file 2:r3 becomes 3. During extract:

IX: 2:r3

Windows: 2%r3

created file names containing a % sign, this ome confusion, but will compile on either example:

nal file name = 0/boards/Test:%failure

g it back to UNIX this would become 70_ROOT/boards/Test::failure

rsion to MS Windows this name would

70_ROOT/boards/Test%%failure.



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

ADVICEUnique 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 tMultdetail

� Librain theOBP

When the Cillegal file n(underscoreExtract, thewhat charac

In the2_@_r

� UN

� MS

If you havemay cause ssystem. For

UNIX origi/var/hp307

After movin$AGILENT30

After convebecome $AGILENT30

© Agilent T 10-47

Chapter 1

70_ROOT/dev/ directory for compatibility

e communication is managed by the , Enterprise UNIX Development on oftware (TM).

ot all, of the GPIB devices which were UNIX are available in the 3070 04.00pa ftware release. These GPIB devices, which

n Table 10-1 on page 10-48, are in different cations on the MS Windows controller.



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

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

$AGILENT30

reasons.

GPIB Devices

GPIB devicNutCrackerWindows S

Some, but nsupported inWindows soare shown idirectory lo

© Agilent T 10-48

Chapter 1

counter

dmm

dmm_ref

gpio1

hpib1

hp3488

null

ps0

ps1

ps10

ps11

ps2

ps3

ps4

ps5

ps6



..

Table 10-1 GPIB device names and locations

File Name (/dev/...) UNIX MS Windows

counter /dev/counter $AGILENT3070_ROOT/dev/

dmm /dev/dmm $AGILENT3070_ROOT/dev/

dmm_ref /dev/dmm_ref $AGILENT3070_ROOT/dev/

gpio1 /dev/gpio1 $AGILENT3070_ROOT/dev/

hpib1 /dev/hpib1 $AGILENT3070_ROOT/dev/

hp3488 /dev/hp3488 $AGILENT3070_ROOT/dev/

null /dev/null $AGILENT3070_ROOT/dev/

ps0 /dev/ps0 $AGILENT3070_ROOT/dev/









© Agilent T 10-49

Chapter 1

ps7

ps8

ps9

scope

synth






scope /dev/scope $AGILENT3070_ROOT/dev/

synth /dev/synth $AGILENT3070_ROOT/dev/

Table 10-1 GPIB device names and locations (continued)

File Name (/dev/...) UNIX MS Windows

© Agilent T 10-50

Chapter 1

he COM port number.

and /dev/com2 do not appear in the /dev ut are managed by the MS Windows stem.

trip printer (rpr1), because it is used in every testplan, is converted by the

ersion Tool. The other input/output devices equire modifications to the testplan.

ansparent to user)

re n is assigned by



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 t

/dev/com1 directory, boperating sy

NOTEThe snearlyConvmay r

Table 10-2 Input/Output Devices

Device type UNIX MS Windows (tr

strip printer /dev/rpr1 /dev/com/2

Serial MUX Box /dev/ttym(xx) where xx is the box and the port

/dev/com/3..10

JOT /dev/JOT_PLC/dev/JOT_BCR_P0/dev/JOT_BCR_P1

/dev/com/4/dev/com/5/dev/com/6

bar code reader /dev/bcr /dev/com/n (whethe user)

© Agilent T 10-51

Chapter 1

ansparent to user)

ws Adapter Part Number

01

07

ble



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.

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

Table 10-2 Input/Output Devices (continued)

Device type UNIX MS Windows (tr

Table 10-3 RS232 MUX adapters

Cable adapter type UNIX Adapter Part Number MS Windo

RJ45 -> DB9M E9970-63200 E9970-632

RJ45 -> DB25M E4000-62105 E4000-621

RJ45 -> DB25F E4000-62106 Not availa

© Agilent T 10-52

Chapter 1

Post-CFile Cl

ds/<BoardName>_compress.tar.z(x) if ts

rdName>/tmp_migration_board if it

ultant Backup Files source and destination controller there are in ~, which are backup files. If disk space is sider whether the backup files are still r more information, see Chapter 1, nt Menu.



onversion eanup

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 ControllerIf 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 ControllerFiles that can be removed include:

� <BoardName>.cvt

� /<BoardName>/conversion.log

� /boar

it exis

� /<Boa

exists

Test ConsOn both thefiles endingneeded, conrequired. FoManageme

© Agilent T 11-1

bility

In thisg this chapter, you should be able to:

lop interoperable runtime tests for both ® and MS Windows® platforms,

to use the common delimiter (%),to use the enable common delimiter ent in the board config file, to use the Agilent Conversion Tool for perability, to process Engineering Change Orders s) for interoperability between UNIX and indows test systems.

tese familiar with Agilent 3070 board test t processes before developing interoperable

nd Fixture Developmentnt Conversion Tool

echnologies 2002, 2003 Test Development Tools 06/2003

11111111 UNIX and MS Windows Interopera

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, 11-10

� Interoperability Use Models, 11-11

ObjectivesAfter readin

� DeveUNIX

� How � How

statem� When

intero� How

(ECOMS W

PrerequisiYou must bdevelopmentests.

� Test a� Agile

© Agilent T 11-2

Chapter 1

Et the desired operating system before ning test development. If developing on with the potential for tests to run on MS

ows, test development should be completed nabling interoperability.

nteroperabilitynning board test development, reference on page 11-3 to help you decide how and elop for interoperability


1: UNIX and MS Windows Interoperability

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

NOTESince Interoperability is a new feature, interoperable tests are not backward compatible with software revisions prior to 3070 05.20p. Board tests developed on software revision 3070 05.20p or newer will not run on testheads using older software revisions.

Beginning with software release 3070 05.20p, 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.

ADVICTargebeginUNIXWindafter e

Enabling IBefore begiTable 11-1 when to dev

© Agil 11-3

Chapt

ow I get there

pgrade to 3070 05.20 or later. The enableommon delimiter statement in board onfig file is optional. Do not use it if you

ntend to use the board on pre- B.03.20 release ystems.

pdate to 3070 05.20 or newer. Use Makenteroperable command in Agilent onversion Tool.

dd enable common delimiter statement o board config file

Upgrade to 3070 05.20 or later. Use Makenteroperable command in Agilent onversion Tool.

ll MS Windows systems will be interoperable. dd enable common delimiter statement

n board config file to allow development, e.g. COs, on UNIX systems; the Prepare for ECO

unction will also be needed then.

ent Technologies 2002, 2003 Test Development Tools

er 11: UNIX and MS Windows Interoperability

Table 11-1 3070 Test Development Decision Matrix

I have a board from: I am Targeting: H

UNIX software releases B.03.60 through 3070 05.00p

UNIX only Uc

c

is

Interoperable on UNIX and MS Windows

UI

C

UNIX at software release 3070 05.20p or later

Interoperable on UNIX or MS Windows

At

MS Windows pre-software release 3070 05.20p


I

C

MS Windows at software release 3070 05.20p or later


AAiEf

© Agilent T 11-4

Chapter 1

Use ofConve

E making a UNIX board interoperable, use ke Interoperable feature in the Agilent

ersion Tool. Do not attempt conversion ally. You may miss files that require rsion.

g Change Orders (ECOs)pment and ECOs for a given board on either stem is made simpler with the Agilent

Tool. Utilize the Agilent Conversion Tool to board tests before performing the ECO. See erforming an ECO

gilent Conversion Tool is required for an if the board was developed on an operating

different than the one utilized to complete O.



the Agilent rsion Tool

Beginning with software release 3070 05.20 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.

NOTEVISTA communications test software is not supported by the Agilent Conversion Tool

ADVICWhenthe MaConvmanuconve

EngineerinTest develooperating syConversionconvert the Chapter 5, P

NOTEThe AECO systemthe EC

© Agilent T 11-5

Chapter 1

characters must match the development at. The Prepare for ECO function takes an

le board directory, changes the source text line characters as needed, and modifies the preparation for an ECO. This operation is to the platform on which the ECO is to be

al information on file conversion, please see Agilent Conversion Tool.

oard Directories

E you copy a board directory from UNIX to indows and vice versa, the board text files

to be converted using the Prepare for ECO on. Otherwise, IPG Test Consultant will ate errors.

FTP to transfer board directories, only use at. If the board directory is not packaged and mart or ascii ftp, the board object files will

d.



ADVICEDo 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 FunctionThe Agilent Conversion Tool has two new commands - Make Interoperable and Prepare for ECO. The MakeInteroperable 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 FunctionThe 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 system forminteroperabfile end-of-raw files in be done on performed.

For additionChapter 10,

Copying B

ADVICWhenMS Wneed functigener

When usingbinary formyou utilize sbe corrupte

© Agilent T 11-6

Chapter 1

ning with 3070 05.20 software, it is no r possible to generate test objects that will Series I systems using revision A software

.xx).

5.20 or newer software will be able to read revision A software and convert them to

revision. This change is equivalent to the tware revision b statement always being the config file.

ment regarding board.o, IPG Test has a built-in feature that detects when e been moved. In the LIBRARY OPTIONS veloped board pointing to a library path:

070/library/ttl or 3070_ROOT/library/ttl

on time, will have the complete path th if it included an environment variable) DEVICES section of the board.o.

of what the library paths were in the former stem, IPG Test Consultant is looking at the

th stored in board.o. If the board file has ependent library paths (using 3070_ROOT or another environment d the system library objects exist, then the ompile. However, you can indicate IPG Test



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

NOTEBeginlongerun on(A.xx

The 3070 0objects fromthe current enable sof

included in

Another comConsultant libraries havsection a de

C:/Agilent3$AGILENT

at compilati(resolved pastored in the

Regardless operating syabsolute paplatform ind$AGILENTvariable) anboard will c

© Agilent T 11-7

Chapter 1



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 MatrixThe 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 11-8.

© Agilent T 11-8

Chapter 1

Figure 1

Platf

with without with

ion cts le.

N/A

No conversion. WN reads UNIX objects and up-

revs them.

N/A

Board Conversion required - objects not interoperable.

N/ABoard Conversion required - objects not interoperable.

DN/A Interoperable N/A

NOT SUPPORTED

N/A Interoperable

NOT SUPPORTED

N/A

Objects are interoperable

except ":"; requires conversion.

odel N/AObjects up-revved and reformatted

silentlyN/A

Current WN model N/AObjects up-revved and reformatted

silently

DN/A Current WN model N/A

NOT SUPPORTED

N/A Current WN model

N

wiwi

nt time - not runtime

UN

WN05.20re 05.20

W



1-1 UNIX and MS Windows Interoperability Matrix

orm

3070 SW version

part libraries or panel test (: or

%)without with without with without

Common Delimiter %

withoutfunctionality

not applicableCurrent UNIX

modelN/A

No conversion. Objects up-revved.

Current UNIX model

N/ABoard Conversrequired - objenot interoperab

withfunctionality unavailable

N/ACurrent UNIX

modelN/A

No conversion. Objects up-revved.

Current UNIX model

N/A


not applicableNOT

SUPPORTEDN/A

Current UNIX model

N/ANOT

SUPPORTE

enabled (%) N/ANOT

SUPPORTEDN/A

No conversion. UNIX reads "%"s.

N/A

not enabled (:)

N/ANOT

SUPPORTEDN/A

No conversion. UNIX reads ":"s.

N/A


not applicable

Board Conversion required - objects not interoperable.

N/A

UNIX cannot read WN objects. Conversion

required

N/A Current WN m

withfunctionality unavailable

N/ABoard Conversion required - objects not interoperable.

N/A

UNIX cannot read WN objects. Conversion

required

N/A

without functionality

not applicableNOT

SUPPORTEDN/A Interoperable N/A

NOT SUPPORTE

with enabled (%) N/ANOT

SUPPORTEDN/A Interoperable N/A

/A Configuration not applicableEnable common delimiter means I want interoperability

th enabled A board with part libraries or panel test and 'enable common delimiter' (in board config) - uses %th not enabled A board with part libraries or panel test and no 'enable common delimiter' (in board config) - uses : (on UNIX only)

05.20

common delimiter is enabled/disabled at developme

IX

pre 05.20

pre 05.20

05.20

pre 05.20

with

Board Directory From:

p

Bo

ard

to

ru

n o

n:

N

05.20

UNIX

© Agilent T 11-9

Chapter 1

The CDelimi

) as the delimiter. The colon is forbidden in s file names.

g or running interoperable board tests, the mon delimiter statement must be included config file.

-1 shows the use of the enable common

statement in the board config file. See enable (CONFIGURATION) in Syntax or additional information.

1 Add the enable common delimiter statement to the board config file

073 standardress fixturingtjeteltestmon delimiter

e common delimiter statement appears in nfig file, the Agilent Conversion Tool

this and will not perform the package n the board files.



ommon ter Character

NOTEInteroperability 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 3070 05.20p software release, interoperability between UNIX and MS Windows unifies these delimiter characters to a common delimiter - the percent symbol (%).

The Enable Common Delimiter Statement

NOTEIn 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 3070 05.20p. UNIX test development software before release 3070 05.00p uses

the colon (:MS Window

If developinenable com

in the board

Example 10delimiter Chapter E, Reference f

Example 11-

target hp3enable expenable tesenable panenable com...

If the enablthe board corecognizes operation o

© Agilent T 11-10

Chapter 1

UNIX &Windo



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

NOTEAgilent 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 T 11-11

Chapter 1

InteroModel

oard developed on either a UNIX or MS s test system using B.03.80 or newer .

e Agilent Conversion Tool to make the eroperable and prepare if for ECO.

<board_name>_ECO directory and perform modifications.

e testplan.

ard on either a UNIX or MS Windows test run the testplan.

to the ECO Use Case

ent Model without Conversiones the process of choosing a platform and all development on that platform with 3070 wer software. Runtime can be achieved on

or MS Windows without any conversion.

the chosen development platform.

the board and testplan.

e testplan.

board and run on any runtime system.

to the Development Model without



perability Use s

Operator Use CaseThe runtime system can utilize either UNIX or MS Windows operating systems.

1 Login as operator to a UNIX or MS Windows test system with 3070 05.20p software.

2 Load an interoperable board testplan,

3 Run the testplan.

Please refer to the Operator Use Case Diagram

Developer Use Case1 Login to a UNIX or MS Windows test system with

3070 05.20p 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 Case1 Login to a UNIX or MS Windows test system with

3070 05.20p software.

2 Load a bWindowsoftware

3 Utilize thboard int

4 Go to thethe ECO

5 Debug th

Load the bosystem and

Please refer

DevelopmThis describcompleting 05.20 or neeither UNIX

1 Login to

2 Develop

3 Debug th

4 Load the

Please referConversion

© Agilent T 1

P Q R S T U V W X Y Z

ional testst Grader, 9-2

t Grader, 9-2d Directory query box (IPG Test Consultant), 1-18

0-45ltant

aphics Viewer, 2-31 forms, 2-17

t, 2-82-2, 2-3elp, 2-24-2, 9-29 for items, 2-26 in the forms, 2-22 in the menu bar, 2-24 Overview, 2-25 PanelTest, 2-28n check, 2-292-25


Numerics A B C D E F G H I J K L M N O

Index

AActions menu (IPG Test Consultant), 1-7Agilent AutoAnalog Debug, 4-19Agilent Board Consultant, 2-1

Board Graphics Viewer, 8-4Agilent Board Consultant -- See "Board Consultant��Agilent Conversion Tool, 10-1

Extract, 10-23Make Interoperable, 10-32Objectives, 10-2Package, 10-7Post Conversion File Cleanup, 10-52Practice, 10-3Prep for ECO, 10-33Prerequisites, 10-2Running, 10-4Tools & Materials, 10-3Transfer, 10-19Troubleshooting, 10-38View Log, 10-34

Agilent IPG Test Consultant, 1-1Clean Up Board Directory form, 1-17

Agilent Pushbutton Debug, 4-1Alignment Plot (Plot Generator), 5-4

Analog functBoard Tes

Analog testsBoard Tes

Archive Boar

Bback-slash, 1Board Consu

Board Grdata entryFlowcharinvoking,Main formon-item hquitting, 2searchingshortcutsshortcutsusing theusing withverificatioviewport,

© Agilent T 2

Index � Bookshelf� Syntax Reference� Master Index


e, 3-3dit" softkey (f1), 3-12tement, 3-7file9-6, 9-716, 9-6, 9-7 command, 9-7ntry Form (Part Description Editor), 6-9oard Directory form (IPG Test Consultant), 1-19

age, 9-23ing Config command, 9-6ing Testplan command, 9-6the Macros menu (Agilent Pushbutton 21

ith Board Consultant, 2-1Board Test Grader, 9-13

r Macros menu, 4-10ment, 3-5s Calculation form (IPG Test Consultant), 1-7 board testTest Consultant, 1-22



board grader see Board Test GraderBoard Graphics Viewer (Board Consultant), 2-31

associated BT-BASIC statements, 2-31using with backtrace or autolearn, 2-33

Board Test Grader"config.bdg" file listing, 9-16data files, 9-13".discharge" file, 9-9making board tests gradable, 9-9overview, 9-2prerequisites for existing board directories, 9-5report files, 9-14running in a BT-BASIC Window, 9-7running in Pushbutton Debug, 9-5"testplan.bdg" listing, 9-21tests types evaluated, 9-2

board test gradermacros (Pushbutton Debug), 4-10

Board_XY Plot (Plot Generator), 5-3

CCAMCAD, 7-1Capacitor Entry Form (Part Description Editor), 6-8"change" statement, 3-5"changem" statement, 3-5"changen" statement, 3-5Clean Up Board Directory form (IPG Test Consultant), 1-17

command lin"command/e"compile" sta"config.bdg"

creating,listing, 9-modifying

configurationConnector ECopy/Move Bcoverage

test coverCreate GradCreate Gradcustomizing

Debug), 4-

Ddata

entering wdata files for default

options fo"delete" stateDependenciedeveloping a

with IPG

© Agilent T 3



Pushbutton Debug, 4-9st Consultant, 1-14ent, 3-5

at runtime, 3-11at the line level, 3-11in general, 3-11

4), 3-13u (Agilent Pushbutton Debug), 4-16

nsultant, 2-2, 9-29onsultant, 8-3Consultant, 1-2e, 8-2

st Consultant, 1-3rm (Part Description Editor), 6-11entditing, 3-5

Pushbutton Debug, 4-6st Consultant, 1-7ent, 3-6



Device Coverage see Test Coveragedevice entry form

Capacitor Entry Form (Part Description Editor), 6-8Connector Entry Form (Part Description Editor), 6-9Diode Entry Form (Part Description Editor), 6-10FET Entry Form (Part Description Editor), 6-11Fuse Entry Form (Part Description Editor), 6-12Inductor Entry Form (Part Description Editor), 6-13Jumper/Strap Entry Form (Part Description Editor), 6-14overview (Part Description Editor), 6-6Pin Library Entry Form (Part Description Editor), 6-15Potentiometer Entry Form (Part Description Editor), 6-16Resistor Entry Form (Part Description Editor), 6-17Switch Entry Form (Part Description Editor), 6-19Transistor Entry Form (Part Description Editor), 6-20Zener Entry Form (Part Description Editor), 6-21

Digital functional tests, 9-2Digital tests, 9-2Diode Entry Form (Part Description Editor), 6-10".discharge" file, 9-9Display menu (Agilent Pushbutton Debug), 4-17"duplicate" statement, 3-5

EECOs

Interoperability, 11-4Make Interoperable, 10-32Prep for ECO, 10-33

Edit menuin Agilentin IPG Te

"edit" statemerror

checking checking checking

"execute"softkey (f

Execute menexiting

Board CoFixture CIPG Test

external nod

Ffeatures

of IPG TeFET Entry Fo"fetch" statem

used for eFile menu

in Agilentin IPG Te

"find" statem

© Agilent T 4



, tasks, and forms (Part Description Editor), 6-2

y Form (Part Description Editor), 6-13Form in Part Description Editor, 6-5Plot Generator), 5-4ity, 11-1onversion Tool, 11-4 Delimiter, 11-9le Objects, 11-6ctories, 11-5

, 11-211-2

atrix, 11-7roperable, 11-5CO, 11-5

11-10ls, 11-11

nversion Tool, 11-4

xture Consultant, 8-3nsultant, 2-2Consultant, 1-2 Test Consultant, 1-2sultant



"findm" statement, 3-6"findn" statement, 3-6fixture

electronics, 8-2using Fixture Consultant, 8-2viewing with Fixture Consultant, 8-2

Fixture Consultant, 8-2features, 8-2invoking, 8-3quitting, 8-3

Fixture Consultant -- See "HP Fixture Consultant"fixture electronics, 8-2fixture format

specifying in IPG Test Consultant, 1-3, 1-5Fixture Graphics, 8-4Flowchart (Board Consultant), 2-8forward slash, 10-45Fuse Entry Form (Part Description Editor), 6-12

G"generate debug macros" statement, 9-5, 9-23Generate Test Coverage command, 9-23, 9-24, 9-25generating

plots for fixturing, 5-1"get" statement, 3-7grade tests /, 9-7

Hhierarchy

of menus

IInductor EntrInitialization Inserts Plot (Interoperabil

Agilent CCommonCompatibCopy DireDefinitionEnabling,Interop MMake IntePrep for EServers,Use ModeUsing Co

invokingAgilent FiBoard CoIPG Test

invoking IPGIPG Test Con

© Agilent T 5



Entry Form (Part Description Editor), 6-14

ugging (Pushbutton Debug), 4-4r checking, 3-11nt, 3-6ent, 3-6ent, 3-6ent, 3-7nsitivity test grading method, 9-4

u (Agilent Pushbutton Debug), 4-9u (HP Pushbutton Debug)ng, 4-21tions, 4-10oard Consultant), 2-3G Test Consultant), 1-3

t menu (IPG Test Consultant), 1-16IPG Test Consultant), 1-11y (f5), 3-13 form (Board Consultant), 2-20



Actions menu, 1-7Archive Board Directory query box, 1-18Copy/Move Board Directory form, 1-19Dependencies Calculation form, 1-7Edit menu, 1-14exiting, 1-2features, 1-3File menu, 1-7main form, 1-3Management menu, 1-16Mark menu, 1-11menu bar, 1-6multiple step method, 1-10Programs menu, 1-20quitting, 1-2Restore Board Directory query box, 1-19single step method, 1-12specifying the fixture format, 1-3, 1-5using to develop a board test, 1-22View Summary/Details File menu, 1-14View/Edit Board Configuration, 1-16View/Edit Board Files menu, 1-14View/Edit CAD Files menu, 1-16View/Edit Fixture Files menu, 1-16View/Edit Other File, 1-16View/Edit Test Files menu, 1-14

IPG Test Consultant -- See "HP IPG Test Consultant��

JJumper/Strap

Llevels of debline-level erro"list" stateme"listm" statem"listn" statem"load" statemlogic level se

MMacros menMacros men

customizidefault op

Main form (Bmain form (IPManagemenMark menu ("mark" softkemaximizing amenu bar

© Agilent T 6



or, 5-1essages, 5-10

t Plot, 5-4 Plot, 5-3f files for the top plate, 5-10ot, 5-4ported plotters, 5-9n of plots, 5-8rs and types, 5-8 and scaling, 5-9t, 5-3-7

n a network, 5-10do before running, 5-6 plotters, 5-8lot files, 5-10t, 5-5

ters supported by Plot Generator, 5-9 the Plot Generator, 5-8Agilent Pushbutton Debug), 4-19r Entry Form (Part Description Editor), 6-16 sensitivity test grading method, 9-3t type, 9-2

s of verification checks, 2-29lot Generator), 5-3nu (IPG Test Consultant), 1-20ebug



features in IPG Test Consultant, 1-6"merge" statement, 3-7mode

operating, 3-7Mode menu (Agilent Pushbutton Debug), 4-15"move" statement, 3-6multiple

multiple step method in IPG Test Consultant, 1-10

Nnormalizing a form (Board Consultant), 2-20"number" statement, 3-6

Oon-item help (Board Consultant), 2-24operating modes, 3-7

Ppanels, 2-28Part Description Editor, 6-1

Initialization Form, 6-5Task Menu, 6-4

Pin Library Entry Form (Part Description Editor), 6-15Pins test type, 9-2

Plot Generatadvisory mAlignmenBoard_XYdeletion oInserts Pllist of suporientatiopens coloplot sizingProbe Plorunning, 5spooling ithings to using withviewing pWires Plo

plotterlist of plotusing with

Ports menu (Potentiometepower supplyPreshorts tesprinting

the resultProbe Plot (PPrograms mePushbutton D

© Agilent T 7



Test Grader, 9-14tement, 3-7y Form (Part Description Editor), 6-17tement, 3-7oardre Consultant, 8-2 checking, 3-11

ent, 3-7tement, 3-6 items in Board Consultant, 2-26gilent Pushbutton Debug), 4-17

Agilent Pushbutton Debug, 4-10pe, 9-2ethod in IPG Test Consultant, 1-12

, 3-12r" statement, 3-13ement, 3-13& off" statement, 3-13tement, 3-13 over" statement, 3-13

mat (IPG Test Consultant), 1-3, 1-5



customizing the Macros menu, 4-21Display menu, 4-17Edit menu, 4-9Execute menu, 4-16File menu, 4-6Macros menu, 4-9Mode menu, 4-15Ports menu, 4-19Set menu, 4-17setup macros, 4-10testplan macros, 4-10using with vacuum fixtures, 4-21Util menu, 4-18

Qquality test grading method, 9-3quitting

Agilent Fixture Consultant, 8-3Board Consultant, 2-2, 9-29IPG Test Consultant, 1-2

R"recall minus" softkey (f3), 3-12"recall plus" softkey (f2), 3-12redefining

softkeys, 3-12report files

for Board"re-save" staResistor Entr"re-store" starotating the b

with Fixturuntime error

S"save" statem"scratch" stasearching forSet menu (Asetup

macros inShorts test tysingle step msoftkey, 3-12

redefining"softkey clea"softkey" stat"softkeys on "softkeys" sta"softkeys to &specifying

fixture for

© Agilent T 8



gilent Pushbutton Debug), 4-18

st grading method, 9-2l" statement, 4-21, 9-5heck (Board Consultant), 2-29e results of, 2-29

verage, 9-23, 9-25 coverage" statement, 9-23, 9-25ry/Details Files menu (IPG Test Consultant), 1-14ard Configuration (IPG Test Consultant), 1-16ard Files menu (IPG Test Consultant), 1-14D Files menu (IPG Test Consultant), 1-16ture Files menu (IPG Test Consultant), 1-16er File (IPG Test Consultant), 1-16t Files menu (IPG Test Consultant), 1-14

ard Consultant), 2-25

T-BASIC in a window, 3-2lot Generator), 5-5



speed sensitivity test grading method, 9-4statements

editing, 3-5file manipulation, 3-6

status line, 3-3"store line" softkey (f8), 3-13"store" statement, 3-7Switch Entry Form (Part Description Editor), 6-19

TTask Menu in Part Description Editor, 6-4Test Consultant -- See "HP IPG Test Consultant��Test Coverage

running, 9-23running on a custom "testplan", 9-25running on a standard "testplan", 9-23"testcoverage.rpt" file, 9-26

test grader see Board Test Gradertest types evaluated by Board Test Grader, 9-2testability report, 2-34"testcoverage.rpt" file, 9-26testplan

macros (Agilent Pushbutton Debug), 4-10"testplan.bdg" file

listing, 9-21Transistor Entry Form (Part Description Editor), 6-20

UUtil menu (A

Vvacuum off te"vacuum welverification c

printing thverify

device co"verify deviceView SummaView/Edit BoView/Edit BoView/Edit CAView/Edit FixView/Edit OthView/Edit Tesviewport (Bo

Wwindow

running BWires Plot (P

© Agilent T 9





work area, 3-3workspace, 3-3workstation

clearing the screen, 3-4

ZZener Entry Form (Part Description Editor), 6-21

Test Development Tools - Abcelectroniquenotes-application.abcelectronique.com/018/18-26773.pdf ·...

Documents

Transcript of Test Development Tools - Abcelectroniquenotes-application.abcelectronique.com/018/18-26773.pdf ·...