Customer Config txt - Keysight · Format: The config.txt file has a set format with each line of the file containing a word and data sets separated by a keyboard space. Config.txt

The Config.txt

File

MVTM V Technology Ltd.

______________________________________________________________________________________________________________

______________________________________________________________________________________________________________DOC- 5000-0072 ii

M V T I N S P E C T I O N S Y S T E M S

The Config.txt file

Revision 1.0

April ‘99

Document Part Number 5000-0072

MV Technology Ltd.

Unit 24 IDA Enterprise Centre, Pearse Street, Dublin 2, Ireland

Phone 353-1-6718177 • Fax 353-1-6718470

Email: [email protected] Home Page: www.mvt.ie

All rights reserved. No part of this document may be stored in a retrieval system, transmitted, or used in any form or

by any means, electronic, mechanical, photocopying, recording or otherwise without the prior permission of the

copyright holder.

MV Technology Ltd. retains the right to modify this document without notice.

______________________________________________________________________________________________________________

______________________________________________________________________________________________________________DOC- 5000-0072 iii

Chapter Contents

Overview...........................................................................................1

Config.txt Format.............................................................................1

Editing the config.txt file .................................................................3

Config.txt reference table................................................................3

Obsolete config.txt entries..............................................................5

Config.txt parameters......................................................................61. ! or # ________________________________________________ 6

2. action_on_Failure_extended ____________________________ 6

3. alarm________________________________________________ 8

4. asynch ______________________________________________ 8

5. Auto_delay or Auto_wait_delay _________________________ 9

6. auto_anded _________________________________________ 10

7. bad_panel_detect ____________________________________ 11

8. Barcode ____________________________________________ 13

9. bazic_mode _________________________________________ 13

10. blob________________________________________________ 14

11. delete_results _______________________________________ 15

12. digital_io____________________________________________ 16

13. Dual_file ____________________________________________ 16

14. False_fail ___________________________________________ 18

15. fid_model ___________________________________________ 19

16. file_extension________________________________________ 21

17. gem ________________________________________________ 22

18. goMVC _____________________________________________ 22

19. has_pentium ________________________________________ 23

20. Home_fixed _________________________________________ 23

21. Image_save _________________________________________ 24

22. incoming_disk_cad ___________________________________ 25

23. leds_delay __________________________________________ 26

24. Logging ____________________________________________ 26

25. MB_________________________________________________ 27

______________________________________________________________________________________________________________

______________________________________________________________________________________________________________DOC- 5000-0072 iv

26. Measurement_results _________________________________ 27

27. microns_____________________________________________ 28

28. MMS_System ________________________________________ 28

29. Multi_colour_brds ____________________________________ 29

30. name _______________________________________________ 29

31. no_action_on_fail ____________________________________ 30

32. no_results_in_softstop________________________________ 31

33. OCR________________________________________________ 31

34. Only_one ___________________________________________ 32

35. outgoing_disk_cad ___________________________________ 32

36. placement___________________________________________ 33

37. Printer_level_________________________________________ 34

38. pyramid_data ________________________________________ 35

39. retry_fiducial ________________________________________ 36

40. Reverse_plc _________________________________________ 37

41. Rotate_cad __________________________________________ 37

42. rows _______________________________________________ 37

43. Scroll_errors ________________________________________ 38

44. skew_display ________________________________________ 38

45. skip_delete_allow ____________________________________ 39

46. Sweet_spot__________________________________________ 39

47. two_lines ___________________________________________ 40

48. VScale______________________________________________ 41

49. Width_adjust ________________________________________ 41

50. want_compressed ____________________________________ 41

51. xytable _____________________________________________ 43

52. yx_mode ____________________________________________ 43

53. Zimage _____________________________________________ 45

______________________________________________________________________________________________________________

______________________________________________________________________________________________________________DOC- 5000-0072 v

Revision History

Revision Nature of Change Date1.0 First release April 99

©MVT CONFIG.TXT FILE______________________________________________________________________________________________________________

______________________________________________________________________________________________________________DOC- 5000-0072 1

Overview

The config.txt file is used to set and configure various software features on MVT's

GS-1, SP-1, and SJ-10 inspection systems. A standard config.txt file is shipped with

each system that enables various software settings and functions. However, additional

functionality exists that can be enabled or disabled by the user by manually editing the

config.txt file located in the C:/cpi/data directory.

The config.txt file has the following specifications:

Name Config.txt File.

Location: C:\cpi\data directory.

File type: Text based file that can be edited using Notepad or Wordpad.

Function: Sets and configures various software features on the system.

Format: The config.txt file has a set format with each line of the file containing a

word and data sets separated by a keyboard space.

Config.txt Format

The config.txt file has a set format as shown below:

e.g. alarm 1 1 2

NameName is the word(s) that start every new config.txt line, e.g., alarm.

a The system uses the first and, in some cases, the second letter of the name

to call this function. Case is very important so "alarm" is not the same as

"Alarm". The name "alarm" calls the functionality to do with the machine

alarm.

a If there is more than one word then multiple words must be joined with

an underscore or the config.txt line will not be called by the code.

Therefore "bad panel detect" is an incorrect entry but "bad_panel_detect"

is a correct entry.

a A # or ! at the start of a line can be used for comments or to disable the

functionality of the line.


______________________________________________________________________________________________________________DOC- 5000-0072 2

SpaceSpace represents the keyboard space that must separate each data set. This is very

important and it is essential that at least one keyboard space is left between each

data set.

X (integer, character, or string) X represents one of three things: an integer (%d), a character (%c), or a string (%s).

¾ Integer (%d): These are the most common parameters in the config.txt file.

a In many cases these are simply a "1" to enable some functionality or "0"

to disable some functionality. Other numbers may also be used to call

specific functionality.

a They can represent numerical values such as radii or thresholds.

a They can also be bitfields where each bit calls different functionality. To

enable multiple bits simply add the bit numbers together, e.g., to enable

the functionality of bits 1 and 2 set %d to 3 (1 +2 = 3).

¾ Character (%c): this is a letter or a number. For instance barcodes can start

with either letters or alphabetical characters e.g. "1" or "A."

¾ String (%s): these generally represent file extensions or the locations of

files or directories. e.g. ".txt" for a file extension or a "/tmp" to represent the

temp directory in C:/cpi/.

Important

¾ The system will automatically use the default vaue for a data set ("X"

parameter) if that particular entry is left blank. However this is only the case

if no actual parameters follow this particular data set on the config.txt line.

a For a config.txt line of the form "name %d1 %d2 %d3" and you wish to

use the default value for %d2 by leaving it blank then there can be no

manual entry for %d3. This is because the system will assume that the

%d3 entry is the %d2 entry. Therefore to use the default value for %d2,

the %d3 entry must also be left blank and its default value also used.


______________________________________________________________________________________________________________DOC- 5000-0072 3

¾ In some cases config.txt lines are not present in the config.txt file because

the system automatically uses the default value for that line (see Section 62).

¾ Unless othwerwise specified in sections 1 to 69 the reader can assume that

the config.txt entry applies to all MVT inspection stations, i.e., GS-1, SP-1,

and SJ-10.

Editing the config.txt file

The config.txt file is a text file that must be edited manually using Notepad or

Wordpad. Extreme caution must be taken that the correct case is used, that there is at

least one keyboard space between all data sets, and that multiple words are joined by

an underscore for the "name" parameter. Always make a backup copy of the config.txt

file before editing it.

CAUTION

Caution must be taken when altering config.txt parameters becausean incorrect value or sequence can disable important functionality

and potentially make the inspection station inoperable.

Config.txt reference tableNo. Config.txt name Function1. ! or # Used to insert comments or to disable the functionality of an existing line.2. action_on_failure_

extendedWith this new function enabled, the operator will be asked to act-on-failure onlyafter a critical number of failures have been detected. (Release 1.31)

3. alarm Enables or disables the alarm.4. asynch This sets various parameters for large area cameras.5. auto_shadow

(or auto_anded)This functionality automatically creates a secondary anded unknown DeviceType for every component that is split into 2 or 4 views. This is especiallyuseful for adding polarity checks to parts that have been split into multipleviews.

