Module 10 Shorts &amp Pins Push Button Debug

Agilent 3070 User Fundamentals
Module 10: PushButton Debug for Shorts & Pins Tests
Table of Contents
The Test Development Process ..............................................................................2 Agilent PushButton Debug.....................................................................................3 Start Agilent PushButton Debug ..................................................................4 The PushButton Debug interface offers two levels of debug.................................5 Board Level Debug.......................................................................................5 Device Level Debug .....................................................................................7 PushButton Debug's Pulldown Menus .........................................................8 The MACROS Menu..................................................................................10 HELP Menu................................................................................................13 How these Menus apply to Fixture Verification.........................................14 How these Menus apply to Shorts & Pins ..................................................16 Lab Preparation ....................................................................................................18 LAB 10A: Verify Fixture Wiring.........................................................................19 LAB 10B: Debug Shorts and Pins Tests ..............................................................28 Questions and Answers about Shorts Testing ......................................................36 Review........................................................................................................39
PushButton Debug for Pins & Shorts 10 - 1
Agilent Technologies
Test Development Flow chart

Process
1 2
Files
board
Tools
CAMCAD Translator BT-BASIC Board Consultant Part Description Editor Digital Setup Editor IPG Test Consultant PushButton Debug
Translate CAD Describe board & system
board_xy config Custom libraries
3 4 5 6
Generate Test & Fixture files Build & Verify test Fixture Turn-On / Debug all Tests Release to Production & Long Term Support
testability.rpt Fixture Files Individual Test Files testplan
ECO
Generates
Modify
1
3070 User Fundamentals Module 10: Shorts & Pins Debug
sA
The Test Development Process

In previous modules you: Created the directory and the "config" file Translated the CAD data using CAMCAD Finished the board description using Board Consultant, the Part Description Editor and the Digital Setup Editor Generated and evaluated the "testability.rpt" Ran Test Consultant to generate fixture and test files Learned about verifying the test fixture Examined the Pins Test and the Shorts Test theory Having built the fixture, you are ready to verify the fixture and begin turning on the individual tests that comprise the overall 3070-test suite. In this lecture, you will: Learn about Agilent's PushButton Debug interface and learn to use it to verify the test fixture and when testing Pins and Shorts. After a discussion of analog incircuit tests, you will see how to use PushButton Debug to turn-on and debug those tests. Etc. During the lab, you will: Use PushButton Debug to verify the test fixture. Use PushButton Debug to turn-on and debug the Pins and Shorts tests.
Agilent PushButton Debug
sA

Agilent PushButton Debug is the interface used to verify the fixture, turn-on and debug your new tests. It is also used to turn-on and debug boards after engineering changes. When you have learned to debug, it really does not matter if it is newly developed board or an ECO. Most of the functions that PushButton Debug provides can be done directly from the BT-BASIC window. However, to do all these functions requires the programmer to remember hundreds of commands and options to those commands.
During this module, you will start the debug process with Fixture Verification, Pins and Shorts tests. There is a "Pre-Shorts test" which sets switches, jumpers and potentiometers in known states before running the Pins or Shorts test. The Angela Board does not have any adjustable devices (it does have them, but they are to simulate failures, the software does not know about the switches), so we are skipping the Pre-Shorts test for now. You will see it later.
Start Agilent PushButton Debug

There are several possible ways to start PushButton Debug. Use the CDE Panel and popup menu - you will receive a query window asking for the path to your board directory. You can start it from BT-BASIC. This method will be illustrated in the lab. msi "<board directory>" load board | debug board If you are using an NT controller, there is a shortcut icon, double click on that icon.
sA
Board Level Device Level
The PushButton Debug interface offers two levels of debug

Board Level Debug

The Board Level of PushButton Debug is used for system and test initialization. Board Level Debug functions are grouped under the SETUP MACRO menu and include: Initialize and take control of the testhead Load the testplan Lock the fixture to the testhead Verify the fixture
A second function of Board Level Debug is testing groups of devices based on their test type. These test functions are grouped under the TESTPLAN MACRO selection: Pre-Shorts test Shorts test Analog Incircuit tests TestJet Polarity Check Connect Check Turn on the power supplies Digital Incircuit tests Analog Functional tests Boundary Scan tests Remove power from the board Apply power to the board Provide access to custom macros that you write
Analysis is a third function of Board Level Debug. Having turned on the tests, you need to analyze the quality of the tests. This is done using reports and tests under the TEST GRADER MACROS. This macro is currently not available on the MS Windows . This macro includes: Generate Test Coverage Report Create Grading Config & Testplan Grade Tests
A fourth function is available with optional software (Quick 70). This is the Quick Report Macro and generator. This report creates a summary of how to optimize your tests for better throughput. This function will not be taught during this class.
sA
Device Level Debug

Using Board Level Debug, load the board's tests, initialize the testhead and run a specific test subroutine. This provides a list of devices that need to be debugged. When you have the list, you start debugging those devices. This moves to the Device Level of debug. Initialize with Board Level Debug: Initialize test with the SETUP_MACRO. Use the TESTHEAD_MACRO to test a specific type of test. (E.g.: analog incircuit, digital incircuit, ...) This results in a list of failing devices. You need to debug each failing device. Device Level Debug: Use the DEBUG menu to debug a specific device or the next component in the list of failing devices. When you select a specific device to debug, the entire debug environment changes from the Board Level to the Device Level. In the Device Level, the menus change according to what subsystem is entered. The Analog subsystem uses a different set of debug tools than used by the Digital subsystem. During this module, the emphasis will be on learning to navigate and use the PushButton Debug interface and specifically on Pins and Shorts debug tools.
sA
PushButton Debug's Pulldown Menus

