Skip to main content

Posts

Showing posts from April, 2015

GUIDED PROBE

13.0     GUIDED PROBE 13.1           The primary purpose of the guided probe is to verify fixture probe contact  continuity from a node on the UUT, through the test fixture, and down to the appropriate interface pin on the testhead. 13.2           To invoke the guided probe from a BT-BASIC window, click the mouse on the “Stop” softkey  or the “Stop” button on the operator keypad window. 13.3           At the BT-BASIC command line, type find pins .  This will clear the working area of the BT-BASIC window. Only two softkeys “Start”, F1 and “Done”, F8 will be now be displayed.  The following message will appear:                         Place the guided probe on the pin to ….. 13.4           Using the Board Graphics Viewer, locate the physical location of the suspect node. To be probed. 13.5           Click the mouse on the “Start” sofkey or press F1 on the keyboard. The node information of the point being probed will appear on the BT-BASIC window.  Note:

Full Diagnostics

12.6           Using the same method as for the previous window, highlight the “Full Diagnostics” selection. 12.7           Click the mouse on the “Execute” softkey, or press the F1 keyboard key. 12.8           The system self test will now execute automatically.  The test counter will appear in the top loft hand corner of the window and increment as the tests execute.  Any test failures will be displayed in the window as well. 12.9           When the first portion of the testing is completed, the following message will appear in the window: Move the self test fixture to the other testhead bank and press  to continue the test. 12.10       Remove the testhead cover from the unused bank of the testhead. 12.11        Move the selftest fixture to the unused bank of the testhead.  Install the protective cover on the opposite bank of the testhead. 12.12       Click the mouse on the “Continue” softkey, or press F1 on the keyboard.  The system will vacuum the sel

TEST STATION READINES – System Selftest Program

12.0     TEST STATION READINES – System Selftest Program 12.1           The system selftest program can only be executed while logged in under the service1 account. 12.2           At the system log in window, refer to figure 3, type in service1 and click the mouse on the “OK” button displayed on the screen or press the “ENTER” key on the keyboard. 12.3           The system will then prompt you to enter the proper password for the account that you are logging in under.  Click the mouse on the “OK” button displayed on the screen or press the “ENTER” key on the keyboard. 12.4     Place the system self test fixture, refer to figure 10, onto either bank 1 or 2 of the testhead.  Orient the test fixture so that the test points are towards the center of the testhead.    Ensure that the protective cover is installed over the unused bank. FIGURE 10 12.5     A “diagnostics” window will appear on the screen, refer to figure 11.

TEST STATION READINES - AutoAdjust Program

11.0     TEST STATION READINES - AutoAdjust Program 11.1     The autoadjust program can be executed while logged in the user1 account.  This program will also run automatically whenever there is greater than a 5 degree change in the testhead air temperature. 11.2     To manually run the autoadjust program, type autoadjust at the BT-BASIC command line and press the “ENTER” key on the keyboard.  11.3     The program will begin executing and you will see the BT-BASIC window go blank. 11.4     The following message will appear in the BT-BASIC window: AutoAdjust:    xxx of 472 tests completed. 11.5     The number in value xxx will increment from 1 to 472 as the test runs.  When the testing is completed the system will restore the default BT-BASIC window, reference figure 7. 11.6     The test status will be displayed on the status line of the BT-BASIC window: Completed = passed  or    AutoAdjust Failed = failed 11.7     If the autoadjust progra

TEST STATION READINESS – Confirmation Program

10.0     TEST STATION READINESS – Confirmation Program 10.1           There are two methods of determine system performance they are the selftest and confirmation programs. 10.2           The confirmation program can be executed while logged in the user1 account.  It is recommended that this program be run at least once a day.  This program does not require the use of the system self test fixture. 10.3           Type confirm at the BT-BASIC command line and press the “ENTER” key on the keyboard.  10.4           The program will begin executing and you will see the BT-BASIC window go blank. 10.5           The following message will appear in the BT-BASIC window: Confirmation:  xxx of 2232 tests completed. 10.6           The number in value xxx will increment from 1 to 2232 as the test runs.  When the testing is completed the system will restore the default BT-BASIC window, reference figure 7. 10.7           The test status will be displayed on the status