6. Auto_wait_delay This initially set the seconds to delay before starting inspection - useful ifclamping is slow.New functionality in Releases 1.30 & 1.31 also enables the automatic editingof fiducial parameters.

7. bad_panel_detect Used to specify which panels are to be skipped from inspection. It is also usedto abort the inspection if over a certain % of components are defective.

8. Barcode Specifies various parameters relating to barcode processing.9. bazic_mode Specialist functionality released in Release 1.31 for only one site. It performs

measurements with stretch compensation on but reports measurement withstretch compensation off.

10. blob Enables blob analysis functionality that is used to prevent false accepts whenthere are instances of "cut-back-paste" on the board.


______________________________________________________________________________________________________________DOC- 5000-0072 4

11. delete_results This site-specific functionality can be used to delete all *.acc files or allassociated file types in the res directory.

12. digital_io This mandatory functionality is used to specify whether the inspection station isan actual machine or an offline software version.

13. Dual_file This enables the system to automatically load the correct plx file for the correctsided of a 2-sided board.

14. False_fail This config.txt line performs various functions relating to the marking of falsefailures on the PCB. In addition it can also enable the upgrading of action onfailure options from operator level 1 to higher operator levels.

15. fid_model This important functionality released in Release1.30 enables the system tocompensate for global fiducials that have been placed offset from their nominalpositions.

16. file_extension Specifies the type of file extension the input CAD will have such as a *.txt fileor *.ncx file. It is used when the "F4: Create Board Template" option is selectedfrom the Engineering menu - limited use now.

17. gem This enables SECS-GEM processing18. goMVC This entry is used to enable and configure the Multi Variable Classifier

functionality on the GS-1 that is used to prevent false fails and false accepts.19. has_pentium This is only required for a couple of early prototype GS-1s that did not have a

pentium processor. These machines have since been donated to colleges.20. Home_fixed This is used to specify that the users CAD coordinate system is aligned with

the GS-1s coordinate system. If this is the case (almost never) then theposition of the fiducials do not have to be set.

21. Image_save This important config.txt entry allows the user to specify various parametersrelating to the automatic saving of images of board defects detected duringinspection.

22. incoming_disk_cad This informs the inspection station of where the raw user CAD is located foruse with the "F4: Create Board Template" option from the Engineering menu.

23. leds_delay This config.txt parameter specifies a time delay in milliseconds during whichthe LEDs cannot be turned off or on after an image has been snapped. Thistime delay is used to ensure that the image information has time to travel to thecamera sensor after an image has been snapped.

24. Logging Turns on event logging in the errors.log file, which is useful for diagnosticpurposes if there is a system failure.

25. MB This is used for internal code processing by the SP-1.26. Measurement

_resultsThis functionality for the SJ-10 enables the writing of solder joint inspectionmeasurement results to the Joixxxxx.txt file in the cpi/rep directory.

27. microns Specifies that micron scaling is used.28. MMS_System This is used to specify that the system is an old MMS type system. This is not

required for current systems.29. Multi_colour_brds This enables the GS-1 to automatically differentiate between green and white

boards.30. name This mandatory config.txt entry specifies the name of the MVT inspection

system, e.g., GS-1, SP-1, SJ-10.31. no_action_on_fail This entry enables various Action on Failure options.32. no_results_in_

softstopNo inspection data is written while the system is in softstop so as not to affectresults for charting and process control (Release1.31).

33. OCR This function enables optical character recognition -reading text on SOICs.34. Only_one This is used to set only one component per field of view. It increases inspection

accuracy but also the inspection time.35. outgoing_disk_cad This was initially devised for development of the cpi code but has never had

any function. Through an oversight it is still present in most config.txt files36. placement_type This specifies the CAD conversion mode to be used when the "F4: Create

Board Template" option is selected from the Engineering menu, e.g., sanyo,generic, multi-fuji

37. Printer_level This allows the user to develop their own external program that will beautomatically called after an inspection. This program must use a file called"error ticket" as an input and can be useful for results processing.

38. pyramid_data This allows the user to set various options relating to writing of pyramid files.39. retry_fiducial The enables the system to retry fiducial 1 inspection until the image is stable.

This should improve load/unload R&R tests when there is no clamping.(Release 1.3.1)

40. Reverse_plc This is used to reverse boards back out of the GS-1 when a repair station islocated before the GS-1.


______________________________________________________________________________________________________________DOC- 5000-0072 5

41. Rotate_cad This can be used to automatically rotate the CAD by 180 or 90 degrees uponloading. This may be required if the board is loaded onto the conveyor in adifferent orientation to the one in which it was programmed.

42. rows This specifies the maximum number of components in the plx file.43. Scroll_errors This functionality for the SJ-10 allows the user to have the last 24 lines of the

errors.log file displayed in a new console window on screen once errors aredetected on the board.

44. skew_display This allows the user to set various parameters relating to the display of cameraskew

45. skip_delete_allow This function allows users to delete a skip file when the *.plx file is loaded(Release 1.31). This allows the user to control what is being inspected.

46. Sweet_spot This optional functionality specifies that only components within a certainpercentage of the field of view are to be displayed in the Bullyseye chart andreported in the *.cmp files. This does not make a significant difference inaccuracy and it is not recommended that this functionality be used.

47. two_lines This is a mandatory config.txt entry for dual rail systems that also informs thecode whether barcodes are being used by the system.

48. Vscale This is used to bias the XY tables movement in the axis that carries the leastphysical weight in order to optimize the view path.

49. want_compressed This useful config.txt entry controls various options relating to the writing ofcompressed results files to the C:\cpi\res directory.

50. Width_adjust This enables the functionality of the of the Automatic Width Adjust system,which is used to automatically adjust the conveyor rail with for different boardtypes used.

51. xytable This specifies whether the system is an actual machine or offline software.52. yx_mode Switches the X and Y results in the rep and other output files so that the

standard XY coordinate system can be used.53. Zimage This optional config.txt entry specifies various options relating to the display of

the board graphic view of the board, i.e, the charting display shown after aninspection.

Table 1.0 Functtional config,txt parameters

Obsolete config.txt entries

The following config.txt entries have become obsolete since they were initially

developed. If a user encounters any of the following "words" (config.txt name)

starting a new line in their config.txt file they should delete the line.Config.txt name Format0rthogonality 0rthogonality % d1 %d2 %d3Calibration Calibartion %d1 %d2 %d3check_commands check_commands %dcim cim %ddatabase database %dexecutable directory executable_dir %sLeds_always Leds_always %dSa Save %dsKew sKew %dspecial special %dunknown_data unknown_part_num_file %sview_offsets view_offsets %dXystop_bit Xystop_bit %dzoom_ok zoom %d

Table 1.0 Obsolete config.txt parameters


______________________________________________________________________________________________________________DOC- 5000-0072 6

Config.txt parameters

1. ! or #

Function

A "!" or "#" as the first character of a line allows the user to input a comment in the

config.txt file.

Placing a "!" or "#" before an existing line is also a simple method of disabling the

functionality of the line. To enable the functionality at a future time the user simply

has to delete the "!" or "#".

Format

"!" followed by a line or comment or "#" followed by a line or comment.

Example

The following line inserts a comment into the config.txt file

! The previous line enables barcode processing.

The following example disables the functionality of an existing line.

! alarm 1

2. action_on_Failure_extended

Function

With this new functionality enabled, the operator will be asked to "Act-on-Failure"

only after a critical number of failures have been detected. The critical failure

threshold can be set depending on the type of component and failure type. The user

can define all of these thresholds (see Release 1.31).

This means that if skew and/or offset failures are not a critical failure for your

company you can program the system not to flag the operator about these types of

failure until a threshold number of defects has been detected. If no critical errors

occur then the system will not stop.

Note: All errors will still be recorded in the *.rep files.

Format

action_on_failure_extended %d


______________________________________________________________________________________________________________DOC- 5000-0072 7

Set %d to 1 if you want to enable this functionality.

To disable this functionality set %d to 0, delete the line, or comment out the line.

Example:

action_on_failure_extended 1

How to use this functionality

To add this functionality to your system perform the following:

1 Add the line "action_on_fail_extended 1" to the config.txt file.

2 Download version Release 1.31 or greater.