There are five menu selections across the top of the PushButton Debug window. They are FILE, DEBUG, EDIT, MACROS and HELP. FILE When this selection is clicked, the following list is offered: Open..., New Save Save As... path Unlink... Exit a new board directory reset PushButton Debug save custom macros that you might create save the custom macros in a specific directory delete a specific file close PushButton Debug
Agilent 3070 User Fundamentals Debug When this selection is clicked, the following list is offered. It is assumed that you have a list of failing devices. The software automatically highlights the first device in the list. You can click on a device in the list to move the highlight marker. Debug Next Test Debug the next device after the one highlighted. Debug Selected Test Debug the highlighted device Debug Test... Specify a device for debug - not on list is okay Debug Current Test Debug the highlighted device Debug Board Return to the Board Level of Debug Debug Status Returns the level of debug Compile Selected Test Create an object for the highlighted device Compile Selected Test; Debug Create a debug object highlighted device Compile Test... Create an object for a specified device Mark Permanent Mark the test permanent in the "testorder" file
These various levels of debug will be explained in detail during the labs, when you actually use them.
Agilent Technologies The EDIT Menu When the EDIT selection offers tools to assist you in moving through a file and editing it. This is not the best text editor in the world. Indeed, the debug editor is only provided so you can easily make simple changes and document them. When this selection is clicked the following list is offered: Cut Delete highlighted text Copy Copy highlighted text into mouse buffer Paste Paste mouse buffer at point where cursor is now Find String... Search for specified word or phrase Go To Line... Move to a specified line number Duplicate A Line Paste a copy of the current line below the current line
The Duplicate A Line function is particularly important. When debugging a test, it is recommended that you duplicate a line, comment the original line so it is not executed and change the copy of the line. This makes the code self documented and when you return to work on this test several weeks or months after the initial turn-on, you have an immediate history. This will save you lots of time in the long run.
The MACROS Menu

Selecting the MACROS menu gives you the following choices: Setup Macros Testplan Macros Board Grading Macros Quick Report Macros
Each of these will be reviewed, but only to the level that applies for Pins and Shorts testing. During later modules, more functionality will be described.
Agilent 3070 User Fundamentals SETUP MACROS The Setup Macros menu offers the following sub-menu: Initialize All Setup the testhead to perform tests. Testhead Power On Restart the testhead if shutdown. Testhead is 1 Take control of the testhead Testhead is * Relinquish control of the testhead Fixture Lock Lock the fixture to the testhead Fixture Unlock Unlock the fixture Get Testplan Get the "testplan" - required for PushButton Debug to function. Verify Fixture Verify fixture - same as Verify All Verify All Nodes Verify fixture - same as Verify All Nodes Verify Mux Cards Verify fixture - same as Verify Mux Cards Verify TestJet Verify fixture - same as Verify TestJet Custom Define your own macro (s).
Agilent Technologies TESTPLAN MACROS Pins Perform Pins test Preshorts Perform Pre-Shorts test Shorts Perform Shorts test Calculate Test Limits... Recalculate test limits after debug Analog Incircuit Perform the Analog Incircuit tests TestJet Perform the TestJet tests Power Supplies Setup and test the Power Supplies Digital Incircuit Perform the Digital Incircuit tests Analog Functional Perform the Analog Powered tests Digital Functional Perform the Digital Functional tests BScan Powered Shorts Perform Boundary Scan's Powered Shorts tests BScan Interconnect Perform Boundary Scan's Interconnect tests BScan Incircuit Perform Boundary Scan's Incircuit tests Unpowered Turn off the power supplies and discharge board Powered Setup to power the board Custom Create your own macro.
TEST GRADER MACROS (Not available on the MS Windows ) Generate Test Coverage Report A test coverage summary Create Grading Config Create a custom "config" for grading Create Grading Testplan Create a custom "testplan" for grading Grade Tests Grade the test
Agilent 3070 User Fundamentals QUICK REPORT MACRO (Not available on the MS Windows ) Generate Quick Report Generate two reports describing how to improve test throughput.
HELP Menu
The HELP menu provides access to help files for PushButton Debug.
sA
How these Menus apply to Fixture Verification

Agilent PushButton Debug and BT-BASIC are used together for Fixture Verification. In the PushButton Debug interface are several Verify tasks. These are used to quickly initialize the testhead and start the verification process. Having started the process, if there are problems, you will frequently move to the BT-BASIC window to work at a more detailed level. These functions only work at the testhead. These are all Board Level Debug tools: Start Agilent PushButton Debug Define the board directory being debugged Click MACROS | SETUP MACROS | TESTHEAD POWER ON This selection is only needed if the testhead has been shutdown. If the testhead is running, it is not necessary. Click MACROS | SETUP MACROS | INITIALIZE ALL This initializes the testhead and gets it ready to run any test you specify. The individual steps performed: testhead is 1 fixture lock Takes control of the testhead Lock the fixture to the testhead
get basic "testplan" Load the "testplan"
Agilent 3070 User Fundamentals Click MACROS | SETUP MACROS | VERIFY FIXTURE This starts the fixture verification process. The Verify Fixture invokes the Verify All BT-BASIC command. Many programmers will use the Verify All Nodes instead to save time. This is especially true if they have an experienced fixture vendor. Click MACROS | SETUP MACROS | VERIFY MUX CARDS If there are TestJet probes; you need to verify the multiplex card associated with the TestJet probes. Click MACROS | SETUP MACROS | VERIFY TESTJET If there are TestJet probes, you need to verify those probes.
These tools are illustrated in the following lab.
sA
How these Menus apply to Shorts & Pins

