H3 GUI Manual

Tanisys M550 User’s Manual

H3

Graphical User Interface

OPERATIONS MANUAL

August 2010

Copyright

© 2010, 2011 Tanisys Technology, Inc. All rights reserved. Test software and menu screens

are protected by copyright under applicable laws. This manual may not be copied or reproduced in any manner without prior written permission of Tanisys Technology, Inc. The Tanisys logo is a registered trademark of Tanisys Technology, Inc. DNA•2 is a trademark of Tanisys Technology, Inc. Other brand and product names are trademarks of their respective holders

This page has been left intentionally blank.

H3 GUI OPERATIONS MANUAL

Table of Contents 3

Table of Contents

Chapter 1: Introduction__________________________________________________ 5

1.1 Use of this document __________________________________________________ 5

1.2 Document Conventions ________________________________________________ 6

Chapter 2: Quick Start Guide _____________________________________________ 7

2.1 Starting the Hardware _________________________________________________ 7

2.2 Starting the H3 GUI ___________________________________________________ 7

2.3 Loading and Running a Recipe __________________________________________ 9 2.3.1 Change the User Privilege _________________________________________ 9 2.3.2 Lock the HW Core board or Sub-Chassis component or Chassis __________ 10 2.3.3 Load an XML Recipe file _________________________________________ 11 2.3.4 Run the desired Recipe __________________________________________ 13

Chapter 3: H3 GUI Comprehensive Usage _________________________________ 16

3.1 File Menu__________________________________________________________ 16 3.1.1 Load Recipe… _________________________________________________ 16 3.1.2 New Recipe ___________________________________________________ 17 3.1.3 Save Recipe ___________________________________________________ 24 3.1.4 Save Recipe As … ______________________________________________ 25 3.1.5 Close Recipe __________________________________________________ 25 3.1.6 Exit __________________________________________________________ 25

3.2 View Menu _________________________________________________________ 26 3.2.1 Refresh Blades_________________________________________________ 26 3.2.2 DUT Display ___________________________________________________ 27 3.2.3 Recipe _______________________________________________________ 28 3.2.4 Log __________________________________________________________ 29 3.2.5 Real Time Statistics _____________________________________________ 31 3.2.6 Blades _______________________________________________________ 32

3.3 Lot Management Menu _______________________________________________ 33

3.4 Tools Menu ________________________________________________________ 33 3.4.1 Change Privilege _______________________________________________ 34 3.4.2 Start Custom Front End __________________________________________ 35 3.4.3 Reset Real Time Monitor _________________________________________ 35 3.4.4 Run Tests_____________________________________________________ 36 3.4.5 GPIB Settings… ________________________________________________ 36 3.4.6 Options… _____________________________________________________ 37 3.4.7 Load Hifix Configuration __________________________________________ 38

3.5 Help ______________________________________________________________ 39

Chapter 4: Contact Information __________________________________________ 40


Table of Contents 4

4.1 Technical Support ___________________________________________________ 40

4.2 Corporate Offices: ___________________________________________________ 40

4.3 Global Field Sales / Support Offices: _____________________________________ 40

Appendix A: Glossary ____________________________________________________ 41


Chapter 1: Introduction 5

Chapter 1: Introduction The goal of this manual is to enable operators to utilize the H3 Graphical User Interface (GUI).

1.1 Use of this document

Thank you for choosing to use the H3 Graphical User Interface on a Tanisys Test System Platform. The development team at Tanisys is proud to provide you, our customer, with some of the most advanced tools available to develop sophisticated test programs on a Tanisys Test Platform. This document contains the information needed to utilize the H3 Graphical User Interface.


Chapter 1: Introduction 6

1.2 Document Conventions

The table below outlines the conventions used in this documentation.

Item Convention Example

Acronyms Uppercase CS, DRAM

Book titles Italic The Hardware Reference

Code example Monospace #include . . .

Commands on menus and buttons

Bold Run Test . . .

Constants Bold cm_per_inch

Device Names Uppercase COM1, AUX port

Dialog-box titles Bold Parallel PD Bit Setup

Dialog- box options Bold Read, OK

Directories Bold DNA2\R1.10\Tester

