Ppii Tutorial Manual

Tutorial Manual for the
PinPoint Series Test Systems
The PinPoint Series
TestVue32™ Operating Environment
Pin-TuT-0801
Edition 3.20
Issue 1.5 Jan 2012

ii
 Copyright 2001 - 2012 rights reserved
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or
transmitted, in any form by means of electronic, mechanical, photocopying, recording or otherwise,
without the prior written permission of Diagnosys. No patent liability is assumed with respect to the use
of the information contained herein. Neither is any liability assumed for damages resulting from the
use of the information contained herein.
Neither Diagnosys not its affiliates shall be liable to the purchaser of this equipment or third parties for
damages, losses, costs or expenses incurred by the purchaser or third parties as a result of: accident,
misuse or abuse of this equipment or unauthorized modifications, repairs or alterations to this
equipment.
General Notice
Other product names that are used herein are for identification purposes only and may be trademarks
of their respective companies.
Diagnosys Test Systems Limited • Systems House • Bedford Road • Petersfield

Hampshire • GU32 3QH • United Kingdom
Telephone: +44 (0) 1730 260699 • Facsimile: +44 (0) 1730 260659
Diagnosys Systems Inc. • 5 Lan Drive, 1st Floor • Westford

Massachusetts • 01886 • USA
Telephone: +1 800 788 6219 (Toll Free); + 1 978 392 0406 • Facsimile: +1 978 392 3622
email: [email protected]
www.Diagnosys.com
Document Pin-Tut-0801
Issue 1.5
iii
Contents
1 SYSTEM FAMILIARISATION .............................................................................. 7

1.1 About this Tutorial ................................................................................................................................... 8
1.1.1 How to Use this Tutorial ........................................................................................................................ 8
1.2 Login .......................................................................................................................................................... 9
1.3 Task Bar .................................................................................................................................................. 10
1.4 Supervisor Utilities ................................................................................................................................. 13
1.5 User Utilities............................................................................................................................................ 15
1.5.1 Self Tests.............................................................................................................................................. 15
1.5.2 Password .............................................................................................................................................. 20
1.6 Theory and Overviews ........................................................................................................................... 21
1.6.1 Program Studio .................................................................................................................................... 21
1.6.2 Board Test ............................................................................................................................................ 23
1.7 Program Studio ...................................................................................................................................... 25
2 INSTRUMENT MODES ...................................................................................... 27
2.1 Device Test Mode ................................................................................................................................... 29
2.1.1 Device Test .......................................................................................................................................... 30
2.1.2 Device ID ............................................................................................................................................. 33
2.2 VI Instrument Mode .............................................................................................................................. 36
2.2.1 Multiplexer / Scanner ........................................................................................................................... 42
2.2.2 Pulse Mode .......................................................................................................................................... 44
2.3 Analog Instrument Mode Overview ..................................................................................................... 45
2.3.1 Analog Instrument ............................................................................................................................... 48
3 DEFINE BOARD ................................................................................................ 61
3.1 Board Programming .............................................................................................................................. 62
3.2 Define Board ........................................................................................................................................... 63
3.3 Board Size ............................................................................................................................................... 65
3.4 Adding Devices ....................................................................................................................................... 67
3.5 Passive Wizard........................................................................................................................................ 70
3.6 Package Wizard ...................................................................................................................................... 72
3.7 Dummy Devices ...................................................................................................................................... 74
3.8 Adding Text ............................................................................................................................................ 75
3.9 File Save .................................................................................................................................................. 75
3.10 Bit Map Files ........................................................................................................................................... 76
4 PROGRAM BOARD ........................................................................................... 79
4.1 Program Board ....................................................................................................................................... 80
4.2 VI and Functional................................................................................................................................... 89
4.3 Operator Messages ................................................................................................................................. 92
4.4 TestFlow Summary ................................................................................................................................ 94
4.5 TestFlow Exercise ................................................................................................................................... 97
4.6 Analog Testing ...................................................................................................................................... 101
4.7 Board Properties .................................................................................................................................. 107
4.8 Simulated Test Mode............................................................................................................................ 108
4.9 NetList Generator ................................................................................................................................ 110
4.10 Schematic Generation .......................................................................................................................... 114
Issue 1.5
iv
5 LIBRARIES ...................................................................................................... 118

5.1 Library Summary ................................................................................................................................ 119
5.2 Device Library Editor .......................................................................................................................... 123
5.2.1 Data Sheets............................................................................................................................................. 125
5.3 Package Library Editor ....................................................................................................................... 126
5.4 Symbol Library Editor ........................................................................................................................ 130
5.5 Test Clip Editor .................................................................................................................................... 134
5.6 Functional Library Editor ................................................................................................................... 136
6 TEST BOARD .................................................................................................. 140
6.1 Test Board ............................................................................................................................................. 141
7 CONCLUSION .................................................................................................. 144
7.1 Conclusion ............................................................................................................................................. 145
Issue 1.5
v
List of Figures
Figure 1.1 PinPoint Login Dialog Box ..................................................................................................9
Figure 1.2 PinPoint Task Selector .......................................................................................................10
Figure 1.3 PinPoint Task Bar...............................................................................................................11
Figure 1.4 User Utilities Menu Task Bar ..............................................................................................15
Figure 1.5 RED Loopback Plug. ..........................................................................................................15
Figure 1.6 YELLOW Loopback Plug. ..................................................................................................16
Figure 1.7 Power Loopback Plug. ........................................................................................................18
Figure 1.8 Digital Loopback Plug.........................................................................................................19
Figure 2.1 Resistor R17 - 1k (15V test signal) ....................................................................................37
Figure 2.2 Diode D6 (5V test signal)...................................................................................................38
Figure 2.3 Opto Coupler – Pulse Mode ...............................................................................................44
Figure 2.4 DMM Instrument Mode Select Dial ....................................................................................49
Figure 3.1 Setup Grid / Units of Measurement .....................................................................................64
Figure 3.2 Add Board Outline Dialog Box ..........................................................................................65
Figure 3.3 Add Device Dialog Box .....................................................................................................67
Figure 3.4 Select Package Description..................................................................................................68
Figure 3.5 Passive Wizard Dialog Box ................................................................................................70
Figure 3.6 Add Device – Bit Map Mode...............................................................................................77
Figure 3.7 Add Pin Identifier ................................................................................................................77
Figure 4.1 Options Menu......................................................................................................................80
Figure 4.2 Edit Device Dialog Box ......................................................................................................83
Figure 4.3 Select SeaWave Menu .........................................................................................................85
Figure 4.4 Add Guards Dialog Box......................................................................................................86
Figure 4.5 Device Settings – Voltage Pull-up Termination ...................................................................87
Figure 4.6 Edit Device Dialog Box – View VI Signatures ....................................................................90
Figure 4.7 Edit Device Dialog Box – Probe Underside .........................................................................90
Figure 4.8 Board Pre-Text Menu ..........................................................................................................92
Figure 4.9 Device Pre-Text Menu ........................................................................................................93
Figure 4.10 TestFlow Graphics ..........................................................................................................95
Figure 4.11 Flow Chart Elements .......................................................................................................96
Figure 4.12 Analog Flow Chart Elements.........................................................................................101
Figure 4.13 Analog Flow Example ...................................................................................................104
Figure 4.14 TestFlow Manager ........................................................................................................105
Figure 4.15 Export Subroutine .........................................................................................................106
Figure 4.16 NetList Generator Options Menu...................................................................................110
Figure 4.17 NetList Generator Utilities Menu ..................................................................................110
Figure 4.18 Schematic Save / Restore ..............................................................................................117
Figure 5.1 Close Tiles ........................................................................................................................122
Figure 5.2 Opening Device Library ....................................................................................................123
Figure 5.3 Add Datasheet ...................................................................................................................125
Figure 5.4 Opening Package Library .................................................................................................126
Figure 5.5 Package Command Window - Help...................................................................................126
Issue 1.5
vi
Figure 5.6 Place Pin Properties Menu ................................................................................................127

Figure 5.7 Opening Symbol Library ...................................................................................................130
Figure 5.8 Test Clip Editor – New Clip ..............................................................................................134
Figure 5.9 Add Device Menu .............................................................................................................138
Figure 5.10 Re-Fetch Device Dialog Box .........................................................................................139
Issue 1.5
7
CHAPTER 1
1 System Familiarisation
Contents
1.1 About this Tutorial ................................................................................................................................... 8

1.1.1 How to Use this Tutorial ........................................................................................................................ 8
1.2 Login .......................................................................................................................................................... 9
1.3 Task Bar .................................................................................................................................................. 10
1.4 Supervisor Utilities ................................................................................................................................. 13
1.5 User Utilities............................................................................................................................................ 15
1.5.1 Self Tests.............................................................................................................................................. 15
1.5.2 Password .............................................................................................................................................. 20
1.6 Theory and Overviews ........................................................................................................................... 21
1.6.1 Program Studio .................................................................................................................................... 21
1.6.2 Board Test ............................................................................................................................................ 23
1.7 Program Studio ...................................................................................................................................... 25
Chapter 1 System Familiarisation 8
1.1 Abou t th is Tu to r ia l
The purpose of this Tutorial is to provide the new user with the basic knowledge of
how to use the system, and in particular on how to generate and test Board
Programs. It is NOT intended to provide the new user with ALL the details of how
to generate Board Programs, but just to provide the basics. More details of using
the system are provided by Diagnosys in the Standard and Advanced User Training
Courses.
New users should complete this tutorial before attempting to generate their own
programs and it is a pre-requisite of the Diagnosys Standard Training Course that
this Tutorial is completed prior to attending the course.
Contact Diagnosys Sales Department for details on the Standard and Advanced
Training Courses.
1.1.1 How to Use this Tutorial

The PinPoint Tutorial consists of both “On-Line” Help type and this written
document that can be used in conjunction with the ”On-Line” Help.
The “On-Line” Tutorial is broken down into Main Topics, or "Browse Sequences",
and Sub Topics. It is possible to go from one topic to the next, when the topic is
completed, by selecting the button at the bottom of each topic page, or

by selecting the >> symbol at the top of the Help Screen. It is also possible to Jump
to the Next Main Topic by selecting the button, or return to the
Contents Page at any time by selecting the button.
In this Tutorial we will follow the process of generating a comprehensive Board

Test Program, using the supplied Tutorial Board as an example.
To "toggle" between this Tutorial Help and the current window of the PinPoint
Software use the keyboard combination "Alt + Tab".
Alternatively you can print out the "PP II Tutorial Manual.DOC File (Word document
located in the PinPoint / Bin Directory)
Whenever you are requested to select a function, use the mouse to locate the
required function and then click with the "Left Mouse Button" to activate the
required function.
Issue 1.5
1.2 Log in
Before you can use the system you must Login to the PinPoint Software.
From the PinPoint Login screen (Figure 1.1):
Figure 1.1 PinPoint Login Dialog Box
Using the Mouse Pointer and left button, first select SUPERVISOR from the
USER-NAME drop down list box, and then select the PASSWORD box and type
TESTVUE (not case-sensitive).
This Login sequence will provide the user with access to all of the PinPoint
functions.
Once the user has logged in, the PinPoint will automatically perform a series of
system Self-Tests - wait for these tests to complete before proceeding.
If any of the tests fail contact Diagnosys Applications Department for assistance.
Issue 1.5
1.3 T a sk Bar
Select from the following "radio buttons" the required function and press OK
Alternatively press the Cancel Button to launch PinPoint from the taskbar.
Figure 1.2 PinPoint Task Selector
Start Program Studio ?

Selecting this "radio button" takes you directly to the PinPoint Program
Studio Application.
Start Test Board ?

Selecting this "radio button" takes you directly to the PinPoint Test Board
Application.
Launch the Tutorial ?

Selecting this "radio button" takes you directly to the appropriate PinPoint
Tutorial Program.
Start the PinPoint (TestVue) taskbar ?

Selecting this "radio button" takes you directly to the PinPoint Taskbar
situated at the lower right of the screen.
The PinPoint Task Bar or is situated in one of two possible

locations, dependent upon the Customise Settings. By default when the system is
supplied the PinPoint Task Bar will be located at the Bottom Right hand side of the
Screen, compliant with a standard Windows (tm) format.
It is strongly recommended that new users DO NOT modify these Customise

Settings.
Issue 1.5
The PinPoint Task Bar (see Figure 1.3) consists of 9 Sections:-
Figure 1.3 PinPoint Task Bar
Test Board
Allows Testing of Boards that have been Programmed using the Program
Studio Application.
Program Studio
Provides ALL the necessary "Tools" for generating a Program for Testing
Boards.
Accessories
Provides access to the main system Options and Accessories.
Contact Diagnosys Sales Department for information on any of these

Accessories.
Windows
Provides access to the main Windows functions, such as Program Manager,

File Manager etc.
Utilities
Provides access to the PinPoint Self Tests and User Password controls.
Supervisor Utilities
Provides access to Operator Controls, Customisation of PinPoint Settings and

Library Program Maintenance.
Issue 1.5
MS DOS Prompt
Exits to MS DOS Prompt.
Help
Access to the PinPoint Help and Tutorial Help.
Exit
Exit from the PinPoint Operating Software. Also allows login as a different
user.
Issue 1.5
1.4 Sup erv isor U tilities

Having logged in as the Supervisor you have access to ALL of the PinPoint's
functions. You also have the ability to define restrictive controls for other Users. In
this part of the Tutorial we will Add a New user to the system, and ensure that
correct controls are applied to that user. We will also browse through the Hardware
and Customise settings.
Add User
To add a New User to the System select the Supervisor Utilities Menu from the
PinPoint Task Bar and then select Add User
1) Type in the name of your New User and OK
2) Account Restriction.
Leave the default settings as they are. This ensures that the New User has a Unique
Password, and allows him to change this Password as required.
The Account Disable check box will "hide" the New User's name from the Login
Dialog box - for example when the user in away on holiday etc.

The Supervisor has the ability to
change ALL Passwords as required
3) Trustee Assignments
This allows you to select which of the PinPoint's features that you want the New
User to be able to access. For example, if the New User is simply a Test Operator,
you will want to restrict him to features such as Testing, but restrict him from
making any changes to the software, or Programming.
We will assume that the New User is a Test Operator, and therefore ONLY enable
the Testing functions. Ensure that ONLY the Device Test, Test Board and System
Diagnostics are enabled (ticked) before selecting OK. This will allow the New
User to test ONLY Devices, Boards and the PinPoint system itself.
4) Change Password.
Enter the required Password for the New User. You will be required to enter this
twice in order to verify the correct typing.
Issue 1.5
Additional Features
1) Customise
Select the Customise Menu and review it. Refer to the On Line Help if required
BUT DO NOT MAKE ANY CHANGES. Once you have finished Browsing
CANCEL from the dialog box.
2) Library Maintenance
Select the Library Maintenance Menu and review it. This is used primarily to
update the PinPoint Libraries from an external source eg remote programming
station. Refer to the On Line Help if required. Once you have finished CANCEL
from the dialog box
3) Diagnostics
Select the Diagnostics Menu and review the Diagnostics. Press Function Key F1 to
access the PinPoint Maintenance Manual.
Select File Menu > Exit to exit from the Diagnostics.
Issue 1.5
1.5 U ser U tilitie s

Select the Utilities Menu from the PinPoint Task Bar (see Figure 1.4).
Figure 1.4 User Utilities Menu Task Bar
From this Menu we will perform a series of Self Tests and show you how to
Change the Supervisor's Password if required.
1.5.1 Self Tests

Select Self Tests from the Utilities Menu and perform ALL the listed Tests.
If ANY Test Fails Contact Diagnosys Applications Department for assistance.
There are eight topics to complete a System Self Test. Items 1 to 3 inclusive are
performed whenever anyone logs onto the system.
Item 4 (Driver Loopback Test) requires a "RED Loopback Plug" to perform the test
and as this is NOT performed during Login it is recommended that you perform the
test regularly, say once a week, or if a system problem is suspected.
Figure 1.5 RED Loopback Plug.
Item 5 (Scanner Test) is applicable for those systems with an In Circuit Driver Card
(with integrated Multiplexer), Matrix (or Scanner cards) and is performed on Login if
appropriate.
Item 6 (Scanner Loopback Test) is only applicable for those systems fitted with the In
Circuit Driver Card (with integrated Multiplexer), Matrix (or Scanner cards). This test
requires a YELLOW Scanner loopback plug to perform the test and as this is not
performed after login it is recommended that the test be performed regularly, say
weekly, or if a system problem is suspected.
Issue 1.5
Figure 1.6 YELLOW Loopback Plug.
Item 7 (Power Loopback Test) is only applicable for systems licensed with the
NetGen option. This test requires a special power loopback plug assembly to perform
the test. (See Figure 1.7 below)
Item 8 (Digital Loopback Test) is only applicable for those systems fitted with the
Digital Edge Driver Board.
This test is not performed at login and therefore needs to be performed periodically
(say weekly). This test ensures that the Digital edge-board drivers and receivers are
operating correctly.
The 8 Self Tests are:-
VECTOR RAM TEST
This tests the RISC Processor RAM located on the Controller Board
Select Vector RAM Test using Mouse Pointer and "click" with the Left
Button.
Select GO (or CANCEL if not required). The Ram Test will execute until
STOP is selected. (The current cycle of RAM test will be completed). The
Pass / Fail Status is shown in TEST COUNT / PASSED / FAILED Columns.
Select CANCEL to return to Utilities Menu.
DRIVER RAM TEST
This tests the Driver / Sensor RAM located on each of the Driver Boards
Select Driver RAM Test using Mouse Pointer and "click" with the Left
Button.
Select GO (or CANCEL if not required). The Ram Test will execute until
STOP is selected. (The current cycle of RAM test will be completed). The
Pass / Fail Status is shown in TEST COUNT / PASSED / FAILED Columns.
Issue 1.5
LINE TERMINATION TEST
This tests the Termination biases (Pull up, Pull down, Tri State and Contacts)
on the Driver Boards
Select Line Termination Test using Mouse Pointer and "click" with the Left
Button.
Remove any Test Clips or Guard leads connected to a DUT before selecting
GO (or CANCEL if not required). The Line Termination Test will execute
until STOP is selected. (The current cycle of Line Termination Test will be
completed). The Pass / Fail Status is shown in the TEST COUNT / PASSED /
FAILED Columns. Failed Pins are shown in the box below the TEST
COUNT Column. To view the failed pins "click" with the Left Button in the
box and scroll up/down using the keyboard scroll arrows.

If the system fails the LINE
TERMINATION TEST it is
possible for the System to cause
damage to a device with this
faulty Driver / Sensor Channel.
Contact Diagnosys Service Department if a failure is detected.
DRIVER LOOPBACK TEST
This tests the integrity of cabling to the system front panel as well as the
Driver Source / Sink currents.

1) USE THE "RED" LOOP BACK TEST POD FOR
DRIVER LOOPBACK TEST.
2) USE THE "YELLOW" LOOP BACK TEST POD
FOR SCANNER LOOPBACK TEST.
There are two options for LOOP BACK TEST.
a) TEST ALL
Select TEST ALL using Mouse Pointer and "click" with the Left Button. Place
the appropriate LOOP BACK TEST CONNECTOR (RED for Driver / Sensor
Loop Back and YELLOW for Scanner Loop Back option) in each TEST CLIP
position on the Front Panel as instructed for the appropriate configuration of
the System. The Pass / Fail Status is shown in TEST STATUS / RESULTS
Box. To view the failed pins "click" with the Left Button in the box and scroll
up/down using the keyboard scroll arrows.
Issue 1.5
b) INDIVIDUAL CARDS
Select the appropriate Card / Test Clip for testing by moving the Mouse Pointer
to the required Test Clip box and "click" with the Left Button. Place the
appropriate LOOP BACK TEST CONNECTOR (RED for Driver / Sensor
Loop Back and YELLOW for Schematic Loop Back option) in the appropriate
TEST CLIP on the Front Panel. Once the test has been completed the Test Clip
Box will be filled with an X. The Pass / Fail Status is shown in TEST STATUS
/ RESULTS Box. To view the failed pins "click" with the Left Button in the
box and scroll up/down using the keyboard scroll arrows.
SCANNER TEST
If the Integrated Scanners / Matrix cards are fitted to the system they will
require periodic testing.
This tests the integrity of the Scanner relays as well as communication to the
Controller Board
Select Scanner Test using Mouse Pointer and "click" with the Left Button.
Select GO (or CANCEL if not required). The Scanner Test will execute until
STOP is selected. (The current cycle of the Scanner Test will be completed).
The Pass / Fail Status is shown in TEST COUNT / PASSED / FAILED
Columns.
SCANNER LOOPBACK TEST
This test ensures that the Controller resistance measurement system is

operating correctly and is capable of being routed through the matrix /
multiplexer channels
For operation see Driver Loopback Test Above
POWER LOOPBACK TEST
Tests the integrity of the Schematic Power connections as well as the

operation of the Strike Probe
Connect the Power Loopback Pod assembly between Test Clip position "A"
and the appropriate positions on the Power Nets sockets on the Front Panel.
Connect the Red and Blue leads to Guard 8 and Guard 7 respectively
Figure 1.7 Power Loopback Plug.
Issue 1.5
Select TEST (or CANCEL if not required). Once the appropriate connections
have been made press the ESC (or any other key) to start the test process. Any
faults that occur will be listed in the White message box area.
Select CANCEL to return to the Utilities Menu.
DIGITAL LOOPBACK TEST
Figure 1.8 Digital Loopback Plug.
This tests the integrity of cabling to the system front panel

Only available if any optional
Digital Driver Boards are fitted.
Issue 1.5
1.5.2 Password
As the current User is the Supervisor, the Password we are about to change is the
Supervisor's.
Select Change Password and type in the new required Password for the Supervisor. It
is recommended that at this stage you keep the Password the same - type in the current
Password TESTVUE.
Select OK and re-type TESTVUE.
Select OK to change the current user's Password.

If we Login as a different User (e.g. New
User) the Password we will change is the
New User's.
Issue 1.5
1.6 Th eor y and Ov erv iews

