VisualATE Users Guide

visualATE 5.2™User Guide

PN: 071-0489-00August, 2004

Credence Systems Corporation1421 California CircleMilpitas, CA 95035Tele: (408) 635-4300Fax: (408) 635-4985

Customer Service Center(503) 466-7678 (North America and International)(800) 328-7045 (Toll-free within the United States)[email protected] (Internet email)(503) 466-7814 (Fax)

Legal NoticeNo part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated intoany language or computer language, in any form or by any means—electronic, mechanical, magnetic, optical,chemical, manual or otherwise—without the prior written permission of Credence Systems Corporation.Credence Systems Corporation makes no representations or warranties with respect to the contents hereof andspecifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore,Credence reserves the right to revise this publication and to make changes from time to time in the content hereofwithout obligation of Credence to notify any person of such revision or changes.

Restricted Rights LegendUse, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of therights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph (c)(2) of theCommercial Computer Software – Restricted Rights Clause at FAR 52.227-19, as applicable.

Printed in August, 2004 in the U.S.A. All rights reserved.© 2004 Credence Systems Corporation

Notices:

Accelerated Vector Mode, ASAP, AVM, BatchProbe, Credence, BOST, EPRO, EPRO with design, FIRE PIN, Fluence,IDS, IDS OptiFIB, Kalos, Keep Alive, KITE, MemBIST, MemBOST, MVNA, NxGenConnect, PBRIDGE, SABER,SCANBRIDGE, SEF SCANBRIDGE, SEF, SEQUENCEMATCH, Sequencer Per Pin, SRC, STIL2WDB,STILACCESSOR, STILEDITOR. STILNAVIGATOR, STILPURIFIER, STILREADER, STILVIEWER, STILWRITER,STRATEGIES, TDRAW, TDS, TIMEPLATE, TPFORCEGEN, TPGEN, TPMATCH, TPSTROBEGEN, TRAM, TRC,TRITON, TSPEC, TSSI, Valstar, VBRIDGE, VCOBOST, WAVEBRIDGE, WAVEGRABBER, WAVEMAKER,WAVEMASTER, WDB, WDB2STIL, and WGL are all registered trademarks of Credence Systems Corporation.

APE, ASL 1000, ASL 3000, ASL 3000RF, CONCURRENT ALGORITHMIC TEST NETWORK, Duo, Electra, IDSOptiCA, ISOCHRONOUS FABRIC INTERFACE, Logic50, Logic100, NanoBlade, NPower, NxGenSupport, Octet 200,Octet 400, Octet 800, Personal Kalos, Kalos (xp), Kalos XW, Quartet One, Quartet Logic, Quartet LC, RAMBOST,RFx, Sapphire NP, SC 212, SC 312, SC Valstar, TimeStamper, Vanguard, Vanguard II, Vista LT-1101, Vista LT-1001,Vista LT-1001E, VistaLOGIC, VistaLOGICxf, VistaLOGICxp, VistaVISION, VistaVISIONxp, VISUAL STIL, and XTOSare all trademarks of Credence Systems Corporation.

Gemini is a registered trademark of Micro-Probe, Inc. and is licensed for use to Credence Systems Corporation.

The following are trademarks or registered trademarks of their respective companies or organizations:

UNIX / X/Open Company Ltd.Sun Microsystems, Sun Workstation, OpenWindows, SunOS, NFS, Sun-4, SPARC, SPARCstation, Java, Solaris / Sun Microsystems.Ethernet / Xerox CorporationMicrosoft, Windows, Windows NT / Microsoft Corporation

All other brand or product names are trademarks or registered trademarks of their respective companies.

The visualATE 5.2 series of test stations meets the following classifications under European Standard EN 55011, titled“Limits and Methods of Measurement of Radio Disturbance Characteristics of Industrial, Scientific and Medical (ISM)Radio-Frequency Equipment”:

Group 1 Equipment ISM Equipment: Equipment which utilizes radio-frequency energy for internal functioning of the equipment itself.

Group A Equipment Equipment radio-frequency emissions comply with Class A limits.

CONTENTS

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1 - visualATE Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Executable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Dynamic Link Library Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

visualATE Test Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Test Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Lists and Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Proprietary File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Standard File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Default File Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34The visualATE User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Launching visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35visualATE Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

To Access Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Security and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2 - Getting Started with visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39The visualATE System Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40New Install Logon and Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Logging On to visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41To log on to Windows NT as an administrator . . . . . . . . . . . . . . . . . . . . . . . 41To log on to Windows NT as a visualATE user . . . . . . . . . . . . . . . . . . . . . . 41

Starting visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Critical Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Printable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Accessing Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Reinstalls and Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Administrator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Upgrading to visualATE 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Backup Existing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

visualATE5.2 User Guide 3

Uninstall Existing visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Install visualATE 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47To batch build DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3 - Microsoft Developer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Visual C++ File Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54The Visual C++ Workspace Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Customizing the Tools for Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

To remove the execute tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57To Add the Debugging Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4 - Configuring System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61To Configure visualATE System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Defining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Creating a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63To Create a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63To Create User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Editing and Deleting Existing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68To Edit User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68To Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Setting the Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Setting Up Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

To Extract Information From Test.exe on Startup . . . . . . . . . . . . . . . . . . . . 71To Choose an Alternate Tester Executable File . . . . . . . . . . . . . . . . . . . . . . 71

Setting Up the Demonstration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Setting an Event Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Operator Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Show a List of Available Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Force Entry of Program Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Shutdown System When Leaving Program . . . . . . . . . . . . . . . . . . . . . . . . . 74

Defining Maintenance Program Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Editing Screen Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Defining Printing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

5 - Setting Default Program Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81The Default Program Properties Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Defining Production Program Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Automatically Continue a Program After a Failed Function . . . . . . . . . . . . . . . . 83Automatically Print on End of Lot: Lot Summary and Test Statistics . . . . . . . . . 83Automatically Upload File on End of Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Automatically Create a New Datalog on New Lot Event . . . . . . . . . . . . . . . . . . 84Display Lot Summary By Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4 PN: 071-0489-00, August, 2004

Disable Bin Bar Chart on Lot Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Enable Collection of Test Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Use Only Passed Devices in Test Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Calibration Expires in __ days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Checker Expires in __ days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Results summary lifetime (days) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Arm Yield alarm at device count = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Fail alarm if yield percentage is < OR if consecutive fail count > = . . . . . . . . . . 85

Defining Program Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Display Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Display Tests for All Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Use Relative DLL Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Disable Lot-Sublot for EOW handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87QA Retest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Defining Datalog Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Log Data to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Log Passed Device Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Log Failed Device Results (unconditionally) . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Commit Datalog to File After Every Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Fractional Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Datalog Lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Datalog File Name and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Setting Handler Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Prober Control of Wafer LOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Suppress OnNewLot Wafer Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Assigning Bin Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Software bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Setting Alarm Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Add Hardware Bins to the Lot Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Defining Setup Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Defining File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Setting Version Control Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Enabling AutoCorrelation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Specified Number Usage Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Validate Both AutoCorrelation Data and Limits Sets . . . . . . . . . . . . . . . . . . . . 102

6 - The Networked visualATE System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Engineering Program Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Production Program Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109


Program Control Folder Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Example of a Production Program Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Supported Networking Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Unsupported Networking Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

7 - visualATE/ASL-DOS Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Moving Files Between DOS and NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Converting DOS Files to NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8 - Creating Lists and GeneratingSource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Steps to Create DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122List File Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Opening Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126The List Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Creating a New List (.lst) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Inserting an Existing List (.lst) File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Working with the Create Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Displaying Test Function Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

To display the function without parameters . . . . . . . . . . . . . . . . . . . . . . . . 132To display functions without tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Entering Test Function Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Overwriting Test Parameters or Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Copying, Cutting, and Pasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

To copy or cut and paste a single parameter or test . . . . . . . . . . . . . . 133To copy or cut and paste multiple parameters or subtests . . . . . . . . . 135Copying and pasting test functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Dragging and Dropping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Working with List Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Opening Lists Within the Create Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Saving, Renaming and Closing Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

To Save a List and Its Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Save As (Renaming Lists) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Closing Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

To close a list file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138To close the file and exit visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Working with Multiple Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139To Open a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139To Close an Active File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Editing Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Adding Test Function Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Adding a New Test Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

6 PN: 071-0489-00, August, 2004

Adding and Editing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Insert a new parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Define the parameter format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Define the parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Define the parameter scale factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Adding and Editing Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144To insert a new test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144To define testname and test limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Defining List Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144To Bring Up the List Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . 144Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Assigning Instruments and Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145To configure the required boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Changing the Instrument Configuration Without Editing a List . . . . . . . . . 146

Updating Lists After Creating Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Generating Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Generate Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Generate List Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Adding Code to the Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Build Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Access Information On a Build Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Open the Code and Fix the Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Move Between Lines of Code with Build Errors . . . . . . . . . . . . . . . . . . . . . . . 153

Rebuilding DLL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154After Editing a List or Reinstalling visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . 154After Updating Source Files For a List (Adding A Test Function) . . . . . . . . . . 154

9 - Writing Test Programs and Working in Engineering mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Test Programs and Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Program Creation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Accessing Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159The Program Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Creating a New Test Program File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Inserting an Existing File into Program Selection . . . . . . . . . . . . . . . . . . . . . . 162

Test Program File Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163The Engineering Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Working with the Engineering Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Displaying Test Program Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Modifying Function Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170


Overwriting Parameters Values and Test Limits . . . . . . . . . . . . . . . . . . . . 171Copying, Cutting, and Pasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Dragging and Dropping — Copying and Pasting Complete Functions . . . 172

Working with Test Program Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Opening Programs Within the Engineering Editor . . . . . . . . . . . . . . . . . . . . . . 173Saving, Renaming and Closing Test Programs . . . . . . . . . . . . . . . . . . . . . . . . 173

Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Rename or Relocate Files with “Save As” . . . . . . . . . . . . . . . . . . . . . . . . . 173Closing Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Editing Program Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Inserting and Enabling Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Creating Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Editing Limit Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Entering Limit Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Defining Program Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Defining Operator Program Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Automatically continue a program after a failed function . . . . . . . . . . . . . . 184Enable editing of a lot summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Enable deletion of a lot summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Automatically print program results summary . . . . . . . . . . . . . . . . . . . . . . 185Automatically upload STDF file on end of lot . . . . . . . . . . . . . . . . . . . . . . 185Automatically create a new datalog on new lot event . . . . . . . . . . . . . . . . 185Results summary lifetime (days) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Defining Program Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Assigning a Screen Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Use Relative DLL Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Disable Lot-Sublot for EOW handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187QA Retest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Defining Datalog Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Log data into file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Automatic datalog creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Log passed device results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Log failed function results (unconditionally) . . . . . . . . . . . . . . . . . . . . . . . . 192Commit datalog to file after every device . . . . . . . . . . . . . . . . . . . . . . . . . 192Log device summary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Fractional Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Compute fraction to save from Lot and Target size . . . . . . . . . . . . . . . . . . 193Datalog Lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Datalog File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Setting Handler Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Prober Control of Wafer LOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Suppress OnNewLot Wafer dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

8 PN: 071-0489-00, August, 2004

Assigning Bin Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Setting the Program Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Using Test Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Using AutoCorrelation to Verify Tester Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . 200Overview of AutoCorrelation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Creating Initial Values and Golden Devices . . . . . . . . . . . . . . . . . . . . . . . . . . 200Defining Tolerances (Delta Limits) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Auto Correlation Interval Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Validate Both Autocorrelation Data and Limits Sets . . . . . . . . . . . . . . . . . . . . 203AutoCorrelate File Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Synchronizing Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Updating Test Programs After Changing the Parent List . . . . . . . . . . . . . . . . . . . . 206

10 - Debugging Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Preparing for Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Debugging Source Code Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Correcting Errors Discovered in Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

11 - Running Test Programs and Collecting Data in Engineering Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 223Run Screen Window and Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

The Header, Information Bar and Command Key Legend . . . . . . . . . . . . . . . 225The Run Screen Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Running Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Working with Lot Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Displaying the Lot Summary (No Data is Logged) . . . . . . . . . . . . . . . . . . . . . 233Printing Lot Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Saving Lot Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Working with Saved Lot Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Setting Up and Using Wafer Sort Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Enabling Wafer Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

In Sys Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241In Engineering, only for the open test program . . . . . . . . . . . . . . . . . . . . . 242

Starting Wafer Sort Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Without an SOL Event Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244With an SOL Event Handler: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Using the Wafer Sort Control Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Lot Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Lot Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Sub-Lot Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Select Wafers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Total Wafers in Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247


Wafer Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Completed Wafers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Wafers in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Missing Wafers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Creating and Setting Up a New Lot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

In Engineering: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248In Operator: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Working with Existing Lots and Sublots . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Working with Datalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Displaying Datalogged Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Using Datalog Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Setting Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Saving Datalogged Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Printing Datalogged Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Charting Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Charting Device Results in a Bin Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Graphing Test Results as a Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Printing, Saving and Editing Histograms . . . . . . . . . . . . . . . . . . . . . . . . . . 267Creating a Time-Domain Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Graphing Test Results in 3D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Plotting Test Results on a Set of X-Y Axes . . . . . . . . . . . . . . . . . . . . . . . . 271

Viewing Lot Summary Trees and Per-Test Statistics . . . . . . . . . . . . . . . . . . . . 271Working with Saved Datalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

12 - Running Test Programsin Operator Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Tasks in Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276The Operator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277The Operator Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278Operator Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Lot Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Datalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Accessing the Operator View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282Running a Test Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Displaying, Printing and Saving Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

10 PN: 071-0489-00, August, 2004

Printing Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Saving Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

13 - visualISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Starting visualISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290visualISE User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Instrument Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Strobe Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Tool bar Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

User Test Interface Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Instrument Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Code Bar Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Closing visualISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Generating Code with visualISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

14 - visualPLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Starting visualPLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312visualPLOT User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Mode Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Test Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Test Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Test Mode Options Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

visualPLOT Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Test Definition Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Parameter History Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Other Parameters Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323


Browser Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Color Scheme Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Edit an Existing Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Change Interval Colors: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Delete an Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Using Hexadecimal Values for Interval . . . . . . . . . . . . . . . . . . . . . . . . 326

Test Result Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Toggle Between Grid and Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Toggle Between Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 327Show/Hide Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Copy Test Result Pane as a Bitmap . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Grid Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Graph Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3293D Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330General Controls Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

visualPLOT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Selecting a Test Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Running a Test Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Disconnect from visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Displaying Pass/Fail Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Saving Shmoo Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333Closing visualPLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Retesting the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Retest in Grid Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Retest in Graph Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Printing the Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Print as Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Print as Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Preview Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Page and Print Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Editing Test Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Adding a Repeat Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Changing Parameter Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Changing Fixed Step Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Changing Static Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Changing Input Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Changing a Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Aborting a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Setting the Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Setting 3D Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Defining StartUp and ShutDown Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

12 PN: 071-0489-00, August, 2004

FIGURES

Figure 1. visual ATE Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 2. visualATE Test Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 3. Lists and Source Code Files (Create Mode) . . . . . . . . . . . . . . . . . . . . . 29Figure 4. Test Program Creation (Engineering Mode) . . . . . . . . . . . . . . . . . . . . . 31Figure 5. NT Desktop and visualATE Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 6. Run INIT Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 7. visualATE Logon Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 8. Main Access Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 9. System Properties Window at Log On . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 10. The Welcome Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 11. The Select Components Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 12. The visualATE License Agreement Screen . . . . . . . . . . . . . . . . . . . . . . 48Figure 13. The visualATE Readme File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 14. Rebuild DLL Reminder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 15. The Setup Complete Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 16. The Sys Admin Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 17. The Build Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 18. Visual C++ Opened From Batch Build . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 19. The Dependencies List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 20. Visual C++ Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 21. Directory Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 22. Blank Source Code View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 23. The Customize Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 24. The Category Pop-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 25. Removing the Execute Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 26. The Debug Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 27. The MS C++ Recommended Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 28. System Properties WIndow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 29. Create New User Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 30. The Edit User List Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 31. A New User in the User list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 32. The Edit User Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 33. A New User with Defined Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 34. A Defined User Shown in the List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 35. The New Password Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 36. Maintenance and Operator Access for Same User . . . . . . . . . . . . . . . . 69


Figure 37. The Programs Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 38. Select Tester Executable File Window . . . . . . . . . . . . . . . . . . . . . . . . . 71Figure 39. The Operator Tab in the System Properties Dialog . . . . . . . . . . . . . . . . 73Figure 40. Operator Opening Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 41. The Maintenance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 42. The Maintenance Program Selection Dialog (Checker) . . . . . . . . . . . . 76Figure 43. Format View Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 44. Format View - Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 45. Format View - Datalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 46. Format View - Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 47. The Printing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 48. Default Program Properties, Operator Tab . . . . . . . . . . . . . . . . . . . . . . 83Figure 49. Default Program Properties, Program Tab . . . . . . . . . . . . . . . . . . . . . . 86Figure 50. Engineering Editor with Function Numbers . . . . . . . . . . . . . . . . . . . . . . 86Figure 51. Figure 5-4 Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 52. Enabling QA Retest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 53. QA Retest New Lot Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Figure 54. QA Retest Datalog and Datalog Tiled . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 55. Two Views of the Engineering Editor

Upper left: Two functions with unwrapped parameters. Lower right: A function with unwrapped parameters, tests and the comments column displayed. 91

Figure 56. Default Program Properties, Datalog Tab . . . . . . . . . . . . . . . . . . . . . . . 92Figure 57. Default Program Properties Dialog, Handler Tab Selected . . . . . . . . . . 94Figure 58. Default Program Properties Dialog, Bins (1-16) Tab . . . . . . . . . . . . . . . 95Figure 59. The Setup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 60. The File Names Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 61. The Version Control Tab and its Effect . . . . . . . . . . . . . . . . . . . . . . . . 100Figure 62. AutoCorrelation Tab in the Default Program Properties . . . . . . . . . . . 102Figure 63. Entering Network Path in Engineering Properties . . . . . . . . . . . . . . . . 106Figure 64. Operator System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Figure 65. visualATE Convert Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Figure 66. The DOS->NT Wizard Dialog with a Convert in Progress . . . . . . . . . . 120Figure 67. The Create Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Figure 68. File Structure in Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Figure 69. List Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Figure 70. The New List Names Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . 127Figure 71. List Properties Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Figure 72. Instrument Board Pointers Declared in user.cpp . . . . . . . . . . . . . . . . . 128Figure 73. A New List Opened in the Create Editor . . . . . . . . . . . . . . . . . . . . . . . 129Figure 74. Create Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Figure 75. Two views of the Create Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

16 PN: 071-0489-00, August 2004

Figure 76. The Create Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Figure 77. The Create Editor Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Figure 78. The Create Editor with Two Completed Functions . . . . . . . . . . . . . . . 136Figure 79. Confirm Source Code Directory Window . . . . . . . . . . . . . . . . . . . . . . . 137Figure 80. The Save List Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Figure 81. The Create Editor with Two Lists, a Test Program, and Datalog Tiled 140Figure 82. Creating a New List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Figure 83. Parameter Units Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 84. Select Scale Factor Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 85. List Properties Dialog Box, Names Tab Selected . . . . . . . . . . . . . . . . 145Figure 86. List Properties Dialog Box with an Available Boards Menu . . . . . . . . . 146Figure 87. Generate Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Figure 88. An Open Source Shell (Ready to Code) . . . . . . . . . . . . . . . . . . . . . . . 151Figure 89. User-Entered Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Figure 90. A List File, DLL, Test Program and Limit Sets . . . . . . . . . . . . . . . . . . . 158Figure 91. Program Selection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Figure 92. Selecting and Saving Program Files . . . . . . . . . . . . . . . . . . . . . . . . . . 161Figure 93. Select Program to Insert Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Figure 94. Engineering Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Figure 95. Engineering Toolbar Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Figure 96. Engineering Editor and Datalog Screens . . . . . . . . . . . . . . . . . . . . . . 168Figure 97. Tiled View of the Engineering Editor and Datalog Screens . . . . . . . . . 169Figure 98. Test Program Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Figure 99. Insert Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Figure 100.Tree View of List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Figure 101.Engineering Editor After a Function was Inserted . . . . . . . . . . . . . . . . 178Figure 102.Select Function Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Figure 103.Limit Sets Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 104.Rename Limit Set Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 105.Select Scale Factor Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Figure 106.Program Properties Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Figure 107.Program Properties Dialog, Program Tab Selected . . . . . . . . . . . . . . 186Figure 108.Enabling QA Retest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 109.Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 110.QA Retest New Lot Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Figure 111.QA Retest Datalog and Datalog Tiled . . . . . . . . . . . . . . . . . . . . . . . . . 190Figure 112.Default Program Properties Datalog Tab . . . . . . . . . . . . . . . . . . . . . . . 191Figure 113.Program Properties Dialog with Handler Tab Selected . . . . . . . . . . . . 194Figure 114.Program Properties Dialog, Bins (1-16) Tab Selected . . . . . . . . . . . . . 195Figure 115.The Setup Tab of the Program Properties Dialog . . . . . . . . . . . . . . . . 196Figure 116.Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Figure 117.Auto Correlation Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202


Figure 118.Select Edit List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Figure 119.Edit List Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Figure 120.Modify Test Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Figure 121.Modify Test Window with Only One Limit Set . . . . . . . . . . . . . . . . . . . 205Figure 122.The Insert Function Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Figure 123.Visual C++ Task Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Figure 124.Visual C++ Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Figure 125.Class View and File View in Visual C++ . . . . . . . . . . . . . . . . . . . . . . . 212Figure 126.The Breakpoints Dialog in MSDev . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Figure 127.Build TestDbg Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Figure 128.Windows NT Task Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Figure 129.An Open Code File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Figure 130.The Breakpoints Dialog and Selection Menu . . . . . . . . . . . . . . . . . . . 216Figure 131.Set Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Figure 132.Run to Breakpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Figure 133.Shifting Breakpoint Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Figure 134.The Engineering Run Screen as it Opens, Before the Test Program has

been Run 224Figure 135.A Datalog and a Lot Summary of Test Results . . . . . . . . . . . . . . . . . . 225Figure 136.Test Program Header and Program Information Bar Before the Test

Program is Run 226Figure 137.Engineering Run Screen Toolbar with Tools Identified . . . . . . . . . . . . 227Figure 138.Two Views of the Run Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Figure 139.Lot Summary Display, No Datalog . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Figure 140.Bin Bar Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Figure 141.Bin Names and Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Figure 142.Lot Summary Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Figure 143.Print Settings for Lot Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Figure 144.Save Lot Summary Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . 239Figure 145.Handlers Tab in Sys Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Figure 146.Program Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Figure 147.Handler Tab in Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Figure 148.Setting an Active Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Figure 149.Blank Wafer Sort Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Figure 150.Lot Numbers in Wafer Sort Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Figure 151.Appending a Lot Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Figure 152.The Open Wafer Sort Input File Dialog . . . . . . . . . . . . . . . . . . . . . . . . 249Figure 153.An Existing Lot opened in Wafer Sort Control . . . . . . . . . . . . . . . . . . . 250Figure 154.Tiled View of the Program and Data Editors . . . . . . . . . . . . . . . . . . . . 251Figure 155.Logged Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Figure 156.A Datalog of Failed Results With Tests Hidden . . . . . . . . . . . . . . . . . . 254Figure 157.Views of Fractional Results and Property Setting . . . . . . . . . . . . . . . . 255

18 PN: 071-0489-00, August 2004

290

Figure 158.Two Views of a Datalog, Standard and Minimal . . . . . . . . . . . . . . . . . 256Figure 159.Select Datalog Filter Parameters Dialog . . . . . . . . . . . . . . . . . . . . . . . 257Figure 160.The Select Datalog Filter Parameters Dialog . . . . . . . . . . . . . . . . . . . 258Figure 161.A Filtered Datalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Figure 162.The Datalog Serial Number Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Figure 163.The Datalog Tab of the Program Properties . . . . . . . . . . . . . . . . . . . . 261Figure 164.Default File Location for Automatically Saved Datalogs. . . . . . . . . . . 262Figure 165.Two Different Text Versions of a Datalog File . . . . . . . . . . . . . . . . . . . 263Figure 166.Save Datalog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Figure 167.A Datalog Printed in Portrait Orientation . . . . . . . . . . . . . . . . . . . . . . . 265Figure 168.Test Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Figure 169.A Selected Test and its Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Figure 170.The Parts of a Histogram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Figure 171.A Series of Histograms Showing the Effects of Changing the Parameters

269Figure 172.Two Views of a Time-Domain Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Figure 173.A Lot Summary Tree Dialog and Per-Test Statistics for a Summary . . 272Figure 174.The Toolbar in a Saved Datalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Figure 175.The Operator Window with Lot Summary Displayed and Major Areas

Identified 277Figure 176.The Operator Toolbar with Tools Identified . . . . . . . . . . . . . . . . . . . . . 278Figure 177.The Operator Program Selection Window . . . . . . . . . . . . . . . . . . . . . 283Figure 178.The Program Selection WIndow with Forced Entry . . . . . . . . . . . . . . 283Figure 179.The Operator Window as it Opens . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Figure 180.The Enter Lot ID dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Figure 181.Operator Window with an Open Test Program . . . . . . . . . . . . . . . . . . 285Figure 182.The Datalog Properties Tab; Operator View Without a Datalog . . . . . 287Figure 183.List of instruments in Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Figure 184.visualISE Window Figure 185.visualISE Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Figure 186.visualISE Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Figure 187.visualISE User Test Interface Pane . . . . . . . . . . . . . . . . . . . . . . . . . . 298Figure 188.visualISE Instrument Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Figure 189.visualISE Code Bar Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Figure 190.visualISE Log Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301Figure 191.VisualC++ Edit Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Figure 192.Instruments -> Options Check Boxes . . . . . . . . . . . . . . . . . . . . . . . . . 302Figure 193.VisualC++ Code Pane with Appended Text in CS File . . . . . . . . . . . . 303Figure 194.VisualC++ Code Pane with Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Figure 195.VisualC++ With Generated Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Figure 196.Code Pane with Generated List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Figure 197.Code Generated in Code Bar Pane . . . . . . . . . . . . . . . . . . . . . . . . . . 306


Figure 198.Code generated in Code Bar Pane as Appended in VS Function . . . 306Figure 199.Code Generated in Code Bar Pane and VS Function . . . . . . . . . . . . 307Figure 200.Filling in Parameters and Instrument Functions . . . . . . . . . . . . . . . . . 308Figure 201.TMU Code Appended to the Code in VS File . . . . . . . . . . . . . . . . . . . 308Figure 202.Code Created in visualISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Figure 203.visualISE Code With Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309Figure 204.Displaying Results in visualATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Figure 205.List of Instruments Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Figure 206.visualPLOT Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Figure 207.Menu Bar for visualPLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Figure 208.File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Figure 209.View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Figure 210.Mode Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Figure 211.Test Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Figure 212.Test Mode Options Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Figure 213.Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Figure 214.Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Figure 215.visualPLOT Window Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321Figure 216.Test Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Figure 217.Parameter History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Figure 218.Other Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Figure 219.Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Figure 220.Color Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324Figure 221.Edit List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Figure 222.Color Definition Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Figure 223.Color Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Figure 224.Test Result Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Figure 225.Grid Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327Figure 226.Graph Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Figure 227.visualATE Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Figure 228.General Controls Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Figure 229.Retest in Grid Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Figure 230.Retest in Graph Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Figure 231.Properties Drop Down List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Figure 232.List for Input Parameter Koeff Dialog . . . . . . . . . . . . . . . . . . . . . . . . . 337Figure 233.Formula for Input Parameter Koeff Dialog . . . . . . . . . . . . . . . . . . . . . 338Figure 234.Test Abort Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338Figure 235.Orientation Change Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Figure 236.3D Axis Definition Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Figure 237.3D View of Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Figure 238.StartUp ShutDown Test Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

20 PN: 071-0489-00, August 2004

TABLES

Table 1. visualATE Proprietary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 2. visualATE Standard Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table 3. Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Table 4. Directories for lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Table 5. Directories of Test Program Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Table 6. File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Table 7. Instrument Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Table 8. Strobe Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Table 9. View Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Table 10. Window Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Table 11. Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Table 12. Tool bar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Table 13. File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Table 14. View Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Table 15. Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Table 16. Test Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Table 17. Test Mode Options Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317Table 18. Tools Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Table 19. Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Table 20. Test Definition Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Table 21. Grid Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328Table 22. Graph Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329Table 23. 3D Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Table 24. General Controls Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331


22 PN: 071-0489-00, August, 2004

visualATE5.2 User Guide

1
visualATE SOFTWARE OVERVIEW
This chapter describes the components of visualATE, the elements of a test application, file structures and types, and introduces the visualATE Graphical User Interface (GUI).

23

1 - visualATE Software Overview

Software ArchitecturevisualATE is an application that allows for setting up and running test programs on ASL 1000, ASL 3000 and ASL 3000 RF testers. The software operates on the Microsoft® Windows NT® 4.0 platform, incorporates Microsoft Visual C++ as the system compiler and uses a GUI for access to set up and test programs. Credence Systems’ visualATE delivers extensive C++ device application code that was written to test a range of device properties with each of the available test instruments - it is thus not a requirement for the user to have extensive programming experience to run programs and operate the tester under visualATE.

visualATE includes executable (.exe) files and a collection of supporting Dynamic Link Library (DLL) files. Figure shows the relationship and interaction between the components of visualATE.

Figure 1. visual ATE Architecture

To speed up the code writing process, visualATE automatically generates source code and header files and places them in preassigned directory locations. Think of these source code files as “templates” to use when developing customized programs.

The visualATE file structure is organized so that source code entered one time is available to a variety of customized test programs. A completed code file is compiled into a single set of executable instructions (a function library), that different test

Test Head (Backplane w/Instruments)

Data/Control Bus Cable

ASL.exe

Test.exe

IF Card

Active X

Your CompiledSource Code (DLL)

You work hereto create sourcecode and run testprograms; ASL.exe

your code to

tells Test.exe(via ActiveX) to runthe programs

Test.exe executes

test devices

Tester PC

24 visualATE5.2 User Guide

Software Architecture

programs can call to as desired. Using this file structure, test programs can be created and edited without modifying or recompiling the source code. This method works to protect the source code files from unnecessary changes, and reduces the need to write original code for every test program.

Executable FilesExecutable files (*.exe) are the programs that run the user interface and hardware control. The following executable files are significant to this discussion of visualATE:

Init.exe — Runs on system startup and on visualATE startup. Init.exe initializes the ASL test head interface card installed in the PC, as well as the installed test instruments, and updates ASL_nt\system\config\ASL1000.cfg.

ASL.exe — Runs the Graphical User Interface, primarily letting you analyze and manipulate data and communicate instructions to the tester control program. The GUI communicates user action to the hardware control through periodic polling of Test.exe using the Active X protocol.

ASL.exe also creates source files for the system compiler (Visual C++) from user-entered data. ASL.exe creates the required Visual C++ project files (*.dsp), complete header files (*.h), and source code files (*.cpp).

Test.exe — Controls the test head instrumentation during component testing as well as data collection. When you select a test program, Test.exe links to your compiled code (DLL) and directs the tester hardware to test devices according to the test program instructions. At the same time, Test.exe also uses the visualATE system DLLs to control instrument calibration and system events.

To test components, both ASL.exe and Test.exe must be running. For programming tasks, ASL.exe can run on its own, such as in Demonstration Mode. (Test.exe does not run on startup when visualATE is set to Demonstration Mode. See the “Configuring System Properties” chapter for details on how to set mode.)

HandlerMgr.exe — The Handler Manager, a resource allowing you to create and manage Test Head Interface card-based handlers; it is integrated into visualATE’s Maintenance mode.

Dynamic Link Library FilesDynamic Link Library file (*.DLL) is a Windows library of routines and resources that links to the executable (*.exe) file at run time. In visualATE, all user-written code is compiled into DLLs. Additionally, visualATE has its own system DLLs with hardware and interface controls. Multiple DLLs can attach to a single executable file.



When running a test program, the necessary system DLLs and your own code attach to the hardware control executable file (Test.exe) to control the tester hardware. While a test program is running, the program calls code within the DLL to perform the measurement(s).


visualATE Test Structure

visualATE Test Structure In visualATE, test programs carry out device testing. Test programs instruct the tester hardware to execute test functions, which contain the instructions to the tester. Shown in Figure 2 is a functional diagram of how the hardware carries out the test process.

Figure 2. visualATE Test Structure

The executable modules carry out the following actions as they interact with the DLLs during visualATE operation:

1. Upon startup, ASL.exe has no active user test programs.

2. When opening your program, ASL.exe becomes active.

3. ASL.exe creates an instance of Test.exe.

4. ASL.exe requests Test.exe to load DLL.

5. Test.exe loads DLL and sends DLL structural information to ASL.exe.

6. ASL.exe examines DLL structure to determine if the test program matches DLL.

7. If needed, ASL.exe restructures the test program file to match DLL.

8. Run your program: ASL.exe sends test limits and function parameters to Test.exe.

9. When exiting your test program, ASL.exe tells Test.exe to detach DLL and exit.

IF CardHardware Control.dll

Test Head DUT Board

Interface Card



Test Functions Test functions are organized into function libraries called lists. When developing a test program, the first step is to create a list file and add the desired test functions. Next comes writing and compiling source code, then writing test programs that call the functions.

A test function, like any other C++ function, instructs the computer to perform a specific task. In visualATE, test functions contain the C++ code that instruct the tester hardware to perform the required test(s) on a device under test (DUT).

The test function sets up the tester hardware, performs the specified measurements on the device, and performs data logging of the results to the user interface. Test functions can include passed parameters that define how the function operates, and limits that determine whether a test passes or fails. You define default parameter and limit values for each test function that work for a family of devices or a range of conditions, as shown in the “Creating Lists and Generating Source Files” chapter. To test specific devices, you write test programs, adjusting these default parameters and limits for the device under test - see the “Test Programs” section in this chapter.

A single test function can contain multiple tests. A test compares the data resulting from a particular measurement or calculation with preset test limits. The comparisons are recorded as test results in datalog files -- see the "Running Tests..." chapters.

Lists and Source Code Files A list is a function library: a collection of user-defined test functions, complete with parameters and limits. Lists contain default parameter and limit values that can be modified as desired in individual test programs. Lists are compiled into DLLs in Visual C++.

Lists are usually specific to one type of device. For example, one list might contain a variety of functions designed to test single opamps, another list might contain functions written to test voltage regulators, and still another might be made up of functions for testing comparators.



Figure 3 illustrates the process of creating a list file and completing source code.

Figure 3. Lists and Source Code Files (Create Mode)

List files (.lst) are generated automatically—you choose a name for the new list and visualATE creates the file. You then create test functions in this list, adding one or more tests to each function. Once a list file is complete (all desired functions and their default values have been defined), you execute a simple menu command to generate the source files. A header (*.h) and a source (*.cpp) file are created for each test function in the list. These code files are saved to the appropriate visualATE directory locations.