Environment variables Uppercase INCLUDE

Extensions (file) Bold anyFile.t2s

File names Bold the Constants.t2s file

Folders Bold the Recipes folder

Functions and methods Bold KnotsToMiles function

Icon names Title caps Accessories icon

Key names, combinations, and sequences, title caps

Bold Ctrl, Ctrl+Alt+Del

Keywords (of language or operating system)

Bold typedef

Links Underscore and blue. Documentation Links

Logical keys Title caps Insert Field key

Logical operators Bold, uppercase AND, OR

Macros Bold LOWORD

Menu names (in Windows) Bold, title caps File menu

New terms Italic The handler

Operators Bold +, –

Placeholders Italic Type the password.

Programs Title caps (or as used by producer)

Visio

Registers Uppercase REGS registers

User input Italic Type -cCutoff

Variables Italic the lineno variable


Chapter 2: Quick Start Guide 7

Chapter 2: Quick Start Guide The H3 GUI will be installed in a Windows based Desktop Controller PC. The program and all subcomponents will be pre-installed, so the user will have the opportunity to start the use of the H3 GUI very quickly. If Tanisys Software is not pre-installed on the Desktop Controller PC, a soft copy of it will be available on both a CD and on the Tanisys FTP site (206.127.28.196). For the latter case, instructions for Tanisys Software retrieval and installation procedure will be made available separately.

2.1 Starting the Hardware

The preferred process, for running Tanisys Test Systems, is to turn on the HW first. The user should switch on the Tester Chassis by lifting up a Power switch or pressing a button. Once the HW is on for 5 to 10 minutes depending on specific systems, then one can start the use of the H3 GUI on the Desktop Controller PC.

2.2 Starting the H3 GUI

To get the H3 GUI started, please either double click the Desktop Icon labeled H3. The Desktop Icon looks like the one shown below.

H3 GUI Desktop Icon

An alternative way of starting the H3 GUI is to go to:

Start button��Programs��Tanisys Technology�� H3



As the H3 GUI is loading the splash display below will pop up and then disappear when the H3 GUI has fully loaded.

H3 GUI start up splash pop up

Once the H3 GUI has fully loaded the window below will appear.

H3 GUI after it’s fully loaded



2.3 Loading and Running a Recipe

To run any test on the H3 GUI, one needs to load a Recipe. In order to load a Recipe on the GUI, there are a number of steps that need to be taken. These are: � Change the User Privilege � Lock the Hardware (HW) Core board or Sub-Chassis component or Chassis � Load an XML Recipe file � Run the desired Recipe

Please find the following sub-chapters describing this process

2.3.1 Change the User Privilege

The default Privilege level of the H3 GUI is “Basic”. The next set of instructions is based on that fact. If the Privilege level has been previously set to either “Tech” or “Expert” then this Section may be skipped. Under the Tools menu option, one can find an option called “Change Privilege”, under which all Privilege levels reside.

Illustration of how to change the privilege level



Once the user clicks on either “Tech” or “Expert”, then the user must know and input the required password for this access level. Tanisys Technology Inc provides these separately to the appropriate level staff. The different user levels allow access control of features that can be altered within the H3 GUI. The “Expert” user has full access.

Change Privilege Screen

2.3.2 Lock the HW Core board or Sub-Chassis component or Chassis

The user must “Lock” the HW to initiate communication between the HW and the H3 GUI. To do so, one must right click on either: the HW Core Board (called the Blade in many cases) the Sub-Chassis component (called Bay in many cases) the Chassis The following figure illustrates how to “Lock” the HW Core Board.

Locking the HW Core Board or Blade in this particular case



2.3.3 Load an XML Recipe file

To load a recipe file the user may do so one of three ways. These are: � Press “F3” on the keyboard � Go to File�Load Recipe… � Click on folder button on the GUI

The last two are illustrated below.

Opening Recipe from File menu

Opening Recipe via Folder button



Once one of those three methods is used to open a recipe, the window shown below will appear and the user must select a desired recipe. Usually recipe files have an .xml extension.

Window showing recipe files to open



Once a recipe is opened, the “XML Recipe” tab will show the recipe’s test blocks and other components as shown below.

