YesAX V3.1.2 - Software User Manual - 第212页
15 -8 SPC Data Logg ing On a board with no real defects, the opportunity for false calls is the same as the opportunity for defects. To simplify the calculation we assume the opportunity for false calls also a s the sum …

SPC Data Logging 15-7
Mark1 Mark2
Using Edge Locators for Position Tracking
In addition to using pattern matching you can also use the Edge Locator algorithm for position
tracking. Edge locator provides more accurate position tracking on targets with clear and well
defined horizontal and vertical edges. To use Edge locator for position tracking, train two marks
with the Edge Locator algorithm. The first mark should be trained to locate a vertical edge or
strip and the second mark should be trained to locate a horizontal edge or strip. The first mark
will provide the X position plus the angle data and the second mark provides the Y position data
to the database.
15.5 Robust Mode for Data Logging
In the normal operating mode for data logging, the software opens a link to the database during
software start-up and assumes the link to be there for all the subsequent data logging operations.
This mode of operation works well for most of the network environment. In environments where
the network traffic is heavy and a prolong connection to one computer cannot be guaranteed, the
YesAX software offers a more robust mode of data logging. In the Robust Mode, the software
tests the database connection before each batch of data logging operations. It is slightly slower
but far more reliable. To enable Robust Mode, edit the YesAX.ini file:
[ODBC_Report]
..
RobustMode=1
15.6 Process Alarm
YesAX allows users to setup various trigger conditions to raise process alarms. There are
currently two types of alarms, rate alarms and defect alarms. The rate alarm triggers when the
defect rate or the false call rate exceeds a preset level. The defect alarm triggers when a user-
specified defect condition has been reached.
15.6.1 Rate Alarms
The Rate Alarm triggers when the defect rate or false call rate exceeds the preset level. The
defect rate is measured as PPMO (Part Per Million Opportunities) and is calculated as:
Defects
-------------------------------- * 1,000,000
Opportunity for Defect
The opportunity for defects is the total number of tests performed. It is usually the sum of
Marking, Lead Bank, and Solder inspections.
The false call rate is also measured as PPMO and is calculated as:
False Call Count
-------------------------------- * 1,000,000
Opportunity for False Call

15-8 SPC Data Logging
On a board with no real defects, the opportunity for false calls is the same as the opportunity for
defects. To simplify the calculation we assume the opportunity for false calls also as the sum of
Marking, Lead Bank, and Solder inspections.
A high defect rate would indicate problems upstream. A high false call rate may indicate the
inspection recipe should get additional tweaking.
15.6.2 Defect Alarms
The defect alarm triggers when the user-specified defect conditions are exceeded. There are 10
defect alarms. You can set one defect alarm to trigger when there are more than 3 part defects in
the last 5 runs of boards. You can set another defect alarm to trigger when there are more than 10
solder defects in the last 3 runs of boards.
The first step to setup a defect alarm is to group the defects into classes. This is done by editing
the defect.ini file. Use the @C# notation to assign a class to each defect. The class number starts
with 1 and ends with 9. Defects with no class assignment default to class 0. Here is a sample
defect.ini file with the class assignment.
[01] Unclassified
[02] Missing Part@S@C2
[03] Wrong Part@S@C1
[04] Tombstone Part@S@C4
[05] BillBoard Part@S@C2
[06] Skew Part@C2
[07] Wrong Polarity@S@C3
[08] Lead Solder Bridge@C4
[09] Bend Lead@C4
[10] Insufficient Solder@C4
[11] Solder defects@C4
[12] False Call
After setting the defect classes, setup the trigger condition by selecting Process Alarm.. from the
System menu. The Process Alarm Setup dialog displays.

SPC Data Logging 15-9
15.7 External DLL Interface
YesAX’s extension DLL (Dynamic Link Library) interface is a custom API (application program
interface) designed to interface various shop floor management systems or WIP (work-in-
progress) tracking systems. For various data logging events, the YesAX software calls functions
in the extension DLL (DataLogExt.DLL). You can implement these functions in the DLL to
link with their specific data collection system. Programming skills are required to implement
these interfaces.
Please refer to the ExtDLL.zip file in the Document folder on the YesAX release CD for sample
code and a write-up about the interface.