1.6.1 Program Studio
The Program Studio is used to generate and store a board program. It should be
used in conjunction with the FUNCTIONAL Library Application to verify the
functional programs.
The main uses of the Program Studio are as follows:-
a) Generate the Board Layout and fetch the required devices from the appropriate
PinPoint Device Library.
b) Generate, if required, new Graphics Outlines for Device Packages not currently
in the PinPoint Device Library.
c) Create and verify Functional, Parametric and VI tests for individual Integrated
Circuits.
d) Create and modify Execution Order of testing the devices.
e) Create and modify Operator Help Messages.
BOARD PROGRAMMING
Board Programming consists of four basic functions / applications:-
DEFINE BOARD
Defines the Board Layout and fetches the Devices to be tested from
the appropriate PinPoint Library.
PACKAGE EDITOR
Is used to create new Graphics Outlines for device packages not

currently in the PinPoint Package Library.
PROGRAM BOARD
Configures the individual Devices on the Board according to the

specific In-Circuit conditions for that Device, and verifies that each
device being tested returns consistent results.
TESTFLOW
The TESTFLOW is the sequence that the test operator will be guided
through when in the TEST BOARD Mode of operation.
Issue 1.5
Each of the above applications are described in more detail in the relevant sections
of this Tutorial.
Associated with each of the above applications are a set of Menu Commands and a
set of Mode Control Command Icons
MENU COMMANDS
To select one of the Menu Commands position the mouse pointer over the
required Command and "click" - further sub-menu commands will appear
below the main Menu Command. Some of the Menu Commands are specific
to one application only whereas others are general and relate to more than one
application.
MODE CONTROL ICONS
The Mode Control Command Icons are situated beneath the Menu
Commands. Most of the Icons are a duplication of the Menu Commands and
are therefore described under the Menu Command topics. There are however
a few which are not duplicated and are therefore described under the
respective Mode Control Command topic.
Issue 1.5
1.6.2 Board Test

Board Test is used to TEST a faulty board once the Program has been completed.
Board Test allows the operator to record Test Result History of the board for
future reference.
When a board program is first loaded the Graphic Display of the board is displayed
together with the Select Function Dialog Box.
There are two Modes of Test and two options within each Mode:-
a) Auto Test
Guides the operator along the programmed Execution Order of Test as defined
by the Programmer. Logging of Failures and Historical Data is enabled in this
mode of operation.
b) Component Test
Allows the operator to select any device to test by a simple "point and click" of
the mouse. No logging of Failures or Historical Data is performed in this mode
of operation.
i) Functional Test
As the name implies Functional Test carries out a functional test (and Clip
Verify, Opens, Voltage, Shorts VI etc.) on the selected board. A Functional
Test may be performed on the entire board or on a single component
ii) TrakTest (Optional)
TrakTest is only available if the Board Program File contains a Net Listing of
the device interconnections. There are two basic modes of operation
selectable by the check box situated in the lower left of the TrakTest Selection
Box.
a) Full TrakTest
A Full TrakTest performs a test for both Short Circuits and Open Circuits
on the Board. To perform this task two test clips are used; one to clip over
the Device from which Opens and Short Circuits are to be detected and
the second clip to clip over ALL remaining devices in turn. This
technique detects all connections between the Source Device and all other
devices on the Board from which the PinPoint is capable of determining
Open Tracks and / or Short Circuits.
b) Open TrakTest
An Open TrakTest is similar to the Full TrakTest but is designed to detect

only open Circuit tracks (the large majority of track failures are Open
Circuit). To achieve this, the "Source Clip" is placed over the device from
which Opens are to be detected and the "Destination Clip" is connected to
ONLY the devices that have known connections to the "Source"
Issue 1.5
A Full or Open TrakTest may be performed on the entire board or on a single

component

1) Connect Power to the board using
the Power Nets Sockets rather
than the UUT Power Connector
when performing a TrakTest
2) The Values of the "Set
Resistance" saved within the
NetGen application are used
when performing a TrakTest
The following paragraphs explain the function of each area within the Graphics
Display Area.
1) The GREY BAR at the top of the screen shows the current Test Function
selected and also Instructions to be carried out by the operator.
2) The LEFT GREY BOX represents the Front Panel of the test system.
Also associated with Test Board are a number of "Push Buttons" situated
directly beneath the VI Probes. These "Push Buttons" select functions such as
End Test, Go to Previous Device etc.
3) The LOWER LEFT GREY BOX with a green shows a representation of the
board area for programming. This box is used to display the "Birds Eye View"
for ZOOM IN / OUT of the board area. When the system is "Zoomed In" on a
device a Red rectangle displays the position of the device in relation to the
entire board.
Issue 1.5
1.7 P rogra m S tud io

Program Studio is the PinPoint software application used to generate Board
Programs, Test Devices and control the PinPoint Libraries.
The Program Studio application consists of a number of sub-applications,

dependent upon the system configuration. These Program Studio sub-applications
are displayed as "Tabs" at the bottom of the screen.
The Program Studio applications consist of:-
1) Device Test Mode
2) VI Instrument (Optional)
3) Define Board
4) Program Board
5) NetGen
6) Schematic (Optional)
7) Libraries
Device Test Mode
Device Test Mode consists of two functions:-
1) Device Test Mode
The Device Test Mode is designed to allow you to test devices either on a
board or out-of-circuit without having to Program a Board using the Program
Studio.
2) Device Identifier
The Device Identifier Mode is used to identify devices where the marking on
the device has been removed - this is often done by in an attempt to prevent
"pirating" or copying of propriety information. However, when repairing these
types of boards, device part numbers are essential.
VI Instrument
The function of the VI system is to apply a controlled alternating voltage (usually a

Sine Wave) into a circuit node and to display, and record if required, the Voltage
and Current responses in a variety of formats.
Define Board
The prime purpose of the DEFINE BOARD Editor is to produce a graphical layout
of the Board as an aid to "Board Test" by persons unfamiliar with the Board or the
PinPoint Test System. In placing the components on the graphical layout the
Device Circuit Reference, Part Number, Package Style and Location / Orientation
of each device is specified and loaded.
Issue 1.5
Program Board
The function of PROGRAM BOARD is to generate test programs for each of the
devices generated using the DEFINE BOARD and LIBRARY PACKAGE Editors.
These test programs can consist of Functional, VI and Parametric Tests.
If a device contains Functional data it may be necessary to view, modify or correct

the program utilising the FUNCTIONAL LIBRARIES.
The functions required whilst programming a board are dependent upon the type of
device, the in-circuit conditions and whether the device program is resident within
the PinPoint Device Libraries.
NetGen (Optional)
NetList Generator (NetGen) is the process in which a Board Net List is created and
added into the Program Database by learning the connectivity between devices. A
net between two devices is "CAPTURED" by simultaneously clipping over each
device with a test clip and performing a Connectivity / Resistance Test between
these two clips. This test is performed with no UUT Power being applied to the
board.
Schematic (Optional)
Once the device interconnections have been learnt, these interconnections together
with the Graphic symbols derived from the PinPoint Libraries can easily be
displayed as a circuit diagram.
Libraries
The Libraries application is used primarily to generate, modify or test Device

Functional Programs and ancillaries such as Symbols, Test Clip and Device
Package data. Associated with this Section is a set of COMPILER COMMANDS.
The Libraries Application should be used in conjunction with the PROGRAM

BOARD Application when editing or verifying a functional device whilst
generating a Board Program.
Issue 1.5
27
CHAPTER 2
2 Instrument Modes
Contents
2.1 Device Test Mode.................................................................................................................................... 29

2.1.1 Device Test .......................................................................................................................................... 30
2.1.2 Device ID ............................................................................................................................................. 33
2.2 VI Instrument Mode .............................................................................................................................. 36
2.2.1 Multiplexer / Scanner ........................................................................................................................... 42
2.2.2 Pulse Mode .......................................................................................................................................... 44
2.3 Analog Instrument Mode Overview ..................................................................................................... 45
2.3.1 Analog Instrument ............................................................................................................................... 48
Chapter 2 Instrument Modes 28
The PinPoint currently has 3 separate Instrument Modes.
Device Test
VI Instrument
Analog Instrument (Optional with Analog sub - system)
The Instrument Modes allow the user to utilise the respective functions almost as
though they are simple "Bench-top Instruments". This means that there is virtually
NO saving to disk of any of the functions used.
The Instrument Modes can be very useful in understanding more about the
functions available of the respective apparatus, and can be useful in a "quick"
verification, or determination, of a problem.
It is not recommended to use these facilities to test an entire board, as

information displayed is not recorded for future use.
Issue 1.5
2.1 D ev ic e Te s t Mod e
Device Test Mode consists of two primary applications
1) Device Test
The Device Test Mode is designed to allow you to test devices either on a
board or out-of-circuit without having to Program a board using the Program
Studio.
It is not recommended to use this facility to test a complete board as

information displayed is not recorded for future use - it is only really designed
to allow you to test devices "Out-of-Circuit" or to test / retest devices that have
been replaced after being diagnosed as faulty by the Test Board application.
2) Device ID
The Device Identifier Mode is used to identify devices where the marking on
the device has been removed - this is often done by manufacturers in an
attempt to prevent "pirating", or copying of propriety information. However,
when repairing these types of boards, device part numbers are essential. The
Device Identifier Mode first determines the "Device Shorting Algorithm"
(Power Supply connections and other external shorts about the device) and
then selects suitable Functional Programs from the PinPoint Library to test the
"unknown" device in an attempt to identify its "functionality".
Issue 1.5
2.1.1 Device Test

Locate the Tutorial Board and its associated Power Supply lead from the supplied
items.
Connect either the Tutorial Power Lead (if supplied) or individual Power Supply
easy-hooks to the Tutorial Board and also to the PinPoint front panel Power Supply
Connectors.
TP1 0 Volts Black
TP2 +5 Volts Red
TP3 -12 Volts Green
TP4 +12 Volts Yellow
Ensure that the switches S1 are set as follows:-
Position 1 Open
Position 2 Open
Position 3 Open
Position 4 Open
Position 5 Closed
Position 6 Closed
Load Program Studio from the PinPoint Task Bar and then select the Device Test
Mode "Tab"
At the top of the screen you will see a Menu Bar and Icons. Hover the mouse over
these Icons and you will see the "Tool Tips" displayed for these Icons.
EZMode
Select the EZ Mode Icon and ensure that the Yellow "LED" in the Icon
Box is "illuminated".
EZ Mode (analogous to Easy Mode) allows the PinPoint system to make

certain decisions to aid the Test Operator, dependent upon the Test results
received. These EZ Mode decisions are ALWAYS displayed to the Test
Operator.
Performing EZ Mode operations is NOT part of this Tutorial and is covered

extensively in the Standard Training Course. For more information on EZ
Mode refer to the On Line Help.
Issue 1.5
Options Menu
The Options Menu allows you to select the number of time the Opens Test is
to be performed to check for consistency. It is recommended that the Opens
Test be performed at least 3 times to ensure there are no intermittencies.
Test Menu
Select the Test Menu (alternatively Function key F4 or Icon). This opens
a "Select New Device" Dialog box.
Enter the Part Number 74F08 and see the change to as the final
number is inserted, and the system recognises that the device is in the
PinPoint Library.
Ensure that the "Assign Default Test Clip" check box is enabled (ticked)
Select the "Find" tab and ensure that the Part Number "Radio Button" is
enabled - type in 74F and see the Part Numbers scroll to the beginning of the
74F section.
Select "Description" radio button and see the format change. Double click on
"AND Gate" and then select "QUAD 2 I/P" and you will see the full range of
"Quad 2 Input AND Gates" that are in the PinPoint Library.
Select the "Clip" tab and you are able to select the required front panel
position that you want to apply the "Default Test Clip" to. Select position "A"
OK from the Dialog box and the PinPoint Tests should start - however, because the
test clip is NOT attached to the device the system waits for Contacts between the
device and the system to be achieved.
Connect a 14 pin DIL Test Clip to position "A" and then attach the clip to device
U1 on the Tutorial Board.
The Test process is carried out in two parts:-
Part 1 - Parametrics
The first "pass" of the Device Test obtains the external Parametric
information about the device - this includes the external "Shorting Pattern"
and any Open Circuit pin.
Part 2 - Test
The second "pass" uses the above "Shorting Pattern" to obtain the "correct"
functional program to use on the device in order to test it correctly. It then
applies this "correct" program to determine whether the device is working
correctly.
Issue 1.5
Having tested the device it is now possible to "Repeat the Test"

(alternatively select the Test Menu > Re-Test Device or Function Key F5), or
perform a "Loop Test" (alternatively select the Test Menu > Repeat/Loop
Test Device or Function Key Shift + F5) to check for intermittent operation.
To stop the test cycling in “Loop Test” mode press any keyboard key.
Utilities Menu
From the Utilities Menu, or the Icons, you can also Edit Device Parameters
, view SeaWave , or view the Functional Source for the selected
device - these functions are common the other applications and will be
completed at a later date.
Follow the above procedures to test U2 and U3
Remove the Test Clip from device U3 when completed.
Issue 1.5
2.1.2 Device ID
The Device Identifier Mode is used to identify devices where the markings on the
device has been removed - this is often done by board manufacturers in an attempt
to prevent "pirating" or copying of propriety information. However, when repairing
these types of boards, device part numbers are essential. The Device Identifier
Mode first determines the "Device Shorting" pattern (Power Supply connections
and other external shorts about the device) and then selects suitable Functional
Programs from the PinPoint Library to test the "unknown" device in an attempt to
identify its "functionality".

Only Functional Library Devices utilising Drive
Levels between 0 and +5 volts will be scanned in
order to attempt to identify an "unknown"
device.
Search Libraries
From the Device ID Menu select "Select Search Libraries" or alternatively the
Icon.
This "Load Device Library" allows you to select which PinPoint Libraries the
Device Identifier will utilise in order to attempt the identification. The
Libraries on the left side are the list of Available Libraries, but are NOT
currently selected for the identification process. The Libraries on the right
side are the ones being used to identify the device. If you know the
technology of the unknown device then ensure the appropriate Library is
loaded into the right hand side.
To move Libraries from one side to the other, select the required Library and
either select the Add>> or Remove<< buttons, or alternatively "double click"
on the required Library.
The Libraries in the right side (Search Libraries) are ordered in the prioritised
Search Sequence - the top Library is the first Library used to attempt the
identification process, followed by the next and so on.
To move Libraries within the Prioritised order, select the "Move" check box,
and then "double click" on the required Library to move. This Library
temporally "disappears" allowing you to select ("double click") the required
new location.
Ensure that the CMOS and TTL0 Libraries are in the right hand column - if
others exist, then <<Remove them. When you OK from the dialog box the
system will re-order, or update the Library Database, which will take a few
seconds
Issue 1.5
Perform Device ID
Once the Libraries are sorted select Perform Device ID from the Device ID Menu
(alternatively the Icon)
From the Device ID Wizard Dialog box, select 14 Pin DIL Test Clip and enter 14
pins as the Device Pin Number. Also ensure that Test Clip position "A" is selected.
Before selecting OK from this Dialog box, ensure that the test clip is NOT attached
to any device.

When a Device is selected for Identification, the
Program Loading and Device Identification is
effectively a "2 Stage Pass" - as with Device Test
performed earlier, the first "Pass" is to identify
the "shorting pattern" and the second to identify
the actual device
Clip the test clip over device U2 and allow the identification process to complete.
After the first "Pass" the system will generate a prompt indicating how many
PinPoint Functional Library Programs exist with the SAME shorting pattern.
ALL these functional programs are then applied to the device in turn to determine
whether the functional program Passes or Fails - programs that Pass are listed and
form the identified list.
You will notice that for the 74F04 device selected, we identify the following
possibilities:-
7404
7414
CD4069

We CANNOT Identify the Device Technology - we
don't know whether the device is CMOS or TTL,
or the category i.e. 74F04
Follow the same procedure to identify devices U1, U3 and U5.
You will notice that, even though U5 is the same device as U3 (74F74), we were
NOT able to identify U5 - this is because there are certain In-Circuit conditions
applying to U5 that prevent us from identifying it. The reason will become
apparent later on during this Tutorial, and will be explained then - suffice to say
that it is NOT possible to ALWAYS identify devices in-circuit and therefore it
may be necessary to remove them from the circuit board in order to identify them.
Issue 1.5

Only Functional Library Devices utilising Drive
Levels between 0 and +5 volts will be scanned in
order to attempt to identify an "unknown"
device. This is to ensure that we do not damage
the device by applying excessive voltages to the
device. Applying +12 volts to a TTL device will
NOT identify it but destroy it - not a good idea if
we don't even know what type of device it is !!
We have now completed the Tutorial for the Device Test Mode
If you have the VI Test System fitted, continue to Section 2.2 - VI Instrument
Mode.
If you have the Analog Card / sub-system fitted, jump to Section 2.3 - Analog
Instrument Mode.
If you have neither of the above options fitted, jump to Section 3 - Define Board.
Issue 1.5
2.2 VI Ins tru me n t Mod e

Using the V/I Instrument Mode of Program Studio
In this particular section of the tutorial we will be working through the Instrument
Mode of TestVue. This mode is best demonstrated using the VI section of the
Tutorial Board.
1) Before starting with this Tutorial section ensure that all the switches on the VI
Section of the Tutorial Board S2 are set to OFF. Remove the power leads from
connector J1 or Test Points 1 to 4.
2) All the discrete devices, with the exception of the transistors, that require to be
probed during this tutorial have test points situated above the component.
3) The function of the VI system is to apply a controlled alternating voltage

(usually a Sine Wave) into a circuit node and to display, and record if required,
the Voltage and Current responses in a variety of formats.
Select the VI INSTRUMENT function from the Program Studio "Tab".
From within the VI INSTRUMENT function, select "Manual" from the MODE
Menu Command Bar and chose the "Probe A" option from the SOURCE Menu
Command. You will notice that the trace colour is GREEN - this represents the
Green Probe - and with nothing connected the trace is a horizontal line. Short the
Green Probe to the Black Common lead and notice that the trace is now vertical i.e.
an open circuit is represented by a horizontal line and a short circuit by a vertical
line.
From the Menu Command bar select VOLTAGE and then select the 15 Vpk
Voltage option and clip one lead of the Black Common assembly to Test Point TP1
(0 Volts) on the Tutorial Board. Next, using the Green Probe, probe Resistors R16
R17, R18 and R19 in turn. Notice the different angle of rotation of the display for
each resistor {R19 (47K Ohms) is almost horizontal whilst R16 (51 Ohms) is
almost vertical} and also the Impedance value in the lower left quadrant. Change
the Voltage setting by clicking on the V+ and V- buttons at the top of the
display - observe the changes in the waveform and the associated Volts / Division
displayed in the top left quadrant.
For small increments / decrements of the voltage range (0.1 Volts) hold down the
keyboard SHIFT key whilst depressing the V+ or V- buttons.
Adjust the Frequency setting by clicking on the F+ and F- buttons and

notice there is no change in the traces - resistors are not frequency dependent (See
Figure 2.1).
Issue 1.5
Figure 2.1 Resistor R17 - 1k (15V test signal)
Whilst probing on Resistor R16, select MODE and then AUTO. The system will
automatically scan through all the Voltage and Frequency ranges to determine, and
display, the most suitable setting. This setting will also display the most accurate
Impedance measurement value. This AUTO VF setting may be rapidly selected for
each component by using the Hot Key combination of Ctrl + A.
Change the Mode selection to STATIC – you will notice that the trace remains
displayed even after the probe has been removed form the device. Revert back to
AUTO Mode.
Displaying ALL the Voltage ranges may be enabled by selecting VOLTAGE from
the Menu Command bar and then CYCLE.

When VOLTAGE CYCLE is selected the system
automatically reverts back to the MANUAL MODE
of operation. Note also that to revert back to
AUTO Mode VOLTAGE CYCLE must be de-
selected.
Next, connect the Green Probe to the Cathode (Top Leg) of Diode D6. Current can
flow in a Diode from the Anode to the Cathode and is blocked from the Cathode to
the Anode (see Figure 2.2). As the injected voltage into the diode is sinusoidal, this
characteristic can be seen from the trace where part of the trace is virtually an open
circuit (right hand quadrant) and the other part (left hand quadrant) a short circuit
once the voltage approaches 0.6 volts (the diode breakdown voltage).
Observe the changes in the waveform for all the voltage settings. Adjust the
Frequency setting by clicking on the F+ and F- buttons and notice there is
no change in the trace - like resistors diodes are not frequency dependent.
Issue 1.5
Figure 2.2 Diode D6 (5V test signal)
Return the display to 15Vpk by selecting 15Vpk from the VOLTAGE menu.
Connect the Green Probe to the Cathode of Diode D7 and notice that, at a voltage
setting of 10 volts and above, the previous horizontal trace quadrant now rises
significantly into the top right quadrant - this indicates that there is some parallel
resistance, or leakage, in the normally non-conductive region of the diode.
Next we will have a look at the different types of display available within the VI
Test system. Select the OPTIONS Menu Command, and from within this command
select DISPLAY and then Voltage Response Curve. The trace display now changes
to a dual format - the Yellow trace indicates the original Voltage Source voltage
and the Green trace the response to this trace across the green and black leads.
Briefly move the Green Probe and short it to TP1 - notice that the Response
waveform is horizontal (there being no voltage drop across a short circuit). Now
remove the Green Probe from TP1 - the response trace is now identical to the
Source trace indicating there is maximum voltage drop across an open circuit.
Finally re-connect the Green Probe to the Cathode (Top Leg) of Diode D6 and
observe the waveforms throughout the voltage ranges. At a setting of 1Vpk you
will notice that there is approximately a 0.6 Volt peak differential between the
horizontal and the Green "Response voltage" in the left quadrant - the normal diode
forward voltage drop - whereas there is a maximum voltage differential in the right
quadrant. The 0.6 volts differential in the left quadrant will exist in all voltage
ranges, but is visibly more pronounced at lower voltages.
Return the Display back to Lissajous Figure format
Issue 1.5
It is possible to compare traces directly by selecting Probe Compare Mode. To

select this mode of operation select PROBE COMPARE from within the Source
menu command. A Red trace (representing the Red Probe) is added to the display.
With the Green Probe still connected to Diode D6 connect the Red Probe to Diode
D7 and compare the traces through the voltage ranges. (Select VOLTAGE CYCLE
Mode to display all voltage ranges.) You will notice that there is no difference in
the traces in the left quadrant whereas there is in the right quadrant. At a voltage
setting of 15 Vpk and above there is a significant difference between the Red and
Green traces showing the leakage resistance across diode D7.
Finally, in the PROBE COMPARISON mode, it is possible to view the tolerance