Illustration showing an open recipe

2.3.4 Run the desired Recipe

Running a recipe is as easy as: � Pressing “F5” on the keyboard � Alternatively you may click the green Play button shown below

Run button on H3 GUI



Once the user starts running a recipe, most buttons will gray out and the Stop button will become available for use. The Stop button is used in cases, where the user wants to abort a test run. The “Log View” window, below, shows status of tests from the first Test Block to the last is executed. The user may chose to monitor it for immediate intermediary result checking as the recipe is running.

Illustration of recipe running



Once the recipe has completed it’s run or has been stopped manually by the user via the Stop button, then the Play button will become available again for the following run. At the same time, the results for the last run will be available on the “DUT Display” tab. The numbers shown in the grid represent a “Bin Code” for each individual DUT.

Illustration of DUT Display tab and individual DUT results


Chapter 3: H3 GUI Comprehensive Usage 16

Chapter 3: H3 GUI Comprehensive Usage The H3 GUI has an extended set of menus, views and displays. In this chapter, the user will be able to understand the value and usage of such.

3.1 File Menu

The “File” Menu is composed of several options. All of which, are designed to give the user the ability to manipulate Recipes. Please see the illustration below showing all available options under the “File” Menu.

File Menu

3.1.1 Load Recipe…

The “Load Recipe…” menu option under the “File” menu allows the user to open an existing recipe. Some details of this option have been previously covered in Section 2.3.3 of this Manual.



3.1.2 New Recipe

The “New Recipe” menu option under the “File” menu allows the user to create a NEW recipe from scratch. In this sub-Section of the manual, we will go over an example of how to create a very simple recipe, to illustrate general usage.

3.1.2.1 Create and Save a NEW xml file

To create and save a NEW xml file, the user has to click on the “New Recipe” menu option under the “File” menu. That will open the following window. In the case below, the user has entered the name “NewRecipe” as a file name for the NEW xml file to be created. Upon clicking the “Save” button, the resulting NEW xml recipe will be “NewRecipe.xml”. One thing to note, a recipe can reside anywhere on the Desktop PC Controller, so the user may have also decided to change the “Save in” location of the resulting xml file.

Illustration of NEW xml creation and save



Once the NEW recipe has been created and saved, the “XML Recipe” tab will display the recipe.

Illustration of a NEW recipe upon creation

The NEW recipe will have “Global_User” and “Global_System” input parameters. The user does generally not use these. It is highly recommended for a user not to alter these, unless advised by Tanisys. The right side of the illustration shows the details of what’s available for viewing or change for the item highlighted on the left side. The example above shows “Global_User” highlighted (left side) and the properties of it (right side). If the user clicks on the “NewRecipe.xml” name in the tree view of the recipe (left side of the above illustration), the user can see and alter the path and filename of the associated “Executable” file for the recipe. The “Download Files” tab on the right hand side of the above illustration is now obsolete and should not be used by the user.



If the user clicks on “Types”, the H3 GUI will display all available types of variables.

Illustration of “Types” in a recipe

3.1.2.2 Manipulating Test Blocks and Input Parameters

On all types of recipes, whether new or existing, the user will, more than likely, need to add/alter Test Blocks and Input Parameters.



To add a Test Block, the user must right click on the recipe name. In the case below, the user has right clicked on the “NewRecipe.xml” label to bring up the menu. Once the menu is up, the user can click on “Add Testblock”.

Illustration of “Add Testblock”

Once the “Add Testblock” has been clicked, the “Test Block Editor” window will pop up. The user must then input a “Test Block Name” and a “Test Block Type”. The example below shows the user has typed “NewTestBlockName” and “NewTestBlockType” in the respective fields. Take note, the “Test Block Type” must match the name in the application. (please see Programming Manual for details)

Test Block Editor



Once the above input has been entered and the user has clicked “Save”, the resulting NEW Test Block will appear in the tree view of the recipe as shown below.

New Test Block

To add an Input Parameter to a Test Block, the user must click on the “Types” tab and drag and drop the desired variable type from “Types” (see left on illustration below) to the Test Block (see right on the illustration below). In the following case, the user has dragged and dropped a “bool” type into the “NewTestBlockName” test block.