For now, you are only interested in those menu selections that initialize the testhead and test the Pins Test and the Shorts test. These functions only work at the testhead. Start with Board Level Debug tools: Start Agilent PushButton Debug Define the board directory being debugged Click MACROS | SETUP MACROS | TESTHEAD POWER ON This selection is only needed if the testhead has been shutdown. If the testhead is running, it is not necessary. Click MACROS | SETUP MACROS | INITIALIZE ALL This initializes the testhead and gets it ready to run any test you specify. The individual steps performed: testhead is 1 fixture lock Takes control of the testhead Lock the fixture to the testhead
get basic "testplan" Load the "testplan" Click MACROS | TESTPLAN MACROS | PINS This performs the Pins Test. Click MACROS | TESTPLAN MACROS | SHORTS This performs the Shorts Test.
Agilent 3070 User Fundamentals If all tests pass, you advance to the next level; that of analog incircuit tests. If a Pins or Shorts test fails, you will debug the test using a BT-BASIC window instead of the Device Level of Debug. Remember that you are testing nodes during these tests, not devices. The description of the Device Level of Debug will be delayed until the Analog Incircuit test module. Analog Incircuit and most of the other test types use the Device Level of debug. Debugging a Pins test involves testing with: No board on the fixture A blank, unpopulated board A board wrapped in aluminum foil A properly populated board
Troubleshoot: The node failed because it is isolated although it should not be isolated. Verify that the node really is or is not isolated. If it is isolated and should be isolated, change the Board Consultant description - there must be a data entry error for the software to think there is a current path. If it is isolated, but should not be, there is a fixturing problem. Check for missing probes, missing wires, miswires, probe not hitting testpad or board correctly, test probe permanently compressed, contamination on printed circuit board preventing contact, personality pin not through the Alignment Plate, etc. The node failed because it is not isolated when it should be isolated. Verify that the node really is or is not isolated. If it is not isolated and should not be isolated, change the Board Consultant description - there must be a data entry error for the software to think there is a current path. If it is not isolated, but should be isolated, there is a fixturing problem. Check for two personality pins through the same Alignment Plate funnel, miswire, probes touching (above or below Probe Plate), probe deflecting on board and bridging to another node, etc.
These debug procedures are usually done in BT-BASIC because you will use it to uncomment isolated nodes, re-comment them, etc.
Lab Preparation
sA
Lab Preparation
During the following labs, several details will be described. These need to be reviewed before you encounter them there: In PushButton Debug, you must tell the software how the vacuum is configured. There are several ways to accomplish this. The lab describes one method that you will find useful in many situations. When performing the fixture verification steps, the lab will describe a technique and have you test three or four of the nodes. It will then direct you to another method. You and your lab partner can do more than the three nodes described in the lab. But as always, remember that some experimentation is good, too much delays the class. There are two labs. Lab10A focuses on fixture verification. Lab 10B covers Pins and Shorts testing. The instructor may ask you to do both labs at one time or to perform just Lab10A and let someone else on the testhead. Returning later to do Lab10B. There are some questions following Lab10B. Please answer them before looking at the review section.
LAB 10A: Verify Fixture Wiring