POWERING DOWN THE TESTER

9.0       POWERING DOWN THE TESTER             Note:   The test system must always be shut down in a controlled manner or data may be lost. 9.1               In order to properly power down the tester first all running processes must be halted and the disk drives must be unmounted. This process requires system root user privilege and must be performed by the test engineering department or its authorized representative. 9.2       Exit from all running BT-BASIC windows.              At the HP VUE graphical interface, click the mouse on the terminal icon on the Workspace Manager bar displayed at the bottom of the screen. 9.3         This will open an hpterm window on the screen.  If not currently logged into the system as user root, type the following at the command line $ prompt:  $ SU -root   and press the “ENTER” key on the keyboard. 9.4         Enter the correct password when queried by the system. 9.5         Type shutdown –h 1 at the command line # pr

BT-BASIC softkeys or the operator keypad window

8.11           The operator may use either the BT-BASIC softkeys or the operator keypad window to run the test. 8.11           When all testing is completed for this board type, execute the “stop” command, F7 softkey on the testmain window.  This will halt the HP3070 Testmain program and make the command line available. 8.18     Type fixture unlock at the BT-BASIC command line and press the “ENTER” key on the keyboard.  Remove the test fixture from the testhead and return it to the carousel for storage. 8.12           If there is another UUT type to test, repeat paragraphs 8.7 through 8.18.  If all testing is completed,  click the mouse on the “exit” buttonon the operator keypad.  Or type exit on the BT-BASIC command line. 8.20     This will return you to the HP VUE graphical interface. Click the mouse on the “EXIT” button on the Workspace Manager bar displayed at the bottom of the screen. Install the testhead covers to protect the system.

BT-BASIC commands used

8.10     Some of the most frequently used BT-BASIC commands used are: msi                               Changes default working directory. Mass storage is            Same as “msi” cat                               Catalogs (list)the node names in the specified directory.             get                               Brings the contents of a file into the system workspace.             load                             Same as “get”.             msi$                            Returns the directory pathname of the current working directory.             msi “..”                       Backs up one directory level.             findn                            Locates the next occurrence of the a given sting in the workspace. 8.11           If you wish to invoke the HP Board Graphics Viewer, type board graphics at the BT-BASIC command line and press the “ENTER” key on the keyboard. 8.12           A HP Board Graphics Viewer window should now appear

BT-BASIC command line

8.8       At the BT-BASIC command line type the command  msi  and the directory path, then press the “ENTER” key on the keyboard.  Example:                   msi ‘/hp3070/boards/aspect/main’ 8.9       At the BT-BASIC command line type the command  get ‘testplan’ and press the   ENTER” key on the keyboard.  You should now see the body of the testplan file displayed in the work space of the BT-BASIC window. 8.10     Some of the most frequently used BT-BASIC commands used are:

USER1 ACCOUNT SCREENS AND OPTIONS

5.0         USER1 ACCOUNT SCREENS AND OPTIONS 8.1       After successfully logging onto the tester under the “user1” account, the HP VUE             Environment screen will be displayed.   8.2               Click the mouse on the arrow above the “HP 3070” button on the Workspace Manager bar displayed at the bottom of the screen.  This will cause the “HP 3070 Programs” menu bar to be displayed, refer to figure 6 above. 8.3               Click the mouse on the “BT-BASIC” icon on the HP 3070 Programs menu bar. 8.4               This will open a “BT-BASIC” window similar to that shown in figure 7 below. Warning: Unix is a case sensitive programming language, type all commands in the case shown.  The BT-BASIC window is only active if the mouse is moved to within the window.  You will notice that the window frame will become highlighted when the mouse moves into the window. 8.5               Move the mouse into this BT-BASIC window, type  testhead is 1 on the c

Execute the “test fixture unlock”