banding around the Green Signature in order to determine the extent of the
difference between the two signatures.
Select the % Button situated at the top of the screen. You will observe the
green "shading" around the display and the tolerance value displayed in the bottom
right of the screen. The tolerance values may be adjusted by selecting the
"increment" or "decrement" buttons adjacent to the % Button .
To remove the tolerance display, simply re-select the % Button again.

The tolerance banding is only available utilising
the "Lissajous Figure" Display Option.
This displacement is the same for all types of waveform (Sine, Square, Triangle
and Saw Tooth) as can be seen by selecting these different WAVEFORMS from
the OPTIONS Menu Command.
Return the waveform back to a Sine Wave, the VOLTAGE to CYCLE and the
Source to Probe A. Now select the Current Response Curve from the OPTIONS
Menu Command. Now a short circuit between the Green and Black Probes shows
no displacement between the Yellow and Green traces (maximum displacement
from zero reference point indicating maximum current flow) whereas an open
circuit shows a horizontal response trace indicating no current flow. Again observe
the waveforms across the diode D6. Note that current flows in the left quadrant but
not in the right quadrant.
Compare the traces between diodes D6 and D7 by selecting PROBE COMPARE

from the Source menu and again note the leakage current shown in the right
quadrant for the Red Display.
Issue 1.5
Return the OPTIONS Display to the Lissajous figure format, the VOLTAGE to
CYCLE and select the FREQUENCY range of 1500Hz. Connect the Green Probe
to Capacitor C21 and the Red Probe to Capacitor C22. Observe that the waveforms
are elliptical and that the waveform varies greatly both with voltage and frequency
(select the F+ or F- buttons to change the frequency). Note that at 300 Hz the best
Voltage / Frequency characteristic for the larger capacitor C22 (10uF) {Red Trace}
is at low voltages whereas for the smaller capacitor C21 (0.1uF) {Green Trace} a
higher voltage setting is best - however this is not necessarily the case for other
frequencies.
Inductors exhibit similar waveforms to capacitors as can be seen by probing the top
leg of Inductor L1.
Change the display to Voltage Response Curve and then Current Response Curve
and observe the waveforms for different voltages and frequencies for C21, C22 and
L1. In particular notice the phase delay change with voltage and frequency i.e. the
voltage and current are out of phase in a Capacitive and Inductive circuits
Return the Display back to Lissajous Figure format
Resistor R14 and Capacitor C23 are in parallel with each other. Compare
waveforms between Capacitors C22 and C23. Observe the waveform is an ellipse
and that the waveform varies greatly both with voltage and frequency. Notice that
with a frequency setting of 50Hz, the elliptical display for C23 {Red Trace} is
tilted over indicating that there is some resistance, or leakage, in the circuit.
However, at higher frequencies (700 Hz and above) it can be seen that the effect of
the resistance becomes negligible, showing the importance of capturing as many
trace signatures as possible - a feature unique to the VI Test system.
Again change the display to Voltage Response Curve and then Current Response
Curve and observe the waveforms for different voltages and frequencies.
Return the Display to the Lissajous figure format. Next observe (and understand)
the traces for Zener Diode ZD1, NPN Transistor TR1, PNP Transistor TR3 and
LED D1 (D1 / R1 junction) on the Tutorial board. Apply varying voltages and
frequencies and for all types of display and waveforms. Refer to the section on
Basic Component Signatures in the Reference Manual for details on specific
waveforms for these devices.
Compare Transistors TR1 and TR2 in Probe Compare and Voltage Cycle Mode.
Close Switch S2-6 and observe the difference when TR1 has Base Emitter
Leakage. (Bottom Pins of TR1 and TR2)
Compare Transistors TR2 and TR3 in Probe Compare and Voltage Cycle Mode.
Notice in particular the Base signatures (Bottom Pins of TR1 and TR3) are
basically the same except they are in totally opposite quadrants.
Observe the traces for Digital Device U7 in Voltage Cycle mode. Note that pins 1
and 19 are pure Input pins whereas pins 2 to 9, 11 to 18 are bi-directional Tri-State
pins. The signatures on pin 6 to 9 may be very slightly different due to being
connected to the inputs of devices U11 and U12.
Compare pins 1 and 19 with Switch S2-2 closed to show the effect of leakage on
Input pins.
Issue 1.5
Compare pins 2 and 3 with Switch S2-1 closed to show the effect of leakage on
Tri-State pins. Note the importance of viewing the response on as many voltage
ranges as possible otherwise this particular error may be missed.
Compare devices U11 and U12. Notice the difference between U11 pin 1 and U11
pin 13 which are both input pins. One would normally expect input pins to exhibit
the same signatures - however U11 pin 13 is connected in-circuit to U7 pin 9 which
is a Tri-State output pin and hence the difference. Probe U12 pin 9 - switch S2-4
ON to introduce a short on 2 input pins and observe the signature - notice that there
is NO difference. Switch S2-3 to introduce a short on 2 output pins and observe
again that the signatures on U12 pin 8 do not change. This highlights one of the
normal shortcomings of traditional VI systems i.e. that a short circuit between 2
pins that normally exhibit the same signature will NOT be detected. However, with
the Diagnosys VI Test System and MULTIPLEXER / SCANNER we can perform
a Shorts Test around all the pins of a device to overcome this traditional limitation.
See below for more details.
Probe pins 1, 2 and 3 of device U10 (an Analog Switch). Notice that on pins 2 and
3 the waveform changes for a few seconds before stabilising. This phenomenon,
known as Pre-Charge, will require special attention when we come to develop a
complete Board Program later in this tutorial.
Notice that the order in which the pins are probed may affect the required Pre-
Charge period. Follow the following steps to observe the phenomenon.
1) Probe pin 1 and allow for any possible Pre-Charge.
2) Remove probe from pin 1 once the signature has stabilised.
3) Replace probe on pin 1 and notice no Pre-Charge requirement.
4) Probe pin 2 and allow for any possible Pre-Charge.
6) Replace probe on pin 2 and notice no Pre-Charge requirement.
8) Probe pin 1 and notice the Pre-Charge requirement.
Issue 1.5
2.2.1 Multiplexer / Scanner

If you have the MULTIPLEXER / SCANNER cards fitted there are four further
features available. For this option you will require 2 off 14 pin DIL Test Clips (a
16 pin Test Clip will be suitable provided pin 1 of the Test Clip is positioned over
pin 1 of the device).
Clip
Firstly select the SOURCE CLIP mode and clip over device U11 with a 14
pin Test Clip inserted into Test Clip Connector A. From the Drop-down List
Box at the bottom of the screen select a 14 pin DIL Test Clip.
. You can increment or decrement through
the 14 pins of the device by selecting the P+ or P- buttons.

The pin number, voltage and frequency
ranges are displayed in the Grey boxes at
the bottom of the screen.
All the other modes described above are

available with the Scanner i.e. Auto VF,
Voltage Cycle Mode and the Display and
Waveform Options.
Clip Compare
Secondly, select the SOURCE CLIP COMPARE mode and place a second
Test Clip, fitted to Test Clip Connector C over device U12.
This mode is usually used to compare the signatures between devices on a

known good board and faulty board. However U11 and U12 on the Tutorial
board are like devices and therefore can be compared in this mode. Again,
scan through the device pins using the P+ and P- buttons. Compare
the signatures on pins 6, 8, 9, 10 and 11 with switch S2 3, 4 and 5 in both the
ON and OFF states.

On higher voltage ranges some digital
devices may exhibit the beginnings of a
Zener effect. This is normal and is the
reason why digital devices are not normally
tested at these voltage ranges.
Issue 1.5
Device Compare
The third feature is DEVICE COMPARE MODE. The function of this mode
is to display, and compare, up to 10 device pins simultaneously. When this
mode is entered, the system scans through all of the device pins (as
determined by the Test Clip setting) and can determine the AUTO VF for
each pin. Associated with each device pin display is the Voltage and
Frequency settings and the ability to increment / decrement these ranges with
the associated buttons. If the AUTO VF setting is changed by the Voltage /
Frequency range buttons, there is the ability to re-select the AUTO VF range
for each individual pin - this is done by selecting the "A" button situated
immediately above the F button, or, globally for ALL pins, by
selecting the Auto VF button next to Close.
The 10 displayed pins may be incremented or decremented by 1 by selecting

the Up / Down Scroll Bar buttons (or by dragging the Scroll Button) situated
on the right of the screen, or by 5 by selecting inside the Scroll Bar either
above or below the actual Scroll Button itself.
Select “Close” to exit Device Compare Mode
Filter Mode
The fourth and final feature is the FILTER MODE. This is similar to the
Device Compare Mode defined above but only the pins that fail to compare
against the defined tolerance setting are displayed.
Select FILTER from the MODE Menu, select the required Device Test Clip
Selection, and then the required tolerance, say 20 % (displayed at the bottom
right of the screen). Once the conditions are set up, clip over devices U11 and
U12 on the Tutorial Board (ensure that ALL the switches are set to “Open”)
and select "GO" to start the FILTER procedure. You will notice at the
bottom left of the screen that the system is "Collecting Traces" for each pin.
With all the switches on S2 set to "Open" there will be a message displayed at
the bottom of the screen "All Pins PASSED" and no signatures visible. Repeat
the process with switches 3, 4 and 5 "Closed" and observe the difference in
signatures.
Select "END" to stop the display and, if necessary, repeat the process
with different tolerance settings.
Return to the Manual mode of operation by selecting the MODE Menu.
Issue 1.5
2.2.2 Pulse Mode

There is one additional feature in the System. This feature is the
Programmable Pulse Generator. This feature is useful in testing devices such
as Triacs, Thyristors etc and also in testing the transfer characteristics of Opto
Couplers.
Connect the Pulse Generator Channel A output to pin 2 of device U13 (the
input Diode Cathode) and the GND point to pin 4 (Transistor Emitter).
Select Pk from the Pulse Menu , “Voltage Cycle” from the

Voltage Menu, and probe around the output transistor pins 5 and 6 using the
Green Probe. Adjust the pulse and observe the displays generated on the
transistor outputs. Note that the signature on the transistor base (pin 5)
changes dramatically when the diode transfer characteristic has been obtained
(between 1 and 2 volts). See Figure 2.3 below.
Pulse @ 1 Volt Pk Pulse @ 2 Volt Pk

Figure 2.3 Opto Coupler – Pulse Mode
We have now completed the Tutorial for the VI Instrument Mode
If you have the optional Analog Card / sub system fitted, continue to the Section
2.3 - Analog Instrument Mode, otherwise jump to Section 3 - Define Board.
Issue 1.5
2.3 An a log In s tru me n t Mode Ov erv ie w
The Analog Option consists of a number of separate Instruments depending upon

the options installed on your system. The options are:-
1) Digital Multimeter (DMM)
2) Counter / Timer
3) Arbitrary Function Generator (ARB)
4) Oscilloscope
5) LCR Bridge
6) DC Source / Parametric Measurement Unit
7) Shorts Locator
With the Analog sub-system is fitted, the following Icons will be visible
in the Program Board and Libraries Tabs within

Program Studio.
1) Digital Multimeter
The Functions / Modes for the DMM are:-
a) DC Voltage Measurement
b) AC Voltage Measurement
c) Resistance Measurement
d) Direct Current Measurement
e) Alternating Current Measurement
f) Diode Measurement
g) Capacitance Measurement
2) Counter / Timer
The Functions for the "Dual Counter / Timer" are:-
a) Frequency from either Channel A, Channel B or the High Frequency Channel.
b) Period from either Channel A, Channel B or the High Frequency Channel.
c) Time AB. Time difference between the selected clock edges from Channels A
and B.
Issue 1.5
d) Unit Counter. Counts the number of pulses from either Channel A or the High
Frequency Channel.
e) Frequency Ratio. Measures the frequency ratio of either Channel A or the High
Frequency Channel Frequency over Channel B Frequency.
3) Arbitrary Function Generator
The Arbitrary Function Generator is capable of generating the following

waveforms:-
a) Sine Wave.
b) Saw-Tooth Wave.
c) DC Wave.
d) Square Wave.
e) Triangle Wave.
f) User Wave.
Up to 4 Waveform Generators are available as options.
4) Oscilloscope
The Functions / Modes for the Oscilloscope are:-
a) Dual / Quad Channel.
b) Programmable Trigger.
c) Auto / Manual Mode.
d) Hold / Free Run.
5) DC Source / PMU
The Functions / Modes for the DC Source are:-
a) Dual / Quad Channel.
b) Programmable Constant Current Mode
c) Programmable Constant Voltage Mode
d) Stimulus / Read-back Modes.
e) Hold / Free Run.
Issue 1.5
6) Shorts Locator
The Functions / Modes for the Shorts Locator are:-
a) Maximum 1 Amp Short Circuit (programmable)
b) Maximum 500mV Open Circuit Voltage (programmable)
7) LCR Bridge
The Functions / Modes for the LCR Bridge are:-
a) Measure Resistance, Capacitance, Inductance
b) Calibrate Probe feature
c) Indication of Frequency, Impedance and Phase Angle
Issue 1.5
2.3.1 Analog Instrument
As specified before, the Analog Option consists of up to seven separate

Instruments:-
2) Timer / Counter
4) Oscilloscope
5) DC Source / PMU
6) Shorts Locator
7) LCR Bridge
We will look at each of these in turn.
Locate the Tutorial Board and its associated Power Supply leads from the supplied
items.
Connect the Power Supply leads to the Tutorial Board and also to the PinPoint
front panel.
TP1 0 Volts Black
TP2 +5 Volts Red
TP3 -12 Volts Green
TP4 +12 Volts Yellow
Ensure that the switches S1 are set as follows:-
Position 1 Open
Position 2 Open
Position 3 Open
Position 4 Open
Position 5 Closed
Position 6 Closed
Issue 1.5
The Functions / Modes for the DMM are listed below and are selected by the
"Front Panel Dial" (see Figure 2.4).
Figure 2.4 DMM Instrument Mode Select Dial
a) DC Voltage Measurement
b) AC Voltage Measurement
c) Resistance Measurement
d) Direct Current Measurement
e) Alternating Current Measurement
f) Diode Measurement
g) Capacitance Measurement
From within Program Studio select the DMM Instrument icon . The DMM will
be switched on and a default setting of VDC will be selected. Click once on the
Range button to select Auto, so that the DMM will cycle through the ranges to
obtain the best range for any given measurement.
VDC Mode
Connect probes to each of the DMM terminals DMM+ and DMM-. Select UUT
Power On/Off from the DMM instrument Front Panel to switch on the UUT Power
Supply. Probe pin 7 of U1 with DMM- and pin 14 with DMM+. A reading of 5Vdc
should be visible in the seven-segment display panel. Now try probing various
points around the board. Switch UUT Power Supply Off.
VAC Mode (in conjunction with Arbitrary Waveform Generator)
Switch to VAC Measurement Mode, select the Arbitrary Waveform Generator

and Switch it on with the Red Power Button. By default the Signal Generator will
be set to 0V DC. The DMM VAC measurement is a VACrms measurement.
Connect the DMM+ to the ARB 1 Out and DMM- to Analog GND, a measurement
of around 3.535V should be displayed. You can increase/decrease the output from
Issue 1.5
the Signal Generator by using the Pk-Pk Voltage adjustment (top). Remove the
probes from Analog GND and ARB Out.
Resistance Mode
Switch to Resistance Mode and connect the DMM probes to either side of R6. A
resistance measurement of around 100R should be displayed, allowing that R6 is a
100R with a 5% tolerance. Again use various points around the board to make
further measurements.
Diode Mode
Switch to Diode Mode and probe D4 anode on the PinPoint Tutorial Board with
DMM- and D4 cathode with DMM+. The result displayed should be voltage over
range or in other words the diode is reverse biased. Now swap the DMM probes
over to forward bias the diode. A forward bias voltage of between 0.65v and 0.7v
will be displayed. This feature can be used to test the integrity of diodes. Similarly
Zener diodes can be tested, the breakdown voltage of the Zener when reverse
biased will depend on the Zener itself i.e. 3v7. Remove the probes from D4.
Capacitance Mode
Switch to Capacitance Mode. It is difficult to find a good example to use to

demonstrate Capacitance Mode on the PinPoint Tutorial Board, due to the in-
circuit nature of capacitors in parallel. This function can be best demonstrated
using capacitors out of circuit. Try using capacitors between 10nF - 2uF at first.
2) Dual Counter /Timer
From within Program Studio select the Counter / Timer Instrument icon .
Channel Select
The Channel Switch button selects either the Channel A or the High Frequency
Channel.

Both Channel A and Channel B have a
Trigger Input Threshold range
between -10 Volts to + 10 Volts
whereas the High Frequency Channel
is purely a TTL level and therefore has
no programmable Trigger Threshold.
Trigger Level
Adjust the Trigger Level by the "rotary" switch until the required voltage is
displayed. Alternatively you can type in the required value by selecting the switch
with the right mouse button and typing in the required voltage in the "Type It"
Dialog Box.
Issue 1.5
Clock Edge Select
The active edge of the Clock input may be selected as either a +ve edge or a -ve
edge by selecting the Icon.
Function
The required function that you wish the "Counter / Timer" to perform is selected by
means of the "Function" button. The functions that are available are:-
a) Frequency from either Channel A, Channel B or the High Frequency Channel.
b) Period from either Channel A, Channel B or the High Frequency Channel.
c) Time AB. Time difference between the selected clock edges from Channels A
and B.
d) Unit Counter. Counts the number of pulses from either Channel A or the High
Frequency Channel.
e) Frequency Ratio. Measures the frequency ratio of either Channel A or the

High Frequency Channel Frequency over Channel B Frequency.
Cycles
This defines the number of cycles that the relevant Function is measured over -it is
selected by the "Cycles" button.
The number of Cycles is 1, 10, 100 or 1000 and is valid for Period, Time AB and
Frequency Ration.
Gate
This defines the period (or time interval) that the relevant Function is measured
over - it is selected by the "Gate" button.
The Gate period is selectable from 0.01us, 0.1us, 1.0us or 10.0us and is only valid
for the Frequency measurement.
Exercise
Using the PinPoint Tutorial Board connect the Frequency Input A Channel to U1
pin 13. Connect the Frequency Input B Channel to TP5 and connect Analog GND
to U9 pin 10. Move switch S1 position 1 to the “On” position (to the right). Switch
both of the Counter /Timers on using the Switches. Select Frequency
Measurement and adjust the trigger level for each channel to +2.2v. Using the Gate
Switch select a rate of 0.01s.
Frequency
Switch the UUT Power “On” and within a few seconds Channels A & B
should be reading a frequency at each position. Channel A should read
10MHz and Channel B should read 5MHz. With the gate rate at 0.01s we are
sampling at 100 samples per second. We can select a range of sample rates by
clicking on the Gate Switch.
Issue 1.5
Period
Select a rate of 0.1s and now using the Function Switch click to change the
function to Period. This will display the waveform period of the two signals
we are monitoring. Channel A should read 0.1uS and Channel B should read
0.2uS. If we move Channel B to TP6 we should read 0.4uS (2.5MHz).
Time AB
Move Channel B back to TP5. Using the Function Switch click to change the
function to Time AB. This will display time difference between the selected
clock edges from Channels A and B and should read 0.100uS. If we move
Channel A to TP6 we should see a Time AB of 0.200uS.
Unit Counter
Using the Function Switch select Unit Counter. Immediately you will see the
unit counter rapidly incrementing at 2.5MHz. With the counter still running,
move switch S1 position 1 to the “Off” position (to the left). The counter will
stop. Move the switch from “Off” to “On” and back to “Off” again to see the
counter stopping and starting.
Frequency Ratio
Ensure the clock is still running and move Channel A back to U1 Pin 13.
Using the Function Switch select Frequency Ratio. With a 10MHz signal
present on Channel A and 5MHz present on Channel B the frequency ratio of
Channel A to Channel B is 2 (two pulses on Channel A for every one pulse on
Channel B). Move Channel B from TP5 to TP6 (2.5MHz), the frequency ratio
is now 4.
Finally, turn off the UUT Power Supply .
From within Program Studio select the ARB Instrument icon .
Functions
The Arbitrary Waveform Generator is capable of generating the following

waveforms:-
a) Sine Wave. Selected by the Switch Icon.
b) Saw-Tooth Wave. Selected by the Switch Icon.
c) DC Wave. Selected by the Switch Icon.
d) Square Wave. Selected by the Switch Icon.
e) Triangle Wave. Selected by the Switch Icon.
f) User Wave. Selected by the Switch Icon.
Issue 1.5
Frequency Range
The Range of frequencies can be selected between 300Hz, 3KHz, 30KHz or

300KHz by selecting the appropriate Frequency Range Switch Icon e.g.
Waveform Settings
The selected waveform can be modified / adjusted by selecting the appropriate

"Rotary Switch" until the required setting is displayed. Alternatively you can type
in the required value by selecting the switch with the right mouse button and typing
in the required setting in the "Type It" Dialog Box.
The selected waveform and settings are displayed at the right of the Arbitrary
Function Generator display.
User Waveform
A User Waveform can be generated by using an external Text file
<filename.EAW>.
The "External ARB Waveform" file should consist of 1024 lines (1 line for each
memory location) and each line contain a value between -1.0 and + 1.0. (1.0
representing full scale)
To import a User Waveform enable the USR Button -

this User Waveform file MUST be stored in the PinPoint EXTDIR directory
WHILST the board is being programmed. The file will then be stored and included
in the Test Program once the Test Program is saved - the EXTDIR Directory is
"cleared" once Program Studio is exited.
The Gain, Offset and Frequency of the External Waveform is controlled as per any
other waveform type.
A part example of an External Waveform File for a Pulse Generator is shown
below:-
1.0
1.0
1.0
0.0
0.0
0.0
0.0
where 1.0 represents the Pulse height and 0.0 represents the "space" between the
pulses (at zero volts) as shown below
Issue 1.5
Exercise (in conjunction with Counter / Timer)
Connect a probe from the ARB 1 OUT terminal to FREQ A terminal.
Connect Analog GND to U9 Pin 10.
Select Square Wave Generator using the Switch icon.
Adjust the Pk-Pk voltage to 5v by right clicking the mouse on the Pk-Pk
switch and typing in 5 in the Type it window.
Change the DC offset value to 2.5v by clicking on the DC Offset switch and
entering 2.5 in the Type IT window.
Change the frequency to 300KHz by clicking right mouse on the Frequency

