MultiWriter pps Instruction Manual - CheckSum

MultiWriter pps 

Production Programming System 

INSTRUCTION MANUAL 

CheckSum, LLC 

6120 195th Street NE 

Arlington, WA 98223 

1-877-CHECKSUM / 1.360.435.5510 

Fax (360) 435-5535 

Web Site: www.checksum.com

P/N 4400-059 

Revision 20150113 

© Copyright 1990-2015, CheckSum, 

LLC All rights reserved 

Printed in U.S.A. 

Specifications and operational characteristics of the System are subject to change without 

notice. CheckSum, LLC cannot take responsibility for any direct or consequential damages 

arising from use of this manual or the related product. 

MultiWriter is a trademark of CheckSum, LLC. 

ii

Table of Contents 

Chapter 1: CheckSum MultiWriter pps System 

System Introduction 1-1 

On-Board Gang Programming (ISP) 1-1 

Main Topics 1-3 

Operation and Installation 1-3 

Generating Device Program Setups 1-3 

Customer Support 1-3 

System Components 1-4 

PC System Requirements 1-5 

Power Supplies (PS-UUT-L1) 1-5 

Related Topics 1-5 

MultiWriter Controller 1-6 

Fixture Receiver Interface 1-7 


Custom fixture with a bed-of-nails interface 1-8 


Customer Support 1-8 

Chapter 2: Getting Started 

Getting Started 2-1 

Overview 2-1 

Connecting to the Assembly 2-1 

Creating a Program 2-2 

Programming Devices on an Assembly (DUT) 2-2 

Chapter 3: Main Window 

Main System Window 3-1 

Main System Window Choices 3-2 

Toolbar Choices 3-2 

Menu-Bar Choices 3-3 

Main Window File Menu 3-4 

Main Test Menu 3-5 


Main Edit Menu 3-6 


Chapter 4: System Installation 

System Installation 4-1 

System Power, Controls, and Vacuum Setup 4-4 

Operator Keyboard Use 4-8 

Keyboard Mask 4-9 

GPIB-USB IEEE-488 Installation 4-10 

Model T-120-2 Strip Printer Installation 4-11 

Bar Code Reader Option 4-11 

iii

Bar Code Reader 4-11 

USB or Keyboard Entry Example 4-12 

RS232 Example 4-13 

RS232 Cable Wiring 4-14 

Software Installation 4-14 

Completing the Software Installation 4-18 

Self-test 4-19 

Save Configuration 4-20 

System Motherboard 4-20 

System 160 Pin Blocks 4-24 

Chapter 5: System Configuration 

System Configuration 5-1 

Overview 5-1 

Configure System Window 5-3 

Save Button 5-3 

Print Button 5-4 

Modules Configuration 5-4 

Module Configuration 5-5 

Print 5-6 

Adding/Deleting Modules 5-6 

Reverting/Saving Configuration Information 5-6 

Built-In Self-Test 5-6 

Self-Test of the System Controller 5-7 

Self-Test of Power Supplies 5-7 

Other Modules 5-7 

Environment Configuration 5-8 

Configure Reporting 5-8 

SPC Logging tab: 5-9 

Automatic Test Results Report tab: 5-10 

Test Results tab: 5-11 

Batch Report tab: 5-14 

General tab: 5-15 

Test Program tab: 5-16 

Configure Directories/Locations 5-16 

Manage User Accounts 5-18 

Add User 5-19 

External Hardware 5-22 

System Fixture Configuration 5-23 

Chapter 6: MultiWriter Fixture Design Guidelines 

MultiWriter Fixture Design Topics 6-1 

Programming Multiple Devices 6-2 

Fixture Layout 6-3 

Panelization 6-3 

Power Supply Considerations 6-5 

Power for the DUT 6-5 

Power Supply Controls 6-5 

Buffer Modules 6-6 

ISP Buffer module (Slave) 6-6 

Buffer Module Details 6-7 

Twisted Pair Termination 6-13 

iv

MultiWriter Fixture I/O (MW FIX I/O) 6-13 

Fixture Ready 6-17 

Internal USB and program storage 6-21 

HASP Remote Update System (RUS) 6-22 

Fixture Mechanical Design 6-24 

DUT Fixture Alignment 6-24 

Installing Guide Pins 6-24 

Installing Spring Probes 6-25 

Internal Wiring 6-26 

Pressure Rods 6-27 

Installing and removing the fixture 6-27 

Installing the DUT on the test fixture 6-28 

Fixture Checklist 6-28 

Design 6-28 

Build 6-30 

Design for Part Programming 6-31 

ISP Restrictions 6-32 

Considerations Before Making ISP Changes 6-34 

Chapter 7: System Operation 

Programming an Assembly 7-1 

Overview 7-1 


Programming Window Menu 7-1 

Selecting the Program File 7-2 

File Selection Window 7-2 

Executing the Program File 7-4 

Component Test Failure Window 7-4 

Test Failure Function Buttons 7-4 

Test Display 7-5 

Main Test Functions 7-7 

Menu Bar 7-9 

Test File Menu 7-10 

Program Menu 7-11 

Report Menu 7-12 

Environment Menu 7-14 

Panel Menu 7-18 

Test Window - Help Menu 7-20 

Chapter 8: Statistical Analysis of Test Results 

Statistical Analysis 8-1 

Overview 8-1 

Report Types 8-3 


Using Statistical Process Control 8-4 

Activating Statistical Analysis 8-4 

UUT Reported On 8-5 

Change Starting/Ending Period 8-5 

Statistics Data Path 8-6 

Production Report 8-7 

Pareto Failure Report 8-9 

X-Bar/Sigma Report 8-11 

v

Interpreting the Graphs 8-12 

Examine SPC Data 8-14 

Edit Run Failures 8-15 

Reporting on Panelized PCBs 8-17 

SPC Data Format 8-17 

Chapter 9: Test Programs 

Writing Programs 9-1 

Overview 9-1 


Background 9-2 

Manual Entry 9-2 

Setting the Execution Order 9-3 

Editing Tools & Testing Methods 9-3 

Special Features 9-3 

Statistical Data (SPC) Logging 9-3 

Optimize for Best Results 9-4 

Save Program 9-4 


Edit Test Program Window 9-4 

Menu Descriptions 9-5 

Edit File Menu 9-6 

Edit Menu 9-7 

View Menu 9-10 

Measure Menu 9-12 

Setup Menu 9-13 

Tools Menu 9-21 

Help Menu 9-23 

Loading a Program or Erasing Memory 9-23 

Assigning Point Names 9-24 

Probing 9-26 

Entering Test Steps 9-26 

Listing Test Program Data 9-26 

Saving Test Programs 9-26 

Saving/Loading Programs in Binary 9-26 

Saving/Loading Test Programs in ASCII 9-27 

Chapter 10: Entering Test Steps 

Entering Test Steps 10-1 

Overview 10-1 

Topics 10-1 

Using the Edit Window 10-2 

Test Step Descriptions 10-2 

Using the Edit Window 10-3 

Fixture Control 10-3 

Measurement Analysis 10-4 

Overview 10-4 

Display Messages 10-5 

MultiWriter MISP 10-7 

MultiWriter MISP Setup 10-7 

Title, DUT Power Control and Reporting 10-8 

Device and Image Files Selection 10-9 

Diagnostics and Commands 10-14 

vi

Buffer Wiring 10-17 

Control Buttons 10-21 

Controlling Program Flow 10-24 

Controlling Program Flow 10-24 

Branching 10-25 

Exiting the Program 10-26 

Running Another Test Program 10-26 

Extending Test Program Length 10-27 

Encapsulating a Test 10-27 

External Programs and Control (COM) 10-27 

Executing a User-Written Program 10-27 

Automation Interface (COM) 10-28 

Generating Reports from a Test Program 10-31 

Generating Reports from a Test Program 10-31 

Normal Test Reports 10-32 

Statistical Data Reports 10-32 

Changing Report Paths 10-32 

Panelized Testing 10-33 

Panelized Testing 10-33 

Overview 10-33 


Panelization Programming by Wizard 10-36 

Manual Panelization Programming 10-37 

Use of Program Memory Locations 10-39 

Use of Program Memory Locations 10-39 

Overview 10-39 


Special Notes about MEMS 10-46 

Special Notes about MEMR and MEMD 10-47 

Special Notes about MEMI and MEML 10-47 

Memory Variables and Program Storage 10-47 

Chapter 11: Program Examples 

Example Programs 11-1 

Programming One Device 11-1 

Programming Multiple Identical Devices 11-3 

Programming Multiple Different Devices 11-6 

Screen and Display Attribute Manipulation 11-10 

Display a Picture 11-19 

Fixture Identification 11-20 

Chapter 12: Fixture Receiver Wiring 

Fixture Receiver Wiring 12-1 

Fixture Receiver Interface Blocks Overview 12-1 

Fixture Wiring 170-Pin Blocks Overview 12-2 

Chapter 13: System Power Supplies (PS-UUT-L1) 

System Power Supplies (PS-UUT-L1) 13-1 

Overview 13-1 


Installing the Power Supplies 13-3 

vii

Chapter 14: Program Command Descriptions 

Test Type Descriptions 14-1 

Power Supply Control 14-3 

Power Supply Control 14-3 

DC Voltage Output 14-4 

DC Current Output 14-4 

Monitor Power Output 14-5 

ISP and Digital Test Types 14-6 

Digital Test Types 14-6 

In System Programming with MultiWriter (MISP) 14-6 

General Digital I/O Programming 14-7 

DIGx Test Types 14-7 

Digital Input Test 14-7 

Digital Output 14-8 

Digital Active 14-8 

PORTx Test Types 14-9 

Port Input Test 14-9 

Port Output 14-9 

Transfer of Control Test Types 14-10 

Transfer of Control Test Types 14-10 

Specify Label 14-11 

Jump Unconditionally 14-11 

Jump Based on PWR Measurement 14-11 

Jump Based on Result of Digital Input 14-12 

Jump Based on Result of Port Input 14-12 

Jump Based on Result of Key Input 14-13 

Set Error Counters, Control Error-Based TRY Blocks 14-13 

Jump Based on Number of Errors 14-14 

Jump Based on Self-test 14-15 

Call a Subroutine 14-15 

Return from Subroutine 14-15 

Load and Run a Test Program 14-16 

Load and Run a Test Sub-Program 14-16 

Return from Test Sub-Program 14-17 

Message Test Types 14-17 

Message Test Types 14-17 

Display a Short Message to the Operator 14-18 

Display a Message to the Operator 14-18 

Erase an Operator Message 14-19 

Wait for a Key to Be Pressed 14-19 

PCB Number Being Tested 14-19 

Enhanced Display Attributes using SCRN Test Type 14-20 

SCRN Test Type Table 14-21 

SCRN Test Range Table 14-21 

User-Defined Tests 14-23 

User-Defined Tests 14-23 

Generate Test Result 14-23 

Execute User-Written Routine 14-23 

Memory Manipulation Test Types 14-25 

Memory Manipulation Test Types 14-25 

Memory Manipulation (Integer) 14-26 

Memory Manipulation (Real) 14-30 

Memory Manipulation (String) 14-32 

General Purpose Interface (GPIB) Bus I/O 14-37 

General Purpose Interface Bus (GPIB) I/O 14-37 

viii

RS232 Serial Interface I/O 14-40 

RS232 Serial Interface I/O 14-40 

Miscellaneous Tests 14-43 

Miscellaneous Tests 14-43 

Turn Fixture Vacuum On and Off 14-44 

Fixture Control 14-45 

Control Relays 14-47 

Pause a Specified Time 14-48 

Self-test Module 14-48 

BreakPoint 14-49 

Print Test Results 14-49 

Sound the PC's Beeper 14-52 

Put a Remark in the Test Program 14-52 

Conditional Test Report Output 14-52 

Chapter 15: Sample Reports 

Sample Reports 15-1 

Test Results Report Example 15-1 

Test Program Listing Example 15-2 

Test Program in ASCII 15-3 

Batch Report Example 15-6 

Statistics Data File Example 15-6 

Wire Run Report Example 15-7 

Production Report Example 15-9 

Pareto Failure Report Example 15-10 

X-Bar/Sigma Report Example 15-11 

Chapter 16: Command Line Parameters 

System Command Line Parameters 16-1 

MultiWriter Command Line Options 16-3 

Chapter 17: Error Messages 

Error Messages 17-1 

Chapter 18: Help for Problems 

In Case of Problems 18-1 

Display Problems 18-2 

Serial Printer Problems 18-2 

Troubleshooting Tips 18-2 

Getting Help From CheckSum 18-3 

Critical Items To Provide For Assistance 18-3 

Contacting CheckSum 18-4 

ix

Limited Warranty 

CheckSum, LLC products, exclusive of custom fixturing products, are covered by a one-year 

limited parts and labor warranty for defects in materials and workmanship from time of 

original product shipment. Custom fixture products include a 90-day limited warranty. This 

warranty extends only to the original purchaser and excludes products or parts that have been 

subject to misuse, neglect, accident, or abnormal conditions of operations. 

CheckSum, LLC reserves the right to replace the product in lieu of repair. If the failure has 

been caused, as determined by CheckSum, by misuse, neglect, accident, or abnormal 

conditions of operation, repairs will be invoiced at a nominal cost. In such case, an estimate 

will be submitted before the work is started, if requested. 

NOTE 

THE FOREGOING WARRANTY IS IN LIEU OF ALL OTHER 

WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 

LIMITED TO ANY IMPLIED WARRANTY OF 

MERCHANTABILITY, FITNESS, OR ADEQUACY FOR ANY 

PARTICULAR PURPOSE OR USE. CHECKSUM, LLC SHALL 

NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, OR 

CONSEQUENTIAL DAMAGES, WHETHER IN CONTRACT, 

TORT, OR OTHERWISE. 

In the event of a failure of a product during the warranty period: 

Contact CheckSum for a returned material authorization number (RMA). 

Pack the product in its original packing material or suitable equivalent and return it postagepaid 

to CheckSum, Inc. Mark the package clearly with the RMA number. 

CheckSum will repair the product and return it postage-paid. Repairs are typically completed 

within two working days of receipt. 

In the event that expedited repair is necessary, call CheckSum for information. In many cases 

a replacement module can be provided immediately.

Chapter 1 

CheckSum MultiWriter pps 

System 

System Introduction 

This information is for use with the CheckSum MultiWriter pps (production programming 

system). The System contains an extensive set of features and capabilities that will serve your 

requirements. Because of this, it may take you some time before you want (or need) to use all 

the features of the System. 

To help you get your System up and testing as quickly as possible, you might want to expedite 

your initial reading of this information. The information has been organized to support you in 

doing so. 

1. First, read this Introduction section. 

2. Then read the Getting-Started section. By this time, you should have a general knowledge 

of what the System can do and how to navigate through it. 

3. Finally, using the remainder of the documentation as reference material, you can install 

your hardware and software, and begin experimenting with the system as you become 

familiar with its use. 

On-Board Gang Programming (ISP) 

On-Board Gang In-System Programming (ISP) is a technique to simultaneously program serial 

devices after the devices have been inserted on circuit boards (in-system). Programming 

devices "on-board" allows for rapid code changes on the manufacturing line which reduces 

development time, manufacturing cycles, and time-to-market. Simultaneous programming 

insures the minimum impact on the manufacturing takt time (cycle time or maximum time per 

unit). 

The MultiWriter Production Programming System (pps) is a standalone, on-board 

programming solution that simplifies and speeds the programming process of parts such as 

embedded controllers and flash memories mounted on printed circuit boards (PCBs). The 

system enables manufacturers to program unique data such as serial numbers, calibration data, 

and date codes in the programming sequence, a capability that conventional device

CheckSum MultiWriter pps System 


Instruction Manual 

programmers lack. The enormous amount of data to be programmed, especially on panelized 

‘multi-up’ boards, often slows manufacturing throughput. 

The MultiWriter pps uses innovative, patent-pending technology to gang program serial flash 

and embedded flash devices mounted on the board or multi-up panel at near-data book speeds. 

Specific code (e.g. a serial number) can be written to individual chips, even while they are 

being gang-programmed. High-throughput is possible only by simultaneous programming and 

verification of one, or up to 384 chips at a time. The system is based on low cost “universal 

hardware” and easily configured software that eliminates costly channel cards used by most incircuit 

testers. High signal quality is maintained with programming buffers mounted inside the 

fixture. A comprehensive serial flash and micro-controller library is used to accommodate a 

vast number of device families and parts. These attributes are necessary for a universal 

solution that adapts the system to program a wide array of devices in a multitude of possible 

configurations. 

The MultiWriter pps system includes the necessary elements to perform the programming task: 

• MultiWriter pps control system 

• Universal fixture interface 

• Programmable power supplies for the assembly 

• System software 

• Device program library 

Programmable logic devices (PLDs/CPLDs) such as micro-controllers, serial Flash, and 

FPGAs contain internal non-volatile memory that is programmed to perform specific functions 

in a circuit and this makes the devices very popular with design engineers. As board sizes 

shrink and circuit functionality increases designers use serially programmed PLD parts for 

simple and complex applications. These programmable parts eliminate hardware, reduce 

product size and parts cost. They shrink product cost and design cycle times. New features 

can be added in a product “re-spin” just by changing the program code, eliminating the need to 

alter the physical circuit design or hardware. 

Many OEMs can design a single board type and then supply multiple versions of the product 

by using variations in the device program. They can program and ship reasonably priced 

custom versions with fast turnaround when customers order the product. 

Part programming creates an additional step in the assembly process and can reduce overall 

productivity due to tradeoffs among cost, logistics and throughput. MultiWriter provides a 

universal solution to reduce cost and deliver the necessary throughput. 

Non-volatile memory parts can be pre-programmed offline as individual chips before being 

attached to the circuit board. Alternatively, ‘blank’ parts may be attached to the board prior to 

being programmed, often called “on-board” or “in-system programming (ISP)”. On-board part 

programming may occur on an in-circuit tester (ICT) or functional tester (FT), or on a 

standalone on-board programming system. 

On-board part programming occurs after the board has been tested and is defect-free. In 

medium-to-high volume environments, on-board programming results in substantial cost 

savings compared to outsourcing offline programming to third parties. Since all chips are 

‘blank’ prior to being placed on the board, on-board programming eliminates the need to track 

different versions of pre-programmed parts, simplifying inventory management and 

eliminating rework (reprogramming) cost. 

1-2




Unique device- and board-specific data such as serial numbers, date codes, calibration data, 

and even measurements made on the board itself may be inserted along with the main 

programming code ‘on-the-fly,’ eliminating an additional downstream programming step. 

On-board part programming eliminates any additional step involving manual handling of the 

part during the programming process, avoiding potential physical damage such as bent leads or 

electrostatic discharge. 

MultiWriter is designed to handle multiple devices including different device types 

simultaneously. This standalone system combines the throughput and cost advantages of 

offline simultaneous (gang) part programming to the process and ability to program deviceand 

board-unique data found in on-board part programming. 

Simultaneous gang programming capability for multiple chips of multiple family types 

overcomes the throughput disadvantages of other in-system programmers. The fixtures and 

software are much simpler and inexpensive than traditional ICT fixtures, speeding 

implementation time and reducing operating and support cost. 

Custom engineering cost and time is reduced by virtue of this systemized and documented 

approach to part programming. 

The system uses in-fixture memory to maintain both the programming algorithm and the 

device program. This insures the fixture can be transferred to any other system without any 

potential system-to-system incompatibility concerns. This is possible since the board fixture is 

unique to the final assembly both physically and in the device types. The device program data 

can be changed when necessary. 

The device program data is stored and transferred in an encrypted format to insure your 

intellectual property (IP) is safe. 

Main Topics 

Operation and Installation 

• System Components on page 1-4 

• Main System Window on page 3-1 

• System Installation on page 4-1 

• System Configuration on page 5-1 

• Programming Devices on an Assembly on page 7-1 

• Statistical Analysis on page 8-1 

Generating Device Program Setups 

• Writing Programs on page 9-1 

• The Edit Program Window on page 9-4 

• Entering Test Steps on page 10-1 

• MultiWriter Fixture Design Topics on page 6-1 

Customer Support 

• Contact CheckSum on page 1-8 

1-3


System Components 



This section describes the MultiWriter pps elements so you will have better understanding of 

the complete system: 

• System (PC) Controller 

• DUT (DUT or UUT) Programmable Power Supplies (PS-UUT-L1) 

• System MultiWriter Controller 

• Fixture Receiver Interface 

• Custom bed-of-nails fixture for programmable devices, includes USB Stored Data 

(security HASP USB drive on page 6-21) 

The following diagram shows the interconnection of the system elements. 

1-4




PC System Requirements 

The system controller (PC) requires a 1GHz or faster CPU and Windows operating system, 

1GB of RAM, CD-ROM drive, and at least four USB 2.0 ports. For best performance, contact 

CheckSum for a current recommendation. To allow room for the system software and test 

programs, it is recommended that your disk drive have at least 40MB of space. If a USB 1 

port is connected to the MultiWriter controller, a warning message will alert the user that the 

test system requires USB 2.0 to meet the specified performance. Although the test system 

should function properly, using a slower USB port connection, such as USB 1, will likely 

increase the programming time. 

The PC includes the LCD monitor, keyboard and mouse for the system operator. 

A USB 2 cable is connected between the PC and the MultiWriter controller. 

The PC controls the programmable power supplies via a RS232 COM interface. 

Power Supplies (PS-UUT-L1) 

The system is configured with programmable power supplies to provide the necessary voltage 

and current to apply power to the assembly during device programming. Note that power is 

applied to the entire assembly not just to the programmable devices since these devices are 

normally connected to the board power supply buss. 

The system software can restrict power from being applied to selected assemblies. This is 

useful for situations where some boards in a panel are not defect-free and applying power may 

damage the board and/or the board would fail to program. A panel is simply a set of boards 

that may be connected. Panels of duplicate or similar boards are a common method to 

manufacture the assemblies. The power applied can be current limited under program control. 

The power system is designed using remote sense such that the voltage at the fixture is 

monitored to insure the voltage is maintained to the proper setting. This requires that the 

fixture be designed to connect the remote sense to the power supply output. 

Power is only applied during the programming process and otherwise no power is present at 

the fixture interface or to the assembly (DUT). The system includes a hardware monitored 

(Enable/Disable) signal from the system board to remove power. This allows the fixture 

design to include a switch that removes DUT power if the operator opens a safety lid, for 

example. 

The power supply subsystem is connected to the PC by a RS232 COM interface cable. This 

requires the power supply is configured to match the system configuration setup. In particular, 

the power supply address must match the system configuration address. The power supply 

baud rate of the first power supply must match the system configuration. The power supply 

must be setup to run via RS232. If more than one power supply is included in the 

configuration, power supply #1 must be setup to run in MultiDrop mode. The power supply 

connector J1 Enable is used for safety and connects to the system board to enable or disable 

the power supply output. For additional information, see the PS-UUT-L1 Model GENH 60 - 

12.5 Technical Manual, Programmable DC Power Supplies. CheckSum configures the system 

power supplies prior to shipment. 

Related Topics 

System Power Supplies (PS-UUT) on page 13-1 

1-5




Power Supply Control on page 14-3 

MultiWriter Controller 

The MultiWriter controller has the resources to communicate with the system PC and the 

electronics to program all of the devices mounted on the assembly simultaneously. The 

controller is a programmable unit and generates the appropriate signals to the assembly as 

defined by the device manufacturer data sheet to correctly program each device. 

The controller can use any of the industry standard programming algorithms called I2C, PIC, 

SPI, Microwire, and JTAG. There are other programming methods that are also supported 

such as BDM. 

The PC sends commands via USB2 to the controller based on the user’s program sequence. 

The MultiWriter controller sends signals through the fixture receiver interface to the buffer 

modules mounted inside the fixture. 

The MultiWriter controller generates the programming signals based on the programming 

algorithm and the device data file. Each type of device has a unique programming algorithm. 

CheckSum develops the device programming algorithm for the specific device. The cost of 

the test fixture includes the cost for the programming of the device. The device data file is 

developed by the board design group and can be changed by replacing one, or more, data files. 

A standard data file format (Intel, hex, Motorola S-record, binary) is used for storage of the 

unique data that is accessed during the programming process. This data is also stored in the 

fixture memory located in the fixture hub. 

Inside the fixture, cable assemblies with twisted-pair wires are used with the buffer modules. 

Generally, a mass-terminated, push-on connector is used on one end and the other end of the 

wire is wire-wrapped to the connector pin. The use of the push-on connector allows easy 

replacement in case a buffer module should ever fail. 

These setups allow the ISP buffer module to be installed physically close to the device to be 

programmed which is required for clean signal characteristics and reduce ringing, overshoot, 

undershoot, and noise pickup. The fixture should be designed to minimize the length of the 

twisted pair wiring from the buffer module to the spring-probe receptacle. The twisted-pair 

wires should be separated from other twisted-pair wires and from all other wiring. 

The programming control structure of the MultiWriter pps system can be viewed as: 

1-6




CheckSum develops the ISP bus algorithms and the device algorithms. The customer creates 

the device data file during the engineering design process for the assembly. This data file can 

be changed and control of this file is the customer’s responsibility. The control program that 

combines these elements to “program” the device or multiple devices, depending on the 

assembly, is developed by the customer using the CheckSum system editor. 

Fixture Receiver Interface 

The system includes an industry standard fixture receiver interface. This interface is 

compatible with the GenRad 227X type fixtures. The receiver has 170-pin blocks that make 

contact with the fixture when the fixture is installed. 

The fixture includes 170-pin wiring blocks that make contact with receiver blocks. A 

mechanical lever arm is used to lock the fixture to the receiver to insure a good mechanical and 

electrical connection. 

Note 

Do not attempt to use the system unless the fixture is installed properly and 

the receiver lever arm is locked down. 

The interface blocks are identified by letter (A, B, C, D, E, F, G, H, or K) and each pin (1 to 

170) is indexed from the pin 1 corner. 

Each of the first 8 blocks (A to H) is used for up to 24 buffer modules and programmable 

devices. Power for the buffer modules is provided at each of these blocks. Block K provides 

connections to the system power supplies for the DUT and to the security HASP USB Drive. 


MultiWriter Fixture Design Topics on page 6-1 

1-7




Fixture Receiver Interface Wiring on page 12-1 

Custom fixture with a bed-of-nails interface 

To use the system, a customized fixture needs to be designed and built. 

Each fixture is designed and developed specifically for each type of assembly. Fixtures can be 

developed by CheckSum, the customer, or by any fixture supplier. Contact CheckSum for a 

list of fixture suppliers or visit the CheckSum web site and click on Customer Support. 


MultiWriter Fixture Design Topics on page 6-1 

Fixture Mechanical Design on page 6-24 

Customer Support 

If you have any problems or questions, don't hesitate to call CheckSum at 1.877.CHECKSUM 

or +1.360.435.5510, located in the U.S. Pacific Time Zone, GMT-8, for assistance. We are 

here to help you. 

Our web site is at: www.CheckSum.com 

1-8

Chapter 2 

Getting Started 


Overview 

This section guides you through typical sequences for each major use of the System. These 

sequences include: 

• Connecting to the Assembly below (fixturing) 

• Creating a Program on page 2-2 

• Programming Devices on an Assembly on page 2-2 

Read through this section to get an overview of each activity. Complete detail is not given in 

this section, so you will probably want to refer to the individual sections of the manual that 

describe each action in detail as you perform the task. 

Connecting to the Assembly 

The System's electrical resources (programming control signals, power supplies, etc) are 

available on the pins at the fixture interface. Each pin is called a point, port, or test point. The 

connections to the assembly with programmable devices (DUT ) are specifically determined 

based on the device pin-out and board design. The connections between the system and the 

buffer modules are predefined. The type of device and the DUT design determines the 

connections between the buffer modules and the device to be programmed. 

The fixture is first connected to the fixture interface mechanism on page 12-1 and then the 

DUT is placed on the fixture. Electrical connection to the DUT is made the DUT is pushed or 

pulled down onto the fixture spring-probes. The simplest method is for the operator to close a 

top-lid over the DUT that pushed the assembly down on spring-probes. The lid normally locks 

in place when closed. As the lid closes, it contacts a fixture-mounted switch that closes to 

signal the system to start the ISP process.


Creating a Program 


Creating a Program 

The program tells the System the steps to perform ISP. The program is generated once, saved 

on the disk, then used each time one or more of the same assemblies are programmed. 

The program consists of a number of steps, most of which can generate pass/fail results. 

The system software includes a program editor to generate the program sequence. Access to 

the editor is from the main System window. You may use the System in random sequences of 

configuration, programming, debug, and other operations. From time to time, remember to 

save your program to disk so you don't lose your work. 

Following is a typical programming sequence: 

• The first step is to assign test point names. To get to this window, select 'Edit', select a 

Blank Program and then from the 'Setup' pull-down menu, select 'Fixture Test Points'. 

This window allows you to enter names specific to your DUT into the System. When you 

do this, the System displays and reports will contain the names that you enter. 

• Enter the assembly name with the 'Setup' pull-down menu and select 'Assembly Name'. 

The assembly name is added to the other pass/fail results that are saved. 

• The Operator set-up window, accessed from 'Operator Instructions Setup' from the 'Setup' 

pull-down, can be used to create a window of text that the operator sees prior to beginning 

a program for each DUT. This text can be used for precautions, connection information, 

or other things that you would like to convey to the operator. This window can also 

contain simple character-graphic drawings that you create. 

• Enter the program steps. This can be as simple as applying power to the DUT and then 

programming the device list. The programming step is controlled by a command "MISP 

on page 10-7". This programming step is controls the buffer modules that connect to the 

DUT and the power applied to each board. 

• Once you have entered the program, you will want to run a batch of DUTs on the System 

to verify that the setup is appropriate to meet any variations. You can use data logging in 

conjunction with the X-Bar/Sigma Control Report to help determine appropriate tolerances 

by analyzing the readings from the first few batches of DUTs. 

• When you are finished writing the program, you can save it using the file menu and using 

the same menu obtain a print out. As with any other software application, you should 

frequently save your work as you develop a program. 

Programming Devices on an Assembly (DUT) 

With the program created for a DUT, all the devices can be programmed simultaneously. To 

program a DUT, select `Program' ([F1]) from the System window. If the program file has not 

been already opened, you are then presented with the Open File window. Select the program 

name, then OK to load it. Execution will then begin in the Test window on page 7-5. 

If any failures are detected (and the System is set for halt on fail), you are presented with a 

display describing the failure. You may continue, stop, or retry to program the devices. 

2-2




Once the test is completed, you see the Test Complete window. This window allows you to 

either continue on to the next assembly in this run (batch) or to retry the present assembly. 

At the end of any program, you may also generate a report. The Report ([F3]) contains the 

programming pass/fail results. The selection for the report output device (for example CRT or 

LPT1) is configured in the Test window menu Environment > Report Device. The contents of 

the report (failures-only or all step results) is setup in Test window menu Environment > Test 

Reports Contents. The Report pull-down also allows you to select a batch report that gives a 

summary of all of the DUT's tested in this run. Use of the various configuration windows is 

described in System Configuration on page 5-1. 

2-3




2-4

Chapter 3 

Main Window 

Main System Window 

Main System Window

Main Window 



Note 

The System environment can be modified to meet a variety of testing needs 

unique to each facility. For example, the system may have logins enabled 

that provide different levels of access and selection visibility to each user. 

If this is enabled on your system, the screens shown in this manual may not 

exactly match those of your system. See the menu control on page 5-19 

section for information on menu selection visibility. 

In general terms, this is what each major option will do for you: 

Main System Window Choices 

There are four main selections in the center of the main system window, each is discussed 

below: 

• Program [F1] is used to program devices on an assembly. The selection of 'Program' also 

allows you to choose a program file describing the steps to be performed on the DUT, and 

to display or print results. See Selecting the Program on page 7-2. 

• Edit [F2] is used if you want to program ('learn') the test sequence and test tolerances for a 

particular DUT. You can use 'Edit' to assign pin names, assign operator instructions, 

assign an assembly name, edit a program, save the program on the disk, or get a test 

program report for the assembly. See the Editor Window on page 9-4. 

• Generate SPC Report [F3] is used to generate statistics reports to describe testing that 

has occurred on the System. These reports include Production Reports to list the number 

of DUTs tested over a period of time, how many passed or failed, the yield and how many 

defects. The Pareto Failure Report allows you to find out what type of errors have 

occurred and their frequency. The X-Bar/Sigma Control Report allows you to analyze 

analog measurements to observe trends or for setting test limits. See Statistical Analysis 

on page 8-1. 

• Configure System [F4] is used to change the configuration of your testing environment. 

With this option you can: 

– Configure the system modules and options. Self-test (which verifies proper operation) 

is available. 

– Specify the system directory structure 

– Configure password access 

– Configure the reports generated by the System 

See System Configuration on page 5-1. 

Toolbar Choices 

There are several tools (toolbar icons) available in the main system window: 

• Folder (Open) allows you to open a file. This option allows you to select a program to be 

executed and load it from the system disk. 

• Disk (Save) saves the program now in memory to a disk file. 

3-2


Main Window 


• People (Login) allows you to log into the system. If logins are enabled, each user has a 

name, and optionally a password. Different users may be assigned different levels of 

access to system operations. If you try to access an operation for which you do not have 

permission, the system will not allow you to continue. This tool bar item allows you to 

login to the system with your user-name and password. 

• Green Door (Exit) allows you to terminate operation of the System software. Once this 

option is selected, you return to the normal Windows environment. 

Menu-Bar Choices 

There are a number of menu choices available to the user. These include: 

• File Menu on page 3-4 

• Main Test Menu on page 7-1 

• Edit Menu on page 3-6 

• Statistical Analysis on page 8-1 

• Configure System on page 5-1 

3-3

Main Window 

Main Window File Menu 


Main Window File Menu 

Main File Menu 

• Open loads a new program from disk into memory so that it is available for execution. 

See Selecting the Test Program on page 7-2 . 

• Save saves the program now in memory to a disk file. 

• Save As opens a dialog box to allow the test program to be saved to another file. It is 

saved in standard binary format (Program). See Saving Test Programs on page 9-26 for 

additional information. 

• Exit stops execution of the system software and returns you to the normal Windows 

operating environment. You are prompted to save the program if necessary. 

3-4


Main Window 

Main Test Menu 



• Run Test [F1] is used to program devices on an assembly. The selection of 'Program' 

also allows you to choose a program file describing the steps to be performed on the DUT, 

and to display or print results. See Selecting the Program on page 7-2. 

• Test Window opens the Test Display on page 7-5 window. 

• Enter UUT Serial Number [F7] allows the UUT serial number to be entered prior to 

programming. 


Writing program sequences (test programs) is described in more detail in the following topic: 

Editor Window on page 9-4 

3-5

Main Window 

Main Edit Menu 




• Edit Test opens the Editor Window on page 9-4, used to create and modify programs. 

• Edit Program CheckList opens the CheckList window. The CheckList window shows 

the basic setup for this programming sequence. The setups can be modified in this 

window, see View Menu on page 9-10 

• Change MISP Image Files allows different device data files (Image Files) to be selected. 

The device data files or image files contain the data to be programmed into the device. 

The image files are selected in the MISP on page 14-6 step and can also be selected in the 

Edit Program CheckList setup on page 9-10 in the MultiWriter ISP setting. 


Writing programs is described in more detail in the following topics: 

Entering Programming Steps on page 10-1 

3-6

Chapter 4 

System Installation 


Overview 

There are several steps in the installation process. It's a good idea to read through this entire 

installation section before beginning. 

Installation topics: 

• System Power, Controls, and Vacuum Setup on page 4-4 

• Operator Keyboard Use on page 4-8 

• GPIB-USB IEEE-488 Installation on page 4-10 

• T-120-2 Strip Printer Installation on page 4-11 

• Bar Code Reader Option on page 4-11 

• PS-UUT-L1 Programmable Power Supply on page 13-3 

• Software Installation on page 4-14 

• Completing the Software Installation on page 4-18 

• System Motherboard on page 4-20 

The test system software and modules were installed by CheckSum, so you do not need to 

perform any hardware or software installation. The tower PC and two chassis are contained 

inside the system. The PC can be installed by removing the front, lower panel cover. A small 

door in the upper center of the front panel provides convenient access to the PC power switch 

and the CD drive. 

The system is shipped with a printed copy of the system setup. This document provides stepby-step 

instructions to uncrate the system, assemble the items shipped separately, and make 

connections to the required facility services. 

The printed system setup document supercedes the setup instructions that follow. 

Before use, it is necessary to assemble several items for the system and connect power and 

other resources. The following sections are described: 

• Uncrating the System




• Assembling the System: Read this section before connecting to the power mains, 

connecting any compressed air and/or vacuum lines. 

• System Power-off Procedure 

Uncrating the System 

The system is shipped in a wooden crate. The crate can be moved with a forklift. Accessories 

are packed in boxes on the top shelf of the crate. 

The minimum required floor space for the system is 24 x 30 inches (61 x 77 cm). 

To remove the system from the crate: 

1. Remove any zip ties that attach to the latches of the crate. 

2. Open the front door slowly since objects may shift during shipping. 

3. Lay the door in front of the crate opening with the flat surface up. The lower end of the 

door should be placed next to the crate. 

4. Locate the triangular piece of wood marked “ramp”. Place the ramp at the far end of the 

door to transition the top surface of the door to the floor. This ramp will allow the system 

to roll off the door to the floor carefully. 

5. Loosen the two straps by releasing the ratchet system. Remove the hooks at the end of the 

strap from the rings on the crate bottom. 

6. Turn the corner four leveling feet to the up position, so the system can roll on the casters. 

7. Pull the unit out of the crate onto the door and ramp to carefully move the unit to the floor. 

8. Once the system has been moved to the required location, turn the four leveling feet to 

insure the unit cannot roll and use the jamb nuts to lock the feet in the down position. 

Assembling the System 

Note 

When handling any system items, always use an ESD wrist strap attached to 

the banana jack on the left side of the receiver interface. Do not connect the 

system power until instructed. 

1. Locate the LCD monitor, monitor mounting assembly, tower PC, optional printer and 

mounting tray, and the monitor mounting post from the boxes. 

2. Place the monitor face down on a soft surface to protect the unit from damage. 

3. The monitor mounting plate has multiple holes to attach to the back of the monitor. 

Choose the configuration of 4 holes to fit your height requirement. Position the plate to 

align with the four holes in the back of the monitor. Install the four spacers and screws. 

4. Insert the monitor post base and extension post on the back of the system base. 

4-2




5. Route the monitor power cable and video cable below the post through the channel area of 

the post to the monitor. Be sure to have some excess cable outside the routing channel so 

the monitor can be moved to various positions without pulling on the cable ends. Connect 

the USB cables to the keyboard/mouse. 

Note 

The power to the PC and the monitor are only switched on/off with the 

main power switch. There are two "unswitched" power outlets; one for the 

PC and one for the monitor. The system is shipped with these power cords 

connected to the outlets. Be sure to connect these two power cords to the 

PC and the monitor. 

6. Generally, the LCD monitor will automatically adjust for 110V to 240V, but check the unit 

to be sure. Ensure that the system power supply setting matches the system power input 

voltage. Connect the power cable and video cable to the LCD monitor. 

7. Check the PC for either a manual voltage selection switch (115V / 230V) or an autosensing 

voltage circuit. Read the PC product information guide and follow the instructions 

for power safety. Ensure the manual voltage selection switch setting matches the system 

power input voltage. 

8. If the PC is already installed, skip this step, otherwise loosen the front door fasteners and 

place the PC on the sliding tray. Untie the zip tie that bundled the PC Power cable, 

Monitor video cable, optional printer port cable, and USB cables, and connect them to the 

PC. Install the PC facing the front of the console. 

9. If an optional CheckSum printer will be mounted on the left side panel or right side panel, 

install the printer tray with the 2 screws located in either side panel. Connect the printer 

cable and printer power cable to the back of the printer. 

10. Re-install the front panel fasteners. 

11. After all parts and covers are installed, connect the optional system air (95 to120 PSI / 655 

to 827 kPa), power (220 to 240VAC, 10A max) and/or optional vacuum (18 to 23 inches 

Hg / 61 to 78 kPa) to the back panel on the unit. 

12. Set the back panel main power switch to the ON position. 

13. Check the back panel light on lower left corner is On. 

14. Check side panel, red “Emergency” button/knob to be sure the knob is not pushed and 

latched down. Turn the knob clockwise to release it. 

15. Press and release the top side of the Programmer Power rocker-style button. This will 

turn-on the green “Power” indicator on the button. 

Notes 

Switch-on the system power before starting the PC. Windows will autostart 

the CheckSum software. 

16. Press the tower PC power button. The CheckSum system software will auto-start. 

4-3


System Power, Controls, and Vacuum Setup 


17. If a vacuum connection has been made, verify the vacuum setting is adequate since typical 

test heads require 20-30 CFM at 18-25 inches of Mercury (61-85 kPa). 

18. If a pps spare kit was supplied, be sure to store these items carefully for future use. 

System Power-off Procedure 

It is recommended to exit the system software before turning-off system power. To turn-off 

the system power, press and latch the “Emergency” power-off switch knob. After the power is 

off, you should release the latched “Emergency” switch by turning it clockwise to release it. 

This insures this switch is not latched in the off position for the next time the Programmer 

Power switch is used to turn-on the system. 


There are two switches to control the system power; Main Power and Programmer Power. 

The Main Power switch is located on the lower right side of the back panel. Press the "1" side 

of the switch to turn-on the main power. 

On the lower left side of the back panel is a green panel-mount light and a small momentary 

Reset switch for a thermal overload breaker. This green light indicates the switched power 

strip has power from the Main power. The power strip has a thermal overload breaker and 

Reset switch built-in. 

4-4




When the system power line is connected to a power source and the Main Power switch is ON, 

the green light will turn-on. 

A local area network (LAN) connection to the PC can be made through the system at the lower 

left side of the back panel. 

A single-point (Red) probe connects to the side panel. The probe is used to identify test points, 

see the Buffer Wiring > Probe UUT Point on page 10-7 selection. 

The Programmer Power switch is located on the right side of the fixture receiver panel. Press 

the rocker-style switch on the top to turn-on the system programmer power. 

When the Main Power switch is ON and the Programmer Power switch is turned-on, then the 

Programmer Power switch green light and the light on the power strip in lower left side of the 

back panel will be ON. 

The Programmer Power switch is a 3-position, rocker-style switch; Top Position-In = ON, 

Bottom Position-In = OFF, and the Center Position = Normal (switch released). 

The Programmer Power switches on a relay that applies +5Vdc, +12Vdc and +24Vdc to the 

system motherboard. It also switches on a latching power relay and applies power to the 

switched outlets for the PS-UUT power supplies, printer, etc. 

When pressed, the Emergency button/knob overrides the Programmer Power switch and if not 

reset will not allow power to be applied. The Emergency button will latch down when pressed. 

Turn the Emergency button/knob clockwise to release it. When released, Programmer Power 

4-5




will not be automatically reapplied. Press the Top Position on the Programmer Power switch to 

turn-on the Programmer Power. 

The Emergency button and the Programmer Power settings cannot remove power to the PC or 

the monitor. These two items are powered from the Main Power strip. 

A flat silver START button is located at the top, front of the fixture receiver assembly. This 

button allows the operator to start the program. Press this button to start a program, or to 

program the next assembly. Fixtures can also be designed to automatically start programming 

when the lid is closed, see the Editor Setup menu on page 9-13, Progam CheckList on page 9- 

10, Fixture Ready on page 6-17, MultiWriter Fixture I/O module on page 6-13, and Test 

Environment on page 7-14 windows. 

An ESD connector is provided for the operator. Make connection at the front left side of the 

fixture receiver: 

System Vacuum Connection 

The vacuum connection is located on the rear panel: 

4-6




An automated vacuum valve is controlled by the system software, see Turn Fixture Vacuum 

On and Off on page 14-44 . 

Typical test heads require 20-30 CFM providing 18-25 inches of Mercury (61-85 kPa) 

Provide a 1¼ inch I.D. hose or ¾ inch NPT connection 

System Specifications 

System dimensions: 24 inches (51 cm) wide front, 30 inches (77 cm) deep side, 31.5 inches 

(80 cm) high to the top base plate and 40 inches (102 cm) high to tallest portion of the fixture 

receiver. The monitor post is 26.5 inches (68 cm) high and the mid-point of the monitor is 

30.5 inches (78 cm) above the base plate. 

The keyboard drawer extends out up to 26 inches (66 cm). 

System weight is approximately 185 lbs (84 kg). 

The test system operating temperature range is 0°C to +35°C with 0 to 80% RH (without 

condensation). Rated accuracy at ±10°C from calibration temperature. Maximum altitude for 

operation is 3000m (9843 ft.). 

Power input is factory-configured for 110-130VAC 15A max. or 208-240VAC 10A max., 

single-phase. 

4-7


Operator Keyboard Use 



The keyboard allows the operator to control the execution of the system software and can 

replace the use of a mouse. The keys can be masked to further limit the operator selections 

(see Keyboard Mask on page 4-9). 

The keyboard can be used on several windows. 

Keyboard use in Open File dialog box: 

F4 - Same as the keyboard Enter key 

F6 - Next item (Scroll down) 

F3 - Previous item (Scroll up) 

F7 - Next selection (Tab) 

F5 - Previous selection (Shift Tab) 

ESC - Cancel 

Keyboard use in Programming Window: 

F1 - Program the next assembly 

F2 - ReProgram the assembly 

F3 - Test Report 

F4 - Skipped PCB selection (if panelized) 

F5 - Batch Report 

F6 - Open File dialog box 

ESC - Stop 

Keyboard use in Halt on Fail /Single Step Window: 

F1 - Next step 

F2 - ReProgram 

F3 - Continuous Test 

ESC - Stop 

Keyboard use in Skipped PCB Selection Window: 

F1 - Toggle Skip Selection On/Off 

F2 - Move left 

F3 - Move up 

F4 - OK 

F5 - Move right 

F6 - Move down 

F7 - Retain Skip Selections 

ESC - Cancel 

Keyboard use in Enter UUT/Batch ID Window: 

F4 - OK 

ESC - Cancel 

Keyboard use in Comments/Instructions Window: 

F4 - OK 

ESC - OK 

4-8




Keyboard use in Test Results Window: 

F3 - Page Up 

F4 - OK 

F6 - Page Down 

Keyboard use in Confirmation, Warning, and Error dialog 

boxes when test programs are started: 

F4 - OK 

F5 - Yes 

F7 - No 

Keyboard Mask 

The following keyboard keys can be enabled/disabled via the keyboard mask using the test 

step MEMI range 33. The command line parameter (/km) on page 16-1can also be used to set 

the keyboard mask when the system software is started. Setting the keyboard mask bit enables 

that key on the keyboard. A mask value of 255 enables all of the keys and a mask value of 0 

disables all of the keys. The mask value is the sum of the mask bits for the keys to be enabled: 

Key Mask Bit 

[ESC] 1 

[F1] 2 

[F2] 4 

[F3] 8 

[F4] 16 

[F5] 32 

[F6] 64 

[F7] 128 

The System motherboard on page 4-20 provides a DB25 connector with access to a limited set 

of control signals, primarily for use with an automated handler such as the CheckSum Analyst 

ils. The following shows the pins and signal names on this DB25 connector: 

4-9


GPIB-USB IEEE-488 Installation 


+3.3V 

1000 

+5Vdc SW 

0.75A 

Dig I/O bit 6 

Dig I/O bit 5 

Dig I/O bit 8 

Dig I/O bit 7 

SW0 

SW1 

SW5 

SW7 

GND 

100 

100 

100 

100 

100 

100 

100 

100 

Red (FAIL) 

Green (PASS) 

Yellow (Busy) 

1 

14 

4 

17 

5 

18 

6 

19 

7 

20 

8 

21 

9 

22 

10 

23 

11 

24 

12 

25 

13 

2 

15 

3 

16 

100 

+3.3V 

1000 

100 

+3.3V 

1000 

100 

+3.3V 

1000 

100 

1nF 

GND 

1nF 

GND 

1nF 

GND 

1nF 

Dig I/O bit 2 

Dig I/O bit 1 

Dig I/O bit 4 

Dig I/O bit 3 

GND 

System DB25 Connector 

GPIB-USB IEEE-488 Installation 

The GPIB-USB IEEE-488 option is normally installed in the System using the default setup as 

described in its instruction manual. This option includes the standard USB driver installation 

software used by USB devices. 

The System, upon starting, looks for presence of the GPIB-USB module, and automatically 

installs this in the test system configuration. If the GPIB-USB module is not detected, then a 

question mark is displayed on the module configuration window to the left of the GPIB entry. 

4-10



Model T-120-2 Strip Printer Installation 

Model T-120-2 Strip Printer Installation 

The Model T-120-2 Strip Printer can be used to print test results in a compact form. The 

Model T-120-2 is available in either parallel (-2P, standard) or serial (-2S, no-cost option) 

configurations. Both include the appropriate cable. Normally, the parallel printer connects to 

the LPT1 connector, and the serial version connects to the COM1 connector on the back of the 

controller. 

The serial printer has a DIP switch located under a cover on the bottom of the printer (see the 

printer manual). In the printer, set DIP switch 6 and switch 7 to OFF to configure the printer 

for 1200 baud. Be sure to turn-off the power before changing the switch settings. The printer 

baud rate is set at power-up of the printer. All the other switch settings are normally in the ON 

position. 

For the serial printer, you also need to specify to the System the baud rate and other 

communication parameters. The values are entered into the `External Hardware' page of the 

Configure System screen. The default values are baud rate 1200, data bits 8, retry action 

polling, parity none, and stop bits 1. Also, set the report width to 40, and blank lines at end to 

6. 

Finally, for the parallel printer specify "LPT1" as the output device in the Configure System > 

External Hardware > Test Report Device menu. Set it to "COM1" if you have the serial 

printer. Once changed, saving the station configuration data on disk will save the setting for 

future use. Prior to use, check that the printer ribbon and paper are installed and that the printer 

is switched to the on-line position before printing results. 

If you encounter any problems, see In Case of Problems on page 18-1 in the Trouble Shooting 

section. 

Bar Code Reader Option 

Bar Code Reader 

The best model often depends on the application. If the bar code scanner/reader is operated by 

a person at the test station, a keyboard wedge type of scanner or USB type works well. The 

wedge type of scanner is connected between the standard PC keyboard and the PC. When the 

operator scans the assembly and presses the trigger button on the scanner, the scanner reader 

the bar code it’s aimed at and sends the scanned characters to the PC as if the operator had 

typed-in the keys on the keyboard. The CheckSum software can be configured to input serial 

numbers via the keyboard (from the scanner). Alternatively, the bar code data can be stored in 

file by another application and the CheckSum software can access the file contents to acquire 

the bar code data. 

The Welch Allyn Model 3800VHD-12 with the PS-2 cable option (42206132-02) has been 

used on CheckSum test systems. Several companies sell USB type bar code scanners. These 

scanners provide a key press type of input similar to the wedge type scanner. 

There are two general methods to acquire the assembly identification or serial number. The 

system can be configured to automatically ask the operator to input this information for every 

assembly. This can be setup to query the operator before the programming sequence, after the 

4-11




programming sequence, or when the test results are saved. The second method requires adding 

steps to the test sequence that acquires the assembly identification or serial number and setup 

the system UUT Serial Number string variable. 

The first method does not require any special steps in every test sequence program. The 

second method allows you to decide if, and when, to use serial numbers. 

The system can be configured to verify the length of the serial number and with additional test 

steps, validate the sequence in more detail. For example, the serial number can be checked to 

insure it always begins with a capital letter from A to M and ends with a digit from 1 to 9. 

The serial number is stored with the results to allow SPC tracking assemblies by serial number. 

Related topics: 

UUT Serial Number string variable (MemS Range 13, 33, & 29) on page 14-32 

Environment Menu (Check UUT Serial Number) on page 7-14 

Serial Numbers in a File, see MemS Ranges 59, 60, 61 & 64 on page 14-32 

Configure Reporting > Test Results tab > Get UUT Serial Number on page 5-8 

Configure Directories/Locations > UUT ID Input File on page 5-16 

USB or Keyboard Entry Example 

The following is an example section of a test sequence to acquire the assembly bar code serial 

number, validate the acquired bar code, and store the code in the system variable “UUT Serial 

Number”. The operator is prompted to scan the assembly serial number bar code. The 

software waits until the serial number is scanned and the characters are received (via the 

keyboard or the USB “keyboard” port). The serial number must start with the characters 

“UC24” followed by 7 characters (11 total). If the serial number meets the criteria, the serial 

number is stored in the system variable “UUT Serial Number” otherwise the operator is 

prompted once more. 

----From---- -----To----- -----------Test------------ --Limits-- -Nom- 

Point Name Point Name Type Range Title Low High 

Rem 

SerialNum 

Rem 

Rem 

Serial 

Rem 

Number 

Label try again 

Rem 

UC24 -> MemS 

MemS 1 UC24 0.000 0.000 

MemS 15 CS MemS 0.000 0.000 

Disp 1 Get S# 

MemS 3 S# -> MemS 53.000 4.000 

DispE 1 Erase line 

MemS 33 S# MemS 0.000 0.000 

MemS 29 S# -> MemS 0.000 0.000 

Rem Length 11? 

MemI 28 Len(MemS) 0.000 0.000 

MemI 23 try again 11.000 11.000 

Rem 

First=UC24? 

MemS 12 Left(MemS,4) 1.0000 4.0000 

MemS 21 try again 0.000 0.000 

DispE 0 

MemS 13 MemS -> SN 0.000 0.000 

Displays: 

No Col Row 

Display 

4-12




1, 22, 4, Bar code the Serial Number 

RS232 Example 

The following is an example section of a 2 unit (left and right), test sequence to setup the 

RS232 COM ports (#1 and #2) to acquire the assembly bar code, send a trigger character (“#” 

character followed by CR LF) to the bar code unit, input the bar code, validate and display the 

acquired bar code, and store the bar code (or set the code to SN#1 Fail) in the system variable 

“UUT Serial Number”. The bar code reader was preconfigured to match the test system 

communication protocol, wait for the RS232 trigger signal character (“#” character), sample 

the bar code, delay sending back the bar code, and then output the bar code with the expected 

postamble (CR LF). RS232 communications is also dependent on the wiring protocol signals 

so be sure to verify the RS232 cable wiring is correct also. See RS232 Serial Interface I/O on 

page 14-40 for the RS232 step details. 

----From---- -----To----- -----------Test------------ --Limits-- -Nom- 


Displays: 

Rem 

SDM DS 

Rem 

PCB 0 

Rem 

Setup COM1 

RS232 4 9600,8,N,1 

RS232 11 Timeout 

RS232 4 

Rem 

RS232 4 Setup COM2 

RS232 11 9600,8,N,1 

RS232 4 Timeout 

Rem 

Left Side 

PCB 1 

DispE 0 

Disp 1 

RS232 1 # 

RS232 4 #13#10 

RS232 0 SN -> MemS 

MemI 28 Len(MemS) 0.000 0.000 

MemI 2 SN#1 Fail 5.0000 5.0000 

MemI 22 SN1nul 1.0000 0.000 

MemS 1 Reader1 Fail 0.000 0.000 

Label SN1nul 

Disp 2 Left SN = 

MemS 5 Show MemS 40.000 2.0000 

MemS 13 MemS->SN 0.000 0.000 

No Col Row 

1, 20, 1, 

Display 

CheckSum test in progress for left unit... 

2, 30, 2, Left SN = 

Note: The RS232 driver software for input (Range 0) clears any received data when it 

executes (e.g., the input buffer is cleared). Therefore, any received data must be sent after the 

input command starts. In the above example, the output from the scanner was programmed 

with a delay after receiving the RS232 output trigger character (“#”). If this delay was not 

possible and the scanner immediately responded to the trigger character, it’s very likely the 

4-13


Software Installation 


RS232 input would be executed too late such that any reply from the scanner would be lost 

when the input buffer was cleared. Another solution is a custom executable “transmit and 

receive” program that does not clear the input buffer. Contact CheckSum for additional details 

or questions. 

RS232 Cable Wiring 

1 

2 

3 

4 

5 

6 

7 

8 

9 

Computer to Computer 

1 

2 

3 

4 

5 

RS-232 Cable Connections 

1 = Carrier Detect 

6 2 = Receive Data 

3 = Transmit Data 

7 4 = Data Terminal Ready 

5 = System Ground 

8 

6 = Data Set Ready 

7 = Request to Send 

8 = Clear to Send 

9 

9 = Ring Indicator 

DB9 

(female) 

DB9 

(female) 

Computer to Simple Serial Device 

1 

2 

3 

4 

5 

6 

7 

8 

9 

1 

2 

3 

4 

5 

6 

7 

8 

9 

2 = Receive Data 



DB9 

(female) 

DB9 


The next step of the installation procedure entails installing the system software in your 

computer. This step was performed at the factory so section is for information only. 

The system controller (PC) requires a 1GHz or faster CPU and Windows operating system, 

1GB of RAM, CD-ROM drive, and at least four USB 2.0 ports. For best performance, contact 

CheckSum for a current recommendation. To allow room for the system software and test 

programs, it is recommended that your disk drive have at least 40MB of space. If a USB 1 

port is connected to the MultiWriter controller, a warning message will alert the user that the 

test system requires USB 2.0 to meet the specified performance. Although the test system 

should function properly, using a slower USB port connection, such as USB 1, will likely 

increase the test time. 

Be sure to connect a USB 2 cable between the PC and the USB control module. 

The System uses the main executable file PPS.EXE that is accessed during some operations. It 

also uses the system configuration file $PPS$.DAT that contains system information specific 

4-14




to your installation (hardware setup, data paths,...). It also uses other files such as the Help 

files. 

As a default, the installation procedure installs the system software into a new subdirectory 

called C:\CHECKSUM. Normally, the directory below CHECKSUM, named SPECFILE is 

used for test programs. You can change the selection of the test program subdirectory in the 

Configure System > Environment > Directories / Locations menu window. 

Insert the CheckSum software distribution media in your computer. 

To install the software, use the Windows RUN command to invoke setup.exe on the 

installation disk. Follow the instructions of the installation procedure. 

When you are done with installation, remove the CheckSum software media and store it in a 

safe place. 

File names with the extension .SPEC will be associated with the CheckSum test system 

software. The .SPEC file association setups the CheckSum software to load and run the test 

program when the file is double-clicked in Windows Explorer. 

Start the system software by using the mouse to double-click on the MultiWriter pps icon, or 

use the run menu-item to invoke PPS.EXE in the CHECKSUM directory. If you encounter 

any display problems, see the section In Case of Problems on page 18-1. 

Set the PC Control Panel Power Management to "Always On with No standby or hibernate". 

Antivirus Note 

If the system is used with a HASP USB Drive and the computer Antivirus is 

ESET NOD32, please disable the Real-time file system protection. 

Uncheck the Scan on setting for File Creation. This protection will cause 

the computer to freeze/lockup and require a hard reboot (Hold down the 

Power Button to reboot). 

Symptoms: 

Your computer will freeze when changing fixture (HASP Drive) but it will 

be normal again after a hard reboot. 

Cause: 

The system software will mount the USB Drive to 

"C:\Checksum\PPS\Fixture USBDrive" during startup and the Antivirus 

software detects this "File Creation" as a threat. 

Other Antivirus software may cause the same problem, please check the 

Antivirus software setup. 

Steps for normal MultiWriter pps use by an XP Limited User 

Windows XP provides for limited file access by users when password logins are enabled but 

the default scheme allows only access under Shared Documents by all users when 

Administrator folders and files are private. Access by only MultiWriter pps users and 

administrators is desirable for normal use. 

4-15




Here are some steps for an operator with system Administrator privileges to allow a limited 

User to run MultiWriter pps. These comments are based on use of Windows XP Professional, 

Service Pack 2. 

1. Log in with system Administrator privileges. 

2. Add a Limited user group for MultiWriter pps operators under “Control Panel”|”User 

Accounts”|”Create a new account”. 

3. Open Windows Explorer and create the MultiWriter pps installation directory, e.g. 

c:\CheckSum. 

4. On the Windows Explorer menu select Tools | Folder Options | View. 

5. Scroll down in the Advanced Settings list until “Use simple file sharing” is seen. If checked 

then click on the check mark to uncheck then click on Apply then Ok to close the dialog. 

6. Right click on the CheckSum folder then select Properties. 

7. Now select the Security tab. 

8. Select the User that you want to have PPS use on the “Group or user name” list. If they 

aren’t already on the List you can click “Add”, enter their name, then press “Check Names”, 

then “Ok”. 

4-16




9. You now can assign privileges to access this folder for the selected user. Click on the Allow 

boxes for “Modify” and “Write” and if not already checked “Read&Execute”, “List Folder 

Contents” and “Read”. Then click “Apply”. 

10. You can now log out from Administrator into the User. 

11. You can now install MultiWriter pps. To do so XP will present the “Install Program As 

Other User” dialog since a Limited User can not update Windows Registry settings. Chose to 

run the install as the Adminstrator level user, enter your password, then click “Ok”. 

4-17


Completing the Software Installation 


12. MultiWriter pps should can now be added to the desktop and Start Up folders for the 

Limited user. 

13. Select PPS.exe in the CheckSum folder using Windows Explorer then right click and then 

select “Run As”. Choose to run as user with Administrator privileges by entering the user 

name and password and clicking on “Ok”. Exit PPS. 

14. You can now run PPS normally with User level access. Use of “Run As” in 13 may be 

necessary with installation of a new MultiWriter pps version. 


At this point, you should see the system screen, which is called the Main System window. This 

is the starting window for all System operations. 

4-18





Software installation is complete at this time. 

Self-test 

After installation and power-up, the System software should auto-run otherwise start the 

system software by running PPS.EXE. At this point, you will see the Main System Window 

above which is the hub of all System operations. 

When first installing the System, it is recommended to run a complete self-test. This ensures 

that the hardware is installed properly. Self-test is executed by selecting 'Configure System' 

from the Main System Window above ([F4]). In the Modules Configuration on page 5-4 

window, select each module installed in the System and press 'Self Test' to execute the self-test 

for each module. 

Refer to Modules Configuration on page 5-4 to learn how to run self-test on the modules and 

alter the system configuration to meet your specific needs. This needs to be done as part of the 

installation process. 

4-19


System Motherboard 


For each of the CheckSum Modules installed in the System, there is a module shown in the 

configuration window. In most cases, upon shipment, the configuration of your hardware will 

already be initialized. 

Be sure to connect a USB 2 cable between the PC and the USB control module. 

Once self-test has started, press the keys as prompted to sequence through the self-test. 

Save Configuration 

When self-test is completed for all modules in the test system, save the configuration data on 

disk, as prompted, for use the next time the System software starts up. 

Saving the configuration data on disk saves the current value for most selections of the 

Configure System window. 


The MultiWriter pps system contains one system motherboard (3800-103) and optionally an 

expansion motherboard (3800-104). 

The system motherboard provides connection to four MultiWriter (MW1 to MW4) control 

boards. Each expansion motherboard provides connection to four additional MultiWriter 

control boards (MW5 to MW8). 

Each MultiWriter control board (MW1 to MW4) provides programming signals for up to 24 

devices through the fixture interface 170-pin block connections to the Fixture Wiring on page 

12-1 Blocks A, B, C, and D. The motherboard has five 160-pin system blocks on page 4-24 

A, B, C, D, and K. 

4-20




Motherboard Assembly (3800-103) 

The system power (+5Vdc, +12Vdc and +24Vdc), controlled by the Emergency Stop and 

Programmer Power switch, for the motherboard assemblies connects to a System Power 

connector. A second connector allows the power to also be connected to an expansion 

motherboard (3800-104). 

Motherboard System Power Connectors 

4-21




The PS-UUT power and the enable signals are routed through the motherboard connectors to 

Block K. 

Motherboard DUT/UUT Power and Enable Connectors 

The Single-Point Probe and F1 Start signal (to the front panel flat, silver button) connect to 

the motherboard. 

Motherboard F1 and Single-Point Probe Connectors 

Several motherboard status and control signals are available at the J3 connector. These signals 

can be used with other systems such as handlers. 

Motherboard External I/O DB25 Connector (J3) 

4-22




+3.3V 

1000 

+5Vdc SW 

0.75A 

Dig I/O bit 6 

Dig I/O bit 5 

Dig I/O bit 8 

Dig I/O bit 7 

SW0 

SW1 

SW5 

SW7 

GND 

100 

100 

100 

100 

100 

100 

100 

100 

Red (FAIL) 

Green (PASS) 

Yellow (Busy) 

1 

14 

4 

17 

5 

18 

6 

19 

7 

20 

8 

21 

9 

22 

10 

23 

11 

24 

12 

25 

13 

2 

15 

3 

16 

100 

+3.3V 

1000 

100 

+3.3V 

1000 

100 

+3.3V 

1000 

100 

1nF 

GND 

1nF 

GND 

1nF 

GND 

1nF 

Dig I/O bit 2 

Dig I/O bit 1 

Dig I/O bit 4 

Dig I/O bit 3 

GND 

Motherboard External I/O DB25 Connector Signals 

Control signals for up to 2 pneumatic air valves and up to 2 vacuum valves are provided on the 

system motherboard. A 24Vdc signal is present on pin 2 of each connector. Pin 1 on each 

connector is controlled by the Fixture Control on page 14-45 setup for pneumatic air and 

Vacum on page 14-44 setup for vacuum. 

Motherboard Vacuum and Pneumatic Air Control Signal Connectors 

4-23


System 160 Pin Blocks 



For installations that do not use the standard 170-pin block fixture receiver system, the 

following provides information for the 160-pin block signals on the motherboard and 

expansion board. 

Motherboard Assembly (3800-103) 

4-24




Motherboard and Expansion Assembly (3800-104) 160-Pin Blocks (Top View) 

The pin numbers are referenced facing the topside of the assembly. The pins are numbered as 

pin 1-1 in the lower right corner, pin 1-16 in the upper right corner, pin 10-1 in the lower left 

corner, and pin 10-16 in the upper left corner. The pin layout is same for each 160-pin block. 

The motherboard blocks contain the system signals to control and communicate with the buffer 

modules. In addition, block A contains some system pins that are used for all test fixtures plus 

signals for the USB security device on page 6-21. The USB connections at the fixture 

interface are normally direct to the USB hub (bypassing the motherboard assembly) or the 

USB signals can be connected through the motherboard assembly at connector USB1. If the 

USB connection to the fixture interface is made direct to the USB hub then the USB signals 

will not be present on the Block A pins A10-11 to A10-15. 

The motherboard 160-pin block pin-out is defined in the following sections: 

160 Pin Block A on page 4-26 for Ports 1 to 24 and USB security device 

160 Pin Block B on page 4-29 for Ports 25 to 48 

160 Pin Block C on page 4-32 for Ports 49 to 72 

160 Pin Block D on page 4-36 for Ports 73 to 96 

160 Pin Block K on page 4-39 for PS-UUT power supplies #1 to #4 

4-25




The 160-pin block signals are defined in the same top view orientation as the board layout with 

pin 1 at the bottom of the column for each of the 10 columns (16 pins in each column). 

Block A Pin-Out (Ports 1:24) 

Block Pin Block : Signal 

A1-16 N/C 

A1-15 N/C 

A1-14 N/C 

A1-13 N/C 

A1-12 N/C 

A1-11 N/C 

A1-10 N/C 

A1-9 N/C 

A1-8 A : E– Ports 1:24 

A1-7 A : E+ Ports 1:24 

A1-6 A : I– Ports 1:24 

A1-5 A : I+ Ports 1:24 

A1-4 A : M– Ports 1:24 

A1-3 A : M+ Ports 1:24 

A1-2 A : C– Ports 1:24 

A1-1 A : C+ Ports 1:24 

A2-16 A : Port 4- 

A2-15 A : Port 4+ 

A2-14 A : Relay Port 4 

A2-13 N/C 

A2-12 A : Port 3- 

A2-11 A : Port 3+ 


A2-9 N/C 

A2-8 A : Port 2- 

A2-7 A : Port 2+ 


A2-5 N/C 

A2-4 A : Port 1- 

A2-3 A : Port 1+ 


A2-1 N/C 

A3-16 A : Port 8- 

A3-15 A : Port 8+ 


A3-13 N/C 

A3-12 A : Port 7- 

A3-11 A : Port 7+ 


A3-9 N/C 

A3-8 A : Port 6- 

A3-7 A : Port 6+ 


A3-5 N/C 

A3-4 A : Port 5- 

A3-3 A : Port 5+ 

4-26





A3-1 N/C 

A4-16 A : Port 12- 

A4-15 A : Port 12+ 


A4-13 N/C 

A4-12 A : Port 11- 

A4-11 A : Port 11+ 


A4-9 N/C 

A4-8 A : Port 10- 

A4-7 A : Port 10+ 


A4-5 N/C 

A4-4 A : Port 9- 

A4-3 A : Port 9+ 


A4-1 N/C 

A5-16 A : Port 16- 

A5-15 A : Port 16+ 


A5-13 N/C 

A5-12 A : Port 15- 

A5-11 A : Port 15+ 


A5-9 N/C 

A5-8 A : Port 14- 

A5-7 A : Port 14+ 


A5-5 N/C 

A5-4 A : Port 13- 

A5-3 A : Port 13+ 


A5-1 N/C 

A6-16 A : Port 20- 

A6-15 A : Port 20+ 


A6-13 N/C 

A6-12 A : Port 19- 

A6-11 A : Port 19+ 


A6-9 N/C 

A6-8 A : Port 18- 

A6-7 A : Port 18+ 


A6-5 N/C 

A6-4 A : Port 17- 

A6-3 A : Port 17+ 


A6-1 N/C 

4-27




A7-16 A : Port 24- 

A7-15 A : Port 24+ 


A7-13 N/C 

A7-12 A : Port 23- 

A7-11 A : Port 23+ 


A7-9 N/C 

A7-8 A : Port 22- 

A7-7 A : Port 22+ 


A7-5 N/C 

A7-4 A : Port 21- 

A7-3 A : Port 21+ 


A7-1 N/C 

A8-16 N/C 

A8-15 N/C 

A8-14 N/C 

A8-13 N/C 

A8-12 N/C 

A8-11 N/C 

A8-10 N/C 

A8-9 N/C 

A8-8 N/C 

A8-7 N/C 

A8-6 N/C 

A8-5 N/C 

A8-4 N/C 

A8-3 N/C 

A8-2 N/C 

A8-1 N/C 

A9-16 A : Fixture Present/ 

A9-15 A : TXD (MW1 RXD) 

A9-14 A : GND 

A9-13 A : RXD (MW1 TXD) 

A9-12 A : GND 

A9-11 A : I2C Data1 

A9-10 A : GND 

A9-9 A : I2C Clock1 

A9-8 N/C 

A9-7 A : Probe Input 

A9-6 A : Fixture 2 Control/ 

A9-5 A : GND 

A9-4 A : Fixture 2 Ready/ 

A9-3 A : Fixture 1 Control/ 

A9-2 A : GND 

A9-1 A : Fixture 1 Ready/ 

A10-16 N/C 

A10-15 A : USB VBUS (+5V) (see the 

4-28




USB wiring comments on page 4- 

25) 

A10-14 A : USB D- 

A10-13 A : USB D+ 

A10-12 A : USB GND 

A10-11 A : USB Shield 

A10-10 A : GND 

A10-9 N/C 

A10-8 A : +5Vdc SW1 

A10-7 N/C 

A10-6 A : +12Vdc SW1 

A10-5 N/C 

A10-4 A : +24Vdc SW1 

A10-3 N/C 

A10-2 A : HUB PS- 

A10-1 A : HUB PS+ 

Note: If Fixture Present/ (Block Pin A9-16) is not connected to the MW FIX IO module or 

to a GND pin, the PS-UUT switched power outputs (+5Vdc SW, +12Vdc SW, and +24Vdc 

SW) will not be enabled and switched power will not be available to the fixture. 

Block B Pin-Out (Ports 25:48) 


B1-16 N/C 

B1-15 N/C 

B1-14 N/C 

B1-13 N/C 

B1-12 N/C 

B1-11 N/C 

B1-10 N/C 

B1-9 N/C 

B1-8 B : E– Ports 25:48 

B1-7 B : E+ Ports 25:48 

B1-6 B : I– Ports 25:48 

B1-5 B : I+ Ports 25:48 

B1-4 B : M– Ports 25:48 

B1-3 B : M+ Ports 25:48 

B1-2 B : C– Ports 25:48 

B1-1 B : C+ Ports 25:48 

B2-16 B : Port 28- 

B2-15 B : Port 28+ 

B2-14 B : Relay Port 28 

B2-13 N/C 

B2-12 B : Port 27- 

B2-11 B : Port 27+ 


B2-9 N/C 

B2-8 B : Port 26- 

B2-7 B : Port 26+ 

4-29





B2-5 N/C 

B2-4 B : Port 25- 

B2-3 B : Port 25+ 


B2-1 N/C 

B3-16 B : Port 32- 

B3-15 B : Port 32+ 


B3-13 N/C 

B3-12 B : Port 31- 

B3-11 B : Port 31+ 


B3-9 N/C 

B3-8 B : Port 30- 

B3-7 B : Port 30+ 


B3-5 N/C 

B3-4 B : Port 29- 

B3-3 B : Port 29+ 


B3-1 N/C 

B4-16 B : Port 36- 

B4-15 B : Port 36+ 


B4-13 N/C 

B4-12 B : Port 35- 

B4-11 B : Port 35+ 


B4-9 N/C 

B4-8 B : Port 34- 

B4-7 B : Port 34+ 


B4-5 N/C 

B4-4 B : Port 33- 

B4-3 B : Port 33+ 


B4-1 N/C 

B5-16 B : Port 40- 

B5-15 B : Port 40+ 


B5-13 N/C 

B5-12 B : Port 39- 

B5-11 B : Port 39+ 


B5-9 N/C 

B5-8 B : Port 38- 

B5-7 B : Port 38+ 


B5-5 N/C 

4-30




B5-4 B : Port 37- 

B5-3 B : Port 37+ 


B5-1 N/C 

B6-16 B : Port 44- 

B6-15 B : Port 44+ 


B6-13 N/C 

B6-12 B : Port 43- 

B6-11 B : Port 43+ 


B6-9 N/C 

B6-8 B : Port 42- 

B6-7 B : Port 42+ 


B6-5 N/C 

B6-4 B : Port 41- 

B6-3 B : Port 41+ 


B6-1 N/C 

B7-16 B : Port 48- 

B7-15 B : Port 48+ 


B7-13 N/C 

B7-12 B : Port 47- 

B7-11 B : Port 47+ 


B7-9 N/C 

B7-8 B : Port 46- 

B7-7 B : Port 46+ 


B7-5 N/C 

B7-4 B : Port 45- 

B7-3 B : Port 45+ 


B7-1 N/C 

B8-16 N/C 

B8-15 N/C 

B8-14 N/C 

B8-13 N/C 

B8-12 N/C 

B8-11 N/C 

B8-10 N/C 

B8-9 N/C 

B8-8 N/C 

B8-7 N/C 

B8-6 N/C 

B8-5 N/C 

B8-4 N/C 

B8-3 N/C 

4-31




B8-2 N/C 

B8-1 N/C 

B9-16 B : GND 

B9-15 B : TXD (MW2 RXD) 

B9-14 B : GND 

B9-13 B : RXD (MW2 TXD) 

B9-12 B : GND 

B9-11 B : I2C Data2 

B9-10 B : GND 

B9-9 B : I2C Clock2 

B9-8 N/C 

B9-7 N/C 

B9-6 N/C 

B9-5 N/C 

B9-4 N/C 

B9-3 N/C 

B9-2 N/C 

B9-1 N/C 

B10-16 N/C 

B10-15 N/C 

B10-14 N/C 

B10-13 N/C 

B10-12 N/C 

B10-11 N/C 

B10-10 B : GND 

B10-9 N/C 

B10-8 B : +5Vdc SW2 

B10-7 N/C 

B10-6 B : +12Vdc SW2 

B10-5 N/C 

B10-4 B : +24Vdc SW2 

B10-3 N/C 

B10-2 N/C 

B10-1 N/C 

Block C Pin-Out (Ports 49:72) 


C1-16 N/C 

C1-15 N/C 

C1-14 N/C 

C1-13 N/C 

C1-12 N/C 

C1-11 N/C 

C1-10 N/C 

C1-9 N/C 

C1-8 C : E– Ports 49:72 

C1-7 C : E+ Ports 49:72 

C1-6 C : I– Ports 49:72 

C1-5 C : I+ Ports 49:72 

4-32




C1-4 C : M– Ports 49:72 

C1-3 C : M+ Ports 49:72 

C1-2 C : C– Ports 49:72 

C1-1 C : C+ Ports 49:72 

C2-16 C : Port 52- 

C2-15 C : Port 52+ 

C2-14 C : Relay Port 52 

C2-13 N/C 

C2-12 C : Port 51- 

C2-11 C : Port 51+ 


C2-9 N/C 

C2-8 C : Port 50- 

C2-7 C : Port 50+ 


C2-5 N/C 

C2-4 C : Port 49- 

C2-3 C : Port 49+ 


C2-1 N/C 

C3-16 C : Port 56- 

C3-15 C : Port 56+ 


C3-13 N/C 

C3-12 C : Port 55- 

C3-11 C : Port 55+ 


C3-9 N/C 

C3-8 C : Port 54- 

C3-7 C : Port 54+ 


C3-5 N/C 

C3-4 C : Port 53- 

C3-3 C : Port 53+ 


C3-1 N/C 

C4-16 C : Port 60- 

C4-15 C : Port 60+ 


C4-13 N/C 

C4-12 C : Port 59- 

C4-11 C : Port 59+ 


C4-9 N/C 

C4-8 C : Port 58- 

C4-7 C : Port 58+ 


C4-5 N/C 

C4-4 C : Port 57- 

C4-3 C : Port 57+ 

4-33





C4-1 N/C 

C5-16 C : Port 64- 

C5-15 C : Port 64+ 


C5-13 N/C 

C5-12 C : Port 63- 

C5-11 C : Port 63+ 


C5-9 N/C 

C5-8 C : Port 62- 

C5-7 C : Port 62+ 


C5-5 N/C 

C5-4 C : Port 61- 

C5-3 C : Port 61+ 


C5-1 N/C 

C6-16 C : Port 68- 

C6-15 C : Port 68+ 


C6-13 N/C 

C6-12 C : Port 67- 

C6-11 C : Port 67+ 


C6-9 N/C 

C6-8 C : Port 66- 

C6-7 C : Port 66+ 


C6-5 N/C 

C6-4 C : Port 65- 

C6-3 C : Port 65+ 


C6-1 N/C 

C7-16 C : Port 72- 

C7-15 C : Port 72+ 


C7-13 N/C 

C7-12 C : Port 71- 

C7-11 C : Port 71+ 


C7-9 N/C 

C7-8 C : Port 70- 

C7-7 C : Port 70+ 


C7-5 N/C 

C7-4 C : Port 69- 

C7-3 C : Port 69+ 


C7-1 N/C 

4-34




C8-16 N/C 

C8-15 N/C 

C8-14 N/C 

C8-13 N/C 

C8-12 N/C 

C8-11 N/C 

C8-10 N/C 

C8-9 N/C 

C8-8 N/C 

C8-7 N/C 

C8-6 N/C 

C8-5 N/C 

C8-4 N/C 

C8-3 N/C 

C8-2 N/C 

C8-1 N/C 

C9-16 C : GND 

C9-15 C : TXD (MW3 RXD) 

C9-14 C : GND 

C9-13 C : RXD (MW3 TXD) 

C9-12 C : GND 

C9-11 C : I2C Data3 

C9-10 C : GND 

C9-9 C : I2C Clock3 

C9-8 N/C 

C9-7 N/C 

C9-6 N/C 

C9-5 N/C 

C9-4 N/C 

C9-3 N/C 

C9-2 N/C 

C9-1 N/C 

C10-16 N/C 

C10-15 N/C 

C10-14 N/C 

C10-13 N/C 

C10-12 N/C 

C10-11 N/C 

C10-10 C : GND 

C10-9 N/C 

C10-8 C : +5Vdc SW3 

C10-7 N/C 

C10-6 C : +12Vdc SW3 

C10-5 N/C 

C10-4 C : +24Vdc SW3 

C10-3 N/C 

C10-2 N/C 

C10-1 N/C 

4-35




Block D Pin-Out (Ports 73:96) 


D1-16 N/C 

D1-15 N/C 

D1-14 N/C 

D1-13 N/C 

D1-12 N/C 

D1-11 N/C 

D1-10 N/C 

D1-9 N/C 

D1-8 D : E– Ports 73:96 

D1-7 D : E+ Ports 73:96 

D1-6 D : I– Ports 73:96 

D1-5 D : I+ Ports 73:96 

D1-4 D : M– Ports 73:96 

D1-3 D : M+ Ports 73:96 

D1-2 D : C– Ports 73:96 

D1-1 D : C+ Ports 73:96 

D2-16 D : Port 76- 

D2-15 D : Port 76+ 

D2-14 D : Relay Port 76 

D2-13 N/C 

D2-12 D : Port 75- 

D2-11 D : Port 75+ 


D2-9 N/C 

D2-8 D : Port 74- 

D2-7 D : Port 74+ 


D2-5 N/C 

D2-4 D : Port 73- 

D2-3 D : Port 73+ 


D2-1 N/C 

D3-16 D : Port 80- 

D3-15 D : Port 80+ 


D3-13 N/C 

D3-12 D : Port 79- 

D3-11 D : Port 79+ 


D3-9 N/C 

D3-8 D : Port 78- 

D3-7 D : Port 78+ 


D3-5 N/C 

D3-4 D : Port 77- 

D3-3 D : Port 77+ 


D3-1 N/C 

4-36




D4-16 D : Port 84- 

D4-15 D : Port 84+ 


D4-13 N/C 

D4-12 D : Port 83- 

D4-11 D : Port 83+ 


D4-9 N/C 

D4-8 D : Port 82- 

D4-7 D : Port 82+ 


D4-5 N/C 

D4-4 D : Port 81- 

D4-3 D : Port 81+ 


D4-1 N/C 

D5-16 D : Port 88- 

D5-15 D : Port 88+ 


D5-13 N/C 

D5-12 D : Port 87- 

D5-11 D : Port 87+ 


D5-9 N/C 

D5-8 D : Port 86- 

D5-7 D : Port 86+ 


D5-5 N/C 

D5-4 D : Port 85- 

D5-3 D : Port 85+ 


D5-1 N/C 

D6-16 D : Port 92- 

D6-15 D : Port 92+ 


D6-13 N/C 

D6-12 D : Port 91- 

D6-11 D : Port 91+ 


D6-9 N/C 

D6-8 D : Port 90- 

D6-7 D : Port 90+ 


D6-5 N/C 

D6-4 D : Port 89- 

D6-3 D : Port 89+ 


D6-1 N/C 

D7-16 D : Port 96- 

D7-15 D : Port 96+ 

4-37





D7-13 N/C 

D7-12 D : Port 95- 

D7-11 D : Port 95+ 


D7-9 N/C 

D7-8 D : Port 94- 

D7-7 D : Port 94+ 


D7-5 N/C 

D7-4 D : Port 93- 

D7-3 D : Port 93+ 


D7-1 N/C 

D8-16 N/C 

D8-15 N/C 

D8-14 N/C 

D8-13 N/C 

D8-12 N/C 

D8-11 N/C 

D8-10 N/C 

D8-9 N/C 

D8-8 N/C 

D8-7 N/C 

D8-6 N/C 

D8-5 N/C 

D8-4 N/C 

D8-3 N/C 

D8-2 N/C 

D8-1 N/C 

D9-16 D : GND 

D9-15 D : TXD (MW4 RXD) 

D9-14 D : GND 

D9-13 D : RXD (MW4 TXD) 

D9-12 D : GND 

D9-11 D : I2C Data4 

D9-10 D : GND 

D9-9 D : I2C Clock4 

D9-8 N/C 

D9-7 N/C 

D9-6 N/C 

D9-5 N/C 

D9-4 N/C 

D9-3 N/C 

D9-2 N/C 

D9-1 N/C 

D10-16 N/C 

D10-15 N/C 

D10-14 N/C 

D10-13 N/C 

4-38




D10-12 N/C 

D10-11 N/C 

D10-10 D : GND 

D10-9 N/C 

D10-8 D : +5Vdc SW4 

D10-7 N/C 

D10-6 D : +12Vdc SW4 

D10-5 N/C 

D10-4 D : +24Vdc SW4 

D10-3 N/C 

D10-2 N/C 

D10-1 N/C 

Block K Pin-Out Pin-Out (Power Supplies PS#1 to PS#4 and USB security device) 


K1-16 K : PS#1 +V 

K1-15 K : PS#1 +V 

K1-14 K : PS#1 +V 

K1-13 K : PS#1 +V 

K1-12 K : PS#1 +V 

K1-11 K : PS#1 +V 

K1-10 K : PS#1 +V 

K1-9 K : PS#1 +S 

K1-8 K : PS#1 -S 

K1-7 K : PS#1 -V 

K1-6 K : PS#1 -V 

K1-5 K : PS#1 -V 

K1-4 K : PS#1 -V 

K1-3 K : PS#1 -V 

K1-2 K : PS#1 -V 

K1-1 K : PS#1 -V 

K2-16 K : PS#2 +V 

K2-15 K : PS#2 +V 

K2-14 K : PS#2 +V 

K2-13 K : PS#2 +V 

K2-12 K : PS#2 +V 

K2-11 K : PS#2 +V 

K2-10 K : PS#2 +V 

K2-9 K : PS#2 +S 

K2-8 K : PS#2 -S 

K2-7 K : PS#2 -V 

K2-6 K : PS#2 -V 

K2-5 K : PS#2 -V 

K2-4 K : PS#2 -V 

K2-3 K : PS#2 -V 

K2-2 K : PS#2 -V 

K2-1 K : PS#2 -V 

K3-16 K : PS#3 +V 

K3-15 K : PS#3 +V 

4-39




K3-14 K : PS#3 +V 

K3-13 K : PS#3 +V 

K3-12 K : PS#3 +V 

K3-11 K : PS#3 +V 

K3-10 K : PS#3 +V 

K3-9 K : PS#3 +S 

K3-8 K : PS#3 -S 

K3-7 K : PS#3 -V 

K3-6 K : PS#3 -V 

K3-5 K : PS#3 -V 

K3-4 K : PS#3 -V 

K3-3 K : PS#3 -V 

K3-2 K : PS#3 -V 

K3-1 K : PS#3 -V 

K4-16 K : PS#4 +V 

K4-15 K : PS#4 +V 

K4-14 K : PS#4 +V 

K4-13 K : PS#4 +V 

K4-12 K : PS#4 +V 

K4-11 K : PS#4 +V 

K4-10 K : PS#4 +V 

K4-9 K : PS#4 +S 

K4-8 K : PS#4 -S 

K4-7 K : PS#4 -V 

K4-6 K : PS#4 -V 

K4-5 K : PS#4 -V 

K4-4 K : PS#4 -V 

K4-3 K : PS#4 -V 

K4-2 K : PS#4 -V 

K4-1 K : PS#4 -V 

K5-16 N/C 

K5-15 N/C 

K5-14 N/C 

K5-13 N/C 

K5-12 N/C 

K5-11 N/C 

K5-10 N/C 

K5-9 N/C 

K5-8 N/C 

K5-7 N/C 

K5-6 N/C 

K5-5 N/C 

K5-4 N/C 

K5-3 N/C 

K5-2 N/C 

K5-1 N/C 

K6-16 N/C 

K6-15 N/C 

K6-14 N/C 

K6-13 N/C 

4-40




K6-12 N/C 

K6-11 N/C 

K6-10 N/C 

K6-9 N/C 

K6-8 N/C 

K6-7 N/C 

K6-6 N/C 

K6-5 N/C 

K6-4 N/C 

K6-3 N/C 

K6-2 N/C 

K6-1 N/C 

K7-16 N/C 

K7-15 N/C 

K7-14 N/C 

K7-13 N/C 

K7-12 N/C 

K7-11 N/C 

K7-10 N/C 

K7-9 N/C 

K7-8 N/C 

K7-7 N/C 

K7-6 N/C 

K7-5 N/C 

K7-4 N/C 

K7-3 N/C 

K7-2 N/C 

K7-1 N/C 

K8-16 N/C 

K8-15 N/C 

K8-14 N/C 

K8-13 N/C 

K8-12 N/C 

K8-11 N/C 

K8-10 N/C 

K8-9 N/C 

K8-8 N/C 

K8-7 N/C 

K8-6 N/C 

K8-5 N/C 

K8-4 N/C 

K8-3 N/C 

K8-2 N/C 

K8-1 N/C 

K9-16 N/C 

K9-15 N/C 

K9-14 N/C 

K9-13 N/C 

K9-12 N/C 

K9-11 N/C 

4-41




K9-10 N/C 

K9-9 N/C 

K9-8 N/C 

K9-7 N/C 

K9-6 N/C 

K9-5 N/C 

K9-4 N/C 

K9-3 N/C 

K9-2 N/C 

K9-1 N/C 

K10-16 N/C 

K10-15 N/C 

K10-14 N/C 

K10-13 N/C 

K10-12 N/C 

K10-11 N/C 

K10-10 N/C 

K10-9 N/C 

K10-8 N/C 

K10-7 N/C 

K10-6 N/C 

K10-5 N/C 

K10-4 N/C 

K10-3 N/C 

K10-2 N/C 

K10-1 N/C 

Block K Notes: 

The “–S“ and “+S” pins are the remote Sense pins. For each power supply, 

connect –S to –V and +S to +V at the load, e.g., connect “PS#1 –S” to 

“PS#1 –V” and also connect “PS#1 +S” to “PS#1 +V”. 

4-42

Chapter 5 

System Configuration 


Overview 

The Configure System window is used to either temporarily or permanently change the 

configuration of the System. This applies to characteristics such as printer configuration, 

report configuration, automatic reporting, hardware setup, and so on. 

Almost all of the attributes configured into the System can be saved on the System disk with 

the 'Save' button of the Configure System window. 

If you use password protection, users cannot access the Configure System window without 

permission. This provides System integrity against accidental configuration changes.




Configure System Menu 

• Modules allows you to enter the hardware configuration of CheckSum Modules in the 

System, and to perform self-test on them. See Modules Configuration on page 5-4. 

• Environment allows you to enter information about the configuration of system reports, 

the directory structure for the system, and password protection. See Environment 

Configuration on page 5-8. 

• External Hardware allows you to enter information about the configuration of printer, 

beeper, and the USB disconnect warning. See External Hardware on page 5-22. 

• Fixture allows you to enter information about the configuration of your fixturing system. 

The fixture selection determines the connector information shown in the Connector 

column of the Modules window and in the fixture wiring reports. See Fixture on page 5- 

23. 

• Login User allows you to enter a user (operator) name into the System. If the system is 

configured with login names turned on, a user must be logged in at all times. Optionally, a 

password may be required for each user. The system can be configured so that different 

users have different access privileges and may see different menu options. Login 

privileges are defined in the 'Configure System' section of the software that can be 

accessed from the main window. 

5-2




Configure System Window 

Picking one of the first four entries causes the Configure System Window to appear with the 

appropriate tab selected as shown in the following figure for Modules Configuration. 

Configure System Window 

Save Button 

The Save button is used to save your configuration selections to the disk drive. When you 

save the configuration, each time you restart the system software you will not need to 

reconfigure your System. The configuration file is transparent to you. It is named 

"$PPS$.DAT" and is stored in the same directory as the system software. Selection of 'Save' 

saves the report configuration, automatic reporting configuration, the I/O module 

configuration, the active points, the measurement characteristics, the printout configuration 

parameters, the passwords, and the System calibration constants. With a command line 

parameter, you can also specify an alternate path for the configuration file. This is useful in 

networking environments so that test systems on the network can share the same system 

executable file but have their own unique calibration and configuration data. 

5-3


Modules Configuration 


Print Button 

Use the Print button to printout the complete system configuration setup for documentation 

purposes. Select Print To File to create a text file that can be stored and emailed as an 

attachment. 


The Modules page is used to specify the hardware configuration of CheckSum Modules in 

your controller. With its use, you can specify how many modules you have, their address 

jumpers, and their connection to the fixture system. With this window you also run self-test on 

the modules to ensure that they are operating properly and to self-calibrate them. The Print 

feature can be used to document the configuration. Print To File allows you to create a text 

file that can be stored and emailed as an attachment. The Modules page is shown in the 

following figure. 

Modules Page 

5-4




Module Configuration 

The top section of the Modules page shows a list of the CheckSum modules in the System. 

Each line represents one slot in the system chassis. Note that the module order does not 

necessarily have to match the order in your controller, although as you insert modules, a 

logical order is used by the System as a default. The Modify button, or double-click on a 

selection, can be used to change most entries. 

The Auto Detect button can be used to detect some modules automatically. The system 

searches for modules having the board select feature and inserts any modules that it finds. 

This feature only works for modules that have a board select address. Any modules in the list 

that are not detected are removed. 

Note 

A question mark on the left side of the line of a module that has a board 

select address indicates that the module does not appear to be present at the 

specified base address and/or board select setting. A question mark at the 

left side of a GPIB module indicates that it is installed in the system but 

does not appear to be at the specified base address. 

• The Module column shows the name of each module. 

• The Points column shows the test points used by the module. 

• The Base Address column shows the base I/O address used by the module. Except for 

modules that have board select addressing (see the discussion of board select addressing in 

the next paragraph), the I/O addresses cannot overlap. The addresses can be shown in 

decimal or hexadecimal, the 'Address Mode' button is used to select the preferred mode. 

– The Jumpers column shows the jumper positions on the module that will achieve the 

specified address. 

– The Addresses column shows the I/O address range currently specified for the 

module. You can change either the jumper or addresses by clicking on the 'Modify' 

button. If you change either the address or the jumpers, the System will change the 

other accordingly. If you numerically enter the base address, the System will not 

accept numbers that cannot be set by the jumpers for that module. 

• Board Select column: Not Applicable (N/A) 

• The Interface column specifies which fixture receiver interface connectors that the 

module will be connected. For example, if J1 is specified, the System expects that the 

module will be connected to J1 on the fixture receiver. If the module has more than one 

connector, the listed connector is the first connector of the module, then the others are 

added in sequence. The entries in this field are used for the Wire Run Report (I/F Block 

column) to document your interface block (I/F Block) connections. 

• The Relay Bus column specifies the internal 2-wire relay bus connection. Not all modules 

support connection to this 2-wire bus. 

• Module Specific allows entry and control of settings unique to a module. 

5-5


Adding/Deleting Modules 


Print 



attachment. 

Other Configure topics: 

• Adding/Deleting Modules below 

• Reverting/Saving Configuration Information below 

• Module Self-Test below 

• System Module on page 5-7 

• Other Modules on page 5-7 

Adding/Deleting Modules 

If you want to add a new module to the System configuration, use the 'Add Module' button. 

With this button, you obtain a list of the module types that can be added. When you choose 

one, it is added to the configuration table. It is assigned a default base address, and location in 

the table. The location, while not required, is one that should work well with the internal 

cabling. You can select a module in the configuration with the mouse, then use the 'Delete' 

button to eliminate it from the list. 

Reverting/Saving Configuration Information 

If you modify your configuration unsuccessfully, you can recover with the 'Revert' button. 

Once you have selected this function, you can elect to either reset the window to the factory 

default settings, or to reset it to the values when you started the system software. 

The 'Save' feature can be used to save the settings and self-test calibration data on the disk. 

You should always save the configuration settings after running self-test or changing the 

configuration of your system so that the changes will be available next time you start up the 

PPS software. When you save the settings, everything in all the Configure System pages are 

saved on the disk. 

Built-In Self-Test 

You can use the 'Self-Test' button to invoke a self-test on the currently selected module. 

Normally, you should start at the top of the configuration table, and work down module-bymodule. 

Self-test provides several basic functions. It calibrates the system speed so that the System 

will operate correctly in a wide variety of processor environments. It then checks the modules 

5-6



Self-Test of the System Controller 

in your system to ensure that they are functional. You should run self-test twice a year or if 

you suspect any problems with the System's operation. 

When self-test has started, follow the prompts until it is completed. It will report any errors 

that it finds. 

Beside each module that has been self-tested, you will see a green check to show that it has 

passed, or a red X that shows it has failed. A smaller check mark indicates the self-test was 

canceled before it finished and no failures were found. The "?" indicates that the system was 

not able to locate the module as defined. Check the addressing specification in this case. 

Note 

Ensure that no test assemblies are connected during the self-test. 

Otherwise, you may get incorrect test results. 

In the event that a failure occurs, you are presented with an error message describing the nature 

of the failure. 

When the test is complete, it is important that you save the System configuration data on the 

disk with use of the 'Save' button of the Configure System window. When you save the 

configuration data, it saves the newly determined calibration constants on the disk drive so that 

they will not be lost when you power down the computer or complete your use of the system 

software. 

Self-Test of the System Controller 

The system controller self-test confirms proper operation of the system programming module. 

Self-Test of Power Supplies 

The system power supplies are tested to insure they are correctly configured. 

Other Modules 

If you have other optional CheckSum modules installed in your test system, self-test is 

normally available for each module type. Follow the prompts when executing self-test, and 

see the Chapter describing the Module for any special requirements regarding the Module. 

5-7


Environment Configuration 


Environment Configuration 

The Environment page is used to specify the configuration of reporting, directory structure, 

and user accounts. The Environment Configuration window is shown in the following figure. 

Environment Configuration Window 

Topic details: 

• Configure Reporting below 

• Configure Directories/Locations on page 5-16 

• Manage User Accounts on page 5-18 

Configure Reporting 

With the 'Configure Reporting' button of the Environment page, you can obtain the Configure 

Reporting window shown in the following figure. This window is used to specify report 

formats, SPC logging and automatic reporting for the System. 

The Configure Reporting window works like a standard Windows tab-oriented selection page. 

Clicking the tab at the top of the window, shows the setup items for the selection: 

• SPC Logging on page 5-9 

• Automatic Test Results Report on page 5-10 

5-8




• Test Results on page 5-11 

• Batch Report on page 5-14 

• General on page 5-15 

• Test Program on page 5-16 

The following is a description of the items on each tab: 

SPC Logging tab: 

Configure Reporting Window - SPC Logging 

• Statistics Data Logged is used to turn on or off SPC logging and specify how much data 

is saved from testing for SPC analysis. If the box is not checked, no test results data is 

saved. If it is turned on (box is checked) 'Summary' information about the test such as 

pass/fail status, test time, operator, serial number and so on is saved. No detailed test step 

results are saved unless either the Pass or Fail Results box is checked. 

– Pass Results saves detailed information about the test steps that pass. 

– Fail Results saves detailed information about the test steps that fail. 

Most installations that use SPC logging save Fail Results information. This allows you to 

obtain Production Reports and Pareto Charts. When you are debugging test programs, it is 

normal to save Pass Results. This allows you to obtain X-Bar/Sigma reports for finetuning 

the test program. 

• Operator Name specifies whether the SPC data contains the operator name. The operator 

name is taken from the login name. 

5-9




Path allows you to specify which directory your statistics data files will be saved in. The 

statistics data is saved in comma-delimited ASCII files. Each day, a new file is generated that 

is named YYYYMMDD.DAT. For example, the SPC data file name generated on December 

1, 2010 is named ' 20101201.DAT'. 

Automatic Test Results Report tab: 

Configure Reporting Window - Automatic Test Results Report 

• Automatic Test Results Report can be turned on or off. This allows you to specify 

reporting that happens automatically after testing. Report On allows you to specify 'all 

assemblies' (always print a test report), or 'failed assemblies' (print a report if the assembly 

fails). Most installations that use automatic reporting specify failure-only reports (see 

Type). Send to allows you to direct the test report to one of several destinations. You can 

choose a printer connected to one of the printer or COM ports, or to a file. If a file name is 

specified, the file is appended with each new report. Type allows you to specify what the 

test report contains. You can choose between failure data only or all test results. Most 

installations choose to use reports that contain failure data only. Filename and Path 

specify a file that will contain the test reports if the box is checked (enabled). 

• Automatic Batch Report can be turned on or off. If turned on, the System automatically 

generates a batch report each time a new test program is loaded, or the operator returns to 

the Main System window. 

• Send Automatic Batch Report to allows you to direct the batch report to one of several 

destinations. You can choose a printer connected to one of the printer or COM ports, or to 

a file. If a file name is specified, the file is appended with each new report. 

5-10




• Automatic Batch Report Data Path specifies a directory name that will contain the test 

reports if you have specified 'Send Automatic Batch Report to a file. 

Test Results tab: 

Configure Reporting Window - Test Results 

• Report Format Width, Column Formats, and Max Lines allow you to customize the 

reports to meet your requirements. Max Lines (per UUT) allow you to limit the total 

report length. By limiting the maximum number of lines, you can prevent excessively 

long reports that result from catastrophic failures, such as when the test is started without a 

UUT present. For panelized assemblies, the MAX Lines limit is applied separately to each 

PCB tested. A length of 0 allows for unlimited lines. If you are using a CheckSum Model 

T-120-2, select the 40-column width setting. If you are using a standard 80-column 

printer, select the 80-column width setting. 

5-11




• Column Format Modify selection displays a window to control the test and batch reports. 

With this selection, you obtain the Configure 80/40 Column Formats Window shown in 

the following figure. In this window, you can chose which items that you want to include 

in the report, and the order in which they occur. To eliminate an item from the list, click 

on the line, then press the 'Delete' button. To add a new field to the list, click on a field in 

the list and press the 'Insert' key. You can then select the field to add. To change the 

order, click on the item that you wish to reorder, then use the up and down arrow buttons 

to move it to the desired position. The 'Default' button returns the window to the factory 

defaults. 

Configure 80/40 Column Formats 

• Test Report Headers allows you to turn on and off data that is included in the header of 

the test report. The items that you can turn on and off include dashed lines, test title, test 

facility, assembly name, total failures, date/time, model ID, column headers, UUT serial 

number, batch ID, system ID, and operator name (login name). 

5-12




• Test Report Headers Special Line allows you to include a special string of text in the test 

report header. You may enter a line of up to 32 characters. If nothing is entered, the 

reports do not contain this special line. If something is entered, it is placed in the header of 

the report, left justified. If the line contains a colon, the information before the colon 

(including the colon) is placed in the left column, and the information after the colon is 

placed in the second column aligned with the other header items. This special line of text 

can be used for any information that you would like included in the reports. For example, 

if you would like to have the operator initial each test report, you could use the entry 

'Operator Initials:__________'. 

Additional lines can be added at the end of the header section and at the beginning of the 

body of the test report. These additional lines are only added if special files exist in the 

test system software installation directory (normally C:\checksum) or C:\checksum\temp if 

this temporary directory was specified in the Directories/Locations setup. The names of 

two of these files are $RHDR$.DAT and $RBODY$.DAT. The contents of the 

$RHDR$.DAT file are added to the end of the header section. The contents of the 

$RBODY$.DAT file are added at the beginning of the body of the test report. Two other 

temporary files can also be used for this purpose, the names of these two additional 

temporary files are $RHDRT$.DAT and $RBODYT$.DAT. The contents are added in the 

same sections of the test report. You need to write (see MEMS) these temporary files 

during the test program since the files are automatically deleted by the system each time 

the test program is executed. 

• Get UUT Serial Number allows you to configure the system for serial number (UUT ID) 

tracking of UUTs. With this option, you can specify that the operator enters the serial 

number 'After testing', 'Before testing', 'When Reported', or 'No' for no entry. At the point 

of execution that you specify, the System displays a dialog box for entry of the serial 

number. It can be typed in, or if you have a wedge-style bar-code scanner on your System, 

it can be bar-coded in. Wedge-style bar-code scanners make the bar-coded data look just 

like operator entry. 

• Get Batch ID allows you to configure the system for tracking batch numbers or 

identifiers. With this option, you can specify that the operator enters the batch (or lot) ID 

'After testing', 'Before testing', 'When Reported', or 'No' for no entry. At the point of 

execution that you specify, the System displays a dialog box for entry of the Batch ID. It 

can be typed in, or if you have a wedge-style bar-code scanner on your System, it can be 

bar-coded in. 

5-13




Batch Report tab: 

Configure Reporting Window - Batch Report 

• Batch Report Header Special Line allows you to include a special string of text in the 

batch report header. You may enter a line of up to 32 characters. If nothing is entered, the 

reports do not contain this special line. If something is entered, it is placed in the header of 

the report, left justified. If the line contains a colon, the information before the colon 



can be used for any information that you would like included in the batch report. 

• Test Screen Yield % when checked, will show the Yield% in the Pareto information 

(lower right corner) on the Test Window on page 7-5. If unchecked, the number of batch 

Pass and Fail assemblies will be shown: 

Test Window with Batch Setup for Yield%, checked or unchecked 

5-14




General tab: 

Configure Reporting Window - General 

• Facility Name allows entry of a string of characters that is included in the test result 

reports. For example, you can use this to list items such as your company name or testing 

department. 

• System ID allows entry of a string of characters that can be used to specify the name of 

the tester that is used. This is typically used in companies that you have multiple test 

stations. The contents of this string are included in the test result reports. 

• Page Headers/Footers allows you to turn on and off data that is included in the header of 

each page in the System reports. The items that you can turn on and off include the report 

type, the System ID, the date/time, and the page number. As default, these items are all 

turned on. 

• Viewer allows you to specify what application is used to view reports. The default is 

'WordPad', part of the Windows standard operating software. 

• Date Format allows you to specify the format used for reports. 

5-15


Configure Directories/Locations 


Test Program tab: 

Configure Reporting Window - Test Program 

• Special Line allows you to include a special string of text in the test program report 

header. You may enter a line of up to 32 characters. If nothing is entered, the reports do 

not contain this special line. If something is entered, it is placed in the header of the 

report, left justified. If the line contains a colon, the information before the colon 



can be used for any special information that you would like included in the reports. 

• Automatic Warning Cross Checks allows you to automatically Perform Cross Checks to 

identify problems in the test program that may not be obvious before exiting the editor, see 

the Tools menu, Perform Cross Checks on page 9-21. This will write a file named 

chkrpt.txt into the Temporary Files directory setting below. 


With the 'Directories/Locations' button of the Environment page, you can obtain the window 

shown in the following figure. 

5-16




Directories/Locations Configuration 

The Directories/Locations Configuration window allows you to set up the directory structure 

for your System software. These directory locations can be set up in other locations. Options 

include: 

• Programs entry specifies the test program directory. 

• Test Results Report entry specifies the location of test results reports that are written to a 

file. 

• Statistics Data entry specifies the location of saved SPC data. 

• Automatic Batch Report entry specifies the location of batch reports that are directed to a 

file name. 

• RunT Programs entry specifies the directory for sub-programs (RunT test programs). 

The test executive looks in the RunT test program directory first and if the test program is 

not found, it then looks in the Test Programs directory. 

• Temporary Files entry specifies the directory where temporary files from the System are 

written. These include files such as interim test results while a final test report is being 

collated. 

• Skipped PCB Input File specifies the directory and file name where the system will read 

or write the file with the list of Skipped PCBs, see MemS on page 14-32 ranges 56 and 57. 

5-17


Manage User Accounts 


Example file skips.xml: 

 

 

2 

3 

 

• UUT ID Input File specifies the directory and file name where the system will read or 

write the file with the UUT IDs (e.g., serial numbers), see MemS on page 14-32 ranges 60 

and 61. 

Example file sns.xml: 

 

 

 

1 

ABC123 

 

 

2 

ABC124 

 

 

3 

ABC125 

 

 

Manage User Accounts 

With the 'Manage User Accounts' button of the Environment page, you can enable user log-ins, 

passwords, and permission of activities by user. This activity is managed with the Manage 

User Accounts window shown in the following figure. 

5-18



Add User 

Manage User Accounts Window 

From the Manage User Accounts Window, you can add, delete, or edit user profiles. Each user 

can be assigned a name, optional password, privileges, test program path, and ability to view 

menu-items in the various System windows. 

In the Manage User Accounts Window, you can use the following buttons: 

• Add allows you to add a new user to the System. See Add User below. 

• Delete allows you to delete the selected user from the System. 

• Edit Profile allows you to modify the privileges, password, and menu-control of the 

selected user. 

• Turn On Login allows you to enable or disable the log-in capabilities of the System. If, 

for example, you have users set up in the System, but you choose to temporarily ignore the 

log-in capabilities, you can do so with this button without deleting all the users. 

Add User 

Once you have elected to add a user, or modify a user profile, you are presented with the 

Add/Edit User Window shown in the following figure. 

5-19


Add User 


Add/Edit User Window 

In the Add/Edit User window, you can select from a number of options: 

• User Name is the name used for log-in. 

• Assign / Change User Password can be used to assign, or change an existing secret 

password for each user. It is not required that you enter a password, but most installations 

that limit privileges do. If you assign a password, the user can not log in unless he enters 

the proper password. The password can be up to twelve characters long and can contain 

any normal keyboard characters. The System does not discriminate between upper and 

lower-case characters in the password. 

• Run Privilege specifies whether the user can run test programs. 

• Load Privilege specifies whether the user can load a new test program. 

• Modify Privilege specifies whether the user can edit (change) a test program. 

• Save Privilege allows you to specify whether the user can save a test program. 

• Limited Modify specifies whether the user can change the CheckList settings on page 9- 

10. The CheckList is the only program editing tool when you have logged in with the 

Limited Modify privilege. 

• SPC Privilege specifies whether the user can generate SPC reports. 

5-20



Add User 

• Modify Configuration Privilege specifies whether the user can access the Configure 

System window system. 

• Save Configuration Privilege specifies whether the user can save the station 

configuration data on the system disk. 

• Run Self-Test Configuration Privilege allows you to specify whether the user can 

execute module self-tests. 

• User Administration Configuration Privilege allows you to specify whether the user can 

access the 'Manage User Accounts' windows. 

• Test Program File Path specifies a unique directory for each user's test programs. 

• Pre Defined allows you to select user profiles for typical users. For example you can 

specify typical operator and programmer templates. Once the template is loaded, you can 

modify the capabilities as desired to meet your specific needs. 

• User Control Change Password allows you to specify whether the user can change his 

own password from the log-in window. 

• User Control Modify Menu Control allows you to specify whether the user can change 

his own menu visibility from the log-in window. 

• User Control Rename User allows you to specify whether the user can change his own 

log-in name from the log-in window. 

• Menu Control allows you to specify what menus and menu-items that the user can see. 

The 'Menu Control' button allows you to obtain the Menu Control window shown in the 


Menu Control Window 

5-21


External Hardware 


In the Menu Control window, you can scroll through the various System menus and menuitems. 

Some of the items can be expanded to show lower level menu items. When you have 

selected an item, the status column shows the status of that item. If it is Fixed, the item cannot 

be changed. If it is Visible, the item can be toggled to be Invisible. Once an item is invisible, 

not only can the user not see it, he cannot select it. You can use the four pointing fingers to 

move around in the display, or you can click on the items directly. Items that can be expanded 

are shown as closed folders, end-items are shown as text documents. 

The file menu on the menu control window allows you to export and import your personal user 

account settings. By transferring the exported file to another test system, you can import the 

file there and configure another test system with the same user setup. 

External Hardware 

The External Hardware page is used to specify the configuration of the test system printer, 

beeper, and the USB disconnect warning. The External Hardware window is shown in the 


External Hardware Window 

5-22



System Fixture Configuration 

• Test Window Report Device allows you to select the printer that will be used for test and 

batch reports. You can select from the console (your CRT), serial ports (COM), parallel 

printer ports (LPT), a file on the disk, Windows printer, or a specified viewer. Once you 

have selected the device, the area below solicits additional information about the device. 

For example, in all cases the System needs to know the report width (40 or 80 columns). 

If you are using a COM port, the system needs to know the communication setup 

parameters. If you are using a CheckSum Model T-120-2S serial printer, the correct 

settings are 40-columns, 1200 baud, 8 bits, polling, no parity, and 1 stop bit. If you are 

reporting to a file, the System needs to know the file name, and an optional path. When 

reporting to a file, the System appends the data each time a new report is generated. 

• Printer Setup is used to configure the printer output with a form feed (new page) if 

needed and/or extra blank lines at the end of the report. This can be used to provide extra 

space to separate the report printouts for ease of use. 

• Beeper on or off allows you to enable the System beeper. If enabled, the beeper alerts the 

operator in most cases when a key has been pressed, a key press is necessary, or when a 

failure or error occurs. The software Beep command provides two tones. One is for 

routine notification to the operator, and another when an error condition occurs. 

• USB Disconnect Warning entry is used to configure the time before the USB 

disconnection is detected and a warning is displayed. Set to "Only once" (left-most 

setting) when running the software on a PC that is not connected to the CheckSum chassis. 



attachment. 

You can use the Save button on this window to save the station configuration data for use the 

next time the system software is started. 


The Fixture Press page is used to specify what type of System fixturing is used. The Fixture 

Press window is shown in the following figure. The selected entry is used for fixture wiring 

reports so that interface connections are appropriate for your installation. The 'Custom' entry 

assumes that you have a series of standard 50-pin connectors on your fixture interface. 

5-23




Fixture Press Selection Window 



attachment. 

You can use the Save button on this window to save the station configuration data for use the 

next time the system software is started. 

5-24

Chapter 6 

MultiWriter Fixture Design 

Guidelines 

MultiWriter Fixture Design Topics 

The fixture design needs to address the following elements: 

1. Confirm that the MultiWriter library supports all of the required programmable devices. 

2. "Design for Part Programming" on page 6-31 review of the assembly is performed. 

3. If the assembly is a multi-up panel on page 10-33, the PCB reference numbers are 

specified. 

4. The physical layout minimizes the length of the signal wiring from each buffer module to 

each device. 

5. The buffer module twisted-pair signal wiring design layout minimizes noise pickup, see 

Buffer Modules on page 6-6 and Fixture Layout on page 6-3. 

6. The buffer module power supply wiring is included. 

7. The MultiWriter Fixture I/O module on page 6-13 wiring is included. At least one MW 

FIX I/O module is required (one MW FIX I/O module connects to each MultiWriter 

controller). 

8. The fixture, internal USB device is connected to Block K as required, see Internal USB 

and program storage on page 6-21. 

9. The DUT power supply (PS-UUT) resource meets the assembly voltage/current 

requirements and the power supply wiring includes the remote sense and output enable 

connections, see Power Supply Considerations on page 6-5. 

10. The Fixture Ready switch, if used is added to the fixture design, see Fixture Ready on page 

6-17. 

11. The fixture mechanical design insures alignment and proper access to the required ISP 

nodes/nets, see Fixture Mechanical Design on page 6-24.

MultiWriter Fixture Design Guidelines 

Programming Multiple Devices 


12. The test program MISP on page 10-7 is setup with the proper device types and for the 

correct number of devices. 

13. Before making changes to an existing device programming setup, review the section 

Considerations Before Making ISP Changes on page 6-34. 

Programming Multiple Devices 

The MultiWriter pps system can simultaneously program identical devices using the same 

device programming algorithm or different devices using different device programming 

algorithms, see the MISP on page 10-7 step. 

The following are some extreme, multiple device examples. Assemblies with fewer devices 

are easily supported, just reduce any of the numbers in these examples. 

Standard System with 4 programming receiver blocks installed (A, B, C & D plus K for 

power) 

Any mix of groups up to 24 devices, up to 96 (24 x 4) devices total simultaneously: 

• With 1 programmable device per PCB, then the maximum number of PCBs is 96 

• With 2 programmable devices per PCB, then the maximum number of PCBs is 48 

• With 3 or 4 programmable devices per PCB, then the maximum number of PCBs is 24 

Examples: 

96 PCBs with 96 identical devices 

48 PCBs with 48 "U1" devices and 48 "U2" devices 

24 PCBs with 24 "U1" devices, 24 "U2" devices, and 24 "U3" devices 

24 PCBs with 24 "U1" devices, 24 "U2" devices, 24 "U3" devices, and 24 "U4" devices 

24 PCBs with 4 different devices on each PCB 

Fully Loaded with 8 programming receiver blocks installed (A, B, C, D, E, F, G, & H plus 

K for power) 




• With 3 or 4 programmable devices per PCB, then the maximum number of PCBs is 48 

• With 5, up to 8 programmable devices per PCB, then the maximum number of PCBs is 24 

Examples: 





24 PCBs with 5, up to 8 different devices on each PCB 

6-2



Fixture Layout 

Maximum system 







• With 6, 7, or 8 programmable devices per PCB, then the maximum number of PCBs is 48 

• With 9, up to 16 programmable devices per PCB, then the maximum number of PCBs is 

24 

Examples: 





72 PCBs with 72 "U1" devices, 72 "U2" devices, 72 "U3" devices, 72 "U4" devices, and 72 

"U5" devices 

48 PCBs with 6, 7, or 8 different devices on each PCB 

24 PCBs with 9, up to 16 different devices on each PCB 

Contact CheckSum on page 1-8 for any questions regarding the maximum number of devices 

or combination of boards and devices that can be programmed simultaneously with any system 

setup. 


For a single assembly (PCB), there is no need for panelizing since each device is referenced 

uniquely. That is, there is only one “U25” that is programmed and could possibly fail that 

needs to be identified. 

The layout for the location of the buffer modules needs to be done after the probe receptacle 

placement is completed. The buffer modules have holes in the PCB that are used to mount 

connectors to attach these modules to the bottom side of the fixture plates. 

The wires from the 170-pin block to the buffer modules can be done with preconfigured cables 

or point-to-point wiring. All of the wire pairs (NAME+ / NAME-) need to be twisted-pairs. 

These signals should be considered transmission lines with low-voltage differential signaling 

(LVDS). 

The wire pairs from the buffer module to the spring-probe receptacles need to be twisted-pairs. 

By mounting the buffer modules as physically close to the device to be programmed as 

possible, the highest signal integrity can be best maintained. 

Panelization 

See the topic, Panelized Assemblies on page 10-33, in Entering Program Steps on page 10-1. 

6-3




To program devices on a panel with multiple boards, the program is “panelized” to match the 

panel. The panelized program identifies the test points in the section of the panel including a 

PCB number identifier and the wiring also needs to match the assembly in the same manner. 

The number of the PCB is specified in the panelization setup. Three typical, example panel 

maps are shown in the following figures (top view): 

It is important to identify each individual PCB (number) on the panel before wiring. The test 

engineer responsible for the test program must supply this information. We recommend that 

you do not proceed with any fixture wiring without this PCB information. 

6-4



Power Supply Considerations 

Although the devices are programmed simultaneously, the PCB number will be very useful to 

identify any device(s) that fail verification. 

To make it easy to locate each PCB: 

1. Mark the PCB number on the G-10 plate in the probe area (bottom/top side of the test 

fixture) 

2. Place a label with the PCB number on each buffer module 

These simple steps will make the job easier to complete and maintainable in the future for 

changes or service. 

The link between the UUT PCB number and the buffer module Port number can be modified 

in the MISP setup on page 10-7. 

Power Supply Considerations 

Power for the DUT 

Power supplies for each assembly are controlled by relays on each buffer module. There are 

numerous power supply connections available on Power Block K on page 12-31. 

The power supply wire connection from the 170-pin block to each buffer module needs to use 

appropriate gauge wire for the current and voltage required by the DUT assembly. 

Inside the fixture, be sure to connect the remote Sense to the power supply pins (+S to +V and 

–S to –V) for each power supply that is used. The connections can be done at the 170-pin 

block or at the DUT located near the center of the fixture. Use of remote sense will insure the 

programmed supply voltages are accurately supplied to the DUTs. 

Power Supply Controls 

The DUT power supplies are setup from CheckSum with the ENA_IN (enable inputs) configured to require a 

positive voltage input to enable the power supply output. 

The power supply output enable is controlled by the system control board installed in the test 

system and controlled by the system software. 

When the system switches on the +5Vdc SW power, the DUT power supplies are Enabled. 

The output voltage to the fixture is controlled by the system software setting of the DUT power 

supplies. 

If the PS-UUT setup fails, the system will alert the operator with a pop-up message: 

Setting below Under Voltage Limit attempted 

Attempt to set DCV level below a voltage specified by a previous DCV MIN step for that 

supply. 

Setting above Over Voltage Limit attempted 

Attempt to set DCV level above a voltage specified by a previous DCV MAX step for that 

supply. 

COM1 unavailable for supply control 

6-5


Buffer Modules 


COM1 port already in use. If in use by RS232 step execution, we recommend execution of 

RS232 on page 14-40 Range 12 to free up the port. 

Supply response garbled, check COM settings 

PS-UUT-L1 communication response strings are not recognized. 

Supply shut down fault 

Seen when PS-UUT-L1 returns an E07 status. 

Supply setting out of range 

Seen when PS-UUT-L1 returns an C05 status. 

Supply error = "Error String" 

Seen when PS-UUT-L1 returns any E** or C** status other than the two preceding 

messages. 

Setting below Under Current Limit attempted 

Attempt to set DCI level below a current specified by a previous DCI MIN step for that 

supply. 

Setting above Over Current Limit attempted 

Attempt to set DCI level above a current specified by a previous DCI MAX step for that 

supply. 


The MultiWriter control module has sets of signals to control the ISP buffer modules. The 

layout plan needs to accommodate the wiring to the pin blocks and the wiring to the probe 

receptacles. The buffer modules are normally mounted perpendicular to the fixture plate. This 

minimizes the space needed for the buffer modules since one module is needed for each device 

to be programmed. 

The control module provides signals to the fixture receiver block using twisted-pair cables for 

the clock (C, CLK, Serial Clock, + / –) to the buffer modules, mode (M, MODE, + / –) to the 

buffer modules, DUT serial data input (I, MOSI, Serial Input, + / –) to the buffer modules, 

extra (Extra, E + / –) to the buffer modules, and the DUT serial data outputs (MISO) from the 

buffer modules. The four twisted-pair signals C, M, I, and E are wired in parallel (daisy-chain 

style) to each buffer module. These signals should be considered transmission lines with lowvoltage 

differential signaling (LVDS). 

MOSI stands for "Master Out Slave In". The Master is the MultiWriter controller and the 

Slave is the DUT. The serial data is transferred from the MultiWriter controller through the 

buffer modules to the DUT. MISO stands for "Master In Slave Out". The serial data output is 

transferred from the DUT through the buffer modules to the MultiWriter controller. 

These buffer module connectors are designed to accept headers with wire-wrap pins. This 

allows the quick replacement of the any module that is not functioning properly. 

ISP Buffer module (Slave) 

This module is used to buffer the ISP signals (for programming) and switch power on/off to 

the DUT(s). A single relay control signal (Relay Port) switches the relays. 

6-6




The module has several sets of pins. One ISP buffer module is used for each two 

programmable parts. The module is mounted to the bottom fixture plate as close as possible to 

the test points for the programmable part. 

The buffer module is powered by +5V (logic) and +12V (relay) provided from the system 

control board. The buffer modules are powered on during programming only. Power to the 

DUT is controlled by the system and only applied if the DUT is not skipped. 

The signal Relay Port N connects from the fixture interface wiring blocks to each buffer 

module (where N is the port number from 1 to 24, 25 to 48, etc). For example, connect wiring 

block A signal Relay Port 1 to buffer module #1 Relay Port 1. Then using twisted-pair wires 

connect wiring block A signals Port1 +/– to buffer module #1 Port +/–. 

The twisted-pair signals C (Serial Clock) +/–, M (MODE) +/–, I (Serial Data Input to DUT) 

+/–, and E+/– are wired in parallel (daisy-chain style) from the Fixture Wiring Block to each 

buffer module in the set. The order is not important. The last module must be the MultiWriter 

Fixture I/O module on page 6-13 since this assembly contains the termination impedance for 

the differential signals. 

Daisy-chain (sequential) wiring connects the same signal to multiple assemblies in sequence; 

e.g., C+/- from the system control module signals on the fixture interface are wired to buffer 

#1 C+/– which is wired to buffer #2 C+/– and then wired to buffer #3 C+/–, etc. Some of the 

buffer module connectors (e.g., LA1 and RA1) are bussed together on the buffer module. This 

allows the daisy-chained signals to be routed “to and from” the buffer module easily. The 

buffer module is available as a dual module (X2) or as an interconnected set of 4 modules 

(X4). The daisy-chain signals are connected to all four modules with PWB traces. 

Cable assemblies with twisted-pair wires are used with the buffer modules. Generally, a massterminated, 

push-on connector is used on one end and the other end of the wire is wirewrapped 

to the connector pin. The use of the push-on connector allows easy replacement of a 

failed assembly. 

These setups allow the buffer module to be installed physically close to the IC which will 

improve the signal characteristics and reduce ringing, overshoot, undershoot, and noise pickup. 

In general, minimize the length of the twisted pair wiring from the buffer module to the springprobe 

receptacle. The twisted-pair wires should be separated from other twisted-pair wires and 

from all other wiring. 

Insure the IC device ground test point is located as physically close to the IC as possible. 

Signal noise problems can occur if the buffer modules are located too far from the IC, the 

twisted-pair wiring is not as short as possible, or the test points are not located as physically 

close to the IC as possible. 

Buffer Module Details 

The cable connections to LA1 and RA1 are interchangeable. These connectors make daisychaining 

the signals simple to do. Use the connector that is closest to the next and previous 

modules. 

6-7




The first 8 A1 pins connect to the first 8 pins on the fixture wiring block. The +5Vdc SW and 

+12Vdc SW also connect to the fixture wiring block pins. The VPP & VIO power pins are 

device dependent. The VPP and VIO voltages can be programmed on the MultiWriter Fixture 

I/O module on page 6-16. 

Buffer Module X2 (3800-105 or 3800-107) 

The fixture block connects to A1 on the closest buffer, normally close to the Block A position 

to allow the fixture to open without stretching any wires, then daisy-chain these signals to the 

remaining buffers and finally end at the A1 connector on MultiWriter Fixture I/O module. 

The A9 and A10 connectors of the MultiWriter Fixture I/O module connect to the fixture 

wiring block, then you wire-wrap VPP and VIO to the desired voltage on the MultiWriter 

6-8




Fixture I/O module. Those voltages are then distributed to the buffers through the daisychained 

A1 connectors. 

The signals on the LA1 & RA1 connectors are connected in parallel and therefore identical: 

A1-1 C+ 

A1-2 C– 

A1-3 M+ 

A1-4 M– 

A1-5 I+ 

A1-6 I– 

A1-7 E+ 

A1-8 E– 

A1-9 +5Vdc SW 

A1-10 +12Vdc SW 

A1-11 VPP 

A1-12 VIO 

A1-13 PWR1 

A1-14 GND 

A1-15 PWR2 

A1-16 GND 

LA1 and RA1 Connections 

The buffer module uses the differential control signals to generate the buffered signals to the 

UUT/DUT: 

C+ and C– generate the buffered signal CLK to UUT1 and UUT2 

M+ and M– generate the buffered signal MODE to UUT1 and UUT2 

I+ and I– generate the buffered signal MOSI to UUT1 and UUT2 

E+ and E– generate the buffered signal EXTRA to UUT1 and UUT2 

A SPST relay is used for each of the 8 UUT & MDA signals. This isolates the signals and 

power until programming is initiated. Any assemblies that are Skipped, are not powered-on 

and no programming signals or power are applied to the DUT: 

Signal/Power xxx 

Signal/Power xxx_UUT 

Signal/Power xxx_MDA 

Relay NO (Normally Open) 

Relay COM to connectors UUT1 and UUT2 

Relay NC (Normally Closed) to connectors MDA1 and MDA2 

SPST Relay UUT and MDA Connection Example 

6-9




UUT1-1 PWR1 

UUT1-2 N/C KEY 

UUT1-3 CLK 

UUT1-4 GND 

UUT1-5 MODE 

UUT1-6 GND 

UUT1-7 MOSI 

UUT1-8 GND 

UUT1-9 EXTRA 

UUT1-10 GND 

UUT1-11 MISO 

UUT1-12 GND 

UUT1-13 PWR2 

UUT1 Connections 

UUT2-1 PWR1 


UUT2-3 CLK 

UUT2-4 GND 

UUT2-5 MODE 

UUT2-6 GND 

UUT2-7 MOSI 

UUT2-8 GND 

UUT2-9 EXTRA 

UUT2-10 GND 

UUT2-11 MISO 

UUT2-12 GND 

UUT2-13 PWR2 

UUT2 Connections 

The UUT side is wired to the fixture spring-probe receptacles to make connection to the DUT. 

The following is a sample wiring setup for a NEC V850 device - uPD70F3350: 

Buffer Pin (UUT1) DUT Node Name 

UUT1-1 PWR1 

5V 


UUT1-3 CLK 

SCK 

UUT1-4 GND 

GND 

UUT1-5 MODE 

/RESET 

UUT1-6 GND 

GND 

UUT1-7 MOSI 

SI 

UUT1-8 GND 

GND 

UUT1-9 EXTRA FLMD0 

UUT1-10 GND 

GND 

UUT1-11 MISO 

SO 

UUT1-12 GND 

GND 

UUT1-13 PWR2 3.3V 

6-10




Example wiring setup for a NEC V850 device 

A 10K ohm resistor is provided between each of the signals on the UUT and MDA connectors 

pins: 

UUT to MDA Connections 

MDA1-1 PWR1_MDA1 

MDA1-2 N/C KEY 

MDA1-3 GND_MDA1 

MDA1-4 SCK_MDA1 

MDA1-5 MODE_MDA1 

MDA1-6 SDI_MDA1 

MDA1-7 EXTRA_MDA1 

MDA1-8 SDO_MDA1 

MDA1-9 N/C 


MDA1 Connections 

MDA2-1 

MDA2-2 

MDA2-3 

MDA2-4 

PWR1_MDA2 

N/C KEY 

GND_MDA2 

SCK_MDA2 

6-11




MDA2-5 MODE_MDA2 

MDA2-6 SDI_MDA2 

MDA2-7 EXTRA_MDA2 

MDA2-8 SDO_MDA2 

MDA2-9 N/C 


MDA2 Connections 

A power discharge resistor can be connected from the PWR_MDA to GND_MDA points to 

discharge the voltages on the UUTs. 

The J1 pins can be used for connection to the system power supplies: 

J1-1 PWR1 

J1-2 GND 

J1-3 PWR2 

The PS-UUT power can be wired to J2 on the MultiWriter Fixture I/O module, to J1 on the 

middle buffer, or if the UUTs draw more than 500mA, to multiple J1 connectors on the buffer 

modules. Many UUTs draw much less current and the MultiWriter Fixture I/O module 

provides a standard place to wire it. 

The A2 Relay Port and Port #+/– connect to the fixture block pins: 

A2-1 N/C 

A2-2 Relay Port N 

A2-3 Port N+ 

A2-4 Port N– 

A2-5 N/C 

A2-6 Relay Port M 

A2-7 Port M+ 

A2-8 Port M– 

The buffer module cable sets can be used: 

Part Number Description Connects to buffer module 

5000-119 MultiWriter cable 2 x 7 J4 / J5 

5000-120 MultiWriter cable 2 x 2 J1 



5000-247 MultiWriter cable 1 x 13 UUT1 & UUT2 

5000-248 MultiWriter cable 1 x 10 MDA1 & MDA2 

5000-263 MultiWriter cable 1 x 16 LA1 / RA1 

5000-264 MultiWriter cable 1 x 8 A2 

6-12



MultiWriter Fixture I/O (MW FIX I/O) 

These cable sets provide twisted-pair wires for the necessary signals. The cable length is 

approximately 24 inches (60 cm). The cables are terminated with headers at one end only. 

Cut the wires to the minimum length needed. 

Twisted Pair Termination 

The last buffer module in each set of the daisy-chain will require termination resistors (100Ω), 

one on each bus-plus signal to the corresponding bus-minus signal, C (CLK)+/–, M (MODE) 

+/–, I (MOSI ) +/–, and E+/– (EXTRA). The MW FIX I/O module below provides the 

termination resistors. 


Each fixture must contain at least one MW FIX I/O module. For each unique device type 

programmed with a fixture, at least one MW FIX I/O module is required. For example, if two 

different device types are programmed on an assembly, then two MW FIX I/O modules are 

needed. One MW FIX I/O module is needed for each unique device. 

The MW FIX I/O module can be used to run a fixture wiring check on the fixed voltage 

supplies provided at the fixture interface. The single-point probe, fixture ready and in-fixture 

solenoid control features are only used on the first MW FIX I/O module which connects to the 

first MultiWriter controller in the system on Block A of the Fixture Wiring Interface. The 

MW FIX I/O module provides connector pins for USB hub power (A-154 : HUB PS+ and A- 

155 : HUB PS-). The MW FIX I/O module must be connected to the last buffer module in the 

chain of buffer modules controlled by a MultiWriter controller to provide the four I2C 

differential signal pair termination. 

The 3800-102 MultiWriter Fixture I/O module provides a variety of controls and outputs: 

• Fixture Self-test 

• Single-Point Probe input 

• Fixture Ready signal detection 

• Fixture Present detection 

• 8 bits of digital I/O 

• 24 relay control bits 

• VIO and VPP voltages 

• Termination (100Ω) for the four I2C differential signal pairs 

6-13




The Fixture Wiring Block pins A-1 to A-8 on page 12-3 cable to first buffer module. Buffer 

modules are daisy chained wired from one module to the next, the last buffer module cables to 

the 3800-102 board A1 connector. The buffer modules will also have a connector that cables 

to the Fixture Wiring Block A pins A-18 to A-33, A-35 to A-67, etc for the individual devices 

to be programmed (Port 1 to 24). Depending on the number of devices and device types, the 

buffer module connections may connect to the Fixture Wiring Blocks B to H. 

A1-16 GND 

A1-15 PWR2 

A1-14 GND 

A1-13 PWR1 

A1-12 VIO 

A1-11 VPP 

A1-10 +12Vdc 

A1-9 +5Vdc 

A1-8 E- 

A1-7 E+ 

A1-6 I- 

A1-5 I+ 

A1-4 M- 

A1-3 M+ 

A1-2 C- 

A1-1 C+ 

6-14




Connector A9 cables to the Fixture Wiring Block pins A-152 to A-137: 

A9-16 GND (Fixture Present/) 

A9-15 TXD (same as MW RXD) 

A9-14 GND 

A9-13 RXD (same as MW TXD) 

A9-12 GND 

A9-11 I2C Data 

A9-10 GND 

A9-9 I2C Clock 

A9-8 N/C 

A9-7 Probe Input 

A9-6 Fixture 2 Control/ 

A9-5 GND 

A9-4 Fixture 2 Ready/ 

A9-3 Fixture 1 Control/ 

A9-2 GND 

A9-1 Fixture 1 Ready/ 

Note: If Fixture Present/ (Fixture Receiver pin A-152) is not connected to the 

MW FIX IO module or to a GND pin, the PS-UUT switched power outputs 

(+5Vdc SW, +12Vdc SW, and +24Vdc SW) will not be enabled and switched 

power will not be available to the fixture. 

Connector A10 cables to the Fixture Wiring Block pins A-154 to A-163, note that the security 

HASP USB drive connects to the Fixture Wiring Block on pins K-165 to K-169: 

A10-10 GND 

A10-9 N/C 

A10-8 +5Vdc SW# (# = 1 – 8, MW controller unit) 

A10-7 N/C 

A10-6 +12Vdc SW# 

A10-5 N/C 

A10-4 +24Vdc SW# 

A10-3 N/C 

A10-2 HUB PS- 

A10-1 HUB PS+ 

Note: At start-up, if the security USB device is disconnected, not installed, or defective then 

the message "HASP dongle missing or driver not installed" will be shown. This is normal 

when running the software without any hardware attached to the PC. The HASP USB drive is 

normally installed inside the test fixture. 

Connector J1 cables to any optional modules controllable with RELAY test type: 

J1-4 GND 

J1-3 I2C Clock 

J1-2 I2C Data 

J1-1 +12Vdc 

6-15




Connector J2 connects to Block K. Connect the power supply sense pins (+S / -S) to the 

output at Block K. If the DUTs draw in excess of 500mA current, add redundant wires from 

Block K to each buffer module: 

J2-3 PWR2 

J2-2 GND 

J2-1 PWR1 

Connector J3 is used for optional in-fixture USB HUB and lid switch(es) for Fixture Ready 

detection: 

J3-1 HUB PS+ 

J3-2 HUB PS- 

J3-3 Fixture 1 Ready/ 

J3-4 GND 

J3-5 Fixture 2 Ready/ 

Connector J4 is a "pin programming" header used to set the VIO and VPP voltages: 

J4-2 PROG5 J4-4 VIO J4-6 VPP J4-8 PROG24 

J4-1 +3.3Vdc J4-3 +5Vdc J4-5 +12Vdc J4-7 N/C 

Two resistors, R18 and R19, can be added to the PCB to set the values of PROG5 and 

PROG24. 

Install a 1K resistor for R18, to set the PROG5 voltage to be approximately 2.2Vdc. The 

PROG5 voltage on J4-2 can be connected to J4-4 to set the VIO voltage. 

Install a 15.8K resistor for R19, to set the PROG24 voltage to be approximately 9.1Vdc. The 

PROG24 voltage on J4-8 can be connected to J4-6 to set the VPP voltage. For example, the 

9.1Vdc for VPP is used for the HC908 family. 

The general formula for each voltage is: 

J4-2 Prog5 = 4.4/(1 + R18/1000) Vdc 

J4-8 Prog24 = 23.4/(1 + R19/10000) Vdc 

Alternatively, connect VIO and/or VPP to J4-1, J4-3, or J4-5 for +3.3Vdc, +5Vdc or +12Vdc. 

Connector J6 provides 16 bits for relay drivers, e.g. for board markers. Relay drivers are 

controlled with RELAY on page 14-47 test type: 

RLY1 J6-1 J6-2 RLY9 

RLY2 J6-3 J6-4 RLY10 

RLY3 J6-5 J6-6 RLY11 

RLY4 J6-7 J6-8 RLY12 

RLY5 J6-9 J6-10 RLY13 

6-16



Fixture Ready 

RLY6 J6-11 J6-12 RLY14 

RLY7 J6-13 J6-14 RLY15 

RLY8 J6-15 J6-16 RLY16 

Connector J5 can be used for +12V or +24V to board markers: 

J5-1 Fixture 2 Control/ J5-4 +5Vdc J5-6 +24Vdc 

J5-2 Fixture 1 Control/ J5-3 GND J5-5 +12Vdc 

Connector J7 provides 8 bits for relay drivers plus 8 bits of digital I/O. Relay drivers are 

controlled with RELAY on page 14-47 test type and the digital I/O is controlled with the 

DIGA, DIGO and DIGI on page 14-6 test types: 

RLY1 

7 

RLY1 

8 

RLY1 

9 

RLY2 

0 

RLY2 

1 

RLY2 

2 

RLY2 

3 

RLY2 

4 

J7-1 J7-2 IO1 

J7-3 J7-4 IO2 

J7-5 J7-6 IO3 

J7-7 J7-8 IO4 

J7-9 J7-10 IO5 

J7-11 J7-12 IO6 

J7-13 J7-14 IO7 

J7-15 J7-16 IO8 

Fixture Ready 

The system includes two (2) fixture ready signals on the fixture interface “A” wiring block. 

These signals can be used to start the programming. The Lid 1 (Left) signal creates Fixture 1 

Ready/ (A-137) signal and is normally used for a single fixture. The Lid 2 (Right) signal 

creates Fixture 2 Ready/ (A-140) and is normally used for a dual-well setup. These signals 

connect to the MultiWriter Fixture I/O board and can be used to start device programming. 

6-17


Fixture Ready 


One example of a fixture-down switch assembly uses an assembly block, spring-mounted 

center-tapered rod, and a SPDT roller switch (Honeywell Sensing & Control PN V7-2S17D8- 

201). The fixture-down switch assembly is mounted on the bottom side of the G-10 fixture 

probe plate, as are the buffer modules. 

Typical Fixture-Down Switch Assembly Mounting 

A hole in the fixture probe plate allows a rod mounted on the lid to push the fixture-down 

center-tapered rod when the lid is closed. The tapered section of the movable rod closes the 

fixture-down switch contact (COM to NO) to indicate the fixture is ready. 

6-18



Fixture Ready 

Example Fixture-Down Switch Assembly 

A DUT detect switch can be added to the top of the fixture plate to detect the DUT board is 

installed. By wiring the DUT detect and fixture-down switch contacts in series, the fixture 

ready signal indicates the DUT board is installed and the fixture lid is down. 

6-19


Fixture Ready 


Example DUT Detect Switch 

Switch closure indicates the operator has closed the fixture top lid and programming can begin. 

The currently loaded program sequence is started. 

Left 

Right 

J3-4 

GND 

Fixture 1 Ready/ J3-3 Lid 1 

COM 

NO (Normally Open) 

COM 

NO (Normally Open) 

Fixture 2 Ready/ J3-5 

Lid 2 

3800-102 MW FIX I/O 

A9 

Connects to the Fixture Wiring Block 

Pins A-152 to A-137 

Fixture Lid Switch Wiring to MW FIX I/O : MultiWriter Fixture I/O on page 6-13 

6-20



Internal USB and program storage 

Alternatively, the operator can press the F1 function key on the keyboard, press the system 

START button, or click the Program button in the test window to start the program sequence. 

The program start can be setup in the Editor on page 9-13, Progam CheckList on page 9-10, 

and Test on page 7-14 windows. 


A USB device ("HASP USB drive" or "HASP protection key") is installed inside each fixture. 

The flash drive stores several files that are necessary to program the parts. The device is wired 

to Block K on page 12-31 on pins K-165 to K-169. 

Typical HASP USB Drive 

At start-up, if the security HASP USB drive ("dongle") is disconnected, not installed, defective 

or the Programmer Power on page 4-4 is not turned-on then the message "HASP dongle 

missing or driver not installed" will be shown. This is normal when running the software 

without any hardware attached to the PC. The HASP USB drive is normally installed inside 

the test fixture. 

The following files are stored in this flash drive: 

• Customer data image file(s) 

• Device programming algorithm 

• Specific program sequence for the DUT and program associated files 

The HASP USB drive appears in the test system directory as "Fixture USBDrive": 

6-21




The HASP files are stored in the fixture USB drive to insure that the fixture can be used by 

another CheckSum MultiWriter pps system without encountering compatibility problems. By 

storing the files and software with the fixture, this item becomes a standalone setup with 

respect to programming the devices. When the fixture is transferred anywhere in the world, it 

arrives ready to program devices just as it did the last time it was used. 

HASP Remote Update System (RUS) 

To send information to CheckSum about the fixture HASP key or update the HASP key, run 

the CSRUS.EXE application located in C:\CheckSum or the install directory to generate a 

Customer-to-Vendor (c2v) file or to apply a Vendor-to-Customer (v2c) file, where CheckSum 

is the "Vendor". 

If you are using a pay-per-use model, you will need to run this application and send the c2v 

file to CheckSum so we can check the usage. If you need a license update, we are going to 

send a v2c file to you. 

First, please connect the HASP key to your computer and run the CSRUS.EXE application, 

you will see the "Welcome to CheckSum . . . ." message. The HASP key is normally installed 

in a test fixture. Be sure to turn-on the Programmer Power switch to power-on the HASP key. 

You can click the "Collect Key Status Information" and generate a c2v file about your HASP 

key, then you can send this file to CheckSum so that we can review the "protected internal 

information" from the HASP protection key. It will not collect any user information from the 

HASP protection key Flash memory. 

6-22




The RUS window consists of the following tabs: 

• Collect Key Status Information: The parameters in this tab are used to collect information 

on the current status of the licenses in the HASP protection key. The end user specifies a 

name and location for the generated c2v file. If more than one HASP protection key is 

installed, the user selects the required key. No private customer data is included in the c2v 

file. 

• Apply License Update: The parameters in this tab are used to apply a v2c file and update 

licenses in a HASP protection key. 

Using HASP Remote Update System (RUS) 

You must connect the key before performing collecting license data or applying an update. The 

HASP key is normally installed in a test fixture. Be sure to turn-on the Programmer Power 

switch to power-on the HASP key. 

Collecting HASP Protection Key License Data 

You can use HASP RUS to produce a Customer-to-Vendor (c2v) file containing information 

on the current status of the licenses in your HASP protection keys. You can then send this file 

in order to receive a license update. 

To retrieve the current license information from a HASP protection key: 

1. Launch the HASP RUS (csrus.exe). 

2. Click the Collect Key Status Information tab. 

3. Click Collect Information. The Save key status as window is displayed. 

4. Specify the directory where you want to store the c2v file. Enter a file name and click Save. 

5. If more than one HASP protection key is located, a list of the keys is displayed. Select the 

required key, or disconnect the keys that are not required, and click Refresh. 

6. The c2v file for the HASP protection key is generated and saved in the required location. 

The file can now be sent for processing to produce an update. 

Applying an Update 

You can also use HASP RUS to apply an update to the licenses stored in your HASP 

protection keys. To update the licenses in HASP protection keys: 

1. Launch RUS (csrus.exe) or double-click the Vendor-to-Customer (v2c) file that you have 

received containing the update data. 

Note: 

If you have received an update as an executable, double-click the file and it 

will automatically launch the RUS. 

2. Click the Apply License Update tab. (This might be the only tab displayed.) 

6-23


Fixture Mechanical Design 


3. If the Update file field is empty, browse to the directory where the update file (.v2c file) is 

located and select the file. 

4. Click Apply Update to apply the new license data to be used with the HASP key. 


DUT Fixture Alignment 

Alignment is accomplished by positioning the DUT accurately with respect to the test fixture 

spring-probes. The XY position of the test fixture spring-probes is determined from the same 

CAD information that is used to create the printed circuit/wire board (PCB / PWB). In 

addition to the spring-probe CAD data, the PCB normally has holes added to position the PCB 

during the manufacturing process for inserting or placing components for example. Ideally, 

the PWB holes should not be plated since the plating thickness can vary and cause the hole 

dimension to vary in size. Also, the plating material causes fiction with the guide pins. 

By referencing the position of the holes, called tooling holes, in the PCB, the DUT can be 

located precisely with respect to the spring-probes which are mounted in the test fixture. 

The test fixture includes pins, called guide pins, typically made of stainless steel for long wear. 

The operator aligns the DUT holes over the guide pins and slides the DUT down on these 

guide pins when they place the assembly on the test fixture. 

If the DUT does not have any holes due to a lack of good design for test criteria or some 

design restrictions, then the outside edge of the PWB is often used to align the assembly to the 

spring-probes. Since the size of the assembly cannot be as well controlled as the PWB holes 

and copper, edge alignment is not as precise and so this alignment mechanism is not the 

preferred method. 

Installing Guide Pins 

Guide pins are used to accurately position the DUT with respect to the spring probes. The 

guide pins go through tooling holes in the DUT. You should attempt to have at least two guide 

pins, positioned as far apart as possible, for every DUT. 

In most cases it is easiest for the operator to install and remove DUTs with only two guide 

pins. If the DUT is somewhat symmetrical and could be installed incorrectly, it is a good 

practice to install an additional, smaller guide pin in an unused non-symmetrical hole in the 

DUT. This can prevent the DUT from being installed incorrectly. 

Note 

If your DUT does not have tooling holes, you can use edge-guide brackets 

or guide pins. However, this is not ideal since alignment can be unreliable. 

The position of the guide pins is used as a reference for all of the spring probes, so they must 

be accurately placed. The guide pins should be approximately 0.003 inches (0.076 mm) 

smaller than the tooling holes in the UUT to allow easy placement of the UUT without 

binding, but still accurately positioning the UUT. The position and size of the tooling holes is 

6-24




normally called out in the drill and trim drawing used for PCB fabrication or in the drill file for 

the UUT. 

There are four standard diameters of guide pins available from CheckSum. These can be 

reduced in size by a lathe if necessary. Since they are made of hardened stainless steel, use of a 

carbide cutting tool is recommended when turning them down to a different size. CheckSum 

also can provide a variety of non-standard sizes, contact the factory for size availability. 

The guide pins should not be installed until after the holes for the spring probes have been 

located and drilled. Otherwise they get in the way of the drilling process. When using 

CheckSum Model FIX-GPIN-nnn guide pins, you can use a #18 drill in the probe plate for 

each guide pin, then press the guide pin into place. Alternatively, you can use an 11/64 inch 

(4.366 mm) drill, slip the guide pin into place, then fasten it from the bottom with a #2-56 

screw. 

Installing Spring Probes 

A standard practice is to use one spring probe for each electrical network to be used, even 

though that network might go to multiple components and pins. 

The maximum current that can be provided by the test systems is in the low mA region, so 

large wires (greater than # 22-# 28) are not required except for some power supply wiring. 

Note 

If you are wiring power to the DUT for power-on tests or other special 

requirements, you may need to increase the wire sizes beyond typical wirewrap 

sizes to accommodate current draws in excess of 100 mA. 

The first step is to assign test point numbers. If you are using CAD conversion to generate 

your test program, you can use the points assigned in this process. For manual test point 

assignment, it is easiest to first mark a schematic with sequential numbers showing the test 

points. This can be used to wire the fixture, then serves as a valuable aid to the programmers 

and technicians troubleshooting and repairing DUTs. Using this technique also allows the test 

program to be entered in parallel with fixture construction. 

Once you have electrically selected the probe points, you can determine where to physically 

drill them. It is a good idea to drill all the PCB pad positions, but only install probes where 

necessary. This allows the flexibility to easily add or move probes as necessary to 

accommodate design changes or to correct for errors when first choosing probe placement. 

If you have a drill data for your boards, but not an NC drill, it may be practical to have a 

facility with an NC drill (such as a PCB fabrication shop or CheckSum) do the drilling. If not, 

you can do the drilling yourself, either by drilling through an unloaded PCB or by using 1:1 

film-work of the PCB as a guide. 

For standard spring probe receptacles, such as those available from CheckSum, a #50 or 1.75 mm drill is 

used. This yields a 0.068 to 0.070 inch (1.727 mm to 1.778 mm) hole. 

If you have any components on the bottom of the board, you can use a milling machine to 

create openings in the probe plate to provide clearance. 

The FR-4 (G-10) material, as used in the probe plate, is quite abrasive. Use of carbide drill 

bits and milling tools helps make the bits last longer. 

6-25




Once the probe board is drilled, you can install the spring probe receptacles (such as the 

CheckSum Model FIX-RECEP-100) from the top of the probe plate. To install them, use a 

small hammer in conjunction with a special tool (e.g., CheckSum Model FIX-TOOL-150) to 

tap the receptacles into place. 

The receptacles should be installed to the depth for proper compression when the DUT is 

pressed down. Typically, the proper compression length is two-thirds of the total travel for the 

probes. For example, if you are using a probe with 0.250 inch (6.35 mm) full stroke, total travel (such as 

those provided by CheckSum) is 0.167 inch (4.24 mm) stroke, it should be fully compressed when the UUT is 

pushed down by the pressure rods. 

The CheckSum FIX-TOOL-150 installs the receptacles to be 0.150 inch (3.81 mm) from the 

top of the probe plate. When used with the standard length pressure rods, this provides the 

proper amount of travel for standard probing with 0.062 inch (1.5748 mm) thick PCBs. This 

spacing also allows the probes, in most instances, to make adequate contact when directly 

touching the PCB where there are no leads. For optimum height when probing a bare PCB 

pad, you can install these receptacles at 0.200 inch (5.08 mm) height from the probe plate. 

Conversely, you can decrease the height of the receptacles if you have longer leads on the 

PCB. 

After the receptacles are in place, the spring probes are installed. These can be hand-pressed 

into the top of the receptacle with light pressure or with a plastic tool. Most probing can be 

accommodated by crown head style probes. 

Standard probes use about 5.5 oz. of spring force each, although higher force probes can be 

used if the probe count is relatively low and lower force probes (e.g., 3.5 oz) can be used in 

very high probe-count applications. 

The limiting factor on the total probe load (number of probes times the probe spring force) is 

the amount of pressure that the system needs to exert to press the DUT on the spring probes. If 

probe loading is excessive, it can also cause the fixture cover and probe plate to flex, causing 

improper operation. 

In high pin-count applications, you can install fixture support posts in the fixture base. These 

can support the G-10 probe plate towards the middle of its span to minimize flexing. These are 

installed by drilling a 0.187 or 0.190 inch ( 4.75 mm or 4.83 mm) diameter hole in an unused 

area near the center of the fixture kit, and installing the post below the probe plate. 

Internal Wiring 

Once the receptacles are installed, the Fixture can be internally wired. This is performed by 

wire-wrapping from the bottom of the spring probe receptacles to the wiring blocks. 

Typically, a wire size of #22 to #26 gauge is used for this purpose. 

Fixture kits are shipped from CheckSum with blank covers over the unused wiring block 

cutouts. These covers can be cut to be resized or are available in several sizes from 

CheckSum. 

You will need enough 170-point wiring blocks to accommodate all of the points wired for the 

assembly. These are available from CheckSum. They are installed into the interface plate on 

the fixture kit, so that the wire-wrap leads are inside the fixture. 

6-26



Installing and removing the fixture 

Pressure Rods 

After the DUT has been drilled and wired, the pressure rods that press the DUT down onto the 

spring probes are installed. 

The fixed-length pressure rods are installed by drilling holes in the top polycarbonate cover, 

then installing the pressure rod with a screw or by pressing the top portion of the pressure rod 

into the top cover. 

You should install a minimum of four to six pressure rods. The more probes that you have and 

the larger the DUT, the more pressure rods you will need. For each 100 probes that are 

installed, the upward force on the DUT will be about 35 pounds. Typically, one rod is 

installed for about each 15-25 probes, depending on the board layout. 

If the DUT has any switches or adjustments which require access from above, the access holes 

should be drilled or milled out at this time. In order to maintain the strength of the top cover 

for high point-count assemblies, the access holes should be no larger than necessary for access. 

Note 

In order to ensure proper alignment when drilling or milling the cover plate, there are 

accurate matching alignment holes near the center edge of the fixture probe plate and top 

cover. 

Installing and removing the fixture 

To accommodate different assemblies, the system operator will typically need to change the 

fixture (also known as the “test head”). 

The following applies to CheckSum's standard vacuum fixtures. Other types of fixtures may 

require different methods for installation and removal. 

First remove any fixture that is already installed: 

1. Move the latching bar up and to the rear of the fixture until it stops. 

2. Slide the front of the fixture up and to the rear. 

3. Lift the fixture away from the fixture receiver. 

Then install the new fixture: 

1. Place the new fixture in place by sliding it towards you until it is all the way forward. 

2. Slide the front of the fixture down onto the latches on each side. 

3. Move the latching bar down and to the front of the fixture until it stops. 

The fixture installation is now complete. 

6-27


Installing the DUT on the test fixture 


Installing the DUT on the test fixture 

To install the DUT into the fixture, first open the top cover. To do so, using one hand, grasp 

the latch in the front and the latch bar and squeeze them together. Once the handle is 

unlatched, you can open the top cover to any position. 

The DUT is then installed over the guide pins. Once the DUT is in place, the top cover is 

pressed down until the latch engages, which holds the top cover and DUT in place with tension 

on the spring probes. This can take several pounds of pressure, depending upon how many 

probes are installed. Some types of fixture require that you actuate a top-mounted lever arm to 

engage the probes. 

The DUT is now ready for programming. 

Remove the DUT by reversing this procedure. 

Fixture Checklist 

Use this checklist to verify the fixture design and build is complete. 

Design 

“Design for Part Programming” review of the assembly is complete 

The exact part identifier of the ISP components is needed to validate the part for insystem 

programming. The part identifier is normally found in the bill-of-material (BOM). 

ISP data files are available for each device 

Access to each pin used for programming and power since ISP requires the same access 

as any other ICT fixture. This information is acquired from various files, typically the 

Gerber file set contains this information however other CAD files may provide this data. 

Contact CheckSum for additional details. 

The UUT physical information is needed to validate probe size and probe placement. In 

addition, the method needed to align the assembly to the fixture is determined. Other 

issues to be resolved are items such as solder-mask areas, size of test pads, and vias plus if 

any vias are not to be probed. In addition, some assemblies provide specific test points 

for ISP. 

If ISP is already performed with this assembly such as in an engineering lab, determine 

hardware items and files used to do this. Include the programming system model and part 

number. Please specify if a bed-of-nails (BON) fixture is being used or another 

attachment method such as ISP test-access pins or cables. 

Most assemblies have one IC that requires ISP and generally these assemblies are on a 

panel such that multiple ICs can be programmed simultaneously. Be sure to specify how 

many ICs are to be programmed on each assembly and on the entire panel. 

Since programming the parts simultaneously requires that all assemblies have power-on at 

the same time, the voltages and current requirements to power-on the entire panel is 

needed. Verify the power supply requirements are available from the system supplies. 

6-28




No overdrive is required for signals from the buffer module to the assembly 

ISP nets have no, or very small, capacitors (




Internal USB device and power supply wiring is specified 

Fixture Ready/ switch wiring is specified 

Fixture Present/ wiring is specified (see MW FIX I/O on page 6-13) 

Build 

System/Program 

Fixture checked on comparable system 

Final Report 

Programmer’s name, notes, programming execution time 

Wire list, probe map with head styles legend, spare probes 

Program media labeled and virus scanned 

Hardware 

Configuration of interface blocks verified 

Tooling pins secured with appropriate hardware; extra tooling pins included if required 

Push/pressure rods do not touch components 

Transfer probes & targets align properly (if applicable) 

Identifying label attached to the fixture 

DUT seats correctly on the fixture 

Spring probes compress about 2/3 of travel distance uniformly across fixture 

Boards can be loaded only in one orientation on the fixture 

Each buffer module is marked to identify the PCB number for each ISP device 

Wiring 

Twisted pair wiring used with the buffer modules and MW FIX I/O modules 

Every buffer module header pin has one wire connected, no unused header pins 

The ground side (-) of every twisted pair is connected to a spring-probe, no loose wires 

The last buffer module in each set has four 100Ω termination resistors added 

Power supply wiring from block K to each buffer module is the specified gauge wire 

Each power supply remote sense is connected to the appropriate power output line(s) 

Power supply output Enable/Disable control verified 

USB device signals wired to the fixture interface “K” wiring block (K-165 to K-169) 

Fixture Ready switch signal(s) wired to the fixture interface “A” wiring block 

6-30



Design for Part Programming 

Any optional USB hub power supply wired to the fixture interface “A” wiring block (A- 

154 & A-155) 

Software 

General 

Program optimized and working correctly 

Program panelized (if applicable) 

Customer supplied boards Pass with the exception of known defects 

Fixture matches description on work order 

Overall fixture is clean, hardware is fully installed, and fixture has quality appearance 

Unused fixture block spaces are covered with plates 

Documentation 

Final Report 

Fixture photo 

Probe map; top and bottom views 

Schematic with annotated probe points added 

Mechanical drawings 

Programming data and files 

Materials on loan that must be returned to the customer 

Boards 

Schematics (if paper copies were provided) 

Program files and media 


Many industry standard devices are designed to support In-System Programming (ISP). To be 

sure, see the device manufacturers’ specifications for information on whether a device can be 

programmed in-system, and the specific protocol it uses. 

There are many device programming protocols and the most common are: SPI, I2C, PIC, 

Microwire, and JTAG. Even if the target device manufacturer specifies the device supports In- 

System Programming, certain restrictions may apply. You will need to pay special attention to 

the DUT design to ensure the device can be programmed. Target device specifications and 

board design must be reviewed to determine if any issues apply. 

CheckSum engineers can provide answers to your ISP questions. 

6-31




The exact part identifier of the ISP components is needed to validate the part for in-system 

programming. The part identifier is normally found in the bill-of-material (BOM). Contact 

CheckSum to confirm the device is currently supported. The CheckSum web page 

“http://www.checksum.com/isp/multi-lib.asp” lists most of the supported devices and family 

of devices. 

ISP requires the same net access as any other fixture. This information is acquired from 

various files, typically the Gerber file set contains this information however other CAD files 

may provide this data. Contact CheckSum for additional details. 

The physical information is needed to validate probe size and probe placement. In addition, 

the method needed to align the assembly to the fixture is determined. Other issues to be 

resolved are items such as solder-mask areas, size of test pads, and vias plus if any vias are not 

to be probed. In addition, some assemblies provide specific test points for ISP. 

If ISP is already performed with this assembly such as in an engineering lab, please list the 

setup hardware items and files used to do this. Include the programming system model and 

part number. Please specify if a bed-of-nails (BON) fixture is being used or another 

attachment method such as ISP test-access pins or cables. 

Most assemblies have one IC that requires ISP and generally these assemblies are on a panel 

such that multiple ICs can be programmed simultaneously. Be sure to specify how many ICs 

are to be programmed on each assembly and on the entire panel. 

Since programming the parts simultaneously requires that all assemblies have power-on at the 

same time the system needs to provide the voltages and current required to power-on the entire 

panel. Confirm this is possible with the system power supply resources. 

ISP Restrictions 

If the UUT has capacitors connected to any programming test points, ISP may not be possible. 

The larger the capacitor value, the more likely this will be a problem. If any of the ISP nets are 

connected directly to power supplies or ground, ISP may not be possible. 

Since the ISP buffer module is not designed to overdrive other IC outputs, depending on the 

connections from the ISP part to other ICs, ISP may not be possible. For example, if ISP 

6-32




requires use of the device Reset, the board design may interfere with an external Reset from 

the buffer module. 

If the assembly uses a one-time programmable “OTP” IC, ISP may not be possible. If the ISP 

ICs are in sockets and there is a pin-for-pin compatible, non-OTP part available then we may 

be able to develop and verify the test fixture for ISP. Some MultiWriter ISP setups for OTP 

ICs have been developed, so contact the factory for more details. 

6-33


Considerations Before Making ISP Changes 


If electrical noise from on-board sources (switching power supplies, generators, etc) cannot be 

disabled then ISP may be unreliable or not possible. 

Considerations Before Making ISP Changes 

The device to be programmed, the circuit assembly, fixture, and program files are mutually 

dependent on each other. Any changes to the device, assembly, fixture, or files may cause the 

device programming to fail. Finding the cause afterwards can be very time consuming and 

costly. 

Before making any changes, be aware of the consequences and avoid unnecessary work. 

Here are some example changes that may lead to problems: 

• Changing the device type on the assembly 

• Changing the memory size of the device 

• Changing the device oscillator frequency 

• Changing the PCB layout, adding capacitance to programming signal traces, changing 

pull-up resistors, etc 

• Changing the location of the data file(s) 

• Changing the device control bits such as the option bytes or security bits 

• Changing any of the device parameters on page 10-14 in the MISP setup on page 10-7 

Changes are often required and not every change will necessarily cause problems. Just be 

aware that some types of changes to one part of the setup will require changes to another 

section. 

CheckSum can help review the changes that are being considered, contact us on page 18-3 

before the changes are made. 

6-34

Chapter 7 

System Operation 

Programming an Assembly 

Overview 

This topic describes how to use the Test System to test assemblies (called UUTs or unitsunder-test). 

If you have not already installed the CheckSum hardware and software into your 

PC, refer to Installation on page 4-1. 

Caution 

The CheckSum Test System provides adequate protection against normal 

input voltages at the test points. However, the System can be subject to 

damage in environments of high electrostatic discharge (ESD). If this is the 

case in your testing application, ensure that you wear a grounding strap 

connected to the system chassis or earth ground, and that the UUT is 

adequately discharged before connection. If it is not possible to take these 

precautions, contact CheckSum to discuss alternative forms of ESD or 

overvoltage protection. 


Program Window Main Menu below 

Selecting the Test Program on page 7-2 

Executing the Test on page 7-4 

Test Display on page 7-5 

Example Programs on page 11-1 

Programming Window Menu 

To start the System, click on the MultiWriter pps shortcut on your desk-top, use Windows 

Explorer, or use the run command to execute the PPS.EXE program.


Selecting the Program File 


You will then see the System window shown in the following figure. 

Main Window, Test Menu 

• Run Test (F1) begins execution of a test program. You are first asked if you would like to 

load a new test program or execute the one currently loaded. Once this is completed, test 

execution will start. 

• Test Screen window transfers control to the Test Window. From this window you can 

start a test of your assemblies. See Test Display on page 7-5. 

• Enter UUT Serial Number (F7) allows the serial number for an assembly to be entered 

prior to starting a test. This can be used to verify the serial number to insure it is valid. 


File Selection Window 

To test an assembly, select 'Test' from the System window. See Main Window, Test Menu on 

page 7-1. This displays the Open File dialog box shown in the following figure: 

7-2




Open File 

Above the File name box is a list of the file names present in the current working directory. If 

you press the Open button, it will load the test program shown in the File name box. You can 

also double-click on one of the file names to load it. You can also type the file name in the 

File name box. Click on the directory box in the upper left part of the dialog box to change the 

directory. Move the mouse into the list of file names and click the mouse right button on a file 

name for more file options (Delete, rename, etc). Right click anywhere else in the file list box, 

then the menu of View, Arrange Icons, Display Folder At, New Folder, and Refresh will 

appear. 

At the bottom of the dialog box, the function keys and their actions are shown. 

Note that the names shown in the list of files may not be test programs. The system uses the 

convention that it lists names less than eight characters without an extension, or names eight 

characters long with any extension. 

The recommended file name extension (File Type) is .SPEC since this extension is associated 

with the CheckSum test system software. The .SPEC file association setups the CheckSum 

software to load and run the test program when the file is double-clicked in Windows Explorer. 

If an assembly has been learned but not saved on disk, it is valid to continue with the test even 

though no file name is present, i.e., "( )". 

7-3


Executing the Program File 


Executing the Program File 

Once the test program is loaded, execution begins. In the default configuration, the system 

halts after each failure. You can configure the system to continue to the end of the test without 

halting if you wish by disabling 'halt on fail' in the 'Test' menu. 

If halt on fail is enabled, you are presented with the 'Component Test Failure' window shown 

in the following figure. The same window pops up for each test step when 'Single Step' is 

enabled or when testing is halted. 

Component Test Failure Window 

The 'Component Test Failure' Window is displayed when a tests step halts due to a failure. It 

can also be displayed after each test step if the system is in 'single step' mode. It is shown in 

the following figure. 

Component Test Failure Window 

In the Component Test Failure Window, there are several different items describing the failure: 

• The name of the component that has failed is shown in yellow. This is taken from the title 

field of the test program. 

• The From Pin and To Pin are shown on each side of the component name. These are the 

UUT points that are being measured at the time of the failure. 

• On the right side of the display, the system displays the high limit and the low limit. A 

passing test is between these two values. 

• The Measured value is positioned in different locations, depending on the measured 

value. If the test has passed, it is between the high and low limits. If the test failed with a 

value that is too high, the measured value is above the high limit. If the test failed with a 

value that is too low, the measured value is shown below the low limit. 

Test Failure Function Buttons 

In the Component Test Failure Window, there are several different options that the operator 

can choose by pressing the buttons at the bottom of the display: 

7-4



Test Display 

• Stop terminates execution of the test program and shows the 'Test Window' window, see 

the Test Display below. 

• Next logs the test result presently being displayed, and moves to the next test step for 

execution. Use Next to continue normal execution of the test program. 

• ReTest executes the step again. The new result is then displayed. This can be used, for 

example, if you suspect a fixture contact problem. You can cycle the fixture switch 

up/down, then perform a ReTest to see if the problem is corrected. 

• Continuous Test is used to make measurements continuously and display the results. In 

this mode, the system works much like a bench-top meter, in that the displayed readings 

are continually refreshed. The Continuous Test button works like a toggle. Press it once 

to start continuous measurements, then press it again to stop them. 

• Help is used to find information about the test system and its use. 

• Other: While the failure window is displayed, Ctrl-H allows the Halt on Fail setting for 

this test run to be toggled. Ctrl-S allows the Single Step setting for this test run to be 

toggled. 

Test Display 

After each test, you are presented with the 'Test' display shown in the following figure. From 

this display, the most common operations are to invoke a ReProgram of the last assembly, 

program the next assembly, or print a test report for the assembly that has just been tested. 

Test Window 

7-5


Test Display 


This window shows information during the test execution and after the test completes. The 

window format can be modified with the environment pull-down menu in the Environment 

Menu on page 7-14. Turning-off the "Show Pass/Fail" selection changes the size, quantity, 

and position of the toolbar buttons. The "Show Pass/Fail" selection is normally enabled 

(checked). 

At the top of the display, the total test time is shown plus the total number of errors. At the top 

right of the display, the test status box next to the Stop button, shows either "Testing" (in 

progress), waiting for operator input, test complete, or test terminated. The center top box 

shows "Passing" or the number of errors. The center section of the window (with 4 large 

buttons) indicates the test completion status in green (PASS), red (FAIL), or yellow if the test 

was terminated by the operator (Esc key / Stop button). If the background color is yellow at 

test complete then the test program was terminated by the operator before it completed its 

normal test sequence and no test errors were found therefore the test sequence may contain 

skipped steps that normally are not skipped. A yellow PASS background indicates the UUT 

was not fully tested and that no steps failed prior to the test termination by the operator. 

A status graph, just below the test time, shows a test progress gauge for the test program. 

Portions of the test program that passed are shown in green, and portions that failed are shown 

in red. This can be used at test time so the operator can watch the status of program execution. 

Note that test programs can be written that do not proceed through the test steps linearly. In 

this case, the progress gauge will not be filled out from left to right in a smooth manner 

(sections that are not green or red were skipped). 

7-6



Test Display 

Test FAIL Results for a Panel of Boards 

For a panelized assembly on page 10-33, with multiple boards in the panel, the test results, 

shown by the color of the small boxes in the PCB Test Map, indicate several possibilities: 

White box = this board has not been tested (if the test is complete, this board was 

skipped) 

Black box = test is "in progress" for this board 

Yellow box = this board has not failed any tests 

Red box = this board failed at least one test 

Green box = the test is complete and this board passed, any yellow boxes are set to 

green 

Note: The use of jumps/loops on page 14-10, Error on page 14-13, and Rprts on page 14-49 

can affect the test results and the color of the PCB boxes. 

Main Test Functions 

There are several major buttons for the operator to press: 

7-7


Test Display 


• Program (F1) begins execution of the program sequence for the next UUT. Prior to 

pressing this button, load the next UUT on the fixture. After the program button has been 

pressed, the System logs and/or prints results (depending on how the system has been 

configured) for the assembly that has just been tested, then begins a test of the assembly. 

Exiting the Test Display or loading a new program will reset the Batch Count and Batch 

Errors to zero. 

The Batch Count will increment by 1 for each assembly (PCB) programmed (F1). If all of 

the PCBs in a panel are skipped, the Batch Count will increment by 1. 

• ReProgram (F2) runs the program sequence again on the assembly that has just been 

programmed. This is similar to the 'Test' button, but results are not logged or printed for 

the UUT that has just been tested. 

Selecting ReProgram instructs the system to discard the last test results and to test the 

assembly again. 

The test results are written to the Statistics Data log file when one of these actions occur: 

1. When the next test is started 

2. Exit the test results window 

For example: 

Action 

[F1] Program an assembly 

Test complete 

[F1] Program next assembly 

Test complete 

[F1] Program next assembly 

Test complete 

[F2] ReProgram 

Test complete 

[ESC] Exit 

Log (SPC) file contents 

No test results are saved yet 

First set of test results are now saved 

Second test results are not saved yet 

Second set of test results are now saved 

Third test results are not saved yet 

Third test results are discarded 

New third test results are not saved yet 

New third test results are saved now 

Exiting the Test Display or loading a new program will reset the Batch Count and Batch 

Errors to zero. 

ReProgram (F2) first decrements the Batch Count by the number of assemblies in the 

previous program, then increments the Batch Count by 1 for each assembly programmed. 

The previous test results are discarded and not saved in the SPC file. If all of the PCBs in 

a panel are skipped, the Batch Count will increment by 1. 

• Report (F3) prints a test results report or a test failure report for the UUT that has just 

been tested. The report is printed in the format and to the device specified in the menu 

section Environment > Report Device (selected option) and Environment > Test Report 

Contents. If the selected report device is the CRT, then a window will open with the 

report, for example: test results, for example: 

7-8



Test Display 

Test Results Report 

There are several print options provided: 

Print … allows you to select and set the preferences for the windows printer. 

Win Print F5 prints to the default windows printer in 80-column format. 

Strip Print F7 formats the output and prints to the CheckSum Model T-120-2P 40- 

column printer, normally connected to LPT1. 

Pressing the Report Button in the Test Window can create two files, test.rpt & output.txt in 

the Temporary Files on page 5-16 directory. 

The creation and contents of these temporary files may change with different versions of 

the test system software. Review the Statistics Data log file on page 8-17 for test results. 

• Exit (ESC) is used to terminate testing. After selecting EXIT, you will return to the 'Main 

System' or Edit window. Exit is normally used when you are changing from one type of 

UUT to another UUT (although you can do so from this window with the 'File' pull-down), 

or if you have completed a batch of UUTs, and wish to start another. 

• Stop Test, the STOP sign button in the upper right corner of the test window can be used 

to stop the test program. 

Menu Bar 

At the top of the 'Test' display, there are several pull-down menus for performing various 

functions. These are: 

File Menu on page 7-10 

Test Menu on page 7-11 

7-9


Test File Menu 


Report Menu on page 7-12 

Environment Menu on page 7-14 

Panel Menu on page 7-18 

Help Menu on page 7-20 

Test File Menu 

Test Window - File Menu 

• Open loads a new test program from disk into memory so that it is available for execution. 

• Save writes the test program now in memory to a disk file. 

• Save As allows the program file name and location to be changed before the save 

operation. 

• Edit returns to the test program editor. 

• Examine SPC Data by UUT Serial Number is used to review and edit the test results of 

a particular UUT that has been tested with the System. SPC logging and serial number 

logging must both be enabled in order for this option to be usable. 

• Set Recently Used Files List Capacity allows you limit the list of recently used files that 

are shown. 

• Exit exits to the 'Main System' window. 

7-10



Program Menu 

Program Menu 

Test Window - Program Menu 

• Program F1 begins execution of the test program to test a UUT. Prior to selecting this, 

put the next UUT to be tested onto the test fixture. 

• ReProgram F2 begins execution of the test program to test a UUT. This is used to 

ReProgram the UUT that you have just tested. This selection is similar to 'Test Assembly', 

but does not log any data for the test that has just been completed. 

• Stop will stop the program. The STOP sign button in the upper right corner of the test 

window can also be used to stop the test program. 

• Program Multiple Times will run the test program multiple times. The number of times 

is specified in the menu item Environment > Multiple Test Count, see the Environment 

Menu on page 7-14. This feature is used to verify the test passes many times and the test 

results can be saved for SPC analysis if SPC data logging is turned-on, see Activating 

Statistical Analysis on page 8-4. Using multiple UUTs and multiple tests, the SPC results 

can be sufficiently significant to validate the test limits. 

• Probe UUT Point sets the system into probing mode. The probe needs to be connected to 

the banana jack on the side panel of the System. 

• Single Step can place the System into the mode in which it halts after each test step 

(whether passing or failing) and presenting the 'Component Test Failure' window. This 

mode can be used for debugging a test program. 

7-11


Report Menu 


• Halt on Fail will place the System into the mode in which it halts after each failed test 

step and displays the 'Component Test Failure' window. If 'Halt on Fail' is not selected, 

the test will completely execute before stopping at the 'Test' window. The 'Halt on Fail' 

mode is often used to allow the operator the opportunity to repeat a test or make simple 

repairs during the test. 

Report Menu 

Test Window - Report Menu 

• Test Report F3 prints a test report on the UUT test that has just been completed to the 

device selected in the 'Environment' pull-down. The contents of the test report (whether it 

shows just failures or passes and failures) can be changed in the 'Environment' pull-down. 

Most facilities elect to print paper copies of the reports on failed UUTs, with the report 

only containing the failures. The System can be configured to automatically output reports 

in the configuration section of the Software. If the selected report device is the CRT (test 

system display), then a window will open with the report, for example: 

7-12



Report Menu 

Test Report 

There are several print options provided: 

Print… allows you to select and set the preferences for the windows printer. 

Win Print F5 prints to the default windows printer in 80-column format. 

Strip Print F7 formats the output and prints to the CheckSum Model T-120-2P 40- 

column printer, normally connected to LPT1. 

Note: An asterisk * at the end of the line indicates a Failed step. If the USB connection is 

not working, the measured value will show Fail. A measurement unit may follow Fail, 

such as FailV has the value Fail and unit of V, for Volts. 

• Batch Report prints a report that describes the batch of UUTs that have been tested. This 

report contains the total number of assemblies tested, how many have failed, and the 

resultant yield. 

Exiting the Test Display or loading a new test program will reset the Batch Count and 

Batch Errors to zero. 

The Batch Count will increment by 1 for each assembly (PCB) programmed (F1). 

If all of the PCBs in a panel are skipped, the Batch Count will increment by 1. 

ReProgram (F2) first decrements the Batch Count by the number of boards tested in the 

previous test, then increments the Batch Count by 1 for each board tested. The previous 

test results are discarded and not saved in the SPC file. 

7-13


Environment Menu 


• Enter UUT Serial Number . . . F7 allows you to enter the serial number of the UUT that 

you have just completed, or are about to test. This information is included in the SPC 

logging file (if enabled) and in the UUT test report. You may type in the UUT serial 

number, or if you have a wedge-style bar-code reader, you may read it from a bar-code 

label on the UUT. With the configuration section of the system software, you can enable 

the System to automatically solicit the UUT Serial Number from the operator. 

• Enter Batch ID allows you to enter a name describing the batch of UUTs that you are 

currently testing. This is used in the batch report and the SPC log (if enabled). With the 

configuration section of the system software, you can enable the System to automatically 

solicit the Batch ID from the operator. 

• Edit UUT Serial Numbers allows you to edit a serial number that was previously entered. 


7-14




Test Window - Environment Menu Primary & Secondary selections 

The environment menu is used to alter the configuration of the testing environment. Following 

is a description of each of the options available to you from this menu: 

• Show Pass/Fail changes the appearance of the testing window at the end of the each test. 

In the default mode (Show Pass/Fail enabled), the system presents a large bar in the middle 

of the window. The color of this bar changes to green if the test has passed, or red if the 

test has failed. In the middle, large text says pass or fail, which is surrounded by buttons 

for test, ReProgram, report, and exit. If Show Pass/Fail is turned off, this display does not 

appear, and a tool bar is present at the top of the window. This tool bar offers the same 

functions as the larger buttons, but in a more compact format. Also, if Show Pass/Fail is 

turned off, the operator can see the last messages of test program execution in the user 

display. This may be confusing to the operator if they are messages that are inadvertently 

left over, but the test program can be written to leave messages that are useful to the 

operator at the end of the test, such as repair information about the UUT. 

• Show Pareto of Batch Errors allows you to enable display of a Pareto chart at the bottom 

of the window after each test. The Pareto chart shows the errors during testing, sorted in 

order of frequency. The errors refer to the batch of UUTs that are being tested rather than 

the last UUT tested. To reset the statistics, you can either exit from this window and reenter, 

or reload another test program. The Pareto chart is useful because it alerts you about 

potential systematic errors that you would like to detect as soon as possible. For example, 

if a pick-and-place machine has an incorrect reel loaded for one of the parts, you will see 

that the error frequency for that part will be high. In the chart, the top shows how many 

defects have occurred during the batch. Each line, then shows the failed part (taken from 

the title of the test step), then a percentage that shows what percentage of all failures in the 

batch can be attributed to this particular failure. At the bottom of the display the number 

of assemblies tested and the percentage of failed assemblies is shown. 

7-15




• Show Pareto for execution times shows the amount of time taken for the slowest test steps 

of the program. This can be used if you would like to optimize overall test speed of the 

program by fine-tuning or deleting some of the test steps. 

• Show Test Progress allows you to enable or disable displays to the operator that show 

program execution progress. There are two ways to monitor progress, either of which can 

be enabled individually. 'Show Test Progress Step Number' enables display of the step 

number that is presently being executed, or at which you have paused. The step number is 

the line in the program, which matches the step number displayed in the upper left corner 

of the edit window. 'Show Test Progress Progress Gauge' enables a bar graph in the upper 

left corner of the display. The bar graph fills up as the test executes. Portions of the test 

program that pass are shown as a green bar, and those that fail as a red bar. In most cases 

the bar will fill up from left to right, however if the test program has control conditionals 

such as jumps and calls, the bar may fill in a random order, and some areas may be void. 

The progress gauge is a convenient way for the operator to observe test execution progress 

and easily observe the approximate proportion of failed steps in the program thus far. 

• Test Report Contents allows you to specify which test steps are included in the test 

report. You can select between reporting on all steps that have been executed or just 

reporting on steps that have failed. In most installations, reporting only the failed steps is 

the most practical since reports are shorter and only contain information that is needed for 

repair purposes. 

• Report Device allows you to select the device that test reports will be sent. In the default 

mode, they are sent to the display (CRT). With this selection you can select to send the 

reports to printer devices, or to a file on the system disk. Note that this only specifies the 

device, but does not output the report. In order to output the report, you must select 

'Report' separately. This option applies to batch reports and test reports, but not other 

reports, such as test program listings that can be output with the system. If CRT is 

selected, when the Report is selected (F3), a window is displayed that you can page down, 

page up, and go to the top of the report. If 'Viewer' is selected, the reports are displayed in 

Windows WordPad (or a viewer you have specified in the configuration setup). With 

WordPad you can scroll, and even print the report. 

• SPC Logging allows you to enable logging of testing outcome to a file on the system disk. 

This is used if you want to use the SPC features of the test system. There are different 

levels of logging available: 

– Summary only records information about the overall test, for example pass or fail, 

number of errors, operator, UUT serial number, batch name, elapsed time, and start 

time. This logging is compact and records all of the information that is used for 

production reports. 

– Summary+Fails also records the details of steps in the test that have failed. If you 

record this data, it is used for SPC Pareto reporting. 

– Summary+Passes+Fails also records the details of steps in the test that have passed. 

If you record this data, it is used for SPC X-Bar/Sigma reporting. 

7-16




• Max Errors sets how many failures can occur on a UUT before the test is terminated. In 

the default mode, 10000, the test always completes regardless of the number of errors, 

unless the operator manually terminates the test. If a lower number is set, and the test 

exceeds that number of failures, the system stops the test, alerts an operator (see Warning 

in the next paragraph), and jumps to the program step "LABEL SHUT DOWN". If there 

is no SHUT DOWN routine, the test program exits to the Test Display. Note that the 

actual number of errors may exceed the limit in some cases. For example, the error count 

may be exceeded in the middle of a CONTinuity test that may have additional errors occur 

before the check is completed. Use of limited Max errors can speed test flow. 

The Max Errors Exceeded Warning checkbox, in the maximum number of errors setup, 

allows the system to alert an operator when the test exceeds that number of failures. To 

allow the test to automatically continue, leave the checkbox unchecked. The warning 

message allows the operator to continue to the next test step or exit (see LABEL SHUT 

DOWN in the previous paragraph). 

• Multiple Test Count (value) sets the test count for testing the assembly multiple times. 

The test menu item Test > Run Multiple Times uses this test count value. For example, if 

the value is set to 10, the test is run 10 times, see the Test Menu on page 7-11. 

• Measurement Messages allows you control how warning and error messages affect test 

execution. If enabled (checked) then the system will display and wait for the operator to 

acknowledge the warning or error message before proceeding. If disabled (not checked) 

then the system will only beep when these conditions occur and the system will 

automatically continue to the next test step. 

• Check UUT Serial Number allows you to either warn the operator or prevent testing if 

the UUT Serial Number (UUT ID) is not appropriate. The UUT serial number can be 

tested for the correct length, and for panelized assemblies, a duplicate entry between the 

serial numbers on the panel. 

• Login User allows you to enter a user (operator) name into the System. If the system is 

configured with login names turned on, a user must be logged in at all times. Optionally, a 

password may be required for each user. The system can be configured so that different 

users have different access privileges and may see different menu options. Login 

privileges are defined in the 'Configure System' section of the software that can be 

accessed from the main window. 

• Program Start selections control when the program starts. The keyboard function key 

signal F1 and the fixture ready (left and right) signals can be used. The operator action of 

closing the fixture lid can generate the fixture ready signal on page 6-17. 

• Program Auto Load is used to specify the Flash drive location and name of the program 

and a checkbox to enable/disable use of this option. When enabled and the Flash drive is 

detected, the system offers to load the specified program when in the Main, Test, or Edit 

windows. 

7-17


Panel Menu 


Panel Menu 

Test Window - Panel Menu 

The Panel menu is active and available when you are testing a panelized assembly. It provides 

you with several functions that can ease testing of UUTs that are not separated prior to test. 

• Select Skips allows you to skip over some of the PCBs in the panel. You may wish to do 

so because some may not be populated or some of the PCBs may have already been 

rejected. To eliminate a PCB in the panel, move to it with the four arrow keys, then press 

the SKIP button. An S will then appear in the selected PCB location. By pressing SKIP 

again, it will be deselected. You can press OK to continue on to the test, or select other 

PCBs for skipping in the same manner. 

7-18



Panel Menu 

• Retain Skip Selections provides the capability for the system to remember the last settings 

for 'Select Skips'. This can be used, for example, to eliminate re-entry of the skipped 

selection if you have a run of boards with the same configuration. 

• Status Map instructs the System to display a graphic of the panelized assembly. Each of 

the PCBs in the panel are displayed, along with the last test status of passed, failed, or 

skipped. 

• Reports sorted by PCB can be used to change the order of the test results listing. In the 

default mode, the system sorts the test report so that each PCB is reported on in order by 

PCB. If reports sorted by PCB is turned off, the system reports in the order of the test 

program steps. In most cases, test programs are written in a linear fashion so either 

selection will work the same. 

• Max Errors per PCB selection causes the Environment > Max Errors limit to be applied 

to individual PCBs rather than to the total errors of the UUT. 

7-19


Test Window - Help Menu 


Test Window - Help Menu 

Help Menu 

The Help menu can be used to obtain on-line help about the Test System. 

• Contents... allows you to search the table of contents for the help sections. 

• Topic Search... allows you to search the help data based on a topic that you enter. 

• Getting Started... helps you learn how to use the test system hardware and software. 

• About... shows information about the software that you are using. It provides the revision 

number, a number to call at CheckSum if you would like to talk to an engineer, and the 

most recent date that the System self-test has been run. 

7-20

Chapter 8 

Statistical Analysis of Test 

Results 

Statistical Analysis 

Overview 

The following figure shows how to display the Statistical Analysis functions from the main 

window.

Statistical Analysis of Test Results 



Statistical Analysis Menu 

• Generate SPC Report allows you to generate reports based on the assemblies you have 

tested. These reports include X-Bar/Sigma Reports (statistics about individual analog 

measurements), yield Production Reports (statistics about how many assemblies have 

passed and failed), and Pareto Failure Reports (information about the frequency of failures 

by failure type). 

• Examine SPC Data by UUT Serial Number allows you to enter the serial number of 

assemblies that have been tested, and recover the history of testing that UUT. 

The Generate SPC Report window, shown in the following figure, is used to obtain reports 

from the System that can be used to analyze productivity, find process problems and determine 

which are the most significant, and to analyze testing tolerances. Sample Reports on page 15- 

1 shows examples of the various reports that you can generate using this capability. 

8-2




Generate SPC Report 

Report Types 

There are three basic types of reports. 

• The Production Report displays how many assemblies are tested during the reporting 

period, and the results of the testing, for example, how many passed and how many failed. 

• The Pareto Failure Report displays information about the defects that are occurring, 

sorted by frequency so that you can easily find out the relative occurrence of faults so that 

you can address the most significant ones first. 

8-3


Using Statistical Process Control 


• The X-Bar/Sigma Report displays information about specific analog readings, such as 

measurement averages, closeness to limits, and dispersion. The primary use for this report 

is to help assign tolerances and limits within the test program, although it can also be used 

to analyze process trends. 


• Using Statistical Process Control below 

• Examine SPC Data on page 8-14 

• Edit Run Failures on page 8-15 

• Reporting on Panelized PCBs on page 8-17 

• SPC Data Format on page 8-17 


Activating Statistical Analysis 

To activate statistical analysis, you must enable logging for the dates of the reporting period. 

Logging is enabled from the Configure System screen, 'Environment' page, 'Configure 

Reporting', tab marked 'SPC Logging', check the Statistics Data Logged box as shown in the 


• Production Reports only require that logging of summary information is enabled. 

• Pareto Reports require that logging of failure information is enabled. 

• X-Bar/Sigma Reports require that logging of pass information is enabled. 

Logging of more data than is minimally required for each report does not create any problems, 

other than the use of more disk space and the time to write the data between tests. 

8-4




Configure SPC Reporting 

SPC reporting is performed by selecting from the following options in the Generate SPC 

Report screen: 

• UUT Reported On below 

• Change Starting/Ending Period below 

• Statistics Data Path on page 8-6 

• Production Report on page 8-7 

• Pareto Failure Report on page 8-9 

• X-Bar/Sigma Report on page 8-11 

UUT Reported On 

This selects which UUT to report on. The default, All, reports on all UUTs that have been 

tested in the selected time frame. If a 'Selected UUT' is specified, only UUTs tested with that 

test program are analyzed. It is necessary to select a single UUT with X-Bar/Sigma Reports, 

but either option is applicable to Production Reports and Pareto Failure Reports. 

After selection of selected UUTs, you can use the entry box to select the particular UUTs (by 

test program name) to analyze. 

Change Starting/Ending Period 

The 'Change Starting Period' and 'Change Ending Period' selections of the Generate SPC 

Report screen allow you to specify the time frame which the report encompasses. The default 

when you first enter the Generate SPC Report screen is for the entire present day. You can 

8-5




enter any range of dates and times to allow analysis of a single shift or analysis over a long 

period of time. 

To change a date/time: 

1. Select the button for Starting Period or Ending Period. 

2. Use the Change Starting/Ending Period screen shown in the following figure to set the 

date and time. 

Other methods: 

• select entries in the date box or type in new values 

• click on a date on the calendar 

• use the arrow buttons to change the month 

• use the AM/PM buttons, or click on the hands of the clock and drag them to a new position 

Change Starting/Ending Period 

Statistics Data Path 

Allows you to specify the directory that contains the log files for the System. For your 

interest, the log files are named YYYYMMDD.DAT. For example, SPC data stored on 

December 1, 2010 is saved in the file named '20101201.DAT'. When you elect to change the 

statistics data path, you use the Directories Configuration screen shown in the following 

figure. In this screen, use the middle entry to specify where to store the raw SPC data files. 

8-6




Directories Configuration 

Production Report 

Allows you to review and print a Production Report as shown in Sample Reports on page 15-1 

and shown in the figures below. The Production Report lists 

• how many UUTs have been tested 

• how many passed 

• how many failed 

• the yield 

• the total number of defects encountered. 

If you are reporting on all UUTs and more than one has been tested, the Production Report also 

shows the production information (total, passed, failed, yield, defects) listed by UUT type. 

The list includes the PCB number of any panelized test failures when PCBs are counted as 

separate UUTs. 

Once you are displaying the Production Report, you can print it with the 'Print' button. As an 

option prior to printing, you can also elect to save the report to a file on the disk. The format 

of this ASCII file is shown in Sample Reports on page 15-1. 

8-7




Production Report Details 

8-8




Production Report Header 

Pareto Failure Report 

Selection of the Generate SPC Reports window allows you to review and print a Pareto Failure 

Report as shown in the following figures and Sample Reports on page 15-1. The Pareto 

Failure Report is used to analyze the failures that have occurred over the testing period. This 

allows you to find which failures have occurred most frequently so that you can best spend 

your time correcting the necessary aspects of the process. Logging of failure data must be 

enabled during the reporting period to obtain Pareto Reports. 

The Pareto Failure Report lists the total number of defects, then each defect in descending 

order by frequency. The defect descriptions include: 

• the test program name 

• the calling test program if the test program is called from another test program 

• which step number has failed 

• what test type (e.g., MISP) 

• the test title (e.g., U203), how many failures have occurred 

• the percentage of the total number of defects that have occurred over the reporting period. 

8-9




Pareto Failure Report Details 

Pareto Failure Report Header 

8-10




X-Bar/Sigma Report 

Selection of the Generate SPC Reports window allows you to review and print an X- 

Bar/Sigma Report. The X-Bar/Sigma Report button displays an X-Bar/Sigma Report as shown 

in the following figures and Sample Reports on page 15-1. The X-Bar/Sigma Report is used to 

identify trends of analog measurements to tell if a process (or component value) is tending to 

be near one of the test limits. It can also be useful when determining test tolerances to use for 

a UUT. 

If you print the detail report directly to a printer, the graphic images for each step are printed. 

If you print the detail report to a file, the report is converted to a character-oriented version of 

the information. 

The X-Bar/Sigma Report contains an entry for each test that has been logged during the 

reporting period for the UUT selected. Each step is described as a bar with a pointer and a 

bell-shaped curve. 

X-Bar/Sigma Report Details 

8-11




X-Bar/Sigma Report Header 

Interpreting the Graphs 

The length of the horizontal bar approximates the distance from the low test limit to the high 

test limit. Below the ends of the bar, the test's low limit (LL) and high limit (HL) are shown. 

Red tick marks near the end of the bar locate the precise high and low limit positions. 

The bell-shaped graphic above the bar is the statistically predicted range and frequency of test 

measurements as based on the logged data. The peak (center) of the curve is the average (Xbar) 

reading, which is also listed in the title. The area contained under the bell-curve for a 

certain range of readings, as a percentage of the total area under the bell curve, tells you what 

percentage of readings will fall into that range. Above the bar, in the center, the System lists 

the step number, the step type, and the X-Bar (average) computed value. Areas under the bell 

curve that are within the test limits are shaded in green. Areas outside the test limit are shaded 

red. Note that in cases such as "less than" or "greater than" tests, you may see a red area under 

the curve that is of no consequence. 

Below the bar, the System lists the Standard Deviation (Sigma) of the readings recorded during 

the logging period. This tells how randomly or widely spread the individual readings are. This 

data is used to generate the bell-shaped curve. 

The end of each bell curve represents approximately the 3-Sigma limit. The 3-Sigma limit 

(computed by multiplying the Standard Deviation by 3 and adding/subtracting from the X-Bar 

reading) shows how far readings can be expected to vary based on the sample set of readings. 

If the number of UUTs logged is fairly large, the 3-Sigma limits show the test limits that 

virtually all typical UUTs would pass. 

The computed values for Cp and CpK are also shown above the bar. The Cp value is on the 

upper left and the CpK value is on the upper right. Cp is an indication of how widely spread 

8-12




the readings are with respect to the high and low test limits. Cp should normally be well above 

one. If it becomes less than one, normal deviations in the readings will cause out-of-tolerance 

conditions. This is an indication that the limits are too close for this measurement. 

CpK indicates whether the average readings are getting too close to one of the test limits. 

Where Cp shows the range of variations with respect to the size of the tolerance window, CpK 

shows if the variations are not centered in the tolerance window. If the high and low limits are 

symmetrical with regards to X-Bar, Cp and CpK will be equal. CpK becoming less than one is 

an indication that the average readings value are becoming so close to the high or low test limit 

that some good readings will start to fail. 

The X-Bar/Sigma Report can be useful for adjusting tolerance values when first programming 

a new UUT. You can initially set the test limits fairly widely, then test a batch or two of 

UUTs. From the X-Bar/Sigma Report you can then determine the typical measured values (X- 

Bar) and the typical range of readings (the 3-Sigma value or edges of the bell curve). The 3- 

Sigma limits can be useful guides for setting the limits. For consistent testing results, bell 

curve should be well within the high and low test limits for the test step. 

Note 

Limits set by using the 3-Sigma indication can be tighter than the accuracy 

of the System. Before tightening measurement tolerances from the entry 

defaults, ensure that you are not exceeding System specifications. 

Note that the X-Bar/Sigma Report bases its calculations on UUT measurements that passed 

and ignores failed measurements. This is because ATE failures are typically catastrophic in 

nature (for example, if a component is missing or shorted) and hence would skew the outcome 

excessively. As a result, when you are using the X-Bar/Sigma Report for assigning test 

tolerances, you should first assign quite wide tolerances to ensure that virtually all good UUTs 

pass. 

System logging for passed data must have been enabled for the UUT during the period which 

the data is generated. 

A UUT must be selected for X-Bar/Sigma Reporting ('All' UUTs is not valid). The X- 

Bar/Sigma Report will try to find the test program for the selected UUT in the Test Program 

directory. If the test program for the selected UUT is found, the low and high limits specified 

in the test program will be used for the analysis. If the test program for the selected UUT is 

not found, the low and high limits in the logged data file will be used for the analysis. 

At the bottom of the X-Bar/Sigma Report screen, you can choose to display all test step entries 

or just those beyond a specified CpK by pressing the Options button. The CpK default, three, 

displays readings that are more than 1/3 of the expected measurement range from the average 

reading to the test limit. By displaying only entries with low CpKs, you can quickly determine 

which test steps are likely to need attention. 

The Options dialog box also allows you to select the type of X-Bar/Sigma graphical display. 

The selections are the normal distribution Bell Curve, Histogram, or both. 

The Set Limits button allows you to change the limits of the corresponding step and view how 

this changes the graph. Note that there is no change in the set of sampled data. To get a new 

set of sampled data that reflects the new limits, we need to analyze the logged data again using 

the new limits. To do this, use the ReAnalyze button in the X-Bar/Sigma Report Screen. (it 

8-13


Examine SPC Data 


may take a while depending on the size of the logged data). Fit All Limits Button 

automatically fits all entries that have CpK less than 3.0 to fit into CpK = 3.0. 

Note 

For some test types, the system does not allow a limit value less than 0. 

Hence, Fit All Limits does not guarantee that all entries will have CpK 

value at least 3.0. 


This screen and its submenus allow you to view summaries of a UUT test by UUT serial 

number. You can also modify SPC file contents by deleting an entire test on a UUT, by 

deleting single test steps, by assigning failure codes to test steps or by adding failure codes to a 

test run. The failure codes can contain diagnostic information about the cause of run failures. 

After a UUT is repaired, these can be used to enter the actual failure that occurred. Access to 

these screens requires password privileges both to modify SPC files and to run SPC analysis 

when password protection is in use. 

To obtain the Examine SPC Data Screen, select 'Examine SPC Data by UUT Serial Number' 

from the 'Statistical Analysis' pull-down menu in the System screen. 

8-14



Edit Run Failures 


• UUT Serial Number allows you to specify the UUT serial number used for searching the 

SPC database. For data recorded without a serial number the string recorded in the log is 

. 

• Change Starting Period specifies the beginning date and time of the search. The 

resultant entry screen is exactly like that in , with its associated description of use. 

• Change Ending Period specifies the beginning date and time of the search. The resultant 

entry screen is exactly like that in Change Starting/Ending Period on page 8-5, with it 

associated description of use. 

• Search executes a search for tests done on the specified UUT in the interval specified by 

the starting period and ending period. The search results are summarized by the total test 

runs, total failed runs and total failures counts. A summary for the first run, if found, is 

displayed in the right side of the 'Test Runs' box. 

• Choosing the Run By typing in a 'Run Number', or using the adjacent up and down 

arrows, you can select a specific test of a UUT. This is only applicable if the UUT has 

been tested more than once during the selected reporting period. If a run is displayed, its 

summary includes its pass/fail status, test date and time, its failure count, the test system 

ID, the operator ID, and the name of the test program used to test it. 

• Edit allows you to examine and modify failing test steps by bringing up the Edit Run 

Failures screen shown in Edit Run Failures below. 

• Save allows you to save any changes made to the current search results. 

• Exit allows you to leave the Examine SPC Data screen. 


This screen displays up to 10 existing failed test steps and allows you to delete or modify these 

steps. It shows the measured value, step number and component description for displayed 

steps. You can also add additional failure codes to the failed run. 

8-15





• Clicking on a Step allows you to select one of any of the failed test steps displayed. For 

summary-only recording of failed runs, no failing steps are found in the SPC log. 

• [F1]-[F7] allows you to replace the measured value of the selected step failure with a 

failure type. This allows you to replace existing failure steps with a failure type. A failure 

type is selected by pressing one of the [F1] through [F7] buttons. You can select 'Undo' to 

clear the step entry from being replaced by a failure type. A step component description is 

modified when the edit results are saved only if the step is also replaced with a fail code. 

– [F1] assigns a "Missing" failure code to the test step. 

– [F2] assigns a "Wrong" failure code to the test step. 

– [F3] assigns a "Backwards" failure code to the test step. 

– [F4] assigns a "Short" failure code to the test step. 

– [F5] assigns an "Open" failure code to the test step. 

– [F6] assigns a "Faulty" failure code to the test step. 

– [F7] assigns an "Other" failure code to the test step. 

– Undo restores the current step to its initial value. 

• Delete allows you to delete a step failure or undelete a failure selected for deletion. 

Deletions are not final until the edit changes are saved, but are marked on the screen so 

you know what will be deleted after you exit. Pressing delete again toggles the step to not 

be deleted. 

• Add Failures allows you to add an additional SPC step to the log. This step allows the 

same [F1] through [F7] choices to enter the failure reason. 

• Exit allows you to return to the Examine SPC Data screen. 

8-16



Reporting on Panelized PCBs 

If you modify a step (Change Failure Code or Delete), you will see an indication that the data 

has been modified. 

Reporting on Panelized PCBs 

Panelization adds additional information to the test results log file. The Panel number and 

method of counting PCBs for statistical analysis are recorded in test log for each test 

execution. Test Steps for PCB 0 are not recorded in the test log for panelized tests and thus 

aren't available in X-Bar/Sigma Reporting. 

Individual PCBs on a panel may either be counted as duplicates of a single UUT, as parts of 

one-panel UUT, or each as a separate unique UUT. Test steps with the same test title and test 

limits on a panelized board with PCBs counted as duplicates are grouped together for X- 

Bar/Sigma analysis. If all panels analyzed have the same number of PCBs per panel or the 

same method for counting results from each PCB, then the corresponding value is displayed in 

the report header. 

For Pareto reports, the PCB number is included in the description if the PCBs are not counted 

as duplicates of one UUT and summary record information is in the results log. When PCBs 

are counted as duplicates on a panel then neither the step number or PCB number of the test 

are displayed. Failing steps with the same test title are lumped together for error counting if 

they are not part of a panelized test counting PCBs separately or if they are in the same PCB 

block number. 

SPC Data Format 

In the case of passed or failed logged data, the outcomes of tests are logged. Since the amount 

of data being generated can get large, it is recommended that passed data only be logged if you 

are planning to obtain an X-Bar/Sigma Report or are testing a relatively small number of 

UUTs. 

The results are stored in a format that can be read and processed by a spreadsheet such as 

Lotus 1-2-3 or Microsoft Excel. The data is ready to be read in as numeric data for failure 

analysis. For example, in Lotus, the sequence '/fin' can be used to import the data. Since the 

data is stored in ASCII, you can also edit it with most standard editors and word processors. 

A new file is created each calendar day. The name of the file is `YYYYMMDD.DAT' where 

YYYY is the year, MM is the month, and DD is the day of the month. For example, on 

December 1, 2010 the file is named '20101201.DAT'. 

Each entry contains the following information: 

1. The test program name. 

2. The time of day, in 24-hour format, that the test was completed. For example, if the test 

was completed at 1:10 P.M., the entry might be "13:10:46". All entries for a single test 

have the same time logged. If data logging is done in a RPRTS step in a test program (see 

RPRTS Print Test Results on page 14-49), then the elapsed time is not available and a time 

8-17


SPC Data Format 


of 0 is logged. Logging both in a test program step and by automatic logging is not 

recommended. 

3. The number of failures. If this number is zero, the test passed. 

4. The step number (as listed in the Edit screen). If the step number is zero, this is a 

summary record only and only describes a test as passed or failed. The test has failed if 

item 3 is not zero. 

5. Test execution time in seconds. 

6. UUT Serial Number enclosed in double parenthesis. 

7. Test Program revision number. 

8. PCB counting method, enclosed in double parenthesis if program uses panelization, "" 

otherwise. 

9. Name of main program if this is a subprogram called via RunT, "" otherwise. 

10. Batch string enclosed in double parenthesis. 

11. Operator name enclosed in double parenthesis. 

12. System ID string enclosed in double parenthesis. 

The following fields will only be present if the record is used to report a passed or failed test 

step result. This only occurs if the logging for detailed data (e.g., `summary + passes + fails'). 

For these steps, the test step number will also be non-zero so that you can differentiate between 

summary records and step-result records. 

1. The test type (e.g., MISP) 

2. The measured value (e.g., 1). If the USB connection was not working, the measured value 

will show Fail. A measurement unit may follow Fail, such as FailV has the value Fail and 

unit of V, for Volts. 

3. The test title (e.g., U101) 

4. The low test limit (e.g., 0) 

5. The high test limit (e.g., 0) 

6. The last field, presently the sixth field, is reserved to hold the test title. 

An example statistics file is shown in Sample Reports on page 15-1. 

8-18

Chapter 9 

Test Programs 

Writing Programs 

Overview 

The system must be programmed for each type of assembly (DUT/UUT) that you will be 

testing. The system provides a program editor that is easy to use for generating new test 

programs or modifying existing ones. 

A system such as the CheckSum MultiWriter pps is sophisticated enough to handle a wide 

variety of testing needs. As such, it has many advanced features and tools available to the user 

- many of which may never be used in most installations. 

• This topic covers most of the common operations and concepts used for programming. 

– Background on page 9-2 

– Manual Entry on page 9-2 

– Setting the Execution Order on page 9-3 

– Editing Tools Testing Methods on page 9-3 

– Special Features on page 9-3 

– Statistical Data (SPC) Logging on page 9-3 

– Optimize for Best Results (minimize test time with maximum test coverage) on page 

9-4 

– Save Program on page 9-4 

• For information about how to program specific steps for testing components on your UUT, 

see Entering Test Steps on page 10-1. 

• For complete details of what each test step in the programming language can do, refer to 

Test Type Descriptions on page 14-1. 

To help you use the system, the description of test programming is broken into sections: 

• The Background on page 9-2 section gives an overview of how to enter and program tests 

for a UUT. It describes the capabilities and tools used for most programming.

Test Programs 



• The Edit Window on page 9-4 describes the various top-level windows available in the 

system. This description includes some, more esoteric capabilities of the system, and can 

be used as reference material. 

• Loading a Program or Erasing Memory on page 9-23 describes how to get started writing 

a program. 

• Assigning Point Names on page 9-24 describes how to assign names to the test points for 

your test program. 


• Entering Programming Steps on page 10-1 describes how to enter test steps into your test 

program. 

• Printout Program Steps on page 9-26 describes how to get a print-out of your test 

program. 

• Saving Programs on page 9-26 describes how to save your completed program on disk. 

Toolbar Buttons and Shortcut Keys 

In the pull-down menus, shortcut key sequences are often available. These 

shortcut key sequences are shown in the menus next to the command. Also, 

in many windows, toolbar buttons are available at the top of the window. 

The toolbar buttons can be used as substitutes for frequently used menu 

items. By moving the mouse pointer over the toolbar button, then pausing, 

a 'hint' will appear that describes what the toolbar button does. 

Background 

• Programming an assembly is the process of entering testing instruction information about 

the assembly into the system so that it can be tested. The system provides the capability 

for this information to be entered in several ways. 

If you are testing a panelized PCB, you will enter and debug the program for the first PCBs on 

the panel, then use the automated tools included with the system to step-and-repeat the 

program for the other PCBs on the panel. 

Manual Entry 

You can manually generate the test data as shown in the following steps: 

• First annotate the DUT schematic with the node (test point) numbers. This done by 

placing sequential numbers on the schematic, one for each electrical network (e.g., 

Ground, VCC, DATA0). 

• Next, enter the node names into the system. Using the Edit Test Program Setup > Fixture 

Test Points window, you can assign names up to 255 characters in length. Different 

conventions can be used. Some facilities use physical locations (e.g., J1-1, U2-4, C1-2) 

and others use signal names (e.g., GND, VCC, DATA0), and others use a combination of 

these names (e.g., use signal names when available, and physical locations otherwise). In 

most displays, you are able to directly see up to about 32 characters of each point name. 

Beyond that, you may need to scroll to see more characters. 

9-2


Test Programs 


• Once the node names are entered, you can generate a wiring report to give to the fixturing 

facility to use when wiring the fixture. This report gives the test point numbers, the 

connector/interface block to wire to, and the name of the signal or pin. An example of this 

report is shown in Sample Reports on page 15-1. With use of the configuration windows 

you can tell the software which type of fixture system that you are using so that the reports 

will generate the proper interface pin-out in the wiring report. 

• Next, enter the test program using The Edit Test Window on page 9-4. You first insert the 

tests for each individual component on the UUT. For each component: 

– Insert a new line in the test program using the Insert key, 

– Enter the type of test (e.g., MISP, DCV, etc) in the 'Test Type' column, 

– Enter the two test point numbers or names connected to the component in the 'From 

Point' and 'To Point' columns, 

– Enter the component designator (e.g., U33) in the 'Test Title' column, 

– Enter the nominal value in the 'nominal' column. 

It can be helpful to use a highlighter to mark each component on the schematic as it is 

entered. If you enter the test program before you release the fixture for wiring, it can save 

errors since you might discover probe locations missed in the first pass. 

• Next, use the Set Initial Limits and Range (in the Measure menu pull-down) to assign 

tolerances and default measurement ranges for all of the entries. 

Setting the Execution Order 

When the program is entered or generated for all of the component values, you will probably 

want to put it into the execution order that you want. 

Editing Tools & Testing Methods 

There are a number of tools available from The Edit Test Window on page 9-4 to help you 

debug the program. Once you are familiar with the system, you will probably find it the most 

efficient to go through the following steps for each component test: 

• Select Step Analysis from the Measure pull-down (or use the toolbar button equivalent) to 

obtain the Measurement Analysis window. In this window, you can move the cursor to 

different fields and enter/edit the entry. 

Special Features 

You can program special features into the test program. For example, you can provide for 

operator adjustments and displays in the program. The available test step types provide the 

necessary flexibility in writing test programs to perform almost any task. 

To instruct the operator how to installing the DUT, you can generate an operator window of 

instructions using the Operator Setup Entry Window. This is displayed on the first execution 

of the test program after it is loaded, but not between subsequent UUTs. 

Statistical Data (SPC) Logging 

At this point you should turn on statistical process control logging, and run a sampling of 

UUTs through the system. Then, you can generate an X-Bar/Sigma Report. This report shows 

how well centered the measurements are between the high and low test limits and how much 

variation there is from reading to reading. From analyzing the X-Bar/Sigma Report, you will 

9-3

Test Programs 

Edit Test Program Window 


probably want to go back and fine-tune some of the measurement methods to reduce the 

reading variations, and if you cannot do so, change some of the test tolerances so that test steps 

won't fail for good UUTs. Statistical Analysis on page 8-1 discusses how to use the SPC 

facilities of the system. 

Optimize for Best Results 

Optimizing the test program insures the test time is minimized and the test coverage is 

maximized. Sometimes there are trade-offs between test coverage and test time. When 

writing the test program, you have several tools to help you minimize the test time and verify 

the test coverage. The test step measurement analysis statistics on page 10-4, tools menu 

Cross Checks on page 9-21, and the SPC analysis X-Bar/Sigma Report on page 8-11 will help 

you verify the test coverage. 

To minimize the test time, you should review the following suggestions: 

Remove or minimize the Pause time steps. 

Use the test program editor tool menu Sort for Best Speed on page 9-21. 

Finally, don't overlook the flow of boards in and out of the test system area. Often times, 

changes in this flow can make significant impact in test system utilization. 

Save Program 

When an assembly is programmed (or 'learned'), the system provides the capability of saving 

this information on the system's disk for future use. Virtually all of the information established 

with the 'Edit Test' selection from the system menu is saved with the test program. 

At this point, the program is ready to use as described in Executing the Test on page 7-4. 


• The Edit Test Window below 

• Loading a Program or Erasing Memory on page 9-23 

• Assigning Point Names on page 9-24 

• Entering Test Steps on page 9-26 

• Listing Test Program Data on page 9-26 

• Saving Test Programs on page 9-26 


The Edit Test Program Window is the center of test program generation facilities. It is 

accessed by pressing [F2] or selecting the 'Edit Test' button in the center of the window of the 

Main System window. The Edit Test window is shown in the following figure. 

The overview section in Writing Test Programs on page 9-1 describes the general procedure 

for writing a test program. This section, a general reference section, describes what each of the 

menus and menu-items in the Edit Test window is used. The next section, Entering Test Steps, 

describes the details of entering individual test steps. 

9-4


Test Programs 



Note 

The system provides the capability to use a password to prevent 

unauthorized modification of test programs. If password protection is 

enabled (via the Configure System > Environment > Manage User 

Accounts menu), you may be required to log-in prior to having access to the 

Edit window. 

Menu Descriptions 

• File Menu on page 9-6 

• Edit Menu on page 9-7 

• View Menu on page 9-10 

• Measure Menu on page 9-12 

• Setup Menu on page 9-13 

• Tools Menu on page 9-21 

• Help Menu on page 9-23 

9-5

Test Programs 

Edit File Menu 


Edit File Menu 

Edit Test Program, File Menu 

• New provides a selection of templates and sample program sequences to begin writing a 

new test sequence. Once a template or sample program is selected, the present program in 

memory will be closed. A dialog box allows you to save your current program or cancel 

the new selection. 

• Open solicits a test program file name, then reads the test program data from the specified 

file into memory. After it is open, it can be edited and/or executed. If the test program 

was saved in ASCII format, use the Open dialog box and select the 'Type: ASCII (*.asc)' 

to select and open the file. The test system will be reset (initialized to a known state) when 

the test program is opened (Reset System check box is selected). If you which to override 

this system reset, deselect the check box. 

• Append solicits a test program file name (saved as file type ASCII, .asc), then reads it into 

memory, appending to the end of the existing test program. Append can be used to merge 

two test programs together. Test point names are also merged together. The test point 

names of the test program that is appended are used if the two test programs both specify 

the same test point. See the "Note (Copying Test Steps from one program to another)" in 

the following section for another method of appending just the test steps. 

• Save writes the test program data in memory to the specified file. 

• Save As opens a dialog box to allow the file destination and file name to be changed 

before it is written. The dialog box has a 'Save File as Type:' field to allow the program to 

be saved in standard binary format (Test Program) or in ASCII format on page 15-3. The 

ASCII format is useful for appending two programs or editing the test program with 

another application. For use with the CheckSum software, save the program as 'Type: 

Test Program'. 

9-6


Test Programs 

Edit Menu 

• Print allows you to obtain a printout or listing of the test program on page 15-2 that you 

have entered or edited. You can either send it to a printer, or to a file on the disk in ASCII 

format (it will look just like the printer output, but instead sent to a file). 

• Run allows you to run the test program in memory. This selection invokes the 'Test 

Window'. This is a handy way to test your program during editing. 

• Set Recently Used Files List Capacity allows you limit the list of recently used files that 

are shown. 

• Exit leaves the editor and returns to the Main System window. 

Edit Menu 

Edit Test Program, Edit Menu 

9-7

Test Programs 

Edit Menu 


Note (Fields and Lines) 

Cut and paste functions operate on the selected data in your test program. 

Depending on whether you have selected a field (entry on a line) or line 

(test step), the options in the Edit Menu will change to reflect what is 

currently selected. To select a field, click on it and it turns to a dark 

background. To select an entire test step, click on the box on the left of the 

edit window and the entire line turns yellow. You can select multiple lines 

in the program by clicking on the left box of the first and last lines, or by 

dragging over the boxes on the left. To deselect lines, click again on any 

field. 

The contents of a field (individual cell) can be edited. If you need to edit a 

field (the Test Title, for example), position the mouse pointer on the field 

and double-click the mouse or press the Enter key. The edit cursor will 

appear at the end of the entry in the field. Use the arrow keys or the mouse 

to move the edit cursor. If you right-arrow at the far-right side of the field 

or left-arrow at the far-left side of the field, the next cell is selected. To 

replace the contents, single click the mouse to select the field (blue 

highlight appears) and type in the new entry. If you start to replace the 

contents of a field and change your mind, press the Escape key once. The 

original contents will return. 

Many of the frequently used commands are available as toolbar buttons on the Toolbar as well 

as in the different menus. 

• Insert (Insert key) allows you to enter a new test step just below the test step currently 

selected. 

• Insert Before (Ctrl+Insert) allows you to enter a new test step just above the test step 

currently selected. 

• Delete (Ctrl+D) allows you to delete the test step that is currently selected. To delete test 

steps, highlight the steps and use the Edit > Delete. A dialog box will prompt you for 

confirmation. If a field is selected, you will not be prompted for confirmation and the test 

step will be immediately deleted. 

• Clear All (Alt+D) deletes all of the present test program steps. 

• Cut Field/Test Step allows you to copy the selected data so that it can be placed 

elsewhere. If a field is selected, cut (Ctrl+X) simply copies it into a buffer (the cut field 

remains unchanged). If a test step is selected, cut copies the test step into a buffer, then 

deletes the selected test step. 

Select (yellow highlight) the test steps you wish to move and use the Edit > Cut Test Step 

feature. To insert the cut test steps below a test step, highlight any field on that test step 

and use the Edit > Paste Test Step. The toolbar has buttons for these features also. 

• Copy Field/Test Step allows you to copy the selected data so that it can be pasted 

elsewhere. If a field is selected, copy simply copies it into a buffer. If a test step is 

selected, copy copies the test step into a buffer. 

Fields (individual cells) can be copied and pasted to single or multiple fields. Position the 

mouse on a field and click to select the field (the selected field is highlighted in blue). Use 

Edit > Copy Field menu feature to copy the field (or press Ctrl+C). If you select another 

9-8


Test Programs 

Edit Menu 

field, you can paste the copy contents into this field. If you select multiple fields (click 

and drag the mouse), you can paste the copy contents to all the selected fields (Edit > 

Paste Field or Ctrl+V). 

Entire lines (test steps) of a program can be copied and pasted into the program. Position 

the mouse on the far left gray box and click to select the test step. The test step will be 

highlighted in yellow. If you click and drag the mouse, you will select multiple test steps. 

If you hold the keyboard Alt-key down, each press of the up-arrow or down-arrow will 

select a test step. Use Edit > Copy Test Step or the toolbar button to copy the test steps. If 

you select another test step, you can paste the copied test steps in place of this test step. If 

you select multiple test steps (click and drag the mouse), you will replace all of the 

selected test steps with the copied test steps (Edit > Paste Test Step). Note: If you select a 

single field (blue highlighted field) on a test step, the Edit > Paste Test Step feature will 

insert the copied test steps below the test step with the blue highlight. The selected test 

step will be unaltered and located above the inserted steps. 

Note (Copying Test Steps from one program to another) 

The test step lines that are copied are saved when opening test programs. You can use 

this feature to copy test steps from one test program, open and then paste to another. 

• Paste Field (Ctrl+V) allows you to copy the data from the buffer (stored with a cut or 

copy operation), into the selected field. 

• Paste Test Steps (Shift+Ctrl+V) allows you to insert the test steps saved in the buffer 

(stored with a cut or copy operation) to the lines just after the selected lines. 

• Mark Begin Block (Ctrl+B) selects the beginning step for a block command such as 

measure selected steps, sort by test title, or copy/cut selected steps. 

• Mark End Block (Ctrl+E) selects the last step for a block command such as measure 

selected steps, sort by test title, or copy/cut selected steps. 

• Re-Mark Block (Ctrl+Q) selects the steps previously selected by the Mark Begin and 

Mark End Block commands. The steps are highlighted. 

• Goto Step (Ctrl+G) allows you to enter a step number. The system then adjusts the 

window for you to see it then selects the test-type field on the selected line. 

• Goto Next Error (Ctrl+N) allows you to jump to the next step that failed (the test program 

must be run first). The system then adjusts the window for you to see it then selects the 

test-type field on the selected line. 

• Find (Shift+Ctrl+F) allows you to enter a string of information, then search through the 

test titles in the test program to find a matching string. You can either specify that the 

search is case sensitive (upper and lower cases must match), or not case sensitive. This 

can be used, for example, if you want to find the test step for a particular component, such 

as R101. Find starts at the beginning of the test program. 

• Find Next (Ctrl+F) allows you to search for the next occurrence in the test program of the 

string last entered in the Find menu. 

9-9

Test Programs 

View Menu 


• Point Name Entry allows you to specify how the point name columns are used in The 

Edit Test Window on page 9-4. If Point Name Search is turned on (checked), when you 

enter a name in the point name column, the system searches the existing test file for the 

point name that has been entered, then substitutes the appropriate point number. If Point 

Name Overwrite (Ctrl+O) is turned on (checked), when you enter a name in the point 

name column, the system assigns the entered name for the point number that is entered for 

this point. In this mode, you can enter the point names directly from the edit window. 

View Menu 

Edit Test Program, View Menu 

• Expand provides detailed information about the selected test type. Available for many of 

the analog test types, the expanded view tells you more information about how the 

measurement is made. For example, it includes the measurement type, amplitude range, 

guard points, external sensing points, and so on. Much of this information can also be seen 

in the Measurement Analysis window. 

• Program CheckList shows the basic setup for the programming sequence. The setups are 

numbered in column 1. The Skip column indicates if the setup is available (or N/A, not 

available) and if this setup is skipped ( double-click to toggle skip on/off or press F9). 

The Entry column indicates if the setup is used ( )in this program sequence. The 

Action column shows the setup action. The last column shows an icon, double-click the 

icon to view or modify the selection setting. 

9-10


Test Programs 

View Menu 

The CheckList is the only program editing tool when you have logged in with Limited 

Modify privilege on page 5-19. 

The CheckList is intended as a tool for setup and modification of simple test programs. 

It is not intended for use in viewing programs generated with the normal Edit Screen. It 

is not intended for use in viewing CheckSum test programs written for other platforms 

such as Analyst ems. 

As in the full feature Edit window, you can insert, delete, modify and skip test steps. 

The Program CheckList groups one or more test steps into the categories called 

“actions”. The delete and skip functions apply to all test steps that make up that action. 

The Operator Instructions, Program Start Option and UUT Panelization are settings 

stored in a test program but not as test steps. The other actions are stored in a program as 

one, or more test steps. 

The Fixture Engage/Disengage actions on the CheckList assume use of the default 

control of pneumatics with the FixCt on page 14-45 test type. For manual closure of 

UUTs to compress the probes in a fixture, these actions are not needed. 

The PS-UUT Power On/Off actions are for control of a programmable voltage power 

source. The system also comes with built-in fixed voltage sources (+24Vdc SW, 

+12Vdc SW, and +5Vdc SW) that can be used for low power UUT programming. The 

fixed sources are used without any CheckList actions. 

9-11

Test Programs 

Measure Menu 


Board Marking is setup to mark passing UUTs. You have the option of control of one 

marker probe for a UUT/panel or for panelized assemblies, the option of one marker per 

PCB. See wiring details on the wiring convention assumed by this automatic setup. 

• Show Unedited Field Values allows you to specify how the fields are shown in The Edit 

Test Window on page 9-4. In the default mode, Unedited Field Values > All disabled (not 

checked), the system displays a bullet in each field of the test program that you have not 

entered or assigned, other than the Test Type column which is always displayed. In this 

mode, you can easily see which fields need to be filled in to complete the test program. If 

Unedited Field Values has All checked, the system shows a value in every applicable field, 

whether you have entered it or not. This will show default values that are entered when 

you insert a test step. You can use the Unedited Field Values > Selected menu to toggle 

the selected fields between bullets (if unedited) or the display of the default values. 

• Default Grid allows you to return the 'Edit' window to its default column width and 

spacing. The width of a column can be changed by clicking on the right-side edge of the 

title column and dragging the column edge. 

• Font Size allows you to select the font that is used in The Edit Test Window on page 9-4 

for the test program entries. The default (10-point) works well with most displays. 

Measure Menu 

Edit Test Program, Measure Menu 

• Make Measurement executes the selected step and displays the result in the Measured 

column. If you have selected more than one test step, all selected steps are executed. 

Steps in the selected range that are executed are all normal measurement steps, exclusive 

of transfer of control, display, and operator I/O. 

The Run Test toolbar button can be used to run all of the test steps. It will close the 

edit window, open the programming window and let you run the test in the normal test 

window. When running a test starting from the edit window, you (as a 'programmer') will 

have full access to all of the test window menus and selections. For example, you will be 

able to set/clear the Test menu 'Single Step' and 'Halt on Fail' flags. These flags are saved 

with the test program. Several test operation control features, such as the Environment 

9-12


Test Programs 

Setup Menu 

menu, are not available to an operator or when you run the test from the main system 

window. When you exit the test window, it returns to the edit window. 

• Make Measurement (Hold off Reset) executes the selected test step as described in the 

previous section however the module is not reset before the measurement is made. This 

special measurement is used for advanced test step debug. 

• Step Analysis is available for most measurement types. It allows you to fine-tune the 

measurement by selecting ranges and measurement types, add guarding, offsets, and 

measurement delays. When you select Step Analysis, the window displayed will vary with 

the test type. Each type is discussed in more detail under Test Type Descriptions on page 

14-1. 

• Skip Test Step allows you to toggle the selected test step (or test steps if you have selected 

a range) between skipped and unskipped. If a test step is skipped, it is not executed nor 

reported on. The skipped test steps are marked with a character in the left column of the 

step. If the test program is saved with any skipped steps, the steps are skipped when the 

program is run. Select the first and last steps to select all steps, then use the "Skip/UnSkip 

Test Step" to remove all of the skip test steps. One use of skipped tests is to speed up test 

debug by temporarily skipping tests that have already been debugged. 

• Set Initial Limits and Range assigns the high and low limits based on the nominal value. 

The assignments are based on the 'Default Limit Setup'. This selection also assigns the 

initial measurement type and range to be appropriate for the anticipated measurement. 

• Set Limits from Nominal Value assigns the high and low limits based on the nominal 

value. The assignments are based on the 'Default Limit Setup'. 

• Set Limits from Measured Value assigns the high and low limits based on the last 

measured value. The assignments are based on the 'Default Limit Setup'. 

Setup Menu 

9-13

Test Programs 

Setup Menu 


Edit Test Program, Setup Menu 

• Fixture Test Points allows you to enter point names into the test program. Point names 

are used for reporting purposes and can be used to make the test reports more meaningful 

to the user. In the normal case, you can type in the name of each point, or assign names by 

using the probe in the system. 

There are six (6) columns shown with information regarding each test point. The first 

column does not have a title. This first column indicates if the test point is an active or 

inactive test point. The second column shows the system test point number. The third 

column shows the assigned name for this test point. The fourth column indicates if the test 

fixture has a spring-probe in this. The fifth column shows the location. The sixth column 

shows the PCB number for this test point. 

The Edit menu item 'Use Probe Presence' entry allows the test program to skip any test 

fixtures that do not have a spring-probe in the location. Only test points that are indicated 

in the Probe column will be included in the learn process and the test if the Edit menu item 

'Use Probe Presence' is checked. 

The Edit menu item 'Use PCB Number' entry allows the test program to intelligently test 

fixtures with multiple UUTs that have overlapping test point numbers. Only test points 

that are specified for a PCB will be included in the learn process and the test when that 

PCB is tested if the Edit menu item 'Use PCB Number' is checked. 

The Fixture Test Points window also allows you to go to a point (type in the point number 

and it is selected in the window), find duplicate names that have been assigned, and 

display naming statistics. Statistics include first and last named point name and number, 

and the number of points that have been named. 

The File menu selection 'Print…' is used to print the Wire Run Report directly to a printer 

or a file. To make it easy to review system wiring, the report lists the test system 

connections in two columns. One column shows the connections sorted by test point 

numbers. The other column shows the connections sorted by the name assigned to the 

connection (for example, +5V). See Wire Run Report on page 15-7 for an example. 

9-14


Test Programs 

Setup Menu 

9-15

Test Programs 

Setup Menu 


Fixture Test Points window 

• Display Messages allows you to enter text strings that are presented to the operator during 

the test program with the display test types (see DISP, DISPL, DISPE and SCRN test 

types). Operator messages can also be used to provide information for the RS232, and 

GPIB test types. The first column lists the message number. The next two columns are 

used to enter the column and row of the message area on the window that the message will 

be displayed on. Finally, the message (Display Line) is entered. You can have up to 999 

messages in each .SPEC file format test program. For more details see Display Messages 

on page 10-5. 

9-16


Test Programs 

Setup Menu 

Display Messages Window 

• Variables List is used to open the memory variables list window. The use of the memory 

variables is described in the program memory variables section on page 10-39. The 

variables list window displays the variable list and allows you to add, rename, 

import/export, or delete a variable. 

9-17

Test Programs 

Setup Menu 


Variables List Setup 

In the variables list window, you can: 

View the Named Variables that are currently defined, both used (by at least one test step) 

and unused (by no test steps) 

Add a new variable and specify the memory type 

Delete a Variable: If the variable is being used in the test program, you will be notified and 

asked whether you still want to delete the variable. If so, then the variable is removed, and 

all Mem steps that use the variable will be set to use the original Mem variable. Additional 

feature: Delete all unused variables. 

Rename a Variable: If you try to rename a variable to another existing name, the rename 

will be refused and you will be notified and given an explanation. If the rename is 

successful then all Mem steps that use the variable will display the new variable name. 

If a variable is defined but not used (Used column entry will show No) in the program, you 

can change the type by mouse clicking on the type field. If the variable is used in the test 

program, first delete the variable from the list and then add the variable with the desired 

type. 

The Options menu (or mouse right-click on a variable name) provides selections to make 

changes to each variable. The list can be sorted by the options Sort selection or by 

clicking on the column title: Name, Type, Batch Persistent, or Used. The variables 

(Integer and Real) are reset to zero or cleared (string) at the beginning of each Batch. The 

variables will be reset to zero or cleared at the beginning of each Test in a Batch, unless 

the Batch Persistent setting is Yes. Setting Batch Persistent to Yes, allows the variable to 

be unchanged between tests. 

9-18


Test Programs 

Setup Menu 

Select a variable: When the list is displayed from the Mem Setup window, you can select 

the variable with a mouse click. 

Viewing features: 

View the variables: by name, type, and used/unused 

Sort the list based on the name, type, and used/unused 

Filter the list based on the type – only variables of the types checked will be displayed. 

For example, you can select to view only the variables of type integer, both integer and 

real, etc. 

Note: If you use a set of variables over and over again in different test programs, use the 

Export and Import features to transfer the variables between test programs: 

Import Variable lists from a file – text format, they are added to the existing list 

Export Variable lists to a file – text format 

To examine the values of the memory variables, use the editor menu item Tools > 

Show BreakPoint Information. To see the individual array values in the BreakPoint 

dialog box, double-click on the array name. Double click in the same box again to see the 

list of variable names and values. 

• Operator Instructions Setup allows you to enter a window of information that is 

displayed to the operator prior to starting each batch of UUTs. This window is typically 

used to provide one-time information such as how to install the test head, UUT orientation, 

and location of parts to be adjusted. 

Operator Instructions Setup 

9-19

Test Programs 

Setup Menu 


Generally, you use the mouse to move the cursor to where you would like to type in 

information, then start typing. If you wish to have line drawings, you can use the toolbar 

buttons to select single-line or double-line drawings. Once in a drawing mode, when you 

move the cursor around with the arrow-keys, a line will follow. Press the toolbar button 

again to come out of the drawing mode. If you wish to enter special characters, use the 

'Insert Symbol' menu-item in the 'Edit' menu to select the special characters. With these 

tools, you can make descriptive windows for the operator. 

The operator setup window is saved with the test program. You can also save it in a 

separate file with the 'File' menu's 'Save' selection. The default file extension is .CMT. 

Once it has been saved, you can merge it into another test program with the merge 

command. Since 'Merge' only adds the characters that are used, you can overlay several 

files. With these tools, you can build your own library of operator setup windows to help 

speed future test program development. If you use the unmerge command, every character 

that is in the .CMT file is erased in the displayed setup window. 

• Assembly Name is used to enter a name describing the UUT. It is included in the header 

of test reports from the system. Since it can be longer than the program name (it can be up 

to 32 characters), it can be used to describe the UUT more fully, including information 

such as revision information. 

• Measurement Messages allows you control how warning and error messages affect test 

execution. If enabled (checked) then the system will display and wait for the operator to 

acknowledge the warning or error message before proceeding. If disabled (not checked) 

then the system will only beep when these conditions occur and the system will 

automatically continue to the next test step. 

• Program Start selections control when the program starts. The keyboard function key 

signal F1 and the fixture ready (left and right) signals can be used. The operator action of 

closing the fixture lid can generate the fixture ready signal on page 6-17. 

• Program Auto Load is used to specify the Flash drive location and name of the program 

and a checkbox to enable/disable use of this option. When enabled and the Flash drive is 

detected, the system offers to load the specified program when in the Main, Test, or Edit 

windows. 

9-20


Test Programs 

Tools Menu 

Tools Menu 

Edit Test Program, Tools Menu 

• Perform Cross Checks can be used to find problems in the test program that may not be 

obvious. For example, it looks through the test program to find potential problems, such 

as possible attempts to use mutually exclusive sources simultaneously, use of DMM input 

for the UCT when the specified frequency is too high, possible fail on measurement 

overrange, and other similar sort of errors. For the overrange problem, it checks the 

measurement range against the high limit to insure that the system will not go into 

overrange before it can achieve the high limit. You may wish to do this in some cases, but 

may have accidentally ended up in this situation in other cases. 

• PCB Panelization is used with UUTs that consist of several UUTs that are combined on a 

single larger PCB. Once you have written and debugged the test program for the first 

UUT, you can have the system automatically step and repeat the program for the other 

identical PCBs on the panel (or pallet). Panelization also provides testing functions such 

as the ability to separate results by UUT in the panel, the ability to skip over some UUTs 

in the panel, and descriptive methods by which the operator can see which UUT is being 

tested, and relating the test results to a physical location on the panel 

For details, see Panelized Testing on page 10-33 and Panelization Programming by 

Wizard on page 10-36. 

• Show BreakPoint Information opens the BreakPoint Information dialog window: 

9-21

Test Programs 

Tools Menu 


The current values of the memory variables are displayed on the Variables page. 

Click the top tab to view the current system settings. 

• Fixture Toggle is used to engage a test fixture that is disengaged or disengage a test 

fixture that is engaged. The test program must have two FixCt steps (engage and 

disengage) to use this feature. The fixture toggle uses the same two ranges as the FixCt 

steps to toggle the test fixture. 

9-22


Test Programs 

Help Menu 

Help Menu 

Edit Test Program, Help Menu 

The Help menu can be used to obtain on-line help about the Test System: 

• Contents... allows you to search the table of contents for the help sections. 

• Topic Search... allows you to search the help data based on a topic that you enter. 

• Getting Started... helps you learn how to use the test system hardware and software. 

• About... shows information about the software that you are using. It provides the revision 

number, a number to call at CheckSum if you would like to talk to an engineer, and the 

most recent date that the system self-test has been run. 

Loading a Program or Erasing Memory 

The programming facilities of the CheckSum System are similar for editing an existing test 

program or generating a new one. If you are editing an existing program, you first load it by 

selecting 'Open' from the 'File' menu in The Edit Test Window on page 9-4, then selecting the 

proper test program file. If you want to erase the existing data and start with new data, select 

9-23

Test Programs 

Assigning Point Names 


'New' (or press Alt-D) from the 'File' menu of the Edit window. A dialog box will confirm if 

you want to erase the test program. 

The program that you are editing will stay in memory as you enter and debug it. Once you are 

satisfied, you can save it on disk. As in normal computer practice, you should also frequently 

save the file to prevent loss of your time in case the computer should halt or lose power, in 

which case all the information in the computer memory is lost. To save the program, use the 

'Save' option in the 'File' menu or press the save toolbar button (disk icon). 


You will probably want to assign meaningful point names so that the reports from the system 

will be more useful. Points are sometimes referred to as pin names, test point names, or nails. 

The System allows you to enter a point name of up to 255 characters for each test point. In 

most windows, up to about 32 characters can be directly viewed. To assign point names, use 

the Fixture Test Points window (see the following figure). This window is accessed by 

selecting 'Fixture Test Points' from the 'Setup' menu in the Edit Test Program window. 

9-24


Test Programs 


9-25

Test Programs 

Entering Test Steps 


Fixture Test Points 

The Fixture Test Points window works much like a spreadsheet. Use the page up, page down, 

arrow keys, or the Goto Point menu-item, to move the highlighted, active area to the row to 

add or edit a point name. 

After you have entered a name and pressed Enter, the system automatically moves to the next 

position to make entry of a list faster. 

Probing 

You can use probing to locate a test point number. With this feature you do not need to know 

the specifics of how the UUT is connected to your test system. You may either use the probe 

that comes with CheckSum fixturing or your own probe. 

• Probe UUT Point sets the system into probe mode. 

• Exiting When you have completed entry of connection information, select the Green 

Door to move back to The Edit Test Screen on page 9-4. 


For details about what test types to use, and how to enter them, refer to Entering Test Steps on 

page 10-1. 

Listing Test Program Data 

You can obtain a printout of your completed test program for documentation purposes. To do 

so, from the 'File' menu of the 'Edit' Window, select 'Print'. An example test program listing is 

shown in Sample Reports on page 15-1. 

If you would like to print a report showing the fixture wiring, go the 'Fixture Test Points' 

window by selecting 'Fixture Test Points' from the 'Setup' menu of the 'Edit' window. Then 

from the 'File' menu, select 'Print'. An example wiring report is shown in Sample Reports on 

page 15-1. 

Saving Test Programs 

Saving/Loading Programs in Binary 

To save your test program to disk, select 'Save' from the 'File' menu of the 'Edit' Window or 

press the save toolbar button (disk icon). You should get in the habit of frequently saving your 

test program during the editing process. This prevents loss in the event of power-failure or if 

the system should malfunction. 

9-26


Test Programs 


The system is designed to normally save test programs in binary format. Binary files are 

compact, fast to load and execute. They also cannot be easily modified without use of the test 

system, which helps enhance test integrity. 

The file name extension can be either .SPEC or no extension. A file name with no extension is 

backward compatible with the previous 16-bit versions of Windows 98 software and DOS 

software. File names with the extension .SPEC will be associated with the 32-bit version of 

the CheckSum test system software. New test programs with the .SPEC file extension are not 

backward compatible with the 16-bit versions of Windows 98 software and DOS software. 

Test programs with the .SPEC file extension can have long (up to 255 characters) file names, 

long test titles, named memory variables, and the test program can contain up to 30,000 test 

steps. 

Saving/Loading Test Programs in ASCII 

As an alternate, the system allows you to write and read files in ASCII format. An example 

test program in ASCII format is shown in Sample Reports on page 15-1. 

To save a test program in ASCII, use the 'File' menu of the 'Edit' Window and select Save As. 

This opens a dialog box to allow the file name and destination to be changed before it is 

written. The dialog box also has a 'Save file as type:' field to allow the program to be saved in 

standard binary format (Test Program) or in ASCII format. Use of the .ASC file extension is a 

good choice since it will show in the menu when you want to read it back in (Open File). 

This allows you to generate an ASCII file, modify it off-line with an editor, then read it back 

in. Note that special attributes (such as failure delay and active test points) are not translated to 

and from ASCII. Also, using ASCII input, you can read from a file that has been created 

elsewhere. For example, you may wish to use a word processor or spreadsheet to describe an 

assembly. 

For normal use with the CheckSum software, save the program as 'Type: Test Program', 

which is the binary format. 

The text file can contain the assembly name, connections, point names, operator instructions, 

comments, and test step information for an assembly. 

In general, each of the sections is optional and may be placed in any order. However, the point 

names must be assigned prior to their use in the 'Test Steps' section of the file. 

The file typically has several sections, each of which is optional. Each section is prefaced by a 

keyword followed by a colon (:). Valid keywords are NAME:, PIN NAMES:, TEST STEPS:, 

DISPLAYS:, COM:, OPENS: and CONNECTIONS:. Keywords may be entered in either 

upper or lower case and must be the only thing on the line. 

After each keyword are one or more lines of data applying to the keyword. Valid data includes 

the following: 

Name: Followed by an assembly name with up to 32 characters. 

Pin Names: Followed by one or more lines each of which contains the test-point number, 

a comma, and the point name with up to 255 characters. 

Test Steps: Followed by one or more lines, each of which contains 'From' and 'To', type, 

range, title, low limit, high limit and nominal value, each separated by a comma delimiter. 

The 'From' and 'To' fields can either be a test point number or a point name preceded by a 

tilde (~). If a point name is used, it must have been previously defined in the 'Pin Names:' 

9-27

Test Programs 



section. Low and high limits are real numbers in volts, ohms or farads and can not include 

alphabetic modifiers such as 'u' or 'k.' 

Displays: Followed by one or more lines describing the displays used by the DISP and 

DISPE test types. Each line includes the display number, a comma, the row number, a 

comma, the column number, a comma, the display itself. 

Com: Followed on the same line by an operator instruction (comment). These are read in 

order and appended, line by line. As an alternate to 'Com:' you may use an asterisk ('*') at 

the beginning of each line. 

! An exclamation point is used to start a comment in the ASCII file. Everything after it on 

the line is ignored. 

Blank lines These lines are ignored. Blanks at the beginning or end of a line are ignored 

also. 

Note 

When reading ASCII files, the system uses commas to separate the input 

fields. Therefore, you should not use commas in test titles for the test steps 

since this will confuse the system during ASCII input. During ASCII 

output, the system converts any commas that it finds in the test titles to 

semi-colons. 

9-28

Chapter 10 



Overview 

The Edit window is used for entry and debugging of test programs. The Edit window is 

described in The Edit Test Window on page 9-4. 

This discussion covers the specifics of testing each component on the DUT. The Test Display 

on page 7-5 is used to enter and debug a wide variety of test-types that describe each 

measurement. This topic describes what test types to use and how to optimize test steps for 

most common types of parts. Additional reference information about each test type is included 

in Test Type Descriptions on page 14-1. 

Topics 

Toolbar Buttons and Shortcut Keys 

In the pull-down menus, shortcut key sequences are often available. These 

shortcut key sequences are shown in the menus next to the command. Also, 

in many windows, toolbar buttons are available at the top of the window. 

The toolbar buttons can be used as substitutes for frequently used menu 

items. By moving the mouse pointer over the toolbar button, then pausing, 

a 'hint' will appear that describes what the toolbar button does. 

• Using the Edit Window on page 10-2 

• Controlling the Fixture on page 10-3 

• Display Messages to the Operator on page 10-5 

• MultiWriter MISP Setup on page 10-7 

• Controlling Program Flow on page 10-24 

• Executing a User-Written Program on page 10-27 

• Automation Interface (COM) on page 10-28 

• Generating Reports from a Test Program on page 10-31 

• Panelized Testing on page 10-33


Using the Edit Window 


• Panelization Programming by Wizard on page 10-36 

• Manual Panelization Programming on page 10-37 

• Use of Program Memory Locations on page 10-39 


The Edit window (shown in the following figure) allows you to enter or edit the test steps that 

are performed when testing the UUT. Each line describes one test step. 

Edit Window 

Test Step Descriptions 

Each line in the Edit window shows a test step type and a test title that describes the 

component being tested. The test title can be used for the component designator (e.g., U332) 

and can contain other information (e.g., the part number). 

The other fields are dependent upon the test type. For most tests, the high and low limits are 

used to describe the limits for the test. The 'To (+)' and 'From (-)' test points describe the test 

points that are accessed for the measurement. The range shows the measurement range. The 

last two columns show the nominal (expected) measured value for the component, and the last 

column shows the measurement that was taken for the test step during the last test execution or 

when measure was selected. 

Refer to Test Type Descriptions on page 14-1 for the specifics of each test type and its 

corresponding information. 

10-2



Fixture Control 


You may individually alter each test step field by moving the brackets to the desired area, then 

typing the new value that you would like. The System works much like a spreadsheet. You 

can move to new lines by using the scroll bar, and from field to field with the four arrow keys 

or clicking on the selected field with the mouse. 

You can also use the mouse on the left column of boxes on the window. Clicking on a line 

selects it. It turns yellow when selected. Some operations can also be used with a range of test 

lines. For example, you can make measurements on a block of lines, or a single line. To select 

a block of lines, click on the left blocks of the first and last line, or grab the block on the first 

line and drag to the last line. 

You can also change the appearance of the Edit window if you wish. Refer to View Menu on 

page 9-10. 

Most numeric entries can be entered in scientific notation if desired. For example, 10Meg can 

be entered as 10000000 or 10000e3 or 10e6 or 1e7. Alternatively, you may enter most 

numbers with a letter such as: p for pico, n for nano, u for micro, m for milli, k for kilo, or M 

for mega. 

When you enter a point name, the System searches the point names that have already been 

assigned. When it finds a match, the System inserts the point number and point name that 

have been found. If a match is not found, the System gives an error message and returns the 

original point name. To be found, the entered point name must exactly match the assigned 

point name, including upper and lower case. 

An alternate way of entering programs is to assign the point names as you go. First, go into 

the point-naming (rather than search) mode. To do so, either select the 'Point Name Search' 

item from the 'Edit' menu to turn the check off, or enter [Ctrl+O]. In this mode, when you type 

in a point name, it assigns the point name that you enter for the test point number that is 

already present on the adjacent column. To use this mode, type in the test point number. If 

there is no name present for the new number (the name column is blank), move to the name 

column and type in the name. 

There are a number of advanced features available for manipulating the data in the Edit 

Window. These include cutting, pasting, and moving lines and fields of data. If you want to 

use these, refer to the description of the Edit Test Program Window on page 9-4, paying 

particular attention to the 'Edit' menu description. 


If the fixture uses manual operation to close the lid and compress the spring-probes, no fixture 

control is needed. 

Automated fixture systems require a digital input from the System to actuate the fixture at the 

beginning of the test and to release it at the end of the test. The digital input of the test fixture 

is connected at the fixture interface. 

At the beginning of the program, enter a FIXCT on page 14-45 test-type with a range value of 

1. This will cause the fixture to be actuated. 

10-3


Measurement Analysis 


You can also wire a Fixture Ready (fixture-down) switch into the test fixture. Use of a fixturedown 

switch is not necessary for most testing installations, but can be used to ensure the UUT 

is engaged or to slightly enhance loading speeds. 

Depending on the type of fixture system selected, see Fixture on page 5-23, the fixture controls 

for this step vary. 

The Fixture Safety Rule steps presented in the Title and Number pull-down list must proceed 

the FixCt step. The steps types can be MemS/MemI/MemL/MemR/MemD on page 14-25 

with Range 2 for Pass/Fail or Exec on page 14-23 without the To Pin bit mask of 1 set (enable 

Pass/Fail test results). 

At the end of the program, enter a FIXCT test-type with a range value of 0. This will cause the 

fixture to be released. If you do not use a FIXCT at the end of the program, the fixture will be 

released regardless. 

Measurement Analysis 

Overview 

Use the Edit Test Program window Measure > Step Analysis [F6] menu selection is used 

initially to setup and then modify settings that are not performing as expected. 

Selecting Step Analysis will open a unique window for each type of test step. 

10-4



Display Messages 


In some cases, may wish to display messages to the operator to advise of System status or to 

prompt the operator to perform some action. The CheckSum test system allows this capability 

through use of the DISP, DISPL, DISPE and WAITK test types. 

The DISPLay test type is the easiest to use. To enter a message for the operator, specify a test 

type of DISPL, a 'From (-)' test point value that shows the column number (1-78) to start the 

message on, a 'To (+)' test point value that shows the line number to write the message on (1- 

8), and the text of the message in the test title column. 

For example, if you would like to make a display that would show test progress, structure your 

test program with the following DISPL statements: 


For longer messages in the test title column, you can use the DISP test type. Rather than 

displaying the message from the test title (like the DISPL test type), the DISP test has a 

message number in the range column. In addition to allowing longer messages, the DISP test 

type is useful if you would like to display the same message from several places in your test 

program. 

When a DISP test type is selected in the Edit window, either select 'Step Analysis' from the 

'Measure' menu or select Display Messages...' from the 'Setup' menu to obtain the operator 

Display Messages window shown in the following figure: 

10-5




Display Messages Window 

The Display Messages window allows you to type in a row and column number and the text 

for each message. You can also edit a selected message (press Enter or double-click the on the 

line in the top part of the window). In the lower part of the window, the selected message is 

shown in the specified row and column location. The Center button can be used to quickly 

center the text in the row. If you click and hold the mouse pointer on a message in the lower 

window, you can drag the text to the desired row and column. A lined-box shows the message 

while moving. The small bullet located between the message number and the column entry 

can be selected (bullet color changes when selected) to show multiple lines in the lower 

window. The selected line in the top window is shown with blue characters in the lower 

window. 

Once you have entered or edited your messages, you can return to the Edit window by clicking 

on the OK button. You can have up to 999 different messages in a single, .spec file format, 

program. 

If you want to erase the display area of the testing display, use a test type of DISPE with a 

range of 0. If you wish to erase a single message, insert a range value corresponding to the 

DISP range of the message that you want to erase. Sometimes you might want to prompt the 

operator to perform an action, then wait until he presses a key before continuing. In this case, 

use the DISP or DISPL test types to display the message, then a WAITK (wait for key) test 

type with a range of 0. The WAITK test step will wait until any key on the controller is 

pressed, then continues on to the next test step. 

10-6



MultiWriter MISP 

You can also use other ways to get an operator's response: 

1. With the WAITK test type you can wait until a particular key has been pressed before 

proceeding. See the detailed description of the WAITK test type in Wait for a Key to Be 

Pressed on page 14-19 for more details about how to do this. 

2. Use two test points connected to a switch as an operator input. Use the SWCHR or 

JMPR/JMP/LABEL test types to wait for the switch change. 

3. Use a bar-code reader connected to a keyboard wedge and have the operator scan in the 

desired entry. Bar-code readers typically emulate the keyboard and any input that can be 

typed in can be scanned in. 

4. Use one of the digital I/O points available from the System in conjunction with the 

DIGI/JMP/LABEL test types to wait for the digital bit to change states. 

5. Use the MEMI, MEML, MEMR, MEMD, or MEMS test types with a range of 3 to wait 

for operator input, then save it in the corresponding memory location. You can then use it 

later for other purposes if desired. 

If you would like to have the System include the measured value from the last analog 

measurement step, you can include the text {MEAS} in the display string. This applies to both 

DISP and DISPL statements. At execution time, the System replaces the text {MEAS} with 

the most previous measured value. This can be used if you want to display information to the 

operator, such as in a custom measurement and adjustment loop. 

If you want more sophisticated messages that include colors and flashing information, you can 

use the SCRN test type on page 14-21. In addition to these functions, you can use the window 

test type to save the present contents of the operator display area (as filled with DISP, DISPL 

and SCRN test steps) to the disk. The SCRN test type can then be used to restore the display 

later from the disk file. If you have standard windows, you can generate them, save them to a 

file, then use the files as a library for future test programs. 

If you want to use operator-input for controlling program flow, see Controlling Program Flow 

on page 10-24. 


MultiWriter MISP Setup 

The setup for the MISP step requires several entries. The form is designed to group the setups 

for ease of entry. 

Some entries are optional and some are required. The minimum, required information for the 

MISP setup is: 

1. The device type or types 

2. The image file or files 

3. Number of Devices (UUTs), if more than one device 

4. The MultiWriter command/programming string 

10-7




Many of the other entries are recommended for documentation and program verification. 

Title, DUT Power Control and Reporting 

Step Title - Normally the component reference designator plus any other text to help 

document the test step. 

ISP32 Data Set # [entry] - This is an index number of the data set for the MISP step (sets the 

Range value). 

Next - Displays the next MISP data set entry containing setup information. 

The Pre/Post Test Options provide a method to setup the UUT power on and UUT power off 

when debugging. The power on and off routines must have a CALL subroutine on page 14-15 

step in the program sequence. First, click the Pre or Post checkbox to select a subroutine. 

Next, click the drop down list to select the appropriate Call subroutine label step. The Execute 

buttons can be pressed at anytime the item is enabled (box is checked). When the MISP step is 

executed in the editor (F3) or in the MISP Setup window, the checked routines are executed. 

When the MISP step is executed in the Test/Programming window, the routines are not called 

by these settings since the program sequence should be setup to power on and power off the 

DUT. 

You can enable the Pre/Post item (turn-on the checkbox), press the Execute button and then 

disable the item (turn-off the checkbox). Then single step execution will not change the power 

setting. 

10-8




Errors - Shows the number of errors after the step is executed (see the button labeled Run 

Device). 

Report Details - Selects the type of details to be reported in a Test Results Report; None, 

Summary, Pass + Fail, Fail or Pass. Normally, Pass + Fail is selected. 

Do not Set Pass/Fail - If checked, this test step will not report the results and will not set 

Pass/Fail status. Normally, this box is not checked. 

Device and Image Files Selection 

Click the Device drop down box to select the first device. A list of licensed devices will be 

shown. Click on the DUT device type such as the 25HP512. Next click the Insert Device 

button. This will enable any device specific options to modify the entries in the setup form. 

If a different device should have been selected, select it now and press the Apply Device 

button. The selected device will be shown on the Device Group line. 

10-9




Multiple devices can be inserted if required. After each device is inserted, a New Device 

button will appear on the right side of the Device Group list. 

Press the New Device button to add another device type to be programmed simultaneously 

with the other devices. 

Use the Delete Device button to remove any selection. 

You can insert up to 16 device groups but the maximum number also depends on number of 

UUTs per device group, see Programming Multiple Devices on page 6-2. To switch between 

devices, click the device group button on top. 

Some devices have only FLASH or only EEPROM. Some devices have both FLASH and 

EEPROM. The entries in the MISP setup change depending on the selected device. For 

example, the PIC16L877A has both FLASH and EEPROM memory that can be programmed: 

10-10




For the PIC16LF877A device, therefore separate tabs are available to setup the Common 

FLASH (Default) and the Common EEPROM. 

To select common image files to program this device, click the Common EEPROM (Default) 

or Common FLASH (Default) tab below. 

Click the Add button on right to insert a new image file entry. Each row will be used to 

specify a common device image file. 

Click the small square box in the Device Files column to open the file folder dialog and select 

the image file. If more than one image file is added, the control software will try to merge all 

the image files with the same memory type before programming. It is typical to program the 

common image file to all devices but it is optional when device specific image file(s) for each 

DUT are selected. 

10-11




Select the Device Image File Load Option 

Runtime (Default): The control software on page 16-3 will load the file for every execution 

from the specified path. 

Embedded: The contents of the file will be added to the fixture USB memory on page 6-21 

setup file. The control software will not load the file from the path. Instead, the embedded file 

will be used to program the device. The embedded file is stored in the test fixture memory. 

The embedded file is only modified when this setup is executed. A warning will be given if 

there are any changes between the specified file and the embedded file. Updating may be 

canceled at this point. 

AutoEmbedded: Same as Embedded except it will check the date code of the file and 

automatically update the test fixture memory file during each execution. 

Revision (Optional) 

You can specify the revision for a file and select a revision to be programmed. If no specific 

revision is selected, all revisions will be loaded and programmed. 

Multiple UUTs 

It is very common to have multiple DUTs/UUTs on multiple boards to be programmed. These 

devices normally have the same component name, such as U21. Before specifying the Number 

of UUTs, double click and enter the Device Name in the first Device Name cell. 

Now select the number of UUTs and press the Apply button. 

10-12




To add/remove UUTs, click the Number of UUTs drop down and click the Apply button on 

the right. Press the Add Row to increase the number of UUTs by one. If you select fewer 

UUTs, a warning will be shown prior to deleting rows. To delete the last row, click the Delete 

Row button. A minimum of one UUT per device group is required. To delete the entire device 

group, click Delete Device button. 

The various entries such as Port# and PCB# can be modified by double-clicking the cell and 

changing the entry. Double-click the Port#, Device Name, or PCB# column title box to 

change the displayed order from lowest-to-highest or highest-to-lowest. 

The Device Group Enable selection will toggle the enable for all of the device specific 

entries. The Enable check-box by each line allows individual selection for Enable/Disable. 

10-13




If any device specific files are needed, such as a separate serial number for each programmed 

device, select the device and click the small square box in the Device Specific Files column to 

open the file folder dialog and select the device specific image file. 

Diagnostics and Commands 

Finally, a MultiWriter command string must be inserted, for the complete list of commands see 

MultiWriter Command Line Options on page 16-3. 

10-14




Double click in the Command String cell to enter a MultiWriter command string. To execute 

the setup, press F3 or the Run Device button on right. If there is more than one device in the 

device group, the Run All Devices button will be available. An execution window will show 

the programming progress. You can disable the execution window in the Diagnostics/Options 

tab setup. This setup will write a temporary file (.xml format) to 

C:\CheckSum\MultiWriter\Temp when Run. 

The Diagnostics/Options settings are used to validate and debug the programming. 

If the Advanced Mode checkbox is checked, a Device Parameters tab will be shown next to 

the MultiWriter Setup tab selection. This advanced feature allows modification of critical 

programming settings, do not change any of these settings if you do not understand the 

consequences. 

10-15




10-16




Buffer Wiring 

MISP Buffer Wiring Window 

10-17




MISP Buffer Wiring Modify Options 

10-18




MISP Buffer Voltage Settings 

Buffer Connection section shows the in-fixture connections between the fixture interface and 

the ISP Buffer modules. Each buffer module Port/Pin connection (e.g., #1/J2-7) to the Fixture 

Interface Block/Pin (e.g., A-1:2) is identified. 

UUT Connection section shows the UUT Point Number (e.g., 11) and Name (e.g., Clk #1) that 

is connected to the buffer module Port/Pin (e.g., #1/J3-9) and Pin Name (e.g., CLK). These 

UUT connections are available externally at the test point spring-probe on the UUT/DUT. 

Modify . . . pops-up a selection to modify the selected field. The modifications are Delete 

Line, Delete Port, Insert Line, Insert Port, Insert Port Options, Insert Active Ports, Replicate 

PCB1, Sort Ports, specify the Buffer type, voltage settings, Show Probe Info plus Auto- 

Advance Probe Point. The selection Insert Active Ports adds buffer pin connections to the 

table for all ports on the Operations Details Devices list. Any ports already entered are not 

changed. The selection Replicate PCB 1 first inserts active ports and then examines the test 

point numbers you entered for ports on PCBs 1 and 2. If you entered test point numbers for all 

PCB 1 ports and at least one test point on a PCB 2 port then the system fills in the test points 

for the entire table. If you omit entries on some but not all PCB 1 ports, the system replicates 

test points for only those specified. 

Probe UUT Point pops-up a window to verify a specified point using the single-point probe 

on page 4-4. 

10-19




Voltage Settings Information When probing, if a power pin for the specified voltage source 

on the buffer does not measure within the stated tolerance (± margin) then it will fail the 

probing test. Since the expected voltage range for the high and low limits depend upon the 

UUT, the buffer module, and how the buffer is wired, the fixture designer must specify the 

voltages and tolerances (± margins). 

Self-Test runs diagnostics on the MW Fix IO board. This checks out the wiring of the module 

to the fixture interface, wiring within the fixture, and checks the health of this board. 

Self-test checks that the PIC on the MW FIX I/O board is responding, reads the board software 

and hardware revision, and more. Verifies the twisted pair signals at the end of the buffer 

chain to make sure there are no board-to-board or fixture-to-board wiring errors. This does not 

insure the wiring to the spring-probes is correct. Reads out the various voltage levels used to 

insure the MW FIX I/O module is generating proper levels and the power wiring is correct. 

This section will not cause a failure it will simply display the results. 

Then pass/fail information is displayed: 

MISP Self-Test Pass/Fail 

10-20




MISP Self-Test Results Report 

Check Table . . . verifies the information in the buffer wiring table. 

Control Buttons 

Reset Setup - Provides a fast method to clear all the test step entries to the default state. 

Import & Export . . . - Export is used to save the complete MISP test step in a file with the 

extension “.TXT”. The exported file can be imported to another test program MISP test step. 

The export and import method transfers all of the field entries for the MISP step. This is 

10-21




required since the standard edit functions of copy or cut, for the MISP test step, do not provide 

a corresponding paste function to transfer all of the field entries. 

OK - Closes the MISP test step window and saves any changes. 

System Files 

The system uses several files to operate and program devices: 

pps.exe 

$pps$.dat 

CheckSum test system software, file type is binary, normally located in c:\checksum 

MultiWriter pps system configuration, Configure System setup Save modifies, file type 

is binary, normally located in c:\checksum 

program_device.spec 

Typical device program sequence, customer creates and modifies the file using the 

CheckSum pps editor, file type is binary, normally located in c:\CheckSum\specfile 

program_device.asc 

Typical ASCII version of the program file, created with the "Save as ASCII" editor 

feature in the editor. Use for printing and Appending (import/export). 

operator.cmt 

device.hex 

device.s19 

device.bin 

device.raw 

Typical operator instructions setup, file type is binary, normally located in 

c:\CheckSum, see the Operator Instructions Setup in the editor Setup Menu on page 9- 

13 

sernum1.bin 

devices.xml 

Typical hex-format image file, customer creates and provides this file 

Typical image file, customer creates and provides this file 

Typical binary image file, customer creates and provides this file 

Typical binary image file, customer creates and provides this file 

Typical binary image file, used for device serial numbers, creates and provides this file 

10-22




schema.xsd 

device.ini 

csisp.log 

devices xml file, CheckSum provides the licensed version for systems other than the 

MultiWriter pps. For MultiWriter pps, license information in stored in the HASP USB 

Drive located inside each fixture. 

Typical xsd file 

Device ini files (not used in MultiWriter pps systems), CheckSum provides licensed 

version 

Optional diagnostic file, created at run time, see the MISP Diagnostics/Options settings 

csispdebug.log 

Optional diagnostic debug file, created at run time, see the MISP Diagnostics/Options 

settings 

Skip PCB file 

See Configure Directories/Locations > Skipped PCB Input File on page 5-16 

YYYYMMDD.dat 

SPC Data file, controlled by SPC Logging, see Statistics Data File Example on page 

15-6 and Statistical Analysis on page 8-1 

MultiWriter pps Required Files 

1) In c:\checksum\ (or in the install directory) 

pps.exe 

csMWDiag.exe 

csRUS.exe 

csMWDiag.dll 

csGrid.dll 

csISPui.dll 

haspcdfs.dll 

usbdrvd.dll 

csMWDiag.ini 

Main system software 

Wrapper for csMWDiag.dll 

Create HASP c2v file on page 6-21, fixture connected with 

power-on 

PPS diagnostic and 2 Demo devices execution 

MISP setup screen Grid (COM, needs installation) 

MISP setup screen and Wizard (COM, needs installation) 

HASP Drive required DLL 

CheckSum USB Driver 

Optional 

2) In c:\checksum\multiwriter\ (or in the install directory\multiwriter\) 

10-23


Controlling Program Flow 


devices.xml 

schema.xsd 

Contains 2 demo devices when no fixture is present. If a fixture 

is "engaged", the USB dongle devices.xml is used instead. 

Schema file 

3) In c:\checksum\pps\selftest\ (or in the install directory\pps\selftest\) 

csISP_SelfTest.ini 

Internal28F320C3.ini 

csISP_SelfTestData.hex 

dummy1.hex 

dummy2.hex 

Dummy file for demo template 

Dummy file for demo template 

4) In HASP USB Dongle (or in the install directory\pps\fixture USBDrive) 

autorun.inf 

Name of the USB Drive 

Fixture_Config.ini (Optional) auto load program path (relative or full path) 

Bin\csMISP.dll 

Main MultiWriter execution (HASP SRM Envelope) 

Bin\csMISP.exe 

Wrapper for csMISP.dll 

Bin\csMISP.ini 

Any changes to configDir and deviceDir 

Bin\MultiWriter\devices.xml List of available devices for each fixture 

Bin\MultiWriter\schema.xsd Schema file 



Under most circumstances, CheckSum test programs are executed linearly from top to bottom. 

However, you can alter or extend this flow with use of some special test types. 

• Branching on page 10-25 

• Exiting the Program on page 10-26 

• Running Another Test Program on page 10-26 

• Extending Test Program Length on page 10-27 

10-24




• Encapsulating a Test on page 10-27 

• Executing a User-Written Program on page 10-27 

Branching 

The System software supports program labels and branching. A branch is a tool programmers 

use to change the order of the program by transferring execution to begin at another part of the 

program. 

This allows execution to move from one point in the program (i.e., the branch or jump 

statement) to another (a label statement) rather than the next step in the program. You can 

specify that a program branch occur unconditionally (always) or based on the outcome of an 

analog or digital measurement or an operator entry. 

Labels are names assigned to a step in the test program with use of the LABEL test type. To 

put a label in the test program, insert the LABEL test type, then the name of the label in the 

test title column. The label can be up to 255 characters long (including spaces). The System 

ignores whether characters in label titles are upper or lower case. 

There are a series of jump commands that transfer to a label. In all cases the destination of the 

jump is typed into the test title column. The jump destination must match a LABEL 

destination or you will get an error when exiting the Edit window. 

You can use jumps and labels to form small loops to wait for digital or analog changes to 

occur, or to wait until the operator provides an appropriate input. You can also use jumps to 

abort the program when a specified number of errors have occurred. 

There are a number of jumps based on most types of measurements. These measurements are 

exactly like the corresponding measurement test types but rather than generate test Pass or Fail 

results, they generate program flow changes if the test step passes. 

For example, the corresponding jump test type for a DIGI test type is JMPDI. When the 

JMPDI step is executed, it generates an internal pass or fail status based on the high and low 

limits. If it fails, it continues on to the next test step in the program. If it passes, it begins 

program execution at the LABEL test step where the two test titles match. 

An unconditional jump (the JMP test type) always generates a change in control flow. 

You can also branch on the numbers of jump errors (failures) in the test program. You can use 

this, for example, to stop the test earlier (for faster System throughput) if there are a significant 

number of errors during a test. Unlike the system error count displayed in the upper section of 

the test display, the jump error counter counts all failures that occur, even if the test step is 

subsequently repeated and passes, see Jump Based on Number of Errors on page 14-14 and 

Set Error Counter, Control Error-Based TRY Blocks on page 14-13. 

Following are the JMP test types that can be used: 

10-25




JMP 

unconditional jump to label 

JMPDI 

jump based on digital input 

JMPPI 

jump based on port input 

JMPK 

jump based on keyboard input 

JMPE 

jump based on the jump error count of the test program 

JSTST 

jump based on self-test 

MEMS jump based on contents of MEMS variable (ranges 20 to 22) 

MEMI / MEML jump based on contents of MEMI / MEML variable (ranges 20 to 23) 

MEMR / MEMD jump based on contents of MEMR / MEMD variable (ranges 20 to 23) 

Exiting the Program 

In most cases, the system is run so that it halts at the end of an entire test. However, the test 

can be terminated (Escape key or Exit button) by the operator in the middle of a test. 

If your test program has special actions that you want to occur at the end of each test 

execution, even if the operator aborts the test prematurely, you can insert a special LABEL test 

step on page 14-11 into the program. If you have a LABEL test type with the name (test title) 

of SHUT DOWN in your test program, the System will execute the test steps after it if the 

operator aborts the test. 

For example, perhaps you want to log test results after each test with a RPRTS test step on 

page 14-49. If you make the last two lines of the program as a LABEL SHUT DOWN 

followed by the RPRTS test step, the report will always be generated. 

Running Another Test Program 

In some cases, you might want to leave the program file that you are executing and load and 

run another test program. For example, you may write a supervisory program that asks the 

operator to type in the name of the UUT. Based on what the operator types in, you can load 

and run another test program for that UUT, then return back to the supervisory program. You 

could, for example, also base the program that is to be run upon a bar-code input from the 

UUT. 

The statement that allows you to do this is the RUN test type. Enter the name of the test 

program that you want to load and run as the test title for the test step. This name is the same 

as you would type in for loading a test program from other System menus. 

When you call a test program with a RUN command, the called program is loaded over the top 

of the calling program, and execution begins at the first step of the loaded program. All of the 

test results of the calling program are lost and can only be logged with use of the RPRTS test 

type on page 14-49. 

At the end of the called program, the System comes to the Test menu which allows for Test, 

ReProgram, Print (show) report or Exit. However, you can use the RUN command again to 

reload the initial program again prior to the end if you wish. 

Remember to use the RPRTS test type to save results prior to using a RUN test step if you 

want to log data for the UUT. 

10-26



External Programs and Control (COM) 

Extending Test Program Length 

Test programs with the .SPEC file extension allow up to 30,000 test steps which is normally 

adequate for performing all necessary tests on the UUT. However, you can make the test 

program longer by using the RUNT test type. When you use a RUNT test type with a range of 

2, and a test title with the called test program's name, the following actions occur: 

1. The results of the present test program are temporarily saved, 

2. The called program is loaded and executed, 

3. At the end of the called program, its results are saved, 

4. The calling program is reloaded and execution begins at the test step following the RUNT 

test step. 

5. At the end of the main program's execution, the results of all of the main and called 

programs are collated to form one test result. 

In the System operator's eyes, only one test program has been loaded and executed. You can 

have several RUNTs in a single program so as to provide an almost unlimited program length 

from a practical perspective. 

Encapsulating a Test 

You can use the RUNT test type to encapsulate several actions into a single test result. You 

might want to have a group of test steps that cause the System to perform a number of actions 

(for example an interactive adjustment on the UUT), but only generate one (or no) test result 

for the entire group. To do so, use a RUNT test type with a range of 0 for a pass/fail result, 1 

for no result, and a test title of the called test program's name. 

If the called program passes, the RUNT test step passes. If the called program has one of more 

errors, the RUNT test step fails. 


Executing a User-Written Program 

In the event that you have special program needs, the system allow you to write a program in 

any programming language that will generate a DOS .EXE or .COM file (such as C, Pascal, or 

Basic), execute it, then return to the main program. 

This feature allows you to perform tasks such as interfaces to factory data logging systems or 

special register-level IO for non-CheckSum hardware control. 

These programs are executed using the EXEC test type. The name of the program to load and 

execute is specified in the test title. You can cause a pass/fail result if you wish by setting the 

'To (+)' point column to 0 and returning a DOS error-level in the called program. If the error 

level is zero upon return, the step passes, otherwise it fails. If the 'To (+)' point is 1, the step 

always passes. 

Special characters, or strings, in the test title specify the parameters to pass to the routine. You 

can pass the value of memory variables as command-line parameters by special codes in the 

10-27




test title. See Execute User-Written Routine on page 14-23 for details. You can send 

information back to the test program by writing it to ASCII disk files from the EXECed 

program, then reading them back in with the MEMI, MEML, MEMS, MEMD, or MEMR 

commands using a range of 7 or 35. 

Automation Interface (COM) 

ActiveX Automation Server 

If your software development tool can access ActiveX Automation Server, you can automate a 

subset of Visual software test functions from your application. For example: starting Visual 

software, opening a test program, executing the test program, printing the test result report to a 

file, etc. 

Using a Visual Basic Script (see the following tutorial) is one example of automating Visual 

software using the COM interface. Visual Basic Script is a simple scripting language and 

readily runs in most Microsoft Windows Operating System – (with Internet Explorer 3.0 or 

above). If there is no tutorial available for your development toolkit, this tutorial can give you 

some directions on how to find the corresponding information in your development toolkit. 

List of COM Interface Methods, Properties, and Types 

If your development toolkit can access ActiveX Automation Server, it usually has a tool to 

import ActiveX type library. Use it to import Visual software ActiveX Automation Server 

library and create the corresponding source file(s) in your development language, so you can 

view and use the available interface methods and properties. 

Notes: 

During automation, most of User Interface features (error dialogs, user input dialogs, etc) in 

Visual software are still functional. Therefore, if you do not want any User Interface prompts 

to appear, avoid settings or situations that cause such things to occur. Examples are: 

• User Input dialogs that appear 

• Error dialogs that appear because of: error in loading file, error in finding system module, 

etc. 

Certain features are automatically disabled when Visual software is started via COM Interface: 

• Halt on Fail 

• Single Step 

• Ask user for UUT Serial Number Before or After Test. The interface method 

SetUUTSerialNumber can be used to set UUT Serial Number from your application. 

• Ask user for Batch ID Before or After Batch. The interface method SetBatchID can be 

used to set UUT ID from your application. 

Regarding automation, there are two possible modes when Visual software is running. One, in 

AutoTestMode, meaning Visual software is started by Windows in response to a request from 

an automation controller. (your application). Two, NOT in AutoTestMode, meaning Visual 

software is started by a user (e.g. starting Visual software from Windows Explorer). To 

automate Visual software from your application (e.g. executing test), Visual software must be 

in AutoTestMode. There is an interface property you can inspect from your application to find 

10-28




out which mode Visual software is when your application is running. 

Tutorial for Automating Visual software using Visual Basic Script 

The following is a brief tutorial on creating a Visual Basic Script that automates Visual 

software to do the following tasks: start Visual software, open a test program, execute it, and 

display a dialog box that shows whether the test pass or fail. Visual Basic Script is a simple 

scripting language and readily runs in most Microsoft Windows Operating System - (with 

Internet Explorer 3.0 or above). If there is no tutorial available for your development toolkit, 

this tutorial can give you some directions on how to find the corresponding information in your 

development toolkit. 

1. Before you can start automating the system software from your application, you have to 

run Visual software at least once so it will register its automation object to Windows. Or, 

on the command line parameter (where you have the system software executable file), you 

can type and hit enter : 

[MultiWriter executable filename] /regserver 

2. Create a blank Visual Basic Script file, call it tutorial.vbs. 

3. Now, we can start writing the program to automate Visual PPS. First you need to start 

Visual software and get an interface to Visual PPS automation object. 

[1] Dim Vispps ' Interface to control system software test execution 

[2] Set VisPPS = CreateObject("VisPPS.AutoVisPPS") 

Note that the brackets and number on the left is the line number to help identifying code in this 

tutorial. They should not be present in the actual Visual Basic Script. 

When line [2] is executed, Visual PPS will be started as a minimized window. 

4. The VisPPS variable now holds the interface to the Visual PPS automation object and you 

can invoke methods or obtain properties of the Visual PPS automation object. At this 

point, we want to open a test program and execute it then display whether the test pass or 

fail (you need to have the testauto test program in c:\checksum\specfile, or you can 

replace it with your own test program name). 

[3] VisPPS.Open "c:\checksum\specfile\testauto" 

[4] VisPPS.Test 

[5] If VisPPS.IsTestPass = True Then 

[6] Msg = "Pass." 

[7] Else 

[8] Msg = "Fail." 

[9] End If 

[10] MsgBox Msg, vbOKOnly, "Visual PPS Controller" 

5. However, we are not done yet. If we run the tutorial.vbs script now, Visual PPS will start 

and the test program may or may not get executed. This is because after line [2], Visual 

PPS will be started and it takes some time to do some initialization, where line [3], and so 

on, might be executed by Visual Basic Script. If Visual software is not finished with its 

initialization, many of the subsequent calls to the automation object methods will not have 

any effect. Hence, after line [2] before we proceed with opening the test program, we need 

10-29




to wait until Visual PPS initialization is completed. Below is the script modified to do so - 

see line [3] and [4]. 

[1] Dim VisPPS ' Interface to control Visual PPS Test Execution 


[3] Do While Not VisPPS.IsAutoTestInitialized 

[4] Loop 

[5] VisPPS.Open "c:\checksum\specfile\testauto" 

[6] VisPPS.Test 

[7] If VisPPS.IsTestPass = True Then 

[8] Msg = "Pass." 

[9] Else 

[10] Msg = "Fail." 

[11] End If 


Now if you run the tutorial.vbs script (double click it on Windows Explorer), Visual PPS will 

start, wait till the initialization is finished, load the test program, execute it, and display 

pass/fail on the dialog box. When your script is finished, Visual PPS is automatically closed. 

Since the Visual PPS software takes several seconds to start up and initialize, to minimize 

execution, do not open and close it often. The calling test program needs to use a loop and 

keep Visual PPS open as long as possible. 

6. Finally, one more thing to go over. To automate Visual PPS from your application, Visual 

PPS must be in AutoTestMode, meaning Visual PPS is initially started by a controller 

application (e.g. your application). We can improve the script above to handle the situation 

where Visual PPS is not in AutoTestMode, e.g. it was initially started from Windows 

Explorer. After line [2] above, we can check whether Visual PPS is in AutoTestMode, if 

this is so, simply show a message dialog and exit. Below is the script modified to do so - 

see lines [3] and [4]. 

[1] Dim VisPPS ' Interface to control Visual PPS Test Execution 


[3] If Not VisPPS.IsAutoTestMode Then 

[4] Msg = "Visual PPS is not in Auto Test Mode." 


[6] Else 

[7] ' do open test program, execute, and display pass fail here 

. . . . 

[ ] End If 

7. The following is the complete Visual Basic Script (after minor changes to make it more 

readable). 

' The following is a simple example that shows how to use 

' Visual PPS as automation server in VBScript. 

' To verify and observe the expected result, copy the given test 

' program to the proper folder and make sure you have c:\temp folder 

' or edit the code below accordingly. 

Dim VisPPS ' Interface to control Visual PPS Test Execution 

10-30



Generating Reports from a Test Program 

Dim OKToExecuteTest 

Dim Msg, DialogTitle 

DialogTitle = "Visual PPS Controller" 

Set VisPPS = CreateObject("VisPPS.Auto VisPPS ") 

' Check whether Visual PPS is properly started 

' for Automating Test Execution 

If Not VisPPS.IsAutoTestMode Then 

Msg = "Visual PPS is not in Auto Test Mode." 

MsgBox Msg, vbOKOnly, DialogTitle 

OKToExecuteTest = False 

Else 

OKToExecuteTest = True 

End If 

If OKToExecuteTest Then 

' Since Visual PPS takes some time to do system initialization 

' it is nescessary to wait until Visual PPS is ready 

' to execute Test 

Do While Not VisPPS.IsAutoTestInitialized 

Loop 

VisPPS.Open "c:\checksum\specfile\testauto" 

VisPPS.Test 

' Display whether Test Pass or Fail 

If VisPPS.IsTestPass = True Then 

Msg = "Test Pass." 

Else 

Msg = "Test Fail." 

End If 

MsgBox Msg, vbOKOnly, DialogTitle 

End If 



There are several way to generate reports from the CheckSum test system: 

• After each test, from the Test window, the operator can manually select a full test report or 

a test report that contains data for failed steps only. 

• The System can be configured, using the Configuration windows described in Configure 

Reporting on page 5-8, to automatically output a test report that contains full or failed-only 

test results. The report can be generated after each UUT, or only after UUTs that fail. The 

amount of data reported can also be fine-adjusted from within the test program with use of 

the RSLTS test type. 

10-31




• The test programmer, using the RPRTS test type on page 14-49, can output test reports 

from within the test program. 

The RPRTS test type allows you to control test results output directly from within the test 

program. The RPRTS test type can be useful in cases such as when you never leave a test 

program (i.e., you jump back to the top of the test program after each UUT so that you can 

more carefully control the test environment) or you are using the RUN test type. 

Normal Test Reports 

To output normal test reports, put the name of the report destination in the test title (e.g., 

COM1, LPT1, a disk file name), and add the range numbers for your selection from the 

following list: 

1 Include a sequence number in the test report header. The sequence number starts at one 

with each assembly tested in a batch. To reset the sequence number, either reload the test 

program, or move back to the 'Main System' window then start testing again. 

2 Send the test results report, which includes the header and the failed steps, to the name in 

the test title (otherwise it goes to the report destination as specified in the Test window). 

8 Only print the report if there were one or more failures during the test. 

16 After the report, clear out results in memory to start a fresh UUT run. 

64 Also include detailed information about test steps that passed. 

Statistical Data Reports 

The System can also generate statistical process control (SPC) reports as described in 

Statistical Analysis on page 8-1. SPC reporting includes yield reports, X-Bar/Sigma reports, 

and pareto charts. SPC reporting deals with information about all of the testing done on a test 

station rather than individual UUT reporting. You can also process this ASCII log information 

yourself using tools such as spreadsheets or custom analysis software. 

You can also use the RSLTS test type to output data to the SPC log. Even though this table is 

shown separately for clarity, you can add together the values between this table and the 

previous one if you wish. If you want to use two test step, one for normal results, and another 

for SPC data, make sure that you do not clear out the results by including a range value of 16 

on the first RSLTS test step. 

To send data to the SPC log, add the range numbers for your selection from the following list: 

4 Print results to the SPC log. 

8 Only write to the SPC log if there were one or more failures during the test. 

16 After the report, clear out results in memory to start a fresh UUT run. 

32 Report summary information in the SPC log. 

64 Include detailed information about passed test steps in the SPC log. 

128 Include detailed information about failed test steps in the SPC log. 

Changing Report Paths 

You can also use a RSLTS test step to specify the path to the report or SPC data. Normally, 

this information is specified for the System in the Configuration windows (see Configure 

Directories/Locations on page 5-16). If the RSLTS test type is used for this purpose, it 

10-32



Panelized Testing 

changes the path during program execution. The path is automatically added to the front of the 

file name specified in the title of the RSLTS test step. 

The new path is specified in the MEMS string variable. Load it with the desired new path 

string. Then, to change the path for the SPC data use a range value of 256, and set the 'From 

Point' to 0. To change the path for the normal results data, use a range value of 246 and set the 

'From Point' to 1. 



Overview 

UUTs that consist of several individual PCBs (usually identical) in a single panel can be 

accommodated using the multi-PCB capability of the test System. 

The multi-PCB panel capability provides several features: 

• You can program the first PCB in the panel, then have the System replicate the point 

names and/or program data for the other PCBs. The System automatically updates the test 

point numbers as it copies the data. 

• When testing a panel, the System displays the location of the PCB currently under test in 

the lower right of the testing window. This way the operator always is aware of which 

PCB is being tested. As each PCB test is completed, it turns green if it passes, and red if 

there are any failures. An example is shown in the following figure. 

Test Window with Multi-PCB Panels 

10-33




• At the end of each test (and prior to the first test) an additional selection, 'Select Skips' is 

available from the 'PCB' menu. This selection only appears if the assembly that you are 

testing is configured as a multiple-PCB panel. When you have selected to select skips, you 

are presented with Skip PCBs in Panel display shown in the figure below. 

By moving the cursor to the PCB(s) that are to be skipped, then pressing the SKIP button, the 

test on the selected PCBs will not be performed. This selection is helpful when one or more of 

the PCBs in the panel are rejected and a test is not desired. Note that with the 'Retain Skip 

Selections' item in the 'PCB' menu, you can instruct the System to remember and reuse the 

skipped information. This can be handy if you have built a batch of UUTs with a missing or 

known-faulty position. 

Select Skipped PCBs in Panel 

10-34




Test FAIL Results for a Panel of Boards 

With multiple boards in the panel, the test results, shown by the color of the small boxes in the 

PCB Test Map, indicate several possibilities: 

White box = this board has not been tested (if the test is complete, this board was 

skipped) 

Black box = test is "in progress" for this board 

Yellow box = this board has not failed any tests 

Red box = this board failed at least one test 

Green box = the test is complete and this board passed, any yellow boxes are set to 

green 

Note: The use of jumps/loops on page 14-10, Error on page 14-13, and Rprts on page 14-49 

can affect the test results and the color of the PCB boxes. 


• Panelization Programming by Wizard on page 10-36 

• Manual Panelization Programming on page 10-37 

10-35




Panelization Programming by Wizard 

For most common panelized UUTs, the System includes a Panelization Wizard that makes 

panelization quick and easy. To use the System for panelized PCBs with the wizard, use the 

following sequence: 

1. Wire the fixture with each PCB in the panel wired identically, but begin at a new range of 

test point numbers. 

2. Write and fully debug the test program for the first PCB in the panel (the one with the 

lowest numbered test points). 

8. From the 'PCB' menu, select 'Panelization'. Then, from the 'PCB Panelization' window 

shown in the following figure, select 'Use Panelization Wizard'.' 

PCB Panelization Window 

9. From the 'PCB Replication Wizard' window (shown in the following figure), first select 

where you have chosen to wire the first test points in your fixture. The default is the upper 

left corner, but you can choose other corners if you wish. Next, indicate whether you have 

wired your test points so that they increment as you go across (which is by row) or as you 

go up or down (which is by column). Next enter the size of your PCB matrix by the 

number of PCBs in each row (the first number) and by the number of PCBs in each 

column (the second number). Finally, you press OK, and the System goes to work for you. 

It will confirm that you want to perform the individual steps, then generate the test 

program. Once it is done, the test program is ready to save and run. 

10-36




PCB Replication Wizard Window 

The System will have assigned a PCB test-step at the beginning of each new PCB in the panel, 

and replicated (step and repeated) the point names and point numbers as appropriate. If you 

have to make a global change to your test program, you can make it on PCB 1, then run the 

sequence again. It will overwrite all of the PCBs greater than one with the new data. 

Manual Panelization Programming 

In the event that you have a more complicated panel, you can individually perform steps that 

the wizard does for you. This allows you to do unique operations, such as ordering the PCBs 

differently, specifying layouts that are not rectangles, or accommodating wiring that is not in 

even increments. 

The first step in panelizing is to specify the physical layout of the panel. This is done with the 

'PCB Locations/Numbers' window shown in the following figure. To obtain this window, 

select 'Panel Map' from the 'PCB Panelization' window. In the upper left corner, you can 

specify the overall size of your array. In each PCB position, you see a PCB number associated 

with the PCB. The System replicates and tests starting at the lowest PCB number, then 

sequentially tests each following one. If you want to change the order, move to the desired 

position, then delete the old number and enter the new number. You may not have duplicate 

PCB numbers for replication and testing, but temporarily you may during the assignment 

process in this window. 

If your panel is not a rectangular matrix of PCBs, you will want to specify a PCB in the panel 

as not being used. To do so, select the PCB that is not in the panel, delete the PCB number, 

then press the BACKSPACE key. When you move off the PCB, you will see that it does not 

have a number anymore, and will not be displayed or used for replication or testing purposes. 

10-37




PCB Panel Map Window 

The next option has to do with point naming for the PCBs past the first. 'Replicate Point 

Names' requests that the System duplicates the point names from the first PCB to the other 

PCBs. 

There are some other options available from the 'Advanced Options' selection of the 'PCB 

Panelization' window. When you make this selection, you are presented with the 'PCB 

Runtime Options' window shown in the following figure. 

10-38



Use of Program Memory Locations 

Advanced Options Window 

The 'Panelization Enabled' feature is normally turned on. If you turn it off, even if the test 

program is panelized, the System will not display the panel map during testing or after the test 

program is completed. 

'Multiple UUT Serial Numbers Per Panel' can be enabled if you are tracking UUT serial 

numbers for the panel, and you have different serial numbers for each PCB on the panel. If 

this is enabled, and you have enabled (in the Configuration/Environment windows) the feature 

of asking for serial numbers, you will be asked for the serial number for each PCB in the panel, 

as opposed to one serial number for the complete panel. 

'PCB SPC Reporting' allows you to enter how SPC data is logged for panelized PCBs. The 

differences allow you to track your panels in the way that is most efficient for your facility. In 

the default case, 'Panel consists of identical PCBs,' the System tracks each PCB in the panel as 

a different UUT. If you select 'Treat Entire Panel as one UUT,' the System reports on the 

complete panel (including all PCBs) as a single UUT. If you select 'Panel consists of different 

PCBs,' the System tracks each PCB on the panel as a unique PCB. This case is normally used 

if your panels contain different UUTs. For example, you might build on one panel, both a 

PreAmp circuit PCB and a Power Amp circuit PCB. Both are different, but on the same panel. 



Overview 

The System can test most assemblies with the basic test steps that have been discussed in this 

topic. In some cases, however, you may need to do special things, such as mathematics based 

on readings, special operator input processing, and reading/writing data from files on the disk. 

The System provides unnamed variables for compatibility with previous software versions. 

Named variables are recommended for improved documentation and ease of programming. 

10-39




The named variables are created when they are first used or when entered into the list of 

variables. Use the program editor menu item Setup > Variables List to access the named 

variables. This window allows you to add, delete, rename, import and export the named 

variables. 

The Options menu (or mouse right-click on a variable name) provides selections to make 

changes to each variable. The list can be sorted by the options Sort selection or by clicking on 

the column title: Name, Type, Batch Persistent, or Used. The variables (Integer and Real) are 

reset to zero or cleared (string) at the beginning of each Batch. The variables will be reset to 

zero or cleared at the beginning of each Test in a Batch, unless the Batch Persistent setting is 

Yes. Setting Batch Persistent to Yes, allows the variable to be unchanged between tests. 

After you have inserted the appropriate memory manipulation test type, the easy way to 

manipulate (assign, change, etc) the variable is to use the memory setup (Mem Setup) window 

that is accessed with the editor menu item Measure > Step Analysis F6 (function key F6). 

Click the mouse on any BLUE colored item in the memory setup (Mem Setup) window to 

access the pull-down menu: 

10-40




The name of the variable is shown in the test step column labeled To (+) Name. The variable 

name must follow these rules: 

• The first character must be a letter or an underscore 

• The subsequent characters must be a letter, numeric, or underscore 

• Upper or lower case letters can be used since the variable names are case insensitive 

A named variable can also be an indexed array. The first array index is "1" so to define the 

array counter with ten entries, use Counter[1..10]. The array index can be an integer or an 

integer variable, such that Counter[10] = Counter[Index] when Index is equal to 10. 

The memory manipulation test types (MEMI, MEML, MEMR, MEMD, MEMS on page 14- 

25) allow use of the System's memory to assign, keep track of, manipulate, and use variables 

within a test program. 

There are five types of memory variables: 

1. The 16-bit integers can be whole numbers ranging from -32,768 to +32,767. The test-type 

that works with the memory-integer variable is MEMI. 

2. The 32-bit integers can be whole numbers ranging from - 2,147,483,648 to 

+2,147,483,647. The test-type that works with the memory-integer variable is MEML. 

3. The 48-bit real variables include a fractional part and can range from plus to minus 

10E±37. The test-type that works with the memory-real variable is MEMR. 

4. The 64-bit (IEEE floating point) real variables include a fractional part and can range from 

plus to minus 9.99999E±307. The test-type that works with the memory-real variable is 

MEMD. 

10-41




5. String variables can be up to 255 characters long and can include any normal ASCII 

characters. The test-type that works with the memory-string variable is MEMS. 

These steps allow entry or assignment of the memory contents, pass/fail test generation based 

on the value of the memory contents, fundamental math and manipulation of the memory 

contents, transfer of control based on the contents of memory, or display of the variable. 

These test steps can be used to form a counter, to control program execution based on operator 

entry, or as an alternate way to generate test results based on operator entry. 

After you have inserted a memory manipulation test type, the memory type can be changed in 

the setup window (press function key F6). Click the mouse on the BLUE colored memory 

type item to access the pull-down menu: 

By clicking on any Blue colored item in the setup window, you can modify the operation or 

function desired. 

There are numerous operators that can be used on the memory variables to initialize, 

increment, transfer, display, and otherwise manipulate the memory variable value. For 

example, the assign operator on the MemI variable named LoopCount is setup as shown: 

10-42




Specifying the index by using a Named Integer Variable allows the user to programmatically 

change the index of the array. For example, to set the array variable Results[1..10] to be 

Results[1..10] = [1, 2, 4, 8, 16, 32, 64, 128, 256, 512], use the following test step sequence: 

10-43




Refer to the test-type descriptions (Memory Manipulation Test Types) in Test Type 

Descriptions on page 14-1 for information about the specific range values that can be used 

with these test-types. 

The sections for each memory variable provide descriptions for the range setting. You may 

prefer to read the descriptions to determine the correct range value rather than use the pulldown 

menus. 

Here are several windows that show the main operators on the pull-down menus: 

10-44




To examine the values of the memory variables, use the editor menu item Tools > Show 

BreakPoint Information. To see the individual array values in the BreakPoint dialog box, 

double-click on the array name. Double click in the same box again to see the list of variable 

names and values. 

10-45





• Special Notes about MEMS below 

• Special Notes about MEMR / MEMD on page 10-47 

• Special Notes about MEMI / MEML on page 10-47 

• Memory Variables and Program Storage on page 10-47 

Special Notes about MEMS 

Note that there are several string variables (see MEMS on page 14-25): 

• The System string variable (MemS) is called the "Memory String". 

• The memory string variable, referred to as the "Compare String", can be used to make 

pass/fail comparisons against the memory string variable. For example, you can load the 

compare string with data, then compare it to the main memory string and make decisions 

based on the result. 

• The memory string variable, called the "Batch Memory String", is only cleared between 

batches. As such, you can use it to solicit input about the batch as a whole (e.g., batch 

number, UUT configuration), then not ask the operator again until a new batch has started. 

You can do this by checking to see if the batch memory string is empty, and if so, 

assigning it as appropriate. 

10-46




Special Notes about MEMR and MEMD 

In addition to the normal memory operations, there is a related time storage location (called 

Memory-Time) in the MEMR / MEMD on page 14-30 command set. You can use this to 

compute the time from an event to another event, or to set a beginning time, then delay until 

specified time. This can be useful, for example, to time events or to check how long the 

present program has been executing. 

Special Notes about MEMI and MEML 

In addition to the normal memory operations, you can obtain the base addresses of the 

CheckSum modules in the System. This can be helpful if you would like to do some direct 

addressing of the hardware in the program. You can also use some of the MEMI / MEML on 

page 14-26 commands to control input and output from the operator keyboard. The MEML 

commands are similar to the MEMI commands. 

Memory Variables and Program Storage 

While most of the variable operations are fairly straightforward, one type of operation can be a 

little confusing to understand at first. There are three variable types (integer, real, and string) 

available to store data. You can use named variables, the five system variables (MemI, MemL, 

MemR, MemD, and MemS), and fields in the test program as storage space. With some of the 

range values, you can specify a step number and column in the test program, then move data 

between the specified location and the memory variables. Since the storage space for a 

program is 30,000 steps, and most programs are much shorter, you can specify step numbers 

above the last program step, but less than 30,000 and they will not conflict with the program 

being executed (however, they can be overwritten if you do a RUNT or RUN). Named 

variables on page 10-39 provide an enhanced method to store and manipulate variables. 

If you take advantage of moving data back and forth between memory variables and test 

program fields in the test program (rather than the space beyond the program), you can do 

many special things in your test program. For example, you can read the measured value from 

an earlier measurement step, do math with it, and then write it into a later test step as a low or 

high test limit. In programming, this is called impure code since you can modify the test 

program as it executes. 

When doing this type of programming, you can specify a test step number directly (the step 

number is shown in the lower right corner of the 'Editor' window). This works fine if you are 

transferring data to the area above the test program area. If you are transferring data within the 

test program, however, directly using the step number is not recommended since if you add or 

delete a line with a lower number, the program will not work properly anymore. In this case, 

you should use a relative address in the MEM command. If you want to refer to a step number 

X steps beyond the MEM command, use a step value +X. If you want to refer to a step 

number Y steps previous to the MEM commend, use a step value of -X. If you use this 

relative programming convention, your program will not be affected by adding or deleting 

steps unless they are in the relative range specified. 

10-47




10-48

Chapter 11 

Program Examples 

Example Programs 

The CheckSum Test System provides a flexible software environment to solve unique 

programming problems. 

The following sections show example test program segments. 

Programming One Device below 

Programming Multiple Identical Devices on page 11-3 

Programming Multiple Different Devices on page 11-6 

Screen and Display Attribute Manipulation on page 11-10 

Open a Window with a Picture on page 11-19 

Fixture Identification on page 11-20 

Programming One Device 

The following example shows how to program a single device installed on an assembly. 

U1 

Top View of the PCB Assembly 

The fixture design and build checklist on page 6-28 has been verified.


Programming One Device 


First, the power supply is setup. Since the assembly has already been tested on a CheckSum 

Analyst ems ICT, the units are known to be defect-free and power can be applied for ISP. The 

voltage and current are checked to verify the setup to the assembly is functioning properly. 

The step to program the U1 device is MISP on page 10-7. This step includes all the 

information needed to program the device. Several system files are referenced by this single 

step. The "U1", an ATTiny45, device program data is stored in the file "U1eepromdata.hex". 

For a single device, the PCB map is not used. 

The test program might be as simple as this: 

The MISP title setup, on program step 5: 

The MISP device and image file setup: 

11-2



Programming Multiple Identical Devices 


The following example shows how to program 5 identical devices on a panel with 5 identical 

PCBs. 

PCB 1 

U5 

PCB 2 

U5 

PCB 3 

U5 

PCB 4 

U5 

PCB 5 

U5 

Top View of the 5-up PCB Assembly 

The fixture design and build checklist on page 6-28 has been verified. 

11-3




The panel has 5 identical PCBs each with one device. The device on each PCB is the same 

part number and needs to be programmed with the same data. 

First, the power supply is setup. Since the assemblies on the panel have already been tested on 

a CheckSum Analyst ems ICT, the units are known to be defect-free and power can be applied 

for ISP. The voltage and current are checked to verify the setup to the assembly is functioning 

properly. 

The step to program all five of the U5 devices simultaneously on the 5-up assembly is MISP 

on page 10-7. This step includes all the information needed to program the device. Several 

system files are referenced by this single step. The "U5", an 25HP512, device program data is 

stored in the file "U5flashdata.hex". 

The setup for the PCB panel map for this 5-up panel matches the assembly: 

The "5-up PCB panelized" version of the test program might be like this: 

11-4




The MISP title setup, on program step 16: 

The MISP device and image file setup: 

11-5


Programming Multiple Different Devices 



The following example shows how to program 2 different devices on a panel with 10 identical 

PCBs. 

PCB 1 

U2 

U7 

U2 

U7 

PCB 2 

PCB 3 

U2 

U7 

U2 

U7 

PCB 4 

PCB 5 

U2 

U7 

U2 

U7 

PCB 6 

PCB 7 

U2 

U7 

U2 

U7 

PCB 8 

PCB 9 

U2 

U7 

U2 

U7 

PCB 10 

Top View of the 10-up PCB Assembly 

The fixture design and build checklist on page 6-28 has been verified. 

11-6




The panel has 10 identical PCBs and each PCB has two different devices "U2" and "U7". The 

"U2" device on each PCB is the same part number and needs to be programmed with the same 

"U2" data. The "U7" device on each PCB is the same part number and needs to be 

programmed with the same "U7" data. 

First, the power supply is setup. Since the assemblies on the panel have already been tested on 

a CheckSum Analyst ems ICT, the units are known to be defect-free and power can be applied 

for ISP. The voltage and current are checked to verify the setup to the assembly is functioning 

properly. 

The step to program all twenty (2 devices on 10 PCBs) of the U2 and U7 devices 

simultaneously on the 10-up assembly is MISP on page 10-7. This step includes all the 

information needed to program the device. Several system files are referenced by this single 

step. The "U2" device program data is stored in the file "U2flashdata.hex" and the "U7" 

device program data is stored in the file " U7flashdata.hex". EEPROM data can also be 

programmed for either of these devices. 

The setup for the PCB panel map for this 10-up panel matches the assembly: 

The "10-up PCB panelized" version test program might be like this: 

11-7




11-8




The MISP title setup, on program step 26:: 

The MISP, U2 (25HP512) and U7 (PIC16LF877A) device and image file setups: 

Note that the ports numbers for U7 start at 25 since the first 24 ports are reserved for the first 

device type, the 25HP512, even though only ports 1 to 10 are used for U2: 

11-9


Screen and Display Attribute Manipulation 



The following examples show how to use the SCRN test type for manipulating display 

attributes (i.e. text color and background color). 

The menu selection Measure > Step Analysis F6 in the edit window opens the easy to use, 

fill-in the form setup window to select these settings. 

First, the area from row 2 to 7, column 10 to 40 is setup with yellow text color (0) and black 

background color (16). Use the Set Display Attribute operation (512) to turn-on this set of 

attributes. The resulting total range value is 656 (0+16+512 = 528). 

11-10




Display messages are written in this region with the DISP 1, 2 and 3 steps. 

Next, the adjacent area from column 41 to 70 is setup with light white text color (15) and red 

background color (64). Use the Set Display Attribute operation (512) to turn-on this set of 

attributes. The resulting total range value is 591. 

11-11




Display messages are written in this region with the DISP 4, 5 and 6 steps. 

The operator is told to press any key. After a key is pressed, the display area is saved, text and 

background in rows 2 to 7 and columns 10 to 70 in a file named "screen.txt", specified in the 

step Title. This file will be used in the next section. 

11-12




Finally, we ask the operator to press any key to finish. The text is erased on the entire display 

(rows 1-8 and columns 1-80). The background is not affected. A final message is displayed 

across both regions with the DISP 7 step. 

11-13




Example Program for Display Attribute Manipulation 

11-14




Test Program Display Messages 

The following is the result if we run the test program. 

11-15




Example Screen Result for SCRN Test Type 

The following example shows how to use the SCRN test type with Range 8318 to load an 

existing message and attribute file. The screen.txt file created in the previous example is 

loaded. 

11-16




Example Program for SCRN Load Operation 

However, instead of putting the message and attribute in rows 2 to 7 and columns 10 to 70, the 

screen is positioned in rows 1 to 6 and columns 7 to 67. 

11-17




SCRN Load Screen Setup 

The following is the result after the test program runs, note the changed position of the boxes 

and text. 

11-18



Display a Picture 

Example Screen Result for SCRN Load 

Display a Picture 

To open a window with a picture, use the EXEC on page 14-23 step and pass the windows 

application run32dll.exe the parameters with the full path and file name of the picture. This 

calls the Windows Picture and Fax Viewer application (rundll32.exe) to display the image. 

Insert an EXEC step and press F6 to open the easy to use, fill-in the form setup window. 

The EXEC step Title is used to provide the entire parameter list: 

rundll32.exe C:\WINDOWS\System32\shimgvw.dll,ImageView_Fullscreen 

c:\checksum\temp\DUTSetup.jpg 

In the Title, be sure to include one space character between rundll32.exe and 

C:\WINDOWS… and between ImageView_Fullscreen and c:\checksum… 

11-19


Fixture Identification 


In the example, the file name for the image is DUTSetup.jpg in the directory 

c:\checksum\temp 

Exec Step Setup to Display the Picture DUTSetup.jpg 

Note that the first character in the Parameter(s) box, before C:\WINDOWS…, is a space 

character. The same as the space needed between rundll32.exe and C:\WINDOWS… in the 

step Title. 

Windows Picture and Fax Viewer can open several file formats including jpg, bmp, gif, png, 

and tiff. 


Each fixture will contain a USB device on page 6-21 ("HASP USB drive" or "HASP 

protection key") installed inside the fixture. To identify a fixture, you can save a file with a 

unique number to identify the fixture. Each fixture file can use the same file name and the 

contents (fixture ID) will be unique for each fixture. This unique number provides a unique ID 

for each fixture. 

11-20




The Memory Manipulation Commands MemI and MemL are used to write and read from a 

file on the internal USB device. Use MemI for fixture IDs from - 32,768 to +32,767 and 

MemL for fixture IDs from - 2,147,483,648 to +2,147,483,647. 

The MemI/MemL commands use Range 6 to write a value into a file and Range 7 to read the 

file contents. 

Rem 

Subprogram to 

Rem 

set the Fixture ID 

Disp l Enter Fixture ID Value 

FixID MemL 3 Get Fixture ID 

24.000 1.0000 

Rem 

Write FixID to USBDrive file: 

FixID MemL 6 C:\CheckSum\PPS\Fixture USBDrive\Data 

Files\FixID.txt 0.0000 0.0000 

Displays: 

1, 1, 1, Enter Fixture ID Value 

The above steps show how to enter the fixture ID value from the keyboard, store this value in a 

named variable (e.g., FixID) and write the value of the variable into the USB device file named 

"FixID.txt". 

The contents of the file are the ASCII characters for the numbers entered, such as 12345. You 

can use any editor to view or modify the contents of this file. 

Use the MemI or MemL Range 7 command to read the fixture ID from the USB device file 

named "FixID.txt" into a named variable: 

Rem 

Read FixID from USBDrive file: 

FixID MemL 7 C:\CheckSum\PPS\Fixture USBDrive\Data 

Files\FixID.txt 0.0000 0.0000 

This variable can be checked to insure the fixture ID matches the expected value for the 

program. For example, if the expected Fixture ID is 7, then use MemI or MemL with Range 

20 to check for the value 7: 

FixID MemL 20 Equal to 

Jmp 

Wrong FixID 

7.0000 7.0000 

In the above steps, if the value read from the file is 7, then the program proceeds (jumps to the 

Label "Equal to"). If not, then the program jumps to the Label "Wrong FixID". 

11-21




11-22

Chapter 12 

Fixture Receiver Wiring 


Fixture Receiver Interface Blocks Overview 

The 170-pin block receiver interface block designation (A to K) is shown below: 

Since the MultiWriter pps fixture system uses GenRad 2270-style fixture (or "test heads"), test 

heads can either be obtained from CheckSum or alternate local suppliers. CheckSum offers 

test head kits in three sizes. These test head kits can accommodate UUT sizes of up to 4 inches 

less than their nominal sizes. For example, a large kit can accommodate UUTs up to 21 by 17 

inches (53.3 x 43 cm). The top lid may reduce the usable size. Contact CheckSum for specific 

details about your assembly.




For each 24 devices in one device family, up to 170 connections are wired into the test head 

and one fixture wiring block is used. These fixture receiver wiring blocks mate with the 

receiver pin blocks to route the signals from the test head to the receiver. 

Within each pin block, the pin positions are numbered as shown below: 

These numbers are referenced when facing the spring-probes on the receiver pin block or when 

facing the wiring side of the interface block from inside the test head. The pins are numbered 

as pin 1 in the upper left corner, pin 17 in the lower left corner, pin 154 in the upper right 

corner, and pin 170 in the lower right corner. 

Fixture Wiring 170-Pin Blocks Overview 

The wiring blocks contain the system signals to control and communicate with the buffer 

modules. In addition, block A contains some system pins that are used for all test fixtures. 

12-2




Block K contains the power supply output pins and the power sense signals plus connections to 

the USB security device on page 6-21. 

The fixture blocks pin-out are defined in the following sections: 

Block A below for Ports 1 to 24 

Block B on page 12-6 for Ports 25 to 48 

Block C on page 12-10 for Ports 49 to 72 

Block D on page 12-13 for Ports 73 to 96 

Block E on page 12-17 for Ports 97 to 120 

Block F on page 12-20 for Ports 121 to 144 

Block G on page 12-24 for Ports 145 to 168 

Block H on page 12-27 for Ports 169 to 192 

Block K on page 12-31 for PS-UUT power supplies #1 to #4 and USB security device 

The 170-pin block signals are defined in the same orientation as the receiver/wiring blocks 

with pin 1 at the top of the column for each of the 10 columns (17 pins/rows in each column). 

Block A Pin-Out (Ports 1:24) 

Column Row Block-Pin Block : Signal 

1 1 A-1 A : C+ Ports 1:24 

1 2 A-2 A : C– Ports 1:24 

1 3 A-3 A : M+ Ports 1:24 

1 4 A-4 A : M– Ports 1:24 

1 5 A-5 A : I+ Ports 1:24 

1 6 A-6 A : I– Ports 1:24 

1 7 A-7 A : E+ Ports 1:24 

1 8 A-8 A : E– Ports 1:24 

1 9 A-9 N/C 

1 10 A-10 N/C 

1 11 A-11 N/C 

1 12 A-12 N/C 

1 13 A-13 N/C 

1 14 A-14 N/C 

1 15 A-15 N/C 

1 16 A-16 N/C 

1 17 A-17 N/C 

2 1 A-18 N/C 

2 2 A-19 A : Relay Port 1 

2 3 A-20 A : Port 1+ 

2 4 A-21 A : Port 1- 

2 5 A-22 N/C 


2 7 A-24 A : Port 2+ 

2 8 A-25 A : Port 2- 

2 9 A-26 N/C 


2 11 A-28 A : Port 3+ 

2 12 A-29 A : Port 3- 

2 13 A-30 N/C 

12-3





2 15 A-32 A : Port 4+ 

2 16 A-33 A : Port 4- 

2 17 A-34 N/C 

3 1 A-35 N/C 


3 3 A-37 A : Port 5+ 

3 4 A-38 A : Port 5- 

3 5 A-39 N/C 


3 7 A-41 A : Port 6+ 

3 8 A-42 A : Port 6- 

3 9 A-43 N/C 


3 11 A-45 A : Port 7+ 

3 12 A-46 A : Port 7- 

3 13 A-47 N/C 


3 15 A-49 A : Port 8+ 

3 16 A-50 A : Port 8- 

3 17 A-51 N/C 

4 1 A-52 N/C 


4 3 A-54 A : Port 9+ 

4 4 A-55 A : Port 9- 

4 5 A-56 N/C 


4 7 A-58 A : Port 10+ 

4 8 A-59 A : Port 10- 

4 9 A-60 N/C 

4 10 A-61 A : Relay Port 11 

4 11 A-62 A : Port 11+ 

4 12 A-63 A : Port 11- 

4 13 A-64 N/C 

4 14 A-65 A : Relay Port 12 

4 15 A-66 A : Port 12+ 

4 16 A-67 A : Port 12- 

4 17 A-68 N/C 

5 1 A-69 N/C 


5 3 A-71 A : Port 13+ 

5 4 A-72 A : Port 13- 

5 5 A-73 N/C 


5 7 A-75 A : Port 14+ 

5 8 A-76 A : Port 14- 

5 9 A-77 N/C 

5 10 A-78 A : Relay Port 15 

5 11 A-79 A : Port 15+ 

5 12 A-80 A : Port 15- 

12-4




5 13 A-81 N/C 

5 14 A-82 A : Relay Port 16 

5 15 A-83 A : Port 16+ 

5 16 A-84 A : Port 16- 

5 17 A-85 N/C 

6 1 A-86 N/C 


6 3 A-88 A : Port 17+ 

6 4 A-89 A : Port 17- 

6 5 A-90 N/C 


6 7 A-92 A : Port 18+ 

6 8 A-93 A : Port 18- 

6 9 A-94 N/C 

6 10 A-95 A : Relay Port 19 

6 11 A-96 A : Port 19+ 

6 12 A-97 A : Port 19- 

6 13 A-98 N/C 

6 14 A-99 A : Relay Port 20 

6 15 A-100 A : Port 20+ 

6 16 A-101 A : Port 20- 

6 17 A-102 N/C 

7 1 A-103 N/C 

7 2 A-104 A : Relay Port 21 

7 3 A-105 A : Port 21+ 

7 4 A-106 A : Port 21- 

7 5 A-107 N/C 

7 6 A-108 A : Relay Port 22 

7 7 A-109 A : Port 22+ 

7 8 A-110 A : Port 22- 

7 9 A-111 N/C 

7 10 A-112 A : Relay Port 23 

7 11 A-113 A : Port 23+ 

7 12 A-114 A : Port 23- 

7 13 A-115 N/C 

7 14 A-116 A : Relay Port 24 

7 15 A-117 A : Port 24+ 

7 16 A-118 A : Port 24- 

7 17 A-119 N/C 

8 1 A-120 N/C 

8 2 A-121 N/C 

8 3 A-122 N/C 

8 4 A-123 N/C 

8 5 A-124 N/C 

8 6 A-125 N/C 

8 7 A-126 N/C 

8 8 A-127 N/C 

8 9 A-128 N/C 

8 10 A-129 N/C 

8 11 A-130 N/C 

12-5




8 12 A-131 N/C 

8 13 A-132 N/C 

8 14 A-133 N/C 

8 15 A-134 N/C 

8 16 A-135 N/C 

8 17 A-136 N/C 

9 1 A-137 A : Fixture 1 Ready/ 

9 2 A-138 A : GND 

9 3 A-139 A : Fixture 1 Control/ 

9 4 A-140 A : Fixture 2 Ready/ 

9 5 A-141 A : GND 

9 6 A-142 A : Fixture 2 Control/ 

9 7 A-143 A : Probe Input 

9 8 A-144 N/C 

9 9 A-145 A : I2C Clock1 

9 10 A-146 A : GND 

9 11 A-147 A : I2C Data1 

9 12 A-148 A : GND 

9 13 A-149 A : RXD (MW1 TXD) 

9 14 A-150 A : GND 

9 15 A-151 A : TXD (MW1 RXD) 

9 16 A-152 A : Fixture Present/ 

9 17 A-153 N/C 

10 1 A-154 A : HUB PS+ 

10 2 A-155 A : HUB PS- 

10 3 A-156 N/C 

10 4 A-157 A : +24Vdc SW1 

10 5 A-158 N/C 

10 6 A-159 A : +12Vdc SW1 

10 7 A-160 N/C 

10 8 A-161 A : +5Vdc SW1 

10 9 A-162 N/C 

10 10 A-163 N/C 

10 11 A-164 N/C 

10 12 A-165 N/C 

10 13 A-166 N/C 

10 14 A-167 N/C 

10 15 A-168 N/C 

10 16 A-169 N/C 

10 17 A-170 N/C 

Note: If Fixture Present/ (Fixture Receiver pin A-152) is not connected to the MW FIX IO 

module or to a GND pin, the PS-UUT switched power outputs (+5Vdc SW, +12Vdc SW, and 

+24Vdc SW) will not be enabled and switched power will not be available to the fixture. 

Block B Pin-Out (Ports 25:48) 


1 1 B-1 B : C+ Ports 25:48 

1 2 B-2 B : C– Ports 25:48 

1 3 B-3 B : M+ Ports 25:48 

12-6




1 4 B-4 B : M– Ports 25:48 

1 5 B-5 B : I+ Ports 25:48 

1 6 B-6 B : I– Ports 25:48 

1 7 B-7 B : E+ Ports 25:48 

1 8 B-8 B : E– Ports 25:48 

1 9 B-9 N/C 

1 10 B-10 N/C 

1 11 B-11 N/C 

1 12 B-12 N/C 

1 13 B-13 N/C 

1 14 B-14 N/C 

1 15 B-15 N/C 

1 16 B-16 N/C 

1 17 B-17 N/C 

2 1 B-18 N/C 

2 2 B-19 B : Relay Port 25 

2 3 B-20 B : Port 25+ 

2 4 B-21 B : Port 25- 

2 5 B-22 N/C 


2 7 B-24 B : Port 26+ 

2 8 B-25 B : Port 26- 

2 9 B-26 N/C 

2 10 B-27 B : Relay Port 27 

2 11 B-28 B : Port 27+ 

2 12 B-29 B : Port 27- 

2 13 B-30 N/C 

2 14 B-31 B : Relay Port 28 

2 15 B-32 B : Port 28+ 

2 16 B-33 B : Port 28- 

2 17 B-34 N/C 

3 1 B-35 N/C 


3 3 B-37 B : Port 29+ 

3 4 B-38 B : Port 29- 

3 5 B-39 N/C 


3 7 B-41 B : Port 30+ 

3 8 B-42 B : Port 30- 

3 9 B-43 N/C 

3 10 B-44 B : Relay Port 31 

3 11 B-45 B : Port 31+ 

3 12 B-46 B : Port 31- 

3 13 B-47 N/C 

3 14 B-48 B : Relay Port 32 

3 15 B-49 B : Port 32+ 

3 16 B-50 B : Port 32- 

3 17 B-51 N/C 

4 1 B-52 N/C 


12-7




4 3 B-54 B : Port 33+ 

4 4 B-55 B : Port 33- 

4 5 B-56 N/C 


4 7 B-58 B : Port 34+ 

4 8 B-59 B : Port 34- 

4 9 B-60 N/C 

4 10 B-61 B : Relay Port 35 

4 11 B-62 B : Port 35+ 

4 12 B-63 B : Port 35- 

4 13 B-64 N/C 

4 14 B-65 B : Relay Port 36 

4 15 B-66 B : Port 36+ 

4 16 B-67 B : Port 36- 

4 17 B-68 N/C 

5 1 B-69 N/C 


5 3 B-71 B : Port 37+ 

5 4 B-72 B : Port 37- 

5 5 B-73 N/C 


5 7 B-75 B : Port 38+ 

5 8 B-76 B : Port 38- 

5 9 B-77 N/C 

5 10 B-78 B : Relay Port 39 

5 11 B-79 B : Port 39+ 

5 12 B-80 B : Port 39- 

5 13 B-81 N/C 

5 14 B-82 B : Relay Port 40 

5 15 B-83 B : Port 40+ 

5 16 B-84 B : Port 40- 

5 17 B-85 N/C 

6 1 B-86 N/C 


6 3 B-88 B : Port 41+ 

6 4 B-89 B : Port 41- 

6 5 B-90 N/C 


6 7 B-92 B : Port 42+ 

6 8 B-93 B : Port 42- 

6 9 B-94 N/C 

6 10 B-95 B : Relay Port 43 

6 11 B-96 B : Port 43+ 

6 12 B-97 B : Port 43- 

6 13 B-98 N/C 

6 14 B-99 B : Relay Port 44 

6 15 B-100 B : Port 44+ 

6 16 B-101 B : Port 44- 

6 17 B-102 N/C 

7 1 B-103 N/C 

12-8




7 2 B-104 B : Relay Port 45 

7 3 B-105 B : Port 45+ 

7 4 B-106 B : Port 45- 

7 5 B-107 N/C 

7 6 B-108 B : Relay Port 46 

7 7 B-109 B : Port 46+ 

7 8 B-110 B : Port 46- 

7 9 B-111 N/C 

7 10 B-112 B : Relay Port 47 

7 11 B-113 B : Port 47+ 

7 12 B-114 B : Port 47- 

7 13 B-115 N/C 

7 14 B-116 B : Relay Port 48 

7 15 B-117 B : Port 48+ 

7 16 B-118 B : Port 48- 

7 17 B-119 N/C 

8 1 B-120 N/C 

8 2 B-121 N/C 

8 3 B-122 N/C 

8 4 B-123 N/C 

8 5 B-124 N/C 

8 6 B-125 N/C 

8 7 B-126 N/C 

8 8 B-127 N/C 

8 9 B-128 N/C 

8 10 B-129 N/C 

8 11 B-130 N/C 

8 12 B-131 N/C 

8 13 B-132 N/C 

8 14 B-133 N/C 

8 15 B-134 N/C 

8 16 B-135 N/C 

8 17 B-136 N/C 

9 1 B-137 N/C 

9 2 B-138 N/C 

9 3 B-139 N/C 

9 4 B-140 N/C 

9 5 B-141 N/C 

9 6 B-142 N/C 

9 7 B-143 N/C 

9 8 B-144 N/C 

9 9 B-145 B : I2C Clock2 

9 10 B-146 B : GND 

9 11 B-147 B : I2C Data2 

9 12 B-148 B : GND 

9 13 B-149 B : RXD (MW2 TXD) 

9 14 B-150 B : GND 

9 15 B-151 B : TXD (MW2 RXD) 

9 16 B-152 B : GND 

9 17 B-153 N/C 

12-9




10 1 B-154 N/C 

10 2 B-155 N/C 

10 3 B-156 N/C 

10 4 B-157 B : +24Vdc SW2 

10 5 B-158 N/C 

10 6 B-159 B : +12Vdc SW2 

10 7 B-160 N/C 

10 8 B-161 B : +5Vdc SW2 

10 9 B-162 N/C 

10 10 B-163 B : GND 

10 11 B-164 N/C 

10 12 B-165 N/C 

10 13 B-166 N/C 

10 14 B-167 N/C 

10 15 B-168 N/C 

10 16 B-169 N/C 

10 17 B-170 N/C 

Block C Pin-Out (Ports 49:72) 


1 1 C-1 C : C+ Ports 49:72 

1 2 C-2 C : C– Ports 49:72 

1 3 C-3 C : M+ Ports 49:72 

1 4 C-4 C : M– Ports 49:72 

1 5 C-5 C : I+ Ports 49:72 

1 6 C-6 C : I– Ports 49:72 

1 7 C-7 C : E+ Ports 49:72 

1 8 C-8 C : E– Ports 49:72 

1 9 C-9 N/C 

1 10 C-10 N/C 

1 11 C-11 N/C 

1 12 C-12 N/C 

1 13 C-13 N/C 

1 14 C-14 N/C 

1 15 C-15 N/C 

1 16 C-16 N/C 

1 17 C-17 N/C 

2 1 C-18 N/C 

2 2 C-19 C : Relay Port 49 

2 3 C-20 C : Port 49+ 

2 4 C-21 C : Port 49- 

2 5 C-22 N/C 


2 7 C-24 C : Port 50+ 

2 8 C-25 C : Port 50- 

2 9 C-26 N/C 

2 10 C-27 C : Relay Port 51 

2 11 C-28 C : Port 51+ 

2 12 C-29 C : Port 51- 

12-10




2 13 C-30 N/C 

2 14 C-31 C : Relay Port 52 

2 15 C-32 C : Port 52+ 

2 16 C-33 C : Port 52- 

2 17 C-34 N/C 

3 1 C-35 N/C 


3 3 C-37 C : Port 53+ 

3 4 C-38 C : Port 53- 

3 5 C-39 N/C 


3 7 C-41 C : Port 54+ 

3 8 C-42 C : Port 54- 

3 9 C-43 N/C 

3 10 C-44 C : Relay Port 55 

3 11 C-45 C : Port 55+ 

3 12 C-46 C : Port 55- 

3 13 C-47 N/C 

3 14 C-48 C : Relay Port 56 

3 15 C-49 C : Port 56+ 

3 16 C-50 C : Port 56- 

3 17 C-51 N/C 

4 1 C-52 N/C 


4 3 C-54 C : Port 57+ 

4 4 C-55 C : Port 57- 

4 5 C-56 N/C 


4 7 C-58 C : Port 58+ 

4 8 C-59 C : Port 58- 

4 9 C-60 N/C 

4 10 C-61 C : Relay Port 59 

4 11 C-62 C : Port 59+ 

4 12 C-63 C : Port 59- 

4 13 C-64 N/C 

4 14 C-65 C : Relay Port 60 

4 15 C-66 C : Port 60+ 

4 16 C-67 C : Port 60- 

4 17 C-68 N/C 

5 1 C-69 N/C 


5 3 C-71 C : Port 61+ 

5 4 C-72 C : Port 61- 

5 5 C-73 N/C 


5 7 C-75 C : Port 62+ 

5 8 C-76 C : Port 62- 

5 9 C-77 N/C 

5 10 C-78 C : Relay Port 63 

5 11 C-79 C : Port 63+ 

12-11




5 12 C-80 C : Port 63- 

5 13 C-81 N/C 

5 14 C-82 C : Relay Port 64 

5 15 C-83 C : Port 64+ 

5 16 C-84 C : Port 64- 

5 17 C-85 N/C 

6 1 C-86 N/C 


6 3 C-88 C : Port 65+ 

6 4 C-89 C : Port 65- 

6 5 C-90 N/C 


6 7 C-92 C : Port 66+ 

6 8 C-93 C : Port 66- 

6 9 C-94 N/C 

6 10 C-95 C : Relay Port 67 

6 11 C-96 C : Port 67+ 

6 12 C-97 C : Port 67- 

6 13 C-98 N/C 

6 14 C-99 C : Relay Port 68 

6 15 C-100 C : Port 68+ 

6 16 C-101 C : Port 68- 

6 17 C-102 N/C 

7 1 C-103 N/C 

7 2 C-104 C : Relay Port 69 

7 3 C-105 C : Port 69+ 

7 4 C-106 C : Port 69- 

7 5 C-107 N/C 

7 6 C-108 C : Relay Port 70 

7 7 C-109 C : Port 70+ 

7 8 C-110 C : Port 70- 

7 9 C-111 N/C 

7 10 C-112 C : Relay Port 71 

7 11 C-113 C : Port 71+ 

7 12 C-114 C : Port 71- 

7 13 C-115 N/C 

7 14 C-116 C : Relay Port 72 

7 15 C-117 C : Port 72+ 

7 16 C-118 C : Port 72- 

7 17 C-119 N/C 

8 1 C-120 N/C 

8 2 C-121 N/C 

8 3 C-122 N/C 

8 4 C-123 N/C 

8 5 C-124 N/C 

8 6 C-125 N/C 

8 7 C-126 N/C 

8 8 C-127 N/C 

8 9 C-128 N/C 

8 10 C-129 N/C 

12-12




8 11 C-130 N/C 

8 12 C-131 N/C 

8 13 C-132 N/C 

8 14 C-133 N/C 

8 15 C-134 N/C 

8 16 C-135 N/C 

8 17 C-136 N/C 

9 1 C-137 N/C 

9 2 C-138 N/C 

9 3 C-139 N/C 

9 4 C-140 N/C 

9 5 C-141 N/C 

9 6 C-142 N/C 

9 7 C-143 N/C 

9 8 C-144 N/C 

9 9 C-145 C : I2C Clock3 

9 10 C-146 C : GND 

9 11 C-147 C : I2C Data3 

9 12 C-148 C : GND 

9 13 C-149 C : RXD (MW3 TXD) 

9 14 C-150 C : GND 

9 15 C-151 C : TXD (MW3 RXD) 

9 16 C-152 C : GND 

9 17 C-153 N/C 

10 1 C-154 N/C 

10 2 C-155 N/C 

10 3 C-156 N/C 

10 4 C-157 C : +24Vdc SW3 

10 5 C-158 N/C 

10 6 C-159 C : +12Vdc SW3 

10 7 C-160 N/C 

10 8 C-161 C : +5Vdc SW3 

10 9 C-162 N/C 

10 10 C-163 C : GND 

10 11 C-164 N/C 

10 12 C-165 N/C 

10 13 C-166 N/C 

10 14 C-167 N/C 

10 15 C-168 N/C 

10 16 C-169 N/C 

10 17 C-170 N/C 

Block D Pin-Out (Ports 73:96) 


1 1 D-1 D : C+ Ports 73:96 

1 2 D-2 D : C– Ports 73:96 

1 3 D-3 D : M+ Ports 73:96 

1 4 D-4 D : M– Ports 73:96 

1 5 D-5 D : I+ Ports 73:96 

12-13




1 6 D-6 D : I– Ports 73:96 

1 7 D-7 D : E+ Ports 73:96 

1 8 D-8 D : E– Ports 73:96 

1 9 D-9 N/C 

1 10 D-10 N/C 

1 11 D-11 N/C 

1 12 D-12 N/C 

1 13 D-13 N/C 

1 14 D-14 N/C 

1 15 D-15 N/C 

1 16 D-16 N/C 

1 17 D-17 N/C 

2 1 D-18 N/C 

2 2 D-19 D : Relay Port 73 

2 3 D-20 D : Port 73+ 

2 4 D-21 D : Port 73- 

2 5 D-22 N/C 


2 7 D-24 D : Port 74+ 

2 8 D-25 D : Port 74- 

2 9 D-26 N/C 

2 10 D-27 D : Relay Port 75 

2 11 D-28 D : Port 75+ 

2 12 D-29 D : Port 75- 

2 13 D-30 N/C 

2 14 D-31 D : Relay Port 76 

2 15 D-32 D : Port 76+ 

2 16 D-33 D : Port 76- 

2 17 D-34 N/C 

3 1 D-35 N/C 


3 3 D-37 D : Port 77+ 

3 4 D-38 D : Port 77- 

3 5 D-39 N/C 


3 7 D-41 D : Port 78+ 

3 8 D-42 D : Port 78- 

3 9 D-43 N/C 

3 10 D-44 D : Relay Port 79 

3 11 D-45 D : Port 79+ 

3 12 D-46 D : Port 79- 

3 13 D-47 N/C 

3 14 D-48 D : Relay Port 80 

3 15 D-49 D : Port 80+ 

3 16 D-50 D : Port 80- 

3 17 D-51 N/C 

4 1 D-52 N/C 


4 3 D-54 D : Port 81+ 

4 4 D-55 D : Port 81- 

12-14




4 5 D-56 N/C 


4 7 D-58 D : Port 82+ 

4 8 D-59 D : Port 82- 

4 9 D-60 N/C 

4 10 D-61 D : Relay Port 83 

4 11 D-62 D : Port 83+ 

4 12 D-63 D : Port 83- 

4 13 D-64 N/C 

4 14 D-65 D : Relay Port 84 

4 15 D-66 D : Port 84+ 

4 16 D-67 D : Port 84- 

4 17 D-68 N/C 

5 1 D-69 N/C 


5 3 D-71 D : Port 85+ 

5 4 D-72 D : Port 85- 

5 5 D-73 N/C 


5 7 D-75 D : Port 86+ 

5 8 D-76 D : Port 86- 

5 9 D-77 N/C 

5 10 D-78 D : Relay Port 87 

5 11 D-79 D : Port 87+ 

5 12 D-80 D : Port 87- 

5 13 D-81 N/C 

5 14 D-82 D : Relay Port 88 

5 15 D-83 D : Port 88+ 

5 16 D-84 D : Port 88- 

5 17 D-85 N/C 

6 1 D-86 N/C 


6 3 D-88 D : Port 89+ 

6 4 D-89 D : Port 89- 

6 5 D-90 N/C 


6 7 D-92 D : Port 90+ 

6 8 D-93 D : Port 90- 

6 9 D-94 N/C 

6 10 D-95 D : Relay Port 91 

6 11 D-96 D : Port 91+ 

6 12 D-97 D : Port 91- 

6 13 D-98 N/C 

6 14 D-99 D : Relay Port 92 

6 15 D-100 D : Port 92+ 

6 16 D-101 D : Port 92- 

6 17 D-102 N/C 

7 1 D-103 N/C 

7 2 D-104 D : Relay Port 93 

7 3 D-105 D : Port 93+ 

12-15




7 4 D-106 D : Port 93- 

7 5 D-107 N/C 

7 6 D-108 D : Relay Port 94 

7 7 D-109 D : Port 94+ 

7 8 D-110 D : Port 94- 

7 9 D-111 N/C 

7 10 D-112 D : Relay Port 95 

7 11 D-113 D : Port 95+ 

7 12 D-114 D : Port 95- 

7 13 D-115 N/C 

7 14 D-116 D : Relay Port 96 

7 15 D-117 D : Port 96+ 

7 16 D-118 D : Port 96- 

7 17 D-119 N/C 

8 1 D-120 N/C 

8 2 D-121 N/C 

8 3 D-122 N/C 

8 4 D-123 N/C 

8 5 D-124 N/C 

8 6 D-125 N/C 

8 7 D-126 N/C 

8 8 D-127 N/C 

8 9 D-128 N/C 

8 10 D-129 N/C 

8 11 D-130 N/C 

8 12 D-131 N/C 

8 13 D-132 N/C 

8 14 D-133 N/C 

8 15 D-134 N/C 

8 16 D-135 N/C 

8 17 D-136 N/C 

9 1 D-137 N/C 

9 2 D-138 N/C 

9 3 D-139 N/C 

9 4 D-140 N/C 

9 5 D-141 N/C 

9 6 D-142 N/C 

9 7 D-143 N/C 

9 8 D-144 N/C 

9 9 D-145 D : I2C Clock4 

9 10 D-146 D : GND 

9 11 D-147 D : I2C Data4 

9 12 D-148 D : GND 

9 13 D-149 D : RXD (MW4 TXD) 

9 14 D-150 D : GND 

9 15 D-151 D : TXD (MW4 RXD) 

9 16 D-152 D : GND 

9 17 D-153 N/C 

10 1 D-154 N/C 

10 2 D-155 N/C 

12-16




10 3 D-156 N/C 

10 4 D-157 D : +24Vdc SW4 

10 5 D-158 N/C 

10 6 D-159 D : +12Vdc SW4 

10 7 D-160 N/C 

10 8 D-161 D : +5Vdc SW4 

10 9 D-162 N/C 

10 10 D-163 D : GND 

10 11 D-164 N/C 

10 12 D-165 N/C 

10 13 D-166 N/C 

10 14 D-167 N/C 

10 15 D-168 N/C 

10 16 D-169 N/C 

10 17 D-170 N/C 

Block E Pin-Out (Ports 97:120) 


1 1 E-1 E : C+ Ports 97:120 

1 2 E-2 E : C– Ports 97:120 

1 3 E-3 E : M+ Ports 97:120 

1 4 E-4 E : M– Ports 97:120 

1 5 E-5 E : I+ Ports 97:120 

1 6 E-6 E : I– Ports 97:120 

1 7 E-7 E : E+ Ports 97:120 

1 8 E-8 E : E– Ports 97:120 

1 9 E-9 N/C 

1 10 E-10 N/C 

1 11 E-11 N/C 

1 12 E-12 N/C 

1 13 E-13 N/C 

1 14 E-14 N/C 

1 15 E-15 N/C 

1 16 E-16 N/C 

1 17 E-17 N/C 

2 1 E-18 N/C 

2 2 E-19 E : Relay Port 97 

2 3 E-20 E : Port 97+ 

2 4 E-21 E : Port 97- 

2 5 E-22 N/C 

2 6 E-23 E : Relay Port 98 

2 7 E-24 E : Port 98+ 

2 8 E-25 E : Port 98- 

2 9 E-26 N/C 

2 10 E-27 E : Relay Port 99 

2 11 E-28 E : Port 99+ 

2 12 E-29 E : Port 99- 

2 13 E-30 N/C 

2 14 E-31 E : Relay Port 100 

12-17




2 15 E-32 E : Port 100+ 

2 16 E-33 E : Port 100- 

2 17 E-34 N/C 

3 1 E-35 N/C 

3 2 E-36 E : Relay Port 101 

3 3 E-37 E : Port 101+ 

3 4 E-38 E : Port 101- 

3 5 E-39 N/C 

3 6 E-40 E : Relay Port 102 

3 7 E-41 E : Port 102+ 

3 8 E-42 E : Port 102- 

3 9 E-43 N/C 

3 10 E-44 E : Relay Port 103 

3 11 E-45 E : Port 103+ 

3 12 E-46 E : Port 103- 

3 13 E-47 N/C 

3 14 E-48 E : Relay Port 104 

3 15 E-49 E : Port 104+ 

3 16 E-50 E : Port 104- 

3 17 E-51 N/C 

4 1 E-52 N/C 

4 2 E-53 E : Relay Port 105 

4 3 E-54 E : Port 105+ 

4 4 E-55 E : Port 105- 

4 5 E-56 N/C 

4 6 E-57 E : Relay Port 106 

4 7 E-58 E : Port 106+ 

4 8 E-59 E : Port 106- 

4 9 E-60 N/C 

4 10 E-61 E : Relay Port 107 

4 11 E-62 E : Port 107+ 

4 12 E-63 E : Port 107- 

4 13 E-64 N/C 

4 14 E-65 E : Relay Port 108 

4 15 E-66 E : Port 108+ 

4 16 E-67 E : Port 108- 

4 17 E-68 N/C 

5 1 E-69 N/C 

5 2 E-70 E : Relay Port 109 

5 3 E-71 E : Port 109+ 

5 4 E-72 E : Port 109- 

5 5 E-73 N/C 

5 6 E-74 E : Relay Port 110 

5 7 E-75 E : Port 110+ 

5 8 E-76 E : Port 110- 

5 9 E-77 N/C 

5 10 E-78 E : Relay Port 111 

5 11 E-79 E : Port 111+ 

5 12 E-80 E : Port 111- 

5 13 E-81 N/C 

12-18




5 14 E-82 E : Relay Port 112 

5 15 E-83 E : Port 112+ 

5 16 E-84 E : Port 112- 

5 17 E-85 N/C 

6 1 E-86 N/C 

6 2 E-87 E : Relay Port 113 

6 3 E-88 E : Port 113+ 

6 4 E-89 E : Port 113- 

6 5 E-90 N/C 

6 6 E-91 E : Relay Port 114 

6 7 E-92 E : Port 114+ 

6 8 E-93 E : Port 114- 

6 9 E-94 N/C 

6 10 E-95 E : Relay Port 115 

6 11 E-96 E : Port 115+ 

6 12 E-97 E : Port 115- 

6 13 E-98 N/C 

6 14 E-99 E : Relay Port 116 

6 15 E-100 E : Port 116+ 

6 16 E-101 E : Port 116- 

6 17 E-102 N/C 

7 1 E-103 N/C 

7 2 E-104 E : Relay Port 117 

7 3 E-105 E : Port 117+ 

7 4 E-106 E : Port 117- 

7 5 E-107 N/C 

7 6 E-108 E : Relay Port 118 

7 7 E-109 E : Port 118+ 

7 8 E-110 E : Port 118- 

7 9 E-111 N/C 

7 10 E-112 E : Relay Port 119 

7 11 E-113 E : Port 119+ 

7 12 E-114 E : Port 119- 

7 13 E-115 N/C 

7 14 E-116 E : Relay Port 120 

7 15 E-117 E : Port 120+ 

7 16 E-118 E : Port 120- 

7 17 E-119 N/C 

8 1 E-120 N/C 

8 2 E-121 N/C 

8 3 E-122 N/C 

8 4 E-123 N/C 

8 5 E-124 N/C 

8 6 E-125 N/C 

8 7 E-126 N/C 

8 8 E-127 N/C 

8 9 E-128 N/C 

8 10 E-129 N/C 

8 11 E-130 N/C 

8 12 E-131 N/C 

12-19




8 13 E-132 N/C 

8 14 E-133 N/C 

8 15 E-134 N/C 

8 16 E-135 N/C 

8 17 E-136 N/C 

9 1 E-137 N/C 

9 2 E-138 N/C 

9 3 E-139 N/C 

9 4 E-140 N/C 

9 5 E-141 N/C 

9 6 E-142 N/C 

9 7 E-143 N/C 

9 8 E-144 N/C 

9 9 E-145 E : I2C Clock5 

9 10 E-146 E : GND 

9 11 E-147 E : I2C Data5 

9 12 E-148 E : GND 

9 13 E-149 E : RXD (MW5 TXD) 

9 14 E-150 E : GND 

9 15 E-151 E : TXD (MW5 RXD) 

9 16 E-152 E : Exp Fixture Present/ 

9 17 E-153 N/C 

10 1 E-154 N/C 

10 2 E-155 N/C 

10 3 E-156 N/C 

10 4 E-157 E : +24Vdc SW5 

10 5 E-158 N/C 

10 6 E-159 E : +12Vdc SW5 

10 7 E-160 N/C 

10 8 E-161 E : +5Vdc SW5 

10 9 E-162 N/C 

10 10 E-163 E : GND 

10 11 E-164 N/C 

10 12 E-165 N/C 

10 13 E-166 N/C 

10 14 E-167 N/C 

10 15 E-168 N/C 

10 16 E-169 N/C 

10 17 E-170 N/C 

Note: If Exp Fixture Present/ (Fixture Receiver pin E-152) is not connected to the MW FIX 

IO module or to a GND pin, the PS-UUT switched power outputs (+5Vdc SW, +12Vdc SW, 

and +24Vdc SW) will not be enabled and switched power will not be available to the fixture 

for outputs SW5 to SW8. 

Block F Pin-Out (Ports 121:144) 


1 1 F-1 F : C+ Ports 121:144 

1 2 F-2 F : C– Ports 121:144 

1 3 F-3 F : M+ Ports 121:144 

12-20




1 4 F-4 F : M– Ports 121:144 

1 5 F-5 F : I+ Ports 121:144 

1 6 F-6 F : I– Ports 121:144 

1 7 F-7 F : E+ Ports 121:144 

1 8 F-8 F : E– Ports 121:144 

1 9 F-9 N/C 

1 10 F-10 N/C 

1 11 F-11 N/C 

1 12 F-12 N/C 

1 13 F-13 N/C 

1 14 F-14 N/C 

1 15 F-15 N/C 

1 16 F-16 N/C 

1 17 F-17 N/C 

2 1 F-18 N/C 

2 2 F-19 F : Relay Port 121 

2 3 F-20 F : Port 121+ 

2 4 F-21 F : Port 121- 

2 5 F-22 N/C 

2 6 F-23 F : Relay Port 122 

2 7 F-24 F : Port 122+ 

2 8 F-25 F : Port 122- 

2 9 F-26 N/C 

2 10 F-27 F : Relay Port 123 

2 11 F-28 F : Port 123+ 

2 12 F-29 F : Port 123- 

2 13 F-30 N/C 

2 14 F-31 F : Relay Port 124 

2 15 F-32 F : Port 124+ 

2 16 F-33 F : Port 124- 

2 17 F-34 N/C 

3 1 F-35 N/C 

3 2 F-36 F : Relay Port 125 

3 3 F-37 F : Port 125+ 

3 4 F-38 F : Port 125- 

3 5 F-39 N/C 

3 6 F-40 F : Relay Port 126 

3 7 F-41 F : Port 126+ 

3 8 F-42 F : Port 126- 

3 9 F-43 N/C 

3 10 F-44 F : Relay Port 127 

3 11 F-45 F : Port 127+ 

3 12 F-46 F : Port 127- 

3 13 F-47 N/C 

3 14 F-48 F : Relay Port 128 

3 15 F-49 F : Port 128+ 

3 16 F-50 F : Port 128- 

3 17 F-51 N/C 

4 1 F-52 N/C 

4 2 F-53 F : Relay Port 129 

12-21




4 3 F-54 F : Port 129+ 

4 4 F-55 F : Port 129- 

4 5 F-56 N/C 

4 6 F-57 F : Relay Port 130 

4 7 F-58 F : Port 130+ 

4 8 F-59 F : Port 130- 

4 9 F-60 N/C 

4 10 F-61 F : Relay Port 131 

4 11 F-62 F : Port 131+ 

4 12 F-63 F : Port 131- 

4 13 F-64 N/C 

4 14 F-65 F : Relay Port 132 

4 15 F-66 F : Port 132+ 

4 16 F-67 F : Port 132- 

4 17 F-68 N/C 

5 1 F-69 N/C 

5 2 F-70 F : Relay Port 133 

5 3 F-71 F : Port 133+ 

5 4 F-72 F : Port 133- 

5 5 F-73 N/C 

5 6 F-74 F : Relay Port 134 

5 7 F-75 F : Port 134+ 

5 8 F-76 F : Port 134- 

5 9 F-77 N/C 

5 10 F-78 F : Relay Port 135 

5 11 F-79 F : Port 135+ 

5 12 F-80 F : Port 135- 

5 13 F-81 N/C 

5 14 F-82 F : Relay Port 136 

5 15 F-83 F : Port 136+ 

5 16 F-84 F : Port 136- 

5 17 F-85 N/C 

6 1 F-86 N/C 

6 2 F-87 F : Relay Port 137 

6 3 F-88 F : Port 137+ 

6 4 F-89 F : Port 137- 

6 5 F-90 N/C 

6 6 F-91 F : Relay Port 138 

6 7 F-92 F : Port 138+ 

6 8 F-93 F : Port 138- 

6 9 F-94 N/C 

6 10 F-95 F : Relay Port 139 

6 11 F-96 F : Port 139+ 

6 12 F-97 F : Port 139- 

6 13 F-98 N/C 

6 14 F-99 F : Relay Port 140 

6 15 F-100 F : Port 140+ 

6 16 F-101 F : Port 140- 

6 17 F-102 N/C 

7 1 F-103 N/C 

12-22




7 2 F-104 F : Relay Port 141 

7 3 F-105 F : Port 141+ 

7 4 F-106 F : Port 141- 

7 5 F-107 N/C 

7 6 F-108 F : Relay Port 142 

7 7 F-109 F : Port 142+ 

7 8 F-110 F : Port 142- 

7 9 F-111 N/C 

7 10 F-112 F : Relay Port 143 

7 11 F-113 F : Port 143+ 

7 12 F-114 F : Port 143- 

7 13 F-115 N/C 

7 14 F-116 F : Relay Port 144 

7 15 F-117 F : Port 144+ 

7 16 F-118 F : Port 144- 

7 17 F-119 N/C 

8 1 F-120 N/C 

8 2 F-121 N/C 

8 3 F-122 N/C 

8 4 F-123 N/C 

8 5 F-124 N/C 

8 6 F-125 N/C 

8 7 F-126 N/C 

8 8 F-127 N/C 

8 9 F-128 N/C 

8 10 F-129 N/C 

8 11 F-130 N/C 

8 12 F-131 N/C 

8 13 F-132 N/C 

8 14 F-133 N/C 

8 15 F-134 N/C 

8 16 F-135 N/C 

8 17 F-136 N/C 

9 1 F-137 N/C 

9 2 F-138 N/C 

9 3 F-139 N/C 

9 4 F-140 N/C 

9 5 F-141 N/C 

9 6 F-142 N/C 

9 7 F-143 N/C 

9 8 F-144 N/C 

9 9 F-145 F : I2C Clock6 

9 10 F-146 F : GND 

9 11 F-147 F : I2C Data6 

9 12 F-148 F : GND 

9 13 F-149 F : RXD (MW6 TXD) 

9 14 F-150 F : GND 

9 15 F-151 F : TXD (MW6 RXD) 

9 16 F-152 F : GND 

9 17 F-153 N/C 

12-23




10 1 F-154 N/C 

10 2 F-155 N/C 

10 3 F-156 N/C 

10 4 F-157 F : +24Vdc SW6 

10 5 F-158 N/C 

10 6 F-159 F : +12Vdc SW6 

10 7 F-160 N/C 

10 8 F-161 F : +5Vdc SW6 

10 9 F-162 N/C 

10 10 F-163 F : GND 

10 11 F-164 N/C 

10 12 F-165 N/C 

10 13 F-166 N/C 

10 14 F-167 N/C 

10 15 F-168 N/C 

10 16 F-169 N/C 

10 17 F-170 N/C 

Block G Pin-Out (Ports 145:168) 


1 1 G-1 G : C+ Ports 145:168 

1 2 G-2 G : C– Ports 145:168 

1 3 G-3 G : M+ Ports 145:168 

1 4 G-4 G : M– Ports 145:168 

1 5 G-5 G : I+ Ports 145:168 

1 6 G-6 G : I– Ports 145:168 

1 7 G-7 G : E+ Ports 145:168 

1 8 G-8 G : E– Ports 145:168 

1 9 G-9 N/C 

1 10 G-10 N/C 

1 11 G-11 N/C 

1 12 G-12 N/C 

1 13 G-13 N/C 

1 14 G-14 N/C 

1 15 G-15 N/C 

1 16 G-16 N/C 

1 17 G-17 N/C 

2 1 G-18 N/C 

2 2 G-19 G : Relay Port 145 

2 3 G-20 G : Port 145+ 

2 4 G-21 G : Port 145- 

2 5 G-22 N/C 

2 6 G-23 G : Relay Port 146 

2 7 G-24 G : Port 146+ 

2 8 G-25 G : Port 146- 

2 9 G-26 N/C 

2 10 G-27 G : Relay Port 147 

2 11 G-28 G : Port 147+ 

2 12 G-29 G : Port 147- 

12-24




2 13 G-30 N/C 

2 14 G-31 G : Relay Port 148 

2 15 G-32 G : Port 148+ 

2 16 G-33 G : Port 148- 

2 17 G-34 N/C 

3 1 G-35 N/C 

3 2 G-36 G : Relay Port 149 

3 3 G-37 G : Port 149+ 

3 4 G-38 G : Port 149- 

3 5 G-39 N/C 

3 6 G-40 G : Relay Port 150 

3 7 G-41 G : Port 150+ 

3 8 G-42 G : Port 150- 

3 9 G-43 N/C 

3 10 G-44 G : Relay Port 151 

3 11 G-45 G : Port 151+ 

3 12 G-46 G : Port 151- 

3 13 G-47 N/C 

3 14 G-48 G : Relay Port 152 

3 15 G-49 G : Port 152+ 

3 16 G-50 G : Port 152- 

3 17 G-51 N/C 

4 1 G-52 N/C 

4 2 G-53 G : Relay Port 153 

4 3 G-54 G : Port 153+ 

4 4 G-55 G : Port 153- 

4 5 G-56 N/C 

4 6 G-57 G : Relay Port 154 

4 7 G-58 G : Port 154+ 

4 8 G-59 G : Port 154- 

4 9 G-60 N/C 

4 10 G-61 G : Relay Port 155 

4 11 G-62 G : Port 155+ 

4 12 G-63 G : Port 155- 

4 13 G-64 N/C 

4 14 G-65 G : Relay Port 156 

4 15 G-66 G : Port 156+ 

4 16 G-67 G : Port 156- 

4 17 G-68 N/C 

5 1 G-69 N/C 

5 2 G-70 G : Relay Port 157 

5 3 G-71 G : Port 157+ 

5 4 G-72 G : Port 157- 

5 5 G-73 N/C 

5 6 G-74 G : Relay Port 158 

5 7 G-75 G : Port 158+ 

5 8 G-76 G : Port 158- 

5 9 G-77 N/C 

5 10 G-78 G : Relay Port 159 

5 11 G-79 G : Port 159+ 

12-25




5 12 G-80 G : Port 159- 

5 13 G-81 N/C 

5 14 G-82 G : Relay Port 160 

5 15 G-83 G : Port 160+ 

5 16 G-84 G : Port 160- 

5 17 G-85 N/C 

6 1 G-86 N/C 

6 2 G-87 G : Relay Port 161 

6 3 G-88 G : Port 161+ 

6 4 G-89 G : Port 161- 

6 5 G-90 N/C 

6 6 G-91 G : Relay Port 162 

6 7 G-92 G : Port 162+ 

6 8 G-93 G : Port 162- 

6 9 G-94 N/C 

6 10 G-95 G : Relay Port 163 

6 11 G-96 G : Port 163+ 

6 12 G-97 G : Port 163- 

6 13 G-98 N/C 

6 14 G-99 G : Relay Port 164 

6 15 G-100 G : Port 164+ 

6 16 G-101 G : Port 164- 

6 17 G-102 N/C 

7 1 G-103 N/C 

7 2 G-104 G : Relay Port 165 

7 3 G-105 G : Port 165+ 

7 4 G-106 G : Port 165- 

7 5 G-107 N/C 

7 6 G-108 G : Relay Port 166 

7 7 G-109 G : Port 166+ 

7 8 G-110 G : Port 166- 

7 9 G-111 N/C 

7 10 G-112 G : Relay Port 167 

7 11 G-113 G : Port 167+ 

7 12 G-114 G : Port 167- 

7 13 G-115 N/C 

7 14 G-116 G : Relay Port 168 

7 15 G-117 G : Port 168+ 

7 16 G-118 G : Port 168- 

7 17 G-119 N/C 

8 1 G-120 N/C 

8 2 G-121 N/C 

8 3 G-122 N/C 

8 4 G-123 N/C 

8 5 G-124 N/C 

8 6 G-125 N/C 

8 7 G-126 N/C 

8 8 G-127 N/C 

8 9 G-128 N/C 

8 10 G-129 N/C 

12-26




8 11 G-130 N/C 

8 12 G-131 N/C 

8 13 G-132 N/C 

8 14 G-133 N/C 

8 15 G-134 N/C 

8 16 G-135 N/C 

8 17 G-136 N/C 

9 1 G-137 N/C 

9 2 G-138 N/C 

9 3 G-139 N/C 

9 4 G-140 N/C 

9 5 G-141 N/C 

9 6 G-142 N/C 

9 7 G-143 N/C 

9 8 G-144 N/C 

9 9 G-145 G : I2C Clock7 

9 10 G-146 G : GND 

9 11 G-147 G : I2C Data7 

9 12 G-148 G : GND 

9 13 G-149 G : RXD (MW7 TXD) 

9 14 G-150 G : GND 

9 15 G-151 G : TXD (MW7 RXD) 

9 16 G-152 G : GND 

9 17 G-153 N/C 

10 1 G-154 N/C 

10 2 G-155 N/C 

10 3 G-156 N/C 

10 4 G-157 G : +24Vdc SW7 

10 5 G-158 N/C 

10 6 G-159 G : +12Vdc SW7 

10 7 G-160 N/C 

10 8 G-161 G : +5Vdc SW7 

10 9 G-162 N/C 

10 10 G-163 G : GND 

10 11 G-164 N/C 

10 12 G-165 N/C 

10 13 G-166 N/C 

10 14 G-167 N/C 

10 15 G-168 N/C 

10 16 G-169 N/C 

10 17 G-170 N/C 

Block H Pin-Out (Ports 169:192) 


1 1 H-1 H : C+ Ports 169:192 

1 2 H-2 H : C– Ports 169:192 

1 3 H-3 H : M+ Ports 169:192 

1 4 H-4 H : M– Ports 169:192 

1 5 H-5 H : I+ Ports 169:192 

12-27




1 6 H-6 H : I– Ports 169:192 

1 7 H-7 H : E+ Ports 169:192 

1 8 H-8 H : E– Ports 169:192 

1 9 H-9 N/C 

1 10 H-10 N/C 

1 11 H-11 N/C 

1 12 H-12 N/C 

1 13 H-13 N/C 

1 14 H-14 N/C 

1 15 H-15 N/C 

1 16 H-16 N/C 

1 17 H-17 N/C 

2 1 H-18 N/C 

2 2 H-19 H : Relay Port 169 

2 3 H-20 H : Port 169+ 

2 4 H-21 H : Port 169- 

2 5 H-22 N/C 

2 6 H-23 H : Relay Port 170 

2 7 H-24 H : Port 170+ 

2 8 H-25 H : Port 170- 

2 9 H-26 N/C 

2 10 H-27 H : Relay Port 171 

2 11 H-28 H : Port 171+ 

2 12 H-29 H : Port 171- 

2 13 H-30 N/C 

2 14 H-31 H : Relay Port 172 

2 15 H-32 H : Port 172+ 

2 16 H-33 H : Port 172- 

2 17 H-34 N/C 

3 1 H-35 N/C 

3 2 H-36 H : Relay Port 173 

3 3 H-37 H : Port 173+ 

3 4 H-38 H : Port 173- 

3 5 H-39 N/C 

3 6 H-40 H : Relay Port 174 

3 7 H-41 H : Port 174+ 

3 8 H-42 H : Port 174- 

3 9 H-43 N/C 

3 10 H-44 H : Relay Port 175 

3 11 H-45 H : Port 175+ 

3 12 H-46 H : Port 175- 

3 13 H-47 N/C 

3 14 H-48 H : Relay Port 176 

3 15 H-49 H : Port 176+ 

3 16 H-50 H : Port 176- 

3 17 H-51 N/C 

4 1 H-52 N/C 

4 2 H-53 H : Relay Port 177 

4 3 H-54 H : Port 177+ 

4 4 H-55 H : Port 177- 

12-28




4 5 H-56 N/C 

4 6 H-57 H : Relay Port 178 

4 7 H-58 H : Port 178+ 

4 8 H-59 H : Port 178- 

4 9 H-60 N/C 

4 10 H-61 H : Relay Port 179 

4 11 H-62 H : Port 179+ 

4 12 H-63 H : Port 179- 

4 13 H-64 N/C 

4 14 H-65 H : Relay Port 180 

4 15 H-66 H : Port 180+ 

4 16 H-67 H : Port 180- 

4 17 H-68 N/C 

5 1 H-69 N/C 

5 2 H-70 H : Relay Port 181 

5 3 H-71 H : Port 181+ 

5 4 H-72 H : Port 181- 

5 5 H-73 N/C 

5 6 H-74 H : Relay Port 182 

5 7 H-75 H : Port 182+ 

5 8 H-76 H : Port 182- 

5 9 H-77 N/C 

5 10 H-78 H : Relay Port 183 

5 11 H-79 H : Port 183+ 

5 12 H-80 H : Port 183- 

5 13 H-81 N/C 

5 14 H-82 H : Relay Port 184 

5 15 H-83 H : Port 184+ 

5 16 H-84 H : Port 184- 

5 17 H-85 N/C 

6 1 H-86 N/C 

6 2 H-87 H : Relay Port 185 

6 3 H-88 H : Port 185+ 

6 4 H-89 H : Port 185- 

6 5 H-90 N/C 

6 6 H-91 H : Relay Port 186 

6 7 H-92 H : Port 186+ 

6 8 H-93 H : Port 186- 

6 9 H-94 N/C 

6 10 H-95 H : Relay Port 187 

6 11 H-96 H : Port 187+ 

6 12 H-97 H : Port 187- 

6 13 H-98 N/C 

6 14 H-99 H : Relay Port 188 

6 15 H-100 H : Port 188+ 

6 16 H-101 H : Port 188- 

6 17 H-102 N/C 

7 1 H-103 N/C 

7 2 H-104 H : Relay Port 189 

7 3 H-105 H : Port 189+ 

12-29




7 4 H-106 H : Port 189- 

7 5 H-107 N/C 

7 6 H-108 H : Relay Port 190 

7 7 H-109 H : Port 190+ 

7 8 H-110 H : Port 190- 

7 9 H-111 N/C 

7 10 H-112 H : Relay Port 191 

7 11 H-113 H : Port 191+ 

7 12 H-114 H : Port 191- 

7 13 H-115 N/C 

7 14 H-116 H : Relay Port 192 

7 15 H-117 H : Port 192+ 

7 16 H-118 H : Port 192- 

7 17 H-119 N/C 

8 1 H-120 N/C 

8 2 H-121 N/C 

8 3 H-122 N/C 

8 4 H-123 N/C 

8 5 H-124 N/C 

8 6 H-125 N/C 

8 7 H-126 N/C 

8 8 H-127 N/C 

8 9 H-128 N/C 

8 10 H-129 N/C 

8 11 H-130 N/C 

8 12 H-131 N/C 

8 13 H-132 N/C 

8 14 H-133 N/C 

8 15 H-134 N/C 

8 16 H-135 N/C 

8 17 H-136 N/C 

9 1 H-137 N/C 

9 2 H-138 N/C 

9 3 H-139 N/C 

9 4 H-140 N/C 

9 5 H-141 N/C 

9 6 H-142 N/C 

9 7 H-143 N/C 

9 8 H-144 N/C 

9 9 H-145 H : I2C Clock8 

9 10 H-146 H : GND 

9 11 H-147 H : I2C Data8 

9 12 H-148 H : GND 

9 13 H-149 H : RXD (MW8 TXD) 

9 14 H-150 H : GND 

9 15 H-151 H : TXD (MW8 RXD) 

9 16 H-152 H : GND 

9 17 H-153 N/C 

10 1 H-154 N/C 

10 2 H-155 N/C 

12-30




10 3 H-156 N/C 

10 4 H-157 H : +24Vdc SW8 

10 5 H-158 N/C 

10 6 H-159 H : +12Vdc SW8 

10 7 H-160 N/C 

10 8 H-161 H : +5Vdc SW8 

10 9 H-162 N/C 

10 10 H-163 H : GND 

10 11 H-164 N/C 

10 12 H-165 N/C 

10 13 H-166 N/C 

10 14 H-167 N/C 

10 15 H-168 N/C 

10 16 H-169 N/C 

10 17 H-170 N/C 

Block K Pin-Out (Power Supplies PS#1 to PS#4 and USB security device) 


1 1 K-1 K : PS#1 –V 

1 2 K-2 K : PS#1 –V 

1 3 K-3 K : PS#1 –V 

1 4 K-4 K : PS#1 –V 

1 5 K-5 K : PS#1 –V 

1 6 K-6 K : PS#1 –V 

1 7 K-7 K : PS#1 –V 

1 8 K-8 K : PS#1 –S 

1 9 K-9 K : PS#1 +S 

1 10 K-10 K : PS#1 +V 

1 11 K-11 K : PS#1 +V 

1 12 K-12 K : PS#1 +V 

1 13 K-13 K : PS#1 +V 

1 14 K-14 K : PS#1 +V 

1 15 K-15 K : PS#1 +V 

1 16 K-16 K : PS#1 +V 

1 17 K-17 N/C 

2 1 K-18 K : PS#2 –V 

2 2 K-19 K : PS#2 –V 

2 3 K-20 K : PS#2 –V 

2 4 K-21 K : PS#2 –V 

2 5 K-22 K : PS#2 –V 

2 6 K-23 K : PS#2 –V 

2 7 K-24 K : PS#2 –V 

2 8 K-25 K : PS#2 –S 

2 9 K-26 K : PS#2 +S 

2 10 K-27 K : PS#2 +V 

2 11 K-28 K : PS#2 +V 

2 12 K-29 K : PS#2 +V 

2 13 K-30 K : PS#2 +V 

2 14 K-31 K : PS#2 +V 

12-31




2 15 K-32 K : PS#2 +V 

2 16 K-33 K : PS#2 +V 

2 17 K-34 N/C 

3 1 K-35 K : PS#3 –V 

3 2 K-36 K : PS#3 –V 

3 3 K-37 K : PS#3 –V 

3 4 K-38 K : PS#3 –V 

3 5 K-39 K : PS#3 –V 

3 6 K-40 K : PS#3 –V 

3 7 K-41 K : PS#3 –V 

3 8 K-42 K : PS#3 –S 

3 9 K-43 K : PS#3 +S 

3 10 K-44 K : PS#3 +V 

3 11 K-45 K : PS#3 +V 

3 12 K-46 K : PS#3 +V 

3 13 K-47 K : PS#3 +V 

3 14 K-48 K : PS#3 +V 

3 15 K-49 K : PS#3 +V 

3 16 K-50 K : PS#3 +V 

3 17 K-51 N/C 

4 1 K-52 K : PS#4 –V 

4 2 K-53 K : PS#4 –V 

4 3 K-54 K : PS#4 –V 

4 4 K-55 K : PS#4 –V 

4 5 K-56 K : PS#4 –V 

4 6 K-57 K : PS#4 –V 

4 7 K-58 K : PS#4 –V 

4 8 K-59 K : PS#4 –S 

4 9 K-60 K : PS#4 +S 

4 10 K-61 K : PS#4 +V 

4 11 K-62 K : PS#4 +V 

4 12 K-63 K : PS#4 +V 

4 13 K-64 K : PS#4 +V 

4 14 K-65 K : PS#4 +V 

4 15 K-66 K : PS#4 +V 

4 16 K-67 K : PS#4 +V 

4 17 K-68 N/C 

5 1 K-69 N/C 

5 2 K-70 N/C 

5 3 K-71 N/C 

5 4 K-72 N/C 

5 5 K-73 N/C 

5 6 K-74 N/C 

5 7 K-75 N/C 

5 8 K-76 N/C 

5 9 K-77 N/C 

5 10 K-78 N/C 

5 11 K-79 N/C 

5 12 K-80 N/C 

5 13 K-81 N/C 

12-32




5 14 K-82 N/C 

5 15 K-83 N/C 

5 16 K-84 N/C 

5 17 K-85 N/C 

6 1 K-86 N/C 

6 2 K-87 N/C 

6 3 K-88 N/C 

6 4 K-89 N/C 

6 5 K-90 N/C 

6 6 K-91 N/C 

6 7 K-92 N/C 

6 8 K-93 N/C 

6 9 K-94 N/C 

6 10 K-95 N/C 

6 11 K-96 N/C 

6 12 K-97 N/C 

6 13 K-98 N/C 

6 14 K-99 N/C 

6 15 K-100 N/C 

6 16 K-101 N/C 

6 17 K-102 N/C 

7 1 K-103 N/C 

7 2 K-104 N/C 

7 3 K-105 N/C 

7 4 K-106 N/C 

7 5 K-107 N/C 

7 6 K-108 N/C 

7 7 K-109 N/C 

7 8 K-110 N/C 

7 9 K-111 N/C 

7 10 K-112 N/C 

7 11 K-113 N/C 

7 12 K-114 N/C 

7 13 K-115 N/C 

7 14 K-116 N/C 

7 15 K-117 N/C 

7 16 K-118 N/C 

7 17 K-119 N/C 

8 1 K-120 N/C 

8 2 K-121 N/C 

8 3 K-122 N/C 

8 4 K-123 N/C 

8 5 K-124 N/C 

8 6 K-125 N/C 

8 7 K-126 N/C 

8 8 K-127 N/C 

8 9 K-128 N/C 

8 10 K-129 N/C 

8 11 K-130 N/C 

8 12 K-131 N/C 

12-33




8 13 K-132 N/C 

8 14 K-133 N/C 

8 15 K-134 N/C 

8 16 K-135 N/C 

8 17 K-136 N/C 

9 1 K-137 N/C 

9 2 K-138 N/C 

9 3 K-139 N/C 

9 4 K-140 N/C 

9 5 K-141 N/C 

9 6 K-142 N/C 

9 7 K-143 N/C 

9 8 K-144 N/C 

9 9 K-145 N/C 

9 10 K-146 N/C 

9 11 K-147 N/C 

9 12 K-148 N/C 

9 13 K-149 N/C 

9 14 K-150 N/C 

9 15 K-151 N/C 

9 16 K-152 N/C 

9 17 K-153 N/C 

10 1 K-154 N/C 

10 2 K-155 N/C 

10 3 K-156 N/C 

10 4 K-157 N/C 

10 5 K-158 N/C 

10 6 K-159 N/C 

10 7 K-160 N/C 

10 8 K-161 N/C 

10 9 K-162 N/C 

10 10 K-163 N/C 

10 11 K-164 N/C 

10 12 K-165 K : USB Shield 

10 13 K-166 K : USB GND 

10 14 K-167 K : USB D+ 

10 15 K-168 K : USB D– 

10 16 K-169 K : USB VBUS (+5V) 

10 17 K-170 N/C 

Power Block K Notes: 

The “–S“ and “+S” pins are the remote Sense pins. For each power supply, 

connect –S to –V and +S to +V at the load, e.g., connect “PS#1 –S” to 

“PS#1 –V” and also connect “PS#1 +S” to “PS#1 +V”. 

12-34

Chapter 13 

System Power Supplies (PS- 

UUT-L1) 

System Power Supplies (PS-UUT-L1) 

Overview 

The PS-UUT-L1 programmable power supply is used to power-on the assembly with 

programmable devices (DUT or UUT) during ISP. The board or multiple boards (PCBs) are 

all powered-on simultaneously. 

PS-UUT-L1 Model GENH 60 - 12.5 Programmable Power Supply 

Some features of the PS-UUT-L1 programmable power supply: 

• High Power Density 750W in 1U half-rack size 

• Wide Range Input (85 - 265VAC Continuous) 

• Active Power Factor Correction (0.99 typical) 

• Output Voltage up to 60V, Current up to 12.5A 

• Built-in RS-232/RS-485 Interface Standard 

• Side-by-side mounting of two units in a 19-inch rack 

• Worldwide Safety Agency Approvals; CE Mark for LVD and EMC Regulation 

Specifications 

AC Input 85-265 VAC continuous single phase, 47-63 Hz




AC Line Current (100/200VAC): 10.5A/5A 

Active PFC: 0.99 @100/200VAC, rated output power 

Output Characteristics 

Accuracy: 

Voltage Output 

Current Output > 50mA to 12.5A 

Current Output < 50mA 

Vout readback 

Iout readback 

OVP/UVL programming 

Regulation: 

0.01% + 2mV line/load (constant voltage mode) 

0.01% + 2mA line (constant current mode) 

0.01% + 5mA load (constant current mode) 

0.05% of Vout + 30mV 

0.10% of Iout + 25mA 

0.10% of Iout + 50mA 

120mV 

50mA 

600mV 

Protective Features 

Adjustable Over Voltage Protection (OVP) & Under Voltage Limit (UVL) 

Adjustable Current Foldback 

Over-temperature 

Safe/Auto Start 

Front Panel Lock 

Programming Interface 

RS232/RS485 Standard 

Mechanical 

Size: 8.4 in. W x 1.75 in. H x 17 in. D (21.34cm W x 4.445cm H x 43.18cm D) 

Weight: 9.9 lbs / 4.5 kg 

Over Voltage Protection (OVP) 

The OVP circuit protects the load in the event of a remote or local programming error or a 

power supply failure. The protection circuit monitors the voltage at the power supply sense 

points and thus provides the protection level at the load. Upon detection of an Over Voltage 

condition, the power supply output will shut down. 

Under Voltage Limit (UVL) 

The UVL prevents adjustment of the Output Voltage below a certain limit. The combination of 

UVL and OVP functions, allow the user to create a protection window for sensitive load 

circuitry. 

Foldback Protection 

Foldback protection will shut down the power supply output if the load current exceeds the 

current limit setting level. This protection is useful when the load circuitry is sensitive to an 

overcurrent condition. 

There are numerous power supply connections possible at the fixture interface block, see 

PS-UUT-L1 program control commands: 

• DCV - DC Voltage Output on page 14-4 

• DCI - DC Current Limit Output on page 14-4 

• PWRMN - Power Monitor on page 14-5 

13-2



Installing the Power Supplies 

• JMPWR - Jump based on Power Monitor Results on page 14-11 

Separate PCBs can be skipped and these boards will not be connected to the system power 

supply. This is needed when some boards in a panel are not defect-free and applying power 

may damage the board. A panel is simply a set of boards that may be connected. Panels of 

duplicate or similar boards are a common method to manufacture the assemblies. The power 

applied can be current limited under program control. 

The power system is designed using remote sense such that the voltage at the fixture is 

monitored to insure the voltage is maintained to the proper setting. This requires that the 

fixture be designed to connect the remote sense to the power supply output. 

Power is only applied during the programming process and otherwise no power is present at 

the fixture interface or to the assembly (DUT). The system includes a hardware monitored 

(Enable/Disable) signals from the fixture to remove power. This allows the fixture design to 

include a switch that removes power if the operator opens a safety lid, for example. 

The system power supply is connected to the PC by a RS232 COM interface cable. This 

requires the power supply is configured to match the system configuration setup. In particular, 

the power supply address must match the system configuration address. The power supply 

baud rate of the first power supply must match the system configuration. The power supply 

must be setup to run via RS232. If more than one power supply is included in the 

configuration, the power supply #1 must be setup to run in MultiDrop mode. 

For more details, see Power Supply Considerations on page 6-5 and Fixture Ready on page 6- 

17.CheckSum configures the system power supplies prior to shipment. 


Installing the Power Supplies below 

Fixture Receiver Interface Power Block K Wiring on page 12-31 

Power Supply Considerations on page 6-5 

DC Voltage Output on page 14-4 

DC Current Output on page 14-4 

Monitor Power Output on page 14-5 


This section describes the process to install the power supplies. Skip this section if the power 

supplies were ordered from CheckSum as part of a complete test system, since the power 

supplies are installed and verified prior to shipment. 

See Power Supply Considerations on page 6-5 and Fixture Receiver Interface Power Block K 

Wiring on page 12-31 for additional information. 

13-3




Caution 

Always disconnect AC power and vacuum from the tester before any panels are 

removed from the test system. Mechanical parts internal to the test system can be 

dangerous when in operation. 

Here are the steps to install the power supplies. 

1) Turn-off the system AC power and disconnect the VAC input line and the compressed 

air supply line to the rack. Verify AC switch on front of power supplies are in the “O” 

(OFF) position. Disconnect AC line cord from back of power supply if connected. 

2) Remove the front and side panels for access. 

3) Install the rack mount kit(s) on the power supply and the system. 

Single Supply Rack Mount (mount left or optionally right) 

Dual Supplies Rack Mount 

4) Connect the power supply wiring to the supply and the fixture interface. 

5) Route the wires between the power supply and the fixture interface. 

6) Reinstall the panels, power and air supply. 

13-4




The power supply can be installed at the bottom of the system rack. One part of the rack slides 

attach to each side of the power supply. The other parts of the rack slides attach to the system 

rack. After installing the rack slides, install the power supply in the rack. 

Part of the power supply kit includes the wiring harness to connect the power supply to the 

fixture interface. The wire harness includes the 200-pin block since several of the wires are 

soldered to a special power supply pin block. 

The wires to the power supply are labeled. In addition to the ± voltage output wires, there are 

± sense wires, power supply enable output wires, communication cable, and the VAC power 

cable. The communication cable with the RJ45 connector and a DB-9 connector must be 

connected from the system PC COM1 port to the #1 power supply Remote In. A 

communication cable, with RJ45 connectors on each end, connects from Remote Out to 

Remote In on each subsequent power supply. 

On the back of the power supply, remove plastic cover from J2 and SW1 on back panel; retain 

the cover and screw. 

Power Source Back Panel 

Notes: 

Remote/Local output voltage sense connections (J2). 

DIP switch SW1. 

DB25 for analog program and monitor plus other functions (J1). 

RS-485 OUT to other power supplies (OUT). 

RS-232/RS-485 IN remote serial programming port (IN). 

AC power input 85 to 265VAC, 47 to 63Hz with active power factor correction (0.99 

typical). 

Exit air slots. 

Voltage output bus bars. 

Optional IEEE 488.2, isolated analog, LAN, USB interface (none provided). 

Set the SW1 switches: 

1) On supply #1, SW1-9 switch (Enable/Disable control Active) should be UP, all other 

SW1 switches should be DOWN. 

2) On all other supplies (if installed) SW1-6 (RS485 interface) and SW1-9 should be UP, 

all other SW1 switches should be DOWN. 

13-5




Connect power supply to Source and Sense wires from interface block: 

1) Install the lugs onto the bus bars as shown in the following figure, using the indicated 

torque. 

Power Source Voltage Output Bus Bar Wiring 

2) The power supply Sense wires in the +S and -S positions of the J2 connector should be 

connected to the +Sense and -Sense wires from the Power Supply Interface board. Do 

not make connections to the Local Sense, +LS and -LS positions on the J2 connector. 

3) Reinstall the cover over J2 and SW1. 

4) Install the metal cover over the bus bar source outputs of the power supply. 

Connect power supply J1 (safety Enable output feature) to the system control board: 

1) Use the provided DB25 IDC style connector to make these connections. The connector 

must be shrouded when completed. 

2) On each supply, connect the wires to each of the J1 connectors. 

Verify or change the address of each supply: 

NOTE: The default address setting from the power supply manufacturer is 6. 

The front panel controls can be locked to protect from accidental power supply parameter 

change. Press and hold the front panel PREV button to toggle between "Locked Front Panel" 

LFP and "Unlocked Front Panel" UFP. The front panel display will cycle between LFP and 

UFP while the PREV button is held down. Release the button when the display shows the 

desired setting. 

13-6




Press the REM/LOC button until an address is displayed in the left LED field for voltage 

setting (e.g. A 06). Rotate the VOLTAGE knob to change the address numeric value. If, 

when you rotate the VOLTAGE knob you see LFP displayed then the front panel is locked 

out from updating the address until you hold the PREV button and see UFP displayed and the 

panel is unlocked. Once unlocked then you can set an address. 

1) If the REM/LOC LED is lit, press the REM/LOC button momentarily. 

2) Press and hold the REM/LOC button until the display indicates the address and baud 

rate. The address is shown on the left display as “A 06” and the baud rate is shown on 

the right display. 

3) Adjust the address of each supply using the VOLTAGE knob. Set the address of the 

first supply to “A 06”, the second supply to “A 07”, etc. The default PS-UUT-L1 

address in the system configuration for the first supply is 6. Any system with more than 

one power supply will require the addresses of the additional supplies be set on 

installation. Each power supply requires a unique address that matches the displayed 

address in the CheckSum System Configuration window. 

4) Verify the baud rate of 9600. Adjust with the CURRENT knob if necessary. 

5) Switch the supply/supplies OFF. 

Connect serial cables: 

1) Connect the DB-9 to RJ-45 cable from the PC COM1 port to the “IN” connector at the 

back panel of supply #1. 

2) Using the provided RJ-45 to RJ-45 cable, connect the “OUT” connector of supply #1 to 

the “IN” connector of supply #2 (if applicable), then connect the “OUT” connector of 

supply #2 to the “IN” connector of supply #3, etc. 

3) Connect any additional supplies “IN” to the “OUT” connector of the previous supply. 

13-7




Dual Power Supply Back Panel Wiring 

Power-up the supplies: 

1) One each power supply, connect the AC line cord. Use only the AC line cord supplied 

with the power supply. The supply accepts universal AC input (85-265VAC). 

2) Operate the switch on the front panel to the “|” (ON) position. 

3) In the CheckSum test system software, Configure System F4, add the PS-UUT-L1 

supplies (Add Module… > Functional Modules), verify the address, interface location, 

and baud rate. 

4) Self-Test each power supply added to the system configuration. 

The cables from the power supply to the PC and the fixture interface must be routed such that 

they never touch any moving part of the system. If the cables are kept to the side and back of 

the rack they should be safe. Be certain to tie down all of the cables to a stationary part of the 

rack away from the moving items. 

13-8

Chapter 14 

Program Command 

Descriptions 

Test Type Descriptions 

Overview 

The descriptions in this chapter provide detailed information about each of the test types that 

can be used in a test program. These test types are entered with the Edit window described in 

Entering Test Steps on page 10-2. Writing Programs also gives general information about 

how many of these test types are used in a program. 

Get HELP Fast: To access the test type help page quickly, type in the test type, press the 

Enter key, and press the F1 function key. 

Power Supply Control on page 14-3 

DC Voltage Output DCV on page 14-4 

DC Current Output DCI on page 14-4 

Monitor Power Output PWRMN on page 14-5 

Digital Test Types on page 14-6 

In System Programming with 

MISP on page 14-6 

MultiWriter 

Digital Input Test DIGI on page 14-7 

Digital Output DIGO on page 14-8 

Digital I/O Configuration DIGA on page 14-8 

PC Port Input Test PORTI on page 14-9 

PC Port Output PORTO on page 14-9 

Transfer of Control Test Types on page 14-10 

Specify Label LABEL on page 14-11 

Jump Unconditionally JMP on page 14-11 

Jump Based on Power JMPWR on page 14-11 

Measurement 

Jump Based on Result of JMPDI on page 14-12 

Digital Input

Program Command Descriptions 

Test Type Descriptions 


Jump Based on Result of JMPPI on page 14-12 

Port Input 

Jump Based on Result of JMPK on page 14-13 

Key Input 

Set Error Counter Used ERROR on page 14-13 

for JMPE 

Jump Based on Number of JMPE on page 14-14 

Errors 

Jump Based on Self-test JSTST on page 14-15 

Call a Subroutine CALL on page 14-15 

Return from a Subroutine RET on page 14-15 

Load and Run a Test RUN on page 14-16 

Program 

Load and Run a Test Sub- RUNT on page 14-16 

Program 

Return from a Test Sub- RETT on page 14-17 

Program 

Operator Message Test Types on page 14-17 

Display a Short DISPL on page 14-18 

Message to the 

Operator 

Display a Message to DISP on page 14-18 

the Operator 

Erase an Operator DISPE on page 14-19 

Message 

Wait for a Key to be WAITK on page 14-19 

Pressed 

PCB Number Being PCB on page 14-19 

Tested 

Screen Test Type Table SCRN on page 14-21 

User-Defined Tests on page 14-23 

Generate Test Result EVAL on page 14-23 

Execute User-Written Routine EXEC on page 14-23 

Memory Manipulation Test Types on page 14-25 

Memory Manipulation (Integer) MEMI / MEML on page 14-26 

Memory Manipulation (Real) MEMR / MEMD on page 14-30 

Memory Manipulation (String) MEMS on page 14-32 

General Purpose Interface Bus (GPIB) I/O on page 14-37 

GPIB (IEEE-488) Control GPIB on page 14-37 

RS232 Serial Interface I/O on page 14-40 

RS232 Control RS232 on page 14-40 

Miscellaneous Tests on page 14-43 

Vacuum Control VACUM on page 14-44 

Fixture Control FIXCT on page 14-45 

14-2



Power Supply Control 

Pause a Specified Time PAUSE on page 14-48 

Self-test Module STST on page 14-48 

BreakPoint BRKPT on page 14-49 

Print Test Results RPRTS on page 14-49 

Sound PC's Beeper BEEP on page 14-52 

Put a Remark in the Test REM on page 14-52 

Program 

Conditional Test Report RSLTS on page 14-52 

Output 

The following list shows the general test types that are available and where to find them in this 

section: 

• Power Supply Control below 

• Digital I/O Types on page 14-6 

• Transfer of Control Types on page 14-10 

• Message Steps on page 14-17 

• User-Defined Steps on page 14-23 

• Memory Manipulation Steps on page 14-25 

• General Purpose Interface Bus (GPIB) I/O on page 14-37 

• RS232 Serial Interface I/O on page 14-40 

• Miscellaneous Steps on page 14-43 



Overview 

The power supply command steps allow you to apply power to the DUT from within a test 

program. 

Review the output enable control signals in Power Supply Considerations on page 6-5 and 

Fixture Ready on page 6-17. 

The commands used to control the system power supplies (PS-UUT-L1) are: 

• DC Voltage Output on page 14-4 

• DC Current Output on page 14-4 

• Monitor Power Output on page 14-5 

• Jump Based on PWR Measurement on page 14-11 

• Memory Manipulation (Integer); see MemI Range 65 on page 14-26 

• RS232 Serial Interface I/O on page 14-40 

14-3




DC Voltage Output 

Provides DC voltage output from the PS-UUT-L1 power supplies. 



Parameters 

Test Type 

Title 

Range 

From (-) Point 

To (+) Point 

Low Limit 

High Limit 

Description 

DCV 

If 'RESET' is entered, the specified DCV output is set to 0 volts. 

DC source being programmed: 

8 to 15 = For control of the voltage-mode output of PS-UUT-L1 

supplies numbered 1 through 8, respectively. 

Reserved Titles: MIN to specify the minimum allowed 

output voltage when the supply is on, MAX to specify the 

maximum allowed output voltage. Note that the supply 

contains built-in hardware protection for these two settings. 

Not used 

Not used 

Not used 

Amplitude in volts: 

If Range = 8 to 15 (PS-UUT-L1) 

0-60Vdc, in 1mV steps 

If the PS-UUT DCV setup fails, the system will alert the operator with a pop-up message: 

Setting below Under Voltage Limit attempted 

Attempt to set DCV level below a voltage specified by a previous DCV MIN step for that 

supply. 

Setting above Over Voltage Limit attempted 

Attempt to set DCV level above a voltage specified by a previous DCV MAX step for that 

supply. 












messages. 

DC Current Output 

Sets the current limit for the PS-UUT-L1 power supplies. 

14-4






Parameters 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DCI 

If 'RESET' is entered, all connections for the specified source are 

removed and the amplitude is set to 0 for the source. 

DC source being programmed: 

8 to 15 = For control of the current-mode output of PS-UUT-L1 

supplies numbered 1 through 8, respectively. 

Reserved Titles: FOLD0 to disable current foldback, FOLD1 

to enable foldback, MIN to specifiy the minimum allowed 

output current when the output is on, MAX to specify the 

maximum allowed output current limit. 

Not used 

Not used 

Current in Amps: 

If Range = 8 to 15 (PS-UUT-L1) 

0 to 12.5A, in 1mA steps 

Not used 

If the PS-UUT DCI setup fails, the system will alert the operator with a pop-up message: 

Setting below Under Current Limit attempted 

Attempt to set DCI level below a current specified by a previous DCI MIN step for that 

supply. 

Setting above Over Current Limit attempted 

Attempt to set DCI level above a current specified by a previous DCI MAX step for that 

supply. 












messages. 

Monitor Power Output 

Allows measurement of voltage and current output from the PS-UUT-L1 power supplies. 



14-5


ISP and Digital Test Types 


Parameters 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

PWRMN 

Normally not used. 

DC source being monitored and type of monitor. 

Sum of: 

PS-UUT-L1 monitor: 

8 = Monitor PS-UUT-L1 #1 output, or 







15 = Monitor PS-UUT-L1 #8 output, and 

16 = Measure PS-UUT-L1 Voltage, or 

32 = Measure PS-UUT-L1 Current 

Not used 

Not used 

Not used 

Not used 


Digital Test Types 

Overview 

The digital test types allow you to input and output digital data from within a test program. 

• In System Programming with MultiWriter (MISP) below 

• General Digital I/O Programming on page 14-7 

• Digital Input Test on page 14-7 

• Digital Output on page 14-8 

• Digital Active on page 14-8 

• PORTx Test Types on page 14-9 

• Port Input Test on page 14-9 

• Port Output on page 14-9 

In System Programming with MultiWriter (MISP) 

The MultiWriter pps MISP test step is used to program and verify programmable parts. The 

step has multiple uses and can control many types of programmable parts. For example, this 

test step can be used to erase, program and verify a programmable component. Since the 

programming is done in parallel, the programming time is the same for 1 part or up to 384 

parts. Several types of bus protocol are supported (e.g. SPI, I 2 C, JTAG, Microwire, PIC) with 

more added as needed. 

14-6




This test type uses the CheckSum MultiWriter pps ISP controller and ISP buffer modules. 

These modules are mounted inside the test fixture to insure accurate programming signals to 

the ICs. 

The MISP setup form has several entries, for a detailed explanation of each of the entries and 

options, see the MultiWriter MISP Setup on page 10-7. 

The MISP test step includes a method to apply UUT power during MISP single-step execution. 



Parameter 

Test Type 


To (+) Point 

Range 

Title 

Low Limit 

High Limit 

Description 

MISP 

Not used 

Not used 

ISP data set 

Used to describe the component and action, e.g., U105 erase, 

program & verify. 

Not used 

Not used 

General Digital I/O Programming 

The numbers used with the digital test types (DIGI, DIGO, DIGA, PORTI, PORTO) are all 

decimal. As such, if you would like to send a byte of all ones, you would specify 255. A byte 

of all zeros is 0. Individual bits (which can be added) are 128 (MSB), 64, 32, 16, 8, 4, 2, and 1 

(LSB). 

The least-significant 4 bits (nibble) are bi-directional tri-state I/O. This nibble has pull-ups to 

3.3V and should be 3.3V and TTL IO compatible. The most-significant nibble is open-drain 

so only is controlled by DIGO. 

Masks are used to specify inactive bits during input. Any one in the mask is used to mask out 

the specified bits. For example, if you want to mask out the two least significant bits, specify a 

3. Test results are presented after the masking operation. 

DIGx Test Types 

The DIGx (DIGI, DIGO, DIGA) test types perform input and output via the CheckSum system 

module (8 bits) and and MultiWriter Fixture I/O module (MW FIX I/O). 

Digital Input Test 

Reads a byte of digital data and generates a test result. 

The menu selection Measure > Step Analysis F6 in the edit window provides an easy to 

use, fill-in the form method, to select these settings. 

14-7




Parameter 

Description 

Test Type 

DIGI 

Title 

Name of test step (e.g., U234 Out) 

Range 0 = bits 1 to 8 (System on page 4-9) 

1 = bits 9 to 16 (MW FIX I/O on page 6-13 module 1) 

2 = bits 17 to 24 (MW FIX I/O module 2) 


… 


From (-) Point Not used 

To (+) Point 0 = normal execution, set Pass/Fail 

1 = do not report results, do not set Pass/Fail 

Low Limit 

Input mask: Data read is ignored for any bit set as one in this 

field (e.g., if input mask is 3, the LSB and next LSB are 

ignored). 

High Limit 

Expected data 

Digital Output 

Write a byte of digital data. 



Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DIGO 

Not used 

Output byte number: 

0 = bits 1 to 8 (System on page 4-9) 

1 = bits 9 to 16 ((MW FIX I/O on page 6-13 module 1) 



… 


Not used 

Not used 

Not used 

Data byte to output 

Digital Active 

Set selected bits to be active. Sets specified one-bits as active and zero-bits as tri-state in the 

selected byte. All bits are tri-stated as a default. 



14-8




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DIGA 

Not used 

Output byte number: 

0 = bits 1 to 8 (System on page 4-9) 

1 = bits 9 to 16 ((MW FIX I/O on page 6-13 module 1) 



… 


Not used 

Not used 

Not used 

Tri-state data information. Each bit set as one is activated. 

PORTx Test Types 

The PORTx (PORTI, PORTO) test types perform I/O to the PC's input and output ports 

allowing you to communicate with peripherals and other I/O-mapped devices such as the 

Model RM-1. 

The Port I/O commands can perform I/O on the local PC bus or the Remote PC bus. For 

options located in the test system chassis such as the RM-1 option, select the Remote check 

box in the setup window (press F6 to open the setup window). 

Port Input Test 

Read a byte of digital data from the PC's I/O bus and then generate a test result. 

PORTI can input data from the local PC bus or the Remote PC bus. For options located in the 

test system chassis such as the RM-1 option, select the Remote check box in the setup window 

(press F6 to open the setup window). 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

PORTI 

Name of test step (e.g., Data In) 

Input port address 

Not used 

0 = normal execution 

1 = do not generate or report results 

Input mask: Data read from port is ignored for any bit set as 

one in this field (e.g., if the input mask is 5, the 1-bit (LSB) and 

4-bit are ignored). 

Expected data 

Port Output 

Write a byte of digital data to the PC's I/O bus. 

14-9


Transfer of Control Test Types 


PORTO can output data to the local PC bus or the Remote PC bus. For options located in the 

test system chassis such as the RM-1 option, select the Remote check box in the setup window 

(press F6 to open the setup window). 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

PORTO 

Not used 

Output port address 

Not used 

Not used 

Not used 

Data byte to write 



Overview 

The following test types are used for transfer of control within the test program. A label is first 

specified that can be used as the destination of JMPs and CALLs. Labels are not casesensitive 

(differences in upper and lower case are ignored). 

Note 

The measurement parameters set in the Special Features menu, such as 

failure retries and discharge times, also affect the speed and accuracy of the 

analog JMP test types, i.e., JMPR, JMPC, JMPZ and JMPD. To enhance 

testing speed, you can use the RETRY and RESRG test types to modify 

these measurement parameters during a test. 

• Specify Label on page 14-11 

• Jump Unconditionally on page 14-11 

• Jump Based on PWR Measurement on page 14-11 

• Jump Based on Result of Digital Input on page 14-12 

• Jump Based on Result of Port Input on page 14-12 

• Jump Based on Result of Key Input on page 14-13 

• Set Error Counter Used for JMPE on page 14-13 

• Jump Based on Number of Errors on page 14-14 

• Jump Based on Self-test on page 14-15 

• Call a Subroutine on page 14-15 

• Return from Subroutine on page 14-15 

• Load and Run a Test Program on page 14-16 

14-10




• Load and Run a Test Sub-Program on page 14-16 

• Return from Test Sub-Program on page 14-17 

Specify Label 

Specify a label to be used as the destination of transfer of control commands. If the label is 

'SHUT DOWN', the test steps following it are executed, even if the test is aborted (see Exiting 

the Program on page 10-26). This can serve as a power-down sequence at the end of the 

program. If the label is 'REPEAT', next time the [F2] Repeat key is pressed when the System 

is paused between steps, the repeat will occur to this point. This repeat action can be canceled 

and returned to normal with a label of 'CLEAR REPEAT.' 

If the title begins with TRY, this step specifies the start of a TRY block. The TRY block ends 

at the matching ERROR TRY test step. The enclosed block is executed up to the number of 

times specified by the matching ERROR TRY as long as the block generates at least one jump 

error. You can have up to five nested TRY blocks at a time. Each TRY block needs to have a 

unique title (e.g. TRY1, TRY2, TRY3). 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

LABEL 

Label Name: The labels SHUT DOWN, REPEAT, 

CLEAR REPEAT, and TRY (case insensitive) are 

special, see above. 

Not used 

Not used 

Not used 

Not used 

Not used 

Jump Unconditionally 

Unconditionally transfer control to a specified label. 

Parameter Description 

Test Type 

JMP 

Title 

Destination label 

Range 

Not used 


To (+) Point Not used 

Low Limit 

Not used 

High Limit 

Not used 

Jump Based on PWR Measurement 

The System measures the current or voltage output of the PS-UUT-L1, then jumps to the 

specified label if the test passes. No results are logged. With the exception of the test type and 

title, all the fields are the same as the PWRMN test type on page 14-5. This test step requires 

14-11




the PS-UUT-L1, see PS-UUT-L1 Power Supply Considerations on page 13-1 for more details 

about the PS-UUT-L1. 

Parameters 

Test Type 

Title 

Range 

Description 

JMPWR 

Destination of jump if monitored voltage/current is between the 

low and high test limits. Must match the title of a LABEL test type 

in the test program. 

DC source being monitored and type of monitor. 

Sum of: 








15 = Monitor PS-UUT-L1 #8 output, and 


To (+) Point 

Low Limit 

High Limit 

16 = Measure PS-UUT-L1 Voltage, or 

32 = Measure PS-UUT-L1 Current 

Not used 

Not used 

Not used 

Not used 

Jump Based on Result of Digital Input 

The System inputs the digital data, and if the test passes, a jump to the specified destination 

occurs. No results are logged. With the exception of the test type and title, all the fields are 

the same as the DIGI test type. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

JMPDI 


Same as DIGI on page 14-7 test type 

Not used 

Not used 

Input mask: Data read from the System module digital 

input is ignored for any bit set as one in this field (e.g., if 

input mask is 5, the LSB and 2nd bit from the LSB are 

ignored). 

Expected data 

Jump Based on Result of Port Input 

The System inputs digital data from the PC's I/O port, and if the test passes, a jump to the 

specified destination occurs. No results are logged. With the exception of the test type and 

title, all the fields are the same as the PORTI test type. 

14-12




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

JMPPI 


Input port address 

Not used 

Not used 

Input mask: Data read from port is ignored for any bit 

set as one in this field (e.g., if the input mask is 5, the 1- 

bit (LSB) and 4-bit are ignored). 

Expected data 

Jump Based on Result of Key Input 

The System checks to see if the operator has pressed a key on the PC's keyboard. If so, and if 

the key matches the specified key, the System performs the jump. Otherwise, if no key or the 

wrong key is pressed, the System performs the next test step. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

JMPK 


Decimal ASCII value on page 14-36 of key. For 

example, 65 is A and 48 is 0. F1-F10 are 131-140. If 0 

is specified, the System accepts any key as true. If a 

lower-case key is pressed on the keyboard, it is 

converted to upper case before making the comparison. 

If the comparison is true, the key stroke is removed from 

the key buffer. If the comparison is not true, the key 

remains in the buffer for use by other JMPK test steps. 

The key buffer can be cleared by entering a JMPK 

range of 255. 

Not used 

Not used 

Not used 

Not used 

Set Error Counters, Control Error-Based TRY Blocks 

This test type allows you to: 

• Set the jump error counter that is used with JMPE test type on page 14-14. This can be 

used to set the jump error counter to 0 or to set a defined higher value for subsequent 

JMPE decisions. 

• Set the jump error counter to the system error counter (use RESET as the title). 

• Set the system error counter to the jump error counter (use SET as the title). 

• Clear the jump error counter, clear the system error counter, and all steps are set to skipped 

(use CLEAR ALL as the title). 

• Set the system error counter to a value greater than, or equal to, zero. This is displayed on 

the Test Screen and in the test results report. 

14-13




• Specify the end and number of attempts in a TRY block. 

This test type can be used when testing for errors in repetitive tests using the same test 

program or to reset the counter between PCBs on multi-PCB panels. 

Note that unlike the system error count displayed in the upper section of the test display, the 

jump error counter counts all failures that occur, even if the test step is subsequently repeated 

and passes. If a test title of RESET is used, the jump error counter is set to the value of the 

system error counter. This can be helpful if you have been resetting the counter and then need 

to find out how many total errors have occurred since the test program began executing. If a 

test title of SET is used, the system error counter is set to the value of the jump error counter. 

If a test title of CLEAR ALL is used, then both the system error count and jump error count 

are set to zero and all test results in the test program are set to skipped. This is useful at the 

start of main program loops with a different UUT tested for each loop execution. 

If the ERROR step title begins with the letters TRY (e.g., TRY1, TRY2, TRY3) then this step 

specifies the end of a TRY (loop) block. This TRY block is repeated up to the number of 

times specified in the range as long as one or more jump errors have occurred since the 

matching "LABEL TRY" step was executed. 

The menu selection Measure > Step Analysis F6 in the edit window opens an easy to use, 


Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

ERROR 

Normally not used, but if the title is RESET, the JMPE 

error count is set to the value of the system error count. 

If the title is SET, the system error count is set to the 

value of the jump error count (see JMPE). If the title is 

CLEAR ALL both the system error count and the jump 

error count are set to zero and all steps are set to 

skipped. If the title begins with TRY then this step 

specifies the end of a TRY block. 

The jump error count used for JMPE or the maximum 

number of TRY block attempts. 

Not used 

Not used 

Not used 

Not used 

Jump Based on Number of Errors 

If the number of errors (based on the jump error counter) encountered up until the time of 

execution exceeds the specified number, the System performs the jump. Otherwise, the 

System performs the next test step. Note that unlike the system error count displayed in the 

upper section of the test display, the jump error counter includes all failures that occur, even if 

the test step is subsequently repeated and passes. Also, see the ERROR on page 14-13 and 

MEMI on page 14-26 test types for manipulation of the jump error count and the system error 

count. 

14-14




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

JMPE 


Specified number of jump errors. If the number of jump 

errors encountered during test program execution 

exceeds the specified number of jump errors, a jump to 

the destination label specified in the title occurs. 

Not used 

Not used 

Not used 

Not used 

Jump Based on Self-test 

The System performs a self-test (see STST test type on page 14-48), and if the test passes, a 

jump to the specified destination occurs. No results are logged. 



Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

JSTST 


Same as STST test type 

Not used 

Not used 

Not used 

Same as STST test type 

Call a Subroutine 

Control transfers to the Label step named in the Title, then resumes to the next test step when 

a RETurn is executed. CALLs can be nested up to 16 deep. 

Parameter 

Description 

Test Type 

CALL 

Title Destination Label on page 14-11 

Range 

Not used 



Low Limit 

Not used 

High Limit 

Not used 

Return from Subroutine 

Control transfers to the test step immediately following the last CALL step that was executed. 

14-15




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

RET 

Not used 

Not used 

Not used 

Not used 

Not used 

Not used 

Load and Run a Test Program 

Causes the System to load a specified test program into memory and begin execution at the 

first test step. 

When a RUN test step is executed, the test program presently in memory is overwritten. Also, 

any results information from the present test program is lost. If you want to save any test 

results from the present test program execution before doing the RUN, you may use the 

RPRTS test type. 

The memory locations are not reset during the RUN execution and consequently can be used to 

transfer information from one test program to the next. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

RUN 

Name of test program to load and run. If the title is @M, use 

the contents of the memory string as the test program 

name. See MemS Range 1 on page 14-32 to load MemS, 

memory string, with a character string for the test program 

path and name. 

Not used 

Not used 

Not used 

Not used 

Not used 

Load and Run a Test Sub-Program 

Causes the System to load a specified test program into memory and begin execution at the 

first test step. When a RUNT test step is executed, the test program file presently in memory is 

overwritten with the RUNT test program. The present test program and its accumulated 

results information are saved. When a RETT test step in the RUNT test program is 

encountered, the results from the RUNT test program are saved, and the original test program 

and its results are restored. The pass/fail status and location of any PCB panels from the main 

test program are available from the RUNT test program. 

The memory locations are not reset during the RUNT execution and consequently can be used 

to transfer information from one test program to the next. Up to 10,000 lines of additional 

results and up to 16 test programs can be connected together with the use of RUNT range 2 

14-16



Message Test Types 

commands from a single test program (one main program plus up to 15 sub-programs executed 

with the RUNT using range 2). A main program can have any number of RUNT with range 0 

or 1 test steps. Nesting of RUNT test steps is not allowed. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

RUNT 

Name Of Sub-Program To Execute. If the title is @M, use 

the contents of the memory string as the test program 

name. See MemS Range 1 on page 14-32 to load MemS, 

memory string, with a character string for the test program 

path and name. 

Extent of Result Reporting For Called Program 

0 = No individual test step results saved from called test 

program, only its pass/fail status is returned 

1 = Return only Pass (Fail Only if Called Program 

Non-Existent) 

2 = All results of called test program saved. 

Not used 

Not used 

Not used 

Not used 

Return from Test Sub-Program 

Control transfers to the test step immediately following the last RunT on page 14-16 test type 

that was executed. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

RETT 

Not used 

Not used 

Not used 

Not used 

Not used 

Not used 



Overview 

The following test types allow you to display messages to the operator during test time. 

Messages are shown in the message area of the test screen. 

A short display message (up to twelve characters) can be displayed directly by the DISPL test 

type. The message displayed is contained in the title field of the test step. 

14-17




Longer messages are displayed with the DISP test type which references displays by a message 

number. These displays are defined by selecting 'Step Analysis' after selecting the DISP test 

type in the Edit screen. Up to 999 messages can be defined in a test program (.spec file 

format) with each used more than once if desired. When a message is defined, it is displayed 

beginning at the specified column and row of the message area of the display. Allowable rows 

are 1 through 8 and allowable columns are 1 through 78. 

Messages can contain a special code {MEAS}. When the System encounters the {MEAS}, it 

inserts the measured value for the closest step above this step that generated a result. This 

feature can be used for displaying a measured value as the operator makes an adjustment on 

the UUT. 

• Display a Short Message to the Operator below 

• Display a Message to the Operator below 

• Erase an Operator Message on page 14-19 

• Wait for a Key to Be Pressed on page 14-19 

• PCB Number Being Tested on page 14-19 

• Enhanced Display Attributes using SCRN Test Type on page 14-20 

• SCRN Test Type Table on page 14-21 

Display a Short Message to the Operator 

Display a message contained in the test step's test title to the operator. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DISPL 

Text of message to display 

Not used 

Beginning column to display the message on. If this 

is greater than 78, the message is not displayed. 

Line to display the message on. If this is greater than 

8, the message is not displayed. 

Not used 

Not used 

Display a Message to the Operator 

Display a specified message number to the operator. See Display Messages on page 10-5 

and Display Attributes on page 14-20 for additional information. 

14-18




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DISP 

Not used 

Message number to present 

Not used 

Not used 

Not used 

Not used 

Erase an Operator Message 

Erase the message area of the display from the beginning location of the specified message to 

the end of the line. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

DISPE 

Not used 

Message number to erase. If zero is entered, 

the System erases the entire display area. 

Not used 

Not used 

Not used 

Not used 

Wait for a Key to Be Pressed 

The System waits until the specified key is pressed, then continues to the next test step. 

Parameter 

Description 

Test Type 

WAITK 

Title 

Not used 

Range Decimal ASCII value on page 14-36 of key. For example, 65 is A and 48 is 0. The F1- 

F10 key values are 131-140. If 0 is specified, the System waits for any alpha-numeric or 

function key to be pressed (Windows blocks some keys from the software). If a lowercase 

key is pressed on the keyboard, it is converted to upper case before making the 

comparison. 



Low Limit 

Not used 

High Limit 

Not used 

PCB Number Being Tested 

Used with multi-PCB panels to specify to the operator which PCB is being tested. Test results 

also contain the PCB number to show which PCB results are being listed. See the section of 

this manual describing Multi-PCB Panels for complete detail. 

14-19




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

PCB 

Typically not used, but if it is specified as SKIP FAIL, the System will advance to the next 

PCB statement in the test program if there have been any failures for this PCB during the 

test. SKIP FAIL can be used, for example, to skip over functional tests of a PCB if the 

tests have failed. 

Which PCB is being tested. Valid values are 0-360 (up to 16 rows and 20 columns). 

Normally PCB 1 is the first PCB, followed by the others in sequential order. The value of 

0 can be used for common test steps used by all PCBs so that these test steps will be 

executed, even if the PCB previously assigned has been skipped by the operator. 

Not used 

Not used 

Not used 

Not used 

Enhanced Display Attributes using SCRN Test Type 

The SCRN test step on page 14-21 allows manipulation of display attributes (i.e. text color 

and background color), in the user display area (area controlled e.g. by DISP, DISPE, and 

DISPL test types). It also writes and reads user display area screen to and from files. There are 

six different operations that can be applied simultaneously with a single test step: 

• Get Display Attribute: Copy the display attribute value for a specified row/column 

location (From Point / Low Limit, respectively) into the integer memory (see MEMI on 

page 14-26). 

• Set Display Attribute: Set the display attribute of the specified area according to the 

specified display attribute value. 

• Save Screen: Save the message and display attribute of the specified area to an ASCII file 

whose name is specified in the test step Title. Note: This file can later be modified 

separately. 

• Load Screen: Load the message and display attribute of the specified area from an ASCII 

file whose name is specified in the test step Title. 

• Refresh User Display Area: Redraw the user display area. 

• Refresh Measurement Display Area: Redraw the measurement display area. This is the 

area above and below the user display area. 

The Refresh Measurement Display and Refresh User Display Area will be useful when 

messages other than display messages have been printed on the screen and it is necessary to 

restore the previous user messages. 

The coordinates of a specified area are defined by the From/To Points and High/Low Limits. 

The corresponding values of the operations are listed in the following SCRN Range table, 

along with the list of display attribute values. After values for each display attribute and 

operation are determined, those values are added to get the final range value. Examples on 

how to specify the range are given at the end of the following section and in the Screen and 

Display Attribute Manipulation on page 11-10 test program example. 

14-20




SCRN Test Type Table 

See example programs with SCRN steps on page 11-10. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

SCRN 

filename, used when a save or load screen operation is specified 

color attribute and operation set up, see SCRN Test Range Table 

starting row 

ending row 

starting column 

ending column 

SCRN Test Range Table 

Toolbar Note 

In the edit test program window, after you have entered the SCRN test step, 

use the F6 'Step Analysis' key to open a dialog box to setup all the attributes 

of this command. Using the mouse, you can move and size the area in the 

bottom section of this window. 

14-21




Parameter Value Description 

Text Color 0 Yellow (default) 

1 Blue 

2 Green 

3 Cyan 

4 Red 

5 Purple 

6 Brown 

7 White 

8 Gray 

9 Light Blue 

10 Light Green 

11 Light Cyan 

12 Light Red 

13 Magenta 

14 Black 

15 Light White 

Text Background 0 Blue (default) 

16 Black 

32 Green 

48 Cyan 

64 Red 

80 Magenta 

96 Brown 

112 White 

Operation 256 Get Display Attribute 

(can be masked 512 Set Display Attribute 

together) 1024 Refresh Measurement Display Area 

2048 Refresh User Display Area 

4096 Save Screen 

8192 Load Screen 

(If load file is invalid, there will be no effect.) 

Note 

The operations are executed in the above order, from top to bottom 

sequentially (if specified). This SCRN test step is related to all test steps 

that show messages on the user display area e.g.: DISP, DISPL, DISPE, 

MEMS, MEMI, MEMR (range = 5). 

Examples: 

• Set Display Attribute with cyan text and black background. 

Range = 512 (set attribute) + 3 (cyan text) + 16 (black background) 

= 531 

14-22



User-Defined Tests 

• Refresh the Measurement and User Display Area 

Range = 1024 (refresh measurement display) + 2048 (refresh user display area) 

= 3072 

See also SCRN example programs on page 11-10. 



Overview 

• Generate Test Result below 

• Execute User-Written Routine below 

Generate Test Result 

Place a pass or fail into the test results. This can be used with conditional jumps to generate 

and record a passed or failed result. 

If the range is 2, the System searches upward through the test program and finds the last 

measured value from an analog test type (or its equivalent JMP command). This becomes the 

measured value for the step and it is compared against the high and Low Limits to generate a 

pass or fail result. This can be used after an adjustment loop to generate a pass or fail result 

based on the JMPx measurement the last time through the loop. 

Parameter 

Description 

Test Type 

EVAL 

Title 

Descriptive title (e.g., Gain) 

Range 

0 for Pass 

1 for Fail 

2 for compare against High/Low Limits 

4 for same as 2, but use present memory-real value as 

measured value 



Low Limit Not used unless the range is 2 or 4 

High Limit Not used unless the range is 2 or 4 

Execute User-Written Routine 

The EXEC command will execute an external routine. The called routine can be written in any 

language that generates a .EXE or .COM file. During test program execution, the specified 

routine is loaded into memory and then executed. Once it has completed operation, control is 

resumed with the test software. If the DOS error level is non-zero upon return, the test fails. If 

it is zero, the test passes. 

If the System reports a DOS error 8, the EXECed program is too large to fit into the available 

RAM memory. Exec first looks in the current directory for the .EXE or .COM file. If it is not 

14-23




found in the current directory, it searches through the directory locations in the DOS PATH 

environment variable. Only if the file is not in any of these locations does the System report a 

DOS error 2. 

The test title describes the program name to EXEC. It can also specify command line 

parameters to pass to the program. Special characters, or strings, in the test title specify the 

parameters to pass to the routine: 

^ (up arrow) to pass the characters in the title as a parameter 

@i to pass the value of the integer memory variable (MemI) 

@l to pass the value of the long memory integer variable (MemL) 

@r to pass the value of the real memory variable (MemR) 

@d to pass the value of the double-precision real memory variable (MemD) 

@s to pass the value of the string memory variable (MemS) 

@named variable to pass the value of the named variable 

@b to pass the value of the batch string 

@c to pass the value of the compare string 

@d# to pass the value of the #th display string 

@n to pass the step number being executed at the time of the call 

@u# to pass the value of the #th UUT ID string 

@t# to pass the iteration value of a TRY block The # in @t# specifies the 

TRY block number (see MEMI/MEML 42 for details). 

@ps# to pass a PCB skip bitmap 

@psf# to pass a PCB skip-fail bitmap 

The # in @ps# and @psf# specifies a group of 16 PCBs; 1 specifies the map for PCBs 1 

through 16, 2 specifies the map for PCBs 17-32, etc. For @ps#, a bit is set if and only if the 

PCB is not skipped. For @psf#, a bit is set if and only if a PCB neither is skipped nor has 

failed any tests. See MEMI/MEML ranges 61 and 62 on page 14-26 for other methods. 

See display a picture on page 11-19 to the operator for an example EXEC step. 

If the first test title field is an unnamed string variable parameter, instead of a file name, then 

EXEC uses the first field of that string as the file name. A file name may include a path. Any 

fields that follow the file name obtained from a string variable are prepended to any other title 

field parameters and sent as command line parameters to the executable file. 

14-24



Memory Manipulation Test Types 

Parameter 

Test Type 

Title 

Range 


Description 

EXEC 

Name of routine to execute. If the name has special characters, or strings, 

then the specified data is passed to the exec'ed routine as a parameter string. 

If no extension (e.g., .EXE or .COM) is specified, the System adds on, as a 

default, .EXE. See text above for more detail about passable parameters. 

Not used 

Not used 

To (+) Point Valid entries are 0,1,8, 32 plus optionally 2 or 4: 

0 = normal execution 

1 = do not generate or report Pass/Fail results 

2 = load DOS exit code from executed program into the integer 

memory variable (see MEMI) 

4 = load DOS error code from executed program the integer 

memory variable (see MEMI) 

8 = run executable routine and continue without waiting for it to terminate 

32 = perform CheckSum custom handshaking, used with CheckSum 

supplied utilities. 

Low Limit 

Not used 

High Limit 

Not used 

Note: 

Most user written executables run via EXEC are console mode Windows programs. This 

includes whether a DOS window is displayed during execution, the size of any such window 

and whether any window will automatically close on exit. 

Sequential EXECution of an executable causes the system software to wait for closure of any 

window displayed for program execution. 



Overview 

The memory manipulation test types (MEMI / MEML on page 14-26, MEMR / MEMD on 

page 14-30, MEMS on page 14-32) allow use of the System's memory to assign, keep track of, 

manipulate, and use variables within a test program. 

Additional programming information is described in the section Use of Program Memory 

Locations on page 10-39. 

There are five types of memory variables: 

1. The 16-bit integers can be whole numbers ranging from -32,768 to +32,767. The test-type 

that works with the memory-integer variable is MEMI. 

2. The 32-bit integers can be whole numbers ranging from - 2,147,483,648 to 

+2,147,483,647. The test-type that works with the memory-integer variable is MEML. 

14-25




3. The 48-bit floating point real variables include a fractional part and can range from plus to 

minus 10E±37. The test-type that works with the memory-real variable is MEMR. 

4. The 64-bit (IEEE floating point) real variables include a fractional part and can range from 

plus to minus 9.99999E±307. The test-type that works with the memory-real variable is 

MEMD. 

5. String variables can be up to 255 characters long and can include any normal ASCII 

characters. The test-type that works with the memory-string variable is MEMS. There are 

several system-defined string variables: 

– Memory String (memory string) 

– Compare String (compare string) 

– UUT Serial Number String 

– Assembly Name String 

– Batch ID String 

– Test Title String 

– Batch Report Special String 

– Test Report Special String 

– User Name String (see MemS Range 67) 

– System ID String (read only) 

The memory string can be up to 255 characters long. The Compare String variable (referred to 

as the "compare string" in the MEMS test type) can be used to make pass/fail comparisons 

against the memory string variable. The UUT Serial Number String is an array of 321 strings 

(accessible using MEMS 33). There is one Test Title String for each test step. 

The "Batch ID String" is only cleared between batches. As such, you can use it to solicit input 

about the batch as a whole (e.g., batch number, UUT configuration), then not ask the operator 

again until a new batch has started. You can do this by checking to see if the batch memory 

string is empty, and if so, asking the operator to enter it. 

These steps allow entry or assignment of the memory contents, pass/fail test generation based 

on the value of the memory contents, fundamental math and manipulation of the memory 

contents, transfer of control based on the contents of memory, or display of the variable. 

These test steps can be used to form a counter, to control program execution based on operator 

entry, or as an alternate way to generate test results based on operator entry. 

• Memory Manipulation (Integer) below 

• Memory Manipulation (Real) on page 14-30 

• Memory Manipulation (String) on page 14-32 

Memory Manipulation (Integer) 

Allow manipulation of the number in the integer memory variable. The name in the To (+) 

Point specifies the named integer variable. The To (+) Point is left blank to specify the 

unnamed integer memory variable. Use MemI for 16-bit signed integer values (-32,768 to 

+32,767) and MemL for 32-bit signed integer values (-2,147,483,648 to +2,147,483,647). 

14-26




Parameter 

Test Type 

Title 

Range 

Description 

MEMI (16-bit integer) or MEML (32-bit integer) 

Description of the test step, or label of the jump destination for jumps based on the 

memory number (used when range is 20 - 23). 

Type of operation to perform on the integer memory: 

1 = Copy the value of the Low Limit of this test step into the integer memory. 

2 = Perform a pass/fail test based on the value of the integer memory as compared 

to the test step High and Low Limits. 

3 = Copy the keyboard entry into the integer memory. The entry cursor is positioned 

in the column/row of the display as indicated by the Low/High Limits respectively. 

4 = Same as 3, but accept one character only with no [Enter] key required. 

5 = Display the value of the integer memory at the column/row of the display as 

indicated by the Low/High Limits respectively. 

6 = Write the value of the integer memory to a file named in the test title. 

7 = Set the value of the integer memory from a file named in the test title. 

8 = Perform a logical shift-left operation on the integer memory by the number of bits 

specified by the value in the Low Limit. 

9 = Perform a logical shift-right operation on the integer memory by the number of 

bits specified by the value in the Low Limit. 

10 = Add the value in Low Limit to the integer memory. To subtract, use a negative 

number for the value. 

11 = Multiply the integer memory by the value in the Low Limit. To divide, use a value 

between 1 and 0 (also see range 24). 

12 = Perform a logical 'and' operation on the integer memory with the value in the Low 

Limit. 

13 = Perform a logical 'or' operation on the integer memory with the value in the Low 

Limit. 

14 = Perform a logical 'not' operation on the integer memory. 

15 = Copy the contents of the integer memory into the sequence counter used by the 

RPRTS test type. 

16 = Copy the contents of the integer memory into the High Limit of the next test step. 

This can be used, for example, to set the output for a DIGO command. 

17 = Copy the contents of the integer memory into the real memory variable. 

18 = Read the specified test program data into the integer memory. If the Low Limit 

does not have a plus or minus sign, the number is the step number of the test 

program. If the Low Limit has a plus (+) sign then the step number is the number 

forwards from the current step. If the Low Limit has a minus (-) sign then the step 

number is the number backwards from the current step. The High Limit indicates 

the data of that step number to read: 

1 = From Point, 2 = To Point, 3 = Test Range, 4 = Low Limit, 5 = High Limit, 

6 = Measured, 7 = Nominal 

19 = Write the value in integer memory into the specified test program location. If the 

Low Limit does not have a plus or minus sign, the number is the step number of 

the test program to write into. If the Low Limit has a plus (+) sign then the step 

number is the number forwards from the current step. If the Low Limit has a minus 

(-) sign then the step number is the number backwards from the current step. The 

High Limit indicates the data of that step number to write: 



20 = Jump to the label in the Test Title if the value of the integer memory is greater 

than or equal to the Low Limit and less than or equal to the High Limit. 

14-27




21 = Jump to the label in the Test Title if the value of the integer memory is less than 

or equal to the High Limit. 

22 = Jump to the label in the Test Title if the value of the integer memory is greater 

than or equal to the Low Limit. 

23 = Jump to the label in the Test Title if the value of the integer memory is less than 

the Low Limit or greater than the High Limit. 

24 = Divide the integer memory by the integer part of the Low Limit. 

25 = Set the integer memory to the step number of the last failed step or to zero if no 

failures. 

26 = Set the integer memory to the current jump error count. 

27 = Set the integer memory to the current system error count. 

28 = Set the integer memory to the length of the memory string variable. 

29 = Add the ASCII value of the character on page 14-36 in the Low Limit location of 

the memory string to the integer memory and subtract the High Limit from the 

integer memory. 

30 = Swap the integer memory and the total number of assemblies tested in this batch. 

31 = Swap the integer memory and the total number of assemblies that have failed in 

this batch. 

32 = Load integer memory with the eight bit keyboard mask value. 

33 = Load the keyboard mask value with the lower eight bits in integer memory, 

see the Operator Keyboard Use on page 4-8 for keyboard mask bit information. 

34 = Append the value of the integer memory as a line at the end of the file named in 

the Test Title. 

35 = Open the file named in the Test Title, read the data on the line that is specified by 

the Low Limit, and set the integer memory to the value on that line. If there is a 

read error or if the line doesn't contain a valid integer representation, then the 

integer memory is unchanged and a fail beep is emitted. 

36 = Set keyboard LEDs according to the two least significant integer memory bits. A 

value of 0 clears the LEDs, 1 turns on the TESTING LED, 2 turns on the PASS 

LED, 3 turns on the FAIL LED. 

37 = Set the integer memory to the starting IO address configured for the specified 

module. For modules with a Board Select Address, the integer memory is set to 

the Board Select Address. The module type is specified by the Low Limit: 

15 = PS-UUT 

Specifies a check on PS-UUT configuration address. The High Limit indicates the 

supply number to verify, between 1 (first PS-UUT configured address, normally 

address 6) and 8 (last PS-UUT address, normally 13). If the returned address is 

positive then a PS-UUT is configured at that address setup (PS-UUT address 6, 7, 

up to 13), see Installing PS-UUT-L1 on page 13-3. The return value is -1 if there is 

no PS-UUT or if the High Limit is out of bounds. 

38 = Controls the Measurement 'Warnings' and 'Errors' messages setup based on the 

high limit bits 0 and 1, respectively, using the low limit. If the low limit is 1, then the 

current setup is saved before the selected setup is changed. If the low limit is 0, 

then the current setup is not saved before the selected setup is changed. If the 

low limit is 2, the previous saved setup is restored. For example, if the low limit is 0 

and high limit is 2 then the 'Warnings' messages are disabled and the 'Errors' 

messages are enabled (the setup prior to this step is not stored). 

40 = Sets the integer memory to the current number of errors for the currently tested 

PCB if the Low Limit is less than or equal to -1. Otherwise, it is set to the number 

of errors for the PCB number (0 to 320) specified in the Low Limit. 

41 = Sets the number of errors of the currently tested PCB to the High Limit value if the 

Low Limit is less than or equal to -1. Otherwise, the number of errors for the PCB 

number (0 to 320) specified in the Low Limit is set to the High Limit value. 

14-28




42 = Sets the integer memory to the iteration number of the specified TRY block. A 

TRY block is defined by the LABEL TRY and ERROR TRY test steps. The Low 

Limit specifies the TRY block number. The outermost TRY block is number 1 and 

the block numbers increment with nesting depth. There can be up to 5 nested 

TRY blocks. 

43 = Sets the integer memory to 1 if the test program test sequence was terminated 

before completing, or to 0 otherwise. 

44 = Sets the integer memory to 1 if current testing is a Failures Only ReProgram, or to 

0 otherwise. 

45 = Swap the integer memory and the test Environment setting for Max Errors limit 

value. 

46 = Sets the integer memory to 1 if current testing is a repeat test (e.g., F2 

ReProgram or Failures Only ReProgram) of the assembly, or to 0 if it is an F1 

Test. 

47 = Sets the integer memory to 1 if the file named in the Test Title exists, or to 0 

otherwise. 

50 = Sets the integer memory specified in the To (+) Name to the value of the integer 

memory specified in the From (-) Name. 


memory specified in the From (-) Name added to the value of the integer 

memory specified in the To (+) Name. 


memory specified in the From (-) Name subtracted from the value of the integer 



memory specified in the From (-) Name times the value of the integer memory 

specified in the To (+) Name. 


memory specified in the From (-) Name divided by the value of the integer 


55 = Swaps the integer memory specified in the To (+) Name with the integer 



memory specified in the From (-) Name AND'ed with the value of the integer 



memory specified in the From (-) Name OR'ed with the value of the integer 


58 = For MEMI, sets the integer memory(MemI) to the integer memory(MemL). For 

MEML, sets the integer memory(MemL) to the integer memory(MemI). 

59 = Sets the integer memory specified in the To (+) Name to a random value that is 

greater than or equal to the Low Limit and less than or equal to the High Limit. 

60 = Sets the integer memory specified in the To (+) Name to the Low Limit minus the 

value of the integer memory specified in the From (-) Name. 

61 = Sets the designated integer memory variable to a bit mask corresponding to an 

interval of PCBs that are not skipped and are passing. The PCB interval starting 

PCB number is set in the Low Limit and the ending PCB is set in the High Limit. 

The starting PCB status is in bit 0 of the result and successive PCBs in successive 

bits. For the MEMI commands the maximum number of PCBs in the interval is 16. 

For the MEML commands the maximum number of PCBs in the interval is 32. 

62 = Sets the designated integer memory to a bit mask corresponding to an interval of 

PCBs that are not skipped and are failing. See range 61 for additional details. 

63 = Swaps the integer memory with an offset used by the Display steps that follow. 

The initial default Display (Disp) offset is 0 but by setting the offset with this range 

14-29





To (+) Point 

Low Limit 

High Limit 

you can select "a new section of the DISP messages", e.g. to change from English 

to Spanish operator messages. 

64 = Changes the PCB skip selection. The integer memory variable is used to update 

the PCB skip selection. A set bit (1) causes the corresponding PCB to be skipped 

and a cleared bit (0) causes the PCB to be tested. The Low Limit specifies the 

lowest index of the PCB to be updated by the MEMI / MEML bit mask and the High 

Limit specifies the ending PCB index. For MEMI, the skip status of at most 16 

PCBs can be updated by one step. For MEML, the skip status of at most 32 PCBs 

can be updated by one step. 

65 = Returns the status byte of the PS-UUT-L1 whose number is specified by the Low 

Limit value. Sets the integer memory variable to the byte value. The specific 

status byte is determined by the High Limit. A High Limit of 1 will return the PS- 

UUT-L1 "STAT?" register and a High Limit of 2 will return the "FLT?" register, see 

the PS-UUT-L1 Model GENH 60 - 12.5 Technical Manual section 7.11.2 for 

details. During typical PS-UUT-L1 use, these bits are only useful if a supply is 

operated at the margins where it may reach thermal limit or go into foldback. Test 

programs may need to react accordingly. 

Not used 

Not used 

See range assignment for usage 


Memory Manipulation (Real) 

Allow manipulation of the real memory (floating point) variable. The name in the To (+) 

Point specifies the named real variable. The To (+) Point is left blank to specify the unnamed 

real memory variable. Use MemR for 48-bit floating point real values and MemD for 64-bit 

IEEE floating point real values. 

14-30




Parameter 

Test Type 

Title 

Range 

Description 

MEMR (48-bit real) or MEMD (64-bit real) 

Description of the test step, or label of the jump destination for jumps based on the 

memory number (used when range is 20-23). 

Type of operation to perform on the real memory: 

1 = Copy the value of the Low Limit of this test step into the real memory. 

2 = Perform a pass/fail test based on value of the real memory as compared to the 

test step High and Low Limits. 

3 = Copy the keyboard entry into the real memory. The entry cursor is positioned in 

the column/row of the display as indicated by the Low/High Limits respectively. 


5 = Display the real memory value at the column/row of the display as indicated by the 

Low/High Limits respectively. 

6 = Write the value of the real memory to a file named in the Test Title. 

7 = Set the value of the real memory from a file named in the Test Title. 

10 = Add the value in the Low Limit to the real memory. To subtract, use a negative 

number for the value. 

11 = Multiply the real memory by the value in Low Limit. To divide, use a value 

between 1 and 0 (also see range 24). 

16 = Copy the contents of the measured value from the last test step into real memory. 

This can be used, for example, to obtain a measured value, then make calculations 

based on the outcome. 

17 = Copy the contents of the real memory into the integer memory. If the value is 

greater than 32,767, transfer the number -1 as an error indication. 

18 = Read the specified test program data and load it into the real memory. If the Low 

Limit does not have a plus or minus sign, the number is the step number of the test 



number is the number backwards from the current step. The High Limit indicates 

the data of that step number to read: 



19 = Write the value in real memory into the specified test program location. If the Low 

Limit does not have a plus or minus sign, the number is the step number of the test 

program to write into. If the Low Limit has a plus (+) sign then the step number is 

the number forwards from the current step. If the Low Limit has a minus (-) sign 

then the step number is the number backwards from the current step. The High 

Limit indicates the data of that step number to write: 



20 = Jump to the label in the Test Title if the value of real memory is greater than or 

equal to the Low Limit and less than or equal to the High Limit. 

21 = Jump to the label in the Test Title if the value of real memory is less than or equal 

to the High Limit. 

22 = Jump to the label in the Test Title if the value of real memory is greater than or 

equal to the Low Limit. 

23 = Jump to the label in the Test Title if the value of real memory is less than the Low 

Limit or greater than the High Limit. 

24 = Divide the real memory by the Low Limit. 

26 = Copy the current time (in seconds past midnight) into the time memory. 

27 = Copy the current time (in seconds past midnight) into the real memory. 

14-31




28 = Wait until the number of seconds specified in the Low Limit has past since the time 

memory has been saved (see range 26), then continue to the next test step. 

29 = Compute the amount of time (in seconds) since the time memory has been saved 

(see range 26) and place the result in the real memory. 

30 = Swap the contents of the real memory and the time memory. 

31 = Sets the real memory to the measured value of the closest lower-numbered, 

unskipped, test step that generates a pass/fail result. For example, jumps (e.g., 

JMPR) do not generate pass/fail results. 

32 = Convert the real memory into the memory string having a maximum string width 

specified by the Low Limit value and having the number of digits to the right of the 

decimal point specified by the High Limit. The High Limit must be less than or 

equal to the Low Limit amount. 

33 = Append the value of the real memory as a line at the end of the file named in the 

Test Title. 

35 = Open the file named in the Test Title, read the data on the line that is specified by 

the Low Limit, and set the real memory to the value on that line. 

36 = Sets the real memory value to -1 if the selected PCB has not yet been tested, set 

to 0 if tested and so far passing, or set to 1 if it has already failed. The PCB 

selection is specified by the Low Limit if the Low Limit value is between 1 and 320. 

Otherwise, the PCB selection is the current PCB. 

50 = Sets the real memory specified in the To (+) Name to the value of the real 



memory specified in the From (-) Name added to the value of the real memory 



memory specified in the From (-) Name subtracted from the value of the real 



memory specified in the From (-) Name times the value of the real memory 



memory specified in the From (-) Name divided by the value of the real memory 


55 = Swaps the real memory specified in the To (+) Name with the real memory 

specified in the From (-) Name. 

58 = For MEMR, sets the real memory(MemR) to the real memory(MemD). For 

MEMD, sets the real memory(MemD) to the real memory(MemR). 

59 = Sets the real memory specified in the To (+) Name to a random value that is 

greater than or equal to the Low Limit and less than or equal to the High Limit.. 

60 = Sets the integer memory specified in the To (+) Name to the Low Limit minus the 

value of the integer memory specified in the From (-) Name. 

61 = Sets the integer memory to the square root (SQRT) for non-negative numbers. 

For negative numbers, the function is -SQRT(ABS(integer memory)), where ABS 

means absolute value. 

Memory Manipulation (String) 

Allow manipulation of the characters in the memory string and other strings. The name in the 

To (+) Point specifies the named string variable. The To (+) Point is left blank to specify the 

unnamed memory string variable. The ASCII decimal character table on page 14-36 is listed 

after the MEMS description table. 

14-32




Parameter 

Test Type 

Title 

Range 

Description 

MEMS 

Description of the test step, or as described below. 

Type of operation to perform on the memory string variable: 

1 = Copy the character string in the Title of this test step to the memory string. 

2 = Perform a pass/fail test based on the memory string being equal to the compare 

string (Pass) or not equal (Fail). 

3 = Copy the keyboard entry into the memory string. The entry cursor is positioned in 

the column/row of the display as indicated by the Low/High Limits respectively. 


5 = Display the memory string at the column/row of the display as indicated by the 

Low/High Limits respectively. 

6 = Write the memory string to a file named in the Test Title. 

7 = Set the memory string from the contents of a file named in the Test Title. 

9 = Add the string in the Test Title to the beginning of the memory string. 

10 = Add the string in the Test Title to the end of the memory string. 

11 = Make the memory string upper case. 

12 = Convert the memory string to a sub-string starting at the Low Limit character 

number and being High Limit characters long. 

13 = Copy the memory string to the UUT Serial Number of the test results. 

14 = Copy the Assembly Name into the memory string. 

15 = Swap the contents of the memory string and the compare string. 

16 = Convert the memory string to an integer variable and put the result into the 

integer memory. If there is an error, convert it to -1. 

17 = Convert the memory string to a real variable and put the result into the real 

memory. If there is an error, convert it to -1. 

. 18 = Swap the contents of the Batch ID string with the contents of the memory string. 

19 = Copy the contents of the Batch ID string to the memory string. 

20 = Jump to the label in the Test Title if the memory string is the same as the 

compare string. 

21 = Jump to the label in the Test Title if the memory string is not the same as the 

compare string. 

22 = Jump to the label in the Test Title if the memory string is less than the compare 

string (when compared on an ASCII basis - see ASCII decimal character table on 

page 14-36). 

24 = Copy the Test Title of the specified test program step into the memory string. If 

the Low Limit does not have a plus or minus sign, the number is the step number 

of the test program. If the Low Limit has a plus (+) sign then the step number is the 

number forwards from the current step. If the Low Limit has a minus (-) sign then 

the step number is the number backwards from the current step. 

25 = Copy the memory string into the specified test program Test Title. If the Low Limit 

does not have a plus or minus sign, the number is the step number of the test 



number is the number backwards from the current step. 

26 = Swap the memory string with the system memory string variable SystemString1. 

This variable, SystemString1, is a spare memory location. 

27 = Swap the memory string with the system memory string variable SystemString2. 

This variable, SystemString2, is a spare memory location. 

28 = Append to the end of the memory string the character whose ASCII value equals 

14-33




the integer memory value plus that in the test step High Limit. 

29 = Copy the UUT Serial Number string into the memory string. 

30 = Copy the memory string into the Batch Report Special string. 

31 = Copy the memory string into the Test Report Special string. 

32 = Write the contents of the memory string to the end of the file named in the Test 

Title. 

33 = Swap the memory string with the UUT Serial Number string identified by the 

Low Limit index. A Low Limit value of 0 accesses the UUT Serial Number string 

for one UUT Serial Number string per panel. For multiple UUT Serial Numbers 

per panel, the Low Limit value equal to the PCB number accesses the UUT Serial 

Number string for that PCB. 

. 34 = Add the Test Title of the test step identified in the Low Limit to the beginning of the 

memory string. If the Low Limit does not have a plus or minus sign, the number 

is the step number of the test program. If the Low Limit has a plus (+) sign then the 

step number is the number forwards from the current step. If the Low Limit has a 

minus (-) sign then the step number is the number backwards from the current 

step. 

35 = Open the file name specified in the Test Title, read the data from the line that is 

specified by the Low Limit, and set the memory string to the data on that line. 

36 = Append the Test Title of the test step identified in the Low Limit to the end of the 

memory string. If the Low Limit does not have a plus or minus sign, the number 

is the step number of the test program. If the Low Limit has a plus (+) sign then the 

step number is the number forwards from the current step. If the Low Limit has a 

minus (-) sign then the step number is the number backwards from the current 

step. 

37 = Get a message line from User Display into memory string (row line = Low Limit). 

38 = Get a line of Display Attributes from User Display into memory string (row line = 

Low Limit). 

39 = Write a line of Display Attributes from memory string to User Display Area (row 

line = Low Limit). 

40 = Write the memory string into the specified test program Test Title in the same 

manner as MEMS 25. In addition, any Test Title changes for JMP or LABEL 

operations are recognized by the system software. 

41 = Set the memory string to the current date in YYYYMD format (see Range 48). 

42 = Copy the System ID on page 5-15 string into the memory string. 

43 = Set the memory string to the test system software type: MultiWriter pps 

44 = Set the memory string to the name of the currently executing test program. 

45 = Set the memory string to the name of the calling program if the currently 

executing test program was called with a RUNT or to an empty string otherwise. 

46 = Deletes the file specified in the memory string. The memory string may include 

a path preceding the file name. 

47 = Set the memory string to the operator Display Message specified by the number 

in the Low Limit. 

48 = Set the memory string to the current date in YYYYMMDD format. 

50 = Set the memory string specified in the To (+) Name to the memory string 


51 = Add the memory string specified in the From (-) Name to the beginning of 

memory string specified in the To (+) Name. 

52 = Add the memory string specified in the From (-) Name to the end of memory 

string specified in the To (+) Name. 

55 = Swaps the memory string specified in the To (+) Name with the memory string 


14-34




56 = Reads the PCB skip selections from the memory string named file, displays 

warning if Low Limit bit mask 1 set and file missing, displays error message and 

aborts program execution if Low Limit bit mask 2 set and file missing, uses file 

indirection if Low Limit bit mask 4 set, deletes file after read if Low Limit bit mask 8 

is set. See MemS Range 63 to write a PCB skip file. 

57 = Reads the PCB skip selections from the system configured input file (see Configure 

Directories/Locations on page 5-16), displays warning if Low Limit bit mask 1 set 

and file missing, displays error message and aborts program execution if Low Limit 

bit mask 2 set and file missing, uses file indirection if Low Limit bit mask 4 set, 

deletes file after read if Low Limit bit mask 8 is set. See MemS Range 63 to write a 

PCB skip file. 

58 = Reads the PCB skip selections from the Select Skipped PCBs selection window, 

see Select Skips on page 7-18. 

59 = Reads the UUT serial numbers from UUT ID entry window. 

60 = Reads the UUT serial numbers from the memory string named file, displays 

warning if Low Limit bit mask 1 set and file missing, displays error message and 

aborts program execution if Low Limit bit mask 2 set and file missing, uses file 

indirection if Low Limit bit mask 4 set, deletes file after read if Low Limit bit mask 8 

is set. See MemS Range 64 to write a UUT IDs (e.g., serial numbers) file. 

61 = Reads the UUT serial numbers from system configured input file (see Configure 

Directories/Locations on page 5-16), displays warning if Low Limit bit mask 1 set 

and file missing, displays error message and aborts program execution if Low Limit 

bit mask 2 set and file missing, uses file indirection if Low Limit bit mask 4 set, 

deletes file after read if Low Limit bit mask 8 is set. See MemS Range 64 to write a 

UUT IDs (e.g., serial numbers) file. 

62 = Performs a Pass/Fail test of the UUT serial number (UUT IDs). The serial number 

is checked for a valid entry. An invalid (bad) entry can be ignored, prevented, or a 

warning dialog can be presented to the operator. The index limits the range of the 

PCB numbers that are tested. 

The test Title of the step "specifies" the allowed serial number format. 

The serial number format specifier is composed of regular ASCII characters and 

wild cards. If the Title contains an invalid format specifier, a message is given 

when the step is executed (e.g. override of a non-wild-card character, unexpected 

end of format string). The following is a description of the wild card characters and 

how to override these characters to use them as a required character. 

Wild card characters: 

a = one or more alpha characters 

d = one or more decimal characters 

. = one or more of any characters 

h = one or more hex characters 

\ = escape or override wild card (prefix) characters 

? = zero or one characters 

* = one or more characters 

! = one character 

Note: If the test Title is blank then only a blank serial number will pass. 

The Test window Environment menu on page 7-14 provides several selections to 

Check the UUT Serial Number. 

63 = Write the PCB skip selections to the memory string named file. 

64 = Write the UUT IDs (e.g., serial numbers) to the memory string named file. 

65 = Load the memory string variable with Configure > Environment > Directories > 

Locations entry. (Low Limit = 1 for Test Program path, 2 for Test Results Report 

path, 3 for Statistics Data path, 4 for Batch Report path, 5 for CAD Data path, 6 for 

runt folder path, 7 for temporary file path, 8 for Skip PCB file location, 9 for serial 

number file location.) 

66 = Performs a Pass/Fail test of UUT serial numbers (UUT IDs) for duplicates. The 

index limits the range of the PCB numbers that are tested. A duplicate entry can 

be ignored, prevented, or a warning dialog can be presented to the operator. 

14-35





To (+) Point 

Low Limit 

High Limit 

The Test window Environment menu on page 7-14 provides several selections to 

Check the UUT Serial Number. 

67 = Load the memory string variable with the name of the logged-in user. 

Not used 

Not used 



ASCII Decimal Character Table 

Dec Char Dec Char Dec Char Dec Char 

0 NUL null 32 space 64 @ 96 ` 

1 SOH start of heading 33 ! 65 A 97 a 

2 STX start of text 34 " 66 B 98 b 

3 ETX end of text 35 # 67 C 99 c 

4 EOT end of transmission 36 $ 68 D 100 d 

5 ENQ enquiry 37 % 69 E 101 e 

6 ACK acknowledge 38 & 70 F 102 f 

7 BEL bell 39 ' 71 G 103 g 

8 BS backspace 40 ( 72 H 104 h 

9 TAB horizontal tab 41 ) 73 I 105 i 

10 LF line feed, NL new line 42 * 74 J 106 j 

11 VT vertical tab 43 + 75 K 107 k 

12 FF form feed, NP new page 44 , 76 L 108 l 

13 CR carriage return 45 - 77 M 109 m 

14 SO shift out 46 . 78 N 110 n 

15 SI shift in 47 / 79 O 111 o 

16 DLE data link escape 48 0 80 P 112 p 

17 DC1 device control 1 49 1 81 Q 113 q 

18 DC2 device control 2 50 2 82 R 114 r 

19 DC3 device control 3 51 3 83 S 115 s 

20 DC4 device control 4 52 4 84 T 116 t 

21 NAK negative acknowledge 53 5 85 U 117 u 

22 SYN synchronous idle 54 6 86 V 118 v 

23 ETB end of trans. block 55 7 87 W 119 w 

24 CAN cancel 56 8 88 X 120 x 

25 EM end of medium 57 9 89 Y 121 y 

14-36



General Purpose Interface (GPIB) Bus I/O 

26 SUB substitute 58 : 90 Z 122 z 

27 ESC escape 59 ; 91 [ 123 { 

28 FS file separator 60 < 92 \ 124 | 

29 GS group separator 61 = 93 ] 125 } 

30 RS record separator 62 > 94 ^ 126 ~ 

31 US unit separator 63 ? 95 _ 127 DEL 


General Purpose Interface Bus (GPIB) I/O 

Overview 

Allows control of external instrumentation connected via the IEEE-488 interface. Use of this 

capability requires an optional GPIB interface that is available from CheckSum. 

The GPIB can be used for most common IEEE-488 operations by use of the GPIB test step. 

In general, when using the GPIB test type, you will specify the address of the instrument on 

the bus. 

When writing information to the bus, you can choose from sending the information in the test 

title (the To (+) Point is 0 in this case), sending the information in a display line (just like the 

data used for the DISP test type - the To (+) Point is 1 in this case), sending information from a 

disk file (the To (+) Point is 37 in this case and the test title contains the name of the file to 

open and read), or you can directly send the contents of a memory variable (the To (+) Point is 

38, 39, and 40 for the memory string (MEMS), real memory (MEMR), and integer memory 

(MEMI) respectively). Note that any string can be loaded into the memory string that then can 

be used by Output to GPIB device operation. Use MemS Range 50 to load the memory string 

from another string variable and MemS Range 47 to load any operator display string into the 

memory string. 

When reading information from the bus, you can specify that the returned information goes 

into a memory location (the To (+) Point is 0, 1, and 2 for the real memory (MEMR), memory 

string (MEMS), and integer memory (MEMI) respectively), or to send the data to a disk file 

(the To (+) Point is 3 in this case and the test title contains the name of the file to create and 

write to). 

GPIB Test Type parameters: 

14-37




Input from GPIB Device (i.e. enter) 

Parameter 

Description 

Range 0 


Device address 

To (+) Point 

0 = Input a number into the real memory (see MEMR) 

1 = Input a string into the memory string (see MEMS) 

2 = Input an integer into the integer memory (see MEMI) 

3 = Input data and write the data into the file named in the Title 

Output to GPIB Device (i.e. output) 

Parameter 

Description 

Range 1 



To (+) Point 

0 = Output the data in the Title 

1-36 = Output the data in the Operator DISPLAY area 

37 = Output the data from the file named in the Title 

38 = Output the data from the memory string (see MEMS) 

39 = Output the data from the real memory (see MEMR) 

40 = Output the data from the integer memory (see MEMI) 

Abort (i.e. abort) 

Parameter 

Range 2 

Device Clear (i.e. devclr) 

Parameter 

Description 

Description 

Range 3 


>0 = Selected device clear 

0 = Full bus device clear 

Set Bus Terminators (i.e. eol) 

Parameter 

Description 

Range 4 



Title 

a,b,c,d (default is 0,0,10,13,10) where: 

a = Output termination (default is 0) 

0 = EOL (End-Of-Line) string and EOI (End Or Identify) 

with last character 

1 = EOI with last character only 

2 = EOL string (End-Of-Line) only 

b = Input termination (default is 0) 

0 = Input end-of-line (see c below) or EOI 

1 = EOI (End Or Identify) only 

c = Input end-of-line termination, decimal ASCII code on page 

14-36 of the 

input termination character (default is 10 for line feed) 

14-38




I/F Init (i.e. init) 

Parameter 

d = EOL string, comma-separated decimal ASCII code of the 

character string (up to 8 characters, default is 13,10 

which is carriage return then line feed) 

Description 

Range 5 

From (-) Point GPIB address [21] 

To (+) Point total of [0]: 

32768 background DMA 

16384 block DMA 

4096 fast 

32 non-system controller 

16 IRQ 2 

17 IRQ 3 

19 IRQ 5 

21 IRQ 7 

1 DMA 1 

2 DMA 2 

3 DMA 3 

Local Lockout (i.e. llo) 

Parameter 

Description 

Range 6 



Remote (i.e. remote) 

Parameter 

Description 

Range 7 



User Command (i.e. send) 

Parameter 

Description 

Range 8 

To (+) Point 

0 = Send the data in the Title 

1-36 = Send the data in the Operator DISPLAY area 

37 = Send the data in the file named in the Title 

Serial Poll (i.e. spoll) 

Parameter 

Description 

Range 9 



Puts the serial poll result into the integer memory (MEMI) 

Status (i.e. status) 

Parameter 

Description 

Range 10 

14-39


RS232 Serial Interface I/O 


To (+) Point 

8 = Error number 

9 = Byte count 

Puts the result into the integer memory (MEMI) 

Timeout (i.e. timeout) 

Parameter 

Description 

Range 11 

To (+) Point 

>0 = Depends on microprocessor 

0 = Disable 

Trigger (i.e. trig) 

Parameter 

Description 

Range 12 





Overview 

Allows communication with serial port devices. 

The RS232 test type allows flexible input and output of data to the controller's COM ports 1 

through 4. Data strings of up to 255 characters can be transferred. When sending data, the 

data transmission can have an optional preamble and/or postamble string of up to 32 

characters. 

As alternatives to use of the RS232 test type, you can write a .EXE or .COM file and call it 

with the EXEC test type, or you can use the MEMS test type with a file name designating a 

serial port (e.g., COM1). 

When writing information to the port, you can choose between sending the information from 

the Test Title (the To (+) Point is 0 in this case), sending the information from a display line 

(just like the data used for the DISP test type - the To (+) Point is between 1 to 36 or 41 to 

999), sending information from a disk file (the To (+) Point is 37 in this case and the Test Title 

contains the name of the file to open and read), or you can directly send the contents of a 

memory variable (the To (+) Point is 38, 39, and 40 for the memory string (MEMS), real 

memory (MEMR), and integer memory (MEMI) respectively). Note that any string can be 

loaded into the memory string that then can be used by Output to RS232 device operation. Use 

MemS Range 50 to load the memory string from another string variable and MemS Range 47 

to load any operator display string into the memory string. 

When reading information from the port, you can specify that the returned information goes 

into a memory location (the To (+) Point is 0, 1, and 2 for the real memory, memory string, 

and integer memory respectively), or to send the data to a disk file (the To (+) Point is 3 in this 

case and the test title contains the name of the file to create and write to). 

14-40




A cable with the following wiring can be used between two RS232 interfaces: 

1 

2 

3 

4 

5 

6 

7 

8 

9 

Computer to Computer 

1 

2 

3 

4 

5 

RS-232 Cable Connections 

1 = Carrier Detect 

6 2 = Receive Data 


7 4 = Data Terminal Ready 


8 

6 = Data Set Ready 

7 = Request to Send 

8 = Clear to Send 

9 

9 = Ring Indicator 

DB9 

(female) 

DB9 

(female) 

Computer to Simple Serial Device 

1 

2 

3 

4 

5 

6 

7 

8 

9 

1 

2 

3 

4 

5 

6 

7 

8 

9 

2 = Receive Data 



DB9 

(female) 

DB9 

RS232 Test Type parameters: 

14-41




Input from RS232 Device 

Parameter 

Description 

Range 0 


Device address of desired COM port (e.g., 1 for COM1) 

To (+) Point 

0 = Input a number into the real memory (see MEMR) 

(destination of data read) 1 = Input a string into the memory string (see MEMS) 

2 = Input an integer into the integer memory (see MEMI) 

3 = Input data and write the data to the file named in the Title 

Output to RS232 Device 

Parameter 

Description 

Range 1 



To (+) Point 

0 = Output data from the Title 

(source of data sent) 

1 to 36 = Output data from the Operator DISPLAY lines 

37 = Output data from the file named in the Title 

38 = Output data from the memory string (see MEMS) 

39 = Output data from the real memory (see MEMR) 

40 = Output data from the integer memory (see MEMI) 

41 to 999 = Output data from the Operator DISPLAY lines 

Device Clear 

Parameter 

Description 

Range 3 


>0 = Clear status for COM port number (e.g.,1 for COM1) 

0 = Clear status for all COM ports 

Set Communication Parameters 

Parameter 

Description 

Range 4 



To (+) Point 

Parameter, specified in the Test Title, is initialized: 

0 = Setup the UART communication parameters. The baud 

rate, data length, parity, and stop bit length are respectively 

defined by comma separated values in the Test Title, such 

as 9600,8,N,1. The parity is specified by a single character 

and the other values by numeric values. The allowed baud 

rate is from 50 to 115200. The data length is from 5 to 8. 

Parity can be specified as N for None, E for Even, O for 

Odd, M for Mark, or S for Space. The stop bit length can 

be 1 or 2 bits. 

1 = Setup the optional transmission preamble. The default is 

no preamble. A non-null preamble is specified by a 

sequence of decimal values for the ASCII characters on 

page 14-36 in the preamble. Each decimal value consists 

of the pound sign (#) followed by a decimal number in the 

range from 0 to 127. An empty string sets the preamble to 

null. 

14-42



Miscellaneous Tests 

Status 

Parameter 

2 = Setup the end of transmission postamble. The default is 

carriage return, line feed (#13#10). A non-null postamble is 

specified by a sequence of decimal values for the ASCII 

characters on page 14-36 in the postamble. Each decimal 

value consists of the pound sign (#) followed by a decimal 

number in the range from 0 to 127. An empty input string 

sets the postamble to null. 

Description 

Range 10 


0 = Check for any UART error status bit on any COM port 

Puts the result into the integer memory (see MEMI) 

>0 = Read status for this COM port number (e.g., 1 for COM1) 

Puts the result into the integer memory (see MEMI) 

Timeout 

Parameter 

Description 

Range 11 



To (+) Point 

0 = Disable I/O timeouts 

>0 = Number of 0.1 second increments to wait before timing 

out when a transmission should be active, but is not. The 

default timeout is 10 seconds. 

Close COM Port 

Parameter 

Description 

Range 12 



To (+) Point 

Used to close the desired COM port. 

This range closes a COM port opened by previous RS232 

operations on the port and by any previous PS-UUT-L1 power 

supply control steps when the specified port is 1 for COM1. 

This range allows swapping between "standard" control of PS- 

UUT-L1 supplies via the test types that control the PS-UUT-L1 

supplies (DCI, DCV, PWRMn, JMPWR, and MEMI) and 

"custom" control of PS-UUT-L1 supplies via RS232 commands. 

It also allows COM port sharing between RS232 steps and 

other applications during execution of a test program. 



Overview 

The topics in this category are as follows: 

• Turn Fixture Vacuum On and Off on page 14-44 

14-43




• Fixture Control on page 14-45 

• Pause a Specified Time on page 14-48 

• Self-test Module on page 14-48 

• BreakPoint on page 14-49 

• Print Test Results on page 14-49 

• Sound the PC's Beeper on page 14-52 

• Put a Remark in the Test Program on page 14-52 

• Conditional Test Report Output on page 14-52 

Turn Fixture Vacuum On and Off 

Turns vacuum on and off to the test fixture. For applying air pressure, see the FIXCT on page 

14-45 test type. 

This test-type controls one of two fixture control bits available from the system controller. 

Vacuum-on is a low output and vacuum-off is a high output. 

Use of Fixture Ready 1 and Fixture Ready 2 fixture close left and right status inputs for 

starting program execution is provided by the Test Window > Environment > Program Start 

menu and the main window Edit > Edit Program CheckList > Program Start Option selection. 

The connector for wiring to the fixture is on the MW FIX I/O on page 6-13 module. 







If a fixture safety rule fails, the system will alert the operator with a pop-up message: 

Fixture Lid Identification Test Failed 

Check of fixture top before closing fixture failed within a FixCt or Vacum step. 

Fixture Base Identification Test Failed 

Check of fixture bottom before closing fixture failed within a FixCt or Vacum step. 

The menu selection Measure > Step Analysis F6 in the editor provides an easy to use, push 

button method, to setup this test step. 

14-44




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

VACUM 

Optional Comment Field 

Sum of the following: 

0 - Remove vacuum from fixture 

1 - Apply vacuum to fixture via Fixture 1 control 

2 - Apply vacuum to fixture via Fixture 2 control 

3 - Apply vacuum to fixture by activating both Fixture 1 

and Fixture 2 controls 

Not used. 

Not used. 

Not used. 

Not used. 


Engages and Disengages CheckSum Pneumatic fixture systems. 

The FIXCT command allows the test program to control the automated pneumatic systems. 

Like the VACUM on page 14-44 test type, the FIXCT test type controls the fixture using the 

two signals called Fixture 1 Control and Fixture 2 Control available on the system 

controller. 

Use of Fixture Ready 1 and Fixture Ready 2 fixture close left and right status inputs for 

starting program execution is provided by the Test Window > Environment > Program Start 

menu and the main window Edit > Edit Program CheckList > Program Start Option selection. 

The connector for wiring to the fixture is on the MW FIX I/O on page 6-13 module. 

14-45










If a fixture safety rule fails, the system will alert the operator with a pop-up message: 

Fixture Lid Identification Test Failed 

Check of fixture top before closing fixture failed within a FixCt or Vacum step. 

Fixture Base Identification Test Failed 

Check of fixture bottom before closing fixture failed within a FixCt or Vacum step. 

The menu selection Measure > Step Analysis F6 in the editor provides an easy to use, push 

button method, to setup this test step. 

14-46




Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

FIXCT 

Optional Comment Field 


0 - Disengage Fixture 1 and Fixture 2 

1 - Engage Fixture 1 

2 - Engage Fixture 2 

Not Used. 

Not Used. 

Not Used. 

Not Used. 

Control Relays 

The system motherboard controller supports RELAY range 0 which has two lines for in-fixture 

solenoid control (Fixture 1 Control/ and Fixture 2 Control/). 

The system supports three RELAY ranges that can be used for example to activate relays for 

board marking. The first MultiWriter controller supports RELAY ranges 1..3 (each range can 

control up to 8 relay control bits), the second MultiWriter controller supports ranges 4..6, and 

so on through the 8th MultiWriter controller. Each MultiWriter controls a MW FIX I/O on 

page 6-13 module in the fixture which has the hardware to actuate the three RELAY bytes. 

The connector for these relay control bytes is on the MW FIX I/O module on page 6-13 

(3800-102) in the fixture. 



14-47




Pause a Specified Time 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

PAUSE 

Not used 

Time to pause in milliseconds (0-32000 mSec) 

Not used 

Not used 

Not used 

Not used 

Self-test Module 

Performs system self-test of various modules. 


use, fill-in the form method, to select these settings. Following is the syntax of the STST test 

type: 

14-48




Parameters 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

STST 

Normally not used 

Normally not used 

Add 16384 to the range to obtain results without Pass/Fail indication 

Not used 

Not used 

Not used 

Mask bit. Sum of the following bits and for each bit set, perform the test: 

If Range = 1000 (USB) 

1 = test for module "connected" 

BreakPoint 

The breakpoint (BrkPt) test type opens a window with a snapshot of the current state of system 

variables and hardware settings during test step execution from either the Edit or Test screens. 

It is used as a debugging tool during test program development. The values and settings are 

only displayed and can not be changed in this window. The system variables include variables 

set via the MEM and FLAGS commands. The system hardware includes the DIG I/O 

resources, RELAY connections, and sourcing via Analog Source types. 

The breakpoint window has several tabs to display the various pages of information. At the 

right corner of each tab page is a selection button. Click on the button to make it become the 

selected tab page. A black dot will indicate the selection. The selected tab page will be 

displayed when the breakpoint test step is executed. Clicking on any tab shows the contents of 

that page. 

Note that the Test Point Sources screen (ranges 500 through 510) contains a Find Next button 

which automatically displays the next source from the Source list that has any test point 

connections. 

Parameters 

Test Type 

Title 

Range 

Description 

BRKPT 

Optional comment field 

100 – Displays System Variables 

200 – Displays System Flags 


To (+) Point 

Low Limit 

High Limit 

Not used 

Not used 

Not used 

Not used 

Print Test Results 

Allows the System to print or output the test results report from within a test program. The 

report is printed in the same format as configured for test results report specified in the 

Configure System > Environment > Configure Reporting > Test Results screen. This function 

14-49




can be used, for example, if a number of similar assemblies are tested repetitively in a loop 

without exiting the test execution between assemblies. (See also the ERROR step and title 

CLEAR ALL option for initializing the loop results before testing an assembly.) This test 

step also allows the system to programmatically change the SPC log data path or report data 

path and reconfigure automatic test reporting. 

For example, to print test result failures to a COM1 printer only when there are test failures use 

RPRTS range 10 with a test title of COM1. If you want the report to also include results from 

test steps that pass and output results to the default test report device (specified in the 

Configure System > Environment > Configure Reporting > Automatic Reports screen) then use 

a range of 74 and a blank title. To log to the SPC file "summary only" information, use a 

range of 36. To log to the SPC file "summary and failure" information, use a range of 164. To 

log to the SPC file "summary, failure and passing" information, use a range of 228. 

Note: The number of test failures shown in the output for the RPRTS step is the jump error 

count number, not the system error count number. Unlike the system error count displayed in 

the upper section of the test display, the jump error counter counts all failures that occur, even 

if the test step is subsequently repeated and passes. To set the jump error count number to the 

system error count, use the ERROR step with the title RESET before the RPRTS step, see 

Set Error Counter, Control Error-Based TRY Blocks on page 14-13. 

Notes: 

If data logging is done in a RPRTS step in a test program, then the elapsed 

time is not available and a time of 0 is logged. Logging both in a test 

program step and by automatic logging is not recommended. 

Doing SPC logging from program steps and by automatic SPC logging 

concurrently is not recommended as the Production Report would show 

double counting of UUTs. 

14-50




Parameter 

Test Type 

Title 

Range 

Description 

RPRTS 

Output device. For example: LPT1, COM1, @WP, or a file name. 

Using @WP specifies that the report be sent to the default 

Windows printer. If the title is @S then the contents of the 

memory string variable (see MemS on page 14-32) are used to 

specify the file name. 


1 = Include a sequence number in the test report to 

describe which assembly of the batch is being 

reported on. The sequence number starts over each 

time the test program is restarted. 

2 = Print results report to file named in test title or to 

the default test report output device if the title is blank. 

4 = Print results to SPC log. 

8 = Print report only if the jump error count is greater than 0. 

16 = Clear out all test results after report(s). 

32 = Report summary information. (For SPC only) 

64 = Report on test steps which pass. 

128 = Report on test steps which fail. (For SPC only) 

256 = Set SPC data path or Report data path to the 

memory string value, see From (-) Point note below. 

512 = Set Automatic Reporting Configuration, see 

To (+) Point note below. 

1024 = Print Batch Report to the output device named in the 

test title or to the default batch report device if 

the test title is blank. 

2048 = Update the Run Time failure statistics with the current 

test results, see From (-) Point note below. 

4096 = Print SPC Production Report to the output device 

named in the test title or to the default batch report 

device if the test title is blank. 

8192 = Print SPC Pareto Report to the output device 

named in the test title or to the default batch report 

device if the test title is blank. 

From (-) Point Used By Range = 256 

0 = update SPC data path from memory string value 

1 = update Report data path from memory string value 

Used By Range = 2048 

0 = decrement the test results (allows ReProgram results to be 

stored) 

1 = increment the test results 

To (+) Point Used By Range = 512 

1 = automatic report on failed assemblies 

2 = automatic report on passed and failed assemblies 

4 = automatic report of failed results data only (all results 

otherwise) 

Low Limit 

Not used 

High Limit 

Not used 

14-51




Sound the PC's Beeper 

Sounds the PC's beeper with either a single tone beep or the warble-like beep used during 

failures. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

BEEP 

Not used 

0 is normal beep. 1 is warble-like beep. 

Not used 

Not used 

Not used 

Not used 

Put a Remark in the Test Program 

Allows a test program remark for the purpose of test program documentation. The test step is 

ignored for all purposes other than being displayed or printed with the test program. 

Parameter 

Test Type 

Title 

Range 


To (+) Point 

Low Limit 

High Limit 

Description 

REM 

Remarks for test program documentation 

Not used 

Not used 

Not used 

Not used 

Not used 

Conditional Test Report Output 

This test type allows you to put a string of characters in the test results report based on whether 

the previous test passed or failed. For example, this can be used to provide hints, to the person 

repairing the assembly, based on the failures that have occurred. 

Use a range code of 0 if you would like to output the text in the test title of the test step into the 

test results file. Use a range code of 1-36 if you want to output the text from one of the 

operator display messages, or 1000 if you would like to output the contents of the memory 

string. 

You can output the string of data beginning at a specified column of the test report. The 

column number is placed in the 'From (-) Point' field. 

The Low Limit column specifies the condition that will cause the string to be included in the 

results. If the Low Limit is 1, the string is output only if the last test passed. If the Low Limit 

is 2, the string is output on a failed last test. If the Low Limit is 3, it is output in any case. The 

case of always can be used as a way to put a variable string in the results. 

An alternate use of the RSLTS test-type is to turn on and off reporting of test steps during 

program execution. For example, you may want to turn off detailed step reporting during part 

14-52




of the program if you are encapsulating a test. For this use of the RSLT test-type, use a range 

value of 2000, and place the reporting mode that you want to invoke in the Low Limit (1 = 

report on passing tests, 2 = reporting on failing tests, 3 = reporting on all tests, 4 = reporting on 

skipped tests). In this mode, you can use a range of 2001 to temporarily set a mode, then a 

range of 2002 to return to the previous mode of results reporting. 

For example, to output the text from the test title of this test step to column 5 of the test results, 

only if the previous step failed, use a range of 0, From (-) Point of 5, and a Low Limit of 2. 

For purposes of pass/fail status, the closest previous test step that generates test results is used. 

Steps such as REMarks and LABELs are ignored. 

Parameter 

Test Type 

Title 

Range 

Description 

RSLTS 

If the range is 0 and the reporting condition is true (see Low Limit), this step's 

Title is printed in the test results report. 

Source of text string to place in the test report if the reporting condition is true: 

0 = Use Comment from the Test Title 

1-36 = Use Comment from the Display Messages string of the same index 

1000 = Use Memory String for comment 


To (+) Point 

Low Limit 

High Limit 

Output reporting control of subsequent test steps: 

2000 = Report on any of the subsequent steps if, and only if, they have 

results matching outcomes specified in the Low Limit. 

2001 = Same as 2000 but in addition remember the current reporting strategy. 

2002 = Restore the results reporting strategy to what it was before the last 

use of RSLTS 2001. 

2010 = Do not Show Pass/Fail (see System Operation, Environment Menu on 

page 7-14) 

2011 = Show Pass/Fail 

2012 = Use 'Show Pass/Fail' setup from the last open/run of currently 

executing test file. 

Specifies the starting column location of the comment in the test report (applies if 

the range is below 2000). 

Not used 

Specifies the test result condition reported on. The sum of any of the following: 

1 = test steps which have passed 

2 = test steps which have failed 

4 = test steps which have been skipped 

Not used 

14-53




14-54

Chapter 15 

Sample Reports 


This section is composed of report examples. 

• Test Results Report Example below 

• Test Program Listing Example on page 15-2 

• Test Program in ASCII on page 15-3 

• Batch Report Example on page 15-6 

• Statistics Data File Example on page 15-6 

• Wire Run Report Example on page 15-7 

• Production Report Example on page 15-9 

• Pareto Failure Report Example on page 15-10 

• X-Bar/Sigma Report Example on page 15-11 

Test Results Report Example 

============================================================================ 

Test Results Report 

Testing Facility: 


Assembly Name: 5-Up Sun Ultra 24 

Failures: 0 

Report Date: 

Time: 

Test System: 

File Name: 

Jul 15, 2O10 

14:34 


MISP EXAMPLE 5.SPEC 

=============================================================================


Test Program Listing Example 


PCB Panel Pass/Fail Summary 

[P] 

[P] 

[P] 

[P] 

[P] 

============================================================================= 

From From To To Test Test Test 

Low High Measured 

Point--Name-- Point--Name-- -Type Range ----Title--- -Limit- -Limit- - 

Value-- 

PCB 0 

MemS 60 

Read UUT IDs 0.000 0.000 

MISP 1 

U21 Rev 2O10 0.0000 

End of data 

Test Passed, no failures... 

Example Test Results Report 

Note: An asterisk * at the end of the line indicates a Failed step. If the USB connection is not 

working, the measured value will show Fail. A measurement unit may follow Fail, such as 

FailV has the value Fail and unit of V, for Volts. 

Test Program Listing Example 

============================================================================ 

Test Program Listing 




File Name: 

File Date: 


Jul 15, 2O10 

Time: 14:28 

Test System: 


============================================================================ 

---From--- ---To--- ---------------Test----------------- --Limits-- -Nom- 


Rem 

Rem 

Rem 

MultiWriter 

Rev 2OO90715 

15-2



Test Program in ASCII 

PCB 1 

Rem 

PCB 2 

Rem 

PCB 3 

Rem 

PCB 4 

Rem 

PCB 5 

Rem 

PCB 0 

MemS 1 sns.xml 0.000 0.000 

MemS 60 Read UUT IDs 0.000 0.000 

Call 

3.5V UUT Power On 

MISP 1 U21 Rev 2OO9O4O1-A 

Call 

UUT Power Off 

Jmp 

End 

Label 

3.5V UUT Power On 

DcV 8 Turn On 3.500 

Pause 100 Power On Delay 

PWRMn 24 Check Voltage 3.450 3.550 

PWRMn 40 Check Current 400.0m 600.0 

m 

Ret 

Label 

UUT Power Off 

DcV 8 RESET 0.000 

Ret 

Label 

End 

End of data 

Example Test Program Listing 


!==================================================================== 

! CheckSum 

! CheckSum MultiWriter pps 

! Test Program Data - ASCII Output Format 

Name: 

5-Up Sun Ultra 24 

!==================================================================== 

Pin Names: 

1, AC #1 

2, DAC #1 

3, DAC_CS* #1 

4, EE_CS* #1 

5, SI #1 

6, +5V #1 

15-3




7, GND #1 

8, LED #1 

10, RST* #1 

11, CLK #1 

12, SO #1 

13, OUT #1 

15, AC #2 

16, DAC #2 

17, DAC_CS* #2 

18, EE_CS* #2 

19, SI #2 

20, +5V #2 

21, GND #2 

22, LED #2 

24, RST* #2 

25, CLK #2 

26, SO #2 

27, OUT #2 

29, AC #3 

30, DAC #3 

31, DAC_CS* #3 

32, EE_CS* #3 

33, SI #3 

34, +5V #3 

35, GND #3 

36, LED #3 

38, RST* #3 

39, CLK #3 

40, SO #3 

41, OUT #3 

43, AC #4 

44, DAC #4 

45, DAC_CS* #4 

46, EE_CS* #4 

47, SI #4 

48, +5V #4 

49, GND #4 

50, LED #4 

52, RST* #4 

53, CLK #4 

54, SO #4 

55, OUT #4 

57, AC #5 

58, DAC #5 

59, DAC_CS* #5 

60, EE_CS* #5 

61, SI #5 

62, +5V #5 

63, GND #5 

64, LED #5 

66, RST* #5 

67, CLK #5 

68, SO #5 

69, OUT #5 

Test Steps: 

!-From- -To- ------------------Test------------------ -------Limits------ Nom 

! Type Range Title Low High 

0, 0, Rem, 0, MultiWriter pps, 0.000E+00, 0.000E+00 

0, 0, Rem, 0, Rev 2OO9O715, 0.000E+00, 0.000E+00 

15-4




0, 0, Rem, 0, , 0.000E+00, 0.000E+00 

0, 0, PCB, 1, , 0.000E+00, 0.000E+00 

0, 0, Rem, 1, , 0.000E+00, 0.000E+00 

0, 0, PCB, 2, , 0.000E+00, 0.000E+00 

0, 0, Rem, 1, , 0.000E+00, 0.000E+00 

0, 0, PCB, 3, , 0.000E+00, 0.000E+00 

0, 0, Rem, 1, , 0.000E+00, 0.000E+00 

0, 0, PCB, 4, , 0.000E+00, 0.000E+00 

0, 0, Rem, 1, , 0.000E+00, 0.000E+00 

0, 0, PCB, 5, , 0.000E+00, 0.000E+00 

0, 0, Rem, 1, , 0.000E+00, 0.000E+00 

0, 0, PCB, 0, , 0.000E+00, 0.000E+00 

0, 0, MemS, 1, sns.xml, 0.000E+00, 0.000E+00 

0, 0, MemS, 60, Read UUT IDs, 0.000E+00, 0.000E+00 

0, 0, Call, 0, 3.5V UUT Power On, 0.000E+00, 0.000E+00 

0, 0, MISP, 1, U21 Rev 2OO9O4O1-A, 0.000E+00, 0.000E+00 

0, 0, Call, 0, UUT Power Off Setup, 0.000E+00, 0.000E+00 

0, 0, Jmp, 0, End, 0.000E+00, 0.000E+00 

0, 0, Label, 0, 3.5V UUT Power On Setup, 0.000E+00, 0.000E+00 

0, 0, DcV, 8, Turn On, 0.000E+00, 3.500E+00 

0, 0, Pause, 100, Power On Delay, 0.000E+00, 0.000E+00 

0, 0, PWRMn, 24, Check Voltage, 3.450E+00, 3.550E+00 

0, 0, PWRMn, 40, Check Current, 4.000E-01, 6.000E-01 

0, 0, Ret, 0, , 0.000E+00, 0.000E+00 

0, 0, Label, 0, UUT Power Off Setup, 0.000E+00, 0.000E+00 

0, 0, DcV, 8, RESET, 0.000E+00, 0.000E+00 

0, 0, Ret, 0, , 0.000E+00, 2.000E+07 

0, 0, Label, 0, End, 0.000E+00, 0.000E+00 

Panelization: YES: 

Multiple SNs: NO 

SPC Reporting: IDENTICAL 

UsePointProbes: YES: 

AC #1, DAC #1, DAC_CS* #1, EE_CS* #1, SI #1, +5V #1, GND #1, LED #1, RST* #1 

CLK #1, SO #1, OUT #1, AC #2, DAC #2, DAC_CS* #2, EE_CS* #2, SI #2, +5V #2 

GND #2, LED #2, RST* #2, CLK #2, SO #2, OUT #2, AC #3, DAC #3, DAC_CS* #3 

EE_CS* #3, SI #3, +5V #3, GND #3, LED #3, RST* #3, CLK #3, SO #3, OUT #3 

AC #4, DAC #4, DAC_CS* #4, EE_CS* #4, SI #4, +5V #4, GND #4, LED #4, RST* #4 

CLK #4, SO #4, OUT #4, AC #5, DAC #5, DAC_CS* #5, EE_CS* #5, SI #5, +5V #5 

GND #5, LED #5, RST* #5, CLK #5, SO #5, OUT #5 

UsePointPCBs: YES: 

PCB1: AC #1, DAC #1, DAC_CS* #1, EE_CS* #1, SI #1, +5V #1, GND #1, LED #1 

PCB1: RST* #1, CLK #1, SO #1, OUT #1 









! End of data 

Example Test Program in ASCII Format 

15-5


Batch Report Example 


Batch Report Example 

============================================================================ 

Batch Test Report 




Number Tested: 50 

Failures: 0 

Yield: 100% 

File Date: 

Jul 15, 2O10 

Time: 14:36 

Test System: 


============================================================================ 

Example Batch Test Report 

Statistics Data File Example 

The SPC file name format is YYYYMMDD.DAT, for example on 19-AUG-2O1O, the 

data file name is 2O1OO819.DAT 

Example file contents: 

"Spec-File", "Time","Fails","Step","Type","Measure","Test Title", "Low- 

Lim", "High-Lim", 

------------- ---------- --- ----- ------- --------- --------------, -------- 

-, ----------, 

"MISP EXAMPLE 5.SPEC", "14:45:02", 0, 0, 41, "",19, "PCB 1(5 same 

UUTs/panel)", "", "", "", "C#7", 

"MISP EXAMPLE 5.SPEC", "14:45:02", 0, 18,"MISP",, "U21" 


UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 

15-6



Wire Run Report Example 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 



UUTs/panel)", "", "", "", "C#7", 


Example Statistics Data File (the long lines wrapped around for printout) 


============================================================================= 

Wire Run Report 




Report Date: 

Jul 15, 2O10 

Time: 14:57 

Test System: 

Fixture Type: 


TR-3 standard 

============================================================================= 

Test Point Number Sort 

Test Point Name Sort 

Point - Name- I/F Block Name - Point - I/F Block 

1 AC #1 +5V #1 6 

2 DAC #1 +5V #2 20 

3 DAC_CS* #1 +5V #3 34 

4 EE_CS* #1 +5V #4 48 

5 SI #1 +5V #5 62 

15-7




6 +5V #1 AC #1 1 

7 GND #1 AC #2 15 

8 LED #1 AC #3 29 

10 RST* #1 AC #4 43 

11 CLK #1 AC #5 57 

12 SO #1 CLK #1 11 

13 OUT #1 CLK #2 25 

15 AC #2 CLK #3 39 

16 DAC #2 CLK #4 53 

17 DAC_CS* #2 CLK #5 67 

18 EE_CS* #2 DAC #1 2 

19 SI #2 DAC #2 16 

20 +5V #2 DAC #3 30 

21 GND #2 DAC #4 44 

22 LED #2 DAC #5 58 

24 RST* #2 DAC_CS* #1 3 

25 CLK #2 DAC_CS* #2 17 

26 SO #2 DAC_CS* #3 31 

27 OUT #2 DAC_CS* #4 45 

29 AC #3 DAC_CS* #5 59 

30 DAC #3 EE_CS* #1 4 

31 DAC_CS* #3 EE_CS* #2 18 

32 EE_CS* #3 EE_CS* #3 32 

33 SI #3 EE_CS* #4 46 

34 +5V #3 EE_CS* #5 60 

35 GND #3 GND #1 7 

36 LED #3 GND #2 21 

38 RST* #3 GND #3 35 

39 CLK #3 GND #4 49 

40 S0 #3 GND #5 63 

41 OUT #3 LED #1 8 

43 AC #4 LED #2 22 

44 DAC #4 LED #3 36 

45 DAC_CS* #4 LED #4 50 

46 EE_CS* #4 LED #5 64 

47 SI #4 OUT #1 13 

48 +5V #4 OUT #2 27 

49 GND #4 OUT #3 41 

50 LED #4 OUT #4 55 

52 RST* #4 OUT #5 69 

53 CLK #4 RST* #1 10 

54 SO #4 RST* #2 24 

55 OUT #4 RST* #3 38 

57 AC #5 RST* #4 52 

58 DAC #5 RST* #5 66 

59 DAC_CS* #5 SI #1 5 

60 EE_CS* #5 SI #2 19 

61 SI #5 SI #3 33 

62 +5V #5 SI #4 47 

63 GND #5 SI #5 61 

64 LED #5 SO #1 12 

66 RST* #5 SO #2 26 

67 CLK #5 SO #3 40 

68 SO #5 SO #4 54 

69 OUT #5 SO #5 68 

MultiWriter Wiring Connections: 

I/F Block MultiWriter 

Buffer Pin 

#1/J2-7 

15-8



Production Report Example 

End of Data 

Example Wire Run Report 

#1/J2-6 

#1/J2-5 

#1/J2-4 

#1/J2-3 

#1/J2-1 

#2/J2-7 

#2/J2-6 

#2/J2-5 

#2/J2-4 

#2/J2-3 

#2/J2-1 

#3/J2-7 

#3/J2-6 

#3/J2-5 

#3/J2-4 

#3/J2-3 

#3/J2-1 

#4/J2-7 

#4/J2-6 

#4/J2-5 

#4/J2-4 

#4/J2-3 

#4/J2-1 

#5/J2-7 

#5/J2-6 

#5/J2-5 

#5/J2-4 

#5/J2-3 

#5/J2-1 

Production Report Example 

============================================================================ 

Production Report 


Report Date: 


Jul 15, 2O10 

Time: 14:59 

UUTs tested from: 

to: 

UUTs included: 

Jul 15, 2O10 (00:00) 

Jul 15, 2O10 (23:59) 

All 

5 PCBs counted as replicates of one UUT. 

Test System: 



c:\checksum\stats\ 

============================================================================ 

Summary: 

15-9


Pareto Failure Report Example 


Number of UUTs: 10 

UUTs Passed: 10 

UUTs Failed: 0 

UUT Yield: 100% 

Total Defects: 0 

Analysis by UUT type: 

UUT Tested 

--------------------- 


Total 

----- 

10 

Passed 

------ 

10 

Failed 

----- 

0 

Yield 

----- 

100% 

Defects 

------ 

0 

PCB 

--- 

All 

End of data 

Example Production Report 

Pareto Failure Report Example 

============================================================================= 

Pareto Failure Report 


Report Date: 


Jul 15, 2O10 

Time: 15:02 


to: 


Jul 15, 2O10 (00:00) 

Jul 15, 2O10 (23:59) 

All 


Test System: 




============================================================================= 

Total Defects: 0 

Defect Analysis: 

No Defects to Analyze 

End of data 

Example Pareto Failure Report 

15-10



X-Bar/Sigma Report Example 


============================================================================= 

X-Bar/Sigma Control Report 


Report Date: 


Jul 15, 2O10 

Time: 15:05 


to: 


Jul 15, 2O10 (00:00) 

Jul 15, 2O10 (23:59) 



Test System: 




============================================================================= 

Example X-Bar/Sigma Control Report (Print to File Version) 

15-11




12

Chapter 16 

Command Line Parameters 

System Command Line Parameters 

The System allows you to specially tailor operation with command line parameters. 

Command line parameters are used when you first invoke the Software. The parameters are 

entered on the line after PPS (or PPS.EXE). Each parameter is separated by one or more 

spaces and can be in upper or lower case.


System Command Line Parameters 



Parameter 

Action 

/r Open, load and run a test program. When /r is followed by a test program 

name, the System automatically loads the requested test program, then 

begins execution. 

/rq 

Open, load, run a test program, then quit PPS when test completes. When 

/rq is followed by a test program name, the System automatically loads the 

requested test program, executes the program and terminates. 

/l Open and load the test program specified after the command (for example, '/l 

MY_TEST'). The main system screen is displayed. 

/lt 

Open and load the test program specified after the command (for example, '/lt 

GO_TEST'). The test screen is displayed. 

/nc 

No calibration. Normally, the System measures internal reference values 

each time the PPS software is invoked. If the System is started with this 

parameter, the internal references are not measured during power up. 

Instead, the reference values determined during the last self-test are used. 

Use of this parameter can provide more consistent operation if the PC is 

powered up and the software started at a greatly different ambient 

temperature than normal operating temperature. 

/cf 

Configuration File. Specify the file name (optionally preceded by a path) for 

the station configuration file. If not specified, the file name is $pps$.DAT in 

the same directory as the PPS.EXE file. The /cf parameter can be used in 

network configurations so that the PPS.EXE file can be shared, but each 

station can use its own configuration file which includes the station's unique 

calibration and setup information. 

/sf 

Show Failures. When executing a test program, display the failed test 

outcomes on the CRT, even if the System does not halt on the test step. This 

can be used to allow the operator to keep better track of System test activity, 

but at the expense of a little test speed. 

/sfp 

Show Failures and Passes. Same as /sf, but also shows passed test steps. 

/net 

Set network retry time. Allows you to specify how long, in seconds, to wait for 

the system to wait for a network file to become available for use. This time is 

necessary when more than one System is sharing a file and it is necessary 

for one System to close the file before the other can use it. The default is 10 

seconds. To set a maximum delay of 30 seconds for example, specify /net 

30. 

/pw 

Password for exit. If the System is started with this command line parameter, 

the operator must enter the System password before exiting from the System 

Menu). 

/spc 

Additional SPC Log File output. If /spc . is specified, the System, 

whenever writing SPC data to the disk, will also write to the log file having the 

. suffix specified. If the is not present, it will be created. The 

log file name prefix matches that of the default SPC Log File. 

/tl 

Time logging. If /tl is specified, the System keeps track of execution time of 

each test step. This capability can be used to fine-tune test program 

execution speed by identifying test steps which take excessive time. When /tl 

is specified, you can press [Control-M] while in the Edit screen, and the 

System will display the execution time (in mSec) of each test step in the 

range column. Resolution of the times is about 50mSec. Pressing [Control- 

M] again returns to the regular display. 

/t Specify temporary file directory. If /t is specified, the string that follows it 

specifies the location of the directory used to hold temporary files. These files 

are used e.g. to create test result reports sorted by PCB number. If no 

location is specified, then the current directory at the time pps.exe is executed 

is used. The temporary file location should generally not be a server location 

shared by more than one test station. 

16-2



MultiWriter Command Line Options 

/li 

/km 

/ppath 

/spath 

/multiple 

/-skip_q 

/no_histogram 

Automatically logs in a user having a blank password when /li is followed by 

the user name which is one of the login user dialog name choices. Does 

nothing if Login is disabled. 

Load the lower eight bits of the specified value into the operator keyboard 

mask register (see the Operator Keyboard Use on page 4-8 for key mask bit 

information). 

Specifies the test program directory location in the string following this option. 

This overrides the spec data path stored in the system configuration. 

Specifies the SPC Log File directory location in the string following this 

option. This overrides the statistics data path stored in the system 

configuration. 

This allows a second session of PPS to run. This must be the last parameter 

in the command line parameter list. It is only used on the command line of 

the second PPS session. 

Disables the question regarding PCB skip selection for panelized assemblies 

at the start of the batch. 

Disables the X-Bar/Sigma Report Histogram generation. This is useful if the 

system memory resources are limited. 


Note 

Not all the parameters displayed apply to any given device. 

For syntax, see the notes below on page 16-7. 

[-c ] [--config ] 

Customer Configuration file 

[-e] [--erase] 

Erase enabled ISP devices 

[-p] [--program] 

Program enabled ISP devices 

[-v] [--verify] 

Verify device data of enabled ISP devices 

[] [--pvp] 

Program and Verify device data of enabled ISP devices 

[-d ] [--dump ] 

Dump device data to file 

[-f] [--file {memType}] 

Use device specific data file for device 

[-s ] [--select] 

Select PCB Panel using bitmask where bit 0 = PCB 1 

16-3




[-a ] [--devconfig] 

Device Configuration file 

[-k] [--checkid] 

Verify Device and Manufacturing IDs 

[-b] [--blankcheck] 

Blank Check ISP device before erasing 

[] [--qbc {-}|{, {memType}] 

Quick Blank Check device Memory 

location X (hex value) or range before erasing 

[-t] [--status] 

Read status register of DUT 

[] [--static] 

Keep relays closed after app exits 

[-l] [--protect] 

Check device for protection and protect before exiting. 

[] [--chiperase] 

Chip Erase the device 

[] [--blankchip] 

Blank Check entire device 

[] [--read {-}|{,} {memType}] 

Read device Memory 

location X (hex value) or range 

[] [--memtofile {-}|{,} 

] 

Read device Memory 

location X (hex value) or range and write data in to 

[-w] [--writeconfig] 

Program the config data 

[] [--svf {parserlog} {exelog}] 

Run svf file specified in Customer Configuration file 

[] [--diag {-}|{, {resultfile}] 

Perform MultiWriter Self Test for MultiWriters 

[] [--initdly ] 

Insert time delay in milliseconds before device 

initialization 

[] [--exe ""] 

Execute specified application before reading image files. 

Enclose the complete command line with double quote. 

[] [--reload] 

Reload Device and Bus Drivers 

16-4




[] [--call ""] 

Override Memory/Config Words/Fuse/Option Bytes Parameters 

in XML file Override function under ISP_Advanced 

[] [--power ] 

Turn on or off relays, where 1 = on, 0 = off 

[] [--arm_init {devclass}] 

Initialize ARM7TDMI driver 

[] [--arm_reset ] 

Perform SW reset instruction on ARM CPU 

[] [--arm_status] 

Display ARM7 status 

[] [--arm_halt ] 

Halt ARM7 processor (timeout in s seconds) 

[] [--arm_devid 0x] 

Verify ARM7 Device ID , comparing only bits specified 

by 0x 

[] [--arm_forceArm] 

Force ARM7 processor into 32-bit ARM mode 

[] [--arm_map 0x 0x] 

Map memory region to address with size bytes 

[] [--arm_read_msm 0x] 

Read the MSMPWL(0-3/4-7) locations beginning at address 

to unlock security 

[] [--arm_ write 0x 0x] 

Write 32-bits of data 0x to ARM7 processor address 

0x 

[] [--arm_read 0x] 

Read 32-bits of data at ARM7 processor address 0x 

[] [--arm_verify 0x 0x 0x< mask>] 

Verify that data at ARM7 address 0x is equal to 0x 

masked by 0x< mask> 

[] [--arm_load 0x ] 

Load data in binary image file to ARM7 address 

beginning at 0x 

[] [--arm_run ] 

Execute code at ARM7 address 0x and Stack Pointer at 

0x 

[] [--sleep ] 

Insert time delay in milli-seconds 

[] [--dccload 0x ] 

16-5




Load data in binary image file to ARM7 address 

beginning at 0x using DCC Module. DccMonitor must be 

running. 

[] [--dccwrite 0x] 

Write data 0x to DCC. DccMonitor must be running 

[] [--dccread] 

Read 32-bits of DCC data. DccMonitor must be running 

[] [--dccpoll ] 

Poll DCC for value up to seconds 

[] [--ferase ] 

Erase ARM FLASH of enabled ISP devices. Entire sector 

will be erased. Fails if seconds elapse. 

[] [--fprogram ] 

Program ARM7 FLASH of enabled ISP devices. Fails if 

seconds elapse. 

[] [--fverify ] 

Verify ARM7 FLASH of enabled ISP devices. Fails if 


[] [--ffastverify ] 

Fast Verify ARM7 FLASH of enabled ISP devices. Fails if 


[] [--fprogverifypage ] 

Program and Verify per page of enabled ISP devices. Fails 

if seconds elapse. 

[] [--fblankcheck ] 

Blank Check ARM7 FLASH of enabled ISP devices. Fails if 


[] [--fblankchip ] 

Blank Check entire ARM7 FLASH of enabled ISP devices. 

Fails if seconds elapse. 

[] [--fchiperase ] 

ChipErase ARM FLASH of enabled ISP devices. All sectors 

will be erased. Fails if seconds elapse. 

[] [--fcompact ] 

Compact ARM FLASH of enabled ISP devices. Fails if 


[] [--fmatchkey ] 

Unlock ARM FLASH using specified (K1-K4) keys of enabled 

ISP devices. Fails if seconds elapse. 

[] [--fprotect ] 

UnProtect/Protect ARM7 FLASH of enabled ISP devices. 

Fails if seconds elapse. 

16-6




[] [--fclock {y}] 

Set system clock to MHz given an Oscillator of 

MHz. Will also set Flash Delay Parameter used by Flash 

algorithms accordingly. 

[] [--rambufsize 0x] 

Set RAM buffer size for flash program and/or verify 

operations 

[-?] 

Display the above list. 

Notes 

In general, all numeric parameters can be either decimal or hexadecimal 

(hex), use a leading 0x for hex values. The hexadecimal values (base-16) 

use sixteen symbols of 0 to 9 to represent values zero to nine, and A, B, C, 

D, E, F (or a through f) to represent the values ten to fifteen. For example, 

100 decimal is 0x64 hex and 0xA2D2 hex is 41682 decimal. 

0x where a 0 (zero) bit in the mask indicates "don't care" (e.g., 

0xFE is the mask for the 0 bit, the LSB is a "don't care"). 

For , the file path can be relative or full path. For the relative path, 

the root will be the current executable directory, typically c:\checksum (for 

the standard installation). 

[-Single dash option] or [--Double dash option] specification 

-Single dash option allows single letter options and can be combined, for 

example: 

-epvw 

--Double dash option uses descriptive words, easier to understand but each 

option must be separated by at least one space, for example: 

--erase --program --verify --writeconfig 

Most commands allow the form [--word], such as: 

[] [--chiperase] Chip Erase the device 

The only method to "Chip Erase the device" is: 

--chiperase 

Some commands have two forms [-letter] or [--word] such as: 

[-e] [--erase] Erase enabled ISP devices 

16-7




Two equivalent commands to "Erase enabled ISP devices" are: 

-e 

or 

--erase 

–e & –p vs. – –chiperase & – –blankcheck The e & p only work in the 

memory range defined in the hex data file, the others do the operation to the 

entire device. 

– – exe option runs any program prior to inputting the hex data files for 

each device location. This can be used for unique serial number (S/N), 

calibration data, data code, etc. 

16-8

Chapter 17 

Error Messages 


At start-up, if the security HASP USB drive ("dongle") is disconnected, not installed, defective 

or the Programmer Power on page 4-4 is not turned-on then the message "HASP dongle 

missing or driver not installed" will be shown. This is normal when running the software 

without any hardware attached to the PC. The HASP USB drive is normally installed inside 

the test fixture. 

Other errors while reading or writing the computer's disk or during other operations include:




Error 

Message 

Error 1 

Invalid DOS function number 

Error 2 

File not found 

Error 3 

Path not found 

Error 4 

Too many files open 

Error 5 

File access denied 

Error 12 Invalid file access code 

Error 15 Invalid drive number 

Error 97 Incorrect test program revision 

Error 99 Not a valid spec data file 

Error 100 Disk Read error 

Error 101 Disk out of space 

Error 103 File Open error 

Error 105 File not open for output (is LPT1 printer connected?) 

Error 150 Disk is write-protected 

Error 152 Drive is not ready 

Error 156 Disk seek error 

Error 160 Device Write-Fault (normally printer) 

Error 162 Hardware failure 

Error 200 Division by zero 

Error 201 Range check error 

Error 202 Stack overflow error 

Error 203 Heap overflow error 

Error 205 Floating point overflow 

Error 206 Floating point underflow 

Error 207 Invalid floating point operation 

Error 209 Overlay file read error 

Error 216 General protection fault 

System Error Messages 

17-2

Chapter 18 

Help for Problems 

In Case of Problems 

At start-up, if the security HASP USB drive (normally installed inside the test fixture) is 

disconnected, not installed, defective or the Programmer Power on page 4-4 is not turned-on 

then the message "HASP dongle missing or driver not installed" will be shown. This is normal 

when running the software without any hardware attached to the PC. 

If you suspect problems in the operation of your Test System, you should run the self-test that 

is available from the Configure screen on the Modules page. See the Module Self-Test on 

page 5-6 section in the System Configuration chapter for running the self-test. 

Set the PC Control Panel Power Management to "Always On with No standby or hibernate". 

Antivirus Note 

If the system is used with a HASP USB Drive and the computer Antivirus is 

ESET NOD32, please disable the Real-time file system protection. 

Uncheck the Scan on setting for File Creation. This protection will cause 

the computer to freeze/lockup and require a hard reboot (Hold down the 

Power Button to reboot). 

Symptoms: 

Your computer will freeze when changing fixture (HASP Drive) but it will 

be normal again after a hard reboot. 

Cause: 

The system software will mount the USB Drive to 

"C:\Checksum\PPS\Fixture USBDrive" during startup and the Antivirus 

software detects this "File Creation" as a threat. 

Other Antivirus software may cause the same problem, please check the 

Antivirus software setup.


Troubleshooting Tips 


Display Problems 

If the windows do not display fully (they look cut off), you will need to adjust the Windows 

display properties settings. The Display Properties settings are controlled in the Windows 

Control Panel. The Display Properties Font Size is controlled under the Advanced button 

option. Select the Control Panel > Display > Settings tab > Advanced… button > Display 

Font Size and set this selection to Small Fonts. If the Font Size selection is set to Large 

Fonts, several windows may not display properly. 

Serial Printer Problems 

In general, first review the manual provided with the printer. If you are using a serial printer 

and it appears to be working normally but stops printing at times, check the baud rate setup. 

The baud rate is set with switches inside the printer and in the test system in the Configure 

System > External Hardware tab > Test Screen Report Device COM1 (or COM2) > Baud 

Rate 1200. Some serial printer problems can be fixed if you set the baud rate to 1200 for both 

the printer and in the test system configuration. In the serial printer, set DIP switch 6 and 

switch 7 to OFF to configure the printer for 1200 baud. Be sure to turn-off the power before 

changing the switch settings. The printer baud rate is set at power-up of the printer. The 

printer DIP switch is located under a cover on the bottom of the printer (see the printer 

manual). All the other switch settings are normally in the ON position. 

Troubleshooting Tips 

In case of problems, this list of items should be verified: 

• System and Programmer Power are ON on page 4-4 

• The fixture is installed and connected to the receiver properly 

• The DUT assembly is “known good” 

• Check the DUT assembly to insure it is installed properly 

• Check the fixture spring-probe connections to the DUT 

• Check the Fixture Ready Switch closes properly 

• Check the fixture wiring connections 

• Check the DUT power for ISP; signal wiring, signal/power grounds and voltages 

Note: If Fixture Present/ (Fixture Receiver pin A-152 and E-152) is not connected to the 

MW FIX IO module or to a GND pin, the PS-UUT switched power (SW) outputs (+5Vdc 

SW, +12Vdc SW, and +24Vdc SW) will not be enabled and switched power will not be 

available to the fixture. 

• Check the remote sense connections from the system power supplies 

• Check the MISP test setup on page 10-7 and supporting files 

• Check the panel map to insure it matches the fixture wiring and the assembly 

Note: You can use the fixture self-test, single point probe, or an ohm-meter to verify the 

fixture wiring. 

Spares Kit 

18-2



Getting Help From CheckSum 

If a failed item can be identified, check the pps spares kit for a replacement part. 


Critical Items To Provide For Assistance 

If you are not able to diagnose the problem, give CheckSum technical support a call at 1- 877- 

CHECKSUM (in the USA) or +1.360.435.5510 (Pacific time zone, GMT-08:00) for additional 

help. 

If you need assistance from CheckSum please provide the following: 

1. A description of the problem 

2. The name of the company that created the test fixture. 

3. Any unique fixture serial number or other identifying information. 

4. The name of the company that created the test program. 

5. CheckSum test system software name and software version number (see Help > About …) 

6. Test system configuration file $PPS$.DAT (binary), typically in C:\checksum 

7. Program file on page 9-6 (.spec, is binary) 

8. Test Results Report on page 15-1 (print the Passes and Failures test results to a file) 

9. Schematic pages with the test point locations indicated if available 

10. Bill-of-material (BOM) 

11. Fixture test point locations and wiring on page 12-1 

12. ISP IC data sheets 

13. ISP Files 

a. Test Step INI or XML file 

b. Component INI or XML file 

c. Component data / image file(s) 

d. Serial number XML file on page 5-16 

e. Skip PCB XML file on page 5-16 

f. Log files (.log) in the c:\checksum (default) directory 

18-3




Notes: 

The Test Results Reports should be printed to a text file so you can attach 

them to your email message. For examples of how to print a text file, see 

the CheckSum web site for help at: 

http://www.checksum.com/support/downloads.asp 

Document to review: 

Saving a copy of the Test Results Report 

Contacting CheckSum 

Email: support@checksum.com 

Tel: 1 – 877 – CHECKSUM (in the USA 1-877-243-2578) Pacific time zone, GMT- 

08:00 

Tel: +1.360.435.5510 Pacific time zone, GMT-08:00 

Fax: +1.360.435.5535 

Website: www.checksum.com 

Ship-to street address: 

CheckSum LLC 

6120 195th St. NE 

Arlington, WA 98223 

18-4

Index 

! 

! Grouped Listing of the Test Types ........................................................................................... 14-1 

! Test Type Categories ....................... 14-1, 14-6, 14-10, 14-17, 14-23, 14-25, 14-37, 14-40, 14-43 

$ 

$RBODY$.DAT........................................................................................................................... 5-13 

$RBODYT$.DAT......................................................................................................................... 5-13 

$RHDR$.DAT ............................................................................................................................. 5-13 

$RHDRT$.DAT........................................................................................................................... 5-13 

. 

.INI File ........................................................................................................................................ 434 

1 

160-Pin Blocks .......................................................................................................................... 4-25 

170-Pin Blocks .......................................................................................................................... 12-2 

3 

3800-102 MW FIX I/O Board ...................................................................................................... 6-13 

3800-105 ISP Buffer X2 Board..................................................................................................... 6-6 

3800-107 VPP ISP Buffer X2 Board............................................................................................. 6-6 

4 

40/80 Column Report Format....................................................................................................... 5-8 

A 

Abort / Terminate Test.................................................................................. 7-5, 7-11, 10-26, 14-11 

Active X..................................................................................................................................... 10-28 

Add a Test Step............................................................................................................................ 9-7 

Add User..................................................................................................................................... 5-19 

Antivirus Software..............................................................................................................4-15, 18-1 

Append ......................................................................................................................................... 9-6 

ASCII Decimal Character Table ............................................................................................... 14-36 

ASCII Format................................................................................................................9-6, 9-7, 9-27 

ASCII Input Files..................................................................................................................9-6, 9-26 

Assembly Name.......................................................................................................................... 9-13 

Assign / Change Point Names.................................................................................................... 9-24 

Assign Connection Information................................................................................................... 9-13 

Assign Operator Display Messages ........................................................................................... 10-5 

Assigning Point Names .............................................................................................................. 9-24 

Assigning Test Limits.................................................................................................................. 9-12 

Assistance and Support Contact ................................................................................................ 18-3 

Attribute Manipulation ........................................................................................................... 11-14 

Auto Load ..........................................................................................................................7-17, 9-13 

Automatic Batch Data Path ........................................................................................................ 5-16 

Automation Interface (COM)..................................................................................................... 10-28

B 

Bar Code Reader Option ................................................................................ 4-11, 5-8, 5-16, 14-32 

Base Addresses.............................................................................................................10-47, 14-26 

Batch Count.........................................................................................................................7-8, 7-13 

Batch Errors................................................................................................................7-8, 7-13, 7-15 

Batch ID ....................................................................................................................5-12, 5-13, 7-14 

Batch Persistent........................................................................................................................ 10-39 

Batch Report.............................................................................................................7-13, 7-14, 15-6 

Batch Report - Special Line.......................................................................................................... 5-8 

Batch Report Example................................................................................................................ 15-6 

BEEP Test Type ....................................................................................................................... 14-52 

Beginning time.......................................................................................................................... 10-47 

Bell Curve ................................................................................................................................... 8-12 

Branching.................................................................................................................................. 10-25 

BreakPoint .......................................................................................................................9-21, 14-49 

Buffer Modules.................................................................................................. 6-6, 6-7, 6-12, 10-19 

Buffer Type ............................................................................................................................... 10-19 

Buffer Wiring.......................................................................................................10-17, 10-18, 10-21 

Built-In Self-Test ....................................................................................................................5-6, 5-7 

C 

Call a Subroutine ...................................................................................................................... 14-15 

Change Ending Period ............................................................................................................... 8-15 

Change Pin Names .................................................................................................................... 9-24 

Change Starting Period .............................................................................................................. 8-15 

Changing Report Paths ............................................................................................................ 10-32 

Check Serial Number ..........................................................................................................5-8, 7-14 

Check Test Limits ....................................................................................................................... 9-21 

Checklists ..........................................................................................................................6-28, 9-10 

Fixture Checklist ..................................................................................................................... 6-28 

Program Setup CheckList....................................................................................................... 9-10 

CheckSum Support ...................................................................................................................... 1-4 

Choosing the Run Number ......................................................................................................... 8-14 

COM Interface .......................................................................................................................... 10-28 

Command Line Parameters...............................................................................................16-1, 16-2 

Comments (Remarks) .............................................................................................................. 14-52 

Completing the Software Installation.......................................................................................... 4-18 

Conditional Test Report Output................................................................................................ 14-52 

Configuration Table ...................................................................................................................... 5-4 

Configure Directories/Locations ................................................................................................. 5-16 

Configure Test Program Report ...................................................................................................5-8 

Connecting to the UUT ................................................................................................................. 2-1 

Connection Information .............................................................................................................. 9-13 

Considerations Before Making Changes.................................................................................... 6-34 

Contact CheckSum..................................................................................................................... 18-3 

Control input and output ........................................................................................................... 10-47 

Control Relays .......................................................................................................................... 14-47 

Controlling Program Flow ......................................................................................................... 10-24 

Copy Field/Lines........................................................................................................................... 9-7 

Cp and CpK .......................................................................................................................8-12, 8-13 

Creating a Test Program .............................................................................................................. 2-2 

Cross Checks ....................................................................................................................5-16, 9-21 

csIsp.exe............................................................................................................................10-7, 16-3 

CSRUS.EXE............................................................................................................................... 6-22 

CSV (comma separated variable) .............................................................................................. 9-21

Customer Support ........................................................................................................................ 1-3 

Customizing Reports .................................................................................................................... 5-8 

Cut Field/Lines.............................................................................................................................. 9-7 

D 

Date .............................................................................................................................................. 8-6 

Date Format.................................................................................................................................. 5-8 

DB25 Connector ..................................................................................................................4-9, 4-10 

DC Current Output...................................................................................................................... 14-4 

DC Voltage Output ..................................................................................................................... 14-4 

Default Grid................................................................................................................................. 9-10 

Delete Test Program .................................................................................................................... 9-6 

Delete Test Steps ......................................................................................................................... 9-7 

Design for Part Programming ..................................................................................................... 6-31 

Designing the Fixture.......................................................................................................5-23, 14-45 

Device Data Files........................................................................................................................ 10-7 

Device Programming ................................................................................. 2-2, 6-2, 6-31, 10-7, 11-1 

Device Write-Fault ...................................................................................................................... 17-2 

Diagnostics - Report ..................................................................................................................... 7-5 

DIGA Test Step........................................................................................................................... 14-8 

DIGI Test Type ........................................................................................................................... 14-7 

Digital Active............................................................................................................................... 14-8 

Digital Input Test Type................................................................................................................ 14-7 

Digital Output Test Step ............................................................................................................. 14-8 

Digital Test Types....................................................................................................................... 14-6 

DIGO Test Step .......................................................................................................................... 14-8 

Direct Addressing ..................................................................................................................... 10-47 

Directories Configuration ............................................................................................................ 5-16 

Disk is write-protected ................................................................................................................ 17-2 

Disk Out of Space....................................................................................................................... 17-2 

Disk Read Error .......................................................................................................................... 17-2 

Disk Seek Error........................................................................................................................... 17-2 

DISP Test Step......................................................................................................................... 14-18 

DISPE Test Step....................................................................................................................... 14-19 

DISPL Test Step....................................................................................................................... 14-18 

Display a Message to the Operator.................................................................................10-5, 14-18 

Display a Picture....................................................................................................................... 11-19 

Display a Short Message to the Operator .......................................................................10-5, 14-18 

Display Attribute Manipulation..............................................................................11-1, 11-10, 14-21 

Display Enhanced Screen ........................................................................................................ 14-20 

Display List for SCRN Test Step .............................................................................................. 11-10 

Display Message .............................................................................................................10-5, 14-18 

Display Problems ..................................................................................................................... 18-2 

Division by Zero.......................................................................................................................... 17-2 

Drive is Not Ready...................................................................................................................... 17-2 

Duplicate Serial Number..................................................................................................7-14, 14-32 

DUT/UUT Detect Switch............................................................................................................. 6-17 

E 

Edit........................................................................................................3-2, 3-3, 9-4, 9-5, 10-2, 10-3 

Measure Menu ....................................................................................................................... 9-12 

Step Analysis .......................................................................................................................... 10-4 

View Menu.............................................................................................................................. 9-10 

Edit Profile .................................................................................................................................. 5-18 

Edit Program CheckList.............................................................................................................. 9-10

Edit Window................................................................................................................9-5, 10-2, 10-3 

Embedded Files.......................................................................................................................... 10-7 

Encapsulating a Test ................................................................................................................ 10-27 

Enter Batch ID ............................................................................................................................ 7-12 

Enter UUT Serial Number........................................................................................................... 7-12 

Entering Test Steps .................................................................................................................... 10-1 

Erase an Operator Message .................................................................................................... 14-19 

Erasing Memory.......................................................................................................................... 9-23 

Error Messages......................................................................................................................... 17-2 

ERROR Test Type.........................................................................................................14-11, 14-13 

ESD Strap Connection ................................................................................................................. 4-4 

EVAL Test Type........................................................................................................................ 14-23 

Event timing .............................................................................................................................. 10-47 

Example Test Program Segments.............................................................................................. 11-1 

EXEC Test Type............................................................................................................10-27, 14-23 

Execute User-Written Routine .................................................................................................. 14-23 

Executing a User-Written Program........................................................................................... 10-27 

Executing the Test........................................................................................................................ 7-4 

Execution time .......................................................................................................................... 10-47 

Execution times .......................................................................................................................... 7-16 

Exit program ................................................................................................................................. 3-4 

Exiting the Program .................................................................................................................. 10-26 

Expand........................................................................................................................................ 9-10 

Expansion Assembly .................................................................................................................. 4-20 

Export ......................................................................................................................................... 5-22 

Extending Test Program Length............................................................................................... 10-27 

F 

Fail FailV Test Result ...............................................................................................7-12, 8-17, 15-1 

Failed Components .................................................................................................................... 18-1 

Field Values................................................................................................................................ 9-12 

File access denied...................................................................................................................... 17-2 

File Menu .....................................................................................................................3-4, 7-10, 9-6 

File not found.............................................................................................................................. 17-2 

File Open error............................................................................................................................ 17-2 

File Selection............................................................................................................................... 7-2 

File Viewer .................................................................................................................................... 5-8 

Find............................................................................................................................................... 9-9 

Find Next ...................................................................................................................................... 9-7 

FIXCT Test Type .............................................................................................................4-20, 14-45 

Fixture Checklist ......................................................................................................................... 6-28 

Fixture Control .................................................................................................................4-20, 14-45 

Fixture Identification ................................................................................................................. 11-20 

Fixture Layout............................................................................................................................... 6-3 

Fixture Mechanical Design ......................................................................................................... 6-24 

Fixture Present Signal ..............................................................................................6-13, 12-1, 18-2 

Fixture Ready ....................................................................................................................6-17, 6-19 

Fixture Safety Rule ...............................................................................................10-4, 14-44, 14-46 

Fixture Toggle............................................................................................................................. 9-22 

Fixture USBDrive........................................................................................................................ 6-21 

Fixture-Down Switch..........................................................................................................6-18, 6-19 

Floating point overflow................................................................................................................ 17-2 

Floating point underflow ............................................................................................................. 17-2 

Font Size..................................................................................................................................... 9-10 

From Pin ..............................................................................................................................7-4, 10-2

G 

General Programming ................................................................................................................ 14-7 

General protection fault .............................................................................................................. 17-2 

General Purpose Interface Bus I/O .......................................................................................... 14-37 

Generate Test Result ............................................................................................................... 14-23 

Generating Reports from a Test Program ................................................................................ 10-31 

Get Batch ID from operator .......................................................................................................... 5-8 

Get UUT Serial Number from operator......................................................................................... 5-8 

Getting Help From CheckSum.................................................................................................... 18-3 

Getting Started.............................................................................................................................. 2-1 

Goto Next Error............................................................................................................................. 9-9 

Goto Step...................................................................................................................................... 9-7 

GPIB Test Type ........................................................................................................................ 14-37 

GPIB-USB IEEE-488 Installation................................................................................................ 4-10 

H 

Halt on Fail....................................................................................................................7-4, 7-5, 7-11 

Hardware failure ......................................................................................................................... 17-2 

HASP Remote Update System (RUS) ............................................................................6-22, 6-23 

HASP USB Drive ..............................................................................................................6-21, 18-1 

Help Menu.................................................................................................................................. 9-23 

High Limit......................................................................................................................7-4, 9-1, 10-4 

Histogram ................................................................................................................................... 8-13 

I 

ICT ................................................................................................................................................ 1-3 

Image Files ......................................................................................................................10-9, 10-11 

Import.................................................................................................................................. 5-22, 436 

Import File (Append)............................................................................................................. 9-6, 434 

Impure code.............................................................................................................................. 10-47 

In System Programming with MultiWriter (MISP) ....................................................................... 14-6 

Incorrect spec file revision .......................................................................................................... 17-1 

INI File ......................................................................................................................................... 435 

Insert a Test Step ......................................................................................................................... 9-7 

Installing and removing the fixture.............................................................................................. 6-27 

Installing Guide Pins ................................................................................................................ 6-24 

Installing Spring Probes .......................................................................................................... 6-25 

Installing the DUTon the test fixture ........................................................................................... 6-28 

Installing the Power Supplies ..................................................................................................... 13-3 

Internal USB and program storage............................................................................................. 6-21 

Interrupts..................................................................................................................................... 18-1 

Introduction................................................................................................................................... 1-1 

Invalid drive number ................................................................................................................... 17-2 

Invalid file access code............................................................................................................... 17-2 

Invalid floating point operation.................................................................................................... 17-2 

Invalid HASP USB Drive............................................................................................................. 18-1 

ISP Buffer X2 Module ................................................................................................................... 6-6 

ISP Restrictions ........................................................................................................................ 6-32 

ISPMw Buffer Wiring ................................................................................................................... 436 

ISPMw Test Type ........................................................................................................................ 434 

J 

JMP Jump Unconditionally ............................................................................................10-25, 14-11 

JMPDI Jump Based on Result of Digital Input ......................................................................... 14-12

JMPE Jump Based on Number of Errors ......................................................................14-13, 14-14 

JMPK Jump Based on Result of Key Input .............................................................................. 14-13 

JMPPI Jump Based on Result of Port Input ............................................................................. 14-12 

JSTST Jump Based on Self-test .............................................................................................. 14-15 

JUMP based on Integer Variable (MemI) ................................................................................. 14-26 

Jump Based on PWR Measurement ........................................................................................ 14-11 

JUMP based on Real Variable (MemR) ................................................................................... 14-30 

JUMP based on String Variable (MemS) ................................................................................. 14-32 

Jump Error Count ..................................................................................................................... 14-14 

K 

Key............................................................................................................................................ 14-19 

Keypad.................................................................................................................................4-8, 12-1 

Keypad Mask............................................................................................................4-8, 14-26, 16-1 

L 

LABEL test................................................................................................................................ 10-25 

Label Test Step......................................................................................................................... 14-11 

LAN Connection............................................................................................................................ 4-4 

Limited User (XP) ....................................................................................................................... 4-14 

Listing Test Program Data.......................................................................................................... 9-26 

Load a Test Program.................................................................................................................... 3-4 

Load and Run a Test Program ................................................................................................. 14-16 

Load and Run a Test Sub-Program.......................................................................................... 14-16 

Loading a Program ..................................................................................................................... 9-23 

Log File ....................................................................................................................................... 10-7 

Log into the System....................................................................................................5-1, 5-18, 5-19 

Login User ........................................................................................................ 5-1, 5-18, 5-19, 7-14 

Loop on Error......................................................................................................14-11, 14-13, 14-14 

Low Limit.......................................................................................................................7-4, 9-1, 10-4 

M 

Main Power Switch ................................................................................................................4-4, 4-5 

Main Screen.........................................................................................................................3-1, 4-18 

Main System Window..........................................................................................................3-1, 3-2 

Main Test Menu........................................................................................................................... 3-5 

Manage User Accounts .............................................................................................................. 5-18 

Manual Panelization Programming........................................................................................... 10-37 

Max 40 Column Report Lines per UUT ........................................................................................ 5-8 

Max Errors .......................................................................................................................... 7-17, 434 

Measure...................................................................................................................................... 9-21 

Measure Menu............................................................................................................................ 9-12 

Measured value ............................................................................................................................ 7-4 

Measurement Analysis ............................................................................................................... 10-4 

Measurement Messages ...................................................................................................7-17, 9-20 

Measurement Retries ................................................................................................................. 9-13 

Measurement Statistics ................................................................................................................ 9-1 

MEMD Test Type...........................................................................................................10-39, 14-30 

MEMI Test Type ............................................................................................................10-39, 14-26 

MEML Test Type ...........................................................................................................10-39, 14-26 

Memory Locations .................................................................................................................... 10-39 

Memory Manipulation (Integer)................................................................................................. 14-26 

Memory Manipulation (Real) .................................................................................................... 14-30 

Memory Manipulation (String) .................................................................................................. 14-32 

Memory Manipulation Test Types ............................................................................................ 14-25

Memory Variables..........................................................................................................10-39, 10-47 

MEMR Test Type...................................................................................................................... 14-30 

MEMS Test Type...................................................................................................................... 14-32 

Menu Control....................................................................................................................5-21, 5-22 

Merge (Copy/Append) Test Steps.........................................................................................9-6, 9-7 

Merge Parallel Components ....................................................................................................... 9-21 

Message Test Step................................................................................................................... 14-17 

Miscellaneous Tests ................................................................................................................. 14-43 

MISP Test Type.......................................................................................................................... 14-6 

Monitor Power Output................................................................................................................. 14-5 

Motherboard ................................................................................................... 4-20, 4-21, 4-22, 4-23 

Multi-PCB Panels.................................................................................................................... 10-33 

MultiWriter Command Line Options............................................................................................ 16-3 

MultiWriter Controller......................................................................................................1-4, 1-5, 1-6 

MultiWriter Fixture Design Topics................................................................................................. 6-1 

MultiWriter Fixture I/O (MW FIX IO) ........................................................................................... 6-13 

MultiWriter In System Programming........................................................................................... 10-7 

MultiWriter ISP............................................................................................................................ 14-6 

MultiWriter pps Required Files ................................................................................................... 10-7 

MW FIX I/O Module ...................................................................................................................... 6-6 

N 

Named Variables ...........................................................................................................10-39, 10-40 

New Test Program File................................................................................................................. 9-6 

Nominal Fit.................................................................................................................................. 10-4 

Normal Test Reports ................................................................................................................ 10-32 

Not a valid spec data file ............................................................................................................ 17-2 

Notes about MEMI and MEML ................................................................................................. 10-47 

Notes about MEMR and MEMD ............................................................................................... 10-47 

Notes about MEMS .................................................................................................................. 10-46 

O 

Open File ..................................................................................................................................... 7-3 

Operator Adjustments................................................................................................................... 9-3 

Operator Instructions Setup Screen ........................................................................................... 9-13 

Operator Keypad Installation and Usage ..................................................................................... 4-8 

Operator Message Displays ....................................................................................................... 10-5 

Operator Messages .................................................................................................................... 9-16 

Operator name (Login name) ..................................................................................................... 5-12 

Optimize for Best Results ......................................................................................................9-1, 9-4 

P 

Panelization ................................................................................................................................ 9-21 

Panelization Programming ....................................................................................................... 10-37 

Panelization Programming by Wizard ...................................................................................... 10-36 

Panelization Wizard.................................................................................................................. 10-36 

Panelized assembly.........................................................................................................7-19, 10-36 

Panelized PCBs.......................................................................................................................... 8-17 

Panelized Testing ..................................................................................................................... 10-33 

Pareto Failure Report ........................................................................................................8-1, 15-10 

Pareto Failure Report Example ................................................................................................ 15-10 

Pareto of Batch Errors ................................................................................................................ 7-14 

Part Programming...............................................................................2-2, 6-1, 6-2, 6-31, 10-7, 11-1 

Pass/Fail Indication ...........................................................................................................10-4, 15-1 

Password..................................................................................................................5-19, 5-20, 5-21

Paste Field.................................................................................................................................... 9-7 

Paste Test Steps .......................................................................................................................... 9-7 

Path not found ............................................................................................................................ 17-2 

Pause a Specified Time............................................................................................................ 14-48 

PAUSE Test Step ..................................................................................................................... 14-48 

PCB 

Locations/Numbers Screen................................................................................................... 10-37 

Runtime Options ................................................................................................................... 10-37 

Wiring Assignments .............................................................................................................. 10-37 

PCB Fixture Alignment ............................................................................................................... 6-24 

PCB Number Being Tested ...................................................................................................... 14-19 

PCB Panel Map Window ................................................................................................ 10-38, 434 

PCB Panelization Window ..................................................................................................... 10-36 

PCB Replication Wizard Window.......................................................................................... 10-37 

PCB Test Step.......................................................................................................................... 14-19 

PCB: ......................................................................................................................................... 10-37 

PIF Note.................................................................................................................................... 14-23 

Pin Names .................................................................................................................................. 9-24 

Point Information......................................................................................................................... 10-4 

Point Name Entry.................................................................................................................9-7, 9-24 

Point/Pin Names - Assign / Change ........................................................................................... 9-24 

Port Input Test ............................................................................................................................ 14-9 

Port Output ................................................................................................................................. 14-9 

PORTI Test Type........................................................................................................................ 14-9 

PORTO Test Step....................................................................................................................... 14-9 

PORTx Test Types ..................................................................................................................... 14-9 

Power Supply Considerations ...................................................................................................... 6-5 

Power Supply Control................................................................................................................. 14-3 

Power Supply Overview ............................................................................................................. 13-1 

Pressure Rods...................................................................................................................6-26, 6-27 

Print .....................................................................................................................................9-6, 9-14 

Print Test Results .................................................................................... 4-11, 5-8, 5-22, 7-5, 14-49 

Printer .................................................................................................... 4-11, 5-10, 5-11, 5-22, 5-23 

Printer Setup............................................................................................................................... 5-22 

Printing Test System Configuration.......................................................................................5-1, 5-4 

Probe UUT Point.......................................................................................................4-20, 7-11, 9-24 

Probing ...................................................................................................................................... 9-26 

Problems and Help ..................................................................................................................... 18-1 

Problems with the Test System....................................................................................5-4, 5-6, 18-1 

Production Report.....................................................................................................8-1, 15-9, 15-10 

Production Report Example........................................................................................................ 15-9 

Program Auto Load ...........................................................................................................7-14, 9-20 

Program CheckList ............................................................................................................9-10, 9-11 

Program Flow ........................................................................................................................... 10-24 

Program for SCRN Load Operation.......................................................................................... 11-10 

Program Memory Locations (variables) ................................................................................... 10-39 

Program Multiple Times.............................................................................................................. 7-11 

Program Segments..................................................................................................................... 11-1 

Program Storage ...................................................................................................................... 10-47 

Programmable Power Supply.......................................................................................................6-5 

Programmer Power Button ........................................................................................................... 4-4 

Programming Multiple Devices........................................................................... 2-2, 6-2, 11-3, 11-6 

Programming Multiple Different Devices .................................................................................... 11-6 

Programming Multiple Identical Devices .................................................................................... 11-3 

Programming Multiple Times...................................................................................................... 7-11 

Programming One Device .......................................................................................................... 11-1

Programs in ASCII .................................................................................................................... 9-27 

Programs in Binary .........................................................................................................9-26, 9-27 

PS-UUT-L1 ............4-20, 6-6, 12-1, 13-7, 13-8, 14-3, 14-4, 14-5, 14-6, 14-11, 14-12, 14-30, 14-43 

R 

Read ASCII File.......................................................................................................................... 9-26 

Relative Address....................................................................................................................... 10-47 

RELAY Test Type..................................................................................................................... 14-47 

REM Test Type......................................................................................................................... 14-52 

Remark/Comment in the Test Program.................................................................................... 14-52 

Replicate Options Screen......................................................................................................... 10-37 

Report Device....................................................................................................................5-22, 7-14 

Reporting on Panelized PCBs.................................................................................................... 8-17 

Reports ....................................................................................................................................... 15-1 

Reports sorted by PCB............................................................................................................... 7-19 

ReProgram ..........................................................................................................................7-4, 7-11 

Required Files........................................................................................................................... 10-23 

Reset System ............................................................................................................................... 9-6 

RET Return from Subroutine .................................................................................................... 14-15 

Retain Skip Selections................................................................................................................ 7-18 

ReTry ...................................................................................................................................7-4, 7-11 

RETT Test Type ....................................................................................................................... 14-17 

Return from Test Sub-Program ................................................................................................ 14-17 

RPRTS Test Type .................................................................................................................... 14-49 

RS232 Serial Interface I/O........................................................................................................ 14-40 

RS232 Test Type...................................................................................................................... 14-40 

RSLTS Test Type ..................................................................................................................... 14-52 

Run Test Program from the Editor................................................................................................9-6 

RUN Test Type......................................................................................................................... 14-16 

Running Another Test............................................................................................................... 10-26 

RUNT Test Type....................................................................................................................... 14-16 

Runtime Options....................................................................................................................... 10-37 

RUS (Remote Update System) .................................................................................................. 6-21 

S 

SAFE_HI..............................................................................................................................6-5, 12-1 

SAFE_LO.............................................................................................................................6-5, 12-1 

Sample Reports.......................................................................................................................... 15-1 

Save a Test Program....................................................................................................3-4, 9-6, 9-27 

Save Configuration ..............................................................................................................5-1, 5-16 

Screen and Display Attribute Manipulation .............................................................................. 11-10 

Screen Result for SCRN Test Type....................................................................................... 11-16 

SCRN Load Operation............................................................................................................ 11-17 

SCRN Test Step .................................................................................................11-10, 14-21, 14-22 

Select Skipped PCBs in Panel ................................................................................................. 10-33 

Select Skips................................................................................................................................ 7-18 

Selecting the Test Program .......................................................................................................... 7-2 

Self-Test ............................................................................................................. 1-4, 5-6, 5-7, 14-48 

Self-Test ISP................................................................................................................................ 434 

Self-Test Module Test Step ...................................................................................................... 14-48 

Self-Test of the System Module ................................................................................................... 5-7 

Serial Number..3-5, 4-11, 4-12, 4-13, 5-9, 5-12, 5-13, 5-16, 7-10, 7-14, 7-16, 7-17, 8-14, 8-15, 14- 

34, 14-35, 14-36 

Set Error Counter Used for JMPE ............................................................................................ 14-13 

Set Limits from Measured Value ................................................................................................ 9-12

Show Pareto ............................................................................................................................... 7-14 

Show Pass/Fail........................................................................................................................... 7-15 

Show Unedited Field Values ...................................................................................................... 9-10 

SHUT DOWN............................................................................................................................ 10-26 

Sigma Report............................................................................................................................ 15-11 

Single Step ..........................................................................................................................7-5, 7-11 

Single-Point Probe.............................................................................................................7-11, 10-7 

Skipped PCBs in Panel .............................................................................. 5-16, 7-18, 10-34, 14-32 

Software Installation ................................................................................................................... 4-14 

Sort by Test Title......................................................................................................................... 9-21 

Sort for Best Speed .................................................................................................................... 9-21 

Sound the PC's Beeper ............................................................................................................ 14-52 

Spares Kit ..........................................................................................................................18-2, 18-3 

SPC ................................................................................................................................8-2, 8-3, 8-4 

SPC Data Format ....................................................................................................................... 8-17 

SPC Logging............................................................................................................................... 7-14 

Special features .......................................................................................................................... 9-3 

Special Line ..............................................................................................................5-13, 5-14, 5-16 

Specify Label ............................................................................................................................ 14-11 

Speed (minimize test time) ........................................................................................................... 9-1 

Square Root Function (SQRT) ................................................................................................. 14-30 

Standalone Installations ............................................................................................................. 4-24 

START Button............................................................................................................................... 4-6 

Start Program ................................................................................................... 4-4, 6-13, 6-17, 9-10 

Statistical Analysis.................................................................................................................8-1, 8-2 

Statistical Data Reporting ......................................................................................................... 10-31 

Statistics Data File Example....................................................................................................... 15-6 

Statistics Data Path .................................................................................................................... 5-16 

Status Map.................................................................................................................................. 7-18 

Step Analysis.............................................................................................................................. 10-4 

Storage space........................................................................................................................... 10-47 

Strip Printer................................................................................................................................. 4-11 

STST Test Type........................................................................................................................ 14-48 

System 160-Pin Blocks............................................................................................................... 4-24 

System Configuration ................................................................................................................... 5-4 

System Error Count .................................................................................................................. 14-14 

System Files ............................................................................................................................. 10-22 

System Installation.................................................................................................................1-4, 4-1 

System Module............................................................................................................................. 5-7 

System Motherboard and Expansion ......................................................................................... 4-20 

System Power and Controls ......................................................................................................... 4-4 

System Required Files ............................................................................................................... 10-7 

System Requriements .................................................................................................................. 1-4 

System Variables.................................................................................... 14-25, 14-26, 14-30, 14-32 

T 

T-120-2 Strip Printer Installation................................................................................................. 4-11 

Template for New Test Program .................................................................................................. 9-6 

Temporary Test Results File ........................................................................................................ 7-5 

Terminate Test.............................................................................................. 7-5, 7-11, 10-26, 14-11 

Test............................................................................. 7-1, 7-4, 7-5, 7-6, 7-7, 7-8, 7-9, 10-27, 10-28 

Test Display.................................................................................................................................. 7-8 

Test Failure Screen ...................................................................................................................... 7-4 

Test Menu ...........................................................................................................................7-2, 7-11 

Test Point Assignment................................................................................................................ 9-24 

Test Program

Opening..............................................................................................................................3-4, 9-6 

Printing ...................................................................................................................................... 9-6 

Saving ..............................................................................................................................9-6, 9-26 

Test Program in ASCII.............................................................................................................. 15-5 

Test Program Report .........................................................................................................5-16, 15-2 

Test Program Report Example ................................................................................................... 15-2 

Test Program Segments............................................................................................................. 11-1 

Test Program:........................................................................................................................3-4, 7-2 

Test Progress ............................................................................................................................. 7-16 

Test Report...............................................................................................................7-12, 7-13, 7-14 

Test Report - Special Lines .......................................................................................................... 5-8 

Test Report $RBODY$.DAT File.................................................................................................. 5-8 

Test Report $RBODYT$.DAT File................................................................................................ 5-8 

Test Report $RHDR$.DAT File .................................................................................................... 5-8 

Test Report $RHDRT$.DAT File .................................................................................................. 5-8 

Test Report Contents ................................................................................................................. 7-14 

Test Report Data Path................................................................................................................ 5-16 

Test Results - Report Lines per UUT ........................................................................................... 5-8 

Test Results Report....................................................................................................5-8, 15-1, 15-2 

Test Results Report Example..................................................................................................... 15-1 

Test Screen with Multi-PCB Panels.......................................................................................... 10-33 

Test Steps.....................................................................................................................9-8, 9-9, 10-1 

Test System Configuration ....................................................................................................5-1, 5-4 

Test System Software Installation .............................................................................................. 4-14 

Test Times (minimize) .................................................................................................................. 9-1 

Testing a panelized assembly .................................................................................................... 7-18 

Testing an Assembly .................................................................................................................... 7-1 

Thermal Overload Reset Button...................................................................................................4-4 

Time Estimate Analysis .............................................................................................................. 9-21 

Time storage location ............................................................................................................... 10-47 

Timing events ........................................................................................................................... 10-47 

To Pin ..................................................................................................................................7-4, 10-2 

Tolerances .............................................................................................................................9-3, 9-4 

Too many files open ................................................................................................................... 17-2 

Toolbar....................................................................................................................................... 10-1 

Tools Menu................................................................................................................................ 9-21 

Transfer of Control Test Types................................................................................................. 14-10 

Troubleshooting the Test System.................................................................................5-4, 5-6, 18-1 

Troubleshooting Tips .........................................................................................................18-1, 18-2 

Try Blocks ......................................................................................................................14-11, 14-13 

Turn Fixture Vacuum On and Off ............................................................................................. 14-44 

U 

Unconditional jump ........................................................................................................10-25, 10-26 

Unedited Field Values ................................................................................................................ 9-10 

USB 2 ........................................................................................................................................... 1-5 

USB Disconnect Warning ..................................................................................................5-22, 5-23 

USB Program Storage................................................................................................................ 6-21 

Use PCB Number ..............................................................................................................9-13, 9-24 

User Accounts .......................................................................................................................... 5-19 

User Name.......................................................................................................................5-19, 14-32 

User Password ..................................................................................................................5-18, 5-19 

User-Defined Tests................................................................................................................... 14-23 

User-Written Routines .............................................................................................................. 14-23 

UUT .............................................................................................................................................. 2-1 

UUT ID Serial Number Checking..............................................................................5-8, 7-14, 14-32

V 

VACUM Test Step ....................................................................................................4-4, 4-20, 14-44 

Vacuum Connection ..........................................................................................................4-6, 14-44 

Variables.........................................10-39, 10-40, 10-41, 10-42, 10-45, 10-46, 14-26, 14-30, 14-32 

List.................................................................................................. 9-17, 9-18, 9-19, 10-40, 10-45 

Named...................................................................................... 10-39, 10-40, 10-41, 10-42, 10-43 

Persistent .............................................................................................................................. 10-40 

System ..........................................................................14-26, 14-28, 14-30, 14-33, 14-34, 14-35 

View Menu .................................................................................................................................. 9-10 

Visual Basic Script..............................................................................................10-28, 10-29, 10-30 

Voltage Settings...........................................................................................................10-19, 10-20 

W 

Wait for a Key to Be Pressed ................................................................................................... 14-19 

Memory Manipulation Tests.................................................................................................. 14-25 

WAITK Test Type.................................................................................................................. 14-19 

Wire Run Report.......................................................................................................9-14, 15-7, 15-9 

Wire Run Report Example.......................................................................................................... 15-7 

Wiring Assignments................................................................................................9-13, 10-37, 15-7 

Wiring Diagrams ......................................................................................................................... 12-1 

Wizard Screen .......................................................................................................................... 10-36 

Write ASCII File .......................................................................................................................... 9-26 

Writing a Test Program................................................................................................................. 9-1 

X 

X-Bar/Sigma Report ..................................................................................................................... 8-1 

X-Bar/Sigma Report Example .........................................................................................15-1, 15-11 

XML Files................................................................................................................5-16, 10-7, 14-32 

XSD Files................................................................................................................5-16, 10-7, 14-32 

Y 

Yellow PASS Background ............................................................................................................ 7-6

MultiWriter pps Instruction Manual - CheckSum

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?