Drag and Drop of “bool” type into a Test Block



The user can drag and drop as many Input Parameters into a Test Block. In the case below, several steps were taken. The user changed the name of the “bool” variable to “bBoolVariable”. The user also dragged and dropped a “char” variable, which the user later changed its name to “sString”. The user also changed the “Cnt”, which is the count of characters from the default of “1” to “5”. The user changed the “Value” of “sString” from a default of “0” to “Hello”.

Input Parameter manipulation



Clicking back to the “Recipe” tab from “Types”, the user can then follow up with several other action with a Test Block. To do so, the user must right click on the Test Block label, to bring up the menu. Please see below illustration. The user can choose several actions including:

� Adding another Test Block � Deleting the highlighted Test Block � Copying and Pasting the Test Block (once a “Copy” followed by a “Paste” occurs, H3

will automatically set a different Test Block Name to the New Test Block, but will keep the Test Block Type and all properties and Input Parameters)

� Moving up or down the Test Block in the list (if you have more than 1 Test Block) � Enabling and Disabling one or more Test Blocks will change the execution of recipe. (a

check mark on the left side of the Test Block indicates whether a certain Test Block is enabled or disabled.

� Importing and Exporting isn’t supported any longer. � Closing a recipe is also an option.

Available Menu for Test Blocks



There are also a number of available actions for an Input Parameter. Right clicking on any Input Parameter will give the user access to the options available (right hand side of illustration below). The main ones are copying and pasting.

Available Menu for Input Parameters

3.1.3 Save Recipe

The user may save the recipe file under a previously selected recipe name (in the previously selected file path) by clicking “Save Recipe” under the “File” menu. Alternatively, the user may click on the “Save” button shown in the below illustration.

“Save” button



3.1.4 Save Recipe As …

The user may save the recipe file under a different name and path by clicking on “Save Recipe As …” under the “File” menu. A window will pop up to select the new name and desired location on the Desktop PC Controller. Please see illustration below.

Save Recipe As … window pop up

3.1.5 Close Recipe

The user may close a recipe by clicking “Close Recipe” under the “File” menu or by pressing the “x” button at the top right hand corner of the inner window.

3.1.6 Exit

The user may close the H3 GUI by clicking “Exit” under the “File” menu or by pressing the “x” button at the top right hand corner of the top window.



3.2 View Menu

The “View” Menu is composed of several options. All of which, are designed to give the user the ability to switch view of different parts of the H3 GUI. Please see the illustration below showing all available options under the “View” Menu.

“View” Menu

3.2.1 Refresh Blades

The “Refresh Blades” label under the “View” menu allows the user to “ping” or re-initiate connection to the HW Core board of the system. In many cases, this type of board is referred to as a “Blade”. Upon clicking on the “Refresh Blades” label, the Tanisys Test system will update the “Log View” window with all HW Core boards that have communicated back to the H3 GUI. Please see example of such below.

“Log View” after a “Refresh Blade” click



3.2.2 DUT Display

The “DUT Display” label under the “View” menu allows the user to bring up the graphical representation of the DUTs. This is a grid showing a partition of DUTs, with several features. The equivalent can be achieved by either pressing “F7” or pressing the “DUT Display” tab. Please see illustration below for details.

DUT Display

There are several viewing features on the “DUT Display” window: In general, test sites, that are available on all HW Core boards within a Chassis, are either represented with a white, green, gray or black rectangle. (i.e. “white” if HW Core board is Locked; “green” if HW Core board is Unlocked; “gray” if HW Core board is Locked, but specific DUT is disabled; “black” if HW Core board is not physically present within a Chassis). The “DUT Display” window also features a “Blade Info” box, in which the Chassis Serial Number, the Bay Number within a Chassis, the Slot Number of the Blade within a Bay, the Blade Serial Number, the IP address of the Blade, the Port to which the Blade is attached as well as the Lock/Unlock status.



There is also a “Legend” box that provides a quick reference to all permutations for status of any particular DUT, including the Bin Code coloring scheme for specific DUTs. In general, the previous test run result is represented within the rectangle containing the specific DUT, in which a Bin Code in “green” font represents a passing condition and a Bin Code in “red” font represents a failing condition. The user that developed the application determines the Bin Code number. In general, HW Bin Codes are used for binning compartments of Handlers or other equipment attached to a Tanisys Test System. The number of such HW Bin Codes is usually small (i.e. usually under 10 HW Bin Codes). On the other hand, SW Bin Codes give the freedom to the application developer the opportunity to use a large number of SW Bin Codes to distinguish between a variety of failure signatures of a failing DUT. The application developer can then associate a number of SW Bin Codes to a specific HW Bin Code. Please review the Programming Manual for more details on Bin Codes. There are a few action features on the “DUT Display” window: The user may Enable or Disable a particular DUT by either, right clicking on a particular DUT and selecting the opposite state from the current state of a DUT. (i.e. user can enable a previously disabled DUT or disable a previously enabled DUT). The same action can be achieved by selecting a particular DUT and pressing either the “Disable DUT” or “Enable DUT” on the right hand side of the grid. The “Import” and “Export” buttons should NOT be used, unless previously instructed by Tanisys. The user may also change the view of the “DUT Display” grid by selecting from a pull down between “Show Bin Codes” and “Show Hifix Index”. The first shows the DUT results from the previous test run. The latter shows the configuration of DUTs of a system that’s connected to a Hifix and Handler. The user is also given the ability to view the Bin Codes in, either, Hex or Decimal as well as the ability for the H3 GUI to do the translation of Soft to Hard Bin Codes. These can be achieved by a click or unclick of the check boxes named “Hex” and “H/W” respectively.

3.2.3 Recipe

The “Recipe” label under the “View” menu allows the user to bring up the “XML Recipe” tab. Either pressing “F8” or pressing the “XML Recipe” tab itself can achieve the equivalent.



3.2.4 Log

The “Log” label under the “View” menu allows the user to bring up the “Log View” tab. Either pressing “F9” or pressing the “Log View” tab itself can achieve the equivalent. Please see the “Log View” tab shown below. The “Log View” displays the test results and print output from the user developed application.

“Log View”

3.2.4.1 Clear All

The “Clear All” button under “Log View” allows the user to clear the displayed text previously on the “Log View” window.

3.2.4.2 Log View Pull Down

The “Log View” pull-down defaulted with the name “All” allows the user to filter the displayed application output by HW Core board or Blade. The illustration below shows an example of this.

Pull down on “Log View” to filter by Blade



3.2.4.3 Log File Change

The H3 GUI allows for logging to not only be displayed in “Log View”, but to automatically save a text file in any user specified location, containing all the same data. Under the “Log View” tab, the user can select a new filename and location by clicking the button next to the current file display.

Current log file and location

If the user clicks the above button, then the following window will pop up. The user may then select a filename and file path for the application output log. The log file name selected by the user is used to create the first log file. Subsequent log file names after the first has reached its predetermined size, will be a combination of the selected log file name and a number to indicate which one it is. The size and number of log files kept in the system is determined by the selections of the user in the Options Menu.

Selecting a new log file named “NewLogFile”



3.2.5 Real Time Statistics

The “Real Time Statistics” label under the “View” menu allows the user to view real time statistics of test results with various filters to obtain the desired data. When the user clicks on that label the tab below comes to the forefront. The equivalent would happen if the user just clicked on the “Real Time Statistics” tab adjacent to the “Log View” tab at the bottom of the H3 GUI. Please see the illustration below for details.

3.2.5.1 Results by Chassis

The “Real Time Statistics” tab has results by Chassis (see top of previous illustration or details below). The amount on the bar that’s filled indicates the passing rate on each individual Blade (i.e. HW Core board).

Results by Chassis with no filtering



3.2.5.2 Results by Blade

The “Real Time Statistics” tab has results by Blade (see top of previous illustration or details below). The amount on the bar that’s filled indicates the passing rate on each individual DUT slot.

Results by Blade with no filtering

3.2.5.3 Filtering

The “Real Time Statistics” tab allows the user to filter the data and narrow down to only display results of interest. The “Select Blade” box allows the user to pick any one Blade or All. The “Select DUT” box allows the user to pick any one DUT on each selected Blade.

Filtering data to display

3.2.6 Blades

The “Blades” button under “View” menu allows the user to bring the “Blades” tab to the forefront. The equivalent action would be to click on the “Blades” tab directly.



3.3 Lot Management Menu

The “Lot Management” Menu and all sub-component options are now obsolete and will be removed completely in a future release. Please refer below illustration for details.

“Lot Management” menu

3.4 Tools Menu

The “Tools” Menu is composed of several options. This section of the H3 GUI Operations manual will go over the details of the “Tools” Menu. Please see the illustration below showing all available options.

“Tools” Menu



3.4.1 Change Privilege

Under the Tools menu option, one can find an option called “Change Privilege”, under which all Privilege levels reside. The user must click on “Change Privilege” to bring up the options available and they are: “Basic”, “Tech” and “Expert”.

Illustration of how to change the privilege level

The “Basic” option does not require any further input. However, once the user clicks on either “Tech” or “Expert”, then the user must know and input the required password for this access level. Tanisys Technology Inc provides these separately to the appropriate level staff.

Change Privilege Screen



3.4.2 Start Custom Front End

The “Start Custom Front End” option under the “Tools” menu is designed to launch any third party GUI control application designed by the customer. This button is basically used to launch all third party custom front end GUI/programs. If none, is available the error window below will appear.

H3 GUI Error if no third party custom front end is found

3.4.3 Reset Real Time Monitor

The “Reset Real Time Monitor” option under the “Tools” menu can be used by the user to reset all real time statistics to zero. Once the user has clicked on “Reset Real Time Monitor”, a warning window will pop up to ensure the user is given the opportunity to make a decision on the erasing of real time statistics data. The details, of the data being erased, have been previously covered in Section 3.2.5. Please refer to the illustration below for details.

Warning window to ensure user is sure prior to erase of real time statistics data



3.4.4 Run Tests

The “Run Tests” option under the “Tools” menu can be used by the user to run two Tanisys provided applications. These are Calibration and Diagnostics. Clicking on the “Run Tests”, then clicking on either “Run Calibration” or “Run Diagnostics” can do this Please refer to the illustration below to see the details.

“Run Tests” options to run Calibration and Diagnostics applications

3.4.5 GPIB Settings…

The “GPIB Settings…” option under the “Tools” menu can be used by the user to change GPIB settings to other equipment attached to the Tanisys Test System. In most cases, this equipment is a Handler. Once the user clicks on “GPIB Settings…”, the window shown below will appear. The options selected must match the settings set on the Handler.

“GPIB Settings” window and options



3.4.6 Options…

The “Options…” label under the “Tools” menu can be utilized by the user to alter settings, including Error Bin Codes, Timeouts and Logging options. Once the user clicks on “Options…”, window shown below will appear. The “Errors” field lets the user update the specific Hardware Bin Code to be used for System Failures. The “Timeouts” fields allow the user to update: a) the timeout to be used to locate a Blade in milliseconds; b) the timeout to be used to ensure a recipe does not run indefinitely (note: a timeout of “0” in this field does allow an infinite timeout); c) the timeout to be used to check connectivity with an attached Handler. The “Log View” field allows the user to set the maximum number of lines made available in the “Log View” tab at the bottom of the H3 GUI. The “Log File” fields allow the user to select: a) the maximum size of any saved log file; and b) the maximum number of log files present on the Desktop PC Controller at any time. The “Yield Colors” fields allow the user to change the coloring scheme of the passing yield bars in the “Real Time Statistics” tab.