switch and entering 300000 in the Type It window.
We should now see displayed on Channel A of the Counter / Timer a 300KHz

(ensure that Frequency Measurement and a Trigger Level of 2.2v are
selected).
4) Oscilloscope
From within Program Studio select the Oscilloscope Instrument icon .
If you do not have the Oscilloscope Option fitted then the Oscilloscope display will
indicate "Demo Version"
Switch on the Oscilloscope Power Switch and use the instrument as per any other
Oscilloscope (we will leave you to use the Oscilloscope Option)
5) DC Source / PMU
From within Program Studio select the DC Source icon .
If you do not have the DC Source/PMU Option fitted then the DC Source/PMU
display will indicate "Demo Version".
The DC Source/PMU provides 2 discrete channels for precision DC voltage and

current sources. Each channel works independently from the others and can output
± 10V at up to 20mA.
Channel Select
Toggling this button will switch the selected Channel On/ Off. (The PinPoint front
panel LED associated with this instrument will be illuminated when the instrument
is switched on)
Issue 1.5
Ranges
There are two operating ranges for each channel and each may be selected
independently i.e. the low voltage range can be used with the high current range.
Voltage Current
Low range: ± 1V 0 - 2mA
High range: ± 10V 0 - 20mA
SET/MEAS Button
When the instrument is in 'SET' mode, the user can specify the voltage and current
to be output on the selected channel. When the instrument is in 'MEAS' mode, the
instrument measures the voltage and current being output, which allows the user to
monitor the actual voltage and current on each channel to determine whether the
channel is in current limit or voltage limit.
ON/OFF Button
Toggling this button will switch the output relay on or off, enabling or disabling
the output at the instrument front panel. When the relay output is on the LED
indicator on the button is illuminated
Voltage and Current Values
The voltage and current values can be modified / adjusted by selecting the
appropriate "rotary button" with the left mouse button and using the mouse
"Wheel" to increase or decrease the value (if you haven't got a Wheel Mouse
"click" adjacent to the red indicator to change the value), until the required setting
is displayed.
Issue 1.5
Alternatively you can type in the required value by selecting the "rotary button"
with the right mouse button and typing in the required setting in the "Type It"
Dialog Box.
The selected voltage and current values are displayed in the DC Source display,
along with whether the instrument is in SET or MEAS mode.
Exercise
Using the PinPoint Tutorial Board make the following connections to TR2:
DC1 - Base
DC2 - Collector
GND - Emitter
_______
Emitter 1 ----I I
Collector 2 ----I O I
Base 3 ----I _______ I
Switch on CH1and select +/- 10v range. Set the voltage level to 3v.
Select the 2mA range and set the current to 0.04mA.
Click the CH1 On/Off button to enable the output.
Switch CH1 from SET to MEASURE.
Switch on CH2and select +/- 10v range. Set the voltage level to 5v.
Select the 20mA range.
Switch CH2 from SET to MEASURE.
Click the CH2 On/Off button to enable the output.
The voltage read back on CH1should be between 0.55v - 0.75v
The current read back on CH1should be between 0.035 mA - 0.06mA
The read back on CH2should be between 4.8v - 5.2v
The current read back on CH2 should be between 14mA – 17mA
If we take the base-emitter and collector-emitter we can calculate the hFE
hFE = Ice / Ibe = 15mA / 0.04mA = 375
Issue 1.5
6) LCR Bridge
From within Program Studio select the LCR Bridge icon .
If you do not have the LCR Bridge Option fitted then the LCR Bridge display will
indicate "Demo Version".
Overview
The LCR Bridge is an instrument that can be used to accurately measure the value
of a resistive, inductive or capacitive component. When the LCR Bridge is first
launched, a Characterisation routine will automatically be run to take into account
environmental factors. This will be run once a week when the instrument is started.
If the Characterisation fails, you can get a Dump file defining the reason for the
failure.
Set the Registry string to 1 under the LCR Bridge key to enable dumping the file - it
dumps to the file C:\TestVue\TPD\LCRDump.CSV.
Instrument Select
Toggling this button will switch the LCR Bridge On/ Off. (The PinPoint front panel
LED associated with this instrument will be illuminated when the instrument is
switched on)
Modes
The LCR Bridge may be used in one of three modes – Resistance, Capacitance
and Inductance to measure the value of a component. Click on the appropriate
button to select the required mode.
Expected Value
The LCR Bridge works best if an expected value is supplied which allows the
instrument to select the most efficient internal ranges for measuring the
component. The expected value can be modified / adjusted by selecting the
appropriate "rotary button" with the left mouse button and using the mouse "Wheel"
to increase or decrease the value (if you haven't got a Wheel Mouse "click"
adjacent to the red indicator to change the value), until the required setting is
displayed. The display will automatically update the units to make the value more
readable if small values are used with lots of zeroes after the decimal point.
Issue 1.5
Display
For information, the display panel shows the internal frequency value that is used
to make the measurement and also the measured impedance and phase that are
used to measure the component's value. The calculated measured value is then
shown in larger font. The units will update so that the value is readable in case of
small values with lots of zeroes after the decimal point.
Probe Calibration
To get more accurate results, the impedance of the probe may be taken out of the
equation by calibrating the probe. This is a two part calibration.
When the 'Calibrate Probe' button is pressed a dialog is displayed asking the user
to select whether they wish to calibrate the probe for Resistance and Inductance or
for Capacitance (both may be selected). The user will then be prompted to short
the probe together and hit OK if calibrating for Resistance and Inductance or make
sure the probe is open circuit if calibrating for Capacitance.
When the calibration is complete, the letters R, L and C will be shown at the bottom
of the display to indicate that calibration values are stored. These values will
continue to be used each time the LCR Bridge is used.
The values may be cleared, for example if a different cable is to be used, by hitting
the 'Clear Probe Calibration Data' button.
Issue 1.5
7) Shorts Locator
From within Program Studio select the Shorts Locator icon .
If you do not have the Shorts Locator Option fitted then the Shorts Locator display
will indicate "Demo Version".
Overview
The shorts locator instrument is a tool to enable PCB shorts circuits to be found
audibly. The ear is much more sensitive to pitch change than it is to volume, so as
the resistance between the measurement probes goes down, the frequency goes
up. Once the frequency has reached its peak, then the probes should have found
the point where two tracks are shorted together (the point of least resistance).
Instrument Select
Toggling this button will switch the Shorts locator On/ Off. (The PinPoint front panel
LED associated with this instrument will be illuminated when the instrument is
switched on)
Short Detected Current
This is the current value which will be supplied through the probes to enable the
resistance to be measured. The value can be between 0A and 1A and the default
is 100mA.
Open Circuit Voltage Limit
This can be between 100mV and 500mV and the default is 500mV.
Exercise
1. Switch the Shorts Locator On.
2. Set the Short Detected Current to 250mA
3. Set the O/C Voltage Limit to 500mV
Issue 1.5
4. Using the Shorts Locator lead set make the following connections.
I) Connect Black probe to U11 pin 12
II) Connect the Red probe to U7 pin 8 or the via shown in the diagram. Note
the audible change to the output tone.
III) Now move the Red probe to the via just above TR3 (see diagram below).
The audible output tone will become higher pitched.
IV) Now Connect Red probe to U11 pin 12 (effectively shorting the two
probes). An even higher pitch audible output will now be heard.
We have now completed the Tutorial for the Instrument Modes.
Issue 1.5
61
CHAPTER 3
3 Define Board
Contents
3.1 Board Programming .............................................................................................................................. 62

3.2 Define Board ........................................................................................................................................... 63
3.3 Board Size ............................................................................................................................................... 65
3.4 Adding Devices ....................................................................................................................................... 67
3.5 Passive Wizard........................................................................................................................................ 70
3.6 Package Wizard ...................................................................................................................................... 72
3.7 Dummy Devices ...................................................................................................................................... 74
3.8 Adding Text ............................................................................................................................................ 75
3.9 File Save .................................................................................................................................................. 75
3.10 Bit Map Files ........................................................................................................................................... 76
Chapter 3 Define Board 62
3.1 Boa rd P rogra mmin g

Board Programming may sound terrifying to the uninitiated PinPoint user, but is in
reality an extremely simple process - there is no requirement to know any
programming software - it is predominantly a process of mouse "Point and Click"
at the relevant positions.
The processes for Board Programming are:-
1) Define Board
Define the Board Graphics, including Board Outline and Device Placement.
2) Program Board
Apply current PinPoint Library Device programs to the above-placed devices.
3) NetGen Board.
Learn device interconnections in order to produce Circuit Diagrams and other

documentation.
In some cases it may be a requirement to add Functional Coding in order to create

New Device Programs, or modify existing ones. As this is an extensive topic, it
will be skipped in this Tutorial, and covered in both the Standard and Advanced
Training courses.
Issue 1.5
3.2 D ef ine Boa rd

