4002720-En Software Manual Tpsys 3.3 English A
4002720-En Software Manual Tpsys 3.3 English A
4002720-En Software Manual Tpsys 3.3 English A
3
Software Manual
Original Instructions
English
TPSys™ 3.3
Software Manual
Original Instructions
English
This document is applicable to the TPSys running the TPSys software version 3.3.
A standard system and available options are covered by this document. Depending on your system configuration you may lack some
of the features mentioned in the document.
Disclaimer
Hardware and software mentioned in this document are subjected to continuous development and improvement. Consequently,
there may be minor discrepancies between the information in the document and the performance or design of the product.
Specifications, dimensions and other statements mentioned in this document are subject to changes without prior notice.
Federal Communications Commission (FCC)
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a
commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in
a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own
expense.
Mycronic Technologies AB and its suppliers shall not be liable for any damages related to this software or hardware, or for any other damages whatsoever caused by the
use of or inability to use any Mycronic Technologies AB product. This is applicable even if Mycronic Technologies AB has been advised of the damage risk. Under any
circumstances, Mycronic Technologies AB’s entire liability shall be limited to replace such defective software or hardware that was originally purchased from
Mycronic Technologies AB.
Mycronic, MYDATA, MYDATA automation and MY; MY100, MY100DX, MY100SX, MY100LX, MY100e, MY100HXe, MY100DXe, MY100SXe, MY100LXe,
MY200, MY200HX, MY200DX, MY200SX, MY200LX, MY500, MY600, MY600JD, MY600JP, MY600JP and MYSynergy; T3, T4, T5 and T6; HYDRA
Speedmount, Midas, ISIC; Agilis, Agilis Linear Magazine (ALM), Agilis Linear Magazine Flex (ALM FLEX), Agilis Stick Magazine (ASM), Agilis Tray Magazine
(ATM), Mycronic Tray Exchanger (TEX), Mycronic Tape Magazine (TM), Mycronic Tray Wagon Magazine (TWM); Mycronic Dip Unit (DPU); Mycronic SMD
Tower; Mycronic Standard Vision System (SVS), Mycronic Dual Vision System (DVS), Mycronic Linescan Vision System (LVS), Mycronic HYDRA Vision System
(HVS); Mycronic Assembly Process Management (APM) including; JPSys, TPSys, MYLabel, MYPlan, MYCenter, MYTrace, MYCam, FlowLine and Cad Conversion
are registered trademarks or trademarks of Mycronic AB. Mycronic is ISO 9001:2008 certified. Other trademarks mentioned in this document are trademarks or
registered trademarks of their respective owners.
Table of Contents
New Features Overview ................................................................................................... -xii
• This version of the manual has been updated with the new Agilis™Tray
Magazine (ATM). When both a TEX Tray Exchanger and an ATM is
mentioned, the term 'tray exchanger' will be used.
• Chapter 3, TPSys has been expanded with the following ATM information:
– Added similar info for ATM as for TEX.
• Appendix A – Messages Reference Guide has been expanded with the
following ATM information.
– The ATM has no removable covers.
– Message added: For an ATM: The fiducials on the pallet have not
been located for this ATM in this magazine slot.
– Only TEX has a barcode scanner. The ATM has no barcode scanner.
– For ATMs:
- Electrical problem on the CAN bus.
- The CMOT board in the ATM is broken.
– For ATMs: The CMOT may be broken.
– For ATM: The ATM unit must be disconnected and removed from the
slot before the pallet can be removed.
– Added - a fourth object, the ATM.
– Generic description modified to 'Pallet name'.
– Added ASTM and N pallets.
– Serial number and type code (X02) has been modified.
• Appendix D – Import/Export Data Formats has been expanded with the
ODDSHAPE type.
– R12 fiducial-mark type has been updated.
– R24 taught has been added.
– R25 xstartcoord ystartcoord xendcoord yendcoord has been added.
Text Conventions
This document uses text conventions to present information in various
situations. This is explained below.
Danger
Warning
Caution
Note, example 1
Note, example 2
One type of assisting information is tips, which normally have this icon.
Italic Font
Italic font is used for software screen text (for example Parameter 1), names
(for example Spare Parts Catalog), and for warning text (described in the
previous section).
Bold Font
Bold font is used for particular important words (for example, This must not
be done in reverse order).
Menu Selections
When describing software handling, menu selections are described in the
following format:
File > Page Setup > Paper Size > Portrait > OK
This example describes to open the File menu and select the Page Setup,
Paper Size, and Portrait options, and finally click the OK button.
Lists
Lists of items, points to consider, or procedures that have no relative order
appear in bulleted or hyphenated format like this:
• Item 1.
• Item 2.
or
– Item 1.
– Item 2.
Procedures that must be performed in a specific order appear in numbered lists
like this:
1. Software Overview
This chapter contains a brief overview of software used to run Mycronic pick
and place machines.
Linux
The operating system used in the Mycronic pick and place machines is Linux.
Linux
TPSys
TPSys is a Mycronic developed software for controlling all types of Mycronic
placement machines. TPSys controls all systems and supports all Mycronic
optional systems.
To be able to use some of the optional software in TPSys, the machine requires
magic word and magic time word. Magic word and magic time word are
TPSys
simply passwords that are entered into TPSys to enable the feature.
Service Program
A service program is integrated with TPSys software and is used for
installation, some types of calibrations, troubleshooting and fault finding.
Besides the service program, there is a set of software tools that are activated
from the Linux prompt and used for troubleshooting and fault finding. The
most useful of these software tools are:
Service programs
• Burnin test.
• X axis calibration (for older MY9–MY19 machines).
The service program is described in the service manual.
Software Solutions
Mycronic provides supplementary software that facilitates the programming
work in TPSys.
MYCam
MYCam is a separate Mycronic software package for a standard PC.
Data Sharing
This TPSys feature is used to connect several machines to the same database
in order to share data. The same kind of data can thus be stored and edited in
one database only.
• Component data.
MYCenter
MYPlan
MYPlan is a Windows-based software developed for scheduling board
assemblies in Mycronic placement machines. The purpose of the software is
MYPlan™ 4.X to provide the operator with appropriate loading instructions to increase the
User’s Manual
placement machine performance. MYPlan calculates the best possible
solution to place the components under certain circumstances.
MYLabel
MYLabel keeps track of component carriers (tapes, sticks) used in production
by using barcodes. MYLabel uses an identification barcode linked to a
database with component names, quantities, and batch information. The
MYLabel database also contains component information, such as stock location and
User’s Manual
MYLabel¥ 5.1
owner.
MYTrace
MYTrace is Windows-based software, developed primarily for tracing
defective components mounted by pick and place machines. MYTrace
MYTrace™ 1.1 consists of two applications, MYTrace Harvester and MYTrace Viewer.
User’s Manual
FlowLine
FlowLine is a is a software package which is used to keep the switch over time
for an automated production line to a minimum. This is done by automatically
FlowLine™ 4.4 issuing work orders to machines in the production line, when a board
User’s Manual magazine is inserted into a loader, the line.keeps track of component carriers
(tapes, sticks) used in production by using barcodes.
2. Linux
This chapter describes briefly Linux operating system.
The most important functions of Linux operating system, and for TPSys 3.3
Linux usage of Linux, are listed below and described in the following sections:
• Linux Kernel.
• Users and Root.
• Drivers
• Files and Directories.
• USB Flash Drives.
• The 'bash' Program.
• Standard I/O.
• Process Environment and Symbols.
• Symbolic Links.
• Pipes
• The 'proc' File System.
• Common Linux Commands and Utilities.
• Shutdown
Linux Kernel
The main part of Linux system is Linux kernel, which is the program that starts
when Linux is booted. The term ’boot’ means to load and initialize the
operating system on a computer.
Linux kernel provides, among other things, the following:
• A file system.
• A time sharing system for parallel processing.
• A method to start programs (processes).
• Device drivers for hardware interface.
• Basic security such as user identification, file ownership and access
privileges.
• A configurable initialization procedure.
Programs are stored as files in the Linux file system. Once a program is started
it becomes a Linux process. There may be more than one process that run the
same program.
In this chapter programs means programs stored in the file system and
processes means Linux processes.
The configurable initialization procedure normally starts a number of
processes. Some of these processes start logon sessions on the terminal lines.
A logon session is a program that waits for a user to type a user name and,
optionally, a password.
In the TPSys system a user named tpsys (lower case) with password mydata
(lower case) is created at installation.
Drivers
Linux is designed to be run on any type of hardware. This means that the Linux
kernel must be configured for all types of hardware platforms. This is achieved
by using drivers, which are portions of code written to access specific
hardware. Drivers are loaded into the Linux kernel. If a new type of hardware
is connected, a new Linux driver has to be installed in the Linux kernel to
access this hardware.
Important Files
This is a short list of especially important files in Linux:
/etc/inittab
This file is read at the initialization. This file is generated automatically
and it contains information about automatic logon etc. When TPSys is
installed, it modifies this file to automatically log on tpsys to tty1.
/etc/passwd
This file contains information about all users in the system. When TPSys
is installed, tpsys and tpspool are added as new users in this file.
/usr/share/terminfo
This file contains information about all terminal types known in the
system. The terminal types are stored under a sub-directory with an one-
character name that is equal to the first character in the terminal type
name, for instance ’vt100’ is found under
/usr/lib/terminfo/v/vt100.
In addition to the system terminal settings, TPSys also uses local terminal
settings stored in the directory /home/tpsys/.terminfo.
.profile
If this file is present in the home directory, it is executed at logon (similar
to AUTOEXEC.BAT in MS-DOS). TPSys uses this file to start the system
when ’tpsys’ is logged on to tty1.
Important Directories
This is a short list of especially important directories in Linux:
/bin
A directory in which most of Linux standard program files are stored.
/dev
A directory in which all devices appear. Devices are treated as files in
Linux.
When inserting a USB flash drive in a USB port, TPSys will automatically
mount it as a disk on /mnt/usbX, where X is 0, 1, 2 or 3. TPSys will use the
first unused directory. The TPSys message log will show the disk name for the
USB flash drive.
To copy a file from the current directory to a USB flash drive mounted as
’/mnt/usb0’, type the following at Linux prompt:
cp filename.txt /mnt/usb0/filename.txt
The USB flash drive is mounted asynchronously, which means that
copying a file to a USB flash drive will go through the usual Linux disk
buffers before actually stored on the stick. When using the USB flash
drive from the Linux prompt, it is therefore important to run the command
sync at the command prompt, before removing the flash drive. This
ensures that all files are physically stored on the USB flash drive.
Therefore type the following at the Linux prompt before removing the USB
flash drive:
sync
When using the USB flash drive within TPSys application, for instance to
store backups, exports, and save statuses, the USB flash drive is
automatically synchronized.
The system is only designed for flash type of USB memory modules with
FAT32 file system. It may not work correctly with USB hard disks or USB CD
burners.
If bash is typed (lower case) at the command prompt, then another shell starts
as a child-process to the first shell.
Standard I/O
A Linux process will have at least one input and two output channels. The
channels are referred to as I/O-streams.
The input stream is referred to as ’stdin’ (standard in). Standard in is typically
the keyboard.
The two output streams are referred to as ’stdout’ (standard out) and ’stderr’
(standard error). Standard out is the normal program output and is typically the
monitor. Standard error is reserved for error reports and is typically the
monitor. These streams can be redirected by using the command line interface.
To redirect standard in from a file, enter:
command <filename
The process started by command will now read its standard input from the
filename file.
To redirect standard out to a file, enter:
command >filename
The output to standard out from the process started by command will now
be written into the filename file. If the filename file already exists, then it
will be replaced.
To redirect standard error to a file, enter:
command 2>filename
The output to standard error from the process started by command will
now be written into the filename file. If the filename file already exists,
then it will be replaced.
If double brackets (>>) are used instead of a single bracket (>) in the
redirection command, then the data will be appended to the file.
A process can create and read its own symbols but most of the symbols are
normally inherited from the parent in Linux. If a process starts another
process, the started process is referred to as the child process and the starting
process is referred to as the parent process. The purpose of symbols is to be
able to define a symbol that contains for instance a file name. If the file name
is changed there is no need to change it in the program because it uses the
symbol and the symbol is easy to change.
export SYMBOL
To show the value of a symbol in the shell, enter:
echo $SYMBOL
The $ sign informs the shell that the symbol name is to be translated.
The set command prints a list of all symbols.
Symbolic Links
In Linux, symbolic links are used. A symbolic link is a file that points to
another file. The symbolic link has its own inode number but appears as the
file it points to, when used in commands.
A symbolic link is created by giving the -s switch to the ln command like this:
ln -s afile alink
Pipes
In Linux the output of one process is often used as input to another. This is
realized with a pipe from the first process to the second. To pipe the output
from command1 to command2, enter:
command1|command2
Special Characters
There are a few special characters that are not interpreted as arguments to the
command. Useful for service purposes may be:
>
Direct output to a file.
>>
Appends output to end of a file.
|
Pipes output to another command.
Example 1 ls > myfile
Creates a file named myfile and prints the result of the directory listing
into it.
Example 2 ls -l >> myfile
Appends a new long format listing to the end of myfile.
Wild Cards
?
A question mark indicates a character (anyone).
*
An asterisk indicates any number of any characters.
Command Descriptions
This section contains a list of the most commonly used Linux commands with
syntax and examples. The command selection, the descriptions and the
examples refer to the TPSys usage for the Mycronic placement machines.
For further information about the commands, enter the man command for the
desired command, for example man cat.
Example:
cat lib/params/axis
The axis file is printed on the monitor.
cd – Change directory
Changes to the indicated directory.
Syntax:
cd [path]
Example:
cd lib/params
Moves to the ’params’ directory.
Example:
Note! space period period cd ..
Moves to the lib parent directory.
Example:
cd
Moves to the ’tpsys’ home directory.
cp – Copy
The contents of the source file is transferred to the copied file.
Syntax:
cp sourcefile newfile
Example:
cp lib/params/axis testdir
The axis file is copied to the testdir directory.
Example:
cp lib/params/axis testdir/axiscopy
The axis file is copied as axiscopy to the testdir directory.
diff – Difference
Compares two files and shows the differences.
Syntax:
diff [-b] file1 file2 [or dir1 dir2]
-b
Ignore end spaces.
-b Ignore end spaces.
Example:
diff lib/par-tp9/caxis lib/params/caxis > cdiff
Creates the cdiff file in the tpsys directory containing the differences
between the default file /home/tpsys/lib/par-tp9/caxis and the
used file /home/tpsys/lib/params/caxis.
Example:
dmesg|less
All messages are printed on the monitor.
emacs filename
Some of the most common emacs functions are found below.
Function Command
Open file <Ctrl> + X <Ctrl> + F
Save file <Ctrl> + X <Ctrl> + S
Save as <Ctrl> + X <Ctrl> + W
Exit <Ctrl> + X <Ctrl> + C
Erase <Del> or <Backspace>
Move Arrow keys, <PageUp>, <PageDown>
Abort command <Ctrl> + G, sometimes repeated.
Find <Ctrl> + S
Find and Replace <Alt> + %
Mark text <Ctrl> + <Space> and then move using the arrow keys.
Cut <Ctrl> + W
Copy <Alt> + W
Paste <Ctrl> + Y
Example:
fdformat /dev/fd0H1440
Formats the floppy disk as follows:
/dev Device
fd Floppy disk.
0 Drive A.
In TPSys 3.3 the following two devices can be used when formatting floppy
disks:
Example:
fdformat /dev/fd0def
The floppy is formatted to its size automatically.
Example:
fsck -y /dev/sda1...sda(n)
Result:
The system runs a manual file system check and automatically repairs any
inconsistencies. If you issue the fsck command during computer startup,
you may need to type exit to continue the startup procedure after the file
system check.
Alternatively, you can issue the command without the -y switch.
fsck device
The system will now prompt you for every inconsistency found. Answer
Y to all questions to make a repair.
If the manual file system check (fsck) fails to repair the file system, this
may indicate a hard disk problem.
A common cause for automatic file system check during startup is that the
computer has been powered off before it has finished its shutdown procedure.
When an application writes to a file in Linux the file will, for performance
reasons, not actually be written to the hard disk but stored in memory until the
system finds some more suitable time to write it.
When you shut down Linux, it will first ensure that all files are actually written
to disk and then tell you to turn power off.
Example:
grep speedScale lib/params/caxis
Result:
I speedScale: 320 E 7 32768 0
This line in the caxis file has a matching word.
Example:
cat lib/params/mountComp | less
The mountComp file is shown. Press <Space> to proceed page-wise, or
use the arrow keys to move up or down in the file.
Example:
less lib/params/mountComp
Simplified way to enter the same command.
ls – List
Lists the files in the directory. By default in alphabetical order.
Syntax:
ls [-CF] [-l] [-i] [-a] [directory]
Example:
ls
Files in the current directory is listed in alphabetical order, except files
that start with a period (.).
Example:
ls -l lib
Files in the lib directory are listed in long format.
Example:
ls -i file1 file2
Reveals if two file names are linked to the same file.
Syntax:
man <command>
Example:
man ls
A help file for the ls command is shown on the monitor. To return to the
Linux prompt after viewing, press Q.
Example:
mcopy myfile A:
The myfile file is copied to a DOS disk in drive A.
Example:
mcopy * A:
All files in the current directory (maximum eight characters, see below)
are copied to a DOS disk in drive A.
Example:
mcopy LongFileName A:longfile
The LongFileName file in the current directory is copied as LONGFILE
to a DOS disk in drive A.
Example:
mcopy A:mountcom NewMount
The mountcom file in the A drive is copied to the current directory in
Linux as the NewMount file.
Only files with maximum eight characters in the file name can be copied to a
DOS disk. Rename the files as shown in the second last example if the file
names are longer than eight characters.
Example:
mdir A:
The files are listed on the monitor.
Syntax:
mformat drive
Example:
mformat a:
Low-level formats a DOS disk in drive A.
Example:
mkdir testdir
A new directory named /home/tpsys/testdir is created.
mv – Move, rename
Moves/renames files. Note that existing files may be overwritten.
Syntax:
mv path1 path2
Example:
Note! space and period. mv testdir/axiscopy
The axiscopy file is moved to the tpsys directory.
Example:
mv axiscopy testdir
The axiscopy file is moved back to the testdir directory. If the
testdir directory does not exist, then the file is renamed to testdir.
Example:
mv testdir/axiscopy testdir/newname
The axiscopy file is renamed to newname.
Example:
pwd
Current directory path is shown.
rm – Remove file
Removes indicated files.
Syntax:
rm [-i] file [file...]
-i Interactive confirmation (y) for each file to be deleted.
Example:
rm -i testdir/newname
The newname file in the testdir directory is deleted.
Example:
rm -i testdir/*
All files in the testdir directory are deleted.
Example:
rmdir testdir
The testdir directory is removed, if empty.
Example:
sync
If you have save the archive with the tar command, you need to use the tar
command also to extract or restore files.
Syntax:
tar [cvf] [xvf] [tvf] file
cvf Writes.
xvf Reads.
tvf Lists.
Example:
tar cvf /dev/fd0 filename
Writes to disk in drive A.
Example:
tar xvf /dev/fd0 filename
Reads from disk in drive A.
Example:
tar tvf /dev/fd0 filename
Lists content in archive in drive A.
Example:
top
Shows CPU and memory usage.
Example:
tty
Current terminal path and name is shown, for example /dev/tty3.
Example:
vi
Starts the editor. The most important commands for simple editing are
listed in the following table.
who – Which terminals are used, and which users are logged on
Responds the terminal names that are currently used.
Syntax:
who
Example:
who
Responds all invoked terminals, for example tty1, tty2, tty8.
Shutdown
Never reset the computer on the machine computer box, or turn the power off
before you have shut down the Linux system.
Shut down the Linux system from the command line by entering the following
command:
halt
You can safely turn off the power after the following message:
System halted - press Ctrl-Alt-Del to reboot
Rebooting
If you want to reboot the system, enter the following command:
su -c reboot
3. TPSys
This chapter describes TPSys software, which is developed by Mycronic and
used to control all the Mycronic placement machines.
This chapter contains information about how to modify parameters. Note that
most of the system parameters must be changed by authorized Mycronic
service engineers only.
Introduction
This chapter contains for example information about how to handle and
navigate in TPSys software, some useful settings and hang-up instructions.
The contents is divided into the following sections:
Virtual Terminals
A terminal, monitor and keyboard, on a machine, running TPSys, can operate
up to seven virtual terminals, in other words up to seven independent Linux
terminal processes can be used from the machine terminal.
Virtual terminal 1.
This terminal is used to run TPSys online. TPSys is set up to start
automatically on this terminal. This is set up in /etc/inittab and
/home/tpsys/.profile.
Virtual terminal 2.
This terminal is used for the TPSys web interface if TPSys runs in high
resolution mode. If high resolution is not available, this terminal is the same
as virtual terminal 3 below.
Virtual terminal 3.
This terminal can be used to run TPSys offline, for example for programming
purposes.
Virtual terminal 4.
Same as virtual terminal 3.
Virtual terminal 5.
Same as virtual terminal 3.
Virtual terminal 6.
Same as virtual terminal 3.
Virtual terminal 8.
This terminal is used as console for system messages.
To switch between the terminals, press <Alt> + <F#>, where # is the number
of the desired terminal.
Example:
<Alt> + <F2> switches to virtual terminal 2.
Login Instructions
Linux allows you to login to the system in the following two different levels:
'tpsys'
The ’tpsys’ login level is used for the following purposes:
Press <Space> if you want to access the startup menu. Otherwise, a hardware
initiation dialog box is shown. After initiation, TPSys main menu is shown.
Starting TPSys If you have exited to Linux from TPSys, restart TPSys by typing go at the
prompt.
For advanced users, you can instead type exit or press <Ctrl> + D at the
prompt. This restarts the terminal and then starts TPSys.
Linux operation
Login as tpsys followed by password mydata on either of the tty3 to tty6
terminals. These terminals can be used for offline purposes.
System supervision
Terminal tty8 is automatically selected as console and reports process
information without being logged on.
'root'
The highest logon level is ’root’. In most systems ’root’ is protected with a
password, accessible to a system administrator only as a super-user. However,
TPSys is an open system in which no password is required to log on as ’root’.
Do not log on to ’root’ level unless you are very familiar with the system, and
have specific reason to do so.
To log on the ’root’ level, type su at the prompt (su does not need a password).
Hang-Up
This section describes what to do if you get a terminal hang-up or a system
hang-up.
Terminal Hang-Up
If a terminal does not respond to key pressing, kill the current process as
follows:
System Hang-Up
If no terminal responds to any key pressing, then you have a system hang-up.
CAUTION! Never press the reset button on the computer box after the
operating system has been booted.
Setting Time
The system clock on the computer motherboard indicates current time to
various processes in the system. This section shows how to set this clock.
1. Exit TPSys by selecting Exit > Exit TPSys in the main menu.
2. Enter the following commands at the prompt.
su
/home/tpsys/etc
./timeconfig = time zone
./timesetup = time
A popup box will inform you that the system needs to be rebooted.
3. Reboot the system to make the changes to take affect by selecting Yes in
the popup box.
NTP Setup
Setup of a Network Time Protocol server:
Example:
serial -n
Prints the machine number on the monitor.
Example:
serial -a
Prints the machine name on the monitor.
Example:
serial -m
Prints the machine model and serial number on the monitor.
The machine name, number, and available options are also shown if selecting
About... > This Machine in the TPSys main menu.
Time Lock
The Time lock feature makes it possible for Mycronic to allow each
installation of TPSys to function for a limited period. Only authorized
Mycronic representatives may modify the parameters specifying this period.
When the time lock is activated, the machine will not be able to mount any
components, but other functionality is undisturbed.
Parameters
Parameters involved:
241.0001 Time Lock magic word.
241.0011 Time Lock Details; Infinite time.
241.0012 Time Lock Details; End year.
241.0013 Time Lock Details; End month.
241.0014 Time Lock Details; End day.
The date given by the above parameters is the date upon which the lock will
be activated unless the infinite time parameter is set to ’TRUE’ and the magic
word is valid.
TPSys
Starts TPSys.
Parameters
A program for setting parameters during installation and service without
initiating the machine.
Service
A service program for test of various functions. For further information see the
service manual.
Show Transducers
A position program for installation and service.
Backup
A backup tool for TPSys databases, parameters and calibration. For further
information, see Chapter 6
Restore
A restore tool for TPSys databases backed up with the Backup tool. For further
information, see Chapter 6.
UNIX
Moves to the Linux prompt ($). To restart TPSys in Linux, type exit at the
prompt and press <Enter>.
Software Upgrade
A program for upgrading TPSys with software patches from the CD-ROM unit
or USB.
Measure TEX
A service program for reinstallation of the TEX.
Measure ATM
A service program for reinstallation of the ATM.
System shutdown
Shutdown command to exit both TPSys and Linux.
System reboot
Shutdown and restart command for TPSys and Linux. TPSys is then
automatically restarted.
Line Configurator
A program for line configuration for usage with the Line Mode functionality.
The line configuration command is started by typing lineConfig at the unix
prompt.
To understand the directory tree in Linux you first have to understand the use
of symbolic links. Symbolic links are described on page 2-6.
The home directory for tpsys is /home/tpsys, for usage in scripts the symbol
BASE is defined.
/home/tpsys is a symbolic link to the directory that holds the current TPSys
version.
magazines
DB init board
tmp
/home/tpsys/lib/language/english
English text files for TPSys screen and web interface.
/home/tpsys/lib/language/french ... german
Text files in various languages for TPSys screen and web interface.
/home/tpsys/lib/mot1
This directory contains MOT servo files.
/home/tpsys/lib/par-XXXX
Default parameter files for the machine type (XXXX = machine type).
/home/tpsys/lib/params
This directory is created during TPSys installation. It contains individually
calibrated parameter files for the machine.
/home/Backup
This directory is the default directory for backups
/home/tpsys/lib/DB/init/...
This directory includes subdirectories for different data types
Offline Terminal
In TPSys, terminals tty3 to tty6 can, after logging on as tpsys, be used as
TPSys offline terminals by entering the following command:
go
In addition to the virtual terminals, a standard PC can be used as an external
TPSys offline terminal (further described in the service manual). The optional
MYPlan software also contains an offline terminal.
TPSys offline terminals do not slow down the machine performance because
online processes have higher priority than offline processes.
TPSys offline menu is reduced in comparison to TPSys online menu, for
instance the Production menu is not shown.
Stepper Feature
The machine in its natural state runs at full speed. When doing diagnostic
work, you may need a way to run the machine slower so that you can follow
the machine movements better.
The Stepper feature slows down these machine movements and is suitable for
troubleshooting.
For instance, assume that a component drops off between picking and placing.
Due to the fast machine movements it is difficult to see where in the sequence
the component falls off. By stepping through the machine movements, it is
easier to see when the component falls off. When the exact cause is known, it
is easier to take corrective action, for instance slow down the acceleration of
that axis.
– Single stepping.
– Continuous slow running.
If the user access system is in operation, the user currently logged in must have
Service field in the Users window set to High.
You can run the Stepper in continuous mode and then press <F7/Front> to
switch to single step mode.
Although you can use the Stepper without looking at the internal system
messages, they can be helpful for troubleshooting.
Take the following two messages as an example.
Tx:MOV y pos: 519876um prec: 1 acc: 0 mode: 00 id: 160546
Headlines
--- Z Center right ---
This type of message works as a header for a block of messages related to a
certain task.
Note that other messages may be in between the matching pair of ’Tx’ and
’Rx’. You need to look at the ’id:’ fields, see below, to pair them up.
Servo commands
Some of the more useful servo commands are listed below.
MOV; MOVNICE; MOVSLOWMOV
An instruction to move an axis to a position.
HYDRAFLASH
An instruction to flash with a HYDRA camera or a Linescan camera.
MOVIND, MOVSEND; MOVINVDVVACWAIT
An instruction to move an axis until the axis meets resistance, for instance
move the vertical axis (z) until the spring-loaded tool hits the board.
READPOS
An instruction to read the encoder position for an axis. The reply comes
promptly.
WAITPOS
An instruction to read the encoder position for an axis. The reply comes when
the axis has reached the target position.
Axes
X, Z, HZ, C, Fi, HFi
The different axes on the X wagon. If the machine has two X wagons, these
axes refer to the right X wagon.
x2, z2, hz2, c2, fi2, hfi2
These axes are only present on a machine with two X wagons, and refer to the
left X wagon.
Y, conh, cont, conw
The different axes on the board handling system.
Status codes
status: 0
The servo computer reports that all went well.
status: xxxxx
For certain commands MOVIND, MOVSEND; MOVINVDVVACWAIT the status
field will contain a value between 1 and 15 when returned. This is normal.
If the status field contains a value above 15, it is generally an error code.
Axis positions
pos:
The information following after this contains the axis encoder coordinate in
internal units, for instance micrometers or millidegrees. Note that some axes
go backwards.
Message identifiers
id:
Each transmitted command has a unique identifier, last on the line. There will
come a reply message with the same unique identifier further down in the
Stepper window.
Message color
White If a message is displayed in white, it contains either a response
to a given command, or an internal communication message.
Yellow If a message is displayed in yellow, then the message is next
in line to be sent when you press <F7/Front>.
1. Select Exit > Shutdown in TPSys main menu or in the Startup program
menu.
2. Select Yes to power down the system.
3. The power can be turned off when this message is shown:
System halted
Users Window
In TPSys there is a user security feature in which passwords are used to
prevent from unauthorized data modification. User names, passwords and
individual data modification privileges are used for this feature.
Disabled any user can modify the security information without logging
on.
Enabled the user must be logged on with the User privilege level set to
High.
The currently logged on user name is shown at the bottom of the screen.
It is not possible to lock the system for all users by manipulating the security
feature. However, in a network system with shared User database, the client
system might be locked, if manipulating the user privilege levels and the log
on/off feature in the client and server systems. But, a locked client system can
always be accessed again by changing the User privilege level in the server
system.
The Users window is opened by selecting Edit > Users in the main menu.
Command Keys
All available commands for the Users window are found in the upper-right
area of the window.
Commands that are common in the TPSys interface are described in the
operator’s manual.
Commands that are specific to the Users window are listed below.
F2 – Change password
The password for the highlighted user can be changed after pressing <F2>.
Passwords are sensitive to upper/lower case.
Names
This list contains the users defined in the system.
Use the arrow keys or <PgUp>, <PgDn>, <Home>, or <End> to select user.
* A user currently logged on is marked with an asterisk (*). Only one user can
be logged on to the system in online mode. Several users can, however, be
logged on to the system in offline mode.
Data
Name
User name, which must be a unique name for each user.
Access rights
Privilege levels for the highlighted user can be set individually for a number
of system actions, further described below.
High and Low privilege levels can be chosen for most of the actions. For some
of the actions, an additional Standard privilege level can be selected.
The three privilege levels are intended for the following purposes:
Low Intended for minimal trained operators and allows to run the
system, locate boards and re-load components, but it does not
allow to change any settings.
Standard Intended for trained operators and allows to modify the
contents of the magazines, and to modify board positions in
panels.
High Intended for programmers and service personnel and has no
limitations, in other words any placement and system settings
can be changed.
Actions allowed for the three privilege levels are described below. Standard
points out only what is allowed in addition to the Low level. High is not
included since it has no limitations.
Layout – Low
Boards in Layout window – Move the board position fiducial marks.
Board – Low
PCBs window – Toggle the ’D’ and ’M’ status in the Items list.
– All actions in the View position mode except for changing the
component position.
Board – Standard
PCBs window – Modify the component angle, position and local fiducial mark
positions.
– Modify the following data:
Bad board mark position
Mount tool test position
Glue tool test position
Panels window – Move the PCB position fiducial marks.
– Modify the following panel header information:
Bad board mark position
Mount tool test position
Glue tool test position
Component – Low
Components window – No modification is allowed, but the F6 Search magazines feature can
be used.
Package – Low
Packages window – No modification is allowed.
Glue dot – Low
Glue Dots window – No modification is allowed, but you can apply and view a glue dot
using the Apply and view option in the menu.
Fiducial marks – Low
Fiducial Marks window – No modification is allowed but you can verify a fiducial mark using
the Test mark option in the menu.
Magazine – Low
Magazines window – Perform the following magazine actions:
Locate magazine.
Step ASM/VM magazine.
Step all ASM/VM magazines.
YWM Trays window – Perform the following actions:
TWM Trays window
TEX Trays window Refill tray.
Remove from magazine.
– Modify the following tray information:
Quantity
Position
TEX Units window – Perform the following actions:
Locate TEX pallet.
Refill all trays.
Magazine – Standard
Magazines window – Modify all feeder contents information accessed by selecting the Edit
feeder contents option in the menu.
YWM Trays window – Perform the following actions:
TWM Trays window
TEX Trays window Add tray.
Delete tray.
Toggle sort order.
– Modify the tray information, for example Name/barcode, Comment,
and Batch ID.
Magazine Kits window – Apply a magazine kit.
Tray type – Low
Tray Types window – No modification is allowed.
Magazine kit – Low
Magazine Kits window – No modification is allowed, but you can change the sort order by
selecting the Toggle sort order option in the menu.
User – Low
Users window – No modification is allowed, neither of any user privileges nor
passwords.
To avoid the risk of locking everyone out from the system, the currently
logged on user cannot set his own User level to Low.
Switches – Low
– No modification is allowed of the switches accessed by selecting
Production > Switches in the main menu.
Mount/glue switch – Low
– No modification is allowed of the mount and glue switches accessed
by selecting Production > Mount/Glue Switches in the main menu.
Parameter – Low
Parameters window – No modification is allowed of the parameters accessed by selecting
Edit > Parameters in the main menu.
Schedule Backup – No access is given to the Schedule Backup feature in the Utility menu.
Service – Low
Service tools – No access is given to the Installation and Calibration and Diagnostics
service tools in the Utility menu.
Management – Low
If this field is set to Low then the following actions are, contrary to the
above descriptions, NOT allowed to be performed:
– Clear the event log (the Clear Event Log option in the Utility menu).
– Clear management data (the Clear Management Data option in the
Production menu).
– Delete management data (the Delete Management Data option in the
Utility menu).
Interface
This field controls if the full TPSys menu is shown or if the menu is reduced.
The reduced menu is quicker to learn, and could, for instance, be used for
newly trained operators.
– Minimal
A reduced menu is shown.
– Standard
A full menu is shown.
Security On/Off
The security can be switched on/off from the TPSys main menu in online
mode, provided the User privilege level is set to High for the currently logged
on user.
Log On/Off
How to log on and log off is described in the operator's manual.
Preferences
If you want to select preferences for the web interface, for instance language
and units, select Set Preferences in the web interface main menu.
For data such as PCBs, you also get inconsistency checks, for instance if a
component is referring to a package that does not exist in the library.
Note that no editing of assembly data can be made in the web interface.
This part of the web interface is further detailed in the programming manual.
The report is highly configurable. For instance, you can generate a report for
a specific layout or for a given time period. You can sort the results in several
ways, and you can choose the level of detail in the report.
Active time
The time a layout has been loaded in TPSys.
Runtime
The time the machine has mounted components. Note that fiducial mark
search time and board change time is not included. Run time will therefore
never become 100% of Active time. Run time will not include boards where
the assembly has been interrupted and never finished.
PCBs
The number of produced PCBs (one row per PCB if Show PCB list was
selected during configuration).
Parts
The number of mounted components.
You can select a certain layout or all layouts, and the time period. Depending
on the settings in the window, the information can for example include
assembly time in seconds, the time spent on fiducial search time and, time
waiting for boards.
The data is extracted from the event log.
One use of this feature is to see if a given layout runs faster or slower after a
’tweak’.
– Summary report
A report with summary statistics is generated for the selected layouts.
This implies that the mean, minimum and maximum values for each
measurement are calculated and displayed.
– Full report
The report will display the data for each board that has been produced.
For Machine
Generates a report for a specific machine or for all the machines in a network.
For Layout
Produces a report for a layout or layouts. This could be all the layouts that have
been produced, or a subset of the layouts produced. It is possible to select an
arbitrary subset by holding down the <Ctrl> key and selecting with the mouse.
Start time
Selects the start time of the time span that the report shall be generated for.
End time
Selects the end time of the time span that the report shall be generated for.
Layout
The name of the produced layout.
Batch
The batch of the produced layout.
Start assembly
The start time of the report.
Automatic fiducial mark search time
The time spent on automatic fiducial mark search.
Manual fiducial mark search time
The time spent on manual fiducial mark search.
Z tool change time
Time spent by the single mount head on tool changes.
Total time
The total production time including the time spent for board change.
Net throughput
The net throughput, NTP, is defined as follows:
Z-mounted components
The number of components mounted with the single mount head.
HYDRA mounted components
The number of components mounted with the HYDRA mount head.
Mounted components
The total number of mounted components.
Rejected components
The number of faulty components that have been rejected.
Printing
Printers cannot be connected to a machine running TPSys 3.0, or later. It is,
however, possible to print by connecting to the TPSys web interface from an
office PC that has a printer configured and using the printer functions/reports.
The images taken by the vision systems in the machine contain much
information that is useful for troubleshooting.
The system can be set to automatically save images taken during vision
centering, during fiducial mark search and when magazines are located. The
web interface can then be used for browsing and analyzing these images, and
if needed, to download them to an office computer. The images can also be
sent to Mycronic for further analysis.
The Save image when vision failed and the Save all images settings will make
the machine run slower. Therefore, remember to switch back to Off after
finished troubleshooting.
1. Select Service Tools > Image Log in the TPSys web interface. This
opens a thumbnail view of the images in the image log, as shown in
Figure 3-4.
– Browse through the image gallery by clicking View next page ...or
View previous page ...
1. Select which images to download using the check boxes next to each
image. If desired, you can select all images with the Select All button.
2. Click on Save selected images. The system will now collect all necessary
files and create a compressed archive.
3. Select to save the compressed archive as a file.
4. If requested, send the downloaded file to Mycronic support, where it will
be analyzed further. The file contains all data required to re-create the
situation when the images were taken. This makes it possible to use these
images for detailed analysis, and to improve future versions of the vision
software.
Such a system termination can be caused by a software error. If you answer ’y’
to this question, the system will collect various system files that Mycronic
support needs to troubleshoot the error.
For this purpose, the save status program can be started by selecting Utility >
Save System Status in TPSys.
Parameters
Parameters are used to configure TPSys. As an example, you can configure
how the system should behave if a feeder runs out of components.
Parameter Structure
The TPSys parameters form a structure with the following two levels:
1. Parameter group.
The first level contains parameter groups, for example 21 Z-mount
component.
2. Parameter
The second level consists of specific parameters, which are briefly
described on page 3-33. A comprehensive description of the parameters
are found in Appendix B.
Command Keys
All available commands for the Parameters window are found in the upper-
right area of the window.
Commands that are common in the TPSys interface are described in the
operator’s manual.
Commands that are specific to the Parameters window are listed below.
Parameter Groups
This box contains all the parameter groups (for instance 22 Z vacuum).
Use the arrow keys or <PgUp>, <PgDn>, <Home>, or <End> to select the
desired parameter group.
You can also select a parameter group by simply entering the first characters
of the parameter group name.
Editing Parameters
Note that most of the system parameters must be changed by authorized
Mycronic service engineers only. A password may be required to save
modifications made in parameters.
An adequate access level is required to change parameter data. Each user can
be set to a personal password and individual access level. Further information
about user access is found on page 3-18.
1. Press <Enter> when a parameter group is highlighted to open up another
window where editing of the individual parameters is made.
2. Change the desired parameter by entering a new value or toggling
another option as described in the information line at the lower left box
border.
Note that minimum and maximum values shown in this information line
are not always adequate to the capacity of the machine but more of
mathematical limitations.
3. To save the changes, move the cursor to the Save and exit field and press
<Enter>. A Password may be required.
To exit without saving, press <Esc> instead.
Taking effect
Most of the parameters take effect immediately after modification.
Some parameters require a system restart to take effect. If such parameters are
changed, the system will inform that a system restart is required.
• Parameter password.
• Parameter file location.
• Parameter backup.
• Units and ticks.
Password
Password for parameters accessed either by selecting Edit > Parameters in the
main menu, or selecting the Parameters option in the startup menu is ’anders’
(lower case). This password is stored in the 'directory.PW' file in the
/home/tpsys/lib/params directory. The password can be changed or
deleted. A deleted password means that no password is required.
File Location
Parameter groups used by the system are stored in the following directory:
/home/tpsys/lib/params
If you modify a parameter using the Parameters window, you change a
file stored in this directory.
If a parameter group is copied (in Linux) from:
/home/tpsys/lib/par-XXXX
to:
/home/tpsys/lib/params
then included parameters are set to the default values.
Some of the parameters are measured and set to individualized values during
installation and commissioning. Such parameters should not be copied.
Backup
A backup should be taken before a parameter that controls an essential
function is modified, see Chapter 6 for information regarding backup.
Units
The following metric units are used in the TPSys parameters:
Ticks
The word ’tick’ is common in some of the parameters. It signifies one step
from a digital incremental transducer.
Sometimes you may need to remove all data from one or all databases, for
instance if the machine has been used in another facility before, or used during
training.
You can remove all data types except event log data with this method, using
the reference table below.
cd lib/DB/init
psql -U postgres -d mydata_common_db < createDB.sql
cd
cd lib/DefData
import *.pck
cd
You can import the following data types with this method, using the reference
table below.
This documentation assumes all the local area network hardware is already
installed. For further information about hardware installation, see the
corresponding service manual.
Network Configuration
To ensure that the server and the clients are able to communicate over the
network, the network has to be configured.
1. Exit TPSys.
2. Type netsetup at the Linux prompt., and press <Enter>. The Main
dialog appears.
3. Select Netsetup, and OK.
4. Select one of these network configuration methods:
– DHCP client: Select if the machine/server is connected to a network
with a DHCP server. The machine will get its network settings from
the DHCP server, and its IP address dynamically. Go to step 6.
– Fixed IP: Select if the machine/server is connected to a network, and
the machine/server should have static network parameters. Go to
step 5.
– No network: Select if all network functions for the machine/server is
turned off, or if the machine/server is not connected to a network. Go
to step 6.
Example:
The file /etc/hosts can look like this before editing:
127.0.0.1 localhost
192.168.1.32 my100-14n1234 my100-14n1234.company.com
Retain the first line (127...) and the current machine’s data in the file.
1. First check that the host names are working by pinging. Example:
ping myserver
or like this:
--- myserver.mydata.se ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
Each machine or server has an FTP server running. the network can be used to
transfer files. This can be done either from the machine or server (Linux) or
from a Windows computer on the network. Both procedures are described
below.
-u – This flag tells the command that the next string is a user name.
<user> – The user name on the remote computer
<hostname> – The host name or IP address of the remote computer.
4. The FTP program will then prompt you for the password on the remote
computer. Enter the password to connect to the other computer.
5. Change directory on the remote computer until you are in the folder
where the file to transfer is located. To change directory, use the
command cd.
6. Enter the following command to transfer the file to the machine/server.
get <file>
<file> – The name of the file that you want to transfer from the
remote computer.
7. When the transfer is completed, exit the FTP program by giving the
command exit.
-u – This flag tells the command that the next string is a user name.
<user> – The user name on the remote computer.
<hostname> – The host name or IP address of the remote computer.
4. The FTP program will then prompt you for the password on the remote
computer. Enter the password to connect to the other computer.
5. Change directory on the remote computer until you are in the folder
where you want to put the file. To change directory, use the command
cd.
6. Enter the following command to transfer the file to the remote computer.
put <file>
<file> – The name of the file that you want to transfer to the remote
computer.
7. When the transfer is completed, exit the FTP program by giving the
command exit.
A readily available FTP program is the one built into Windows Explorer.
Simply type ’ftp://tpsys@’ followed by the IP address or host name in the
Windows Explorer address field. Example:
ftp://tpsys@my12n678
From here you will access files and folders that are located in the
machine/server’s /home/tpsys directory. Files can be copied, pasted,
dragged and dropped using standard Windows features.
5. Data Sharing
This chapter describes the general structure of TPSys database, and how it is
operating when several machines in a network share a database and data in the
database.
TPSys Databases
The following sections describe how TPSys data is stored in its database,
especially if there are several machines connected in a network.
If you have two machines in the network, one of the machines can act as a
server.
If you have more than two machines in the network, a stand-alone server is
required.
The following pages explains schematically how the database is structured and
linked to a machine in some common cases.
Single Machine
A single machine without a server, and without any network connection to
other machines, stores its data in a database on the local machine’s hard disk.
The data in the database is divided into a private area that only this machine
can use, and a shared area that can be used by any machine in the network. In
case of a single machine, or a single machine connected in a network, it does
not matter which data area is used.
The data in the database is divided into a private area to each machine and to
a shared area that can be used by any of the machines.
The data in the database is divided into a private area to each machine and to
a shared area that can be used by any machine in the network.
Data Areas
As described above, the database keeps the data in one or several private areas
and in a shared area. All data areas are stored in the same database, on the
server on the network. Figure 5-1 illustrates the data areas.
A private area is specific for a certain machine in the network. The other
machines in the network can not see this data, and cannot use it. For instance,
if a machine stores its package data in its private area, this package data can
only be used by this machine.
The shared area is available for all machines in the network. All machines can
see and use the data. For instance, package data stored in the shared area, can
be seen, used and changed by any machine.
Data Types
The database keeps different types of data for example component and
package data. Figure 5-1 illustrates the data types that can be shared.
my100-14n1234 my100-14n5678
my100-14n1234
Private area
my100-14n5678 TPSys
Private area server
Shared area
Component data
Package data
Mount data
Magazine data
TWM/YWM tray data
User data
Figure 5-1. A network with two machines and a standalone server. To the left, the different data areas
are indicated. The different data types are illustrated as vertical segments.
The default setting is that all machines have all their data of all data types in
the shared area, as illustrated by the dots in Figure 5-1 above.
It is possible to configure the system so that a machine store some or all of its
data in its private area. Data in the private area can only be seen and used by
the machine that owns it. Figure 5-2 shows an example where two machines
store most of their data in the shared area, for instance the component and
mount data, but the package data is private to each machine.
my100-14n1234 my100-14n5678
my100-14n1234
Private area
my100-14n5678 TPSys
Private area server
Shared area
Component data
Package data
Mount data
Magazine data
TWM/YWM tray data
User data
Figure 5-2. Data sharing where both machines store most of their data in the shared area, but the
package data is stored in their respective private areas.
my100-14n1234 my100-14n5678
my100-14n1234
Private area
my100-14n5678 TPSys
Private area server
Shared area
Component data
Package data
Backup for machine
my100-14n5678 Mount data
Magazine data
TWM/YWM tray data
User data
Figure 5-3. Backup of data taken from machine ’my100-14n5678’ will contain all private data from all
machines and all data from the shared area.
Even if the server holds the database, the backups should always be taken on
all the machines in the network including the standalone database server. The
backup on the machine will include parameters and calibration data. A backup
on a server will not include these data types.
Event log
Event log data is always private to the machine. Event log data is stored on the
machine’s hard disk if there is no network. Event log data is stored on the
server if the machine is linked to the server.
Parameters
Parameters are stored on the machine’s hard disk. This is regardless of the data
sharing settings.
Calibration data
Calibration data are stored on the machine’s hard disk. This is regardless of the
data sharing settings.
Database Copies
The system has an integrated fallback method that makes it possible to keep
production running despite temporary network problems.
The system can be configured to regularly make exact copies of the server’s
database and place them on each machine in the network.
These database copies are not used during normal production, but in case of
network problems, they can be activated, so that production can continue even
though the network connection to the server fails.
These copies are refreshed at regular intervals. Any information that has been
added, changed or deleted from the server will then be added, changed or
deleted from the copy on each machine.
These copies should not be used as data backup, since data that is deleted from
the server by mistake will also be deleted from the copies, next time a
scheduled refresh is made. Ensure that the system has normal backup
procedures according to Chapter 6.
The copies will contain all data in the main database, with the exception of
event log data.
It is also explained how to configure data that should be available for all
machines, and data that should be private to each machine. The default setting
is that all machines in the network share all types of data.
Preparations
1. If you are upgrading from a version lower than TPSys 3.3 and want to
keep the data sharing settings, take note of the 181 Network parameter
settings before upgrading. The upgrade will not transfer those settings
automatically.
2. Make sure that TPSys 3.3 is installed on all machines and on the server.
See TPSys 3.3 installation guide and TPSys 1.x & 2.x to TPSys 3.3
upgrade guide.
3. Check that all machines and the server run exactly the same version of
TPSys. To check this, select About... > TPSys on each machine and on
the server to obtain the version number.
4. Check that the network connections work between the server and all
machines and vice versa. Use ’ping’, as described in Chapter 4.
5. Start TPSys on the server and on all machines in the network.
If you want to change private data to shared data this must be done before the
backup is taken using the export/import procedure, see page 5-14.
If a machine stores old data that you want to move to the server, follow the
procedure below for each machine.
CAUTION! Do this backup before linking the client to the server, otherwise
all data may be permanently lost.
The 182 Data sharing settings are by default set to Shared on the server and
cannot be changed.
The copy made to the machine’s hard disk is not used by the system, if the
181.0301 Database connection; Host name parameter points to the server.
The purpose of the copy is to quickly get production up and running if there
are network problems. This is not a backup, so ensure that you take regular
data backups according to Chapter 6.
The settings in the 182 Data sharing parameter group do only refer to the
ownership of the data, not to the storage location. If the 181.0301 Database
connection; Host name parameter points to the server, the data will always be
stored on the server.
Restore Backup
Do not restore the machine configuration, as that would overwrite the data
sharing settings.
When the data sharing parameters are configured, it is time to restore any
previous backup on the machine. Skip these steps if no backup was taken.
Do not restore the whole backup since that would overwrite all existing data.
If you took backups from several machines and want to restore them all, notice
that the last restored backup will overwrite data that was previously restored.
For instance if two backups contain component ’Q123-456’, with different
settings, the last restored backup will decide the settings for that component.
The procedures below describe some of the most common data maintenance
operations.
Disconnecting a Machine
Sometimes it is needed to disconnect a machine from the server, for instance
during server maintenance or during network problems.
If the 181.1002 Refresh; Refresh local data base parameter is set to Yes and
you are sure that you have not changed any data since the last refresh, you can
skip the backup and restore procedures. If so, simply change the 181.0301
Database connection; Host name parameter to ’localhost’ on the machines to
disconnect.
Reconnecting a Machine
When machines in a network have been disconnected from the server, the most
updated information will lie on the machines’ hard disks. The reconnecting
procedure therefore consists of copying the machines’ data to the server, and
to change the 181.0301 Database connection; Host name parameter on the
machines.
If you are sure that you have not changed any data since the machines were
disconnected, you can skip the backup and restore steps. If so, simply change
the 181.0301 Database connection; Host name parameter to the server’s host
name on the machines to reconnect.
Export procedure:
1. Select Utility > Export in the main menu.
2. Select the data type to export.
Shared area
3. Choose Export Channel.
4. Select the items you want to export.
5. Dependant on what data type you want to export a popup box may
appear in order to make you select and confirm an alternative.
6. Select a file name and directory for the selected items.
7. Repeat step 2 to 6 for each data type you want to export and then exit.
Change data sharing settings:
1. Select Edit > Parameters > 182 Data sharing.
2. Set the exported data types to Shared and exit.
Import procedure:
1. Select Utility > Import.
2. Select import format.
3. Choose Import Channel.
4. Select file name and directory for the selected import channel.
5. Select the items you want to import.
6. A popup box appears allowing you to rename the data file or to confirm
the existing file name.
7. Repeat step 2 to 6 for each data type you want to import and then exit.
If you have several machines with private data you want to export to the shared
area, the export/import procedure must be repeated on each machine.
Moving data from the shared area to the private area involves the same steps
as when data is moved from the private area to the shared area. However, the
import needs to be made on each machine, not on the server.
Export procedure:
1. Select Utility > Export in the main menu.
Shared area 2. Select data type to export.
3. Choose Export Channel.
4. Select the items you want to export.
5. Dependant on what data type you want to export a popup box may
appear in order to make you select or confirm an alternative.
6. Select file name and directory for the selected items.
7. Repeat step 2 to 6 for each data type you want to export and then exit.
Change data sharing settings:
1. Select Edit > Parameters > 182 Data sharing.
2. Set the exported data types to Private and exit.
Import procedure:
1. Select Utility > Import.
2. Select import format.
3. Choose Import Channel.
4. Select file name and directory for the selected import channel.
5. Select the items you want to import.
6. A popup box appears allowing you to rename the data file or to confirm
the existing file name.
7. Repeat step 2 to 6 for each data type you want to import and then exit.
The backup/restore feature is used to save and restore the TPSys database and
configuration data.
Each machine in the network, including the standalone database server, must
be backed up.
Note that the backup does not include any barcode translation files.
The backup feature also includes a scheduled backup feature, which is
described on page 6-5.
Backing up
Backup can also be selected in the startup menu which is opened by pressing
<Space> while TPSys is starting.
UNIX/NFS
Select this option if you want the backup to be stored locally on the machine
hard disk or, if NFS (Network Files System) is used, on a hard disk on another
machine in the network.
When the backup is completed, press <Enter> to return to the TPSys main
window.
FTP
Select this option if you want the backup to be stored on a host machine in a
network using the FTP (File Transfer Protocol).
The default information in the dialog box shown can be changed.
Backup name
The name of the backup target file.
The default name is set in the 208.0060 FTP backup data; Backup base
name parameter found in the 208 Backup/Restore parameter group. If
there is no file name in this parameter, then the machine type, number,
date and time form a file name.
Directory name
The destination for the backup target file. The default destination is set in
the 208.0061 FTP backup data; Backup directory parameter.
Host name or IP address
The name of the host machine in the network, or the IP address for
external transfer using the FTP protocol. The default host name or IP
address is set in the 208.0062 FTP backup data; Host name or IP address
parameter.
User name
The user name for logging on to the host system. The default user name
is set in the 208.0063 FTP backup data; User name parameter.
Password
The password for logging on the host system. The default user name is set
in the 208.0064 FTP backup data; Password parameter.
When the FTP backup destination is completely specified, press <Enter> to
start the backup procedure.
When the backup is completed, press <Enter> to return to the TPSys main
window.
Backup name
The name of the backup target file.
The default name is set in the 208.0071 USB backup data; Backup base
name parameter. If there is no file name in this parameter, then the
machine type, number, date and time form a file name.
When the USB backup destination is completely specified, press <Enter> to
start the backup procedure.
When the backup is completed, press <Enter> to return to the TPSys main
window.
Scheduled Backup
TPSys has a scheduled backup feature that can be configured to perform a
backup automatically at a preset time interval.
All entries in the backup configuration box have default parameters in the 208
Backup/Restore parameter group in the same way as described in the previous
section. However, these parameters cannot be modified in the Parameters
window. They only indicate what has been entered in this configuration box.
Directory
The destination of the backup target files.
Directory
The destination for the backup target files.
Host name or IP address
The name or IP address of the host machine in the network.
User name
The user name for logging on to the host system.
User password
The password for logging on the host system.
Time settings Use day of week or date
Press <Space> to select Date or Day of week.
Select Date for backing up the same day or days every month, for instance the
1st and 15th day each month. Select Day of week for backing up the same day
or days every week, for instance every Friday and Tuesday.
Day of week
This option is enabled only if Day of week is selected in the Use day of week
or date field. Press <Ins> and select Every day of week or a specific day, or
several days of the week from the dialog box shown.
Date
This option is enabled only if Date is selected. Press <Ins> and select Every
day or a specific date, or several dates from the menu shown.
Hour
Press <Ins> and select Every hour or a specific hour, or several hours from the
menu shown.
Minute
Type the desired minute value at which you want the backup to start.
Restoring
Restore can also be selected in the startup menu which is opened by pressing
<Space> while TPSys is starting.
2. Select Yes from the pop-up box Exit TPSys to restore. (If No is selected
TPSys returns to the main menu.)
3. Select backup type to restore and press <Enter>.
– Last saved backup
When this option is selected a window appears showing information
about the last backup taken on that machine.
– UNIX/NFS
Select backup file
This option restores a UNIX/NFS backup file stored locally on the
machine hard disk, or if NFS (Network Files System) is used, on
another computer on the network.
Enter the backup and directory name in the dialog box, press <Enter>
and follow the Select items to restore instructions on page 6-7.
– FTP
Select backup file
This option restores a FTP backed up file stored on a host machine in
a network.
Enter the desired data in the dialog box, press <Enter> and follow the
Select items to restore instructions on page 6-7.
– USB flash drive
This option is only available if a USB flash drive is inserted into the
computer.
4. Select items to restore
Highlight the item to restore, press <Enter> and follow the on-screen
instructions.
– Configuration
Select this option to restore the configuration data such as parameter
files and calibration data.
When restoring the configuration data, it is important that the backup was
taken on the same machine that it is restored to.
– Database
This option is only enabled if the backup contains database data.
Select this option to replace the current database with the database in
the backup. All new, not backed up data will be lost.
Exit TPSys and any other Mycronic software on all connected machines when
restoring data on a machine acting as a server.
Restoring specific database items can be done from any machine connected to
the server and does not require exiting TPSys on the other machines.
When TPSys has been installed on the server and a scheduled backup have
been restored, the carrier database will most likely not be up-to-date. To fix
this, the carrier database should be restored from the mirrored carrier
databases on one of the machines that is up-to-date. On the server, do this:
7. Import/Export TPSys
TPSys import feature is used to import data into TPSys databases. Data can be
imported from the machine hard disk, from another machine in a network, or
from floppy disks.
TPSys export feature is used to export data from TPSys databases to the
machine hard disk, to another machine in a network, or to floppy disks.
The import and export features include for example, all the databases used for
TPSys
placing components, handling the user security and, management data.
The import and export features can include all data in a specific database, or
selected items of a specific database.
To import mount data from a CAD system is not described in this manual. This
description can be found in the CADConversion, user’s manual which is
provided with the Mycronic CADConversion software package.
TPSys Format
The TPSys format is an ASCII format, described in Appendix D.
Directline Format
Directline is an old Mycronic proprietary format.
For further information about the Directline format, see separate directline
manual.
Manual Importing
All exported data from a TPSys system, can be imported into the same or
another TPSys system of the same or later version.
Imported items, for instance layouts and PCBs, will keep their names, if not
changed by the user during the import procedure. The item names are not to
be confused with the file names.
Selecting Format
To import data to TPSys databases, do the following:
Selecting Channel
3. Select the desired import channel.
– UNIX/NFS
Select this option to import from the local hard disk or, if NFS
(Network Files System) is used, from another computer in the
network.
The default path is set in the 201.0101 Paths; UNIX parameter.
– FTP
Select this option to import from a host computer in a network or
import via an IP address by using FTP (File Transfer Protocol) format.
The default FTP parameters are set in the 202.0001 Host name,
202.0002 Logon name, 202.0003 Password and 202.0004 Directory
parameters found in 202 FTP transfer parameter group.
– Directline
Select this option to import using Directline format.
This option is only included in the menu if an option with the
Directline format was selected in the Import list (page 7-3).
– USB flash drive
Select this option to import from a USB flash drive. This option is
only included in the menu if a USB flash drive is inserted into the
computer.
The default path is set in the 201.0103 Paths; USB flash drive
parameter.
Selecting Source
4. Enter the file name and path, or press <Enter> and select one or several
files from the list shown:
Select or deselect single files to import by highlighting the file and
pressing <Space>, or press <Ctrl> + A to select all files. Asterisks (*)
indicate selected files in the box.
The file types corresponding to the various databases are found in the
File Extensions parameters in the 201 Import/Export parameter group.
5. When ready, press <Enter>.
You can bypass the overwrite warning by pressing <Space> in the field where
the item name goes, and then pressing <Enter>. This will import all items with
their original names. Any existing items with the same names will be
overwritten without warning.
Automatic Importing
TPSys has an import utility that automatically imports files that is placed in the
assigned import directory in the machine or the server.
Settings
The following parameters control how the automatic import utility operates.
Exporting
To export data from TPSys databases, do the following:
Selecting Channel
4. Select the desired export channel.
– UNIX/NFS
Select this option to export to the local hard disk or, if NFS (Network
Files System) is used, to another computer in the network.
The default path is set in the 201.0101 Paths; UNIX parameter.
– FTP
Select this option to export to a host computer in a network.
The default FTP parameters are set in the 202.0001 Host name,
202.0002 Logon name, 202.0003 Password and 202.0004 Directory
parameters found in the 202 FTP transfer parameter group.
– Directline
Select this option to export using Directline format.
This option is only included in the menu if an option with the
Directline format is selected in the Export list.
– USB flash drive
Select this option to export to a USB flash drive. This option is only
included in the menu if a USB flash drive is inserted into the
computer.
The default path is set in the 201.0103 Paths; USB flash drive
parameter.
Selecting Items
5. Select if you want to export a specific item or all items in the category.
Select or deselect single items by highlighting the item and pressing
<Space>, or press <Ctrl> + A to select all items. Asterisks (*) indicate
selected files in the box.
6. For some categories, you will be prompted to select if you want to export
only the data for the category, or if you want to include underlying data.
– Layout ---------------- TPSys Format
If Export with underlying data is selected, the export will include data
for the layout and data for panels, PCBs and components included in
the layout. However, machine dependent data, for instance package
data, is not included.
– Panel ----------------- TPSys Format
If Export with underlying data is selected, the export will include data
for the panel and data for PCBs and components included in the panel.
However, machine dependent data, for instance package data, is not
included.
– PCB ------------------- TPSys Format
If Export with underlying data is selected, the export will include data
for PCBs and components included in the PCB. However, machine
dependent data, for instance package data, is not included.
– Package --------------- TPSys Format
If Export with underlying data is selected, the export will include data
for the package and data for glue dots included in the package.
Selecting Destination
7. Depending on the selections above, you may be prompted to enter the
destination file name.
8. Press <Enter> to start the export procedure.
When the export procedure is completed, the Export list is shown again.
9. Press <Esc> if you want to return to TPSys main window.
8. Barcode Translation
This chapter explains how TPSys handles barcode strings and how to do
advanced filtering of barcodes for board and component identification.
abc0001:4711:0002 The chapter is divided into the following sections:
• Barcode Systems.
• Serial Start Scanners.
• Handheld Barcode Scanner.
• Regular Expressions.
• Meta Characters.
• Filters.
• Testing the Barcode Translation Filter File.
• Basic Filters Quick Reference.
• Real-Life Filters.
Barcode Systems
The following barcode types can be used in TPSys:
The barcode strings can be very varying. Therefore the standard functions in
TPSys may not be enough to make the system interpret the barcode scan
correctly.
The following sections describe a way to find this unique pattern of a barcode
string and add the appropriate prefix so that TPSys identifies the barcode in the
right way.
Serial start scanners are located on the conveyor that loads boards into the
machine and are used to read layout name and/or PCB ID from board
barcodes.
There can be one or two serial start scanners on the conveyor system; they are
called device A and device B. Both devices are used for scanning layout or
PCB ID barcodes.
The filter file names for device A and device B must be as follows:
/home/tpsys/lib/bcTransSerStartA.dat
/home/tpsys/lib/bcTransSerStartB.dat
TPSys comes with an example filter file. All examples are inactive, in other
words made into comments. The example file has the following name:
/home/tpsys/lib/bcTransExample.dat
The filter file name for layout related data must be as follows:
/home/tpsys/lib/bcTransComponent.dat
The filter file for layout data is the same as the one used for serial start
device A. The layout filter will only be used for the handheld scanner when the
cursor is in the Layout field in the Select Layout box or in the Get ID for PCB
field. When scanning a barcode in general, the component filter will be used.
The X-wagon camera scanner uses a translation filter to read panel or PCB
related data on barcodes.
The filter file name for panel and PCB data to be read by the X-wagon camera
must be as follows:
/home/tpsys/lib/bcTransXWC.dat
TPSys comes with an example filter file. All examples are inactive, in other
words made into comments. The example file has the following name:
/home/tpsys/lib/bcTransExample.dat
1. Grab the hole in the middle of the diffuser (’1’ in the figure below) and
remove it.
2. Gently rotate the transparent pipe (’2’ in the figure below) until the weak
glue that holds it releases and then remove it.
3. Apply black tape around the transparent pipe.
4. Reassemble the transparent pipe and the diffuser.
Figure 8-1.
Regular Expressions
To translate a general barcode to a string recognized by the system, there must
be something that makes the barcode unique. Something called regular
expressions is used to find this unique feature in the barcode.
The fundamental building blocks are the regular expressions that match a
single character or a set or characters. The match is case sensitive by default.
You can match all ASCII characters such as letters, digits and "!#%&$" and
so on. There are also meta characters that can be used to build special matches.
Meta Characters
Most characters simply represent themselves when used in a regular
expression. However, some characters are used for special purposes, for
instance as wild cards. These special characters are called meta characters.
Below are a few of the most common meta characters.
.
Matches any one character.
^
Matches empty string at the beginning of a line.
$
Matches empty string at the end of a line.
It will not find a match in the following string since the expression requires
that there is a "Duck" in the string:
Mickey and Donald
The following examples in this section describe how the regular expression in
the example above can be modified to be more discriminating.
It will not find a match in the following string since the expression requires
that there are no characters before "Duck":
Donald Duck
It will not find a match in the following string since the expression requires
that there are no characters after "Donald":
Donald Duck
It will not find a match in the following strings since the expression requires
that there are no characters before or after "Donald":
Donald Duck
Mickey and Donald
Number of Matches
All characters can be matched a specific number of times. To control the
number of matches, add the meta character or expression below after the
character that you like to match.
*
Matches zero or more times.
?
Matches zero or one time.
+
Matches one or more times.
{n}
Matches n times.
{n,}
Matches n or more times.
{n, m}
Matches at least n but not more than m times.
A common type of match expression is combining a meta character that
controls the type of match (for instance ".") with a meta character that controls
the number of matches (for instance "*").
Note that you need to have the "." character before the "*" character, otherwise
you would search for the string "Donal" followed by zero or more "d"
characters.
It will not match the following strings since the expression requires zero or one
character after "Donal":
Donaldddd
Donald Duck
It will not match the following string since the expression requires at least one
character after "Donal":
Donal
It will not match the following string since the expression requires between
one and six characters after "Donal":
Donald Duckling
Bracket Expressions
There is a way to specify exactly which characters to match with a bracket
expression.
Enclose all characters you like to match with square brackets "[]" and they will
be matched.
For instance, write [abcd] to match any one of those four characters.
Sequences of letters or digits, like A-Z, a-z or 0-9, can also be enclosed with
the square brackets. For instance, write [a-d] to match any of the first four
characters in the english alphabet. The expressions [abcd] and [a-d] are
equivalent.
An alternative method for this case is to use the IGNORECASE line in your
filter file, see page 8-16.
It will not match the following strings since the expression requires one upper-
case or lower-case A to Z or one digit after "Donal":
Donal
Donal+
It will not find matches in the following strings since the expression requires
one upper-case or lower-case A to Z or one digit after "Donal". It also requires
that there are no characters before "Donal" and that there is one, and only one,
character after "Donal".
Donal
Donal+
Dunald Duck
Mickey and Donald
Filters
The expressions explained above are used to create so called filters. Filters are
simply text commands in a text file. This text file is then used by the system to
translate one string to another string.
Use only Roman characters within the expressions; for instance Japanese
characters will not work.
Also note that there is a <Space> separating the two parts of the filter. You
may have as many spaces as you like, or a <Tab>.
When a pattern matches a part of a string, it is replaced by the output from the
match. The entire string does not have to match, it is enough that some part of
the string matches. If a long string is passed through a filter and the filter finds
a match at one part of the string, that part will be translated and the remaining
part of the string will be passed on unchanged.
To match the exact string and nothing else, use "^" at the beginning and "$" at
the end of the pattern.
"^Pattern to match$" "Output from match"
When the pattern does not match there will be no translation of the barcode. It
will be passed on unchanged.
The "Donald" part of the filter is the regular expression containing the pattern
that is searched for. As said above, it has to be placed within double quotation
marks.
The "Duck" part of the filter stands for the string that should replace the string
found by the regular expression. As said above, it has to be placed within
double quotation marks.
Assume you want to make a different filter that changes the string "Donald"
or the string "donald" to "Donald". The filter would look like this:
"[Dd]onald" "Donald"
Assume you want to make a filter that changes the string "donald" to
"Donald". The filter would look like this:
"donald" "Donald"
Assume you want to make a filter that changes the string "Donald" to "Donald
duck", but only if "Donald" are the only characters in the string. The filter
would look like this:
"^Donald$" "Donald Duck"
Multiple Filters
You can have several filters in a filter file. They will be used in the order they
appear in the filter file.
Variables in Filters
The filters above have been quite simple. For practical barcode translation
tasks, you need another tool called variables.
() If a set of characters is enclosed with parentheses, a variable is connected with
the match. This variable can then be used in the output from the match. In the
translated string, the variable will be replaced with the string that matched the
regular expression that the variable matches.
The first variable is called "$1" when it is used in the "Output from match" part
of the filter.
There is also a special variable "$0" that represents the entire string.
Variables: $1 $2 $3
String: abc0001:4711:0002
In a previous section we have described the meaning of the "$" character when
it is used in regular expressions. Note that the "$" character has a different
meaning when it is used in the "Output from match" part of the filter.
The "$" character has a special meaning in the outpart part of the filter. If you
want to actually write the "$" character to the output string, you need to write
"$$". For an example, see page 8-24.
The example below shows how a more useful variable "$1" is created by using
the characters "([Dd])". The string that is matched by the variable is then used
in the output part of the filter.
"([Dd])onald" "$1uck"
The example below uses the variable "$0" that means the whole string.
"([Dd])onald" "$0 $1uck"
The example below shows how one filter can use two variables, "$1" and "$2".
The first variable is the "D" or "d" character at the beginning of the match. The
second variable is the "d" character at the end of the match.
"([Dd])onal(d)" "$1onal....$2"
Greedy Matches
The matches are greedy. This means that the first match will try to match as
much as it can. If there is something left of the string the second match will try
to match as much as it can, and so on. The second match must still match. The
first match can't match the entire string if the second match must match
something.
Greedy matches can be used to create powerful filters, but it requires good
programming skills to get it right.
For barcode translation filters, it is not needed to master this property of
regular expressions. It is mentioned here, since it can cause problems during
troubleshooting.
The second variable above has the following regular expression: "([0-9]+)".
This expression requires at least one digit. Because the first variable is greedy,
it will take everything it can and leave the minimum possible to the second
variable. In this case, the second variable is left with the last of the "2"
characters.
The example below instead uses the "([0-9]{2})" regular expression, to be sure
that it only matches a string with two digits.
"Donald(.*)([0-9]{2})" "DD$1$2"
Case Sensitive
There is a way to control if the matches should be case sensitive or not.
All matches after the following line will be matched not using case sensitive
match:
IGNORECASE
On the other hand, all matches after the following line will be matched using
case sensitive match:
NOIGNORECASE
The "\" indicates that the character following should be treated as a normal
character and not a meta character.
The following characters are meta characters in regular expressions.
. ^ $ * + ? { [ ] \ | ( )
The '.' is a meta character. To make the regular expression correct for this
purpose, simply write "\." instead of "." where the match should be.
"Donald(.*)\." "Donald$1!"
Splitting a String
Certain barcodes, for instance 2D barcodes, can contain information that needs
to be separated before the system can understand it. For instance, a barcode
can contain both the component name and the component batch.
To split a string in two, use the following set of characters in the output string:
\\n
If you are using the serial start feature, you cannot just convert the quantity
information with a filter, the system needs one layout name string for every
single board.
If you make the output string contain the the string below, this will instruct the
system to repeat the remaining characters in the output string as as many times
as specified by the 'nnn' part of this expression.
REPEAT nnn;;;
Comment Lines
A line in the filter file that begins with "#" is not treated as a regular expression
but as a comment. This can be used to describe the pattern with words.
# This line is a comment
More Information
This description of regular expression is not intended to be a complete
description. For more extensive information on regular expressions, search the
Internet.
The program is started from the Linux prompt in the following way:
bcTranslationTest -t filterfile -s "demo0001"
-t – This flag tells the program that the next string is the filter file.
filterfile – Place the name of the filter file here. It can be any name, it does
not have to be the names that the system requires for actual production.
-s – This flag tells the program that the next string is the string to translate.
"demo0001" – Type in the string that you use to test the filter here. You
need to place it within single quotation marks. This string should
represent the string that comes from the barcode scanner.
After pressing <Enter>, the program will try to translate the string and displays
the result of the filtering on the monitor.
– If the filter finds a match, the output will be the translated string.
– If the filter fails to match, the output will be the unchanged string.
If you are working in a temporary filter file, remember to later rename your
filter file to the names used by TPSys, see page 8-2 and .8-3.
If you only type bcTranslationTest at the Linux prompt, the system will
show basic information about the barcode translation test program.
Real-Life Filters
Below are more examples, showing how actual filter files could be designed.
The filter files are plain text files that you create with a regular text editor, and
then place in the location described on page 8-2 and 8-3.
Chapter 2 in this manual describes a simple text editor that you can use directly
in the Linux system.
Once the filter files are in place, they will automatically be used by the system
when a barcode scanner is sending data to TPSys.
As described above, the filter files can have comment lines. Any line in the text
file that starts with a "#" character is interpreted as a comment line.
abc0001:4711:0002
abc0001:4711:0002
IGNORECASE
# This is the
bcTransSerStartA.dat
# filter file.
# it divides one combination
string
# into two separate strings
"(.*):(.*):(.*)" "L$1\\nI$3"
Labc0001
I0002
TPSys
– The first set of "" characters are marking out the regular expression
that is searched for. For further information, see page 8-11.
– The "()" characters are used to create a variable. For further
information, see page 8-14. This variable is needed, since it will be
used in the output part of the filter. Since there is only on set of "()"
characters, this is the first and only variable defined in this filter.
– The ".*" meta characters defines the pattern that is searched for. In
this case, the pattern is any string of characters with zero or more
characters. For further information, see page 8-7.
– The second set of "" characters are marking out the output from the
filter. For further information, see page 8-11.
– The "L" means that L will be placed first in the output string if the
pattern above finds a match. For further information, see page 8-14.
– The "$1" characters define that the string found in the first variable,
see above, should be added to the output string directly after the "L".
For further information, see page 8-14.
The table below shows how this example translates various strings:
This is a rudimentary filter file. It will put an "L" in front of any string that is
passed through the filter file. Although it works in many cases, the examples
below show how more competent filter files can be built, for more demanding
situations.
The filter is similar to the one in Example 22 – Adding a prefix to a string, but
the "." meta character is replaced with "[0-9]" to limit the matching to only
digits. For further information, see page 8-9.
The table below shows how this example translates various strings:
The filter is similar to the one in Example 23 – Adding a prefix to a string with
digits, but the "^" and "$" meta characters are added to limit the matching to
strings containing only digits. For further information, see page 8-6.
The table below shows how this example translates various strings:
Note that TPSys has a number of prefixes defined in the 123 Barcode
parameter group. The filter file therefore starts with regular expressions that
match strings with such prefixes and pass them on unchanged. The filter file
ends with a filter that adds a "C" to any string that is not matched by the
previous filters.
Pass on barcodes with any of "^C(.*)$" "C$1"
the following prefixes "^B(.*)$" "B$1"
unchanged: "C", "B", "QT", "^QT(.*)$" "QT$1"
"T+", "FD", "S%", "L%", "AN", "^T\+(.*)$" "T\+$1"
"!", "@", "$", "+" and "T%" "^FD(.*)$" "FD$1"
unchanged.
"^S%(.*)$" "S%$1"
"^L%(.*)$" "L%$1"
"^AN(.*)$" "AN$1"
"^!(.*)$" "!$1"
"^@(.*)$" "@$1"
Note that '$$$1" means first a "^\$(.*)$" "$$$1"
"$" character, then variable "^\+(.*)$" "+$1"
"$1". "^T%(.*)$" "T%$1"
#
#
#
Add a component prefix (C) to "(.*)" "C$1"
any other barcode.
The table below shows how this filter file translates various strings:
Another filter file in machine 2 should append "_2" to all layout barcodes
scanned by that machine.
These filter files should also add an "L" as a prefix, just like in Example 22 –
Adding a prefix to a string.
"(.*)" "L$1_1"
"(.*)" "L$1_2"
If your barcode on the boards already contains the prefix L, simply skip the
corresponding L in the filter files.
Note that this filter file only works correctly if the layout section only contains
letters and the PCB-id section only contains digits.
The table below shows how this example translates various strings:
The table below shows how this example translates various strings:
Component name string. The "(.{7})" characters matches the 7 characters forming the component
name. Since parentheses "()" are used, this becomes variable "$1".
The "(.*)" characters matches the characters coming after the 7 first ones.
Since parentheses "()" are used, this becomes variable "$2". Since this part of
the string is irrelevant information, it will not be used in the output part of the
filter. The filter would work exactly the same if you used ".*" instead of "(.*)".
The "C$1" characters are used to write a "C" and then the 7 component name
characters from variable "$1" to the string sent to TPSys.
The table below shows how this example translates various strings:
The simple filter above will do the job in most cases, but is has the downside
of finding matches also if there are other characters such as "-" among the first
seven characters.
This alternative filter only translates the string if all first seven characters are
either digits, a-z or A-Z. It may be a better option if you have several filters in
your filter file.
– The first set of "" characters are marking out the regular expression
that is searched for. For further information, see page 8-11.
– The ".{3}" characters matches the first three characters in the string.
Since they will not be used in the output, they do not need to be made
into a variable. For further information, see page 8-11 and page 8-14.
Component name string. – The "(.{10})" characters matches the 10 characters coming after the
three first ones. Since parentheses "()" are used, this becomes variable
"$1". This is the component name information.
Component batch string. – The "(.+)" characters matches the characters coming after the 13 first
ones. Since parentheses "()" are used, this becomes variable "$2".
This is the component batch information. Note the use of the "+" meta
character, this pattern will only match if there is at least one character
after character 13.
– The second set of "" characters are marking out the output from the
filter. For further information, see page 8-11.
– The "C$1" characters are used to write a "C" and then the
10 component name characters to the string sent to TPSys.
– The "\\n" characters define that there should be a new line in the
output string. For further information, see page 8-17.
– The "B$2" characters are used to write a "B" and then the component
batch characters to the string sent to TPSys.
If the string contains only the first three characters and the 10 component name
characters (no component batch information), the first line will not find a
match, and the string will pass through the filter unchanged. Therefore there is
a second filter that handles such strings.
The table below shows how this example translates various strings:
If your string uses a different divider than "-", simply replace the "-" character
in the filter to the one used in your barcode.
Note that if the separating divider is a meta character (see page 8-5), you need
to use the '\' character before it. For instance, if the separating character is a
"+", you need to write "\+".
The table below shows how this example translates various strings:
In this example, the "()" characters are used to create a variable also for the
second section. This is not strictly necessary, but makes the filter "better
looking". An alternative filter file is shown below.
"^(.*):.*:(.*)$" "L$1\\nI$2"
This filter uses "L" and "I" as prefixes. You may need to change this,
depending on how the barcode parameters are set.
The table below shows how this example translates various strings:
This filter assumes that the barcode string always contains four sections. If
there are fewer or more sections, the filter will not work correctly.
This filter uses "C" and "B" as prefixes. You may need to change this,
depending on how the barcode parameters are set.
The filter also assumes the sections are always divided by a comma (,).
However, the filter can easily be modified to use different dividers, as well as
having different dividers in the different positions.
The table below shows how this example translates various strings.
The first four characters in the barcode string contains the conveyor width.
This information is not needed by TPSys, and should be blocked by the
filter.The four characters are matched by using "....". The next two characters
contains the number of boards in the cassette. This is matched by a first
variable by using "(..)". The remaining characters contains the layout name,
matched by the second variable "(.*)".
The output part of the filter must start with the prefix for layout, in this case
"L". It will not work to place the "L" after the REPEAT command.
This is followed by the string "REPEAT $1;;;" which will create the desired
string that informs the system that there are a number of boards coming in.
Finally, the string "-1" is also added, since the example filder resides in the
first machine in the line and the TPSys names for those layouts end with "-1".
Of course, this is only needed if the "-1" convention is used.
The table below shows how this example translates various strings.
If you are using the "-1" naming convention for the layouts for the first
machine in the line, you can modify the filter for the second machine in the
line by changing the end of it:
"....(..)(.*)" "LREPEAT $1;;;$2-2"
In the example below, the unwanted strings are "error" and "no read". To be
safe, the filter is made case insensitive. After the two filters, the filter file is
then changed back to being case sensitive.
IGNORECASE
"^error$" ""
"^No Read$" ""
NOIGNORECASE
Introduction
TPSys generates a message when something unexpected happens or as a
feedback to an operator action. An unexpected message usually indicates that
there is an error and that operator intervention may be required. Messages that
function as feedback to operator actions are only informational.
Messages are displayed at the bottom of the screen and stored in a message log
for later printout.
Message Severity
There are four message severity classes:
I – Information
Information to the operator that does not indicate any problem. The
messages are printed mainly as feedback to operator actions. For instance
magazine inserted.
W – Warning
Indicates that something has happened that may require operator
intervention but the machine operation can continue.
E – Error
Indicates that something has happened that will require operator
intervention. The machine operation may continue but will eventually
stop and the current assembly cannot be completed.
F – Fatal
Indicates that something has happened that prevents further operation
without operator intervention.
The message severity or class is not part of the message itself. The severity of
a specific message will often depend on current machine status.
The messages are shown in a color that depends on the message severity class
and the parameters controlling the color for each class. If you want to modify
the color for Information messages, change parameter 231.0084 Messages;
Information. Note that the color settings are in hexadecimal code.
<class>-<group>-<number>:<message text>
<class> Message severity class as described on page A-1.
<number> Message number. Note that the MOT group has a special
message number format. See documentation for the MOT group,
page A-56.
<message text> Message text. For the most common messages, message
text is translated to the local language.
Certain message texts contain both a standard text as well as a name or value.
In this manual, the names or values are illustrated with the following
placeholder: ’[***]’. On the TPSys screen, there will be an actual name or a
value in the placeholder position.
Example:
This is a message with error class, ’AUTOFID’ group number 35 and the
message text: ’Failed to find fiducial mark [***]''’ where ’[***]’ is replaced
by an actual fiducial mark name when shown on the TPSys screen.
Message Groups
The messages in TPSys are grouped. Messages in the same group are
technically related to each other. Each message group is identified by its
mnemonic.
In this guide, the messages are sorted by message group and then by message
number.
Messages By Group
Conventions
The messages are described in this manual in a consistent format. Each
message will appear similar to the example below, but will contain actual
information. The message number (following the group name) will of course
also vary.
AUTOFID Group
These messages are generated by the automatic fiducial mark search routines.
AUTOFID-3: Fiducial mark is not symmetric
The fiducial mark to teach was expected to be symmetric, but it was not.
– The fiducial mark is not symmetric.
– Teach area is too big. The teach area contains more than the fiducial
mark.
– Teach area too small. The fiducial mark must fit within the teach area.
– Camera calibration database corrupt. Re-calibrate camera.
AUTOFID-4: Cannot update fiducial mark list
The fiducial mark data cannot be written to the database.
– The server is not running. Restart TPSys.
– The database is corrupt.
– Version mismatch between TPSys and the server.
– Network problem.
AUTOFID-7: ID: [***]'Fiducialmarknotfound'
The fiducial mark was not found at all.
– There is no fiducial mark at all within the scan area.
– X-wagon camera lamp broken.
– Hardware problem. The acquired image contains no information at
all.
AUTOFID-9: ID: [***]'Unknownfiducialmark'
The fiducial mark was not found in the database.
– Define and teach the fiducial mark in the Fiducial Marks window.
– Search area too narrow. The whole fiducial mark does not fit within
the specified search area. Increase the search area in the Fiducial
Marks window.
– Wrong dimensions specified for the fiducial mark. Check the
dimensions in the Fiducial Marks window.
– The camera is not calibrated. Re-calibrate the camera.
AUTOFID-37: Failed to fit detected edges to fiducial mark [***]''
The fiducial mark was found in the coarse search step, but TPSys detected
that the shape of the detected mark does not correspond to the pre-defined
shape of the fiducial mark.
– Wrong type chosen for the fiducial mark.
– Wrong color chosen for the fiducial mark.
– The dimensions of the fiducial mark are wrong, try re-teaching the
fiducial mark.
– Search area is too narrow. The whole fiducial mark does not fit within
the specified search area.
– The shape of the fiducial mark does not correspond to any of the pre-
defined shapes in TPSys. Try re-teaching the fiducial mark as a mark
with type Generic.
– Not enough edge points were detected, try adjusting the Coarse
search method and Contrast offset fields for the fiducial mark.
AUTOFID-38: Frame grabbing failed
The frame grabber card failed to acquire an image using an X-wagon
camera.
– The coaxial cable from the camera is not connected to the frame
grabber card.
– Hardware error, for instance camera, VVG2 card or interrupt
conflicts. Contact Mycronic support.
AUTOTEACH Group
These messages are generated by the Autoteach routines.
AXIS Group
These messages are generated by the routines that control the machine
movements. Most messages may contain an axis identifier.
Identifiers
The <Axis> identifier in the messages below is one of:
C Axis
The mechanical centering.
Theta Axis
The rotating movement for the standard mount head.
X Axis
The X movement.
Y Axis
The Y wagon.
Z Axis
The vertical movement for the standard mount head.
Traywagon
The TWM tray magazine Y movement.
ConWidth-Axis.
The conveyor board width movement.
HZ Axis
The HYDRA vertical movement.
Htheta-Axis
The rotating movement for the HYDRA heads.
ConTransp-Axis
The conveyor board transport movement.
ConHold-Axis
The conveyor board hold movement.
Messages
AXIS-<Axis>/0: Error reading parameter file
Failed to read parameter.
– Parameter file corrupted.
– Software problem.
– Corrupted file system.
AXIS-<Axis>/1: Timeout in wait for axis to reach above specified position
The axis did not reach a specified position.
– High friction.
– Obstacles in axis path.
– Parameter problem.
– Problem in the package/assembly data.
AXIS-<Axis>/2: Timeout in wait for axis to reach below specified position
The axis did not reach a specified position.
– High friction.
– Obstacles in axis path.
– Parameter problem.
– Problem in the package/assembly data.
The message terms above and below refer to transducer values and not to
physical positions. For example the Z and HZ axis lower values are at the
physical upper position.
BACKUP Group
These messages are generated by the scheduled automatic backup routine.
BADBOARD Group
These messages are generated by the bad-board vision routines.
BC Group
These messages are generated by the barcode utility.
XWBC Group
This message is generated by the barcode utility.
BRDH Group
These messages are generated by the board handler routines.
CALIBRATION Group
These messages are generated by the calibration routines.
CAME Group
Camera system interface routines.
DATAS Group
Not documented.
EXORD Group
These messages are generated by the internal executor order routines.
EXP Group
These messages are generated by the export routines.
FTP Group
These messages are generated by the FTP transfer routines.
GLU Group
Glue station control routines.
GRAP Group
Graphical interface routines.
HEATMON Group
Messages from the X-beam heat deformation monitoring process.
HOPT Group
A message in this group indicates that the HYDRA optimization process has
failed.
HRDW Group
These messages are generated by the hardware control routines.
Most messages in this group will always appear in the context of messages
from other groups that indicates the source of the problem.
Most messages in this group will always appear in the context of messages
from other groups that indicates the source of the problem.
HTLM Group
These messages are generated by the HYDRA tool manager routines.
HTLM-3: Tool fetch fail. Group front, tool [***] (set to error)
TPSys has failed to fetch the specified tool from the HYDRA tool bank.
– The HYDRA tool tube may not have been able to move down far
enough into the tool bank. Check for obstructions, or something stuck
in the tool bank.
– No tool tip was found when checking after the fetch. It either fell off
or there was no tool in the tool bank.
HTLM-4: Tool fetch fail. Group back, tool [***] (set to error)
See HTLM-3.
HTLM-5: HYDRA tool length wrong for tool tube [***]. Expected tool length
[***] mm. Tool length found [***] mm.
TPSys has checked the tool length for the specified tool, and it was not the
expected length.
– The wrong tool may be on the tool tube.
– The tool present may be damaged (tip broken off, for example).
HTLM-6: Cannot fetch entire row simultaneously in tool bank [***]
The specified tool bank is not sufficiently parallel to the line of the
HYDRA tools, so fetching of the tools must be performed in smaller
groups, instead of fetching all tools at once.
HTLM-7: Bad transform for HYDRA tool bank [***]. Uninstalled
The positions of the fiducial marks on the specified tool bank are not in
the expected ratio.
– The wrong coordinates may have been selected during installation.
– The wrong type of tool bank may have been selected.
– The scaling factors for the X-wagon camera may be wrong (re-
calibrate the camera).
HTLM-8: Unknown tool present for head [***].
TPSys expected no tool to be found on the specified tool tube, but
something was found.
HTLM-9: HYDRA tool change turned off due to bad parameters.
The parameter file hydratoolman is corrupt or missing.
HTLM-10: HYDRA Tool Bank [***] is [***] µm too low
The HYDRA unit is unable to reach down enough to change tools in the
specified tool bank.
– Re-install the tool bank in a higher position.
HTLM-11: HYDRA tool [***] remains up at tool change
The specified HYDRA tool latch wasn't released when asked for.
– HYDRA indicators are not working.
– HYDRA latches are not working.
– Error in parameter 29.0062 Sensor level limit.
HWICLIENT Group
These messages are generated by the HWI (hardware interface) client side
software.
IMAGE_ORDER Group
These messages are generated by the image order process.
IMGPROC Group
These messages are generated by the img process.
IMP Group
These messages are generated by the import routines.
Common import
IMP-1: Unexpected data at line [***]
The specified line does not comply with any of TPSys import formats.
IMP-2: Error parsing line [***]
The specified line does not comply with the TPSys import format.
IMP-3: Unexpected end of file
End of file occurred before all mandatory lines of the imported type had
been read.
IMP-4: No such file
The file specified for import does not exist.
IMP-5: Barcode "[***]" is not unique. Used by "[***]"
The imported barcode is already used by the specified component.
IMP-6: Removable feeder "[***]" already exists.
The imported removable feeder name is already in use.
Layout import
IMP-100: Layout [***] already exists
IMP-101: Layout [***] imported
IMP-102: Failed to import layout [***]
IMP-103: Layout list is protected
If the user access system is active, a user needs access level High for the
Layout field to be able to import one.
IMP-104: Barcode [***] already exists. Used by [***]
The imported barcode is already used by the specified layout.
Panel import
IMP-200: Panel [***] already exists
IMP-201: Panel [***] imported
IMP-202: Failed to import panel [***]
IMP-203: Panel list is protected
If the user access system is active, a user needs access level High for the
Board field in the Users window to be able to import one.
PCB import
IMP-300: PCB [***] already exists
IMP-301: PCB [***] imported
IMP-302: Failed to import PCB [***]
IMP-303: PCB list is protected
If the user access system is active, a user needs access level High for the
Board field in the Users window to be able to import one.
Component import
IMP-400: Component [***] already exists
IMP-401: Component [***] imported
IMP-402: Failed to import component "[***]"
IMP-403: Component list is protected
If the user access system is active, a user needs access level High for the
Component field in the Users window to be able to import one.
Package import
IMP-700: Package [***] already exists
IMP-701: Package [***] imported
IMP-702: Failed to import package "[***]"
IMP-703: Camera [***] used inconsistently by package [***]
The specified camera is in both the usable and non-usable camera lists for
this package.
IMP-704: Camera type [***] in banned list for package [***]
Camera types cannot appear in the banned list, only specific cameras.
IMP-705: Package list is protected
If the user access system is active, a user needs access level High for the
Package field in the Users window to be able to import one.
Magazine import
IMP-800: Component [***] already exists
IMP-801: Component [***] imported
IMP-802: Failed to import component "[***]"
IMP-803: Magazine [***] is inserted, cannot import it
IMP-804: Failed to import magazine "[***]", serial number [***]
IMP-805: Removed duplicated barcode "[***]", magazine "[***]"
IMP-806: Magazine list is protected
If the user access system is active, a user needs access level High for the
Magazine field in the Users window to be able to import one.
IMP-807: Failed to import pallet [***]
IMP-808: Pallet list is protected
If the user access system is active, a user needs access level High for the
Magazine field to be able to import a pallet list.
IMP-809: Failed to import tray [***]
IMP-810: Tray lists are protected
If the user access system is active, a user needs access level High for the
Magazine field in the Users window to be able to import a tray list.
IMP-811: Inconsistent data for magazine [***], feeder group [***].
IMP-812: Magazine [***] with serial number [***] and type code [***]
already exists. Cannot import magazine [***] with different type code.
A magazine with the same serial number as the magazine being imported
already exists, but the type code differs. That is not allowed. The
magazine will not be imported.
IMP-813: Magazine named "[***]" already exists. Renaming imported
magazine to "[***]"
A magazine with the same name as the magazine being imported already
exists. The one being imported will be renamed, with the new name
shown in the message.
User import
IMP-950: User [***] already exists
IMP-951: Failed to import user [***]
IMP-952: Importing user [***]
IMP-953: User list is protected
If the user access system is active, a user needs access level High for the
User field in the Users window to be able to import one.
IMPORTD Group
These messages are generated by the automatic import feature.
LSCD Group
These messages come from the Linescan camera process.
MAGREF Group
These messages are generated by the magazine fiducial mark search vision
routines.
MAGREF-0: Bad input parameters
Search area outside image boundaries.
– Parameter 41.0053 Magref; Length of scanline is larger than image
width.
– The absolute value of parameter 41.0052 Magref; Vertical offset is
larger than half the image height.
MAGREF-1: Bad scan length
Obsolete error message.
MAGREF-2: Fiducial mark not found
Fiducial mark could not be found within search area.
– No fiducial mark in image.
– Bad fiducial mark.
– Check if parameters 41.0056 Magref; Min width, 41.0057 Magref;
Max width, 41.0058 Magref; Min length and 41.0059 Magref; Max
length corresponds to the physical dimensions of the magazine
fiducial mark.
– Parameter 41.0060 Magref; Check length is set to Yes in the case
where all of the fiducial marks (length-wise) is not visible in the
camera image. Change the parameter setting to No.
MAGREF-3: Cannot read the correction data. (Try to re-calibrate camera)
The camera's correction data could not be read.
– Camera is not calibrated. Redo the camera calibration.
– Correction data is corrupt.
MHPR Group
These messages are generated by the magazine handler process.
MIPR Group
These messages are generated by the magazine interface process.
MIPR-1: Unknown magazine type. Slot: [***] number: [***] type: [***]
A magazine with an invalid type code has been inserted.
– A faulty magazine has been inserted.
– Software problem in the MOT-M servo program.
– Electrical problem on the magazine bus.
MIPR-2: Fatal error. Reloading motor controller M
The MOT-M servo program does not respond to commands and servo
program is automatically reloaded.
– Software problem in the MOT-M servo program.
– The MOT-M or MI board is broken.
MIPR-3: Cannot load motor controller M
Reloading the MOT-M board failed. The system cannot work properly
without a loaded MOT-M board.
– The MOT-M or MI board is broken.
– The servo software was not correctly installed.
MIPR-7: Bad magazine in slot [***]. Contact Mycronic service
There is some problem with the magazine, preventing it from working
correctly.
– The magazine is broken.
– The magazine is too old and is only compatible with TPSys 1.4 and
older.
– The MOT-M or MI board is broken.
MIPR-12: Fatal process error ID: [***]: [***]. Restart system
The magazine interface system crashed. The system has to be restarted.
– Software problem. Make a ’savestat’ diskette and contact Mycronic
support.
MIPR-13: Feeder [***] communication error at slot [***], feeder [***]
There is some problem with the feeder, preventing it from working
correctly.
– The feeder is broken.
– The MOT-M or MI board is broken.
MIPR-20: System voltage [***] measured [***] V (outside limits)
A system voltage deviates too much from the nominal value. The machine
will refuse to run.
– Electrical problem in the machine.
– The MOT-M or MI board is broken.
– Wrong voltage limits specified in parameter group 141 Voltage check.
MMI Group
These messages are generated by the man machine interface process.
MNTSYNC Group
The messages in this group relates to the synchronization between the two
X wagons in a MY100DX machine.
MONT Group
These messages are generated by the Mounter routines.
MONT-0: Error reading parameter file
Cannot read one of the parameters.
– Corrupted parameter file.
– Could also be a software error.
MONT-1: Fatal error: exception on exception
An error occurred while the system tried to recover from an earlier error.
– See previous messages in log.
MONT-2: Exception
An error occurred in the motor control system.
– See previous messages in log.
MONT-4: Stop key pressed
Operator pressed stop key. Information message.
MONT-5: Wrong type of tool for mounting
The tool specified for mount is not a mount tool.
– Parameter error.
– Error in package data.
– Software problem.
MOT Group
For each command sent to a motor control computer, a status is returned.
For historical reasons this group is labeled MOT but it applies to messages
generated from MOT1, MOT2, MOT3 and CMOT boards.
MOT commands
This is a list of commands sorted alphabetically.
AIRFLOW
Read air flow sensor.
AUXILLARY FUNCTION 1
Read name of auxiliary function 1 of a CMOT board.
AUXILLARY FUNCTION 2
Read name of auxiliary function 2 of a CMOT board.
AXISACC
Read maximum acceleration for an axis.
AXISDIST
Read covered distance for an axis.
AXISFORCE
Read minimum and maximum valid axis force.
AXISRANGE
Read minimum and maximum valid axis positions.
BEAMPOS
Read beam sensor and X position.
BLOCKREC
Receive file from a CMOT board.
BLOCKSEND
Send file to a CMOT board.
CALIBAMP
Calibrate Prima amplifier.
CALIBSENSORS
Calibrate board edge sensors and/or set sensor trigger levels.
CAMERAFLASH
Waits for X axis to reach a specified position and then trigger HYDRA
camera or Linescan camera.
CHECKIDLE
Find out if an axis is idle.
CITYTIME
Read the clock of a CMOT board.
CLEAR
Software reset for a given MOT/CMOT board.
CLEARMAGPOLL
Initialize the magazines.
CLEARCITY
Initialize the command id table of a CMOT board.
CONHOLD
Control conveyor board support for MOT controlled conveyors.
CONSTAT
Read conveyor sensor status for MOT controlled conveyors.
DMPLOG
Create a log file containing a history of the last 1000 commands sent to
the motor controllers.
EANNUMBER
Read the EAN number of a CMOT board.
FAN
Control cooling fans.
FILESIZE
Read the size of an internal log file.
FORCECAL
Calibrate the force sensor system for mount tools.
GENERICCAN
Send generic command to a CMOT board.
GENERICMOTQOM
Send generic command to a MOT board.
GETMAXERROR
Get 'maximum error' log from an axis.
GETSMEMA
Read conveyor SMEMA signals.
HAIR
Open/close air valve for HYDRA Z.
HOODOPENED
Check if the hood has been opened since last call.
INCSTEPCNT
Increment step counter value in ALM magazines.
INDPOS
Read hZ position of first indicator hit for the HYDRA.
INDPOSALL
Reads hZ position of all indicator hits for the HYDRA, corresponding to
the most recent MOVEIND or MOVEINDVACWAIT command.
LAMP
X-wagon camera lamps off /on.
LATCHPOS
Read the lowest latch position for the HYDRA.
LIGHTCURTAINTST
Test light curtain.
LISTMOT
Create a listmot log for an axis.
LOADBRD
Load/unload board to/from conveyor for MOT controlled conveyors.
LOAD
Load software to MOT/CMOT board.
LOGMAXERROR
Start/stop maximum error log.
MAGAXISFORCE
Read minimum and maximum valid magazine axis force.
MAGAXISRANGE
Read minimum and maximum valid magazine axis positions.
MAGDISPENSE
Perform a Dip Unit dispensing movement.
MAGFEED
Step one or more feeders in a magazine simultaneously.
MAGGONE
Notify the MOT board M that a component has been picked. This
message exists for the magazine control system in the TP9 SYS 2.92
system.
MAGINIT
Initialize a magazine.
MAGLINK
Send/Receive maglink messages (in other words TEX commands, not for
ATM).
MAGMOVEGO
Similar to MOVEGO but with a specified magazine. Only valid for
magazines with linear movement.
MAGPOLL
Check magazine bus for inserted/removed magazines.
MAGREAD
Read data from magazine port.
MAGREADLONG
Read Agilis feeder serial number from magazine port.
MAGREADPAR
Read magazine parameter.
MAGREADUSER
Read the eight user data bytes in the ID chip in an Agilis feeder.
MAGSETPAR
Set magazine parameter.
MAGSETRAKE
Apply force to the Dip Unit knives. Used for test.
MAGSETVOLT
Apply voltage to a magazine motor. Used for test.
MAGSOLTEST
Activate a solenoid in magazine. Used for test.
MAGSTEP
Send a “step feeder” order to a magazine on the magazine bus.
MAGSTEPOFFSET
Step one feeder in an ALM magazine. The command includes a Y offset
to fine tune the step length.
MAGVIBOFFSET
Step all feeders in an ASM magazine. The command includes a Y offset
to fine tune the step length.
MAGVIBTEST
Vibrate magazine. This command is used when testing a stick magazine.
MAGWRITE
Write data to magazine port.
MCALIB
Calibrate electrical verifier board.
MCOMP
Command to the electrical verifier.
MOVE
Move axis to a specified position.
MOVEGO
Move axis to a specified position with reduced speed and force.
MOVEIND
Move axis to a specific position and run with reduced speed and force
until indicator hit.
MOVEINDVACWAIT
Move axis to a specific position, continue with reduced speed and force
until indicator activated and turn vacuum on or off.
MOVEINDVACWAITPREVACOFF
Move axis to a specific position, continue with reduced speed and force
until indicator is activated. The vacuum is turned off before the expected
indicator is activated.
MOVENICE
Move axis to a specific position with reduced acceleration and speed.
Extra time delay at target is optional.
MOVESEND
Move axis to a specified position and continue with reduced speed and
force.
MOVESENDHOLD
Like a MOVESEND, but use a lower hold force once the axis has stopped.
MOVESLOWMOVE
Move axis to a specified position but reduce speed over a specified
interval (go fast – go slow – go fast to final position).
MOVETOIND
Move a board on the conveyor transport belt relative to a conveyor sensor.
MSETDYN
Initiate axis.
NODEFUNC
Read name of the primary function for a CMOT board.
NODENAME
Read CAN version of a CMOT board.
NODESTARTED
Check start-up status for a CMOT board.
PASSIV
Turn off all motor currents for an axis.
POTSTART
Start the glue pot rotation.
POTSTOP
Stop the glue pot rotation.
PRESSURE
Read air pressure sensor.
PUMP
Start/stop the vacuum pump.
READBORDERLINE
Read border line position.
READCALIBLEV
Read conveyor board edge sensor calibrated level.
READCOUNT
Read transducer count of an axis.
READDELTAX
Read minimum allowed distance between two axes.
READEEPROM
Read EEPROM data from a CMOT board.
READIND
Read status of all conveyor board detection sensors.
READINDEX
Read the axis position where the index pulse was last found. Used for
detecting encoder drift. Currently only implemented for CAN-Y
hardware.
READLPT
Read parallel port.
READMAGINDEXPOS
Read index pulse position and its limits in an ALM magazine.
READMAGREV
Read revision codes from an ALM magazine.
READPAR
Read parameter values.
READPORTS
Read status ports from a CMOT board.
READPOS
Read axis position.
READSERVOPAR
Read internal servo parameter.
READSIZESWITCH
Read the size switch on the conveyor.
READSTAT
Read the status on an axis.
READSTEPCNT
Read step-counter value from an ALM magazine.
READTTY
Read serial port.
READVERSION
Read the servo version.
READVOLTLEV
Read the internal voltage and current levels.
READXUPS
Read UPS bit status for X.
REINITIALIZE
Read configuration files in the HWI process.
RELEASEBOARD
Release a board in a conveyor by moving the hold axis downwards or the
width axis outwards. This command works even if the axis in
uninitialized.
RESET
Perform a hardware reset on the motor controller board.
RESETCOUNTER
Reset the position counter for the conveyor transport belt.
SAFE
Check the safety switches.
SAVEEEPROM
Write EEPROM data to a CMOT board.
SERNUMBER.
Read serial number for a CMOT board.
SETACC.
Set maximum acceleration value.
SETACTIONMODE
Set run mode of a CMOT board.
SETBORDERLINE
Set border line status and position.
SETCANBUS
Set active CAN bus on a CMOT board.
SETCURRENT
Set current at any output stage for a CMOT board.
SETLATCHH
Set HYDRA latches.
SETLOGMODE
Set the HWI logging mode.
SETLOGSET
Start internal logging in servo.
SETLOGSIZE
Set the HWI log size.
SETMAGLED
Set LEDs of a magazine.
SETSERVOPAR
Set servo parameter.
SETSMEMA
Set conveyor SMEMA signals.
SETTRIGOFFSET
Set board edge sensor trigger level.
SETVALVH
Control HYDRA vacuum valves.
SETVIDCHAN
Set video channel.
SETVIDSYNC
Set video synchronization configuration.
SOFTWARE VERSION
Read Altera version of a CMOT board.
STARTCITY
Start CMOT board.
STARTUPSTATUS
Read the start-up status of a CMOT board.
TEST
Send special command to a process on a MOT board.
TESTC
Send a special test command to CMOT board.
TESTDM
Send special command to process D on MOT board M.
TESTEM
Send special command to process E on MOT board M.
TRANSF
Send special message to a MOT board.
VACSENS
Read vacuum and force sensors for axis.
VACSENSH
Read vacuum and force sensors for HZ axis.
VACUUM
Read vacuum sensor.
VALVA
Open/close air valve for Z.
VALVP
Open/close vacuum valve for Z.
VIBR
Resume/hold stick magazine operation.
WAITFORIND
Wait for a specified state on one or more of the conveyor board detection
sensors.
WAITPOS
Wait for axis to reach a specified position.
WAITPOSLATCHHZ
Wait for HYDRA Z axis to reach a specified position and then set
HYDRA latches.
WAITSMEMA
Wait for a SMEMA signal.
WRITELPT
Write to parallel port.
WRITETTY
Write to serial port.
WRITEXUPS
Write to bit status for UPS.
ZEROTIME
Restart the clocks on the CMOT boards.
ZLOCK
Open/close Z lock.
MOT-Command/3: At target
Information message.
– Force or speed too low (may be controlled by parameter).
– Mechanical problem.
MOT-Command/4: Mechanical stop after ind.
Information message.
– Force or speed too low (may be controlled by parameter).
– Mechanical problem.
MOT-Command/15: Command interrupted
Information message. A movement command has been interrupted by
another movement command.
MOT-Command/17: Cannot activate magazine LEDs
No contact with magazine.
– Hardware problem.
– Check XMIF connectors.
– Check settings of select rotary switch SW1 on MIBB board.
MOT-Command/18: Cannot access magazine hardware
No contact with magazine.
– Hardware problem.
– Check XMIF connectors.
– Check settings of select rotary switch SW1 on MIBB board.
MOT-Command/19: Cannot read from magazine
No contact with magazine.
– Hardware problem.
– Check XMIF connectors.
– Check settings of select rotary switch SW1 on MIBB board.
MOT-Command/20: Magazine missed stop position
Error in magazine step operation.
– Magazine hardware problem.
– Check that magazine electronics are clean.
MOT-Command/21: Magazine communication error
Unknown magazine type.
– Magazine hardware problem.
– Check XMIF connectors.
– Check settings of select rotary switch SW1 on MIBB board.
– Check that magazine electronics are clean.
– Check that the setting of the 'SERVO' rotary switch corresponds to the
hardware the controller board is connected to.
– Servo software doesn't recognize the SERVO setting. Update to latest
servo software.
MOT-Command/1094: Encoder direction error on right wagon
MOT-Command/1095: Encoder direction error on left wagon
The servo for the X axis tests the encoder using current pulses in both
direction and checking for movement on the encoder. When this error
occurs, the current output direction does not correspond with detected
movement.
– The XMB board or Prima amplifier may be faulty.
MOT-Command/1096: Linear encoder dead on right X wagon
MOT-Command/1097: Linear encoder dead on left X wagon
The servo for the X axis tests the encoder using current pulses in both
direction and checking for movement on the encoder. When this error
occurs, no movement is detected on the encoder. Either there is no
movement on the X wagon or the encoder fails to detect the movement.
– Check for any movement on the X wagon during initiation.
– Check the encoder operation using "motortest" in the service
program.
– The motor or motor power cable may be faulty.
– The encoder or the encoder cable may be faulty.
– The XMB board or the Prima amplifier may be faulty.
MOT-Command/1098: Servo failed to separate left and right wagon at start
Before the servo starts to operate the left and right X wagons with a servo
controller, the wagons need to be parted. The parting sequence is
performed using the current output to both wagons with opposite
direction.
– The calibration of the amplifiers may be bad, perform the calibration
using the service program.
– The tension in a cable chain may cause external force on an X wagon.
MOT-Command/1100: Axis stroke too short
MOT-Command/1101: Axis stroke too long
Servo measured movement too long or short during initiation.
– Check for loose coupling on the encoder or motor.
– Check for object blocking the movement.
– Check the operation of the motor and encoder using "motortest" in the
service program.
MOT-Command/1102: Drift on hfi error
The servo measures the mechanical end stop position several times during
initiation. This error is generated if the measured stop positions differ too
much.
– Check if the encoder or motor is loose.
– The Hydra theta belt may need cleaning.
The tool pipes need to be clean from old lubrication/dirt and too much
lubrication also gives this problem.
MOTIONDEV Group
Joystick and trackball interface routines.
MOTQ Group
These messages are generated by the MOT communication interface library.
OPTCENT Group
These messages are generated by the optical centering vision routines when
using LSCs or DVCs to take the image or when using an LSC to perform a
calibration.
OPTCORR Group
These messages are generated by the optical correction vision routines.
OPTP Group
These messages are generated by the optimizer process.
–
–
OPTP-50: Fatal process error ID: [***]: [***]. Restart system
The optimization process crashed. The system has to be restarted.
– Internal software error. Make a ’savestat’ diskette and contact
Mycronic support.
ORGP Group
These messages are generated by the organizer process.
OSM Group
Messages in this group come directly from the Linux operating system, and are
not part of TPSys. These messages may indicate problems with the computer
network or with the system hardware. They may also indicate a harmless
condition.
If you are experiencing any problem with your system and such a message
appears, contact Mycronic service.
PARFILE Group
These messages are generated by parameter file reader.
QWIN Group
These messages are generated by an internal operator interface utility.
All messages of this type indicate an internal software error. Make a 'savestat'
diskette and contact Mycronic support.
SERCOM Group
These messages are generated by the serial communication routines user for
directline format host communication.
SERSTART Group
These messages are generated by the serial start facility.
SHDB Group
These messages relate to data sharing.
TCP Group
These messages are generated by the shared database communication.
The text refers to pallet parameters. There are several equivalent sets of pallet
parameters, one set for each pallet type. The text below refers to the first pallet
type, but applies to all pallet types.
TLMN Group
These messages are generated by the tool management routines.
UCOPY Group
These messages are generated by the UNIX copy routines.
UNIX Group
The messages in this group are generated by the operating system inside the
SW. A message of this type typical indicates an internal SW error.
Most of these messages are not explained or commented because the exact
meaning of each message is determined by the context in the source code. For
more information, see a UNIX software developer manual.
USR Group
The messages in this group are generated by the User handling routines.
VACC Group
Vacuum system interface routines.
VER Group
These messages are generated by the electrical verifier interface routines.
VISION Group
These messages are generated by the vision routines.
XINSP group
Messages generated when inspecting components on trays with the PVC (X-
wagon camera).
Appendix B – Parameters
This chapter describes some of the most common parameters (settings) for the
system. The description follows the order in the Parameters window.
1 Axis
This parameter is used to set the servo save status prerequisites.
5 Y axis
5.0051 Acceleration Code Translation; Highest
This parameter controls the acceleration the Y axis uses at all times except
when a component with a package Acceleration code in the Y axis field
is set to High, Low or Lowest.
It you have trays with poorly secured components on the Y wagon, you
may need to slow down the maximum acceleration, to avoid components
falling out of the tray pockets.
Possible values:
– 0 – full acceleration (about 0.5 to 1 G). Default value.
– 1 – acceleration reduced by 50%. Recommended for trays with poorly
secured components on the Y wagon.
– 2 – acceleration reduced by 75%. Not recommended.
– 3 – acceleration reduced by 87.5%. Not recommended.
Note that any other setting than 0 will slow down all Y movements.
21 Z-mount component
21.0229 Centering Levels; Level 8
Most mechanical centering level parameters should not be edited.
However, 21.0229 Centering Levels; Level 8 can be used if you have an
unusual component that needs a non-standard centering level height.
21.0241 Diode Handling; Turn if electrical test failed
Yes – If the system electrically verifies a diode and the test fails, the
system will automatically rotate the diode and test it again with reversed
polarity. If it passes the test, it will be mounted.
No – If the system electrically verifies a diode and the test fails, the system
will reject the part.
21.0242 Diode Handling; Warn when turning
This parameter is only relevant if the 21.0241 Diode Handling; Turn if
electrical test failed parameter is set to Yes.
Yes – Alert the operator that the system is rotating the diodes before
placing. This is the recommended setting.
No – No alert.
21.0325 Place Force; Place force stiff tool
The default force used to place packages with stiff mount tools. If this
parameter is lower than the friction parameter 6.1003 Z Settings; Friction,
a warning is issued as an operator alert.
23 Tool manager
24 HYDRA-mount component
24.0201 Centering; Flash offset 1
24.0202 Centering; Flash offset 2
These two parameters should swap values if the HYDRA camera is
mounted at the right side of the Y wagon.
32 Reject positions
Reject bins are containers where components are dropped if the centering fails.
Which bin to use is controlled by settings in the Components window.
Different component types can have different bins assigned.
For MY100 machines, use either the Not Used setting or the Y Wagon setting.
For MY9–MY19 machines, you may use all three settings.
CAUTION! Use the same set of reject bins activated on all machines in a
factory. Otherwise problems may occur if the component list is shared
between the machines.
33 Dip Unit
33.0012 Data for Dip unit; Down force
The Z-force used, after end-of-fast, when moving down into the flux until
mechanical stop.
33.0013 Data for Dip unit; Down speed
The Z-speed used, after end-of-fast, when moving down into the flux until
mechanical stop.
33.0014 Data for Dip unit; Dwell time
The wait time in the flux.
33.0015 Data for Dip unit; Up speed
The Z-speed when moving up from the flux.
33.0016 Data for Dip unit; Up distance
The distance the up speed (0015) is used.
33.0017 Data for Dip unit; Y pick position
The (y) position of the DPUs shuttle wagon during dispensing.
33.0018 Data for Dip unit; Dispense speed
The (y) speed of the DPUs shuttle wagon when moving to the dispense
position (0017).
33.0019 Data for Dip unit; Rake force
The down force of the rakes that even out the flux.
33.0020 Data for Dip unit; Park position
The (y) position of the DPUs shuttle wagon when parked.
33.0021 Data for Dip unit; Roll-out interval
How often a special flux roll-out sequence should be performed.
33.0022 Data for Dip unit; Roll-out start position
The start position of the roll-out sequence.
33.0023 Data for Dip unit; Roll-out end position
The end position of the roll-out sequence.
33.0024 Data for Dip unit; Number of roll-outs
Number of roll-outs in the roll-out sequence.
33.0025 Data for Dip unit; Number of roll-outs at init
Number of roll-outs in the roll-out sequence the first time after a DPU is
inserted.
33.0026 Data for Dip unit; Indicator offset
Only used for spring tools. The indicator offset determines how much the
spring is to be compressed when the component reaches the bottom of the
cavity. From the indicator offset, the spring pre-tension and the spring
constant, the applied force can be calculated.
41 Vision
Optical Inspection
41.0034 Optical Inspection; Outline search area
Outlines the image regions inspected to locate packages.
41.0035 Optical Inspection; Mark leads
Marks found package leads or package contour edges.
41.0036 Optical Inspection; Mark model
Marks package model definition.
41.0037 Optical Inspection; Mark index
Marks found index mark and search area.
45 Autoteach
The PCB Id parameters can be changed for a specific PCB ID. See Chapter 8
in the TPSys, Programming Manual.
PCB Id
46.0051 PCB Id; Front Red
46.0052 PCB Id; Ambient Red
46.0053 PCB Id; Ambient Blue
Pre-pick inspect
46.0121 Pre-pick inspect; Front Red
46.0122 Pre-pick inspect; Ambient Red
46.0123 Pre-pick inspect; Ambient Blue
If the system has problems finding reference points or components, you can
try lowering this value.
84 Magazine
Tape Magazines
84.0104 Tape Magazines; Reject percent
The system will shut down a feeder if its ratio of rejected components has
reached this level. Default value is 5%.
84.0105 Tape Magazines; Warning percent
The system will display an operator alert if a feeder's ratio of rejected
components has reached this level. Default value is 1%.
84.0400 Shut down feeder when quantity = 0
This parameter controls whether a tape or stick feeder is shut down when
the component quantity is zero.
– Yes – If a component quantity in a tape or stick feeder is zero, no
attempts to feed or pick will be made for that component. This
includes during adjusting the pick position. If the operator attempts to
start assembly when a component has zero quantity, the component
will be considered unavailable, and the same operator alert will be
displayed as if it were not loaded.
– No – (Default) The feeder will still be available for picking when the
component quantity is zero. Note that the component quantity referred
to here is the value in TPSys, and is not necessarily the same as the
actual quantity in the reel/stick of components.
This parameter controls the behavior for both tape and stick magazines.
Stick Magazines
84.0204 Stick Magazines; Reject percent
See 84.0104 Tape Magazines; Reject percent above.
84.0205 Stick Magazines; Warning percent
See 84.0105 Tape Magazines; Warning percent above.
84.0210 Stick Magazines; Allow HYDRA picks
This parameter controls whether the HYDRA head is allowed to pick
from stick magazines. If this parameter is set to No, the HYDRA head will
not be used for picking from stick magazines, even if the package settings
allow HYDRA picks.
Trays
84.0252 Trays; Reject percent
See 84.0104 Tape Magazines; Reject percent above.
84.0253 Trays; Warning percent
See 84.0105 Tape Magazines; Warning percent above.
84.0255 Trays; Pick level tolerance
This parameter adds an extra tray pick level tolerance to the general pick
level tolerance.
The parameter influences the slow part of the pick cycle. The higher the
value, the better the machine will be to pick from trays that are uneven or
sloping. Default value is 0 mm.
Setting this parameter to a higher value than the default value will slow down
the machine movements during picking from trays.
General
84.0502 Step error recovery activated
Applies to AM8 and TM8F magazines. These magazines have a feeding
resolution of 2 mm. Depending on how the tape is loaded and the pitch in
the tape, TPSys can get out of sync.
– Yes – TPSys will assume that any pick errors are caused by pick
position being out of sync and adjust the pick position 2 mm.
Note that if the pick error is not caused by feeding being out of sync,
this behavior might cause extra pick errors.
– No – TPSys will not perform any 2 millimeter adjustment if pick
errors occur. This is the recommended setting.
123 Barcode
123.0211 Component; Prefix1, 123.0212 Component; Prefix2, and 123.0213
Component; Prefix3
These prefixes control how the system handles incoming barcode scans.
If the scanned string starts with any of the characters listed in these
parameters, the string will be interpreted as a component barcode.
Default is ’C’ for all three parameters.
123.0216 Component Batch; Prefix1, 123.0217 Component Batch; Prefix2,
and 123.0218 Component Batch; Prefix3
These prefixes control how the system handles incoming barcode scans.
If the scanned string starts with any of the characters listed in these
parameters, the string will be interpreted as a component batch barcode.
Default is ’B’ for all three parameters.
123.0511 Layout; Prefix1, 123.0512 Layout; Prefix2, and 123.0513 Layout;
Prefix3
These prefixes control how the system handles incoming barcode scans.
If the scanned string starts with one of the characters listed in these
parameters, the string will be interpreted as a layout barcode.
Default is ’L’ for all three parameters.
123.0521 PCB ID; Prefix1, 123.0522 PCB ID; Prefix2, and 123.0523 PCB
ID; Prefix3
These prefixes control how the system handles incoming barcode scans.
If the scanned string starts with one of the characters listed in these
parameters, the string will be interpreted as a PCB ID barcode.
Default is ’I’ for all three parameters.
Blink parameter
233.0001 Blink rate
The light tower lamps and the buzzer can be steady or intermittent with a
desired frequency. Default setting of the frequency is 1 Hz (233.0001
Blink rate set to 1000 ms).
For every machine state parameter above, it is possible to control how the
lamps and buzzer should behave during that machine state. Use values
from the table below, or read overleaf for more detailed guidelines.
0x4246 The prefix is ’0x’ which simply means that the next four digits are in
hexadecimal code.
0x4246 The first digit is the sum of the following values:
Lamp/Buzzer Off On
White lamp. 0 1
Buzzer. 0 4
Lamp Off On
Red lamp. 0 1
Yellow lamp. 0 2
Green lamp. 0 4
You ’turn on lamps or buzzer with the third and fourth digits. The first and
second digits only control how the lamps or buzzer behave when turned on.
If you type in ’0x0004’ in the field and press <Enter>, the leading zeros after
’0x’ will be removed. The field will show up as ’0x4’.
This chapter describes the ASCII format used by TPSys for the Event Log
export. Note that an application to parse (interpret) the event log data is
relatively advanced.
There is also a utility in the TPSys web interface that presents the data in the
event log in a concise table format, without any need for parsing.
Like other TPSys data formats this format is not intended for humans and
requires post processing to be intelligible.
The format is line oriented and all lines have the same general format, a line
type followed by a number of data fields separated by semicolon:
Character Substitution
The data may contain characters that may be confused for delimiters ’;’ (the
semicolon) or other characters that should, for some reason, not be printed.
These characters are written as a percent sign followed by two hex digits that
identifies the ASCII code in ISO Latin 1 character set.
%3B Semicolon(;)
Time Format
Many event lines come with date-and-time information. The date and time
information is formatted as seconds since January 1, 1970. An example of an
event log line with its time stamp is shown below:
TST;1159774073
(For more information about the TST line, sse page C-11.)
This implies that the list format must be parsed from start to end of the data
and most format parsers will require a memory.
Event Lines
The event lines are grouped into four groups. Below are the groups and the
lines listed.
Header
Special line type that indicates which machine the data is for.
Q1 – Header.
Time Stamp
Special line type that has two properties: Divides the data into ’chunks’ and
marks the time.
T – Time stamp.
LL – Layout loaded.
LU – Layout unloaded.
PL – PCB list.
PID – PCB ID.
PBS – PCB skipped.
STA - Assembly started.
STP - Assembly stopped.
CLR – Clear assembly status
M2 – Mounted.
D2 – Dispensed.
ME2 – Mount error.
TC2 – Tool changed.
RS – Fiducial mark searched.
LRS – Local fiducial mark searched.
MEV2 – Measure electric value.
AC – Alternative components.
ML – Magazine load.
FI – Feeder information.
MI – Magazine inserted.
MR – Magazine removed.
Header
The header line tells from which machine, and until which point of time, the
data is exported.
If you have several machines linked to a server and share event log data, you
will have one Q1 – Header line for each machine.
Q1 – Header
Q1;<machine-name>;<date-and-time>
<machine-name> is the name of the machine (always one word without
spaces).
<date-and-time> Time stamp. Point of time the data was exported from
the machine.
Time Stamp
T – Time stamp
Marks a time stamp in the data.
T;<date-and-time>
<date-and-time> Time stamp.
LL – Layout loaded
Marks the event of a layout load in the machine. The data contains layout name
as well as a batch id. If a layout is loaded this line also implies an LU – Layout
unloaded line later. The LL – Layout loaded line is followed by extra PL –
PCB list lines if the loaded layout is edited, that is removing or adding boards.
LL;<name>;<date-and-time>
<name> Name of layout.
<date-and-time> Time stamp.
LU – Layout unloaded
Marks the event of a layout unload.
LU;<date-and-time>
<date-and-time> Time stamp.
PL – PCB list
This line specifies all PCBs in the layout specified in last LL – Layout loaded
line. The PL – PCB list line always follows an LL – Layout loaded line.
PL;<;-separated-list-of-PCB-names>
<;-separated-list-of-PCB-names> A list of the PCB names included in the
loaded layout. The list will contain one PCB for each PCB in the layout.
Even PCBs not present will be part of the list. The order of the PCBs in
the list will be the same as the order in which they appear in the layout list.
If there are panels in the list, the PCBs will be inserted in the same order
as they appear in the panel.
This list will define the PCBs for subsequent references in the M2 –
Mounted and D2 – Dispensed lines.
PID – PCB ID
PCB ID for a physical PCB. If PCB IDs are used, there is one PID – PCB ID
line for each present PCB in the layout.
PID;<PCB>;<PCB-ids>
<PCB> PCB offset in the PCB list from last PL – PCB list line.
<PCB-ids> PCB ID of the physical PCB.
PBS;<PCB>
<PCB> PCB offset in the PCB list from last PL – PCB list line.
If the assembly contains both gluing and mounting the gluing is done first and
then the mounting. In the event log one will find a pair of Assembly start and
Assembly stop events even though the assembling was not started and
stopped.
STA;<date-and-time>;<identity-code>;<batch>
<date-and-time> Time stamp.
<identity-code> A string used to distinguish this specific layout. This
string could be used to track a layout that is assembled in different
machines in a line.
<batch> Batch id for assembly.
When the assembly contains both gluing and mounting there will be one
’STP;<date-and-time>;REDY ’ event after gluing and one after mounting.
That is, the layout is not ready until there has been an STP - Assembly stopped
event preceded by at least one M2 – Mounted event.
CLR;<date-and-time>
<date-and-time> Time stamp.
M2 – Mounted
Position mounted.
M2;<time>;<PCB>;<location>;<feeder-index>;<mount-head>
<time> Total time for operation in milliseconds.
<PCB> PCB offset in the PCB list from last PL – PCB list line.
<location> Location designator on PCB.
<feeder-index> Magazine feeder Index. Corresponds to a feeder-index as
specified in an ML – Magazine load line (see below).
<mount-head> is the mount head. One of:
Z – For the single mount head on a single X machine.
ZR – For the single mount head on the right X wagon.
ZL – For the single mount head on the left X wagon.
H1 – For tool 1 on the HYDRA head on a single X machine.
H1R – For tool 1 on the HYDRA head on the right X wagon.
H1L – For tool 1 on the HYDRA head on the left X wagon.
H2 – For tool 2 on the HYDRA head on a single X machine.
H2R – For tool 2 on the HYDRA head on the right X wagon.
H2L – For tool 2 on the HYDRA head on the left X wagon.
and so on.
Other head names can be added in the future.
D2 – Dispensed
Position dispensed.
D2;<time>;<PCB>;<location>;<mount-head>
<time> Total time for operation in milliseconds.
<PCB> PCB offset in the last PL – PCB list line.
<location> Location designator on PCB.
<mount-head> Mount head (as defined in the M2 – Mounted line).
ME2;<date-and-time>;<error-type>;<feeder-index>;<mount-head>
<date-and-time> Time stamp.
<error-type> Type of error:
PICK – Failed to pick. Attempt to pick component from magazine
failed. This includes failed vacuum-test.
MDIM – Wrong mechanical dimension. Component mechanical
dimensions not within spec.
ELVE – Failed electrical verification.
OPTC – Optical centering failed.
STEP – The magazine cannot be stepped. Probably a hardware error.
LSFE – Local site fiducial search failed.
OTHER – Other errors, for instance package not mountable.
<feeder-index> Magazine feeder index. Refers to a feeder index in one of
the ML – Magazine load lines that occurred since last STA - Assembly
started line.
<mount-head> Mount head (as defined in the M2 – Mounted line).
RS;<time>
<time> Total time for operation in milliseconds.
LRS;<time>
<time> Total time for operation in milliseconds.
MEV2;<type-of-test>;<result>;<PCB>;<location>;<feeder-index>
<type-of-test> Type of electric test.
R – Resistance test. Results in Ohms.
C – Capacitance test. Results in Farads.
C1 – Low voltage capacitance test. Results in Farads.
CP – Polarized capacitance test. Results in Farads.
DF – Diode voltage drop. Results in Volts.
DB – Diode leakage. Results in Amperes.
Z – Zener diode voltage drop. Results in Volts.
TN – NPN transistor current gain test. Results in hfe.
TP – PNP transistor current gain test. Results in hfe.
NO – No test. Should never appear in the event log.
<results> The results of the measurement. The unit of the results is
depending on the type of the test.
<PCB> PCB offset in the PCB list from last PL – PCB list line.
<location> Location on PCB.
<feeder-index> Magazine feeder index. Corresponds to a feeder Id as
specified in an ML – Magazine load line (see below).
AC – Alternative components
Indicates that an alternative component has been used in assembly of the
following M2 line.
AC;<PCB>;<Location>
PCB – PCB offset in the PCB list from last PL-line.
Location – Location designator on PCB.
ML – Magazine load
Describes magazine load data. Many other events contain fields that refer to a
feeder index that is declared in this line. There are as many ML – Magazine
load lines as there are magazines in the machine.
This line only handle magazines that contain components that are used in the
currently loaded layout. No magazine information is saved about magazines
that are not needed in current layout.
ML;<type>;<magname>;<magserial>;<feeder-
index>;<feederNo.>;<component>;<batch>[;<feeder-
index>;<feeder>;<component>;<batch>...]
<type> Magazine type. One of:
REM – Removable vibratory or tape magazine.
YW – Y-wagon magazine.
TW – Tray-wagon magazine.
TE – Tray elevator magazine (Obsolete).
TEX – TEX magazine.
ATM – ATM magazine.
<mag-name> Magazine name.
<mag-serial> Magazine serial number. This field is only valid for
magazine type REM, TEX, and ATM.
<feeder-index> Magazine feeder index. Used for later reference to the
feeder.
<feederNo.> Feeder number.
<component> Component name.
<batch> Batch info.
FI – Feeder information
Gives more information about the feeders used in magazines with removable
feeders. Follows an ML – Magazine load line if that line contains data for a
removable feeder magazine.
FI;<mag-serial>;<feeder>;<feeder-name>;<feeder-serial>
[;<feeder>;<feeder-name>;<feeder-serial>...]
<mag-serial> Magazine serial number.
<feeder> Feeder position in the magazine.
<feeder-name> Feeder name.
<feeder-serial> Feeder serial number.
MI – Magazine inserted
Magazine inserted event. Magazine type is always a removable vibratory or
tape magazine. This line is always followed by an ML – Magazine load line.
MI;<mag-name>;<mag-pos>;<mag-serial>
<mag-name> Magazine name.
<mag-pos> Magazine position number. Specifies in which slot the
magazine is inserted.
<mag-serial> Magazine serial number. This is a number is used to
identify magazine.
MR – Magazine removed
Magazine removed event. Magazine type is always a removable vibratory or
tape magazine.
MR;<type>;<mag-serial>
<type> Type of magazine, see ML – Magazine load.
<mag-serial> Magazine serial number. This number is used to identify the
magazine.
TST;<date-and-time>
<date-and-time> Time stamp.
TSP;<date-and-time>
<date-and-time> Time stamp.
BC – Board changed
Board load/unload. This line will only appear if the machine is connected to a
conveyor. The line specifies the time for a complete board change, including
the time that the machine has waited for the conveyor.
BC;<time>;<result>
<time> Time in milliseconds. The time from assembly stop until next
board is loaded and it's possible to start a new assembly.
<result> Reason for end of wait:
OK – The board change went well.
ABORT – Aborted.
CUW;<time>;<result>
<time> Time in milliseconds. The amount of time that the machine has
waited for the unloading event.
<result> Result for end of wait:
OK – Board unloaded.
ABORT – Wait aborted.
FE – Feeder error
Signal that it is not possible to pick components from this feeder anymore. The
feeder is unusable until an FO – Feeder ok line occurs.
FE;<date-and-time>;<feeder-index>
<date-and-time> Time stamp.
<feeder-index> Feeder index for the feeder that fails. Refers to a feeder
index specified in one of the ML – Magazine load lines.
FO – Feeder ok
Signal that a feeder is ’back in business’. The problem that caused the feeder
error has been taken care of by the operator. It is now possible to pick
components from the feeder again.
FO;<date-and-time>;<feeder-index>
<date-and-time> Time stamp.
<feeder-index> Feeder index for feeder that is now OK. Refers to a feeder
index specified in one of the ML – Magazine load lines.
MTC;<time>
<time> Total time for operation in milliseconds. The time it took for the
operator to change tools.
MRS;<time>;<result>
<time> Time in milliseconds. Time that the operator used to search for the
fiducial mark.
<result> Result of the reference search:
OK – Adjust ready.
ABORT – Adjust aborted.
OW – Operator wait
Wait for operator. This is a ’catch all’ event that logs an event where the
machine waits during assembly for operator to do something that does not fit
any event above.
OW;<time>;<event>
<time> Time in milliseconds.
<event> A description of type of event. Example could be: ’Wait for OK
to initiate HW’.
ULI;<date-and-time>;<user>;<tty>
<date-and-time> Time stamp.
<user> Name of the user that logged in to the system.
<tty> The terminal (tty) that was used.
ULO;<date-and-time>;<user>;<tty>
<date-and-time> Time stamp.
<user> Name of the user that logged out of the system.
<tty> The terminal (tty) that was used.
ASO;<date-and-time>
<date-and-time> Time stamp.
ASF;<date-and-time>
<date-and-time> Time stamp.
Note that future versions of TPSys may remove these lines from the export
completely. It is therefore recommended to update the parsers to use the new
lines only.
TC – Tool changed
Obsolete. Replaced by the TC2 – Tool changed line.
Standard head tool change event. Show the standard tool changes in the
machine.
TC;<time>;<from-tool>;<to-tool>
<time> Total time for operation in milliseconds.
<from-tool> Tool before change. The standard tool type can have one of
the following values:
– A12, A13, A14, A23, A24, A34,
– B12, B13, B14, B23, B24, B34,
– C12, C13, C14, C23, C24, C34,
HYDRA tool change event. Show the HYDRA tool changes in the machine.
This type of event handles up to eight HYDRA tool changes.
HTC;<time>[;<pipette_no>;<typeOfTool>;<toolTipPosition>...]
<time> Total time for operation in milliseconds.
<pipette_no> HYDRA pipette number. The HYDRA pipettes are
numbered from 1 up to 8.
<typeOfTool> Type of HYDRA tool tip. The HYDRA tool type can have
one of the following values:
– H01, H02, H03, H04, H05, H06,
– H07, H08, H09, H10, H11, H12,
– H13, H14 and H15.
<toolTipPosition> Fetch position for the tool tip.
M – Mounted
Obsolete. Replaced by the M2 – Mounted line.
Position mounted.
M;<time>;<PCB>;<line>;<feeder-index>;<mount-tool>
<time> Total time for operation in milliseconds.
<PCB> PCB offset in the PCB list from last PL – PCB list line.
<line> PCB Line No.
<feeder-index> Feeder Index. Corresponds to a feeder Id as specified in
an ML-line (see below).
<mount-tool> Tool number. A numeric value where 0 represents Z (the
standard mount head) and 1..8 represents a nozzle number for the
HYDRA.
D – Dispensed
Obsolete. Replaced by the D2 – Dispensed line.
Position dispensed.
D;<time>;<PCB>;<line>
<time> Total time for operation in milliseconds.
<PCB> PCB offset in the last PL – PCB list line.
<line> PCB Line No. Specifies offset in the PCBs designator list.
ME – Mount error
Obsolete. Replaced by the ME2 – Mount error line.
PCB;<PCB-name>;<;-separated-list-of-location-designators>
<PCB-name> Name of the PCB.
<;-separated-list-of-location-designators> Location designators in line
number order separated by ’;’.
MEV;<typeOfTest>;<result>;<PCB>;<line>;<feeder-index>;<Standard
deviation>
<typeOfTest> Type of electric test.
R – Resistance test. Results in Ohms.
C – Capacitance test. Results in Farads.
C1 – Low voltage capacitance test. Results in Farads.
General information
• Formats.
Mount data
• Layout Data Format.
• Panel Data Format.
• PCB Data Format.
• Fiducial Mark Data Format.
Magazine data
• Magazine Data Format.
• Tray Type Data Format.
• Tray Position Data Format.
• Removable Feeder Data Format.
• Magazine Kit Data Format.
Auxiliary data
• Management Data Format.
• TEX Data Format.
• User Data Format.
Formats
The formats are all ASCII-based with typically multiple lines of data for each
item. An item can for example be a component or a magazine.
Id data
Id – the line id. The line id is composed of one or two letters followed
by one or more digits and optional extra characters. Examples:
C01
M1
P08a
M30-TR
Note that leading zeros in numbers are significant for the Id field. C1
is not the same as C01.
data – is the data for this line. The format and type of data is defined by
the line Id.
Obsolete lines
Some lines or fields are marked as ’Obsolete but supported for import’. This
means that the line is read at import, and that the data is either ignored or
converted to a newer data structure. Obsolete lines are never exported.
– Numerical data.
Numerical data usually define a physical property. See below for
units. Unless otherwise specified, the format can be integer numerical
data, decimal numerical data or floating point numerical data.
– Text data.
A text, usually with a specified maximum length. Leading and trailing
spaces are ignored and multiple spaces and tabs are treated as a single
space. Text data that contain spaces must be surrounded by double
quotes ("). The double quotes are optional if the text data is the last (or
only) data on the line. The characters back slash (\) and double quote
(") are coded with a preceding back slash, in other words \\ and \".
– Enumerated data.
Same as a text data but only a selected set of strings accepted.
– Boolean data.
Special type of enumerated data that express a TRUE/FALSE data
item.
The ’TRUE’-value can be represented with one of:
TRUE
YES
Y
1
The ’FALSE’-value can be represented with one of:
FALSE
NO
N
0
Comparison is not case sensitive.
Optional data
Optional data items are surrounded by brackets([]).
Example:
I30 type-code serial-No [magazine-name]
Lists
A data item followed by two dots represents a list of data items. The list is
space separated.
Example:
P04 lead-No. first-lead-offs
Comments
The data format accepts comments and empty lines. Comments are lines
starting with a hash-mark ’#’.
Example:
# This is a comment line and will be ignored.
U unit-code
unit-code – defines the unit. It can be:
nn– nn is a positive decimal or floating point number. All
length data is multiplied by this number and the result is
interpreted as micrometers.
nnI – Where nn is an optional positive decimal or floating
point number with default value of 1. All length data is
multiplied by this number and the result is interpreted as
thousands of an inch (mil).
Examples:
U 1000
Unit is mm (millimeters).
U I
Unit is thousandths of an inch (mil).
U 1000I
Unit is inch.
U 1e3I
Same as above.
U 1000.0I
Same as above.
U1000I
Same as above (the space after 'U' is optional).
Recommendation
Since the unit specification line is not available for all formats and only for the
length property we recommend to used it only when no option is available. The
internal format is an integer representing micrometers which means the U line
cannot be used to increase resolution.
UNKNOWN
Magazine type is not known.
TAPE_MAG
Tape magazine.
VIB_MAG
Vibratory magazine.
TRAY_MAG
Matrix tray magazine.
GFI_MAG
GFI magazine.
Acceleration Codes
The acceleration codes can have one of the following values:
ACC_HIGHEST
Highest possible acceleration.
ACC_HIGH
High acceleration (will reduce acceleration only on the fastest machines).
ACC_LOW
Low acceleration.
ACC_LOWEST
Lowest possible acceleration.
Name
S1 name
Layout name line. Must be first line of file.
– name – Text data. Corresponds to the Layout Data, Name field in the
Layouts window. Leading and trailing spaces are ignored and the
name is truncated to 35 characters. An empty name is not allowed.
Barcode
S1B barcode (Optional)
Barcode line.
barcode – Text data. Corresponds to the Layout Data, Barcode field
in the Layouts window.
Comment
S2 info (Optional)
Layout info line. There may be any number of S2 lines.
info – Text data. Layout information line. Corresponds to the Layout
Data, Comment field in the Layouts window. Leading and trailing
spaces are ignored and the text is truncated to 35 characters.
Unit Code
U unit-code (Optional)
Unit line. This is a line that defines the length unit used in the file. If the
line is omitted the unit is assumed to be um (micrometers). This line is
never exported.
unit-code – Text data. Defines the unit. See page D-4 for further
information.
Board Name
S3B name (Optional)
Board name line. There may be any number of S3B lines, but each S3B
line should be followed by one S4 line and optionally one or several S4M
- S4 combinations.
name – Text data. Corresponds to the Board Data, Name field in the
Boards in Layout window. Leading and trailing spaces are ignored
and the name is truncated to 35 characters.
Panel Name
S3P name (Optional)
Panel name line. There may be any number of S3P lines, but each S3P line
should be followed by one S4 line and optionally one or several S4M - S4
combinations.
name – Text data. Corresponds to the Board Data, Name field in the
Boards in Layout window. Leading and trailing spaces are ignored
and the name is truncated to 35 characters.
Machine Name
S4M machine-name (Optional)
Machine name line. One S4M line for every machine that the layout has
been located in.
If present it will follow an S3B, S3P or an S4 line. There may be any
number of S4M lines, but each S4M line should be followed by one
S4 line.
machine-name – Text data. Name of the machine that the board has
been located in.
Fiducial Marks
S4 x1 y1 x2 y2 [x3] [y3] (Optional)
Panel/board fiducial mark positions. This line specifies the coordinates of
the fiducial marks for the panels/boards in the layout. The S4 lines may
follow an S3B, S3P or S4M line.
There should be one S4 line for each panel or board in the layout, and one
S4 line after each optional S4M line.
x1 – Floating point numerical data. X position of fiducial mark 1.
Corresponds to the Board Data, Fiducial mark 1 field in the Boards
in Layout window.
y1 – Floating point numerical data. Y position of fiducial mark 1.
Corresponds to the Board Data, Fiducial mark 1 field in the Boards
in Layout window.
x2 – Floating point numerical data. X position of fiducial mark 2.
y2 – Floating point numerical data. Y position of fiducial mark 2.
Conveyor Data
S5 conveyor-width (Optional)
Conveyor width specification line. Maximum one S5 line per S1 line.
conveyor-width – Integer numerical data. Corresponds to the Layout
Data, Conveyor width field in the Layouts window.
S6 conveyor-board-type (Optional)
Conveyor board type specification line. Maximum one S6 line per
S1 line.
conveyor-board-type – Enumerated data. Corresponds to the Layout
Data, Conveyor board type field in the Layouts window. Value may
be one of the following:
NORMAL – For normal boards. Parameters 92.0121 Normal
Boards; Maximum allowed belt acceleration to 92.0127
Width Axis; Clamp force control how this board type is
handled.
SMALL – For small boards. Parameters 92.0141 Small
Boards; Maximum allowed belt acceleration to 92.0147
Width Axis; Clamp force control how this board type is
handled.
LARGE – For large boards. Parameters 92.0161 Large
Boards; Maximum allowed belt acceleration to 92.0167
Width Axis; Clamp force control how this board type is
handled.
SPECIAL – For special boards. Parameters 92.0181 Special
Boards; Maximum allowed belt acceleration to 92.0187
Width Axis; Clamp force control how this board type is
handled.
Name of one machine that the board has been located in .............. my12n123
Position of board location in that machine
Board Data, Fiducial mark 1 ......................................... 3.192 mm/2.452 mm
Board Data, Fiducial mark 2 ................................. 240.634 mm/430.019 mm
Board Data, Fiducial mark 3 ..................................... 240.677 mm/2.489 mm
Name of one machine that the board has been located in .............. my15n234
Position of board location in that machine
Board Data, Fiducial mark 1 ......................................... 2.731 mm/2.291 mm
Board Data, Fiducial mark 2 ................................. 239.810 mm/430.012 mm
Board Data, Fiducial mark 3 ..................................... 239.901 mm/2.421 mm
Name
P1 name
Panel name line. Must be first line of file.
name – Text data. Corresponds to the Panel Data, Name field in the
Panels window. Leading and trailing spaces are ignored and the name
is truncated to 35 characters. An empty field is not allowed.
Comment
P2 comment (Optional)
Panel information line. It is possible to use more P2 lines than one at
import but it is only the first that is actually imported. This line is not
exported if the Comment field is empty.
comment – Text data. Corresponds to the Panel Data, Comment field
in the Panels window. Leading and trailing spaces are ignored and the
text is truncated to 35 characters.
Unit Code
U unit-code (Optional)
Unit line. This is an optional line that defines the length unit used in the
file. This line should follow the P2 or the P1 lines. If the line is omitted
the unit is assumed to be um (micrometers). This line is never exported.
unit-code – Text data. Defines the unit. See page D-4 for further
information.
Tools
P21 level-measure-tool-type (Optional)
Level measure tool line. Zero to ’n’ P21 lines may be specified for a panel,
where ’n’ is the number of selectable tools.
level-measure-tool-type – Corresponds to the Level measurement
tools field in the Panels window. Value may be one of the following:
All_Tools
All_Indicator_Tools
Tool type code. See page D-5 for further information.
HYDRA tool type code. See page D-5 for further information.
Fiducial Marks
P3 xcoord ycoord [name]
Panel fiducial marks line. There must be two or three P3 lines in one panel
specification. The P3 lines correspond to the Mark 1 ID, 2 ID and
optionally the 3 ID fields in the Panels window, and the corresponding
pos. fields.
xcoord – Floating point numerical data. X coordinate of fiducial
mark.
ycoord – Floating point numerical data. Y coordinate of fiducial
mark.
name – Text data. Optional. Name of fiducial mark. Leading and
trailing spaces are ignored and the name is truncated to 10 characters.
Test Positions
P5 xcoord ycoord
Glue tool board level test position. Corresponds to the Glue tool test
position field in the Panels window.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
P6 xcoord ycoord
Mount tool board level test position. Corresponds to the Mount tool test
position field in the Panels window.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
P6B xcoord ycoord (Optional)
Bad board mark position. This line is optional and should follow the
P6 line. If the line does not exist, the bad board mark position is set to (0,
0). Corresponds to the Bad board mark position field in the Panels
window.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
Barcode Positions
P51 xcoord ycoord (Optional)
Barcode position centre point.
xcoord – Centre point for panel barcode position.
ycoord – Centre point for panel barcode position.
PCB Name
P7 pcb-name (Optional)
Line that specifies a PCB on the panel. This line should follow a P6 or
P8 line. There may be any number of P7 lines (including zero).
pcb-name – Text data. Corresponds to the PCB Data, Name field in
the Panel PCBs window. Leading and trailing spaces are ignored and
the name is truncated to 35 characters.
Obsolete Lines
P4 xcoord ycoord
Obsolete. Ignored during import. Coordinate line for the lower left corner
of the panel.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
P41 xcoord ycoord (Optional)
Obsolete. Ignored during import. Coordinate line for the upper right
corner of the panel.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
P52 illumination-type (Optional)
X-wagon camera illumination type for barcode.
illumination-type – Enumerated data. Value may be one of the
following:
– AUTO – Use a standard illumination level as specified in parameters
46:0051, 46:0052, 46:0053.
– CUSTOM – Use the illumination level specified in the following P53
row.
P53 frontlight ambient-red ambient-blue (Optional)
X-wagon camera illumination level to use when illumination-type is set to
CUSTOM in row P52
frontlight – Integer numerical data between 0 - 100. Specifies the
frontlight illumination level.
ambient-red – Integer numerical data between 0 - 100. Specifies the
ambient-red illumination level.
ambient-blue – Integer numerical data between 0 - 100. Specifies the
ambient-blue illumination level.
Name
F1 name
Board name line. Must be first line of file.
name – Text data. Corresponds to the Name field in the PCBs
window. Leading and trailing spaces are ignored and the name is
truncated to 35 characters. An empty name is not allowed.
Comment
F2 info (Optional)
Board information line. Must follow the F1 line if present.
info – Text data. Corresponds to the Comment field in the PCBs
window. Leading and trailing spaces are ignored and the text is
truncated to 35 characters.
Tools
F21 level-measure-tool-type (Optional)
Level measure tool line. Zero to ’n’ F21 lines may be specified for a PCB,
where ’n’ is the number of selectable tools.
level-measure-tool-type – Corresponds to the Level measurement
tools field in the PCBs window. Allowed types are:
All_Tools
All_Indicator_Tools
Tool type code – See page D-5 for further information.
HYDRA tool type code – See page D-5 for further
information.
Unit Code
U unit-code
Unit line. Optional. This line defines the length unit used in the file. The
U line follows the F21 line. If there is no F21 line, the U line follows the
F2 line. If there is no F2 line either, the U line follows the F1 line. If the
line is omitted, the unit is assumed to be um (micrometers). This line is
never exported.
unit-code – Text data. Defines the unit. See page D-4 for further
information.
Fiducial Marks
F3 xcoord ycoord [name]
Fiducial marks line. There may be two or three F3 lines. Corresponds to
the Mark 1 ID, 2 ID or 3 ID fields in the PCBs window, and the
corresponding pos. fields.
xcoord – Floating point numerical data. X coordinate of fiducial
mark.
ycoord – Floating point numerical data. Y coordinate of fiducial
mark.
name – Text data. Optional name of fiducial mark. Leading and
trailing spaces are ignored and the name is truncated to 10 characters.
Test Positions
F5 xcoord ycoord (Optional)
Glue tool board level test position. Corresponds to the Glue tool test
position field in the PCBs window.
xcoord – Floating point numerical data. X coordinate of test position.
ycoord – Floating point numerical data. Y coordinate of test position.
F6 xcoord ycoord (Optional)
Mount tool board level test position. Corresponds to the Mount tool test
position field in the PCBs window.
xcoord – Floating point numerical data. X coordinate of test position.
ycoord – Floating point numerical data. Y coordinate of test position.
F7 xcoord ycoord (Optional)
Bad-board test position. Corresponds to the Bad board mark position field
in the PCBs window.
xcoord – Floating point numerical data. X coordinate of test position.
ycoord – Floating point numerical data. Y coordinate of test position.
Barcode Positions
F51 xcoord ycoord
Barcode position centre point.
xcoord – Centre point for PCB barcode position.
ycoord – Centre point for PCB barcode position.
Auxiliary Data
F12 fid-dist-err brd-angle-err max-obstacle-height (Optional)
Special flags line for the PCB.
fid-dist-err – Floating point numerical data. Accepted fiducial mark
relative distance error, in percent. Corresponds to the Accepted
fiducial mark distortion error field in the PCBs window.
brd-angle-err – Integer numerical data. Accepted board angle
deformation value. Corresponds to the Accepted board angle
deformation field in the PCBs window.
max-obstacle-height – Integer numerical data. The height of the
highest premounted object on the PCB that is not defined as a
premounted component. Corresponds to the Highest undefined
obstacle field in the PCBs window.
Obsolete Lines
F4 xcoord ycoord (Optional)
Obsolete. Ignored during import. Coordinate line for the lower left corner
of the PCB.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
F41 xcoord ycoord (Optional)
Obsolete. Ignored during import. Coordinate line for the upper right
corner of the PCB.
xcoord – Floating point numerical data.
ycoord – Floating point numerical data.
Header
Name .................................................................................................... tsoplay
Mark 1 ID, pos. ....................................................................... square, 0/0 mm
2 ID, pos. ............................................................. square, 205.86/-103.63 mm
Glue tool test position ......................................................................... 0/0 mm
Mount tool test position .............................................................. 3.93/0.1 mm
Bad board mark position .................................................................... 0/0 mm
Item 1
pos. ................................................................................... 145.848/-8.930 mm
Angle ................................................................................................ 0 degrees
Group ............................................................................................................. 0
Mount ......................................................................................................... No
Glue ........................................................................................................... Yes
Component .......................................................................................... tsoptest
Comment ............................................................................................... tsop-1
Item 2
pos. ................................................................................. 145.932/-21.590 mm
Angle .............................................................................................. 90 degrees
Group ............................................................................................................. 0
Mount ........................................................................................................ Yes
Glue ........................................................................................................... Yes
Component .......................................................................................... tsoptest
Comment ............................................................................................... tsop-2
Auxiliary data
Accepted fiducial mark distortion error ............................................. 0.125%
Accepted board angle deformation ................................................ 0.5 degrees
Highest undefined obstacle ................................................................... 15 mm
Name
R10 name
Fiducial mark name line. Must be first line of file.
name – Text data. Corresponds to the Name field in the Fiducial
Marks window. Leading and trailing spaces are ignored and the name
is truncated to 10 characters. This field is not allowed to be empty.
Comment
R11 comment (Optional)
Comment line.
comment – Text data. Corresponds to the Comment field in the
Fiducial Marks window. Leading and trailing spaces are ignored and
the comment is truncated to 40 characters.
Type
R12 fiducial-mark-type
Specifies the type of fiducial mark.
fiducial-mark-type – Enumerated data. Corresponds to the Type field
in the Fiducial Marks window. Value may be one of the following:
CIRCULAR
RECTANGULAR
TRIANGULAR
CROSS
BUTTERFLY
TRIANGULAR BUTTERFLY
GENERIC
ODDSHAPE
Color
R14 color
Specifies polarity of the fiducial mark.
color – Enumerated data. Corresponds to the Color field in the
Fiducial Marks window. Value may be one of the following:
BRIGHT – A bright fiducial mark on a dark background.
DARK – A dark fiducial mark on a bright background.
R17 search-contrast
This line specifies search contrast for non-generic fiducial marks.
search-contrast – Integer numerical data. Corresponds to the Contrast
offset field in the Fiducial Marks window. The search contrast to use
in the coarse search step. -1 means ’Auto’.
Obsolete Lines
R00 camera-Id taught name
Fiducial mark name line. Must be first line of file.
camera-Id – Obsolete. Ignored during import.
taught – Obsolete. Ignored during import.
name – Text data. The name of the fiducial mark. Leading and trailing
spaces are ignored and the name is truncated to 10 characters. Name
is not allowed to be empty.
R00-1 machine-name (Optional)
Obsolete. Ignored during import.
R01 comment
Obsolete but supported for import. Comment line.
comment – Text data. A comment about the fiducial mark. Leading
and trailing spaces are ignored and the comment is truncated to
40 characters.
R02 teach-area-x teach-area-y search-area-x search-area-y object-size
contrast-polarity correlation-threshold symmetric-fiducial-mark
[fiducial-mark-type]
Obsolete but supported for import. Specifies the sizes of the teach area
and the search area. Both areas are centered in the frame grabber image.
teach-area-x teach-area-y – Positive integer numerical value. The size
of the teach area in micrometers
search-area-x search-area-y – Positive integer numerical value. The
size of the search area in micrometers
object-size – Ignored during import.
contrast-polarity – Boolean data. Contrast polarity. If 1, white on
black. If 0, black on white.
correlation-quality – Ignored during import.
symmetric-fiducial-mark – Ignored during import.
fiducial-mark-type – Integer numerical data. Zero means 'No defined
shape'. 1 means 'Circle'. (Optional).
R03 object-size-x object-size-y min-object-x-size [min-object-y-size] min-
edge-contrast nom-background-level x-offset y-offset
Obsolete. Ignored during import.
R04 x-gradient-M1 x-gradient-P1 y-gradient-M1 y-gradient-P1
Obsolete. Ignored during import.
R05 xcoord ycoord contrast edge-mean edge-quality background-mean
background-variation x-correction y-correction (Optional)
Obsolete. Ignored during import.
Example 1
R10 AX123
R11 ’For AX board’
R12 CIRCULAR
R13-1 1500 1425 1575
R14 BRIGHT
R15 5000 5000
R16 AUTO
R17 -1
The example above shows a fiducial mark with the following properties:
Example 2
R10 FS456
R12 BUTTERFLY
R13-5 3000 2850 3150 3000 2850 3150
R14 DARK
R15 6000 6000
R16 CONTRAST
R17 44
The example above shows a fiducial mark with the following properties:
Name
P00 name
Package name. Must be first line of a package.
name – Corresponds to the Name field in the Packages window.
Leading and trailing spaces are ignored and the name is truncated to
25 characters.
Type
P000 package-type (Optional)
Package type line. If present, it follows the P00 line. This file is exported
for information purposes. The line is ignored during import.
package-type – Enumerated data. The type of the package. Value may
be one of the following:
PT_GENERIC
PT_TWO_POLE
PT_THREE_POLE
PT_TWO_SYM
PT_FOUR_SYM
PT_TWO_PLUS_TWO
PT_FOUR_ON_TWO
PT_BGA
PT_OUTLINE
PT_GENERIC_BGA
Geometric Data
P01 body-length body-width overall-length overall-width nom-height max-
height min-height
General dimensions line. See spage D-2 for information about units.
body-length – Integer numerical data. Corresponds to the Body length
field in the Packages window.
Handling Data
P022 mount-tool pick-wait place-wait place-force mount-precision [tool-to-
top-offset] [hydra-fine-pitch] [pick-speed] [place-speed]
Replaces P02. Pick and place data line. See page D-2 for information
about units.
mount-tool – Tool type code. Corresponds to the first entry in the
Mount tools field in the Packages window. See also P021 below. Care
must be taken to specify a valid mount tool even though the data
format allows any tool. See page D-5 for further information.
pick-wait – Integer numerical data. Corresponds to the Pick wait time
field in the Packages window.
place-wait – Integer numerical data. Corresponds to the Place wait
time field in the Packages window.
place-force – Integer numerical data or the string ’Low’. Force to use
when placing. Corresponds to the Z mount force field in the Packages
window.
mount-precision – Integer numerical data. Corresponds to the Mount
precision field in the Packages window. Value may be one of the
following:
0 – Normal precision.
1 – Extra high precision (will be slower).
2 – Extra low precision (might be faster).
Accelerations Data
P03 skip-vacuum theta-acc x-acc z-acc hold [y-acc] [hz-acc] [htheta-acc]
[zup-speed] [zup-dist] [tape-acc] [pick-in-centre]
Handling flags and accelerations line. See sections General Data Formats
and Special Enumerated Data Types for further information.
skip-vacuum – Boolean data. Corresponds to the Vacuum test field in
the Packages window. If ’TRUE’, vacuum tests will not be performed
during mount.
theta-acc – Enumerated data. Corresponds to the Acceleration codes,
Theta field in the Packages window.
x-acc – Enumerated data. Corresponds to the Acceleration codes,
X field in the Packages window.
z-acc – Enumerated data. Corresponds to the Acceleration codes,
Z field in the Packages window.
hold – Boolean data. Corresponds to the Hold during X move field in
the Packages window. If ’TRUE’, the package will be held by the
centering jaws while X runs.
y-acc – Enumerated data. Corresponds to the Acceleration codes,
Y field in the Packages window. Optional. Default value if not
supplied is 'ACC_HIGHEST'.
hz-acc – Enumerated data. Corresponds to the Acceleration codes,
HYDRA Z field in the Packages window. Default value if not supplied
is same as z-acc.
Obsolete Lines
P02 mount-tool pick-wait place-wait place-force mount-precision [tool-to-
top-offset]
Obsolete but supported for import. Replaced by P022. Pick and place data
line. See page D-2 for information about units.
mount-tool – Tool type code data. Care must be taken to specify a
valid mount tool even though the data format allows any tool.
pick-wait – Integer numerical data.
place-wait – Integer numerical data.
place-force – Integer numerical data.
mount-precision – Integer numerical data. Value may be one of the
following:
0 – Normal precision.
1 – Extra high precision (will be slower).
2 – Extra low precision (might be faster).
tool-to-top-offset – Integer numerical data. Default value is 0.
Optional.
P031 HYDRA-mountable HYDRA-angle (Optional)
Obsolete but supported for import. HYDRA data line.
HYDRA-mountable – Boolean data. If ’TRUE’, the package is
HYDRA mountable, and tool H02 is selected as mount tool.
HYDRA-angle – Integer numerical data.
P064-O1 OVC-illum [standard-ambient-light] (Optional)
Optical centering phase data. Follows P064-O. If P064-O is omitted
P064-O1 shouldn't be present either.
OVC-illum – Enumerated data. Represents whether the illumination
settings used by the standard camera are those specified by the user or
are automatically calculated by TPSys. Corresponds to the OVC, Z
illumination field in the Packages, Centering Phases window. Value
may be one of the following:
AUTO – Allow TPSys to calculate illumination settings.
CUSTOM – Use illumination settings specified by the user.
OVC-ambient-light – Integer numerical data. Optional. Corresponds
to the OVC, Ambient light field in the Packages, Centering Phases
window. Percent value for ambient light illumination to use with the
standard camera. Value must be between 0 and 100. If standard-
ambient-light is outside the specified limits, the value is changed to
the nearest limit.
Component Name
C00 name
Component name.
name – Text data. Corresponds to the Name field in the Components
window. Leading and trailing spaces are ignored and the name is
truncated to 35 characters. The name field is not allowed to be empty.
Package Name
C01 package-name
Package type for the component specified in the last C00 line.
package-name – Text data. Corresponds to the Package field in the
Components window. Leading and trailing spaces are ignored and the
name is truncated to 25 characters.
Comment
C02 comment (Optional)
Comment line for component specified in last C00 line. Not exported if
the comment field is empty.
comment – Text data. Corresponds to the Comment field in the
Components window. Leading and trailing spaces are ignored and the
text is truncated to 40 characters.
Skip Flags
C03 skip-mount skip-dispense [skip-test]
Status of mount, dispense and test flags for the component. Note that the
skip flags are reversed compared to the corresponding fields in the
Components window.
skip-mount – Boolean data. Corresponds to the Mount field in the
Components window. If ’TRUE’, the component is not mounted.
Exported as ’TRUE’ or ’FALSE’.
skip-dispense – Boolean data. Corresponds to the Glue field in the
Components window. If ’TRUE’, the component is not dispensed.
Exported as ’TRUE’ or ’FALSE’.
skip-test – Boolean data. Corresponds to the Electrical test field in
the Components window. If ’TRUE’, electrical testing of the
component, even when specified, is not performed. Exported as
’TRUE’ or ’FALSE’.
Electrical Test
C06 el-test not-used angle nominal max min (Optional)
Optional electrical test line. There may be zero, one or two C06 lines.
el-test – Enumerated data. Corresponds to the Type field in the
Components window. Represents the electrical test code. Value may
be one of the following:
NO – No test.
R – Resistance test.
C – Normal capacitance test.
C1 – Low voltage capacitance test.
CP – Polarized capacitance test.
DF – Diode forward voltage drop test.
DB – Diode reverse leakage current test.
Z – Zener diode voltage test.
TN – NPN transistor amplification test.
TP – PNP transistor amplification test.
not-used – Boolean data. Not used. Should be set to ’FALSE’ at
import, always exported as ’FALSE’.
angle – Integer numerical data. Corresponds to the Angle field in the
Components window. Specifies the centering angle where it is
possible to perform the specified electrical test. See page D-2 for
further information.
nominal – Integer numerical data. Corresponds to the Value field in
the Components window. The value is expressed in Ohms (R), Farads
(C, C1 and CP), Volts (DF, Z), Amperes (DB) or gain (TN and TP).
max – Integer numerical data. Corresponds to the Value field in the
Components window. For unit, see ’nominal’ above.
min – Integer numerical data. Corresponds to the Value field in the
Components window. For unit, see ’nominal’ above.
Barcode
C07 barcode (Optional)
Barcode data. The C07 line is not exported if the barcode field is empty.
barcode – Text data. Corresponds to the Barcode field in the
Components window. Leading and trailing spaces are ignored and the
text is truncated to 40 characters.
Feeder Type
C08 feeder-type (Optional)
Feeder type line. The feeder type data is used for magazine preparation
and optimization. It is not used by the system during assembly.
feeder-type – Text data. Corresponds to the Feeder type field in the
Components window. Leading and trailing spaces are ignored. The
following values are recognized by the system:
For tape magazines:
8 mm – 8 mm tape feeder.
fp8 mm – 8 mm fine-pitch tape feeder.
12 mm – 12 mm tape feeder.
16 mm – 16 mm tape feeder.
24 mm – 24 mm tape feeder.
32 mm – 32 mm tape feeder.
44 mm – 44 mm tape feeder.
56 mm – 56 mm tape feeder.
72 mm – 72 mm tape feeder.
st32mm – Obsolete.
custom – other feeder type.
For stick magazines:
below10mm – Sticks below 10 mm in height. Corresponds to
sticks that can be loaded in ASP10, ASP1028 and VMF30.
above10mm – Sticks above 10 mm in height. Corresponds to
sticks that can be loaded in ASP1028.
For matrix trays:
None.
Magazine Type
C081 magazine-type (Optional)
Magazine type line. The magazine type is used together with the feeder
type for magazine preparation and optimization. It is not used by the
system during assembly.
magazine-type – Enumerated data. Corresponds to the Magazine type
field in the Components window. Leading and trailing spaces are
ignored. See page D-2 for further information.
Magazine Data
C09 Servo Adjustment (Optional)
Servo adjustment line for Agilis Linear Magazines. The servo adjustment
is used when adjusting tape guides in Agilis Linear Magazines. It
represents how much extra a tape has to be feed for the magazine to feed
the component to the desired location.
Servo Adjustment – Integer numerical data. Servo adjustment in
micrometers.
C10 default-tape-angle default-stick-angle (Optional)
Default load angles line. The values are used when the component is
loaded in a magazine.
default-tape-angle – Integer numerical data. The default load angle
for tape magazines. Corresponds to the Default load data, Tape angle
field in the Components window.
default-stick-angle – Integer numerical data. The default load angle
for stick magazines. Corresponds to the Default load data, Stick angle
field in the Components window.
C12 default-step-length [default-step-length-trim] (Optional)
Default step length value for tape and stick magazines.
default-step-length – Integer numerical data. The step length in
micrometers. Corresponds to the Default load data, Step length field
in the Components window.
default-step-length-trim. Integer numerical data. Corresponds to the
Default load data, Extra ASM feeding steps field in the Components
window.
Obsolete Lines
C11 default-steps finepitch (Optional)
Obsolete but supported for import. Default steps line. The values are used
when the component is loaded in a magazine.
default-steps – The number of steps.
finepitch – Boolean data. Represents the finepitch flag.
Examples
Example 1
C00 123-000
C01 1206-07
C02 A component
C03 FALSE FALSE
C05 FALSE 0 BIN_1
Example 2
C00 123-001
C01 1206-07
C02 RES 1Mohm
C03 FALSE TRUE
C05 FALSE 0 BIN_2
C06 R FALSE 90000 1e+06 1.05e+06 950000
C07 R123-001
C08 8mm
C081 TAPE_MAG
The example above shows a component with the following properties:
Example 3
C00 123-002
C01 1206-07
C02 10nF cap.
C03 FALSE FALSE
C05 FALSE 0 BIN_2
C06 C FALSE 90000 10e-9 20e-9 9e-9
C08 8mm
C081 TAPE_MAG
C10 90000 0
C12 4000 1
Component data
Name .................................................................................................. 123-002
Package .............................................................................................. 1206-07
Comment ......................................................................................... 10nF cap.
Mount ........................................................................................................ Yes
Glue ........................................................................................................... Yes
Polarized ..................................................................................................... No
Reject position ............................................................................. Reject bin 2
Feeder data
Feeder type .............................................................................................. 8mm
Magazine type ......................................................................................... Tape
Tape angle ...................................................................................... 90 degrees
Stick angle ........................................................................................ 0 degrees
Step length .............................................................................................. 4 mm
Extra ASM feeding steps ....................................................................... 1 step
Name
G00 name
Glue dot name line. Must be first line of file.
name – Text data. Corresponds to the Name field in the Glue Dots
window. Not allowed to be empty. Leading and trailing spaces are
ignored and the name is truncated to 15 characters.
Comment
G01 [comment] (Optional)
Comment line.
comment – Text data. Corresponds to the Comment field in the Glue
Dots window. Leading and trailing spaces are ignored and the name
is truncated to 35 characters. May be empty. An empty comment is
not exported.
Tool
G02 tool
Dispense tool line. Specifies which glue tool to use.
tool – Enumerated data. Corresponds to the Tool field in the Glue
Dots window. See page D-5 for valid tools.
Settings
G03 depth-offset wait-time up-distance up-force up-speed
Glue fetch data line. See page D-2 for information about units.
depth-offset – Integer numerical data. Corresponds to the Dip depth in
glue field in the Glue Dots window. Dip depth offset in glue pot, in
micrometers.
wait-time – Integer numerical data. Corresponds to the Wait time in
glue field in the Glue Dots window. Wait time in glue, in milliseconds
(ms).
up-distance – Integer numerical data. Corresponds to the Slow up
distance from glue field in the Glue Dots window. Distance to run
slowly when going up from glue pot, in micrometers.
Examples
G00 DOT0.5mm
G02 C12
G03 0 64 1200 5000 80
G04 0 0 1200 5000 80
The example above shows a glue dot with the following properties:
Special characters
The special characters are not a part of the file format. They are just used to
specify the combination of the line types.
[] means optional.
Magazine
M10 type-code serial-No fiducial-mark-X name [barcode] [step-count]
[fiducial-mark-Y-left] [fiducial-mark-Y-right] [auto-search-fiducial-
mark]
Magazine data line. Must be first line of file.
type-code – Integer numerical data. Type code of the magazine.
Allowed type codes for a magazine are:
-1 – YWM (Y-wagon magazine.)
-2 – TWM (Tray-wagon magazine).
-3 – TEX/ATM Pallet.
1 – Tape magazine 16×8. Obsolete.
2 – Vibratory magazine VM30.
5 – Tape magazine 4×12+4×16. Obsolete.
6 – Tape magazine 5×24. Obsolete.
7 – Tape magazine 8×12. Obsolete.
8 – Tape magazine 8×16. Obsolete.
9 – Trimmable tape magazine TM8.
13 – Trimmable tape magazine TM1216. Obsolete.
14 – Trimmable tape magazine TM24. Obsolete.
15 – Trimmable tape magazine TM12. Obsolete.
16 – Trimmable tape magazine TM16. Obsolete.
17 – Tape magazine TM8B.
21 – Tape magazine TM1216B.
22 – Tape magazine TM24B.
23 – Tape magazine TM12B.
24 – Tape magazine TM16B.
25 – Tape magazine TM32B.
26 – Tape magazine TM44B.
27 – Tape magazine TM5632B.
28 – Tape magazine TM8FB.
32 – Tape magazine TMFLEX.
34 – Generic Feeder Interface GFI.
48 – Agilis magazine AM8.
Cavity Contents
M21-D cavity-number [[cavity name] [typical package]]
Cavity feeder contents line. There should be one M21-D and one M30-
DM line for each cavity feeder in the DPU magazine.
cavity-number – Integer numerical data. The cavity ("feeder")
number.
cavity name – Text data. Name of cavity. Empty if no cavity present.
typical package – Text data. A typical package for this cavity. Used
by the magazine editor when trimming the x-offset (see below).
Empty if no typical package is applicable.
M30-DM x-offset y-offset
Data line for dip cavities. There should be one M21-D and one M30-DM
line for each cavity feeder in the DPU magazine.
x-offset – Integer numerical data. X-wise offset of cavity, in
micrometers, relative the slot position. (DPU have no reference
points).
y-offset – Integer numerical data. Y-wise offset from the DPU’s zero
position. That is, the position the cavity plate is moved to in order to
expose the cavity. Currently not used.
Tray Contents
M20-C tray-name kit-flag feeder-type [angle] [quantity] [component] [batch-
id] (Optional)
Tray contents line. There should be one M20-C and one M30-TP or M30-
TR line for each tray in the YWM/TWM/TEX pallet. Empty trays will not
be present in exported data. Non-present feeders in imported data will be
emptied.
tray-name – Text data. Corresponds to the Name/barcode field in for
instance the TWM Trays window.
kit-flag – Boolean data. Obsolete. Always FALSE when exported.
Ignored when imported.
feeder-type – Obsolete. Ignored when imported.
angle – Integer numerical data. Corresponds to the Component angle
field in for instance the TWM Trays window. Default
90000 millidegrees. Optional (not present if feeder is empty). See
page D-2 for further information.
quantity – Integer numerical data. Corresponds to the Quantity field
in for instance the TWM Trays window. Default value is 0. Optional
(not present if feeder is empty).
component – Text data. Corresponds to the Component field in for
instance the TWM Trays window. Leading and trailing spaces are
ignored and the name is truncated to 35 characters. Optional (not
present if feeder is empty).
batch-id – Text data. Corresponds to the Batch ID field in for instance
the TWM Trays window. The batch id is truncated to 35 characters.
Optional (not present if feeder is empty).
Tray Position
M40-T inserted-In [tray-position] [orientation] (Optional)
Feeder data line for trays.
inserted-In – Integer numerical data. Corresponds to the Machine
field in the YWM Trays or TWM Trays window. ’0’ means not inserted
in any machine. TEX trays always have ’0’ as value.
tray position – Text data. Optional. Corresponds to the Position field
in the YWM Trays or YWM Trays or TEX Trays window. Leading and
trailing spaces are ignored and the name is truncated to 20 characters.
Obsolete Lines
M20 number kit-flag feeder-type [angle] [quantity] [component] [batch-id]
[low-on-components] (Optional)
Obsolete but supported for import. Replaced by M21. Feeder contents
line.
number – Integer numerical data. The feeder number.
kit-flag – Boolean data. Obsolete. Always FALSE when exported.
Ignored when imported.
feeder-type – Text data. The feeder type. Ignored if the feeder type is
fixed.
angle – Integer numerical data. Optional (not present if feeder is
empty). See page D-2 for further information.
quantity – Integer numerical data. Default value is 0. Optional (not
present if feeder is empty).
component – Text data. Leading and trailing spaces are ignored and
the name is truncated to 35 characters. Optional (not present if feeder
is empty).
batch-id – Text data. The batch id is truncated to 35 characters.
Optional (not present if feeder is empty).
low-on-components – Ignored when imported.
M30-TM x-offset step (Not exported. Imported if there.)
Obsolete but supported for import. Feeder data line for tape feeders.
X offset – Integer numerical data. Feeder X-wise offset relative to the
magazine fiducial mark in micrometers.
step – Integer numerical data. Number of steps per feed.
Example 1
M10 48 131080 -122323 ’AM8-131080’ ’’ 0 0 0 Y
M15 0 -1
M21 0 false 8mmtape 90000 -1 ’motis3’ ’abc123’
M35-TM 10300 4000
M21 1 false 8mmtape
M35-TM 20300 4000
M21 2 false 8mmtape
M35-TM 30300 4000
M21 3 false 8mmtape
M35-TM 40300 4000
M21 4 false 8mmtape 90000 -1 ’motis’ ’’
M35-TM 50313 4000
M21 5 false 8mmtape 90000 0 ’’ ’’
M35-TM 60472 4000
M21 6 false 8mmtape
M35-TM 70394 2000
M21 7 false 8mmtape 90000 0 ’’ ’’
M35-TM 80300 4000
M21 8 false 8mmtape
M35-TM 90300 4000
M21 9 false 8mmtape
M35-TM 100300 4000
M21 10 false 8mmtape
M35-TM 110300 4000
M21 11 false 8mmtape 90000 -1 ’motis2’ ’’
M35-TM 120467 4000
M21 12 false 8mmtape
M35-TM 130300 4000
M21 13 false 8mmtape
M35-TM 140300 4000
M21 14 false 8mmtape
M35-TM 150300 4000
M21 15 false 8mmtape
M35-TM 160300 4000
The example above shows a tape magazine with the following properties:
Feeder 1
Angle .............................................................................................. 90 degrees
Quantity ........................................................................................... Indefinite.
Name .................................................................................................... motis3
Batch ID ............................................................................................... abc123
Example 2
M20-C ’TQFP48-0.50’ false tray 0 30 ’tst’ ’D345678’
M30-TR 8000 16000 143898 57507 true ’TQFP48-0.50 3x10’
true
M40-T 5108 "Pos1" LOWER_LEFT
Name
T00 name
Tray type name line. Must be first line of file.
name – Text data. Corresponds to the Name field in the Tray Types
window. Leading and trailing spaces are ignored and the name is
truncated to 20 characters.
An empty field is not allowed.
Size
T02 width length
Tray type dimension line. The tray type coordinate system is defined by
the corners. Corresponds to the Width/length field in the Tray Types
window. Follows the T01 line if present, otherwise it follows the T00 line.
See page D-2 for information about units.
width – Integer numerical data.
length – Integer numerical data.
Fiducial Marks
T04 x y (Optional)
Tray type fiducial marks line. Corresponds to the First fiducial mark
position or the Second fiducial mark position field in the Tray Types
window. There may be zero, one or two T04 lines. See page D-2 for
information about units.
x – Integer numerical data.
y – Integer numerical data.
Pocket Size
T05 pocket-width pocket-length
Size of the tray pocket that contains the component. Corresponds to the
Tray pocket width/length field in the Tray Types window. See page D-2
for information about units.
pocket-width – Integer numerical data.
pocket-length – Integer numerical data.
The example above shows a tray type with the following properties:
Name
TP00 name
Tray position name line. Must be first line of file.
name – Text data. Corresponds to the Name field in any of the YWM
Tray Positions window, TWM Tray Positions window or TEX Tray
Positions window. Leading and trailing spaces are ignored and the
name is truncated to 20 characters.
Empty names are not allowed.
Data
TP01 xcoord ycoord type
Tray position data line. See page D-2 for information about units.
xcoord – Integer numerical data. Corresponds to the Corner at field in
any of the YWM Tray Positions window, the TWM Tray Positions
window or the TEX Tray Positions window.
ycoord – Integer numerical data. Corresponds to the Corner at field in
any of the YWM Tray Positions window, the TWM Tray Positions
window or the TEX Tray Positions window.
type – Integer numerical data. Corresponds to the Type field in any of
the YWM Tray Positions window, the TWM Tray Positions window or
the TEX Tray Positions window. Although the value in TPSys is
enumerated, the data is imported/exported as an integer. Value may be
one of the following:
0 – Lower left corner.
90000 – Upper left corner.
180000 – Upper right corner.
270000 – Lower right corner.
Magazine
TP02 magazine
Magazine type code line.
Machine Number
TP03 machine-number [barcode]
Tray position machine number.
machine-number – Integer numerical data. Corresponds to the
Machine field in the YWM Tray Positions window or the TWM Tray
Positions window. Set to 0 for TEX tray positions.
barcode – Text data. Optional barcode for tray position. Corresponds
to the Barcode field in any of the YWM Tray Positions window, the
TWM Tray Positions window or the TEX Tray Positions window.
Maximum 35 characters.
The example above shows a tray position with the following properties:
Comment
TG20 comment (Optional)
Comment line.
comment – Text data. Corresponds to the Comment field for the
feeder in the Removable Feeders window. Leading and trailing spaces
are ignored and the comment is truncated to 50 characters. Optional,
may be empty. An empty comment is not exported.
Contents
TG31 component batch angle quantity (Optional)
Component data line. See page D-2 for information about units.
component – Text data. Corresponds to the Name field for the
component in the Removable Feeders window. The component name
is truncated to 35 characters.
batch – Text data. Corresponds to the Batch ID field for the
component in the Removable Feeders window. The batch information
is truncated to 35 characters.
angle – Integer numerical data. Corresponds to the Angle field for the
component in the Removable Feeders window.
quantity – Integer numerical data. Corresponds to the Quantity field
for the component in the Removable Feeders window. If the value is
-1, the quantity is interpreted as an indefinite amount.
Magazine Information
TG40 magazine-serial-number feeder-number (Optional)
Magazine information line. Ignored at import.
magazine-serial-number – Integer numerical data. The serial number
of the magazine where the tape is inserted.
feeder-number – Integer numerical data. Feeder position in the
magazine where the removable feeder is inserted. The first position is
0.
Obsolete Lines
TG25 stepPerFeed finePitch
Obsolete but supported for import. Replaced by TG26.
stepsPerFeed – Integer numerical data. Number of steps per feed for
the tape guide.
finePitch – Integer boolean data. 1 if fine pitch steps are to be used, 0
otherwise.
TG30 component batch angle quantity low-on-components (Optional)
Obsolete but supported for import. Replaced by TG31.
component – Text data. The name of the component in the tape. The
component name is truncated to 35 characters.
batch – Text data. The component’s batch information. The batch
information is truncated to 35 characters.
angle – Integer numerical data. The component’s angle in the tape.
quantity – Integer numerical data. Number of components left in the
tape.
low-on-components – Data in this field is ignored at import.
The example above shows a removable feeder with the following properties:
002
VM30 magazine. Vibratory magazine.
011
TM8 magazine. 8 mm tape magazine.
021
TM8 magazine. 8 mm tape magazine.
025
TM1216 magazine. 4X12 mm plus 4X16 mm tape magazine.
026
TM24 magazine. 24 mm tape magazine.
027
TM12 magazine. 12 mm tape magazine.
030
TM16 magazine. 16 mm tape magazine.
031
TM32 magazine. 32 mm tape magazine.
032
TM44 magazine. 44 mm tape magazine.
033
TM5632 magazine. 2X56 mm plus 1X32 mm tape magazine.
034
TM8F magazine. 8 mm tape magazine for tape with 2 mm pitch.
035 036
TMX magazine. Custom magazine.
040
TMFLEX magazine. Flexible tape magazine.
041
STM32 magazine. Obsolete.
042
Generic Feeder Interface GFI.
060
AM8 magazine. Agilis 8 mm magazine.
062
ALM8 magazine. Agilis Linear Magazine 8 mm.
063
ALM1216 magazine. Agilis Linear Magazine 12/16 mm.
064
ALMFLEX magazine. Flexible Agilis Linear Magazine.
0100
Agilis Stick Magazine pallet ASP10. Note that the first ’0’ is significant.
0101
Agilis Stick Magazine pallet ASP1028. Note that the first ’0’ is
significant.
0102
Agilis Stick Magazine pallet ASP28. Note that the first ’0’ is significant.
100
YW magazine. Y-wagon magazine.
101
TW magazine. Tray-wagon magazine.
102
TE magazine. Tray elevator magazine. Obsolete.
201
TEX magazine
201
Single TEX pallet
202
Double TEX pallet
35
ATM magazine
211
ATM 0.25" pallet
212
ATM 0.5" pallet
213
ATM 0.75" pallet
214
ATM 1.0" pallet
215
ATM 1.75" pallet
STM32
Obsolete.
TM8
8 mm tape magazine.
TM8F
8 mm tape magazine for tape with 2 mm pitch.
TM12
12 mm tape magazine.
TM1216
4X12 mm plus 4X16 mm tape magazine.
TM16
16 mm tape magazine.
TM24
24 mm tape magazine.
TM32
32 mm tape magazine.
TM44
44 mm tape magazine.
TM5632
2X56 mm plus 1X32 mm tape magazine.
TMFLEX
Flexible tape magazine.
VM
Vibratory magazine.
YW
Y wagon magazine.
TW
Tray-wagon magazine.
TE
Tray elevator magazine. Obsolete.
TMX
Custom magazine.
TEX
TEX magazine
XS
Single TEX pallet
XD
Double TEX pallet
ATM
ATM magazine
N1
ATM 0.25" pallet
N2
ATM 0.5" pallet
N3
ATM 0.75" pallet
N4
ATM 1.0" pallet
N7
ATM 1.75" pallet
Comment
I20 [comment] (Optional)
Comment line.
comment – Text data. Corresponds to the Comment field in the
Magazine Kits window. Leading and trailing spaces are ignored and
the name is truncated to 35 characters. An empty comment is not
exported.
Magazine
I30 type-name serial-No [magazine-name] (Optional)
Magazine line. This line defines the magazine for the lines following up
to the next I30 line or end of file. If the magazine does not exist, the lines
up to next I30 line or end of file are ignored. Exported as ’I30 - 0’ if the
magazine is not specified.
type-name – Magazine type name or type code. Corresponds to the
Magazine type field in the Magazine Kit Contents window. The magazine
type name is always exported, in other words never exported as an integer
type code. Type code is an integer numerical data between 0 and 255. (See
Magazine type codes above). Type name is a text data. (See Magazine
type names above).
serial-No – Integer numerical data. Corresponds to the Serial number
field in the Magazine Kit Contents window. Magazine serial number
between 0 and 65535. If serial No is 0 the magazine is not specified.
Tray Magazine
I30-X type [Pallet name]
A special version of the I30 line that defines a matrix tray magazine. See
I30 line comment for more info.
type – Text data. Type of tray magazine. Allowed types:
YW – YWM magazine.
TW – TWM magazine.
TE – Obsolete.
XS – Narrow TEX pallet.
XD – Wide TEX pallet.
TEX – TEX magazine.
ATM – ATM magazine.
N1 – ATM pallet 0.25".
N2 – ATM pallet 0.5".
N3 – ATM pallet 0.75".
N4 – ATM pallet 1.0".
N7 – ATM pallet 1.75".
TEX-pallet – Text data. Optional. Name of pallet. Ignored if the type
is YW, TW or TEX.
Magazine Slot
I31 slot (Optional)
Magazine position. Optional line that defines a magazine position for the
magazine. This line must follow an I30 line if present. This line is used to
advise the operator where to put the magazine. There may be zero or one
I31 line for each I30 line.
slot – Integer numerical data. Corresponds to the Slot number field in
the Magazine Kit Contents window. Allowed values are depending on
machine type.
Feeder Contents
I40 feeder-No angle component
Defines feeder contents. One line for each feeder. The lines must follow
an I30 line or an I31 if present. This line also specifies feeder for the
optional I41, (I42,) I45 and I43 lines following this line. Line I42 is not
exported any more but can still be imported.
feeder-No – Integer numerical data. Feeder number. Range depends
on magazine type. No feeder number but a dash mark (-) is exported
if the magazine is unspecified or the magazine is of an invalid type.
Default value: 0.
angle – Integer numerical data. See page D-2 for further information.
component – Text data. Component name. Empty names are not
allowed. Leading and trailing spaces are ignored and the name is
truncated to 35 characters.
I40-X tray-type angle component [tray-name]
Defines feeder contents for matrix tray magazine. This line defines the
feeder contents for a magazine. This line is allowed only if magazine was
specified using an I30-X line. I40-X also specifies matrix tray for the I41-
X line following this line.
tray-type – Text data. Tray type name. ’-’ means that no tray type is
specified.
angle –Integer numerical data. The angle is with respect to the matrix
tray. 0 degrees is pointing into the machine when the tray-type is
defined.
component – Text data. Component name. An empty component
name is not allowed. Leading and trailing spaces are ignored and the
name is truncated to 35 characters.
tray-name – Text data. Optional tray name. Always exported. Leading
and trailing spaces are ignored and the name is truncated to
35 characters. If omitted, a tray name will be generated from the
component name.
Pick Position
I41 x-offset (Optional)
Pick position X offset line. This line is only valid if component was
specified using an I40 line. Follows I40 if present.
x-offset – Integer numerical data. Pick position X offset for feeder.
Offset in micrometers from magazine fiducial mark.
Refill
I41-XA auto-refill (Optional)
Auto-refill line.
auto-refill – Boolean data.
Stepping
I45 steplength (Optional)
Step length data line. There are two versions of this line depending on
magazine type. This version refers to tape magazines.
steplength – Integer numerical data. Length of feed in micrometers.
Valid only for tape magazines.
I45 amplitude time [frequency] [step-length-trim] (Optional)
Step length data line. There are two versions of this line depending on
magazine type. This version refers to stick magazines.
amplitude – Integer numerical data. Vibration amplitude. Value
between 0 and 127. Normal values 50-60. Valid only for VMF
magazines.
time – Integer numerical data. Vibration time in seconds. Valid only
for VMF magazines.
frequency – Integer numerical data. Optional vibration frequency.
Valid only for VMF magazine. Default value: -1. Not exported if
value is equal to -1.
step-length-trim – Integer numerical data. Step length adjustment. For
ASM magazines, a default step length is automatically computed
from the package data. The step-length-trim parameter adds an
adjustment to the automatic value. Default value is -100, which
represents an unspecified trim value.
Quantity
I43 quantity (Optional)
Load quantity line. If quantity line is specified, this data will be used as
loaded quantity when the magazine kit is activated.
quantity – Integer numerical data. Loaded quantity.
If the value is '-1', the quantity is interpreted as an indefinite amount.
Tray Accelerations
I44-X yAcc zAcc (Optional)
Acceleration codes for tray magazines. This line is only valid if
component was specified using an I40-X line. Follows I40-X if present.
yAcc – Enumerated data. Y acceleration to use when handling the
package.
zAcc – Enumerated data. Z acceleration to use when handling the
package.
Obsolete Lines
I42 steps (Optional)
Obsolete but supported for import. Feeding steps data line.
steps – Integer numerical data. Number of steps per feed. Valid only
for tape magazine.
I42 amplitude time [frequency] (Optional)
Obsolete but supported for import. Feeding steps data line. There are two
versions of this line depending on magazine type.
amplitude – Integer numerical data. Vibration amplitude. Value
between 0 and 100. Normal values 50-60. Valid only for vibratory
magazine.
time – Integer numerical data. Vibration time in seconds. Valid only
for vibratory magazine.
frequency – Integer numerical data. Optional vibration frequency.
Valid only for vibratory magazine. Default value: -1. Not exported if
value is equal to -1.
I42-F fine-pitch (Optional)
Obsolete but supported for import. Fine pitch step line. Follows I42 if
present.
fine-pitch – Boolean data. The steps are fine pitch steps if this values
is TRUE. Valid only for tape magazines with removable feeder.
Layout
MD00 layout-name
The header line. Must be first line of file.
layout-name – Text data. Corresponds to the Layout name field in the
Management data printout. Leading and trailing spaces are ignored.
Not allowed to be empty.
Machine
MD01 machine-name
The machine name line.
machine-name – Text data. Leading and trailing spaces are ignored.
Corresponds to the Station field in the Management data printout.
Assembled Layouts
MD02 layouts-assembled
Layouts assembled line.
layouts-assembled – Integer numerical data. Corresponds to the Layouts
assembled field in the Management data printout. The number of layouts
actually assembled.
Assembled Boards
MD03 boards-assembled
Boards assembled line. Specifies number of assembled boards in the
layout specified in the MD00 line.
boards-assembled – Integer numerical data. Corresponds to the PCBs
assembled field in the Management data printout. The number of boards
in the layout that have been assembled.
Assembly Time
MD04 total-time dispense-time assembly-time
Time used for layout.
total-time – Integer numerical data. Corresponds to the Layout loaded
time field in the Management data printout. Total time in milliseconds
the layout has been loaded.
dispense-time – Integer numerical data. Corresponds indirectly to the
Glue time/PCB field in the Management data printout. Total time in
milliseconds used for dispense.
assembly-time – Integer numerical data. Corresponds indirectly to the
Assembly time/PCB field in the Management data printout. Total time
in milliseconds used for component mount.
Component
MD05 component-name (Optional)
Component name line. There may be several MD05 lines or none if
nothing has been assembled yet. When exported there is one MD05 line
for each component.
component-name – Text data. Corresponds to the Component field in
the Management data printout. The name of the component that has
been mounted/dispensed.
Component Statistics
MD06 placed time bad-dimension bad-electric bad-picked bad-placed bad-
other (Optional)
Component statistics line. The MD06 line always follows the MD05 line
and there are always as many MD06 lines as there are MD05 lines. The
MD06 line contains general statistics about the component specified in
the previous MD05 line.
placed – Integer numerical data. Corresponds to the Number placed
column in the Management data printout. The number of components
of the type specified in line MD05, placed on the PCB.
time – Integer numerical data. Corresponds indirectly to the Time (s)/
comp. column in the Management data printout. The amount of time
that was required for placing all placed components of this type.
bad-dimension – Integer numerical data. Corresponds to the
Mechanical failures column in the Management data printout. The
number of components rejected because of incorrect dimensions in
mechanical centering.
bad-electric – Integer numerical data. Corresponds to the Electrical
failures column in the Management data printout. The number of
components rejected because of failed electrical test.
bad-picked – Integer numerical data. The number of failed pick
operations. Includes vacuum failures, vision failures where no
component is found, and those mechanical centering failures that
report Component lost (dimension = 0).
bad-placed – Integer numerical data. The number of mount errors.
Note that a few categories of mount errors are not included.
bad-other – Integer numerical data. The number of times a mount
cycle failed for some other reason than the previous reasons. Includes
all vision failures except where no component is found.
MD07 dispensed time (Optional)
Component statistics line. When specified, it should follow the MD06
line. The MD07 line contains dispense statistics about the component
specified in line MD05 previous to the MD07 line.
dispensed – Integer numerical data. The number of components of the
type specified in line MD05 that has been dispensed.
time – Integer numerical data. The amount of time that was required
for dispensing all components of this type.
Name
X00 name
Tex name line. Must be first line of file.
name – Text data. Name of the TEX. Leading and trailing spaces are
ignored and the name is truncated to 15 characters.
Comment
X01 comment (Optional)
Comment line. An empty comment is not exported.
comment – Text data. A comment about the TEX. Leading and
trailing spaces are ignored and the name is truncated to 50 characters.
Calibration Data
X03 machine slot TEX-pallet-width kxx kx0 kxy kyy ky0 kyx (Optional)
TEX calibration data line. There may exist zero, one or two X03 lines, one
for each TEX column.
machine – Integer numerical value. Machine number where the TEX
is inserted. -1 if not inserted.
slot – Integer numerical value. Slot number where the TEX is
inserted. -1 if not inserted.
TEX-pallet-width – Integer numerical value. Width of TEX pallet
used to trim the TEX column.
kxx – Floating point numerical value. Transform data AC to TC.
X scale factor.
kx0 – Floating point numerical value. Transform data AC to TC.
X offset.
kxy – Floating point numerical value. Transform data AC to TC.
X's Y dependence.
kyy – Floating point numerical value. Transform data AC to TC.
Y scale factor.
ky0 – Floating point numerical value. Transform data AC to TC.
Y offset.
kyx – Floating point numerical value. Transform data AC to TC. Y’s
X dependence.
Name
U00 user-name
User name line. Must be first line of file.
user-name – Text data. Corresponds to the Name field in the Users
window. Leading and trailing spaces are ignored and the name is
truncated to 35 characters.
Password
U01 password
User password line.
password – Text data. The user's encrypted password. Leading and
trailing spaces are ignored and the password is truncated to
15 characters.
Access Data
U02 layout-access board-access
User access rights line for layout and board data.
layout-access – Enumerated data. Corresponds to the Layout field in
the Users window. Value may be one of the following: Low or High.
board-access – Enumerated data. Corresponds to the Board field in
the Users window. Value may be one of the following: Low, Standard
or High.
U03 component-access package-access gluedot-access fiducial-mark-access
User access rights line for component, package, glue dot and fiducial
mark data.
component-access – Enumerated data. Corresponds to the
Component field in the Users window. Value may be one of the
following: Low or High.
package-access – Enumerated data. Corresponds to the Package field
in the Users window. Value may be one of the following: Low or
High.
gluedot-access – Enumerated data. Corresponds to the Glue dot field
in the Users window. Value may be one of the following: Low or
High.
fiducial-mark-access – Enumerated data. Corresponds to the Fiducial
marks field in the Users window. Value may be one of the following:
Low or High.
U04 magazine-access traytype-access magazine-kit-access
User access rights line for magazine, tray type and magazine kit data.
magazine-access – Enumerated data. Corresponds to the Magazine
field in the Users window. Value may be one of the following: Low,
Standard or High.
traytype-access – Enumerated data. Corresponds to the Tray type field
in the Users window. Value may be one of the following: Low or
High.
magazine-kit-access – Enumerated data. Corresponds to the
Magazine kit field in the Users window. Value may be one of the
following: Low or High.
U05 user-access
User access rights line for user data.
user-access – Enumerated data. Corresponds to the User field in the
Users window. Value may be one of the following: Low or High.
U06 switch-access mount-glue-switch-access
User access rights line for switches and mount-glue switches.
switch-access – Enumerated data. Corresponds to the Switches field
in the Users window. Value may be one of the following: Low or
High.
mount-glue-switch-access – Enumerated data. Corresponds to the
Mount/glue switch field in the Users window. Value may be one of
the following: Low or High.
U07 params-access service-access
User access rights line for the Parameters window and the service
program.
params-access – Enumerated data. Corresponds to the Parameter
field in the Users window. Value may be one of the following: Low
or High.
service-access – Enumerated data. Corresponds to the Service field in
the Users window. Value may be one of the following: Low or High.
U08 management-access
User access rights line for management and event log data.
user-access – Enumerated data. Corresponds to the Management field
in the Users window. Value may be one of the following: Low or
High.
Checksum
U100-0 checkstring
Checksum line. This line contains an encrypted version of all user data.
This line is intended to ensure that imported data has the same values as
it had when it was exported.
Import fails if imported user data doesn't agree to the checkstring.
checkstring – Text data. Encrypted text string describing the user’s
access rights.
The TRP format is ASCII-based and the character coding is ISO 8859-1.
Contents:
• Establish Connection.
• Testing Single TRP Commands.
• Quick Reference.
• General Command Format.
• Special Line Types.
• TRP Commands.
• List of Errors.
• TPSys Data Types.
• Unsolicited Messages.
Establish Connection
The TRPserver is not running all the time although it is a server. It is started
by the inet-daemon when a socket-connection is made on port 6549 on a
TPSys machine. After a message has been received, the command is executed
and the result is sent back.
The server terminates when receiving a Terminate command from the process
that opened the connection or when the connection is closed. It is possible to
have more than one TRPServer running on a machine at the same time.
The E line, see page E-4, is not shown when viewing the response in the web
interface.
Quick Reference
ActivateUnsolicited type-list
DeActivateUnsolicited [ type-list ]
GetDataVersion
GetListOf data-type
GetListSize data-type
GetModifiedCount data-type
GetProtocolVersion [ALL]
GetTime [UNIX]
ListOrder
LoadLayout (Obsolete), Use command QueueOrder instead.
MachineInfo [VERBOSE|QUIET]
Ping
PutData [PARSE_FLAG...]
PutEcho [ Parameters...]
RemoveOrder
SetProtocolVersion version
ShowAlerts
ShowCurrentStatus
ShowMessages [ message-Id ]
ShowRunningStatistics
Terminate
VerboseMode mode
<Command-name> [<parameter>...]
Command-name – Text string that contains the name of the
command.
Parameter – The Command-name may be followed by a number of
parameters which depends on which type of command it is. Optional
and non-optional parameters exist. Optional parameters are shown in
brackets [].
All commands are line oriented. The TRPserver accepts commands that follow
the syntax specified in TRP Commands.
The TRPserver is case insensitive. All commands, parameters and data can be
represented by a mix of lower or upper case characters. For instance, 'getdata'
is equivalent to ’GetData’ and ’GeTDaTA’. There are a few exceptions to this,
see Special Line Types and PutData.
Line endings are marked with a newline ('\n', ISO 8859-1 character 10).
For detailed information about all available commands, see TRP Commands.
ack
Acknowledgement line. Returned as a response to some commands. The
line indicates that the command was successfully executed.
ackd
Acknowledgement line. Returned as a response to certain commands that
return some kind of data. The line indicates that the command was
successfully executed.
nack
Error line. Returned if something went wrong when the command was
executed. Indicates that the command failed. The line has following
format:
nack <error-number>[<error-text>]
error-number – Type of error.
error-text – Error description. Only returned if verbose mode is activated,
see VerboseMode.
E
End of data line. Indicates that all requested data is transmitted. Note that
it has to be an upper-case ’E’.
Two commands, PutData and PutEcho, that send data to the server must
be ended with this line.
TRP Commands
ActivateUnsolicited
ActivateUnsolicited type-list
Subscribe to one or more unsolicited messages. The subscription will be
active immediately after the ACK message.
– Parameters:
type-list – List of unsolicited messages to subscribe to. Supported
types are: EventLog and TimeStamp. If you have more than one field
in the list, separate them with either <Tab> or <Space>.
– Special messages:
US connection closed - This message sent by the server indicates that
all subscriptions are terminated by server. This could happen if the
machine is turned off or the system restarted.
US Unknown type – The client tried to subscribe to a nonexistent
message type. This message is sent immediately after the
ActivateUnsolicited.
– Errors reported:
302 – Cannot connect to eventserver.
303 – Cannot start subscription.
– Returned data:
None
DeActivateUnsolicited
DeActivateUnsolicited [ type-list ]
Will unsubscribe one or more unsolicited messages. The specified
unsolicited messages will be deactivated immediately after the ACK has
been received.
– Parameters:
type-list – List of unsolicited messages that server should stop
sending. If this parameter is omitted, all messages are stopped. If you
have more than one field in the list, separate them with either <Tab>
or <Space>.
– Special messages:
US Unknown type – The client tried to unsubscribe to a nonexistent
message type. This message is sent immediately after the
DeActivateUnsolicited message.
– Errors reported:
302 – Cannot connect to eventserver.
303 – Cannot stop subscription. There is no ActivateUnsolicited
command to deactivate.
– Returned data:
None
Delete
Delete data-type name...
Delete data in TPSys internal databases.
– Parameters:
data-type – Type of data. See page E-25 for allowed data types. An
exception: you cannot use the Eventlog TRP data type with this
command.
name... – List of items to delete. If you have more than one field in the
list, separate them with either <Tab> or <Space>.
For items that include special characters such as <Space>, use double
quotation marks around the items. For instance, to delete components
’comp123’ and ’comp 456’, you write the following:
Delete component comp123 "comp 456"
– Errors reported:
6 – Invalid parameter value. Probably a missing parameter.
100 – Unknown data type.
101 – Item <name> does not exist. Even if only one of the items does
not exist, no data will be deleted.
103 – <name> in use, cannot delete. Even if only one of the items
cannot be deleted, no data will be deleted.
305 – Server is not running. The server must be running for this type
of request.
– Returned data:
'ack' line if all selected items, specified by the name-parameter, have
been deleted from the database.
ExitRemoteMode
ExitRemoteMode
Exit remote mode. Not implemented.
– Parameters:
None
– Returned data:
None
GetData
GetData [-s time] [-ext ] data-type [ name...]
Get data from TPSys internal databases.
– Options / Parameters:
-s time – Optional. If omitted, all available data for specified data type
is transmitted. If the parameter exists, only data that is modified since
'time' is transmitted. The time format must be on
MMDDhhmm[[CC]YY][.ss] where:
MM – Month number 01–12.
DD – Day number in month (date) 01–31.
hh – Hour 00–24.
mm – Minute 00–59.
CC – Century 00–99. Optional.
YY – Year 00–99. Optional.
ss – Second 00–59. Optional.
Example
Assume you want to use the GetData command to ask for the data for fiducial
mark ’Calibcomp’. On page E-25 you will find that the data type for fiducial
marks is ’Refpoint’.
Note that the returned data follows the import/export data format described in
Appendix D, with an added ’>’ at the beginning of each line, and a closing line
with an ’E’ followed by a newline character.
GetDataVersion
GetDataVersion
Get (current) data version. The data version is equivalent to the system
release name and number.
– Parameters:
None
– Returned data:
’ackd’ followed by data version information. Data ends with the
E line.
GetListOf
GetListOf data-type
Get a list of available data items for a specific data type
– Parameters:
data-type – Type of data to get. See page E-25 for allowed data types.
– Errors reported:
6 – Invalid parameter value.
100 – Unknown data type.
305 – Server is not running. The server must be running for this type
of request.
– Returned data:
'ackd' followed by a list of available data with one item per line. All
items are preceded by a ’>’. Data ends with the E line.
If the data-type was Eventlog, the returned data will be names of
machines with event log data.
GetModifiedCount
GetModifiedCount data-type
Get a modified count for the specified data type. The modified count is
changed every time data is modified in database. This counter could be
used to detect changes for the specific data type in TPSys internal
database.
– Parameters:
data-type – Type of data to get modified count for. See page E-25 for
allowed data types.
– Errors reported:
100 – Unknown data type. Error code 100 is returned if
’GetModifiedCount’ is used with data type ’eventlog’.
305 – Server is not running. The server must be running for this type
of request.
– Returned data:
’ackd’ followed by the modified counter for specified data type. Data
ends with the E line.
GetProtocolVersion
GetProtocolVersion [ALL]
Get (current) protocol version of TRP.
– Parameters:
ALL – Optional. ALL will instruct command to return a list of
available protocol versions.
– Returned data:
’ackd’ followed by either:
If ALL is not specified: a string containing protocol version info. For
this version it will be 1.0.
If ALL is specified: a new-line separated list of protocol versions
supported. Data ends with the E line.
GetTime
GetTime [UNIX]
Get the current time and date on the machine/server where the TRP server
is executing.
– Parameters:
UNIX – Optional. If specified, the returned time is given in UNIX
style, in other words as seconds since 00:00:00, Jan 1, 1970,
otherwise as a string with time and date explicit. See Returned data:
below for details.
– Errors reported:
6 – Invalid parameter value.
– Returned data:
'ackd' followed by a time and date string.
If no UNIX parameter is given, the time and date string is given on the
format MMDDhhmm[[CC]YY][.ss] where:
MM – Month number 01–12.
DD – Day number in month (date) 01–31.
hh – Hour 00–24.
mm – Minute 00–59.
CC – Century 00–99. Optional.
YY – Year 00–99. Optional.
ss – Second 00–59. Optional.
Help
Help [COMMAND|ACK] [ALL| Command-name ]
Help command. This command returns help about the current version of
the protocol. Not implemented.
– Parameters:
COMMAND | ACK – Select help for ACK-values or COMMAND-
formats. Default id COMMAND.
ALL | Command-name – If parameter 1 is COMMAND, this
parameter specifies the command to get help for.
The command ’Help’ without parameters is equivalent to: Help
COMMAND Help.
– Returned data:
Information about requested item.
ListOrder
ListOrder
List orders in queue for all machines.
– Parameters:
None
– Returned data:
The output is a header and one line per queue position.
Items line are separated by tabs.
Lines are grouped per machine No. and within each machine No.
ordered in the order they where inserted.
Example
For the example, the command looks like this:
ListOrder
ackd
>Machine No. Order Id. Layout Batch Size Started
>13115 kalle ALLAN b2 3 0
>13115 oid 2x 1 0
>13115 2x 2008-01-16 23:46.07 2x 1 0
>15215 kalle2 ALLAN b22 1 0
>15515 kalle2 ALLAN b22 1 0
E
LoadLayout (Obsolete)
This command has been replaced by the new command QueueOrder, see page
E-16. This command may be removed from future versions of TPSys Remote
Protocol (TRP).
LoadLayout layout-name
Load layout to assemble. Layout will be loaded as soon as the current
assembly (if any) is finished and board unloaded.
If there exists a layout queue, that queue will be removed when
LoadLayout is called.
– Parameters:
layout-name – Name of layout to load. For layout names that include
special characters such as <Space>, use double quotation marks
around the name.
– Errors reported:
400 – No such layout.
1000 – Cannot find the queue directory.
– Returned data:
’ack’ if the layout was successfully inserted first in the layout queue.
MachineInfo
MachineInfo [VERBOSE|QUIET]
Request information about the machine and HW/SW options. The request
will take a while to process.
– Parameters:
VERBOSE | QUIET – Optional switch that controls if prompt texts
will be added to return data to make it human readable.
If format is VERBOSE a prompt will precede each data. If format is
QUIET no prompt is added, and only the ’machine-type’ to
’HYDRA-option’ fields are returned. The default value depends on
the current ’verbose mode’ setting, see VerboseMode.
Note that the QUIET mode for this data type is obsolete, and should
not be used for new applications.
– Returned data:
machine-type – The machine type, for instance ’my19’. For a separate
server, the machine type will be ’tp0’. Prompt text: Machine type:
machine-name – The name of the machine, for example my19n032.
For a separate server, the machine name will be ’tp0n000’. Prompt
text: Name:
serial-No. – Machine serial number. (will be set to -1 for a server).
Prompt text: Serial No.:
tpsys-version – The TPSys version string, for instance 2.9.x. Prompt
text: TPSys:
The remaining data fields are only returned from machines, not from servers.
Ping
Ping
No operation. Used to check channel.
– Parameters:
None
– Returned data:
’ack’ is returned if channel is ok.
PutData
PutData [PARSE_FLAG...]
Send data to TPSys databases. The sent data must follow the TPSys
Import/export data format. Data sent to the TRPserver must end with the
E line.
Note that the E line must use an upper-case ’E’ and that the strings
identifying the line type must use upper-case characters, for instance ’S1’.
It's possible to send special parse flags to the server that will affect how
the data lines that follow will be imported into TPSys.
– Example:
Inserting a layout named testlayout in the databases:
PutData
S1 testlayout
E
– Parameters:
PARSE_FLAG – One or more ’parse flags’ that will affect how the
data is imported. The flags should be ’space separated’. Valid values
for the flags:
MAG_UPDATE_ONLY – This ’flag’ is only valid for
magazine data. If the flag is given as an argument to PutData,
the magazine contents will not be cleared. This means that
only feeders specified in the data lines that follow, will be
modified. All other feeders are unchanged and will keep their
old values.
– Errors reported:
102 – Data parse error.
104 – Unexpected line.
105 – Unexpected end of file.
106 – Invalid argument.
305 –Server is not running. The server must be running for this type
of request.
– Returned data:
’ack’ if data was ok and saved in the database.
PutEcho
PutEcho [ Parameters...]
Return the same parameters and data that was sent. Sent data must end
with the E line.
– Parameters:
Parameters – If parameters are supplied they will be returned as data.
– Returned data:
’ackd’ followed by the command followed by an empty line followed
by each parameter word. Data ends with the E line.
QueueLayout (Obsolete)
This command has been replaced by the new command QueueOrder, see page
E-16. This command may be removed from future versions of TPSys Remote
Protocol (TRP).
QueueLayout layout-name
Insert layout in queue of layouts to assemble. Layout will be added to a
queue of layouts that are loaded in the same order as they are sent. If a
LoadLayout (Obsolete) message arrives, it will first clear the queue and
then insert its own parameter in the queue.
– Parameters:
layout-name – Name of layout to load. For layout names that include
special characters such as <Space>, use double quotation marks
around the name.
– Errors reported:
400 – No such layout. The layout could not be found in TPSys
databases.
1000 – Cannot find the queue directory.
– Returned data:
’ack’ if the layout was inserted in the layout queue.
QueueOrder
QueueOrder
Add order to queue.
– Parameters:
None
– Data
The data contains a newline separated list of field-data pairs.
Field names are separated from the data by a : (colon).
Field
Content Max size Comment
name
Layout Name of 35 chars. Mandatory field.
layout.
Batch Id Batch Id 35 chars Optional
Order Size Number of MAXINT Optional, default is 1.
layouts. Must be a positive
integer.
Order Id Identifies the 60 chars. Optional, defaults to
order. Layout name + date and
time when order was
received.
Machine Machine to use. Optional, unless the TRP
No. server run on a data
server. Must be a valid
machine No.
– Returned data:
’ack’ if the order was inserted in the order queue.
Example
For the example, the command looks like this:
RemoveLayoutFromQueue (Obsolete)
This command has been replaced by the new command RemoveOrder, see
page E-17. This command may be removed from future versions of TPSys
Remote Protocol (TRP).
RemoveLayoutFromQueue [LAST]
Remove the first (last) layout name in queue.
– Parameters:
LAST – Optional. Switch that causes command to remove last layout
in queue instead of first.
– Errors reported:
6 – Invalid parameter value. In this case probably invalid lastflag.
401 – Layout queue empty. Cannot remove items from a non existing
queue.
1000 – Cannot find the queue directory.
– Returned data:
’ack’ if a layout is removed from the layout queue.
RemoveOrder
RemoveOrder
Remove an order from queue.
– Parameters:
None
– Data
The data contains a newline separated list of field-data pairs.
Field names are separated from the data by a : (colon).
Field
Content Max size Comment
name
Order Id Identifies the 60 chars. Optional, defaults to
order. Layout name + date and
time when order was
received.
Machine Machine to use. Optional, must be a valid
No. machine No. If not
specified all orders with
the specified Id is
removed.
Example
For the example, the command looks like this:
SetProtocolVersion
SetProtocolVersion version
Set protocol version. Does nothing in present version but can be used in
future to make protocol behave as older versions. The protocol version
affects the command structures.
– Parameters:
version – String containing protocol version. Only valid value is 1.0.
– Errors reported:
6 – Invalid parameter value. Invalid protocol version.
– Returned data:
’ack’ if successful request.
ShowAlerts
ShowAlerts
Get current alert data. Returned data format will depend on verbose mode.
Not implemented.
– Parameters:
None
– Errors reported:
200 – This is not a TPSys machine.
– Returned data:
Not yet defined.
ShowCurrentStatus
ShowCurrentStatus
Get current assembly status. Not implemented.
– Parameters:
None
– Returned data:
current-layout – Is the name of the current layout (or empty string if
none loaded).
status – Is one of ASSEMBLE or IDLE.
Total-to-mount – Is the total number of components in layout.
No.-left-to-mount – Is the number of mount positions left to mount.
Not-available – Is number of mount positions that cannot be mounted
since component is missing.
Not-mountable – Is number of mount positions that cannot be
mounted since component is not mountable.
Layouts-produced – Is accumulated number of layouts produced.
Boards-produced – Is accumulated number of boards produced.
If the mode is VERBOSE, see VerboseMode, a prompt according to
the table below will precede each data.
ShowLayoutQueue (Obsolete)
This command has been replaced by the new command ListOrder, see page
E-11. This command may be removed from future versions of TPSys Remote
Protocol (TRP).
ShowLayoutQueue
List queue of layouts that should be assembled. The queue is created with
the commands LoadLayout (Obsolete) or QueueLayout (Obsolete).
– Parameters:
None
– Errors reported:
1000 – Cannot find the queue directory.
– Returned data:
’ackd’ followed by a newline-separated list of all layouts in the queue.
All layout lines start with S1;. Data ends with the E line.
ShowMessages
ShowMessages [ message-Id ]
Get messages. Optional messages newer than a specific Id. Not
implemented.
– Parameters:
message-Id – Id of last message received. Transmit only messages
newer than this Id.
– Returned data:
A list of message Id’s and messages. The format is one line per
message containing: Message-Id Message. The Id of the last message
could be used in next call to make sure the same message is not
transmitted twice.
ShowParameters
ShowParameters ParameterFileNumber [ ParameterNumber...]
Get parameter data.
– Parameters:
ParameterFileNumber – Parameter file number.
ParameterNumber – Optional parameter numbers. Space separated
argument list with parameter numbers.
– Errors reported:
500 – Failed to fetch all parameters in selected parameter file.
501 – Invalid parameter file number. Selected ParameterFileNumber
is not a valid parameter file number.
502 – Wrong number of arguments, the command needs at least a
parameter file number.
ShowRemoteMode
ShowRemoteMode
Find out if switch 0006 Mode is activated or not.
– Parameters:
None
– Returned data:
’ackd’ followed by:
ON – if remote mode is enabled.
OFF – if remote mode is disabled.
WAITING – if remote mode is enabled and machine is waiting for a
board or a layout name. The WAITING mode is not implemented and
will therefore never be exported. Data ends with the E line.
ShowRunningStatistics
ShowRunningStatistics
Get number of machine cycles and run-times. Not implemented.
– Parameters:
None
– Returned data:
Not yet defined.
Terminate
Terminate
Terminate connection. After this command is sent (and ’ack’ received) no
further commands are accepted.
– Returned data:
ack
VerboseMode
VerboseMode mode
Sets verbose mode. Default is OFF. Some commands return data in a
different format if verbose mode is ON or OFF.
– Parameters:
mode – Verbose mode. Allowed values are:
ON – Turn verbose mode on. More information in error
messages and returned data.
OFF – Turn verbose mode off. Minimum of information in
returned data.
– Errors reported:
6 – Invalid parameter value.
– Returned data:
’ack’ if VerboseMode has been changed to desired value.
List of Errors
Error
Meaning Explanation Returned by
code
1 Unknown command. Returned if the command is not a
valid TRP command.
6 Invalid parameter value. Given parameter has an invalid Delete, GetData, GetListOf,
value. Get List Size, GetTime,
RemoveLayoutFromQueue
(Obsolete),
SetProtocolVersion,
VerboseMode.
100 Unknown data type. Specified data type is unknown, in Delete, GetData, GetListOf,
other words not a valid data type Get List Size,
in TPSys. GetModifiedCount.
101 Item <name> does not Selected item does not exist in the Delete, GetData,
exist. database. ShowParameters.
102 Data parse error. Sent data is not following the PutData
syntax specified in TPSys external
interfaces specification.
103 <name> in use, cannot Not allowed to delete items that Delete
delete. currently is in use by TPSys.
104 Unexpected line. Sent data does not follow the PutData
syntax specified in TPSys
import/export data format
specification.
105 Unexpected end of file. Sent data is not ended as expected. PutData
106 Invalid argument. Invalid argument was given to PutData
PutData, probably a non valid
’parse flag’.
200 This is not a TPSys ShowAlerts
machine.
302 Cannot connect to TPSys servers are down, it is not ActivateUnsolicited,
eventserver. possible to connect to them. DeActivateUnsolicited.
303 Cannot start/stop Failed to connect to or disconnect ActivateUnsolicited,
subscription. from an unsolicited data source. DeActivateUnsolicited.
Eventserver is probably down.
Restart servers.
305 Server is not running. TPSys servers are down, it is not Delete, GetData, GetListOf,
possible to extract data from them. Get List Size,
GetModifiedCount, PutData.
400 No such layout. Selected layout is unknown, in LoadLayout (Obsolete),
other words does not exist in QueueLayout (Obsolete).
TPSys databases.
401 Layout queue empty. The layout queue does not contain RemoveLayoutFromQueue
any layouts. (Obsolete)
500 Failed to fetch all parameter No parameter values were found ShowParameters
values. in the selected parameter file. This
error will appear if the parameter
file only contains hidden
parameters or if some internal
error occurs.
501 Invalid parameter file Selected parameter file number is ShowParameters
number. not a valid parameter file number.
Error
Meaning Explanation Returned by
code
502 Wrong number of The command needs more ShowParameters
arguments. arguments.
503 Invalid parameter number. Selected parameter number is not ShowParameters
a valid number in selected
parameter file.
1000 Cannot find the queue LoadLayout (Obsolete),
directory. QueueLayout (Obsolete),
RemoveLayoutFromQueue
(Obsolete), ShowLayoutQueue
(Obsolete).
Mount data
TPSys data TRP data type
Layout data Layout
Panel data Panel
PCB data PCB
Fiducial mark data Refpoint
Magazine data
TPSys data TRP data type
Tape and stick magazine data Magazine
TEX/ATM tray data and TEX/ATM Pallet
pallet data
TEX/ATM tray data Pallettray
(Not valid for the following TRP
commands: GetData, GetListOf).
TWM tray data TWtray
YWM tray data YWtray
TEX/ATM tray position data Tetraypos
TEX/ATM tray position data Pallettraypos
(Not valid for the following TRP
commands: GetData, GetListOf).
TWM tray position data TWtraypos
YWM tray position data YWtraypos
Agilis tape guide data TapeGuide
Magazine kit data Kit
Auxiliary data
Unsolicited Messages
EventLog
US: EventLog;machine-name;message
US: R;EventLog;machine-name;message
Report event log messages as they are generated by TPSys.
When unsolicited EventLog message is activated, the server repeats the
last 1000 messages generated since system start. These repeated
messages are prefixed with an R;.
– Parameters
machine-name – Machine that generates the event log message.
message – The message. See separate event log export documentation
in Appendix C.
TimeStamp
US: timestamp;current-time
Send a time stamp message every second. This is more of a debug
function that can be used to ensure that the application can handle
unsolicited messages properly.
– Parameters
current-time – Current time in ’Weekday Month date HH:MM:SS
YYYY’ format.
MessageLog
US: MessageLog mtime mess
Indicates a message written to message log. Not implemented.
– Parameters:
mtime – A time stamp in hh:mm:ss-format (24 hour clock).
mess – The message.
Status
US: Status newstatus
Indicates current machine status. The machine status contains information
about the need for operator intervention. Not implemented.
– Parameters:
newstatus – The current (new) status. newstatus can have one of the
following values:
IDLE – The machine is in idle.
OK – Machine running. No problem.
NEED_OPERATOR – The operator is required but the
machine is still mounting (for instance a feeder has run out).
STOPPED – The machine has stopped for some reason and
requires an operator.
Introduction
Purpose
This chapter describes how to set up a Windows PC to connect to TPSys SQL
databases and retrieve data from the database into an Excel sheet.
This setup is tested on Windows XP SP3, Excel 2003 and QlikView 9.00 SR4.
Available data
The data available is in SQL views. The views are named mydbxxxxview_10
or mydbxxxxview_10_base.
Installation
http://www.postgresql.org/ftp/odbc/versions/msi/
Please note that even on 64-bit version of Windows 7, the 32 bit version should
be used.
Retrieving Data
Database: mydata_common_db
Password: viewsonly
Data to Excel
1. Start Excel and select a cell where you want your data to appear.
2. Select Data > Import External Data > New Database Query …
4. In the appearing window select Options..., set the check boxes as below
and click OK.
5. From the Add Tables window, select the datatype of your interest, for
instance ’component’, add it to the query and select Close.
6. Select the wanted columns from the component tables and drag them to
the area below the tables.
7. Close Microsoft Query and import the data into Excel by selecting OK.
Excel Example
Find out what packages are used in a specific PCB (FortKort Original).
8. Close Microsoft Query and insert the result into Excel and get the result.
Data to QlikView
The example below shows how to get some package, component, PCB, layout,
and carrier data to QlickView. This is just an example and it may not be that
useful as it is. It is possible to add more data by modifying the SQL statements
in the Script window to make it display the data you would like to see.
3. Connect to QDBC.
layoutsassembled,
totaltime,
totalassemblytime,
assemblytime,
assembled,
baddimension,
badeltest,
badpicked,
badplaced,
badother
FROM "mydata_common_db"."mydbmanlview_10".management;
SQL SELECT CarrierId,
ComponentName as component,
BatchId,
MagazineName,
Feeder,
CarrierType,
CarrierSubtype,
Angle,
Quantity,
Location
FROM "mydata_common_db"."mydbcarrview_10".carrier_magname;
7. Wait while data is read and click Add All to add the Available Fields to
Fields Displayed in Listboxes.
8. Move the Listboxes on the screen so you can see the data.
9. Now you can play with the data according to normal QlikView rules.
Edit Data
It is possible to change carrier data only. It is done by using ODBC and calling
a UPDATE or INSERT query on the mydbcarrview_10.carrier_magname
table view. Some of the parameters are ignored and some of them are
generated. This is described in Description of Columns.
ODBC Connection
Use the same parameters as for reading the database but different user name
and password
Password: mydata
Column Changes
There are two minor changes in the new carrier table. All defined values for
magazinename column are now uppercase. Therefore Unloaded becomes
UNLOADED and Discarded becomes DISCARDED. Alarm column has been
removed since it is not used any more.
Description of Columns
magazinename Set to UNLOADED / Set to UNLOADED Used Valid transitions are: UNLOADED -> DISCARDED, UNLOADED -> SHELVED
SHELVED -> UNLOADED
feeder Set to default / Set to default Ignored
carriertype Used / From similar last used Ignored Valid values: UNKNOWN, TAPE_MAG, VIB_MAG, TRAY_MAG, GFI_MAG
carriersubtype Used / From similar last used Ignored Has to be used in combination with carriertype and has to be valid for sp
carriertype set in that value (See 4.4)
angle Used / From similar last used Used
quantity Used / From similar last used Used Has to be greater than -1
amplitude From similar last used / From similar last used Ignored
duration From similar last used / From similar last used Ignored
frequency From similar last used / From similar last used Ignored
steplengthtrim From similar last used / From similar last used Ignored
xoffset From similar last used / From similar last used Ignored
servoadjustment From similar last used / From similar last used Ignored
hydrareachable From similar last used / From similar last used Ignored
yacc From similar last used / From similar last used Ignored
zacc From similar last used / From similar last used Ignored
quantityatnew Used / From similar last used Used Has to be greater than -1
maxtotaltime Used / From similar last used Used It is possible to change this value only for carriers without running timer
previousfeeder From similar last used / From similar last used Ignored
UPDATE mydbcarrview_10.carrier_magname
SET quantity = 102, location = 'Stock 25'
WHERE carrierid = '004828';
Index
A
Access on/off .............................................................................................................. 3-22
Attrition parameters ....................................................................................................... B-8
B
Backup
base name of the backup .............................................................................................. 6-5
host name or IP address ............................................................................................... 6-6
max. number of backups .............................................................................................. 6-5
restore specific data .................................................................................................... 6-8
type of automatic backup ............................................................................................. 6-5
type of backup restoring ............................................................................................... 6-7
use day of week or date ............................................................................................... 6-6
user name ................................................................................................................ 6-6
user password ........................................................................................................... 6-6
Barcode
filter file ................................................................................................................. 8-4
splitting a string ...................................................................................................... 8-17
testing filter ........................................................................................................... 8-19
Barcode filter ................................................................................................................ 8-2
Barcode filters ............................................................................................................. 8-11
Barcode translation ....................................................................................................... 8-11
Base name of the backup .................................................................................................. 6-5
Buzzer parameters ....................................................................................................... B-11
C
Client ......................................................................................................................... 4-1
Configure network .......................................................................................................... 4-2
Copy parameter group in Linux ......................................................................................... 3-34
D
Data areas .................................................................................................................... 5-3
Data sharing ................................................................................................................. 5-3
installing ................................................................................................................. 5-8
Data types .................................................................................................................... 5-3
Database copy ............................................................................................................... 5-7
Database refresh ............................................................................................................ 5-7
Deleting database contents .............................................................................................. 3-35
DHCP server ................................................................................................................ 4-2
E
Edit parameters ............................................................................................................ 3-32
Event Log
export format .......................................................................................................... C-1
Event log .................................................................................................................... C-1
Exporting
Directline ................................................................................................................ 7-7
FTP ....................................................................................................................... 7-7
UNIX/NFS .............................................................................................................. 7-7
USB flash drive ........................................................................................................ 7-7
F
Feeder shutdown parameter .............................................................................................. B-8
File transfer protocol FTP ................................................................................................. 4-6
Filter file ..................................................................................................................... 8-2
editing ................................................................................................................... 8-4
Fixed IP ...................................................................................................................... 4-2
FTP ........................................................................................................................... 4-6
G
Greedy matches ........................................................................................................... 8-16
H
Home directory TPSys ................................................................................................... 3-10
L
Light tower parameters .................................................................................................. B-11
Linux
boot ....................................................................................................................... 2-2
cat ........................................................................................................................ 2-9
cd ......................................................................................................................... 2-9
cp ....................................................................................................................... 2-10
diff ...................................................................................................................... 2-10
directories ............................................................................................................... 2-3
dmesg .................................................................................................................. 2-10
double brackets ......................................................................................................... 2-5
emacs .................................................................................................................. 2-10
fdformat ............................................................................................................... 2-11
files ....................................................................................................................... 2-3
grep ..................................................................................................................... 2-12
I/O-streams .............................................................................................................. 2-5
inittab .................................................................................................................... 2-3
less ..................................................................................................................... 2-13
logon session ............................................................................................................ 2-2
ls ........................................................................................................................ 2-13
mcopy .................................................................................................................. 2-14
mdir .................................................................................................................... 2-14
mformat ................................................................................................................ 2-15
mkdir ................................................................................................................... 2-15
mv ...................................................................................................................... 2-15
passwd ................................................................................................................... 2-3
Passwd file .............................................................................................................. 2-2
profile .................................................................................................................... 2-3
pwd ..................................................................................................................... 2-15
reboot .................................................................................................................. 2-18
redirect standard error to file ......................................................................................... 2-5
redirect standard in from file ......................................................................................... 2-5
redirect standard out to file ........................................................................................... 2-5
rm ....................................................................................................................... 2-16
rmdir ................................................................................................................... 2-16
set a symbol ............................................................................................................. 2-5
shell ...................................................................................................................... 2-4
show value of symbol .................................................................................................. 2-6
shutdown .............................................................................................................. 2-18
standard error ........................................................................................................... 2-5
standard in ............................................................................................................... 2-5
standard out ............................................................................................................. 2-5
stderr ..................................................................................................................... 2-5
stdin ...................................................................................................................... 2-5
stdout ..................................................................................................................... 2-5
tar ....................................................................................................................... 2-17
terminfo .................................................................................................................. 2-3
top ...................................................................................................................... 2-17
tty ....................................................................................................................... 2-17
user ID ................................................................................................................... 2-2
vi .............................................................................................................. 2-15, 2-17
who ..................................................................................................................... 2-18
Logon session Linux ........................................................................................................ 2-2
M
Magazine parameters ...................................................................................................... B-8
Magazine shutdown parameter ........................................................................................... B-8
I-2 Rev. A 2016-04 4002720-EN – Software Manual
Mycronic TPSys 3.3 Index
N
Name server ................................................................................................................. 4-3
Network ...................................................................................................................... 4-2
No hard disk activity ....................................................................................................... 3-6
No terminal response ....................................................................................................... 3-6
P
Parameters ......................................................................................................... 3-32, B-1
buzzer ................................................................................................................. B-11
edit ..................................................................................................................... 3-32
light tower ............................................................................................................ B-11
magazine reject percent .............................................................................................. B-8
magazine shutdown ................................................................................................... B-8
tool calibration ......................................................................................................... B-2
Parameters window
entries .................................................................................................................. 3-33
function keys .......................................................................................................... 3-32
Passwd file Linux ........................................................................................................... 2-2
Ping ........................................................................................................................... 4-5
Preferences ......................................................................................................... 3-32, B-1
R
Refresh database ............................................................................................................ 5-7
Regular expression ......................................................................................................... 8-4
Reject parameters .......................................................................................................... B-8
REPEAT ................................................................................................................... 8-18
Restore a backup ............................................................................................................ 6-7
Restore specific data ........................................................................................................ 6-8
Running stepper ........................................................................................................... 3-13
S
Save status ................................................................................................................. 3-30
Screen dumps .............................................................................................................. 3-12
Serial start .................................................................................................................... 8-2
Server ................................................................................................................. 4-1, 5-2
Settings ............................................................................................................. 3-32, B-1
Shell .......................................................................................................................... 2-4
Standalone server ........................................................................................................... 5-2
Startup menu TPSys ........................................................................................................ 3-9
Stepper ..................................................................................................................... 3-13
T
Terminal does not respond ................................................................................................ 3-5
Text editor ................................................................................................................. 2-10
Tool calibration ............................................................................................................ B-2
TPSys
differences in off-line menu ........................................................................................ 3-12
home directory ........................................................................................................ 3-10
kill current process ..................................................................................................... 3-5
modify user ........................................................................................................... 3-18
no hard disk activity ................................................................................................... 3-6
no terminal response ................................................................................................... 3-6
off-line terminals ..................................................................................................... 3-12
running stepper ....................................................................................................... 3-13
serial number ........................................................................................................... 3-8
set time .................................................................................................................. 3-6
show machine type and serial ........................................................................................ 3-8
Startup menu ............................................................................................................ 3-9
terminal does not respond ............................................................................................. 3-5
user access system on/off ........................................................................................... 3-22
TPSys remote protocol ..................................................................................................... E-1
Troubleshooting
vision .................................................................................................................. 3-29
TRP ........................................................................................................................... E-1
U
USB flash drives ............................................................................................................ 2-4
User Access System on/off .............................................................................................. 3-22
User list
Access rights .......................................................................................................... 3-19
modify user information ............................................................................................. 3-18
V
Variables ................................................................................................................... 8-14
Vision
image log .............................................................................................................. 3-29
troubleshooting ....................................................................................................... 3-29
enter
<Enter>
Single mount Bank Size (mm) Cross section
tools position
<NumLock>
C14 15 0.25
A12 1 0.8
A13 2 1.2
A14S 3 2.0
<PgUp>/<PgDn>
clear
A23 4 3.0
A23S 4 3.0
A24 5 5.0
down
page
page
up
A24S 5 5.0
home
end
16 8.0
<Ins>/<F13>
C23
<Del>
F13
delete
16 8.0
C23S
<Ctrl>
<Enter>
control
Size (mm) Cross section
return
position
A34 6 1.5
F12
B24 11 2.3
option
alt
B23 10 2.5
MY100 keyboard
F11
<Alt>
B34 12 2.0
command
Glue tools Bank Size (mm) Cross section
F10
position
C12 13 0.5
B12 7 0.8
F9
B13 8 1.5
C13 14 2.2
F8
B14 9 3.2
HYDRA tool
F7
H09 0.29
H07 0.4
F5
H01 0.5
H02 0.7
F4
H10 0.7
H04 0.9
H03 1.0
F3
command
H05 2.8
F2
<Alt>
option
F1
alt
<Ctrl>
<Esc>
control
esc
English
TPSys™ 3.3 Software Manual