The header file contains all the code and structures (objects) required to support the parameters and tests. The header data allows you to easily write code (in Visual C++) using the passed parameters. The source file (*.cpp) is thus created by entering your specific code.

To complete the source code for the list, you open the source files in Visual C++ and add the commands required (to direct the test instruments to send the necessary prompts to the DUT and read back responses). Code can be entered manually, or copied and pasted from existing code files.

- Add C++ code- Compile the DLL

visualATE

- Select New List- Add New Function- Define Default Parameters

- Save the list- Generate Source Code

Header Files

- Define Default Limits

Creating a List and DLL

- Repeat as Desired

- Open the SourceShell File

Visual C++

Function n (code, params, limits)

Finished DLL

Function 1 (code, params, limits) Function 2 (code, params, limits) Function 3 (code, params, limits)



When the code for each function is complete, you build the files into a DLL. Once the DLL has been built, any number of individual test programs can be built from this file, as shown in the “Test Programs” section in this chapter. See the “Generated Lists and Generating Source Files” chapter for specific instructions for generating source files.

Test ProgramsA test program is a user-defined sequence of calls to various test functions within a particular DLL. The test program defines which functions in the DLL are called, the order in which they are called, and the passed parameters that control how the test functions run.

All the test functions called must be part of the same DLL—a single test program cannot call test functions from different DLLs. However, a single test program does not need to call every test function in the DLL.

Test functions that are called by a test program are said to be included in a test program. The term included will be used throughout this manual.

As an example of the relationship between a list (the compiled DLL) and a test program, consider a list of functions designed to test single opamp devices. The list would contain a number of functions appropriate to test a variety of these devices. A test program written to test an 8-pin DIP 741 style opamp might call to only a few functions from the single opamp list.

Multiple test programs can be created from a single list, because the source code is not affected. You can add, delete, enable or disable test functions, and change limits and passed parameters, all without having to edit or rebuild the source code. For instance, two programs, one for testing a 741 style opamp, and another for an OP07 style, can be written by including different test functions from the same parent list. Each test program will execute the included test functions in the order specified, and the source file remains intact and unchanged.

Furthermore, while lists contain only one set of default maximum and minimum limits for each test, test programs can contain multiple sets of limits. Therefore, depending on the structure used, a single test program can test a device for different purposes. For example, different tests are often required for final production testing as opposed to quality assurance (QA) testing on the same type of device. In this case, only one test program file is created, and the different sets of limits are saved within the test program. The first set of limits could have tight ranges for the final test, while the second could have limits set to the manufacturer’s specified values for QA testing. Again, the parent list and source code files remain unchanged.



Figure 4 illustrates the process of creating a test program.

Figure 4. Test Program Creation (Engineering Mode)

As shown in this diagram, a test program gets its structure from its parent list. The list structure is made up of the test functions, passed parameters, and tests that are available to test program files. Changing the structure of a list (adding test functions, passed parameters, or tests) affects the relationship between the test program and its parent list. Changing limits does not affect the test programs associated with a particular list.

When a structural change is made to a list, the new structure no longer matches the structures of existing test programs created from the list. This will force a re-assembly of the affected Test Program.

When a user runs a test program, Test.exe compares the test program structure to the parent list structure. If the two structures are not identical, an informational message displays to alert you to the structural difference, and visualATE generates a report file. The report file is a text document that describes the differences between the structures and what was changed, which indicates the work required to bring the Test Program back into proper structure.

Once you closes the informational message, the test program runs normally.

Function1 (code, params, limits)Function2 (code, params, limits)Function3 (code, params, limits)Function4 (code, params, limits)Function5 (code, params, limits)

Built DLL (List)Creating a Test Program

Execute Function1 with Test Limits

Execute Function4 with Test Limits Execute Function3 with Test Limits

visualATE

Test Programs

Execute Function2 with Final LimitsExecute Function3 with Final Limits

Execute Function5 with Final Limits

Same Program, Different Limit Sets

Execute Function2 with QA LimitsExecute Function5 with QA Limits

Select a ListSave as a ProgramInsert Desired Functions

Edit LimitsEdit Parameters

Save the ProgramSave Additional Limit Sets Different Program

Execute Function5 with Test Limits

Execute Function2 with QA Limits

Stop, change limits, then run again



File TypesvisualATE uses and generates both standard and proprietary file types.

Proprietary File TypesTable 1 defines the proprietary visualATE and ASL-DOS file types that are generated and used during visualATE operation.

Table 1. visualATE Proprietary Files

File Type Extension Description

Datalog *.dl4 Standard visualATE database format

Datalog *.stdf Standard test database file format

Dynamically Linked Library

*.dll A shared object library; compiled test functions that are loaded at run time.

Handler Data *.pin Generated by the Handler Manager, has handler data

List *.lst Generated in Create, these files are the basis for generating DLLs.

Lot summary *.ls4 Binary file, bin data output summary generated from Lot Summary

Lot summary *.lsr ASCII file, bin data output summary generated from Lot Summary

NT Export *.nx4 Generated by the export command in Create mode

Spreadsheet *.spd Comma-delineated text file compatible with most spreadsheet programs

Test Program *.prg Generated by actions while in Engineering mode

Text *.txt ASCII text that can be manipulated as follows:Report: — Optional output from Engineering or CreateSpreadsheet: — Datalog files from Datalog screenText: — Output from Datalog screen

Wafer Sort Input *.wfr Lot data created by Wafer Sort Control


File Types

Standard File TypesvisualATE generates and uses complete files of the standard source files types as shown in Table 2:

Table 2. visualATE Standard Files

File Type Extension Description

Header *.h Source code header that can be included in source files

Multi-project workspace file

*.dsw Microsoft Visual Studio file that organizes project files into a shared code base.

Project file *.dsp Microsoft Visual Studio project that organizes source code files by type of programming language.

Source code file *.cpp Microsoft C++ source code file.

Precompiled header file

*.pch Microsoft file, speeds build process.

Intermediate file *.pdb Microsoft file used when stepping through code.

Intermediate file *.ilk Microsoft file used when stepping through code.



Default File DirectoriesDuring installation, visualATE creates several file directories and folders that organize the system files as well as those that you create for its use. Do not change this directory except, for example, when placing files in a central location for sharing over a network, as shown in “The Networked visualATE System” chapter in this manual.

During installation, the Setup utility places visualATE onto local drive C. Do not change this drive designation. All visualATE system files are placed into the directory C:\asl_nt.

Subdirectories may vary with the type of installation.

NOTE — Changing the default directories may affect system performance.


The visualATE User Interface


Launching visualATELaunch visualATE from the Windows NT desktop as you would any other application. At the Credence Systems splash screen, you log in with the appropriate user name and password. When logged in, the visualATE GUI lets you access the operating mode of your choice.

Each mode offers unique tools and menus which are discussed in the similarly named chapters of this manual. Depending on the permissions assigned, some environments may not be available to all users.

NOTE — Upon initial installation, the default access rights are for Sys Admin — which means full access to all features for the system administrator.

visualATE Operating ModesThe visualATE user interface features five integrated software modes that users access to execute specific tasks. The system administrator gives access rights to each user, individually for each mode.

Operator — The Operator mode is designed for production tasks, and includes tools for running test programs, saving and printing test data, and checking instruments.

Engineering — Test engineers use the Engineering environment for development—writing and running test programs. Engineering has two views, an editor for writing test programs, and a run screen for collecting test data. The Engineering run screen duplicates the Operator production environment and also includes development tools.

Create — Programmers and test engineers construct list files (later built into DLLs) and generate source code in the Create environment. From Create, you can access all visualATE file types.

Sys Admin — The system administrator accesses this environment to define the visualATE system properties and use system utilities (DOS-NT conversion, Batch Build).

Maintenance — Technicians and engineers calibrate and verify the installed test instruments using Maintenance mode.

In addition to the five distinct operating modes, visualATE allows access to all the visualATE file types (list, test program, datalog, etc.) from both Create and Engineering modes; either of these editors open any visualATE file type.



Files open in a view of the environment interface for the mode they were created in, preserving the menu commands and editing capabilities of the original environment. For example: when opening a test program file in Create, a separate Engineering screen opens. The toolbars for both Engineering and Create remain accessible, and views can be tiled for convenience.

Maintenance and Operator modes will only open test program and datalog files.

To Access Operating ModesClick Sys Admin and Maintenance buttons for access to these modes — this opens the environment editor.

Access to features of the Sys Admin mode is through a series of property pages once you click this button.

For the Operator, Engineering and Create modes, clicking each button opens a selection dialog window. This selection window shows a list of existing files — sample files show in this window in a new install. You must open a file from this list, insert a file, or create a new file for further access in these modes.

Once a file is opened in the editor, it may be edited as desired. Additional files may be opened, edited and saved. All tools for the environment are now available. Selection windows and editor access are discussed in more detail in the chapters of this manual covering Create, Engineering and Operator modes.

The GUI implements many standard Windows features such as window frames with title bars, toolbars, pull-down menus, and scrollbars.

Toolbar items in each environment are equipped with descriptive text to assist you. To identify a tool and what it does, place the cursor over the tool. Descriptive text displays below the tool and on the status bar.

Security and Access RightsvisualATE requires its own user names and passwords, separate from the Windows NT user IDs defined on the system. visualATE privileges can be assigned in a variety of levels, including operation for testing, system administration, programming, maintenance, or a combination of these. With the separate visualATE user IDs, a supervisor can log onto visualATE to solve a production problem without having to exit to Windows NT.

In addition, the visualATE login screen and main menu are both full-screen bitmapped images that hide the Windows NT desktop and taskbar. The Windows NT desktop remains hidden even when a production user logs off and a supervisor logs on.

The flying window keys (which bring up the Windows taskbar and start menu) are not disabled when visualATE is running. Therefore, Windows NT permissions should be coordinated with visualATE permissions: system administrators should define a



production user Windows ID that limits access to visualATE. Users should log onto production machines with this ID; if they press the flying window, they will see the start menu but will not be able to run any programs.

Supervisors will still be able to log onto visualATE with extended permissions during production; however, if a supervisor will need to access the network from a production machine running under limited permissions they may need to log off Windows and log on again. For more information, see “The Networked visualATE System” chapter in this manual.





2
GETTING STARTED WITH visualATE
This chapter documents the steps that are required to log on to an ASL 1000, ASL 3000 or ASL 300 RF tester that is running under the visualATE software.

NOTE — Never run MS-DOS DeFrag or ScanDisk on a visualATE system. Irrecoverable damage results as Windows NT file names are truncated to eight places.

39

2 - Getting Started with visualATE

The visualATE System DesktopvisualATE is supplied installed onto the ASL 1000, ASL 3000 or ASL 3000RF tester PC. Two shortcuts are placed on the Windows NT desktop during installation. visualATE is also placed in the Windows NT taskbar Start menu and can be opened from Start like any other Windows application.

The Run visualATE icon starts the GUI. Run INIT opens the hardware control program, Test.exe. Run INIT runs automatically on system startup, restart, or when a different user logs on. The system cannot be used until the Init run has finished. The next section describes the logon process as well as the brief Init run.

Figure 5 shows a typical visualATE desktop after a new install, as well as the shortcut icons.

Figure 5. NT Desktop and visualATE Icons


New Install Logon and Start Up

New Install Logon and Start UpCredence Systems supplies a Windows NT user ID for the visualATE user. The visualATE software is supplied with system administrator (super user) access defined.

Anyone logging on with this administrator ID can create additional user IDs with limited privileges, and configure visualATE default settings. Before visualATE is used for testing purposes, the system administrator should define this additional user access and configure the system defaults.

NOTE — For security purposes, change the Windows NT administrator ID and password as soon as possible, by creating a new user ID with administrator privileges.

Logging On to visualATETo log on to visualATE as an administrator, follow the instructions below. To log on as a user, see the steps on the next page.

To log on to Windows NT as an administrator1. Start Windows NT

OR (if Windows NT is already running)

Log off and log on again as an administrator:

a. Go to Start -> Log Off user name. .. The Log Off Windows dialog window appears.

b. Choose YesThe Begin Logon dialog window appears.

c. Press Cntrl+Alt+DelThe Logon Information dialog window appears.

2. Enter Administrator as the user name

3. Enter tmtadmin as the password

4. Enter the target system or network name in the Domain field

Administrator (super user) logon is now complete. After Init has run, start visualATE following the steps on the next page, and then configure the system as shown in the “Setting Default Properties” and “The Networked visualATE” chapters in this manual.

To log on to Windows NT as a visualATE user1. Follow step one on the previous page



2. Enter operator as the user name

3. Enter operator as the password

User logon is now complete. After Init has run, start visualATE and configure the program as desired, following the steps in chapters “Configuring System Properties” and “Setting Default Program Properties.”

Immediately after logon, the Hardware Control screen appears briefly while the tester hardware is initialized (Test.exe is running). The Hardware Control screen displays the status of the interface card initialization process. Figure 6 shows the hardware control screen.

Figure 6. Run INIT Screen

Once Test.exe is finished running and the hardware control window closes, the system is ready to use.

HINT — Create an additional shortcut by placing the Run visualATE icon in the Windows Taskbar; Taskbar icons open on a single click.

HINT — To place the Run visualATE icon in the Taskbar, left-click on the desktop shortcut, hold down the mouse, and drag the icon to the Taskbar.



Starting visualATEStart visualATE by following the steps on the following pages. For security, change the system administrator logon given here as soon as possible.

1. Double-click the Run visualATE desktop icon, orClick on the Run visualATE taskbar icon (if available), orGo to Start -> Programs -> Credence Systems visualATE -> Run visualATE

The Credence logon screen for visualATE appears as shown in Figure 7.

Figure 7. visualATE Logon Screen

2. Enter administrator as the User name

3. Enter administrator as the Password

4. Click OK, orPress Enter at your keyboard.



The main menu for access to visualATE appears as shown in Figure 8.

Figure 8. Main Access Screen

5. 4. Click Sys Admin

The System Properties dialog window appears as shown in Figure 9.

Figure 9. System Properties Window at Log On



visualATE is now ready to configure; see the “Configuring System Properties,” Setting Default Program Properties” and “The Networked visualATE” chapters for details.

Critical FilesThe files within the directory C:\asl_nt\system\config are critical system settings files. Once visualATE is configured with desired user access privileges and default settings, make sure to back up the contents of this folder. Some files are machine-specific, so make a backup of the config folder from each visualATE system.

These critical files are not removed during an uninstall. However, if these files are ever removed manually, custom settings and user access will be lost. If there is a backup copy, the settings can be restored from the backup.

DocumentationThis User Guide and Programming Reference information are available in printable Acrobat PDF form. The Acrobat files are accessible from the Windows Start Menu in the Taskbar.

Printable Files1. Adobe Acrobat Reader must be installed on the system.

2. Go to Start -> Programs->Credence visualATE -> View or Print the User Guide

3. Click on the desired title - to access this manual for example, click visualATE User Guide

NOTE — The Programming Reference also appears in the Start Menu. Follow the path above to view or print programming reference information.

Accessing Help1. Log on to visualATE

2. Access one of the operating modes

3. Click on the yellow question mark in the toolbarA suite of reference information appears on the screen

4. Click on the desired topic



Reinstalls and UpgradesvisualATE is supplied already installed on new systems, so the information in this section specifically addresses either reinstalls of visualATE, or upgrades to new versions of visualATE or upgrades from ASL-DOS.

visualATE upgrades to version 5.2 are supplied on CD-ROM.

Administrator PrivilegesPersonnel who reinstall or update of visual ATE must have administrative privileges on the target system, and be logged on to Windows NT as administrator.

Upgrading to visualATE 5.2Upgrading to visual ATE 5.2 involves several steps of backing up existing data, uninstalling existing versions of visualATE, running the new installation and recompiling existing DLLs as needed.

Backup Existing Data1. Make a copy of the c:\Asl_Nt\System\Config directory. Place the backed up copy

somewhere outside of Visual ATE, ex. E:\Config.

2. Make a copy of the c:\Asl_Nt\System\Handler directory. Place the backed up copy somewhere outside of Visual ATE, ex. E:\Handler.

3. Copy all user directories in the c:\Asl_Nt\Users\Lists except for any directories starting with Maint_xxx, where xxx is the 3-letter acronym describing the TMT board. Ex. Emanative, Maint_OVI. Also, do not copy the Example_xxx directories.

Uninstall Existing visualATE1. Click on Start → Settings → Control Panel → Add/Remove Programs.

2. Highlight visualATE (may also show as “Visual ATE”) and click Add/Remove.

3. Click on Yes when prompted to Confirm File Deletion.

4. Click on Yes To All when asked to confirm deletion of NT files.

5. After uninstall is complete, go to My Computer and delete the c:\Asl_Nt directory and the d:\Asl_Nt directory if there is one.

NOTE — Uninstalling an earlier version of visualATE does not remove any existing test programs, lists, or default system settings.



Install visualATE 5.21. Insert the visualATE Installation CD-ROM into the CD-ROM drive

2. Double-click the system icon (My Computer), then double-click the CD-ROM icon

3. Double-click the Setup.exe icon (the computer with an open box next to it)The Install Shield prepares the installation, then the Welcome screen appears.

Figure 10. The Welcome Screen

4. Click Next; the Select Components dialog appears as shown in Figure 11.

Figure 11. The Select Components Dialog



5. Choose the desired installation optionsOptional files are not installed now. See the Readme text (select Next twice to get to the Readme screen, then Back twice to return to this screen for files to install).

6. Click NextReview the Credence visualATE license agreement, shown in Figure 12.

Figure 12. The visualATE License Agreement Screen

7. Click Yes to accept the agreement, then click NextThe Readme dialog appears as shown in Figure 13. Scroll to see the entire file.

Figure 13. The visualATE Readme File Screen



8. Click NextThe installation begins now. First, a reminder to rebuild all user DLL files (Lists) is displayed as shown in Figure 14.

Figure 14. Rebuild DLL Reminder

9. Click OKThe install status window appears, showing the progress of the installation. After a few minutes, the Setup Complete dialog appears as shown in Figure 15.

Figure 15. The Setup Complete Dialog

10. Choose the desired restart option. If installing Datel and/or GPIB drivers, choose “No, I will restart my computer later.” Otherwise, select “Yes, I want to restart my computer now.” Click Finish to continue.

11. Install any optional third-party software desiredThird-party software is not removed by uninstalling visualATE. However, if the third party files have been manually removed, or new versions are included with the upgrade, reinstall them now.

12. Restart the system, then proceed to rebuilding existing DLLs.



To batch build DLLsBatch Build only builds the DLLs associated with test programs which appear in the Program Selection window in Engineering. Parent lists may have more than one associated test program; a DLL will build from every list that is represented by at least one test program in the Program Selection window. Lists that are not represented by at least one associated test program in the Engineering Program Selection window will not be built. These DLLs may be rebuilt individually, using the Visual C++ shortcut in Create.

If desired, insert any missing test programs into Program Selection before using Batch Build.

Follow the steps to batch build DLLs:

1. Start visualATE

2. Log on as an administrator

3. Select Sys AdminThe System Properties window appears as shown in Figure 16.

Figure 16. The Sys Admin Dialog



4. Select the Build TabThe default list directory is the default. This is the recommended directory.

Figure 17. The Build Tab

5. Enter an alternate list directory, if desired

6. Select Batch BuildVisual C++ opens, as shown in Figure 18.

Figure 18. Visual C++ Opened From Batch Build



7. Select the FileView Tab

8. Make TestDbg the active projectGo to Project -> Set Active Project -> TestDbgTestDbg appears in bold in FileView.

9. Build TestDbgGo to Build -> Rebuild AllAll other projects are dependent on TestDbg and will build as well.

NOTE — To check the dependencies, go to Project -> Dependencies, while the system is idle. The dialog shown in Figure 19 appears, making it possible to change the project being modified and select the dependent files to build.

Figure 19. The Dependencies List

The duration of the build process depends on how many DLLs are built. When the DLLs have been rebuilt, visualATE is upgraded and ready to use.



3
MICROSOFT DEVELOPER STUDIO
visualATE comes packaged with Microsoft Developer Studio (MSDev). This suite of programming packages (including Visual C++, which is the visualATE system compiler), puts at your fingertips a powerful development environment with numerous tools and options.

Some of the tools that are most helpful in debugging visualATE files are not displayed in the standard configuration. Because this manual refers to these tools, it is recommended that the system administrator configure Visual C++ before programmers begin using the system. Not all users of visualATE may be familiar with the MSDev window or its file structure that is designed to integrate multiple development projects.

This chapter helps you become familiar with the MSDev environment and file structure while using visualATE. It also provides instructions for configuring the recommended tools.

53

3 - Microsoft Developer Studio

Visual C++ File OrganizationIn MSDev (Visual C++), test function and system source files are organized into projects that contain all the files used for developing, compiling, building and debugging code. Projects are part of a shared development workspace. Multiple projects in different programming languages can be associated in a single workspace.

All visualATE source files are C++; however, even when all files are the same type, Visual C++ assigns both a project and a workspace to related files.

In visualATE, files are related through the list (*.lst) file. The source files for a list include the test function source and header files, plus user and system source files. These files are stored in the list’s folder in the visualATE directory. The list project organizes these files into a Visual C++ directory of source, header and system file folders.

While the project associates source files so that they appear in a single directory in Visual C++, the workspace organizes multiple projects into a directory. In visualATE, multiple projects are not normally grouped into a single workspace. Each list has only one workspace associated with it, which contains the list project. The list project, in turn, contains all the source files for the list, including the system and user files.

An explanation of the relationship between these various files is described in Chapter 8, “Creating Lists and Generating Source Files.”

The associated files are displayed in the FileView portion of the MSDev desktop, shown in the next section.


The Visual C++ Workspace Window

The Visual C++ Workspace Window There are three primary views in the Visual C++ window:

• Directory: Classes, FileView, and Info tabs. FileView is most important to visualATE users as it shows the files contained in a list project or workspace

• Source Code: Opens the source code; the code editor

• Output: Displays the progress of a build or compile

Figure 20 shows the standard Visual C++ window as it opens the first time.

Figure 20. Visual C++ Window

Figure 21 shows an open source file and all three tabs.

Figure 21. Directory Tabs

Source Code View

Directory View

Output View

Source Code Window

Output Window- Shows progress of the build

File View Window



visualATE installation on the tester includes the complete Visual C++ package, complete with help and tutorial files. Upon launching Visual C++, the information file is displayed in the source code view. From here, it is possible to continue opening more information on the listed topics. These topics are beyond the scope of this manual, however, and are not discussed here.

If you wish, close the help file and Visual C++ will open with a blank editor the next time the application is opened.

To close the help file, go to Window, then Close All. The source code view is blank, as shown in Figure 22.

Figure 22. Blank Source Code View

To display the help file, go to View, then InfoViewerTopic. The file appears in the source code editor as shown in Figure 21.


Customizing the Tools for Debugging

Customizing the Tools for DebuggingThe extensive number of tools available in MSDev makes it impossible for each tool to be displayed in the window at the same time. A set of commonly used tools are included in the standard configuration. The toolbars can then be configured according to personal preferences.

Tools are organized by the type of task (file, edit, debug, etc.). Entire toolbars or individual tools may be added to or removed from the window toolbars. This section covers only the modifications recommended for visualATE users: removing the execute tool, and adding a few breakpoint tools. To set up the toolbars as recommended, follow the step-by-step instructions below.

First, remove the execute tool. It is virtually never used, and if needed, there is a keyboard shortcut as well a menu item. The execute tool looks like an exclamation mark:

To remove the execute tool1. Go to Tools -> Customize. The Customize Dialog appears with the Commands tab

selected, as shown in Figure 23.

Figure 23. The Customize Dialog



2. Choose Build in the Category pop-up menuThe pop-up menu appears as shown in Figure 24.

Figure 24. The Category Pop-Up

3. Click and hold on the execute tool

4. Drag the tool from the toolbar to the Customize window

Click on the arrowto see the pop-up

The Build toolsare displayed


Customizing the Tools for Debugging

5. Release the mouseThe execute tool is removed from the toolbar.

Figure 25. Removing the Execute Tool

Adding tools is the reverse of the above process; bring up the Customize dialog, select the target tool, and drag it to the desired place in the toolbar. Two tools are recommended, as they are referred to in the debugging instructions. Both are part of the MSDev Debug series. The recommended debugging tools are as follows:

Move instruction pointer to cursor position

Disable all breakpoints

Click onthis tool

Drag the toolto the dialog

The tool isremoved



To Add the Debugging Tools1. Go to Tools -> Customize

2. Choose Debug from the Category pop-up menuThe Debug tools are displayed as shown in Figure 26.

Figure 26. The Debug Tools

3. Select any of the tools and drag it to the desired place in the toolbars

4. Repeat for the remaining tools

NOTE — In the Customize dialog, click once on a tool to see a description of the tool. The description appears below the Category text field, as shown in the above figure.

Figure 27 shows the recommended toolbar with the execute tool removed and the two breakpoint tools inserted.

Figure 27. The MS C++ Recommended Toolbar



4
CONFIGURING SYSTEM PROPERTIES
System Properties are those functional settings that let you define how you view, run and handle programs in the production environment. You control details of appearance such as screen colors, fonts, sizes, etc., all within the Sys Admin mode:

• Define users and their access privileges

• Enable the system to run with or without test hardware

• Set the screen appearance of the various modes

• Define default program properties

Because of the large volume of information on each topic (setting default program properties, networking, and converting files between ASL-DOS and visualATE), these are discussed separately. For more information on system properties, see the “Setting Default Program Properties”, “The Networked visualATE System” and “Creating lists and Generating Source Files” chapters.

NOTE — visualATE cannot be minimized from the Sys Admin mode. To access Windows NT, press the “flying window” on the keyboard or enter either the Create or Engineering mode in visualATE, and then minimize the window.

61

4 - Configuring System Properties

To Configure visualATE System Properties 1. Start visualATE

2. Log on with the supplied administrator ID

3. Click Sys Admin The System Properties dialog window appears as shown in Figure 28.

Figure 28. System Properties WIndow


Defining Users

Defining UsersIn a new installation, the only defined user is the super user (i.e., administrator). Additional users must be defined while in Sys Admin mode. Each user must have a user name and password to use visualATE. For security reasons it is also recommended that the super user define their own login name and password, rather than continue to use the supplied ID.

Creating a New UserThe instructions below assume the system administrator is logged on to visualATE and is in the Sys Admin (Supervisor) mode.

To Create a New User1. Select the Users tab — The Users tab appears as shown in Figure 29.

Figure 29. Create New User Window



2. Select Edit UsersThe Edit User List dialog appears, as shown in Figure 30. In a new install there is one defined user, the Administrator. The Administrator user is selected, and checked privileges are displayed in the status field below the list.

Figure 30. The Edit User List Dialog

3. Select New UserA default user name appears in the dialog list, with the following format: NewUser_year_month_ day_hour_minute_second. See Figure 31.

Figure 31. A New User in the User list

4. Highlight the default new userrname

5. Select Edit User


Defining Users

The Edit User dialog appears, as shown in Figure 32. Note that the new user does not have any privileges by default. Checked boxes indicate the allowed privileges.

Figure 32. The Edit User Dialog

6. Change the name by typing over the default name

NOTE — user names must be at least four characters long and are not case sensitive. Names must begin with either a letter or an underscore; they cannot begin with a number. Names can contain numbers, so long as they do not start with a number. Names cannot have blank spaces.

7. Check the desired privileges Choices made here set the visualATE modes that users can access. These appear in Table 3:

Table 3. Access Rights

Mode Personnel Access Rights

Operator Operators only — run test programs and check test instruments. The Operator does not see the visualATE main menu.

Maintenance Operators and Maintenance engineers — Operator, plus the ability to configure, calibrate and verify installed instruments and save the results.

Engineering Engineers — write test programs, set program properties, run tests, manipulate results, check boards. Also access to Operator mode.

Programming Engineers — create list files, edit test function data and generate source code templates. Also access to Operator mode.

Sys Admin System administrator — Sys Admin mode only.



Users can have multiple privileges. When more than one selection is made for a user, that user can access all the environments allowed.

Figure 33. A New User with Defined Privileges

8. Click OKThe new user name appears in the list as shown in Figure 34. The checked privileges are shown in the status window below the list.

Figure 34. A Defined User Shown in the List

9. Repeat the preceding steps until all desired new users are createdOnce a user name and privileges are defined, assign the password following the instructions below. Each user password must be assigned individually.


Defining Users

To Create User Password1. Highlight the user name in the Edit User List

2. Click Change PasswordThe New Password dialog window appears, as shown in Figure 35.

Figure 35. The New Password Dialog

3. Type the password in the upper text entry field and press Enter

4. Retype the password in the lower field

5. Click OK

6. Repeat this process for each new user

7. Click Done (OK)The Edit User list dialog closes; the Users tab appears. If this is the final administration task, click OK to close the Sys Admin environment. If not, continue defining system properties by choosing the desired tab.



Editing and Deleting Existing UsersFor security, change the default Administrator password (or the entire ID, name and password both) as soon as possible. Periodically, change all users’ passwords, to prevent unauthorized access. Editing an user is identical to creating a new user, with the exception that the user is already listed in the dialog. The instructions below assume that the system administrator is logged on to visualATE and in the Sys Admin environment.

To Edit User IDEdit user IDs through the Edit Users function.

1. Select the Users tab

2. Click Edit Users

3. Highlight the user name in the list

4. Select Edit User

5. Follow steps 6 - 9 in “To create a new user”, and all of “To create a user password.”

6. Repeat until all users are edited

To Delete UserUsers can be deleted through the Delete User button.

1. Highlight the desired user name in the list

2. Select Del User

In visualATE, user access privileges are implemented by disabling menu and dialog selections.

Figure 36 shows the visualATE main menu for a user whose privileges are limited to Maintenance in the Edit User dialog choices. As shown, the restricted environments are grayed out and will not respond if selected.


Editing and Deleting Existing Users

Production users with access limited to the Operator environment do not even see the visualATE main menu. When an user with Operator privileges logs in, a Program Selection dialog appears where they choose the test program to be run. Menu selections are not displayed at all.

Figure 36. Maintenance and Operator Access for Same User



Setting the Operational Mode visualATE can be run in either Normal mode or in a Demonstration mode, set in the Programs tab shown in Figure 37.

Normal mode is the default condition for new installs, and is indicated by the “Demo Mode” check box not being checked. This manual assumes that systems are running under normal mode. This chapter, however, provides instructions for using the demonstration mode.

Figure 37. The Programs Tab

The Normal mode launches both ASL.exe and Test.exe. The Demonstration mode enables development tasks on systems with no installed tester hardware, but does not give full Operator and Engineering capabilities. Maintenance will not operate on systems running in Normal mode without installed tester hardware.

This section discusses setting up and switching between the two modes. Users must have system administrator rights to switch between Normal and Demonstration modes.


Setting the Operational Mode

Setting Up Normal ModeRunning in normal mode launches Test.exe on startup, and enables real-time hardware control. All production and development tasks are enabled in normal mode.

To access the most current test instrument data, visualATE must be set to extract information from Test.exe on startup. The information extracted is displayed in Maintenance, and includes calibration and checker information for all installed instruments. The normal operating condition on machines with hardware installed is to extract information from Test.exe on startup.

The default executable file is set to C:\asl_nt\system\bin\test.exe, in the visualATE installation directory. Although it should not be necessary, users can launch alternate Test.exe files or change the directory for the default in the Startup Conditions area of the Programs tab. To enable this feature and choose a directory, follow these steps:

NOTE — Credence Systems recommends not changing the default settings for “Extract information from Tester Executable on startup” and the location of the “Tester Executable Workspace File:.”

To Extract Information From Test.exe on Startup 1. Go to the Programs tab

2. Select “Extract information from Tester Executable on startup”A check mark appears in the check box.

To Choose an Alternate Tester Executable File 1. Click on Select

The Select Tester Executable File dialog window appears.

Figure 38. Select Tester Executable File Window



2. Navigate to the desired file and click OKFigure 2 shows the Tester Executable selection dialog

Setting Up the Demonstration ModeFor programming purposes, visualATE can be run in Demonstration mode. In this mode, development tasks are enabled regardless of whether test hardware is installed on the system. Lists and test programs can be created, and source code templates can be generated in Demo Mode. However, no component testing can take place because Test.exe is not used in Demo Mode, and the GUI will not communicate to the hardware control.

1. Go to the Programs tab in the System Properties dialog shown in Figure 37.

2. Select Demo Mode

NOTE — Test program changes are handled differently between Normal and Demo modes. In Normal mode, function parameters edited in Engineering may be visible in the run screen environment immediately after the change is made (see the following section). In Demo mode, exit Engineering and then reenter. The saved changes will now be evident in the Engineering run screen. The system administrator should alert Engineering users to this difference.

Setting an Event HandlerInformation about system configuration items such as program properties, lot summary data, and device data is passed into, and can be returned from, event handler procedures. Event handler procedures may display dialogs in the Operator environment that prompt an action or input by a production user. Credence Systems supplies event handlers upon request.

Event handler DLLs may be networked so that all production systems use the same event handler. See Chapter 6 for details on networking visualATE.


Configuring the Operator Environment

Configuring the Operator Environment Users limited to Operator privileges do not see the visualATE main menu. When an operator logs in, a dialog window appears, prompting them to open the desired test program. The settings in Figure 39 determine how these programs are accessed.

Figure 39. The Operator Tab in the System Properties Dialog

Show a List of Available ProgramsWith this item selected, available test programs are actively listed in the opening dialog window when a user logs on as an operator. The operator can run any of the listed programs by double-clicking the program name or highlighting the program name and then selecting Open.

Force Entry of Program NameThis option brings up a dialog with a blank text entry field. To start a test program, the operator must type the desired program name in this entry field.

Figure 40 shows how these two choices can be implemented.

The view on the left shows the opening Operator dialog with the list of available test programs.

The second view shows the forced entry option.



Forcing the operator to manually enter program names reduces the chance that listed programs with similar names will be confused. If the operator enters a program name incorrectly and no matching file name is found, visualATE generates an error message.

Figure 40. Operator Opening Dialog

Shutdown System When Leaving ProgramWith this option enabled, visualATE exits and returns the system to the Windows NT login screen every time a test program is closed. Users cannot access Windows NT features unless they have a login ID and password.

With the option disabled, closing programs in the Operator environment returns visualATE to its own login screen (the operator is logged out of visualATE).

The Operator Environment

Left: The “show list of availableprograms option is selectedBelow: The” force entry ofprogram name” option is shown

Opening Dialog