The first requirement in Programming a Board is to define the "Board Parameters"
- this includes defining the board size and shape, and all devices to be tested onto
the board.
From within Program Studio select the Define Board "Tab". The screen format is
very similar to the previous "Instrument Modes" - the Menu Bar and underneath
this the Command Icons.
The Command Icons are segregated into Groups
Group 1 File Commands
File New, Open and Save
Group 2 Main Mode Controls
These are the 4 Main Functions within the Define Board application
Group 3 Zoom Controls
Zoom in, Zoom out, Auto
Group 4 Secondary Mode Controls
Secondary controls, dependent upon the Main Mode Controls
Select the "File" menu and then "New" - this ensures that we are working from a
completely "clean" environment.
You will see light grey rectangle positioned in the centre of the screen - this is the
allowable area in which to create the Board Graphics - 40" by 40" (or 1016 mm by
1016 mm)
As with the Instrument Modes, if you "hover" with the mouse pointer over any of
the Icons, a "Tool Tip" is displayed - we will be utilising all of these during this
Tutorial section.
Issue 1.5
Before actually defining the board, we should first select the required units of
measurement (Inches or Millimetre) from the Utilities > Grid menu (Hot Key
combination Ctrl + G).
Figure 3.1 Setup Grid / Units of Measurement
Also select the required "Grid Frequency". This is effectively the minimum spacing
between any items that can be positioned on the board. For Inches the incremental
units are in "thousands of an inch" (and therefore the default setting of 100 equates
to 0.1"), whereas for Metric, the incremental units are in Millimetres (2.54 mm
equates to 0.1").

The Rotate Settings define the direction and
degree of rotation for both Devices and Text that
are positioned onto the board - it DOES NOT
apply to rotation of the entire board. Leave the
Rotate Settings at Clockwise and 90 Degrees.
Issue 1.5
3.3 Boa rd S iz e
Defining Board Size and Shape
Select the Add Board Outline Mode Icon from the top of the screen, and then
click on Add New Board Outline Element Icon. An "Add Board Outline"
Dialog box as shown in Figure 3.2 will appear.
Figure 3.2 Add Board Outline Dialog Box
The Tutorial Board is a simple rectangle of 152 mm x 152mm (or 6" x 6").
For the moment we will ignore the X, Y offset boxes.
In the X, Y size boxes type in either set of values in accordance with your grid unit
of measurement (inches or millimetres), or click on the up/down arrows beside the
box to increase or decrease the dimensions.
Select OK to confirm entry of this data.
The White Board Outline will be displayed in white in the top left corner of the
main drawing area.
Select the Zoom To Board Dimensions Icon (Auto Zoom) to automatically

size the board to the screen extents.
If you wish you can modify the position / size of the outline. Use the mouse by
clicking on the upper left control point to drag/move the outline anywhere within
the main drawing area, or select the lower right control point to drag/resize the
outline to the required dimensions. The resize X, Y dimensions will be displayed in
the Status Bar (lower left) window as you drag the control point, so precise control
of the outline can still be maintained.
A Board outline can be made up of many elements grouped together to form the
required board shape.
Issue 1.5
For example, if the board had an Edge Connector on the bottom we could add this
as an extra board outline.
As an example, we will add another Outline Element.
Re-select the Add New Board Outline Element Icon. We will assume the extra
element is located on the bottom of the existing shape. In the Dialog box enter the
following parameters:-
Size X 100 mm (4.0 ")
Size Y 25 mm (1.0 ")
Offset X 25 mm (1.0 ")
Offset Y 70 mm (2.75 ")
Select "Round Rectangle" as the Outline Style and Arc Values of 5 mm (0.2"). This
will create rectangle of the "Size X and Size Y", positioned with an offset of
"Offset X and Offset Y", and a radius of "Arc Values" at the corners of the
rectangle.
Select OK and review the overall outline. Select the Auto Zoom Icon to again
automatically resize the board.
Click inside an Element to select it and enable the Edit Functions (White outline).
Click outside to de-select it disable the Edit Functions (Green outline).
When the Element is selected (White) you can re-size (bottom right "drag-point"),
move (top left "drag-point") and Delete it.
Almost any shape of board can be created by adding more Outline Elements.
Now we are ready to Add the Devices to be tested onto our board outline.
Issue 1.5
3.4 Add ing D evic e s

Adding Devices
Select the Add Device Mode Icon
You will notice that the 2 outlines generated in the Add Outline Mode are now
"filled in" to produce a composite "Board Outline".
First select UTILITIES and Search Libraries from the Menu Bar. Ensure that the
TTL libraries are in the right hand column - if they are not, double click with the
left mouse button on the libraries in the left-hand column to move them over to the
right. This will ensure that the system will prioritise the search through all the
required libraries when adding a device to the board. This is similar to the process
we carried out Device Test Mode when Identifying Devices.
See Help Text on Search Libraries for more information.
Position the mouse pointer on the board area at the point where pin 1 of the first
device (U1) is to be located, and click the left mouse button (X = 71 mm {2.8"} : Y
= 20 mm {0.8"}) . The Add Device dialog box (Figure 3.3) will now appear.
Figure 3.3 Add Device Dialog Box
Read from the board the device reference (U1) and enter this information into the
dialog box. Note the device part number (74F08), and type this into the dialog box.
Alternatively use the "Find" Tab, select Part Number "Radio Button" and select it
("double click") from the drop down list box. Establish the device package style
(DIL), and select this package from the Package Style drop down list box.
Issue 1.5
Leave the default settings on the Switches Tab (Refer to the Help Text for details
on these Settings).
You may select the "Options" tab within the dialog box to check that the Device
Orientation matches that of the device on the Tutorial Board (left facing).
Leave the "VI Scan" and "Device Generator Test" selections at their default
settings and press return or click on OK.
We will be returning to these at a later stage (Adding Dummy Devices).

The settings defined above are for the current
device and act as the DEFAULT settings for ALL
future devices, unless changed.
If there are two (or more) different package sizes for the device (eg 14-pin DIL or
20-pin PLCC as shown below) select the required Package from the displayed list
(DEFAULT in our case) and OK from the Dialog box
Figure 3.4 Select Package Description
A graphical device, with the correct number of pins and in DIL package format,
will appear on the board with the correct orientation.
If you wish to change / edit the position of the device on the board, you can do so
by selecting the Select Mode Icon. Click on the required device with the left
mouse button to select it (grey). Next click and hold with the left mouse button to
drag the device to a new position. You may move devices at any time within the
Board Editor when the Select Mode is active.
Alternatively you can use the RIGHT mouse button to perform the above function
whilst still in the Add Device Mode
Issue 1.5

You can also select MULTIPLE devices to move
by ensuring that the Ctrl key on the keyboard is
depressed whilst selecting the additional
devices.
Reselect the Add Device Icon to continue to place the remaining devices at the
appropriate locations on the board.
When you have added U4 you will probable see that the device graphics is wider
than the actual device - this is because you probably selected the incorrect Package
Style. You will have to re-fetch the device in order to correct the Package Style.
To re-fetch the device, click inside the device outline with the RIGHT mouse
button - it will turn grey. Select the Re-Fetch Icon (alternatively Hot Key F12
or Utilities Menu > Re-Fetch Device). You will notice that the Package Style now
specifies "24DIL600" instead of the original "DIL" setting. The DIL setting is a
Macro that fetches the appropriate Package Style dependent upon the number of
pins - in this case 24 Pin DIL 0.6" width viz. 24DIL600.
Select the Browse "check box" and view the graphics for the selected Package
Style.
From the drop down list box select the Package Style 24DIL300 and notice that
this package is "thinner" that the original - this is called a "SkinnyDIP" Package.
Scroll up in the Package Style List box to "SkinnyDIP" and notice that we are
unable to display the symbol with a Macro Image specified. If we OK from the
Dialog box with "SkinnyDIP" selected we will now see the correct Package Style
displayed - the ACTUAL image fetched was the 24DIL300 Package.
Ignoring the device U6, fetch the remaining devices up to, and including U10,
bearing in mind that U10 is a SOIC Package. If the actual device Part Number is
not recognised by the PinPoint Library, it is quite possible that there are equivalent
devices in the Library. For U10 select the "Find" Tab and check the "Description"
radio button. The device U10 is a Quad Analog Switch. From the List of Device
Types on the Left side of the Dialog box "double click" on "Analog Switch" and
then select Quad. A list of the entire Quad Analog Switches in the PinPoint Library
is displayed. Double click on DG211 (the device on the Tutorial Board is an
equivalent to this) to return to the General Tab.
Resistor Packs RN1 and RN2 are Part Number "RESPACK9" and Package Style
SIP (Single Inline Package)

Components can be added to the ‘underside’ of
the board by pressing the Function Key F6 to
toggle the board side.
We will now continue to adding Discrete Devices such as Resistors and Capacitors
etc.
Issue 1.5
3.5 P a ss iv e W iza rd
When adding Passive components such as Resistors and Capacitors there are so
many variations in size, polarity etc that it is impossible to define all of them in the
initial Package Library supplied with the system. For this reason we provide you
with a "Passive Wizard" that allows you to easily create your own Package and add
this to the Package Library.

The Passive wizard can ONLY be
applied to 2 - Pin devices.
Add Resistor R6. In the Part Number Field you can either enter the Resistor Value
(most standard Resistor Values are supplied in the PinPoint Library) or simply RES
(abbreviation for Resistor). We will add the actual Resistor value, as this will be
included in any Circuit Diagram that is generated (at a later stage, provided that
you have the requisite Optional software). The Resistor value is 100 Ohms so enter
100R.
In the Package Style field select Passive Wizard, and then OK to open the Passive
Wizard Dialog box (Figure 3.5).
Figure 3.5 Passive Wizard Dialog Box
The Package Style for most resistors is "Axial" (i.e. leads protruding from the side
of the device, rather that from the base - "Radial").

If "Radial" is selected then you have a
further choice of "Round" or
"Rectangular" body styles.
Select "Polarised" if the device to be added has Polarisation e.g. Capacitors and
Diodes. Resistors are not polarised and therefore ensure that the check box is NOT
selected.
Issue 1.5
Enter the Pin Pitch (0.5”) and Body Width (0.1”) parameters by either typing in the
required values or using the Increment / Decrement buttons associated with the
parameters.

ALL dimensions for the Passive Wizard
are "Imperial" measurements i.e. in
Inches.
When you OK from the dialog box, a device with the defined Package is positioned
onto the board graphics. Also, the defined Package is added to the PinPoint Library
if it didn't exist previously.
The format for the created Package in the Library is as follows:-
AXIAL/Pxxxx/Wyyyy for Axial Devices
RECTRAD/Pxxxx/Wyyyy for Rectangular Radial Devices
RNDRAD/Pxxxx/Wyyyy for Round Radial Devices
where Pxxxx is the Pin Pitch in thousands of an Inch
i.e. P0500 = 0.5 " Pin Pitch.
and Wyyyy is the Body Width in thousands of an Inch
i.e. W0100 = 0.1" Body Width
+ after the above dimensions specifies a Polarised Package.
Continue to add a representative sample of Resistors, Diodes and Capacitors.
For Resistors R1, R2 and R3 you will probably have to rotate the device. Select the
device to rotate, either with the RIGHT mouse button if in the Add Device Mode
, or the LEFT mouse button if in the Select Mode . Once the device is
Grey, rotate the device using the Icon (or alternatively Utilities Menu > Rotate
Device or hot Key combination Ctrl + R)

The direction and the degree of Rotation is
defined in the Utilities Menu > Grid Dialog box.
We will now continue to the “Package Wizard”.
Issue 1.5
3.6 P a ckag e W iz ard

The Package Wizard is used to automatically create new Package styles, without
having to resort to the Package Editor. It allows the creation of 6 types of standard
Package design.
We will create a PGA Package from this Wizard for an “imaginary

device” on the Tutorial Board.
Ensure you are in the Add Device Mode and position the mouse pointer
(anywhere within the board boundary) to add “imaginary 68000 device” that we
will call Ux.
Enter the following data:-
Device Ref Ux
Part Number 68000
Select the Package Wizard
Page 1
Enter the name DEMO_PACKAGE IN THE Name Edit Field (this will be the
package name), select your “preferred” Units of Measurement and select the
PGA Package Style.
Select the Next button.

If the Package name already exists in the
Library you will receive an error message.
Page 2
Select either Auto Size or Manual Selection – the default is 0.1” or 25.4mm
depending upon unit previously selected. Select Auto Size as will assume that
this size is applicable to our package.
Select the number of pins to be 10 Rows / Columns, Anchor over pin 1 and
Text to be in the package center.
Page 3
Most PGA packages have some pins removed form the center of the package.
We can remove these pins by simply clicking over the pin to delete, or “drag”
the mouse over the appropriate pins.

This is a “toggle - type” action.
Issue 1.5
Delete pins on Columns C to H and Rows 3 to 8.

Re-add pins C3 and C8 and also pins H3 and H8.

To return all the pins to enabled you can
select the “Reset Pins” Button.
Review the final Package Image. If it is correct, press the Finish Button to add
the created package to the Package Library, otherwise press the Back Button.
Click on the Browse check box to observe your newly created package.
Click OK to add the new device.

You will notice that you now have a choice of Package Descriptions to choose
from – select PLCC as this package size is 68 pins which is the same as the
number of pins we have just created for the PGA package.

We have created a “new” device with the
assumption that the pin-out of the new
PGA package is the same as that for an
existing PLCC Package.
Read the Help topic for this dialog box for more details.
As this is purely an “imaginary device” we should now delete it otherwise it

may cause confusion. To delete the device, select it so that it is “grey” and
select the delete icon (or keyboard delete key)
We will now continue to add a "Dummy" Device in the positions for U6.
Issue 1.5
3.7 Du mmy D evic e s
You may also place "dummy" devices on the board, which are not to be tested but
are for positional reference only.
A "dummy" device is created by fetching a specific part that is not in the Device
Library, and disabling all the tests from the Device Generator Tests section from
within the Add Device > "Options" tab.
Alternatively, create a "dummy" device selecting a device and then disabling all of
the test options from the device (we will be doing this at a later stage).
We will do this for device U6
Ensure you are in the Add Device Mode and position the mouse pointer to add
device U6.
U6 is simply a "Socket" and the actual device that should be fitted is unknown.
In the Part Number field enter Socket. You will notice that the "device" is NOT in
the Library indicated by the Icon.
Select DIL as the Package Style.
Go to the Options Tab you will notice the settings for "Device Generator Tests".
These are the actual Tests that you can perform on a device that is NOT in the
Library. You can perform a VI Test ONLY if you have the VI Test sub - system.
For this exercise we will remove ALL the Tests from this section - the device
placed will only be a graphical representation without ANY tests capable of being
performed. As mentioned in the Add Devices Tutorial Section this setting will now
be the default setting for all future Non Library Devices added (Dummy Devices).
When you OK from the Dialog box, an additional Dialog box is opened, requiring
you to enter the required number of pins.

Even if you enter the actual Package Style for the
device (20DIL300 for device U6) you are
required to enter the actual number of pins in
the subsequent "Device Generator" dialog box.
Device U6 appears identical to the other devices added - we will see the relevance
of Adding Dummy Devices at the Program Board stage.
We have added all the required devices to the board and will now continue to add
Text to the board.
Issue 1.5
3.8 Add ing T ext
Text can be added to the board by selecting the Add Board Text Icon. Once
text has been added, it can be Moved, Rotated or Deleted by selecting the
Select Mode Icon, in exactly the same way as a device.
As with devices, to place Text you MUST be in the correct Mode , and then
click in the required area that the Test is to be placed. The added Text will be
CENTRED about the selected position.
Add the Text for the "PinPoint Tutorial Board" at the lower right of the board.
We have now finished with the Define Board Application and will continue to
Save the work done so far.
3.9 F ile Sav e
When all devices to be tested have been placed, choose File and Save as.. from the
Menu Bar and type in the required name for the Board Program. We will call it
"Demo Tutorial". You don’t have to worry about the extension, as .TPD will be
added automatically by default.
Devices and Packages that are not in the PinPoint Libraries can be added by
accessing the Libraries Tab - this will be done later in this Tutorial.
Issue 1.5
3.10 Bit Map F ile s
Adding Devices
Apart form using the above-defined graphical method of generating board

programs, you are also able to use bit map images as your board definition.
Having saved your original program as “Demo Tutorial” select File New to start a
new board program.
In the Define Board Tab, select the File Menu > Picture > Load. From the Load
Board Picture Dialog Box select the “diagtestboard.bmp” file.
This loads the component-side bit-map image – it is also possible to load the
component side bit-map image (if it exists) by selecting “Load Solder”

Select the “Enable Preview” to display the board
image in the preview pane.
Click Open to load the picture.

Select File Menu > Picture > Unload to delete the
board image.

If the above process fails it will be necessary to
copy the contents of the TestVue > BIN >
FILTERS directory into the TestVue > BIN
Directory.
Select the Auto Zoom icon to display the full image of the board and then
select the Add Device Mode Icon.
Using the left mouse button “drag” over the area of device U1 (preferably from pin
1 to the opposite corner, but any sequence is acceptable). When the mouse button is
released the Add Device Dialog Box is opened – this is fundamentally the same as
per figure 3.3 above but the Package Style list box and Package Wizard buttons are
disabled (grey), as this is no longer a requirement.
Issue 1.5
Figure 3.6 Add Device – Bit Map Mode
The created bounded area is displayed as a blue outline – when selected for editing,
moving, deleting etc it is displayed as a yellow outline.
Once a device is added as above it can be programmed in the same manner as per
the graphical mode that is explained in Chapter 4 below.
Adding Pin Identifiers
Unlike the graphics programming mode (as defined in sections 3.3 to 3.9) where
individual pins are identified by the Package Editor, only the ‘bounding area’ of the
entire device is displayed.
However it is possible to add individual pin identifiers to the ‘bounding area’ of the
device. To do this select the Pin Identifier icon, click on the relevant position
of the device ‘bounding area’ and add the relevant information to the dialog box
Figure 3.7 Add Pin Identifier
Once a device is added as above it can be programmed in the same manner as per
the graphical mode that is explained in Chapter 4 below.
When all devices to be tested have been placed, choose File and Save as.. from the
Menu Bar and type in the required name for the Board Program. We will call it
"Picture Tutorial". You don’t have to worry about the extension, as .TPD will be
added automatically by default.
Issue 1.5

You can add an image of the underside of the
board if required by selecting “load Solder” from
the “Picture” Menu command.
Once the Board Definition has been completed, the next phase of programming is
to actually Program the Board by adding the required Functional information.
You can now select the Program Board application from within the Program
Studio.
Issue 1.5
79
CHAPTER 4
4 Program Board
Contents
4.1 Program Board ....................................................................................................................................... 80

4.2 VI and Functional ................................................................................................................................... 89
4.3 Operator Messages ................................................................................................................................. 92
4.4 TestFlow Summary ................................................................................................................................ 94
4.5 TestFlow Exercise ................................................................................................................................... 97
4.6 Analog Testing ...................................................................................................................................... 101
4.7 Board Properties................................................................................................................................... 107
4.8 Simulated Test Mode............................................................................................................................ 108
4.9 NetList Generator................................................................................................................................. 110
4.10 Schematic Generation .......................................................................................................................... 114
Chapter 4 Program Board 80
4.1 P rogra m Boa rd

The purpose of programming a board is for the PinPoint system to test the device
and verify that it is fully functional. This process can take one of three forms:-
1) For devices that are in the system library, the process is to test the device a
number of times using this library program and to verify that the device
conforms to the library standard. If it does, the device turns Blue indicating a
PASS. If the device does not conform to the library standard, then it will turn
RED indicating a FAILURE. If the device is intermittent - which is when the
device does not verify consistently, it will turn MAUVE.
2) For devices that consist of combinatorial logic, a Boolean device model will
exist in the PinPoint libraries. Regardless of the configuration the device is in,
if a Boolean device model exists, then the PinPoint system can predict the
output response for a good device, and compare this good data against the
device on the board, and hence determine whether the device is faulty. The use
of Boolean device models reduces the time taken to program and verify a
device by removing the need to cross-compile.
3) If the device with the specific configuration is not in the library and has NOT
got a Boolean device model, a process of Cross Compilation occurs. This
process is explained for devices U4 and U5 later in this section.
Before starting to program any device we must set up the required OPTIONS (see
Figure 4.1).
Figure 4.1 Options Menu
Issue 1.5
From the OPTIONS Menu ensure that the following conditions are set as follows:-
Device Program - Opens 3
Functional 5
VI 3
Device Test - Opens 1
Functional 3
VI 1
Assign Default Clip Ticked
Prober Has Priority Don’t Care
VI Settings Not Ticked
EZ Mode Not Ticked
Auto VF Settings Don’t Care
ROM Dump Not Ticked
Refer to the Help Text for information on Assign Default Clip and Popup Device
Information.
Before starting to verify devices some initial conditions must be satisfied. First,
connect the board Power connector to the PinPoint UUT Power Socket using the
lead provided, and secondly, ensure that the switch block SW1 is set as follows:-
1 OFF (Open)
2 OFF (Open)
3 OFF (Open)
4 OFF (Open)
5 ON (Closed)
6 ON (Closed)
At the moment all the devices, with the exception of U6 which is a "Dummy
Device", are shown as black as they have not yet been verified.
Click with the left mouse button on the first device to be verified (U1).
The system will prompt you to select an appropriate size test clip (14 pin) - press
any keyboard key to remove the message and then the system will prompt for you
to place the test clip over the device. At the moment this will be a 14-pin DIL clip
Issue 1.5
and the system will highlight, in YELLOW, the "A" Connector on the system front
panel mimic, and U1 on the Tutorial Board layout.
The default settings for the system will verify that the clip is correctly attached to
the device before performing any tests.
For correct orientation of the clip, the brown wire of the ribbon cable should be at
the pin 1 end of the device.
When the system has confirmed that the clip is correctly attached to the device, the
verification process will begin.
As the various tests are performed, the window at the bottom of the screen (called
the Test Status Box) will detail progress throughout the tests and list any failures (if
any) encountered.
The device U1 (74F08) is a Quad 2-input AND gate. This device is made up of
combinatorial logic and for this type of device - of which there are many- we have
Boolean device models in the PinPoint libraries. The PinPoint system can predict
the output response for any configuration of combinatorial logic device, and this
removes the need to cross-compile - or to learn the output response for a device.
With SW1 set as described above, U1 should produce the following messages in
the White Test Status Box at the bottom of the screen, without Functional errors
and the device will turn Blue.
Please Attach 14 pin DIL Test Clip to U1
Contacts
Voltages
Opens
Opens Test Failed on pin 13
Opens removed on pin 13
Shorts [7=L; 14=H;]
Voltages
Functional
Functional Test End
Functional Test End
Functional Test End
End of Device Test

Pin 13 of device U1 is an Open Circuit
pin and hence the message about pin
13 being detected as an Open Circuit
and subsequently the Opens Test
being removed from this pin.
If the device does fail (turns red or mauve) it will be necessary to change (Edit)
some of the test parameters. To achieve this, click over the device with the RIGHT
mouse button, and select Properties from the menu list.
Issue 1.5
An Edit Device Dialog box (Figure 4.2) is opened from which the test parameters
can be changed. Change the Test Rate from 4 MHz to 2.5 MHz within the
"Settings" tab using the down arrow, select OK and repeat the above process to
verify the device i.e. click over the device with the left mouse button to restart the
test / verification process.
Figure 4.2 Edit Device Dialog Box

EZ Mode will make certain Editing
Changes Automatically if certain
conditions exist. It is important to
review the Help Text for EZ Mode.
Voltage Learn
From the enclosed Circuit Diagram of the board you will see that on pin 4 of U1
there is a pull up resistor to +5 volts (PU3) and also a resistor (R6) in series with a
diode (D4) going to switch SW1 pin 10. The other side of pin 10 is connected to
GND. It is therefore possible to simulate a Device Input Leakage problem with this
circuit. To do this though, we must first enable a Voltage Test to be performed on
pin 4 of device U1.
To enable this test, Edit device U1 (click with the right mouse button) and select
Properties - Pins. Type in 4 in the "Pin X of 14" box and enable a voltage test to be
performed on this pin. You will see that the values in the Lower and Upper Limit
boxes are set to zero. You can either set the required limits in these fields or allow
the system to learn the actual voltage on this pin.
Let us do the latter - i.e. allow the system to learn voltages. Leave the values set in
the two limits boxes to zero and return to the General tab. Once in the main Edit
Device Dialog box select DISCARD PROGRAM (to remove the original
programmed information) and OK out of the Edit box.
Issue 1.5
Reselect device U1 using left mouse button, to program and repeat the above
verification process - you will see the message that pin 4 failed the first voltage test
and then subsequently modified the limits. As before the device will turn Blue.
To verify what the system has learnt on pin 4, re-edit the device, select the Pins tab
and observe the values inserted into the voltage limits for pin 4. These will be +/-
0.5 volts either side of the learnt value.
Once a device has turned BLUE the device status changes to PROGRAMMED. If
a Programmed device is selected with the left mouse button the device will be
tested and if a failure occurs the information is displayed in the white Test Status
Box. To change any information the Edit Device Dialog Box must be selected and
the changes made, or the programmed information Discarded.
EZ Mode
Select the Options Menu and select EZ Mode Setup. This enables a Dialog Box
allowing you to define the EZ modes. Enable the EZ Mode Check box but do NOT
enable any of the additional Check boxes as shown below:-
EZ Mode (analogous to "Easy" Mode) allows the system to make it's own changes
to the device's parameters depending upon the "failure" mode recognised - these
changes include applying Pull-up resistors, reducing Test Rate etc. but are
ALWAYS displayed in the Test Status box at the bottom of the screen.
Refer to the Help Text for more information on EZ Mode,
Repeat the above process for the remaining devices with EZ Mode enabled.
Cross-Compilation
Devices U4 and U5 will require Cross-Compilation.
This process occurs when a device has external shorts on the board, resulting in the
device operating in a different manner to the original library program. When this
occurs, a library program is selected (either the "Generic", or original basic
program, or one selected from a Dialog Box if EZ mode is not enabled) and the
input stimulus is modified to conform to the device’s shorting pattern. This
modified program is then applied to the device and the output responses of the
device are recorded. This is the process of "Cross Compilation" i.e. a device
program has been Cross-linked to an existing program and then Compiled into a
different format than the original program.
Issue 1.5
Once a program has been Cross-Compiled it is reapplied to the device to verify the
program for consistency - if the program is repeatable the device will turn Blue
(with cross-hatching). If it is not, it may require Editing of some of the test
parameters as explained above.
For more information refer to the PinPoint Help on Cross-Compilation.
Guarding
U5
When programming U5 you will notice Warning Messages in the Test Status Box
on the bottom of the screen. Whenever warning messages are displayed READ
THEM. The message displayed will indicate that pins 8 and 9 didn’t sense a High
and Low respectively - this means that the device output pins did not toggle. Even
though the device has turned Blue (indicating consistency) the Warning
Messages indicate that all may not be well !!

Cross Compiling and Guarding are
covered EXTENSIVELY in the PinPoint
Training Courses.
SeaWave
We can look at the "Timing" waveform generated by the above "Cross

Compilation" process.
Right click over U5 and select View > SeaWave (Figure 4.3).
Figure 4.3 Select SeaWave Menu
This will enable SeaWave to generate the timing - type waveform for this device.
Scroll to the right and see that pins 8 and 9 are NOT changing state.
Issue 1.5

White lines represent inputs, Green
lines represent outputs and Yellow
lines represent shorted pins. Look at
pins 2 and 6 (input shorted to output)
For more information refer to the PinPoint Help on SeaWave.
Look at the circuit diagram of the Tutorial Board for device U5 and you will notice
that there is a feedback circuit affecting the device. This feedback circuit needs to
be "broken" for correct operation of U5. This is achieved by connecting a Guard,
programmed to logic 0, to device U1 pin 9 (See the Help Text for more information
on Guarding).
To add this guard, edit device U5 (click with the right mouse button) and select
Properties - Guards.
Figure 4.4 Add Guards Dialog Box
From this Guard Setup Dialog box select Add and then set Guard 1; State Low;
Connected to Device U1 Pin 9. You will see the text displayed in the Guard List
box once the OK button is selected (See Figure 4.4).
Select the General tab from the Edit Device Dialog Box.
Issue 1.5
Because device U5 was Blue (yet cross-compiled incorrectly!!) the program must
first be removed from the Database by selecting Discard Program and then
restarting the verification procedure. This time the program is Cross-Compiled
there should be no Warning Messages.
Re-generate SeaWave again and check that pins 8 and 9 are now toggling.
U8
Device U8 is a standard library configuration and therefore will pass the standard
program. However this may not occur for two reasons:-
The Device will intermittently fail the Voltage Test. This is because the input pins
are connected to a high impedance bus and are therefore floating. This floating
level is close to the input-switching threshold of the device and therefore may start
it oscillating. This oscillation will be seen on the supply pins and result in a
Voltage failure. To overcome this problem Edit the Device and turn on the 2K2
+5V Voltage Test Pull Up resisters to bias the input pins away from the switching
threshold (see Figure 4.5).
Figure 4.5 Device Settings – Voltage Pull-up Termination
Because of the high impedance of the Data Busses, it may be necessary to Edit the
device and reduce the Test Rate. This is to allow time for the pins to reach a true
Tri-State level.
U9
Again U9 is a standard library configuration and therefore does not require cross-
compilation. Again however, the program will not work correctly, even with
reducing the Test Rate etc.
Refer to the circuit diagram and you will see that devices U8 and U9 are connected
to the same Bus - thus while testing U9, the outputs of U8 are interfering with, or
loading, the outputs of U9. This again requires guarding to overcome the problem
We will leave it to you to solve this problem!
(See Help Text for information on Guarding).
Issue 1.5
U10
Device U10 is an analog switch, and is a standard library configuration. It may be

necessary to reduce the test rate to 1MHz in order to test this device.
If you have the VI Test System card fitted in your system continue to Chapter 4.2
(VI and Functional Tests), otherwise Jump to Chapter 4.3 (Operator Messages).
Issue 1.5
4.2 VI and Fun ction a l

As stated in the VI Instrument Mode the function of the VI system is to apply a
controlled alternating voltage (usually a Sine Wave) into a circuit node and to
display, and record if required, the Voltage and Current responses in a variety of
formats.
We have already defined the required Tutorial Board Layout and programmed the
board ICs and the next stage is to program the discrete components on the board
and, if required add VI Tests to existing programmed devices.
Before starting to verify devices some initial conditions must be satisfied:-
Set the Global Tolerance to 20% by selecting the Icon
Select the Contact Detection from the Options Menu and ensure that -5.5 Volt bias
is selected. Refer to Contacts Bias in the Help Text for more details.
Select Auto VF Setting from the Option Menu. This allows you to select the
Voltages and Frequencies to be applied when learning / testing using the InterV3.
Ensure that ALL Voltage and Frequency ranges are enabled and that the Perform
Stability Check is enabled. Refer to Auto VF Settings in the Help Text for more
details.
At the moment all the discrete devices are shown in black, as they have not yet
been verified.
Resistors
Select device R1 to program first by clicking on the device with the left mouse
button. You will now be prompted to use the Probe (Green Probe). The device R1
will turn Yellow and the mouse pointer will be situated over pin 1 of the device,
waiting for the Probe to be attached. Once electrical contact is made the VI sub-
system starts the learn / verify process, and will prompt you with an audible tone
and text information in the white Test Status Box at the bottom of the screen to
move to the next pin of the device, until all pins have been learnt.
If this process is good for ALL pins the device will turn BLUE indicating that the
device has been successfully programmed. If, however any pin fails or is
intermittent (seen by either F or I in the Test Status Box) a VI Test Failed dialog
box is opened allowing you to evaluate the problem. If a failure occurs the device
will turn either RED (ALL pins failing) or MAUVE (only some pins failing)
indicating that the device has not been successfully programmed.
Review the Device Properties (right mouse over the device) and see the VI
Signatures for pin 1 (see Figure 4.6).
Issue 1.5
Figure 4.6 Edit Device Dialog Box – View VI Signatures
Continue to program the remaining Resistors.
Resistor Packs
You will notice that access to the pins of RN1 is very difficult from the component
side of the board. It is possible to tell the system that you wish to probe from the
underside of the board. To do this you need to edit the device Properties - you will
see that there is a Probe Underside option that needs to be selected within the
dialog box (see Figure 4.7).
Figure 4.7 Edit Device Dialog Box – Probe Underside
Issue 1.5
It would be good practice at this stage to also set the other devices that are not
accessible from the component side of the board, to be probed from the underside.
Now we can begin by selecting RN1 to program. You will notice that the now the
board display will flip to show the solder-side, and the mouse pointer will be
positioned over the pin to which the probe must be attached (RN1 pin 1).
Repeat the above process for device RN2. However now introduce a failure by
temporally removing the Probe during a learn process. This will open the VI Test
Failed dialog box allowing you to interpret the failures. Note the Pass / Fail
indicators as you place and remove the Probe and also note the Tolerance banding
when the View Tolerance "check box" is enabled. You may adjust the tolerance
settings if necessary, or even remove test ranges that are not suitable for the device
pin and then re-test.
Once you are conversant with the VI Test Failed dialog box, re-learn the signatures
for RN2 by re-selecting the device with the left mouse button.
See Help Text for more details of VI Test Failures.
If the device is BLUE it is necessary to Discard Traces if you wish to re-learn the
device. To Discard the Traces select the device with the RIGHT Mouse button to
open the Properties dialog box. Select Discard Traces with the left mouse button
and then exit by selecting the OK button.
Once a device has turned BLUE the device status changes to PROGRAMMED. If
a Programmed device is selected with the left mouse button the learnt traces will be
tested and if a failure occurs the VI Test Failed "dialog box" is opened.
Contacts
If NO contact is recognised, as the amount of leakage current drawn by the device

is negligible - press the keyboard ESC key to open the Edit Test Parameters dialog
box and accept the fact that no contact test can be performed. Because there is now
no capability for the system to determine when the test probe is applied or
removed, messages to attach and remove the probes will now be issued. Press any
key when the message instruction has been complied with.
Repeat the above process for the remaining devices.
Integrated VI and Functional Tests
It is possible to apply VI Tests to Integrated Circuits as well as discrete devices

provided you have Driver Multiplexers / Matrix Cards fitted to your system.
For some devices it may be beneficial to perform both Digital and VI testing e.g.
Monostables with timing components fitted.
We will apply VI tests to device U3.
Select U3 with the RIGHT mouse button and select Properties. In the General Tab
enable the VI check box and OK from the Dialog box. U3 will have changed to
RED indicating the device is no longer fully programmed.
Re-program U3 and notice that the VI tests are performed after the Function tests
are completed.
Issue 1.5
4.3 Op er ator Me s sag e s

Board Text
In order to assist the operator during the testing of further boards, you can provide
additional information as operator text, which will be displayed as required.
We will add an instruction to the operator as a reminder of the Power Connections

and the switch settings to be set on the board before testing begins.
This text is added by positioning the mouse pointer anywhere on the board (but not
over a device or text) and clicking the right mouse button and select Pre-Text (see
Figure 4.8).
Figure 4.8 Board Pre-Text Menu
Enter the operator instructions below, and click on OK.
Connect the Power Lead from the PinPoint to the Tutorial Board using the lead
provided.
SW1 should be set as follows:

1 ON
2 ON
3 ON
4 ON
5 OFF
6 OFF

This message will only be displayed in
a TEST Mode.
Issue 1.5
Device Text
We can also add operator help text prior to, or after, testing an individual device.
For example it may be necessary to close a switch prior to testing a device (e.g.
U2) and then to open the switch after the test. This may be achieved in the
following manner: -
This text is input by positioning the mouse pointer over device U2, clicking with
the right mouse button and then selecting Pre-Text (see Figure 4.9).
Figure 4.9 Device Pre-Text Menu
Enter the operator instructions, and click on OK.
CLOSE SWITCH SW1 CONTACT NO 2
Now select Post-Text in the same way and enter the text to be displayed.
OPEN SWITCH SW1 CONTACT NO 2

The above messages will be displayed
in a dialog box in the centre of the
screen when testing U2.
VI and Functional
If you are performing both Functional and VI testing you can add Operator text
between the two types of test (Mid Text) - this is to allow changes to the set-up (if
required).
Issue 1.5
4.4 T e s tF low Su mma r y

We can also change the order in which devices will be tested.
The order in which devices will be tested is currently the same order in which the
devices were originally placed during board layout.
The TestFlow (or Execution Order) is used in TEST BOARD to guide the test
operator through the required test sequence when in the AUTO mode of operation.
Within the Test Flow there can be multiple starting points, known as "Symptom
Entry Points" as well as conditional branches depending upon whether a device
passes or fails.
The TestFlow is displayed as a "Flow Diagram" which can be edited or modified to

the required flow.
The Test Flow is originally created as part of the Board Editor function and the
default flow is the same order as the devices were originally placed on the board.
There are two basic modes of TestFlow:-
DEFAULT
CUSTOM
1) DEFAULT
The Default mode is generated as part of the DEFINE BOARD Editor. The
order that devices are "fetched" from the PinPoint Library forms the
DEFAULT TestFlow. It is therefore important to define the Default TestFlow
prior to laying out the devices on the Board.

If a Device is deleted and then re-
added in the Define Board Editor
this device is initially removed
from the Default TestFlow and
then re-added to the bottom of it.
If a device is required to remain
in the same location in the
TestFlow List the device should
be "RE-FETCHED" from the
library.
The DEFAULT TestFlow is used in both NetGen and TrakTest applications.
Issue 1.5
2) CUSTOM
A Custom TestFlow will be created from the Default TestFlow. This is done by
Editing the TestFlow and is explained in the Custom TestFlow section.
The TestFlow display consists of 6 specific regions:-
1) MENU COMMAND BAR
The Menu Command Bar allows you to select the required Command or
Function.
2) ICONS (MODE CONTROL COMMANDS)
Associated with the TestFlow are a number of "Push Button" ICONS situated
directly beneath the MENU COMMAND Bar at the top of the screen. To
observe the function of these ICONS hover the mouse pointer over the ICON
to display the "TOOL TIP" help summary.
Some of the functions of these ICONS are duplicated by the MENU

COMMANDS.
3) TEST FLOW GRAPHICS DISPLAY AREA
Figure 4.10 TestFlow Graphics
The Graphics Area (see Figure 4.10) is used to display the TestFlow Graphics
and is bounded by horizontal and vertical "Scroll Bars" to centre the required
area of the Flow Chart on the screen.
Issue 1.5
4) FLOW CHART ELEMENTS
Figure 4.11 Flow Chart Elements
This is situated on the left of the screen are the fundamental Elements that can
be inserted into the Flow Diagram. These elements can be "dragged" onto the
Graphics Area in order to insert them into the required area of the Flow Chart.
5) STATUS AREA
This is situated in the Grey area at the bottom of the screen. It contains relevant
Status information about the TestFlow Function selected.
6) TILE SELECTORS
Situated at the bottom of the screen to select a different Program Studio