3 Copy a file called fail_table.txt to the cpi/data/ directory; contact MVT for

this file.

The user must then edit the fail_table.txt file to specify the critical failure

thresholds.

An example of the fail_table.txt:

missing skew offsetall 0 5 6type t 0 2 3type s 0 1 2

First column of the row: all – refers to all components.

type – refers to a specific type of component.

Second column: If “type” is the first entry in the line then the type of

component needs to be specified. The components are

designated in the same way as the algorithms (e.g. r =

resistor; b = bright box; s = SOIC etc.)

If “all” components are specified, this field is left blank.

Third column: threshold for missing components. This is usually 0 as

most sites want to be flagged of this immediately as the

board will not function correctly.

Fourth column: threshold for skew errors before the operator is notified

via the action on failure screen.

Fifth column: threshold for offset errors.


______________________________________________________________________________________________________________DOC- 5000-0072 8

Example:

If we use the above entries to the fail_table.txt a critical error will occur if:

There is a missing component.

all 0 5 6 There are 5 skew errors in all the components.

There are 6 offset errors in all the components.

3. alarm

Function

This line allows the user to specify whether they want an audible alarm to ring when

board defects are detected by the MVT inspection station.

Format

alarm %d

Where % d is an integer with values 0 or 1.

Set %d to 1 if you want the system to ring the audible alarm on Failure.

Set %d to 0 (default setting) if you do not wish the alarm to ring when board defects

are detected after an inspection.

e.g., alarm 1

4. asynch

Function

This mandatory config.txt entry for large area camera GS-1s sets various camera-

related system parameters. This line should never be included for MVT inspection

stations with small area cameras.

Note: asynch refers to the asynchronous mode in which the large area cameras

operate in.

Format

asynch %d1 %d2%d3

¾ %d1 is used to specify the time in milliseconds that the camera must be

stationary after an image has been snapped so that the image information has


______________________________________________________________________________________________________________DOC- 5000-0072 9

time to travel to the camera sensor. This value depends on the framegrabber

used.

a For mutech framegrabbers set this to 8

a For Pulsar framegrabbers set this value to 16

¾ % d2 is used to specify the time delay in milliseconds between when the XY

table comes to a halt and the camera image is snapped. This improves

accuracy because camera vibrations are minimized when the image is

snapped.

a For mutech framegrabbers set this to 16

a For Pulsar framegrabbers set this value to 20

¾ % d3 is used to specify the time delay in milliseconds between when the XY

table comes to a halt and the camera image of the fiducial is snapped.

Because fiducial measurement and location affects all subsequent board

measurements it is essential that these are measured correctly. Essentially

this parameter is used to add an additional time delay so that camera

vibrations are kept to as minimum when the initial camera images of the

global fiducials are taken. This value is typically set to twice the value of

%d2

a Set this value to 40.

Example

The following example shows the default config.txt line for inspection stations with

large area cameras using mutech framegrabbers:

asynch 8 16 40

5. Auto_delay or Auto_wait_delay

Function

This config.txt option performs the following:

1 Previous to Release 1.30 the Auto_delay paramater had the following

function. This optional config.txt line specifies the number of seconds that the

system must delay between when the board comes to a halt at the board stops


______________________________________________________________________________________________________________DOC- 5000-0072 10

and the inspection commences. Basically this funcionality is used to make

sure that the board is completely stationary when the inspection comences. It

should only be required if the clamping is slow or the board is subject to

vibration.

2 Release 1.30 and 1.31 added additional functionality to this config.txt line

regarding automatic fiducial editing.

Format

Auto_delay %d1 %d2 %d3 %d4

¾ %d1 specifies the seconds to delay before inspection. This parameter has a

valid range of between 0 and 5 seconds but should be left at 0 unless

specified by MVT.

¾ %d2 enables Auto-Fiducial Training if set to 1 and disables Auto-Fiducial

Training if set to 0.

¾ Set %d3 to 1 to allow the fiducial parameters to be altered by the software.

Set %d3 to 0 so that the fiducial parameters cannot be altered by the

software.

¾ Set %d4 to 1 so that the software will automatically try and deduce the

shape of the fiducial. If %d4 is set to 0 then the software will not

automatically try and deduce the shape of the fiducial.

Example:

This following default line enables auto-fiducial training with automatic fiducial

parameter setting and optimisation of fiducial shape.

Auto_wait 0 1 1 1

.

6. auto_anded

Function

This functionality for the GS-1 automatically creates a secondary anded unknown

Device Type for every component that is split into 2 or 4 views. This is especially

useful for adding polarity checks to parts that have been split into multiple views.

When the primary Device Type is anded with a secondary Device Type both Device

Types must pass inspection for the part to pass.


______________________________________________________________________________________________________________DOC- 5000-0072 11

Format

auto_anded %d

Set %d to 1 to enable this functionality.

To disable this functionality set %d to 0, delete this line, or comment out the line.

e.g., auto_anded 1

Use

Components larger than the field of view such as large SOICs must be split into 2 or 4

views. To do this the user assigns a primary Device Type to the part and then splits the

part into multiple rows. Each row of leads is then inspected seperately and has a

separate device line in the *.plx file. However, components that have been split into

multiple views cannot have polarity checks assigned to them. To solve this problem a

secondary anded component can be assigned to the part. This can be done manually

from the Device Editor menu or, automatically, by adding the "auto_anded 1" line to

the config.txt.

Once the auto-anding functionality is enabled, a secondary unknown Device Type

(n000) is automatically assigned to the part when the part has been split into multiple

views. The user is then required to assign a valid Device type to the component as the

seconday type. Typically this seconday Device Type is a Statistics algorithm but it

should never be the same algorithm as the primary Device Type.

7. bad_panel_detect

Function

This optional config.txt line allows the user to specify which board panels are to be

skipped from inspection. It also allows the user to specify a percentage of failed

components on a board above which the MVT inspection system will assume the

board to be unpopulated or bad and abort the inspection.

Format

bad_panel_detect %d1 %d2%d3%d4 %d5


______________________________________________________________________________________________________________DOC- 5000-0072 12

%d1 is the percentage of components on a PCB that must fail inspection for the

inspection to be automatically aborted because the board is considered to have

too many errors or is unpopulated. This is set by default at 40.

%d2 is used to enable or disable block skip detection. If this is enabled then the

inspection station will not inspect a board on a panel that has its block skip

mark blackened out. Set %d2 to 2 so that block skip detection is enabled. Set

%d2 to 0 so that block skip detection is disabled.

Note: For block skip detection to work the block skip numbers and locations

must be contained in the *.plx file.

%d3 is the size of a side of the block skip check region in microns

[default = 800 microns ].

%d4 represents the brightness intensity threshold that the system uses when

inspecting block skips to determine if the corresponding board is to be

inspected or skipped from inspection. Block skips with a brightness intensity

below this value are considered bad and the corresponding board on the panel

will be skipped from inspection.The valid range of brightness intensities is 0

to 255 as shown in Figure 1.0. %d4 has a default value of 120. If a board is to

be skipped from inspection the corresponding block skip is blackened out.

The brightness intensity will then be below the threshold value of 120.

Figure 1.0 GS-1 Brightness Intensity Scale

%d5 is used to specify if the LEDS are turned on before inspecting the block skip

regions. This may be required if the block skips are very dull. Set %d5 to 1 to

turn on LEDS on or set to 0 (default) to leave them off.

Example

The following example specifies that board 3 of the PCB should not be inspected and

that the inspection should be aborted if 40 percent of the board is found to be bad.

bad_panel_detect 40 3 800 120 0


______________________________________________________________________________________________________________DOC- 5000-0072 13

8. Barcode

Function

This specifies various paramaters relating to barcode processing. This line was

originally designed for Unix style barcode control and since the introduction of

Windows NT control some of the parameters have become obsolete.

Format

Barcode %d1%d2%d3

¾ %d1

a Set %d1 to 0 if there are no barcodes on the system

a Set %d2 to 1 to read the last barcode serial number. This is the default

mode that should always be used if there is only one barcode on the board.

a Set %d1 to 2 if there are 2 barcodes on the PCB and you wish to read the

last barcode that physically enters the inspection station. This is rarely

used.

¾ %d2 has become obsolete since Windows NT control of barcode processing.