Defining Maintenance Program Options

Defining Maintenance Program OptionsThis tab is included primarily for Credence Systems use in configuring initial installs. The only time a system administrator would access this tab is if hardware has been specifically modified for their installation (such as when a proprietary board has been designed, etc.). In this case, consult with Credence Systems before making any changes to this test program configuration.

NOTE — Users who will not be altering test instruments should disregard this tab altogether.

Each test instrument type (DVI, TMU, etc.) has a series of program (*.prg extension) files associated with it that perform calibration, verification and diagnostics (checker).

The Maintenance tab is used to associate board types with the programs that will perform these maintenance tasks. visualATE is normally configured properly for the installed test instruments, however, users can assign alternate program files, generate maintenance files from DOS Maintenance Specification files, or define alternate directories for the programs.

Figure 41. The Maintenance Tab

1. Enter the Sys Admin environmentThe System Properties Dialog appears.

2. Select the Maintenance tab

3. Highlight the desired board type by clicking once on the three letter name of the test instrument (ACS, TMU, etc.)



4. Choose the desired option, “Select Checker Prg,” “Select Calibrate Prg,” or “Select Verify Prg.”The appropriate dialog browser appears. Figure 42 shows the Select Checker Program for Board dialog.

Figure 42. The Maintenance Program Selection Dialog (Checker)

5. Select the desired file then select OpenThe new program file appears in the Maintenance tab list and will now be used for the appropriate maintenance operation on the associated board type.


Editing Screen Properties

Editing Screen PropertiesIn Create and Engineering modes, the Format View button is available on the toolbar. Click this button to bring up the screen of Figure 43.

Figure 43. Format View Screen

Under the Program tab the Function, Active Function, Selection and Background colors may be modified. Font color, size and style may be modified as in Figure 44.

Figure 44. Format View - Program



The Datalog tab serves to alter the Title, Info Line, Header, and Datalog List of the datalog screens. Font colors, sizes, and styles may be changed for all portions of the Datalog screens as shown in Figure 45.

Figure 45. Format View - Datalog

The Create tab serves to modify the Function, Active Function, Selection and Background of Create screens. Font colors, sizes, and styles may be changed for the Function portion of the datalog screen as shown in Figure 46.

Figure 46. Format View - Create


Defining Printing Properties

Defining Printing PropertiesComplete datalog databases, selected portions of datalogs, and lot summaries can all be printed while in Operator mode. Only users with system administrator privileges can access the printing settings. Figure 47 shows the Printing tab in System Properties.

Margins and header/footer information is edited using the Printing tab of the System Properties dialog. The margins set here apply to all printed files; the header and footer information, however, is not added to lot summary printouts.

Header and footer information is specified as bracket symbols, which extract information from the file being printed. Up to three symbols each may be concatenated for the header and footer. Select the desired information using the pop-up menus in each field.

Datalog printouts match the screen, so if the Operator status field is visible on screen it will be included in the printout. The function key legend, however, does not print. Filtered data prints in the same manner that it displays on screen.

Figure 47. The Printing Tab

NOTE — For printing, the background color is set to white and all text colors are set to black.





5
SETTING DEFAULT PROGRAM PROPERTIES
Program properties determine a wide range of test program behaviors, from their appearance on screen to how the production user accesses a program. Program properties can be defined from within the Engineering editor or Sys Admin mode.

However, program properties set in the Sys Admin environment are default properties that are automatically assigned to each new test program created in Engineering. Conversely, properties set in Engineering apply only to the individual test program currently open for editing.

Once an engineer has changed the properties in the open test program (and saved the changes), the properties will remain as they are set. Any changes made to the default properties in Sys Admin will only apply to new test programs, or those converted from ASL-DOS.

81

5 - Setting Default Program Properties

The Default Program Properties DialogA Default Program Properties button in the Programs tab brings up a new dialog window with several tabs of its own. Program properties primarily determine test program behavior in the Operator environment, and include such variables as whether test results are datalogged, whether the program heading can be edited, and so on.

The program properties defined using these tabs establish the default settings for all programs. These defaults can be edited for individual test programs in the Engineering editor.

Each of the settings tabs are discussed individually in the following sections. All of them are accessed within the Default Program Properties dialog, shown in the next section. To open the Default Program Properties dialog, log onto visualATE with administrator privileges, go to the Sys Admin mode, and follow these steps:

To access the default properties dialog

1. Go to the Programs tab

2. Select Default Program Properties


Defining Production Program Handling

Defining Production Program HandlingThe options in this tab determine how test programs are handled in Operator mode. Define Operator properties by selecting the check boxes next to the desired items as shown in Figure 48.

NOTE — The following functions are not active in this dialog: Enable editing of the datalog header, Enable editing of lot summary, and Enable deletion of lot summary.

Figure 48. Default Program Properties, Operator Tab

Automatically Continue a Program After a Failed FunctionIf a test function fails (results are outside the limits), this feature causes the hardware program to skip all subsequent test functions. Results for the skipped functions are displayed as unknowns in the datalog.

Automatically Print on End of Lot: Lot Summary and Test Statistics

These options automatically bring up Windows NT dialogs at the end of a lot to print lot summaries and test statistics, respectively, to the system printer. Click OK in the print dialog to print lot summary or test statistics, or Cancel.



Automatically Upload File on End of LotThis command automatically sends a Standard Test Data Format (*.std extension), ASCII text format (*.txt), or spreadsheet format (*.spd) file of the completed lot to the directory specified in the Upload path text entry field. If no path is specified, files will be sent to the default datalog directory for the active test program file (C:\asl_nt\users\lists\list Name\Datalog).

Automatically Create a New Datalog on New Lot EventThis option causes a new datalog (*.dl4) file to be generated whenever an operator begins a new lot. When this option is disabled, new lots are appended to the current datalog file. The default datalog directory is C:\asl_nt\users\lists\list Name\Datalog. This directory may be changed in the Datalog tab of the Program Properties dialog.

Display Lot Summary By SiteWhen un-checked, data for all sites is in a one column format. If the box is checked, data for each site has its’ own column.

Disable Bin Bar Chart on Lot SummaryWhen checked, disables the Bin Bar Chart on the lot summary.

SelectDatalogs can be uploaded in formats other than the.dl4 of visualATE. They can be saved in STDF, Spreadsheet, or ASCII text formats. Also, you can upload Lot Summary and Test Statistics reports.

Enable Collection of Test StatisticsCheck this option to allow for the collection of test data during production testing.

Use Only Passed Devices in Test StatisticsWhen you wish to generate test statistics, check this option to use only test data that refers to passed devices.


Defining Production Program Handling

Calibration Expires in __ daysEnter the number of days after which test instrument calibration expires. Always check the actual calibration date before filling in this field. If you wish to prevent operation after the calibration expiration date, click the upper checkbox Abort Operator Program Load on Expiration.

Checker Expires in __ daysEnter the number of days after which the checker expires. If you wish to prevent operation after the checker expiration date, click the lower checkbox Abort Operator Program Load on Expiration.

Results summary lifetime (days)Datalog (*.dl4) files saved to the default directory location are deleted after the number of days specified here. This deletion takes effect when a particular test program is opened. Opening a test program invokes an analysis of the program’s datalog directory, when files older than the number of days specified are removed. Setting the number of days to zero disables the feature.

Arm Yield alarm at device count =Allows arming to be enabled after a designated number of tests. After an alarm the counter resets, and the alarm should not occur again until after the designated device count.

Fail alarm if yield percentage is < OR if consecutive fail count > =

Global alarm failure rate can be set by percentage or consecutive counts.



Defining Program SettingsThe default program settings defined in the Program tab determine how test programs-in-progress are displayed in the Engineering editor. These properties can be altered while in either Sys Admin or Engineering mode. Other system properties, however, can only be altered with system administrator privileges.

Define the settings by selecting the check box next to the desired item.

Figure 49. Default Program Properties, Program Tab

Display FunctionsThis feature identifies the sequence in which the functions will be performed during the test. Functions appear in descending order at the top of the window, beginning with the first one to be executed. Figure 50 shows a list of functions.

Figure 50. Engineering Editor with Function Numbers


Defining Program Settings

Display Tests for All FunctionsThis sets the default Engineering display to show all tests for each function listed one below the other. Tests can be displayed or hidden, but not wrapped as parameters can be. As with the parameter displays, the test settings can be changed within Engineering. This establishes the default only.

Figure 55 shows the Engineering editor with tests hidden and displayed.

Use Relative DLL PathChecking this button forces the system to use the debug path of the loaded file, not the default path.

Disable Lot-Sublot for EOW handlerWith the box in it's default mode, unchecked, visualATE creates a separate datalog (.dl4) for each wafer. If the box is checked, one datalog file will be created for all wafers in the lot.

QA RetestQA Retest allows a subset of devices of the lot to be tested against user defined QA limits in addition to traditional active limit sets. QA Retest avoids the necessity of using off-line QA sampling and provides in-line QA sampling. QA Retest is enabled by checking the appropriate box in the program properties. On program load, the operator can then access the QA Retest sampling setup window, which enables the QA Retest sampling algorithm. During testing VisualATE manages the process of switching between the specified QA parameters. Separate QA datalogs are generated, and have the same properties as the regular final test datalogs.(i.e., same as STDF, ASCII, etc.)

To set up QA Retest follow these steps:

1. Enter visualATE engineering mode and select program.

2. Select View->Limit Sets from toolbar.



3. Create and select the desired FT limit set and click Activate. Do the same for the QA limits and select SetQA.

Figure 51. Figure 5-4 Limit Sets

4. Select View->Program Properties from toolbar.

5. Select Program tab.

6. Check the Enable QA Retest box.

7. Set the default Final Test Limit Set and QA Limit Set. Options for the Limit Sets are FT (Final Test), and QA.

Figure 52. Enabling QA Retest



8. Switch to the Datalog Screen and select the “New Lot” button. The screen shown in Figure 5-6 will appear.

Figure 53. QA Retest New Lot Control

9. Enter into LotID the name of the QA datalog.

10. Enter into Lot Size the total number of devices in the entire lot. Lot Size is used to set the frequency of QA testing. (i.e., 100/20 = 5; one out of every 5 devices are QA tested.)

11. Enter in QA Sampling Size the number of devices to be tested with QA limits.

12. Run the test program. The split screen, in, was achieved Figure 54 by “tiling” the windows horizontally and minimizing the Program Window. This is only allowable in Engineering mode.



NOTE — QA title for the QA Retest Datalog, and the default title for FT is Datalog.

Figure 54. QA Retest Datalog and Datalog Tiled



Figure 55. Two Views of the Engineering Editor Upper left: Two functions with unwrapped parameters. Lower right: A function with unwrapped parameters, tests and the comments column displayed.



Defining Datalog HandlingDatalog properties are defined in the Default Program Properties Datalog tab, shown in the figure below. Set defaults by clicking in the check box next to the item or entering a value in the text entry fields.

Figure 56. Default Program Properties, Datalog Tab

Log Data to File This option sends device results from the running test program to the Engineering run screen. Test results are saved using the path and name assigned in the text entry fields at the bottom of the screen. If no name or path is defined in this dialog, the default directory path is used: C:\asl_nt\users\lists\list Name\Datalog. If this command is disabled, test results will not be saved.

Log Passed Device Results This function causes passing device results to be logged.

Log Failed Device Results (unconditionally)This function causes failed device results to be logged.


Defining Datalog Handling

Commit Datalog to File After Every DeviceSelected, this saves the datalogged results to disk after each device result. Data written to disk will be preserved in the event of a system failure.

Fractional SavingTo reduce file size, save fractions of the devices tested results from a test instead of all the device results. visualATE saves the fraction of the test results entered here. Typing “2” saves one half of the devices, typing “3” saves one third of the devices, and so on. The default setting is 1, which saves all of the devices.

NOTE — This feature is disabled if the “Log passed device results” option is not checked.

With fractional saving, the first result of each fraction is saved. For example, if “10” is entered in the field, visualATE will save one tenth of the test devices. Further, the first of each ten devices will be saved - e.g., in a group of 30, device results 1, 11, and 21 will be saved. This method saves devices in a consistent pattern.

Fractional results are saved according to the options selected for all datalogs. In other words, logging passed results adds the failed device results to the lot summary, but not to the datalog, regardless of whether 100% or some fraction of the results are saved.

Datalog LifetimeDatalog files in the default location (or designated location) are automatically deleted after the number of days entered in the “Auto datalog lifetime (days)” field. This feature operates on test program startup. Setting the number of days to zero disables the feature.

Datalog File Name and LocationTo override the visualATE default datalog directory, assign a datalog file name and directory path here, using the syntax: C:\my_dlog\device_family\device_name\category. Note there is no trailing backslash or file name. The visualATE default is: C:\asl_nt\users\lists\list Name\Datalog.



Setting Handler PropertiesThe Handler tab in Default Program Properties shows a read-only list of handlers that are available to the system. Test.exe manages and communicates this information to ASL.exe. On systems without hardware installed, this dialog will be blank.

The active handler is highlighted in the list and identified next to the Set Active Handler button in the dialog. To change handlers, highlight the desired handler and select the Set Active Handler button.

Figure 57. Default Program Properties Dialog, Handler Tab Selected

The Bins: and Sites: labels show the number of device bins and test sites that the active handler can manage at one time.

The Active Sites area shows the number of devices being handled in a particular setup. This is a program-specific setting, so these sites cannot be edited in the Sys Admin environment, only in Engineering.

Prober Control of Wafer LOTCheck this box if an intelligent prober is controlling the lot.

Suppress OnNewLot Wafer DialogCheck this box if an intelligent prober is controlling the lot and it is not desired to have the wafer dialog box appear.


Assigning Bin Defaults

Assigning Bin DefaultsvisualATE 32 software bins, allowing up to 32 device categories:

• Bins 1-4 are reserved for passing devices, while

• Bins 5-32 are designated for failures.

Software binsIf multiple pass bins are set, then the devices meeting the tightest limits pass into bin 1 (for example, those devices meeting specifications for designated military grade). Devices passing at the next tightest limits pass into bin 2, and so forth. Failing bins are normally used to sort devices by type of failure.

Each bin may be assigned a name that displays in the lot summary and bin bar charts (in the Engineering run screen and Operator environment). Software bins may each be mapped to a hardware bin on the handler, which physically sorts the tested devices.

Normally, software bins 5-32 are mapped to a single hardware bin.

Bin defaults are set in two tabs, Bins (1-16) and Bins (17-32), as shown in Figure 58.

Figure 58. Default Program Properties Dialog, Bins (1-16) Tab

All values must be typed into the fields in these two bin tabs, as there are no pull-down menus or radio buttons. Percentage fields are limited to two characters.



Setting Alarm LevelsSetting an alarm for a fail bin forces operators to stop the lot, encouraging them to investigate the reason for the failures.

The Alarm Percentage refers to the portion of devices that are present in any given bin.

The Alarm Count refers to the consecutive number of devices. Use both the count and percentage together to avoid triggering alarms when the first device of a lot fails. (At the first device, the result is 100% of the bin total, so a failure signals a 100% failure rate for the bin and triggers the alarm.)

An alarm occurs when both the Alarm Percentage and Alarm Count values are exceeded.

NOTE — The “Set Alarm Clear Password” feature applies to these alarms. Setting a password control keeps the Operator from continuing to test parts until an authorized user has entered the password.

To keep an alarm from occurring on a pass bin, set the percentage at 0% to disable the alarm.

Add Hardware Bins to the Lot SummaryDisplays bin information in the lot summary.


Defining Setup Defaults

Defining Setup DefaultsUsers will not access this tab very often because Credence Systems supplies each system shipped with the maintenance programs configured for the tester hardware. However, if tester hardware is updated, the user may make some changes to the programs. Contact Credence Systems Customer Service for assistance.

Maintenance programs require special information. All programs written to test parts will be of program type “standard.”

Figure 59. The Setup Tab



Defining File NamesDevice results can be saved automatically in several file types. Using the File Names tab, a system administrator can set a default name and path for saved results files.

Figure 60. The File Names Tab


Setting Version Control Options

Setting Version Control OptionsVersion control is useful for identifying the date and time a file was created or modified. Version control uses the standard Windows NT feature that creates a date and time stamp for each file when it is created, accessed, modified (and the changes saved), or saved under another name.

Whenever a test program or its associated files are modified in any way, the time stamp on the file will be updated. This occurs both when actual changes are made to the test program, and also each time settings are changed in the Program Properties dialog. visualATE searches for the most recent version of all related files (DLL, list, and so on) every time the test program is opened, and assigns the most recent time stamp as the version number for the test program.

Version Control provides several choices of time stamp: by test program, DLL, source code (*.cpp and *.h) files, or list file. Any single option can be selected, or any combination can be used. If multiple choices are selected, visualATE will use the most recent of the files as the version number.

The test program version is displayed in the title bar and information bar of the Engineering run screen and the Operator screen.

If version control is not enabled, the running test program is labeled with the program name, followed by the phrase “no version #”. If the time stamp has been enabled in the Version Control dialog, then the selected time stamp displays after the program name.



The screens in Figure 61 illustrate the effect of the time stamp.

Figure 61. The Version Control Tab and its Effect

.PRG Time Stamp Displays in Datalog

No Time Stamp Selected; “No Version #” Displays in Datalog


Enabling AutoCorrelation

Enabling AutoCorrelationvisualATE includes a feature designed to verify the tester accuracy in running a specific test program for a particular device, or family of devices. AutoCorrelation can be enabled or disabled for any individual test program on an visualATE system. Generally, in production environments using AutoCorrelation, all test programs released for production will use this process to verify the tester hardware before testing a device lot.

To use AutoCorrelation, a test engineer first writes and runs a program to be verified. Some sample devices that pass with good results (usually those closest to the median value between the minimum and maximum limits) are selected and assigned unique serial numbers. These devices are known as Golden Devices. The passing values on these Golden Devices are saved as initial values in a datalog file. Tolerances for variance from these values are then defined and saved.

Once the initial golden values and the variance tolerances are defined, one Golden Device is retested with the same test program that produced the initial passing values. The tolerances are checked, and if the retest results are within the tolerance level, then AutoCorrelation has passed. If any results are outside the allowed tolerances, the AutoCorrelation has failed. More complete details on implementing AutoCorrelation into specific programs are included in Chapter 10, The Engineering Program Editor.

AutoCorrelation can be enabled through the Default Program Properties dialog in either the Sys Admin or Engineering environments. When AutoCorrelation is enabled for a particular program, the tester using Operator mode must run a correlation at the start of each new lot.



Figure 62 shows the AutoCorrelation dialog.

Figure 62. AutoCorrelation Tab in the Default Program Properties

To enable AutoCorrelate follow these steps:

1. Start the visualATE in Sys Admin mode

2. Tab through the dialog to Programs -> Default Program Properties -> AutoCorrelate

3. Check the AutoCorrelation Enabled check box

AutoCorrelate can be set to automatically print and/or save correlation reports. Enable either of these options by checking the box to the left of the item, and specifying a directory location for the saved report files. Report files are saved in ASCII text (*.txt), and can be opened in visualATE or any text editor.

Specified Number Usage EnabledEnables a specified number to be used as a hold-off before enabling Auto Correlation.

Validate Both AutoCorrelation Data and Limits Sets When enabled, visualATE compares the data and limit sets with initial data looking for a match. If no initial data exists for this device and limit set, then an error message is generated.



6
THE NETWORKED visualATE SYSTEM
visualATE takes advantage of the Windows NT networking capabilities. System files, test programs, source code, event handler DLLs, and production data can all be stored in a central network location. This chapter describes how to set up a network environment using visualATE.

103

6 - The Networked visualATE System

IntroductionThis chapter provides a step by step procedure for setting up a network environment for the Credence ASL Test System platform running under visualATE. It is assumed that the tester has already been physically connected to the network and that the network can be seen by Network Neighborhood. It also assumes that all users have an account set up by the system administrator.

When this procedure is finished, your networked test environment will be able to do the following:

1. Download a production test program on one or more systems simultaneously for running production product. Upload datalog information to the network

2. Copy an engineering program down to a local system from the network for development.

This document explains how visualATE can work over a network. Also included is a section explaining what visualATE cannot do over a network.


Network Setup

Network SetupThe first step in setting up the network environment is done by the customers MIS department or someone who has permissions to be able to create, delete, and assign permissions to directories on the network we will refer to this person as the “system administrator” throughout this document. We will assume here that the network drive we will use is called (mapped as) Test. Next, we will create 4 subfolders in Test. The resultant folder structure will look like this:

Test |----Engineering |----Production |----Program_Control |----Datalogs

The Engineering folder will contain all visualATE Lists still under development or revision by test (or product) engineering. Read and write permissions in this folder are for test and product engineers only.

The Production folder will contain only the .dll and .prg files for released production test programs. The permissions for this folder will be Read-Only for everyone except the system administrator.

The Program Control folder will contain all Lists related to the test programs in the Production folder. This folder will act as a document control area. The permissions for this folder will be Read-Only for everyone except the system administrator.

The Datalogs folder is where all datalogs from engineering and production will be stored. Read and write permissions in this folder will be given to test and product engineers only.

We now have our network environment set up. Now we will work with visualATE to set up the engineering and production environment on the test floor.



Engineering Program Setup1. The system administrator logs on at the Tester.

2. In the NT Workspace, copy and paste the “Run visualATE” shortcut so that there are now two (2) “Run visualATE” shortcuts.

3. Right-click on one of them and select Rename from the menu.

4. Rename the shortcut to Engineering.

5. Right-click on the Engineering shortcut and select Properties from the menu.

6. The Properties box will now open as in Figure 63. Select the Shortcut tab. In the Target field, type the following:

a. If your visualATE software revision is 4.42.00 or higher, use:C:\Asl_nt\System\Bin\Asl.exe C:\ASL_NT\SYSTEM\CONFIG\USERS.XXX /NetConfigPath=\\Test\Engineering

b. If your visualATE software revision is older than 4.42.00, use:C:\Asl_nt\System\Bin\Asl.exe C:\ASL_NT\SYSTEM\CONFIG\USERS.INI /NetConfigPath=\\Test\Engineering

Leave all other settings as they are.

7. Select Apply, then select OK.

Figure 63. Entering Network Path in Engineering Properties


Engineering Program Setup

Here is a practical example - let’s assume the List we want to move to the network is called LM123

1. Launch visualATE from the local drive using the Run visualATE shortcut.

2. Select Engineering.

3. From the program selection list choose lm123.

4. In the Engineering screen, go to Program Properties and choose the Program tab.

5. Make sure the “Use Relative DLL Path” box is checked.

6. Select the Datalog tab.

7. In the Datalog File Location field, type the following:\\Test\Datalogs

8. Select the OK button

9. Save and close the test program, and then exit visualATE.

10. Launch Windows NT Explorer and copy the following folder:C:\Asl_nt\Users\Lists\LM123

11. Paste this folder into \\Test\Engineering.

12. Launch visualATE from the local drive using the Run visualATE shortcut.


14. Delete the lm123 test program from the Program Selection List.

15. Insert the lm123 program back into the Program Selection List but use the Browse button and get the .prg file from the network not the local drive. The desired .prg file will be in \\Test\Engineering\LM123\Programs.

16. Close visualATE.

17. Launch Windows NT Explorer and copy the following two files:*C:\Asl_nt\System\Config Users.INIC:\Asl_nt\System\Config Defaults.DB

18. Paste these two files into \\Test\Engineering and close Windows NT Explorer.



19. For any subsequent addition or removal of .prg files from the Program Selection List, you will need to go to Program tab inside ‘Sys Admin’ and press “Upload present configuration…” button (shown in the example window below). This needs to be done to update the program list in the network otherwise programs added or removed will not be displayed the next time you open the Program List.

20. You can now launch visualATE using the Engineering shortcut. The program(s) appearing in the Operator and Engineering Program Selection List is the program residing on the network drive.


Production Program Setup

Production Program SetupNow that an Engineering shortcut has been created we must now create one for the operators and call it Production.

1. The system administrator logs on at the Tester.

2. In the NT Workspace, copy and paste the Run visualATE shortcut so that there are now two Run visualATE shortcuts.

3. Right-click on one of them and select Rename from the menu.

4. Rename the shortcut to Production.

5. Right-click on the Production shortcut and select Properties from the menu.

6. The Properties box will now open. Select the Shortcut tab.

7. In the Target field, type the following:

If your visualATE software revision is 4.42.00 or higher, use:C:\Asl_nt\System\Bin\Asl.exe C:\ASL_NT\SYSTEM\CONFIG\USERS.XXX /NetConfigPath=\\Test\Production

On visualATE revisions older than 4.42.00, use:C:\Asl_nt\System\Bin\Asl.exe / C:\ASL_NT\SYSTEM\CONFIG\USERS.INI /NetConfigPath=\\Test\Production

8. Select the Apply button then OK.

9. Launch Windows NT Explorer and copy the following two files:*C:\Asl_nt\System\Config Users.INI C:\Asl_nt\System\Config Defaults.DB

10. Paste these two files into \\Test\Production and close Windows NT Explorer.

11. Since we already moved LM123 to the network during the Engineering set-up all we need to do is move the .dll and .prg files over to Production. We must first set up some folders in the Production folder to keep things organized and to take advantage of the Relative DLL feature. In the \\Test\Production folder, create a subfolder called LM123. In this subfolder, create two additional subfolders and call them Debug and Programs. Your Production folder should now look like this:

Test|----Production

|----LM123|----Debug

|----Programs

12. Copy \\Test\Engineering\LM123\Debug\lm123.dll and paste it into \\Test\Production\LM123\Debug



13. Copy \\Test\Engineering\LM123\Programs\lm123.prg and paste into \\Test\Production\LM123\Programs

14. Right click on \\Test\Production\LM123\lm123.prg and select Properties from the menu.

15. Change the property of this program to Read Only. Click Apply, then OK.

16. Launch visualATE Production shortcut.


18. Delete the lm123 test program from the Program Selection List.

19. Insert the lm123 program back into the Program Selection List but use the browser and get the .prg file from the network not the local drive. The desired .prg file will be in \\Test\Production\LM123\Programs.

20. Close visualATE.

21. Launch Windows NT Explorer and copy the following two files:* C:\Asl_nt\System\Config Users.INI

C:\Asl_nt\System\Config Defaults.DB

22. Paste these two files into \\Test\Production and close Windows NT Explorer.

For any subsequent addition or removal of .prg files from the Program Selection List you need to go to Program tab inside ‘Sys Admin’ and press “Upload present configuration…” button. This updates the program list in the network otherwise programs added or removed will not be displayed the next time you open the Program List.

You can now launch visualATE using the Production shortcut. The program(s) appearing in the Operator and Engineering Program Selection List is the program residing on the network drive in the \\Test\Production folder. Since this program has its property set to Read-Only, it cannot be modified and is in no danger of being tampered with by anyone except the system administrator.

To control access to engineering and production test programs, the system administrator should configure the NT workspace on each of the systems on the test floor by log on permissions. Engineers logging on to Windows NT on the test floor should be allowed to see the NT workspace and both the Engineering and Production visualATE shortcuts. Operators on the other hand should not see the NT workspace. The systems should be configured so that when an operator logs on, the Windows NT Start-Up procedure will launch visualATE from the Production shortcut automatically. In addition there is a System Property that can be set in visualATE that will automatically log off of Windows NT should an operator close visualATE thereby preventing an operator from ever seeing the NT workspace. To activate this feature, log on to visualATE with Administrator privilege. Go to Sys Admin->Operator. Select the box labeled “Shutdown System When Leaving Program”.


Production Program Setup

See example of System Property->Operator page window in Figure 64.

Figure 64. Operator System Properties



Program Control Folder SetupThe Program_control folder is to be used as a storage area for program control. This folder will act as a back-up directory for all released production Lists. The system administrator should be the only one with permission to access this folder. When a Test Engineer releases a program to production, the system administrator should copy the entire List folder from the Engineering folder and past it into the Program_control folder.


Example of a Production Program Release

Example of a Production Program ReleaseThe Test Engineer has completed all development on LM123 and wishes to release it to production.

1. The Test Engineer notifies the system administrator that they would like to release LM123 to Production.

2. The system administrator makes a copy of the entire LM123 folder and pastes this folder into \\Test\Program_control

3. The system administrator creates a folder structure in the Production folder on the Test drive as follows:

Test |----Production

|----LM123|----Debug

|----Programs

4. The system administrator then copies lm123.dll file from \\Test\Program_control\LM123\Debug folder and pastes it into \\Test\Production\LM123\Debug.

5. The system administrator then copies lm123.prg file from \\Test\Program_control\LM123\Programs folder and pastes it into \\Test\Production\LM123\Programs.

6. The system administrator will now change the properties of the lm123.prg file in \\Test\Production\LM123\Programs to Read-Only.



Supported Networking OperationsThe following network operations are supported.

1. Send datalog / stdf / ascii / spreadsheet format file to a remote computer on end of lot.Usually this setup is created by the test engineer or system administrator to send output files to a central location. Please consult the visualATE manual for more information about how to do this.

2. Run a program that is installed on a remote computerUsually this setup is created at a production facility that wants to run production on several systems using the same program or set of programs.The user/operator at each visualATE computer does not have the ability to modify the program that is installed on the remote computer.

3. Share the users and system properties on a remote computerUsually this setup is created at a production facility where the system administrator wants to have each operator presented with the same login options and the same set of programs.

NOTE — All installations of visualATE that use this option must have the same version number. It is possible to corrupt the system properties database by sharing it among different versions of visualATE.


Unsupported Networking Operations

Unsupported Networking OperationsThe following operations are not supported by visualATE.

1. Editing programs on a remote computer.Always copy programs to you local (c:\asl_nt\users\lists) directory before running ENGINEERING or CREATE on them.

2. Mixing visualATE Versions on programs or lists that are being edited.You must not attempt to run or edit a program or list on an version of visualATE that is older than the version that was last used to edit the list or program. Specifically:For example: Do not edit a list or program under Version 4.4x.xx and then try to run or edit the same list or program under Version 4.3x.xx.Compatibility is maintained so that it is possible to edit a program or list under Version 4.42.xx and then open or edit the same list or program under any other version of 4.42.xx. In other works, once a software version is released, its database's schemes do not change.

3. Remote installations of visualATEDo not try to install visualATE anywhere except on the C: drive of the computer that runs it.Do not copy any configuration files to other drive letters or computers, other than users.xxx and defaults.db.visualATE can become confused about where its configuration files, for hardware on your system, are located if you make copies of these files; don't do it.





7
visualATE/ASL-DOS CONVERSIONS
This chapter is for the benefit of those users who are familiar with the earlier ASL-DOS systems and are now upgrading. The two programs are structured somewhat differently, as described here. This chapter assumes familiarity with DOS as it discusses ASL-DOS and visualATE.

117

7 - visualATE/ASL-DOS Conversions

Moving Files Between DOS and NTFiles can be ported between ASL-DOS software (3.02e or later) and visualATE. Both software systems must be installed on the same system CPU, and DOS files must be imported before they can be converted.

visualATE is equipped with a wizard to simplify conversions. All processes described in this chapter take place in the Wizard dialog, as shown in Figure 65. You must have system administrator privileges to access the wizard.

Figure 65. visualATE Convert Wizard


Converting DOS Files to NT

Converting DOS Files to NTConverting files involves bringing the file into visualATE, assigning the converted files to projects in Microsoft Visual C++, and editing the source code.

Before conversion, the files must be renamed. There are two guidelines for naming test functions that will be converted:

• Do not use a space as the first character in the English name

• Give each test function a unique name

DOS test functions that are to be converted must have a character (as opposed to a blank space) as the first item in the English name. (This is the function description in ASL-DOS.) Initial spaces cause problems in conversion because visualATE inserts an underscore. This underscore forms a single word with its respective declaration, resulting in compile errors.

To check for spaces at the beginning of function descriptions, go into ASL-DOS Create and press F3 to see the list. Lists are displayed with the C language name on the left and the English name on the right. All English names beginning with a character will line up along the left margin. English names that begin with spaces will be indented slightly. C names cannot have a space.

Test functions must have unique names because when test functions defined in User.cpp share names with functions in the list, the code will not compile correctly. Test functions with the same name set up a cycle in which the test function acts as if it is calling a test function. This action is not possible, so compile errors occur.

If all files are correctly named and resident on the visualATE system, proceed to the step-by-step instructions for converting files, immediately following. If the target files are not resident on the visualATE system, see the following subsection for details.

1. Start visualATE

2. Start the Sys Admin or Engineering environmentIn Engineering:

a. a. Go to View -> System Administration The System Properties dialog appears.

b. b. Select the Convert tab

In Sys Admin:

a. a. Select the Convert tab

3. Select DOS -> NT Wizard

4. Select the DOS Installation Drive letter in the pop-up menuAt this time, the only drive choice is C, which is selected by default. Do not type in an alternate letter, or the Convert Wizard will close.


7 - visualATE/ASL-DOS Conversions

Select the files to be converted (multiple files can be selected at one time)

The DOS -> NT Wizard appears as in Figure 66, the available DOS files listed.

Figure 66. The DOS->NT Wizard Dialog with a Convert in Progress

5. Select ConvertFiles are converted to the visualATE install drive, which appears in the Destination field. During the process, the file being converted is displayed in the Status heading field, and the conversion’s progress, including any errors, is shown in the status window. When the conversion is complete, the status window displays a “finished converting” message.

6. Note any errors in the conversion Errors are usually the result of an incomplete DOS test program or an earlier version of DOS. If errors occur, check the ASL-DOS software (must be 3.02e or later), and the DOS program file.

To compile the source code:

Go to Build -> Build filename.dll, OR Press F7

Once the converted file source code has been compiled, the list file is ready to use in visualATE. Converted lists behave exactly the same as lists created in visualATE. See the “Creating Lists and Generating Source Files” chapter for details on working with lists.



8
CREATING LISTS AND GENERATINGSOURCE FILES
This chapter focuses on the features of Create, showing how to create lists and generate source files.

121

8 - Creating Lists and Generating Source Files

Steps to Create DLLsvisualATE is designed to make writing source code for automated test programs easier by automatically generating C++ header files and source files from user-entered parameters. These templates are generated in the Create environment, and then edited and compiled into complete function libraries (DLLs) in Microsoft Visual C++.

The lists (description files, *.lst extension) are the master files for user function libraries, from which you can create any number of test programs. List files serve several purposes:

• define the structure of the test programs

• define default parameters and subtest limits

• set board allocations

• generate source code templates.