7.2               If the load is successful then an HP3070 testmain will be displayed on the screen.  In addition the HP Board Graphics Viewer may be displayed as well.   7.3               Execute board testing as per paragraph 5.6 of the HP3070 Operating Procedure , SOP-3-1031-9. 7.4               When all testing is completed for this board type, execute the “exit” command, F8 softkey on the testmain window.  This will return you to the window shown in Figure 4. 7.5               Execute the “test fixture unlock” command, F3 softkey. 7.6               If there is another UUT type to test, repeat paragraphs 7.3 through 7.8.  If all testing is completed.  Execute the “quit” command, F8 softkey. 7.7               This will bring up a window similar to that shown in Figure 5.  Execute the “exit” command, F8 softkey to log off the tester. 7.8               Remove the test fixture from the testhead and install the testhead covers. Warning:  The testhead co

OPERATOR ACCOUNT SCREENS AND OPTIONS

5.0         OPERATOR ACCOUNT SCREENS AND OPTIONS 7.1       After successfully logging onto the tester under the “operator” account, a window similar 7.2               The special function keys shown in Figure 4 are mapped to the F1 through F8 keys on the keyboard.  These commands can be executed by pressing the appropriate “Fx” key or clicking on the box with the mouse.   (This works only when the mouse cursor is inside the window the contains the the special function keys.) 7.3               Lock the test fixture onto the testhead using the “fixture lock” command, F2 softkey. 7.4               Execute the “run testplan” command, F1 softkey.  This action will cause the tester to read the autofile code hard-strapped into the ICT test fixture.  The tester will then attempt to locate and load the testplan that corresponds to this autofile value. NOTE:           If for some reason the tester is unable to locate the correct autofile

LOGGING ON THE SYSTEM

5.0         LOGGING ON THE SYSTEM 6.1       When you first power up the test station, the operating system loads the necessary software to initialize.  When this “boot-up” process is complete, you will see a log on window similar to that shown in figure 3. 6.2         Trained and certified test operators may log in as user1.  All other operators must log in as operator. FIGURE 3 6.2         Type in the appropriate username at the log in screen and click the mouse on the “OK” button displayed on the screen or press the “ENTER” key on the keyboard. 6.3         The system will then prompt you to enter the proper password for the account that you are logging in under.  Click the mouse on the “OK” button displayed on the screen or press the “ENTER” key on the keyboard. 6.4         Following the process defined in the Test Department Procedure , SOP-3-1002-9, identify and locate the In-circuit Test Fixture required for the UUT to be tested. 6.5      

Testhead

4.3         Testhead The testhead is that portion of the tester that supports the PIN, ASRU and Controller cards.   The testhead is divided into two BANKS and each BANK is divided into two MODULES, see figure 2 below.  Bank 1 contains modules 0 and 1, bank 2 contains modules 2 and 3.  The test fixtures are placed on the banks of the tester and locked down for board testing.  The testhead cards interface to the test fixture through the spring loaded pogo pin “nails” at the top edge on each of these card types. 4.4       Support Bay The support bay is a stand-alone cabinet that houses the power supplies for the Unit Under Test.  This bay also houses the test station power distribution unit and test station controller on earlier models. 4.5       Emergency Shutdown Switch The emergency shutdown switch is the large red button located at the lower left corner on the front of the testhead.  It turns off all AC power to the testhead, and is equivalent to turning off the m

TEST STATION CONTROLS AND FEATURES

4.0       TEST STATION CONTROLS AND FEATURES 4.1       In the production-testing environment, a test station is most often used by a board test operator.   Figure 1 below shows a typical test station and its primary features.   FIGURE 1 4.2       Some of the primary operator features are: Bar Code Wand                       Saves time and minimizes error when entering board serial numbers. Emergency Shutdown                        Pressing the Emergency Shutdown button powers down the Switch                                     testhead and its associated equipment in an emergency situation. Guided Probe                           Used to verify fixture probe contact continuity from a node on the board under test, through the test fixture, and down to the appropriate interface pin.  Also used to verify fixture wiring.             Operator Footswitch               Functionally the same as the “start” button on the operator keypad, and can