“Options” window



3.4.7 Load Hifix Configuration

The “Load Hifix Configuration” option under the “Tools” menu allow the user to select a Hifix or DUT configuration file to match the corresponding Tanisys Test System configuration attached to the Desktop PC Controller. Once the user clicks on the “Load Hifix Configuration” label, the window shown below appears, from which the user may select a previously saved “Hifix Config File” already on the system.

Selecting a Hifix Configuration file to match the Hardware



3.5 Help

The “Help” menu option can be utilized by the user to identify important information regarding the installed version of the H3 GUI. Once the user clicks on the “Help” label, the window shown below appears. The details included are: a) Title of GUI; b) Product Version; c) File Version; d) User Level and e) Copyright Information.

“Help” menu


Chapter 4: Contact Information 40

Chapter 4: Contact Information

4.1 Technical Support

Email is the best mode of contact for technical support. Click the link below:

[email protected] Customer Service (toll free): 1-888-255-2210

4.2 Corporate Offices:

TANISYS Technology 11001 Lakeline Blvd. Building 1, Suite 150 Austin, TX 78717 512-335-4440 800-533-1744 http://www.tanisys.com/

4.3 Global Field Sales / Support Offices:

Europe - High Tech Trade gmbh Korea - NeoSem Mario Will DH Yeom 49 (089) 54 67 8542 82 31 213 6338 [email protected] [email protected]