Creating a list involves the following steps:

• Open or create a list file

• Define test functions (the code that executes a test) within a list

• Assign default parameters and default limits to each function

• Configure the installed instrument cards

Once a list file has been created, the next step is to generate source code templates using the menu command in the Create editor.

To complete the DLL file, the following steps are necessary:

• Edit the generated code templates in Visual C++

• Add Credence Systems-supplied codes and/or other instructions

• Compile and debug the code

The complete, customized DLL is now available for use in creating numerous test programs.

Debugging is explained later on in this manual. For programming references see the visualATE Programming Guide.


Steps to Create DLLs

The software and hardware information transfer path is described Figure 67, followed by a written outline of the process.

Figure 67. The Create Process

Step 1. When you activate Generate Source Code from within Create, visualATE uses the contents of the list (.lst) to generate header and source code files and a project file for Visual C++.

Step 2. When instructed by you, Visual C++ builds the DLL from the project and source code files generated from the lists written in Create.

visualATE Create Mode

MS Visual Studio

List Files*.lst

Source Code andMS Developer Project Files

*.cpp, *.h, *.dsp, *.dsw

Dynamic LinkLibrary (DLL)

Function Library*.dll

Step 1 Step 2



List File Directories visualATE automatically saves list files, associated test programs, and source code to a default directory created during installation. If possible, maintain this directory structure, so that visualATE can find files as they are needed. Instructions for moving files between machines and sharing files over a network assume this file structure is in place. If it is necessary to place files in an alternative directory, the alternative path may be set in the Program Properties for each test program as shown in the “Writing and Working with Test Programs in Engineering” chapter of this manual.

Executing the “Generate Source Code” command in Create generates a subdirectory for the parent list in the same “Lists” folder.

The subdirectory folder has the same name as the associated list, but no file extension: C:\asl_nt\users\lists\listname\.

When a list is created and saved, the *.lst file is added to the directory C:\asl_nt\users\lists\listname\listname.lst.

Several subfolders are created within this subdirectory for each list, as shown in the table below. These subfolders organize the supporting files associated with the list: generated source code, test programs, and datalogs.

Table 4 outlines the complete directory for a list, while Figure 68 immediately following it shows the file structure as it appears in Windows Explorer.

Table 4. Directories for lists

Directory and Folder Description

\asl_nt\users\lists Contains the list folders (same name, no extension)

\asl_nt\users\lists\listname Contains the source code (*.cpp) and header (*.h), files for each function in the list; plus the Visual C++ project (*.dsp) and workspace (*.dsw) files, and one.lst file

asl_nt\users\lists\listname\debug Contains the DLL (*.dll extension) built from the completed code files, along with associated object files and intermediate files

\asl_nt\users\lists\listname\programs Test programs (*.prg) created from this list (in the Engineering environment) are stored here

\asl_nt\users\lists\listname\datalog Datalogs and summary files of the above test programs are placed here (*.dl4 files, *.ls4 files)


List File Directories

Figure 68. File Structure in Explorer

visualATE directorywith the Lists folder opened.

Note that for each list, there is a folder with the samename, without the *.lst extension.

The right side of the screenshows the contents of theExample_adc1061 folder.



Opening Create1. Start visualATE

2. Select Create from the main menu. The List Selection window appears.

3. Open the desired list:

a. double-click the list name OR highlight the list name

b. Select Open

The list file opens the Create editor. All Create capabilities are now available.

NOTE — In a new install, no list files are shown in the window. To use the Create mode features, list files must be created or inserted as described in the next section.

The List Selection Window Remove takes a file off the list, but does not delete the list file from the disk. A removed list file remains available and can be added to the list selections again later.

Insert adds an existing list file to the window. Selecting Insert brings up a directory browser to search for and choose the desired file. The inserted file is visible in List Selection immediately.

NOTE — List files created in DOS must be converted to visualATE list files using the DOS-NT Wizard in the Sys Admin mode (see Chapter 7) before they can be inserted into list selection or modified in Create.

Choosing New creates a new list file containing a single function and brings up the Create editor. New files are discussed in more detail in the following section.



Once lists have been identified, they will appear in this window when Create is started.

Figure 69. List Selection Window

Creating a New List (.lst) File To create a new list (.lst) file follow these steps:

1. Select New from the choices in the List Selection window A dialog box appears, containing a default name for the list as in the figure below. The default naming convention for new lists is based on the file creation date and time as follows: New_List_year_month_day_hour_minute_second.

Figure 70. The New List Names Dialog Window

2. Rename the list

3. Select OK, or press the Return key

The Create editor opens a new list with one default function, as shown in Figure 73.

The “List Properties” matrix in Figure 71 performs two functions:



• Allows the user to select the instrument set for this particular list, and

• Allows Create to generate the instrument board pointer used during coding to program the instrument board. See Figure 72.

Figure 71. List Properties Matrix

Figure 72. Instrument Board Pointers Declared in user.cpp



Figure 73. A New List Opened in the Create Editor

The new list is ready to edit, and will appear in the List Selection window the next time Create is launched from the visualATE menu. See the “Editing Lists” section in this chapter for complete editing reference.

NOTE — Lists are designed to organize test function code by device type. For example, create one list with all related functions for testing comparators, another list for voltage regulators, another list for a timer, and so on.

Inserting an Existing List (.lst) File 1. Select Insert from the choices in the List Selection window

A directory browser appears with the selection window open to the lists directory that visualATE created during installation. Only files with the .lst extension can be added to List Selection.

2. Choose the desired file and select Open The List Selection window returns, displaying the inserted file name.

3. Open the file from within List Selection

The inserted list file is ready to edit. See the “Editing Lists” section in this chapter for complete editing reference.



Working with the Create EditorOpening any list file shown in the List Selection window brings up the Create editor. Create operates in a manner similar to other Windows applications, where data is entered by highlighting and typing over the existing entry or placeholder text. Clicking on buttons brings up pop-up menus of parameter formats and measurement units.

Figure 74. Create Editor

The data entered in this screen defines the parameters that determine how the function operates. These parameters can be changed in Engineering to customize the function’s behavior for an individual test program.

To illustrate this, see Figure 75. The ib_dual function pictured is used to measure the bias currents of a dual opamp. The parameters include the device power supply voltages Vsup Pos (positive voltage supply) and Vsup Neg (negative voltage supply). Entering these values as passed parameters makes the function versatile enough to test dual supply devices using ± 15 V or ± 5 V supplies, as well as single supply devices where Vsup Neg is 0.0 V.

The function can be customized for these different devices without re-compiling the source code. These parameters declare a variable with a C++ type and a name. visualATE uses this information to build a structure that contains all of the parameters, and makes the structure available in the source code file.


Working with the Create Editor

Displaying Test Function Information Test function data can be displayed in four ways (See Figure 76):

• As a compact list showing the function names only

• Complete functions with parameters and tests showing

• Functions with parameters showing and tests hidden

• Functions with tests showing and parameters hidden

Figure 75 shows side-by-side views of the Create editor. The left view is a list of function names, the right is a function with parameters displayed. The figure in the preceding section shows a function with both parameters and subtests displayed. In any view, function numbers can be displayed or hidden.

Figure 75. Two views of the Create Editor



Parameter and test displays can be accessed by the View menu or the taskbar shortcut buttons, shown in Figure 76.

Figure 76. The Create Toolbar

New list files open a default function with default parameters and default subtests displayed.

To display the function without parametersGo to View -> Hide All ParametersORClick on the toolbar button

To display functions without testsGo to View -> Show All Subtests ORClick on the toolbar button

Toggle Parameters Visual C++ Online Help

Toggle Subtests



Entering Test Function Information Enter information by one of three ways:

• Overwriting placeholder text (in a new list) or existing data (in an existing list file)

• Copying, cutting and pasting

• Dragging and dropping

Overwriting Test Parameters or Values Overwriting text in the Create editor is similar to any other Windows application. Clicking once on a text entry opens an editing field around the entry, with an active cursor at the insertion point. Double-clicking opens the editing field with the text highlighted. As with other Windows applications, typing over highlighted text completely overwrites the entry; typing at an active cursor point adds the new text beginning with the insertion point.

To Overwrite Data:

1. Double-click on the item to be edited

2. Type the new information over the existing data

Copying, Cutting, and Pasting Use Cut, Copy and Paste commands in the Create Edit Menu to move data between functions and lists. Single parameters, tests and functions and blocks of parameters and tests can be copied and pasted. Parameters and tests can be transferred between different functions.

To copy or cut and paste a single parameter or test1. Click in the Edit Bar to the extreme left of the line to be copied

2. Hold the right mouse button down and drag the cursor down until all lines of the parameter or test fields are highlighted.

3. Go to Edit -> Copy to copy the data ORGo to Edit -> Cut to remove the data The data is now in buffer memory and can be pasted into another function.

4. Click in the Edit Bar to the extreme left of the parameter or test to be replaced

5. Drag the cursor down until the entire parameter or test to be replaced is highlighted.



6. Go to Edit -> Paste -> Overwrite ValuesThe copied or cut data appears in the new position. Other menu items that may be enabled, depending on the type of data in memory are:

• Paste-Insert Parameters is enabled when an entire parameter was copied

• Paste-Insert Subtests is enabled when a test has been copied

Figure 77 shows an example of using the Create editor.

Figure 77. The Create Editor Fields

A single parameter field includes all space horizontally across the screen, starting with thetype and name

A block of parametersincludes all space horizontallyacross the screen, from thetop of the first selectedparameter to the bottom of the

A single test field includes all space horizontally across the screen starting with thesubtest number and name(the number cannot be edited)

A block of tests includesall space horizontally acrossthe screen, from the top of thefirst selected subtest to thebottom of the last selected A function field includes all space between gridlines

(function, parameters and tests)

last selected parameter



To copy or cut and paste multiple parameters or subtests 1. Follow the above procedure, making sure to drag the mouse down until all desired

values in the multiple items are highlighted.

2. Go to Edit -> Copy to copy the dataOREdit -> Cut to remove the data

3. Go to Edit -> Paste -> Overwrite Values

The values on that line are overwritten with the copied values.

Copying and pasting test functionsFunctions can be copied and pasted following the procedures outlined for copying parameters and tests. Highlight all data within the gridlines to copy a complete function. Copy the function using the Edit menu. In the Edit menu, the Paste-Insert Functions command will be enabled.

Dragging and Dropping Dragging data from one place to another duplicates the selected data in the new location, leaving the original selection untouched.

In addition to lines of data, complete tests, parameters or test functions can be moved by dragging and dropping.



Working with List Files Note that in Create, new list files can only be created in the List Selection Window. A new list cannot be created from within the editor. Existing lists can be either inserted into List Selection and opened there, or opened from within the editor. Multiple list files can be open at one time, although new lists cannot be created while existing lists are open, because the List Selection window will not be available.

Opening Lists Within the Create Editor To open a list file follow these steps:

1. Go to File -> Open ORPress Ctrl+O A directory browser window appears.

2. Choose the desired file and select Open

Figure 78. The Create Editor with Two Completed Functions


Working with List Files

Saving, Renaming and Closing ListsSaving the file updates an edited list with any changes. Saving a list does not affect source code. Once source code has been generated from a particular list, new source code should be generated any time the file is edited in the following ways:

• Adding or deleting functions

• Adding or deleting parameters or tests within an existing function

• Changing test instrument board allocations

Any changes to the function description within Create Mode requires that new source code be generated and then rebuilt with VisualStudio. This ensures all changes are recorded and available to Engineering Mode.

To Save a List and Its Source Code1. Go to File -> Save

OR Press Ctrl+S

2. Go to Source Code -> Generate Source CodeThe Confirm Directory for Source Code dialog window appears as in Figure 79.

Figure 79. Confirm Source Code Directory Window

3. Click Select to define an alternate directory path if desired

4. Choose Accept to generate the source code to the specified path

If an alternate directory path is chosen, visualATE may not always be able to find the source files. When a test program is launched, it may be necessary to find the files for ASL.exe if the directory is changed.

The new source code will need to be edited and compiled before the list edits will be incorporated into the DLL. See the “Generating Source Code Files” section.

Save As (Renaming Lists) This function overwrites the existing list file with the list name of your choice.



Closing ListsIf only one list file is open, then closing the list file closes both the file and Create editor and returns the program to the visualATE main menu. If unsaved changes have been made, a save prompt will appear as in Figure 80.

To close a list fileGo to File -> CloseOR Click the x in the upper right file title bar (NOT the application title bar)

To close the file and exit visualATEPress Alt+F4

Figure 80. The Save List Prompt


Working with Multiple Documents

Working with Multiple DocumentsvisualATE allows files of different types to be opened when operating in certain modes. All types can be opened within Create and Engineering, not just list files. Files that can be open at the same time include:

• Datalog (*.dl4, *.daa, and *.dat) files

• Engineering (*.prg) files

• Create (*.lst) files

• Report (*.txt) files

The toolbar icons and menu selections vary with each environment, as discussed in the appropriate sections. It is possible to open multiple documents, as each file type opens in a window with the editing tools of its own environment. That is, a datalog file opens with the toolbar and menu selections of the Engineering run screen, a list file opens with the tools available in Create, and so forth. Multiple files of any type can be open at the same time.

Report files (ASCII text) are discussed in “The Engineering Program Editor” chapter in this manual.

Any text (*.txt) file can be opened within the Create or Engineering editors. Text files open the visualATE text editor, which offers editing and printing commands. Data can be copied or cut and pasted between environments as long as the data types are compatible. For example, a parameter copied from Create can be pasted into a parameter field in Engineering, and vice versa. However, source code files may be affected, so use caution when copying and pasting.

Closing any file other than the last open list closes only the file, while the Create editor remains open. Close files by using the File menu command or pressing F4.

To Open a File 1. Go to File -> Open

ORPress Ctrl+OThe file directory browser appears.

2. Select the desired file type in the pop-up selection menu

3. Browse for the desired file



To Close an Active File Go to File -> Close ORClick the x in the upper right file title bar

HINT — Data can be compared at a glance with tiled windows. For example, the default values in a Create (.lst) file can be compared with the assigned values in an Engineering (.prg) file. Figure 81 shows a tiled view of multiple files.

Figure 81. The Create Editor with Two Lists, a Test Program, and Datalog Tiled


Editing Lists

Editing Lists The Create editor must be open in order to edit a file. To open the Create editor, use the List Selection Window to open an existing list, or create a new list. New lists contain a default function with a single parameter and subtest. See Figure 82.\

Figure 82. Creating a New List

Adding Test Function Values The placeholder values in a default function are NEW_FUNC, NEW_PARAM and NEW_SUBTEST, plus various limits. The following values must be defined for each test function in a list:

• Function Name: Each function in a particular list must have a unique name, which is displayed in Engineering

• Parameter Format: The C++ data type must be specified for each parameter, using the pop-up dialog menus discussed in the next section

• Parameter Name: Each parameter within a particular function must have a unique name

• Parameter Default Value: Enter any desired information in this area

• Parameter Units: The scale must be set as unit, mili, micro, etc.



• Subtest Name: Each test within a particular function must have a unique name

• Minimum Limit, Maximum Limit: The default values for Bins 1-4

To define the above values in a function, select and overwrite the placeholder text or existing values, or copy and paste data from another function (see the “Working with the Create Editor” section).

Adding a New Test Function Adding a new test function to a list inserts a default function with one parameter and one subtest, identical to the function contained in a new list. visualATE places the new function below the active function (the function where the cursor is active). New functions can only be added when the cursor is in a test function field as shown in the “Opening Lists within the Create Editor” section.

To insert a new default test function:

1. Place the cursor in the test function below the desired insertion point

2. Go to Insert -> New Function The default test function appears above the function marked with the cursor.

Adding and Editing Parameters New parameters are inserted above the active parameter. This function is enabled when the cursor is in a parameter field as shown in the “Opening Lists within the Create Editor” section earlier in this chapter.

Insert a new parameter1. Place the cursor in the parameter field below the desired insertion point

2. Go to Insert -> New Parameter A new parameter appears above the selected parameter.

Define the parameter format1. Click on the double button to the left of the NEW_PARAM text

The Parameter Units dialog window appears. See Figure 83.


Editing Lists

2. Highlight the desired parameter format, as seen in Figure 83

Figure 83. Parameter Units Dialog

Define the parameter values1. Click on the NEW_PARAM placeholder text

2. Type in a name for the parameter

3. Click on the 0 in the value column

4. Type in the desired value

Define the parameter scale factor1. Click on box to the left of the UNIT placeholder text

The Select Scale Factor dialog appears. See Figure 84.

2. Choose the desired scale factor

Figure 84. Select Scale Factor Dialog



3. Click UNIT placeholder text

4. Type in the applicable unit (spell the word out or use V for voltage, A for amps, etc.)

Adding and Editing Tests New tests are inserted above the active test. This feature is activated when the cursor is in a test field. See the “Entering Test Function Information section earlier in this chapter.

To insert a new test1. Place the cursor in the test field below the desired insertion point

2. Click once to activate the field

3. Go to Insert -> New SubtestA new test appears above the selected test.

To define testname and test limits1. Click on the NEW_SUBTEST placeholder text

2. Type in a name for the test

3. Click on the “none” in the Min column

4. Type in a minimum limit value

5. Repeat for Max value

6. Click on the box to the left of the UNIT placeholder text

7. Set the scale factor and units following the parameter procedure above

8. Add notes or comments in the appropriate columns as desired

Defining List Properties List file properties consist of the list name, directory (disk) location, and the test instrument card configuration. Boards must be assigned for a list before source files are generated. Naming lists is optional, as a default name already exists.

To Bring Up the List Properties Window1. Go to View -> List Properties


Editing Lists

Names The Names tab is selected by default. A list name that you define for the open file (the file name without the .lst extension) is shown in the “List Name” field. The “List File Name” field contains the list directory name and location (including the .lst extension).

Figure 85. List Properties Dialog Box, Names Tab Selected

The screen list name can be changed by overwriting the text in the List Name field. The list will appear under the new screen name in the List Selection window. However, the list directory (disk) name and location will remain unchanged.

Assigning Instruments and SlotsNot every installed test instrument will be used by every test program. Therefore, the test instruments controlled by functions in a DLL must be configured for each list. The board/slot pairing defined in Create will be generated in the source code files for the list. The board/slot number pairs in the Create editor should match the hardware setup.

Test head configuration can be obtained in three ways:

• See the configuration list supplied with the test hardware

• Run Maintenance, which shows the installed instruments and their slots

• Open the front of the test head to see the instrument configuration

visualATE will check the instrument configuration for a DLL whenever a program created from the originating list is launched. If the configuration isn’t correct, an error message appears. Programs cannot run without the required test instruments.

The information entered here is also used by the Create Mode “Generate Source Code” function to generate the instrument board pointers.



To configure the required boards 1. Go to View -> List Properties and select the Brds (01-32) tab

A list of the 32 test head instrument slots appears as in Figure 86. In a new list, the board slot fields are blank. For the ASL 1000, slots 1-22 are available, and slots 23-32 are grayed out.

2. Select the arrow to the right of the text entry field for the desired slotA list of instruments installed in the test head appears as in the figure below.

3. Select the desired test instrument The instrument appears in the slot’s field.

Figure 86. List Properties Dialog Box with an Available Boards Menu

NOTE — While ASL systems are supplied with all test instruments installed and configured in the appropriate slots, configurations may be updated at some point. In this case, there are two configuration restrictions which must be followed: there must be a DVI in slot 9 and a MUX in slot 20, for ASL 1000 testers. For the ASL 3000RF, slot 20 is available for any board. For the ASL 1000, the DVI and MUX are known as the “Minimum Configuration” and are required for the test system diagnostics. For the ASL 3000RF, the DVI is the “Minimum Configuration.”

Changing the Instrument Configuration Without Editing a ListConfiguring boards/slots does not affect test function information entered in the editor, but is incorporated into the source code files. It is possible to configure boards/slots for a list without changing any other data. Once this configuration is complete, new source files can be generated, whether the changes to the list are saved or not. However, saving the board configuration in the list file retains a visible record of the board assignments for the file. This can be edited at any time.


Updating Lists After Creating Test Programs

Updating Lists After Creating Test ProgramsTest.exe requires test programs and their parent lists to be structurally compatible. Changing a list means the structures no longer match. When existing test programs are run after the parent list has changed, Test.exe notes the different structures and changes the test program to match the new list structure. This updating process removes changed functions that were inserted into a test program before the list was changed; other functions remain untouched. Adding functions to a list makes the new function available to its associated test programs and does not change the inserted functions in those programs.

After a list is modified, any associated test programs should be opened so that their structures update, and any changed function should be reinserted. See the “Updating Test Programs After Changing the Parent List” section later in this chapter.



Generating Source Code Files Source code files that are created by the Generate Source Code command are placed in a default directory: \asl_nt\users\lists\listname. All of the source code files, the *.lst file, and the project file are stored in the folder with the same name as the parent list.

Several subfolders are created within each list’s folder, that organize the supporting files associated with the list.

Generate Source Code FilesThere are several steps involved in generating source files, completing source code and building the DLL associated with a saved list file. The first step is to generate the source code files from within Create. Several files are generated for each test function in a list. These generated files are described below.

Several visualATE system files are created. System files allow the test functions in a list to link to Test.exe. Only two of these files are modified by you; User.h and User.cpp. User.cpp declares the pointers to the installed instruments used in the particular list. User.h declares an external pointer to the boards, and is used by all test functions in the list. Each list has one each of these files as shown in the “Updating Test Programs After Changing the Parent List” section later in this chapter.

Two function files are created for each test function in the list: the function header (*.h) file and the function source code file (*.cpp). The function header contains all the information needed to generate parameters and limits, and initialize them to the default values; users do not edit these headers.

NOTE — The first time source files are generated for a particular list, the source code file (*.cpp) is created as a “shell”. The shell contains placeholders to indicate where you enter the source code.

Lists may be edited after source code has been initially entered into the function *.cpp files. Any time a list is edited (in Create) new source code should be generated. As long as code has been entered in the appropriate places indicated in the shell file, it will be preserved. In an edited list, the “Generate Source Code” command will create an entirely new header, and update the *.cpp file with the new information (without overwriting the existing code).

A Visual C++ project file (*.dsp) is also built. The project file organizes related source code files.

CAUTIONDo not edit the function header files.


Generating Source Code Files

Generate List Source Code FilesThis procedure assumes the List is open in the Create editor.

Go to Source Code -> Generate Source CodeORClick the Visual C++ button and answer Yes to the question displayed in Figure 87.

Figure 87. Generate Source Code

This action creates the source files explained on the preceding page. The files are now ready to be edited and compiled.

The next section describes the directory where these source files are saved.



Adding Code to the Source FilesThe source code (*.cpp) files are edited and compiled using Visual C++. Completing source code for a list involves:

• Entering code in each function source (*.cpp) file

• Editing your User.cpp and User.h files

• Rebuilding the DLL to incorporate the edited code

The steps in this section apply to code files generated for the first time. The section “Adding Code to the Source File” describes working with edited lists. If code files have already been generated for a list and the list is later edited, additional steps are needed.

Code is debugged after test programs have been written. See the “Debugging Source Code” chapter for details on debugging source code.

Completing the source code for a list (and DLL) involves coding the *.cpp files.

NOTE — The shell files are set up to guide you in entering code in the correct places. Code cannot be entered randomly. Follow the comments in the code shell.

To edit the source code for a function follow these steps:

1. In Create, press the C++ button.Visual C++ opens and displays the list workspace and project files.

2. Expand the List Project (double-click on the folder icon)

3. Expand the Source Files folder (double-click on the folder icon)

4. Double-click on the desired source code (.cpp extension) file in the FileView screen The source code appears in the source code window, as shown in Figure 88 “Open Source Shell” on the following page.

5. Edit the source code as desired, following the limits described on the next pages


Adding Code to the Source Files

NOTE — The two figures that follow are based on a sample file Example_LM358. The file in the “Open Source Shell” figure was created by the Generate Source Code command in the Create environment. This is the empty source code shell for the test function gain_etc from contained in the list.

Figure 88. An Open Source Shell (Ready to Code)

In the examples on screen: Comments are in greenStatement keywords are in blueProgramming statements are in black



Figure 89 “User-Entered Code” figure shows the completed source code for the gain_etc test function.

Figure 89. User-Entered Code

For valid code strings and usage examples, see the visualATE Programming Reference. These add-in codes can be copied and pasted from the online version of this manual, or typed as they appear on the page. References are organized by test instrument and specific function.

When the test functions are complete, edit your files. Follow the procedure below to declare pointers to each test instrument used in the list. Test instruments are addressed in User.cpp

User-entered init string has been added here

User-entered source code begins here


Build Errors

Build ErrorsIf errors occur during a build, Visual C++ cannot complete the process. Therefore, the DLL will not be generated until the error conditions are corrected. Errors will be shown in the Output screen in the Visual C++ window. This screen serves two purposes:

• It links to the line of code containing the error, and

• Connects to the online help files.

Visual C++ online help contains explanations of common errors, sorted by error number.

Follow these steps to access error explanations, the code that generated the error and move between lines of code:

NOTE — Resolve errors in the order in which they appear, and do a build after each fix (some errors have a tendency to generate multiple messages).

Access Information On a Build Error1. Click on the error number in the Output screen

2. Press F1ORGo to Help -> SearchThe Help dialog appears with the Index tab selected.Type the error number in the text entry field

3. Select Display

Open the Code and Fix the Error 1. Double-click the error message in the Output screen

The appropriate source file opens, with a pointer positioned at the line that generated the error message.

2. Correct the code as needed

3. Rebuild the file

4. Repeat with each error, in the order they appear

Move Between Lines of Code with Build Errors1. Press F4 and Shift+F4



Rebuilding DLL Files

After Editing a List or Reinstalling visualATEThe rebuild process is the same as the original build, with the exception that a workspace (*.dsw) file already exists for the list. Once generated source files have been opened in Visual C++ and the workspace has been saved, the workspace remains available to the project. In some cases, certain source files need to be added to the Visual C++ project when a workspace already exists.

There are two situations when rebuilding the DLL is necessary or recommended: when visualATE is upgraded or reinstalled, and if new source code has been generated from a list. In particular, if a test function has been added to a list, the *.cpp and *.h files for the new test function must be added to the Visual C++ project before the DLL can be built. Follow the appropriate steps below to rebuild the DLL.

After Updating Source Files For a List (Adding A Test Function)

1. With the list in question opened in Create, press the C++ button

2. Add code to the new test function *.cpp file as desired

3. Press F7

The Output screen shows the progress of the build, which takes a few minutes. If errors occur, see section "To edit the source code for a function follow these steps:" earlier in this chapter.



9
WRITING TEST PROGRAMS AND WORKING IN ENGINEERING MODE
This chapter shows how to write test programs based on specific lists, using the visualATE Engineering editor.

When you click Engineering in the visualATE Main Menu, the Program Selection dialog appears. Opening a test program from this window brings up both the Engineering editor and a run screen for the open program. The run screen is described in the “Debugging Source Code” chapter of this manual.

155

9 - Writing Test Programs and Working in Engineering mode

Test Programs and Limit SetsThe difference between a test function and a limit set is that a function contains the code that sets up and operates the tester hardware, while the limits determine whether the test passes or fails.

Test ProgramsAs mentioned earlier, a test program is a sequence of calls to the test functions contained in a particular DLL. Because only one DLL can be linked at a time, all the test functions in a test program must come from the same list.

However, not all test functions in a list must be included in the program. Additionally, test functions may be enabled or disabled within the test program. Enabled functions execute when the test program is run, while disabled functions are skipped.

Saving a test program creates a file (*.prg) that contains:

• A list of included functions that are executed in sequence when the program is run

• One or more sets of parameter values for each of the included functions

• One or more sets of limits

Limit SetsA single test program can contain multiple variations on the structures (parameters, limits, and enabled/disabled status) that determine how the test functions behave. These variations are called limit sets.

When functions are inserted into a test program, the existing structures for all the included functions become the default limit set for the program. With the exception of adding or removing test functions from the program, all editing actually alters the limit set, not the functions themselves.

The default limit set can be edited as desired, saved under a new name, or saved as the new default set for the program. Additional limit sets can be created and edited as desired. When multiple limit sets are created for a single program, the same program can be run with the various limit sets, designed for different test purposes.

Each limit set contains not only the altered parameters and test limits for each function, but also the function’s enabled or disabled status. Therefore, a test function may be enabled in one limit set and disabled in another set.

NOTE — Editing limits in a test program file does not alter the original limits contained in the list. Functions display with their default values when inserted from the parent list, even if the same function was inserted earlier, and the values were altered within the test program.


Test Programs and Limit Sets

Program Creation StepsThe standard procedure for creating a test program involves:

• Opening a list file in Engineering

• Saving the file as a test program file with its own name

• Inserting the desired functions from the list in the order they will run

• Editing parameters and test limits for each test function (the default limit set)

• Creating additional limit sets as desired

• Editing parameters and test limits for each test function in each different limit set

• Defining the program operating properties

• Writing AutoCorrelation verification limits if desired

• Saving the edited test program

• Debugging the program code in Visual C++

The above processes are described in detail in this chapter. Figure 90 illustrates the relationship between list files, test programs and limits.

NOTE — Engineering users can also create list files from test programs, and use the new list to create additional programs. In other words, while a list file must exist before any programs can be built, once a test program is written, additional list files may be created from the test program.



Figure 90. A List File, DLL, Test Program and Limit Sets

1. Create the list (with passed parameters)LIST (*.lst) File: 2. Compile the DLL

ExecutableFunction LibraryFunction 1 [Default Params & Limits]

Function 4 [Default Params & Limits]Function 3 [Default Params & Limits]Function 2 [Default Params & Limits]

Function 5 [Default Params & Limits]Function 6 [Default Params & Limits]

3. Open the list in engineeringand save as a program file

Program (*.prg) File:All List Functions areAvailable; None are Included

4. Insert the desired list functions intothe test programProgram (*.prg) File:Function 4Function 5Function 3Function 6Default Limit Set

[The Param & Limit Values from the List]5. Save the Default Limit Set with a new name

and edit the parameter values and test limits.Repeat as desired Default Limit Set

Commercial Pass Limit Set

QA Limit Set6. The completed program can run the functions

with any of the defined limit sets

Program (*.prg) File With Limit Sets:

The default values entered in the listbecome the Default Limit Set whenthe program is saved

Military Pass Limit Set

Function 4 [Default Limits, Comm Limits, Military Limits, QA Limits]Function 6 [Default Limits, Comm Limits, Military Limits, QA Limits]Function 3 [Default Limits, Comm Limits, Military Limits, QA Limits]Function 5 [Default Limits, Comm Limits, Military Limits, QA Limits]

Included Functions


Accessing Engineering

Accessing Engineering Follow these steps to enter the Engineering environment:

1. Log on to visualATE with engineering privileges

2. Select Engineering from the main menuThe Program Selection dialog appears. See Figure 91.

3. Double-click the name of the desired test programORHighlight the name and select OpenThe Engineering editor now opens. All Engineering tools are now available.

NOTE — In a new install, there are no test program files shown in the window. To use the Engineering editor, test programs must be created or inserted.

The Program Selection WindowThe Engineering Program Selection window doubles as one of the two available Operator opening dialogs. The programs that appear in this window are available for both development and production. Access to these programs, however, is determined by the user’s privileges. Engineering users can double-click on any test program name in the window to open the program in the Engineering editor. Production users may be able to open programs from the window or may have to enter a program name manually, depending on the System Properties set. Production users cannot create new programs or insert programs into the window.

Selecting Remove takes a program file off the window, but does not delete the file from the directory. A removed file remains available and can be reinserted later.

Figure 91. Program Selection Window



Insert adds an existing file to the window. This brings up a directory browser for choosing the desired file. The inserted file is visible in Program Selection immediately.

New brings up a list selection dialog where the user chooses a list file from which to create a program.

Once programs have been identified, they will appear in this window whenever you enter Engineering. If production user access has been set to display a menu of available programs, this window will also appear when Operator is opened. However, the New Insert and Remove tools will be disabled.

Creating a New Test Program File Creating a new program file involves opening a list file and saving it as a test program (*.prg) file. New programs must be saved before they can be opened or edited. The name assigned when the program is saved becomes the file directory name. Once the program has been named and saved, it opens in Engineering and is ready to edit.

Follow these steps to create a new program file:

1. Start visualATE Engineering The Program Selection dialog appears.

2. Select NewThe Select File for New Program Generation browser appears. See Figure 92.

3. Navigate to the desired List Folder and open.

4. Choose the desired list (*.lst) file and select OpenThe Must Save as Program File dialog appears. See the figure below.Name the program (this is the directory name) and Select SaveThe new program opens in the Engineering editor. No functions are displayed.

5. Select Edit -> Insert FunctionA menu of available functions is displayed.

6. Mark the desired Test Function by left clicking on it.

7. Press the “OK” button to insert it onto the Engineering Program Window.

8. Repeat steps 6 and 7 until all desired Test Functions are inserted.

9. Modify the pass parameter and limits value, if required.

10. Enable the Test Functions.


Accessing Engineering

11. Select File -> Save to save this information into the previously named test program file.

Figure 92. Selecting and Saving Program Files

Test programs are saved by default to the directory established during visualATE installation. For best results, test programs should be kept in this default directory. When files are moved, visualATE may not find them the next time a user tries to open a certain file. For information on moving files to a central directory for networking, see Chapter 6, "The Networked visualATE System," on page 103.

Left: The Select File for New Program Generation Dialog. Below: The Save asProgram File Window

Type a name for the program here

Windows shows foldersfirst, then files.



Inserting an Existing File into Program Selection To list, select Insert in the Program Selection window to launch the “Select program file to insert.” window. See Figure 93.

Figure 93. Select Program to Insert Dialog

1. Highlight the program folder(e.g., Example_adc1061) desired in the window shown to the left.

2. Double-click on the highlighted(selected) folder to open the folder window shown below.

3. Highlight the Programs folder inthe window shown to the left.

4. Double-click to open the Programs folder shown in the following window.

5. Double-clicking on the program in the window shown to the left (Example_ADC1061.prg) bringsup the Engineering editor.


Test Program File Directories

Test Program File DirectoriesTest programs generated from a list will be saved to the folder associated with the parent list. The default directory can be changed. However, if a program is saved to a different directory, visualATE may not be able to find the program or its associated list every time the program is opened. The table below shows the basic directory structure.

Table 5. Directories of Test Program Files