Leave this entry blank.

¾ %d3 has become obsolete since Windows NT control of barcode processing.

Leave this entry blank.

Example

Barcode 1

9. bazic_mode

Function

This is very specialist functionality that is curently only used in one site. When this

functionality is enabled the inspection system will measure with stretch correction off

but use stretch correction on for inspection. This is very rarely used.

Format

bazic_mode %d

Set % d to 1 to enable this functionality.


______________________________________________________________________________________________________________DOC- 5000-0072 14

To disable this functionality set %d to 0, delete this line, or comment out this line.

10. blob

Function

This optional functionality for the GS-1 can be used to help prevent false accepts on a

PCB because there are instances of “Cut-back paste “ on the PCB.

“Cut-back paste “ occurs when the solder paste does not fill the entire pad on the

substrate (PCB) and the bare pad (white area) is exposed in part. The blob analysis

mode is available for chips and transistors but is now superceded by the MVC

functionality.

Format

blob %d1 %d2 %d3 %d4 %d5 %d6 %d7 %d8 %d9 %d10

where % d1 to % d10 are min_area max_area circularity interior min_x_extent

max_x_extent min_y_extent max_y_extent bounding_box_min_area

bounding_box_min_area, respectively.

¾ min_area and max_area are limits on area ratios. If the blob area is less than

the expected area divided by min_area or greater than the expected area

times max_area, it is rejected.

¾ circularity is the limit on the circularity ratio. Circularity is a measure of

how much perimeter a blob has with respect to its surface area. A circle has

small circularity, a thin line has large circularity. If the measured blob has a

circularity score larger than the expected value times circularity, it is

rejected.

¾ interior is the smallest allowable blob interior relative to the expected one.

The interior of a blob is taken to be its area minus its perimeter. If the

measured interior is smaller than the expected value divided by interior, it is

rejected.

¾ Min_x_extent, max_x_extent, min_y_extent and max_y_extent do the same

things in the component’s major and minor axes, respectively. The measured


______________________________________________________________________________________________________________DOC- 5000-0072 15

extents of the bounding box of the blob are compared with the expected

values. If the extent in the x direction is less than the expected value divided

by min_x_extent or if it is bigger than the expected value multiplied by

max_x_extent, then the blob is rejected. The same applies in the y direction.

¾ bounding_box_min_area and bounding_box_max_area are limits on area

ratios for the blob’s bounding box. If the bounding box area is less than the

expected area divided by bounding_box_min_area or greater than the

expected area times bounding_box_max_area, it is rejected.

Example:

The recommended blob analysis line will look as follows in the config.txt file:

blob 2.0 2.0 2.5 3.0 2.0 2.0 2.0 2.0 3.0 2.0

11. delete_results

Function

This is very specialist functionality that is verr rarely used. It can be used to delete all

*.acc files or all associated file types in the res directory. This is required for the

Flensburg files and allows the customer to clear out the res directory before starting a

new task.

Format

delete_results % d

set %d 1 to 1 to enable all *.acc files files to be manually deleted

Set %d2 to 2 to enable all of the same file types to be deleted in the res directory.

Use

Once this funcionality is enabled by setting %d to 1 the *.acc files can be deleted by

pressing F1 in the Filing menu.

Once this funcionality is enabled by setting %d to 2 all associated file can be deleted

by pressing F1 in the Filing menu.

Example

delete_results 1


______________________________________________________________________________________________________________DOC- 5000-0072 16

12. digital_io

Function

This mandatory config.txt entry is used to specify whether the inspection station

(SP-1, GS-1, SJ-10) is an actual machine or whether it is an offline software version.

It is also used to specify the duration of the "board failed inspection" signal to the

downstream machine.

Format

digital_io %d1 %d2

¾ %d1 is used to specify wheteher there is a real digital input or not. Set %d1

to 1 if there is a real inspection station. Set %d1 to 0 if you are using the GS-

1 offline software package for training boards.

¾ %d2 is used to specify the duration in milliseconds of the "board failed

inspection" signal to the downstream machine.The downstream machine

may be a repair station, a buffer, or an oven. This is set by default to 2000

milliseconds and MVT recommend that this not be changed.

Example

digital_io 1 2000

13. Dual_file

Function

This optional config.txt line enables dual plx file processing for boards with

components placed on both sides. The system can use block skips, sensors, or

fiducials to determine which side of the board is the correct one to be inspected. If the

current *.plx loaded is for the wrong side of the board then the system will

automatically load the *.plx file associated with the right side of the board to be

inspected.

Format

Dual_file %d

Set %d to1 to enable the automatic switching of plx files.


______________________________________________________________________________________________________________DOC- 5000-0072 17

To disable this functionality set %d to 0, delete this config.txt line, or comment out the

line.

Example:

Dual_file 1

Use

Once dual file processing has been enabled in the config.txt file, the user is required to

set various options relating to dual file processing. Selecting the F5 command in the

Filing menu allows the user to select two files, and switch between them based on an

opto22 Digital Input, blockskips, or fiducials.

Figure 2.0 Dual file menu

Carry out the following procedure for dual file processing:

1 Select the topside plx.file from the list displayed and press return.

2 Select the bottomside plx file from the second list displayed and hit return.

3 Select the method of switching files

a Sensors

Users will initially be asked whether they wish to switch files based on sensor

analysis. This could be set up so that the sensor is looking for a hole in the

board that is not present when the board is flipped over.

a Block Skips

If block skips are selected then the *.plx files will be switched based on a

block skip failure.


______________________________________________________________________________________________________________DOC- 5000-0072 18

a Fiducials

Files will be skipped based on fiducial failuire.

14. False_fail

Function

This config.txt line performs various functions relating to the marking of false failures

on the PCB. In addition, it can also enable the upgrading of Action on Failure options

from operator level 1 to higher operator levels.

Format

False_fail %d1 %d2

¾ %d1 is a bitfiled based on the enabling of bits 1, 2, and 4. Each bit calls

different functionality and to enable multiple bits simply add the bit numbers

together. For instance to enable the functionality of bits 1 and 2 set %d1 to 3

(1 +2 = 3). To enable the functionality of just bit 2 then set %d1 to 2.

a Bit 1 enables the marking of false failures in the action on failure menu.

a Bit 2 is specifically designed for repair loops where a board is re-inspected

in the GS-1 after repair work has been carried out on it. If a part was

marked as a false failure the first time a board was inspected then the part

will never fail inspection when it is reinspected.

a If Bit 4 is enabled then the system does not ask the user to enter a reason

for the false fail. Instead the user should press return when marking a false

fail and the error message displayed on screen will automatically be

entered.

¾ %d2 allows the upgrading of options in the Action on Failure menu.

a If this is set to 0 then this functionality is disabled

a If this is set to 1 then an operator at level 1 can access operator level 2

options in the action on Failure menu by inputting the correct password.


______________________________________________________________________________________________________________DOC- 5000-0072 19

a If this is set to 2 then an operator at level 2 can access operator level 3

options in the Action on Failure menu by inputting the correct password.

Note: The operator level does not automatically reset when the Action on Failure

menu is exited.

Example

False_fail 1 1

15. fid_model

Function

This important functionality enables the system to compensate for global fiducials that

have been placed offset from their nominal positions. This is extremely important

because all positions on the PCB are measured relative to the fiducials. This

functionality was released in June 1998 in Release 1.30 for the GS-1 and should be

added to all systems. This release marks a significant improvement on the fiducial

compensation that was performed by default by the cpi code previous to Release 1.30.

With 2 fiducials the model allows us to correct for translation, rotation and uniform

scaling. Scaling is uniform and is either radial or axial (along the line joining the

fiducials).

With 3 fiducials we can also correct for shear, and have shear and separate x and y

axes.

Background information

¾ Translation – we correct for offset between where we expect the fiducials to

be and where we measure them to be.

¾ Rotation – we rotate the position of the found fiducials so that their line is

parallel with the expected fiducial line.

¾ Isotropic scaling – we scale the found fiducials to coincide with the expected

positions. There are two types of scaling we can use:

a Radial – the found fiducials are taken to be


______________________________________________________________________________________________________________DOC- 5000-0072 20

endpoints on the diameter of a circle. The