Applications.
Issue 1.5
4.5 T e s tF low Ex erc is e

In Program Studio > Program Board, click on the TestFlow tab located on the
upper left of the screen. Use the Zoom tools to zoom in on the flow chart that
is displayed. Initially a flow chart called Unknown Symptoms is displayed with
only two elements present, "Start Test" and "End of Test".
We need to reset the TestFlow chart in order to see which devices are available for
testing.
Click the Reset Flow Chart Icon to display the Reset TestFlow window. Two
sort options are available - they are Layout Options and Sorting Options.
Layout Options
Layout Options are concerned with the page layout, depending on the number of
components that are to be tested, will determine which option is chosen. A Single
Vertical sort will display all of the components to be tested in a single vertical
column, devices are tested from top to bottom, twenty-two devices per page. If
there are more than twenty-two devices to be tested, access to devices on other
pages are accessible using the Page-Up and Page-Down keys. Medium Page
Optimisation will display the device elements in three columns per page and a
Compact Page Optimisation will display the device elements in five columns per
page.
Sorting Options
Sorting Options are concerned with sorting the device elements in formatted orders
for testing. If “None” is selected the TestFlow will display the elements in the
order they were called from the PinPoint Libraries when the board was laid out in
Define Board. This is known as the Default TestFlow. “Package Size Only” will
sort the devices elements into package sizes and display them as smallest package
at the top and largest package at the bottom. Any devices that are tested using a
probe only will appear at the end of the TestFlow. Sorting by package size will
helps with the overall running of the program in Test Board. The operator is not
constantly asked to switch between different test clip sizes. This works particularly
well if the devices on the board are all the same package type i.e. DIL. If however,
the packages on the board are a mixture of package types they will need different
test clips for each package type. This is where a sort by Package Size And Clip
Type would be used.
Select Single Vertical Row Sort and Package Size And Clip Type Sort. The
TestFlow will be sorted and displayed. This is the order in which the operator will
be guided to test the board when auto is selected in Test Board.
Custom TestFlow
The TestFlow can be edited manually into any order that is required. For example
it may not be necessary for the whole board to be tested. If the board has a known
fault symptom it is possible to test the board in the area associated with the fault
i.e. the board has a memory fault, so we only need to test the area of the board that
is associated with memory. This can be achieved by staring the tests at Mid Entry
Point or by setting up a second flow chart that only test the devices concerned.
Issue 1.5
Mid Entry Point
Add a Mid Entry Point by selecting the Mid Entry Point icon from the
left-hand window and dragging it to the desired position.
As an example we will place a Mid Entry Point between U4 & U5. First zoom into
the area of U4 & U5. With the left mouse button select the connecting wire
between the devices; it will be highlighted blue, now press the delete key to
remove this wire.
Pick the Mid Entry Point Icon and drag it to a position between U4 & U5. You will
be prompted to enter a name for the Mid Entry Point, type "MID1". To move the
position of the Mid Entry Element select the Element by clicking it once with the
left mouse button - the element will be highlighted blue to indicate that it has been
selected. Click and drag the element to the required position. Place it below U4,
leaving a gap to place a wire later. Now select the wire between U5 & U8 and
delete it. Select U5 and drag it down one position so that there is now a gap
between U5 and the Mid Entry Element. At the bottom of the U4 element will be a
red box with a cross in it, click once with the right mouse button and select Place
Wire. Click left mouse button on the red box and move the mouse point to the top
red box of the Mid Entry Element and click again. A wire has now been placed
between the two points. Place a wire between the Mid Entry Element & U5 and
one between U5 & U8 to complete the connectivity of the TestFlow.
Add Flowchart
It is also possible to create a completely separate Symptom TestFlow for selection
within a Board Test by selecting the Start Test Icon and dragging it to
the desired area on the page. You will be prompted to give the Start Test a name,
enter "20 Pin Devices". To add device tests to this flow chart, simply click and
drag the Device Test Icon , drop it below the Start Test icon that you have
just placed. You will now be prompted to select the device reference number for
the device test and the number of times the test is to be performed. Enter "U8" as
the device reference number and "1" for the number of tests to be performed. Click
OK. Add a second Device Test for U9 and then drag and drop an End Test Icon
below U9. Now, click right mouse and select Place Wire. Place a wire
between each element of the new flow chart, so that there is continuous flow for
the whole chart. This new Symptom TestFlow, if selected in Test Board, will only
test the devices contained in that flow chart i.e. U8 & U9.
Issue 1.5
Connectors
A Connector is a junction point where two entries flow into one output. This is
used in situations where a "Jump on Fail" from a Device Test to another part of the
TestFlow is required. First, click and drag the "End Test" Icon down a couple of
places on the flow chart "Unknown Symptoms". Click and drag a Connector Icon
to just below the last element of that flow chart. If the Connector icon is
dropped in the right area it will make connection with the wire that was previously
connecting it to the "End Test" Icon" (no red boxes visible on the last element).
You will be prompted to name the connector element - call it "EOT" (End Of Test).
Connect a wire between the connector and the "End Test" element. It is now
possible to define a "Jump on Fail" to this connector.
Place a wire from the right hand blue box of U9 to the right hand blue box of the
connector. If U9 fails during Test Board the program will jump to the connector
position, in this case to the end of the test procedure.

It is possible to jump to any position
in a flow chart. It is also possible to
jump to a position on a separate flow
chart. It is possible for several
elements to jump to the same position
and an individual element can only
jump to one position.
On/Off Page Links
As the names suggest the On/Off page links allow us to create connectivity
between pages. To create a connection between pages you must first place an Off
Page Link . This link will be wired to the last element to be tested on the
page and requires a name (page numbers can be used as a guide). Once an Off Page
Link has been created an On Page Link can be placed - this will require a
link to an Off Page Link i.e. Page One.
Operator Text
It is possible to place Operator Instructions at any point in the TestFlow. Just drag
and drop the Operator Message at the desired position and wire as you
would a Device Test element. Suffice to say it is not possible to "Jump on Fail"
with Operator Text elements.
Issue 1.5
Subroutines
Where a series of tests are repeated through out a TestFlow sequence it would be
desirable to make a call to those tests without having to place all the elements each
time they are required. In this case we can create place a Subroutine Element
that will require a name. Once a Subroutine element has been placed it
can be wired to as any other element. The subroutine elements will be stored on a
separate page specific to that subroutine. To edit the elements contained within the
subroutine, we need to PUSH the Subroutine - click right mouse button on the
subroutine and select "Push Subroutine". This will take us to the Flow Chart for the
Subroutine. Place any elements that are required for the subroutine in this area and
wire them together. To return to the main TestFlow pages click right mouse button
and select "Pop Subroutine".
If you have the Analog Option fitted, continue to Chapter 4.6 (Analog Testing)
otherwise jump to Chapter 4.7 (Board Properties).
Issue 1.5
4.6 An a log Te s ting

Analog Testing is set up from within the TestFlow application. To do this first
"drag" the "Subroutine" icon onto the TestFlow page. Each Subroutine
Element will require a name. Once a Subroutine element has been placed it can be
wired to as any other element. The subroutine elements will be stored on a separate
page specific to that subroutine. To edit the elements contained within the
subroutine, we need to PUSH the Subroutine - click right mouse button on the
subroutine and select "Push Subroutine". This will take us to the Flow Chart for the
Subroutine. Place any elements that are required for the subroutine in this area and
wire them together. To return to the main TestFlow pages click right mouse button
and select "Pop Subroutine".
Once the Subroutine has been "Pushed" you will notice that additional Analog
Elements are displayed on the left side of the screen (see Figure 4.12).
Figure 4.12 Analog Flow Chart Elements
These Analog Elements can be dragged to the TestFlow area in the same way as all
the other Test elements.
Although "Analog Testing" is defined in detail during the Advanced Training

Courses held at Diagnosys we will generate a simple Analog TestFlow now
consisting of basic usage of the DMM and Counter / Timer Instruments.
The fundamental Elements required to perform an Analog Test are:-
a) Message Box to inform the Test Operator of where to attach the Instrument
leads.
b) Relevant Instrument Element in order to perform the required task.
c) Limits Check in order to verify the correct response.
Issue 1.5
1) Generate Subroutine.
a) From the main TestFlow Page "drag" the Subroutine Element onto the
TestFlow page.
b) Enter the required name (Analog Test) in the corresponding Edit Field.
c) Position the "Analog Test" Subroutine Element at the end of the TestFlow (it
will be necessary to move the "End Test" Element in order to position the
Subroutine Element correctly.)
d) Complete the "wiring" of the Subroutine Element into the new TestFlow.
2) Modify Subroutine to Add DMM Measurement.
a) Drag the Power Supply Element onto the TestFlow Page. Select "Turn Power
Supply On" from the Power Supply Control section.
b) Drag a Message Box Element onto the page and enter the following Operator
Message "Connect DMM- to Device U1 Pin 7 and DMM+ to Device U1 Pin
14". (We are going to measure the Supply Voltage to Device U1).
OK from the dialog box and position the Element beneath the Power Supply
Element allowing sufficient space for wiring between the two elements. (We
will complete the "wiring" at the end of placing the Elements).
c) Drag a DMM Element onto the page. Select Measurement Type = DC Volts:
Range = 20V: Rate = 5 cps.: Pre-Measurement Delay = 2000.
OK from the dialog box and position the Element beneath the Power Supply
Element
d) Drag the Limits Check Element onto the page. Change the Upper Limits to
5.25 and the Lower Limits to 4.75 and enter "Volts" into the Units Edit Field.
Enter, if required, Operator and Fail Text messages - these will be displayed in
the Test Results Log. Finally enable "No Branch on Fail" (if we enabled
"Branch on Fail" we would have to complete this additional "Branch" of the
TestFlow).
3) Add Counter / Timer Measurement.
a) Drag a Message Box Element onto the page and enter the following Operator
Message "Connect Counter / Timer A to U1 Pin 13 and Close Switch S1 / 1".
(We are going to measure the Oscillator Frequency).
OK from the dialog box and position the Element beneath the Limits Check
Element.
Issue 1.5
b) Drag a Counter / Timer Element onto the page. Select Measurement Type =
Frequency: Input Control = Positive Trigger @ 1.8 Volts: Select "Setup and
Measure". OK from the dialog box and position the Element beneath the
Message Box.
c) Drag the Calculator Element onto the page. We wish to change the units of
measurement from Hz to MHz and therefore we need to add the following
information:-
Resultant = Test.Result (this is the Variable that stores the actual measurement
value).
Equals = Test.Result / 1000000 (divide the value of Test.Result by

1,000,000).
d) Drag the Limits Check Element onto the page. Change the Upper Limits to
10.5 and the Lower Limits to 9.5 and enter "MHz" into the Units Edit Field
and enter, if required, Operator and Fail Text messages. Finally enable "No
Branch on Fail".
e) Finally drag the Power Supply Element onto the TestFlow Page and select
"Turn All Power Supplies Off".
4) Complete the Subroutine.
We must now complete the Subroutine.
a) Line up the above-placed Elements and connect "wires" between them.
b) Ensure that the "Compile Status" at the bottom right of the screen indicates No
Errors . If there are , then these need to be corrected (see Compile
Status for details).
c) The Subroutine TestFlow should be as shown below in figure 4.13
Issue 1.5
Figure 4.13 Analog Flow Example
5) Debug the Subroutine.
Finally we must now verify that the Subroutine actually performs as expected.
a) Select the "Turn On Power Supplies Element (left mouse button) and then
insert a "Breakpoint" onto this Element. This will allow the TestFlow to
stop on this element and then allow you "single step" through the remainder of
the flow.
b) Ensure that the Tutorial Board is connected to the PinPoint UUT Power
supply.
Issue 1.5
c) Select the Start Debug icon and select "Analog Test" from the resulting
Dialog box. Once the system stops at the Power Supply Element for can
"single step" through the remainder of the flow by selecting the "Step Over
icon or Function Key F10. The results of the testing are displayed in the
white box area at the bottom of the screen.
d) You are able to terminate the Debug process at any time by selecting the "Stop
Debug" icon or Shift+F5.
6) Export / Import Subroutines.

Having verified that the Subroutine is working correctly, it can be exported for use
within other programs where the same functionality is required. To Export a
Subroutine go to the TestFlow Manager dialog box.
This can be located from the Utilities Menu
or right mouse in the graphics display area
Figure 4.14 TestFlow Manager
From the Test Flow Manager dialog box select the required Subroutine for
exporting (ie Analog Test) and then the "Export" button - enter the required
descriptive information in the Export Subroutine dialog box (eg Analog Counter /
Timer Measurement).
Issue 1.5
Figure 4.15 Export Subroutine
Once a Subroutine has been Exported, it can be Imported into another TestFlow
program by simply selecting the Import button.
As specified above, "Analog Testing" is defined in more detail during the

Advanced Training Courses held at Diagnosys.
Issue 1.5
4.7 Boa rd P roper ties

When you have completed programming your board, position the mouse pointer
anywhere on the board (except over a device or text) and click the right button,
select Properties. The Dialog Box allows you to enter the following properties.
General Tab
Board Name
The program we are working on will be saved to the disk drive using a
supplied name - however we may wish to equate a different / longer Board
Name to the program. The limit of this Long Board Name is 20 characters.
Program Version.
This allows for Program Issue Control
Release Board for Testing.
Whilst a board is being programmed you may not wish anyone to have access
to it from within the Board Test Mode. Once it is completed, selecting the
Release Board check box allows access to this program by the Test Board
Application.
There are other Check Box settings, but refer to the Help Text for more details of
these.
Power Supply Tab
This allows you to alter the settings for the UUT (Unit-Under-Test) Power Supply
Refer to the Help Text for more details on the Board Properties Dialog Box
Switches Tab
Refer to the Help Text for more details of these
Enter in "PinPoint Demo Board" in the Board Name box, "1.0" into the Version
box and select the Release Board check box.
Once you have completed these OK out of this dialog box.
Issue 1.5
4.8 S imu la ted Te s t Mod e

Once the board program is completed it should be verified in a Simulated Test
Mode. To enter this mode press keyboard Function key F5, or the Simulate Test
Mode Icon . You will be guided through the Operator Entry Selection,
Operator Help Text and the TestFlow you have just defined.
If the TestFlow still has devices in it that are either "dummies" or have not been
completely programmed you will be asked if you wish to remove these devices
from the Execution Order.
This Simulated Test Mode is not designed to give the operator information relating
to Device Failures but purely to verify things like the ease of Guarding, Help
Messages, Execution Order etc.
Function Keys F5, F7 and F8 are active during this Simulated Test mode to allow
you to Abort (F5 or ) , Step the Next Device (F7 or ), or to return to the
Previous Device (F8 or ).
There are several reasons which may cause one or more of the verify operations to
fail.
VOLTAGE FAILURE
The limits set for voltage measurements on power supply pins in library devices is
4.75 V to 5.25 V for Vcc and -0.150 V to + 0.150 V for GND.
If the 0 V measurement fails out of limits, it is likely that the ground connection
point chosen on the board has a (relatively) high resistance to the device or system
0V connection, or that there is some oscillation on the board.
If the Vcc measurement fails out of limits, it is likely that either, the connection
point chosen on the board has a (relatively) high resistance to the device or system
connection, or that the 5 V sense lines are not connected between the PinPoint
Power Supply and the board. Also check for oscillation.
OPENS FAILURE
An Opens Test is performed on Input pins only. The system applies a Pull Up
resistor, followed by a Pull Down Resistor, followed by a Tri-State bias to the
Device, and pins that follow the resistor combinations are classed as OPEN. During
the programming phase, pins that are detected as OPEN have the Opens test (for
that pin only) disabled e.g. Pin 13 of device U1.
If, after the programming phase, pins are detected to be OPEN, a failure is
reported.
Opens failures may be as a result of an oscillator connected to a device pin, or

where the pin is connected to a Tri-State or Open-Collector output.
It is possible to Edit the device to disable the Opens Test from individual pins.
Issue 1.5
SHORTS FAILURE
The first time a device is verified the "shorts" information is learned. This
information is then used to control the functional tests carried out on the device.
Additional shorts, or shorts missing from the original shorting pattern will be
detected as a SHORTS Failure.
If it is required to relearn a different shorting pattern (e.g. due to an error in

clipping the device) then the program MUST be discarded and then reprogrammed.
FUNCTIONAL FAILURE
The most common reason for a device failing a functional verification is that there
are inconsistencies between the repeat tests.
These are mainly due to spurious signals appearing at the device due to incorrect
guarding, oscillators on the board, or poor Power Supply distribution to the board.
The default setting in the OPTIONS / DEVICE PROGRAM OPTIONS menu is to

perform the functional test five times and confirm that the device passes the test
correctly each time.
Once you have completed the Simulated Test Mode you will be returned to the
Program Board Mode.
Issue 1.5
4.9 N e tL is t G ene ra to r
The next module we will use is NetList Generator. Select the NetGen tab from
within the Program Studio. The function of the NetList Generator is to learn the
interconnections between the devices on the board. This could be for a number of
reasons but there are two main ones:-
Learn Connections in order to find out how to guard busses.
Learn Connections in order to generate a circuit diagram of your board.
From the OPTIONS Menu bar (Figure 4.14) ensure that Prompt Nodes Found is
ticked (if there is no tick against it add it by clicking over the command).
Figure 4.16 NetList Generator Options Menu
This will ensure that when devices interconnect nodes are found that they will be
displayed.
From the UTILITIES Menu bar (Figure 4.15) select NetGen Board.
Figure 4.17 NetList Generator Utilities Menu
The system will guide you through the NetList Generator process.
First you will be prompted to clip over the largest package size device (in this case
U4) with a test clip positioned in A (referred to as the Source Clip).
It is possible to use multiple Source clips but at this stage we will only use one to
keep the process simple.
Issue 1.5
You will be prompted to add a second Source clip to U8 or U9. The pop up
information bar will display:-
‘Attached clip to U8 (U9) {F3 go Dest} Esc/Footswitch to Abort’.
Press F3 to select destination clip.
You will be prompted to use a 14 DIL clip. Click left mouse button on the grey box
and clip on the device indicated in yellow. You will be informed that there are no
connections between U1 and U4.
Press a key to continue and you will then be prompted to remove the clip over U1
and to replace it over U2 - again you will be informed that there are no connections
between these devices.
Now continue onto device U3. This time you will see connections between these
two devices, and therefore a dialog box, defining the inter-connections will appear.
Verify the listed connections against the circuit diagram.
Continue moving the Destination Clip until all devices have been clipped.
When prompted to connect to the discrete devices (or where there is no test clip
available) you will be prompted to use the Strike Probe.
Strike Probe
The Strike Probe is designed to be used in situations where clip access is difficult
(or impossible), and also when attempting to access two large package devices, the
sum of which, exceed the pin-count of the PinPoint System.
When the Strike Probe has been selected, wipe the pins on both sides of the device
with the Strike Probe (taking care not to damage the device or the PCB tracking) or
until continuity is recognised between the two devices. Once continuity is
recognised, you will be prompted to Probe each device pin in turn until all the pins
have been probed and the View NetGen Results dialog box is opened showing the
inter-connections, if any.
When the inter-connectivity between U4 and all other devices has been learnt
device U4 will turn Blue, indicating that all pins of the device have been assigned a
node.
You will then be prompted to remove the Source Clip from U4 and to replace it
over U8 (the first 20-pin package in the execution order).
Follow the instructions above for the Destination Clip until asked to clip over U3.
Strike Override
When asked to clip over U3 with the Destination Clip, press keyboard Function
Key F3 - this selects the Strike Probe for use.
When the Strike Probe has been selected, wipe the pins on both sides of device U3
with the Strike Probe (taking care not to damage the device or the PCB tracking) or
until continuity is recognised between the two devices. Once continuity is
recognised, you will be prompted to Probe each device pin in turn until all the pins
Issue 1.5
have been probed and the View NetGen Results dialog box is opened showing the
inter-connections.
The operation will return to the default Clip mode after Strike Probe is completed
Continue until all devices have been completed.