Subdirectory Description

\asl_nt\users\lists\listname Contains the source code for the list (*.cpp, *.h files)

asl_nt\users\lists\listname\debug Contains the DLL for the list

\asl_nt\users\lists\listname\programs Test programs (*.prg files) created in Engineering are stored here

\asl_nt\users\lists\listname\datalog Files output from Operator or the Engineering Run Screen (*.dl4 and *.ls4) are placed here



The Engineering ToolbarThe Engineering editor toolbar changes depending on the user’s access rights. When opening a program in Engineering, a runscreen opens in the background as well. Closing either of these windows forces the other to close.

If the user has Engineering access, then the Visual C++ icon is no longer available to the user. The user must have Programming access to enter Visual C++. Figure 94 shows the two views of the Engineering toolbar.

Figure 94. Engineering Toolbar

The Engineering toolbar controls are identified in Figure 95. A description of each control follows the illustration.

Run Test and

Available (User has System

No Debug Tools(No System Administrator Access)

System Properties:

Debug Tools

AdministratorAccess)

Enabled (User has System Administrator Access)

Disabled (No System Administrator Access)

Run Once

Run Continuous

System Properties

Limit Sets

Function Numbers

Toggle

Delta Limits

Program

Toggle tests

Properties

Open Test Program Name

Parameters

Visual C++

Active Limit Set

Online Help

Function List Format View


The Engineering Toolbar

Figure 95. Engineering Toolbar Controls

Run Once

Runs the program a single time and brings up the run screen, with the test results displayed according to the defaults defined in Program Properties. However, if “Handler Manual Continuous” is selected, then the handler behaves as if “Run Continuous” is selected.

If this button is grayed out, Test.exe is not running (see Visual C++ on the next page).

Corresponding Menu: Run -> Run Once

Corresponding Function Key: F3

Run Continuous

Runs the program repeatedly until a stop command occurs. This button brings up the run screen with the results datalogged according to the Program Properties set. If this button in “pressed down” and grayed-out, the open test program is running (the run screen displays). If it is grayed-out but not pressed down, see Visual C++ on the next page.

Corresponding Menu: Run -> Run/Stop

Corresponding Function Key: F2 (When the test is not running. When a run is in progress, F2 stops the run.)

Stop

Only enabled when a continuous run is in progress. This button stops the continous run on the end of the test in progress when the button is pressed.

Corresponding Menu: Run -> Run/Stop

Corresponding Function Key: F2 (When the test is running. Otherwise, F2 starts the run.)

Visual C++

This button brings up the Visual C++ application for debugging purposes; checking code, inserting breakpoints and single stepping (see Chapter 10).

You manually start Test.exe in Visual C++. If this tool is pressed down and grayed-out, Test.exe is running under Visual C++. If the button is disabled, visualATE is running in Demo mode. (Debugging requires normal mode.) If the Run tools are disabled, Test.exe has not been started in Visual C++, or is stopped at a breakpoint.

Corresponding Menu: Edit -> Launch Visual C++



Function List

Opens the List Tree dialog, listing the functions contained in the list file from which the program was generated. Functions can be dragged from this window and dropped into the test program. Parameters can be viewed by double-clicking the function folder icon.

Corresponding Menu: View -> List Tree

Limit Sets

Brings up the Limit Sets dialog, where limit sets can be defined.

Corresponding Menu: View -> Limit Sets

Function Numbers

Controls the display of the function sequence numbers (to the left of each function name). If numbers are shown, selecting this button hides them. If numbers are hidden, this button shows them.

Toggle Parameters

Displays the parameters in a column below the function name.

Corresponding Menu: View -> Show/Hide All Parameters

Toggles Tests

Controls the test and limit display for each function. If tests are displayed, this button hides them. If they are hidden, this button displays them.

Display Delta Limits

Controls the delta limit display. If the limits are hidden, this button displays the limits (labeled d1, d2,. etc.), and vice versa. Delta limits pertain to the AutoCorrelation feature.

Program Properties

Brings up the Program Properties dialog, where test program behavior is defined.

System Properties

Brings up the System Properties dialog, where system parameters are edited. This button is only enabled if the Engineering user has system administrator access.

Help

Brings up the online version of the Quick Reference manual in PDF format.


The Engineering Toolbar

Corresponding Menu: Help -> Online Help

AutoCorrelate

Runs an autocorrelation test.

Print

Brings up the standard Windows NT Print dialog with the system printer selected by default.

Corresponding Menu: File -> Print

Corresponding Keyboard Shortcut: Ctrl-P

Format View

Allows the user to format the Create, Programming and Datalog screens.



Working with the Engineering EditorOpening a file in the Program Selection dialog brings up the Engineering editor, with the programming view of the file in front and a run screen in the background. The Engineering editor opens both views so engineers can see test results during the development process.

The Engineering run screen appears at first sight like the Operator environment, but the tools are much more extensive. The run screen is described in Chapter 10, "Debugging Code," on page 209.

Engineering users can also open the Operator environment from the visualATE Main Menu to run a test program in the production mode.

The Engineering editor operates very similarly to Create; however, Engineering offers more extensive menus and toolbars. In addition, Engineering provides full access to the Program Properties dialog.

NOTE — The function and parameter names assigned in Create cannot be edited in Engineering. However, all numerical values can be edited as desired.

Figure 96 below show the editor and run screen, and Figure 97 shows a tiled view of the two screens in Engineering.

Figure 96. Engineering Editor and Datalog Screens

Left: The Engineering Editor.Below: The Datalog Screen


Working with the Engineering Editor

Figure 97. Tiled View of the Engineering Editor and Datalog Screens



Displaying Test Program InformationFigure 98 shows two views of the Engineering editor: the left is a list of test functions with wrapped parameters; the right shows the functions with parameters displayed.

Figure 98. Test Program Information

In the Engineering editor, test function information can be displayed as follows:

• As a compact list with the test function name and parameters

• Expanded with parameters and tests listed in columns

• With parameters listed in columns and tests hidden

• With tests listed in columns and parameters hidden

Function sequence numbers can be displayed or hidden in any of the above views.

Modifying Function DataOnce functions have been inserted, values can be modified in three ways:

• Overwriting existing data

• Copying, cutting and pasting

• Dragging and dropping


Working with the Engineering Editor

Overwriting Parameters Values and Test Limits Any text displayed in color (by default; this can be changed in System Properties) can be edited. This includes parameter values and test names and limits. Function names and parameter names (displayed in black) can only be changed in Create.

Overwriting text in the Engineering editor is similar to any Windows application. Clicking once on a text entry creates an editing field around the entry, with an active cursor at the insertion point. Double-clicking creates the editing field and highlights the text. Typing over highlighted text completely overwrites the entry; typing at an active cursor point adds the new text beginning with the insertion point.

To overwrite data follow these steps:

1. Double-click on the item to be edited

2. Type the new information over the existing data

Copying, Cutting, and Pasting Test names and limits can be cut, copied and pasted between functions within a test program. Single values or entire tests can be manipulated with the Copy, Cut and Paste tools in the Edit menu. Data can only be pasted into an entry field containing similar data; that is, a test limit value can only be pasted into a test limit field, and a test name can only be pasted into a test name.

To copy or cut and paste a single value follow these steps:

1. Double-click on the value to be copied

2. Go to Edit -> Copy to copy the value, or Edit -> Cut to remove the valueOR Press Ctrl+c to copy, Ctrl+x to cut The data is now in buffer memory and can be pasted into another field.

3. Double-click on the value to be replaced

4. Go to Edit -> Paste ValuesOR Press Ctrl+v on the keyboardThe copied or cut data appears in the new position.

To copy or cut and paste entire tests follow these steps:

1. Click in the Edit Bar on the extreme left side of the test to be copied

2. Hold the right mouse button down and drag the cursor down until all test data is highlighted



3. With all lines highlighted, go to Edit -> Copy or Edit -> CutORPress Ctrl+c to copy, Ctrl+x to cut

4. Click on the editor screen to the left of the test to be replaced

5. Hold the right mouse button down and scroll down until all test data is highlighted

6. Go to Edit -> Paste Values ORPress Ctrl+v on the keyboardThe values on that line are overwritten with the copied values.

Dragging and Dropping — Copying and Pasting Complete Functions Functions can be copied and pasted in their entirety. Paste Functions is enabled when an entire function has been placed in memory.

Dragging data from one place to another duplicates the selected data in the new location, leaving the original selection untouched. Data in the target location is overwritten.

Tests can be moved within or between functions in this way. While a selection is being moved, red dots appear to mark its path. When the information is over a compatible data field, the selected information appears in highlighted (contrasting) characters over the existing data. The data being moved can be placed in any location where it images as contrasting characters.

NOTE — It is important to line up both the test name and its values when moving an entire test from place to place. Only those portions of the data that appear in contrasting characters will be moved. For example, highlighting a test and moving it to a location where the numeric values appear in contrasting text but the name does not appear, will replace the values but not the name.

To drag and drop lines or blocks of data follow these steps:

1. Place the cursor in the Edit Bar on the extreme left side of the data to be copied

2. Hold the right mouse button down and scroll down until all desired data is highlighted

3. Click once on the highlighted data and drag the selection to the target area

4. Make sure the data appears as contrasting characters in place of the existing data

5. Release the mouse button The selected information appears in the target area.


Working with Test Program Files

Working with Test Program FilesWhile new test programs must be generated and saved in the Program Selection dialog, existing programs can be opened from within the Engineering mode, whether or not they have been inserted into the Program Selection list. Engineering opens all visualATE file types. Multiple test programs, their associated run screens, lists and report files can all be open at the same time.

Opening Programs Within the Engineering EditorTo open a test program file follow these steps:

1. Go to File -> OpenORPress Ctrl-o; a directory browser dialog appears.

2. Choose the desired file and select OpenThe Engineering editor opens, with a run screen behind it. All tools are available. If the opened file is a new program, the editor will appear empty, as no functions have been inserted.

Saving, Renaming and Closing Test Programs

SavingSaving a program updates the *.prg file and all associated limit sets to the default path: C:\ASL_NT\Users\Lists\List_Name\Programs\Program_Name.prg

To save a program file, go to File -> Save or press Ctrl+s on the keyboard to save the program file in default directory.

Rename or Relocate Files with “Save As”Renaming a file saves the file under the new name without affecting the original file. In other words, if the original file was included in the Program Selection list, it will remain available in the list. The original test program also remains unchanged on the disk or network.Using the Save As command, it is possible to both rename the file and assign a new directory path. Files saved under new names remain open in the Engineering editor, but are hidden behind the original program. The next time Engineering is started, the saved program will appear in the Program Selection window under the new name.

NOTE — If the test program is saved to a directory other than the default, it may be necessary to relocate the file for visualATE the next time the program is opened.



To save a file under another name or in a new directory follow these steps:

1. Go to File -> Save As; a file directory browser appears.

2. Select the new directory if desired

3. Type in the new program name

4. Select OKThe new file is hidden behind the original file, and will appear in Program Selection on launch.

Closing Test ProgramsClosing the last open program exits Engineering and returns visualATE to the main menu.

If unsaved changes have been made to a program that is being closed, a save prompt appears.

To close a file go to File -> Close or click the x in the file title bar

To close a file and exit visualATE press Alt+F4


Editing Program Files

Editing Program FilesThe Engineering editor must be open in order to edit a test program file. To open the Engineering editor, open a program file from the Program Selection dialog. The tasks described in this section are all performed within the Engineering editor, in an open test program file. New test programs will open an editor that appears to be empty because no test functions have been inserted.

Inserting and Enabling FunctionsAlthough the editor appears blank when a new program is opened, all the functions included in the originating list file are available to be inserted.

Functions are run in the order they appear on screen; that is, the first inserted function runs first, the next function runs second, and so forth on to the last inserted function, which is run last. Function numbers are assigned automatically, beginning with 1 assigned to the first inserted function, 2 assigned to the next, and so on. These numbers cannot be overridden. However, the run order of the functions can be changed by removing and reinserting, or copying and pasting, the functions in the desired order.

Functions are inserted above the active function description. The function description is the area between the upper and lower gridlines. Placing the cursor anywhere in this space makes the function active. If the cursor is active in an existing function description, the new function is inserted above the active function and takes that function number. The original active function moves down the screen and is assigned the next number. Figure 99 illustrates how inserted functions affect a program.



Figure 99. Insert Functions

Test functions can be enabled or disabled, and are initially disabled by default. When the test program is run, any disabled functions are skipped, and the next enabled function is run. Disabled functions do not affect the sequential order; test programs will always run the first enabled function first, skip to the next enabled function, and so on, to the last test function.

For example, in a six-function program where test functions 2, 3 and 5 are disabled, the program would run functions 1, 4 and 6 in that order.

Each test function description contains an enable/disable indicator in the upper left corner. Green indicates that the function is enabled (it will run in sequence when the test program is run). Red indicates the function is disabled (it will not be executed).

Green = EnabledEnable/Disable Indicator

Red = Disabled

Two functions shown, place cursor in dark grey area, highlight no functions, selectEdit->Insert Function or the Insert button on the keyboard

New function will appear at bottom disabled

Highlight last function to insert above highlighted function New disabled function appears above

functionselected



NOTE — The enabled/disabled status is saved independently with each limit set, and does affect the program behavior in production. With this independent status, a test function may be enabled in one limit set and disabled in another. If it is disabled, the function will be skipped during production. Make sure the status for each test function is set correctly when saving a limit set.

There are two ways to insert test functions into a program; using the function tree, or the function dialog. With either method, only one function can be inserted at a time, and all parameters and tests will be inserted along with the function. Once the test function is included in the program file, the parameter values and tests may be edited as desired. The tree method is described first.

To insert a function from the list file (list tree method) follow these steps:

1. Go to View -> List TreeThe List Tree window appears, as shown on next page.

2. Click on the desired function and drag it to the program editor.The test function is inserted into the program above the active function. See Figure 100.

Figure 100. Tree View of List Window



Figure 101. Engineering Editor After a Function was Inserted

To insert a function from the list file (dialog method) follow these steps:

1. Go to Edit -> Insert FunctionThe Function Insert dialog appears. See the figure below.

2. Highlight the desired function and select OKThe Engineering editor appears with the function displayed.



Figure 102. Select Function Dialog

To enable the inserted function, either click on the red box to the left of the function name, or place the cursor in the function area and press F5, or go to Edit -> Disable/Enable Function.The box turns green, indicating the test function is enabled. The function will execute when the program is run. To disable an enabled function, follow the same steps as above.

Creating Limit SetsA limit set is an independent collection of values for all editable fields in a program. Editable variables are the parameter values, test maximum and minimum limit values and enable/disable settings.

When a new program is created, the inserted functions bring their default values with them from the list file, and associate them with the program as a default limit set. This default limit set cannot be edited. Multiple limit sets can be defined for a single program, however, only one limit set can be active at one time. Editing values in an open program changes the values in the active limit set, while other limit sets remain unaffected. Values can be copied from one limit set and pasted into another.

Adding or removing functions affects all limit sets. In a program with multiple limit sets, adding a function to the program adds all the values for that function to each limit set. The values must be edited within each limit set after the function has been inserted. Removing a function from a program removes the parameter and test values associated with that function from all the limit sets.



NOTE — To enable a test function in one limit set but not in another, insert the function into the program and enable it in the limit set where it will run. Disable the same function in the limit sets in which it is not needed.

See the “List File, DLL, Test Program and Limit Sets” diagram at the beginning of this chapter for a graphic interpretation of limit sets.

To create a new limit set follow these steps:

1. Insert all desired functions into the program

2. Go to View -> Limit SetsORClick on the toolbar icon (bar chart symbol)The Limit Set Dialog appears, with the Default limit set listed.

3. Select NewA new limit set containing the default values appears in the list with a default name of New_Limit_Set. Figure 103 shows Limit Sets with a new set displayed.

Figure 103. Limit Sets Dialog

4. Select Rename to name the new limit setThe rename dialog appears, as shown in Figure 104.

Figure 104. Rename Limit Set Dialog

5. Type in the new name and click Accept(OK)



Editing Limit Set ValuesAlthough each test program can have a number of limit sets associated with it, only one set can be active at any time. Editing values in a test program changes the current active limit set. Saving a program saves all edits made to all limit sets since the program was opened.

Inserting test functions after limit sets have been created adds the function’s default parameters and test limits to each limit set. Removing a function removes the values for that function’s parameters and tests from each limit set.

To edit values in a limit set follow these steps:

1. Go to View -> Limit SetsORClick on the toolbar icon (bar chart symbol)The Limit Set Dialog appears, displaying all created limit sets.

2. Click once on the desired limit setThe set name is highlighted.

3. Select ActivateThe set name appears in the Active Limit Set field at the bottom of the dialog.

4. Close the Limit Sets dialog

5. Edit the parameter and test values as desired (see the following section)

6. Save the program (File -> Save or Ctrl+s)

7. Repeat as necessary until all limit sets have been edited

Entering Limit Set ValuesChapter 8 covered overwriting, copying and pasting values in Create. Engineering works the same way. Follow the instructions in the “Creating Lists and Generating Source Files” chapter to modify limit set values. In addition, the unit scale factors can also be set. See the instructions below.

To change a scale factor follow these steps:

1. Of Parameters: Click on the box to the right of the parameter value (unit notation should be displayed to the right of the box)Of Tests: Click on the box in the units column (unit notation should be displayed to the right of the box)The Select Scale Factor dialog appears, as shown in Figure 105.



2. Choose the desired scale factor and select OKFor scale factors of other than 100 percent, the appropriate symbol from the dialog appears in the box next to the unit designation.

Figure 105. Select Scale Factor Dialog

Scale factors, like values, must be edited for each limit set.

Once the limits and scale factors have been set, the test program is complete. It is common to debug the source code for new test programs at this point.


Defining Program Properties

Defining Program PropertiesProgram Properties determine many aspects of program behavior, including:

• How test programs behave in the Operator environment

• What type of results are datalogged

• Whether or not STDF files are automatically uploaded at the end of a run

• What type of handler is used, which bins are pass, which are fail, etc.

Default properties can be set in the Sys Admin environment. The system administrator can only set defaults, however, while the Engineering user sets properties specific to each test program. If possible, engineers and system administrators should work together to define default properties that minimize the need to define them here.

The default properties defined are applied to each new test program as it is created in Engineering. Properties defined in Engineering override these defaults, for the open test program only. Any changes to the program properties must therefore be defined in each test program and saved.

In Engineering, properties are set in the Program Properties dialog, which contains several tabs. Each of the tabs are discussed individually in the following sections. Figure 106 shows the Program Properties dialog.

Figure 106. Program Properties Dialog



To access the program properties dialog follow these steps:

1. Open the Engineering editor

2. Go to View -> Program Properties ORSelect the Program Properties tool (folder with PP on it)The Program Properties dialog window appears.

3. Select the desired tab

Defining Operator Program PropertiesThe options in this tab determine how test programs are handled in the Operator environment, including whether or not test results are printed automatically, whether or not the files are uploaded automatically and so on. Define Operator properties by selecting the check boxes next to the desired items in the Operator tab.

Automatically continue a program after a failed functionThis feature causes the hardware program to skip all subsequent test functions if a test function fails (if results are outside the limits). Results for the skipped functions are displayed as unknowns in the datalog.

When this feature is disabled, the program continues running after a failed function. In a continuous run, the functions prior to the failure do not run.

Enable editing of a lot summaryThis item allows Operator access to the lot summary menu editing items and enables the copy function. The Lot Summary menu options are as follows:

• Load - Clears the current lot summary and loads a new one; device counts become the same as the newly loaded lot summary (prompts for the lot summary file *.ls4)

• Clear - Clears the current lot summary; all device counts go to zero

• Add - Appends the device counts in the selected lot summary file; prompts the operator to select the lot summary file to be added

When this feature is disabled, the Operator cannot copy data or edit lot summaries.

Enable deletion of a lot summaryThis item gives the operator access to the clear item in the Lot Summary menu, without access to the other editing items.



Automatically print program results summaryWhen a lot is completed, this option automatically brings up a Windows NT print dialog, set to the system printer. The operator selects OK or Cancel as desired.

Automatically upload STDF file on end of lotThis command automatically sends a Standard Test Data Format (*.std extension) file of the completed lot to the to the default datalog directory for the active test program file (C:\ASL_NT\Users\Lists\Listname\Datalog, where the list is the parent list used to generate the program file). To send the STDF files to an alternate directory, type an upload path in the text entry field provided.

Automatically create a new datalog on new lot eventThis option causes a new datalog (*.dl4) file to be generated whenever a new lot event occurs (whenever an operator assigns a new lot ID). The default datalog directory is C:\ASL_NT\Users\Lists\Listname\Datalog. When this option is disabled, new lots are appended to the current (open) datalog file.

The default datalog directory may be changed in the Datalog tab of the Program Properties dialog.

Results summary lifetime (days)Datalog (*.dl4) files in the default directory location are deleted after the number of days specified here. This deletion takes effect when a particular program is launched. Launching a program invokes an analysis of the program’s datalog directory, during which files older than the number of days specified are removed. Setting the number of days to zero disables the feature.

Defining Program SettingsThe test program settings defined in the Program tab (Figure 107) determine how running test programs are displayed in the Engineering editor. These properties can be altered by users with either system administrator or Engineering privileges.



The following options are all set in the Program tab of the Program Properties dialog, shown in the figure below. Define the settings by selecting the check box next to the desired item. Each item is explained below.

Figure 107. Program Properties Dialog, Program Tab Selected

Assigning a Screen NameThe screen name can be defined in the Program Properties dialog. Normally, it is most convenient to use the same name for both the screen and the directory. If a screen name is not defined in the Program Properties dialog, the file extracts a default screen name composed of the parent list name and the creation time. This default name will display in the Program Selection list when Engineering and Operator are opened.

To assign a screen name follow these steps:

1. Go to View -> Program PropertiesORClick the toolbar button (the PP folder second from the right)The Program Properties Dialog appears.

2. Go to the Program tabThe extracted default program name appears in the text field.

3. Overwrite the default program name with the desired file name



Use Relative DLL PathChecking this button forces the system to use the debug path of the loaded file, not the default path.

Disable Lot-Sublot for EOW handlerWith the box in it's default mode, unchecked, visualATE creates a separate datalog (.dl4) for each wafer. If the box is checked, one datalog file will be created for all wafers in the lot.

QA RetestQA Retest is a new production oriented feature that allows a subset of devices of the lot to be tested against user defined QA limits in addition to traditional active limit sets. QA Retest avoids the necessity of using off-line QA sampling and provides in-line QA sampling. QA Retest is enabled by checking the appropriate box in the program properties. On program load, the operator can then access the QA Retest sampling setup window, which enables the QA Retest sampling algorithm. During testing VisualATE manages the process of switching between the specified QA parameters. Separate QA datalogs are generated, and have the same properties as the regular final test datalogs.(i.e., same as STDF, ASCII, etc.).

To set up QA Retest follow these steps:

1. Check the Enable QA Retest box. (Figure 108)



2. Set the default Final Test Limit Set and QA Limit Set. Options for the Limit Sets are FT (Final Test), and QA.

Figure 108. Enabling QA Retest

3. Enter visualATE and select desired program.The screen shown in Figure 109 is displayed.

Figure 109. Limit Sets



4. Create and select the desired FT limit set and click Activate. Do the same for the QA limits and select SetQA.

5. Switch to the Operator Screen and select the “New Lot” button. The screen shown in Figure 110 will appear.

Figure 110. QA Retest New Lot Control

6. Enter into LotID the name of the QA datalog.

7. Enter into Lot Size the total number of devices in the entire lot. Lot Size is used to set the frequency of QA testing. (i.e., 100/20 = 5; one out of every 5 devices are QA tested.)

8. Enter in QA Sampling Size the number of devices to be tested with QA limits.

9. Run the test program. The split screen, in Figure 111, was achieved by “tiling” the windows horizontally and minimizing the Program Window. This is only allowable in Engineering mode.

NOTE — Note the QA title for the QA Retest Datalog, and the default title for FT is Datalog.



Figure 111. QA Retest Datalog and Datalog Tiled



Defining Datalog HandlingDatalog properties are defined in the Program Properties Datalog tab, shown in the figure below. Set defaults by clicking in the check box next to the item or entering a value in the text entry fields. Each option is explained below.

Figure 112. Default Program Properties Datalog Tab

Log data into file This option displays test results as a datalog file in the Operator view and saves the results as a datalog (*.dl4) file to the default directory path: C:\ASL_NT\Users\Lists\Listname\Datalog.

If the test is run from the Engineering view, the datalog file will be saved with the name Default.dl4. Subsequent tests run from Engineering include the file date and time in the name, to avoid overwriting the first file: DefaultYear-month-day-hour-minute-second.dl4. If the test is run from the Operator view, a lot ID may be assigned, which becomes the datalog file name.

If this command is disabled, test results will not be displayed as a log in the Operator screen, but the results will still be saved when the Operator view is closed.

To define an alternate directory and/or file name, assign the desired path and file name in the text entry fields at the bottom of the screen.

To differentiate files, tests can be run from the Operator view, where a Lot ID can be assigned. When a Lot ID is defined, the file will be saved under the ID name.



Automatic datalog creationWith this option selected, a datalog (*.dl4 file) is created automatically when a program is closed after running. The datalog is saved to the default path described in the “Log data to file option” description above. Test results are shown in the Operator header, but are not logged on-screen.

Log passed device results This item logs passing device results. Failed device results are not logged, but are included in the lot summary.

Log failed function results (unconditionally)This item logs failed results.

Commit datalog to file after every deviceSelected, this saves the datalogged results to disk after each device result, while the program is running. With this feature disabled, data is saved when the program is closed. Data is written to a single datalog file until a new lot is started. Data written to disk will be preserved in the event of a system failure.

Log device summary informationIncludes summary header information in datalog.

Fractional SavingTo reduce file size, save portions of the results from a device test instead of all the device results. visualATE saves the fraction of the test results entered here. Typing 2 saves one half the device results, typing 3 saves one third, and so on. The default setting is 1, which saves 100% of the device test results.

Checking the +all fails box includes all failing data to datalog, not just passing data regardless of sampling data ratio.

Checking the +summary box allows the summary information of the device to be sent to the datalog for all devices, not just the fractional devices.

NOTE — This feature is disabled if the “Log passed device results” option is not checked.



With fractional saving, the first result of each fraction is saved. For example, if 10 is entered in the field, visualATE will save one-tenth of the test results. Further, the first result of each portion will be saved; in other words, in a group of 30 units, results 1, 11, and 21 will be saved. This way, a sampling of results is obtained consistently.

Fractional results are saved according to the options selected for all datalogs. In other words, logging passed results adds the failed device results to the lot summary, but not to the datalog, regardless of whether 100 percent of the results are saved.

If “Log failed device results unconditionally” is active (checked), then all failed results are logged, regardless of the fraction defined here.

Compute fraction to save from Lot and Target sizeFill in target size with the number of samples you want. When the program starts, it will prompt for lot size and set the sample ratio to TargetSize/LotSize.

Datalog LifetimeDatalog files in the default path (or designated path) are automatically deleted after the number of days entered in the Auto datalog lifetime (days) field.

Datalog File InformationTo override the visualATE default datalog directory, assign a datalog file name and directory path here, using the syntax: C:\my_dlog\device_family\device_name\category.

Note there is no trailing backslash or file name. The visualATE default is: C:\ASL_NT\Users\Lists\ProgramFolder\Datalog.

Setting Handler PropertiesThe Handler tab in the Default Program Properties dialog shows a read-only list of the handlers that are available to the system. Test.exe manages and communicates this information to ASL.exe. On systems without hardware installed, this dialog is blank.



The active handler is highlighted in the list and identified next to the Set Active Handler button at the bottom of the dialog. To change handlers, highlight the desired handler and select the Set Active Handler button - see Figure 113.

Figure 113. Program Properties Dialog with Handler Tab Selected

The Bins: and Sites: labels show the number of device bins and test sites that the active handler can manage at one time.

The Active Sites area shows the number of devices being handled in a particular setup. This is a program-specific setting, so these sites cannot be edited in the Sys Admin environment, only in Engineering. To set the active sites for this particular program, check or uncheck the boxes next to the sites as desired.

Prober Control of Wafer LOTCheck this box if an intelligent prober is controlling the lot.

Suppress OnNewLot Wafer dialog boxCheck this box if an intelligent prober is controlling the lot and it is not desired to have the wafer dialog box appear.

Assigning Bin PropertiesvisualATE supports 32 bins. The settings defined here will cause devices to pass into various bins on the hardware handler depending on the test results.



Bins 1-4 are assigned as passing bins, while bins 5-32 are reserved for fails. If several bins are set as pass bins, the devices meeting the tightest tolerances may go into one bin, perhaps designated as military quality; devices passing at the next tightest tolerances pass for commercial sale, and so on.

With fail bins, devices are normally sorted by type of failure. Each bin may be assigned a unique bin name, mapped to a hardware device bin on the handler (this is system-wide, not handler specific) and assigned alarm limits as described below.

All values must be typed into the fields in these two bin tabs, as there are no pull-down menus or radio buttons. Bin properties are set in two tabs, Bins (1-16) and Bins (17-32), as shown in Figure 114.

Figure 114. Program Properties Dialog, Bins (1-16) Tab Selected

The Software Bin Name is a screen name. This name displays in the Engineering run screen and Operator header. Software bins may each be mapped to a hardware bin on the handler, which physically sorts the tested devices. Normally, software bins 5-32 are mapped to a single hardware bin.

The Alarm Percentage refers to the portion of devices that are sorted into any given bin. Failure bins should be set to alarm at 20% or less, as failures of greater than 20% of the devices being tested could indicate a problem with the lot. Percentage fields are limited to two characters. To keep an alarm from occurring on a pass bin, set the percentage at 0% to disable the alarm.

The Alarm Count is most useful for wafer sort testing where, depending on the lot size, a particular count may be monitored as opposed to a percentage.



If both a percentage and a count are specified, the greater quantity will override the lesser quantity. For example consider a lot consisting of 100 devices, with the percentage set at 20% and the count at 23 devices. In this case, the count takes precedence and the alarm will occur if 24 devices fail. Reversing the situation for the same lot, if the percentage is set at 20% and the count at 15 devices, the percentage takes precedence. The alarm will occur if 21 devices fail.

The HW Bin maps the device handler bin to the software name.

NOTE — The “Set Alarm Clear Password” feature applies to these alarms. Setting a password control keeps the Operator from continuing to test parts until an authorized user has entered the password.

Setting the Program TypevisualATE supports several program types; a standard type for testing components, and three specialized maintenance types of programs. Maintenance programs require special information, and are written to check, calibrate and verify the installed test instruments.

All programs written to test parts will be of the standard type, which is the default setting. The program type is set in the Setup tab of the Program Properties dialog, shown in Figure 115.

Figure 115. The Setup Tab of the Program Properties Dialog



Using Test Version ControlVersion control is useful for identifying the date and time a file was created or modified. Version control uses the standard Windows NT feature that creates a date and time stamp for each file when it is created, modified (and the changes saved), or saved under another name. Each time a test program or its associated files are modified in any way, the time stamp on the file will be updated. This occurs each time the Program Properties dialog is accessed and the settings changed, along with actual changes to the test program values. visualATE searches for the most recent version of all related files every time the test program is opened, and assigns the most recent time stamp to as the version number for the test program.



The screens in Figure 116 illustrate the effect of the time stamp.

Figure 116. Version Control

No Time Stamp Selected; “No Version #” Displays in Datalog

The Version Control Tab and its Effect

.PRG Time Stamp Displays in Datalog



Version Control provides several choices of time stamp: by test program, DLL, source code (*.cpp and *.h) files, or list file. Any single option can be selected, or any combination can be used. If multiple choices are selected, visualATE will use the most recent of the files as the version number.

The test program version is displayed in the title bar and information bar of the Engineering run screen and the Operator screen.

If version control is not enabled, the running test program is labeled with the program name, followed by the phrase “no version #”. If the time stamp has been enabled in the Version Control dialog, then the selected time stamp displays after the program name.



Using AutoCorrelation to Verify Tester AccuracyAutoCorrelation is a feature designed to verify the tester accuracy in running a specific test program for a particular device, or family of devices.

AutoCorrelation can be enabled or disabled for each individual test program available on an visualATE system. Generally, in production environments using AutoCorrelation, all test programs released for production will be verified through this process before release.

This feature is available for single sites only; AutoCorrelation data cannot be shared over a network. The AutoCorrelation appears as shown on the next page.

Overview of AutoCorrelationTo use AutoCorrelation, a test engineer first writes and runs a test program, datalogging the results. The devices that pass with the best results (closest to the median value between the minimum and maximum limits set in the program) are called Golden Devices. The passing values on these Golden Devices are saved as initial values in a datalog file. Tolerances for variance from these values are then defined and saved.

Once the initial golden values and the variance tolerances are defined, one Golden Device is retested with the same test program that produced the initial passing values. The tolerances are checked, and if the retest results are within the tolerance level, then AutoCorrelation has passed. If any results are outside the allowed tolerances, the AutoCorrelation has failed.

AutoCorrelation can be enabled through the Program Properties dialog in either the Sys Admin or Engineering environments. When AutoCorrelation is enabled for a particular program, the tester using Operator mode must run a correlation either at the start of each new lot, or before continuing a lot in progress. Figure 117 shows the AutoCorrelation dialog.

Creating Initial Values and Golden DevicesThe first step in defining a set of standards against which to verify tester accuracy is to run a test program, datalog the results and establish a set of initial values.

First find the value that is halfway between the minimum and maximum limit for each test in each test function in the target test program.

When these optimal values are established, follow the steps below to choose the Golden Devices that will become the standard for the target test program.


Using AutoCorrelation to Verify Tester Accuracy

To choose a set of Golden Devices follow these steps:

1. Run the desired test program, datalogging the results for each test in each test function in the program

2. Compare the datalog results to the test limits assigned in the test program

3. Choose one or more devices whose results are closest to the optimal values

4. Assign each device a unique number

5. Save these results as initial valuesWhen saving these initial values, the file should include the device number, the test results, the date and time.

6. 6. Define tolerances for each result as described in the next section

Defining Tolerances (Delta Limits)Tolerances are called Delta Limits in visualATE. Once a Golden Device and its optimal values are determined, tolerances for variation can be set within the test program in the same way that test limits are set. Delta Limits must be set for each limit set within a particular program. These values are denoted with a lower-case d and the test number, as shown in the figure following.