plane is then scaled so this circle is

coincident with the circle defined by the

expected fiducial positions

a Axial – the plane is scaled only along the line

joining the fiducials

a By applying the transformation thus found to the view positions, we can

correct for rotation, offset and scaling.

The three fiducial model

Three fiducials give us more information to work with, allowing us to correct for

stretch along 2 axes and also to correct for shearing along one of the axes.

The code works by first applying the 2 point axial transformation to the first two

fiducials. Having done this, we have to scale in the direction orthogonal to the first

two fiducial lines. Finally, we shear along the fiducial 1 – fiducial 2 axis until the 3

fiducials are aligned.

Format

fid_model %d

where %d is an integer bitfield specifying the user options.

The following bitfields can be enabled:

0 Do nothing. Use the old fiducial model.

1 Use new model.


______________________________________________________________________________________________________________DOC- 5000-0072 21

2 Set origin to midpoint of fiducial 1 – fiducial 2 line. Otherwise fiducial 1

is taken to be the origin of the coordinate system. This affects the behavior

of the scaling.

4 Use axial scaling in the case of 2 fiducials. Otherwise radial scaling is

used.

8 turn on scaling in the fid 1 – fid 2 direction

16 turn on scaling in the fid 2 – fid 3 direction

32 turn on shear correction in the fid 1 – fid 2 direction

Note: Note: the last 2 options only take effect in the case of a 3 fiducial board.

Example

We recommend that number should be set to 63 (=1+2+4+8+16+32) to enable all

options. Therefore the config.txt line will be:

fid_model 63

16. file_extension

Function

This optional config.txt entry is used to specify the CAD file extension that is to be

used by the system when the "F4 : Create Board Template" is selected from the

Engineering menu. Typically the user should select a *.txt for a text file. However,

MVT recommend that CAD files are converted using external CAD converters and

not the cpi-integrated CAD converter.

Format

file_extension %s

where %s specifies the file format that the CAD file is in.

The user should select a ".txt" file. Previously *.ncx files were used by Sanyo.

Example

file_extension .txt


______________________________________________________________________________________________________________DOC- 5000-0072 22

17. gem

Function

This optional functionality enables SECs-GEM processing.

Format

gem %d %s1 %s2

¾ set %d to 1 to enable SECs-GEM processing or set to 0 to disable this

functionality.

¾ %s1 is an optional parameter specifying the name of the computer system

that is running the Security program. The security software is used to

validate the run time license code required to enable the GS-1 Gem interface.

Set to "LocalHost" by default.

¾ %s2 is an optional parameter specifying the location of the batch file used

to start the MVT custom GemServer. Set to

c:\GemProjects\MVTServer\MVTServer.bat by default.

Example

Gem 1 LocalHost c:\GemProjects\MVTServer\MVTServer.bat

18. goMVC

Function

This functionality is used to enable the Multi Variable Classifier (MVC) functionality

on the GS-1. This functionality is used to prevent false fails and false accepts on a

board.

Format

go_MVC %d1 %d2

where

¾ %d1 is either 1 to enable the MVC functionality or 0 to disable it.

¾ %d2 is the number of boards that must be inspected for the MVC to work

properly. This should not be set to lower than 3 (default value). If this is set

to 3 then this means that 3 populated boards and 3 pasted boards must be

inspected before MVC will work.


______________________________________________________________________________________________________________DOC- 5000-0072 23

.Example

goMVC 1 3

19. has_pentium

Function

This functionality is used to inform the system if the inspection station PC is not using

a Pentium processor. This is only required for the early prototype GS-1s, most of

which have now been donated to colleges. In all current machines this config.txt line

is not required and should be deleted if encountered.

It will have the following format in the config.txt file:

has-pentium 0

20. Home_fixed

Function

This optional functionality is used to specify that the user's CAD coordinate system is

aligned with MVT's coordinate system. This is useful because the position of fiducials

on the board never have to be set to inform the inspection station of the offsets

between the 2 coordinate systems. However, for this to work the user must have a

rigorous CAD system where the coordinates are fixed all the time. This is usually not

the case, and unless the user has a wide variety of boards going through the system

MVT recommends that this functionality never be used.

Format

Home_fixed %d

Set %d to 1 if the coordinate systems are aligned.

Set %d to 0 to disable this functionality, delete this line, or comment out this line.

The following example shows the default mode that this line is set to:

Home_fixed 0


______________________________________________________________________________________________________________DOC- 5000-0072 24

21. Image_save

Function

This important config.txt entry allows the user to specify various parameters relating

to the automatic saving of images of board defects detected during inspection. Once

this functionality is enabled images of failed components will be automatically saved

to the C:\cpi\img directory after each inspection.

Format

Image_save %d1 %d2 %d3 %d4 %d5

¾ % d1 can be set to 0, 2, 4, or 8.

a Set %d1 to 0 so that no images are automatically saved when a part fails.

a Set %d1 to 2 so that defect images are automatically saved to the

C:\cpi\img directory and are named after the reference designator. If the

reference designator is named 2:r101 then the image will be saved as E_2-

r101.pgm

Note: The E_ denotes an automatically saved image as opposed to a D_ image,

which is an image that was manually saved from the Action on Failure

menu.

Note: ":" will be mapped to "-" thus E_2:r101.pgm becomes E_2-r101.pgm

a Set %d1 to 4 (default value) so that defect images are automatically saved

to the C:\cpi\img directory are named after both the reference designator

and rep file number. If the reference designator is named 2:r101 and the

rep file number is 124 then the image will be saved as E_124_2-r101.pgm.

It is typically used with dual lane systems or can be used to save the last

512 board's rep files.

a Set %d1 to 8 so that defect images are automatically saved to the

C:\cpi\img directory are named after both the barcode label and reference

designator. If the reference designator is named 2:r101 and the barbode

label is 25EXY then the image will be saved as E_25EXY_2-r101.pgm.

¾ %d2 specifies how many images can be saved to the C:\cpi\img directory per

inspection. This is used to limit the size of the image directory and is set by


______________________________________________________________________________________________________________DOC- 5000-0072 25

default to 12. This only limits the number of E_ type images that are

automatically saved but does not affect the manual saving of images from

the Action on Failure menu.

¾ %d3 specifies the maximum image size in bytes that can be saved to the

C:\cpi\img directory after each inspection. The default value is 40,000.

¾ %d4 allows the user to save an image of the first global fiducial on the

board after every inspection. Set %d4 to -1 so that fiducial images are saved

or set to 1 (default value) so that fiducial images are not saved.

¾ If %d5 is set to 1 (default value) or left blank then all error images in the

img directory will be automatically deleted after a new inspection. If this is

set to 0 then the error images in the img directory will not be deleted after a

new inspection.

22. incoming_disk_cad

Function

This informs the GS-1 where the raw user CAD is located for use with the "F4 :

Create Board Template" option in the Engineering menu. By default, the raw user cad

is kept in the cad directory in a folder called tmp.

Format

incoming_disk_cad %s

where %s specifies the location of the raw user cad in the cpi cad directory.

By default the raw user CAD is located in the tmp folder in the cpi cad directory.

However, users are free to specify an alternate location for the raw CAD within the

cpi cad directory. To do this they create new folders or sub folders within the cad

directory using Windows NT Explorer or File Manager and specify their location in

the config.txt entry. For example the user may rename the tmp directory to the name

raw user cad and create a subfolder within this folder termed muti-panel boards

The config.txt entry would then read

incoming_disk_cad /raw_user_cad/multi_panel_boards


______________________________________________________________________________________________________________DOC- 5000-0072 26

Example

The following example is how this entry will appear by default in the config.txt file

incoming_disk_cad /tmp

23. leds_delay

Function

This config.txt parameter specifies a time delay in milliseconds during which the

LEDs cannot be turned off or on after an image has been snapped. This time delay is

used to ensure that the image information has time to travel to the camera sensor after

an image has been snapped. This parameter is designed for asynchronous cameras, i.e.

large area cameras.

Format

leds_delay %d

where %d is the time in milliseconds during which the LEDs cannot be turned off or

on after an image has been snapped.

The recommended value for %d is 10.

Example

leds_delay 10

24. LoggingThis useful config.txt line enables functionality that reveals the cause of a system