This lab is done at the testhead. STEP 1: Verify the fixture. Before you can start debugging the board, confirm that the fixture is wired correctly. This only needs to be done once. 1. 2. Go to your testhead and locate an Angela Board. Set up the board for test: Make sure the Slide Switches SW3, SW4 and SW5 are in their "Normal" positions. Closed: Right side Down Make sure all the rocker Open: Left side Down switches on SW1 are set down on the right. Make sure all the rocker switches on SW2 are set down on the left. NOTE: The Slide Switches are included to simulate faults. The positions are labeled Normal, High, Low and Open. As the names imply, these positions change resistors and capacitors of correct and incorrect value into the board's circuit. When debugging those devices, you will simulate misloaded devices using these switches. NOTE: The rocker switches are included to simulate faults. Some simulate open circuits, others short nodes to ground. Each function and the reason for that function will be explained when the switch is used. 3. Install the fixture on Bank 2. If the fixture is not already loaded on the testhead. Locate a fixture and load it. Bank 2 is on the left. The labels on the fixture should be right-side-up when installed correctly. 4. Place a board on the fixture. This will be a loaded board, something you should avoid with anything larger than the Angela Board. The correct procedure would be to use a blank board, that is a board that does not have any components loaded. If the board is not already loaded, please locate one and place it on the fixture. Use the tooling pins for alignment.
Agilent Technologies 5. Start PushButton Debug. HP-UX USERS Click the 3070 icon Open a BT-BASIC window. Enter the path to your directory: /<home path>/angela_bd Start PushButton Debug: load board | debug board OR Click on the 3070 icon to pop-up the 3070 menu. Click on the file manager icon on the CDE interface. (It is on the left and looks like a filing cabinet) Navigate to the angela_bd icon in the file manager window. Drag the angela_bd icon and drop it on the Pushbutton Debug icon in the 3070 popup window NOTE: If you are at one of the Agilent training sites, the HP-UX systems use NFS mounts to connect the workstations in the classroom to the testheads. When you log onto the testhead as a user, the software automatically connects you to the workstation in the classroom. When you start a BT-BASIC window, it is automatically associated with your workstation. However, if you started PushButton Debug from the 3070 menu, it is associated with the testhead and will not easily find your files, across the network, on your workstation. MS WINDOWS USERS Start PushButton Debug by double clicking on its desktop icon. Define the path to your directory. . . NOTE: If you are at one of the Agilent training sites, MS Windows uses a Map Network Drive function to connect the workstation's disk in the classroom to the testhead controller. When you log onto a testhead you will find all the Personal Computers in the classroom mapped to the testhead controller. To access your disk drive, use the map definitions below: user1 S: user3 U: user5 W: user7 Y: user2 T user4 V: user6 X: user8 Z: <Map Letter>:/Agilent3070/home/user<#>/angela_bd EVERYONE You will see the PushButton Debug (Board Level) screen. The next step takes control of the testhead and initializes it for test. Click MACROS Click SETUP_MACROS Click INITIALIZE_ALL
Agilent 3070 User Fundamentals 6. While there is an Operator key labeled faon, the vacuum will not work now because the vacuum well definition is part of the testplan. You will not execute the testplan as part of the verification sequence; therefore, you must manually define the vacuum well. In the BT-BASIC window (the testplan is already loaded): find "vacuum well" Use the arrows to move the program up or down so the line, vacuum well a is 2,3 appears on the command line. With the line on the command line, press ENTER or F4: EXECUTE. When you issue the command to verify the fixture, the system will not turn on the fixture vacuum. Instead, you must assert the vacuum manually - before starting to verify. NOTE: Why does the system require you to turn on the vacuum manually? After all, it knows we are verifying the fixture; therefore, we must have a board on the fixture, which means we need vacuum asserted! In fact, you do not need to have a printed circuit board on the fixture for verification. Some users will verify the fixture first, without the board and others will use verify without the board during troubleshooting. 7. Turn on the vacuum In the BT-BASIC window: faon 8.
OR
Using the Operator Keypad: Click the faon button
Use the Board Graphics function to simplify the fixture verification. In the BT-Basic window: Enter board graphics
9.
Begin fixture verification In the PushButton Debug interface: Click on MACROS | SETUP_MACROS | VERIFY FIXTURE The command verify all is executed in the BT-BASIC window. This command will tell you to place the hand-held probe on a point and press the START key. When this is done, the contact between that node and the handheld probe is confirmed. If there is any extra contact detected, that is reported as a failure. If the expected contact is not found, that too is reported as a failure.
Agilent Technologies Notice that C1 pin 1 is flashing in the Board Graphics window. If you prefer, use VERIFY ALL NODES from the PushButton Debug window. This has you probe each node once instead of each probeable location. Note: Please do not neglect the fixture verification step. If you do, you may spend hours debugging a device that should take only a few minutes; all because of a fixture contact problem. There are 111 nodes on the Angela Board. Not all nodes will be verified. The prompt: 1: Probe C1.1 (22064: VCC (22063)
Place the hand-held probe on pin one of C1. Lab partner, press the Start Key. Maintain contact until you hear three quick beeps and the result is reported. 1: Probe C1.1 Node PASSES Repeat for three more device pins, the expected results are listed below 2: Probe c1.2 (21849): GND (22201) (22202) Control Card BRC (21849) was not tested. BRC (22201) Passes 1 ohms. BRC (22202) Passes 1 ohms. Short found to Digital Ground, 0 ohms. (22064: VCC (22063)
3: Probe c2.1 (22064): VCC (22063) Node PASSES. 4: Probe c2.2 (21849): GND (22201) (22202) Control Card BRC (21849) was not tested. BRC (22201) Passes 1 ohms. BRC (22202) Passes 1 ohms. Short found to Digital Ground, 0 ohms.
Press F7: AUTO START1
The Autostart feature enables a single person to verify the fixture without having to press start. It takes a little practice to get the timing correct. "It takes ear hand coordination"
Agilent 3070 User Fundamentals Place the hand-held probe on C3 pin 1. (Remove the probe as soon as you hear the three quick beeps.) 5: Probe c3.1 Node PASSES. Repeat for three more device pins, the expected results are listed below (22064): VCC (22063)
6: Probe c3.2
(21849): GND (22201) (22202) Control Card BRC (21849) was not tested. BRC (22201) Passes 1 ohms. BRC (22202) Passes 1 ohms. Short found to Digital Ground, 0 ohms. (22064): VCC (22063)
7: Probe c4.1 Node PASSES.
8: Probe c4.2
(21849): GND (22201) (22202) Control Card BRC (21849) was not tested. BRC (22201) Passes 1 ohms. BRC (22202) Passes 1 ohms. Short found to Digital Ground, 0 ohms.
Allow your lab partner to test their ear hand coordination. The ground and VCC connections appear to be good. Try some other nodes. Press F5 or click skip 1 device Until node INPUT is displayed Hint: If node INPUT was skipped press F4 or click backup pin to return to node INPUT. Probe the following device pins for more practice. 15: Probe c201.1 (22324): INPUT (22063) Node PASSES. 16: Probe c201.2 (22341): C201-2 Node PASSES. Press F8 quit verify.
Agilent Technologies 10. This is good practice, but what happens when problems arise?. Open SW1 position 2 In the BT-BASIC window, enter the command: verify from D0 (D Zero) Note: PushButton Debug only offers two verification alternatives but there are more available through BT-BASIC. 21: Probe j1.1 (22062): D0 Place the probe on J1 pin 1 and wait. There is no connection. No beeping, no nothing. Press Start 21: Probe j1.1 (22062): D0 BRC (22062) FAILED. The open switch simulated an open to the probe for node "D0" BRC [2 20 62]. What are the possible causes for the open? Pretend this is a real failure. 1 __________________________________________ 2 __________________________________________ 3 __________________________________________ 4 __________________________________________ 5 __________________________________________ How would you debug this problem? 1 __________________________________________ 2 __________________________________________ 3 __________________________________________ 4 __________________________________________ 5 __________________________________________ Press F8 quit verify Return SW1 position 2 to the closed position.
OPEN 1 2 3 4 5 6 7 8 SW1 16 15 14 13 12 11 10 9 CLOSED CLOSED CLOSED CLOSED CLOSED CLOSED CLOSED
Agilent 3070 User Fundamentals The open switch simulated an open to the probe for node "D0" BRC [2 20 62]. What are the possible causes for the open? Pretend this is a real failure. How would you debug each problem? 1 2 3 The probe on J1.1 is broken or missing. Remove the board and look at the probe for J1.1. The wire from J1.1 to the Personality pin [2 20 62] is broken or missing. Measure for continuity from the probe for J1.1 to BRC P pin [2 20 62] The P pin [2 20 62] is blocked by a foreign object. This would be found when you attempted to measure continuity to the P pin BRC [2 20 62]. The probe target on J1.1 could be covered by a foreign substance or the probe is missing the target. Look at the bottom of the board where the probe target for J1.1 is located. There could be a failure in the testhead. Run system diagnostics.
Close SW2 position 8 In the BT-BASIC window, enter the command: verify from DOUT2 (The letter O, as in OUT) 34: Probe j1.14 (22303): DOUT2 (22003) Place the probe on J1 pin 14. Press Start 34: Probe j1.14 (22303): DOUT2 (22003) BRC (22303) Passes 1 ohms. BRC (20003) Passes 1 ohms. Short found to BRC (22201), 1 ohms, node GND. Short found to BRC (22202), 1 ohms, node GND. Short found to Digital Ground, 0 ohms. The switch simulated a short from "DOUT2" to GND. What are the possible causes for the short, not caused by the switch? Focus your answer on half splitting the source of the fault. Consider all possible causes, but answer the two root causes of a real failure. 1 __________________________________________ 2 __________________________________________ Press F8 quit verify Return SW2 position 8 to the open position.
Agilent Technologies What are the possible causes for the short? Pretend this is a real failure, not caused by the switch. 1 The board has an actual short. 2 There is an extra wire from the probe or P pin for node "DOUT2" to one of the ground probes or P Pins. 11. Now try the find pins command: In the BT-BASIC window, issue the command: find pins This asks the HP 3070, Where do I have the probe? Place the probe on any test point on the board and press F1, press the foot switch or use the AUTO START function. Press F8: DONE when you are ready to end the find pins sequence. 12. Experiment with the probe command next: probe J1
Probing Device J1. Pins> 1 1111111112 1234567890 1234567890 ---------- ---------0 + *****************.... 2222222223 1234567890 ---------.......... 3333333334 1234567890 ---------.......... 4444444445 1234567890 ---------.......... T p * . Tested Probe untested Unused
Note the syntax: T for Tested p for probed (now) * for not yet tested . for unused
Place the probe on pin 1. While probing pin 1, the * turns to a p indicating probed. When the probe is removed, the p turns to a T indicating Tested. Repeat for all 16 pins of J1. If you were instructed to do Lab10A and Lab10B skip to Step 4 below, in Lab 10B.
Agilent 3070 User Fundamentals 13. Leave the testhead: Click FAOFF on the opertor widget. Click FIXTURE UNLOCK Click EXIT on the operator widget. (To the right of the RED stop Button). Notice that Push button debug, board graphics and the BT-Basic window are all exited for you. EXIT and Log off the testhead. Let another group have a chance while you review the next lab. Click Exit to Log out. NOTE! Do not leave applications open. If for example you leave Test Consultant open, the next time you login Test Consultant will reopen in the default directory not in your board's directory. Remove the Angela Board from the test fixture Remove the test fixture from the testhead. This concludes Lab 10A
LAB 10B: Debug Shorts and Pins Tests

If you cannot get on the testhead immediately, return to the Part Description Editor module and create one or more additional libraries. When you are on the testhead, remember that other members of the class are waiting. Do not spend too much time experimenting and playing. 1. Go to your testhead and locate an Angela Board. Place the Angela Board on your test fixture. Note: SW1 and SW2 are rocker switches, not slides. If you slide them, you break them Confirm switch SW1 (top switch) is closed - right side pushed down. Confirm switch SW2 (lower switch) is open - left side is pushed down. Confirm slide switches SW3, SW4 and SW5 are in their "NORMAL" positions. 2. Start PushButton Debug HP-UX USERS Click the 3070 icon Open a BT-BASIC window. Enter the path to your directory: /<home path>/angela_bd Start PushButton Debug: load board | debug board MS WINDOWS USERS Start PushButton Debug by double clicking on its desktop icon. Define the path to your directory. . . user1 S: user3 U: user5 W: user7 Y: user2 T user4 V: user6 X: user8 Z: <Map Letter>:/Agilent3070/home/user<#>/angela_bd Closed: Right side Down Open: Left side Down
Agilent 3070 User Fundamentals EVERYONE 3. Initialize your test environment Click MACROS Click SETUP MACROS Click INITIALIZE ALL 4. Test board-fixture-testhead contact Click MACRO Click TESTPLAN MACROS Click PINS No failures. If there are failures, double check the switch settings. Determine what is wrong. Do not spend more than a minute or two. If you cannot correct the problem in that amount of time, ask the instructor for help. Load the pins file, in the PushButton Debug interface: Click DEBUG | DEBUG TEST Enter pins and click OK. The pins test is loaded. All nodes on the Angela Board are listed. If there were capacitively isolated nodes, they would be shown as: !nodes "C110-1" ! Node Capacitively isolated and these nodes would not be tested during the pins test. Click EXECUTE | EXECUTE TO FAIL All pins pass. Click FAOFF on the operator keypad. Click EXECUTE | EXECUTE TO FAIL All 113 nodes on the angela_bd fail. Define when to test Pins. Remember that you can test Pins at the beginning of each test, only after a failure or not at all. In the BT-BASIC window: find "sub Set_Custom_Options" To save typing, you can use: find "sub Set_" In the Set_Custom_Options routine you will find: "Chek_Point_Mode = Failures Set the variable to match your desired test model: If you want to test board-fixture-testhead continuity at the beginning of each board test, change Failures to Pretest. If you want to turn Pins test off completely, change Failures to Off.
Agilent Technologies If you want to leave Pins test on, but only to execute when there has been a failure, leave Chek_Point_Mode set to Failures. (This is the default mode.) Back on the command line, if you made changes, execute a re-save to keep your changes. The next time you run the "testplan" it will perform the Pins test as you have defined it above. Running the "testplan" now would not make much sense as you have not yet debugged any of the tests. 5. Test / set adjustable devices. Click DEBUG DEBUG BOARD To move from device "pins" level debug to board level debug. Click MACRO Click TESTPLAN MACROS Click PRESHORTS There are no devices in the PreShorts routine, so while it appears to execute without failures, it really did nothing. You can verify this by doing a find "sub Pre_Shorts" in the BTBASIC window. However, do not skip this step! If you do and there are adjustable devices (switch, jumper or potentiometer) and one is set incorrectly, you could spend hours debugging nearby devices unnecessarily. Including this step ensures the board is in its proper state for test. If the switches used to simulate faults were included in the Board Consultant description, there would be 19 pre-shorts tests. Eight for SW1 + eight for SW2 + 3 for SW3 - SW5. The Pre-Shorts routine should end without failures.
Agilent 3070 User Fundamentals 6. Test for Shorts. Click MACRO Click TESTPLAN MACROS Click SHORTS The Shorts routine should end without failures. If there are failures, determine why and make corrections. As before, do not spend more than a few minutes isolating and correcting the problem. To clear the old pins failure information from the BT-Basic widow, press F12: CLEAR DISPLAY Set all the toggles on SW2 to all closed (short nodes to ground) Run the Shorts tests again. Click MACROS | TESTPLAN MACROS | SHORTS The failure report shows the results of a shorts test. DATE Angela Board (or your board heading) ----------------------------------------Short #1, thresh 1000, Delay 600us Ohms From: GND 22202 1 * Phantom search terminated at 1488 To: 3A 22223 2 CLOCK_ENABLE 22203 2 VCC 22063 492 DOUT2 22003 2 DO2 21522 35 DBD6 21763 2 DB6 21764 35 DD6 21703 35 D6 22023 2 Total of 10 Nodes, Message is: None. ------End, 1 Problem Reported-----------There are the actually five shorts caused by SW2. 3A CLOCK_ENABLE DOUT2 DBD6 D6 Why are so many shorts reported? The threshold for node GND is 1000, any node less than 1000 ohms to GND is considered a short. Node D6 and DD6 are separated by 33 ohms. D6 is actually shorted to GND the resistance measured between GND and node D6 is 2 ohms the resistance between D6 and DD6 is 33 ohms. Therefore GND measures 35 ohms to DD6.
Agilent Technologies The same situation applies to nodes DOUT2, DO2, DBD6 and DB6. Node VCC measures 492 ohms to GND, because of the internal path of the IC's associated with the shorted nodes and GND. What nodes would fail if node GND were moved to the low impedance section of the shorts test? Remember the low impedance threshold is 8. Circle Yes or No Would GND fail? Would 3A fail? Would CLOCK_ENABLE fail? Would VCC fail? Would DOUT2 fail? Would DO2 fail? Would DBD6 fail? Would DB6 fail? Would DD6 fail? Would D6 fail? Yes or No Yes or No Yes or No Yes or No Yes or No Yes or No Yes or No Yes or No Yes or No Yes or No
Click DEBUG Click DEBUG NEXT TEST This highlights the SHORTS test which has just failed. Click EXECUTE | EXECUTE TO FAIL Pushbutton debug is now in the device level debug mode. The test results are displayed in the BT-Basic window. The shorts test file is loaded in the PushButton Debug interface. Take a look at the shorts test. threshold 15 The expected shorts test threshold is 15ohms. Any measurement below 15ohm is a short; any value above 15ohm is an open. This is used when testing expected shorts. report phantoms Phantom shorts will be explained in detail during the development of the Class Board (the next board used in the class). Please be patient and wait for an explanation later this week. short "A" to "C" short "A" to "B" The test expects to find a short (below 15ohm) between nodes A and C; and between nodes A and B. These are associated with R6, R7 and R8, the "delta" circuit. R6 and R7 are each 10ohms. Notice that the shorts test threshold is set to 15ohms. IPG defined this setting so the two resistors would be tested as shorted.
Agilent 3070 User Fundamentals Further down the program, the threshold is reset to 1000 ohms, to test for high impedance unexpected shorts threshold 1000 settling delay 583.00u nodes "GND" settling delay 50.00u nodes "A" The default settling delay is 50useconds, but for nodes with reactive devices, IPG has recalculated the settling delay to 583.00u in this test (other boards will use different values). Even further down the program, the threshold is reset to 8 ohms, test for low impedance unexpected shorts threshold 8 nodes "C201-2" Move node "GND" to the low impedance section of the shorts test. Click EDIT | FIND STRING Enter GND in the Find String Dialog box. Click FIRST Highlight the entire line nodes "GND"
Click EDIT CUT Enter Threshold in the Find String Dialog box. Click NEXT threshold 8 Move the cursor below the threshold 8 statement Type F9 Insert line on the key board Click EDIT | PASTE threshold 8 nodes "GND" nodes "C201-2" Click FILE | SAVE Click DEBUG | COMPILE SELECTED TEST Click MARK when asked if you want to mark the test PERMANENT. Click DEBUG | SELECTED TEST Click EXECUTE | EXECUTE TO FAIL The results appear in the BT-Basic window. Do these results agree with your earlier answers?
DATE Angela Board (or your board heading) ----------------------------------------Short #1, thresh 8, Delay 50us Ohms From: GND 22202 1 To: 3A 22223 2 CLOCK_ENABLE 22203 2 DOUT2 22003 2 DBD6 21763 2 D6 22023 2 Total of 6 Nodes, Message is: None. ------End, 1 Problem Reported------------
Set SW2 back to all open /default (left side down) Click EXECUTE | EXECUTE TO FAIL The shorts test should pass. If not double check SW2. Try a more realistic short. Set SW2 position 5 to the shorted position. Click EXECUTE | EXECUTE TO FAIL The results appear in the BT-Basic window. DATE Angela Board (or your board heading) ----------------------------------------Short #1, thresh 8, Delay 50us Ohms From: GND 22202 1 TO: CLOCK_ENABLE 22203 2 Total of 2 Nodes, Message is: None. ------End, 1 Problem Reported-----------Assuming this is a real short what is the most likely cause of the short? What information does the repair operator have to isolate the fault? The node names and BRC's. Is there more information available to the operator? Change the report phantoms statement to report netlist, common devices !report phantoms report netlist, common devices Click FILE | SAVE Click DEBUG | COMPILE SELECTED TEST Click EXECUTE | EXECUTE TO FAIL The enhanced results appear in the BT-Basic window.
Agilent 3070 User Fundamentals DATE Angela Board (or your board heading) ----------------------------------------Short #1, thresh 8, Delay 50us Ohms From: GND 22202 1 c1.2 c2.2 c3.2 c4.2 c5.2 c6.2 c7.2 u1.7 u2.10 u3.10 Too many to print. TO: CLOCK_ENABLE 22203 2 r5.2 y1.1 Common Devices: y1 Total of 2 Nodes, Message is: None. ------End, 1 Problem Reported-----------Assuming this is a real short what is the most likely cause of the short? Possibly: Pin 1 of Y1 is soldered to the metal case of Y1. (The case is grounded). Set SW2 position 5 back to the open position. 7. Leave the testhead. Let another group have a chance while you review the next lab. Click FAOFF on the opertor keypad. Click MACROS | SETUP MACROS | FIXTURE UNLOCK Click EXIT on the operator widget. (To the right of the RED stop Button). Notice that Push button debug, board graphics and the BT-Basic window are all exited for you. Click EXIT to Log out. NOTE! Do not leave applications open. If for example you leave Test Consultant open, the next time you login Test Consultant will reopen in the default directory not in your board's directory. Remove the Angela Board from the test fixture Remove the test fixture from the testhead. This concludes Lab 10B.
Questions and Answers about Shorts Testing

Shorts testing on the 3070 is not perfect. Examine the circuit (below) and note that it may result in an undetectable short: A 10 ohm B 10 ohm C
threshold 16 short "A" to "B" short "B" to "C" threshold 1000 nodes "A" nodes "B" nodes "C" Which nodes are expected to be shorted?
How will the shorts test hardware be applied during the shorts test? (Assume there are other nodes on the board.)
What would happen if there were an unexpected short between nodes A and C, will the short be detected? Explain.
The test threshold is 16ohm. If it were changed, would that allow the shorts test to detect an unexpected short between A and C? Explain.
If the short were not detected during shorts test, would that present a serious problem for this board? Explain.
Briefly explain the purpose for using each of the following tools for fixture verification: test shorts
pins test
verify all nodes
verify all
verify device.pin
verify node name
find pins
probe device name"
power up board.
Agilent Technologies The following is an excerpt from the fixture/trace file. Node Name Probe Wire Path Use Path Use Node Name Probe Wire Path Use Path Use ... VCC [2 13.84 15.7] On Device c3.1 Color: Red Gauge: 28 (2 13.00 10.00) <1.5> [2 13.84 DUT Power-H (2 13.00 09.00) <1.5> [2 DUT Power-H 13.84
15.7]
15.7]
VCC [2 13.84 29.1] On Device c6.1 Color: Red Gauge: 28 (2 13.00 12.00) <3.0> [2 13.84 DUT Power Sense (2 20.00 63.00) <7.0> [2 ASRU Source Shorts Test 13.84
29.1]
29.1]
You may not be able to answer the following questions now. But read them and watch for their answers as the class progresses. What would happen if the Sense wire were missing?
What would happen if the Sense wire were mis-wired to OSC_ENABLE?
What would happen if one of the two DUT Power-H wires were missing?
What would happen if the wire for the ASRU Source / Shorts Test were missing?
Review
Look at the opens section of the shorts source for this test. Which nodes are expected to be shorted? Nodes A and B should be shorted. Nodes B and C should be shorted also. How will the shorts test hardware be applied during the shorts test? (Assume there are other nodes on the board.) Connect the source to A, B and C Connect ground to all other nodes. Test. Release node A, connect the source to nodes B and C, all other nodes to ground. Test. Release node B Connect the source to node C, all other nodes tied to ground. Test. Release node C, continue with rest of the board.
Assuming there is an unexpected short between nodes A and C, will the short be detected? Explain. NO. As explained above, the short between A and C will be masked by the source tying A,B and C together for the first test. Once this passes, A is released. This allows the short to be released and thus the short will not be detected. The test threshold is 15ohm. If it were changed, would that allow the shorts test to detect the short between A and C? Explain. If the threshold were changed to a value below either resistor's series resistance and the expected shorts from "A" to "B" and "B" to "C" were commented, then the two resistors would no longer be considered shorts. The hardware connection would not tie A, B and C together, so the short between A and C would be detected. If the short were not detected during shorts test, would that present a serious problem for this board? Explain. Assuming the two 10ohms resistors are tested during the analog in-circuit tests; then they would both fail with an approximate value of 5ohms. The repair person would hopefully notice this combination and look for a solder splash or other common failure tying the two devices together.
Agilent Technologies Briefly explain the purpose for using each of the following tools for fixture verification: test shorts Locate wiring errors. Identify probes placed at the wrong location on the PC board. pins test Indicates probe paths that are broken due to broken wire-wrap wire or a personality pin that is not wired to a probe or a socket with no probe loaded in it. verify all nodes Manually probe every node on the board and verify that there is contact to the expected location in the fixture without unexpected extra connections. verify all Manually probe every point on the board and verify that there is contact to the expected location in the fixture without unexpected extra connections. verify device.pin Manually verify that a specified devices pin is connected to the expected location. verify node name Manually verify that the specific node is connected as expected. find pins Tells you what is connected to a specific point. You need to place the manual probe on a device leg and basically ask the system what that point is connected to. probe device name Manually verifies connectivity to a device. You place the manual probe on each leg of the specified device and the system confirms that contact does or does not exist. This does not verify that the contact goes to the correct location, just that there is current flow. power up board. Check the voltage of the power supply. If it is fluctuating, then look for a mis-wired sense wire.
Agilent 3070 User Fundamentals Regarding the fixture/trace file: What would happen if the Sense wire were missing? The power supply would not be able to regulate Vcc at 5.0 volts and the supply would generate an overvoltage error. What would happen if the Sense wire were mis-wired to OSC_ENABLE? The pullup would produce a voltage of just below 5.0volt (voltage drop through the 1K) so VCC will be regulated at slightly more than 5.0 volts. What would happen if one of the two DUT Power-H wires were missing? The Angela Board, drawing only about 150mA, does not need two wires for Vcc. Therefore, there would be very little difference in test performance without this wire. If the wire were mis-wired to another node, it could damage devices on that node. On another board, omitting a power wire could cause that power node to fluctuate due to limited current availablity through the one remaining wire. (It could melt the one remaining wire in a worst case situation.) What would happen if the wire for the ASRU Source / Shorts Test were missing? 1) Shorts would never fail with a shorted Vcc node because without the wire, it would not test Vcc for shorts. 2) The Pins test would fail because the same wire is used in that test. It would fail because there would be no current flow through that same wire. 3) Fixture verification tests would fail. 4) Any analog incircuit test using the ASRU source via this wire, would fail because the source would never reach the circuit being tested. 5) If the board were powered, bad things COULD happen.