Appendix A: Glossary 41

Appendix A: Glossary The following table contains a brief description of frequently used terms and acronyms discussed in various Tanisys test system manuals.

TERM / ACRONYM DEFINITION

ADC Analog to Digital Converter Bin View Represents either or both software and hardware data collection

counter bins CDROM Compact Disk Read Only Memory Clock A continuously running signal that provides the timing reference

for all DUT operations. Controlled Impedance A means of routing signals while maintaining a constant wiring

impedance from source to termination. DAC Digital to Analog Converter DUT Adapter A plug-in interface board that has test sockets specific to a

particular physical size and class of memory module. DPS Digital Power Supply DUT Device under test DVD Digital Versatile Disk DVM Digital Voltmeter EEPROM Electrically Erasable Programmable Read-Only Memory. A

nonvolatile memory device that can retain information when power is removed

ESD Electrostatic Discharge. Static electricity charges that can accumulate to thousands of volts (when a person moves across a floor, for example) which can discharge to and damage electronic devices. A grounded wrist strap can provide protection at the workstation against ESD.



ETC (Embedded Tester Control)

A device independent DNA2 module, which operates on the embedded processor as a intermediary between the Tester Control on the PC and the Tester’s hardware. Its primary job is to launch test applications, communicate testing progress and results and manage the testing process to maximize testing.