There is one floating point value per test, that scales with the test limits. Changing the scale factor for the limit set causes the delta limit to scale as well.

To define AutoCorrelation tolerances follow these steps:

1. Open the desired program in the Engineering environment

2. Go to View -> Delta LimitsORSelect the Delta Limits Tool (triangle with lowercase Greek delta)

3. Enter the desired values

4. Save the changes to the limit setThe test program now has AutoCorrelation tolerances and the feature can be enabled



.

Figure 117. Auto Correlation Tolerances

To enable AutoCorrelate follow these steps:

In Sys Admin:

1. Enter the Sys Admin environment

2. Tab through the dialog to Programs -> Default Program Properties -> AutoCorrelate


In Engineering:

1. Enter the Engineering environment

2. Go to View -> Program Properties The Program Properties Dialog appears.

3. Select the AutoCorrelate Tab


Delta Limits Displayed

Delta Limits Tool

Delta Limits



Auto Correlation Interval ControlAuto-correlation can be set to occur on every new lot or Auto-Correlation Interval Control can be enabled.

When Auto-Correlation Interval Control is used, there are two options, Elapsed Time or Number of Devices Tested.

If Elapsed Time is selected, a value is entered into the dialog box in hours.

If Number of Devices Tested is selected, a value is entered for the number of devices and Autocorrelation runs after the number of devices specified is tested.

Validate Both Autocorrelation Data and Limits SetsValidates both Auto-Correlation Data and Limit Set

When enabled, visualATE compares the data and limit sets with initial data looking for a match. If no initial data exists for this device and limit set, then an error message is generated.

AutoCorrelate File OptionsAutoCorrelate can be set to automatically print and/or save correlation reports. Enable either of these options by checking the box to the left of the item, and specifying a directory location for the saved report files. Report files are saved in ASCII text (*.txt), and can be opened in visualATE or any text editor.



Synchronizing LimitsWhen using the Edit Lists functionality in Engineering (Figure 118), the user has the option of checking the “Synchronize Limits” checkbox on the Modify Test dialog. When he does so, limit sets 2 through 4 are made equal to limit set 1, and only limit set 1 is displayed. This feature is reached as follows:

Figure 118. Select Edit List

1. Select Edit List to display the tree view as in Figure 119.

Figure 119. Edit List Tree View



2. Click on the “+” to expand the tree, then right-click on a test for the floating menu.

3. Select Modify Test from the floating menu to open the Modify Test window inFigure 120:

Figure 120. Modify Test Window

4. If the user checks Sync. Limits the limits section of the dialog box changes as shown in Figure 121:

Figure 121. Modify Test Window with Only One Limit Set

Only one limit set is shown. When the user changes it, the three un-displayed limit sets are changed to match, so that a program which does not overtly use multiple limit sets can be altered more efficiently.



Updating Test Programs After Changing the Parent List

Test.exe requires a list and each of the test programs generated from it to have identical structures. This means that each file must contain the same number of functions, parameters and tests, and the names must be the same.

In the test program, the structure is what is available to the test program, not what is used in the test program.

NOTE — Important to remember: a test program executes selected functions, it does not change the structure of the list.

A structural change is anything that can be done in Create but not in Engineering (parameter names and types, number of tests, etc.).

To see a test program’s structure follow these steps:

1. Open the test program

2. Go to Edit -> Insert Function

The Insert Function Dialog appears as in Figure .

Figure 122. The Insert Function Dialog

All of the functions (including parameters and tests) available to the test program are displayed. The contents of this dialog match the list elements shown when the list is opened in Create.


Updating Test Programs After Changing the Parent List

When a list is structurally changed (functions, parameters or tests are added or removed), the new structure no longer matches the structure associated with existing test programs created from the list.

When a user runs a test program whose parent list has changed, Test.exe automatically updates the test program structure to match the parent list structure. When the test program is opened, an informational message shows up, along with a report file that describes the differences between the structures and what was changed. The report can be viewed or printed.

The changes are as follows:

• The set of available functions are revised to match the updated parent list (including default values for all parameters and limits).

• Structurally changed functions are removed from the program: if a function used in an existing test program is changed in the parent list, that function is removed from the test program. The updated function must be inserted into the test program manually.

To run a test program after changing the parent list follow these steps:

1. Open the desired test program in EngineeringThe informational message and difference report appear.

2. View or print the report as desired

3. Close the report window

4. Close the informational message

5. Insert any changed functions that were removed:

a. a. Go to Edit -> Insert FunctionThe Insert Function dialog appears, as shown in the “Select Function” dialog.

b. b. Highlight the updated function and select OKThe Engineering editor displays the inserted function in the test program.

6. Repeat for each function to be inserted

7. Save the revised test program

8. Run the test program





10
DEBUGGING CODE
Debugging is the process of tracking down and correcting bugs in a program. In the visualATE environment, the files that are actually debugged are the individual test function source files (extension *.cpp). To be debugged, these test functions must have already been compiled into object files. If test functions are edited, then the DLLs must be rebuilt before debugging.

Code can be debugged from within Engineering; this mode has a shortcut to Visual C++ (the Visual C++ icon in the toolbar).

NOTE — You must have Programming privileges (access to Create and Engineering) to debug programs. However, remember that debugging can only be done from Engineering. Users restricted to Engineering privileges will not have access to the system compiler shortcut that is used in debugging.

209

10 - Debugging Code

Preparing for DebuggingYou can debug code at any time, during production or development, as long as the system is running in normal mode with tester hardware attached. Some simple preparation is required, because Test.exe runs under Visual C++ (not visualATE) during the debug process.

Preparing to debug involves the following:

• Closing any instances of Visual C++ (The shortcuts in Create and Engineering bring up Visual C++ properly set up for debugging)

• Disabling any breakpoints remaining from previous debugging sessions

• Running Test.exe

First close any open instances of Visual C++. If Visual C++ is running, one or more buttons showing the Visual C++ logo will be displayed in the taskbar, as shown in Figure 123:

Figure 123. Visual C++ Task Bar

Click on one of these buttons and quit the Visual C++ application (press Alt-F4 or click in the x in the right corner of the title bar). Repeat with each open instance.

Next, open the list or test program to be debugged, and bring up Visual C++.

To bring up Visual C++ follow these steps:

1. Open the desired test programThe test program opens in the Engineering editor.

2. Go to Edit -> Launch Visual C++ORSelect the Visual C++ button in the toolbarVisual C++ opens as shown in the figure below. The Visual C++ button in the Engineering toolbar is disabled.


Preparing for Debugging

Visual C++ opens as shown in Figure 124.

Figure 124. Visual C++ Screen

NOTE — When Visual C++ opens, manipulate the window to expose the visualATE toolbar, since the run tool is used in debugging. Also, clear the Visual C++ screen by closing any files left open during previous sessions. To close these files In Visual C++, go to Window -> Close All.

The Class view, the screen to the left, shows open projects with the active project displayed in bold text.

If this area is not blank, notall files were closed the lasttime Visual C++ was run


10 - Debugging Code

To set the active project to TestDbg go to Project -> Set Active Project -> TestDbg. The TestDbg file appears in bold text in the Classes viewer. See Figure 125, the Visual C++ workspace with TestDbg active and the active project menu displayed.

Figure 125. Class View and File View in Visual C++

At this point it is useful to display the FileView for the active project. FileView lists the individual test function source files which are debugged, so debugging is easier with this view selected. Click on the FileView tab at the bottom of the workspace window. Figure 125 shows Visual C++ with the FileView selected.

Next, disable any breakpoints remaining from previous debugging sessions. If Visual C++ has been configured with the tools described in the “Setting Default Program Properties” chapter, disable breakpoints by either using the toolbar button or Breakpoints dialog.

Two Views of Visual C++. Top: With Class View Active

and the Project Menu Shown. Bottom: With FileView Active

FileView is Active


Preparing for Debugging

To disable breakpoints follow these steps:

1. Open the desired code file in Visual C++ (Expand the folders in FileView and double-click the file)

2. Select the pair of hands

ORGo to Edit -> BreakpointsOR Press Alt+F9ORPress Ctrl+bThe Breakpoints dialog appears, with the Location tab selected as appearing in Figure 126.

3. Remove all enabled breakpoints

Figure 126. The Breakpoints Dialog in MSDev

Disabling breakpoints retains the breakpoint position in the code, but makes it inactive. Removing a breakpoint clears the position entirely. There is no global disable command within the dialog; use the pair of hands tool to remove all breakpoints.

Visual C++ is now ready to run Test.exe.

Remove all breakpoints


10 - Debugging Code

To start the hardware control (Test.exe) program follow these steps:

1. Select the Go button:

ORGo to Build -> Start Debug -> GoOR Press F5A dialog as in Figure 127 appears.

Figure 127. Build TestDbg Dialog

2. Click Yes

Selecting Yes in this dialog causes Visual C++ to build the necessary instance of Test.exe. Build progress is shown in the watch window at the bottom of the Visual C++ workspace. Selecting No will not create the necessary hardware control, and debugging cannot proceed.

The hardware control program is now running under Visual C++; the empty window appears minimized on the Taskbar.

The Windows NT taskbar (Figure 128) should now show visualATE, Visual C++ and Test.exe as being active:

Figure 128. Windows NT Task Bar


Debugging Source Code Files

Debugging Source Code FilesTo open the desired files follow these steps:

1. Double-Click on the desired source file in the FileViewThe code file is displayed in the Source Code Window, shown in Figure 129.

2. Repeat as desired for additional test functions

Figure 129. An Open Code File

To set breakpoints follow these steps:

1. Place the cursor in the boundary bar to left of the desired executable line

2. Select the Hand Tool OR, press F9, OR go to Edit -> BreakpointsThe Breakpoints dialog window appears. See the “Breakpoints Dialog and Selection Menu” figure following this description.

3. Type in the line where the code should breakOR Click on the arrow to the right of the breakpoint text entry fieldA pop-up menu appears, as shown in Figure 130, “Breakpoints Dialog and Selection Menu.” The line where the cursor is located is listed.


10 - Debugging Code

4. Select the desired option

Figure 130. The Breakpoints Dialog and Selection Menu



5. Click OK A red dot appears in the left boundary as shown in Figure 131. If no red dot appears, then the line chosen was not an executable line of code (comments and some other statements are not valid breakpoints). In this case, the cursor and a red dot will appear on the next valid line of code.

Figure 131. Set Breakpoints

6. Repeat these steps for all desired breakpointsWhen the desired breakpoints are set, run the open test program in visualATE. The status will display in Visual C++ as the test program runs. Below is a step-by-step description of this process.

Placing cursor here and pressing F9 Test.exe is running when set this breakpoint this button is disabled


10 - Debugging Code

To run the test program in visualATE follow these steps:

1. Click on the visualATE window in the desktop to activate it

2. Click the Run tool The Visual C++ window becomes active again, with the source code window displaying the first breakpoint the program encountered. A yellow arrow appears over the red dot and the Visual C++ run button is enabled (the hardware control program is stopped). See Figure 132.

Figure 132. Run to Breakpoint



At this point, the execution point (designated by the yellow arrow) can be moved and the test program can be run from visualATE again using the new point of execution as shown in Figure 133.

Figure 133. Shifting Breakpoint Positions

NOTE — The Watch window is useful in debugging. To see the pass parameter assigned in the program properties, select an area of code and drag it to the watch window. Change the pass parameter if desired, and the change will take effect the next time the program is run.

It is also possible to view the test results in visualATE during debugging. Pressing F5 finishes a run in Visual C++. The visualATE toolbar becomes enabled and parameters can be changed in visualATE Engineering. Changes to parameters are visible in the next Visual C++ run of the test program.

When the debug run is finished, it is a good idea to remove all breakpoints, as they are not removed automatically. Any errors should be noted for later correction.

Errors cannot be corrected while Visual C++ is running the Test.exe workspace. It is necessary first to exit all three running programs; Test.exe, Visual C++ and visualATE.

Point of executionmoved back

“Move point ofexecution” button

Change value inthe ours struct,using ours struct.


10 - Debugging Code

To disable breakpoints and stop debugging follow these steps:

1. Go to Edit -> BreakpointsOR Press F9The Breakpoints dialog appears, with the Location tab selected.

2. Deselect all enabled breakpoints

3. Select OK to close the dialog

4. Press F5 to finish testing

5. Go to Window -> Close All

6. Go to Debug -> Stop DebuggingORPress Shift+F5This command stops the debugging process but does not exit Visual C++. The build window displays the message: “Exiting Debug”.At this point, Visual C++ is no longer in debug mode and can be used as an editor.


Correcting Errors Discovered in Debugging

Correcting Errors Discovered in DebuggingWhen errors are corrected, changes must be saved and the code recompiled. Then the test should be run, either through debug or in real-time, as desired.

To edit test program code follow these steps:

1. Start Visual C++ by pressing the button in Engineering

2. Click on the FileView tab in the File View window

3. Expand the project file

4. Expand the Source Files and Header Files foldersThe.cpp and .h files are now visible in the File View window.

5. Double-click on the debugged functionThe function opens in the Source Code window.

6. Edit the code as desired

7. Go to File -> Save All (to save the changes)

8. Go to Build -> Build Filename OR Press F7 (to build the DLL)

9. Exit MSDev and return back to the Engineering Program Window.

10. Run the test program (through the debugger or real-time as desired)


10 - Debugging Code



11
RUNNING TEST PROGRAMS AND COLLECTING DATA IN ENGINEERING MODE
This chapter describes using the Engineering run screen for development. The Engineering run screen is used to collect test and device data, and provides programmers with an extensive data analysis environment. The Engineering screen differs from the Operator window, in that it has a more extensive toolbar.

Data from a running test program can be generated as either a datalog or lot summary. A lot summary report is created every time a test program is run even if individual data is not logged, and contains the minimum data that is required for most travelers (work orders): statistical data sorted by bin. For wafer sort testing, visualATE offers a Wafer Sort function where wafers can be sorted in lots within a master lot file.

Datalog files, which contain all test information for each test performed on each device, are optional. Datalog options must be defined in the Program Properties dialog. Lot summary and datalog information from test results can be collected and manipulated as either numerical data or a bar chart on screen, printed automatically on end of lot, or saved to a local or network location and then appended.

Datalog information can be plotted as a histogram, a time domain, or as coordinates on a set of X-Y axes.

Saved test data files open a run screen with a modified toolbar. The "Working with Saved Datalogs" section describes working with saved files.

The System Properties configured for the visualATE system, along with the Program Properties defined for the open test program determine how test data is displayed in the run screen, whether data is saved automatically, and other file attributes.

In general, the configured system and program properties determine what type of data is collected during component testing, while the menus and toolbar determine how the collected information is displayed.

This chapter discusses both properties and tools.

NOTE — The Program Properties settings apply to device results, not test results. In other words, when a test program is not set to log passed devices, but is set to log failed devices, then no test data will be collected on passing devices. Devices which fail at least one test will be logged. All test results--both passing and failing--for the failing device will be displayed and logged to file. Passed devices are recorded in the lot summary, regardless of the datalog settings. This distinction is highlighted in appropriate sections of the text.

223

11 - Running Test Programs and Collecting Data in Engineering Mode

Run Screen Window and Toolbar The run screen has several sections: a header that contains information about the open test program, a program information bar that identifies the open program and the visualATE software version, a command key legend, and the results or summary display. The header and legend do not change, while the display area changes with the view. The lot summary view shows device results sorted by bin, while the datalog shows complete test results for each test performed on each device.

The window areas are identified in Figure 134.

Figure 134. The Engineering Run Screen as it Opens, Before the Test Program has been Run

NOTE — visualATE can be minimized to expose the Windows NT desktop while test programs or datalogs are open in Engineering. Operators cannot minimize visualATE to access Windows NT.

Menu Access Toolbar Program Information Bar Program Header

The color of this background can be setindependently for the datalog and lot summary viewsto distinguish the two (see Chapter 6 for details)

Test Results/Lot Summary Area


Run Screen Window and Toolbar

Figure 135 shows a datalog and a lot summary. The different areas of the data editor are described in the next section.

Figure 135. A Datalog and a Lot Summary of Test Results

The Header, Information Bar and Command Key LegendThe program information bar and program header contain specific data about the open test program, while the command key legend shows keyboard shortcuts to selected menu items. The command key legend does not change with the open test program, and cannot be edited. The legend type size and style and background color, however, can be changed in System Administration. The legend does not show in test result printouts.

The information bar shows the test program name and version number on the left. The visualATE environment is displayed in the center; the label Datalog signifies the Engineering run screen, while Operator identifies the Operator window. The visualATE software version number is shown on the right. The information bar is included with the test results when a datalog or lot summary is saved or printed.

The header gives several pieces of information about the open test program and the ASL system, including:

• Test program name and active limit set

DatalogLot Summary Report



• Lot ID

• User and system names

• Device, bin and handler data

The header displays results as they are returned. When a test program is running, the total results, passes and fails are all updated as each device is tested. At any given time, the bin with the highest number of fails is also recorded, along with the current bin number and the current bin yield percentage.

NOTE — Before running a test program, the default program settings show in the header. Most values are set to zero each time a program is opened for the first time during a visualATE session. The Most Fail Bin defaults to 1. If a test program is run from the program editor, when the run screen becomes visible, the header will display the current results as they are returned.

The current bin number contains the data for the current DUT. As each device is tested, the bin number it passes into is displayed in the Bin # field. At the same time, the percentage of tested devices that have passed is shown in the Yield% field. At the end of a lot, or whenever the test program run is stopped, the information from the last tested device is displayed.

The Next Serial # field shows the number that will be assigned to the next returned result. In the example below, the test program has been opened but not yet run, so the Next Serial # is listed as 1. This means that the current serial number is zero, or that no results have been returned.

The test program (with limit set), operator (the Engineering user currently logged on), and the system name will not change during a run of a test program. The handler and limit set may be changed between lots. The change will be reflected immediately in the header.

The Lot ID is the number or name assigned to the current device lot. In Operator, the production user must enter a Lot ID before testing components, but in Engineering the ID “Default” can be used any number of times. The default file name is appended with the date and time of each run of the test program.

Between lots or runs, the user can change the handler and limit set, and at that time these fields will be updated.

Figure 136 shows the test program header, which is the same in both the Engineering run screen and the Operator window.

Figure 136. Test Program Header and Program Information Bar Before the Test Program is Run



The Run Screen ToolbarThe toolbar offers a shortcut to nearly every available menu item. The figure below shows the toolbar and identifies all buttons. The illustration is followed by descriptions of each individual item.

NOTE — The pictured toolbar is available when test programs are running. Saved datalog (*.dl4) files open a version of the results screen with a limited toolbar. Working with saved files is covered in the “Working with Saved Datalogs” section later in this chapter.

Figure 137. Engineering Run Screen Toolbar with Tools Identified

New Lot

This tool brings up the New Lot dialog and creates a new lot.

Corresponding Menu: Lot Summary -> New Lot

End Lot without Update

This button causes visualATE to end the current lot, save the current datalog and lot summary, and then start a new lot.

Stop Wafer Sort

This button stops Wafer Sort testing.

AutoCorrelation

This button runs the AutoCorrelation sequence defined in the Program Properties dialog.

Corresponding Menu: Programs -> Run AutoCorrelation

Run Once

This button runs the current test program a single time. The Engineering toolbar includes this tool, which brings up the Operator view when the test is run.




Run Manual Continuous

This tool runs the current test program continuously until stopped manually or the last device is reached. This control is also available in Engineering, and brings up the Operator view when executed.

Corresponding Menu: Programs -> Run/Stop


Iterations

When an integer is entered into this field, it causes visualATE to run the loaded program the number of times specified by the integer.

Show/Hide Comments

This button shows comments when they have been hidden, or hides comments if they have been displayed. Comments include the device header and notes column in the datalog display.

Corresponding Menu: View -> Datalog (Show/Hide Comments)

Minimal Datalog

This button removes the device header and notes column from the datalog display and shows only the test results, with no additional information.

Corresponding Menu: View -> Datalog (Minimal)

Hide Passed Results

This button causes the datalog to display only fails and unknown results. Passed devices will not be displayed. If passed results are currently hidden, this control will display them.

Corresponding Menu: View -> Datalog (Hide Passed)

Hide Failed Results

This button causes the datalog to display only passes and unknown results. Failed devices will not be displayed. If failed results are currently hidden, this control will display them.

Corresponding Menu: View -> Datalog (Hide Failed)

Hide Unknown Results

This button causes the datalog to display only passed and failed results. Unknown results (such as those from skipped functions) will not be displayed. If unknown results are currently hidden, this control will display them.

Corresponding Menu: View -> Datalog (Hide Unknown)



Hide Tests

This tool causes the datalog to display only the tests specified in the Datalog filter.

Corresponding Menu: View -> Datalog (Hide tests)

Hide Sites

This tool causes the datalog to hide sites not requested.

Enter Filter Parameters

This button brings up the filter dialog. Datalogs can be “filtered” according to a number of criteria entered here.

Lot Summary

This button toggles between the datalog and lot summary views. A lot summary shows the total results per bin, without displaying any test results. See “The Run Screen and Tabors” section for details and illustration.

Corresponding Menu: View -> Lot Summary


Left: (Filtered) With Test ResultsHidden, Below: With Test Results Shown



Figure 138. Two Views of the Run Screen

Lot Summary Tree

This button brings up the Lot Summary view as a small window within the current Operator view. The Lot Summary Tree shows test results by bin.

Corresponding Menu: View -> Lot Summary Tree

Per Test Statistics Tree

This button brings up the Per Test Statistics view as a small window within the current Operator view. Per Test Statistics must be selected in Program Properties or no data will be available.

Limit Sets

This button brings up the Limits Sets dialog which shows the active set and all available sets.

Corresponding Menu: View -> Limit Sets

Small Bin Bar Chart

This button plots the current datalog results as a bar chart, organized by bin number. The small Bin Bar Chart is displayed in a small window within the current Operator view.

Corresponding Menu: View -> Bin Bar Chart (Small)

Large Bin Bar Chart

This button plots the current datalog results as a bar chart maximized to fill the test results window. The bar chart extends from the header to the command key legend.

Corresponding Menu: View -> Bin Bar Chart (Maximized)

Board Checker

This button opens the Maintenance environment.

Corresponding Menu: Utilities -> Board Checker


Histogram

This button displays the results from a single, selected test as a histogram.

Corresponding Menu: View -> Single Test Histogram



Time Domain Plot

This button displays the results from a single, selected test as a time domain plot.

Corresponding Menu: View -> Single Test Time Domain Plot

3D Plot

This button displays the results from a single, selected test as a 3Dplot.

Corresponding Menu: View -> 3D Plot

X-Y Plot

This button plots an array of user data on a set of X and Y axes.

Corresponding Menu: View -> XY Plot

Program Properties

This button opens the program properties dialog box for setting parameters pertaining to operator settings, program and datalog options, etc.

Corresponding Menu: File -> Program Properties

System Properties

This button opens the system properties dialog box for setting parameters that apply to all programs.

Corresponding Menu: File -> System Properties

Format View

This button opens a dialog box that allows the user to customize screen backgrounds and fonts, etc.

Corresponding Menu: View -> Format view

Tool Launcher

This button opens a dialog box giving the user an option to choose between these tools: AWT, RFVT, Visual Plot and Visual ISE

Online Help

This button opens a PDF version of the visualATE Quick Reference Guide providing the user has Acrobat Reader installed on the system.

Corresponding Menu: Help -> Online Help



Running Test ProgramsWhen a test program is run from within the Engineering Program Editor, the run screen opens with the datalog view displayed by default. Depending on the system and program properties set, the view will appear as either of:

• A blank screen with individual test results displayed for each test on each device

• A lot summary.

Programs can be run a single time or in a continuous loop, and results may be printed or saved as desired. Printing and saving results are discussed in subsequent sections.

NOTE — Tests can be run with visualATE running in either Normal or Demo Mode. The information in this chapter applies to both modes; datalog display settings behave the same, regardless of mode.

Demo Mode is most useful for situations where there is no tester hardware installed on the visualATE system, because Test.exe is not used. The data returned from a test program running in Demo Mode is not true data from the test program, but it is returned to screen or saved to disk in the same manner as true data collected in normal operational mode. It is unlikely that data logged in Demo mode will be saved or printed because it is not real data.

To run a test program (in the Engineering program editor or run screen) follow these steps:

1. Select the Run Once or Run Continuous button on the toolbar ORPress F2 to run once

2. Press F3 to run a continuous loopOR Go to Programs -> Run Once or Programs -> Run/StopIf the program editor was active, now the run screen appears as shown in “The Run Screen Window and Toolbar” section earlier in this chapter. Test results will appear in the display area depending on the System and Program Properties.

To stop a continuous run follow these steps:

1. Select the Run/Stop Manual Continuous button on the toolbar

2. Press F3ORGo to Programs -> Run/Stop Manual Continuous

In Demo Mode, multiple test programs can be opened and run at the same time.


Working with Lot Summaries

Working with Lot SummariesThe minimum amount of data returned from a running test program is the lot summary. Whenever a test program is run, a lot summary is created, and information about the program is shown in the header, regardless of the program properties settings. If the datalog view appears as a blank screen, then the program properties have been set to exclude datalogging results. In this case, the most useful view will be the lot summary.

NOTE — The lot summary includes all device results, no matter which information may be configured to datalog. The datalog, as discussed in later sections, may exclude devices which pass or fail.

Displaying the Lot Summary (No Data is Logged) To view the lot summary select the Lot Summary tool in the toolbar ORGo to View -> Lot Summary



Figure 139 shows both views for a test program that is not set to datalog results, and the Program Properties settings.

Figure 139. Lot Summary Display, No Datalog

Left: The Program PropertiesRequired to Avoid Datalogging Test Program ResultsBelow: The Blank Datalog and the Lot Summary Report

These boxes are all unchecked

Only the program headerand lot summary contain data;the datalog (above) is blank



Results can be viewed as a Bin Bar chart when no data has been logged. Figure 140 shows the same test program run with the lot summary data displayed in a compact Bin Bar chart. A full-screen bin bar chart is also available, but not pictured here. Bin bar charts do not print by themselves, but do print out as part of the Lot summary window print out.

Figure 140. Bin Bar Chart

To display a summary as a bin bar chart follow these steps:

1. Run the test program multiple times (continuous loop)

2. Stop the run

3. Go to View -> Bin Bar Chart (Maximized)ORGo to View -> Bin Bar Chart (Small)

The summary displays as a bar chart either as a full-screen or reduced-size view. Passed results are shown in blue, failed results are shown in red.

Two Views of a Test ProgramRun Without DataloggingResults, each with Bin Bar Chart



NOTE — The lot summary and bin bar chart displays reflect any bin names assigned in the Program Properties dialog window. Figure 141 shows a lot summary and bin bar for a test program where the bins are assigned names, along with the Program Property dialog where these names are set.

Figure 141. Bin Names and Assignment

Lot Summary of a Test Program with Bin Names Assigned (seeChapter 4 or Chapter 9 for details)

Bin names displayed

Bin names assigned



Printing Lot Summaries Lot summaries can be printed manually or set to print automatically on end of lot. The summary will print the header, the results and a bin bar chart (whether or not the bin bar chart is displayed on screen); the print preview shows the file exactly as it will print. The lot summary and header background fields are not printed, and all text prints in black. The bin bar chart, however, prints in color.

Summaries, as with any other file, can be printed on portrait or landscape paper. Figure 142 shows a lot summary as it appears when printed both ways.

Figure 142. Lot Summary Printout

NOTE — The Print Preview screen contains its own set of tools; with the exception of the online help button, the toolbar for the results screen is disabled within the Print Preview screen.

The Lot SummaryPrinted Portrait andLandscape; Set the

Sheet Orientation in the Print Dialog



NOTE — The Print Preview can be set to display a single page or two pages side-by-side. The view can be enlarged or reduced. It is also possible to navigate between pages to view a multi-page file. Use the Print button to print the file being viewed, or select Close to return to the lot summary view.

To preview and print a lot summary follow these steps:

1. Go to File -> Print PreviewThe Print Preview window appears, with the lot summary displayed.

2. View the lot summary as desired (move between pages, zoom in or out)

3. Select Print (to print the file)The Print Preview closes, the Lot Summary View returns, and the Print dialog window appears.

4. Select Close

To print a lot summary without previewing:

1. Go to File -> Print ORPress Ctrl+p; the Print dialog window appears.

2. Select Print Automatic printing is set in the Operator tab of Program Properties, but this property is active in the Engineering run screen as well as the Operator environment. See Chapter 9 or Chapter 4 for setting automatic print.

Figure 143 below shows the required program settings.

Figure 143. Print Settings for Lot Summary

Check this option



Saving Lot Summaries Lot summaries can be manually saved. Summary files are saved as the lot summary file type (*.ls4 extension). Saved *.ls4 files can later be loaded and viewed, appended or printed within the Engineering results screen or the Operator environment.

By default, lot summaries are saved to the datalog folder for the parent list unless an alternate directory path is chosen in the Save Lot Summary File dialog. They are called <Lot ID>.ls4

To save a lot summary follow these steps:

1. Go to Lot Summary -> SaveThe Save Lot Summary dialog window appears, showing the default file name and directory path for the lot summary file. See Figure 144.

Figure 144. Save Lot Summary Dialog Window

2. Select Browse and choose an alternate directory path, if desired

3. Type an alternate name for the summary, if desired

4. Select Accept(OK)

Working with Saved Lot SummariesSaved lot summaries can be loaded (in the Engineering run screen or the Operator window), or added to open lot summaries. Loaded summaries can be viewed, printed or appended in the Engineering results screen or Operator. Lot summary files cannot be opened in Create or the Engineering program editor in the same way that datalog (*.dl4) files can be.

To view a previously saved lot summary follow these steps:

1. Go to Lot Summary -> LoadThe Select a Lot Summary File dialog appears, showing only files of the *.ls4 type.

2. Double-click on the desired summary fileORClick on the desired summary file to highlight it

3. Select OpenThe loaded lot summary appears in the results screen or the Operator window.



A bin bar chart can be displayed for the open file. The file can also be printed (see the “Printing Lot Summaries” section), or appended with another lot summary.

Appending a lot summary combines the bin data from different lot summary files into a single lot summary.

To append a lot summary follow these steps:

1. Open the summary to be appended

2. Go to Lot Summary -> AddThe Select a Lot Summary File datalog appears, displaying the contents of the datalog folder for the parent list by default. Navigate to the desired file’s location if needed.

3. Highlight the desired lot summary file

4. Select OpenThe bin summaries of the selected file are added to the open lot summary.

The lot summary displayed on screen should now show the combined totals of the original open lot summary and the summary that was just added to it. Multiple lot summaries can be combined in this way, simply repeat the process of adding the desired lot summaries until the file is complete.

Setting Up and Using Wafer Sort ControlThe Wafer Sort feature is designed to set up entire cassettes of wafers for testing before any tests are run. Setting up the wafers in advance allows testing to proceed without interruptions for end of lot processing.

During testing, end of lot processing is performed automatically as each wafer is completed. When a wafer is finished testing, Wafer Sort Control automatically saves a datalog on the tested wafer and creates a new datalog for the next wafer—you do not need to stop testing for these tasks.

End of Wafer (EOW) processing is user defined, and may include additional operations not described here, such as printing a Lot Summary Report from the datalog files, uploading a data file to a network, and other optional processes.

Wafer Sort categorizes a cassette of wafers into a lot and creates a sublot of each wafer in the cassette. Sublots are saved as separate datalog files which can be opened and analyzed. If testing stops before a wafer is complete, the sublot can be saved and later reopened. You can choose to overwrite all data and begin testing again, or append the sublot by continuing with testing where it stopped.

Wafer Sort files are saved in the *.wfr file type. Datalogs and STDF files can also be saved, using normal end of lot processing commands. Wafer sort files are saved to the Datalog folder for associated list file by default. The associated list file is the parent list from which the test program was generated.



Wafer Sort may be enabled for any handler with an associated EOW signal; at least one wafer sort handler must be available in the Handler Selection list in Engineering to use Wafer Sort. In a new install, Wafer Sort is enabled by default.

When Wafer Sort is enabled and the handler has an EOW signal, the Wafer Sort Control dialog window displays when the user opens a test program. Using this dialog, the user can create a new lot, open an existing lot, name the sublots, renumber the wafers, define missing wafers, etc.

The following sections describe how to enable Wafer Sort Control, how to create a new lot, and how to work with existing lots and sublots.

Enabling Wafer SortTo enable Wafer Sort, select a wafer sort handler and enable the End of Wafer program property by following the instructions below and on the next page. In a new install, the End of Wafer property is enabled by default, so Steps 4 and 5 for Sys Admin and Steps 2 and 3 for Engineering may not be necessary.

To set a wafer sort handler follow these steps:

In Sys Admin1. Select the Handlers Tab

The Handlers tab appears, as in Figure 145.

Figure 145. Handlers Tab in Sys Admin



2. Click on a wafer sort handler to highlight it(visualATE is supplied with the GSI M310 wafer sort handler defined.)

3. Select OKThe dialog disappears; open Sys Admin again to continue.

4. Select the Program Tab

5. Select Default Program PropertiesThe Default Program Properties Dialog opens, as in Figure 146.

Figure 146. Program Properties Tab

6. Deselect “Disable Lot-Sublot for EOW Handler”, if necessary

7. Select OKThe Program tab returns.

8. Select OK

In Engineering, only for the open test program1. Choose the Program Properties tool

ORGo to View -> Program PropertiesThe Program Properties dialog appears.

Deselect this box



2. Select the Program TabThe Program Tab appears (see preceding figure).

3. Deselect “Disable Lot-Sublot for EOW Handler”, if necessary

4. Choose the Handler TabThe Handler Tab appears, as shown in Figure 147. Note that this version of the tab allows site selection.

Figure 147. Handler Tab in Engineering

5. Click on a wafer sort handler to highlight it

6. Select the desired sites

The active handler is Manual becausethe FICO has not yet been set



7. Select Set Active HandlerThe name of the active handler appears next to the button. The new handler is not set until it is shown next to the button.

Figure 148. Setting an Active Handler

8. Select OK

9. Save the test program

Starting Wafer Sort ControlWhen a test program is opened in Operator, the Wafer Sort Control dialog opens automatically right after the New Lot dialog. The steps for opening a test program vary depending on whether a Start of Lot (SOL) event handler has been defined.

Without an SOL Event Handler• The operator opens a test program

• The Select Limits dialog displays; the operator chooses a limit set