Module 10 Shorts &amp Pins Push Button Debug

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 10 Shorts &amp Pins Push Button Debug

Uploaded by

Copyright:

Available Formats

Agilent 3070 User Fundamentals

Module 10: PushButton Debug for Shorts & Pins Tests

PushButton Debug for Pins & Shorts 10 - 1

Test Development Flow chart

Translate CAD Describe board & system

board_xy config Custom libraries

testability.rpt Fixture Files Individual Test Files testplan

3070 User Fundamentals Module 10: Shorts & Pins Debug

The Test Development Process

PushButton Debug for Pins & Shorts 10 - 2

Agilent 3070 User Fundamentals

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

Agilent PushButton Debug

PushButton Debug for Pins & Shorts 10 - 3

Start Agilent PushButton Debug

PushButton Debug for Pins & Shorts 10 - 4

Agilent 3070 User Fundamentals

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

The PushButton Debug interface offers two levels of debug

Board Level Debug

PushButton Debug for Pins & Shorts 10 - 5

PushButton Debug for Pins & Shorts 10 - 6

Agilent 3070 User Fundamentals

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

Device Level Debug

PushButton Debug for Pins & Shorts 10 - 7

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

PushButton Debug's Pulldown Menus

PushButton Debug for Pins & Shorts 10 - 8