FIFO First In, First Out FRU Field Replaceable Unit GUI Graphic User Interface Handler Automated equipment attached to a memory tester; used for bulk

testing and sorting of memory modules or chips into Passed and Failed bins.

IC (Integrated Circuit) As used here, an individual memory chip mounted on a module or card.

JEDEC Joint Electron Device Engineering Council. An industry group established to agree upon standards for electronic components such as memory devices.

LED Light-Emitting Diode. A rugged solid-state indicator that emits light at a specific color.

Map View Visual representation of active, inactive, or disabled test sites NFS The NFS Server allows the embedded Linux system access to

the Windows file system. Security can be individually configured for each shared directory.

ns (nanosecond) One billionth of a second. Mathematically: 10 –9 seconds. 1ns = 1E-09 sec

P/N Part Number Parity A system of storing one additional bit per byte, allowing detection

of single-bit errors. PC Personal Computer PCB Printed Circuit Board PMU Parametric Measurement Unit. A precision device to measure

DC voltage and current. R/W Read/Write Recipe Test File (.tts) SCB site configuration board TCM A device independent DNA2 module, which operates on the PC

as a intermediary between the GUI on the PC and the ETC module executing on the tester hardware. Its primary job is to maintain the operational status of the tester hardware and route the messages between the PC and embedded tester processors.

Test Block One or more test blocks are contained in a test flow. UDP User Datagram Protocol µs (microsecond) One millionth of a second. Mathematically: 10 –6 seconds.

1µs = 1E-06 sec Width The number of bits that can be read or written in a single memory



cycle. Windows Microsoft Windows XP Professional Work Flow Flowchart of test blocks contained in the test file. Workspace Establishes the software configuration, (i.e. software view,

software behavior, visible windows, map view, bin view, etc.) XML Extensible Markup Language

H3 GUI Manual

Documents

hw core boards

desktop pc

desktop controller

hw core board

quick start

hw bin codes

sw bin codes

log view tab