failure. It turns on event logging in the errors.log file, which can be checked after a

system failure to reveal the nature of the failure.

Format

Logging %d1 %d2 %d3

¾ Set %d1 to 1 (default) so that the events.log file is automatically updated or

set to 0 so that it is not updated. To turn off event logging set % d1 to 0,

delete this config.txt line, or comment out the line. The events.log file is

typically updated when a new board is loaded, when the privelege levels are

changed, or upon startup or shutdown.


______________________________________________________________________________________________________________DOC- 5000-0072 27

¾ Set %d2 to 1 so that the edit_databases.log file is automatically updated or

set to 0 so that it is not updated.

¾ Set %d3 so that there is a " Status" line written in the events.log file every

"n" seconds where %d3 is the value n. The default value is 900, which

corresponds to 15 minutes. This line in the events.log file can be checked to

verify that the system is running correctly.

Example

The following line should be included in the config.txt file:

Logging 1 1 900

25. MB

Function

This config.txt entry for the SP-is used for internal code processing.

Format

MB %d

%d should always be set to 1 to enable this functionality unless otherwise instructed

by MVT.

MB 1

26. Measurement_resultsThis functionality for the SJ-10 enables the writing of solder joint inspection results to

the Joixxxxx.txt file in the cpi/rep directory. Currently only joint inspection results for

SOIC components, chips, and transistors will be written to this file.

Note: The xxxx in the joixxx.txt refers to the number of boards inspected since

the machine was started up. Therefore if the 100th board is being inspected

since the machine was started up then the joint inspection results will be

writen to the joi100.txt file in the cpi/rep directory.

Format

Measurement_results %d

¾ %d can be set to 0, 1 or 2.


______________________________________________________________________________________________________________DOC- 5000-0072 28

a Set %d to 0 so that no joint measurement results are written to the

joixxx.txt file.

a Set %d to 1 so that only the joint measurement results of failed

components are writen to the joixxxx.txt file.

a Set %d to 2 so that the joint measurement results of all components are

writen to the joixxxx.txt file.

Example

Measurement_results 1

27. microns

Function

This mandatory config.txt entry specifies the type of scaling used by the MVT

inspection station. It must be set so that micron scaling is used.

Format

microns %d

Set %d to 1 to enable micron scaling. This has been the default scaling used since

1995.

Note: %d can also be set to 0 to set the scaling at a thousandth of an inch.

However, this should never be used.

Example

microns 1

28. MMS_System

Function

This is used to specify that the inspection system is an MMS system. Only a few of

these MMS systems were ever built. However, if the inspection station is an MMS

system then this is a mandatory config.txt entry.

Format

MMS_System 1


______________________________________________________________________________________________________________DOC- 5000-0072 29

29. Multi_colour_brds

Function

This useful config.txt entry can be set so that the inspection station can automatically

differentiate between white and the standard green coloured boards.

Format

Multi_colour_brds %d1 %d2 %d3

¾ Set %d1 1 to enable this functionality or 0 to disable it.

¾ % d2 is a grey level threshold that is used by the system to differentiate

between white and green boards. The system checks a region near fiducial 1

and if the average grey level is greater than this it considers the board to be a

white one. The valid range for %d2 is between 0 and 255 where 0 represents

maximum darkness and 255 represents maximum brightness. The default

value for %d2 is 150. In the case of a white board, the system creates a new

file and changes the Part numbers to begin with W and the shapes to end in

W. Thus you effectively have a new file to process.

¾ %d3 can be used to turn the LEDs on when checking if the board is white or

green so that the contrast is improved. Set this to 1 to turn on the LEDs for

this check or set to 0 (default) to leave the LEDs off.

Example

Multi_colour_brds 1 150 0

30. name

Function

This mandatory config.txt entry is used to specify the name of the MVT inspection

station for internal processing of the cpi code.

Format

name %s

where %s is the name of the MVT inspection station. Valid MVT names include the

following: GS-1, SP-1, SJ-10

e.g., name GS-1


______________________________________________________________________________________________________________DOC- 5000-0072 30

31. no_action_on_fail

Function

This config.txt line enables two action on failure options; however, only one option

can be enabled at any one time.

1 If the first option is enabled boards are automatically released from the

inspection station even if board defects are detected. This option is typically

enabled when there is an MVT repair station used in conjunction with the

inspection station. Basically this is used to specify that a repair station will be

used to re-examine the board defects and not the GS-1.

2 If the second option is enabled operators cannot exit from the action on

failure menu until they have scrolled through all the errors on the board. This

ensures that operators are not releasing the board without viewing the board

defects for authenticity.

Format

no_action_on_fail %d1 %d2 %d3

¾ %d1:

a Set to 2 to automatically release boards from the inspection station even if

board defects are detected.

a Set to 4 so that operators cannot exit the action on failure menu until they

viewed all the board defects.

¾ Set %d2 to 1 if you wish the time taken for the last board inspection to be

displayed in the "Error Status" box in the top right hand corner of the text

screen. This is of limited use

¾ If more than %d3 errors are detected on a board then the operator is not

forced to reinspect all the errors. It need only be set when % d1 is set to 4 so

that the operator cannot exit the action on failure menu until they have

viewed all board defects. The is typically set to 16.


______________________________________________________________________________________________________________DOC- 5000-0072 31

Example

no-action_on_failure 4 1 16

32. no_results_in_softstop

Function

If this optional but useful config.txt entry is enabled, inspection data will not be

written to the charting package when the inspection station is in Softstop. This

ensures that when an engineer is initially training a board and carrying out inspections

the inspection information will not be used for statistical process control. This is

important because if inspections are been carried out and the board is not properly

trained there may be false fails on the board.

Format

no-results_in_softstop %d

where %d1 can be set to 1 to enable this functionality or 0 to disable this functionality.

e.g., no-results_in_softstop 1

33. OCR

Function

This line allows the user to enable the “optical character recognition” functionality on

the GS-1. (see Release notes 1.31 b).

The user should download Release 1.31 b or greater of the code and copy the file

nn_ocr.default.txt (contact MVT for this file) into the directory C:\cpi\data\ocr.

Format

OCR %d

Set %d to 1 to enable the OCR functionality.

To disable this functionality set %d to 0, delete this line, or comment out the line.

Example

The following line in the config.txt will enable the OCR functionality

OCR 1


______________________________________________________________________________________________________________DOC- 5000-0072 32

34. Only_one

Function

If this functionality is enabled only one component, which is automatically centered

in the field of view, will be inspected. This increases measurement accuracy but

significantly increases inspection time because only one component will be inspected

in each camera view. This will not take effect until after the CAD is remade.

Format

Only_one %d

where % d can be set to 1 to enable this functionality or 0 to disable this functionality.

Use

To enable this functionality enter the line " Only_one 1" in the config.txt and save the

changes. Then reload the cpi sofware and remake the CAD.

Setting %d to 0 in the config.txt file and remaking the CAD will return the system to

normal inspection mode in which there are multiple components inspected in a field

of view.

Note: This functionality is useful for the fiducial inspection plate. It can also be

achieved by re-naming the file oo_xxxx.plx

35. outgoing_disk_cad

Function

This config.txt entry was initially devised for development of the cpi code but has

never been used and has no function. Through an oversight this line has never been

deleted from the standard config.txt file that is shipped on all new machines. It is

likely that this config.txt line will be present in most config.txt files but it has no

function and can be deleted.

Format

outgoing_disk_cad %s

where %s specifies the location of the outgoing disk CAD

e.g., outgoing_disk_cad a:


______________________________________________________________________________________________________________DOC- 5000-0072 33

36. placement

Function

This specifies the CAD conversion mode that is to be used by the GS-1s internal CAD

converter. Specifically, this determines the CAD conversion mode used when

the "F4 : Create Board Template" option is selected from the Engineering menu.

However this option is no longer favored by MVT as numerous standalone converters

exist.

Format

placement %s

where %s represents the type of placement CAD that is used. The following options

are valid:

Sanyo, Fuji, MultiFuji, Panasonic, Paragon, Generic.

Use

Integrating with windows NT

The cad conversion program should be placed in the c:\cpi directory, along with a