PushButton Debug for Pins & Shorts 10 - 9

The MACROS Menu

PushButton Debug for Pins & Shorts 10 - 10

PushButton Debug for Pins & Shorts 10 - 11

PushButton Debug for Pins & Shorts 10 - 12

PushButton Debug for Pins & Shorts 10 - 13

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

How these Menus apply to Fixture Verification

get basic "testplan" Load the "testplan"

PushButton Debug for Pins & Shorts 10 - 14

These tools are illustrated in the following lab.

PushButton Debug for Pins & Shorts 10 - 15

Agilent PushButton Debug

3070 User Fundamentals Module 10: Shorts & Pins Debug

How these Menus apply to Shorts & Pins

PushButton Debug for Pins & Shorts 10 - 16

PushButton Debug for Pins & Shorts 10 - 17

3070 User Fundamentals Module 10: Shorts & Pins Debug

PushButton Debug for Pins & Shorts 10 - 18

Agilent 3070 User Fundamentals

LAB 10A: Verify Fixture Wiring

PushButton Debug for Pins & Shorts 10 - 19

PushButton Debug for Pins & Shorts 10 - 20

Using the Operator Keypad: Click the faon button

PushButton Debug for Pins & Shorts 10 - 21

Press F7: AUTO START1

PushButton Debug for Pins & Shorts 10 - 22

7: Probe c4.1 Node PASSES.

PushButton Debug for Pins & Shorts 10 - 23