1) The Execution Order for the
NetGen process can be modified
by selecting EXE Order Menu
followed by EDIT.
2) The status information, or Source
/ Destination table, defining
which combinations of clipping
have been carried out can be
saved (and recovered) by EXE
Order SAVE and OPEN
respectively. This allows you to
stop the NetGen process prior to
the end and return at a later date
to complete the process from
where you exited.
3) When NetList Generator has been
performed on a device, it is
possible to view the nets by
means of Device Edit and then
View Nets. This displays the
connectivity between the selected
device and all others.
WireList
It is also possible to create and view a complete WireList of the board by selecting
File and Export from the Menu bar.
Select file type as WireList and enter the required path and filename e.g. Directory
Pinpoint/ TPD and filename as DEMO.WRL
You will be asked if you want to view this WireList file. Select Yes and observe
the contents - an example is shown below.
Sample WIRELIST FILE
[00034] N34
U4 10 Q7 O 74F269
U6 9 I7 I PAL16R8
U9 9 A8 IOT 74LS245
[00035] N35
U8 2 A1 IOT 74LS245
U9 18 B1 IOT 74LS245
Issue 1.5
Important points to note are:-
Node N34.
This defines a connection between an output (U4 pin 10) and an IOT pin (U9 pin
9).
This would not be possible under Design Rules unless the IOT Pin was
programmed to be an Input. (See the Circuit Diagram for confirmation).
Node N35.
Here there are two IOT pins connected together. This is an immediate indication
that Guarding is required between these two devices.
Modifying NetLists.
There are two possible ways of modifying / correcting NetLists generated by the
PinPoint.
It is possible to modify this WireList file and re-import the changes made.
Edit the Device Properties and make the modifications within the Nets Tab. You
can Add Connections to a selected Net or separate Nets that are combined
incorrectly.
If you have the optional Schematic Generating Software continue to Chapter 4.10,
otherwise jump to Chapter 5 (Libraries).
Issue 1.5
4.10 S ch e ma tic G ene ra tion

This section can only be completed if the Schematic option is installed on you
PinPoint II Test System.
Once the device interconnections have been learnt, these interconnections together
with the Graphic symbols derived from the PinPoint Libraries can easily be
displayed as a circuit diagram.
The main features of the Schematic Generation package are listed blow.
Rapid Generation
The circuit diagram is generated in a matter of seconds.
The circuit diagram can be presented on multiple pages or on a single page

dependent upon the Page Settings.
Nets going across pages are labelled and it is possible to navigate easily between
these pages by:-
a) "Double Click" on the Red Arrow associated with the Net / Buss name.
b) You may scroll or navigate through the pages of the Schematic by selecting the
keys situated on the lower left of the screen or jump to a selected page by
"Double Click" within the "Page x of y" box adjacent to the keys.
It is possible to review the Net "Properties" (net name and connectivity) by

selecting the required Net with the left mouse button and then using the right
mouse button to display the properties.
There is the ability to create "Busses" or "rename" nets by editing information

within the NETLIST STEERING Dialog Box
Symbols of "unknown" devices are automatically generated. Pins defined as inputs

are positioned on the left of the symbol and outputs on the right.
Hard Copy Print out Capability.
The displayed circuit diagram can be printed to any Windows - compatible printer
or plotter.
Issue 1.5
Industry Standard Format
The format of both the Net List and the Schematic are generated in an industry
standard EDIF format. This allows the Schematic to be imported by other CAD
packages for company standardisation or generation of other facilities.

Although the output from the PinPoint
is in an EDIF format, not all CAD
packages can import EDIF designs.
Furthermore different CAD packages
may utilise different EDIF commands
to perform the same function - thus
we cannot guarantee that the EDIF
output that is generated on the
PinPoint system can be imported to
other CAD packages without
modification.
PAGE SET-UP
This Dialog Box allows you to define the required Page parameters for the
Schematic.
You can select the units in either Inches (sizes A to E) or Millimetres (sizes A0 to
A4) or define a Custom page size. You can also select either "Portrait" or
"Landscape" page orientation.
NETLIST STEERING
Incorporated into the Schematic Generator is the capability to create "Busses" and
to rename certain nodes (e.g. rename USER 1 Power Net to +24 V) to enable the
"Schematic Viewer" to generate schematics that incorporate these Busses and
renamed nets.
In order to generate these Busses etc. it is necessary to create a NetList Steering

File.

1) The NetList Steering File is a
replacement to the *.PAN File
used in previous versions of this
Schematic Software. When
OPENing a Version 3.1 program
(*.TPD) that has an associated
PAN File (this must be stored in
the SAME DIRECTORY as the TPD
file) this is appended to the new
version of Test Program when it is
saved.
2) If the PAN File is not in the same
directory as the TPD File when it
is first OPENed, the NetList
Steering File will be empty - it will
be necessary to manually copy
the contents of the PAN File into
the NetList Steering File.
Issue 1.5
The format of the Commands associated with the NetList Steering File are detailed
below:-
DEFBUS_S {BUS NAME};
ELEMENT {ELEMENT NAME followed by CONNECTION};
etc..
etc..
etc..
DEFBUS_E;
NODENAME {NEWNAME followed by CONNECTION};
An example of a NetList Steering File is shown below:-
DEFBUS_S ABUS;
ELEMENT A1 U8~2;
ELEMENT A2 U8~3;
ELEMENT A3 U8~4;
ELEMENT A4 U8~5;
ELEMENT A5 U8~6;
ELEMENT A6 U8~7;
ELEMENT A7 U8~8;
ELEMENT A8 U8~9;
DEFBUS_E;
NODENAME CLK U1~13;

where:-
DEFBUS_S Defines the Start of a Bus
ABUS Defines the Name of the Bus
ELEMENT Defines the Start of the Element Naming convention
A1 Defines the Name of the Element within the above defined
Bus
U8~2 Defines the Device Reference and Pin Number in the
PinPoint Schematic NetList that will be renamed as ABUS,
Element A1.
DEFBUS_E Defines the End of the Bus
NODENAME Defines the Renaming of a Node
CLK Defines the New Name of the Node
U1~13 Defines the Device Reference and Pin Number in the
PinPoint Schematic NetList that will be renamed as CLK.
Issue 1.5
DISCRETE MODE
When the board has discrete components (eg Resistors / Capacitors etc) it is
possible to change / improve the layout by selecting the Discrete Mode. Select the
icon and notice the improvement in layout.
DRAGGING COMPONENTS
It is possible to move components about on the page to further improve the layout.
Select the icon and "drag" a component whilst holding down the keyboard
<shift> key.

Components cannot be dragged from
one page to another
SAVE AND RESTORE
If you have modified the schematic, it may be useful to save the changes and then
restore them when re-loading the program.
To save the schematic select the Utilities menu > Save Schematic
To restore a schematic select the Utilities menu > Restore Schematic
Figure 4.18 Schematic Save / Restore
Issue 1.5
118
CHAPTER 5
5 Libraries
Contents
5.1 Library Summary................................................................................................................................. 119

5.2 Device Library Editor .......................................................................................................................... 123
5.2.1 Data Sheets ............................................................................................................................................. 125
5.3 Package Library Editor ....................................................................................................................... 126
5.4 Symbol Library Editor ........................................................................................................................ 130
5.5 Test Clip Editor .................................................................................................................................... 134
5.6 Functional Library Editor ................................................................................................................... 136
Chapter 5 Libraries 119
5.1 L ib rar y Summa r y

The Libraries Tab Application is used primarily to generate, modify or test Device
Functional Programs and ancillaries such as Symbols, Test Clip and Device
Package data. Associated with this Section is a set of COMPILER COMMANDS
and COMPILER ERRORS or WARNINGS.
The Libraries Application should be used in conjunction with the PROGRAM

BOARD Application when editing or verifying a functional device whilst
generating a Board Program.
To Open a particular Library either "Double Click" on the "Closed Library" Icon in
the Tip Left Tile or use the relevant Menu Command. Once a Library has been
"Opened" then you can select the required device / Library from within.
Before a Device can be tested there are a number of factors that need to be taken
into account.
Does a Device with the correct name (e.g. 74LS00) exist in the Device Libraries
for the actual device on the Board Under Test?
Do we wish to Functionally Test the device (e.g. 74LS00)? If we do, then a link to
a Functional Program (e.g. 7400) in a Functional Library must exist. If we only
wish to perform Parametric or VI / ASA testing then no link to a Functional
Program is required.

There may be many Devices in the
PinPoint Device Library that link to a
single Functional Library. For example
a 7400, 74LS00, 74F00 and many
other variants of 7400 are all
functionally identical and can
therefore all link to the same
Functional code.
Before a device can be tested there must be some test interface to interface between
the device and the PinPoint. For a 7400 device for example there may be two types
of interface required - a 14pin Dual-in-Line Test Clip or a 14 pin SOIC Test Clip
defining the PinPoint Driver / Sensor channels that are connected to the device
pins. The PinPoint Test Clip Library contains these interface details.
The PinPoint system uses device graphics when programming and testing boards.
These device graphics are fetched from the Package Library. For example for the
7400 device, or variants of the 7400, a 14-pin DIL or 14-pin SOIC package is used.
In order to display the Circuit Diagram of a board, the graphical symbol of the
device is required.
Issue 1.5
To summarise, there are 5 specific Library types within the PinPoint Library
structure.:-
DEVICE Library
Many Devices are functionally equivalent to other devices manufactured either by

different suppliers or manufactured with a different technique (e.g. TTL or
CMOS). PinPoint recognises this fact (and that programmers do not necessarily
know these equivalents) by allowing many devices to use the same Functional
Library as the basis of the test. However Drive and Sense parameters etc may
require to be different - separating the Libraries into two simplifies this process.
The Device Library, or PinPoint 's "Look-up Library" contains the basic Device
Information such as Part Number, Drive and Sense Parameters, Test Rate etc and
also a link to a Functional Program stored in a Functional Library. Thus, once a
Device is added to a Functional Library a Device Library entry is still necessary.
FUNCTIONAL Library
When a Functional Program is compiled it is stored away in a PinPoint Functional

Library. This Functional Library contains the basic truth table from the Functional
Block of the Source Compiler Commands together with the "default" parametric
data from the Parameter Block of the Compiler Commands. This Functional
Library is used by the system to generate the "ones and zeros" needed to test a
device. The Test Rate, Drive and Sense Voltages etc (i.e. parametric data) are
derived from a separate library called the Device (or Parametric) Library.

Creating / editing Functional
programs is covered in more detail on
both the Standard and Advanced
Training Courses held at Diagnosys
offices.
TEST CLIP Library
The TEST CLIP LIBRARY MANAGER is the " PINPOINT CLIP TO DRIVER
CHANNEL DEFINITION FILE" and is used by the System to correlate between
PinPoint Channel Number and Device Under Test (DUT) Pin Number.
Standard Device Test Clips are supplied by Diagnosys Ltd for most applications
and are listed in the CLIP LIBRARY MANAGER - however it may be necessary
for Customer Special Clips to be made and these clip definitions must be added to
the Test Clip Library.
PACKAGE Library
The Package Library Editor (sometimes referred to as the PACKAGE IMAGE

EDITOR) is used to create and/or modify Device Packages within the PinPoint
Package Library. These Packages are displayed in a Test Program to indicate
features such as which device is currently being tested, or which devices have
already been tested etc.
Issue 1.5
SYMBOL Library
The Symbol Editor is used to create or modify the Graphic Symbols for devices
within the PinPoint system. These Graphic Symbols are used in both the Symbols
Page of the Device Properties and also in the creation of the Circuit Diagram.
In addition to the above Libraries there is a specific storage area within the Board
Program called:-
TPD CACHE
The TPD Cache stores Functional Information about the devices that have been
programmed in the Program Board Application as well as the Clip, Package and
Symbol information, allowing these to be modified in the Board Test Program
without having to modify the actual PinPoint Package Libraries.
The Library Application consists of 4 regions:-
1) MENU COMMAND BAR
The Menu Command Bar allows you to select the required Command or
Function. These are described in detail in the following pages.
2) TEXT EDIT AREA
Displays the loaded Library Program that can then be Edited, Compiled etc.
Associated with the Text Display Area are a number of ICONS situated
directly beneath the MENU COMMAND Bar at the top of the screen. These
Icons are specific to each Library Application. To observe the function of these
ICONS hover the mouse pointer over the ICON to display the "TOOL TIP"
help summary. Most of the functions of these ICONS are duplicated by the
MENU COMMANDS, or by selecting the required function using the right
mouse button.
3) SYSTEM DISPLAY AREA
Displays the results of Compilation. This area can display the Compile Results,
the Map / Truth Table File or the Debug Results.
4) STATUS AREA
This is situated in the Grey area at the bottom of the screen. It contains relevant
Status information about the Library Function selected.
Issue 1.5
CLOSE TILES
If there are a number of Library Tiles open and you wish to close some of them,
select the Tile you wish to close and then select the Close Tile icon at the bottom
left of the Tile area (see Figure 5.1).
Figure 5.1 Close Tiles
Alternatively you can use the Hot Key combination Ctrl + F4.
Issue 1.5
5.2 D ev ic e L ibra r y Ed itor

There are two types of device that can be added to the Device library:-
Devices linked to an existing Functional Library - this type of device can be

functionally tested.
Devices that are NOT linked to a Functional library - this type of device CANNOT
be functionally tested but can be tested using the InterV3 function.
Devices Linked to a Functional Library
This will be carried out as part of the Functional Libraries later in this Tutorial.
Device NOT Linked to a Functional Library
We will add a device 4N26A to the Device Library.
To do this, select the "Libraries " Tab and "Open" the Devices Library on the
left side of the screen as shown in Figure 5.2 (double click on the icon if the
Library is "Closed" ).
Figure 5.2 Opening Device Library
Right click on any of the Device Libraries and select "New" to enable the Create
New Device Program Dialog Box.
Enter the required number of pins for the device (in our case enter 6)
We now have a Text field template generated, and from this template we need to
fill in the required information as shown below
Issue 1.5
Edit the Device Name parameter as below

DEFBLOCKS;
PARTNUMBER 4N26A;
FUNCTION OPTO ISOLATOR - Single;
PACKAGE 6;
DEFPIN P1, Pin1, I, COS;
DEFBLOCKE;
If the Pin Names, Pin Functions etc. are known insert as appropriate i.e.
DEFPIN P1, CATHODE, I, CS;
DEFPIN P2, ANODE, I, CS;
DEFPIN P3, NC, N;
DEFPIN P4, EMITTER, I, CS;
DEFPIN P5, BASE, I, CS;
DEFPIN P6, COLLECTOR, OC, CS;
Finally we need to compile this new device into the PinPoint Library. Click Right
mouse to enable the Device Properties Menu and select Compile, (alternatively use
Hot Key F5) and from the Compile Device dialog box select the required Library
in which to add the device.
If you wish to create a new "Custom" library simply enter the required library
name in the "Destination Device Library" list box - this will be the case for the
4N26A as the device doesn't really exist so we will create a "Custom" library called
DEMO.

1) If there is a Syntax Error in the above DEFBLOCK
command structure, there will be Compilation Error,
highlighting the line in which the error occurred.
2) There will be an error in the above program - Device
Pin Labels MUST be less than 8 characters and
therefore the Label COLLECTOR will fail to Compile.
You need to change it to eg COLECTR.
3) Comments can be added by prefixing the comment
with either a * or an !.
Issue 1.5
Notice that you can also EDIT or DELETE library devices from the DEVICE
Library tree structure.
5.2.1 Data Sheets

Data Sheets in Adobe Acrobat format can be added to the Device Libraries. From
the Devices Directory tree, select the 4N26A device in the DEMO Device Library
and then “Add Datasheet” with the RIGHT mouse button.
Figure 5.3 Add Datasheet
You now have then choice of either adding a completely new Datasheet or copy an
existing one. As a datasheet already exists for the 4N26 device we shall select to
copy this existing datasheet.
From the subsequent “Browse Datasheet” dialog box simply select the required
device (4N26) to copy. You will be prompted that the Datasheet has been added.
If you wish to add a completely new datasheet select the “Load New File” option
and select the required PDF datasheet to add.
Return back to the Define Board function and fetch an imaginary device (say
U11) and notice that your new device is in the Library.
Issue 1.5
5.3 P a ckag e L ibr ar y Ed itor

The second function of the Program Studio Libraries Application is to define new
package styles that are not in the PinPoint Package Library. Let us create a new
Package style for the NPN and PNP transistors TR1, TR2 and TR3 on the InterV3
Tutorial board.
To do this, select the "Libraries " Tab and "Open" the Packages Library on the
left side of the screen as shown in Figure 5.3 (double click on the icon if the
Library is "Closed" ).
Figure 5.4 Opening Package Library
Right click on any of the Package devices and select "New" to enable the Create
New Device Program Dialog Box.
(Alternatively select the Package Menu and then select New).
Grid
First we need to ensure that the GRID is set to 0.100".
Click with the left mouse button in the Command Bar (wide white box
immediately below the left / right scroll bar).
Figure 5.5 Package Command Window - Help
Type in HELP to observe the commands associated with this Command Bar (see
Figure 5.4). You will see that to define Imperial measurements you must type U
INCH (or U IMP) and to define the required Grid you must type G 100. (i.e. one
hundred thousands of an inch = 0.100 inch). It is possible to change any of these
commands by simply typing U, G etc. followed by the parameters without having
to click inside the Command Bar area.
Issue 1.5
Place Pin
Next, select the Place Add Pin Icon and move the mouse pointer into the
Black screen area. You will see a small white "dot" following the mouse pointer.
Before placing the pin we need to define the properties of the pin(s) to be placed.
Click with the RIGHT mouse button and then select Properties from the Menu (see
Figure 5.5).
Figure 5.6 Place Pin Properties Menu
From the Dialog Box ensure that the Pin No is set to 1, the Style to Round, the Side
to Both and Size X set to 65 th. It is good practice to define pin 1 of a device with a
rectangular pad. To do this, change the type of pin from Round to Rectangle
(ensure that Size Y is now also set to 65 th.)
OK out from the Dialog Box and position the mouse pointer in the centre square
and "click" - pin 1 will be displayed as a rectangle with the horizontal and vertical
sizes etc set as above.
If you wish you can Zoom into the area of the pin by selecting the Zoom +
icon and then "dragging" the mouse over the required area to zoom,
Next, position the mouse pointer over pin 1 and O <return> - this selects pin 1 as
the new origin (0.000" : 0.000" will be displayed on the lower left corner of the
screen). Using the Zoom + icon zoom into the area of pin 1 and create a
reasonable area around pin 1. Select Place Pin icon once more and change the
pin Properties back to Style Round. Close the Dialog Box and position the mouse
at x/y co-ordinates of 0.000" : -0.100" and click to add pin 2.
Repeat the process for pin 3 at x/y co-ordinates of 0.000" : -0.200".

Pin # is automatically incremented.
When all 3 pins are positioned cancel the Pin Placement Mode (Right Mouse
button and End Mode).
Issue 1.5

It is possible to add multiple pins as
an array by selecting the "Repeat Pin"
Check box, defining the required
number of pins and the step
increments.
Create Outline
We will now create an outline around the pins.
Select the Place Rectangle Outline icon - this will allow us to add a rectangle
depicting the body of the transistor. Change the Grid to 0.050" (G 050) and
position the mouse pointer at x/y co-ordinates of 0.100": -0.250". Holding the left
mouse button down 'drag' the mouse down and right until you are at x/y co-
ordinates of 0.500": 0.050". Release the mouse button and observe the body
rectangle.
Next we will create the fixing hole. Now select the Oval Outline icon - this
will allow us to add a circle representing the transistor-fixing hole. Position the
mouse pointer at position 0.350": -0.150", and whilst holding down the mouse
button drag the mouse to position 0.450": -0.050". Release the button and observe
the circle within the transistor body.
Finally we need to create the transistor "legs". Select the Line icon and "drag"
the mouse pointer from the centre of device pin 1 to the edge of the transistor body.
Repeat for legs 2 and 3.

You can create almost any shape
using a combination of rectangle,
circle or lines.
Delete
a) To DELETE an image (pin, rectangle, circle, etc) select the appropriate

function, and whilst holding down the keyboard shift key, click over the
required item to be deleted with the left mouse button.
b) To delete multiple pins select the icon, and then "drag" the left mouse over
the pins that are required to be deleted. The "selected" pins will turn blue and
then press the <Delete> key on the keyboard to delete the pins. You are
prompted to confirm the deletion
Issue 1.5
Device Reference
Next we need to define where the Device Reference Text (TR1 etc) is to be
located. Select the Text icon and using the mouse left button select the correct
location for this text. If no text is required for this device, position the Red text
marker at X Y co-ordinates DATUM 0:0 i.e. at the top left corner of the allowable
entry rectangle.