batch file to call it. The batch file should be called generic.bat and it should contain a

line like the one shown below;

perl converter.perl %1

This tells the system to use the perl interpreter to process the CAD conversion file

called converter.perl, and to pass the first command line argument to it. The first

command line argument will be the name of the CAD file to be converted.

In order for this to work, the perl interpreter executable and associated dll file

(perl100.dll) should both be present somewhere on the system that is accessible

through the PATH environment variable. The recommended place is in the C:\winnt

directory.

To check whether perl is present on the machine, type

perl -v

This runs the perl interpreter and tells it to output its version number. Preferably

version 5.00 or greater should be used, and the version supplied with the GNU tools

(version 4.00 should be deleted), since version 5.00 has a number of very useful extra

commands.


______________________________________________________________________________________________________________DOC- 5000-0072 34

The GS-1 inspection software needs a bit of configuration to ensure it works correctly

with the conversion program. This is done in the config.txt file. The following lines

should be set correctly, as shown;

placement generic

file_extension .xxx

- where .xxx is the correct file extension for the source cad file (eg. .txt or .cad)

Once this has been set up, the system can be used to convert files as follows;

Copy the source cad file into the system’s C:\cpi\cad directory

In the GS-1 Engineering menu, select "F4: Create New Board Template" from CAD

This will bring up a list of the files in the cad directory whose extension matches that

set in the config.txt file. Once a file is selected, the external program will be called

and it will process the file.

Validating Conversion

Place a 1 after the CAD converter type in the config.txt line e.g. Sanyo1, Generic1.

The view file will be automatically compared with the *.plx file and any missing

components will be appended to a file called missing_names.txt in the C:\cpi\log

directory.

37. Printer_level

Function

This functionality allows the user to call an external program after an inspection and

pass it a file called "error_ticket" as an input. This external program can be any MS

DOS program developed by the user, such as a results processing program or a

program for grouping rep files. The only limitation is that the file "error ticket" must

be used as the raw input information for the program.

Parameters explained

Printer_level %d1 %d2

%d can be set to either 2 or 4.

¾ %d1:

a Set to 2 to have the program "error_proc.bat" called after every inspection

and use the file called "error_ticket" as input.


______________________________________________________________________________________________________________DOC- 5000-0072 35

a Set to 4 to call the program "output_proc" every nth inspection.

¾ %d2 specifies the value of n (above). Therefore set %d2 to 3 to have the

program "output_proc" called after every third inspection has finished.

Example

¾ e.g. Printer_level 4 2

Use

The external program called "error_proc" must be written by the user. This program

can be written in any text based package such as Notepad but must be saved as a *.bat

file. Once the program has been written "error_proc.bat" must be saved into the

C:/cpi/ directory.

38. pyramid_data

Function

This config.txt line enables pyramid file processing and allows the user to specify

various options relating to the manner in which these files are processed.

Pyramid files are output files in which data is saved in a file in the same format at

three different levels: per board, per placement machine and per feeder. The three

levels form a pyramid with the board at the top, hence the name. The idea is that you

can use the files to write result analysis tools easily and at several different levels with

the same software. The output processing might include report generation, out of

control alarming, or results charting.

Format

pyramid_data %d 1%d2 %d3 %d4 %s

¾ Set %d1

a to 0 to disable pyramid processing.

a to 1 to perform pyramid processing.

a to 2 to perform pyramid processing on a per component type basis.

a to 4 to perform pyramid processing on a per Part Number basis.


______________________________________________________________________________________________________________DOC- 5000-0072 36

¾ %d2 allows the user to specify that a pyramid file should be written every

nth board where %d2 is the value "n". The default value of %d2 is 10.

¾ %d3 allows the user to wrap the pyramid files after every N boards where N

is the value %d3. The default value is 5,120.

¾ %d4: This allows the user to specify that a pyramid file should be written

every %d4 minutes. The default value is 0, which specifies that a pyramid

file is not to written based on time but rather on number of boards

inspected.If this paramater is to be used then a typical time is 15 minutes.

¾ %s: This optional parameter allows the user to enter a command that will be

executed after every pyramid file is written.

Example

pyramid_data 1 10 5120 0

39. retry_fiducial

Function

This enables the system to retry fiducial 1 inspection until the image is stable. This

should improve load/unload R&R tests when there is no clamping (Release 1.31 for

the GS-1).

Format

retry_fiducial %d1 %d2

¾ %d1 is a fiducial position offset threshold in microns.The difference

between the fiducial position calculated on reinspection and the previously

calculated fiducial position must be less than this threshold for the fiducial

inspection to pass.

¾ %d2 specifies the maximum number of times that fiducial re-inspection can

be carried out. This ensures that the user does not have to go on retrying

fiducial inspection if, for example, the fiducials were faulty. The default

values for this parameter is 10 for the GS-1.


______________________________________________________________________________________________________________DOC- 5000-0072 37

Example

retry_fiducial 10

40. Reverse_plc

Function

This is used in situations where the repair station is before the inspection station. Input

this line into the config.txt file to reverse the boards back down the conveyor to the

repair station after board defects are detected during inspection.

Format

Reverse _plc %d

Set %d to 1 to enable this functionality.

To disable this functionality, set %d to 0,delete the line, or comment out the line.

e.g., Reverse_plc 1

41. Rotate_cad

Function

This can be used to automatically rotate the CAD by 90 or 180 degrees upon loading.

This may be required if the board is to be loaded into the conveyor in a different

orientation to the one in which it was programmed. However MVT recommends that

the CAD be changed manually in the *.plx file instead of using this functionality.

Format

Rotate_cad %d

where %d is an integer with values in degrees of 90 or 180

e.g., Rotate_cad 90

42. rows

Function

This informs the inspection station of the maximum number of components possible

in the plx file.


______________________________________________________________________________________________________________DOC- 5000-0072 38

Example

rows %d

where %d is the maximum number of components possible in the plx file. This has an

acceptable range of 3,000 to 30,000. The default value is 5,000.

e.g. rows 5000

43. Scroll_errors

Function

This functionality for the SJ-10 allows the user to have the last 24 lines of the

errors.log file displayed in a new console window on screen once errors are detected

on the board. This enables the user to obtain useful information about the type of

errors the board is failing for at a glance.

Format

Scroll_errors %d

where %d is 1 to enable this functionality or 0 to disable it.

Example

Scroll_errors 1

44. skew_display

Function

This allows the user to set various parameters relating to the display of board skew on

the graphical results display that is shown on the graphics monitor after each

inspection.

Format

skew_display %d1 %d2 %d3 %d4

¾ Set %d1 to 1 to display the skew mean and sigma on the bullseye chart. If

%d1 is set to 0 then the skew mean and sigma are not displayed on the

bullseye chart.

¾ %d2 should be left at 0.


______________________________________________________________________________________________________________DOC- 5000-0072 39

¾ %d3 is used to specify whether skew will be displayed to a10th of a degree

or to a100th of a degree precision by setting 10 or 100, respectively. The

default value is 10.

¾ Set %d4 to 1 so that the fiducial skew offset is subtracted from the current

skew.

Example

skew_display 1 0 10 0

45. skip_delete_allow

Function

This optional functionality allows users to delete a skip file whenever the *.plx file is

loaded. This gives the user the opportunity to fully control what is being inspected.

Format

skip_delete_allow %d

where %d is 1 or 0 to enable or disable this functionality respectively.

e,g, skip_delete_allow 1

Use

Once enabled, the user will be prompted with the option to delete a skip file whenever

a *.plx file is loaded. This will happen on startup or after pressing the "F3: Set PCB

type" key in the main user menu. This functionality is disabled by default.

46. Sweet_spot

Function

This optional functionality specifies that only components within a certain percentage

of the field of view are to be displayed in the Bullseye chart and reported in the *.cmp

files. This does not make a significant difference to accuracy and it is not

recommended that this functionality be used.

Format

Sweet _spot %d


______________________________________________________________________________________________________________DOC- 5000-0072 40

This optional functionality specifies that only components within a certain percentage

of the field of view are to be displayed in the Bullseye chart and reported in the *.cmp

files. This percentage is set by the user as follows:

(%d x %d)/100 = percentage of the field of view to be used.