• The New Lot dialog opens; the operator enters a lot name or number

• The Wafer Sort Control dialog opens

• The operator chooses a new lot or an existing lot and sets up the lot

• The Operator runs the test program

the FICO is the active handlerOnce Set Active Handler is selected,



With an SOL Event Handler:• The operator opens a test program

• The Select Limits dialog displays; the operator chooses a limit set

• The SOL event handler opens; the operator enters the required data

• The Wafer Sort Control dialog opens

• The operator chooses a new or existing lot, and sets up the lot for the run

• The Operator runs the test program

If the SOL event handler requires a lot ID, then the lot ID entered in the event handler will be displayed in the Wafer Sort Control dialog.

To access the Wafer Sort Control in the Engineering Run screen, create a new lot.

Using the Wafer Sort Control DialogThis section describes the individual features of the Wafer Sort Control dialog window. The blank dialog is pictured in Figure 149, as it opens when a test program is run. The features are defined on the following pages.

Figure 149. Blank Wafer Sort Dialog



Lot ChoiceThis feature contains two radio buttons: New Lot and Existing Lot. Choosing New Lot sets up a 25-wafer cassette, with the wafers numbered 01 through 25. Each wafer is a sublot of the primary lot which contains all wafers. A single lot can contain a maximum of 999 wafers. Figure 150 in “Lot Number” section below shows a new lot.

Choosing Existing Lot enables the Browse button in the Lot Number field, so the user can browse for the desired file. Choosing Browse brings up a standard navigation dialog, opened to the Lists folder. Navigate to the Datalog folder for the associated list and open the desired *.wfr file. Existing sublots will be displayed in the completed wafers list, and can be opened and analyzed.

Lot NumberWhen a new lot is created, the Lot Number ID field displays the name entered in the New Lot dialog which opens immediately before this dialog. Change this name by typing a new name, if desired. The Browse button is disabled in a new lot.

Figure 150. Lot Numbers in Wafer Sort Control

The new lot takesthe name assigned in the New Lot Dialog by default

Each wafer is named individually with the lot nameplus the wafer sublotname plus the number.These are the sublot names.

New lots contain 25 wafers by default,numbered 01 to 25



Sub-Lot NameSublots consist of the lot name (from the Lot Number field) with the wafer number appended to it: Lot_ID_01, Lot_ID_02, etc. (up to the 999 wafer maximum). The lot name can be appended with additional information using this field. Information entered here applies to all wafers in a lot.

Figure 151 shows how to append lot names.

Figure 151. Appending a Lot Name

The complete name shown in the gray area to the right of the Sub-Lot entry field is the sublot file name. The wafer sort input (*.wfr) file name contains only the Lot Number. Using the names in our sample screen shots, the wafer sort file is Sort_Job_1.wfr, and the sublots are either Sort_Job_xx.dl4, or Sort_Job_1_Cassette_1_xx.dl4 files (depending on whether the lot name was appended).

Select WafersThis list shows the wafers in the lot listed in the physical bin order, the order they will be tested. The user highlights wafers in this list before moving or renumbering them.

Total Wafers in LotTo change the number of wafers in a new lot, use the up and down arrows here. The Select Wafers list reflects the changes as the number of wafers is increased or decreased. This area is disabled in an existing lot, since the number of wafers was determined when the new lot was created.

Information entered hereapplies to each wafer (sublot)in the lot



Wafer NumberThis tool changes the number of the selected wafer. Wafer Sort Control assumes that wafer 1 is in slot 1, wafer 2 is in slot 2, etc. However, if the wafers are out of order, their numbers can be changed with this tool. To change a wafer number, highlight the wafer in the Select Wafers list, and use the up/down arrows to increase or decrease the wafer number.

If wafers are missing, highlight the missing wafer number and click Delete. The deleted wafer appears in the Missing Wafer list.

Completed WafersThis list shows the wafers (sublots) which have been tested.

Wafers in ProgressIf testing is stopped before the end of a wafer, the wafer is listed here. To resume testing on an incomplete wafer, highlight the wafer and choose the desired data option in the Open an Existing Sublot area. Open an existing sublot is disabled until a wafer is progress is selected. “Append to it” will resume testing with the last tested die and add the results to the datalog file for the sublot. “Overwrite it” will erase all existing data and start testing from the first die.

Missing WafersIf wafers are missing, they can be placed in this list. Click on a wafer in the Select Wafers list and click Delete. The selected wafer is removed from Select Wafers and displayed in Missing Wafers. A blank space remains where the missing wafer was deleted. Wafers can be returned to the Wafer Select list by using the Add button.

Creating and Setting Up a New Lot These instructions assume that a wafer sort handler has been defined and assigned in the Program Properties of the test program being run.

To create a new lot follow these steps:

In Engineering:1. Open a test program

2. Go to the Datalog window

3. Go to Lot Summary -> New Lot (to open a new lot) First, the New Lot dialog appears, then the blank Wafer Sort Control dialog opens as shown in the “Using Wafer Sort Control” section.



4. Click on the New Lot radio button in the Lot Choice areaThe default lot opens as shown in “Lot Number” section.

5. Perform any of the following optional steps as desired

a. Rename the lot by typing over the name in the Lot Number field

b. Assign a second name to the lot in the Sub-Lot Name field

c. Change the number of wafers (use up/down arrows in Total Wafers in Lot)

d. Delete missing wafers

e. Renumber any wafers that are out of order (highlight a wafer and use the up/down arrows in the Wafer Number area)

6. Select OK; Wafer Sort Control dialog closes and the test program can now be run.

In Operator:1. Open a test program

2. Choose a limit set and select Activate

3. Enter a name for the lot and Select OKThe blank Wafer Sort Control dialog opens.

Working with Existing Lots and SublotsAs the test program runs, end of wafer processing takes place as each wafer is tested. Sublot datalogs are created automatically. A sublot datalog is saved when testing is stopped before a wafer is complete.

All sublot datalogs are accessible through the Wafer Sort Control dialog. To open an existing lot in Wafer Sort Control follow these steps:

1. Click Existing Lot in the Lot Choice area to enable the Browse to open The Open Wafer Sort Input File dialog opens to the Lists director (Figure 152):

Figure 152. The Open Wafer Sort Input File Dialog



2. Click OpenThe Lot opens in Wafer Sort Control. Figure 153 shows an opened lot. Note that the Lot Number, Sub-Lot Name and Total Wafers in Lot fields are all disabled. These settings cannot be changed on a saved lot.

Figure 153. An Existing Lot opened in Wafer Sort Control

To complete testing on a wafer in progress follow these steps:

1. Open the lot that contains the target wafer

2. Highlight the wafer in the Wafers in Progress list

3. Select the desired option in the Open an Existing Sublot area (choose “Append to it” or “Overwrite it”)

4. Select OK

Untested wafers will run consecutively until the cassette is finished. Completed wafers are displayed in the Completed Wafers list. If testing is stopped before the end of the wafer, a datalog is saved automatically and the wafer is listed in the Wafers in Progress list. Testing can be started over, or started from the point where it stopped on these incomplete wafers.


Working with Datalogs

Working with DatalogsDatalogs return the device test results to the user interface. Datalogs are optional and must be configured. Datalog options are configured in the Program Properties dialog window. Use the Datalog tab to determine the type of results to log, default file names and other information. Datalogs can be automatically saved, but there is no option to set automatic datalog printing. Set these properties with either Engineering or system administrator privileges.

Displaying Datalogged ResultsFigure 154 shows a tiled view of a test program and its results. The test program contains only one function, which is displayed in the program editor with the parameters wrapped and tests listed. Comparing the two screens to see how the datalogged results include name of test, measurement values, test limits, and units.

Figure 154. Tiled View of the Program and Data Editors

Units and limitsin the test program arelisted in the datalog

Device result

Tests inthe functionare listed by

name andnumber in

the datalog



When results are set to log to a file, both the datalog view and the lot summary view will contain data. As shown in the “Displaying the Lot Summary” section, the datalog view appears by default when test programs are run.

To view and work with test results, the program property “log data to file” must be selected, together with the type of results that should be logged (passes, fails). All other settings are optional. See instructions for setting these properties in the “Setting System Properties” chapter. Figures in this section show the necessary settings in the Datalog tab of the Program Property dialog, along with the screens that result from the setting.



NOTE — The “log data to file” option has been included primarily to provide a shortcut for turning datalogging on and off. This is a convenience for users who work primarily with lot summaries. Enabling the option on its own does not cause any results to be logged; it is necessary to also select the type of results to log.

Figure 155. Logged Test Results

Left: The Datalog Tab Showingthe Chosen Options; Below:Datalogged Results Shown on Screen

These options determine

Selecting this option displaystest results on screen. This datacan be saved manually

which results will be included

Passed results are shown in black, fails are red



Figure 156. A Datalog of Failed Results With Tests Hidden

Only failed results are set to log

Only the five devices that failed are logged

Tests are hiddenso all failed

devices can be seen

Header shows all tested devices



Figure 157. Views of Fractional Results and Property Setting

One out of every 10 passed devices (10% of passing results) are logged;all failed devices are logged

First 11 devices passedand were logged;Next two resultsare fails and are logged;

passed devices between device oneand 11 are not logged

First and 11th devicespassed and logged;there are no fails

(tests are shown)



Datalogs can also be displayed without the comments for each test. Comments are set off in boxed text above the collected results for each device. Displaying the minimal datalog removes these comments and displays only test results. Figure 158 shows a standard datalog and a minimal datalog. Instructions for viewing a minimal datalog follow the figure.

Figure 158. Two Views of a Datalog, Standard and Minimal

To view a minimal datalog go to View -> Datalog (Minimal)

To return the datalog to the default display (includes comments) go to View -> Datalog (Comments)

Device test commentsare displayed in the

standard datalog

Test results for eachdevice are displayedimmediately followingthe previous device in a minimal datalog



Using Datalog Filters Datalog filtering can be used to display only the results from certain tests, or certain lots and handler sites, within a datalog. The same is true for filtering by lot and by handler site. To view test results from one handler site, select only that handler site and the rest will be filtered out; do the same for lot summaries.

Tests can only be filtered for the current, open datalog. Lot summaries and handler sites can only be filtered when creating a new filtered datalog. A single dialog (Select Datalog Filter Parameters) serves both functions. Filter an existing datalog, or create a new filtered datalog by entering the desired parameters in this window.

To create a new filtered datalog follow these steps:

1. Go to Datalog -> Enter Filter ParametersOR Select the Filter tool. The Select Datalog Filter Parameters Dialog appears, as shown in Figure 159.

Figure 159. Select Datalog Filter Parameters Dialog

When this box is checked. . .

.. . The itemsin the upper portionof the dialog areenabled. . .

. . . And the testsare disabled

The Select DatalogFilter Parameters Dialog



2. Select the box next to Create New Filtered Datalog. All the tests in the program will be disabled when this box is checked.

3. Select the desired handler and lot summaries

4. Check Passed or Failed Devices, or both as desired

5. Select Filter (OK)A new datalog is created.

To filter tests within an open datalog follow these steps:

1. Go to Datalog -> Enter Filter Parameters. . .ORSelect the Filter tool

2. Highlight the desired testsTests that are highlighted will be displayed in the datalog; tests that are not highlighted will be filtered out.

3. Select Filter (OK)The datalog currently displayed on screen refreshes to show the changes.

Figure 160. The Select Datalog Filter Parameters Dialog

The tests list is enabled;choose the desired tests

When this box is notchecked, the lots andsites are disabled



New filter parameters can be assigned at any time. The screen refreshes to show the new filtered effect each time the dialog closes. Figure 161 shows the datalog produced by the filter parameters shown above.

Figure 161. A Filtered Datalog

Setting Serial NumbersSerial numbers can be reset to zero or any other number with the Serial Numbers dialog. Use this dialog to change the default starting serial number from 1 to the desired number at the start of a new datalog, or reset device numbering within an open datalog, between test program runs.

To set a datalog serial number follow these steps:

1. Go to Datalog -> Serial Number ORPress F6The Serial Number dialog window appears. If a datalog is in progress, the next



sequential serial number is entered in the text-entry field by default. The example in Figure 162 was created in a datalog containing results from 60 devices; by default, the next device tested would have been the 61st device.

Figure 162. The Datalog Serial Number Dialog

2. Enter the desired serial number

3. Select OK (Accept)

Saving Datalogged ResultsUsing the Program Properties Datalog settings, datalogs can be configured to print automatically, to either the default directory or a specified location. Engineering, Programming and Sys Admin users can set this property. Currently there is no manual save command, although there are tools for manually saving datalogs in a



variety of file formats. Writing to different file types is discussed in following the information on automatic saving. Figure 163 shows the Datalog tab with the automatic file save option chosen. The options are described following the figure.

Figure 163. The Datalog Tab of the Program Properties

If the “Default datalog file name” and “Datalog file location” fields are left blank, as they are in the above illustration, the files will be saved to the visualATE default location:

C:\ASL_NT\Users\Lists\ListName\Datalog\DefaultDateTime.dl4.

When the “Commit datalog to file after every device” option is selected, test results are added to the file on disk as each device is tested. If this option is not selected, the data is put in a temporary file. Selecting this option ensures as much data as possible is saved to disk in the event of a system interruption (power failure, etc.).

Automatically creates a fileon disk that contains theheader information and anydatalogged test results

At least one of these options must be checked, or no test results will be logged

Adds results after selected

location for the saved filesIf desired, type an alternate directory

number of devices to thedatalog file on disk



The first datalog will be named <Lot Number.dl4>, with subsequent files named Default-Year-Month-Day-Hour-Minute-Second.dl4.

Figure 164. Default File Location for Automatically Saved Datalogs.

In Figure 164, no lot number was entered so the system generated “Default.”

Assigning a name in the Default datalog file name text field creates a series of files with the user-defined name in front of the date-time stamp. As with the Default series, the first file is named with the defined name, and subsequent files add the creation date to distinguish the files from each other.



Datalogs can be written to a variety of file types using the menu commands. Datalogs can be written to Standard Test Data Format (*.std) files, spreadsheet (*.txt) files, and ASCII (*.txt) files. Spreadsheet text files are comma-delineated, while ASCII text files are tabular. Figure 165 shows the same datalog created from a single-function test program, saved two different ways. The files are shown in the visualATE Text Editor.

Figure 165. Two Different Text Versions of a Datalog File

To write a datalog to another file format follow these steps:

1. Go to Datalog -> Write to File (Desired Format)The Save Datalog (file type) window appears. The preceding figure shows the window that appears when a datalog is saved as a spreadsheet.

2. Enter a name for the file

Spreadsheet Format

ASCII Text Format



3. Select Save

Figure 166. Save Datalog Window

Static datalogs (saved files that are not currently collecting results from a running test program) open with a slightly different toolbar than active datalogs. See the “Working with Saved Datalogs” section for information on working with saved files.

Printing Datalogged ResultsDatalogs can be printed any time that the test program is not running. Use the File menu commands or toolbar button to bring up the Print dialog window. The print dialog is a standard Windows type, containing printer configuration choices. Change settings as desired and select the Print button to print the datalog.

The File menu contains a Print Preview option. Print Preview shows the printed pages as they will appear. Working with Print Preview in Datalog view is identical to the Lot Summary view.



Datalogs also include the header file, but do not include bin bar charts. Figure 167 shows a short datalog (only two devices) printed in portrait (vertical) layout. Datalogs can be printed in landscape (horizontal) layout as well.

Figure 167. A Datalog Printed in Portrait Orientation

Charting Test ResultsSeveral charting tools are available. The Bin Bar chart displays device results by bin; the remaining charts plot the results of individual tests on a set of axes. Each type of graph is described individually in the following sections.

Charting Device Results in a Bin Bar Creating a bin bar chart in the datalog view of the run screen is the same as it is in the lot summary view. Once the open program has been run, create a bin bar chart by following the steps listed in the beginning of “Working with Lot Summaries” section.

Bin bar charts can only be printed in the lot summary view. Even if a bin bar chart is displayed in the datalog view, it will not print with the datalog results. To print a bin bar chart, switch to lot summary view and follow the instructions in the beginning of “Working with Lot Summaries” section.

Graphing Test Results as a Histogram Histograms show graphically the frequency distribution of device results for a particular test. In this case the frequency distribution is “how many devices returned a particular result.”

Returned result values are plotted along the horizontal axis; the number of devices is plotted along the vertical axis.



To create a histogram follow these steps:

1. Run the test program, datalogging the desired results

2. Go to View -> Single Test Histogram ORSelect the histogram tool in the toolbarThe Test Selection dialog box will appear as in Figure 169, select the desired test and select OK.

Figure 168. Test Selection Dialog



3. View the selected test data and histogram as shown in Figure 169

Figure 169. A Selected Test and its Histogram

Printing, Saving and Editing HistogramsIf test limits are set in the test program, the limits become the default extreme values for the histogram. Each test has four limit sets that correspond to the four pass bins; the histogram uses the fourth (widest or loosest) values by default. These values can be changed in the histogram window by typing in the desired values, such as the limits for the first pass bin.

The histogram file tools are contained in the histogram window itself; to print the chart, use the Print tool in the histogram window, not the datalog menu command.

Using the datalog menus saves the datalog file—so additional histograms can be created, or the current histogram can be recreated—but the current histogram will not be saved as a chart. Follow the steps below to print or save a histogram.

To print the histogram select the Print tool in the histogram window. The standard Windows Print dialog appears.

Highlighted test

Test limits

Setup, Test limits, etc.



NOTE — It is a good idea to print histograms in landscape format, because they are wide and may be cut off when printed in portrait orientation.

Figure 170. The Parts of a Histogram Window

The following series of figures illustrates the effects of the fields that can be edited: the minimum (Min) and maximum (Max) values, and the number of bars (Bars). When making a change, type the desired value in the text entry field and select the Change button. Changes are incorporated immediately.

To change the histogram display follow these steps:

1. Type the desired values in the Min and Max text-entry fields (See Note)

2. Type the desired number of bars

Chart Print Tool Title bar identifies the plotted test

Number of devicesreturning the value

Units and center values areplotted on the horizontal axis

Chart Properties Save Tool



3. Select Change. The chart refreshes to reflect the changes, as shown in Figure 171.

Figure 171. A Series of Histograms Showing the Effects of Changing the Parameters

1. Default format:test limits, 22 bars

3. Change: Same test limits, 44 bars (double the default)

4. Change:

Narrower test limits,

default 22 bars

2. Change:same test limits, 11 bars (half the default)



Creating a Time-Domain PlotA time-domain plot shows a series of results for a single test sequentially be device. The X-axis shows the device number, while the Y-axis shows the value returned for that device. The word “time” applies to the fact that tests are performed over increments of time as devices are tested in a run. However, the X-axis is labeled with device serial numbers, which normally increase sequentially as time passes and devices are tested. Changing datalog serial numbers will affect the display. For best results, plot a time domain for a series of devices tested without any change in serial number.

Figure 172 illustrates a time-domain plot both with a scale factor used and without the scale factor. Manipulating a time-domain is essentially the same as working with histograms; type desired values in the text-entry fields and use the change and save tools. The time-domain does not contain a print command.

Figure 172. Two Views of a Time-Domain Plot

With Auto Scale unchecked, the test limits are used.Some data pointsmay not show

With Auto Scalechecked, the plot

scales to fit the data points into

the Image

The limits aredesignated bythe blue lines



The Auto Scale option fits the plot to the collected data; if this option is not checked, the test limits will be used by default. The number of devices refers to the maximum number of points that will show in the plot at one time. As testing continues, the device numbers on the horizontal axis will change as this maximum is reached, to show the next set of devices.

Graphing Test Results in 3D The 3D graphing features is not available.

Plotting Test Results on a Set of X-Y AxesIt is necessary to save the datalog to be plotted as a text file, and plot the data from this saved file.

To plot an X-Y graph, filter the datalog as desired, save the datalog as a text file, and click on the X-Y tool in the toolbar. The X-Y input dialog appears. Choose the desired file and select OK. The data is plotted on a set of X-Y axes.

Viewing Lot Summary Trees and Per-Test StatisticsMultiple lot summaries may be created during the time that a test program is open and running. When several lot summaries are created during testing, the lot summary tree shows an overview of each summary associated with the test session. The Lot Summary Tree Dialog can be viewed from either the Lot Summary or Datalog view within the run screen.

The same is true for the Per-Test Statistics Dialog; statistics are shown by lot. Figure 173 shows a lot summary tree and a per-test statistics window.

Both dialogs use the standard Windows format of plus signs and minus signs for expanding and collapsing icons. To see the statistics on any test, or the bin data in any lot summary, click on the plus sign next to the icon and the contents of the icon will display.

When expanded, each lot summary is displayed with the time stamp (the time the lot was last modified) first, followed by the device results sorted by bin.



The test statistics are displayed sorted by lot summary and handler site within the summary. The data provided includes the basic test information, the mean, standard deviation and Cpk values, with any failures listed to the right.

Figure 173. A Lot Summary Tree Dialog and Per-Test Statistics for a Summary

Per-test statistics can be saved as a text file. The text is tabular, and opens in the text editor in the same layout as it appears in the statistics window: statistics are grouped by lot and handler site.

To save per-test statistics follow these steps:

1. Go to Lot Summary -> Write Per-test Statistics. . .The Save Per-test Statistics Output File Dialog appears.

2. Navigate to the desired directory

3. Name the statistics file

4. Select Save



Working with Saved DatalogsDatalog files can be opened in Engineering or Create. Datalogs open a run screen with a modified toolbar and menu selections. There are no new lot and end lot commands, or run tools, and the board checker is not available, for example. Saved results can be printed, or saved under another file name. Bin bar charts and lot summaries can be viewed and printed, and the datalog can be filtered and saved.

Figure 174 shows the modified run screen toolbar that appears when opening a datalog file.

Figure 174. The Toolbar in a Saved Datalog

Run tools, system properties, and program properties are not available





12
RUNNING TEST PROGRAMSIN OPERATOR MODE
In Operator mode, the user of the visualATE system can load and run test programs, display or print test results, and check installed instruments. Test engineers and programmers can use this mode to evaluate how program properties affect test program behavior in production testing. The Operator mode does not give access to the extensive tools available in the Engineering run screen.

This chapter describes the Operator environment for Engineering users, and comments on advanced settings that a production operator would otherwise not require. Appropriate instructions should be prepared for production staff.

275

12 - Running Test Programs in Operator Mode

Tasks in OperatorThe Operator environment is designed to perform the following tasks:

• Open and run test programs

• Display, save, print and upload test results as numerical data and graphic charts

• Check test instruments

For security purposes, the Operator environment is restrictive. Several security features prevent users with limited access privileges from accessing Windows NT or entering restricted areas of visualATE.

When a user logs on as an Operator, one of two Program Selection windows appears (depending on the System Properties set). The visualATE main menu is not visible. Selecting a test program brings up the Operator window, which cannot be minimized: the standard Windows title bar controls are disabled. The open program results view can be reduced inside the Operator window, but a production user cannot minimize visualATE to access Windows NT.

NOTE — Engineering users can open test programs and datalogs from within the data editor by using the File Menu. Users with privileges limited to the Operator environment cannot open additional files from within the Operator view (the File -> Open command is disabled). Operators must exit the current program, which brings visualATE back to the Operator Program Selection screen where they can open another test program.


The Operator Window

The Operator WindowThe Operator window is very similar in appearance to the Engineering run screen, but the tools available to production users are much more limited. The Lot Summary view opens by default.

Figure 175 shows the Operator environment and identifies the available tools.

NOTE — The two screens, Lot Summary and Datalog, have been assigned different colors to distinguish between them at a glance..

Figure 175. The Operator Window with Lot Summary Displayed and Major Areas Identified

Menu Access Toolbar Program Information Bar Program Header

Results (Lot) Summary Area



The Operator ToolbarThe Operator toolbar is an extensive set of shortcuts to nearly every Operator environment function. Figure 176 shows the toolbar with each button identified.

Figure 176. The Operator Toolbar with Tools Identified

New Lot

This tool brings up the Lot ID dialog, where new device lots are identified.

Corresponding Menu: Lot Summary -> New Lot

Run Tool

This button runs the current test program either a single time or in a continuous loop, as appropriate for the selected handler.

Corresponding Menu: Programs -> Run Once


Lot Summary

This button brings up the Lot Summary view and hides the datalog display. Selected by default when a test program is opened.

Corresponding Menu: View -> Lot Summary


Lot Summary Tree

This button brings up the Lot Summary Tree dialog box where the user can view summary information from each site or an overall summary of testing.

Online Help

NewLot

Board CheckerRun Tool

Small Bin Bar Chart Large

Lot Summary View and Tree


The Operator Toolbar

Corresponding Menu: View ->Lot Summary Tree

Small Bin Bar Chart

This button is selected by default.

Corresponding Menu: View -> Bin Bar Chart (Small)

Large Bin Bar Chart

This button plots the current device results as a bar chart maximized to fill the results window. The large bar chart extends from the header to the command key legend.

Corresponding Menu: View -> Bin Bar Chart (Maximized)

Board Checker

This button brings up the board checker utility.

Corresponding Menu: Utilities -> Checker


Corresponding Keyboard Shortcut: Ctrl+p

Online Help

This button brings up help topics.



Operator MenusOperators can only open one test program file at a time, and all programs must be opened from the Program Selection window. When a program closes, the Operator view closes also, bringing up the Program Selection window. Either another test program can be opened and run, or the operator can select Cancel and be returned the visualATE login screen.

Production users cannot save changes to test programs. Engineering users determine whether datalog headers and lot summaries can be edited, by defining these options in the program properties. For more information, see the “Configuring System Properties” and “Writing and Working with Test Programs in Engineering” chapters in this manual.

FileThe following options are available:

• Print Preview — Shows the datalog as it will appear in print

• Print — Brings up a standard windows dialog of printing options

EditEdit menu contains a single command, the Copy function. Copy is disabled until a line or section of data is highlighted in the results display area. Although production users can access the copy function, there is no paste or insert command. This function is useful for Engineering users who wish to copy from a datalog and paste elsewhere.

ProgramThe Run/Stop feature accomplishes the same results as the Run icon in the toolbar.

ViewThe View Menu shows the bin bar charts and lot summary commands. These commands have keyboard shortcuts and toolbar tools, described in the previous section.

Lot SummaryThe Lot Summary menu offers several administrative options for handling lot summary data, that become available when you click on this menu item:

• New Lot — Enter the Lot ID in the dialog box, then click Continue.


Operator Menus

• Save — Opens the Save Lot Summary File dialog, showing the default path; enter new path if needed or click Browse. Click Accept (OK) when done.

• Load — Opens the Select a Lot Summary File dialog. Select the file name in the list of lot summary files.

• Clear — The warning message box opens: “Are you sure that you want to clear the counters for the lot summary?” Click Yes or No.

• Add — Opens the Select a Lot Summary File dialog. Select the file name in the list of lot summary files or type in the file name you wish to add.

• New Lot ID — Opens the “Change Lot ID” dialog that display the Old ID name in the Old ID field. Type in the new ID for the lot summary in the New ID field then click OK. If no changes are made, close the dialog with the x button.

• Write Per Test Statistics — Opens the Save per Test Statistics dialog. Enter the desired file name in the field, then click OK.

DatalogUse these options to either select and open, or set the serial number for a datalog file.

• Open Datalog (.dl4) — Opens the Open Datalog File dialog. Enter the file name for the datalog file you wish to open or select from the list of files.

• Serial Number — Opens “Enter Next Datalog Serial Number” dialog. Enter the serial number fro the datalog associated with the next test run, then click OK (Accept). Click Cancel to quit with no changes.

HandlerClick Options to open the Handler Options dialog.

UtilitiesThis menu option opens the Maintenance screen. Features of this mode allow engineers and technicians to monitor the status of installed test instruments and perform checks.

WindowClick this item to open a drop box showing the names of open or recently opened files.



Accessing the Operator ViewFor Engineering users, there are two ways to access the Operator environment: by logging on as an Engineer and Selecting Operator from the menu, or by logging on as an Operator in the login screen.

There are a few differences between the two:

• Engineers selecting the Operator button can still access Windows NT from within Operator by using the Flying Window key or pressing Alt-Tab.

• Closing a program window closes the Operator environment and returns the system to the visualATE Main Menu. Production users logging on as Operators do not have these privileges.

• Additionally, the “Shutdown when leaving program” system property is disabled for Engineering users. Even if this property is set, visualATE returns to the Main Menu when test programs are closed, as opposed to shutting down the system. Engineering users can also bypass the initial Limit Sets and Lot Summary ID dialogs by closing them with the small x in the upper right corner of the window.

To access Operator, the user has to open a test program. Depending on the system properties set by the system administrator, however, one of two different windows appears. If the system is set up to allow production users to choose from a list of available programs, the Program Selection window appears with an active list of test programs, as shown in the next section. This window is similar to the Program Selection window that appears when users log into Engineering. The difference is that the New and Insert commands are disabled. Operators cannot insert test programs to the list or create new programs.

If the system is set up to force the entry of a test program name, the Program Selection window appears where the user can force entering a program name. In this case, the user has to enter a program name into the text entry field to open Operator. Please see the “Configuring System Properties” chapter for details on this system property.

To log on as a production user and open a test program, follow these steps:

1. Type in the Operator user name in the visualATE log in screen

2. Press Tab

3. Type in the password

4. Select OKORPress Return


Accessing the Operator View

If the system is set up to show a list of available programs, the Program Selection Window appears as shown in Figure 177. Double-click the desired program name or highlight the desired program name and select OK

Figure 177. The Operator Program Selection Window

If the system is set up to force entry of a program name, the Program Selection Window appears as shown in Figure 178. Type the program name in the text entry field and select OK

Figure 178. The Program Selection WIndow with Forced Entry



The test program opens in Operator, as shown in Figure 179.

Figure 179. The Operator Window as it Opens

The initial Operator screen displays the Lot Summary with an active Limit Set dialog. The Lot Summary shows zero values because the test program has not yet been run. The user should select a limit set and define a Lot ID before running the test program. It is possible to close the Limit Set dialog without choosing a limit set. In this case, the active limit set in Operator will be the value of limit set that was active when the test program was last.

To choose a limit set and define a Lot ID, follow these steps:

1. Highlight the desired set in the list

2. Select OKThe Limit Set dialog is replaced by the Enter Lot ID dialog, Figure 180. The header will be updated once the Lot ID is defined.

Figure 180. The Enter Lot ID dialog

3. Enter a file name for the device lot in the text entry field


Accessing the Operator View

4. Click ContinueThe Enter Lot ID dialog disappears, a small Bin Bar Chart window opens, and the test program is ready for use, as shown in Figure 181.

Figure 181. Operator Window with an Open Test Program

To bypass the limit set selection and use the saved active set, click on the x in the right upper corner of the dialog, or select Cancel.

The Limit Set dialog disappears. Define a lot ID following the steps above.



Running a Test ProgramThe blank Operator view displays the default program settings in the header. Most values are set to zero each time Operator is launched or a program is opened for the first time during a particular visualATE session. The Most Fail Bin defaults to 1.

NOTE — Engineering users can open test programs and datalogs from within the Operator view by using the File Menu. Users with privileges limited to the Operator environment cannot open additional files from within the Operator view (the File -> Open command is disabled). Operators must exit the current program, which brings visualATE back to the Operator Program Selection screen where they can open another test program.

To run a test program, select one of these options:

• Click the Run/Stop button on the taskbar

• Press F2 to run once

• Go to Programs -> Run/Stop

The Operator view appears, as shown on the preceding page.

To stop a continuous run, select one of these options:

• Select the Run/Stop button on the taskbar

• Press F2

• Go to Programs -> Run/Stop


Displaying, Printing and Saving Test Results

Displaying, Printing and Saving Test ResultsTest results will be displayed according to the program properties set in Engineering or Sys Admin. If the results are not displaying as desired, check these properties.

It is not necessary to log test results when a program is run. Test information including the number of devices tested and the number of passes and fails is returned and displayed in the Operator header. This header information can be displayed and printed in the same way as datalogged results. In Figure 182, the same single function test program is shown with different datalog properties selected.

Figure 182. The Datalog Properties Tab; Operator View Without a Datalog

The Operator screen would appear as above (that is without any results displayed in the results area) if the “Log data to file” option was not checked.

Results will be logged to screen

No result options are checked

The header contains the sametest information regardless ofwhether or not results are dataloggedNo test results are shown here because

the options to log passing and failing resultsare not checked



If results are not logged to a file, then they will not be displayed on screen, and they cannot be printed or saved. Only the test information that appears in the header has been returned from the test run.

Printing Test ResultsTest results can be printed from the Operator environment. The Print and Print preview commands are identical to the Engineering run screen versions.

Saving Test ResultsGenerally, test results will be saved according to the assigned system and program properties.


visualATE Rev 5.2 User Guide

13
visualISE
visualISE is a graphical-based tool integrated within visualATE 5.2. It is a powerful tool to help programmers write and debug test programs, and provides a powerful interface to ASL instruments. visualISE graphically represents the state of an instrument and allows for executing any of its functions with instrument-specific parameters, as well as generate source code from the board schematic.

With visualISE, it is possible to:

• Attach it to a running test program to help in debugging problems.

• Show and modify the state of an instrument.

• Leave it active while a program is running.

• Display a list of currently available instruments on startup.

• For each instrument, get a list of available functions.

• Access the Instrument State Structure.

• Present a graphical representation of specified instruments.

• Reflect all changes to the Instrument State Structure upon a manual refresh request or when continuing with the user-defined interval.

• Present a simplified schematic for each instrument with active elements linked to the selected fields of the Instrument State Structure.

• Generate source code for the corresponding function with proper (or default) parameters when you activate an element.

• Present a graphical representation to compose source code for a function with properly specified (or default) values of parameters.

• Execute a function and/or insert source code into a special window that acts as a multi-line text editor. This window can be used to edit the source code, execute all or selected lines, place breakpoints, and perform other actions.

• Assign custom labels or DUT signals to test-head pins, which are displayed as Tool Tips on the schematic in the Instrument pane.

• Log visualISE internal events and error messages.

NOTE — visualISE is not a tool for production testing.

289

13 - visualISE

Starting visualISETo start visualISE from within VisualATE using any program to attach to:

1. Log on to visualATE.

2. Click Engineering mode.

3. Click a program in the Program Selection window, then click OK

4. Click (Tool Launcher). The List of Instrument in Application dialog opens.

Figure 183. List of instruments in Application

