4002720-En Software Manual Tpsys 3.3 English A

TPSys™ 3.
3
Software Manual
Original Instructions
English
4002720-EN Rev. A 2016-04

Mycronic TPSys 3.3 Preface
TPSys™ 3.3
Software Manual
English
4002720-EN – Software Manual Rev. A 2016-04 i

Preface TPSys 3.3 Mycronic
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.
Do not start, operate or service the

machine until you have read and
understood the safety chapter.
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.
Mycronic AB, PO Box 3141, SE-183 03 Täby, Sweden.

Phone +46 8 638 52 00 – Fax +46 8 638 52 90 – www.mycronic.com
This document or parts of it may not be reproduced without a written permission of Mycronic AB.
Infringements will be prosecuted. All rights reserved.
Copyright © Mycronic AB, Sweden, 1990–2016.
ii Rev. A 2016-04 4002720-EN – Software Manual

Table of Contents
New Features Overview ................................................................................................... -xii
Text Conventions ............................................................................................................. -xiii

Danger, Warning, Caution, and Note ................................................................... -xiii
Italic Font ............................................................................................................. -xiv
Bold Font ............................................................................................................. -xiv
Menu Selections ................................................................................................... -xiv
Lists ...................................................................................................................... -xiv
1. Software Overview ................................................................................................... 1-1

Linux, TPSys and Service Program ................................................................... 1-1
Linux ............................................................................................................. 1-1
TPSys ............................................................................................................ 1-1
Service Program ............................................................................................ 1-1
Software Solutions ............................................................................................. 1-2
MYCam ........................................................................................................ 1-2
Data Sharing ................................................................................................. 1-2
MYCenter ..................................................................................................... 1-2
MYPlan ......................................................................................................... 1-3
MYLabel ....................................................................................................... 1-3
MYTrace ....................................................................................................... 1-3
FlowLine ....................................................................................................... 1-3
2. Linux ......................................................................................................................... 2-1

Linux Kernel ...................................................................................................... 2-2
Users and Root ................................................................................................... 2-2
Drivers ................................................................................................................ 2-2
Files and Directories .......................................................................................... 2-3
Important Files .............................................................................................. 2-3
Important Directories .................................................................................... 2-3
USB Flash Drives .............................................................................................. 2-4
The 'bash' Program ............................................................................................. 2-4
Standard I/O ....................................................................................................... 2-5
Process Environment and Symbols .................................................................... 2-5
Symbolic Links .................................................................................................. 2-6
Pipes ................................................................................................................... 2-6
The 'proc' File System ........................................................................................ 2-7
Common Linux Commands and Utilities .......................................................... 2-7
Flags and Arguments .................................................................................... 2-8
Special Characters ........................................................................................ 2-8
Wild Cards .................................................................................................... 2-9
Command Descriptions ................................................................................ 2-9
Shutdown ........................................................................................................... 2-18
3. TPSys ........................................................................................................................ 3-1

Introduction ........................................................................................................ 3-2
Virtual Terminals ............................................................................................... 3-3
Login Instructions .............................................................................................. 3-4
'tpsys' ............................................................................................................. 3-4
'root' .............................................................................................................. 3-4
Hang-Up ............................................................................................................. 3-5
Terminal Hang-Up ........................................................................................ 3-5
System Hang-Up ........................................................................................... 3-6
Setting Time ....................................................................................................... 3-6
NTP Setup .......................................................................................................... 3-7
Machine Serial Number ..................................................................................... 3-8
4002720-EN – Software Manual Rev. A 2016-04 iii

Time Lock .......................................................................................................... 3-8

TPSys Startup Programs ..................................................................................... 3-9
TPSys Versions and Directory Tree ................................................................... 3-10
More Than One TPSys Version .................................................................... 3-10
TPSys Directory Tree .................................................................................... 3-11
Offline Terminal ................................................................................................. 3-12
Making TPSys Screenshots ................................................................................ 3-12
Stepper Feature ................................................................................................... 3-13
The Stepper Message Window ...................................................................... 3-14
Logoff and System Shutdown ............................................................................ 3-17
Logging Off From Linux ............................................................................... 3-17
Shutdown From TPSys ................................................................................. 3-17
Shutdown From Linux .................................................................................. 3-17
Users Window .................................................................................................... 3-18
Command Keys ............................................................................................. 3-18
Names ............................................................................................................ 3-18
Data ............................................................................................................... 3-19
Security On/Off ............................................................................................. 3-22
Log On/Off .................................................................................................... 3-22
TPSys Web Interface .......................................................................................... 3-23
Accessing the Web Interface ......................................................................... 3-24
Preferences .................................................................................................... 3-24
Viewing Assembly Data ................................................................................ 3-24
Generating Traceability Reports ................................................................... 3-24
Generating Error Reports .............................................................................. 3-24
Monitoring Machine Utilization .................................................................... 3-25
Viewing Machine Messages .......................................................................... 3-25
Monitoring Machine Performance ................................................................ 3-26
Printing .......................................................................................................... 3-28
Camera Image Log ........................................................................................ 3-28
System Save Status ............................................................................................. 3-30
TPSys Terminates in an Unnatural Way ....................................................... 3-30
Creating a System Save Status from TPSys .................................................. 3-31
Creating a System Save Status from the Web Interface ................................ 3-31
Parameters .......................................................................................................... 3-32
Parameter Structure ....................................................................................... 3-32
Opening the Parameters Window .................................................................. 3-32
Command Keys ............................................................................................. 3-32
Parameter Groups .......................................................................................... 3-33
Editing Parameters ........................................................................................ 3-33
Miscellaneous Parameter Information .......................................................... 3-33
Ticks .............................................................................................................. 3-34
Deleting TPSys Data .......................................................................................... 3-35
Deleting a Specific Data Type ...................................................................... 3-35
Deleting all Data ............................................................................................ 3-36
Restoring Default Data .................................................................................. 3-36
4. Network and File Sharing .......................................................................................... 4-1

Network Configuration ....................................................................................... 4-2
TPSys Network Settings ............................................................................... 4-2
Adding Machines to the Network ................................................................. 4-3
Testing the Network with Ping ...................................................................... 4-5
Transferring Files Using FTP ............................................................................. 4-6
Using FTP from Linux .................................................................................. 4-6
Using FTP from Windows ............................................................................ 4-7
5. Data Sharing .............................................................................................................. 5-1

TPSys Databases ................................................................................................ 5-2
Data Areas ..................................................................................................... 5-3
iv Rev. A 2016-04 4002720-EN – Software Manual

Data Types .................................................................................................... 5-3

Backup and Restore ...................................................................................... 5-5
Event Log, Parameters and Calibration Data ............................................... 5-6
Database Copies ............................................................................................ 5-7
Installing Data Sharing ...................................................................................... 5-8
Preparations .................................................................................................. 5-8
Taking a Backup of Existing Data ................................................................ 5-8
Setting up the Server's Data Sharing ............................................................ 5-9
Linking the Machine to the Server ............................................................... 5-9
Setting up the Machine’s Data Sharing ........................................................ 5-10
Restore Backup ............................................................................................. 5-11
Repeat for Other Machines ........................................................................... 5-11
Data Sharing Maintenance ................................................................................. 5-12
Disconnecting a Machine ............................................................................. 5-12
Reconnecting a Machine ............................................................................... 5-13
Moving Data from Private to Shared Area ................................................... 5-14
Moving Data from Shared to Private Area ................................................... 5-15
6. Backup and Restore .................................................................................................. 6-1

Backing up ......................................................................................................... 6-2
UNIX/NFS .................................................................................................... 6-3
FTP ............................................................................................................... 6-3
USB flash drive ............................................................................................. 6-4
Scheduled Backup .............................................................................................. 6-5
Restoring ............................................................................................................ 6-7
Carrier Restore after Hard Disk Change ....................................................... 6-9
7. Import/Export TPSys ................................................................................................ 7-1

Import and Export Formats ................................................................................ 7-2
TPSys Format ............................................................................................... 7-2
Directline Format .......................................................................................... 7-2
Manual Importing .............................................................................................. 7-3
Selecting Format ........................................................................................... 7-3
Selecting Channel ......................................................................................... 7-4
Selecting Source ........................................................................................... 7-4
Selecting Item Names ................................................................................... 7-5
Automatic Importing .......................................................................................... 7-6
Settings ......................................................................................................... 7-6
Importing with the Automatic Import Utility ............................................... 7-6
Exporting ............................................................................................................ 7-7
Selecting Data Category ............................................................................... 7-7
Selecting Channel ......................................................................................... 7-7
Selecting Items .............................................................................................. 7-8
Selecting Destination .................................................................................... 7-8
8. Barcode Translation .................................................................................................. 8-1

Barcode Systems ................................................................................................ 8-1
Serial Start Scanners .......................................................................................... 8-2
Handheld Barcode Scanner ................................................................................ 8-2
Barcode Scanning with X-Wagon Camera ........................................................ 8-3
Editing Filter Files ............................................................................................. 8-4
Regular Expressions ........................................................................................... 8-4
Meta Characters ................................................................................................. 8-5
Number of Matches ...................................................................................... 8-7
Bracket Expressions ...................................................................................... 8-9
Filters ................................................................................................................. 8-11
Multiple Filters ............................................................................................. 8-13
Variables in Filters ........................................................................................ 8-14
Greedy Matches ............................................................................................ 8-16
4002720-EN – Software Manual Rev. A 2016-04 v

Case Sensitive ............................................................................................... 8-16

Matching Meta Characters as Normal Characters ......................................... 8-17
Splitting a String ........................................................................................... 8-17
The REPEAT Command ............................................................................... 8-18
Comment Lines ............................................................................................. 8-18
More Information ............................................................................................... 8-19
Testing the Barcode Translation Filter File ........................................................ 8-19
Basic Filters Quick Reference ............................................................................ 8-20
Real-Life Filters ................................................................................................. 8-21
Filters for Adding Characters ........................................................................ 8-22
Filters for Splitting Strings ............................................................................ 8-26
Filters for Repeating Strings ......................................................................... 8-32
Blocking Garbage Strings ............................................................................. 8-33
Appendix A – Messages Reference Guide .................................................................... A-1

Introduction ....................................................................................................... A-1
Message Severity ............................................................................................... A-1
General Message Format ................................................................................... A-2
Message Groups ................................................................................................ A-3
Messages By Group ........................................................................................... A-6
Conventions .................................................................................................. A-6
AUTOFID Group ......................................................................................... A-6
AUTOTEACH Group .................................................................................. A-8
AXIS Group ................................................................................................. A-10
BACKUP Group .......................................................................................... A-12
BADBOARD Group .................................................................................... A-12
BC Group ..................................................................................................... A-14
XWBC Group ............................................................................................... A-20
BRDH Group ................................................................................................ A-20
CALIBRATION Group ................................................................................ A-21
CAME Group ............................................................................................... A-21
DATAS Group ............................................................................................. A-21
EXORD Group ............................................................................................. A-21
EXP Group ................................................................................................... A-22
FTP Group .................................................................................................... A-22
GLU Group .................................................................................................. A-23
GRAP Group ................................................................................................ A-23
HEATMON Group ....................................................................................... A-24
HOPT Group ................................................................................................ A-24
HRDW Group .............................................................................................. A-24
HTLM Group ............................................................................................... A-27
HWICLIENT Group .................................................................................... A-29
IMAGE_ORDER Group .............................................................................. A-30
IMGPROC Group ........................................................................................ A-30
IMP Group .................................................................................................... A-30
IMPORTD Group ......................................................................................... A-35
LSCD Group ................................................................................................ A-35
MAGREF Group .......................................................................................... A-36
MHPR Group ............................................................................................... A-37
MIPR Group ................................................................................................. A-41
MMI Group .................................................................................................. A-44
MNTSYNC Group ....................................................................................... A-46
MONT Group ............................................................................................... A-46
MOT Group .................................................................................................. A-56
MOTIONDEV Group .................................................................................. A-107
MOTQ Group ............................................................................................... A-107
OPTCENT Group ......................................................................................... A-109
OPTCORR Group ........................................................................................ A-119
OPTP Group ................................................................................................. A-121
ORGP Group ................................................................................................ A-123
vi Rev. A 2016-04 4002720-EN – Software Manual

OSM Group .................................................................................................. A-125

PARFILE Group ........................................................................................... A-125
QWIN Group ................................................................................................ A-126
SERCOM Group ........................................................................................... A-126
SERSTART Group ....................................................................................... A-127
SHDB Group ................................................................................................ A-128
TCP Group .................................................................................................... A-129
TEX VISION Group ..................................................................................... A-129
TLMN Group ................................................................................................ A-132
UCOPY Group .............................................................................................. A-135
UNIX Group ................................................................................................. A-135
USR Group ................................................................................................... A-135
VACC Group ................................................................................................ A-136
VER Group ................................................................................................... A-136
VISION Group .............................................................................................. A-137
XINSP group ................................................................................................ A-138
Appendix B – Parameters ............................................................................................... B-1

1 Axis ................................................................................................................. B-1
5 Y axis .............................................................................................................. B-1
21 Z-mount component ...................................................................................... B-2
23 Tool manager ................................................................................................ B-2
24 HYDRA-mount component .......................................................................... B-3
32 Reject positions ............................................................................................. B-3
33 Dip Unit ........................................................................................................ B-4
41 Vision ............................................................................................................ B-5
45 Autoteach ...................................................................................................... B-6
46 X Wagon Camera Illumination ..................................................................... B-7
64 HYDRA camera calibration .......................................................................... B-7
65 Optical calibration standard camera .............................................................. B-7
68 Optical calibration HRC camera ................................................................... B-8
69 Optical calibration standard camera 2 ........................................................... B-8
70 Optical calibration HRC camera 2 ................................................................ B-8
84 Magazine ....................................................................................................... B-8
123 Barcode ....................................................................................................... B-10
233 Operator attention signals ........................................................................... B-11
Appendix C – Event Log Export Format ....................................................................... C-1

General Format Information .............................................................................. C-2
Character Substitution .................................................................................. C-2
Time Format ................................................................................................. C-2
Comment for Parser Implementers ............................................................... C-2
Event Lines ........................................................................................................ C-3
Header ........................................................................................................... C-4
Time Stamp ................................................................................................... C-5
Mount Information Lines .............................................................................. C-5
Magazine Data Lines .................................................................................... C-10
External Event Lines ..................................................................................... C-11
Obsolete Mount Information Lines .............................................................. C-14
Appendix D – Import/Export Data Formats ................................................................... D-1

Formats .............................................................................................................. D-2
Data Line Format .......................................................................................... D-2
General Data Formats ................................................................................... D-2
Special Enumerated Data Types ................................................................... D-5
Layout Data Format ........................................................................................... D-6
Name ............................................................................................................. D-6
Barcode ......................................................................................................... D-6
Comment ....................................................................................................... D-6
4002720-EN – Software Manual Rev. A 2016-04 vii

Unit Code ..................................................................................................... D-6

Board Name .................................................................................................. D-7
Panel Name .................................................................................................. D-7
Machine Name ............................................................................................. D-7
Fiducial Marks .............................................................................................. D-7
Conveyor Data .............................................................................................. D-8
Auxiliary Layout Data .................................................................................. D-8
Layout Data Examples ................................................................................. D-9
Panel Data Format ............................................................................................. D-10
Name ............................................................................................................ D-10
Comment ...................................................................................................... D-10
Unit Code ..................................................................................................... D-10
Tools ............................................................................................................. D-10
Fiducial Marks .............................................................................................. D-11
Test Positions ............................................................................................... D-11
Barcode Positions ......................................................................................... D-11
PCB Name .................................................................................................... D-12
PCB Fiducial Marks ..................................................................................... D-12
Auxiliary Panel Data .................................................................................... D-12
Obsolete Lines .............................................................................................. D-13
Panel Data Examples .................................................................................... D-14
PCB Data Format .............................................................................................. D-15
Name ............................................................................................................ D-15
Comment ...................................................................................................... D-15
Tools ............................................................................................................. D-15
Unit Code ..................................................................................................... D-16
Fiducial Marks .............................................................................................. D-16
Test Positions ............................................................................................... D-16
Barcode Positions ......................................................................................... D-17
Mount Positions (Items) ............................................................................... D-17
Mount Position Location .............................................................................. D-18
Local Fiducial Mark ..................................................................................... D-18
Mount Position Flags ................................................................................... D-19
Auxiliary Data .............................................................................................. D-19
Obsolete Lines .............................................................................................. D-19
PCB Data Examples ..................................................................................... D-21
Fiducial Mark Data Format ............................................................................... D-22
Name ............................................................................................................ D-22
Comment ...................................................................................................... D-22
Type .............................................................................................................. D-22
Circular Fiducial Mark Data ........................................................................ D-23
Rectangular Fiducial Mark Data .................................................................. D-23
Triangular Fiducial Mark Data ..................................................................... D-23
Cross Fiducial Mark Data ............................................................................ D-24
Butterfly Fiducial Mark Data ....................................................................... D-25
Color ............................................................................................................. D-25
Search Area and Search Method .................................................................. D-25
Illumination Type and Illumination Level ................................................... D-26
Generic Fiducial Mark Teach Status ............................................................ D-26
Generic Fiducial Mark Data ......................................................................... D-26
Obsolete Lines .............................................................................................. D-28
Fiducial Mark Data Examples ...................................................................... D-30
Package Data Format ......................................................................................... D-31
Name ............................................................................................................ D-31
Type .............................................................................................................. D-31
Geometric Data ............................................................................................ D-31
Handling Data .............................................................................................. D-32
Accelerations Data ....................................................................................... D-33
HYDRA Data and Presentation Angle Data ................................................ D-34
Lead toggling Data ....................................................................................... D-34
viii Rev. A 2016-04 4002720-EN – Software Manual

Lead Groups Data ......................................................................................... D-35

Lead Dimensions Data .................................................................................. D-36
General Centering Data ................................................................................ D-37
Dip Centering Data ....................................................................................... D-38
Optical Centering Data ................................................................................. D-39
Index Mark Type .......................................................................................... D-42
Optical Centering Data ................................................................................. D-42
Index Mark Data ........................................................................................... D-43
Glue Dot Data ............................................................................................... D-43
Obsolete Lines .............................................................................................. D-44
Component Data Format .................................................................................... D-47
Component Name ......................................................................................... D-47
Package Name .............................................................................................. D-47
Comment ....................................................................................................... D-47
Stock Location Data ..................................................................................... D-47
Skip Flags ..................................................................................................... D-48
Polarization and Reject ................................................................................. D-48
Electrical Test ............................................................................................... D-49
Barcode ......................................................................................................... D-49
Feeder Type .................................................................................................. D-50
Magazine Type ............................................................................................. D-50
Magazine Data .............................................................................................. D-51
Obsolete Lines .............................................................................................. D-51
Examples ....................................................................................................... D-52
Glue Dot Data Format ........................................................................................ D-54
Name ............................................................................................................. D-54
Comment ....................................................................................................... D-54
Tool ............................................................................................................... D-54
Settings ......................................................................................................... D-54
Examples ....................................................................................................... D-55
Magazine Data Format ....................................................................................... D-56
Line Type Combinations .............................................................................. D-56
Magazine ....................................................................................................... D-57
Tape and Stick Feeder Contents ................................................................... D-59
Cavity Contents ............................................................................................ D-59
Tray Contents ................................................................................................ D-60
Tape Feeder Data .......................................................................................... D-60
TEX Tray Data ............................................................................................. D-61
YWM and TWM Tray Data ......................................................................... D-61
Stick Feeder Data .......................................................................................... D-62
Tray Position ................................................................................................. D-62
Obsolete Lines .............................................................................................. D-63
Magazine Data Examples ............................................................................. D-65
Tray Type Data Format ...................................................................................... D-66
Name ............................................................................................................. D-66
Package For Teaching ................................................................................... D-67
Size ............................................................................................................... D-67
Rows and Columns ....................................................................................... D-67
Fiducial Marks .............................................................................................. D-67
Pocket Size .................................................................................................... D-68
Pre-Pick Inspection Data .............................................................................. D-68
Tray Type Data Examples ............................................................................ D-68
Tray Position Data Format ................................................................................. D-69
Name ............................................................................................................. D-69
Data ............................................................................................................... D-69
Magazine ....................................................................................................... D-69
Machine Number .......................................................................................... D-70
Tray Position Data Examples ....................................................................... D-70
Removable Feeder Data Format ........................................................................ D-70
Name and Number ........................................................................................ D-71
4002720-EN – Software Manual Rev. A 2016-04 ix

Comment ...................................................................................................... D-71

Step and Trim Data ...................................................................................... D-71
Contents ........................................................................................................ D-71
Magazine Information .................................................................................. D-72
Obsolete Lines .............................................................................................. D-72
Removable Feeder Data Examples .............................................................. D-73
Magazine Kit Data Format ................................................................................ D-73
Special Enumerated Data Types .................................................................. D-73
Magazine Kit Name ..................................................................................... D-77
Comment ...................................................................................................... D-77
Magazine ...................................................................................................... D-77
Tray Magazine .............................................................................................. D-78
Magazine Slot ............................................................................................... D-78
Feeder Contents ............................................................................................ D-79
Pick Position ................................................................................................. D-79
Located Tray Position .................................................................................. D-80
Predefined Tray Position .............................................................................. D-80
Refill ............................................................................................................. D-80
HYDRA Reachable Tray ............................................................................. D-80
Stepping ........................................................................................................ D-81
Quantity ........................................................................................................ D-81
Tray Accelerations ....................................................................................... D-81
Obsolete Lines .............................................................................................. D-82
Management Data Format ................................................................................. D-82
Layout ........................................................................................................... D-82
Machine ........................................................................................................ D-83
Assembled Layouts ...................................................................................... D-83
Assembled Boards ........................................................................................ D-83
Assembly Time ............................................................................................ D-83
Component ................................................................................................... D-83
Component Statistics .................................................................................... D-84
Management Data Examples ........................................................................ D-85
TEX Data Format .............................................................................................. D-85
Name ............................................................................................................ D-85
Comment ...................................................................................................... D-85
Serial Number and Type Code ..................................................................... D-85
Calibration Data ........................................................................................... D-86
User Data Format .............................................................................................. D-86
Name ............................................................................................................ D-86
Password ....................................................................................................... D-87
Access Data .................................................................................................. D-87
Checksum ..................................................................................................... D-88
Appendix E – TPSys Remote Protocol ........................................................................... E-1

Establish Connection .......................................................................................... E-2
Testing Single TRP Commands ......................................................................... E-2
Quick Reference ................................................................................................. E-3
General Command Format ................................................................................. E-4
Special Line Types ............................................................................................. E-4
TRP Commands ................................................................................................. E-5
ActivateUnsolicited ....................................................................................... E-5
DeActivateUnsolicited .................................................................................. E-5
Delete ............................................................................................................ E-6
ExitRemoteMode .......................................................................................... E-6
GetData .......................................................................................................... E-7
GetDataVersion ............................................................................................. E-8
GetListOf ....................................................................................................... E-8
Get List Size .................................................................................................. E-9
GetModifiedCount ........................................................................................ E-9
GetProtocolVersion ....................................................................................... E-10
x Rev. A 2016-04 4002720-EN – Software Manual

GetTime ........................................................................................................ E-10

Help ............................................................................................................... E-11
ListOrder ....................................................................................................... E-11
LoadLayout (Obsolete) ................................................................................. E-12
MachineInfo .................................................................................................. E-12
Ping ............................................................................................................... E-14
PutData ......................................................................................................... E-14
PutEcho ......................................................................................................... E-15
QueueLayout (Obsolete) ............................................................................... E-15
QueueOrder ................................................................................................... E-16
RemoveLayoutFromQueue (Obsolete) ......................................................... E-17
RemoveOrder ................................................................................................ E-17
SetProtocolVersion ....................................................................................... E-18
ShowAlerts ................................................................................................... E-19
ShowCurrentStatus ....................................................................................... E-19
ShowLayoutQueue (Obsolete) ...................................................................... E-20
ShowMessages .............................................................................................. E-20
ShowParameters ........................................................................................... E-20
ShowRemoteMode ....................................................................................... E-21
ShowRunningStatistics ................................................................................. E-21
Terminate ...................................................................................................... E-21
VerboseMode ................................................................................................ E-22
List of Errors ...................................................................................................... E-23
TPSys Data Types .............................................................................................. E-25
Unsolicited Messages ......................................................................................... E-26
EventLog ....................................................................................................... E-26
TimeStamp .................................................................................................... E-26
MessageLog .................................................................................................. E-26
Status ............................................................................................................. E-27
Appendix F – TPSys SQL Interface Setup ..................................................................... F-1

Introduction ........................................................................................................ F-1
Purpose ......................................................................................................... F-1
Available data ............................................................................................... F-1
Installation .......................................................................................................... F-2
Add PostgreSQL ODBC Driver ................................................................... F-2
Retrieving Data .................................................................................................. F-3
Windows Data Source Setup ........................................................................ F-3
Retrieving Data from the Database ............................................................... F-4
Data to QlikView .......................................................................................... F-8
Edit Data ............................................................................................................ F-13
ODBC Connection ........................................................................................ F-13
Column Changes ........................................................................................... F-13
Insert Query Logic ........................................................................................ F-13
Valid Carrier Subtypes ................................................................................. F-14
Description of Columns ................................................................................ F-15
Insert Carrier Query Sample ......................................................................... F-16
Update Carrier Query Sample ...................................................................... F-16
Create Container Query Sample ................................................................... F-16
Delete Container Query Sample ................................................................... F-16
Index ................................................................................................................................ I-1
4002720-EN – Software Manual Rev. A 2016-04 xi

New Features Overview

In this version of the manual, the following changes have been made to reflect
TPSys 3.3:
• 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.
xii Rev. A 2016-04 4002720-EN – Software Manual

Text Conventions
This document uses text conventions to present information in various
situations. This is explained below.
Danger, Warning, Caution, and Note

In this document a particular text layout is used to make danger, warning, and
caution information evident. A triangular icon identifies the type of risk and
the text describes the risk.
Danger, warning, and caution information must be followed.

Assisting information, notes, have the same layout but never triangular icons.
Danger
 DANGER! Danger means a potentially dangerous situation that can cause

death or severe bodily injury. The icon identifies the type of risk.
Warning
 WARNING! Warning means a potentially dangerous situation that can cause

bodily injury or considerable damage to the system or equipment. The icon
identifies the type of risk.
Caution
 CAUTION! Caution means that the system or equipment can be damaged or

data be lost. To distinguish caution information from warning and danger
information, this icon is always an empty triangle.
Note, example 1
 A note contains any type of assisting information.
Note, example 2
 One type of assisting information is tips, which normally have this icon.
4002720-EN – Software Manual Rev. A 2016-04 xiii

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. Perform this step first.

2. Perform this step second.
xiv Rev. A 2016-04 4002720-EN – Software Manual

Mycronic TPSys 3.3 Software Overview
1. Software Overview
This chapter contains a brief overview of software used to run Mycronic pick
and place machines.
Linux, TPSys and Service Program

Linux, TPSys and a Service program are essential for operation of a Mycronic
pick and place machine. They are therefore always provided with the machine.
Linux
The operating system used in the Mycronic pick and place machines is Linux.
Linux is a multi-user and multi-tasking operating system, which TPSys

utilizes by using many terminals and running several processes
simultaneously.
Linux operating system is described in Chapter 2.
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.
TPSys software is described in Chapter 3.
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.
4002720-EN – Software Manual Rev. A 2016-04 1-1

Software Overview TPSys 3.3 Mycronic
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.
MYCam is a software package used to convert a wide range of CAD data, to

do offline programming and to transfer data to and from Mycronic machines
in a network from a remote PC.
The following transfer procedures can be performed by using MYCam:
• Transfer converted CAD files to Mycronic machines.

MYCam
• Retrieve production data.
• Server backup.
The MYCam software package includes a comprehensive user's manual.
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.
Data sharing can contain the following data types:
• Component data.
Data sharing • Package data.

• Magazine data.
• Tray data.
• Mount data.
• User data.
Data sharing is described in Chapter 5.
MYCenter
MYCenter is a software package used to convert CAD files containing

placement data to TPSys in order to use the data for component placing.
MYCenter™
The MYCenter software package includes a comprehensive MYCenter, User’s
User´s Manual
Manual.
P-000-0000-EN Rev. A 2014-12
1-2 Rev. A 2016-04 4002720-EN – Software Manual

Mycronic TPSys 3.3 Software Overview
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.
The MYPlan software package includes a comprehensive MYPlan, User’s

Manual.
P-000-0000-EN Rev. A 2014-12
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.
The MYLabel software package includes a comprehensive MYLabel, User’s

Manual.
User’s Manual
English
abc0001:4711:0002
P-010-0189-EN
P-000-0000-EN Rev. A 2014-12
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
The MYTrace software package includes a comprehensive MYTrace, User’s

Manual.
P-000-0000-EN Rev. A 2014-12
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.
The FlowLine software package includes a comprehensive FlowLine, User’s

Manual.
P-000-0000-EN Rev. A 2014-12

Software Overview TPSys 3.3 Mycronic

Mycronic TPSys 3.3 Linux
2. Linux
This chapter describes briefly Linux operating system.
Linux is a multi-user and multi-tasking operating system distributed by several

vendors. Linux operating system based on Ubuntu 12.04LTS is used for
TPSys software. The multi-tasking feature is utilized by TPSys by using many
terminals and running several processes simultaneously.
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 TPSys 3.3 Mycronic
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.
Users and Root

On a Linux system there are several users defined.
A very important user in the Linux system is the root, which has access to all
files and all system commands.
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.
Mycronic uses several proprietary drivers for communication with, for

example, motor computers and frame grabber.

Files and Directories

Files are very important components in Linux system. Device files such as
terminal lines and disk drives can be opened, read, written, and closed like any
file with the exception that they are often owned by the root and cannot be
accessed by a user with the usual privileges.
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.

USB Flash Drives

TPSys supports hot-plugging of USB flash drives.
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.
The 'bash' Program

The ’bash’ program starts by the logon procedure when somebody logs in. The
bash program is the standard command interpreter for the Linux system. The
command interpreter is also called the shell. The shell reads and executes a
command typed by a user, or starts a program that executes the command.
 If bash is typed (lower case) at the command prompt, then another shell starts
as a child-process to the first shell.
Changes in the current working directory or environment symbols will not

affect the parent shell. A shell is terminated by entering a command (exit) or
by pressing <Ctrl> + D.

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.
Process Environment and Symbols

Every process in Linux has a private data area called the process environment.
The data area contains various information and is accessible to the process.
One type of data in the process environment is symbols.
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.
Symbol names are, as a convention, usually written in upper case.

To set a symbol, enter:
SYMBOL=value
The SYMBOL symbol is now modified in the shell environment. If
programs, started by the shell, have access to the symbol, then it has to be
exported. Export by entering:

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.
Some common symbols are:

HOME
Contains the user’s home directory. If you type cd without a parameter,
then you are moved to the path set in the HOME symbol.
TERM
Contains the name of the current terminal description.
PARAMETERPATH
Defined in TPSys and contains the path to the current parameter files.
 The command cd $PARAMETERPATH takes you to the parameter files.
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
The ls -l command then returns the following result.

lrwxrwxrwx 1 tpsys tpsys 11 Jun 18 08:50 alink -> afile
-rwxr-xr-x 1 tpsys tpsys 1384 Jul 23 10:50 afile
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
Pipes are frequently used in shell scripts.

The 'proc' File System

In Linux a ’proc’ file system is used. This is found in the ’/proc’ directory in
the file system. Files in this directory are not standard files. They can be
accessed like files but the information is not stored on the hard disk but
generated by the kernel.
The command less /proc/cpuinfo returns information about the CPU:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 10
cpu MHz : 701.716
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags :fpu vme de pse tsc msr pae mce cx8 sep mtrr
pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1384.44
Common Linux Commands and Utilities

This section contains a small summary of basic Linux commands and utilities,
which may be helpful during service and software maintenance.
The following commands are included in this section:
• cat – Catenate, concatenate.

• cd – Change directory.
• cp – Copy.
• diff – Difference.
• dmesg – Show boot messages.
• emacs – Start text editor.
• fdformat – Format floppy disk.
• fsck – File system check.
• grep – Match patterns.
• less – View file.
• ls – List.
• man – Show help file.

• mcopy – Copy file to/from DOS disk.

• mdir – List DOS disk.
• mformat – Format a DOS disk.
• mkdir – Make directory.
• mv – Move, rename.
• nano – Start text editor.
• rm – Remove file.
• rmdir – Remove directory.
• sync – Flush file system buffers.
• tar – Read and write from disk.
• top – Display most active processes.
• tty – Terminal path and name.
• vi – Start text editor.
• who – Which terminals are used, and which users are logged on.
Before reading the descriptions of the commands, study the following section
about flags, arguments and special characters.
Flags and Arguments

Linux commands are often followed by modifying flags and major arguments.
Example:
ls lib
’ls’ is the command and ’lib’ is the major argument.
Example:
ls -l lib
Flag ’-l’ follows the command and precedes the major argument.
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.

To see the result, type:

cat myfile
To remove the file, type:
rm 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.
Note that Linux is sensitive to lower and upper case characters.

All the following examples presuppose you are in the home directory.
/home/tpsys
cat – Catenate, concatenate

Reads files and prints on the monitor.
Syntax:
cat file
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.
dmesg – Show boot messages

Shows all messages when the system is booted.
Syntax:
dmesg
Example:
dmesg|less
All messages are printed on the monitor.
emacs – Start text editor

Starts a display oriented text editor named emacs that is included in Linux
operating system.
Start the emact text editor:
emacs
You can also open a text file for editing with emacs with the following
command:

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
There is in-depth information about emacs on the internet.
fdformat – Format floppy disk

Low-level formats floppy disks.
Syntax:
fdformat /device/floppy, drive, density, floppy density
Example:
fdformat /dev/fd0H1440
Formats the floppy disk as follows:
/dev Device
fd Floppy disk.
0 Drive A.
H High density floppy disk.
1440 Kilobytes on the floppy (1440 = 1.44 MB).
In TPSys 3.3 the following two devices can be used when formatting floppy
disks:
/dev/fd0def and /dev/fd1def.
Example:
fdformat /dev/fd0def
The floppy is formatted to its size automatically.

fsck – File system check

This test performs a check of all files in the system partition. The test starts
automatically at every 20th system startup. If the system detects a file system
inconsistency the most inconsistencies are repaired automatically, but in some
cases the system prompts you to issue a manual file system check.
Syntax:
fsck -y device
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.
grep – Match patterns

Searches for indicated pattern in files.
Syntax:
grep pattern file
Example:
grep speedScale lib/params/caxis
Result:
I speedScale: 320 E 7 32768 0
This line in the caxis file has a matching word.

less – View file

Displays the contents of a file on the monitor. Technically, it presents an
output stream to the monitor.
Syntax:
command |less
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]
-CF Lists files in columns and append an asterisk (*) to all

executable files and a slash (/) to all directories.
-l One line of information for each file.
-i Adds inode file number to the list.
-a Lists all files in the 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.

man – Show help file

Shows documentation for a given command.
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.
mcopy – Copy file to/from DOS disk

Copies files from DOS formatted disks to the Linux system, or from the Linux
system to DOS formatted disks.
Syntax:
mcopy file1 file2
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.
mdir – List DOS disk

Lists the contents of DOS disks.
Syntax:
mdir unit
Example:
mdir A:
The files are listed on the monitor.

mformat – Format a DOS disk

Low-level formats a DOS disk.
Syntax:
mformat drive
Example:
mformat a:
Low-level formats a DOS disk in drive A.
mkdir – Make directory

Creates new directories. Requires write permission mode.
Syntax:
mkdir directory
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.
nano – Start text editor

Starts a text editor that is included in the Linux operating system.
Syntax:
nano
pwd – Prints the path to the current directory

Displays the path of the current directory.
Syntax:
pwd
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.
rmdir – Remove directory

Removes directories, provided they are empty.
Syntax:
rmdir directory
Example:
rmdir testdir
The testdir directory is removed, if empty.
sync – Flush file system buffers

Ensures a USB flash drive is updated before removing it from the computer.
Syntax:
sync
 Note that 'sync' is the entire command.
Example:
sync
tar – Read and write from disk

The purpose of the tar (Tape ARchive) command is to read or write an archive
of files. Archives of entire directories, complete with sub-directories and files
can be created or extracted. Tar is used primarily as a backup and transfer tool
and can be compared to the Windows zip file utility, although the files are not
compressed.
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.
top – Display most active processes

Displays the most active processes.
Syntax:
top
Example:
top
Shows CPU and memory usage.
tty – Terminal path and name

Responds the terminal path and name.
Syntax:
tty
Example:
tty
Current terminal path and name is shown, for example /dev/tty3.
vi – Start text editor

Starts a display oriented text editor named ’vi’ that is included in the Linux
operating system.
Syntax:
vi

Example:
vi
Starts the editor. The most important commands for simple editing are
listed in the following table.
Command Function Example

vi Start command. vi file
i Text insert mode. i text
<Esc> Exit text mode. i text <Esc>
x Delete character. x
: Command mode. : command
q Exit, not modified. :q
q! Exit without saving. :q!
w Save :w
wq Save and exit. :wq
u Undo (the last). :u
/ Search /text
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

Mycronic TPSys 3.3 TPSys
3. TPSys
This chapter describes TPSys software, which is developed by Mycronic and
used to control all the Mycronic placement machines.
The description is divided in three main parts:
• General software description, including software structure, terminal and

system hang-up instructions, running more than one TPSys version, and so
on.
TPSys • TPSys web interface.
• Parameter description, including parameter structure, Parameters window
and password.
 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.

TPSys TPSys 3.3 Mycronic
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 (tty).

• Login Instructions.
• Hang-Up (instructions for terminal hang-up and system hang-up).
• Setting Time.
• Machine Serial Number.
• Time Lock.
• TPSys Startup Programs.
• TPSys Versions and Directory Tree.
• Offline Terminal.
• Making TPSys Screenshots.
• Stepper Feature.
• Logoff and System Shutdown.
• Users Window.
• TPSys Web Interface.
• System Save Status.
• Parameters
• Deleting TPSys Data.
TPSys requires the Linux operating system, which is described in Chapter 2.

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.
Description of the seven terminals:
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.
Virtual terminal 6.
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.
Virtual terminal 1 can sometimes be referred to as tty1 and so on.

Login Instructions
Linux allows you to login to the system in the following two different levels:
– ’tpsys’ (password ’mydata’)

– ’root’ (password ’mydata’)
'tpsys'
The ’tpsys’ login level is used for the following purposes:
Startup programs and TPSys operation

Terminal tty1 is logged in as tpsys automatically. When TPSys is started, a
startup message is shown.
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’.
From ’root’, everything in the system is accessible, changeable and erasable.

So, the ’root’ should not be entered unnecessarily. Only authorized personnel
with experiences in Linux should use this level.
 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).

The ’root’ prompt is a hash mark, as shown below.

#
The ’root’ is exited by typing the following text:
exit
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:
1. Switch to another terminal by pressing <Alt> + <F#> (# = the desired

terminal number) and log on as tpsys.
Further information about terminals is found on page 3-3.
2. Enter the following command at the Linux prompt ($):
ps -x
A table of running processes is shown. Example:
PID TTY STAT TIME COMMAND
371 2 ? 0:01 -bash
521 2 S 0:05 mhproc
525 3 S 0:02 dmpmotlog
529 3 S 0:01 -bash
533 3 S 0:00 ps -x
where:
PID – Process identification number.
TTY – Terminal.
STAT – Process status.
TIME – Used processor time.
COMMAND – Command for the running process.
The question mark under STAT means that the status for the hanged-up
process is not known.
3. Read off the lowest process number for the hanged-up terminal. In the
above example it is 371 for terminal tty2.
4. Terminate the process by entering a kill command and the process
number as argument, in this case 371:
kill -9 371
The tty1 terminal only 5. If the hang-up happened on the TPSys online tty1 terminal during
assembling, then inspect the machine to see if there is an incomplete
layout.
6. An incomplete layout can be resumed and completed by loading the
Layout Status for the layout. This is further described in the operator’s
manual.

System Hang-Up
If no terminal responds to any key pressing, then you have a system hang-up.
 Do not press the reset button on the computer box.
Exit the system as follows:
1. Open the front cover.

2. Turn the power off.
3. Watch the hard disk indicator LED on the computer box. It should
indicate activity within one minute.
– Hard disk activity.
If it does, wait until all indicating LEDs on the computer box are
permanently out, and then turn the power on again.
– No hard disk activity.
If it does not, turn the power on again and press the Reset button on
the computer box.
Normally, the system comes up again after resetting. But, in worst
case it does not. A complete software installation and calibration may
be necessary. Please contact Mycronic Customer Support in this
situation.
If there is a backup, the parameter measuring and setting part of the
calibration can be restored.
If there is a complete data backup, all data can be restored.
 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:
• Add an NTP server if it exists in the factory network. Check with IT

department.
• 4 servers are enabled by default, this requires that the machine is connected
to the Internet. To enable this, select menu item Quit.
• To add a local NTP server select menu item Add.
• After adding a server select menu item Exit and save.
• To disable NTP select menu item Disable NTP.

Machine Serial Number

The following command is a TPSys command, but it is executed from Linux.
It shows the machine type and serial number.
serial - Serial number
Returns or checks the machine serial number, name or model.
Syntax:
serial [-s] [-n] [-a] [-m]
-s Test of the device (silent).
-n Print the serial number.
-a or -A Print the machine name in ASCII format.
-m or -M Print the machine model.
c Clear cache, returns no data.
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.
Time lock functionality can be disabled altogether in case of upgrades to

existing installations.
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 Startup Programs

When TPSys is started or restarted, a dialog box is shown a few seconds:
If the space bar is pressed during this time, a collection of service, installation
and backup programs is accessible from the startup menu shown.
The programs accessible from this menu are:
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.

TPSys Versions and Directory Tree

This section describes the links to more than one TPSys version and to TPSys
directory tree.
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.
More Than One TPSys Version

More than one TPSys version can be installed, but only one at a time can be
used.
 Do not change TPSys version by re-linking /home/tpsys.

TPSys Directory Tree

TPSys software is located under Linux operating system in a directory tree
shown in Figure 3-1. The directory tree can vary depending on optional
features and equipment.
magazines
DB init board
usb 0 language english

media (inserted usb stick)
bin mot1 french
etc par-generic german
Linux home tpsys lib par-my200-14
Backup log params
tmp
Figure 3-1. TPSys directory tree.
The main directories are:

/home
The Linux system directories and TPSys home directory.
/home/tpsys
Home directory for TPSys version.
/home/tpsys/bin
Binary execution files for starting and running the TPSys and the startup
programs. The go file is used to automatically start TPSys from Linux.
/home/tpsys/etc
Execution files for TPSys and the startup programs. It also contains software
tools started from Linux, for instance the burnin program.
/home/tpsys/lib
Administration data for databases, languages, and so on.
/home/tpsys/log
Log files created by the various programs under TPSys.
/home/tpsys/tmp
Temporary files for logging and saving various status.
/home/tpsys/lib/language
Language managing files for different languages.

/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.
The startup program cannot be run from 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.
Making TPSys Screenshots

To make a screenshot of the TPSys window, press the <Print Screen> key on
MY9–MY19 machines, and, on MY100 machines, press the <F14> key.
The screenshot can be viewed in the TPSys web interface in section Service
Tools > Image Log. Click on the thumbnail of the picture to view it in full size.
To save it on disk or a USB flash drive, right-click on the picture and select
Save image as….

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.
The Stepper feature can run in two modes:
– Single stepping.
– Continuous slow running.
Activating the Stepper feature

The stepper can be activated while the machine is in board assembly mode, for
instance if there is a need to figure out why a component drops off the mount
tool. It can also be activated from the most of the other modes, for instance
during test centering.
1. Start the TPSys function you want to troubleshoot, for instance board
assembly or test centering.
2. Activate the Stepper mode by pressing <Ctrl> + S.
 If the user access system is in operation, the user currently logged in must have
Service field in the Users window set to High.
Running the Stepper feature step by step

To perform a single machine step, press <F7/Front>. The machine will then
run with full speed during the step, and then stop and wait. Repeat pressing
<F7/Front> to make more machine steps.
Running the Stepper feature in slow continuous mode

Press <F8/Pin> to run the machine continuously. The machine will then run
with full speed during each movement, but add a delay between the
movements. Press PgUp to increase the delay.
 You can run the Stepper in continuous mode and then press <F7/Front> to
switch to single step mode.

Stepper feature commands

The following commands are available when the Stepper is activated.
Command Small keyboard

Action
key key
F6/Grab Grab/Release Normal mode.
F7/Front Front/Back Single step mode.
F8/Pin Toggle Pin Step with 50 ms delay.
PgUp PgUp Increase delay time.
PgDn PgDn Decrease delay time.
F3/Glue Glue Toggle stepper messages on/off.
Deactivating the Stepper feature

When finished using the Stepper function, press <Ctrl> + E to exit.
The Stepper Message Window

While the Stepper mode is activated, the system will display internal system
messages in the Stepper window, see Figure 3-2.
--- Z Center right ---

Tx:MOVENICE fi pos: 210221m° s2: 6000°/s acc: 10000 prec: 0 timeout: 0ms id: 82927
Tx:READPOS x id: 82928
: R->S SETPRIO 0
Rx:READPOS x status: 0 pos: 2319136um id: 82928
Tx:WAITPOS z pos: 35552um gt: 0 t: 2000ms id: 82929
Rx:MOV z2 status: 0 pos: 24428um id: 77723
Rx:MOVENICE fi status: 0 pos: 210223m° id: 82927
Rx:WAITPOS z status: 0 pos: 35306um id: 82929
Tx:ZLOCK z lock: 1 on: 1 id: 82930
Rx:ZLOCK z status: 0 id: 82930
: R->S sY MOVE 519876 1 0
Tx:MOV y pos: 519876um prec: 1 acc: 0 mode: 00 id: 160546
Rx:MOV y status: 0 pos: 519874um id: 160546
Rx:MOV z status: 0 pos: 32883um id: 82924
Tx:HYDRAFLASH x pos: 1702869um gt: 0 to: 4000ms id: 82931
Figure 3-2. Stepper message window.
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
– ’Tx’ stands for transmitted command.

– ’MOV y pos 519876um’ is an instruction to the servo motors to move
the Y wagon to position 519.876 mm.
– ’id: 160546’ is simply an identifier of this command.

Rx:MOV y status: 0 pos: 519876um id: 160546
– ’Rx’ stands for received information.

– ’status: 0’ means the servo motor has moved the Y axis and all went
well.
– ’pos: 519876um’ is the actual encoder position.
– ’id: 160546’ identifies this as the reply to command 160546 above.
Some of the different elements of the stepper messages are detailed below.
Headlines
--- Z Center right ---
This type of message works as a header for a block of messages related to a
certain task.
Transmit and Receive

The messages always exist in pairs. First the transmitted command from the
system to the servo computer, then the corresponding response from the servo
computer to the system.
Tx
A command is transmitted from the main system to the servo computer.
Rx
A reply has come back from the servo computer.
 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>.

Logoff and System Shutdown

This section describes how to log off a terminal from Linux, and how to shut
down the system completely from TPSys and Linux.
Logging Off From Linux

To log off from Linux, enter the following command:
exit
The user is then logged off.
Shutdown From TPSys

It is not necessary to log off from other terminals before shutting down the
system.
To shut down the system:
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
Shutdown From Linux

If TPSys is not running, you can shut down the system from the Linux prompt:
1. Type halt at the Linux prompt.

2. 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.
The user security is configured in the Users window.
User information can be modified when the security is either disabled or

enabled.
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.
Press <Space> to select the privilege levels.
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.
To enable or disable the feature:

1. Select Utility > User Access System, and then select if the User Access
System should be On or Off.
2. Enter your Name and Password in the popup box shown.
This dialog box is not shown if Note that only users for which the User privilege level is set to High and
a user with User privileges set the Interface field is set to Standard are allowed to switch the User
to High disables the feature. Access System either On or Off.
Log On/Off
How to log on and log off is described in the operator's manual.

TPSys Web Interface

The web interface is an add-on to the standard TPSys interface. From here it
is possible to perform the following tasks:
• Viewing package, component, layout, panel and PCB data.

• Generating Traceability reports and Error reports.
• Monitoring the machine utilization, see page 3-25.
• Monitoring the machine performance, see page 3-26.
• Printing various TPSys reports.
• Viewing the current machine messages and a 'virtual light tower'.
• Saving system status, see page 3-31.
• Viewing the camera image log, see page 3-28.
Figure 3-3. TPSys web interface, displaying a layout.

Accessing the Web Interface

You can access TPSys web interface in several different ways:
– By pressing <Alt> + <F2> on the machine keyboard.

– By entering the hostname or IP address for the machine or server in
your office PC browser. This assumes the machine is networked.
Example:
http://my12n123
– By using MYPlan or MYCenter, which has built-in web browsers
dedicated for TPSys web interface.
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.
Viewing Assembly Data

By selecting Assembly data in the web interface main menu, you get access to
a set of viewers for data such as layouts, panels, PCBs, components and
packages. You get a graphical image of the data, and you can browse the data
just like any internet application.
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.
Generating Traceability Reports

By selecting Management information > Traceability Report Generator in the
web interface main menu, a window from where you can configure and either
display or save data from the event log appears.
Generating Error Reports

By selecting Management information > Error Report Generator in the web
interface main menu, a window where you can configure and view data
regarding mispicks and other assembly problems appears.
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.
The report can either be viewed on the screen or saved to a file.

Monitoring Machine Utilization

By selecting Management information > Machine Utilization Report
Generator in the web interface main menu, a window where you can configure
and view data regarding the machine utilization appears.
The fields in the report are described below.

Period
The selected time period.
Uptime
The time TPSys has been used.
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.
Viewing Machine Messages

By selecting Assembly status in the web interface main menu, windows
appears where you can view TPSys messages and operator alerts.
From here, you can also open a small window with a virtual light tower
showing the machine state.

Monitoring Machine Performance

By selecting Management information > Performance Report Generator in
the web interface main menu, a window where you can configure and view
data regarding the machine throughput appears.
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’.
Selecting the report settings

Report type
The choices in this field are the following:
– 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.
Generate report in text format suitable for import into Excel

If this box is selected, the report is generated in a table format that is suitable
for importing in other programs, such as Excel.
How to interpret the Performance report

Description of the fields in the Performance report:
Load wait time

The time the machine waits for a board to become available on the external
conveyor.
Board change time

The time spent by the machine to load the board from the external conveyor,
once it becomes available.

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.
HYDRA tool change time

Time spent by the HYDRA mount head on tool changes.
Total tact time

Time spent to place components. Time spent rejecting faulty components is
included, but not time spent for fiducial mark search and tool changes.
Operator wait time

The time the machine has spent waiting for operator action. This time does not
include time spent for manual fiducial mark search.
Total time
The total production time including the time spent for board change.
Net throughput
The net throughput, NTP, is defined as follows:
Net throughput = 3600* Mounted components / (Total tact time + Automatic

fiducial mark search time + Manual fiducial mark search time + Z tool change
time + HYDRA tool change time + Board change time)
Unload wait time

The time that the machine spent waiting for the external conveyor to be ready
to unload the populated board.
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.
Camera Image Log

Sometimes you may need to troubleshoot vision centering or automatic
fiducial mark location. An example is when a certain package has a high reject
rate. Another example is when the automatic fiducial mark search fails often
for certain fiducial marks.
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.

Turning on the image log

The image log is by default set to off. It means that no images are saved to file
during vision centering or fiducial mark search. To activate the image logging,
do the following:
1. Select Production > Switches in the TPSys menu.

2. Locate switch 0030 Image log mode. Change the setting to one of the
following:
– Off
Vision images are never saved to file (default). This is the
recommended setting for normal production.
– Save image when vision failed
An image is saved every time a vision problem occurs. This is the
recommended setting for troubleshooting.
– Save all images
An image is saved every time a camera is used. This setting can be
used for advanced troubleshooting.
 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.
Browsing the image log

The images saved in the image log can be viewed in the TPSys web interface.
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.
Figure 3-4. The 'Image Log' window in the web interface.
– Browse through the image gallery by clicking View next page ...or
View previous page ...

– If needed, filter the gallery by selecting a category in the Image type

menu.
– Enlarge a thumbnail image by clicking on it.
For some images, you can select Show graphics to include or exclude
the graphics drawn by the vision system.
The enlarged image view will also show the name of the camera that
was used to capture the image, and the error message associated with
the image.
Downloading images from the image log

You can download the images from the image log to another computer. The
download will include the selected images (in .png format) as well as
information for advanced analysis of the images.
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.
Deleting images from the image log

1. Select which images to delete using the check boxes next to each image.
If desired, you can select all images with the Select All button.
2. Click on Delete selected images.
System Save Status

In TPSys there is a utility called System Save Status that saves all the log files
and parameters on the machine in a compressed file. This file can then be sent
to Mycronic support, where it can be unpacked and analyzed.
TPSys Terminates in an Unnatural Way

If TPSys terminates in an unnatural way, that is without the operator choosing
exit from the menu, the following text will appear on the screen.
TPSys terminated in an unnatural way !!!
Do you want to create a "savestatus" ?
Answer y for yes and n for no [n]:
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.

The following procedures apply if you choose to save these files.
1. Answer ’y’ to the question above to start the procedure.

2. The system will ask where to save the file. The save status can be saved
to the hard drive, or a USB flash drive (if inserted).
If File is selected, the program will ask for a directory where the save
status shall be stored.
The program will then ask for the name of the sub-directory in which the
actual save status file will be stored. The default sub-directory name
corresponds to the current date and time. The program then collects all
the files to be included in the save status and compresses them into a file
called AAaa.
3. When the save status program has collected and compressed all the files,
a pop-up informs of the file location.
4. Forward the AAaa file to Mycronic for analysis.
Creating a System Save Status from TPSys

It can sometimes be useful to create a system save status even if TPSys has not
terminated in an unnatural way, for example to debug some machine behavior.
For this purpose, the save status program can be started by selecting Utility >
Save System Status in TPSys.
Creating a System Save Status from the Web Interface

A system save status can also be created using the TPSys web interface.
1. Open TPSys web interface.
2. Select Service Tools > Save system status > Create TPSys Savestat.
3. The program will now list the target directory for the ’savestat’ and list
the progress. Note that the file will be stored on the machine.
4. To download the save status file that was created to your own computer,
click on the link Click Here to download status information at the
bottom of the page.
When you click this link, a window will appear that will let you save the
file on your own hard drive.
5. You can also download the latest saved system save status at a later time
using the web interface. This is done by selecting Service Tools > Save
system status > Get current savestat data.

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.
This section contains information about:
• The parameter structure.

• The Parameters window.
• Parameter modification.
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.
Opening the Parameters Window

The Parameters window can be opened either from TPSys by selecting Edit >
Parameters...
... or from the startup menu by pressing <Space> before TPSys is started and
then select the Parameters option. This option is a way of editing parameters
without initiating the machine.
You can also press the <Shift> + <F10> keys or just <F10> in any text mode,
F10
and select the Parameters option in the Hot Menu.
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.
Miscellaneous Parameter Information

This section contains the following parameter information not associated to
the previous sections:
• 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:
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:
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:
Property Unit Unit

Angle mDeg Millidegrees
° Degrees
Angular speed °/s Degrees per second
Force mN Millinewtons
N Newtons
Length um Micrometers
mm Millimeters
Speed mm/s Millimeters per second
Time ms Milliseconds
s Seconds
Torque mNm Millinewtonmeters
Ticks
The word ’tick’ is common in some of the parameters. It signifies one step
from a digital incremental transducer.

Deleting TPSys Data
 CAUTION! This section describes procedures to erase all information or

large quantities of information from the TPSys databases. These procedures
are suitable for when a machine is decommissioned. There is no undo to the
procedures described.
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.
Deleting a Specific Data Type

To delete all package data, first locate the computer that runs the database by
selecting About... > Databases > Status in the TPSys menu. Then enter the
following at the Linux prompt on terminal 1 on the computer that runs the
database server:
cd /home/tpsys/lib/DB/init/packagelist
psql -U postgres < deleteallpackages.sql
You can remove all data types except event log data with this method, using
the reference table below.
Data type Delete command

Layouts cd /home/tpsys/lib/DB/init/layout
psql -U postgres < deletealllayouts.sql
Mount status cd /home/tpsys/lib/DB/init/mountstatus
psql -U postgres < deleteallmountstatus.sql
Panels cd /home/tpsys/lib/DB/init/board
psql -U postgres < deleteallpanels.sql
Pcbs cd /home/tpsys/lib/DB/init/board
psql -U postgres < deleteallpcbs.sql
Fiducial marks cd /home/tpsys/lib/DB/init/reflist
psql -U postgres < deleteallfiducials.sql
Packages cd /home/tpsys/lib/DB/init/packagelist
psql -U postgres < deleteallpackages.sql
Components cd /home/tpsys/lib/DB/init/complist
psql -U postgres < deleteallcomponents.sql
Carriers cd /home/tpsys/lib/DB/init/carrierlist
(MYCenter Loading module only) psql -U postgres < deleteallcarriers.sql
Containers cd /home/tpsys/lib/DB/init/containerlist
(MYCenter Loading module only) psql -U postgres < deleteallcontainers.sql
Bins cd /home/tpsys/lib/DB/init/binlist
(MYCenter Loading module only) psql -U postgres < deleteallbins.sql
Tray magazine cd /home/tpsys/lib/DB/init/traymagazine
(MYCenter Loading module only) psql -U postgres < deletealltraymagazines.sql
Glue dots cd /home/tpsys/lib/DB/init/gluedotlist
psql -U postgres < deleteallgluedots.sql
Magazines cd /home/tpsys/lib/DB/init/magazinelist
psql -U postgres < deleteallmagazines.sql
Trays for YWM, TWM, TEX, and cd /home/tpsys/lib/DB/init/traylist
ATM psql -U postgres < deletealltrays.sql

Data type Delete command

Pallets cd /home/tpsys/lib/DB/init/pallet
psql -U postgres < deleteallpallets.sql
Tray types cd /home/tpsys/lib/DB/init/traytype
psql -U postgres < deletealltraytypes.sql
Tray positions for YWM, TWM, cd /home/tpsys/lib/DB/init/traypos
TEX, and ATM psql -U postgres < deletealltraypositions.sql
Removable feeders cd /home/tpsys/lib/DB/init/tapeguidelist
psql -U postgres < deleteallremovablefeeders.sql
Magazine kits cd /home/tpsys/lib/DB/init/magazinelist
psql -U postgres < deleteallkits.sql
Management data cd /home/tpsys/lib/DB/init/managelist
psql -U postgres < deleteallmanagementdata.sql
TEX units cd /home/tpsys/lib/DB/init/texlist
psql -U postgres < deletealltexunits.sql
Users cd /home/tpsys/lib/DB/init/user
psql -U postgres < deleteallusers.sql
Deleting all Data

To delete all information in all databases including the event log data, enter the
following at the Linux prompt on terminal 1:
 CAUTION! This procedure deletes all information in the TPSys databases.

There is no undo to this command.
cd lib/DB/init
psql -U postgres -d mydata_common_db < createDB.sql
Restoring Default Data

To refill the package database with the default package library, continue with
entering the following at the Linux prompt on terminal 1:
cd
cd lib/DefData
import *.pck
cd
You can import the following data types with this method, using the reference
table below.
Data type Import command

Packages import *.pck
Glue dots import glu.glu
Tray types import TrayTypes.ttp

Mycronic TPSys 3.3 Network and File Sharing
4. Network and File Sharing

This chapter is about installing network and file sharing, and for using FTP to
transfer files.
This documentation assumes all the local area network hardware is already
installed. For further information about hardware installation, see the
corresponding service manual.
The chapter is divided into the following sections:

• Network Configuration, page 4-2.
This section explains configuration of TPSys network settings.
• Transferring Files Using FTP, page 4-6.
This section explains how to transfer files to and from a TPSys machine.
The following definitions are used throughout the chapter:

Server
Server here means a database server. It may be a machine or a stand-alone
PC running TPSys.
Client
Client here means a Mycronic machine that shares databases with a
server.

Network and File Sharing TPSys 3.3 Mycronic
Network Configuration
To ensure that the server and the clients are able to communicate over the
network, the network has to be configured.
Also a single-machine network can make use of a network connection, for

instance for backups and for easy transfer of MYPlan data.
TPSys Network Settings

To configure the network on a machine running TPSys, do the following:
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.
 Typically, the local IT support will have input on these settings.
5. If you selected Fixed IP, enter these data:

– IP address: The IP address that the machine/server will have in the
network. All machines in the network must have unique IP addresses.
A status window is shown with the information you need to set up the
network.
– Netmask: The netmask address of the network the machine/server is
connected to. It is automatically generated from the IP address. Use
the automatically generated netmask address unless the network
manager says something else.
– Broadcast: The broadcast address of the network the machine/server
is connected to. It is automatically generated from the IP address. Use
the automatically generated broadcast address unless the network

– Gateway: The gateway address of the network the machine/server is

connected to. It is automatically generated from the IP address. Use
the automatically generated gateway address unless the network
– Domain name: The domain name for the machine/server
(company.com). Preferably, use the mydata.se unless the network
– Primary Name server: The IP address of the primary name server on
the network the machine/server is connected to. Leave this field
empty unless the network manager gives you an IP address of a name
server.
– Secondary Name server: The IP address of the secondary name server
on the network the machine/server is connected to. Leave this field
empty unless the network manager gives you an IP address of a
secondary name server.
When you have set the network parameters, a Status window appears showing
all the settings. You can also access this window by selecting View in the Main
dialog.
6. If the In the dialog Main, select Hostname and click OK.

7. Enter the name that the machine will get on the network, for example
my200-14n5678.
The dialog Main appears again.
8. To exit the Netsetup Main dialog, and to save and enable the network
settings, select Quit and OK.
Adding Machines to the Network

The machines on the network need to be made aware of each other and of the
network server. Machines are added to the network in two different ways
depending on whether a name server is used or not.
With a name server

If the network has a name server, and you stated this during netsetup, ask the
local network manager to add the IP address and host name of the new
machine to the name server. The IP address and the host name should be the
ones defined on the network settings in the netsetup program.

Without a name server

If the network does not have a name server, every machine on the network
needs to be configured with data about the other machines on the network.
1. Type su at the Linux prompt on the current machine to become root.

2. Open the /etc/hosts file with ’emacs’ or ’vi’. For further information
about ’emacs’ and ’vi’, see pages 2-10 and 2-17, respectively.
3. Add all hosts on the network. Add hosts by adding a line with the
following syntax for each other host on the network:
IP-address Host_name Host_name.Domain_name
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
In this example, the current machine’s IP address is 192.168.1.32, its host

name is ’my100-14n1234’ and its domain name is ’company.com’.
Assume you want to add ’my9n123’ with IP address 192.168.1.33, and a PC

with name ’myserver’ and IP address 192.168.1.119. The /etc/hosts file
should then be edited by adding two lines at the end, one for each new host.
The end result should look like this:
127.0.0.1 localhost
192.168.1.32 my100-14n1234 my100-14n1234.company.com
192.168.1.33 my9n123 my9n123.company.com
192.168.1.119 myserver myserver.company.com
 Retain the first line (127...) and the current machine’s data in the file.
4. Close the editor.

5. Type exit at the prompt, to log out from being root.
6. Once the current machine is updated, copy its /etc/hosts file and
place it in the same location on the other computers on the network.
Remember that you have to be root in order to be allowed to change the
/etc/hosts file.

Testing the Network with Ping

The ping command is used to check that the network connections are OK.
From each machine it should be possible to ping all other machines on the
network, and it should also be possible to ping the machine itself.
1. First check that the host names are working by pinging. Example:
ping myserver
(’ping’ followed by the host name to check the connection to)

If everything is OK, there will be a response similar to this:
PING myserver.mydata.se (192.168.1.119): 56 data bytes
64 bytes from 192.168.1.119: icmp_seq=0 ttl=64 time=0.3 ms
If there is a problem it will look like this:

ping: unknown host myserver
or like this:
--- myserver.mydata.se ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
Exit the ping command by typing <Ctrl> + C.

2. If pinging using the host name fails, continue by pinging using the
IP addresses on the network instead. Example:
ping 192.168.1.119
(’ping’ followed by the IP address to check the connection to)

Exit the ping command by typing <Ctrl> + C.
If one can ping using the IP address but not when using the host name,
there is likely a problem in the /etc/hosts file or in the name server
(if there is one). For instance, check the spelling of host names.

Transferring Files Using FTP

From time-to-time there may be a need to transfer files to and from a machine
or stand-alone server.
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.
Using FTP from Linux

There is an FTP client shipped with the TPSys distribution. This program can
be used to transfer files to and from the machine/server.
Transferring a file to a machine/server

Assume you want to transfer a file that is located on a remote computer. The
following procedure is used to transfer the file to the machine/server.
1. On the machine/server, switch to a free virtual terminal by pressing

<Alt> + <F#>, where # is the number of the desired terminal. For further
information about virtual terminals, see page 3-3.
2. Change to the directory where you want to put the file. For information
about changing directories in Linux, see page 2-9.
3. Start the FTP program by entering the following command at the Linux
prompt:
ncftp -u <user> <hostname>
-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.

Transferring a file to a remote computer

Assume you want to transfer a file that is located on the machine/server. The
following procedure is used to transfer the file to a remote computer.
1. On the machine/server, switch to a free virtual terminal by pressing

<Alt> + <F#>, where # is the number of the desired terminal.
2. Change to the directory where the file is stored.
3. Start the FTP program by giving the following command at the Linux
prompt:
ncftp -u <user> <hostname>
-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.
Using FTP from Windows

The FTP server on the machine/server can be contacted to from a Windows
computer using an FTP client program.
You can log on to the FTP server on the machine or the TPSys server with the
user name ’tpsys’ and the password ’mydata’. Refer to the manual of the FTP
program for information on how the FTP client program is operated.
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.


Mycronic TPSys 3.3 Data Sharing
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.
The chapter is divided into the following sections:
• TPSys Database, page 5-2.

This section goes through the structure of TPSys data, and how the database
is organized when several machines are connected to a TPSys server. The
section contains information that can be useful for troubleshooting and
system understanding.
• Installing Data Sharing, page 5-8.
This section explains how the system is installed and configured for data
sharing.
• Data Sharing Maintenance, page 5-12.
This section explains how to maintain data sharing settings, for instance
during network maintenance.

Data Sharing TPSys 3.3 Mycronic
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 several machines connected in a network, it is recommended to set

up the system with a server that stores TPSys data.
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.
Two Machines without Standalone Server

Two machines with network connection can store their data in a database in
one of the machine’s computer.
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.
Two or More Machines with Standalone Server

Several machines with a standalone server store their data in a database on the
standalone server.
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.

Backup and Restore

When a database is backed up, both private and shared data will be backed up.
This is regardless of the data sharing settings. See page 6-2 for information
about how to take a backup.
Figure 5-3 shows an example on a backup taken from ’my100-14n5678’. The

backup will include all data from all private areas and all data from the shared
area.
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.
When a database is restored on a machine, the data will be restored according

to how the data was stored when the backup was taken. To restore shared or
private data the Specific data from database feature should be used. Follow the
instructions on page 6-8.
 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, Parameters and Calibration Data

There are some TPSys data types that cannot be shared.
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.
Figure 5-4. Refresh of copies of the database.
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.

Installing Data Sharing

The following pages contain step-by-step guidelines for configuring a network
of machines and a server to use a common database which is a necessary
precondition for data sharing.
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.
Taking a Backup of Existing Data
 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.
1. Take a backup of the data on the machine, according to Chapter 6.

2. Repeat the backup procedure for those machines that store data you want
to move to the server.
 CAUTION! Do this backup before linking the client to the server, otherwise
all data may be permanently lost.

Setting up the Server's Data Sharing

The server is by default set to ’localhost’ and must not be changed. To check
this, do the following:
1. Start TPSys on the server.

2. Select Edit > Parameters, and then select parameter group 181 Network.
3. Select 181.0301 Database connection; Host name parameter and ensure
that ’localhost’ is selected. The remaining settings in 181 Network
parameter group can be left as is.
4. Save and Exit.
 The 182 Data sharing settings are by default set to Shared on the server and
cannot be changed.
Linking the Machine to the Server

Each machine (each client) needs to know where the server is. You can also
control if the database on the server is to be copied to the machine at regular
intervals.
1. Start TPSys on the client machine.

2. Select Edit > Parameters, and then select parameter group 181 Network.
3. Select the 181.0301 Database connection; Host name parameter.
This field is by default set to ’localhost’ which means that the data is
stored on the machine itself. Change this field to the server’s IP address
or host name.
4. Select the 181.1002 Refresh; Refresh local data base parameter.
Select Yes to set up the system to make a complete copy of the server’s
data (excluding event log data) to the machine’s hard disk at regular
intervals.
5. Select the 181.1001 Refresh; Local db refresh interval parameter.
This field is only applicable if the 181.1002 Refresh; Refresh local data
base is set to Yes. It controls how frequently the system should make a
complete copy of the server’s data to the machine’s hard disk. Default is
3600 seconds which is the recommended value. Change if needed.
6. Save and exit.

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.
Setting up the Machine’s Data Sharing

When the machine is linked to the server, configure which data types that
should be defined as private to the machine and which data types should be
defined as shared with the other machines. By default, all data types are
shared.
1. Select parameter group 182 Data sharing.
2. Select parameter 182.0101 Component data.
– If this field is set to Shared, this type of data is shared with the other
machines in the network. This is the default value.
– If this field is set to Private, this type of data is private to this machine.
The other machines in the network cannot see or access this data.
3. Repeat this for the other parameters in the 182 Data sharing parameter
group. The guide below is showing which parameter controls which
types of TPSys data.
Parameter Types of data

182.0101 Component data Components
182.0121 Package data Packages and glue dots.
182.0141 Mount data Layouts, panels, PCBs, layout mount
statuses, fiducial mark data, and
management data.
182.0161 Magazine data Magazines, removable feeders, tray
types, pallets, magazine kits, and tray
exchanger data.
182.0181 YWM/TWM tray Tray exchanger data.
data
4. Save and exit.
 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.
– Follow the instructions in Chapter 6 section Specific data from

database to restore each data type item by item on the machine you
took it from or on the server.
 Do not restore the whole backup since that would overwrite all existing data.
Repeat for Other Machines

If there are other machines in the network, repeat the Linking the Machine to
the Server, Setting up the Machine’s Data Sharing, and Restore Backup
procedures for the other machines.
 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.

Data Sharing Maintenance

Once installed, the database sharing automatically runs in the background.
However, if the network is down for maintenance, you have to temporarily
change the data sharing settings. Another reason for changing the data sharing
settings is if you want to start sharing private data types.
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.
When a network of machines have been connected to a server, the most

updated information will lie on the server’s hard disk. The disconnection
procedure therefore consists of copying the server’s data to the individual
machines, and to change the 181.0301 Database connection; Host name
parameter on the machines.
To disconnect from the server, do the following:
1. Take a backup of the data on the server, see Chapter 6.

2. On the machine, change the 181.0301 Database connection; Host name
parameter to ’localhost’.
3. Set 181.1002 Refresh; Refresh local data base parameter to ’No’.
4. Restore the backup on that machine, see Chapter 6.
The machine is now using the database copy that is stored on the
machine’s hard disk. The backup/restore procedure ensures that the
latest changes made on the server are copied to the machine.
5. If you have several machines to disconnect, repeat step 2 and 4 on the
other machines.
 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.
To reconnect to the server, do the following:

1. Take a backup on the machine, see Chapter 6.
2. On the machine, change the 181.0301 Database connection; Host name
parameter to the server’s host name or IP address.
3. Restore the backup, see Chapter 6. You can restore the data that has been
changed from each machine’s backup by using the Specific data from
database option, see page 6-8, or on the server, with the same result.
Set 181.1002 Refresh; Refresh local data base parameter to the setting it had
when the machine was disconnected.
4. If you have several machines to reconnect, repeat step 1 to on the other

machines. The order in which you reconnect the machine is important.
For instance, if you have made changes to component ’123456’ on
several disconnected machines, and then reconnect all machines as
described above, it will be the last machine’s settings that will apply for
component ’123456’.
 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.

Moving Data from Private to Shared Area

Assume you have been running a machine for considerable time and want to
Machine convert some data from private to shared. To do this, the export/import
Private area
procedure must be used in the following order, make an export on the machine,
change data sharing settings, and then import the data on the same machine or
on a server. Dependant on which machine the data shall be imported on, a
floppy, USB, UNIX/NFS or FTP channel can be used.
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.
See Chapter 7 for detailed information about the import/export procedures.

Moving Data from Shared to Private Area

In some situations it may be a need to move data from the shared area to the
Machine private area. For instance, if the factory has different custom mount tools on
Private area different machines.
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:
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.
 If you have several machines, you need to do the export/import procedure

above for each machine that has data in its private area.
See Chapter 7 for detailed information about the import/export procedures.


Mycronic TPSys 3.3 Backup and Restore
6. Backup and Restore

This chapter describes the TPSys backup/restore feature.
The backup/restore feature is used to save and restore the TPSys database and
configuration data.
The backup/restore feature comprises working with:

• Backing up the TPSys data.
TPSys The backup feature stores TPSys data on a selected media.
The TPSys data consists of database data and configuration data. The
database data consists of for example component data and package data.
Configuration data consists of parameters, calibration data, and so on.
Database data can only be backed up on a machine acting as a server, while
configuration data must be backed up on the individual machines.
How to take a TPSys backup is described on page 6-2.
• Restoring the TPSys database.
The restore feature includes restoral of the whole database, the
configuration data or database items for the different data types.
How to work with the restore feature is describe on page 6-7.
Some data types can be shared between all machines in the network. Other
data types are specific for each machine. For more information about this, see
page 5-4.
 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.

Backup and Restore TPSys 3.3 Mycronic
Backing up
Follow these steps to take a TPSys backup

1. Select Utility > Backup from the main menu.
 Backup can also be selected in the startup menu which is opened by pressing
<Space> while TPSys is starting.
2. Select Media where to store the backup:

– UNIX/NFS
– FTP, or if applicable
– USB flash drive
Each media type is described on page 6-3.
3. Select backup type
This option appears if the machine is acting as a server. For non server
machines only the configuration will be backed up and no backup type
question will be asked.
– Standard backup
This backup will contain configuration data and the TPSys database.
It will not include the event log data.
– Extended backup for upgrade
This backup will contain configuration data, the TPSys database and
also the event log data. Select this option if the backup shall be used
for TPSys hardware upgrade.
 If the machine is acting as a server, parameter 181.0301 Database connection;

Host name set to ’localhost’, the TPSys database will be included in the
backup.

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.
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.0030 UNIX/NFS 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.
Directory name
The destination for the backup target file. The default destination is set in
the 208.0032 UNIX/NFS backup data; Backup directory parameter.
When the UNIX/NFS 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.
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 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.
window.
USB flash drive

This option is only available if a USB flash drive is mounted or inserted in the
machine.
Backup name
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.
window.

Scheduled Backup
TPSys has a scheduled backup feature that can be configured to perform a
backup automatically at a preset time interval.
– For machines acting as a server the scheduled backup will contain

configuration data and the TPSys database except the event log data.
– If the machine is not acting as a server, only the configuration data
will be included in the backup.
Scheduled backup can be set by selecting Utility > Schedule Backup. The
entries in the configuration box are described below.
After configuring a UNIX/NFS or FTP backup, the configuration parameters,

for example path and transfer protocol, can be verified if Yes is selected on the
pop-up question.
Scheduled backup configuration box

The scheduled backup configuration box is described below.
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.
Type of automatic backup

Press <Space> and select the desired type of backup from the menu:
– 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
another computer in the network.
– FTP
Select this option if you want the backup to be stored on a remote host
using FTP (File Transfer Protocol).
 Scheduled backup is not available for USB flash drives.
Max number of backups

To avoid filling the disk with backup files, this entry sets the maximum
number of backups to be stored. When this number is reached, the oldest
backups are deleted as new backups are saved.
UNIX/NFS backup data Base name of the backup
The base part of the backup target file name. The system adds date and time to
the name set. If you for instance enter ’John’ in this field, then the backup file
name will be ’John_A.20060403_1100’ which means a scheduled automatic
(A) backup file created April 3rd, 2006 at 11:00.
Directory
The destination of the backup target files.

FTP backup data Base name of the backup

The base part of the backup target file name. The system adds date and time to
the name set. If you for instance enter ’John’ in this field, then the backup file
name will be ’John_A.20060403_1100’ which means a scheduled automatic
(A) backup file created April 3rd, 2006 at 11:00.
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
Follow these steps to restore data from a backup file

1. Select Utility > Restore in the main menu.
 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.
– Specific data from database

This option is only enabled if the backup contains database data.
Select this option to restore specific data items from the database in
the backup.
 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 Specific data from database is selected, a new menu appears

showing the shared and private areas. Select data area to restore. If
shared is selected only shared data is possible to restore. If a private
area is selected only that private data is possible to restore. It is not
possible to restore from one data area to another.
When wanted data area is selected the Select data type to restore list
appears showing all items in the actual backup.
Highlight the data type you want to restore, press <Enter> and the
Restore from backup list appears.
If some items have been deleted since the backup was taken these
items are marked with a ’+’.
Highlight the item/items you want to restore and press <Enter> to
perform the restore.
Restore data from a backup taken with TPSys 2.7 or earlier

Exit TPSys to Unix and start the restorePre2.8 program at the command
prompt. This will start the restore functionality as it was implemented before
TPSys 3.3.

Carrier Restore after Hard Disk Change

If a stand-alone data server is used together with the optional MYCenter
Loading module, the carriers are continuously backed up on the local database
on the machines connected to the server. These carrier backups can be used to
restore the server after a hard disk change on the server.
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:
1. In TPSys, select Utility > Restore Carriers.

2. Select Yes. TPSys will exit and the restore function will start.
3. Select Database carriers server in the Select Media dialog.
4. Enter the IP address of the latest machine that was connected to the
server before the hard drive was changed.
5. To restore the carrier database, press <Enter>.


Mycronic TPSys 3.3 Import/Export TPSys
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.
Import and export formats are described on page 7-2.
The import feature is described on page 7-3.

The automatic import feature is described on page 7-6.
The export feature is described on page 7-7.
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.

Import/Export TPSys TPSys 3.3 Mycronic
Import and Export Formats

The import and export formats TPSys and Directline are described below.
TPSys Format
The TPSys format is an ASCII format, described in Appendix D.
Directline Format
Directline is an old Mycronic proprietary format.
 When data is exported in Directline format, some information is lost. It is

highly recommended to use TPSys format for exporting.
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:
1. Select Utility > Import in the main menu.

2. Select one of the following import format options:
– General --------------- TPSys Format
By selecting this option, you can import data to several databases in
the same procedure, for instance to the layout, panel, PCB, component
and package databases. This option has to be selected when importing
underlying data. Underlying data is described on page 7-8.
– Mount List ------------ Directline Format
– Component List -------- Directline Format
– Mount & Component Lists Directline Format

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>.

Selecting Item Names

6. Type a new name for each item to be imported if you want to change the
names, otherwise the existing names will remain.
Existing items in the system will be overwritten if you enter the same
names.
You are, however, informed in the dialog box if there is an existing file
with the same name.
 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.
The renaming feature can be enabled or disabled by setting the 201.0204

Import; Ask for new name (rename) parameter to Yes or No.
7. Press <Enter> to start the import procedure.
When the import procedure is completed, the Import list is shown again.
8. Press <Esc> if you want to return to TPSys main window.

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.
207.0002 Directory to monitor

This parameter controls which directory TPSys will monitor for
automatic import. The default path is /home/tpsys/spool.
207.0001 Check interval
This parameter controls how often TPSys checks for files in the assigned
directory. The default value is 40 s.
207.0003 Verbosity
This parameter controls how much information TPSys displays in the
Messages box during automatic import. A value of 3 is default and gives
detailed information about the status of the import. A lower value will
give less information.
Importing with the Automatic Import Utility

1. Place the file to import in the import directory, see 207.0002 Directory
to monitor above. You can use any file extension, the system will read
the contents of the file itself and deduct what type of data it contains.
2. Wait for the automatic import to happen, see 207.0001 Check interval
above. Depending on the value of the 207.0003 Verbosity parameter,
TPSys may show status information about the import in the Messages
window.

Exporting
To export data from TPSys databases, do the following:
Selecting Data Category

2. Select what data to export, and if you want it exported in TPSys format
or in Directline format.
3. If you select to export Tray Magazine --------- TPSys Format or Tray
Position --------- TPSys Format you will be asked to choose which tray
magazine or which pallet or pallets to export data for.
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
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
for PCBs and components included in the PCB. However, machine
dependent data, for instance package data, is not included.
– Package --------------- TPSys Format
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.

Mycronic TPSys 3.3 Barcode Translation
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:
• A one dimensional barcode with a maximum length of a scanned string of

99 characters.
• A two dimensional barcode in DataMatrix format, that is a matrix barcode
that can hold large amount of information.
For more information on how to configure the barcode scanner and how to
perform basic operations with the scanner, see Operator’s Manual.
There can be four barcode scanners in the machine:

• Two scanners can be conveyor mounted and are for layout related data.
• The third is a handheld scanner used for component or layout related data.
• The fourth is a scanner function that allows the X-wagon camera to read
panel ID and PCB ID in DataMatrix format.
The component related barcode information is for example component name
and component quantity. A prefix is typically used to distinguish different
types of barcode strings. The prefix tells TPSys what type of information was
scanned: component or quantity.
For more information about the parameters controlling these prefixes, see
Appendix B – Parameters.
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.

Barcode Translation TPSys 3.3 Mycronic
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

Serial start is a system where TPSys can automatically start a job by reading a
special barcode that is placed on the PCB. The barcode contains all necessary
information that is needed to run the job. For example what layout that should
be loaded and run.
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.
Each serial start barcode scanner has a filter file.
 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
Handheld Barcode Scanner

The handheld barcode scanner also uses two translation filters. One filter when
reading component related data and one when reading layout related data or
PCB ID related data.
 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.

Barcode Scanning with X-Wagon Camera

Barcode scanning with X-wagon camera is an option that allows barcodes in
DataMatrix format to be read on both panels ID and PCB IDs.
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
Preparing the X- wagon camera in purpose to read shiny barcodes

If a barcode has a shiny surface this can give severe reflection in the X-wagon
camera. This reflection can be eliminated by covering the light from the
semitransparent mirror inside the camera.
Follow these steps to adjust the camera:
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.

Editing Filter Files

The filter files described above are plain ASCII text files. They can be edited
with any text editor. Chapter 2 contains a description of such editors.
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.
Basically, a regular expression is a pattern describing a certain amount of text.

With a regular expression pattern, you can search through a text file, or verify
a given string. The term string or character string is used by programmers to
indicate a sequence of characters.
We will use regular expressions to find, match, unique features in barcode
strings. A match is the piece of text, or sequence of bytes or characters that
pattern was found to correspond to by the regular expression.
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.
Below are some examples of simple regular expressions.
Example 1 – Simple pattern

The following string shows a simple pattern.
1abc2
This pattern has a digit followed by three letters followed by a digit.

Example 2 – Simple pattern

The regular expression
Donald
will match "Donald" in all strings containing the word.
It will not match "donald" in any strings containing the word, since the match
is case sensitive by default:
Example 3 – Pattern with meta characters

^[0-9]*$
A more complex regular expression that uses so called meta characters,
for instance the "^" at the beginning of the string. Meta characters are
needed for most practical filter made with regular expressions. The next
section details these meta characters.
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.
Example 4 – Matching any one character

. Assume that you want to match any of "Donald", "Donala", "Donalb" or
"Donal8" with an expression. You can then use the "." meta character in the
expression to represent any character.

Donal.
Matches the following strings:

Donald
Donala
Donalb
Donal8

Example 5 – Matching regardless of position

Assume you want to match the string "Duck" regardless of where in the line it
is. This is the simplest type of regular expression.

Duck
matches "Duck" in the following strings:
Duck
Donald Duck
Duckling
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.
Example 6 – Matching at the beginning of the line

^ To make the regular expression only match the string "Duck" if it appears at
the beginning of a line, use the "^" character at the beginning of the expression.
This will make the expression require an empty string before "Duck".
^Duck
matches "Duck" in the following strings:
Duck
Duckling
that there are no characters before "Duck":
Donald Duck
Example 7 – Matching at the end of the line

$ If you want to make the expression to only find matches in strings where the
word "Donald" appears at the end of the string, use the "$" character.
Donald$
finds matches in the following strings:
Donald
Mickey and Donald
that there are no characters after "Donald":
Donald Duck

Example 8 – Matching an exact line

^ $ If you want to match the string "Donald" only if it is the only string on the line,
use "^" at the beginning of the regular expression and "$" at the end.

^Donald$
Finds a match in the following string:
Donald
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 "*").

Example 9 – Matching zero or more times

* Assume you want to match the string "Donald" followed by zero or more
characters.

Donald.*
will match the following strings:
Donald
Donald Duckling
 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.
Example 10 – Matching zero or one time

? Assume you want to match the string "Donal" followed by zero or one
character.

Donal.?$
Donal
Donald
It will not match the following strings since the expression requires zero or one
character after "Donal":
Donaldddd
Donald Duck
Example 11 – Matching one or more times

+ Assume you want to match the string "Donal" followed by one or more
characters.

Donal.+
will match the following string:
Donald Duck
It will not match the following string since the expression requires at least one
character after "Donal":
Donal

Example 12 – Matching a specified number of times

{1,6} Assume you want to match the string "Donal" followed by between one and
six characters.

Donal.{1,6}$
will match the following string:
Donald Duck
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.
Example 13 – A simple bracket expression

[Dd] Assume you want to match the string "Donald" and you want to get a match
regardless of if the first character is a "D" or a "d".

[Dd]onald
Donald
donald
An alternative method for this case is to use the IGNORECASE line in your
filter file, see page 8-16.

Example 14 – A bracket expression

[A-Za-z0-9] Assume you want to match the string "Donal" followed by one character from
the alphabet or a digit. You want to get a match regardless of if the string is in
the beginning, in the middle or at the end of a larger string.

Donal[A-Za-z0-9]
Donald
Donala
DonalD
Donal4
Donald Duck
Mickey and Donald
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+
Example 15 – A bracket expression

[A-Za-z0-9] Assume you have the situation from Example 14 – A bracket expression but
you want to get a match only if the characters found by the regular expression
are the only characters in the string.

^Donal[A-Za-z0-9]$
will find matches in the following strings:
Donald
Donala
DonalD
Donal4
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.
The basic format for a filter is as follows:

"Pattern to match" "Output from match"
Note that double quotation marks are used around each expression.
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.

Example 16 – Basic filters

Assume you want to make a filter that changes the string "Donald" to the string
"Duck". The filter would look like this:
"Donald" "Duck"
Original string Translated string

Donald Duck
Donald Duck Duck Duck
Donald Donald Duck Donald
Only the first instance of 'Donald' is
translated.
Donald duckling Duck duckling
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"

donald Donald
Donald Donald
Assume you want to make a filter that changes the string "donald" to
"Donald". The filter would look like this:
"donald" "Donald"

Who is donald Duck Who is Donald Duck
Who is Donald Duck Who is Donald Duck
Note! the filter will pass this string on
unchanged.
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"

Donald Donald Duck
Donald is a duck Donald is a duck
unchanged.

Multiple Filters
You can have several filters in a filter file. They will be used in the order they
appear in the filter file.
Example 17 – Multiple filters

Assume you want to make a filter that adds a full stop to the string "Donald"
if it is at the end of as line, as well as changing it to "Donald is a cartoon" if it
is not at the end of a line. The filter would look like this:
"Donald$" "Donald."
"Donald.+$" "Donald is a cartoon."

Donald Donald.
Donald Duck Donald is a cartoon.
Donald... Donald is a cartoon.
This is what happens:

1. The original string will first go through the first filter.
2. If the first filter finds a match, the string will be translated and the
program will skip any remaining filters.
3. If the first filter fails to finds a match, the string will be passed on
unchanged to the second filter, if it exists.
4. If the second filter finds a match, the string will be translated and the
program will skip any remaining filters.
5. If the second filter fails to finds a match, the string will be passed on
unchanged to the third filter, if it exists. And so on.

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.
You can have several variables, as shown in Figure 8-2.
The first variable is called "$1" when it is used in the "Output from match" part
of the filter.
The second variable is called "$2".
More generally speaking, the n"th variable is called "$n".
There is also a special variable "$0" that represents the entire string.
Filter: "(.*):(.*):(.*)" "L$1\\nI$3"
Variables: $1 $2 $3
String: abc0001:4711:0002
Translated string: Labc0001

I0002
Figure 8-2. Variables in filters.
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.

Example 18 – Filters with variables

The example below shows how a filter creates a basic variable, "$1" by using
the characters "(Donald)". The string that is matched by the variable is then
used in the output part of the filter.
"(Donald)" "$1 Duck"

Donald Donald Duck
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"

donald duck
Donald Duck
The example below uses the variable "$0" that means the whole string.
"([Dd])onald" "$0 $1uck"

Donald Donald Duck
donald donald duck
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"

Donald Donal....d
donald donal....d
Donald Duck Donal....d Duck

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.
Example 19 – Filters with examples of greedy matches

"Donald(.*)([0-9]+)" "DD$1 $2"

Donald is 22 DD is 2 2
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"

Donald is 22 DD is 22
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 default is case sensitive match.

Matching Meta Characters as Normal Characters

Assume you want to match a "+" character used in a string. However, the "+"
character is by default interpreted as a meta character, as described on
page 8-7. To make the system interpret it as a normal character, add a "\"
(escape character) in front of it.
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.
. ^ $ * + ? { [ ] \ | ( )
Example 20 – Meta characters as normal characters

Assume you want to search for a string that contains the word "Donald"
followed by zero or more characters and then a "." character (a period). If the
regular expression finds a match, you want to change the "." to a "!" (an
exclamation mark).
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!"

Donald is 22. Donald is 22!
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
Example 21 – Splitting a string in two

"Donald(.*)([0-9]{2})" "DD$1\\n$2"

Donald is 22 DD is
22
Note! note the two rows.

The REPEAT Command

Sometimes you may need to convert a barcode string that contains a layout
string and a layout quantity. An example is if you have a cassette with boards,
and there is only one barcode label containing both the layout name and the
number of boards.
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;;;
 The word "REPEAT" followed by exactly one <Space> followed by one or

several digits followed by three semicolons.
The REPEAT command only applies to layout barcodes.
For an example of this function, see page 8-32.
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.
To get a comprehensive regular expression manual at the Linux prompt, type

man 7 regex at the prompt.
Testing the Barcode Translation Filter File

There is a barcode translation test program that can be used to test the filter file
that you are designing. The program tests text strings that you type in at the
prompt, not strings that are sent to the system from a barcode scanner.
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.

Basic Filters Quick Reference

Below is a quick reference table of the examples above. For more advanced
examples, see page 8-21.
Filter Original string Translated string

"Donald" "Duck" Donald Duck
"Donal." "Duck" Donala Duck
"Donald*" "Duck" Donaldd Duck
"Donal.*" "Duck" Donalabc Duck
"[dD]onald" "Duck" Donald Duck
donald Duck
"[Dd]onald" "Donald" donald Donald
Donald Donald
"([Dd])onald" "$1uck" donald duck
Donald Duck
"([Dd])onald" "$0 $1uck" Donald Donald Duck
donald donald duck
"(Donald)" "$1 Duck" Donald Donald Duck
Donald is a cartoon Donald Duck is a cartoon
"^(Donald)(.*)$" "$1 Duck$2" Donald is a cartoon Donald Duck is a cartoon
"^Donald(.*)([0-9]+)$" "DD$1 $2" Donald is 22 DD is 2 2
(and NOT 'DD is 22" since the
second match only needs at
least one.)
"^Donald(.*)([0-9]{2})$" "DD$1$2" Donald is 22 DD is 22

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
As a result of the scan, TPSys will load the

layout "abc0001" with the PCB ID "0002".
Figure 8-3. A schematic view of how the filter file works.

Filters for Adding Characters
Example 22 – Adding a prefix to a string

This example applies to the Assume that you have barcodes for boards that always contain only the layout
'bcTransSerStartA.dat" file name, without any prefix. The filter file adds the layout prefix "L" to the
and the beginning of the string, so that the system interprets the barcode string as a
'bcTransSerStartB.dat" file,
see page 8-2. layout name string. This is how the filer file would look, without any comment
lines.
"(.*)" "L$1"
The filter is built up in the following way:
– 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:

Demo LDemo
Demo7 LDemo7
4711 L4711
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.

Example 23 – Adding a prefix to a string with digits

This example applies to the This filter translates scanned barcodes to a PCB-id string. Only strings
"bcTransSerStartA.dat" file containing digits will be translated. To translate, an "I" is added in front of the
and the digits in the string. If the barcode parameter settings are using another prefix
"bcTransSerStartB.dat" file,
see page 8-2. character than "I", simply replace the "I" in the filter below with that character.
"([0-9]*)" "I$1"
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.

0001 I0001
Demo7 DemoI7
Note! the filter puts an "I" before the
first number in the string. A more
advanced filter is needed to remove
unwanted letters at the beginning of
the string.
Example 24 – Adding a prefix to a string with only digits

This example applies to the This filter translates a scanned barcode string to a PCB-id string. Only strings
"bcTransSerStartA.dat" file with only digits will be translated. The prefix for a PCB-id is "I" in this
and the example. To translate, an "I" is added in front of the digits in the string. If the
see page 8-2. barcode parameter settings are using another prefix character than "I", simply
replace the "I" in the filter below with that character.
"^([0-9]*)$" "I$1"
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.

0001 I0001
Demo7 Demo7
unchanged. The filter requires digits
only.

Example 25 – Component strings with or without prefixes

This example applies to the Assume your component barcode strings sometimes have prefixes and other
"bcTransComponent.dat" file, times not. This can for instance happen if your component barcode labels
see page 8-2. come from two different labelling systems. The filter below will do the trick.
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:

C1234567 C1234567
1234567 C1234567
HH-1234567 CHH-1234567
QT1234 QT1234

Example 26 – Appending characters to a string

This example applies to the Assume that you have a line with two machines, and are using MYPlan to
"bcTransSerStartA.dat" file optimize the line. The original layouts are split into two layouts by MYPlan,
and the one for each machine. A layout ending with "_1" is for machine number 1. A
see page 8-2. Note that each layout ending with "_2" is for machine number 2.
machine in the example
needs its own unique filter file. Also assume your boards have layout barcodes.
A filter file in machine 1 should append "_1" to all layout barcodes scanned
by that machine, so that the correct layout is loaded.
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.
Filter file for machine number 1:
"(.*)" "L$1_1"
Filter file for machine number 2:
"(.*)" "L$1_2"
Translated string, Translated string,

Original string
machine number 1 machine number 2
Demo LDemo_1 LDemo_2
Demo7 LDemo7_1 LDemo7_2
4711 L4711_1 L4711_2
 If your barcode on the boards already contains the prefix L, simply skip the
corresponding L in the filter files.

Filters for Splitting Strings
Example 27 – Splitting letters from digits

This example applies to the Assume your barcode string for boards contains a section with the layout name
"bcTransSerStartA.dat" file (letters only) and then a section with the PCB-id (digits only).
and the
"bcTransSerStartB.dat" file, IGNORECASE
see page 8-2. "([a-z]+)([0-9]+)" "L$1\\nI$2"
The filter is built up un the following way:
– The "IGNORECASE" characters changes the later matches so that

they are case insensitive. For further information, see page 8-16.
Layout name string. – The first set of "()" characters are used to create a first variable. For
further information, see page 8-14. This variable is needed, since it
will be used in the output part of the filter.
– The "[a-z]+" meta characters define the first pattern that is searched
for. In this case, the pattern is any string of letters with one or more
characters. For further information, see page 8-9.
PCB-id string. – The second set of "()" characters are used to create a second variable.
– The "[0-9]+" meta characters define the second pattern that is
searched for. In this case, the pattern is any string of digits with one
or more characters. For further information, see page 8-9.
– The "L" means that L will be placed first in the output string if the
pattern above finds a match. TPSys will interpret this as a layout
name. 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".
– The "\\n" characters define that there should be a new line in the
output string. TPSys will interpret this as the end of the first scan. For
further information, see page 8-17.
– The "I" means that I will be placed first in second line of the output
string if the pattern above finds a match. TPSys will interpret this as a
PCB ID. For further information, see page 8-14.
– The "$2" characters define that the string found in the second variable,
see above, should be added to the output string directly after the "I".

Note that this filter file only works correctly if the layout section only contains
letters and the PCB-id section only contains digits.

Demo0001 LDemo
I0001
Demo7-0002 LDemo
I7-0002
In this case the filter assumes that the
PCB-id starts at the first number. See
also Example 28 – Splitting letters
from digits.
Demo-0002 Demo-0002
unchanged. The filter requires letter
and digits only.
Example 28 – Splitting letters from digits

This example applies to the Assume your barcode string for boards contains a section with the layout name
"bcTransSerStartA.dat" file (letters only) and then a section with the PCB-id (digits only). This filter
and the contains a condition that the digits must be at the end of the line, otherwise no
see page 8-2. translation is made.
IGNORECASE
"^([a-z]+)([0-9]+)$" "L$1\\nI$2v

Demo0001 LDemo
I0001
Demo7-0002 Demo7-0002
and digits only to match.
Demo-0003 Demo-0003
and digits only.

Example 29 – Splitting a string with known string lengths

This example applies to the Assume you have a barcode string that starts with a component name with
"bcTransComponent.dat" file, seven characters, and the remainder of the string contains irrelevant
see page 8-2. information. The component name is without the "C" prefix, so the filter also
needs to add that.
"^(.{7})(.*)$" "C$1"
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.

549S13605019 C549S136
1234567890 C1234567
123-45-67890 C123-45-
ABCD ABCD
unchanged. The filter requires at least
7 characters.
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.
An alternative, filter solution is shown behow:

v^([0-9a-zA-Z]{7}).*$" "C$1"
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.

549S13605019 C549S136
1234567890 C1234567
123-45-67890 123-45-67890
unchanged. The filter requires that
the first seven characters are letters or
digits to match.
ABCD ABCD
7 characters.

Example 30 – Splitting a string with known string lengths

This example applies to the Assume you have a barcode string that starts with three irrelevant characters,
"bcTransComponent.dat" file, followed by 10 characters that form the component name, and the remainder
see page 8-2. of the string contains the component batch string.
"^.{3}(.{10})(.+)$" "C$1"\\nB$2"
"^.{3}(.{10})$" "C$1"
The first line of the filter is built up un the following way:
– 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 "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.

@@@1234567890334455 C1234567890
B334455
@@@1234567ABC C1234567ABC
Note! the string will pass through the
first filter unchanged but be matched
and translated by the second filter.
@@@123456789 @@@123456789
13 characters.

Example 31 – Splitting strings containing one divider

This example applies to the Assume you have a barcode string that contains both the layout name and the
"bcTransSerStartA.dat" file PCB-id, separated by a "-" character.
and the
"bcTransSerStartB.dat" file, "(.*)-(.*)" vL$1\\nI$2"
see page 8-2.

Demo-0001 LDemo
I0001
Demo7-0002 LDemo7
I0002
Demo7 Demo7
unchanged. The filter requires a "-".
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 "\+".
Example 32 – Splitting with or without a divider

This example applies to the Assume that your barcode strings contain both layout name and PCB-id in the
"bcTransSerStartA.dat" file same string. The layout name is only letters and the PCB-id is only numbers.
and the Some of the barcodes have a "-" character as a divider, but not all of them. To
see page 8-2. handle this, the filter file has two filters.
IGNORECASE
Filter 1 for barcodes without "^([a-z]+)([0-9]+)$" "L$1\\nI$2"
divider. #
#
Filter 2 for barcodes with "^([a-z]+)-([0-9]+)$" "L$1\\nI$2"
divider '-'.
The lines that start with # are comment lines and are ignored.

Demo0001 LDemo
I0001
Demo-0002 LDemo
I0002
Demo7-0003 Demo7-0003
unchanged. The filter requires letters
only before the divider.

Example 33 – Splitting strings containing two dividers

This example applies to the Assume that you have a combination barcode string with three sections
"bcTransSerStartA.dat" file separated by ":". The layout name is in the first section. The second section
and the contains a string that should not be passed on to TPSys. The PCB-id is in the
see page 8-2. third section.
"^(.*):(.*):(.*)$" "L$1\\nI$3"
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.

abc0001:4711:0002 Labc0001
I0002
Demo7::0003 LDemo7
I0003
Example 34 – Splitting strings containing three dividers

This example applies to the Assume that you have a combination barcode string with four sections
"bcTransComponent.dat" file, separated by a comma (,). The component name is the second section and the
see page 8-2. component batch is the third section. The first and the fourth sections of the
string are not needed by the system.
"(.*),(.*),(.*),(.*)" "C$2\\nB$3"
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.

AA,123456,GGG1234,RoHS C123456
BGGG1234
AA,123456,GGG1234 AA,123456,GGG1234
unchanged. The filter requires three
dividers.

Filters for Repeating Strings
Example 35 – Converting a layout + quantity barcode string to a

succession of layouts
This example applies to the If you are using serial start and have a loader with several boards in a cassette,
"bcTransSerStartA.dat" file you may have a barcode label that contains the layout name and the number of
and the boards. TPSys needs one string for every board in the layout if you are using
see page 8-2. serial start. A filter is needed to convert the barcode label data. This filter uses
the REPEAT function described on page 8-18. Note that the filter will not
produce one string for every board in the cassette, it will create a REPEAT
order that is then used by the system.
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.
This is how the filter looks:

"....(..)(.*)" "LREPEAT $1;;;$2-1"
The table below shows how this example translates various strings.
Original string Translated string Effect

123409TestLayout LREPEAT 09;;;TestLayout-1 The system will interpret this
as nine successive boards with
the layout name
"TestLayout-1"
000099123456 LREPEAT 99;;;123456-1 The system will interpret this
as 99 successive boards with
the the layout name
"123456-1"
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"

Blocking Garbage Strings
Example 36 – Skipping unwanted messages

This example applies to all If your barcode scanner occasionally returns error messages, you may want to
four filter files, see page 8-2 block them with a filter. To do so, add the following lines at the beginning of
and 8-3. your filter file:
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


Mycronic TPSys 3.3 Appendix A – Messages Reference Guide
Appendix A – Messages Reference Guide

This reference guide explains the messages that can be displayed by TPSys
3.3.
If a message appears that is not included in this document, please contact

Mycronic support and describe the message.
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.
4002720-EN – Software Manual Rev. A 2016-04 A-1

Appendix A – Messages Reference Guide TPSys 3.3 Mycronic
General Message Format

Error messages are displayed in the following format:
<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:
E-AUTOFID-35: Failed to find fiducial mark [***]''
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.
A-2 Rev. A 2016-04 4002720-EN – Software Manual

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.
AUTOFID Group, see page A-6.

Messages from the automatic fiducial mark search routines.
AUTOTEACH Group, see page A-8.
Messages from the Autoteach routine for packages.
AXIS Group, see page A-10.
Machine high level errors.
BACKUP Group, see page A-12.
Messages from the automatic scheduled backup routines.
BADBOARD Group, see page A-12.
Messages from the bad board search routines.
BC Group, see page A-14.
Messages from the barcode utility.
XWBC Group, see page A-20
Messages from the barcode utility.
BRDH Group, see page A-20.
Messages from the board handler routine (controls the internal conveyor
system).
CALIBRATION Group, see page A-21.
Messages from the camera system.
CAME Group, see page A-21.
Messages from the camera system.
DATAS Group, see page A-21.
Messages from the server.
EXORD Group, see page A-21.
Messages from the internal executor order routines.
EXP Group, see page A-22.
Messages from the export routines.
FTP Group, see page A-22.
Messages from the FTP transfer routines.
GLU Group, see page A-23.
Messages from the glue pot.
GRAP Group, see page A-23.
Messages from the graph system.

HEATMON Group, see page A-24.

Messages from the X beam heat monitoring process.
HOPT Group, see page A-24.
Messages from the HYDRA optimization process.
HRDW Group, see page A-24.
Machine hardware control errors.
HTLM Group, see page A-27.
HYDRA tool manager errors.
HWICLIENT Group, see page A-29.
Messages from the HWI (hardware interface) client side.
IMAGE_ORDER Group, see page A-30.
Messages from process communication related to image processing
process.
IMGPROC Group, see page A-30.
Messages from the image processing process.
IMP Group, see page A-30.
Messages from data import routines.
IMPORTD Group, see page A-35.
Messages from the import daemon.
LSCD Group, see page A-35.
Messages from the Linescan camera process.
MAGREF Group, see page A-36.
Messages from the magazine fiducial mark search routines.
MHPR Group, see page A-37.
Messages from the magazine handler process.
MIPR Group, see page A-41.
Messages from the magazine interface process.
MMI Group, see page A-44.
Messages from the man machine interface process.
MNTSYNC Group, see page A-46.
Messages from the man machine interface process.
MONT Group, see page A-46.
Messages from the mounter process.
MOT Group, see page A-56.
Messages from the motor control computer software.
MOTIONDEV Group, see page A-107.
Messages from motion devices (joystick, trackball and so on).
MOTQ Group, see page A-107.
Messages from the low level communication with the motor control
computers.
OPTCENT Group, see page A-109.
Messages from the optical centering routines.

OPTCORR Group, see page A-119.

Messages from the optical calibration routines.
OPTP Group, see page A-121.
Messages from the optimizer process.
ORGP Group, see page A-123.
Messages from the organizer process.
OSM Group, see page A-125.
Operating system messages. These are messages forwarded from the
operating system.
PARFILE Group, see page A-125.
Messages from the parameter file reader.
QWIN Group, see page A-126.
Messages from the internal operator interface utility.
SERCOM Group, see page A-126.
Messages from the serial communication routines used by directline
communication.
SERSTART Group, see page A-127.
Messages from the serial start (barcode) facility.
SHDB Group, see page A-128.
Messages from the data sharing routines.
TCP Group, see page A-129.
Messages from the shared database communication routines.
TEX VISION Group, see page A-129.
Messages from the TEX VISION routines.
TLMN Group, see page A-132.
Tool manager errors.
UCOPY Group, see page A-135.
Messages from the UNIX copy routines.
UNIX Group, see page A-135.
Messages originating from the UNIX system itself.
USR Group, see page A-135.
Messages originating from the user management process.
VACC Group, see page A-136.
Messages from the vacuum system.
VER Group, see page A-136.
Messages from the electrical verifier.
VISION Group, see page A-137.
Messages from the vision hardware.
XINSP group, see page A-138.
Messages generated when inspecting components on trays with the PVC.

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.
GROUP_NAME-1: Message text with [Data1] and [Data2]

A detailed description of the meaning of the message. This may be several
lines long.
– Bulleted paragraphs following the description like this one indicate a
probable cause of the message or an action to take. Not all messages
indicate a problem which needs action taken, so some of them won't
have paragraphs like this one.
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.

AUTOFID-10: ID: [***]'Fiducialmarkisnottaught'

The fiducial mark is defined in the database but it is not taught.
– Teach the fiducial mark.
AUTOFID-11: ID: [***]'Badsearchareadefinition'
The size of the fiducial mark search area is bad.
– The scan area is bigger than the field of view of the camera.
– The length and/or the width of the scan area is zero (0).
– The database is corrupt.
– The search area is smaller than the fiducial mark.
AUTOFID-13: Cannot read the correction data. (Try to re-calibrate camera)
The database containing data about the distortion of the lens of the X-
wagon camera cannot be read.
– The camera is not calibrated.
AUTOFID-14: Phase error
Synchronization error between the client process (Mounter) and the
server process (Img).
– Internal software error. Make a 'savestat' diskette and contact
Mycronic support.
AUTOFID-15: Result is invalid
Synchronization error. The client process (Mounter) tries to read the
result of a fiducial mark search before the result is valid.
Mycronic support.
AUTOFID-34: Size of detected fiducial mark [***]'isoutofbounds'
The fiducial mark was found be the measured size of the fiducial is
outside the tolerances specified for the fiducial mark in the fiducial mark
edit.
– Dimension tolerances too narrow. Increase the tolerances.
– The camera is not calibrated. Re-calibrate the camera.
AUTOFID-35: Failed to find fiducial mark [***]''
The fiducial mark was not found during fiducial mark search.
– Wrong dimensions specified for the fiducial mark. Check the
dimensions 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 search method or search contrast. Try another coarse search
method and/or coarse search contrast.
AUTOFID-36: Not enough edge points to fit fiducial mark [***]''
The specified fiducial mark was found in the coarse alignment step but it
was not possible to determine the final position. Too few fiducial mark
edge points were detected.

– 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.
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.
AUTOTEACH-0: No leads found

The method failed to find any solder balls or leads; this was probably
caused by to small a contrast between the solder balls and the component
body.
Adjust the illumination and run Autoteach again. Use Algorithm: Bright
on dark if you want the solder balls to be lighter than the component body
without amplifying objects like text or wiring. Use Algorithm: Bright on
bright if you want to illuminate the component in such a way that a dark
ring is formed around each solder ball. A high proportion of front light
generally achieves this ring. For leaded devices you want a high contrast
between the lead and the background around the lead.
For solder ball packages one can try to specify the number of balls on the
package manually and try different algorithms.

AUTOTEACH-1: Failed to measure pitch

The method failed to measure the pitch of the component.
– The component may lack a grid.
–
– Autoteach has detected too few solder balls or leads to measure the
pitch.
– Enter the pitch manually.
AUTOTEACH-2: Error in camera parameter file
There is an error in the camera parameters that prevents Autoteach from
transforming the measured image coordinates of the balls / leads to metric
coordinates.
– Check the parameters for the camera in question and re-calibrate the
camera if necessary.
AUTOTEACH-3: Unable to load camera parameter file
Autoteach failed to load the parameter file for the camera.
– Check that the file exists, if not restore the parameter file with a
backup copy.
AUTOTEACH-4: No more leads to remove
The user tried to delete a lead but there are no more leads left to delete.
AUTOTEACH-6: Unable to adjust the leads to a grid with the pitch [***] mm
The measured or manually entered pitch is out of range.
– If the Pitch field in the Autoteach parameters box was set to Auto, try
entering the pitch manually.
AUTOTEACH-7: Cannot find all leads
This error occurs if the user has specified the number of leads manually
in the Autoteach parameters box but the method didn't find the specified
number of leads.
– Check that the number of entered leads is correct.
– Teach the component using a better illumination, see AUTOTEACH-
0: No leads found above.
– Teach the component using a different algorithm.
AUTOTEACH-8: Failed to load camera correction data
Autoteach was unable to load the calibration data for the camera.
– Re-calibrate the camera.
AUTOTEACH-10: Cannot teach vision data for a package without leads
It's not possible to teach package vision data for a package that doesn't
have any leads.
– Correct the package definition and try to teach vision data again.
– Run Autoteach of mechanical and vision data for the package.

AUTOTEACH-11: Failed to teach illumination- and vision parameters

Autoteach failed to find illumination and vision parameter that makes the
part pass optical centering.
– The mechanical model of the package may be incorrect. Check the
package definition.
– It may not be possible to vision center the package in the camera used.
Try teaching the package in another camera.
– The package may have been picked off center or rotated. When
teaching only vision data it is important to locate the corners of the
component correctly.
– The component rotates on the tool. It is important that the component
cannot rotate on the tool during the teach. Ensure using an appropriate
tool.
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.
– 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.
AXIS-Z/3: Timeout in wait for Z indicator reaction

The Z indicator did not register a hit on the board or component in feeder.
– Dirt in tool holder.
– Other hardware problem.
AXIS-C/4: Not properly out when expected
The centering jaws did not open properly.
– High friction.
– Mechanical centering jaws do not move freely.

AXIS-<Axis>/5: Not properly up when expected

The Z or HZ axis is not above safe position when expected.
– Axis does not move correctly.
– Hardware problem.
AXIS-Theta/7: Axis not stable
The Theta axis did not stop at correct position after a MOVGO
movement.
AXIS-<Axis>/8: Timeout in wait for axis to be idle
The axis did not reach idle status within specified time.
AXIS-<Axis>/9: Axis has unstable zero point
The zero position differs too much from the last measurement.
– Transducer problem.
– Cabling problem.
– Transducer not properly fitted.
AXIS-<Axis>/10: HYDRA indicator activated during tool fetch
The HYDRA unit failed to press the mount tool tip onto the HYDRA
toolpipe. The HYDRA tool locking mechanism is not working properly.
– The HYDRA tool pipe locking mechanism may need adjustment.
– The HYDRA latch unit are faulty and need to be replaced.
BACKUP Group
These messages are generated by the scheduled automatic backup routine.
BACKUP-1: Scheduled backup failed.

BACKUP-2: Scheduled backup failed collect data.
BACKUP-3: Scheduled backup failed to write data
BACKUP-4: Scheduled backup failed, no database connection
BADBOARD Group
These messages are generated by the bad-board vision routines.
BADBOARD-0: Search area too big

The width (X wise) of the search (scan) area is too big.
– The default magnification for the X-wagon camera could be wrong.
Check parameters 51.0310 Characteristics; KXX and 51.0311
Characteristics; KYY.


The same as for BADBOARD-0.
The height (Y-wise) of the search (scan) area is too big.
BADBOARD-3: Indata mindimension'outofrange'
The software calculates, from the size of the scan area, the size of the
smallest detectable object in the scan area. The shortest side of the scan
area (in pixels) is divided by 3. The calculated value must be within the
range 3..100.
– The size of the scan area is too small or too big.
BADBOARD-4: Parameter
MarkMinandMaxcontrast'isillegal.CheckparameterfileVision'
The value of parameter 41.0012 Bad Board; Mark points with max and/or
min contrast is incorrect.
– A bad value has been entered by editing the parameter using a text
editor.
– The parameter file is corrupt.
BADBOARD-5: Too small search area
The scan area is too small.
BADBOARD-6: Did not find any contrast at all
Not used.
BADBOARD-7: Phase error
– Internal software error. Make a ’savestat’ diskette and contact
Mycronic support.
BADBOARD-8: Result is invalid
Mycronic support.

BADBOARD-9: Frame grabbing failed

camera.
grabber card.
BC Group
These messages are generated by the barcode utility.
BC-1: Serial communication error

Not used.
BC-2: Barcode [***] unknown
The prefix on the barcode read by the barcode scanner did not match any
known pattern.
– Barcode label damaged or dirty.
– Check the settings in parameter 123.0211 Component; Prefix1 and the
parameters following directly after it.
BC-3: Magazine [***] unknown
The scanned magazine barcode does not match any known magazine
barcode.
– Magazine not in database.
BC-4: Component [***] unknown
The scanned component barcode does not match any known component
barcode.
– Component not in database.
BC-5: Component [***] already exists
The scanned component barcode is already used for another component.
– Component not in database.
BC-6: Layout [***] unknown
Not used.
BC-7: Barcode read error
Failed to read the barcode.
– Faulty barcode scanner.

BC-8: Failed to load [***] in [***]

Failed to load the specified component into the specified magazine.
– Internal software error.
BC-9: Feeder [***] in magazine [***] occupied
The specified feeder is already loaded with another component.
– Use another feeder or remove old component from feeder.
BC-10: Cannot edit magazine [***] (in other machine)
The magazine is inserted in another machine. To reduce the risk of mount
failures it is not allowed to modify the feeder contents in a magazine
inserted in another machine.
– Locate magazine and remove.
BC-11: Magazine [***] is full
The scanned magazine has no empty feeder positions.
– Locate magazine and remove.
BC-12: Magazine [***] has less than [***] feeders
A feeder position outside the magazine’s range was scanned.
– Select a feeder position within the magazine range.
BC-13: Component [***] reloaded in [***], feeder [***]
Verification message.The scanned component was reloaded in the
scanned magazine feeder position.
BC-14: Component [***] loaded in [***], feeder [***]
Verification that the scanned component was loaded in the scanned
magazine feeder position.
BC-15: Too large step length ([***] > [***])
The scanned step length is too large. The message also indicates the
maximum allowed step length.
– Set step length to the correct value.
BC-16: User not authorized
The user has scanned data that he/she is not authorized to change
according to the user access levels.
BC-17: Removable feeder [***] unknown
Not used.
BC-18: Removable feeder barcode [***] is invalid
The barcode starts with a prefix for removable feeders, but the barcode
does not contain a valid serial number for a removable feeder.
BC-19: Barcode must consist of digits only
This message follows BC-18. The barcode, which is expected to be a
removable feeder serial number, must only contain digits.
BC-20: Invalid barcode length
This message follows BC-18. The barcode, which is expected to be a
removable feeder serial number, does not have the expected length.

BC-21: Component [***] loaded in removable feeder [***]

Verification that the scanned component was loaded in a removable
feeder.
BC-22: Magazine [***] already exists
An already defined magazine barcode was scanned when a new magazine
barcode was expected.
BC-23: Layout [***] already exists
An already defined layout barcode was scanned when a new layout
barcode was expected.
BC-24: Component [***] reloaded in removable feeder [***]
Verification message: The scanned component was reloaded in a
removable feeder.
BC-25: Feeder for demonstration use only
The scanned removable feeder is for demonstration use only. It cannot be
loaded in the machine.
BC-26: Prefix [***] is already used
A barcode prefix is used twice for different types of objects.
– A prefix can only be used for one type of object.
BC-27: Too small step length ([***] < [***])
The scanned step length is too small. The message also indicates the
minimum allowed step length.
– Set step length to the correct value.
BC-28: Y-wagon tray [***] is unknown
The scanned YWM tray barcode does not match any known YWM tray
barcode.
– Define the tray in the YWM Trays window.
BC-29: Tray wagon tray [***] is unknown
The scanned TWM tray barcode does not match any known TWM tray
barcode.
– Define the tray in the TWM Trays window.
BC-30: TEX/ATM tray [***] is unknown
The scanned TEX or ATM tray barcode does not match any known TEX
or ATM tray barcode.
– Define the tray in the TEX Trays window.
BC-31: Y-wagon tray position [***] is unexpected
A YWM tray position barcode was scanned, but the system was not in the
correct mode to accept it.
– An YWM tray position barcode may be scanned in the YWM Tray
Positions window. It may also be scanned in the YWM Trays window
(in the Position field) or as a part of a load sequence.
BC-32: Y-wagon tray position [***] is unknown
The scanned YWM tray position barcode does not match any known
YWM tray position barcode.

– Define the tray position in the YWM Tray Positions window.

BC-33: Tray wagon tray position [***] is unexpected
A TWM tray position barcode was scanned, but the system was not in the
correct mode to accept it.
– A TWM tray position barcode may be scanned in the TWM Tray
Positions window. It may also be scanned in the TWM Trays window
(in the Position field) or as a part of a load sequence.
BC-34: Tray wagon tray position [***] is unknown
The scanned TWM tray position barcode does not match any known
TWM tray position barcode.
– Define the tray position in the TWM Tray Positions window.
BC-35: TEX/ATM tray position [***] is unexpected
A TEX or ATM tray position barcode was scanned, but the system was
not in the correct mode to accept it.
– A tray position barcode may be scanned in the TEX Tray Positions
window. It may also be scanned in the TEX Trays window (in the
Position field) or as a part of a load sequence.
BC-36: TEX/ATM tray position [***] is unknown
The scanned TEX or ATM tray position barcode does not match any
known TEX or ATM tray position barcode.
– Define the tray position in the TEX Tray Positions window.
BC-37: Y-wagon tray [***] already exists
An already defined YWM tray barcode was scanned when a new YWM
tray barcode was expected.
– Use a new name for the new YWM tray.
BC-38: Tray wagon tray [***] already exists
An already defined TWM tray barcode was scanned when a new TWM
tray barcode was expected.
– Use a new name for the new TWM tray.
BC-39: TEX/ATM tray [***] already exists
An already defined TEX or ATM tray barcode was scanned when a new
TEX or ATM tray barcode was expected.
– Use a new name for the new TEX or ATM tray.
BC-40: Y-wagon tray [***] inserted in [***]
Verification message. The tray was inserted in the YWM on the named
machine, and the components are available.
BC-41: Tray wagon tray [***] inserted in [***]
Verification message. The tray was inserted in the TWM on the named
BC-42: TEX/ATM tray [***] inserted in [***]
Verification message. The tray was inserted in the TEX or ATM on the
named pallet, and the components are available.

BC-43: Y-wagon tray [***] re-inserted in [***]

Verification message. The tray was re-inserted in the YWM on the named
BC-44: Tray wagon tray [***] re-inserted in [***]
Verification message. The tray was re-inserted in the TWM on the named
BC-45: TEX/ATM tray [***] re-inserted in [***]
Verification message. The tray was re-inserted in the TEX or ATM on the
named pallet, and the components are available.
BC-46: Y-wagon tray position [***] already exists
An already defined YWM tray position barcode was scanned when a new
YWM tray position barcode was expected.
– Use a new name for the new YWM tray position.
BC-47: Tray wagon tray position [***] already exists
An already defined TWM tray position barcode was scanned when a new
TWM tray position barcode was expected.
– Use a new name for the new TWM tray position.
BC-48: TEX/ATM tray position [***] already exists
An already defined TEX or ATM tray position barcode was scanned when
a new TEX or ATM tray position barcode was expected.
– Use a new name for the new TEX or ATM tray position.
BC-49: Failed to insert [***] into the Y-wagon magazine on [***]
An attempt to insert the scanned YWM tray on the specified machine
failed.
– Probably a database error.
BC-50: Failed to insert [***] into the Tray wagon magazine on [***]
An attempt to insert the scanned TWM tray on the specified machine
failed.
BC-51: Failed to insert [***] into the [***] TEX/ATM magazine
An attempt to insert the scanned TEX or ATM tray into the specified
pallet failed.
BC-52: Tray type [***] is not found
An attempt was made to load a tray, but the tray refers to a non-existing
tray type.
– Check the tray definition and modify the tray type reference to an
existing tray type.
BC-53: Quantity [***] is greater than maximum quantity [***] for tray type
[***]
An attempt was made to set the quantity for the tray, but the referred tray
type cannot hold that many components.
– Set the tray quantity to no more than the maximum quantity which is
Rows*Columns for the referred tray type.

BC-54: Pallet [***] unexpected

A pallet barcode was scanned, but the system was not in the correct mode
to accept it.
– A pallet may be scanned as a part of a load sequence only.
BC-55: Removed Y-wagon tray [***] from tray position [***]
The YWM tray was disconnected from the YWM tray position.
– An YWM tray was inserted by using the tray position occupied by this
tray.
BC-56: Removed Tray wagon tray [***] from tray position [***]
The TWM tray was disconnected from the TWM tray position.
– A TWM tray was inserted by using the tray position occupied by this
tray.
BC-57: Removed TEX/ATM tray [***] from tray position [***]
The TEX or ATM tray was disconnected from the TEX or ATM tray
position.
– A TEX or ATM tray was inserted by using the tray position occupied
by this tray.
BC-58: Invalid step length
The scanned step length was invalid for the magazine. The default
component step length will be used instead.
BC-59: Invalid default step length for component [***]
The scanned component’s default step length was invalid for the
magazine. A value of 4 mm will be used instead.
BC-60: Step length is ignored for stick magazines
A step length barcode was scanned together with a stick magazine. The
step length is ignored.
BC-61: Tray angle ([***]) must be a multiple of 90
The scanned tray angle was not a multiple of 90 degrees.
– Replace the erroneous barcode label and then load the tray with the
barcode scanner again.
– Load the tray manually in TPSys.
BC-62: Feeder [***] cleared
Verification message. A barcode to clear a feeder was scanned. The
feeder has now been cleared from any component data previously
associated with the feeder.
BC-63: Feeder [***] in magazine [***] cleared
Verification message. A barcode to clear a feeder in the magazine was
scanned. The feeder has now been cleared from any component data
previously associated with the feeder.
BC-64: Magazine [***] cleared
Verification message. A barcode to clear the magazine was scanned. All
feeders in the magazine have now been cleared from any component data
previously associated with the feeders.

XWBC Group
This message is generated by the barcode utility.
XWBC-0: Not able to decode barcode

The barcode image could not be decoded.
BRDH Group
These messages are generated by the board handler routines.
BRDH-1: Not initiated

Board handler software on MOT board not initiated.
– Software error.
BRDH-2: Board fetch aborted
Board fetch aborted by operator.
BRDH-3: Board leave aborted
Board leave aborted by operator.
BRDH-4: Cannot use fast change, different fetch and leave positions
Board leave aborted by operator.
– The fast change algorithm requires identical fetch and leave positions.
If the positions are not identical the routines will fall back to normal
leave/fetch.
– Re-adjust the fetch/leave positions for conveyor.
BRDH-5: Conveyor sensors activated after board change
After a board was fetched from the external conveyor, the internal
conveyor sensors indicated a board jam situation.
– The conveyor sensors are incorrectly adjusted or broken.
– A board has been left halfway inserted in the internal conveyor.
BRDH-6: Measured board height too small. Board lost?
After clamping a board in the internal conveyor, the measured board
thickness was very small (less than 0.2 millimeters)
– The board was lost during transport.
– The board is thinner than the system can handle.
– The conveyor height axis zero point was not measured correctly
during conveyor initialization.
BRDH-7: Incorrect sensor reading detected
When loading or unloading a board in the internal conveyor, the conveyor
board detection sensors are giving incorrect sensor readings.
– The board was lost during transport.
– Parameter 92.0014 Fetch; Conveyor speed during manual fetching is
set to a too high speed.

– The conveyor sensors are incorrectly adjusted or broken.

BRDH-8: Board wait aborted
Production was run in auto-start mode and the operator aborted board
fetch from the external conveyor.
BRDH-9: Cannot use fast change, different fetch and leave speeds
When loading or unloading a board in the internal conveyor, the machine
does not run at full speed.
– The fast change algorithm requires identical fetch and leave speeds. If
the speeds are not identical the routines will fall back to normal
leave/fetch.
– Re-adjust the speeds of the external conveyors and update parameters
92.0013 Fetch; Internal conveyor speed and 92.0023 Leave; Internal
conveyor speed.
CALIBRATION Group
These messages are generated by the calibration routines.
CALIBRATION-0: Incorrect model in the machine calibration file.

The machine calibration file has an incorrect machine model. The file will
be ignored and all calibration steps will be marked as uncalibrated.
CAME Group
Camera system interface routines.
CAME-0: Error reading parameter file

Cannot read parameter.
– Corrupted parameter file.
– Software error.
DATAS Group
Not documented.
All messages in this group indicate an internal software error. If a message

from this group appears, make a ’savestat’ diskette and send it to Mycronic
support.
EXORD Group
These messages are generated by the internal executor order routines.
EXORD-1: Wait called without current order

Internal software problem.
– Make a ’savestat’ diskette and contact Mycronic support.

EXORD-2: Order already executing

EXP Group
These messages are generated by the export routines.
EXP-900: Empty layout

The layout can not be exported in mount list format since there are no
PCBs or panels in the layout.
EXP-901: Cannot export layout in mountlist format. Different boards
The layout can not be exported in mount list format since it contains more
than one type of PCB or panel or a mix of PCBs and panels.
EXP-902: No PCB in layout
There is a panel in the layout, but the panel does not contain any PCBs. A
layout with no PCBs cannot be exported in mount list format.
EXP-903: Cannot export layout in mountlist format. Different PCBs
There is a panel in the layout, but it contains more than one type of PCB.
A layout can not be exported on mount list format if it contains more than
one type of PCB.
EXP-904: Exported mountlist contains an unknown PCB
A layout with an unknown PCB type has been exported in mount list
format.
EXP-905: Cannot export layout in mountlist format. Unknown panel
The layout cannot be exported in mount list format since it contains an
unknown panel.
FTP Group
These messages are generated by the FTP transfer routines.
FTP-1: Connection refused

FTP server refused to open a connection.
– Server not up.
– Wrong server name specified.
– Problem with FTP service in server.
FTP-2: Incorrect logon
FTP-3: Logon failed
FTP login failed.
– Wrong user name and/or password specified.
FTP-4: No such file or directory
Wrong directory specified

FTP-5: Please log on with user name and password

FTP login failed.
– Wrong user name and/or password specified.
FTP-6: Not connected
FTP connection failed or terminated by server. Some FTP servers
disconnect after a specific time so the connection may be lost.
– Check server.
– Try again.
FTP-7: Unknown host
FTP server host name unknown.
– Wrong host name specified.
– Host name not specified in configuration files.
FTP-8: No plain file
FTP-9: Permission denied
FTP-10: No route to host
FTP server host name not reachable.
– Wrong host name specified.
– Network configuration error.
GLU Group
Glue station control routines.
GLU-0: Error reading parameter file

– Software error.
GRAP Group
Graphical interface routines.
GRAP-0: Error reading parameter file

– Software error.

HEATMON Group
Messages from the X-beam heat deformation monitoring process.
HEATMON-1: X-beam sensor value out of range

The sensor that detects X-beam heat deformation is malfunctioning.
– The X-beam sensor is saturated. Manually adjust the X-beam sensor
position, using the service program to monitor the sensor values.
– The X-beam sensor, or its cable, is damaged.
– The X-beam sensor AD-converter or other sensor-related electronics
is damaged.
– The steel belt used as a reference for the X-beam sensor is not
tensioned enough. Adjust the tension.
HEATMON-2: Right X-beam sensor value out of range
See HEATMON-1 above.

HEATMON-3: Left X-beam sensor value out of range
See HEATMON-1 above.
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.
HRDW-0: Initiating hardware

Information message. The message indicates that the system is
downloading software to the motion control computers.
HRDW-1: Error during software download to board [***]. Loadmot returned
[***]
Cannot download software to the specified board. The message also
specifies the error number returned from the download operation.
– Board not inserted or not properly inserted.
– Hardware error.

HRDW-2: Hardware initiation failed

Failed to initialize motors. This is in some cases a normal system
behavior. Always check previous messages on the monitor for the cause
of the error.
– Hardware error. (Previous messages should give more information
about the source of the error).
HRDW-3: Hardware not initiated
The application tried to move an axis or send some other message before
the hardware was initiated.
– Operator chose not to initiate the hardware.
– Software problem, unless this happens in combination with messages
that indicate that there is a hardware problem somewhere in the
system.
HRDW-4: Hardware initiation ready
Information message. This message indicates that software download to
motion control computers is ready.
HRDW-5: Emergency stop button not released
An application tried to move a axis while emergency button was pressed,
machine cover open or a conveyor hood open.
– Rear conveyor hood is not properly closed.
– Operator error.
– Hardware problem with the emergency buttons or some other related
hardware.
HRDW-6: Calibrating HYDRA indicators
Information message.
HRDW-7: HYDRA indicator calibration ready
HRDW-8: Light curtain test failed
The test of the light curtain has failed. This test is performed every time
during hardware initialization. If the parameter 4.1101 X Settings;
Disable X on Light Curtain test failure fails is set to Yes, the hardware
initialization will also fail.
– Hardware problem with the light curtain.
HRDW-100: Mount interrupted
Some hardware or parameter check has failed and the system cannot
safely operate the machine.
HRDW-101: Focal distance of HYDRA camera lower than maxSafePos
Parameter 52.0204 Position; Centering level is outside safe limits.
– Check parameters.

HRDW-102: FirstPickEof (Z axis) not 200 µm greater than maxSafePos

Parameter 6.1002 Z Settings; EOF in first pick (without tool) is outside
safe limits.
– Use the ’autoInstall’ routines to set parameters.
HRDW-103: All system voltages are not within limits.
Some system voltage is outside specified limits.
– Check fuses.
– Check system voltages.
HRDW-104: Focal distance of Linescan camera lower than maxSafePos
Parameter 57.0204 Position; Focal distance or parameter 58.0204
Position; Focal distance is outside safe limits.
HRDW-106: Failed to measure X-beam shape
The sensors that measure the straightness of the X beam failed to gather
enough data.
– Error on the CAN hardware.
– Internal software error, TPSys/servo.
HRDW-107: Cannot measure system voltages
The machine failed to verify that the system voltages are correct.
– Error on MOT-M board.
– Error on CMOT board.
– Error on MI board.
HRDW-108: Initiating right X-wagon hardware
HRDW-109: Initiating left X-wagon hardware
HRDW-110: Right X-wagon hardware initiation failed
of the error.
Hardware error. (Previous messages should give more information about
the source of the error).
HRDW-111: Left X-wagon hardware initiation failed
of the error.
Hardware error. (Previous messages should give more information about
the source of the error).

HRDW-112: Right X-wagon hardware not initiated

system.
HRDW-113: Left X-wagon hardware not initiated
system.
HRDW-114: Right X-wagon hardware initiation ready
HRDW-115: Left X-wagon hardware initiation ready
HRDW-116: Cannot center using LSC due to risk of collision with an already
mounted component
There is an already mounted component that is too high to be safe carrying
picked components at the LSC focal plane.
– Check that already mounted packages do not have too high height
tolerances.
– Use grouping to mount high components later in the mount sequence.
HRDW-200: Initiating conveyor
downloading software to the conveyor motor control computer.
HRDW-201: Conveyor initiation failed
Failed to initialize conveyor motor.
– Hardware error. (Previous messages should give more information
about the source of the error).
HRDW-202: Conveyor initiation ready
Information message. This message indicates that the software download
to the conveyor motor control computer is ready.
HTLM Group
These messages are generated by the HYDRA tool manager routines.
HTLM-1: HYDRA tool number [***] is missing

TPSys has checked for the presence of a specific HYDRA tool and it was
not found.

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.

HTLM-12: Error reading file [***]

Cannot read file with current HYDRA tool state information.
– Corrupted currenthtools file.
– Software error.
HTLM-13: Error writing file [***]
Cannot write to file with current HYDRA tool state information.
– Corrupted currenthtools file.
– Software error.
HTLM-14: Parameters for HYDRA tool banks are not consistent
The tool types in the parameter file do not make sense. Contact Mycronic
service.
HTLM-15: Uninstall all HYDRA tool banks, and reinstall
This is advice that can follow one of the above errors.
HTLM-16: Cannot go down in HYDRA tool bank keyhole
The HYDRA tool tube was unable to move far enough down in the tool
bank to leave a tool.
– Check for obstructions.
HTLM-17: Tool leave fail. Group front, tool [***] (set to error)
This is information on which tool has failed. It is accompanied by error
message HTLM-16.
HTLM-18: Tool leave fail. Group back, tool [***] (set to error)
See HTLM-17.
HTLM-19: HYDRA tool [***] unexpectedly down at tool change
The specified HYDRA tool latch was released unexpectedly.
– 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.
HWICLIENT-1: Write error

Communication error between client process and the HWI process.
HWICLIENT-2: Read error
Communication error between client process and the HWI process.
Internal software error.
HWICLIENT-3: Protocol violation

HWICLIENT-4: Stepper aborted a command

Aborted by stepper.
– Operator action.
IMAGE_ORDER Group
These messages are generated by the image order process.
IMAGE_ORDER-0: Error in process communication

There was an error in the communication to the image process.
– Internal software problem.
IMAGE_ORDER-1: Timeout in process communication
There was an error in the communication to the image process.
IMGPROC Group
These messages are generated by the img process.
IMGPROC-0: Fatal process error. Restart system

A fatal system error has occurred. The image process has terminated.
– Software error.
– Hardware error.
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
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
Board field in the Users window to be able to import one.
Tray exchanger import

IMP-350: TEX/ATM [***] already exists
IMP-351: Failed to import TEX/ATM [***]
IMP-352: Importing TEX/ATM [***]
IMP-353: TEX/ATM list is protected
Magazine 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
Component field in the Users window to be able to import one.

Tray type import

IMP-450: Tray type [***] already exists
IMP-451: Failed to import tray type [***]
IMP-452: Importing tray type [***]
IMP-453: Tray type list is protected
Tray type field in the Users window to be able to import one.
Glue dot import

IMP-500: Glue dot [***] already exists
IMP-501: Failed to import glue dot [***]
IMP-502: Importing glue dot [***]
IMP-503: Glue dot list is protected
Glue dot field in the Users window to be able to import one.
Management data import

IMP-550: Management data for layout [***] already exists
IMP-551: Management data for layout [***] imported
IMP-552: Failed to import management data for layout [***]
IMP-553: Management data is protected
Management field in the Users window to be able to import this.
Mount list import

IMP-600: Invalid U line: [***]
The specified line in the imported file has an invalid U line.
IMP-601: Invalid Q1 line: [***]
IMP-602: Invalid M1 line: [***]
IMP-603: Invalid M2 line: [***]
IMP-604: Invalid B line: [***]
IMP-605: Too many B lines: [***]
IMP-606: Invalid O line: [***]
IMP-607: Too many O lines: [***]
IMP-608: Too many CX lines: [***]
IMP-609: Invalid coordinate: [***]
IMP-610: CX line too long: [***]
IMP-611: Missing name or PCB coordinates
IMP-612: PCB without position in panel
IMP-613: B line number 11 does not have a ";"
IMP-614: Failed to import mount list
IMP-615: Mount lists are protected
Layout and Board fields in the Users window to be able to import a mount
list.

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
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
Magazine field in the Users window to be able to import one.
IMP-807: Failed to import pallet [***]
IMP-808: Pallet list is protected
Magazine field to be able to import a pallet list.
IMP-809: Failed to import tray [***]
IMP-810: Tray lists are protected
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.

Magazine kit import

IMP-900: Kit list [***] already exists
IMP-901: Kit list [***] imported
IMP-902: Failed to import kit list "[***]"
IMP-903: Magazine kit list is protected
Magazine kit field in the Users window to be able to import one.
IMP-904: Invalid magazine type code [***] in kit list [***]
An invalid magazine type code was specified in the imported data. Use
the Magazine Kit Contents window or the Magazine Kits window to
correct the data.
User import
IMP-950: User [***] already exists
IMP-951: Failed to import user [***]
IMP-952: Importing user [***]
IMP-953: User list is protected
User field in the Users window to be able to import one.
Removable feeder import

IMP-6: Removable feeder "[***]" already exists.
The imported removable feeder name is already in use.
IMP-1000: Failed to import removable feeder "[***]"
IMP-1001: Imported removable feeder [***]
IMP-1002: Removable feeder list is protected
Magazine field in the Users window to be able to import a removable
feeder.
Tray position import

IMP-1050: Tray position [***] already exists
IMP-1051: Failed to import tray position [***]
IMP-1052: Importing tray position [***]
IMP-1053: Tray position lists are protected
Magazine field in the Users window to be able to import a tray position.
IMP-1054: Tray position barcode [***] already exists
The imported tray position barcode is already used.
Fiducial mark import

IMP-1100: Failed to import fiducial mark [***]
IMP-1101: Fiducial mark list is protected
Fiducial marks field in the Users window to be able to import one.

IMPORTD Group
These messages are generated by the automatic import feature.
IMPORTD-1: Cannot access watch directory [***]

The directory which the automatic import feature shall watch cannot be
accessed.
– Parameter 207.0002 Directory to monitor is not correctly set.
– The watch directory does not exist.
– TPSys does not have proper access to the watch directory.
IMPORTD-2: Watch directory [***] is not a directory
The specified watch directory is not a proper directory.
IMPORTD-3: Cannot access file [***], skipping it
The specified file found in the watch directory cannot be accessed.
– TPSys does not have proper access to the file.
IMPORTD-4: Processing file [***]
The specified file is found in the watch directory and is being processed.
IMPORTD-5: File [***] processed and removed
The specified file is found, successfully imported and removed.
IMPORTD-6: File [***] processed and kept
The specified file is found but import failed. The file is not removed from
the watch directory.
IMPORTD-7: Failed to remove file [***]
The specified file is found, successfully imported, but it could not be
removed.
IMPORTD-8: Cannot open directory [***]
The specified watch directory could not be opened for reading.
– TPSys does not have proper access rights to the watch directory.
LSCD Group
These messages come from the Linescan camera process.
LSCD-0: Failed to initialize Linescan camera hardware

The hardware controlling the LSC could not be initialized.
– Failed to read database containing calibration data for Linescan
camera. Re-calibrate camera.
– Failed to read parameters for camera. Check parameter files 57 and
58.
– Failed to download data to LSC hardware. TPSys or LSAD/VVG2
board not properly installed.
– Hardware error in VVG2 or LSAD.

LSCD-1: Failed to map frame grabber memory. Terminating

Could not allocate memory for frame grabber.
– TPSys not properly installed.
– Hardware error in VVG2 or LSAD.
LSCD-2: Failed to open /dev/frame. Terminating
Could not access frame grabber hardware.
– TPSys not properly installed.
– VVG2 not properly inserted.
– Hardware error VVG2 or CP5 boards.
LSCD-3: Failed to read framegrabber configuration data. Terminating
Could not read configuration data from the frame grabber software driver
– TPSys not properly installed. Probably a version mismatch between
the frame grabber software driver and TPSys system software.
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.

MAGREF-4: Frame grabbing failed

camera.
grabber card.
MHPR Group
These messages are generated by the magazine handler process.
MHPR-10: Magazine [***] inserted in slot [***]

The specified magazine has been inserted in the specified magazine slot.
MHPR-11: Magazine [***] removed from slot [***]
The specified magazine has been removed from the specified magazine
slot. Information message.
MHPR-12: Unknown Magazine type (type: [***])
A magazine with an invalid decimal 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.
MHPR-13: New magazine, serial number: [***] type: [***]
A new magazine, not currently in the magazine database, has been
inserted. Information message.
MHPR-14: Failed to pick [***] components in sequence from [***]/[***].
Feeder shutdown!
The specified magazine/feeder has had several pick failures in sequence.
The feeder will not be used again until the operator intervenes.
– The component reel is empty.
– The located feeder position is bad.
– The magazine fiducial mark has not been located.
– The feeder is loaded with the wrong components.
MHPR-15: Component [***] not available
A component that is needed is not available in the machine.
– Component not loaded in the machine.
– Feeder with component has been shut down by the system due to high
failure rate or manually by the operator.

MHPR-16: Wrong component value [***]/[***]

The specified magazine/feeder had several successive electrical
verification errors. The feeder will not be used again until the operator
intervenes.
– The feeder is loaded with the wrong component.
– Component batch is bad.
– The electrical verifier doesn't work properly.
MHPR-17: Fatal process error ID: [***]: [***]. Restart system:
The magazine handling system crashed. The system has to be restarted.
Mycronic support.
MHPR-20: Magazine [***]/[***] ready to remove
The specified magazine in the specified slot is safe to remove. The system
will not pick components from this magazine. Information message.
– The magazine button was pressed when the magazine was loaded.
MHPR-21: Magazine [***]/[***] ready
The specified magazine in the specified magazine slot is now available for
the machine to pick components from.
– The magazine button was pressed when the magazine was unloaded.
MHPR-22: Magazine [***]/[***] faulty. Remove magazine
The specified magazine in the specified magazine slot failed to step. The
magazine will not be used again until it is removed and inserted again.
– The magazine is broken.
MHPR-23: Fiducial mark on magazine [***]/[***] is not located
The specified magazine’s fiducial mark has not been located in this
magazine slot. The fiducial mark should be located before trying to pick
components from the magazine.
– The magazine was removed and inserted in another magazine
position.
MHPR-24: Too many feeders/trays in machine
The internal data structures cannot hold all feeder/tray information.
During normal operation this can only happen if the tray data defines an
unrealistic amount of trays on a tray exchanger, YWM or TWM tray
magazine.
– Tray data corrupt or contains unrealistic data.
– Magazine data corrupt.

MHPR-25: Failed to pick [***] of last [***] components from [***]/[***].

Feeder shutdown!
The reject rate for the specified magazine slot/feeder is above the
maximum allowed reject rate set for the magazine type in the parameter
file. The feeder will be shut down and not used by the machine until the
operator has reset the magazine error.
Depending on the magazine type, the maximum allowed reject rate before
feeder shutdown is set by the following parameters:
– 84.0104 Tape Magazines; Reject percent,
– 84.0204 Stick Magazines; Reject percent or
– 84.0252 Trays; Reject percent.
MHPR-26: Warning! [***] picks of last [***] failed from [***]/[***].
The reject rate for the specified magazine slot/feeder is above the warning
level set for the magazine type in the parameter file.
Depending on the magazine type, the maximum allowed reject rate before
feeder shutdown is set by the following parameters:
– 84.0105 Tape Magazines; Warning percent,
– 84.0205 Stick Magazines; Warning percent or
– 84.0253 Trays; Warning percent.
MHPR-30: [***] pallets inserted in TEX/ATM [***]/[***]
Reports the number of pallets detected in the specified TEX or ATM unit
in the specified magazine slot. Information message.
MHPR-31: TEX/ATM [***]/[***] deactivated
Information message. The system will not pick components from the
specified TEX or ATM unit in the specified magazine slot. The ATM has
no removable cover.
– The button on the TEX or ATM was pressed.
– The TEX or ATM door was opened or the safety covers were removed
while the TEX or ATM was activated.
MHPR-32: Pallet position of TEX/ATM [***]/[***] is not located
The pallet corners have not been located for this TEX or ATM in this
magazine slot. The corners have to be located before the machine can pick
from the TEX or ATM pallets. For the ATM: The fiducials on the pallet
have not been located for this ATM in this magazine slot.
– A new TEX or ATM unit was inserted in the machine.
– A TEX or ATM unit was removed and re-inserted in a different
magazine position.

MHPR-33: Invalid barcode in TEX/ATM [***]/[***]/[***]

The TEX or ATM barcode scanner in the TEX or ATM/magazine
slot/pallet position has detected a pallet with an invalid pallet barcode.
The pallet will not be used by the machine. Note that only the TEX has a
barcode scanner. The ATM has no barcode scanner.
– The barcode is damaged.
– The barcode scanner is not correctly installed.
– The barcode scanner is broken.
– On the ATM, the barcode is read from an electronic unit on the pallet.
Either that nit or the reader in the ATM is broken or damaged.
MHPR-35: Serial number of removable feeder in slot [***] feeder [***] is
bad.
The specified removable feeder has a bad serial number, or an error
occurred while reading it.
MHPR-36: Feeder [***] in slot [***] for demonstration use only
The specified removable feeder is only usable for demonstrations, not for
production.
MHPR-37: Large fiducial mark offset for magazine [***]/[***]
The fiducial mark for the magazine in the specified magazine slot was not
found in the expected position.
– The fiducial on another magazine was found.
– The magazine is damaged.
– The magazine slot is not adjusted correctly.
MHPR-38: Magazine with serial number [***] in slot [***] has new type
code [***]
New type code has been reported for an existing magazine. Magazine not
inserted.
– Either the magazine or the slot is faulty, or the servo is faulty. Try to
clean the magazine and the slot.
MHPR-39: Feeder [***] in slot [***] shut down with 0 remaining
components
The quantity of the feeder has reached zero and parameter 84.0400 Shut
down feeder when quantity = 0 is set to Yes. TPSys will stop picking from
the feeder.
– Refill the feeder and update the quantity of the feeder in TPSys.
– If you want TPSys to continue picking although the quantity has
reached zero, set parameter 84.0400 Shut down feeder when quantity
= 0 to No.
MHPR-40: Too many cavities in machine
The internal data structures cannot hold all cavity information..
– Cavity data is corrupt or contains unrealistic data.

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.
MIPR-2: Fatal error. Reloading motor controller M
The MOT-M servo program does not respond to commands and servo
program is automatically reloaded.
– 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 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.
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.
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.
– Wrong voltage limits specified in parameter group 141 Voltage check.

MIPR-21: System voltages are within limits

All system voltages are OK. The machine can safely run again.
MIPR-30: Loading TEX/ATM software at slot [***]
A TEX unit with no software loaded has been found. The software is
automatically loaded. Information message.
MIPR-31: Initiating TEX/ATM hardware at slot [***]
The TEX hardware initiation has started. Information message.
MIPR-32: TEX/ATM at slot [***] ready.
The TEX is ready to be used. Information message.
MIPR-33: Cannot initiate TEX/ATM hardware at slot [***]
Initiation of the TEX hardware failed. The system will not be able to use
this TEX. Follows another message explaining why the initiation failed.
– Pallets were present on the shuttle unit.
– Mechanical or electrical problem with the TEX.
MIPR-34: Cannot load TEX/ATM software at slot [***]
Loading the TEX servo program failed. The system will not be able to use
this TEX.
– The servo software was not correctly installed.
– The MOT3 board in the TEX is broken.
– For ATMs:
- Electrical problem on the CAN bus
- The CMOT board in the ATM is broken
MIPR-35: Cannot read TEX/ATM EEPROM data from slot [***]
The system could not read parameters from the TEX EEPROM memory.
The system will not be able to use the TEX.
– The EEPROM memory in the TEX is broken.
– Communication problem with the TEX unit.
– For ATMs: The CMOT may be broken.
MIPR-36: TEX/ATM parking sequence failed at slot [***]
The system could not restore the pallets to the mother unit and move the
mother unit to the parking position. Follows another message explaining
why the parking sequence failed.
– See explanation for the accompanying message.
MIPR-37: Reloading motor controller M.
The MOT-M motor controller software is being reloaded. Information
message.
MIPR-38: TEX/ATM at slot [***] is loaded
A TEX with already loaded software is detected by the system.

MIPR-39: TEX/ATM pallet scan failed at slot [***]

The system could not read any TEX pallet barcodes. Follows another
message explaining why the pallet scanning failed.
MIPR-40: TEX/ATM failed to fetch pallet at slot [***]
The TEX was not able to fetch the requested pallet from the mother unit.
Follows another message explaining why the pallet fetch operation failed.
MIPR-41: Inconsistent pallet scan data from TEX at slot [***]
The meaning of this message depends on whether it is a Warning message
(W) or an Error message (E).
W-MIPR-41: The pallet barcode has been read successfully but the pallet
has not been detected by the inductive sensors. The pallet will be accepted
and can be used by the system.
– The pallet is not pushed in contact with the magnetic hinged lever.
– The barcode scanner may be so misaligned that is scans the pallet
position above or below the correct position. Re-align the barcode
scanner.
– The inductive sensors need adjusting.
E-MIPR-41: The pallet barcode was not read, but the inductive sensors
detected the pallet. The pallet will not be accepted by the system.
– The pallet barcode is damaged.
– The barcode scanner needs adjusting.
– The barcode scanner is broken.
MIPR-42: Pallet left on Y unit at slot [***]. Remove it
A pallet was found on the TEX shuttle unit when a pallet scan operation
was performed, and no suitable free position in the mother unit was found.
– The operator opened the TEX door or removed the safety covers
while the TEX unit was activated.
– TPSys previously crashed when pallets were present on the shuttle
unit.
– For ATM: The ATM unit must be disconnected and removed from the
slot before the pallet can be removed.
MIPR-44: Cannot read valid serial number from magazine in slot [***]
The TEX unit doesn't have a valid serial number. The TEX will not be
used by the system.
– The TEX EEPROM memory is broken.
– Communication problem with the TEX.
MIPR-45: Cannot mix pallets with different sizes
The system detected both normal and extra wide pallets in the same TEX
unit. The system will not use the TEX.
– Some pallets have incorrect barcodes.

MIPR-46: TEX/ATM door open at slot [***]

The TEX door was opened while the TEX was activated.
– The operator forgot to deactivate the TEX before opening the door.
– Electrical or mechanical problem with the safety switches.
MIPR-47: TEX/ATM front hood open at slot [***]
The TEX front hood was removed while the TEX was activated.
– The operator forgot to deactivate the TEX before removing the hood.
MIPR-48: TEX/ATM rear hood open at slot [***]
The TEX rear hood was removed while the TEX was activated.
– The operator forgot to deactivate the TEX before opening the hood.
Not valid for the ATM as this unit is not equipped with a rear hood.
MIPR-49: Magazine not supported by hardware. Type: [***] Slot: [***]
Number: [***]
The magazine is not supported by the hardware in the machine.
– You need to upgrade the hardware in the machine to use this
magazine.
MIPR-50: Empty ASM magazine inserted in slot [***]
An ASM magazine without a stick pallet has been inserted in the machine.
– The stick pallet is not properly inserted in the magazine.
– The stick pallet or the magazine is broken.
MMI Group
These messages are generated by the man machine interface process.
MMI-1: Disk space low on [***]: [***] Kbytes left.

The system is running out of disk space.
– Hard drive almost full, exit system and remove files not used.
MMI-2: Out of disk space on [***], Exit and clean up
The system is out of disk space.
– Hard drive full, exit system and remove files not used.
MMI-4: Too large deviation. X: [***] µm Y: [***] µm angle: [***] m°.
Measurement ignored.
During HYDRA installation, the installation component was not placed
with high enough accuracy.
– Mechanical problem. Try to clean the HYDRA tool tips.
– Parameters 66.0051 Filtering; Maximum allowed X/Y error and/or
66.0052 Filtering; Maximum allowed angle error have too low
values.

MMI-5: Raid disk [***] OK

The Primary master or the Secondary master disk is OK. Displayed after
replacing a disk in a RAID array, and the disk has been fully updated.
MMI-6: Raid disk [***] failed
The Primary master or the Secondary master disk has failed and needs to
be replaced as soon as possible. The system will continue to operate using
the second disk in the RAID array.
MMI-7: Raid disk [***] missing
The Primary master or the Secondary master disk is missing from the
RAID array. The system will continue to operate using the second disk in
the RAID array.
MMI-8: Raid disk [***] rebuilding. [***]% done
The Primary master or the Secondary master disk is rebuilding.
Displayed after replacing a disk in a RAID array.
MMI-9: Battery support disabled. Fix problem and reboot.
UPS cable is detected to be connected but battery support is not enabled.
– Enable battery support or disconnect cable.
MMI-10: Line Mode option disabled. Set Line Mode assembly switch to No
(1002.0043).
Displayed when switch 1002.0043, Activate Line Mode is on but option
0191.0031, Line Mode is off.
MMI-11: Machine is not in a line. Review Line Mode settings
Displayed when switch 1002.0043, Activate Line Mode is set but machine
does not exists in any line defined in the line database.
MMI-12: Line Mode settings consistent
Displayed when there was an error and the error state have been corrected.
MMI-13: Machine [***] in line [***]
Displayed at startup to verify that the machine is in a line.
MMI-14: Invalid Line Mode switch combination. Set Invert meaning of
component mount/glue flags assembly switch to No (1002.0005).
1002.0005.
Displayed when Line Mode is on and switch 1002.0005, Invert meaning
of component mount/glue flags is set to Yes. Line Mode does not work
correctly when this flag is set. When this message is displayed Line Mode
functionality is turned off.
MMI-15: Component [***] used as alternative to [***]
Displayed if the machine starts to mount an alternative component that is
available in the machine instead of the default component that is not
available in the machine.

MNTSYNC Group
The messages in this group relates to the synchronization between the two
X wagons in a MY100DX machine.
MNTSYNC-1: Axis not initialized

One mounter process tries to move an X wagon or the Y wagon, at the
same time as the other mounter process tries to initialize the same
hardware.
MNTSYNC-2: No resource to wait for
A mounter process is waiting for a response, but there is no corresponding
request for a response.
MNTSYNC-3: X-wagon deadlock detected
A deadlock between X-wagons on a DX machine happened due to an
error in TPSys or servo software.
Mycronic support.
MONT Group
These messages are generated by the Mounter routines.
MONT-0: Error reading parameter file
Cannot read one of the parameters.
– 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.

MONT-6: Wrong type of tool for gluing

The tool specified for glue dispense is not a glue tool.
MONT-7: No tool present when one is expected
No tool available when board level should be measured.
No tool installed.
MONT-8: Board measurement position (X,Y) not set
The position where board level should be measured is not set.
MONT-9: Measured board level out of bounds
The board level measured is outside specified limits.
– No board present on Y wagon.
– Board position not measured correctly (tool misses board).
– Board level test position on PCB wrong (tool misses board).
– Board level nominal value and/or tolerances set wrong (parameters).
– Z/hZ friction too high or specified force too low.
MONT-10: Timeout while waiting for component pick-data.
Internal wait time for data from magazine lookup expired.
– Software problem. Make a 'savestat' diskette and contact Mycronic
support.
MONT-11: Component feed cancelled
Assembly interrupted. Information message.
MONT-12: Timeout while waiting for component feed
Internal wait time for data from magazine step expired.
support.
MONT-13: Level too high when picking
Pick level too high with Z head.
Obstacle on feeder.
– Tolerance too tight (parameter).
MONT-14: Level too low when picking
Pick level too low with Z head.
Nothing loaded in feeder.

MONT-15: Bad vacuum when picking

Vacuum level too low after pick of component.
– Nothing loaded in feeder.
– Uneven surface on package causes air to leak between tool tip and
package (remove vacuum test from package).
– Faulty vacuum system.
MONT-16: Failed to pick
Failed to pick a component.
– Faulty ISIC indicator.
MONT-17: Component dimension [***] µm out of bounds ([***] - [***] µm)
The measured component size falls outside the limits. The message also
indicates the maximum and minimum allowed dimensions from the
package data.
– Mechanical size tolerances in package data too tight.
MONT-18: Component electrical properties out of bounds
Wrong electrical properties for component.
– Wrong component loaded in feeder or programmed in the wrong
angle.
– Component specification wrong.
MONT-19: Component lost (dimension = 0)
Component lost or failed to pick component.
– Fail to pick not detected because vacuum and pick level tests turned
off.
MONT-20: Level too high when placing
Place level higher than expected.
– Component already placed.
– Board surface uneven or warped.
– Board level measurement wrong.

MONT-21: Level too low when placing, probably missing component

Place level lower than expected.
– Placement missed board (error in PCB data).
– Board not loaded.
– Board surface uneven or warped.
– Board level measurement wrong.
MONT-22: Failed to place
Failed to place component.
– Placement missed board (error in PCB data).
– Board not loaded.
MONT-24: Specified centering sequence is impossible to perform
This can only happen when using a tool that can only pick in a fixed angle.
(for example tools for cylindrical components such as MELF). This error
will never happen if the machine is equipped with a Midas unit.
MONT-26: Component lost (bad vacuum)
An error in vacuum level indicates that the component has been lost
during transport from pick to place position.
– Acceleration codes set too high for package.
– Error in vacuum system/measurement.
MONT-27: Failed measuring centering device level
Failed to find centering device during centering level installation.
– Indicator faulty.
– Centering device faulty.
MONT-28: Automatic fiducial mark search does not converge
Failed to complete a fiducial mark search using a non-calibrated X-wagon
camera (if the value of parameter 43.0003 Max number of times to try is
greater than 0).
– X-wagon camera installation not correct.
– X-wagon camera loose.
MONT-30: Optical centering does not converge
When using iterative optical centering the algorithm cannot find the
correct position.

– This centering method is used if the parameter 21.0251 Optical

Centering; Max loops (0 = one shot) is set to a value greater than 0.
This is required only for TP9/2 and older machines.
MONT-32: Resistance = [***]
Information message. The message reports the results from the electrical
verifier when used to measure a component value.
MONT-33: Capacitance = [***]
The same as for MONT-32.
MONT-34: Low voltage capacitance = [***]
MONT-35: Polarized capacitance = [***]
MONT-36: Diode voltage drop = [***]
MONT-37: Diode leakage current = [***]
MONT-38: Zener voltage = [***]
MONT-39: NPN hFE = [***] times
MONT-40: PNP hFE = [***] times
MONT-41: Calibrating verifier
Information message:
– This message indicates that the system re-calibrates the verifier
hardware.
MONT-42: No tray wagon magazine present when needed
The TWM was not installed when the software expected it to be.
MONT-43: Put component back is not allowed in this magazine
Information message. A component had its Reject position set to Put
component back but it was picked from a feeder where this operation is
not possible.
– The system will revert to manual leave.
MONT-45: Turning diode
A warning message when the system detects a diode that has wrong
polarity and should be turned 180°.
The message will only appear if electrical test is specified and turned on
and parameters 21.0241 Diode Handling; Turn if electrical test failed and
21.0242 Diode Handling; Warn when turning is on.
– Turning the diode reduces performance.

MONT-56: Z measure unstable

The system does not get stable results when it measures a Z level using
the Z axis.
– Z transducer error.
MONT-57: Glue level too low
The measured glue level is lower than parameter 101.0009 Max glue
depth (from EOF).
MONT-58: No HYDRA on this machine
The system tried to used the HYDRA but no HYDRA is present on the
machine.
MONT-60: HZ measure unstable
The system does not get stable results when it measures a Z level using
the HYDRA Z axis.
– HZ transducer error.
MONT-61: HZ force sensor faulty, tool [***]
The specified HYDRA tool's force sensor did not register impact during
HYDRA tool Z offset measurement.
– HZ transducer error.
MONT-62: HZ nozzle ([***]) friction too high. Might lose components
The system detected a high friction for the specified HYDRA tool.
– Check HYDRA head for damage (use HYDRA service program).
MONT-63: Failed to place with nozzle [***]
The system did not detect board impact when placing with the HYDRA.
– Check PCB programming.
– Check HYDRA indicators.
MONT-64: Component may be stuck in the centering device
The system has detected that the centering device cannot move freely.
This may be because a component is stuck somewhere in the centering
device. Assembly is interrupted to avoid damage.
– Ensure that the centering device can move freely.
MONT-65: Bad vacuum
Vacuum level low, component pick probably failed.
– Uneven surface on package cause air to leak between tool tip and
package (remove vacuum test from package).
– Faulty vacuum system.

MONT-66: Extended verifier calibration (may take a few minutes).

The verifier calibration failed the first time and the system tries to re-
calibrate.
– If the calibration does not finish within a minute, press STOP.
– Faulty or instable verifier board, contact Mycronic service.
MONT-67: FirstPickEof (Z axis) not 200 µm greater than PosZTurnBig (Z
mount)
The system detected an inconsistency in the parameters. This may cause
damage to the system.
– Parameter 6.1002 Z Settings; EOF in first pick (without tool) must be
set to at least 200 micrometers higher than parameter 21.0201 Right X
wagon; Z position under C Unit.
– Check both parameter values and set to correct values according to
procedures described in the service manual.
MONT-68: Tool is bad
The system tried to use a tool that is not installed or not present.
Mycronic support.
MONT-69: Distance between pick level and C-unit is too small to be able to
rotate the component.
The system has detected that the space between the pick level and the
centering device is too small to be able to turn the component.
– The pick position is too high.
– The component is too thick.
MONT-70: HZ reached upper end point.
Failed to measure the hzz-offsets since the axis reached the upper end
point before mechanical stop. The hzz-offsets have to be measured at a
position where the HZ axis can reach the surface to measure on.
MONT-71: Failed to pick calibration plate.
The system failed to pick the calibration plate during optical centering
unit calibration.
MONT-72: Calibration plate dropped.
The system dropped the calibration plate during optical centering unit
calibration.
MONT-73: Throw position [***] not reachable with X. Check the parameter.
The specified throw position is outside the area that the X axis can reach.
– Check parameters 32.0021 Reject Position 1; Type through 32.0093
Reject Position 8; Y position.
MONT-74: No throw position is reachable with X. Check the parameters.
There is no throw position specified inside the area that X axis can reach.
– Check parameters 32.0012 Manual Reject Position; X position and
32.0021 Reject Position 1; Type through 32.0093 Reject Position 8; Y
position.

MONT-75: Manual throw position is not reachable with X. Check the

parameter.
The manual throw position is specified outside the area that X axis can
reach.
– Check parameter 32.0012 Manual Reject Position; X position.
MONT-76: Leave manually instead of put component back due to regrip.
Put-back is specified but cannot be used since the system has moved the
component position on the tool.
– This should never happen for a component that is centered using
vision centering and will be very rare for mechanically centered
components.
MONT-77: Did not get wanted tools in HYDRA tool change
The HYDRA unit has attempted to change mounting tools, and one or
more of the attempted changes has failed.
– Check for obstructions in the HYDRA tool bank.
– Verify that the tools are correctly installed.
MONT-79: No allowed tool present for measuring the board level.
The tools specified in the Level measurement tools field are not present or
not installed.
– Error in PCB/Panel data.
MONT-80: Failed to pick, timeout
Failed to pick a component, the servo returned timeout.
MONT-81: Failed to pick, no indicator hit
Failed to pick a component, the indicator tool did not indicate a hit.
MONT-82: Failed to pick, no hit
Failed to pick a component, the tool did not hit.
MONT-83: Failed to place, force is out of range for tool
The value of parameter 6.1003 Z Settings; Friction is higher than the Z
mount force field for the package.
– Check parameter 6.1003 Z Settings; Friction. The value should
correspond with the actual single mount head friction measured by the
Service program or the test tools program. If this friction is higher
than 3.5 N, there may be a hardware problem with the single mount
head. If the friction is higher than 3.5 N, you may be able to
temporarily avoid the problem by increasing the value of the package
Z mount force field, or to change its value to Low.

MONT-84: Align pick, center and place angles

The component cannot be picked or placed without hitting an object in the
machine.
– The pick angle and the place angle must be aligned with each other.
Try putting the longest side of the component in the X direction of the
machine. Also try to turn the PCB so that the component when placed
also is aligned with the X direction.
MONT-85: Failed to pick, no component within reach
The measured pick level is within 0.2 millimeters of the lowest Z position
of the HYDRA head. It cannot reach low enough to pick the component.
– The HYDRA tool may be broken.
– The feeder may have its pick position too low, check the magazine or
feeder.
– The HYDRA Z movement may need servicing.
MONT-86: Pre-pick inspection requested but option is not enabled
No attempt is done to pick a component on a tray because the tray type
data says the component should be inspected by the PVC, but the option
191.0030 Options; Pre-pick inspection is not enabled in parameter
191.0001 Magic word.
– Request a new value for parameter 191.0001 Magic word from
Mycronic.
– If no pre-pick inspection is necessary, select No in the Inspect before
pick field in the tray type data corresponding to the tray.
MONT-87: Place force [***] mN too high. Using max force ([***] mN)
The mount force, specified by the Z mount force field for the package, is
too high for the specific single mount head. The mount head will use its
maximum allowed force instead.
– Change the Z mount force field to the maximum allowed force for the
specific single mount head.
– Move the job to another machine with a single mount head that can
use the specified force.
MONT-88: Tool too short for board level measurement
The tool that is used for board measurement is too short.
– Specify another tool.
MONT-89: Failed to write parameters
Measurement of the HYDRA tool tube lengths failed, because the
measured values are out of bounds.
– Ensure the measurements are made on a flat and hard surface that is
large enough for the Midas/ZFi tool holder and that does not flex
downwards.
– Check that the HYDRA tool tubes are not broken.

MONT-90: Component too high for HYDRA mounting in this machine

A component cannot be mounted with HYDRA because it defined too
high or because already mounted components are too high.
– Check that the programmed height of the package is within
specifications of the HYDRA.
– If high components were already mounted on the PCB change mount
order using grouping.
– Choose only Z tools as usable mount tools in the package editor.
MONT-91: Failed to place component using the specified force
Mechanical stop was reached without tool indicator hit. MIDAS friction
has probably increased over time.
– Check Z friction in Service and apply maintenance.
– If friction is high and cannot be reduced by maintenance measures,
you can increase temporally the allowed friction to overcome
modifying parameters 6.1003 and 6.1006.
MONT-92: Failed to calculate theta calibration table
Z2 theta calibration could not be calculated.
– Take a ’savestat’ and contact Mycronic service.
MONT-93: Theta calibration table not saved
MONT-94: Bad vacuum. Component lost on the way to Dip Magazine?
The vacuum test (optional see parameter/switch 1001:0006) failed.
Component may be lost. Assembly operation is stopped to avoid dipping
the tool into the paste.
– Control if the component got lost and remove it from the board or dip
unit.
MONT-95: Bad vacuum. Component lost in Dip Magazine?
The vacuum test (optional see parameter/switch 1001:0006 failed.
Component may be lost in the cavity. Assembly operation is stopped to
avoid raking over the component, which could damage the transfer plate,
rake, and/or component.
– Remove the component from the cavity and start the assembly again.
MONT-96: Dip Magazine is missing.
When TPSys tried to access the dip magazine it was suddenly missing.
The operator probably removed the magazine without first pressing the
magazine button or before the magazine LED stopped blinking.
– Insert the Dip magazine and start the assembly again.
MONT-97: Waiting for Z motor to cool down.
The Z motor got too warm because the machine was running too long
using a high mount force. The mounting is paused.
– Wait until the Z motor has cooled down. The mounting will then
continue.

MOT Group
For each command sent to a motor control computer, a status is returned.
To understand the meaning of a status message, the command that generated

the status is required. The messages in the MOT group are combinations of the
commands and the status returned.
To handle this, TPSys display the MOT group messages in a slightly different
format.
For historical reasons this group is labeled MOT but it applies to messages
generated from MOT1, MOT2, MOT3 and CMOT boards.
MOT message number format

The message number format for MOT group messages is:
MOT-<Command> <Axis/Board> /<Status code>

<Command> A code for the command that generated the status.
<Axis> The logical axis or physical MOT/CMOT board which the
command was sent to. Note that some MOT/CMOT boards may control
more than one logical axis.
<Status code> The status returned.
To analyze a message you have to check both the command and the message.
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 status codes

This is a list of the status codes used in the MOT messages. A certain
command can only return a selected set of status codes.
The status code 0 means “OK”. This status is never displayed in the message
log.
MOT-Command/1: Mechanical stop

Indicates that movement stopped before time-out.
– Friction high.
– Force or speed too low (may be controlled by parameter).
– Mechanical problem.
MOT-Command/2: Time out
Indicates that movement stopped by time-out.

MOT-Command/3: At target
MOT-Command/4: Mechanical stop after ind.
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.
– Check XMIF connectors.
– Check settings of select rotary switch SW1 on MIBB board.
MOT-Command/18: Cannot access magazine hardware
MOT-Command/19: Cannot read from magazine
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.


MOT-Command/23: Cannot find calibration value at all
Cannot read force sensor on 3PT1 board.
– Hardware problem (check 3PT1 board).
MOT-Command/24: Calibration signal too shaky
Sensor signal not good during calibration.
– Electrical noise causes signal problem.
MOT-Command/25: Z indicator shaky
Force sensor signal not good.
– Electrical noise causes signal problem.
MOT-Command/26: Z indicator uncalibrated
A message was sent that involved the Z indicator but the Z indicator is not
calibrated.
MOT-Command/28: Cannot find Z indicator value at all
Hardware problem.

MOT-Command/31: Missed flash position

X axis receives HYDFLASH command too late to be able to serve it.
– Wrong parameters.
– Software error.
MOT-Command/32: Error in HYDB communication.
Failed to communicate with the HYDB-board.
– Error in serial communication hardware on Board Z.
– Error in HYDB board.
– HYDB board not properly connected.
MOT-Command/33: No magazine in slot
Tried to step magazine that was not inserted.
– Operator removed magazine without using the magazine button.
– Software error.
MOT-Command/34: Magazine type not supported
Unknown or old magazine type.
– Check correct setting of select rotary switch SW1 on MIBB board.
MOT-Command/35: Transducers out of synchronization
Indicates a transducer synchronization problem for the X transducers.
– Faulty transducers.
– Transducers connection problem.
– Bad or loose bellow couplings on motors.
– Electrical noise causes transmission problems.
Hint: Redo the xCalibrate procedure.
MOT-Command/36: Transducer drift too big
Indicates that changing between HYDRA and Midas failed, encoder has
changed value.
For HYDRA theta: indicates that the HYDRA theta belt slips on the drive
wheel.
– HYDRA Theta belt spring too weak.
– HYDRA Theta belt dirty.

MOT-Command/37: Unreasonable latch position measured

Measured HYDRA Z axis latch position value during initialization out of
bounds.
– Mechanical problems (HYDRA Z axis).
MOT-Command/38: Latch position measurement not repeatable
Measured HYDRA Z axis latch position value during initialization not
stable.
– Mechanical problems (HYDRA Z axis).
MOT-Command/40: Illegal servo program
Servo program not compatible with hardware.
– Configuration error.
MOT-Command/41: Illegal MOT board version
Servo program not compatible with MOT board.
MOT-Command/42: Motor off but still moving
Motor is moving when it should stand still.
– Check current amplifier offset.
– MOT board faulty.
MOT-Command/48: Magazine checksum error
Check sum error from Magazine. Magazine is not answering with correct
check sum.
– Hardware/electrical problem related to Magazine bus and/or MCU
board.
MOT-Command/50: Z axis not in uppermost position
Z axis not in safe position while HYDRA Z is activated.
– XWB board faulty.
– Bad supply voltage.

MOT-Command/51: HZ axis not in uppermost position

HYDRA Z axis not in safe position while Z is activated.
– XWB board faulty.
– Bad supply voltage.
MOT-Command/60: TZ path safety sensor activated.
TZ path safety sensor indicates that TEX Z axis cannot be moved.
– Pallet stuck in TEX.
– Sensor faulty.
MOT-Command/61: TEX EEPROM does not respond correctly
MOT-Command/62: TEX EEPROM write protected
MOT-Command/63: Servo command parameter length mismatch
MOT-Command/64: Cannot move TZ because TY1 or TY2 is not in free area
MOT-Command/65: Internal TEX servo error, command not initiated
MOT-Command/66: Cannot follow/match the calculated moving curve
MOT-Command/67: Critical servo error
MOT-Command/68: Axis already occupied with another move
MOT-Command/69: Motor relay does not follow orders. Relay stuck.
MOT-Command/70: Error when calculating way planning of move
MOT-Command/71: Bad data in EEPROM
MOT-Command/72: Data passed limit
Internal servo software error.
MOT-Command/73: Weight too high on TEX Z table
Load on TEX Z axis too high or movement blocked.
– Reduce the weight of the TEX cassettes.
– Check TEX Z axis for anything that blocks the movement.
MOT-Command/128: Board jammed in conveyor
Board jam sensors detected a board during Y movement.
– Board stuck in conveyor.
– Wrong Y-axis servo program (configuration error).
– Check unload time in parameters.
MOT-Command/129: No such command in this motor controller
Illegal command sent to MOT board.
– Software error.
MOT-Command/137: Cannot calibrate force sensor
Force sensor level not within limits.
– Force sensor dirty (inside Z tool holder).
– Bad force sensor connection.

MOT-Command/139: Magazine blocked or lost connection

Cannot step magazine. Magazine does not respond correctly.
MOT-Command/140: Tried to use a non-existing magazine driver
Wrong number of parameters for magazine setup.
MOT-Command/141: Checksum error in load transfer
Failed to load software to MOT board.
– Communication hardware problem (electrical noise).
MOT-Command/143: Position out of bounds, lower end
Specified position not within range.
– Software error.
MOT-Command/144: Position out of bounds, upper end
Specified position not within range.
– Software error.
MOT-Command/149: Bad MCALIB command
Wrong parameters for electrical verifier.
MOT-Command/153: Tried to address a non-existing feeder
Tried to step a magazine feeder that does not exist.
MOT-Command/156: Motor timeout
General servo command timeout. Command failed.
MOT-Command/157: Magazine slot number out of bounds
Tried to step magazine in a position that does not exist.
MOT-Command/159: Result buffer overflow
MCALIB internal error.
MOT-Command/160: Fatal error, NMI in NMI
Controller error.
– Hardware error.

MOT-Command/161: CODSP not present

The CODSP board on MOT3 is missing.
– Missing or broken CODSP board.
MOT-Command/162: DSP DL_CALC timeout
Internal DSP error.
MOT-Command/163: Illegal value of DSP command argument
Servo command caused illegal value in DSP code.
– Internal servo program error.
– Illegal servo command parameter (TPSys error).
MOT-Command/164: DSP command error
Servo command caused a DSP command error.
– Internal servo program error.
MOT-Command/165: DSP reserved error
Not yet used.
MOT-Command/166: DSP controller error
The DSP servo cannot control the motor(s) properly.
– Problem with power supply, motor current too low.
– Mechanical problem, friction too high or tool stuck in Z.
MOT-Command/167: DSPLink protocol violation
Internal DSP servo error.
MOT-Command/168: DSP software failure
Internal DSP software failure.
MOT-Command/169: DSP hardware error
Hardware problem with DSP board or MOT3 board.
– Hardware error.
MOT-Command/173: Motor warm too long
Simulated motor temperature over safe limit too long.
– Transducer drift causes high currents.
MOT-Command/186: Transducers do not agree
X-axis transducers difference too high.
– Faulty transducer.
– Transducers connection problem.
– Electrical noise causes transmission problems.
– Configuration error (wrong X servo program).

MOT-Command/187: Motor hot

Simulated motor temperature over critical limit.
– Transducer drift causes high currents.
MOT-Command/188: No glue station present
Tried to start glue station when no glue station present.
MOT-Command/189: Magazine tape collector blocked
Failed to complete magazine step operation, on a magazine with tape
collector.
– MOT board M problem.
– MI-board problem.
MOT-Command/190: Axis not initiated
Information message. This is not always an error.
MOT-Command/195: Conveyor support motor cannot stop
The conveyor support movement did not stop when requested.
– Conveyor hardware problem.
– MOT board M problem.
– MI-board problem.
MOT-Command/196: LOADBRD with support down sensor NOT activated
Conveyor load interrupted because support down sensor not activated.
– Support-down sensor faulty.
MOT-Command/198: Board positioning failed
Positioning of conveyor width axis failed.
– Mechanical problem with conveyor width axis.
MOT-Command/200: Board lost during transport
Board did not activate board edge sensor within time limit.
– Board edge sensor faulty.
MOT-Command/201: Board has disappeared
First backward movement of conveyor transport did not get detected by
board edge sensor.

MOT-Command/203: Board stuck

Board left detected on board edge sensor when board should move away
from sensor.
MOT-Command/205: Motor speed out of control
Motor speed deviates from expected speed.
– Problem with power supply, motor current too low.
– Mechanical problem, friction too high or tool stuck in Z.
– Hardware configuration might be wrong, run 'hwconf' program.
– Wrong setting on SERVO rotary switch on adaptor board.
MOT-Command/214: Illegal precision code
Precision code for motor move operation not defined.
MOT-Command/217: Illegal transducer correction data
Illegal values in X servo internal calibration tables.
– X belt damaged.
– Internal software problem in the Xcalibrate routine.
MOT-Command/218: Illegal value of parameter 0
Illegal parameter for command.
MOT-Command/221: Timeout requesting MagLink channel
MOT-Command/222: Data size calculation error
MOT-Command/223: MagLink call timeout
MOT-Command/224: Data verification error while sending

MOT-Command/225: Data error while receiving

MOT-Command/226: Address of client reply does not match
MOT-Command/227: Bad format of address from client
MOT-Command/228: Bad format of error code from client
MOT-Command/229: Bad length word format
MOT-Command/230: Short timeout waiting for reply has expired
Communication error with TEX.
MOT-Command/231: Error storing command for polling
MOT-Command/232: Bad hardware type detected
MOT-Command/233: Short timeout waiting for transmit has expired
MOT-Command/234: Protocol violation
MOT-Command/241: Motor controller internal software error
MOT-Command/242: PAIB problems
MOT-Command/243: Y-wagon safety switch activated
Y covers not closed.
MOT-Command/244: Emergency stop button activated
Emergency switch activated.

MOT-Command/245: Motor drive inhibited

X belt motor drive (ELMO amplifier) unexpectedly shut off.
– ELMO supply voltage too low.
– Supply voltages from Booster to PAIB board too low.
– PAIB board failure.
– ELMO failed.
– Problem with main supply voltage.
MOT-Command/246: Light curtain triggered
Light curtain activated.
– Obstacles in X path.
– WSR/TST board problem.
MOT-Command/248: Door open.
X covers open.
MOT-Command/250: Light Curtain test failed
Sender or receiver failed during test of light curtain either in active or
passive state.
– Solder blob S1 on TST2 board not removed.
– Light curtain disconnected.
– Electrical problem.
MOT-Command/1005: Servo failed with weight measurement
The servo failed to measure the weight.
MOT-Command/1006: Axis controller unstable
The motion controller is oscillating.
– Internal servo software error.
– Hardware configuration might be wrong, run 'hwconf' program.
– Wrong setting on SERVO rotary switch on adaptor board.
MOT-Command/1007: Servo watchdog error
Watchdog alarm from the CMOT board.
– Hardware problem. Change CMOT board.
MOT-Command/1008: Command buffer full
Too many multiple commands sent to servo.

MOT-Command/1009: Axis is e-stopped by internal servo process

Due to an internal error the motion has been stopped by the servo
software.
MOT-Command/1010: Axis is busy (not idle)
Axis is occupied, unable to service command.
MOT-Command/1011: Invalid SMEMA channel
A non existing SMEMA channel has been specified.
MOT-Command/1013: Servo command registration failed
Task list in servo software is full. Registration of new task/command
failed.
MOT-Command/1014: Internal servo data corrupt, software error
– -Internal software error.
MOT-Command/1015: Command cannot be interrupted
Servo command cannot be interrupted.
MOT-Command/1016: Index is out of bounds
Array-index sent to servo is out of bounds.
MOT-Command/1017: Invalid command sent to servo
Command sent to servo is not supported by the servo software.
– Check Servo/TPSys version.
MOT-Command/1018: Invalid axis.
Command sent to servo is not valid for or working with the specified axis.
– Check hardware configuration with hwconf.
MOT-Command/1019: Invalid command argument
Wrong value of command argument sent to servo.
MOT-Command/1022: Invalid A/D channel request.
Invalid A/D channel specified.
MOT-Command/1023: Motor relay is off
Motor relay detected off when not expected.
– Electrical problem, voltage not stable.
– Relay faulty.

MOT-Command/1024: Failed to start motion controller

Servo failed to start the motion controller for the specified axis.
MOT-Command/1025: Motor is going in wrong direction
The specified motor/axis is moving in the wrong direction compared to
the intended direction.
– Check motor cabling, amplifier, encoder and encoder cabling.
MOT-Command/1026: Cannot follow reference trajectory, speed too high
Specified motor/axis is moving too fast. Overspeed error.
– Check amplifier, incoming voltages and motor wiring.
MOT-Command/1027: Cannot follow reference trajectory, speed too low
The specified motor/axis is moving too slow.
– Axis blocked.
– Motor damaged.
– Amplifier error (check fuse).
– Check motor relays.
MOT-Command/1028: Phase list full, pointers might be corrupt.
The internal phase-list in the servo software is full.
MOT-Command/1029: Controller signal is saturated
Maximum output used during movement.
– Axis blocked.
– Friction too high.
– Motor damaged.
– Amplifier error.
– Check motor relays.
MOT-Command/1030: Error in GENMOVE entry 0
Motion trajectory calculation error.
MOT-Command/1031: Wrong number of command arguments
Command sent to servo have too many or too few arguments.
– Check hardware configuration with hwconf.

MOT-Command/1032: 12 Volt MI too low. Magazine bus deactivated

12 volt on magazine bus was detected too low. Magazine bus deactivated.
– Short circuit on Magazine bus.
– Check setting of select rotary switch SW1 on MIBB board.
– Short circuit on Magazine bus.
– Short circuit on magazine bus.
MOT-Command/1035: MCU probably connected wrong (5 volt MI too low
after powerup)
Short time after power up, 5 volt detected too low. Magazine bus
deactivated.
MOT-Command/1036: Multiple controllers connected to the magazine bus (5
volt MI too high before powerup)
Detected 5 volt before power-up. Magazine bus not activated.
– Multiple controllers connected to magazine bus.
MOT-Command/1037: Short circuit in magazine bus, bus was shut down
Current measured too high on magazine bus. Magazine bus deactivated.

MOT-Command/1038: Timeout in command queue

Time limit expired in command queue.
MOT-Command/1039: Index pulse missing
Index pulse not found during initialization.
– Index pulse not adjusted.
– Movement blocked.
– Transducer faulty.
MOT-Command/1040: Axis is moving while issuing RESETCOUNTER
Axis is moving when RESETCOUNTER command received.
MOT-Command/1041: Non-existing indicator
Non existing indicator in MOVIND command.
MOT-Command/1042: Invalid GENMOVE entry
A invalid entry/parameters have been sent to the internal servo command
GENMOVE.
MOT-Command/1043: Position too small
Target position outside limits.
MOT-Command/1044: Position too large
Target position outside limits.
MOT-Command/1045: Speed demand outside limits.
The speed sent to servo is too high for the selected axis.
MOT-Command/1046: A panic phase is executing. MPL might be corrupt.
MOT-Command/1047: Multiple index pulses was found
The servo has found multiple index pulses even though only one (1) was
expected.
– Check that there is only one (1) reference mark present.
– Check that the reference mark is working correctly.
– Check for electrical disturbances on reference mark signal.

MOT-Command/1048: Maglink client error. Probably HW error

There are problems with the communication through the Maglink
protocol.
– Check hardware.
MOT-Command/1049: No maglink client
There are problems with the communication through the Maglink
protocol. No Maglink client exists.
– Check hardware.
MOT-Command/1050: Background process not responding.
The internal background process (or other processes) in the servo is not
working properly.
MOT-Command/1051: Tasklist full.
Too many tasks to handle in servo.
MOT-Command/1052: Resource already locked
Resource could not be used. Resource already locked by another task in
servo.
MOT-Command/1053: Invalid function call
Command could not be executed by servo.
MOT-Command/1054: Wrong state in the internal state machine
Internal servo software error.
MOT-Command/1055: Indexpulse has wrong position
Index pulse not within limits.
MOT-Command/1056: Feeder friction too high
Force too high during magazine stepping.
– Feeder jammed.
– Magazine movement blocked.
– An adjustable feeder may be needed to get smooth feeding.
MOT-Command/1057: Magazine revision not handled by servo
Revision of magazine not compatible with servo.
– Revision selector set wrong in magazine.
– Servo not updated.

MOT-Command/1058: Magazine stroke too long

During initialization of magazine, movement was found too long.
– Type selector set wrong in magazine.
– Mechanical stop removed.
MOT-Command/1059: Magazine stroke too short. A component may be stuck
in the magazine
The movement of the magazine feeding mechanism is shorter than
expected.
– A component may have been dropped into the magazine, remove the
feeders from the magazine and check.
– The tape may be jammed in the magazine feeding mechanism.
MOT-Command/1060: Command-data list full
The internal servo command-data list is full.
MOT-Command/1061: The move cannot be done Error in GENMOVE entry 1.
The trajectory for the move cannot be calculated due to illegal values for
any combination of speed, acceleration and position sent to the servo.
MOT-Command/1064: The move cannot be done Error in GENMOVE entry 4
and above.
MOT-Command/1065: Reserved for future use.
Not documented.
Not documented.


Not documented.
MOT-Command/1068: The move cannot be done Error in GENMOVE entry 8
or above.
A trajectory for the axis could not be calculated with the data provided in
entry 8 or above.
– Possibly faulty parameters.
MOT-Command/1077: Genmove, interrupting current move in phase 3 failed.
The servo can not calculate a new trajectory for an axis when it is
accelerating.
MOT-Command/1078: No valid controller found
The controller or axis number does not exist in the servo.
– Check the hardware configuration with hwconf.
MOT-Command/1079: PWM fuse blown
The fuse for the Pulse Width Modulated (PWM) amplifier on the motor
controller board has gone.
– First check that the axis is not obstructed or irregular when moving
manually with motor cable connector pulled out.
– Then check cables and connectors for damage.
– Check the amplifier circuits on the motor controller board for any
short circuit.
– Check the glass fuse on the motor controller board, or in the case of
an automatic fuse, reload the servo and initiate.
MOT-Command/1080: Beampos buffer overflow
MOT-Command/1081: Mean motor current too high
The motor current have been higher than allowed for a longer time period
(approximately3 seconds).
– Check for objects blocking the movement.
– A combination of very high placement force and long place wait time
may trig this error.
MOT-Command/1082: Amplifier enable and serial cables do not match
The servo for X axis using Prima amplifier failed to verify enable of
amplifier via serial communication. The amplifier is enabled via the XMB
board (connector XAMP1/XMB2), this enable is then verified via serial
communication between XMB board (connector XSER1/XSER2) and the
Prima amplifier.
– The cables may be connected wrong (mixed between left/right) or the
cables between XMB board and Prima amplifier may be faulty.
– The XMB board or Prima amplifier may be faulty.

MOT-Command/1083: Amplifier enable and encoder cables do not match

The servo for X axis using Prima amplifier failed to verify enough
movement during phasing of amplifier. Phasing of Prima amplifiers is
performed after the power-up of a machine during initiation of the
machine. During the phasing sequence of a Prima amplifier the
corresponding X wagon moves slightly back and forth. When this
error occurs, corresponding X wagon has not moved enough.
– The cables may be connected wrong (mixed between left/right) or the
cables between the XMB board and the Prima amplifier may be
faulty.
– The XMB board or the Prima amplifier may be faulty.
MOT-Command/1086: Movement not possible with specified force, force is
lower than friction.
Axis cannot move with the force specified, force is lower than friction.
MOT-Command/1087:Slot connector pin 55 detected low. Magazine bus
deactivated
Short circuit on magazine bus. The MCU board checks that pin 55 is low
at startup.
– Check that the MCU is correctly connected to the magazine bus.
– Check revision of VC boards for vibratory magazines. Early
VC boards cause pin 55 to be low. If this is the problem, removing all
magazines will make MCU to start up OK.
– Check for short circuit in magazine bus XMIF connectors (may be
jammed components).
MOT-Command/1088: Axis range outside limits. Stroke too short
– High friction.
– Axis movement blocked.
MOT-Command/1089: Timeout when axis blocked by border
X movement temporary blocked.
MOT-Command/1090: Auxiliary fan failure. Open circuit.
Current level for fan was measured low indicating an inoperative fan.
– Fan not connected.
– Cable failure.
MOT-Command/1091: Auxiliary fan failure. Short-circuit.
Current level for fan was measured too high indicating an inoperative fan.
– Short circuit in cable or motor.
MOT-Command/1092: Command using axis resource requires axis number
specified in cmdList
Internal software error in the servo software.
MOT-Command/1093: Unknown device detected
Servo doesn't recognize the 'SERVO' rotary switch setting on the
controller board.

– 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.

MOT-Command/1178: Detected high speed with no controller running

The servo detects axis moving just by enabling motor amplifier, current
output from servo set to zero.
– Power down and restart the machine, the amplifier phasing may be off
(encoder may have lost pulses during movement). After power down,
the initiation will redo phasing sequence.
– The calibration of the amplifier may be off, redo the calibration using
the service program.
– The amplifier or servo controller board may be bad.
MOT-Command/1179: No ACK from Prima was received after the AO
command
Communication error between servo controller and Prima amplifier
during amplifier calibration.
– Check the serial cable between the servo controller board and Prima
amplifier.
– The servo controller board or Prima amplifier may be faulty.
MOT-Command/1180: Too big message sent to fifoTx
The buffer for messages to and from the servo is full.
MOT-Command/1181: Fifo communication failure.
The FiFo message buffer was found corrupt by the servo.
MOT-Command/1182: Cooling fan failure. Open circuit.
Current level for fan was measured low indicating an inoperative fan.
– Fan not connected.
– Cable failure.
MOT-Command/1183: Cooling fan failure. Short-circuit.
Current level for fan was measured too high indicating an inoperative fan.
– Short circuit in cable or motor.
MOT-Command/1184: Error while sending CAN message, buffer full.
CAN message could not be sent as the message buffer was full.
MOT-Command/1185: Internal CAN receive buffer full.
CAN message could not be received as the message buffer was full.
MOT-Command/1186: Move not possible. Specified force is lower than the
friction
Axis cannot move with the force specified; force is lower than friction.
– Possibly faulty parameters or package data.

MOT-Command/1198: Timeout when trying to write to EEPROM

The servo could not write to the EEPROM memory on the controller
board.
MOT-Command/1199: Error when trying to update amplifier EEPROM
The servo could not write to the external amplifier’s EEPROM memory.
– A mismatch between servo version and/or external amplifier
firmware version.
– Possibly a faulty motor controller board or external amplifier.
MOT-Command/1200: UART Rx-buffer full
Serial communication failed when the receive buffer was found full on the
motor controller board.
MOT-Command/1201: UART error
General serial communication failure on the motor controller board.
– Check serial cable.
MOT-Command/1202: UART not ready. Not initiated
Serial communication failed because it was not set up properly.
MOT-Command/1203: A false interrupt has been detected
A false signal was found on the motor controller board.
– Internal error in the servo software.
– Hardware error on controller board.
MOT-Command/1204: Port reading error
Error (usually timeout) when reading a port.
– Internal error in the servo software.
MOT-Command/1205: Failed to reboot the amplifier after programming it
The external amplifier connected to the motor controller board could not
be restarted.
– A mismatch between servo version and/or external amplifier
firmware version.
– Possibly a faulty motor controller board or faulty external amplifier.
MOT-Command/1206: Data lost
Expected serial data not present.

MOT-Command/1207: Unknown MAGLINK device detected

The TEX Tray Exchanger on the MAGLINK communication bus was not
recognized.
– Corrupt type identity circuits in device.
– Servo version does not support device.
MOT-Command/1208: MAGLINK Tx error
Sending messages on the MAGLINK (TEX Tray Exchanger)
communication bus failed.
– Check cables and connectors.
– Possibly a servo problem. Check for more recent releases.
MOT-Command/1209: MAGLINK Rx error
Receiving messages on the MAGLINK (TEX Tray Exchanger)
communication bus failed.
– Check cables and connectors.
– Possibly a servo problem. Check for more recent releases.
MOT-Command/1210: UART Tx time out
Message was not acknowledged on the serial communication bus on the
motor controller board.
– Check serial cable connected to the motor controller board.
MOT-Command/1211: UART Rx time out
Message was not received when expected on the serial communication
bus on the motor controller board.
– Check serial cable connected to the motor controller board.
MOT-Command/1213: Primary function error. Wrong servo for this type of
adapator board
The wrong type of servo was loaded onto the motor controller board.
– The hardware configuration is corrupt. Run the hwconf program.
– The motor controller board’s or adaptor board's flashware has been
programmed incorrectly at factory.
MOT-Command/1214: Wrong servo loaded for this edition of adapter board.
The servo will not run on this edition of the motor controller’s adaptor
board.
– Check for a more recent servo release.
– The motor controller board’s or adaptor board's flashware has been
programmed incorrectly at factory.
MOT-Command/1215: Internal servo file full
A log file in the servo’s memory on the motor controller board is full.

MOT-Command/1216: Encoder signal error (A or B channel missing or

unstable)
– Check cables.
MOT-Command/1217: Wrong setting on CSEL rotary switch on adaptor
board
City select rotary switch (CSEL) has wrong setting on adaptor board.
– Change to correct setting on CSEL rotary switch. Restart machine and
run hwconf program.
MOT-Command/1218: Wrong combination of CSEL and SERVO rotary
switch on adaptor board
The combination of city select rotary switch (CSEL) setting and servo
select rotary switch (SERVO) setting on adaptor board is not valid.
– Change to correct setting on CSEL and SERVO rotary switch. Restart
machine and run hwconf program.
MOT-Command/1219: Index pulse not found for right X wagon
– Check cable and connectors.
MOT-Command/1220: Index pulse not found for left X wagon
– Check cable and connectors.
MOT-Command/1222: Timeout when trying to perform a current
measurement calibration in the VFD400
Servo failed during current measurement calibration of Prima VFD400
amplifier.
– Check cable and connectors between servo adaptor board and Prima
amplifier.
– Check amplifier for faults.
MOT-Command/1223: Emergency stop circuit error
Electrical problem with emergency circuit detected.
– Check cable and connectors in the emergency circuit.
MOT-Command/1224: Axis stroke range error for X1

MOT-Command/1225: Axis stroke range error for X2

The distance between the end stops during initiation is not within limits.
– Check the movement during initiation, check for blockage of the
movement.
– Check the motor and amplifier using the "motortest" in the service
program.
– Check the encoder using the "motortest" in the service program.
– Perform the amplifier calibration.
MOT-Command/126: Distance between X1 and X2 too small. Check SERVO
and CSEL settings on XMB board
– Check the CSEL setting on XMB board, see P-010-0816-EN.
MOT-Command/1227: Distance between X1 and X2 too large. Check SERVO
and CSEL settings on XMB board
– Check the CSEL setting on XMB board, see P-010-0816-EN.
– Check for obstacle between the X wagons.
MOT-Command/1228: Emergency stop signal
Servo received emergency stop signal.
MOT-Command/1229: Hood open
MOT-Command/1230: Front hood open
MOT-Command/1231: Rear hood open
MOT-Command/1232: Hood switches error
Hood switches are not working correctly.
– Front or back hood is not fully closed.
– Hood switches misaligned.
– Hood switches broken or cable broken.
MOT-Command/1233: External conveyor hood open
MOT-Command/1234: Motor relay error
Motor relay is not responding correctly.
– Relay cable error.
– Relay broken.
MOT-Command/1235: Clock frequency error.
Clock frequency was not as expected by servo.
MOT-Command/1236: Motor amplifier channel A error
Motor amplifier has tripped or is broken.
MOT-Command/1237: Amplifier phasing failed
Motor amplifier failed during initialization.
– Check encoder and motor operation.

MOT-Command/1238: Amplifier not phased

Amplifier is not initialized.
MOT-Command/1239: Incompatible Altera/Servo code.
The servo will not run with the provided 'Altera' configuration file.
– The hardware configuration is corrupt, run the hwconf program.
MOT-Command/1240: Unknown Y unit
Unrecognized Y-unit. Hardware configuration is wrong.
– Wrong data in EEPROM byte 0, the Y weight not correctly set in
EEPROM.
MOT-Command/1241: Wrong setting on servo version rotary switch.
The SERVO rotary switch is not set to correct value on servo electronics.
Setting on SERVO rotary switch does not correspond with valid
hardware.
– Set SERVO rotary switch to correct value according to current
hardware.
MOT-Command/1242: Linear encoder error
The linear encoder is faulty.
– Encoder is not correctly adjusted.
– Linear encoder scale is dirty or damaged.
– Encoder is broken.
MOT-Command/1243: Linear encoder cable error
Encoder cable is not connected or it is broken.
MOT-Command/1244: Motor cable faulty
Servo detected a faulty cable connected to adaptor board.
MOT-Command/1245: J3 cable error
J3 cable on YMB is broken or disconnected.
MOT-Command/1246: J2 cable error
J2 cable on YMB is broken or disconnected.
MOT-Command/1247: Axis not still as expected.
Servo software detects axis is moving when expected to be at standstill.
MOT-Command/1248: Amplifier setup error, programming during startup
failed
Amplifier firmware update has failed.
MOT-Command/1249: Amplifier disconnected after loading servo.
Configuration lost
Amplifier disconnected, servo software needs to be reloaded to get
amplifier configured again.
MOT-Command/1250: Amplifier DC-link voltage too high
Supply voltage electronics to amplifier broken.

MOT-Command/1251: Amplifier DC-link voltage too low

Supply voltage electronics to amplifier broken.
MOT-Command/1252: Amplifier current too high
Amplifier output current too high.
– Short circuit in motor or cable.
– Axis movement mechanically blocked.
MOT-Command/1253: Amplifier temperature too high
Servo software measured amplifier temperature too high.
– Amplifier cooling fan broken.
– Servo electronics broken.
MOT-Command/1254: Amplifier DC-link voltage unstable
Amplifier DC-link voltage not stable.
– Amplifier supply voltage electronics broken.
MOT-Command/1255: PWM output voltage limited
Amplifier output voltage limited by servo software. Voltage output
demand higher than 95% of amplifier DC-link voltage.
– DC-link voltage too low.
– Friction too high.
MOT-Command/1256: Minus 5 Volt outside limit
Servo software measured minus 5 Volt too high or too low.
– Servo software voltage limits set too narrow.
MOT-Command/1257: Minus 7 Volt outside limit
Servo software measured minus 7 Volt too high or too low.
MOT-Command/1258: Plus 7 Volt outside limit
Servo software measured plus 7 Volt too high or too low.


MOT-Command/1262: Amplifier command error
Amplifiers reply to servo not according to protocol.
– Cable between servo electronics and amplifier broken.
MOT-Command/1263: Tray wagon magazine not connected
No TWM (YM) detected by servo.
– Cable between servo electronics and TWM broken.
– TWM not connected.
MOT-Command/1264: Amplifier communication error. Possibly wrong
firmware
Amplifier did not accept data sent by servo software.
– Possibly wrong firmware in amplifier.
– Cable between servo electronics and amplifier broken.
MOT-Command/1265: A/D reading error
Servo software failed to read A/D (Analogue to Digital) converter. Servo
voltage measurement might be incorrect.
MOT-Command/1266: Motor relay switched off (or on) by an external event
Servo detected motor relay switched off. Possibly short a voltage drop to
motor relay.
MOT-Command/1267: Encoder cable error
Encoder cable is not connected or it is broken.
MOT-Command/1268: D/A disabled by hardware
External watchdog have disabled D/A.
MOT-Command/1269: Linear encoder signal is noisy or the read head is bad
The servo software detected not allowed pulses received from the
encoder. Normally electrical disturbance can cause this.
– Check/replace cables and connectors from the encoder to the servo
controller board.
– Replace the encoder.

MOT-Command/1271: Accelerometer signal too low during HZ-latch

measurement
The accelerometer on the Hydra latch unit gives to low signal when
activating a latch.
– Replace the latch unit.
MOT-Command/1272: Accelerometer signal too high during noise
measurement
The accelerometer on the Hydra latch unit gives to high signal when no
latch is activated.
– Replace the latch unit.
MOT-Command/1273: Motor relay switched off by servo SW
MOT-Command/1274: No power, fuse is blown or faulty power
The servo got error status from Prima amplifier during phasing sequence,
most likely loss of power.
– Replace the fuse (check XBOX or YBOX).
MOT-Command/1275: Motor relay unexpectedly off
A short glitch caused the relay to turn of without the servo software
detected a valid cause.
– Glitch on the hood safety switch.
– Glitch on the operator E-stop.
– Glitch 24volt.
MOT-Command/1277: Motor relay error on XMPB board for PRIMA 1
MOT-Command/1278: Motor relay error on XMPB board for PRIMA 2
The servo software detected motor relay stuck in state ON. Before the
relay is successfully turned OFF the servo software will not turn it on.
– Replace the XMPB.
– Work around until replacement; Release all E-stop, close the hoods
and tap on the front of the XBOX (use back of a screw driver or
similar), this will help the relay to turn off.
MOT-Command/1284: Friction too high in HTheta movement
The servo initiation measured friction too high on HTheta movement.
– Check the Hydra theta belt and clean it if needed.
– Replace the HTheta motor, it may be worned out.
MOT-Command/1285: Friction too high in HZ movement
The servo initiation measured friction too high on HZ movement.
– Check the cog play and adjust if needed.
– Replace the HZ motor, it may be worned out.
– Replace the HZ rack.
MOT-Command/1287: Linear encoder error on right X wagon.

MOT-Command/1288: Linear encoder error on left X wagon.

The linear encoder is faulty.
– Encoder is not correctly adjusted.
– Linear encoder scale is dirty or damaged.
– Encoder is broken.
MOT-Command/1289: Linear encoder cable error on right X wagon
MOT-Command/1290: Linear encoder cable error on left X wagon
The signal levels from the encoder have been detected outside limits.
– A cable/connector from the encoder is bad, replace the cable.
– Replace the encoder read head with cable.
– The encoder signals are also connected to the Prima amplifier (in
parallel), there may be a short on any of these signals inside the Prima.
Replace the Prima amplifier.
MOT-Command/1291: Linear encoder signal is noisy on right X wagon
MOT-Command/1292: Linear encoder signal is noisy on left X wagon
There is an disturbance on the encoder signal from one of the X wagon’s.
– Check the sheilding in all connectors from the X wagon motor to the
XBOX.
– Replace cable chain.
– Replace motor cable from XFCB to XBOX.
– Replace motor.
– Replace encoder cable from XFCB to XBOX.
– Replace encoder.
– Check that the Prima amplifier's earth connectors (screw terminals on
the front of the Primas) are in contact with the XBOX chassi.
MOT-Command/1293: No signal from indicator in Z/HZ movement
MOT-Command/1294: Indicator signal too high in Z/HZ movement
Force the sensor reading outside the limits.
– For Hydra, perform an indicator calibration in the service program.
– Clean the indicators.
– Replace the indicator HW.
MOT-Command/1295: Encoder signal is noisy
The servo software detected not allowed pulses received from the
encoder, normally electrical disturbance can cause this.
– Check/replace the cables and connectors from the encoder to the servo
controller board.
– Replace the encoder.

MOT-Command/1296: The indicator hit too early on Z/Hz movement

Midas or HYDRA detected indicator hit higher up than expected.
– Two components on top of each other.
– Board level not measured correctly.
– PCB not even.
– Wrong package height.
MOT-Command/1297: Moved target (by calcPath) failed border check
Internal software error, TPSys/servo.
MOT-Command/1298: Border logic corrupt, fatal error
MOT-Command/1299: Left and right border collision
MOT-Command/1300: Unknown conveyor type
Conveyor type rotary switch is incorrectly set. No conveyor type
corresponds with current setting on SERVO rotary switch.
MOT-Command/1301: Conveyor motors are out of sync
Left and right sides of conveyor lift table do not move equal. This relates
to T3, T4, T5 and T6 with two separate lift motors.
– Lift movement may be blocked by object on lift table.
– Mechanical problem, check tension or wear on belts.
– Mechanical problem, check for loose belt wheels. Mark with a pen on
the belt wheels/shaft and check if there is a movement during
conveyor initiation.
MOT-Command/1302: The indicator mask was met too early
The board edge sensors are confused.
– The PCB may have moved out of position on the conveyor belt.
– Board handler parameters may be incorrectly set.
MOT-Command/1303: No axis movement detected by transducer for B motor
Servo software does not detect movement on B motor.
– Encoder broken or disconnected.
– Motor amplifier broken or motor not connected.
– Motor broken.
MOT-Command/1304: Lift motor 2 amplifier error
The lift motor amplifier has tripped or is broken for the right side internal
conveyor lift motor.
– Reinitiate and check. If the error is gone then this was a temporary
over current with no HW broken.
– Check if the motor is movable by hand. Replace if not.
– Disconnect the right lift motor and try to initiate the lift (conveyor
conh). If the error persists the CB board needs to be replaced.

MOT-Command/1305: Coordinator is not initiated

MOT-Command/1306: Calibrating led light level failed.
Servo software is not able to adjust LED light to desired level according
to force sensor.
– Force sensor/LED electronics broken.
– Obstacle blocking light or sensor mechanically misaligned.
MOT-Command/1307: Calibration not done.
Servo software is not able to read force sensor before sensor is calibrated.
Either calibration failed or calibration is not performed.
– Calibration not performed, internal software error, calibration not
performed.
– Calibration failed, obstacle blocking light or sensor mechanically
misaligned.
– Calibration failed, force sensor/LED electronics broken.
MOT-Command/1310: Timeout when calibrating sensors.
Servo software is not able to calibrate sensors within its time limit.
MOT-Command/1311: Indicator hit detected when not expected.
– Indicator electronics faulty.
– Obstacle caused indicator hit.
– For HYDRA, check the latches for faults.
MOT-Command/1312: Indicator not hit when expected.
Servo software failed to detected indicator hit when expected.
– For HYDRA, check the latches for faults.
MOT-Command/1313: Indicator hit detected when sensor passed linear area.
Servo software failed to detected indicator hit within the sensor's linear
area. Movement might have too high speed.
– Speed too high, parameter value wrong.
MOT-Command/1321: Amplifier In Fault
Internal error in PRIMA amplifier.
– Try to restart amplifier (turn machine power off) and reload servo.
MOT-Command/1322: Amplifier Clamp Overtime
MOT-Command/1323: Amplifier Overvoltage
Voltage too high on PRIMA amplifier DC-bus.
MOT-Command/1324: Amplifier Undervoltage
Voltage too low on PRIMA amplifier DC-bus.

MOT-Command/1325: Amplifier Overcurrent

Current from PRIMA amplifier too high. Check for short-cut in cabling
or at motor.
MOT-Command/1326: Amplifier Power Overtemperature
Internal error in PRIMA amplifier. Internal temperature too high.
MOT-Command/1327: Amplifier Clamp Overload
MOT-Command/1328: Amplifier Main Voltage Fault
Main voltage to PRIMA amplifier missing.
– Check cabling, relay and main voltage supply.
MOT-Command/1329: Amplifier IxT Protection
RMS-current from PRIMA amplifier too high. Check for short-cut in
cabling or at motor.
MOT-Command/1330: Amplifier 24 V Brake Fault
MOT-Command/1331: Amplifier Resolver Fault
MOT-Command/1332: Amplifier SinCos Encoder Signals Fault
MOT-Command/1333: Amplifier SinCos Encoder Interpolation Fault
MOT-Command/1334: Amplifier ProfiBus Communication Error
MOT-Command/1335: Amplifier Over Speed Fault
MOT-Command/1336: Amplifier I2xT Protection
RMS-current from PRIMA amplifier too high. Check for short-cut in
cabling or at motor.
MOT-Command/1337: Amplifier reports Motor Overtemperature
MOT-Command/1338: Amplifier Internal Error
MOT-Command/1339: Amplifier EEPROM Checksum Error
Internal error in PRIMA amplifier. EEPROM corrupt. Needs to be re-
programmed at manufacturer.
MOT-Command/1340: Amplifier reports Following Error
MOT-Command/1341: Amplifier reports Undefined Reference
MOT-Command/1342: Amplifier 0 Programming Failed
Servo has failed in programming of the PRIMA amplifier. Check serial
cable.

MOT-Command/1343: Amplifier 1 Programming Failed

Servo has failed in programming of the PRIMA amplifier. Check serial
cable.
MOT-Command/1344: Amplifier 0 Status Read Failed
Servo has failed in reading the status of the PRIMA amplifier. Check
serial-cable.
MOT-Command/1345: Amplifier 1 Status Read Failed
Servo has failed in reading the status of the PRIMA amplifier. Check
serial-cable.
MOT-Command/1346: Amplifier rail voltage too low
– Check the fuse or power cable on the XBOX or YBOX.
– Replace the XMPB.
– For error on Y, check the voltage level on the power inlet. Large
variations of voltage level may trig this error.
– For error on Y, check the XNET settings.
MOT-Command/1347: Amplifier rail voltage too high
– May occur if E-stop is pressed during operation at high speed,
reinitiate the machine.
– For error on Y, check the XNET settings.
– For error on X, replace the XMPB.
MOT-Command/1348: Movslomov speed parameter violated
The internal software error, TPSys/servo.
MOT-Command/1349: Movslomov eof-eos speed too low
The internal software error, servo.
MOT-Command/1350: Left border violated by right wagon
MOT-Command/1351: Right border violated by left wagon
Left and right X wagon detected too close.
– Perform an amplifier calibration.
– High tension in the cable chain may cause left and right to be pressed
together at start.
MOT-Command/1352: Index pulse detection failed
During initiation, the servo failed to move passed index pulse within a
time limit.
– Check the encoder/motor operation using the ’motortest’ in the
service program.
– Check if the movement passes the index pulse position or not.
– Check the index pulse operation using led on the read head.
MOT-Command/1353: Leave tool failed, check tool lubrication
Force needed to leave the tool was too high.
– Clean and lubricate the tool.

MOT-Command/1354: CAN-Kingdom time has stopped

The servo failed to detect the event signal from XMYCAN cable.
– Check the connection of pin2 and pin7 in XMYCAN, replace bad
cable or board.
MOT-Command/1356: HYDRA Theta not in correct position when expected
Controller performance problem with HYDRA Theta. The position of
HYDRA Theta not correct during the pick up or placement.
– Check and clean the HYDRA theta belt.
– Replace the HYDRA Theta motor, it may be worned out.
MOT-Command/1357: Computer Box Test Command Time Out
Internal software error, servo.
MOT-Command/1358: Indicator hit too early for nozzle 1 during placement
The indicator detected a hit outside the system tolerances during the
component placement. The location with reported error must be checked
manually and the mount status must be set manually. If the mount status
is not changed, TPSys will try to place again on the same location with a
risk of double placement.
– Check the location manually, set correct mount status.
– Check the package height and tolerances.
– Check that the mount tool doesn't hit the conveyor edge or component
close to the mount position.
– Check the board support where the PCB height is measured.
– For large boards with warping, the level tolerance during placement
may need to be increased (parameter 24.0305).
MOT-Command/1366: Check lubrication on nozzle 1. Indicator hit much too
early during placement


The indicator detected a hit outside the system tolerances during
component placement. The hit is most likely caused by too high friction
on a tool pipe. Either too much lubrication/dirt or more lubrication is
needed. The location with reported error must be checked manually and
the mount status must be set manually. If the mount status is not changed,
TPSys will try to place again on the same location with a risk of double
placement.
– Check the location manually, set correct mount status.
– Check the tool pipe operation and lubrication according to HYDRA
troubleshooting guide (P-050-0141).
 The tool pipes need to be clean from old lubrication/dirt and too much
lubrication also gives this problem.
MOT-Command/1374: Check mount tool for damage, indicator hit at high

speed
The indicator detected a hit outside the system tolerances during
component pick.
– Check for obstacle in the feeder/pick up position where the error
occurred.
– Check the component height and tolerance.
MOT-Command/1375: Init sequence failed to determine the machine type, left
and right axis strokes differ
MOT-Command/1376: Short circuit in a magazine
Just after a servo is loaded (during start up sequence for the magazine
bus), the servo outputs voltage on the motor channel of the magazine bus
without selecting any magazine. If any magazine is faulty, the magazine
motor can start to rotate and the servo detects current on the motor
channel.
– Remove one magazine at a time and when the servo starts up without
the error, the last magazine you removed was the faulty magazine.
– Replace TC or QMC board on the faulty magazine.
MOT-Command/1377: Lift motor 1 amplifier error
The lift motor amplifier has tripped or is broken for the left side internal
conveyor lift motor.
– Reinitiate and check. If the error is gone then this was a temporary
over current with no HW broken.
– Check if the motor is movable by hand. Replace if not.
– Disconnect the left lift motor and try to initiate the lift (conveyor
conh). If the error persists the CB board needs to be replaced.
MOT-Command/1379: Dip Unit hood open
A Dip Unit axis will not move because the lid is open.
– Close the hood.

MOT-Command/1380: Lower end-stop measurement not repeating

Poor repeatability in mechanical stop-position measurement. Most likely
caused by a mechanical failure inside the machine.
– Contact Mycronic support.
MOT-Command/3000: Phase executed before its start time has occurred
Internal servo error in trajectory calculation module.
MOT-Command/3001: Target direction is opposite current movement
MOT-Command/3002: After discretisation of jerk time, jerk time not
reasonable
MOT-Command/3003: No entry available, all are locked
MOT-Command/3004: No phase available, all are locked
MOT-Command/3005: Not possible to use entry, already locked
MOT-Command/3006: Not possible to interrupt phase
MOT-Command/3007: Target lower than min position
MOT-Command/3008: Target larger than max position
MOT-Command/3009: Moved target lower than min position
MOT-Command/3010: Moved target larger than max position
MOT-Command/3011: A negative time was encountered after calculating
trajectory times
MOT-Command/3012: Current movement do not pass interrupt position
MOT-Command/3013: Current movement has allowed speed set to zero
MOT-Command/3014: Current target not possible to reach
MOT-Command/3015: Failed to find next phase in phase list
MOT-Command/3016: Failed to remove skipped entries

MOT-Command/3017: Executing phase without initial values

MOT-Command/3018: Next entry start time already occurred
MOT-Command/3019: Failed to remove phases in unused entry
MOT-Command/3020: The time calculations did not come up with a solution
in the N-R loop
MOT-Command/3021: The time calculations cannot solve the target moved
too close case
MOT-Command/3022: Cannot calculate trajectory with lower allowed speed
than current speed
MOT-Command/3023: Trajectory acceleration outside limits
MOT-Command/3024: Trajectory jerk outside limits
MOT-Command/3025: Trajectory force outside limits
MOT-Command/3026: Trajectory speed outside limits
MOT-Command/3027: Discontinuous speed reference values
MOT-Command/3028: Discontinuous position reference values
MOT-Command/3029: Cannot find an interruptible phase in the valid phase
path
MOT-Command/3030: Position synchronization would be too large at
standstill
MOT-Command/3031: Ordered target speed is larger than the allowed speed
MOT-Command/3032: Position synchronization would be too large at target
speed
MOT-Command/3033: Current movement has allowed acceleration to be set
to zero
Wrong parameter sent to servo. Internal software error, TPSys/servo.
MOT-Command/3034: Internal phase construction error
Internal software error, servo.

MOT-Command/3035: Internal phase construction error. Axis not initialized

Internal software error, TPSys/servo. Axis was not initialized before
usage.
MOT-Command/5000: Conveyor lift table misaligned
Left and right sides of conveyor lift table do not move equal. This relates
to T3, T4, T5 and T6 with two separate lift motors.
– Lift movement may be blocked by object on lift table.
– Mechanical problem, check tension or wear on belts.
– Mechanical problem, check for loose belt wheels. Mark with a pen on
the belt wheels/shaft and check if there is a movement during
“Conveyor initiation”.
MOT-Command/5001: Amplifier Software EnableAmplifier Software Enable
PRIMA amplifier software enabled. Amplifier also needs Hardware
Enable to be able to output current.
MOT-Command/5002: Amplifier External Reference Enable
External reference for PRIMA amplifier enabled.
MOT-Command/5003: Amplifier Hardware Enable
PRIMA amplifier hardware enabled. Amplifier also needs Software
Enable to be able to output current.
MOT-Command/5004: Amplifier Power On
PRIMA amplifier main voltage is connected and working.
MOT-Command/5005: Amplifier Axis Referenced
PRIMA amplifier is in servo-mode and has enabled axis (in speed or
positioning mode).
MOT-Command/5006: Amplifier Home Switch
PRIMA amplifier servo axis has reached home-position.
MOT-Command/5007: Amplifier Encoder Marker
Not used.
MOT-Command/5008: Amplifier reports Oscilloscope Triggered
PRIMA amplifier internal oscilloscope triggered.
MOT-Command/5009: yAmplifier reports Oscilloscope Data Ready
PRIMA amplifier internal oscilloscope has finished collecting data.
MOT-Command/5010: Amplifier reports Software Limit Positive
PRIMA amplifier reports that axis has hit positive software limit.
MOT-Command/5011: Amplifier reports Software Limit Negative
PRIMA amplifier reports that axis has hit negative software limit.
MOT-Command/5012: Amplifier reports Hardware Switch Positive
PRIMA amplifier reports that axis has hit positive hardware limit.
MOT-Command/5013: Amplifier reports Hardware Switch Negative
PRIMA amplifier reports that axis has hit negative hardware limit.

MOT-Command/32000: No command specified

Communication error between TPSys processes.
MOT-Command/32001: Unknown command
MOT-Command/32002: Bad arguments
MOT-Command/32003: No free message identifiers
MOT-Command/32004: Message wait timeout
No reply from MOT board.
– Hardware problem (communication failed).
MOT-Command/32005: Write error
Failed to write to CMOT board.
MOT-Command/32006: Read error
Not used.
MOT-Command/32007: No available hardware
TPSys attempted to send a command to a non-existent hardware unit.
– Incorrect hardware configuration. Run hwconf.
– Software error.
MOT-Command/32008: File transfer busy
Not used.
MOT-Command/32009: Internal file transfer error
Communication error between HWI and a CMOT board.
– Software error.
MOT-Command/32010: Cannot open file
Communication error between HWI and a CMOT board.
– Software error.
MOT-Command/32011: Incorrect axis
MOT-Command/32012: Pack error
MOT-Command/32013: Internal startup error

MOT-Command/32014: Ioctl error

Failed to reset MOT board.
MOT-Command/32015: Reset error
MOT board did not answer after reset.
MOT-Command/32016: Position underflow
An application tried to move an axis to a negative position.
– Error in parameter setup.
– Error in package or assembly data.
MOT-Command/32017: Position overflow.
An application tried to move an axis to a position greater than allowed by
the message protocol.
MOT-Command/32018: Cannot read parameter file
Not used.
MOT-Command/32019: Hardware busy
An application tried to use hardware that was already in use by some other
application.
MOT-Command/32020: Illegal acceleration code
Invalid acceleration code was used.
– Software error.
MOT-Command/32021: System call failed
TPSys tried to run another program and failed.
– Software error.
MOT-Command/65004: Busy with file transfer
TPSys tried communicate with CAN node during file transfer
– Software error.
MOT-Command/65100: One or more configuration file checksum error
Configuration file(s) corrupt.
– Software error.

MOT-Command/65101: One or more configuration file of wrong type

Wrong configuration file(s) loaded to CAN node. For instance conveyor
software loaded to a magazine controller.
– Software error.
MOT-Command/65102: Configuration using one or more configuration files
failed
Problems during configuration of a CAN node.
– Software error.
MOT-Command/65200: Power up self test (POST) failed
Problems starting a CAN node after configuration.
– Hardware or software error.
MSETDYN status codes

This is a list of the status codes returned by the MSETDYN command.
MOT-MSETDYN/1: msetdyn returned 1

Servo program returned invalid status code.
MOT-MSETDYN/2: Lower end point not repeatable
End stop position not constant (checked during initialization).
– Mechanical problem. Check end stop hardware for loose screws and
so on.
MOT-MSETDYN/3: Upper end point outside limits
The measured mechanical range for axis is not within specified limits.
MOT-MSETDYN/4: Transducer channel 1 ptp value too low
Transducer signal not within limits or dead.
– Problem with transducer connection.
– Problem with motor connection.
MOT-MSETDYN/5: Transducer channel 2 ptp value too low
The same as for MOT-MSETDYN-4.
MOT-MSETDYN/6: Transducer channel 1 ptp value too high
MOT-MSETDYN/7: Transducer channel 2 ptp value too high
MOT-MSETDYN/10: Lower end point outside limits
Mechanical range not within specified limits.
MOT-MSETDYN/11: Upper end point outside limits
Mechanical range not within specified limits.

MOT-MSETDYN/12: No axis movement detected by transducer

The servo program tries to move an axis but there are no signals from the
transducers.
– Transducer broken.
– Motor broken.
– Problem with transducer connection.
– Problem with motor connection.
MOTIONDEV Group
Joystick and trackball interface routines.
MOTIONDEV 0: Error reading parameter file

– Software error.
MOTQ Group
These messages are generated by the MOT communication interface library.
MOTQ-0: Send byte timeout

Failed to send data to a MOT board.
MOTQ-1: Receive byte timeout.
Failed to read data from a MOT board.
MOTQ-2: Too long message received
A message was received that contained more data than the protocol
allows.
– Software error in motor control program.

MOTQ-3: Bad message number

An application tried to send a message that is not defined.
MOTQ-4: Tried to send too long message
An application tried to send a message that contains more data than the
protocol allows.
MOTQ-5: Board did not wake after reset
Not used.
MOTQ-6: Board A did not wake after reset
Not used.
MOTQ-7: Board C did not wake after reset
The MOT board in position C did not answer after reset.
MOTQ-8: Board M did not wake after reset
The MOT board in position M did not answer after reset.
MOTQ-9: Board T did not wake after reset
Obsolete.
MOTQ-10: Board X did not wake after reset
The MOT board in position X did not answer after reset.
MOTQ-11: Board Y did not wake after reset
The MOT board in position Y did not answer after reset.
MOTQ-12: Board Z did not wake after reset
The MOT board in position Z did not answer after reset.
MOTQ-13: Stepper aborted a command
Aborted by stepper.
MOTQ-14: Position underflow
An application tried to move an axis to a negative position.

MOTQ-15: Position overflow

An application tried to move an axis to a position greater than allowed by
the message protocol.
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.
OPTCENT-0: Phase error

Mycronic support.
OPTCENT-3: Cannot read correction data. (Try to re-calibrate camera)
Error in calibration data.
– Re-calibrate the camera.
OPTCENT-5: Frame grabbing failed
The frame grabber hardware failed to acquire an image from the selected
camera.
grabber.
– Hardware error (the linear encoder, the frame grabber board, the
camera box, interrupt conflicts...).
– For the Linescan cameras: The speed of the X wagon is above
2.1 m/s. Check parameter 57.0211 Speed; Max X speed or 58.0211
Speed; Max X speed.
– Software error.
– For HVCs: The speed of the X wagon is above 1 m/s when it passes
the HYDRA camera. Check parameter 52.0211 Z-Tool Centering
Offsets; X speed.
– For HVCs: Parameter 24.0203 Centering; Min distance between EOF
& flash may need to be increased.
OPTCENT-6: Uninitialized correction data
Internal error.
– The selected camera not properly calibrated.
– Software error.
OPTCENT-7: Uninitialized image buffer
Internal error. Buffer for image not initialized.
– Software error.

OPTCENT-8: Wrong tool model. Inspection aborted

– Software error.
OPTCENT-12: Calibration I/O error
Error during calibration.
Mycronic support.
OPTCENT-13: Invalid image in calibration
Cannot acquire a proper image during calibration.
– Calibration plate damaged.
– Linear encoder damaged or not properly installed.
– Linear encoder scale dirty.
– Earlier phase in calibration failed (LUT table not calibrated).
OPTCENT-14: Invalid state during Linescan camera calibration
Internal error during calibration of Linescan camera.
Mycronic support.
OPTCENT-15: Unknown state during Linescan camera calibration
Internal error during calibration of Linescan camera.
Mycronic support.
OPTCENT-16: Failed to write calibration data to database
The system could not update or create the database file containing
calibration data for the Linescan camera.
– There is no space on the hard disk.
– Hard disk failure.
OPTCENT-17: Component too big for camera field of view
Required a field of view too large for camera.
– Error in component data.
– Error in camera parameter file (number 53-58). Check the ’kxx’ and
the ’kyy’ values (for instance parameters 53.0310 Characteristics;
KXX and 53.0311 Characteristics; KYY).
OPTCENT-18: Midas reference line not found during calibration
The calibration routine has read a distorted image.
OPTCENT-19: Bad reference background
The system cannot find reference marks on reference background.
– Reference background dirty or damaged.
– Reference background not properly aligned.

OPTCENT-20: Calibration plate misaligned

The calibration plate was not displayed in the correct angle or position.
– Calibration plate pick failed.
– Calibration plate hit some object after pick.
OPTCENT-21: Internal error during Linescan camera calibration
Internal error during calibration of the Linescan camera.
Mycronic support.
OPTCENT-22: LUT calibration failed
The LUT (LookUp Table) calibration phase failed.
– Retry calibration.
– Calibration plate damaged.
OPTCENT-23: Error reading parameter file
During calibration of the Linescan camera the system failed to read the
camera’s parameter file. This is file number 57 or 58.
– Check if the file is corrupt. Run the hwconf program.
OPTCENT-24: Internal error. Wrong type of Linescan camera calibration
order
Internal error.
Mycronic support.
OPTCENT-25: Too high deviation in rotation center measurements
When performing the calibration step Measure HYDRA reference line, the
center point of the four fiducial marks surrounding each HYDRA tool is
also measured (nominal rotation center).
The measured value is relative to the center of the reference line and the
repeteability of the measurement should be better than the value given by
parameter 41.0151 HYDRA calibration with LSC; Max standard
deviation of HYDRA rotation centers.
If this message occurs, the repeatability was outside the specificed range.
– If the LSC linear encoder is used to synchronize the LSC image
capturing, change parameter 57.0481 Camera Synchronization; LSC
sync. source or 58.0481 Camera Synchronization; LSC sync. source
to X-wagon sensor.
– If the X-wagon sensor is used to syncronize the LSC image capturing,
check the X-wagon sensor or the X-wagon motor. The source of the
error can also be the servo speed regulation during image capturing.
OPTCENT-26: Not enough frame grabber memory for this operation
The image that was going to be acquired from the selected camera was too
big.
– HW error on the frame grabber board.
– Wrong version of the frame grabber board.
– Error in camera parameter file. Check parameters 57.0310
Characteristics; KXX and 58.0310 Characteristics; KXX.

OPTCENT-27: Linescan camera optical distortion too high

The measured optical distortion is above specifications.
OPTCENT-28: Probably bad tool. Optics differ too much at 0 and 180 degrees
Optical distortion measurements differ too much when rotating the
calibration plate. Probably the plate is carried tilted.
OPTCENT-29: Chosen illumination is zero
The package to be inspected has illumination zero for the camera being
used to inspect it.
OPTCENT-46: Leaded package has no lead groups
The package definition holds less than one lead group.
– Package was defined without lead groups. A probable cause is that a
generic BGA package was defined and accidentally all lead groups
were deleted.
– Package data corrupt.
OPTCENT-47: A lead group has no leads.
One or more lead groups contain too few leads/bumps.
– A lead group was defined holding less than one lead/bump. This is
unlikely to happen, as the Packages window should check for these
errors.
OPTCENT-48: Wrong lead type for a leaded package
Internal error. Should not happen.
Mycronic support.
OPTCENT-50: Lead size or lead group pitch negative or zero
One or more lead groups were detected as having leads with Lead
diameter less than or equal to zero or a Lead pitch less than or equal to
zero.
OPTCENT-52: Lead width or diameter greater than or equal to lead group
pitch
One or more lead groups were defined with a Lead diameter or Lead width
greater than or equal to the Lead pitch for the lead group. This means that
the leads/bumps overlap.
OPTCENT-54: Lead displacement or crosswise or lengthwise deviation
negative or zero
One or more lead groups were defined with a value of the Max lead
displacement, Max cross-wise deviation or the Max length-wise deviation
fields of less than or equal to zero.
OPTCENT-60: Lead group angle not 0, 90, 180 or 270 degrees
Lead group orientation not equal to a multiple of 90 degrees.
– This is most likely to happen for a Generic package of type BALL on
Ceramic, BALL or COLUMN. Check that all lead groups have the
Angle field set to exactly 0, 90, 180 or 270 degrees.

OPTCENT-61: Wrong image to table coordinates transform

A coordinate transform failed due to a singular or near singular
transformation matrix.
– One or more of the parameter files 53-58 may be corrupt.
– If this is the case, hidden parameter xx:0441 or xx:0442 has an illegal
value. Contact Mycronic support.
OPTCENT-62: Linescan camera reference line not found
The system could not find reference pattern in the picture.
– Reference pattern damaged or dirty.
– The calibration of the Linescan camera has failed.
OPTCENT-64: Incorrect angle data. Cannot calculate package angle.
Software was unable to accurately calculate the component angle. This
error can only occur for very small components with few leads or too
sparse distribution of edge points around the component outline.
OPTCENT-65: Lead group angle not within ±45 degrees
The component was estimated to have an angle larger than ±45 degrees.
– All leads were found but the data used for calculating component
angle is unreliable.
OPTCENT-68: Cannot best fit package. Too high deviations
Bent leads detected and the best-fit algorithm failed to fit package.
OPTCENT-69: Lead [***] in group [***] has too big cross-wise deviation:
[***] µm
OPTCENT-70: Lead [***] in group [***] has too big length-wise deviation:
[***] µm
At least one lead has a cross-wise or length-wise deviation larger than the
specified limit for the package.
The specified lead is the first lead in the lead group that was found faulty.
– The inspected component has one or more leads/bumps misaligned.
– Package fields Max length-wise deviation or Max cross-wise
deviation are too low.
– The calibration of the camera has failed. Re-calibrate the camera.
OPTCENT-71: Cannot locate index mark. Correlation: [***]
The index mark defined in the Packages, Index Mark window could not
be found. The message also indicates the found correlation.
– The component picked was misaligned in the matrix tray.
– The component lacks an index mark.
– Adjust the fields related to the index mark definition in the Index
Mark window.
OPTCENT-72: No leads in model
Package does not hold any leads to inspect.
– The package was defined having no leads / bumps.

OPTCENT-73: Failed to locate any component leads

Software was unable to locate component.
– Component under inspection does not match package definition.
– Component and package bump configuration match but package
definition needs fine-tuning, for instance lead diameter.
– Bad contrast between leads/bumps and background. Adjust light
levels.
– Bad component pick. Component offset outside specified limits in
parameters 41.0031 Optical Inspection; Max angle deviation and
41.0032 Optical Inspection; Max positional deviation.
OPTCENT-74: Failed to match located leads with model. Wrong package
height?
Software located leads within search areas but could not match these to
the package model.
– Component under inspection does not match package definition.
Probably the package data has a wrong package height.
– Bad component pick. Component offset outside specified limits in
parameters 41.0031 Optical Inspection; Max angle deviation and
41.0032 Optical Inspection; Max positional deviation.
OPTCENT-76: Incorrect package format
The defined package size is too small to be inspected optically.
– Check the package width and length parameters.
– Select an other camera.
OPTCENT-77: Lead [***] in group [***] has too big length-wise
deformation: [***] µm
At least one lead has a length-wise deformation larger than the specified
limit for the package.
The specified lead is the first lead in the lead group that was found faulty.
– Check Max length-wise deformation in package data.
OPTCENT-78: Chip not found. Bad contrast, size or shape correlation
The software did not find any component at all in the image.
– Pick up error.
– No components in the feeder.
– Component lost.
OPTCENT-79: Failed to locate HYDRA tool reference marks
Fiducial marks were not found in the HYDRA tool reference background.
If image blurred in the Y coordinate:
– Change parameter 57.0481 Camera Synchronization; LSC sync.
source or 58.0481 Camera Synchronization; LSC sync. source to X-
wagon sensor if the linear encoder cannot be used.

OPTCENT-80: Dark field level [***]% is above camera max, (max =

[***]%)
The dark field light level specified for the package is above the maximum
dark field level that the camera used to center the package can produce. If
the reject rate is high for the package one can try the following:
– Check the vision settings for the package.
– Run Autoteach of vision data on the package.
– If possible run the package in another camera.
OPTCENT-81: Ambient light level [***]% is above camera max, (max =
[***]%)
The ambient light level specified for the package is above the maximum
ambient light level that the camera used to center the package can
produce. If the reject rate is high for the package one can try the following:
OPTCENT-82: Front light level [***]% is above camera max, (max =
[***]%)
The front light level specified for the package is above the maximum front
light level that the camera used to center the package can produce. If the
reject rate is high for the package one can try the following:
OPTCENT-100: Bad component size: [***] x [***] µm
The found chip or outline component size (width by length) differs too
much in size from package definition.
– Check package size tolerances.
OPTCENT-101: Cannot find enough edge points on a chip side
Did not find enough edge points along one side of the chip.
– Probably the package has not a well defined side on a line. This can
for instance occur for some MELF packages.
OPTCENT-102: Chip found too far from tool rotation center.
Part of the package was found too far from the tool rotation center.
– Tool centering offset has bad calibration data.
– Picked package is much larger than the defined size.
OPTCENT-103: Chip not found. Segmented object size: [***] x [***] µm
Found foreground object differs too much in size (width by length) from
package definition.
– Component was not picked and tool was found.

OPTCENT-104: Failed to locate any component corner

The option Outline was selected in the Coarse search method field but no
body corners were found.
– Probably package body is too dark.
OPTCENT-105: Failed to locate lead in third corner
No lead was found on a third corner of the package.
– Probably the package data has a wrong package height.
– Some corner leads of the component are bent.
OPTCENT-106: Failed to locate third corner
The option Outline was selected in the Coarse search method field but a
third body corner was not found when taking a dual shot image.
– Body overall size in package data is wrong.
– Too low contrast between package body and background.
OPTCENT-107: Lead [***] in group [***] not found
At least one lead in the group was not found. The specified lead is the first
lead in the lead group that was not found.
– Lead missing or displaced too much.
OPTCENT-108: Lead [***] in group [***] has bad shape. Circularity: [***]
At least one lead of type BALL, BALL on Ceramic or COLUMN was
found having a shape far from circular. The specified lead is the first lead
in the lead group that was found faulty.
The message also indicates the found circularity value (between 0 and
100).
– Damaged lead.
– Bad illumination for the lead/package type.
OPTCENT-109: Lead [***] in group [***] has bad diameter: [***] µm
At least one lead of type BALL, BALL on Ceramic or COLUMN was
found having a too large or too small diameter. The specified lead is the
first lead in the lead group that was found faulty.
The message also indicates the found diameter value.
– Damaged lead.
– Wrong lead diameter in lead group data.
OPTCENT-110: Lead [***] in group [***] has bad width: [***] µm
At least one lead of type GULLWING, J-BEND or RECTANGLE was
found having a too large or too small width. The specified lead is the first
lead in the lead group that was found faulty.
The message also indicates the found lead width.
– Damaged lead.
– Wrong lead width in lead group data.

OPTCENT-111: Lead [***] in group [***] has bad length: [***] µm

found having a too large or too small length. The specified lead is the first
The message also indicates the found lead length.
– Damaged lead.
– Wrong lead length in lead group data.
OPTCENT-112: Lead [***] in group [***] has bad shape correlation: [***]
found having a shape far from rectangular. The specified lead is the first
The message also indicates the found correlation value (between 0 and
100).
– Damaged lead.
– Bad illumination for the lead/package type.
OPTCENT-113: Chip side angles differ too much.
The measured angles of the chip sides differ too much. A reliable angle
cannot be computed.
OPTCENT-114: Lead [***] in group [***] has bad contrast: [***]
At least one lead was found having a contrast too low relative to the rest
of the leads in the group. The specified lead is the first lead in the lead
group that was found faulty.
The message also indicates the found contrast value (between 0 and 255).
– Damaged lead.
OPTCENT-115: Defect component or bad pick
If a component is defect or has been picked badly, perform the steps
below in the given order until the problem is solved.
– Change any inappropriate tool.
– Fine tune the feeder.
– Change any defect or worn tool.
– Remove any loose cover tape.
– Adjust the feeding acceleration.
– Change any inappropriate feeder type.
– Clean the tool from paste.
– Remove defect components.

OPTCENT-116: Defect component or bad pick. Component might be picked

on a corner
If a component has been picked badly, perform the steps below in the
given order until the problem is solved.
– Remove defect components.
– Change any damaged or worn tool.
OPTCENT-117: Pick error detected. Component rejected
This message may arise when the component has been picked on a corner
or when the component is upside down. If a component has been picked
badly, perform the steps below in the given order until the problem is
solved.
– Change any damaged or worn tool.
OPTCENT-118: Odd shape package rejected
This message is shown when a package that has been programmed as an
Odd shape is rejected by the vision system. If this happens, make sure that
the package has passed the package quality test inside the Odd shape
Autoteach. Best practices on how to program Odd shape package can be
found in the TPSys Programming Manual Chapter 7.

OPTCORR Group
These messages are generated by the optical correction vision routines.
OPTCORR-0: Did not find first point

The software didn't find the first point (the leftmost point on the monitor)
in one or more rows in the calibration pattern.
– The parameters for contrast and background noise are too low or too
high. Check parameter groups 64, 65, 68-70, 73 or 74 depending on
the camera. For HYDRA the parameters are 64.0136 Group;
Background variance and 64.0137 Group; Object deviation.
– The contrast polarity (white on black) is wrong. For HYDRA, the
parameter to check is 64.0141 Pin; White on black.
– The calibration pattern is damaged.
– The light from the LEDs causes reflections in the calibration pattern.
– Wrong pattern is used.
OPTCORR-1: Failed to locate all points
The software did not find all points in the calibration pattern.
– The parameters for contrast and background noise are too low or too
high. Check parameter groups 64, 65, 68-70 or 75 depending on the
camera.
– Check parameter 64.0130 Pattern number.
– The contrast polarity (white on black) is wrong. For pattern number 7
(HYDRA) the parameter to check is 64.0141 Pin; White on black.
– The calibration pattern is damaged.
– The light from the LEDs causes reflections in the calibration pattern.
OPTCORR-2: Bad point to point distance
The distance between the points in the image does not match the model.
– The magnification is wrong. Adjust the focus of the camera.
OPTCORR-3: Failed to allocate enough memory
There is no more memory available to the image process.
– Probably a software error.
OPTCORR-4: Invalid type of calibration plate
The number of the calibration pattern is not valid. Calibration patterns are
numbered 0...1.
– Check in parameter group 64, 65, 68 – 70, 73 or 74, depending on the
camera, which pattern should be used for the selected camera.

OPTCORR-5: Failed to update the correction database

The software failed to save the result of the calibration.
– TPSys not properly installed. The directory where the database is
stored is missing.
– The hard disk is full or bad.
OPTCORR-6: Failed to calibrate DVC illumination unitOdd shape
TPSys failed to calibrate the DVC-illumination unit of the camera.
– Ensure that the correct revision of the calibration plate was used. The
illumination unit cannot be calibrated with old calibration plates with
black marks on a white background.
– Check that all LED-groups of the camera are working.
OPTCORR-7: Frame grabbing failed
camera.
grabber card.
OPTCORR-8: Wrong plate or wrong plate side shown when calibrating
illumination
An illumination calibration is being attempted without using the grey
DVC illumination calibration plate.
– Use the grey DVC illumination calibration plate for calibrating
illumination instead of the DVC optical calibration plate.
OPTCORR-9: X-wagon camera front light gain is too high or too low but
illumination calibration was successful
OPTCORR-10: X-wagon camera ambient red light gain is too high or too low
but illumination calibration was successful
OPTCORR-11: X-wagon camera ambient blue light gain is too high or too low
but illumination calibration was successful
– The gain value for partial light is outside the value range of 0.5-1.25.
Calibration result is written after user approves the values, but
technician should be called to correct camera settings.
OPTCORR-12: X-wagon camera front light gain calibration failed.
Illumination unit probably damaged or out of specifications
OPTCORR-13: X-wagon camera ambient red light gain calibration failed.
OPTCORR-14: X-wagon camera ambient blue light gain calibration failed.
– Gain for partial light is outside the value range of 0.1-2.0. Calibration
is canceled. Technician must be called to repair or replace the camera.

OPTP Group
These messages are generated by the optimizer process.
OPTP-1: Component [***] not available

The specified component is not available for assembly.
– Check magazine data.
– Check that magazine is inserted.
OPTP-3: Start assembling
Information message: Assembly is started.
OPTP-6: Stopped, all components mounted
Information message. Assembly stopped and layout is finished.
OPTP-7: Stopped, missing components
Information message. Assembly stopped because there are components
missing and the layout is not finished.
OPTP-8: Stopped, missing components in lower group
Information message. Assembly is stopped because there are missing
components and there are components that cannot be mounted because
the mount positions not mounted have a lower Group number.
OPTP-9: Stopped or aborted
Information message. Assembly interrupted by operator.
OPTP-10: Stopped, error
Assembly interrupted by an error.
OPTP-11: Component [***] available
Information message. The specified component is available again.
OPTP-12: All positions glued
Glue dispense operation finished.
OPTP-13: Stop. Nothing to glue
Glue dispense operation was started but there where no dispense
information in the layout.
OPTP-14: Start gluing
Glue dispense operation started.
OPTP-15: Unknown package [***] specified
The assembly data contains a component with an unknown package.
OPTP-16: Unknown glue dot [***] for package [***]
A glue dot of unknown type was specified for the specified package.
OPTP-17: Tool [***] not present
The specified tool that is required for this layout is not present.
OPTP-18: Tool [***] not installed
The specified tool that is required for this layout is not installed.

OPTP-19: Component [***] not defined

A component specified in the current layout is not defined in the
Components window.
OPTP-20: Mount data modified
The assembly information has been modified during assembly and the
current layout status is no longer valid.
OPTP-21: HYDRA option not active. HYDRA ignored
HYDRA has been specified but the HYDRA option is not activated.
OPTP-22: Electrical measure option is off
The Save electric value field in the PCB Items window was set to Yes but
parameter 191.0024 Options; Electrical measurement is not activated.
Note! The 191.0024 Options; Electrical measurement option saves the
measured values in the event log, while the 191.0012 Options; Electrical
two-pole test option and the 191.0013 Options; Electrical transistor test
option only check the values against specified limits in the component
data.
OPTP-23: Missing glue data for package [***]
No glue dot information was specified for the specified package.
OPTP-26: Cannot mount component [***], try to rotate pick/place angle.
The specified component cannot be picked or placed without hitting an
object in the machine.
The pick angle and the place angle must be aligned with each other. Try
putting the longest side of the component in the X direction of the
machine. Also try to turn the PCB so that the component when placed also
is aligned with the X direction.
OPTP-28: Force is below friction for package [***]
The selected placement force for the specified package is insufficient to
overcome friction and cannot be used.
– Increase the selected placement force.
OPTP-29: The machine is stopped due to an incorrect magazine removal
A magazine was removed without pressing the magazine button first. This
behavior risks damaging magazine hardware.
– Press magazine button before removing the magazine.
OPTP-30: Package [***] is not odd shape and has package offsets. Make a
copy of it and select to remove mount/angle offsets
–
–
OPTP-50: Fatal process error ID: [***]: [***]. Restart system
The optimization process crashed. The system has to be restarted.
Mycronic support.

ORGP Group
These messages are generated by the organizer process.
ORGP-1: Fatal process error ID: [***]: [***]. Restart system

A fatal error has occurred.
– Restart system.
ORGP-2: Changed electrical test method for [***]
The specified component has a capacitor test that cannot handle the
component’s capacitance value. The system will switch to a different test
that can handle the value.
– Check component data.
ORGP-3: Electrical test [***] did not match any centering angle for [***]
The specified component has an electrical test (1 or 2) with an angle that
is not used in any centering phase specified for the package. The system
will not have any opportunity to test the value during assembly and the
test will not be performed.
– Check component data.
– Check package data for component.
ORGP-4: Unknown glue dot type [***] specified for [***]
An unknown glue dot type has been specified in the package data for the
specified component.
– Check glue dot list.
ORGP-5: Option flags are invalid
The magic word does not correspond to the options and machine number.
The machine can still be used but all options are turned off.
– Check the 191 Options parameter group.
– Check machine number hardware.
ORGP-7: Electrical test option is off. Component [***]
Electrical test specified and the electrical test switch is turned on but the
electrical test option is off. No electrical test will be performed.
– Check parameter 191.0001 Magic word.
ORGP-8: Transistor test option is off. Component [***]
Transistor test specified and the electrical test switch is turned on but the
transistor test option is off. No test will be performed.
– Check parameter 191.0001 Magic word.
ORGP-10: Optical centering option is off. Component [***]
Optical centering is specified but the optical centering option is off.

ORGP-11: No usable optical centering cameras defined for [***]

The system could not find a centering camera for the specified
component.
ORGP-12: Tool to top offset too big for package [***]
The specified package’s Tool to top offset value is greater than the value
of the Overall height field.
– Check package data.
ORGP-13: Error mounting component [***] from feeder [***]/[***] in
location [***]
An error occurred while mounting the component picked from the
position indicated in the message. The mounter will give a message
indicating the nature of the problem.
ORGP-14: Error mounting component [***] from tray [***]/[***] in
location [***]
An error occurred while mounting the specified component picked from
the YWM or TWM tray name indicated in the message.
The mounter will give a message indicating the nature of the problem.
ORGP-15: Error mounting component [***] from TEX [***]/[***] pallet
[***]/[***] in location [***]
the TEX or ATM tray name indicated in the message. The message also
indicates which TEX or ATM unit it is, and which cassette/cassette row
the tray is located in.
The mounter will give a message indicating the nature of the problem.
ORGP-19: Error mounting component [***] from feeder [***]/[***] with
nozzle [***] in location [***]
An error occurred while mounting the component picked from the
slot/feeder indicated in the message with the stated HYDRA nozzle. The
system will give a message indicating the nature of the problem.
ORGP-20: Failed to locate magazine in slot [***]
TPSys failed to locate the magazine in the specified slot. If the Fiducial
mark field in the Magazines window is set to Yes, the magazine will not
be used until it has been located.
– Check the fiducial mark on the magazine for damage.
– Locate the magazine manually.
ORGP-21: Optical centering option is off. Package [***]
No attempt is done to pick a component because the package specifies an
optical centering phase, but the optical centering software option is
disabled.
– Request a new magic word from Mycronic
– If no optical centering is necessary, delete the optical centering phase
from the package and use mechanical centering instead.

ORGP-22: Error mounting component [***] from tray [***]/[***] with

nozzle [***] in location [***]
the YWM or TWM tray name indicated in the message with the stated
HYDRA nozzle.
– The mounter will give a message indicating the nature of the problem.
ORGP-23: Error mounting component [***] from TEX [***]/[***] pallet
[***]/[***] with nozzle [***] in location [***]
the TEX or ATM tray name indicated in the message with the stated
HYDRA nozzle.
The message also indicates which TEX or ATM unit it is, and which
cassette/cassette row the tray is located in.
– The mounter will give a message indicating the nature of the problem.
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.
PARFILE-1: Error parsing [***].[***] in parameter file "[***]"

The system failed to parse a parameter in a parameter file.
– File corrupted. Make a ’savestat’ diskette and contact Mycronic
support.
PARFILE-2: Parameter file "[***]" not found
The system tried to read the specified parameter file but the file did not
exist.
support.
PARFILE-4: Unknown typecode in parameter file [***], line [***]
Parse error in parameter file.
support.
PARFILE-5: Invalid ModifyAction in parameter file "[***]"
Parse error in parameter file.
support.

PARFILE-6: No parameter [***].[***] in parameter file "[***]"

Parameter missing from file.
support.
PARFILE-7: Invalid file number in parameter file "[***]"
Unexpected file number in parameter file.
support.
PARFILE-8: Parameter [***].[***] outside limits in file "[***]"
A parameter has an illegal value.
– Use ’pared’ (stand alone parameter editor) to correct problem.
PARFILE-9: Unknown parameter file name "[***]"
The system tried to read a parameter file but the file did not exist.
PARFILE-10: Unknown parameter file number [***]
The parameter group number is not listed as a valid parameter group
number.
support.
PARFILE-11: Attempt to write illegal value to parameter [***].[***]
The system tried to write a value outside allowed limits to a parameter.
support.
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.
SERCOM-0: Error opening communication

Failed to open device for serial communication. For more details check
previous and following messages.
SERCOM-1: Error closing communication
Tried to close an already closed serial communication channel.
Mycronic support.
SERCOM-2: Receive timeout
Errors in serial communication. For more details see the accompanying
messages.

SERCOM-3: Receive error

messages.
SERCOM-4: Transmit timeout
messages.
SERCOM-5: Transmit error
messages.
SERSTART Group
These messages are generated by the serial start facility.
SERSTART-0: Received signal [***]. Terminating

Received a UNIX software signal. This will cause the process to
terminate.
– Software error.
SERSTART-1: Failed to establish signal handlers. Terminating
Internal problem in software.
– Software error.
SERSTART-3: Directory [***] is not accessible
Specified directory cannot be accessed.
– Error in parameter.
– Error in installation procedure.
– Software error.
SERSTART-4: Cannot open file [***] for write
File cannot be opened for write.
– Software error.
SERSTART-5: Cannot write to file
File cannot be opened for write.
– Software error.
SERSTART-6: Barcode option flag is invalid
Barcode option is not set (required for this function).
– Error in parameter 191.0001 Magic word.
– Option not available on this machine.
SERSTART-7: Unknown layout barcode "[***]"
No layout has the scanned barcode.
– Wrong barcode in layout.

SERSTART-8: "[***]" is not a layout barcode

The scanned barcode does not have the expected layout barcode prefix.
– Check the following parameters:
123.0511 Layout; Prefix1.
– Broken barcode.
SERSTART-9: "[***]" is not a PCB ID barcode
The scanned barcode does not have the expected PCB ID barcode prefix.
123.0521 PCB ID; Prefix1.
– Broken barcode.
SERSTART-11: Cannot open device [***]
The specified serial device cannot be opened.
SERSTART-12: Unknown barcode "[***]"
The scanned barcode is not a layout or PCB ID barcode.
SHDB Group
These messages relate to data sharing.
SHDB-1: Bad host name for data server

The given server host name is not a known host.
– Name server problem.
SHDB-2: dataServer: invalid magic word
Invalid magic word. Can't share databases.
– See parameters 191.0001 Magic word and 191.0021 Options; Shared
databases.

SHDB-3: dataServer protocol version mismatch

The server protocol on the server does not match the protocol on this
machine.
– Different TPSys versions on server and machine.
– Problem with network or network board on machine or server.
SHDB-4: dataServer protocol version name is empty
The server process on the server does not respond.
– Software problem on the server.
SHDB-5: Lost network connection to remote data server
Lost network connection with server.
TCP Group
These messages are generated by the shared database communication.
TCP-1: Host "[***]" is unknown. Unable to connect

Tried to share data with an unknown host.
– Specified host not reachable (host or network down).
TCP-2: Lost connection with dataserver at host "[***]"
The communication with the specified host was broken.
– Network error.
TCP-3: Unable to connect to TCP socket.
Cannot find network connection.
– Network support not installed.
TCP-4: Unable to connect to dataserver at host "[***]"
The specified host does not appear to accept server connections.
– Selected host is not a TPSys machine or TPSys server.
TCP-5: Connected to dataserver at host "[***]"
TCP-6: Network connection with host "[***]" reestablished
TEX VISION Group

These messages are generated by the TEX VISION routines.
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.

TEX VISION-0: Phase error

– Internal software problem. Make a ’savestat’ diskette and contact
Mycronic support.
TEX VISION-1: Failed to locate corner
A TEX palette corner was not found.
No point in image with enough correlation was found.
– Decrease parameter 42.0131 Number of pallet types; Correlation
minimum.
– Decrease parameter 42.0121 Sample period; Sparse.
– Try a lower precision on parameter 42.0103 Pallet 1; Corner mask
type, precision.
– Pallet corner lies out of search area. Check parameters 41.0072
Search Area; X-wise width to 41.0075 Search Area; Y-wise offset.
– Image level for background, and objects are too demanding. Decrease
parameters 42.0111 Image level; Background and 42.0112 Image
level; Object.
TEX VISION-2: Image size negative or zero
TEX VISION-3: Image scale negative or zero
TEX VISION-4: Histogram step size out of bounds
Internal error.
– Sample period used for creating image gray-scale histogram lower
than 1 or bigger than image size dimensions.
– Parameter 41.0111 Histogram; Sample period out of bounds.
TEX VISION-5: Histogram image levels out of bounds
Histogram gray minimum and/or maximum levels out of bounds or
inconsistent.
– Parameter 41.0112 Histogram; Min level or 41.0113 Histogram; Max
level out of bounds, or Max. level <= Min. Level.
TEX VISION-6: Histogram bins too few
Too few bins selected for creating image histogram.
– Parameter 41.0114 Histogram; Number of bins is lower than 2.
TEX VISION-7: Sample period out of bounds
Sample period used when rough searching and/or fine searching pallet
corner out of bounds or inconsistent.
– Parameters 42.0121 Sample period; Sparse and 42.0122 Sample
period; Close are lower than 1, or sparse sample period is lower than
close sample period.

TEX VISION-8: Object and/or background level out of bounds

Image gray levels estimated for background and object out of bounds.
– Parameter 42.0111 Image level; Background or 42.0112 Image level;
Object out of bounds.
TEX VISION-9: Correlation out of bounds
Minimum correlation for accepting a possible pallet corner out of bounds.
– Parameter 42.0131 Number of pallet types; Correlation minimum <=
0 or >= 100.
TEX VISION-10: Bad search area
Pallet corner searching area lies partly out of image.
– Parameters 41.0072 Search Area; X-wise width to 41.0075 Search
Area; Y-wise offset too big.
TEX VISION-11: Failed to convert object mask
Failed to convert any TEX corner searching mask to pixel coordinates.
– The file /home/tpsys/lib/palletmaskdata was modified and a
mask without points was defined.
TEX VISION-12: Bad mask boundaries
Mask lies out of image boundaries after conversion to pixel coordinates.
– The file /home/tpsys/lib/palletmaskdata was modified and a
mask without points was defined.
TEX VISION-13: Failed to estimate image intensity levels
Failed to estimate background and object intensity levels in the image.
– TEX search area is incorrect, in other words wrong size or offset.
Check parameters 41.0072 Search Area; X-wise width to 41.0075
Search Area; Y-wise offset.
– TEX histogram parameters are wrong. Check for consistency in
parameters 41.0111 Histogram; Sample period to 41.0114
Histogram; Number of bins.
– Two histogram max were not found, for instance no object in image.
TEX VISION-14: Object ambiguity
Two or more points were found with maximum and equal correlation.
TPSys could not decide which is the pallet corner.
– Locate pallet again.
TEX VISION-15: Failed to use data in pallet vision parameter file.
Failed to read or parse a TPSys parameter file. Most likely the file
containing parameters related to the pallet vision software 'palletVision.'
– File /home/tpsys/params/palletVision is missing.
– This file has been modified and its syntax is incorrect.

TEX VISION-16: Pallet type not valid.

The selected TEX pallet type is not valid.
– The selected pallet type is not defined. Check parameters 42.0102
Pallet 1; Pallet type and 42.0101 Pallet 1; Valid parameters.
TEX VISION-17: Failed to read pallet mask data file
Failed to read or parse the palletmaskdata file. This file contains the
descriptions of the masks used for searching the TEX pallet corners.
– File /home/tpsys/lib/palletmaskdata is missing.
– The file above has been modified and its syntax is incorrect.
TEX VISION-18: Mask type in pallet vision parameter file unknown
The selected mask for searching the TEX pallet corner is not found in the
palletmaskdata file. Check parameters 42.0103 Pallet 1; Corner
mask type, precision and 42.0104 Number of pallet types; if OTHER
specify.
– The mask is not defined in the palletmaskdata file.
TEX VISION-19: Bad mask definition
– Take a savestat and contact Mycronic service
TEX VISION-20: Frame grabbing failed
camera.
grabber card.
TLMN Group
These messages are generated by the tool management routines.
TLMN-0: Error reading parameter file

– Corrupted parameter file (toolmanager).
TLMN-1: Tool identifier out of range
The application tried to access a tool that does not exist.
TLMN-2: Tool type out of range or tried to manipulate generic tool
The application tried to fetch or leave a tool that was not specified in
parameter group 23 Tool manager.

TLMN-3: Failed to fetch tool since tool not installed

The application tried to fetch or leave a tool that was not installed.
TLMN-4: Failed to fetch tool automatically
Automatic tool fetch failed.
– Too much or too little grease on tool.
– Try using a different lubricant.
TLMN-5: Failed to leave tool automatically
Automatic park leave failed.
– Try using a different lubricant.
TLMN-6: Failed to fetch tool
Could not fetch tool automatically or automatic tool fetch failed and
operator refused to insert tool manually.
TLMN-7: Failed to leave tool
Could not leave tool automatically or automatic tool leave failed and
operator refused to remove tool manually.
TLMN-8: Z force sensor faulty
Z-force sensor did not respond to calibration.
– Hardware error.
– Dirt on sensor.
– The system failed to fetch tool properly.
TLMN-9: Preliminary fetch failed, try to unlock tool manually
Failed to fetch tool for tool position measurement.
– Operator error. Check that tool is present and retry.
TLMN-10: Failed position search during installation
Automatic tool position measurement failed.
– Operator error, try again.
– Problem with the preliminary fetch.
TLMN-12: Error writing parameter file
Failed to update parameter values after installation.

TLMN-13: Measured tool length too short

The tool length measured by the system is shorter than the limit specified
in parameter group 23 Tool manager.
– Z friction too high or force too low.
– Check minimum length parameter for specific tool.
TLMN-14: Failed to fetch tool since tool is marked as non-present
The system tried to use or install a tool that is marked as “not present” in
the parameter group 23 Tool manager.
– Software error.
TLMN-15: No tool bank installed
The software tried to perform an action that involves checking a tool, but
no check position was defined.
– Tool bank installation not properly completed.
TLMN-16: Checking Z position failed when cycling tool
Fetch or leave failed during automatic test after checking Z position.
TLMN-17: Measuring Z position failed when cycling tool
Fetch or leave failed during automatic test after measuring Z position.
TLMN-18: Failed to reach tool bank level
Z unit did not reach tool bank during tool installation.
TLMN-19: Failed to leave tool since tool is not installed
TPSys tried to leave a tool that is marked as not installed in TPSys.
– Re-install the tool.
TLMN-20: Failed to leave tool since tool is marked as non-present
TPSys tried to leave a tool that is marked as non-present in TPSys.
– Re-install the tool.
TLMN-21: Tool in use by other X wagon
This message follows after another message that indicates which tool the
message refers to.
A shared mount tool is needed by one X wagon but is used by the other
X wagon.
– Leave the mount tool manually from the other X wagon.
TLMN-22: Tool bank level too low
The tool bank was detected to be too low when trying to install a tool.
– Z might have a too short stroke. Follow Service Bulletin number:
2008064.

UCOPY Group
These messages are generated by the UNIX copy routines.
UCOPY-1: No such file or directory

Attempt to write a file with illegal name.
– The specified directory does not exist.
– File name contain illegal characters.
UCOPY-2: Permission denied
Not allowed to write file to specified directory.
– The selected directory is not owned or writable by user TPSys.
– A file with the specified name already exists and this file is not
writable by user TPSys.
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.
UNIX-2: ENOENT: No such file or directory

The system tried to access a file or a directory that does not exist.
UNIX-6: ENXIO No such device or address
This might indicate a hardware problem where the Linux kernel did not
detect all necessary hardware at boot time. The most common problem is
a connector or board not properly plugged in.
USR Group
The messages in this group are generated by the User handling routines.
USR-1: User "[***]" logged in

The specified TPSys user logged in.
USR-2: User "[***]" logged out
The specified TPSys user logged out.

VACC Group
Vacuum system interface routines.
VACC-0: Error reading parameter file

– Software error.
VER Group
These messages are generated by the electrical verifier interface routines.
VER-0: Error reading parameter file

VER-1: Error writing parameter file
Cannot update parameter values.
VER-3: The verifier is not calibrated
Hardware not calibrated when electrical measurement/verify operation
started.
– Hardware problem in MOT board Z.
VER-4: Tried to measure without preparation
Measurement data not prepared when data should be sent to MOT
board Z.
Mycronic support.
VER-5: Tried to verify without preparation
Verify data not prepared when data should be sent to MOT board Z.
Mycronic support.
VER-6: Illegal electrical test code
Non-existing test code specified.
Mycronic support.
VER-7: Range selection failed
Electrical values are outside specifications.
– Operator error. Check electrical properties in component data against
specification.

VER-8: Measure failed (no value obtained)

Unable to perform measurement.
– Hardware problems.
– Measured property not compatible with component type.
– Actual component value too far from expected.
VER-10: Verifier calibration failed
Failed to calibrate hardware.
VER-11: Verifier failed for [***]
Verify or measure failed for specified component. The reason is specified
in a previous message.
VISION Group
These messages are generated by the vision routines.
VISION-0: Error reading parameter file

Cannot read parameter for vision routines (parameter group 41 Vision).
– Corrupt parameter file.
– Missing parameter file.
– Wrong parameter file version.
– Software error.
VISION-1: Camera is not installed
The requested camera is not installed/enabled.
– The camera were not selected as present when the ’hwconf’ program
were run.
VISION-2: Error in camera parameter file
The image process has detected an error in the parameter file for selected
camera. Normally the parameter file reader (PARFILE) should detect this
type of errors.
– Check the different data in the parameter file against the limits. Check
especially the 52.0310 Characteristics; KXX and 52.0311
Characteristics; KYY parameters and their equivalents.

XINSP group
Messages generated when inspecting components on trays with the PVC (X-
wagon camera).
XINSP-0: Did not find package on tray

Software could not find component in matrix tray pocket when using the
PVC.
– No component in matrix tray pocket.
– Software could not discern between component and matrix tray
pocket.
XINSP-1: Unknown package
The package is not defined in the package database.
– The package is not defined or the package name is misspelled in either
the Packages window or the Components window.
XINSP-2: Package larger than camera field of view
Package dimensions are larger than the PVC field of view at the current
presentation angle on the tray.
– Package covers the whole image and its position cannot be calculated
with a single PVC image. Check if the package fits the PVC field of
view if the tray is rotated 90 degrees, otherwise select No in the
Inspect before pick field in the Tray Types window.
XINSP-3: Package out of camera focal depth
After a successful pick and centering it is discovered that the component
was picked on the tray at a height too far from the PVC focal depth.
– Matrix tray positioned too low or too high relative to the mounting
height. Adjust matrix tray height on the wagon.
XINSP-4: Component not found on board
Software could not find component on the board when using the PVC.
– Background noisy around the component on the board.
– No component on board on this board position.
XINSP-5: Bad component size: [***] x [***] µm
Found chip or outline component size (width by length) differs too much
in size from package definition.
XINSP-6: Cannot find enough edge points on a chip side
Did not find enough edge points along one side of the chip.
– Probably the component does not have a well defined side on a line.
This can for instance happen with some MELF components.
XINSP-7: Chip found with too big position offset
Part of the component was found too far from expected position.
– Component badly placed on matrix tray or PCB.
– Tray not trimmed correctly.

XINSP-8: Bad coarse component size: [***] x [***] µm

Found foreground object differs too much in size (width by length) from
package definition.
– Package cannot be separated from background.
XINSP-9: Chip side angles differ more than 10 degrees
The measured angles of the chip sides differ too much. A reliable angle
cannot be computed.
XINSP-10: Frame grabbing failed
camera.
grabber card.
Hardware error, for instance camera, VVG2 card or interrupt conflicts.
Contact Mycronic support.
XINSP-11: Tray type pocket size is too small
The specified tray pocket is too small to perform any image analysis of
components on the tray.
Pre-pick inspection does not work for components lying in trays with such
small pockets.
– Problems with the tray pocket size definition in the Tray Types
window. For instance, the same coordinate was given twice when
teaching the Tray pocket width/length field using the camera.
– The chosen tray pocket size is too small. The exact limit depends on
the type of X-wagon camera. For instance, the limit is 0.17 mm in
length or width for PVC4.


Mycronic TPSys 3.3 Appendix B – Parameters
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.
1.0007 Axes to include in servo savestatus

Available values: None, Failing, and All.
1.0008 Save system status on shutdown
Available values: Never, Daily, Weekly, and Monthly.
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.
4002720-EN – Software Manual Rev. A 2016-04 B-1

Appendix B – Parameters TPSys 3.3 Mycronic
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
Tool Check and Calibrate

23.0343 Tool Calibration; Always calibrate
Time can be saved during tool changing if the length of the tool is not
measured (calibrated). This parameter controls if a tool needs to be
calibrated every time the tool is changed. The system behavior is
depending on the type of board handling system.
– Machines with CAN-based board handling systems:
Yes – Tools are calibrated when fetched, if the machine has
been restarted or if a Y-wagon hood has been opened.
No – Tools will only be calibrated if marked for calibration in
the Tool Installation menu.
– Other machines:
Yes – Tools are always calibrated when fetched.
No – Tools will only be calibrated if marked for calibration in
the Tool Installation menu.
B-2 Rev. A 2016-04 4002720-EN – Software Manual

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.
To be able to use a reject bin, it needs to be installed. To install a reject bin, it

needs to be activated in the Parameters window.
• On MY9–MY19 machines, bins 1-4 are always activated, and bins 5-8 are
by default deactivated.
• On MY100 machines, bins 1-4 are by default activated, and bins 5-8 are by
default deactivated.
If you need to activate a bin, edit parameter 32.0061 Reject Position 5; Type
(for bin 5) or corresponding. Depending on machine model, the field can have
the following values:
– Not Used – Bin is deactivated and cannot be installed from TPSys.

– Y Wagon – Bin is activated as a bin sitting on the Y wagon. To install,
select Utility > Installation and Calibration > Locate Reject Bins in
the TPSys main menu.
– Frame – Bin is activated as a bin sitting in the machine frame. To
install, select Utility > Installation and Calibration > Locate Reject
Bins in the TPSys main menu.
 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.
Mark Found Object Statistics

41.0171 Mark Found Object Statistics; Mark contrast
During test centering, the lead with the highest contrast is marked with a
'C' and the lead with the lowest contrast with a 'c'.
41.0172 Mark Found Object Statistics; Mark background noise
During test centering, the lead with the highest background noise is
marked with an 'N' and the lead with the lowest background noise with an
’n’.
41.0173 Mark Found Object Statistics; Mark object brightness variance
During test centering, the lead with the highest brightness variation is
marked with a ’V’ and the lead with the lowest brightness variation with
a ’v’.
41.0174 Mark Found Object Statistics; Mark shape correlation
During test centering, the lead with the highest shape correlation feature
is marked with an ’F’ and the lead with the lowest shape correlation
feature with an ’f’.
41.0175 Mark Found Object Statistics; Mark object width
During test centering, the lead with the bigger width value is marked with
a ’W’ and the lead with the smaller width value with a ’w’.

45 Autoteach
Standardized pitches for BGA packages

These parameters define the standardized pitches Autoteach chooses between
when measuring the pitch and aligning the solder balls to a grid. Fifteen
standardized pitches can be defined for each package type.
45.2001 Standardized pitches for BGA packages; pitch1 – 45.2015

Standardized pitches for BGA packages; pitch15
Standardized pitches for BGA packages. If the parameter is set to -1 the
system ignores this entry.
It is recommended to only use the last three of these parameters to enter
custom pitches. Leave the other parameters at default.
Standardized pitches for leaded devices

45.2101 Standardized pitches for leaded devices; pitch1 – 45.2115
Standardized pitches for leaded devices; pitch15
Standardized pitches for leaded devices. If the parameter is set to -1 the
system ignores this entry.
Standardized pitches for flip-chip packages

45.2201 Standardized pitches for flip-chip packages; pitch1 – 45.2215
Standardized pitches for flip-chip packages; pitch15
Standardized pitches for flip-chip packages. If the parameter is set to -1
the system ignores this entry.

46 X Wagon Camera Illumination

These parameters may need to be changed to achieve a satisfactory
illumination result. However the default values will work in most cases.
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
Bad Board Mark

46.0101 Bad Board Mark; Front Red
46.0102 Bad Board Mark; Ambient Red
46.0103 Bad Board Mark; 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
64 HYDRA camera calibration
Measure Reference Background

64.0041 Measure Reference Background; Max X displacement
Max X displacement. This controls the displacement from the ordinary
X position where the pictures are taken.
 If the system has problems finding reference points or components, you can
try lowering this value.
65 Optical calibration standard camera

65.0141 Pin; White on black
This parameter should be set to match the type of calibration board used
(a black board with bright dots or vice versa).

68 Optical calibration HRC camera

69 Optical calibration standard camera 2

70 Optical calibration HRC camera 2

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.
Figure B-1. Sloping tray.
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
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
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
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.

233 Operator attention signals

The light tower and the buzzer are controlled by this parameter group.
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).
Machine state parameters

233.0011 Running; and everything is ok
233.0012 Running; but will stop shortly
233.0013 Running; but with bad performance
233.0021 Waiting; for PCB load/unload
233.0031 Stopped; idle
233.0032 Stopped; need help to continue
233.0033 Stopped; fatal error
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.
Common attention signals

Green Yellow Red Buzzer Value
0x0004
Steady 0x0404
0x0206
0x4246
0x0006
Intermittent 0x0606
0x0105
0x0505
0x0007
0x4747
0x0002
0x0202
0x0003
0x0203
0x0303
0x4043
0x4243
0x0001
0x0101
0x0041

Custom attention signals

If the table above does not cover your needs, you can follow the guidelines
below to derive the value to enter into the corresponding machine state
parameter.
Example:
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 Steady Intermittent

White lamp. 0 1
Buzzer. 0 4
0x4246 The second digit is the sum of the following values:
Lamp Steady Intermittent

Red lamp. 0 1
Yellow lamp. 0 2
Green lamp. 0 4
0x4246 The third digit is the sum of the following values:
Lamp/Buzzer Off On
White lamp. 0 1
Buzzer. 0 4
0x4246 The fourth digit is the sum of the following values:
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.

Example: Assume you want to have an intermittent buzzer, intermittent yellow

lamp and steady green lamp for machine state 233.0013 Running; but with bad
performance. The red lamp and the white lamp should be off.
Green Yellow Red White Buzzer
• The prefix should always be ’0x’.

• The first digit should be ’4’ since the buzzer should be intermittent.
• The second digit should be ’2’ since the yellow lamp should be intermittent,
and the green lamp should be steady.
• The third digit should be ’4’ since the buzzer should be on and the white
lamp should be off.
• The fourth digit should be ’6’ since the yellow lamp and the green lamp
should both be on, and the red lamp should be off.
For the example above, you need to enter 0x, 4, 2, 4 and 6 into the 233.0013
Running; but with bad performance field, in other words 0x4246.
 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’.


Mycronic TPSys 3.3 Appendix C – Event Log Export Format
Appendix C – Event Log Export Format

The Event Log is used to record events related to machine operation. The two
main uses for the event log is to extract management and traceability data.
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.
We will describe the following:
• General Format Information.

• Event Lines.
4002720-EN – Software Manual Rev. A 2016-04 C-1

Appendix C – Event Log Export Format TPSys 3.3 Mycronic
General Format Information

This format does not follow the TPSys General ASCII Format Rules
document.
The main reason for this is that size is an issue.
 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:
<line_type>;<;-separated data fields>

The <line_type> identifies the type of event logged. The line type code is
typically one, two or three letters. A special type code is ’–’ (dash), this type
code indicates that this line is a continuation of last line.
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.
Two common examples:
%3B Semicolon(;)
%25 Percent sign(%)
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.)
Comment for Parser Implementers

A common idiom in the data format is that a list of data, for instance
components, is presented once and the lines below contains data fields
containing numbers used as index in this list.
This implies that the list format must be parsed from start to end of the data
and most format parsers will require a memory.
C-2 Rev. A 2016-04 4002720-EN – Software Manual

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.
Mount Information Lines

Lines that describe start and stop of assembly, and the events that occur during
component mounting and glue dispensing.
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.

Magazine Data Lines

Lines that describe magazine contents, pick problems, magazine insert/extract
and so on. The information in these lines is required to parse the Mount
information lines.
ML – Magazine load.
FI – Feeder information.
MI – Magazine inserted.
MR – Magazine removed.
External Event Lines

These lines log external events such as operator intervention and wait for
external conveyor system.
TST – TPSys started.

TSP – TPSys stopped.
BC – Board changed.
CUW – Conveyor unload wait.
CLW – Conveyor load wait.
FE – Feeder error.
FO – Feeder ok.
MTC – Manual tool changed.
MRS – Manual fiducial mark searched.
OW – Operator wait.
ULI – User logged in.
ULO – User logged out.
ASO – User access system on.
ASF – User access system off.
The following pages contain detailed format description for these lines.
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.
Mount Information Lines
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.
LU – Layout unloaded
Marks the event of a layout unload.
LU;<date-and-time>
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 skipped

There is one PBS – PCB skipped line for each skipped PCB in the layout. A
PCB is skipped if it is bad or not present. The PBS – PCB skipped lines are
repeated after each assembly start, in other words after an STA - Assembly
started line.
PBS;<PCB>
STA - Assembly started

Marks start of assembly. This line shows at what time the assembly started.
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>
<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.
STP - Assembly stopped

Marks stop of assembly. Assembly stop events occur when all components are
mounted or if the assembly is stopped because of some kind of error.
STP;<date-and-time>;<reason>
<reason> Reason for stop:
REDY – Assembly ready.
STOP – Stopped by operator.
NOCP – Components missing.
NOCG – Components missing and these missing components blocks
mount of components with higher group number.
MERR – Stopped by system error.
 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 – Clear assembly status

Clear status of current layout. The status for all mount positions is cleared and
the current layout is abandoned.
CLR;<date-and-time>
M2 – Mounted
Position mounted.
M2;<time>;<PCB>;<location>;<feeder-index>;<mount-head>
<time> Total time for operation in milliseconds.
<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>
<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 – Mount error

An error occurred during mount/dispense.
ME2;<date-and-time>;<error-type>;<feeder-index>;<mount-head>
<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.
TC2 – Tool changed

A tool change is made, either by the single mount head or by the HYDRA
head.
TC2;<time>;[<mount-head>;<old-tool>;<new-tool>;<tool-position>];...
<time> is the tool change time in milliseconds.

<old-tool> is the tool type name of the old tool or NOTOOL if no tool was
present
<new-tool> is the tool type name of the new tool or NOTOOL if no new
tool was picked up.
<tool-position> is the tool position where the new tool was picked up, that
is the HYDRA tool bank and group, or empty string if no tool was picked
or tool position is unknown or not applicable.
The ’<mount-head>;<old-tool>;<new-tool>;<tool-position>’ quadruple
can be repeated for mount heads that can change multiple tools in one
operation (the HYDRA).

RS – Fiducial mark searched

Fiducial mark search. Automatic fiducial mark search line.
RS;<time>
LRS – Local fiducial mark searched

Local site fiducial search. Shows time spent on local fiducial mark search.
LRS;<time>
MEV2 – Measure electric value

Measured a component electrically.
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.
<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.

Magazine Data Lines
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.
 Feeders not explicitly mentioned in the line are not affected.

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.
External Event Lines
TST – TPSys started

TPSys start event. Shows time when TPSys was started.
TST;<date-and-time>
TSP – TPSys stopped

TPSys stop event. Shows time when TPSys was shut down.
TSP;<date-and-time>

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 – Conveyor unload wait

This line exists if the machine has to wait for the external conveyor when
trying to unload a board to the external conveyor.
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.
CLW – Conveyor load wait

This line shows how long the machine has waited for the external conveyor
when loading a new board.
CLW;<time>;<result>
<time> Time in milliseconds. The amount of time that the machine has
waited for a new board.
<result> Result for end of wait:
OK – Board loaded.
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>
<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>
<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 – Manual tool changed

Manual tool change. This includes the time from the operator signal (popup)
until the operator press ok. This line always follows a TC2 – Tool changed
line. The TC2 – Tool changed line shows which tool changes have occurred.
MTC;<time>
<time> Total time for operation in milliseconds. The time it took for the
operator to change tools.
MRS – Manual fiducial mark searched

Manual adjustment of fiducial mark search. Will appear if the automatic
fiducial mark search fails or if the operator selects to adjust the fiducial marks
manually.
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 – User logged in

User logged in to the system.
ULI;<date-and-time>;<user>;<tty>
<user> Name of the user that logged in to the system.
<tty> The terminal (tty) that was used.

ULO – User logged out

User logged out from the system.
ULO;<date-and-time>;<user>;<tty>
<user> Name of the user that logged out of the system.
<tty> The terminal (tty) that was used.
ASO – User access system on

User access system was activated.
ASO;<date-and-time>
ASF – User access system off

User access system was deactivated.
ASF;<date-and-time>
Obsolete Mount Information Lines

The following lines are obsolete. In the export, they will follow directly after
the lines that have replaced them, as support to existing parsers.
 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.
A change from NOTOOL to NOTOOL may occur if TPSys starts in an

unknown state. Probably caused by a system crash.
TC;<time>;<from-tool>;<to-tool>
<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,

– D12, D13, D14, D23, D24, and D34.

<to-tool> Tool after change.
HTC – HYDRA tool changed

Obsolete. Replaced by the TC2 – Tool changed line.
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>...]
<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>
<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>
<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.
An error occurred during mount/dispense.

ME;<date-and-time>;<error-type>;<feeder-index>;<mount-tool>
<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 such as package not mountable and so on.
<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 event.
<mount-tool> Tool number. A numeric value where 0 represents Z and
1..8 represents a nozzle number for the HYDRA.
PCB – PCB contents

Obsolete. Replaced by the M2 – Mounted line.
Lists PCB location designators in line number order to make it easy to

associate line number with location designator. There exists one PCB line for
each PCB in the layout.
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 – Measure electric value

Obsolete. Replaced by the MEV2 – Measure electric value line.
Measured a component electrically.
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.

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.
<line> PCB Line No.
<feeder-index> Feeder Index. Corresponds to a feeder Id as specified in
an ML – Magazine load line (see below).
<Standard deviation> Obsolete.


Mycronic TPSys 3.3 Appendix D – Import/Export Data Formats
Appendix D – Import/Export Data Formats

This chapter specifies the general properties of formats used by TPSys for
import/export of data.
The description below is divided into the following sections:
General information
• Formats.
Mount data
• Layout Data Format.
• Panel Data Format.
• PCB Data Format.
• Fiducial Mark Data Format.
Package, Component and Glue dot data

• Package Data Format.
• Component Data Format.
• Glue Dot 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.
4002720-EN – Software Manual Rev. A 2016-04 D-1

Appendix D – Import/Export Data Formats TPSys 3.3 Mycronic
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.
Data Line Format

A line has the following format:
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.
 A line is optional if it is followed by the text (Optional) in the documentation.

An optional line can be left out.
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.
General Data Formats

The data part of a line contains items separated by space (spaces or tabs).
The types of data items are:
– 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 \".
D-2 Rev. A 2016-04 4002720-EN – Software Manual

– 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]
The data field magazine-name is optional and can be left out.
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
This line consists of a list of lead-No data items followed by a first-lead-offs

data item.
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.

Default units for numerical data

The numerical data type usually defines some physical property with the
following default units:
Angle – millidegrees. Positive angle is clockwise and zero degrees

straight up (or positive Y-direction in the machine). Angles are
always specified as integer values.
Force – mN (milliNewtons).
Length – um (micrometers). See The unit specification line below.
Speed – mm/s (millimeters per second).
Time – ms (milliseconds). In most data fields the actual resolution is
10 ms.
Torque – mNm (milliNewtonmeters).
The unit specification line

Some formats contain a unit specification line. This allows length to be
specified in something else than um (micrometers). Format:
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).
 The unit specification line is never exported.

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.
Special Enumerated Data Types

Some enumerated data types used in related documents.
Magazine type code

The magazine type can have the following values:
UNKNOWN
Magazine type is not known.
TAPE_MAG
Tape magazine.
VIB_MAG
Vibratory magazine.
TRAY_MAG
Matrix tray magazine.
GFI_MAG
GFI magazine.
Standard tool type code

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,
D12, D13, D14, D23, D24, and D34.
HYDRA Tool type code

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.
Note that the obsolete H00 tool is no longer supported.
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.
Layout Data Format

This section defines the ASCII format of the Layout data file used for
import/export of layout descriptions to/from TPSys internal databases.
Unless otherwise stated:
• The lines should appear in the order indicated below.

• There should be exactly one line of the specified type.
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
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.

x3 – Floating point numerical data. Optional X position of fiducial

mark 3.
y3 – Floating point numerical data. Optional Y position of fiducial
mark 3.
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
handled.
LARGE – For large boards. Parameters 92.0161 Large
handled.
SPECIAL – For special boards. Parameters 92.0181 Special
handled.
Auxiliary Layout Data

S7 global-grouping measure-board-level overlapping-warning
Layout grouping data and layout switches.
global-grouping – Boolean data. Corresponds to the Global grouping
field in the Layouts window.
measure-board-level – Enumerated data. Measure board level.
Corresponds to the Measure board level field in the Layouts window.
Value may be one of the following:
ALWAYS – (Always in the Layouts window).
NEW – (When layout is loaded in the Layouts window).
NEVER – (Only once in the Layouts window).
overlapping-warning – Boolean data. Corresponds to the
Overlapping board warning field in the Layouts window.

Layout Data Examples

Our example is a layout, named ’test4x2’, which contains only one PCB also
named ’test4x2’. After the PCB name line follows three different fiducial
mark lines, one for an unspecified machine and two where the machine is
specified.
S1 test4x2
S2
S3B test4x2
S4 2685 2270 239720 429748 240121 2366
S4M my12n123
S4 3192 2452 240634 430019 240677 2489
S4M my15n234
S4 2731 2291 239810 430012 239901 2421
S5 200000
S6 NORMAL
S7 N NEW Y
The example above shows a layout with the following properties:
Layout Data, Name .............................................................................. test4x2

Board Data, Name ............................................................................... test4x2
Board Data, Fiducial mark 1 ......................................... 2.685 mm/2.270 mm
Board Data, Fiducial mark 2 ................................. 239.720 mm/429.748 mm
Board Data, Fiducial mark 3 ..................................... 240.121 mm/2.366 mm
Name of one machine that the board has been located in .............. my12n123
Position of board location in that machine
Name of one machine that the board has been located in .............. my15n234
Position of board location in that machine
Conveyor width .................................................................................. 200 mm

Conveyor board type ........................................................................... Normal
Global grouping .......................................................................................... No
Measure board level ......................................... New (When layout is loaded)
Overlapping board warning ....................................................................... Yes

Panel Data Format

This document defines the ASCII format of the Panel data file used for
import/export of panels to/from TPSys internal databases.

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.
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.
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.
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.
PCB Fiducial Marks

P8 x1 y1 x2 y2 x3 y3 (Optional)
PCB fiducial marks. Corresponds to the PCB Data, Fiducial mark 1, 2
and 3 fields in the Panel PCBs window. There should be one P8 line for
each PCB of the same type as the last P7 line.
x3 – Floating point numerical data. X position of fiducial mark 3. If
the PCB has three fiducial marks, this field is mandatory. If the PCB
has two fiducial marks, this field should be omitted.
y3 – Floating point numerical data. Y position of fiducial mark 3. If
the PCB has three fiducial marks, this field is mandatory. If the PCB
has two fiducial marks, this field should be omitted.
Auxiliary Panel Data

P9 check-type use-panel-mark contrast-level contrast-ok area-size-x area-
size-y fid-dist-err brd-angle-err brd-on-panel (Optional)
Data for bad board handling for the panel, and special panel flags. See
page D-2 for information about units.
check-type – Enumerated data. Corresponds to the Check panel for
bad boards field in the Panel PCBs, Bad board test window. Value
may be one of the following:
OFF
MANUAL
AUTOMATIC
use-panel-mark – Boolean data. Corresponds to the Use bad board
mark on panel field in the Panel PCBs, Bad board test window.
contrast-level – Integer numerical data. Corresponds to the Contrast
level field in the Panel PCBs, Bad board test window.
contrast-ok – Boolean data. Corresponds to the Contrast means board
OK field in the Panel PCBs, Bad board test window.
area-size-x – Integer numerical data. Corresponds to the Bad board
area, X size field in the Panel PCBs, Bad board test window.

area-size-y – Integer numerical data. Corresponds to the Bad board

area, Y size field in the Panel PCBs, Bad board test window.
fid-dist-err – Floating point numerical data. Accepted fiducial mark
distance error. Corresponds to the Accepted fiducial mark distortion
error field in the Panels window.
brd-angle-err – Integer numerical data. Corresponds to the Accepted
board angle deformation field in the Panels window.
brd-on-panel – Boolean data. Corresponds to the Locate all boards
field in the Panels window.
Obsolete Lines
P4 xcoord ycoord
Obsolete. Ignored during import. Coordinate line for the lower left corner
of the panel.
P41 xcoord ycoord (Optional)
Obsolete. Ignored during import. Coordinate line for the upper right
corner of the panel.
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.

P54 preprocessing-type (Optional)

Type of preprocessing to be applied to image read by X-wagon camera.
preprocessing-type – Enumerated data. Value may be one of the
following:
– AUTO – No preprocessing is to be applied, image is to be read
directly.
CUSTOM – Use the preprocessing specified in the following P55
row.
P55 barcode-size elements-per-line element-type (Optional)
Parameters to be used during preprocessing of image read by
X-wagon camera when preprocessing-type is set to CUSTOM in row
P54.
barcode-size – Integer numerical data. The size of the barcode in
micrometers.
elements-per-line – Integer numerical data. The number of elements
in each line of the barcode.
element-type – Enumerated data. Corresponds to the Element type
field in the Board barcode editor. Value may be one of the following:
– SQUARE – Used when element type is Square.
– BLACK_ROUNDLET – Used when element type is Dark Circle.
– WHITE_ROUNDLET – Used when element type is Bright Circle.
Panel Data Examples

P1 demo4-2
P3 0 0 b1
P3 111989 201520 b2
P5 0 0
P6 9910 7160
P6B 16750 17000
P7 demo4
P8 16747 16955 95337 95885
P8 16588 105765 95191 184672
P9 MANUAL N 50 Y 2000 2000 0.125 500 Y
The example above shows a PCB with the following properties:
Panel Data–Name .............................................................................. demo4-2

First fiducial mark ...................................................................... b1 at 0/0 mm
Second fiducial mark ........................................... b2 at 111.989/201.520 mm
Glue tool test position ..................................................................... at 0/0 mm
Mount tool test position .................................................... at 9.910/7.160 mm
Bad board mark position ............................................... at 16.750/17.000 mm

PCB Data, Name ................................................................................. demo4
Two PCBs with their coordinates (the P8 lines).
Check panel for bad boards ................................................................. Manual
Use bad board mark on panel ..................................................................... No
Contrast level .............................................................................................. 50

Contrast means board OK ......................................................................... Yes

Bad board area, X size ............................................................................ 2 mm
Bad board area, Y size ............................................................................ 2 mm
Accepted fiducial mark distortion error ............................................. 0.125%
Accepted board angle deformation ................................................ 0.5 degrees

Locate all boards ........................................................................................ Yes
PCB Data Format

This section defines the ASCII format of the PCB data file used for
import/export of PCBs to/from TPSys internal databases.

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.
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
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.
Mount tool board level test position. Corresponds to the Mount tool test
position field in the PCBs window.
Bad-board test position. Corresponds to the Bad board mark position field
in the PCBs window.

Barcode Positions
F51 xcoord ycoord
Barcode position centre point.
xcoord – Centre point for PCB barcode position.
ycoord – Centre point for PCB barcode position.
Mount Positions (Items)

F8 xcoord ycoord angle group mount-skip dispense-skip component
(Optional)
Mount position line. There may be any number of F8 lines (including
zero). See page D-2 for information about units.
xcoord – Floating point numerical data. X position of component.
Corresponds to the pos. field in the PCB Items window.
ycoord – Floating point numerical data. Y position of component.
Corresponds to the pos. field in the PCB Items window.
angle – Integer numerical data. Corresponds to the Angle field in the
PCB Items window. Zero degrees is in positive Y direction and
positive angles are clockwise.
group – Integer numerical data. Corresponds to the Group field in the
PCB Items window. A number between 0 and 255.
mount-skip – Boolean data. Corresponds to the Mount field in the
PCB Items window. If ’Y’, the component is NOT mounted.
dispense-skip – Boolean data. Corresponds to the Glue field in the
PCB Items window. If ’Y’, the component is NOT dispensed.
component – Text data. Corresponds to the Component field in the
PCB Items window. Leading and trailing spaces are ignored and the
component name is truncated to 35 characters.
F81 z-level (Optional)
Mount position z-level. There can only be one F81 line following a F8
line. The F81 line defines the expected z-level at the mount position
defined by the preceding F8 line.
z-level – Expected z-level at mount position. The z-level must be in
the range [0...15]mm.
F82 enable priority component (Optional)
Alternative components. There can be zero, one or many F82 lines
following a F8 line. The F82 line defines alternative components for the
mount position defined by the preceding F8 line.
enabled – Boolean Y or N. Enable or disable the use of this alternative
component.
priority – Integer. Lower value has higher priority.
component – Text data. Alternative components at mount position.
Leading and trailing spaces are skipped and the component name is

F82E expire (Optional)

Alternative components expire time. There can be zero or one F82E line
following a F82 line. The F82E line defines the last valid time or day or
use, in the local time zone, for this alternative components defined by the
preceding F82 line.
expiration-time – Date Time. YYYY-MM-DD HH:MM:SS Optional.
HH:MM:SS is optional. Missing data is the same as 23:59:59.
If F82E line is missing, alternative components is valid forever.
Default is forever.
F82C comment (Optional)
Alternative components comment. There can be zero or one F82C line
following a F82 line. The F82C line defines the comment for the
alternative components defined by the preceding F82 line.
comment – Text data. Leading and trailing spaces are skipped and the
comment is truncated to 50 characters. Optional.
Mount Position Location

F9 location (Optional)
Comment line for the mount position specified in the last F8 line. If
present, the F9 line follows the F8 line. If there is no F9 line during
import, a location will be generated by the system.
location – Text data. Corresponds to the Location field in the PCB
Items window. Leading and trailing spaces are ignored and the string
is truncated to 35 characters. The location must be unique for each
mount position. If the location is non-unique, it will be made unique
during import.
Local Fiducial Mark

F10 xcoord ycoord name (Optional)
Local fiducial mark for the mount position specified in the last F8 line.
Corresponds to the Local fiducial marks fields in the PCB Items window.
There may be between zero and seven F10 lines following an F9 line or,
if the F9 line is absent, an F8 line.
xcoord – Floating point numerical data. X coordinate of local fiducial
mark.
ycoord – Floating point numerical data. Y coordinate of local fiducial
mark.
name – Text data. Name of fiducial mark. Leading and trailing spaces
are ignored and the name is truncated to 10 characters.

Mount Position Flags

F11 flags-string (Optional)
Special flags line for the mount position specified in the last F8 line.
flags-string – A set of flag keywords that are set for mount position
specified in the last F8 line. If a keyword is present in the line, the
corresponding field in the PCB Items window is set to Yes. If a
keyword is not found in the line, the corresponding field in the PCB
Items window is set to No. Valid keywords are:
TBZD – Turn before Z down flag. Corresponds to the Turn
before Z down field in the PCB Items window.
SMEV – Save electric value in event log flag. Corresponds to
the Save electric value field in the PCB Items window.
NOHYDRA – Forbid use of HYDRA. Corresponds to the
Only Z field in the PCB Items window.
PREMOUNT – Component in position is mounted.
Corresponds to the Premounted field in the PCB Items
window.
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
Obsolete. Ignored during import. Coordinate line for the lower left corner
of the PCB.
Obsolete. Ignored during import. Coordinate line for the upper right
corner of the PCB.

F52 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 F53
row.
F53 frontlight ambient-red ambient-blue (Optional)
X-wagon camera illumination level to use when illumination-type is set to
CUSTOM in row F52
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.
F54 preprocessing-type (Optional)
Type of preprocessing to be applied to image read by X-wagon camera.
preprocessing-type – Enumerated data. Value may be one of the
following:
– AUTO – No preprocessing is to be applied, image is to be read
directly.
CUSTOM – Use the preprocessing specified in the following F55
row.
F55 barcode-size elements-per-line element-type (Optional)
Parameters to be used during preprocessing of image read by
X-wagon camera when preprocessing-type is set to CUSTOM in row
F54.
barcode-size – Integer numerical data. The size of the barcode in
micrometers.
elements-per-line – Integer numerical data. The number of elements
in each line of the barcode.
element-type – Enumerated data. Corresponds to the Element type
field in the Board barcode editor. Value may be one of the following:
– SQUARE – Used when element type is Square.
– BLACK_ROUNDLET – Used when element type is Dark Circle.
– WHITE_ROUNDLET – Used when element type is Bright Circle.

PCB Data Examples

F1 tsoplay
F3 0 0 square
F3 205860 -103630 square
F5 0 0
F6 3930 100
F7 0 0
F8 145848 -8930 0 0 Y N tsoptest
F9 tsop-1
F8 145932 -21590 90000 0 N N tsoptest
F9 tsop-2
F11 TBZD SMEV
F12 0.125 500 15000
The example above shows a PCB with the following properties:
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
Mount position flags

Turn before Z down ................................................................................... Yes
Save electric value ..................................................................................... Yes
Only Z ......................................................................................................... No
Premounted ................................................................................................. No
Auxiliary data
Accepted fiducial mark distortion error ............................................. 0.125%
Accepted board angle deformation ................................................ 0.5 degrees
Highest undefined obstacle ................................................................... 15 mm

Fiducial Mark Data Format

This section defines the ASCII format of the fiducial mark data file used for
import/export of fiducial mark descriptions to/from TPSys internal databases.

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

Circular Fiducial Mark Data

R13-1 nom-diameter min-diameter max-diameter
Line for defining a circular fiducial mark. Corresponds to the Diameter
field in the Fiducial Marks window.
nom-diameter – Integer numerical data. The diameter of the circular
fiducial mark in micrometers.
min-diameter – Integer numerical data. The minimum allowed
diameter of the circular fiducial mark in micrometers.
max-diameter – Integer numerical data. The maximum allowed
diameter of the circular fiducial mark in micrometers.
Rectangular Fiducial Mark Data

R13-2 nom-width min-width max-width nom-length min-length max-length
Line for defining a rectangular fiducial mark. Corresponds to the Width
and Length fields in the Fiducial Marks window.
nom-width – Integer numerical data. The width of the fiducial mark
in micrometers.
min-width – Integer numerical data. The minimum allowed width of
the fiducial mark in micrometers.
max-width – Integer numerical data. The maximum allowed width of
nom-length – Integer numerical data. The length of the fiducial mark
in micrometers.
min-length – Integer numerical data. The minimum allowed length of
max-length – Integer numerical data. The maximum allowed length
of the fiducial mark in micrometers.
Triangular Fiducial Mark Data

Line for defining a triangular fiducial mark. Corresponds to the Width and
Length fields in the Fiducial Marks window.
in micrometers.
in micrometers.

Cross Fiducial Mark Data

nom-thickness min-thickness max-thickness
Line for defining a cross fiducial mark. Corresponds to the Width, Length
and Thickness fields in the Fiducial Marks window.
in micrometers.
in micrometers.
nom-thickness – Integer numerical data. The thickness of the cross
arms of the fiducial mark in micrometers.
min-thickness – Integer numerical data. The minimum allowed cross
arm thickness of the fiducial mark in micrometers.
max-thickness – Integer numerical data. The maximum allowed cross
arm thickness of the fiducial mark in micrometers.

Butterfly Fiducial Mark Data

Line for defining a butterfly fiducial mark. Corresponds to the Width and
Length fields in the Fiducial Marks window.
in micrometers.
in micrometers.
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.
Search Area and Search Method

R15 search-area-width search-area-length
This line specifies the size of the search area.
search-area-width – Integer numerical data. The width of the search
area in micrometers. Corresponds to the Search area width field in the
Fiducial Marks window.
search-area-length – Integer numerical data. The length of the search
area in micrometers. Corresponds to the Search area length field in
the Fiducial Marks window.
R16 search-method
This line specifies search algorithm data for non-generic fiducial marks.
search-method – Enumerated data. The algorithm to use when
searching for the fiducial mark. Corresponds to the Coarse search
method field in the Fiducial Marks window. Value may be one of the
following:
AUTO
EDGES
CONTRAST

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’.
Illumination Type and Illumination Level

R18 illumination-type
This line specifies the X-wagon camera illumination type for all type of
fiducial marks.
Illumination-type- Enumerated data. Value may be one of the
following:
Auto - Use a standard illumination level as specified in parameters
46:0031, 46:0032, 46:0033
Custom - Use the illumination level specified in the following R19
row.
R19 frontlight ambient-red ambient-blue
This line specifies the X-wagon camera illumination level when this mark
is specified with Custom usage in row R18.
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.
Generic Fiducial Mark Teach Status

R22 taught
This line specifies if a generic fiducial mark is taught or not.
taught – Boolean data. Corresponds to the Mark taught field in the
Fiducial Marks window. Defines if a generic fiducial mark is taught
or not.
Generic Fiducial Mark Data

R23-1 xcoord ycoord
This line specifies data for a generic fiducial mark. Defines an edge point
along the upper edge of the fiducial. There may be several R23-1 lines for
a generic fiducial mark.
xcoord – Integer numerical data. The x coordinate of an edge point
along the upper edge of the fiducial mark in micrometers.
ycoord – Integer numerical data. The y coordinate of an edge point
along the upper edge of the fiducial mark in micrometers.

R23-2 xcoord ycoord

along the lower edge of the fiducial. There may be several R23-2 lines for
along the lower edge of the fiducial mark in micrometers.
along the lower edge of the fiducial mark in micrometers.
R23-3 xcoord ycoord
along the left edge of the fiducial. There may be several R23-3 lines for a
generic fiducial mark.
along the left edge of the fiducial mark in micrometers.
along the left edge of the fiducial mark in micrometers.
R23-4 xcoord ycoord
along the right edge of the fiducial. There may be several R23-4 lines for
along the right edge of the fiducial mark in micrometers.
along the right edge of the fiducial mark in micrometers.
R24 taught
This line specifies if a generic fiducial mark is taught or not.
taught – Boolean data. Corresponds to the Mark taught field in the
Fiducial Marks window. Defines if a generic fiducial mark is taught
or not.
R25 xstartcoord ystartcoord xendcoord yendcoord
This line specifies data for a oddshape fiducial mark. Defines a line of the
fiducial. There may be several R25 lines for an oddshape fiducial mark.
xstartcoord – Integer numerical data. The x coordinate of a start point
of the line defining the fiducial mark in micrometers.
ystartcoord – Integer numerical data. The y coordinate of a start point
xendcoord – Integer numerical data. The x coordinate of an end point
yendcoord – Integer numerical data. The y coordinate of an end point

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
R04 x-gradient-M1 x-gradient-P1 y-gradient-M1 y-gradient-P1
R05 xcoord ycoord contrast edge-mean edge-quality background-mean
background-variation x-correction y-correction (Optional)


R09 diameter diameter-tolerance circle-contrast (Optional)
Obsolete but supported for import. Line that defines the parameters for a
fiducial mark of type 'Circle'.
diameter – Diameter of the fiducial mark in micrometers.
diameter-tolerance – Tolerance of the diameter expressed in percent.
circle-contrast – The minimum contrast required between the fiducial
mark and the background.

Fiducial Mark Data Examples
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:
Name ................................................................................................... AX123

Comment ................................................................................... For AX board
Type ...................................................................................................... Circle
Diameter ......................................................................... 1.5 mm ± 0.075 mm
Color ..................................................................................................... Bright
Search area width ................................................................................... 5 mm

Search area length .................................................................................. 5 mm
Coarse search method ............................................................................. Auto
Contrast offset ......................................................................................... Auto
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 ..................................................................................................... FS456

Type .................................................................................................. Butterfly
Width .................................................................................. 3 mm ± 0.150 mm
Length ................................................................................ 3 mm ± 0.150 mm
Color ........................................................................................................ Dark
Search area width .................................................................................... 6 mm

Search area length ................................................................................... 6 mm
Coarse search method .........................................................................Contrast
Contrast offset .............................................................................................. 44

Package Data Format

This section defines the ASCII format of the Package data file used for
import/export of package data to/from TPSys internal databases.

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
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.

body-width – Integer numerical data. Corresponds to the Body width

overall-length – Integer numerical data. Corresponds to the Overall
length field in the Packages window. If body-length is greater than
overall-length, overall-length is set to body-length.
overall-width – Integer numerical data. Corresponds to the Overall
width field in the Packages window. If body-width is less than
overall-width, overall-width is set to body-width.
nom-height – Integer numerical data. Corresponds to the Overall
height field in the Packages window.
max-height – Integer numerical data. Corresponds to the Overall
height field in the Packages window. If nom-height is greater than
max-height, max-height is set to nom-height.
min-height – Integer numerical data. Corresponds to the Overall
height field in the Packages window. If nom-height is less than min-
height, min-height is set to nom-height.
P011 x-offset y-offset type (Optional)
The x-offset y-offset type specifies toggle points. For an Odd shape
package, the package toggle points are in a separate toggle point table.
Toggle point type – custom and mandatory.
x-offset y-offset – X and Y coordinates of one toggle point.
P11 17745 16893 CUSTOM
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
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).

tool-to-top-offset – Integer numerical data. Corresponds to the Tool to

top offset field in the Packages window. Default value is 0. Optional.
hydra-fine-pitch – Boolean data. Corresponds to the HYDRA fine
pitch field in the Packages window. If ’TRUE’, the package will
require the machine to have the option HYDRA fine pitch to mount
with HYDRA. If ’FALSE’, the package will be mounted with
HYDRA regardless of the option HYDRA fine pitch. Optional.
pick-speed – Integer numerical data. Corresponds to the Motion
sequence when picking, Downwards speed field in the Packages
window. Minimum value 10 mm/s. Maximum value 120 mm/s.
Auto = 0. Optional.
place-speed – Integer numerical data. Corresponds to the Motion
sequence when placing, Downwards speed field in the Packages
Auto = 0. Optional.
P021 alternate-mount-tool (Optional)
Alternative mount tool line. One P021 line for every alternative mount
tool for the package. See page D-5 for further information.
alternate-mount-tool – Enumerated data. Tool type code.
Corresponds to all entries except the first entry in the Mount tools
field in the Packages window. See also P022 above.
Care must be taken to specify a valid mount tool even though the data
format allows any tool.
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.

htheta-acc – Enumerated data. Corresponds to the Acceleration

codes, HYDRA Theta field in the Packages window. Default value if
not supplied is same as theta-acc.
zup-speed – Integer numerical data. Corresponds to the Motion
sequence when placing, Upwards speed field in the Packages
Default value if not supplied is 100 mm/s.
zup-dist – Integer numerical data. Corresponds to the Motion
sequence when placing, Upwards distance field in the Packages
window. After this distance has been passed, the movement continues
upwards to safe position using ’ACC_HIGHEST’. Default value is 0.
tape-acc – Enumerated data. Corresponds to the Acceleration codes,
Tape field in the Packages window. Default value is ’ACC_HIGH’.
Optional.
pick-in-centre – Boolean data. Corresponds to the Pick position
feedback field in the Packages window. ’TRUE’ if the pick position
is regulated, ’FALSE’ if it is not regulated. Default value is ’TRUE’.
Optional.
HYDRA Data and Presentation Angle Data

P032-1 presentation-angle (Optional)
Optical centering presentation angle line for both the standard mount head
and the HYDRA head. Corresponds to the Presentation angle field in the
Packages, Centering Phases window.
presentation-angle – Integer numerical data, or the string ’AUTO’.
The value represents the angle between zero degrees and the long axis
of the component.
P032-2 HYDRA-tool (Optional)
HYDRA mount tool line. Corresponds to the HYDRA tools field in the
Packages window. Any number of P032-2 lines may be specified for a
package. Zero P032-2 lines means that the package is not HYDRA
mountable.
HYDRA-tool – HYDRA tool type data. See page D-5 for further
information.
Lead toggling Data

P04 lead-No. first-lead-offset (Optional)
Lead data for the Lead toggling function.
lead-No. – A space-separated list of lead numbers. Corresponds to the
Lead toggling field in the Packages window. A maximum of 8 leads
can be specified. Duplicated lead numbers are removed from the list.
first-lead-offset – Lead number of first lead in first lead group (Lead
groups specified below). Corresponds to the Lead number of upper
lead in left group field in the Packages, Lead Groups window. Note
that if the Lead number of upper lead in left group field value is ’1’,
the first-lead-offset exported value is ’0’.
First-lead-offset is always the last data in the P04 line.

Lead Groups Data

P051 lead-type leads x-offset y-offset angle [lead-orientation] (Optional)
Lead group position line. There should be one P051, one P054 and one
P055 line for each lead group. Any number of lead groups may be
specified. See page D-2 for further information.
lead-type – Enumerated data. Corresponds to the Lead type field in
the Packages window. Value may be one of the following:
J_LEAD – Corresponds to the J-BEND value in the Packages,
Lead Groups window.
FLAT – Leads with an approximately rectangular shape
where the whole lead is presented at the camera focal plane.
Corresponds to the RECTANGLE value in the Packages, Lead
Groups window.
GULLWING – Typical lead for SO-type packages.
BGA – Corresponds to the BALL on Ceramic value in the
Packages, Lead Groups window.
BGAB – Corresponds to the BALL value in the Packages,
Lead Groups window.
CHIP – Chip packages mounted with HYDRA, typically
0201-1210.
CGA – Corresponds to the COLUMN value in the Packages,
Lead Groups window.
OUTLINE - This value is used if the package type is Outline.
LEADLESS – Obsolete but supported for import.
PIN – Obsolete but supported for import.
FLIP – Obsolete but supported for import.
SMALL_CHIP – Obsolete but supported for import.
leads – Integer numerical data. Represents the number of leads in this
lead group. If the lead type is OUTLINE, this value is always zero.
x-offset – Integer numerical data. Represents the X offset from
package mid point to the first lead in the group. If the lead type is
OUTLINE, this value is always zero.
y-offset – Integer numerical data. Represents the Y offset from
package mid point to the first lead in the group. If the lead type is
OUTLINE, this value is always zero.
angle – Integer numerical data. Represents angle of the lead group.
lead-orientation – Enumerated data. Represents the orientation of
leads in the group. Value may be one of the following:
NORMAL – Leads are directed in the traditional sense.
REVERSED – Lead group is reflected so that angles are
increased by 180 degrees whilst lead numbering is
unchanged.

Lead Dimensions Data

P054 lead-color search-contrast min-correlation (Optional)
Lead search properties line. There should be one P051, one P054 and one
P055 line for each lead group. Any number of lead groups may be
specified.
lead-color – Enumerated data. Represents the polarity of illuminated
leads in the group. Corresponds to the Lead color field in the
Packages, Lead Groups window. Value may be one of the following:
BRIGHT – Leads are seen as bright against a darker
background.
DARK – Leads are seen as dark against a brighter
background.
search-contrast – Either the string ’AUTO’ or integer numerical data
between 0 and 255 representing the required contrast of the lead group
features. Corresponds to the Contrast offset field in the Packages,
Lead Groups window.
min-correlation – Either the string ’AUTO’ or integer numerical data
between 0 and 100 representing the required correlation of the lead
group features. Corresponds to the Min correlation field in the
Packages, Lead Groups window.
P055 nom-len max-len min-len nom-width max-width min-width pitch max-x-
error max-y-error max-length-error (Optional)
Lead dimensions line. Replaces P052. There should be one P051, one
P054 and one P055 line for each lead group. Any number of lead groups
may be specified. See page D-2 for information about units.
nom-len – Integer numerical data. Represents nominal lead length.
Corresponds to the Lead length field in the Packages, Lead Groups
window.
max-len – Integer numerical data. Represents maximum lead length.
If nom-len is greater than max-len, max-len is set to the same value as
nom-len. Corresponds to the Lead length field in the Packages, Lead
Groups window.
min-len – Integer numerical data. Represents minimum lead length. If
nom-len is less than min-len, min-len is set to the same value as nom-
len. Corresponds to the Lead length field in the Packages, Lead
Groups window.
nom-width – Integer numerical data. Represents nominal lead width.
Corresponds to the Lead width field in the Packages, Lead Groups
window.
max-width – Integer numerical data. Represents maximum lead.
window. If nom-width is greater than max-width, max-width is set to
the same value as nom-width.
min-width – Integer numerical data. Represents minimum lead width.
window. If nom-width is less than min-width, min-width is set to the
same value as nom-width.

pitch – Integer numerical data. Represents lead c-c distance.

Corresponds to the Lead pitch field in the Packages, Lead Groups
window.
max-x-error – Integer numerical data. Corresponds to the Max cross-
wise deviation field in the Packages, Lead Groups window.
max-y-error – Integer numerical data. Corresponds to the Max length-
wise deviation field in the Packages, Lead Groups window.
max-length-error – Integer numerical data. Represents max deviation
between highest and lowest lead. Corresponds to the Max length-wise
deformation field in the Packages, Lead Groups window.
P056 point1X point1Y point2X point2Y correlation (Optional)
Definition of one line segment in the Odd shape package. Any number of
P056 lines is allowed.
point1X, point1Y – the first point of the line segment.
point2X, point2Y – the second point of the line segment.
correlation – correlation of the line, used by Odd shape algorithms.
P056 – 1884 7458 -1884 2281 50
General Centering Data

P061 method (Optional)
Centering method line. There should be one P061 line for each centering
phase.
Between 0 and 12 centering phases may be specified.
Only the last centering phase in a list of centering phases may be
OPTICAL.
method – Enumerated data. Represents what centering method to use.
MECHANICAL – Mechanical centering. A P061 line for
mechanical centering should be immediately followed by
lines P062-M and P063.
OPTICAL – Optical centering. A P061 line for optical
centering should be immediately followed by lines P064-O,
P064-O1, P064-O2, P064-O3 and P064-O4.
PUSH – Push centering. Obsolete but supported for import.
PUSH centering is always converted to MECHANICAL
centering. Don't use this value.

Dip Centering Data

P062-D angle [cavity name]
Dip centering phase data. There can only be one P062-D line per package,
because there can only be one dip centering phase. The P062-D line is
only present if there is a dip centering phase defined for the package.
angle – Angle of component when dipping.
cavity name – Text data. Name of cavity.
P062-M angle level position force (Optional)
Mechanical centering phase data.
angle – Integer numerical data. Component angle for this centering
phase. Corresponds to the Angle field in the Packages, Centering
Phases window. See page D-2 for further information.
level – Integer numerical data. Value must be between 0 and 11.
Centering level number to use. Corresponds to the Level field in the
position – Enumerated data. Represents centering device position
code. Corresponds to the Position field in the Packages, Centering
Phases window. Value may be one of the following:
POS_UPPER
POS_LOWER
POS_MIDDLE
POS_1QUARTERB
force – Enumerated data. Represents the force applied to the jaws
when centering. Corresponds to the Force field in the Packages,
Centering Phases window. Value may be one of the following:
HIGH_FORCE
MIDDLE_FORCE
LOW_FORCE
NO_FORCE
P063 nom-size max-size min-size mechanical (Optional)
Mechanical centering phase data. Follows P062-M. If P062-M is omitted
P063 shouldn't be present either.
nom-size – Integer numerical data. Corresponds to the Dimension
field in the Packages, Centering Phases window. See page D-2 for
further information.
max-size – Integer numerical data. Corresponds to the max field in the
Packages, Centering Phases window. If nom-size is greater than
max-size, max-size is set to the same value as nom-size.
min-size – Integer numerical data. Corresponds to the min field in the
Packages, Centering Phases window. If nom-size is less than min-
size, min-size is set to the same value as nom-size.

mechanical – Boolean data, ’TRUE’ or ’FALSE’. Corresponds to the

Verify mechanical field in the Packages, Centering Phases window.
If ’TRUE’, mechanical verification will be performed in this
centering phase.
Optical Centering Data

P064-O mount-head (Optional)
Optical centering phase data. There should be one P064-O line for each of
an OPTICAL centering phase's mount heads.
mount-head – Enumerated data. Represents a mount head for which
the centering phase is valid. Corresponds to the Mount heads field in
the Packages, Centering Phases window. Value may be one of the
following:
Z_TOOL – Indicates that the centering phase is valid for the
standard mount head.
HYDRA_TOOL – Indicates that the centering phase is valid
for the HYDRA mount head.
P064-O2 DVC-illum [DVC-dark-field] [DVC-ambient-light] [DVC-front-
light] (Optional)
Optical centering phase data. Follows P064-O1. If P064-O is omitted
P064-O2 should not be present either.
DVC-illum – Enumerated data. Represents whether the illumination
settings used by the DVC are those specified by the user or are
automatically calculated by TPSys. Corresponds to the DVC, Z
illumination field in the Packages, Centering Phases window. Value
AUTO – Allow TPSys to calculate illumination settings.
CUSTOM – Use illumination settings specified by the user.
DVC-dark-field – Integer numerical data. Value must be between 0
and 100. Corresponds to the DVC, Dark field field in the Packages,
Centering Phases window.
DVC-ambient-light – Integer numerical data. Value must be between
0 and 100. Corresponds to the DVC, Ambient light field in the
DVC-front-light – Integer numerical data. Value must be between 0
and 100. Corresponds to the DVC, Front light field in the Packages,
Centering Phases window.
P064-O3 LSC-illum [LSC-ambient-outer-light] [LSC-ambient-inner-light]
(Optional)
Obsolete ignored during import.
P064-O4 HYDRA-LSC-illum (Optional)
Obsolete ignored during import.

P064-O5 illum-LSC-Z illum-LSC-HYDRA [LSC-dark-field] [LSC-ambient-

light] [LSC-front-light] (Optional)
Illum-LSC-Z
Illum-LSC-Z – Enumerated data. Represents whether the
illumination settings used by the LSC are those specified by
the user or are automatically calculated by TPSys.
Corresponds to the Linescan Z illumination field in the
Illum-LSC-HYDRA
Illum-LSC-HYDRA – Enumerated data. Represents whether
the illumination settings used by the LSC with the HYDRA
are those specified by the user or are automatically calculated
by TPSys. Corresponds to the Linescan, HYDRA illumination
field in the Packages, Centering Phases window.
AUTO – Allow TPSys to calculate illumination setting.
LSC-dark-field
LSC-dark-field – Integer numerical data. Value must be
between 0 and 100. Corresponds to the Linescan, Dark field
LSC-ambient-light
LSC-ambient-light – Integer numerical data. Value must be
between 0 and 100. Corresponds to the Linescan, Ambient
light field in the Packages, Centering Phases window.
LSC-front-light
LSC-front-light – Integer numerical data. Value must be
between 0 and 100. Corresponds to the Linescan, Front light
P07 best-fit [contrast-parameters]
Optical centering data. Previous versions of P07 may contain additional
noise and contrast parameters field that are ignored during import.
best-fit – Boolean data, ’TRUE’ or ’FALSE’. Use best-fit algorithm
flag. If ’TRUE’, the best-fit algorithm will be applied. Corresponds to
the Use best fit field in the Packages, Lead Groups window.
contrast-parameters. Ignored if imported.

P071 camera (Optional)

Centering camera specification line. Any number of P071 lines is
allowed. The obsolete values are ignored without messages by import.
camera – Text data representing type or name of a centering camera
that may be used to center the package. Corresponds to the Usable
camera types field in the Packages, Centering Phases window. See
also P073.The value may be one of the following:
standard
Linescan
LOW (Obsolete)
high res.
HIGH (Obsolete)
P072 banned-camera (Optional)
Banned centering camera specification line. Any number of P072
lines is allowed. The obsolete values are ignored without messages by
import.
banned-camera – Text data. Corresponds to the Unusable cameras
field in the Packages, Centering Phases window. The value may be
one of the following:
SVC – Standard Vision Camera.
HRC – High Resolution Camera.
LSCFRONT – Linescan camera with front light and ambient
light (Obsolete).
LSC – Linescan camera with front light and dark field light
and ambient light.
OVC1 – Extended Vision Camera 1. (Obsolete)
EVC1 – Extended Vision Camera 1.

P073 HYDRA-camera (Optional)

HYDRA centering camera specification line. Any number of P073
lines is allowed. The obsolete values are ignored without messages by
import.
HYDRA-camera – Text data representing the name of a HYDRA
centering camera that may be used to center the package. Corresponds
to the Usable camera types field in the Packages, Centering Phases
window. See also line P071.The value may be one of the following:
HYDRA – HYDRA camera 8.
Linescan – Linescan camera with front light and dark field
light and ambient light.
Index Mark Type

P08 index-type (Optional)
Index mark type line.
index-type – Enumerated data. Represents type of index mark. Value
NONE
CORNER
NOCORNER
MARK
CAVITY
Optical Centering Data

P083 location-algorithm (Optional)
Optical centering data. Algorithm used to locate a package. If P08 is
omitted, P083 must be omitted.
location-algorithm – Enumerated data. The type of algorithm used to
roughly locate package position offset and angle. Corresponds to the
Coarse search method field in the Packages, Centering Phases
window. Value may be one of the following:
STANDARD – Position calculated matching the most
external found leads with the model description.
ASSUME_CENTERED – Package is assumed to be centered
at the tool rotation center and package leads are directly
searched.
OUTLINE – Position calculated by detecting a rectangular
outline of a package.
MULTIPLE_LEADS – Obsolete but supported for import.
Information on the external leads’ neighbors are used for
matching the found leads with the model.

Index Mark Data

P084 pos-x pos-y size min-correlation (Optional)
Index mark data line. If P08 is omitted, P084 must be omitted.
pos-x – Integer numerical data. X offset from the center of the
component to the center of the index search area in micrometers.
Corresponds to the Index area offset field in the Packages, Index
Mark window.
pos-y – Integer numerical data. Y offset from the center of the
Corresponds to the Index area offset field in the Packages, Index
Mark window.
size – Integer numerical data. Value must be between 0 and 30000.
Size of the index search area in micrometers. Corresponds to the Index
area size field in the Packages, Index Mark window.
min-correlation – Integer numerical data. Value must be between 0
and 100. Required contrast in percent when searching for index mark.
Corresponds to the Min correlation field in the Packages, Index Mark
window.
Glue Dot Data

P09 x-offset y-offset type (Optional)
Glue dot line. There should be one P09 line for each glue dot. Zero to 8
glue dot lines may be specified.
x-offset – Integer numerical data. X offset from the center of the
component to the glue dot in micrometers. Corresponds to the
Position field in the Packages, Glue Dots window.
y-offset – Integer numerical data. Y offset from the center of the
component to the glue dot in micrometers. Corresponds to the
Position field in the Packages, Glue Dots window.
type – Text data. Corresponds to the Type field in the Packages, Glue
Dots window. Leading and trailing spaces are ignored and the name
is truncated to 15 characters.

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
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.

P052 nom-len max-len min-len nom-width max-width min-width pitch max-x-

error max-y-error max-length-error (Optional)
Obsolete but supported for import, replaced by P055. Lead
dimensions line.
nom-len – Integer numerical data. Represents nominal lead length.
max-len – Integer numerical data. Represents maximum lead length.
If nom-len is greater than max-len, max-len is set to the same value as
nom-len.
min-len – Integer numerical data. Represents minimum lead length. If
nom-len is less than min-len, min-len is set to the same value as nom-
len.
nom-width – Integer numerical data. Represents nominal lead width.
max-width – Integer numerical data. Represents maximum lead
width. If nom-width is greater than max-width, max-width is set to the
same value as nom-width.
min-width – Integer numerical data. Represents minimum lead width.
If nom-width is less than min-width, min-width is set to the same
value as nom-width.
pitch – Integer numerical data. Represents lead c-c distance.
max-x-error – Integer numerical data. Represents length-wise
deviation.
max-y-error – Integer numerical data. Represents cross-wise
deviation.
max-length-error – Integer numerical data. Represents maximum
deviation between highest and lowest lead.
P062-O light-standard [light-DVC] (Optional)
Obsolete but supported for import. Replaced by P064-O1.
light-standard – Integer numerical data. Percent value for light level
to use with standard illumination. Value must be between 0 and 100.
If light-standard is outside the specified limits, the value is changed to
the nearest limit.
light-DVC – Integer numerical data. Optional value. Percent value for
light level to use with DVC illumination. Value must be between 0
and 1000. If light-standard is outside the specified limits, the value is
changed to the nearest limit.
P062-O3 illumination-pattern relative-dark-field-illum relative-ambient-
light-illum relative-front-light-illum(Optional)
illumination-pattern – Enumerated data. The type of illumination to
be applied to the package.
relative-dark-field – Integer numerical data between 0 and 100.
relative-ambient-light – Integer numerical data between 0 and 100.
relative-front-light – Integer numerical data between 0 and 100.

P062-O4 light-LSC illumination-pattern-LSC relative-ambient-light-illum-

LSC relative-front-light-illum-LSC (Optional)
light-LSC – Integer numerical data. Optional value. Percent value for
light level to use with LSC illumination. Value must be between 0 and
100.
illumination-pattern-LSC – Enumerated data.
relative-ambient-light – Integer numerical data between 0 and 100.
relative-front-light – Integer numerical data between 0 and 100.
P074 illumination-pattern-LSC-HYDRA (Optional)
Obsolete but supported for import. Optical centering phase data for the
Linescan camera with the HYDRA tool.
illumination-pattern-LSC-HYDRA – Enumerated data. The type of
illumination to be applied to the package. Value may be one of the
following: Full, Front or Ambient.
P075 light-level-HYDRA (Optional)
Obsolete but supported for import. Optical centering phase data for the
HYDRA camera.
light-level-HYDRA – Enumerated data. The HYDRA camera
intensity level to be applied to the package. Value may be one of the
following: Min, Max.
P081 pos-x pos-y size var-corner dev-corner dev-mark (Optional)
Obsolete but supported for import. Replaced by P084. Index mark data
line.
pos-x – Integer numerical data. X offset from the center of the
pos-y – Integer numerical data. Y offset from the center of the
size – Integer numerical data between 0 and 30000. Size of the index
search area in micrometers.
var-corner – Integer numerical data between 0 and 100. Allowed
contrast variance in percent when searching for index corner.
dev-corner – Integer numerical data between 0 and 100. Required
contrast in percent when searching for index corner.
dev-mark – Integer numerical data between 0 and 100. Required
contrast in percent when searching for index mark.
P082 camera (Optional)
Obsolete but supported for import. Centering camera specification line.
Any number of P082 lines is allowed.
camera – Text data representing type or name of a centering camera
which may be used to center the package. Allowed values are the
same as for the P071 line.

Component Data Format

This section defines the ASCII format of the Component data file used for
import/export of component data to/from TPSys internal databases.

Component Name
C00 name
Component name.
name – Text data. Corresponds to the Name field in the Components
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.
Stock Location Data

C021 stock-location (Optional)
Stock location line for component specified in last C00 line. Not exported
if the stock-location field is empty.
stock-location – Text data. Corresponds to the Stock location 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’.
Polarization and Reject

C05 pol-mount not-used reject-action
Polarization and reject action line.
pol-mount – Boolean data. Corresponds to the Polarized field in the
Components window. If ’FALSE’, the machine may mount the
component 180 degrees from the specified mount angle if it finds it
convenient. If ’TRUE’. the component is always mounted in the
specified angle.
not-used – Value not used. Ignored at import and always exported as
’0’. For compatibility reasons only.
reject-action – Enumerated data. Corresponds to the Reject position
field in the Components window. Value may be one of the following:
MANUAL – Move the component to manual reject position
and prompt operator to remove component.
BIN_1 – Throw component in throw position 1.
PUT_BACK – Put component back in magazine. This option
is available only for matrix trays.
CLOSEST_BIN – The system will try to find the closest bin
and throw the component there.

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
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’.
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
 A barcode made up of minus signs is ignored at import (Example: ’C07 ----’

will for example be ignored).

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.
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
The example above shows a component with the following properties:
Name .................................................................................................. 123-000

Package .............................................................................................. 1206-07
Comment .................................................................................... A component
Mount ........................................................................................................ Yes
Glue ........................................................................................................... Yes
Polarized .................................................................................................... No
Reject position ............................................................................. Reject 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
Name .................................................................................................. 123-001

Package .............................................................................................. 1206-07
Comment .................................................................................. RES 1 MOhm
Mount ........................................................................................................ Yes
Glue ............................................................................................................ No
Polarized .................................................................................................... No
Test 1
Type ............................................................................................... Resistance
Angle .............................................................................................. 90 degrees
Value ........................................................................................ 1 MOhm ±5%
Barcode ........................................................................................... R123-001
Feeder type .............................................................................................. 8mm
Magazine type ......................................................................................... Tape

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
Electrical test, Test 1

Type ............................................................................................. Capacitance
Angle .............................................................................................. 90 degrees
Value ................................................................................. 10 nF +100%-10%
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

Glue Dot Data Format

This section defines the ASCII format for the glue dot data file used for
import/export of Glue dot data to/from TPSys internal databases.

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.

up-force – Integer numerical data. Corresponds to the Slow up force

from glue field in the Glue Dots window. Maximum force when going
up from glue pot in mN.
up-speed – Integer numerical data. Corresponds to the Slow up speed
from glue field in the Glue Dots window. Speed when going up from
glue pot in mm/s.
G04 X-wait-time wait-time up-distance up-force up-speed
Glue place data line. See page D-2 for information about units.
X-wait-time – Integer numerical data. Corresponds to the Wait time
before/after X run field in the Glue Dots window. Wait time before
and after X-wagon movement in milliseconds (ms).
wait-time – Integer numerical data. Corresponds to the Wait time on
PCB field in the Glue Dots window. Wait time on board in
milliseconds (ms).
up-distance – Integer numerical data. Corresponds to the Slow up
distance from PCB field in the Glue Dots window. Distance to run
slowly when going up from the board in micrometers.
up-force – Integer numerical data. Corresponds to the Slow up force
from PCB field in the Glue Dots window. Maximum force when
going up from the board slowly in mN.
up-speed – Integer numerical data. Corresponds to the Slow up speed
from PCB field in the Glue Dots window. Speed when going up from
the board slowly in mm/s.
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:
Name ............................................................................................ DOT0.5mm

Tool ........................................................................................................... C12
Dip depth in glue ...................................................................... 0 micrometers
Wait time in glue .................................................................... 64 milliseconds
Slow up distance from glue ................................................................. 1.2 mm
Slow up force from glue ............................................................................ 5 N

Slow up speed from glue ................................................................... 80 mm/s
Wait time before/after X run .................................................... 0 milliseconds
Wait time on PCB ..................................................................... 0 milliseconds
Slow up distance from PCB ................................................................ 1.2 mm
Slow up force from PCB ........................................................................... 5 N

Slow up speed from PCB .................................................................. 80 mm/s

Magazine Data Format

This section defines the ASCII format of the Magazine data file used for
import/export of Magazine descriptions to/from TPSys internal databases.
Line Type Combinations

The ASCII representation for magazine data consists of a number of different
line types. These line types are only valid in a limited number of combinations.
The different line type combinations are specified below.
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 repeat 0 or many times.
[] means optional.
() just to mark several lines as a unit.
Line type combinations for tape magazine data

M10
[M15]
(M21 [M30-TM [M35-TM] ] )*
Line type combinations for stick magazine data

M10
[M15]
(M21 [M30-VM] )*
Line type combinations for DPUs

M10
[M15]
(M21-D [M30-DM])* (max 8 M30-DM lines per magazine)
Line type combinations for YWM and TWM trays

M10
[M15]
(M20-C [M30-TR [M40-T [M99-TC] ] ] )*
Line type combinations for TEX trays

M10
[M15]
(M20-C [M30-TP [M40-T [M99-TC] ] ] )*


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.
9 – Trimmable tape magazine TM8.
13 – Trimmable tape magazine TM1216. Obsolete.
17 – Tape magazine TM8B.
28 – Tape magazine TM8FB.
32 – Tape magazine TMFLEX.
34 – Generic Feeder Interface GFI.
48 – Agilis magazine AM8.

50 – Agilis linear magazine ALM8.

51 – Agilis linear magazine ALM1216.
52 – Tape magazine ALMFLEX
55 – Dip unit DPU
64 – Agilis Stick Magazine pallet ASP10.
65 – Agilis Stick Magazine pallet ASP1028.
66 – Agilis Stick Magazine pallet ASP28
serial-No – Integer numerical data. The magazine serial number as
encoded in the magazine PAL. Corresponds to the Serial number field
in the Magazines window. This number has no meaning for the
YWM, the TWM or the TEX pallets.
fiducial-mark-X – Integer numerical data. The magazine fiducial
mark X offset relative to the slot position. This number has no
meaning for the YWM, the TWM or the TEX pallets.
name – Text data. Corresponds to the Name field in the Magazines
window, or to the Name field in the TEX Pallets window. Leading and
In the TEX pallet case the name is truncated to 25 characters. If the
TEX pallet has no name, it will be set to "" on export. This data has
no meaning for the YWM or the TWM. On export it will however be
set to YW and TW respectively.
barcode – Text data. Optional. Corresponds to the Barcode field in the
Magazines window, or to the Barcode field in the TEX Pallets
window. Leading and trailing spaces are ignored and the barcode is
If the TEX pallet lacks a name, barcode will be set to "" on export. On
export, barcode will be set to YW for Y wagons and TW for Tray
wagons.
step-count – Integer numerical data. Optional. Number of times a
feeder has been stepped. Used for service.
fiducial-mark-Y-left – Integer numerical data. Optional. The Y offset
of the left fiducial mark relative to the pick position. This number has
no meaning for magazines other than the ALM type.
fiducial-mark-Y-right – Integer numerical data. Optional. The Y
offset of the right fiducial mark relative to the pick position. This
number has no meaning for magazines other than the ALM type.
auto-search-fiducial-mark – Boolean data. Optional. Indicates if
automatic magazine fiducial mark search is active or not. Corresponds
to the Fiducial mark field in the Magazines window.
M15 machine-No slot-No
Second magazine data line. This line is not read on data import. It is for
information only.
machine-No – Integer numerical data. The machine number or 0 if not
inserted.
slot-No – Integer numerical data. The slot number or -1 if not inserted.

Tape and Stick Feeder Contents

M21 number kit-flag feeder-type [angle] [quantity] [component] [batch-id]
(Optional)
Feeder contents line. There should be one M21 and one of the M30 line
for each feeder in the tape or stick magazine. Empty feeders will not be
present in exported data. Non-present feeders in imported data will be
emptied.
number – Integer numerical data. The feeder number.
kit-flag – Boolean data. Obsolete. Always FALSE when exported.
Ignored when imported.
feeder-type – Obsolete. Ignored when imported.
Feeder Contents - Magazine [***] window. The component angle for
stick feeders defaults to 0, and for tape feeders to 90 degrees. Optional
(not present if feeder is empty). See page D-2 for further information.
quantity – Integer numerical data. Corresponds to the Quantity field
in the Feeder Contents - Magazine [***] window. Default value is 0.
If the value is -1, the quantity is interpreted as an indefinite amount.
Optional (not present if feeder is empty).
component – Text data. Corresponds to the Name field in the Feeder
Contents - Magazine [***] 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 the Feeder
Contents - Magazine [***] window. The batch id is truncated to
35 characters. Optional (not present if feeder is empty).
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.
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.
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
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.
Tape Feeder Data

M35-TM x-offset step-length
Feeder data line for tape feeders. There should be one M21 and one M35-
TM line for each tape feeder in the magazine.
x-offset – Integer numerical data. Feeder X wise offset relative to the
magazine fiducial mark in micrometers.
step-length – Integer numerical data. Corresponds to the Step length
field in the Feeder Contents - Magazine [***] window. Length of
feed in micrometers.

TEX Tray Data

M30-TP x1 y1 x2 y2 auto-flag z-acc y-acc [tray-type] [HYDRA-reachable]
(Optional)
Feeder data line for TEX trays. There should be one M20-C and one M30-
TR line for each TEX tray.
x1 – Integer numerical data. X position of the lower left corner of the
tray in micrometers. Corresponds to the Lower left corner field in the
TEX Trays window.
y1 – Integer numerical data. Y position of the lower left corner of the
TEX Trays window.
x2 – Integer numerical data. X position of the upper right corner of the
tray in micrometers. Corresponds to the Upper right corner field in
the TEX Trays window.
y2 – Integer numerical data. Y position of the upper right corner of the
the TEX Trays window.
auto-flag – Boolean data. Corresponds to the Auto refill field in the
TEX Trays window. If ’TRUE’, auto refill mode will be enabled for
this TEX/ATM pallet.
z-acc – Enumerated data. Corresponds to the Acceleration code Z
field in the TEX Trays window. See page D-5 for further information.
y-acc – Enumerated data. Corresponds to the Acceleration code Y
field in the TEX Trays window. See page D-5 for further information.
tray-type – Text data. Optional. Corresponds to the Tray type field in
the TEX Trays window. Leading and trailing spaces are ignored and
the name is truncated to 20 characters.
HYDRA-reachable – Boolean data. Optional. If ’TRUE’, the tray is
high enough for the HYDRA to reach down to the tray. Corresponds
to the HYDRA pick field in the TEX Trays window.
YWM and TWM Tray Data

M30-TR x1 y1 x2 y2 auto-flag [tray-type] [HYDRA-reachable] (Optional)
Feeder data line for YWM and TWM trays. There should be one M20-C
and one M30-TR line for each tray.
x1 – Integer numerical data. X position of the lower left corner of the
YWM Trays or YWM Trays window.
y1 – Integer numerical data. Y position of the lower left corner of the
YWM Trays or YWM Trays window.
x2 – Integer numerical data. X position of the upper right corner of the
the YWM Trays or YWM Trays window.

y2 – Integer numerical data. Y position of the upper right corner of the

the YWM Trays or YWM Trays window.
auto-flag – Boolean data. Corresponds to the Auto refill field in the
YWM Trays or YWM Trays window. If 'TRUE', auto refill mode will
be enabled for this tray.
tray-type – Text data. Optional. Corresponds to the Tray type field in
the YWM Trays or TWM Trays window. Leading and trailing spaces
are ignored and the name is truncated to 20 characters.
HYDRA-reachable – Boolean data. Optional. If ’TRUE’, the tray is
high enough for the HYDRA to reach down to the tray. Corresponds
to the HYDRA pick field in the YWM Trays or TWM Trays window.
Stick Feeder Data

M30-VM x-offset amplitude duration frequency step-length-trim (Optional)
Feeder data line for stick feeders. There should be one M21 and one M30-
VM line for each feeder in the magazine.
x-offset – Integer numerical data. Feeder X-wise offset relative to the
amplitude – Integer numerical data. Corresponds to the Amplitude
field in the Feeder Contents - Magazine [***] window.
duration – Integer numerical data. Corresponds to the Duration field
in the Feeder Contents - Magazine [***] window.
frequency – Integer numerical data. Corresponds to the Frequency
field in the Feeder Contents - Magazine [***] window.
step-length-trim – Integer numerical data. Step length adjustment.
Corresponds to the Extra feeding steps field in the Feeder Contents -
Magazine [***] window.
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

orientation – Enumerated data. Optional. Corresponds to the

Orientation field in the YWM Trays or YWM Trays or TEX Trays
window. The orientation of the tray in the tray position given as the
corner where the first component is located. Value may be one of the
following:
LOWER_LEFT – Orientation: Same as tray type.
UPPER_LEFT – Orientation: Rotated 90°.
UPPER_RIGHT – Orientation: Rotated 180°.
LOWER_RIGHT – Orientation: Rotated 270°.
M99-TC status (Optional)
Feeder data line for trays.
status – Enumerated data. The status of the tray. Value may be one of
the following:
ERROR
OK
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.
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
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.
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
step – Integer numerical data. Number of steps per feed.

M99-TR status tray-position (Optional)

Obsolete but supported for import. Replaced by M99-TC. Feeder data line
for trays.
status – Integer numerical data. Value may be one of the following:
0 – Error
1 – Tray not present.
2 – Tray empty.
3 – Tray ok.
tray-position – Text data. Optional. The name of the tray position of
this tray. Leading and trailing spaces are ignored and the name is
M99-TP status tray-position (Optional)
Obsolete but supported for import. Replaced by M99-TC. Feeder data line
for TEX trays. This line is not exported.
status – Integer numerical data. Value may be one of the following:
0 – Error
1 – Tray not present.
2 – Tray empty.
3 – Tray ok.
tray-position – Text data. Optional. The name of the tray position of
this tray. Leading and trailing spaces are ignored and the name is

Magazine Data Examples
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
M35-TM 130300 4000
M35-TM 140300 4000
M35-TM 150300 4000
M35-TM 160300 4000
The example above shows a tape magazine with the following properties:
Type code ............................................................ 48 – Agilis magazine AM8

Serial number ....................................................................................... 131080
Fiducial-mark X ........................................................................ . -122.323 mm
Name .......................................................................................... AM8-131080
Barcode ......................................................................................................... ' '
Step count ................................................................................ Not applicable

Fiducial-mark Y left ................................................................ Not applicable
Fiducial-mark Y right .............................................................. Not applicable
Fiducial mark ............................................................................................. Yes

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
The example above shows a tray with the following properties:
Name/barcode ........................................................................... TQFP48-0.50

Component angle ............................................................................. 0 degrees
Quantity ....................................................................................................... 30
Component .................................................................................................. tst
Batch ID ........................................................................................... D345678
Lower left corner ............................................................................... 8/16 mm
Upper right corner ........................................................... 143.898/57.507 mm
Auto refill .................................................................................................. Yes
Tray type .......................................................................... TQFP48-0.50 3x10
HYDRA pick ............................................................................................ Yes
Machine ................................................................................................... 5108

Position ................................................................................................... Pos1
Orientation .......................................................................... Same as tray type
Tray Type Data Format

This section defines the ASCII format of the Tray type data file used for
import/export of Tray type descriptions to/from TPSys internal databases.

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
An empty field is not allowed.

Package For Teaching

T01 package-name (Optional)
Package name line. This line is not exported if package-name is empty.
package-name – Text data. Corresponds to the Typical package field
in the Tray Types window. Leading and trailing spaces are ignored
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.
Rows and Columns

T03 columns rows x-first y-first column-step row-step
Tray type layout line. See page D-2 for information about units.
columns – Integer numerical data. Corresponds to the Number of
columns field in the Tray Types window.
rows – Integer numerical data. Corresponds to the Number of rows
field in the Tray Types window.
x-first – Integer numerical data. Corresponds to the Lower left
component position field in the Tray Types window.
y-first – Integer numerical data. Corresponds to the Lower left
component position field in the Tray Types window.
column-step – Integer numerical data. Corresponds to the Column
step/row step field in the Tray Types window.
row-step – Integer numerical data. Corresponds to the Column
step/row step field in the Tray Types window.
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.
Pre-Pick Inspection Data

T06 inspect algorithm contrast
Optical pre-pick inspection parameters.
inspect – Boolean data. Corresponds to the Inspect before pick field in
the Tray Types window. Value may be one of the following:
TRUE – Perform Pre-pick inspection.
FALSE – No Pre-pick inspection.
algorithm – Enumerated data. Corresponds to the Inspect algorithm
field in the Tray Types window. Value may be one of the following:
AUTO – Automatically select one of the algorithms below.
DETECT_CONTRAST – Find component by separating
component from background.
DETECT_EDGES – Find component by detecting its edges.
contrast – Integer numerical data. Corresponds to the Edge contrast
field in the Tray Types window. Value may be between 1 and 30.
Tray Type Data Examples

T00 FC48-8x8
T01 FC48D-63-DC
T02 100200 100200
T03 8 8 15000 15000 9500 9500
T05 9710 9710
T06 1 AUTO 10
The example above shows a tray type with the following properties:
Name ............................................................................................... FC48-8x8

Typical package ...................................................................... FC48D-63-DC
Width/length ......................................................................... 100.2/100.2 mm
Number of columns ....................................................................................... 8
Number of rows ............................................................................................ 8
Lower left component position ....................................................... 15/15 mm

Column step/row step ................................................................... 9.5/9.5 mm
Tray pocket width/length .......................................................... 9.71/9.71 mm
Inspect before pick .................................................................................... Yes
Inspect algorithm ..................................................................................... Low
Edge contrast ............................................................................................... 10

Tray Position Data Format

This section defines the ASCII format of the Tray position data file used for
import/export of tray position descriptions to/from TPSys internal databases.

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
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.

magazine – Integer numerical data. Type code. Controls whether the

tray position will be imported to / is exported from the YWM Tray
Positions window, the TWM Tray Positions window or the TEX Tray
Positions window. Value may be one of the following:
-1 – YWM.
-2 – TWM.
-3 – TEX/ATM.
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.
Tray Position Data Examples

TP00 Pos1
TP01 2000 100000 0
TP02 -1
TP03 19173
The example above shows a tray position with the following properties:
Name ....................................................................................................... Pos1

Corner at .......................................................................................... 2/100 mm
Type .................................................................................... Lower left corner
Magazine ............................................................................................... YWM
Machine ................................................................................................. 19173
Removable Feeder Data Format

This section defines the ASCII format of the Removable feeder data file used
for import/export of removable feeders descriptions to/from TPSys internal
databases.


Name and Number

TG00 serial-number [name]
Removable feeder name and serial number line. Must be first line of file.
serial-number – Numeric data. Corresponds to the Serial number field
for the feeder in the Removable Feeders window.
name – Text data. Optional. Corresponds to the Name field in the
Removable Feeders window. Leading and trailing spaces are ignored
If no name is present, the name of the removable feeder is set to the
removable feeder’s serial number.
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.
Step and Trim Data

TG26 step-length [x-offset] [servo adjustment] (Optional)
Step length and offset line. This line sets the length the tape should be
advanced every feed, offsets to use when picking from tape guide and
required servo adjustment. See page D-2 for information about units.
step-length – Integer numerical data. Corresponds to the Step length
field in the Removable Feeders window. Most be zero or a positive
value.
x-offset – Integer numerical data. Distance between left edge and pick
position in micrometers.
servo adjustment – Integer numerical data. Represents how much
extra a tape has to be feed for the magazine to feed the component to
the desired location.
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
batch – Text data. Corresponds to the Batch ID field for the
component in the Removable Feeders window. The batch information

angle – Integer numerical data. Corresponds to the Angle field for the
component in the Removable Feeders window.
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.

Removable Feeder Data Examples

TG00 16779438 "AF 0016779438"
TG20 C12
TG26 4000 5916 88
TG31 "1206-a" "" 90000 2000
TG40 1023 3
The example above shows a removable feeder with the following properties:
Serial number (of feeder) ................................................................. 16779438

Name (of feeder) .................................................................... AF 0016779438
Comment (of feeder) ................................................................................ C12
Name (of component) ........................................................................... 1206-a
Batch ID (of component) ......................................................... no information
Angle (of component) ..................................................................... 90 degrees
Quantity (of component) ......................................................................... 2000
Magazine serial number .......................................................................... 1023
Feeder position .............................................................................................. 3
Magazine Kit Data Format

This section defines the ASCII format of the Magazine Kit data file used for
import/export of magazine kits to/from TPSys internal databases.

Special Enumerated Data Types
Magazine type codes

The magazine type code for the magazine kit data can have one of the
following values:
002
VM30 magazine. Vibratory magazine.
011
TM8 magazine. 8 mm tape magazine.
021
025
TM1216 magazine. 4X12 mm plus 4X16 mm tape magazine.
026

027
030
031
032
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
Magazine type names

The magazine type name can have one of the following values:
-
Not specified or not a valid type name.
ALM8
Agilis Linear magazine for 8 mm tape guides.
ALM1216
Agilis Linear magazine for 12/16 mm tape guides.
ALMFLEX
Flexible Agilis Linear magazine.
AM8
Agilis magazine for 8 mm tape guides.
ASM10
Agilis Stick Magazine pallet ASP10.
ASM1028
ASM28
GFI
Generic Feeder Interface GFI.

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
TM24
TM32
TM44
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
Magazine Kit Name

I10 name
Magazine kit name. Must be first line of file.
name – Text data. Corresponds to the Name field in the Magazine Kits
window. An empty name field is not allowed. Leading and trailing
spaces are ignored and the name is truncated to 35 characters.
Comment
I20 [comment] (Optional)
Comment line.
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.

magazine-name – Text data. Corresponds to the Magazine name field in

the Magazine Kit Contents window. This parameter is optional when
importing. Leading and trailing spaces are ignored and the name is
 If the serial number is valid, the type-code and magazine-name is ignored.
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".
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
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
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.

Located Tray Position

I41-X x1 y1 x2 y2 (Optional)
Tray position line. Defines position of tray in tray magazine coordinate
system. This line is only valid if component was specified using an I40-X
line. Follows I40-X if present.
x1 y1 – Integer numerical data. Position of lower left corner of tray.
Lower left as defined when the tray type was defined, not necessarily
the lower left for current position.
x2 y2 – Integer numerical data. Position of upper right corner of tray.
Upper right as defined when the tray type was defined, not necessarily
the upper right for current position.
Predefined Tray Position

I41-XP tray-position-name [orientation] (Optional)
Tray position line. Defines position as one of the predefined tray
positions. This line is only valid if component was specified using an I40-
X line. Follows I40-X if present.
tray-position-name – Text data. Name of tray position for tray.
Leading and trailing spaces are ignored and the name is truncated to
20 characters.
orientation – Enumerated data. Optional. The orientation of the tray in
the tray position given as the corner where the first component is
located. Value may be one of the following:
LOWER_LEFT
UPPER_LEFT
UPPER_RIGHT
LOWER_RIGHT
Refill
I41-XA auto-refill (Optional)
Auto-refill line.
auto-refill – Boolean data.
HYDRA Reachable Tray

I41-XH HYDRA-reachable (Optional)
HYDRA reachable line.
HYDRA-reachable – 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.
Management Data Format

This section defines an ASCII format of the Management data file used for
import/export of management data to/from TPSys internal databases.

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.

Management Data Examples

MD00 toolchange
MD01 tp94n064
MD02 7
MD03 7
MD04 9652550 0 182260
MD05 comp 1
MD06 21 35860 0 0 0 0 0
MD07 0 0
MD05 comp 2
MD06 21 36630 0 0 0 0 0
MD07 0 0
MD05 comp 3
MD06 24 54180 1 0 12 0 0
MD07 0 0
TEX Data Format

This section defines the ASCII format of the TEX data file used for
import/export of TEX descriptions to/from TPSys internal databases.

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
Serial Number and Type Code

X02 serial-number [type-code]
Tray Exchanger serial number and type code line.
serial-number – Integer numerical value. Serial number of the Tray.
type-code – Integer numerical value. Type code of the Tray
Exchanger. Default value, when import, is 201, that is, type code for
TEX.

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.
User Data Format

This section defines the ASCII format of the User data file used for
import/export of user descriptions to/from TPSys internal databases.

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

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
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
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
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
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.

Mycronic TPSys 3.3 Appendix E – TPSys Remote Protocol
Appendix E – TPSys Remote Protocol

This chapter describes the TPSys Remote Protocol (TRP). This protocol
makes it possible to access TPSys internal databases, load layouts to mount or
examine hardware and software options at the machine. When a connection is
established, it is possible to extract and modify all information that is stored in
the databases.
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.
4002720-EN – Software Manual Rev. A 2016-04 E-1

Appendix E – TPSys Remote Protocol TPSys 3.3 Mycronic
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 TRPserver terminates if TPSys internal servers terminate.
Testing Single TRP Commands

TPSys web interface contains a utility that allows you to send a TRP command
to TPSys. Any response is then shown on the screen. This tool is primarily
intended for testing and troubleshooting purposes.
1. Open the TPSys web interface.
2. Select Service Tools > Send TRP commands.
3. Enter a TRP command in the Command box, press <Enter> and view the
response.
 The E line, see page E-4, is not shown when viewing the response in the web
interface.
E-2 Rev. A 2016-04 4002720-EN – Software Manual

Quick Reference
ActivateUnsolicited type-list
DeActivateUnsolicited [ type-list ]
Delete data-type name...

ExitRemoteMode
GetData [-s time] [-ext ] data-type [ name...]
GetDataVersion
GetListOf data-type
GetListSize data-type
GetModifiedCount data-type
GetProtocolVersion [ALL]
GetTime [UNIX]
Help [COMMAND|ACK] [ALL| Command-name ]
ListOrder
LoadLayout (Obsolete), Use command QueueOrder instead.
MachineInfo [VERBOSE|QUIET]
Ping
PutData [PARSE_FLAG...]
PutEcho [ Parameters...]
QueueLayout (Obsolete), Use command QueueOrder instead.
RemoveLayoutFromQueue (Obsolete), Use command RemoveOrder instead.
RemoveOrder
SetProtocolVersion version
ShowAlerts
ShowCurrentStatus
ShowLayoutQueue (Obsolete), Use command ListOrder instead.
ShowMessages [ message-Id ]
ShowParameters ParameterFileNumber [ ParameterNumber...]
ShowRunningStatistics
Terminate
VerboseMode mode
US: MessageLog mtime mess
US: Status newstatus

General Command Format

All commands are line oriented and follow the format:
<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.
Special Line Types

There are some special lines that are returned from the TRPserver, or in some
cases accepted by the server also.
The special lines are:
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.
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"
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.
 The century should be 20 for year 2007.
-ext – Optional. Get data in extended format.

data-type – Type of data to get. See page E-25 for allowed data types.
name... – Optional list of items to get data for. If list is omitted, all
data for specified data type is transmitted. 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.
6 – Invalid parameter value. Probably bad "since usage".
101 – Item <name> does not exist. Even if only one of the items does
not exist, no data will be transmitted.
of request.
– Returned data:
’ackd’ followed by requested data. All lines of transmitted data are
preceded by ’>’ and end with a newline character. The data format
follows the import/export format in Appendix D or the event log
export format described in Appendix C.
The data ends with an ’E’ followed by a newline character.

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’.
For the example, the command looks like this:

getdata Refpoint Calibcomp
The returned data will look like this:

>R10 CalibComp
>R12 CIRCULAR
>R13-1 985 739 1231
>R14 BRIGHT
>R15 1900 1900
>R16 AUTO
>R17 -1
E
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:
6 – Invalid parameter value.
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.
Get List Size

GetListSize data-type
Get size of list for a specific data type.
– Parameters:
of request.
– Returned data:
’ackd’ followed by the number of items of the specified type. Data
ends with the E line.
If the data-type was Eventlog, the returned data will be the number
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.
 This command is not possible to use on data type ’eventlog’.
– Parameters:
data-type – Type of data to get modified count for. See page E-25 for
allowed data types.
100 – Unknown data type. Error code 100 is returned if
’GetModifiedCount’ is used with data type ’eventlog’.
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.
– 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.
 The century should be 20 for year 2007.
If UNIX style is specified, the returned time and date string is an

integer representing the number of seconds since 00:00:00, Jan 1,
1970. Data ends with the E line.

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
Sent to TRP connection.
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.
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:

list-of-SW-options – Lists the available SW options separated by a

comma (,). Prompt text: SW options:
magic-word – Magic word. Prompt text: Magic word:
Y-wagon position – Leftmost magazine position occupied by
Y wagon. Prompt text: Y placement:
Y-wagon width – Number of magazine positions occupied by
Y wagon. Prompt text: Y width:
Camera-type – Type of camera for optical centering. Prompt text:
OC camera:
Tray-magazine-list – List of available Tray magazines. Prompt text:
Tray mags:
HYDRA-option – ’YES’ if the HYDRA is enabled in parameter
191.0023 Options; HYDRA. 'NO' otherwise. Prompt text: HYDRA
option:
 The remaining data fields are only returned from machines, not from servers.
camera-type – One of highres, standard, Linescan and

HYDRA. This is the first field after the following prompt text:
Camera:
camera-xpos – X position of camera center, measured in
micrometers. There is one camera line for each installed camera. This
is the second field after the following prompt text: Camera:
Note that there is one Camera line for each installed camera.
tex-slot – tray exchanger slot position. This is the first field after the
following prompt text: TEX:
palletSize – The pallet width, measured in number of slots. This is the
second field after the following prompt text: TEX:
Note that there is one TEX line for each installed tray exchanger.
tw-slot – Slot position where the tray wagon is installed. This is the
first field after the following prompt text: TW:
tw-width – Tray wagon width, measured in number of slots. This is
the second field after the following prompt text: TW:
free-list – Comma separated list of free slot positions. Prompt text:
FreeSlots:
slot-pos-list – Comma separated list of X coordinates for all slot
positions. Prompt text: SlotPositions:
alm-supported – ’YES’ if ALM magazines are supported, ’NO’
otherwise. Prompt text: ALMMag:
x-type – Type of X axis servo/system. ’dsp’ or ’pre-dsp’. Prompt text:
XSystem:
z-type – Type of single head system. ’Midas’ or ’ZFi’. If the machine
has two X wagons, only data for the right X wagon will be presented.
Prompt text: ZSystem:

y-acc – Maximum Y acceleration, in m/s^2. Prompt text: YAcc:

HYDRA-present – ’YES’ if the HYDRA is present and enabled,
’NO’ otherwise. If the machine has two X wagons, only data for the
right X wagon will be presented. Prompt text: HYDRAPresent:
href-bgtype – Type of HYDRA reference background installed on the
HYDRA. One of TYPE_14, TYPE_23 and TYPE_28. If the machine
has two X wagons, only data for the right X wagon will be presented.
Prompt text: HRefBg:
board-handling-type – Type of board handling system. One of ’T’,
’PT’ and ’standalone’. Prompt text: BoardHandling:
board-direction – Board transport direction for T conveyor machines.
’LeftToRight’ or ’RightToLeft’. Prompt text: BoardDirection:
ztools-list – Comma separated list of available Z tools. Prompt text:
ZTools:
hbank-list – Comma separated list of 8 HYDRA tool types
corresponding to one row in a HYDRA tool bank. An empty position
is represented with a ’-’. There is one HBank line for each HYDRA
tool bank row in the machine. Prompt text: HBank:
htools-list – Comma separated list of 8 HYDRA tool types
corresponding to the manual HYDRA tools present on the HYDRA
unit. An empty position is represented with a ’-’. If the machine has
two X wagons, only data for the right X wagon will be presented.
Prompt text: HTools:
Data ends with the E line.
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.
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
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.
400 – No such layout. The layout could not be found in TPSys
databases.
– 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.
Field names are not case-sensitive.

The data must be followed by an end-of-data marker (a line with
single E).
101 – Nonexisting field specified.
102 – Unable to parse data.
200 – Missing machine number and the receiver is a data server.
400 – No such layout or layout not specified.

– Returned data:
’ack’ if the order was inserted in the order queue.
Example

QueueOrder
Layout : NameOfLayout
Batch Id : batchId
Order Size : 23
Machine No.: 141003
E
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.
6 – Invalid parameter value. In this case probably invalid lastflag.
401 – Layout queue empty. Cannot remove items from a non existing
queue.
– 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.
Field names are not case-sensitive.

The data must be followed by an end-of-data marker (a line with
single E).
101 – Nonexisting field specified.
102 – Unable to parse data.
– Returned data:
’ack’ if the order was removed from order queue.
Example

RemoveOrder
Order Id : batchId
Machine No.: 141003
E
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.
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
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.
Prompt (only shown if mode is

Data
VERBOSE)
current-layout Current layout:
status Status:
Total-to-mount Total to mount:
No.-left-to-mount Left to mount:
Not-available Not available:
Not-mountable Not mountable:
Layouts-produced Layout produced:
Boards-produced Boards produced:

ShowLayoutQueue (Obsolete)
This command has been replaced by the new command ListOrder, see page
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
– 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.
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.

503 – Invalid parameter number. At least one of the selected

parameter numbers is not a valid parameter number in selected
parameter file.
– Returned data:
If no parameter number given: A complete list of all parameters in
selected parameter file. One number-value pair per line. Otherwise,
only the selected parameter.
Returned data follows the format:
ParameterFileNumber:ParameterNumber parameterValue
The values are expressed in internal units, see page D-4.
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.
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.
– 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).

TPSys Data Types

The following data types are valid as parameters in TRP:
Mount data
TPSys data TRP data type
Layout data Layout
Panel data Panel
PCB data PCB
Fiducial mark data Refpoint
Package, Component and Glue dot data

Package data Package
Component data Component
Glue dot data Gluedot
Magazine data
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

Management data Management
TEX/ATM units data Tex
User data User
Event log export data Eventlog

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.


Mycronic TPSys 3.3 Appendix F – TPSys SQL Interface Setup
Appendix F – TPSys SQL Interface Setup
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.
The mydbxxxxview_10_base views contain mainly the table header

information and mydbxxxxview_10 views contain data from additional
tables.
Example: mydbpcbview10_base view contains one line per PCB in the

database (maybe thousands of lines) but mydbpcbview10 has one line for
each mount-line in all PCBs (hundred thousands of lines).
The data in the SQL tables is not possible to access.
4002720-EN – Software Manual Rev. A 2016-04 F-1

Appendix F – TPSys SQL Interface Setup TPSys 3.3 Mycronic
Installation
Add PostgreSQL ODBC Driver

Download the PostgreSQL ODBC driver from http://www.postgresql.org/.
Might be found under Download / Software Catalogue / Drivers and Interfaces

Product psqlOBDC
Description psqlODBC is the official PostgreSQL ODBC
Driver.
http://www.postgresql.org/ftp/odbc/versions/msi/
Select the latest 32 bit version and install it.
 Please note that even on 64-bit version of Windows 7, the 32 bit version should
be used.
F-2 Rev. A 2016-04 4002720-EN – Software Manual

Retrieving Data
Windows Data Source Setup

1. Windows 7 64 bit only:
Run c:\windows\sysWOW64\odbcad32.exe
2. Open the Control Panel / Administrative Tools / Data Source (ODBC) /
System DSN.
3. Add a PostgreSQL Unicode Data Source and give it a name.

4. You will be prompted to add data about the data connection.
Data Source: mydata db
Database: mydata_common_db
Server: ip-number or node name to TPSys server
User name: viewreader
Password: viewsonly
Retrieving Data from the Database
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 …
3. Select the datasource you configured previously and select OK.

Note the unchecked check box.

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.

8. The data is now displayed in the sheet.
Excel Example
Find out what packages are used in a specific PCB (FortKort Original).
1. Start Excel and make a new database query.

2. Select the data source and add 3 views:
- component
- package
- PCB
3. Connect (by dragging) ’component.package’ to ’package.name’.
4. Connect ’component.name’ to ’pcb.article’.
5. Add a criteria to the PCBs.
6. Limit the result to unique names.

7. Select ’package.name’ and drag it to the white area below.
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.
1. Start QlikView and select File > New.

2. Select File > Edit Script...

3. Connect to QDBC.
4. Select the mydata db created in section Windows Data Source Setup.

5. Enter below SQL statements in Main.
ODBC CONNECT TO [mydata db];
SQL SELECT name as component,

feedertype,
comment as component_comment,
package
FROM mydata_common_db.mydbcompview_10.component;
SQL SELECT name as board_name,

article as component,
location
FROM mydata_common_db.mydbpcblview_10.pcb;
SQL SELECT name as layout_name,

board_name,
comment as layout_comment
FROM mydata_common_db.mydblytlview_10.layout
where ispcb = 1;
ODBC CONNECT TO [mydata db];
SQL SELECT name as package, ztoolset, hydratoolset,

pickwaittimeoffset, placewaittimeoffset
FROM "mydata_common_db"."mydbpackview_10".package;
SQL SELECT articlename as component,

// layout as layout_name,
boardsassembled,

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;
Figure F-1. Resulting Data Structure in QlikView.
6. Save and then select Reload.

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
User name: carrierviewwriter
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.
Insert Query Logic

When a new carrier is inserted through a view, TPSys tries to find a similar
carrier and fill the values that are not set as same. Search function finds carrier
with same component name (of the same carrier type and subtype if set) in the
carrier database (carrier archive database and component database if not
found) and use values from last used carrier that is found.

Valid Carrier Subtypes

Carrier type:
• UNKNOWN
“”
• TAPE_MAG
“8mm”, “12mm”, “16mm”, “24mm”, “32mm”, “44mm”, “56mm”,
“72mm”, “88mm”, “104mm”, “120mm”, “136mm”, “152mm”, “custom”
• VIB_MAG
“below10mm”, “above10mm”,
• TRAY_MAG
“”
• GFI_MAG
“”

Description of Columns
Column name Insert (Set/NULL) Update Validation
carrierid Must not exist in the database. Ignored
componentname Used / Not allowed Ignored
batchid Used / Set empty Used
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
trayposition 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
step Used / From similar last used Used
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
autorefill Used / From similar last used Ignored
hydrareachable From similar last used / From similar last used Ignored
location Used / Set “Unknown” Used
owner Used / Set empty Used
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
quantityatload Set to default / Set to default Ignored
hasbeenloaded Set to default / Set to default Ignored
supplierpartnumber Used / From similar last used Ignored
timeatfirstload Set to default / Set to default Ignored
maxtotaltime Used / From similar last used Used It is possible to change this value only for carriers without running timer
timeatwarning Set to default / Set to default Ignored
timeatpause Set to default / Set to default Ignored
previouspauses Set to default / Set to default Ignored
timeatlocation Set to default / Set to default Ignored
previousfeeder From similar last used / From similar last used Ignored
lastchanged Generated / Generated Generated
created Used /Generated Ignored
aux1..9 Used / From similar last used Used

Insert Carrier Query Sample

If the location does not exist, a new custom container is created. If it exists,
the carrier is automatically inserted into that container.
INSERT INTO mydbcarrview_10.carrier_magname (carrierid,
componentname, batchid, carriertype, location, created, aux1)
VALUES ('04143214', 'Component 1' , 'batch 125' , 'TRAY_MAG',
'Shelf1', '2011-10-10 00:00:00', 'Created from view');
Update Carrier Query Sample

Perform the same sequence as in create from view. If the location does not
exist, a new custom container is created. If it exists, the carrier is moved to the
new location.
UPDATE mydbcarrview_10.carrier_magname
SET quantity = 102, location = 'Stock 25'
WHERE carrierid = '004828';
Create Container Query Sample

To create a container, see the query below for mandatory fields.
INSERT INTO mydbcontview_10.container(

modifiedtime, modifiedcount, id, barcode, name, ismslcompliant,
isshelved, comment)
VALUES (NULL, NULL, NULL, 'barcode01', 'name01', 0, 0,
'comment01');
Delete Container Query Sample

To delete container(s) only the container ID(s) is required. The example below
show how to delete two containers (IDs 36 and 37) using a single query:
DELETE FROM mydbcontview_10.container

WHERE id IN (36,37);

Mycronic TPSys 3.3 Index
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
4002720-EN – Software Manual Rev. A 2016-04 I-1

Index TPSys 3.3 Mycronic
Host name or IP address ................................................................................................... 6-6

I
Image log ................................................................................................................... 3-29
image log
download .............................................................................................................. 3-30
Import
Directline ................................................................................................................ 7-4
FTP default path ........................................................................................................ 7-4
renaming ................................................................................................................. 7-5
selecting files ........................................................................................................... 7-4
UNIX/NFS default path ............................................................................................... 7-4
USB flash drive ......................................................................................................... 7-4
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
Max. number of backups ................................................................................................... 6-5

Meta characters ............................................................................................................. 8-5
Mispick parameters ........................................................................................................ B-8
Modify user ................................................................................................................ 3-18
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
4002720-EN – Software Manual Rev. A 2016-04 I-3

Index TPSys 3.3 Mycronic
data types ............................................................................................................. E-25

testing ................................................................................................................... E-2
Type of automatic backup ................................................................................................. 6-5
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
I-4 Rev. A 2016-04 4002720-EN – Software Manual

Tool guide
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>
Melf tools Bank
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
Color Size (mm) Cross section

nozzles
H06 0.25
F6
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

4002720-En Software Manual Tpsys 3.3 English A

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4002720-En Software Manual Tpsys 3.3 English A

Uploaded by

Copyright:

Available Formats

TPSys™ 3.

4002720-EN Rev. A 2016-04

4002720-EN – Software Manual Rev. A 2016-04 i

Do not start, operate or service the

Mycronic AB, PO Box 3141, SE-183 03 Täby, Sweden.

ii Rev. A 2016-04 4002720-EN – Software Manual

Text Conventions ............................................................................................................. -xiii

1. Software Overview ................................................................................................... 1-1

2. Linux ......................................................................................................................... 2-1

3. TPSys ........................................................................................................................ 3-1

4002720-EN – Software Manual Rev. A 2016-04 iii

Time Lock .......................................................................................................... 3-8

4. Network and File Sharing .......................................................................................... 4-1

5. Data Sharing .............................................................................................................. 5-1

iv Rev. A 2016-04 4002720-EN – Software Manual

Data Types .................................................................................................... 5-3

6. Backup and Restore .................................................................................................. 6-1

7. Import/Export TPSys ................................................................................................ 7-1

8. Barcode Translation .................................................................................................. 8-1

4002720-EN – Software Manual Rev. A 2016-04 v

Case Sensitive ............................................................................................... 8-16

Appendix A – Messages Reference Guide .................................................................... A-1

vi Rev. A 2016-04 4002720-EN – Software Manual

OSM Group .................................................................................................. A-125

Appendix B – Parameters ............................................................................................... B-1

Appendix C – Event Log Export Format ....................................................................... C-1

Appendix D – Import/Export Data Formats ................................................................... D-1

4002720-EN – Software Manual Rev. A 2016-04 vii

Unit Code ..................................................................................................... D-6

viii Rev. A 2016-04 4002720-EN – Software Manual

Lead Groups Data ......................................................................................... D-35

4002720-EN – Software Manual Rev. A 2016-04 ix

Comment ...................................................................................................... D-71

Appendix E – TPSys Remote Protocol ........................................................................... E-1

x Rev. A 2016-04 4002720-EN – Software Manual

GetTime ........................................................................................................ E-10

Appendix F – TPSys SQL Interface Setup ..................................................................... F-1

Index ................................................................................................................................ I-1

4002720-EN – Software Manual Rev. A 2016-04 xi

New Features Overview

xii Rev. A 2016-04 4002720-EN – Software Manual

Danger, Warning, Caution, and Note

Danger, warning, and caution information must be followed.

 DANGER! Danger means a potentially dangerous situation that can cause

 WARNING! Warning means a potentially dangerous situation that can cause

 CAUTION! Caution means that the system or equipment can be damaged or

 A note contains any type of assisting information.

4002720-EN – Software Manual Rev. A 2016-04 xiii

1. Perform this step first.

xiv Rev. A 2016-04 4002720-EN – Software Manual

Linux, TPSys and Service Program

Linux is a multi-user and multi-tasking operating system, which TPSys

TPSys software is described in Chapter 3.

4002720-EN – Software Manual Rev. A 2016-04 1-1

MYCam is a software package used to convert a wide range of CAD data, to

• Transfer converted CAD files to Mycronic machines.

Data sharing can contain the following data types:

Data sharing • Package data.

MYCenter is a software package used to convert CAD files containing

P-000-0000-EN Rev. A 2014-12

1-2 Rev. A 2016-04 4002720-EN – Software Manual

The MYPlan software package includes a comprehensive MYPlan, User’s

P-000-0000-EN Rev. A 2014-12

The MYLabel software package includes a comprehensive MYLabel, User’s