Therefore if %d is set to 90 then the percentage of the field of view to be used is:

(90 x 90)/100 = 81%.

If %d is set to 0 (default value) then all of the field of view is used.

Example

Sweet_spot 0

47. two_lines

Function

This is a mandatory config.txt entry only for dual rail inspection stations. It also

informs the code whether barcodes are being used by the system.

Format

two_lines %d1 %d2 %c

where %d1 sets whether the system is a single or dual rail inspection system.

¾ %d1:

a Set %d1 to 0 if the system is a single rail system.

a Set %d1 to 1 if the system is a dual rail system.

a Set %d1 to 3 if the system is a dual rail system and if there is a separate

repair station on each rail. This will generate separate log files for each

rail; namely, errors1.log for rail 1 and errors2.log for rail 2. These separate

log files are required by the 2 Repair stations.

¾ %d2 sets the number of barcode readers on the system. The maximum

number is 4 but typically there is 1.

¾ %d3 is the character of the lowest barcode line and must always be left at 0.

Example

two_lines 0 1 0


______________________________________________________________________________________________________________DOC- 5000-0072 41

48. VScale

Function

This config.txt entry is used to inform the MVT inspection station whether the XY

table's X or Y axis carries the most physical weight .The purpose of this is to bias the

XY table's movements and accelerations in the axis that carries the least weight in

order to optimize the view path. For the GS-1 this is the Y axis (standard XY axes

coordinate framework). For the older developmental MMS systems the X axis carries

the least weight. Typically this line is not included in the config.txt because by default

the GS-1 is biased towards the Y axis.

Format

Vscale %d

where %d is 15 for GS-1, SP-1, and SJ-10 inspection systems

where % d is 7 for the old MMS systems.

The following example shows the config.txt line for the MMS systems:

Vscale 7

49. Width_adjustThis enables the functionality of the Automatic Width Adjust System, which is used

to automatically adjust the rail width to suit the different type of boards used in

production.

Format

Width adjust %d

where %d is an integer with values 1 or 0 to enable or disable this functionality,

respectively.

e.g., Width_adjust 1

50. want_compressed

Function

This useful config.txt entry controls various options relating to the writing of

compressed result files (*.cmp files) to the C:\cpi\res directory. These files are

currently used for charting and alarms programs and as a statistical summarizer.


______________________________________________________________________________________________________________DOC- 5000-0072 42

Format

want compressed %d1 %d2 %d3 %d4

¾ %d1:

a if set to 0 then no cmp files are written to the res directory

a if set to 1 then *.cmp files will be written for every board inspected.

Therefore if the board name is "star1.plx" then the file "star1.cmp" will be

written to the res directory.

a if set to 2 then *.cmp files will be written for every placement machine

and every board after each inspection. If you are inspecting the file

star1.plx and have the placement machines cp1, cp2 and ip3 placing

components then the system will write the following into the res directory:

startac1.cmp, startac1.cp1.cmp, startac1.cp2.cmp and startac1.ip3.cmp,

a if set to 4 then the file "overall.cmp" will be written to the res directory in

addition to the 2 above options (setting %d1 to 1 and 2). Therfore for a

board named star.plx with a feeder named cp1 the following cmp files will

be written to the res directory "overall.cmp", "star.cmp" and

"star.cp1.cmp"

Note: The file overall.cmp (from mode 4) is useful when you are changing

boards a lot and want to see how the machine has been performing at a

glance. In particular it is useful if you perform a pi test and you can then

compare the results

a if set to 8 then the Overall.cmp file, the "board name.cmp" and the

"machine name.cmp" files will be written to the res directory. Therefore

for a board named star.plx with a feeder named cp1 the following cmp

files will be written to the res directory "overall.cmp", "star.cmp" and

"cp1.cmp." The mode 8 files are named after the placement machines

only. Thus, no matter what mix of boards you are putting through, you

keep the data for a single placement machine together.

¾ %d2 is the value n where a cmp file is written every nth board. The default

value is 1.


______________________________________________________________________________________________________________DOC- 5000-0072 43

¾ %d3 tells the system to wrap the *.rep files after N number of boards where

%d3 is the value N. Typically this value N is set to 512 but values up to

5,120 are acceptable. Wrapping means that once up to 512 rep files are

written then the next rep file will overwrite the first rep file and so on.

¾ %d4 specifies where the "Last_rep" file is to be written.

a set %d4 to 1 to write the last_rep_file.txt file in the cpi/log directory

a set %d4 to 2 to write the last_rep_file.txt file in the C:/tmp directory

a set %d4 to 3 (default) to write the last_rep_file.txt in both of the above

directories.

DO NOT SET %d4 to 0 or the system will crash

Example

As a general rule, you should set the want_compressed flag to 2 in the file

data\config.txt. The default values for the other parameters will be automatically used

if there is no value entered for these.

e.g. want_compressed 2

51. xytable

Function

This specifies whether the MVT inspection station is an actual inspection machine or

an offline software package.

Format

xytable %d

where %d is 1 for a real GS-1 (default setting) and 0 for the offline software.

e.g., xytable 1

52. yx_mode

Function

The system currently reports measurements in the X and Y directions according to the

camera orientation of the MVT's inspection station. This can be confusing for users

whose X and Y axes directions differ from our systems.


______________________________________________________________________________________________________________DOC- 5000-0072 44

This config.txt line allows the user to rotate the axes to a more standard configuration.

This can cause confusion as it has knock-on effects on X & Y dimensions in many

system files. The figure below shows current default coordinate system.

Default MVT coordinate axes setup Standard coordinate axes setup

Format

yx_mode %d

¾ %d

a Set to 0 to disable this functionality:

a Set %d to 1 so that our axes are rotated to the standard configuration used

by most placement machines.

a Set %d to 2 switch the sign of the Y-axis only, insert the line

a Set %d to 4 switch the sign of the X-axis only, insert the line

Example

yx_mode 1

Caution

This can cause much confusion as it has knock-on effects on X & Y dimensions in

many system files. The affected files are the rep files, the errors.log file, charting, the

*.cmp files, the *.cpk files, the *.plx files, and the Bullyseye chart. If % d is set to 1 so

that the axes are switched to the standard configuration used by most placement

machines then the following occurs:

rep_files -X and Y are switched, Y is negative

errors.log - X and Y are switched, Y is negative

Charting - X and Y are switched, Y is negative

.cmp files - Y is negative

.cpk files- No change

.plx files- No change


______________________________________________________________________________________________________________DOC- 5000-0072 45

Bullseye chart Y is negative

53. Zimage

Function

This optional config.txt entry controls various options relating to the graphical display

of the board layout. This includes the board charting display that is shown

immediately after an inspection and the graphic display obtained by typing "B" from

the XY Table menu.

Format

Zimage %d1 %d2 %d3%d4%d5

¾ %d1 is used by the cpi code and must always be set to 1.

¾ %d2 can be used to rotate the orientation of the graphics display to how it is

loaded in the xy table.

a Set this to 0 so that the Board graphic view is displayed in the same

orientation as the camera view of the board is displayed on the monitor.

This orientation is at 90 dgrees counterclockwise ti how the board is

actually clamped in the xy table.

a Set this to 1 so that the Board graphic view is displayed in the orientation

in which it is clamped in the xy table (default setting).

¾ Setting %d3 to 1 renders components in the board charting display (shown

immediately after an inspection) as solid color boxes and not merely color

boundaries (boxes with no internal color). This can help highlight the error

code associated with smaller components that may be difficult to otherwise

see. By default %d3 is set to 0 so that components are rendered as color

boundary boxes with no internal color fill.

¾ %d4 sets the radius in microns of the bullseye chart that is displayed in the

board charting display immediately after an inspection. By default this is set

to 150 microns. However users may wish to set this larger or smaller as they

see fit.

¾ %d5 is the maximum number of errors that can be written into the log file

after each inspection. This ensures that an excessive number of entries are


______________________________________________________________________________________________________________DOC- 5000-0072 46

not written to this file The default value is 30 but the user may wish to set

this to a lower value.

Example

Zimage 1 1 0 150 30

Documents

Customer Config txt - Keysight · Format: The config.txt file has a set format with each line of the file containing a word and data sets separated by a keyboard space. Config.txt