You can Auto Place the Text by using
the right mouse and then Auto Place.
Device Anchor
Finally we need to define the "Anchor" position - usually over pin 1 of the device.
This Anchor position defines the location position, and the position around which
the device will rotate. Select the Anchor icon and select the pin to position it
at.

You can Auto Place the Anchor by
using the right mouse and then Auto
Place.
Save
Now the Device Image is completed we need to save the Image to the Library -
select the Save icon Menu Bar and then save the Image as "DEM-220" using
the "Save as Device Image" command (there is already a TO-220 package in the
Package library).
Return back to the Define Board function and fetch an imaginary device (say
TR1) and notice that your new device is in the Package Library.
Issue 1.5
5.4 S ymb o l Libr ar y Ed itor

The third function of the Program Studio Libraries Application is to define new
device schematic symbols that are not in the Symbol Library.
To do this, select the "Libraries " Tab and "Open" the Symbols Library on the
left side of the screen (double click on the icon if the Library is "Closed" ).
A list of all the available symbol libraries will be expanded, and individual
schematic symbols can be selected - this is done by “double clicking” on the
required library and locating the desired part number. Open the symbol for a 7400,
this can be found in the library TTL0. Notice that only one gate is displayed. To
view the remaining three gates click on the button to step forward and to
step back. There will be associated information for each gate such as pin number,
pin label, pin type etc.
We will now look at creating a new device and adding the relevant information for
each gate.
Let us create a new symbol for a NAND gate.
Figure 5.7 Opening Symbol Library
Expand the required Symbol library that you want to add the symbol to and right
click on any of the Symbol devices and select "New" as shown in Figure 5.6.
(Alternatively select the Symbol Menu and then select New). A square with a green
outline will appear in the right hand window - this is the Symbol’s Graphical Body
and any outlines for the symbol must be placed within this box.
Select any line of the rectangle with the left mouse button and it will turn Blue.
Now, either use the <enter> key on the keyboard or the right mouse button and
select Properties to open the Symbol Properties dialog box. Alternatively "double
click" on the rectangle to open this dialog box
Body Width
Enter 6 for the width of the symbol. Dimensions are always in tenths of an inch. i.e.
0.6 inch increments.
Issue 1.5
Body Height
Enter 4 for the height of the symbol. Dimensions are always in tenths of an inch.
i.e. 0.4 inch increments.
Gates per Symbol
Define the required number of Gates with the device. e.g. a 7400 will have 4 Gates
Define whether the Symbol has a Graphical Body or not.
Graphic Body
A Graphical body consists of elements such as Lines, Arcs, Ellipse etc placed
WITHIN the above width and height parameters, whereas a non Graphical Body is
a simple rectangle of the size defined above. Therefore, we need to check this box,
as our symbol will consist of lines and arcs.
Discrete Device.
If the device is a discrete device (eg Resistor, Capacitor etc) enable this check box.
Selecting the device to be a Discrete device will improve the placement algorithm
in the Schematic Generator application.
Resistors.
These are Non-Polar (ie current can flow in either direction)
Capacitors.
These are No Flow (ie No current flow)
Transistors.
These are Polar. Select the direction of current flow (eg from the Collector to
the Emitter)
Click OK to apply these properties.
Click on the Auto Zoom button to re-size the display area. Using the
buttons we can now step through all four gates. Fortunately we will only have to
create an image for one gate, as any changes made to a gate will be applied to all
gates in that symbol. Return to gate 1 where we will create a symbol for this
device.
There are four outline tools available to us for the purpose of creating symbol
outlines
Place Line Mode
Place Rectangle Mode
Place Ellipse Mode
Place Arc Mode

Issue 1.5
Line
Select Place Line mode and draw a vertical line from the top left to the bottom left
of the Graphic Body. To draw a line in Place Line Mode click the left mouse
button at the start point, hold the mouse button down and drag the mouse to the
finish point and release the mouse button. This will draw the line between the two
points.
If you make a mistake you can use the button to undo the line you have drawn.
The undo button will allow you undo the last ten actions.
Continue to draw the outline of the symbol. Start a horizontal line in the top left
corner and drag it along 0.4" or to X position 1.4 (co-ordinates are visible in the
bottom left corner of the Symbol Editor window). Draw the same size line from the
bottom left of the symbol.
Arc
Now select the Place Arc Mode button.
When placing an Arc, the Arc will be drawn counter-clockwise from the start
point. This time there is no need to hold the mouse button down between start and
finish points, just click once where you want to start and once when you want to
finish.
You can now increase the size of the Arc by moving the mouse towards the Arc
line or decrease it by moving away from the Arc line.
It may take a few attempts to become familiar the way the Arc is drawn, so try
drawing a few Arcs. Don’t forget to use the undo button to remove them
again. Move the mouse to co-ordinate 1.400, 1.400 and use this as your starting
position; use co-ordinate 1.400, 1.000 as you finishing position. A semi-circle will
be drawn between the two points and will be the correct size to fit the Graphic
Body.
Click left mouse button to accept this Arc size.
Pins
We are now ready to place the pins of the device.
Select the Pin Placement button and the Add Pin Dialog Box will be
displayed. This allows us to define the pin properties, such as pin number, pin
name, pin style and pin type.
Type in the following information in the relevant boxes:-

Pin Number 1
Pin Name 1A
Pin Style All boxes left empty
Pin Type Input
Click Ok.
Issue 1.5
You will now be able to drag the pin, using the mouse, to the position at which you
wish to place the pin - click left mouse button to place the pin and, automatically,
you will be requested to enter information for the next pin. Call this Pin 1B and
place the pin below pin 1.
For pin three enter the information below

Pin Number 3
Pin Name 1Y
Pin Style DOT
Pin Type Output
Power Pins
The placement of power pins is required.
These will not be displayed on the final schematic symbol. The power pins can be
placed anywhere around the edge of the Graphic Body, but generally we place
VCC in the top left and GND in the bottom left corners.
Before we can declare the symbol finished we must enter the pin information for
the remaining three gates.
Step to gate 2 and you will notice that the pin numbers are all zero. Click the
Select Mode button and move the mouse to the pin you wish to edit - double
click left mouse button and edit the information so that it is correct.
Ensure all pins for gate 2 are correct and repeat for gates 3 & 4.
Save
The symbol is now finished and needs to be saved into a Symbol Library.
Select the icon (or select Save from the Symbol Menu).
You will be prompted to enter the name of the symbol library you wish to save the
new symbol in. This will usually be of the same name as the library for the
Functional program for which the symbol is associated. In this case we will create
a library called TEMP.
You will next be prompted for a name for the symbol, again this is usually the
same as the part number of the device i.e. 7400, but in this case we will call it
7400TEMP.
Before we can view the symbol we have just created, we will need to link it to a
Functional Device program. We will do this as part of Chapter 5.6 (Functional
Library) later in this Tutorial.
Issue 1.5
5.5 T e s t Clip Ed itor

The Test Clip Editor function of Program Studio is to define new test clips that are
not in the Test Clip Library.
To do this, select the "Libraries " Tab and "Open" the Clips Library on the left
side of the screen (double click on the icon if the Library is "Closed" ). A list of
all the available test clips will be displayed and individual clips can be selected by
double clicking on the required clip.
Display Pins. Double click the test clip for a 14 Pin DIL Test Clip and a list of all
the pins for the test clip and the associated Driver Channels will be displayed in the
right hand window. This is used by the System to correlate between PinPoint
Channel Number and Device Under Test (DUT) Pin Number.
Standard Device Test Clips are supplied by Diagnosys Ltd for most applications
and are listed in the CLIP LIBRARY MANAGER - however it may be necessary
for Customer Special Clips to be made and these clip definitions must be added to
the Test Clip Library.
To add a new test clip to the Test Clip Library click left mouse button once on the
main “Clips” heading. Once the “Clips” is highlighted blue, click the right mouse
button once to view the Test Clip Pop-up Menu. Select New Clip and the New Clip
window will appear (see Figure 5.7).
Figure 5.8 Test Clip Editor – New Clip
You are required to enter two bits of information - the test clip name and the
number of pins the test clip has. In this case we will call the test clip a "14 Pin
Temp Clip" and naturally it will have 14 pins.
Click OK and the new clip will be displayed in the right hand window. Before we
can use this clip we must define the relationship between the PinPoint Driver
Channel and the pin of the test clip. This can be achieved in two ways, by entering
the pin information manually or by using the Auto Detect feature (preferred
method).
Manual Pin Edit
Select the required pin to change (e.g. Pin 2) and then, either clicking with the right
mouse button, or "double clicking" with the left mouse button enter the new
required Channel Number that clip Pin 2 is connected to.
Issue 1.5
Auto Detect
Instead of entering / editing each Channel Number for each test clip pin it is
possible to allow the system to Auto Detect which Channel Number each of the
Test Clip pins is connected to.
Place the Test Clip into Position A (if the Clip has more than 48 pins start from
Position A, working upwards through Positions B, C etc.) and select the Auto
Detect Properties command (right mouse button > Auto Detect).
Place a "Strike" probe into the "Controller Card" GND position and probe each pin
of the test clip in sequence (pin 1, pin 2 etc). The system will automatically insert
the appropriate Channel Number into the selected pin number. Continue the
process until ALL pins have been probed or press Function F5 to terminate the
process.
Save
To save the new test clip select Save from the File Menu. Your new 14 Pin Temp
Clip will now appear in the list of clips available for use.
Issue 1.5
5.6 Fun c tion a l L ib rar y Ed itor

A Device Source Code consist of two major sections:-
DEVICE PARAMETER BLOCK
This Block of data basically defines the device's Parametric properties such as
TEST RATE, DRIVE / SENSE VOLTAGES, MAX/MIN VOLTAGES etc and is
stored in the PINPOINT's DEVICE (PARAMETER) LIBRARY.
Also, this area will contain DEFINED information, such DEFPIN, DEFBUS,
SHORTS etc and allows PIN NAMES, PIN TESTS, SHORTING ALGORITHMS,
BUS PINS etc to be defined.
DEVICE FUNCTIONAL BLOCK
This Block of data contains the basic "Truth Table" of how the device operates
functionally - this is achieved by driving input pins high and low, by strobing clock
pins and monitoring the output response against the required truth table.
Alternatively, with simple logic devices we can use Boolean equations to represent
the device. When compiled, the Boolean equation automatically generates the test
patterns for any given shorting algorithm.
The PinPoint Compiler Commands listed in the Help File relate to entering basic
(Default) data for both the Parameter and Functional Blocks. However, the
information is stored into two separate Libraries - A Functional Library and a
Device Library.
Functional Library
When a Functional Program is compiled it is stored away in a PinPoint Functional

Library. This Functional Library contains the basic truth table from the Functional
Block of the Source Compiler Commands together with the "default" parametric
data from the Parameter Block of the Compiler Commands. This Functional
Library is used by the system to generate the "ones and zeros" needed to test a
device. The Test Rate, Drive and Sense Voltages etc. (parametric data) are derived
from a separate library called the Device (or Parametric) Library.
We will have a simple look at a 7400 Program.
To do this, select the "Libraries " Tab and "Open" the Functional Library on the
left side of the screen (double click on the icon if the Library is "Closed" ).
Scroll down to TTL0 and click on the + symbol to expand this library and then
double click on 7400.
Alternatively you can select the Functional Menu and then Open. Using this
method allows you to "Find" specific types of devices. For example select
Functional Menu > Open and a Dialog box is opened. Select the Find Tab and
scroll down to NAND Gate. Double click on the + symbol to expand the field
(double click on the - symbol to compress the field) and you will see the different
types on NAND Gate displayed. Select Quad 2 I/P and see the types of Quad 2 I/P
Nand Gates currently in the Library.
Issue 1.5
Ensure that you have opened the 7400 Library program by one of the above
sources.
The following are the main features of this program:-
Green Text
Comments generated by the characters * or !
Red Text
Compiler Commands. Click over the Command and press Function Key F1 for
Help on the specific Command.
Parameter Block
Commands within the Block Specifiers DEFBLOCKS and DEFBLOCKE
BOOLEAN specifies that the program is of a Boolean type
SET Commands define the Test Parameters e.g. Drive Levels (DLV, DHV) Sense
Levels (SLV, SHV) and Test Rate
DEFPIN define the Pin Labels, Pin Type and Pin Tests
Functional Block
All commands following the DEFBLOCKE command are Functional Block

commands. For the 7400 program these are simple Boolean equations.
Compile
Once a program has been generated (or an existing one modified) it must be
Compiled into a Functional Library. However, before this is possible the program
MUST have passed all the in-built "syntax" checking to ensure that only correct
syntax programs are stored.
To Compile a program select the Functional Menu (alternatively right click in the
Blue area) and then Compile. This opens a Dialog box allowing you to compile.
For this example we do NOT want to compile the program into a Library so ensure
that the Syntax Check Only check box is selected. (If it is de-selected the program
will be compiled into the displayed Library)

If you wish to compile to a new
Library instead of an existing one,
simply enter the required new Library
name in the Link to Library edit field.
Issue 1.5
SeaWave
It is also possible to view the SeaWave timing waveform of the displayed program
by selecting SeaWave from either the Functional Menu or right click.

Creating / editing Functional
programs is covered in detail by both
the Standard and Advanced Training
Courses held at Diagnosys offices.
Linking to Device Library
When fetching devices in the Define Board application, ONLY devices stored in
the PinPoint DEVICE library can be fetched. Therefore, even once a Functional
Program is created and stored into the Functional Library, a link to a Device in the
Device library MUST be made.
Earlier in this Tutorial we made a Symbol for a 7400TEMP device and therefore
we will create this Device and link it to the 7400 Functional Library program.
Select the Device Menu and then select “Add Functional Link” to open the Add
Device Dialog Box (see Figure 5.8)
Figure 5.9 Add Device Menu
Enter the required Device Name (7400TEMP) and the required Device Library
(DEMO created during the Device Library tutorial). Then select TTL0 from the
Functional Library and select 7400 from the Functional Name.
Once you select OK a further Dialog Box is opened allowing you to make changes
to the default 7400 parameters. For example the program 7400TEMP may require
CMOS drive levels and therefore we will change the Drive high to say 4.00 volts.
When you OK from this dialog box the Device 7400TEMP will be added to the
DEMO Device Library and will be linked to the 7400 Functional program stored in
the TTL0 Functional Library.
Issue 1.5
Linking to Symbol Library
Earlier in this Tutorial we created a symbol for a 7400TEMP device. We have now
also created a Device of the same name and therefore we can review the effects of
these additions.
Return to the Program Board for your Demo Tutorial Board program.
Re-fetch device U1 (right mouse over U1 and then select Re-Fetch Device).

The Device Database will be updated
as we have added a new device to the
Library.#
From the Re-Fetch Dialog Box (Figure 5.9) enter the program 7400TEMP and
verify this is in the Library
Figure 5.10 Re-Fetch Device Dialog Box
OK from the Dialog Box - the device changes to Black as we have fetched a new
device to program.
Select the Device Properties (right mouse over the device > Properties) and review
the General Tab. Notice the Partcode (7400TEMP) and the Functional Src Program
(ttl0...7400).
Select the Symbol Tab and the schematic symbol that is displayed is the one you
created during the Symbol Edit section of this Tutorial.

DO NOT SAVE THE CHANGES YOU
HAVE JUST MADE, AS THE PROGRAM
ENTERED IS NOT THE CORRECT
DEVICE - IT WAS JUST ENTERED TO
SHOW THE CORRELATION BETWEEN
THE DIFFERENT LIBRARIES.
Issue 1.5
140
CHAPTER 6
6 Test Board
Contents
6.1 Test Board ............................................................................................................................................. 141

Chapter 6 Test Board 141
6.1 T e s t Boa rd
Finally, it is a good idea to test the board that has just been programmed.
Functional Test
Select Test Board from the PinPoint Menu Selector and your board name from the
Select Board List and then AUTO Functional Test (Component Functional Test
allows you to select with the mouse which device you want to test and TrakTest is
defined later in this section)
Next you will be prompted to enter a Serial No and whether you wish to search for
previous test results - Do not select this check box as there will be no previous
results.
Select Unknown Symptoms from the Test Entry Point box, and you will then be
guided through the Execution Order as per the TestFlow in Program Studio.
The only difference between the Simulated Test Mode and Test Board is the
manner that the Device Failure information is displayed.
If a device fails a dialog box is opened displaying the actual failure. From this
dialog box you can:
Re-Test
Will Re-Test the device from the test routine that failed. i.e. if the Functional Test
failed only the Functional Test will be retried - prior tests which passed such as
Opens, Volts etc. will not be retried. Re-Test Push Button is enabled for ALL
failures.
Continue
Will allow continuation of the test sequence for the failed device under certain
failed conditions. Continue Push Button is enabled for OPENS and VOLTAGE
Tests only.
Cancel
Will cancel the test for the selected device. The device will be highlighted in RED
to show a FAILURE but the failure results will not be logged.
Log
Will LOG the failure results to the Test Results Log for future reference. The
device will be highlighted in RED to show a FAILURE.
Follow the defined sequence until all the components have been tested.
Issue 1.5
The switch setting of SW1 can simulate the following failures:
Position 1 ON.
Turns on the Oscillator to U1 pin 13. This will result in a functional failure on
U1.
Position 2 ON.
Connects a short to GND on pin 2 of U1.
Position 3 ON.
Introduces Leakage to 2 places when testing U1.
Input Leakage on pin 4 of U1. This will fail the Voltage Test on pin 4.
Input Leakage on pin 9 of U2.
Press continue after above failure to continue the test sequence and a
Functional Failure will occur on pin 6 of U1.
The indication will be Expected High but Received T, i.e. pin 6 is being
loaded by the leakage on pin 9 of U2.
Position 4 ON.
Introduces a short between pins 1 and 6 of device U2.
Position 5 OFF.
Introduces an Open Circuit track between U2 pin 8 (output) and U8 pin 19.
This will be detected when testing U8.
Position 6 OFF.
Introduces an Open Circuit track on a Data Bus between U9 pin 18 and U8

pin 2. This will NOT be detected by the usual Opens test during the
Functional sequence but will be detected by TrakTest. This shows the
advantage of TrakTest is bus related systems.
TrakTest
When all the Functional sequence has been completed you will be asked if
TrakTest is to be performed. Select YES and follow the procedure.
TrakTest allows you to check for the existence of tracking between two
components. There are two basic types of TrakTest:-
Opens Trak
Opens TrakTest will ONLY prompt you to clip over devices that the system knows
should be shorted together and is primarily used to find Open Circuits, although, if
an extra short is recognised between the respective devices, this will also be
displayed as a fault.
Issue 1.5
Full Trak
This performs a complete test of the device interconnections and is effectively

repeating the NetGen process, but instead of learning the nets, it is verifying them.
Once the test is completed view the Test Results for the board and exit.
Issue 1.5
144
CHAPTER 7
7 Conclusion
Contents
7.1 Conclusion ............................................................................................................................................. 145

Chapter 7 Conclusion 145
7.1 Con clu s ion

This concludes the Basic Tutorial Section for the PinPoint.
There are a number of topics that this Tutorial does not cover - it is STRONGLY
recommended that the user attend a Diagnosys Training Course to familiarise
themselves with the other features. You should contact Diagnosys Sales
Department for details of times and venues for these courses.
Issue 1.5

Ppii Tutorial Manual

Uploaded by

Copyright:

Available Formats

Ppii Tutorial Manual

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

Ppii Tutorial Manual

Uploaded by

Copyright:

Available Formats

Tutorial Manual for the

PinPoint Series Test Systems

The PinPoint Series

TestVue32™ Operating Environment

Issue 1.5 Jan 2012

 Copyright 2001 - 2012 rights reserved

Diagnosys Test Systems Limited • Systems House • Bedford Road • Petersfield

Diagnosys Systems Inc. • 5 Lan Drive, 1st Floor • Westford

1 SYSTEM FAMILIARISATION .............................................................................. 7

5 LIBRARIES ...................................................................................................... 118

Figure 5.6 Place Pin Properties Menu ................................................................................................127

1.1 About this Tutorial ................................................................................................................................... 8

1.1.1 How to Use this Tutorial

completed, by selecting the button at the bottom of each topic page, or

to the Next Main Topic by selecting the button, or return to the

Contents Page at any time by selecting the button.

In this Tutorial we will follow the process of generating a comprehensive Board

From the PinPoint Login screen (Figure 1.1):

Figure 1.1 PinPoint Login Dialog Box

Figure 1.2 PinPoint Task Selector

Start Program Studio ?

Start Test Board ?

Launch the Tutorial ?

Start the PinPoint (TestVue) taskbar ?

The PinPoint Task Bar or is situated in one of two possible

It is strongly recommended that new users DO NOT modify these Customise

The PinPoint Task Bar (see Figure 1.3) consists of 9 Sections:-

Figure 1.3 PinPoint Task Bar

Provides access to the main system Options and Accessories.

Contact Diagnosys Sales Department for information on any of these

Provides access to the main Windows functions, such as Program Manager,

Provides access to Operator Controls, Customisation of PinPoint Settings and

Exits to MS DOS Prompt.

Access to the PinPoint Help and Tutorial Help.

1.4 Sup erv isor U tilities

1) Type in the name of your New User and OK

1.5 U ser U tilitie s

Figure 1.4 User Utilities Menu Task Bar

1.5.1 Self Tests

If ANY Test Fails Contact Diagnosys Applications Department for assistance.

Figure 1.5 RED Loopback Plug.

Figure 1.6 YELLOW Loopback Plug.

The 8 Self Tests are:-

VECTOR RAM TEST

Select CANCEL to return to Utilities Menu.

DRIVER RAM TEST

Select CANCEL to return to Utilities Menu.

LINE TERMINATION TEST

Select CANCEL to return to Utilities Menu.

Contact Diagnosys Service Department if a failure is detected.

DRIVER LOOPBACK TEST

There are two options for LOOP BACK TEST.

Select CANCEL to return to Utilities Menu.

Select CANCEL to return to Utilities Menu.

Select CANCEL to return to Utilities Menu.

SCANNER LOOPBACK TEST

This test ensures that the Controller resistance measurement system is

For operation see Driver Loopback Test Above

POWER LOOPBACK TEST