1. Double Click visualISE. The visualISE window opens.

Figure 184. visualISE Window

The visualISE debugger can be used to directly query and control test instruments, allowing the user to determine if the instruments are behaving as expected.

290 visualATE Rev 5.2 User Guide

visualISE User Interface

visualISE User InterfaceThe following describes each menu and its commands in the visualISE graphical user interface.

Menu Bar

The menu bar contains the following menus:

• File

• Instruments

• Strobe

• View

• Window

• Help

File Menu

The File menu contains the following commands:

Table 6. File Commands

Command Description

New Creates a new User Test Interface file.

Open Opens an existing User Test Interface file.

Save Saves changes to an existing User Test Interface file.

Save As Saves to a different User Test Interface file.

Recent File Loads the last used User Test Interface file.

Exit Closes visualISE.

visualATE Rev 5.2 User Guide 291

13 - visualISE

NOTE — visualISE is designed to work with only one User Test Interface file at a time. When a User Test Interface pane is open, the New and Open commands are inactive. To create a new User Test Interface file or open an existing User Test Interface file, you must first close the active User Test Interface file.

Instrument Menu

The Instrument menu contains the following commands:

Table 7. Instrument Commands

Command Description

Configuration Opens the Configuration dialog box.

The user can view the current configuration here. Simulated boards may be entered into un-used slots by selecting the check box next to the desired board. After required boards are selected, click OK to display the list in the left pane of the Code Bar window. Simulated boards will be designated with (Simulated) next to the board’s ID



Show Opens the Instruments dialog box.

Asserting the check box of an instrument will show or hide each instrument window on the viewing area. Windows may be set to tiled or cascaded view.

Table 7. Instrument Commands (Continued)

Command Description


13 - visualISE

Options Opens the Options dialog box.

Reload last document at startup: visualISE loads the last used User Test Interface file on startup.Strobe: Sets the strobe interval in milliseconds.Strobe on Visual Studio ‘Breakpoint Hit’ event: Stops execution on breakpoints.Execute assigned function: Allows the user to control the instrument via the graphical interface. The Controls in the Instrument Schematic window execute the corresponding functions.Generate source code for assigned function: Using the Controls in the Instrument Schematic window will generate code for the corresponding functions in the Code Bar window.Insert into Visual studio Active Document: All generated or executed functions are inserted as a string in the active Visual C++ document at the cursor position.

Table 7. Instrument Commands (Continued)

Command Description



Strobe Menu

This allows you to keep track of hardware changes if another program (such as a user test program) is using the same hardware as visualISE.

View Menu

The View menu contains the following commands:

Table 8. Strobe Commands

Command Description

Once Strobes only once.

Start/Stop Starts and stops strobing. The strobe interval is set in the Options dialog box.

Table 9. View Commands

Command Description

Code Bar Shows or hides the Code Bar window.

Log Shows or hides the Log window.

Tool bar Shows or hides the tool bar.

Status Bar Shows or hides the status bar.


13 - visualISE

Window Menu

The Window menu contains the following commands:

Help Menu

The Help menu contains the following commands:

Table 10. Window Commands

Command Description

Cascade Arranges the open windows as a set of overlapping windows.

Tile Arranges the open windows as a set of side-by-side windows.

Arrange Icons Arranges the set of icons.

Table 11. Help Commands

Command Description

Online Help Displays the entire Help file.

Context Help Displays the portion of the Help file that relates to the location from where you clicked this command within visualISE.

About visualISE…

Displays the About dialog box, with information on the installed version of visualISE.



Tool bar Definitions

Figure 185. visualISE Toolbar

Table 12. Tool bar Icons

Icon Tool Tip Description

NewOpens a new User Test Interface file.

Open Opens an existing User Test Interface file.

SaveSaves the changes to the current User Test Interface file.

ConfigurationOpens the Configuration dialog box.

Show or Hide Instruments

Opens the Instrument dialog box.

StrobeStrobe once.

Start/StopStarts and stops the strobe. The strobe interval is set in the Options dialog box.

Toggle Code Bar Shows or hides the Code Bar window.

Toggle LogShows or hides the Log window.

OptionsOpens the Options dialog box.

Toggle Auto coding on Schematic

Using the Controls in the Instrument Schematic window will generate code for the corresponding functions in the Code Bar window.

HelpDisplays help information about the next item you click.


13 - visualISE

Main Window

To open the main window, click (Tool), (System Tools), then (visualISE).

Figure 186. visualISE Main Window

The main window has four panes: User Test Interface, Instrument, Log and Code Bar.

User Test Interface PaneTo display the User Test Interface pane, click File, then click New (or Open).

Figure 187. visualISE User Test Interface Pane

If visualISE is running in OffTester mode, select the Tester type. The choices are:

• ASL1000

• ASL3000

UTI

Instrument

Log

Code bar



The User Test Interface pane displays the current configuration of the ASL tester, which is stored in a .uti file.

• To view a description of a pin, click a pin in the DUT board diagram.

• View the outputs of the actual instruments in the form of “not soldered” pins ( ) if you create a new .uti file.

• View a connector or pin by moving the mouse over the desired connector or pin.

• Add a label for a signal in the list column, which selects the corresponding pin on the connector ( ).

• To remove a soldered connection, delete the label.

Instrument Pane• To display the Instrument pane, double-click a board in the Code Bar pane (or

click Instruments, then click the desired board).

Figure 188. visualISE Instrument Pane

The Instrument pane is composed of two parts:

• Status (on left)

• Schematic (on right)

StatusThis displays the current status of the instrument. If a parameter has changed value since the last strobe, it is highlighted with the red icon to the left of the changed parameter. To define a new value, right-click the parameter.


13 - visualISE

For example, voltage_channel_0 = 3.50000 is displayed in red after the following function is executed from the Code Bar pane:

dvi_9-> set_voltage (DVI_CHANNEL_0,3.5, VOLT_AUTO_RANGE,FAST_VOLTAGE_MODE);

SchematicThis displays the schematic diagram of the current instrument. To change the status or values of controls (relays, analog switches, buttons, down-down boxes, and edit boxes), click the control.

The last-changed control is highlighted in red icon in the schematic. It remains red until the next strobe.

If labels were defined in the User Test Interface pane, they are displayed as Tool Tips for the corresponding instrument pins.

Code Bar Pane

Figure 189. visualISE Code Bar Pane

The Code Bar pane is used to generate and execute functions for ASL tester instruments. The available instruments are shown in the Boards list.

• To view an instrument’s functions in the Functions list, click an instrument.

• To view a list of parameters for a function, click a function in the Functions list. The first column indicates the parameter type. The second column indicates the parameter name. The third column shows the allowed values for each parameter, which can include drop-down boxes and edit boxes.

• Click a parameter value to update Command Line.

• Click Execute to execute the selected (composed) function.

• Click Generate to generate the code for the selected function as a string.

• View the generated functions on the right side of the Code Bar pane.

• To copy the generated functions to the clipboard, press Ctrl-C.

• Code may be run by pressing the Execute Generated List button.

• Delays may be entered by pressing the button, 100 mS delays will be added.



Log Window

Figure 190. visualISE Log Window

The Log window displays the following items:

• Information messages

• Warnings

• Errors

• Debug messages

The Log pane contains three columns: Time, Source, and Description.

• To sort items, click the column whose items you want to sort.

• To copy a line from the log, click the line, then press Ctrl-C. You can then paste the information into any file that accepts plain text (such as Notepad, Word, or Excel).

• To delete a line from the log, click the line, then press Delete.

Closing visualISETo close visualISE, click File, then click Exit.


13 - visualISE

Generating Code with visualISEIn this section, the user will generate code into the code bar window and an open visual ATE .cpp file. In the first example, a DVI CH0 will force a voltage through to BUS2. MUX20 will then route the signal to BUS3 where DVI9 CH1 will be used to measure the voltage. Example2 will use DVI9 CH0 to force 5 Volts. Then the signal is routed through BUS2 and MUX20 and into BUS8(TMU) for reading the rise time of the signal.

Example 1Create a list and program that uses the default boards DVI9 and MUX20. The cursor in the example function will be the used as a placeholder to insert the generated code. Launch the program from Visual ATE engineering mode. Launch Visual C++. Place cursor in function as shown below.

Figure 191. VisualC++ Edit Area

Go to Instruments->Options, check the boxes shown below to generate code in the Code Bar pane and Visual Studio active document.

Figure 192. Instruments -> Options Check Boxes

Double click DVI9 in the Board list. Click on the following relays in the graphic window to the open position: CONN_FORCE0, CONN_SENSE0, CONN_FORCE1, and CONN_SENSE1. Click on the following relays in the graphic window to the close position: BUS_FORCE0, BUS_SENSE0, BUS_FORCE1, BUS_SENSE1.


Generating Code with visualISE

The following code will appear in the code pane and also appended in your example CS file.

Figure 193. VisualC++ Code Pane with Appended Text in CS File

Double click MUX20 in the Board list, Click on the following relays in the graphic window to the close position: MUX_2_BUS2, MUX_BANK _2_3, and MUX_3_BUS3. The following code will be displayed in the code bar and the VS active document.

Figure 194. VisualC++ Code Pane with Code


13 - visualISE

Double click DVI9 in the Board list, use the code bar to generate the following commands:

Set DVI9 CH1 to measure voltage.

Set DVI9 CH0 current and voltage to 0.001A and 2V.

Set delay using the delay button above the code pane. Delays will be generated in the 100 mS increments, may be changed in code later.

Measure using DVI9 CH1.

Results of all code generated below.

Figure 195. VisualC++ With Generated Code

The code generated may be run and results may be viewed in the DVI instrument window.



Click the Execute Generated List button in the upper left hand corner of the code pane.

Figure 196. Code Pane with Generated List

Example 2In this example, DVI9 CH0 is used to force 5 Volts. Then the signal is routed through BUS2 and MUX20 and into BUS8(TMU) for reading the rise time of the DVI 5V signal

Create a list and program that uses the default boards DVI9, MUX20 and the TMU. The cursor in the example function will be the used as a placeholder to insert the generated code as in Example 1. Launch the program from Visual ATE. Launch Visual C++, place the cursor in desired location.

Switch to visualISE, if not open.

Result

ExecuteGeneratedList Button


13 - visualISE

Double click the MUX20 in the Board list. Click on the following relays in the graphic window to the close position: MUX_2_BUS2, MUX_BANK_1_2, MUX_BANK_8_1, and MUX_8_BUS8. The following code will be generated in the Code Bar pane and in your VS function.

Figure 197. Code Generated in Code Bar Pane

The same code will show up in your VS function appended after the cursor as shown below.

Figure 198. Code generated in Code Bar Pane as Appended in VS Function

Next, DVI9 is set up to output to the bus and set to measure voltage. Double click on DVI9 in the Board list. Use the Code Bar window to generate the following commands:

Open relays CONN_FORCE0 and CONN_SENSE0 on DVI9

Close relays BUS_FORCE0 and BUS_SENSE0 on DVI9

Set Measure Mode to (DVI_CHANNEL_0, DVI_MEASURE_VOLTAGE)



The following code will be generated in the Code Bar pane and the VS function.

Figure 199. Code Generated in Code Bar Pane and VS Function

Now the TMU trigger thresholds and edges must be set up. Double click on TMU6 in the Board list. Use the code bar to generate the following statements:

• Set start trigger TMU CHA to 1V positive going edge.

• Set stop trigger TMU CHA to 4V positive going edge.

• Close relay TMU_CHAN_A_BUS.

• Generate a Arm command.

Add a delay statement using the button in the in the right pane of the Code Bar

The delays come in values of 100ms, delays may need to be modified in VS user code.


13 - visualISE

Below is an example of the TMU setup generated by selecting Instrument functions and filling in the desired parameters.

Figure 200. Filling in Parameters and Instrument Functions

The TMU code should be appended to the end of the previous code in the VS file.

Figure 201. TMU Code Appended to the Code in VS File

The TMU is now armed and waiting for a trigger event. The DVI’s current and voltage must be set to obtain the rising edge for the TMU to capture.

• Double click on DVI9 in the Board list.

• Use the Code Bar to set DVI9’s current to 5mA and the voltage to 5V.

• Set a delay. Double click on TMU6 in the Board list.

• Next, read back the TMU value.

• Double click on DVI9 in the Board list and take a DVI measurement.

• Set the DVI’s voltage to 0V.



All code created using visualISE is shown below.

Figure 202. Code Created in visualISE

In the VS code, variables have been added to save the results of the DVI and TMU.

Figure 203. visualISE Code With Variables

NOTE — Note: The visualISE editor is not a full featured programming debugger but allows interpretive execution of selected instrument commands. Any commands sequenced in the visualISE editor pane will not execute ‘at speed’. The visualISE editor does not allow for the creation of variables to hold the results of the measurements, these variables will have to be added in VS code but the results will be shown in the Read and Measure windows of the TMU and


13 - visualISE

DVI respectively as shown below. To run the code generated from the visualISE window, click on the Execute Generated List button located in the upper left hand corner of the code pane

Figure 204. Displaying Results in visualATE

Results

Execute Generated List Button



14
visualPLOT
visualPLOT is a powerful interactive Shmoo tool and general-purpose plotting tool that allows the test engineer to perform sophisticated device characterization functions on an ASL tester. The test results are displayed as a plot in a grid or graph mode.

When setting up visualPLOT, the following actions area available:

• Setup which test parameters will be changed from a minimum to a maximum value.

• Choose the number of steps and step values.

• Choose the plot orientation (vertical, horizontal, and other).

The plot results give the user extensive feedback towards achieving the desired test results:

• Determine which combination of test conditions produced passing results.

• Determine where a transition occurs between passing and failing test conditions.

• Measure test value results.

311

14 - visualPLOT

Starting visualPLOT1. Log in to visualATE, then enter Engineering mode.

2. Click a program in the Program Selection window, then click OK.

3. The visualATE window displays a list of all test functions in the selected program.

4. Choose a test function.

5. Click (Tool Launcher).

6. The List of Instruments in Application dialog opens (Figure 205).

Figure 205. List of Instruments Dialog

7. Click (visualPLOT).The visualPLOT window opens and loads all test functions, parameters, and other information as shown in Figure 206.

Figure 206. visualPLOT Window

Other Parameters pane

Color Scheme pane

Test Result pane

Browser pane

Parameter History pane

Test Definition pane


visualPLOT User Interface

visualPLOT User InterfaceThe following describes each menu and its commands in the visualPLOT graphical user interface.

Menu Bar

Figure 207. Menu Bar for visualPLOT

The menu bar contains the following menus:

• File

• View

• Mode

• Test

• Tools

• Help

File Menu

Figure 208. File Menu

The File menu contains the following commands:

Table 13. File Commands

Command Description

New Test File Creates a new test file.

Open Test File Opens an existing test file.


14 - visualPLOT

View Menu

Figure 209. View Menu

Save Test File Saves changes to an test file.

Save Test File As

Saves to a different test file.

Open Result File

Opens an existing results file.

Save Result File As

Saves changes to an results file.

Export Exports a result file as a test file or as a bitmap.

Print Preview Previews the results prior to printing.

Print Setup Allows changes to the printer setup.

Print Prints the results to a printer.

Exit Closes visualPLOT.

Table 13. File Commands (Continued)

Command Description



The View menu contains the following commands:

Table 14. View Commands

Command Description

Toolbars Shows or hides the toolbars.The Toolbars command contains the following submenu:

Status Bar Show or hide the Status Bar.

Test Definition Show or hide the Test Definition pane in the main window.

Browser Show or hide the Browser pane in the main window.

Parameters History

Show or hide the Parameters History pane in the main window.

Coloring Scheme

Show or hide the Coloring Scheme pane in the main window.

Uniform Axes Show or hide uniform axes.

Show Gridlines Show or hide the gridlines.

Show Markers Show or hide the markers.

Show Guidelines

Show or hide the guidelines.

Smooth Curves Show or hide smooth curves.

Accumulate curves

Show or hide the Accumulate Curve

Logarithmic X Scale

Show or hide the logarithmic X scale.

Main toolbar Show or hide the Toolbar.General controls toolbar

Show or hide the General controls toolbar.

Grid toolbar Show or hide the Grid toolbar.Graph toolbar Show or hide the Graph toolbar.visualATE toolbar Show or hide the visualATE toolbar.


14 - visualPLOT

Mode Menu

Figure 210. Mode Menu

The Mode menu contains the following commands:

Test Menu

Figure 211. Test Menu

Logarithmic Y Scale

Show or hide the logarithmic Y scale.

Zoom In Zoom in on a graphic or grid.

Zoom Out Zoom out from a graphic or grid.

Restore size Displays the graphic or grid in its actual size.

Table 14. View Commands (Continued)

Command Description

Table 15. Mode Commands

Command Description

Grid Switches to Grid mode.

Graph Switches to Graph mode.



Test Menu CommandsThe Test menu contains the following commands:

Test Mode Options Submenu

Figure 212. Test Mode Options Submenu

The Test Mode Options submenu contains the following commands:

Table 16. Test Commands

Command Description

StartUp/Shutdown Functions

Opens the Startup/Shutdown macros dialog box.

Start Test Starts test execution.

Pause Test Pauses test execution.

Abort Test Aborts test execution.

Retest Retests selected results.

Test Mode Sets the test mode.

Test Mode Options

Opens the Test Mode Options dialog box. For information on the Test Mode Options submenu commands, see "Test Mode Options Submenu" on page 317.

Table 17. Test Mode Options Commands

Command Description

Full Test Runs a full test (default mode). Tests are performed for all specified parameters.


14 - visualPLOT

Chess-board Test

Runs a chess-board test. Use this command more for fast testing. This opens the Test mode options dialog box, with the Chess Mode tab active.

The Chess Mode tab contains the following fields:

Table 17. Test Mode Options Commands (Continued)

Command Description

Step Defines the number of omitted untested cells between two tested cells. The range is 1 to 10.

Change of step phase by rows

Defines the point from which to start counting untested cells in a new row. This has three options: Chess mode, Continues mode, and Identical mode.Chess mode: The starting point grows on one cell rather than starting at the previous row.Continues mode: The starting point is determined by counting the untested cells from the end of the previous row.Identical mode: The starting point is the same as the previous row.



First Error Test Runs a First Error test.Test of each row stops when the output value is found within the range defined as erroneous. This opens the Test mode options dialog box, with the First Error Mode tab active.

The First Error Mode tab contains the following fields:

Table 17. Test Mode Options Commands (Continued)

Command Description

Error range for output

Choose the min/max output values to define the error range. The error range can have one or two conditions.

To set a second condition, select a condition from the AND/OR drop-down list, choose a limit in the next drop-down list, then type a value in box on the far right and optionally in the far left.The example shows the error range for output set for Error flag[site_1] with limits from -2.45 to -1.78.


14 - visualPLOT

Tools Menu

Figure 213. Tools Menu

The Tools menu contains the following commands:

Help Menu

Figure 214. Help Menu

The Help menu contains the following commands:

Table 18. Tools Commands

Command Description

Reposit Axes Repositions the axes (only available after test execution).

3D Representation

Presents a 3D representation of the test results.

Table 19. Help Commands

Command Description

Contents Displays the entire Help file.

Item help Displays the portion of the Help file that relates to the location from where the user clicked this command within visualPLOT.

About Graph Controller

Displays the About dialog box, with information on the installed version of visualPLOT.



visualPLOT Window

Figure 215. visualPLOT Window Details

The visualPLOT window contains the following panes:

• Test Definition pane

• Parameters History pane

• Other Parameters pane

• Browser pane

• Color Scheme pane

• Test Result pane

To start visualPLOT click (Tool), click (System Tools), then click (visualPLOT).

NOTE — Also see "Starting visualPLOT" on page 312.

Other Parameters pane

Color Scheme pane

Test Result pane

Browser pane

Parameter History pane

Test Definition pane


14 - visualPLOT

Test Definition Pane

Figure 216. Test Definition

Use the Test definition pane to configure tests. It is possible to add parameters from the Insert Repeat parameter line at the bottom of the pane.

Table 20 describes the columns in the Test definition pane.

Table 20. Test Definition Columns

Column Description

Name Name of the parameters used in a test program.

Type Parameter type used in a test program.

Properties Parameter properties: Fixed Step, Static, List, Formula.

Start Start value for parameters with Fixed Step properties.

Stop Stop number for parameters with Fixed Step properties.

Step Num Step number for parameters with Fixed Step properties.

Step Value Start value for parameters with Fixed Step properties.

Static value The value that will not change during a test when a parameter has Static properties.

List Values that are taken sequentially if a parameter has List properties.

Formula Values that are taken sequentially if a parameter has Formula properties.

Orientation Orientation of test results (Horizontal, Vertical, or Other). Parameters with Horizontal and Vertical orientation are presented on a grid as X and Y values. Parameters with Other orientation are displayed using sliders.Note: A grid’s Vertical parameter is represented as Other in Graph mode. To view the result using various values, move the slider.



Parameter History Pane

Figure 217. Parameter History

The Parameters History pane displays those function parameter definitions that were used to run the test.

To copy the results to the clipboard right-click Parameter History, then click Copy.

Other Parameters PaneThe Other Parameters pane displays those parameters that are NOT treated as Vertical or Horizontal. Function parameters, which do not have a Vertical or Horizontal orientation, are treated as other parameters.

Figure 218. Other Parameters

The Other Parameters pane contains a parameter name, current value, and slider. Each slider tick is equal to a parameter’s Step number.

To change a parameter value, move the slider to the desired value.

The new parameter value displays in the Test Result pane.


14 - visualPLOT

Browser Pane

Figure 219. Browser

Use the Browser pane to load and display either test or result files. The Browser pane displays a list of recently used test files for the currently VisualATE test program.

To load a Test file or a Result file: in the Browser pane, double-click the desired file in the Test or Result files folder.

Tooltips display the full path of the selected file name.

Color Scheme Pane

Figure 220. Color Scheme

The user can set a unique color scheme for each output parameter. A color scheme consists of a set of intervals, where each interval is linked to a different color. An interval is a pair of test limits that define the upper and lower values for a test. The default color scheme is based on the test interval.

NOTE — Invalid intervals are ignored.

In Grid mode, each result is shown by its corresponding color scheme. The user can copy-and-paste a color scheme between various outputs as well to any other application such as Microsoft Word or Excel.



To edit a color scheme right-click Color Scheme pane, then click Edit list (Figure 221).

Figure 221. Edit List

The Color definition dialog box opens (Figure 222).

Figure 222. Color Definition Dialog

To add a new interval follow these steps:

1. Click the last line in the color list.

2. Type a lower limit in the From box.

3. Type an upper limit in the to box.

4. Enter a value in the Intervals box (must be different than existing intervals).

5. Select the Interval conditions.

NOTE — To automatically apply the output color scheme to all sites, select the Apply to all sites check box. Clear the check box to not apply the color scheme to other sites.

6. Click Generate.


14 - visualPLOT

Edit an Existing Interval1. Click an interval line in the color list.

2. Type a new value for the upper or lower limit.

Change Interval Colors:1. Double-click a color box on the line whose color interval is to be changed.

A color dialog box opens.

Figure 223. Color Selection Dialog

2. Select a new color.

3. Click OK.

Delete an Interval1. Click the line whose interval is to be deleted.

2. Press Delete.

Using Hexadecimal Values for IntervalAll interval values must be integers.

Hexadecimal entries must be made in the following format:

0xFF



Test Result Pane

Figure 224. Test Result Pane

The Test Result pane (Figure 224) displays the test results as a grid or graph.

Toggle Between Grid and GraphFrom the Mode menu, click Grid or Graph (or press Ctrl-Tab).

Toggle Between Output ParametersClick the corresponding sheet at the top of the Test Result pane.

Show/Hide Output ParametersRight-click the parameter, then click Show\Hide outputs.

Copy Test Result Pane as a BitmapPress Ctrl-C.

The Test Result pane must not be hidden under any other pane.

Grid Toolbar

Figure 225. Grid Toolbar

Grid Mode Graph Mode


14 - visualPLOT

In Grid mode, test results appear as a grid of rows and columns. The user can use the Grid toolbar to change the appearance of the test results when in Grid mode.

Table 21. Grid Toolbar

Tool Name Description

Color Each result is represented as a colored square on a grid. The color is defined in the Color definition dialog box in the Color Scheme pane.

Color with Text

Each result is represented as a colored square containing the test result value.

Text Each result is represented as a square containing the test result value.

Top Left Sets the graph origin to top left.

Bottom Left

Sets the graph origin to bottom left.

Top Right Sets the graph origin to top right.

Bottom Right

Sets the graph origin to bottom right.

Accumulate Grid

Toggles between displaying one graph or two superimposed graphs.

Clear Results

Clears the accumulated results.

Mode Sets the accumulation mode. Values are:ANDORBIT ANDBIT ORBIT XORMINMAXAVERAGE



Graph Toolbar

Figure 226. Graph Toolbar

In Graph mode, test results appear as a line graph. The user can use the Graph toolbar to change the appearance of the test results when in Graph mode.

Table 22. Graph Toolbar


Uniform Axes

X-axes and Y-axes have the same scale factor and allocates the unit scale uniformly for all axes in the graph.

Show Gridlines

Show or hide grid lines.

Show Markers

Show or hide markers

Show Guidelines

Show or hide guidelines.

Smooth Curves

Smooths the curves using quasi-spline.

Accumulate Curves

Superimposes more than one graph.

Clear Curves

Clears all graphs except the last graph.

Natural Log X

Uses the natural log scale for the X axis.

Natural Log Y

Uses the natural log scale for the Y axis.


14 - visualPLOT

3D Toolbar

Use the 3D toolbar to change the appearance of the 3D display when in 3D mode.

Table 23. 3D Toolbar


Zoom In Zoom in on 3D graph.

Zoom Out Zoom out on 3D graph.

Rotate Z CCW

Rotate the 3D graph counter-clockwise around the Z axis. The amount of change increases the longer the user holds down the button.

Rotate Z CW

Rotate the 3D graph clockwise around the Z axis. The amount of change increases the longer the user holds down the button.

Rotate X CCW

Rotate the 3D graph counter-clockwise around the X axis. The amount of change increases the longer the user holds down the button.

Rotate X CW

Rotate the 3D graph clockwise around the X axis. The amount of change increases the longer the user holds down the button.

Shift Right Shift the 3D graph right. The amount of change increases the longer the user holds down the button.

Shift Left Shift the 3D graph left. The amount of change increases the longer the user holds down the button.

Shift Down Shift the 3D graph down. The amount of change increases the longer the user holds down the button.

Shift Up Shift the 3D graph up. The amount of change increases the longer the user holds down the button.

Color Surface

Toggle the color surface on and off.

Fill Surface

Toggle the fill surface on and off.



General Controls Toolbar

Use the General Controls toolbar to start and stop a function, and to start, stop, pause, continue, and abort a test.

Table 24. General Controls Toolbar


Start/Stop Function

Opens a dialog box to start or stop a function. For more information, see "Defining StartUp and ShutDown Functions" on page 340.

Start Test Start a test and display results as a grid or graph.

Pause/Continue

Pause or continue a test. When a test is paused, the user can view the results up to that time.

Abort Test Aborts a test. The Test abort dialog box opens. For information on using the Abort Test tool, see "Aborting a Test" on page 338.

Retest Retest the selection.

Axis Reposition

Change the parameter orientation. For information on using the Axis Reposition tool, see "Setting the Orientation" on page 339.

3D Mode Display graph results in 3D. For information on using the 3D Mode tool, see "Setting 3D Mode Parameters" on page 339.

Zoom In Zoom in.

Actual Size

Display using actual size.

Zoom Out Zoom out.

Mode Choose Grid or Graph mode.


14 - visualPLOT

visualPLOT Operation

Selecting a Test FunctionTo select a test function, click the drop-down list from the visualATE toolbar (Figure 227), then click a function.

Figure 227. visualATE Toolbar

Running a Test ProgramvisualPLOT receives a set of functions from the current visualATE test program. The user can use more than one function from the same test program. All parameters for the selected function are listed in the Test Definition pane in the visualPLOT window.

To run a test follow these steps:

1. Choose a function.

2. Change a parameter characteristics for the selected function.

3. Change the test limits characteristics for the selected function.

4. From General controls toolbar (Figure 228), click (Start) to run the test.

Figure 228. General Controls Toolbar

5. Record the number of errors (or other events, as defined by the test program) that were detected.

6. Repeat for each additional plot.

7. Display a plot of the test results in the test results window.

NOTE — Do NOT run visualATE test programs while a visualPLOT work session is in progress.


visualPLOT Operation

Disconnect from visualATE

To disconnect from visualATE, click on the visualATE toolbar.

Displaying Pass/Fail CriteriaPass/fail criteria are available for display as follows:

• By color (visualPLOT selects the color, but the user can change the color scheme).

• Color with text (to select the characters and color).

• Cell with text (to select text only).

Saving Shmoo Test DataWhen a test is aborted, the test results are saved in Test Files and Result Files, which are listed in the Browser pane. visualPLOT saves the following types of information in these files:

• Test Files receives the current test definition and current visualPLOT application configuration.

• Result Files receives data from the most recent test run (if any).

Closing visualPLOTClick File, then click Exit.

visualPLOT prompts the user to save any unsaved tests.


14 - visualPLOT

Test ResultsWhen the user runs a test, the grid is filled with data and a curve is plotted based on the data. The user can view the grid or plot in the Test Results pane.

Retesting the ResultsThe user can retest the results in both Grid and Graph mode.

Retest in Grid Mode1. Press Ctrl while the user drag over the cells to be tested (Figure 229).

2. From General controls toolbar, click (Retest).

Figure 229. Retest in Grid Mode


Test Results

Retest in Graph Mode1. Press Ctrl while the user drag the points to be tested.

Figure 230. Retest in Graph Mode

2. From General controls toolbar, click (Retest).

Printing the Results

Print as Grid1. From the Mode menu, click Grid.

2. Click File, then click Print.

Print as Graph1. From the Mode menu, click Graph.

2. From the File menu, click Print.

Preview Results In the File menu click Print Preview.

Page and Print SetupIn the File menu click Print Setup.


14 - visualPLOT

Editing Test DefinitionsThe user can select non contiguous cells, edit selected cells, and select an entire column in the Test Definitions table.

To select discontinous cells, press Ctrl while clicking cells that the user wishes to select in Properties, Start, Stop, Step Num, Step Value, Static Value columns.

To edit the selected cells, right-click on the selection.

All selected cells in that column take the new value.

To select an entire column, right-click a column head.

Adding a Repeat ParameterThe Repeat parameter allows the user to run a test repeatedly using fixed function parameters. The user can also add more than one parameter.

To add a Repeat parameter click Insert Repeat parameter, then click (Displayed).

To delete a Repeat parameter click the cell, then press Delete.

Changing Parameter Properties

Figure 231. Properties Drop Down List

To change a parameter’s properties:

1. Click the cell whose properties are to changed.

2. Click the new property from dropdown menu.

Changing Fixed Step ValuesThe Start, Stop, Step Num, and Step columns are available only for parameters that have Fixed Step properties.

To change a value, edit directly in the cell.

The values in these cells have relations. For example, if a parameter is of type float, the Start value equals 0, the Stop value equals 20, and the Step value equals 6. The Step number automatically becomes 4.


Editing Test Definitions

Changing Static ValuesThe Static Value columns are available only for parameters with Static properties.

To change a value, edit directly in the cell.

Changing Input ValuesThis function is available only for parameters that have List properties.

To change the list of input values, follow these steps:

1. Click the cell whose parameter properties are to be changed.

2. Click (Displayed)

The List for input parameter koeff dialog box opens (Figure 232).

Figure 232. List for Input Parameter Koeff Dialog

3. To change a value, click a cell, type a value, then press Enter.

4. To add a new value, click an empty cell, type a value, then press Enter.

5. To delete a value, click the line, then press Delete.

NOTE — If a parameter has List properties, but the list is undefined, the cells contain “Not defined” (in plain text).

Changing a FormulaThis is available only for parameters that have Formula properties.

To change the list of input values for a selected parameter follow these steps:

1. Click the cell whose properties are to be changed.


14 - visualPLOT

2. Click (Displayed) to display the Formula for input parameter koeff dialog box(Figure 233).

Figure 233. Formula for Input Parameter Koeff Dialog

3. In the Formula box, type a formula that will change the parameter value.

4. Click Test to view the change in parameter value.

The change appears in the Test Results pane.

NOTE — If parameter has Formula properties, but the formula is undefined, the cells contain “Not defined” (in plain text).

Aborting a TestThe user can abort a running test at any time.

1. From the General Controls toolbar, click (Abort Test).

2. The Test Abort dialog box opens (Figure 234).

Figure 234. Test Abort Dialog

3. Select Collect results to collect the results before aborting the test.

4. Click Yes to abort the test. Click No to not abort the test.



Setting the OrientationThe user can set the orientation of a parameter.

1. From the General Controls toolbar, click (Axes Reposition).

The Orientation change dialog box opens (Figure 235).

Figure 235. Orientation Change Dialog

2. Click the Orientation cell whose parameter are to be changed, then choose the desired orientation from the drop-down list.

3. Click OK.

Setting 3D Mode ParametersThe user can set the 3D parameters that control how a 3D graph appears in 3D mode.

To set the 3D parameters follow these steps:

1. From the General Controls toolbar, click (3D Mode).

The 3D axis definition. dialog box opens (Figure 236).

Figure 236. 3D Axis Definition Dialog


14 - visualPLOT

2. Click on the cell in the Name column that corresponds to the axis that is to be changed, then choose a parameter from the drop-down list.

3. Click OK. A 3D view of the test results appears in the Test Result pane, as shown in Figure 237.

Figure 237. 3D View of Test Results

4. Use the 3D Toolbar to adjust the presentation of the 3D view.

Defining StartUp and ShutDown FunctionsThe user can start and stop a test by defining StartUp and ShutDown functions. These functions are called before and after execution.

The user can select these functions from a test program received from visualATE.

To define a function follow these steps:

1. From the General Controls toolbar, click (Start/Stop Function).



The StartUp ShutDown test functions dialog box opens as shown in Figure 238.

Figure 238. StartUp ShutDown Test Functions

1. Choose a function from the StartUp function drop-down list.

NOTE — These functions can include function sets from visualATE.

2. In Function parameters choose a function from the ShutDown function list.

NOTE — These functions can include function sets from visualATE.

To disable a function, choose (None) from the StartUp function drop-down list.


14 - visualPLOT
