SW TLV en PDF

Interface description
TLV commands and interpreter

for the TruTops Mark software program
TLV commands and

interpreter
for the TruTops Mark software program
Edition: 2017-02-23
Material number: 1436502

SW-TLV-EN
Order Information Please specify when ordering this document:
TLV commands and interpreter
2017-02-23
SW-TLV-EN
Material number: 1436502
© TRUMPF Schweiz AG
Table of contents
Chapter 1 Command-interpreter user interface for

TruTops Mark®
1. Functional scope of the command-interpreter ........... 1-3
2. Starting the TLV command interpreter ........................ 1-5
3. Application window ....................................................... 1-5

3.1 Status info ........................................................................ 1-6
3.2 Monitor area ..................................................................... 1-7
3.3 Buttons for the command interpreter ............................... 1-8
3.3.1. "F2 Monitor on/Monitor off" ............................... 1-8
3.3.2. "F3 Clear Monitor" ............................................ 1-8
3.3.3. "F4 Configuration" ............................................ 1-9
3.3.4. "F5 Find TLV-CMD" (command)..................... 1-10
3.3.5. "F6 Next TLV-CMD" (command) .................... 1-11
3.3.6. "F7 Configure interface" ................................. 1-11
3.3.7. "F8 Display interface/Hide interface" .............. 1-11
3.3.8. "F9 Reset interface" ........................................ 1-12
Chapter 2 TLV Commands
1. Structure of TLV Commands/TLV

Communications ............................................................ 2-7
1.1 TLV Commands ............................................................... 2-7
1.2 TLV Communications ...................................................... 2-7
2. Structure of the TLV Command Listings..................... 2-8

2.1 TLV Sequence with ASCII string as TLV Value............... 2-8
2.2 TLV Sequence with Unicode string as TLV Value ......... 2-10
2.3 Legend of the abbreviations used for the zero-
terminated strings .......................................................... 2-11
2.3.1. Result of the TLV request (G1)....................... 2-12
2.3.2. Extended error code (G2) ............................... 2-12
3. TLV commands for laser control system .................. 2-13

3.1 Laser/shutter .................................................................. 2-13
3.2 Shutter ........................................................................... 2-14
3.3 Pilot laser ....................................................................... 2-15
SW-TLV-EN 2017-02-23 Table of contents 5

3.4 Marking .......................................................................... 2-16
3.5 Trigger marking .............................................................. 2-18
3.6 Abort marking ................................................................ 2-19
3.7 Marking status ............................................................... 2-20
3.8 Laser status in Winmark format ..................................... 2-21
3.9 Laser reset ..................................................................... 2-22
3.10 Trigger conversion ......................................................... 2-23
3.11 Conversion status .......................................................... 2-24
3.12 Read pilot laser mode .................................................... 2-25
3.13 Set pilot laser mode ....................................................... 2-26
3.14 Read "Marking on the fly" parameters ........................... 2-27
3.15 Set "Marking on the fly" parameters .............................. 2-29
3.16 Read RTC parameters................................................... 2-30
3.17 Segment info .................................................................. 2-31
3.18 Segment data ................................................................ 2-33
3.19 Mark Segment ............................................................... 2-34
3.20 Creating the matrix and binning file for matrix
segmentation ................................................................. 2-36
3.21 Creation of a new matrix file for the matrix
segmentation ................................................................. 2-38
3.22 Laser status ................................................................... 2-41
3.23 Last error........................................................................ 2-42
3.24 Short error/warning text ................................................. 2-43
3.25 Last warning .................................................................. 2-44
3.26 Laser .............................................................................. 2-45
3.27 Q-switch ......................................................................... 2-46
3.28 Initialization of beam monitoring by the scanner ........... 2-47
3.29 Scanner beam monitoring.............................................. 2-49
3.30 Laser power ................................................................... 2-50
3.31 Frequency ...................................................................... 2-51
3.32 Defocusing ..................................................................... 2-52
3.33 Set laser parameters offsets .......................................... 2-53
3.34 Switching on or switching off "Marking on the fly" ......... 2-54
3.35 Switching on or switching off the retrigger mode ........... 2-55
4. TLV commands for Mechanics SW module .............. 2-56

4.1 Reference all axes ......................................................... 2-56
4.2 Reference axis ............................................................... 2-57
4.3 Reference two axes ....................................................... 2-58
4.4 Move axis ....................................................................... 2-59
4.5 Move two axes ............................................................... 2-61
4.6 Axis position ................................................................... 2-62
4.7 Recognize focal position ................................................ 2-63
4.8 Set segment offset for axes ........................................... 2-64
4.9 Open door ...................................................................... 2-65
4.10 Close door...................................................................... 2-66
6 Table of contents 2017-02-23 SW-TLV-EN

4.11 Rotate rotation door ....................................................... 2-67
4.12 Status rotating door ....................................................... 2-68
4.13 Move foil module ............................................................ 2-69
4.14 Edge-detection ............................................................... 2-70
4.15 Mechanics status ........................................................... 2-71
4.16 Mechanics error ............................................................. 2-74
4.17 Moving axes continuously (from TTM 2.7) .................... 2-78
4.18 Stop all axes (from TTM 2.7) ........................................ 2-79
4.19 Switch axis on or off....................................................... 2-80
5. TLV commands for the digital interface .................... 2-81

5.1 Inputs of the digital interface .......................................... 2-81
5.2 X input of the digital interface ........................................ 2-82
5.3 Digital interface outputs ................................................. 2-83
5.4 X output of the digital interface ...................................... 2-84
5.5 Inputs 1 to 8 of the digital interface ................................ 2-85
5.6 Inputs 9 to 16 of the digital interface .............................. 2-86
5.7 Inputs 17 to 24 of the digital interface............................ 2-87
5.8 Outputs 1 to 8 of the digital interface ............................. 2-88
5.9 Outputs 9 to 16 of the digital interface ........................... 2-89
6. TLV commands for the marking control system ...... 2-90

6.1 Load marking file ........................................................... 2-90
6.2 Convert marking file ....................................................... 2-91
6.3 Mark marking file X ........................................................ 2-92
6.4 Set directory path ........................................................... 2-93
6.5 N text variable (see also "Set variable") ........................ 2-94
6.6 Read file name/directory ................................................ 2-95
6.7 Set variable .................................................................... 2-96
6.8 Read variable ................................................................. 2-98
6.9 Scaling/displacement ..................................................... 2-99
6.10 Rotating/displacing the marking field in MHS
systems ........................................................................ 2-100
6.11 Load marking objects into the scanner ........................ 2-101
6.12 Activate scanner list ..................................................... 2-104
6.13 Start scanner list .......................................................... 2-105
6.14 Delete active VCT files ................................................ 2-106
6.15 Delete all VCT files ...................................................... 2-107
6.16 Hiding and showing the HMI ........................................ 2-108
6.17 Generating marking file for editing ............................... 2-109
6.18 Load marking file for editing......................................... 2-110
6.19 Import CAD file ............................................................ 2-111
6.20 Save the marking file opened for editing ..................... 2-113
6.21 Adding a line ................................................................ 2-113
6.22 Add an arc.................................................................... 2-115
6.23 Add a circle .................................................................. 2-116

6.24 Add a rectangle ............................................................ 2-117
6.25 Add a text ..................................................................... 2-118
6.26 Add an expanded text .................................................. 2-119
6.27 Add a variable .............................................................. 2-121
6.28 Replace laser parameter ............................................. 2-122
6.29 Replace fill parameter .................................................. 2-123
6.30 Initialize all variables .................................................... 2-124
6.31 Initialize variable .......................................................... 2-125
6.32 Set laser parameters – properties ............................... 2-126
6.33 Read laser parameter – Properties ............................. 2-127
6.34 Hide blocks .................................................................. 2-128
6.35 Add a Bitmaps (as of TruTops Mark 2.5.3).................. 2-129
6.36 Close the TruCad Server ............................................. 2-130
6.37 Adding a polyline ......................................................... 2-131
6.38 Adding an ellipse ......................................................... 2-133
6.39 Adding an ellipse arc ................................................... 2-135
6.40 Copying a file .............................................................. 2-137
6.41 Starts the adding of an assembled geometry object ... 2-138
6.42 Add an assembled geometry object to a polyline ........ 2-139
6.43 Closes the editing of an assembled geometry
object ........................................................................... 2-141
7. Unicode TLV commands ........................................... 2-142

7.1 Set variable with Unicode data .................................... 2-142
7.2 Read variable with Unicode data ................................. 2-145
7.3 Initialize variable with Unicode data (from TruTops
Mark 2.9) ...................................................................... 2-146
8. Additional TLV commands ....................................... 2-148

8.1 External program ......................................................... 2-148
8.2 DLL function ................................................................. 2-149
8.3 Start laser calibration (LPC) or cancel
(from TTM 2.7) ............................................................. 2-150
8.4 LPC status (from TTM 2.7) .......................................... 2-152
8.5 Load camera settings .................................................. 2-154
8.6 Execute camera function ............................................. 2-155
8.7 Set tag value ................................................................ 2-156
8.8 Read tag value ............................................................. 2-158
8.9 Capture image ............................................................. 2-160
8.10 Load image in camera (not yet implemented) ............. 2-161
8.11 Save image .................................................................. 2-162
8.12 Query available cameras ............................................. 2-163
9. Sample processes for activation of the laser

marking system with TLV sequences...................... 2-164

9.1 Example_01 Load and mark a marking file without
variables....................................................................... 2-164
variables for which the marking has been moved
and scaled.................................................................... 2-165
9.3 Example_03 Load and mark a marking file
with three variables ...................................................... 2-166
9.4 Example_04 Create a marking file Add objects and
mark the created marking file ...................................... 2-167
9.5 Example_05 Add a rectangle and a line to an
existing marking file and mark the revised marking
file ................................................................................ 2-168
9.6 Example_06 Include a CAD file in a marking file
and mark the modified marking file .............................. 2-169
9.7 Example_07 Mark 2 points without marking file
using scanner beam monitoring .................................. 2-170
9.8 Example_08 Load, convert and activate the
marking file in the 2 scanner lists ................................ 2-171
9.9 Example _09 Load and mark a marking file with a
variable that is set with Unicode data .......................... 2-172
9.10 Example_11 Load the marking file in scanner list
and set the MOF parameters ....................................... 2-173
9.11 Example_12 Demonstration of using automated
Binning ......................................................................... 2-174
9.12 Example_13 TLV conversion statuses (G2) with
variable ........................................................................ 2-175
9.13 Example_14 Execute camera function and carry
out code analysis. ........................................................ 2-176

Chapter 1
Command-interpreter user
interface for TruTops Mark®
1. Functional scope of the command-interpreter ........... 1-3
2. Starting the TLV command interpreter ........................ 1-5
3. Application window ....................................................... 1-5

3.1 Status info ........................................................................ 1-6
3.2 Monitor area ..................................................................... 1-7
3.3 Buttons for the command interpreter ............................... 1-8
3.3.1. "F2 Monitor on/Monitor off" ............................... 1-8
3.3.2. "F3 Clear Monitor" ............................................ 1-8
3.3.3. "F4 Configuration" ............................................ 1-9
3.3.4. "F5 Find TLV-CMD" (command)..................... 1-10
3.3.5. "F6 Next TLV-CMD" (command) .................... 1-11
3.3.6. "F7 Configure interface" ................................. 1-11
3.3.7. "F8 Display interface/Hide interface" .............. 1-11
3.3.8. "F9 Reset interface"........................................ 1-12
SW-TLV-EN 2017-02-23 1-1

1-2 SW-TLV-EN 2017-02-23
1. Functional scope of the command-
interpreter
With the command interpreter for TruTops Mark®, the laser
marking system can be controlled by means of TLV commands.
Different communication-interface modules can be used for
communication. The following communication interfaces are
currently supported:
• Profibus DP/DPV1 with the control processor as Profibus slave
• A "CIF 50-DPS" or a "CIFX 50-DP" Field bus card from
Hilscher must be installed in your control processor.
• Profinet with the control processor as ProfiNet device
• A "CIFX 50-RE" Field bus card from Hilscher must be
installed in your control processor.
• EtherCat with the control processor as Ethercat slave
• A "CIFX 50-RE" Field bus card from Hilscher must be
installed in your control processor.
• Serial interfaces with a simple log
• Ethernet TCP/IP protocol
• COM interface (SW interface)
o See Interface description
The supported TLV commands are described in chapter 2

TLV commands.
The main functions of the command interpreter are:
• Interpreting the received TLV commands and activating
the corresponding marking function.
• Recording the TLV communication in a monitor.
• Recording the TLV communication in a LOG file.
Note
The LSB (least significant bit) abbreviation appears in the
description in chapter 2, section 3.8.
If you imagine a horizontal bit sequence, then it depends on the bit
sequence whether the bits are counted from the right (with the
LSB) or left (with the MSB).
The counting starts with zero for the lowest-value bit (LSB) on the
right side and goes from right to left. The lowest-value bit has the
lowest value of 1.
Fig. 1-1
SW-TLV-EN 2017-02-23 1-3

The command interpreter supports two types of the TLV
communication:
1. TLV sequences:
Every TLV request is answered with a TLV response by the
command interpreter in this case.
2. Individual TLV commands:
The TLV request from the command interpreter is not
answered with a TLV response in this case.
In addition, TLV responses are provided by the command
interpreter without having received a TLV request in the first
place.
This type of communication is used together with Profibus DP

and allows controlling the "Marking laser" using the Process-
data interface of Profibus DP.
The available process-data interface is described in separate
documentation (Profibus documentation).
1-4 SW-TLV-EN 2017-02-23

2. Starting the TLV command interpreter
Start TruTops Mark®.

Select one of the above-listed interfaces supported by the
command-interpreter in the "Module" menu.
3. Application window
After starting the command-interpreter successfully, it is displayed

on the right side of the TruTops Mark® user interface such that the
following display appears:
3.1
3.2
3.3
Initial screen of the command interpreter Fig. 1-2
The user interface (GUI) of the command-interpreter basically

comprises three parts:
• Display area (3.1) for the communication interface status
• Monitor area (3.2) for recording the commands executed in
TLV notation
• Bar (3.3) with the buttons for controlling the command-
interpreter
SW-TLV-EN 2017-02-23 1-5

3.1 Status info
The current status of the communication interface is displayed via

an LED. Allocation of the individual statuses/colors is explained
below.
• A total of four different statuses are displayed:
• The communication interface is not ready as yet to replace

TLV commands (status color is gray)
Status display in the "Not ready for TLV commands" status
• The communication interface is ready to replace TLV

commands (status color is green)
Status display in the "Ready for TLV commands" status
• The communication interface is reset or configured at present

(status color is yellow)
Status display in the "Reset & configuration" status
• Communication interface is in the error state (status color is

red)
Status display in the "Error" status
The statuses, causes and possible error correction measures can

be seen in the Communication interfaces documentation:
• Profibus documentation and Interface description
1-6 SW-TLV-EN 2017-02-23

3.2 Monitor area
The executed TLV commands can be executed here, where

a maximum of the last 400 recorded lines are saved in the
monitor.
Two types of TLV commands are recorded:
• TLV sequences comprising a TLV request and a TLV
response
Example of a TLV sequence Fig. 1-3
• Structure of a recorded TLV sequence:

1. Line: TLV request with TAG, LENGTH and VALUE
in HEX representation
2. Line: TLV response with TAG, LENGTH and
VALUE in HEX representation
3. Line: interpreted TLV sequence with the result of
the functional execution
• Individual TLV commands
Example of an individual TLV command Fig. 1-4
• Structure of a recorded TLV command:

1. Line: TLV command with TAG, LENGTH and
VALUE in HEX representation
2. Line: interpreted TLV command with the result of
the execution
SW-TLV-EN 2017-02-23 1-7

3.3 Buttons for the command interpreter
The command-interpreter function can be controlled using

these buttons or the allocated function keys.
Fig. 1-5
• Controlling the monitor

• Searching for TLV commands
• Configuring the command-interpreter or configuring and
diagnosing the communication interfaces
3.3.1. "F2 Monitor on/Monitor off"
Statuses of the F2 button Fig. 1-6
This button can be used to start or stop the recording of the

TLV commands in the monitor.
• Recording that has started
The button has the "F2 Stop monitor" text
The F5/F6 buttons or their functions are not available.
• Recording that has stopped

The button has the "F2 Start monitor" text
The F5/F6 buttons or their functions are available.
The command-interpreter continues running in the
background.
3.3.2. "F3 Clear Monitor"
This button can be used to delete the monitor recording.
1-8 SW-TLV-EN 2017-02-23

3.3.3. "F4 Configuration"
This button can be used to configure the command-

interpreter.
• Click the button or press the relevant function key
• The following input dialog box is displayed, via which
you can configure the different settings.
Configuration dialog box of the command-interpreter Fig. 1-7
The following configuration options are available:

• Log mode:
– You can activate/deactivate the option of recording the
TLV command in a LOG file. The name of the LOG file can
be freely selected in this case.
Default name of the LOG file: "CMI.LOG"

• Laser status and input status (available only for the Profibus
interface):
– You can activate/deactivate the option of sending the
laser/input status automatically in case of changes in the
respective statuses.
SW-TLV-EN 2017-02-23 1-9

3.3.4. "F5 Find TLV-CMD" (command)
This button can be used to find a TLV command in the monitor

recording.
(Start the search is the first input in the monitor recording.).
• Click the button or press the relevant function key
– The following input dialog box is displayed using the
buttons, in which you can enter the number of the
searched TLV command as a decimal number.
Input dialog box for finding the TLV commands Fig. 1-9
• If the searched TLV command is found in the monitor

recording, it is highlighted and displayed on the monitor.
Displaying a TLV command that is found Fig. 1-10
1-10 SW-TLV-EN 2017-02-23

3.3.5. "F6 Next TLV-CMD" (command)
This button can be used to find the next

occurrence of a TLV command in the monitor recording, which has
already been searched for previously with the F5 button.
3.3.6. "F7 Configure interface"
This button can be used to start the configuration dialog box of the
communication interface.
For more information regarding the configuration options, refer to
the following communication interfaces:
• Profibus documentation
• Interface description
3.3.7. "F8 Display interface/Hide interface"
Statuses of the F8 function key Fig. 1-12
This button can be used to display/hide the user interface of the

communication interfaces.
The user interface of the communication interfaces can be used to
configure or diagnose the same:
See the following documentation of the communication interfaces:
• Profibus documentation
• Interface documentation
SW-TLV-EN 2017-02-23 1-11

3.3.8. "F9 Reset interface"
This button can be used to reset the communication interfaces.
1-12 SW-TLV-EN 2017-02-23

Chapter 2
TLV Commands
Communications ............................................................ 2-7
1.1 TLV Commands ............................................................... 2-7
1.2 TLV Communications ....................................................... 2-7
2. Structure of the TLV Command Listings ..................... 2-8

2.1 TLV Sequence with ASCII string as TLV Value ............... 2-8
2.2 TLV Sequence with Unicode string as TLV Value ......... 2-10
2.3 Legend of the abbreviations used for the zero-
terminated strings ........................................................... 2-11
2.3.1. Result of the TLV request (G1) ....................... 2-12
2.3.2. Extended error code (G2) ............................... 2-12
3. TLV commands for laser control system................... 2-13

3.1 Laser/shutter .................................................................. 2-13
3.2 Shutter ............................................................................ 2-14
3.3 Pilot laser ........................................................................ 2-15
3.4 Marking ........................................................................... 2-16
3.5 Trigger marking .............................................................. 2-18
3.6 Abort marking ................................................................. 2-19
3.7 Marking status ................................................................ 2-20
3.8 Laser status in Winmark format ..................................... 2-21
SW-TLV-EN 2017-02-23 TLV commands 2-1

3.9 Laser reset ..................................................................... 2-22
3.10 Trigger conversion.......................................................... 2-23
3.11 Conversion status........................................................... 2-24
3.12 Read pilot laser mode .................................................... 2-25
3.13 Set pilot laser mode........................................................ 2-26
3.14 Read "Marking on the fly" parameters ........................... 2-27
3.15 Set "Marking on the fly" parameters............................... 2-29
3.16 Read RTC parameters ................................................... 2-30
3.17 Segment info .................................................................. 2-31
3.18 Segment data ................................................................. 2-33
3.19 Mark Segment ................................................................ 2-34
3.20 Creating the matrix and binning file for matrix
segmentation .................................................................. 2-36
3.21 Creation of a new matrix file for the matrix
segmentation .................................................................. 2-38
3.22 Laser status .................................................................... 2-41
3.23 Last error ........................................................................ 2-42
3.24 Short error/warning text .................................................. 2-43
3.25 Last warning ................................................................... 2-44
3.26 Laser............................................................................... 2-45
3.27 Q-switch ......................................................................... 2-46
3.28 Initialization of beam monitoring by the scanner ............ 2-47
3.29 Scanner beam monitoring .............................................. 2-49
3.30 Laser power .................................................................... 2-50
3.31 Frequency ...................................................................... 2-51
3.32 Defocusing ..................................................................... 2-52
3.33 Set laser parameters offsets .......................................... 2-53
3.34 Switching on or switching off "Marking on the fly" .......... 2-54
3.35 Switching on or switching off the retrigger mode ........... 2-55
4. TLV commands for Mechanics SW module .............. 2-56

4.1 Reference all axes.......................................................... 2-56
4.2 Reference axis ............................................................... 2-57
4.3 Reference two axes........................................................ 2-58
4.4 Move axis ....................................................................... 2-59
4.5 Move two axes ............................................................... 2-61
4.6 Axis position ................................................................... 2-62
4.7 Recognize focal position ................................................ 2-63
4.8 Set segment offset for axes ........................................... 2-64
4.9 Open door ...................................................................... 2-65
4.10 Close door ...................................................................... 2-66
4.11 Rotate rotation door........................................................ 2-67
4.12 Status rotating door ........................................................ 2-68
4.13 Move foil module ............................................................ 2-69
4.14 Edge-detection ............................................................... 2-70
4.15 Mechanics status............................................................ 2-71
2-2 TLV commands SW-TLV-EN 2017-02-23

4.16 Mechanics error.............................................................. 2-74
4.17 Moving axes continuously (from TTM 2.7) ..................... 2-78
4.18 Stop all axes (from TTM 2.7) ......................................... 2-79
4.19 Switch axis on or off ....................................................... 2-80
5. TLV commands for the digital interface..................... 2-81

5.1 Inputs of the digital interface .......................................... 2-81
5.2 X input of the digital interface ......................................... 2-82
5.3 Digital interface outputs .................................................. 2-83
5.4 X output of the digital interface ....................................... 2-84
5.5 Inputs 1 to 8 of the digital interface ................................ 2-85
5.6 Inputs 9 to 16 of the digital interface .............................. 2-86
5.7 Inputs 17 to 24 of the digital interface ............................ 2-87
5.8 Outputs 1 to 8 of the digital interface ............................. 2-88
5.9 Outputs 9 to 16 of the digital interface ........................... 2-89
6. TLV commands for the marking control system ...... 2-90

6.1 Load marking file ............................................................ 2-90
6.2 Convert marking file ....................................................... 2-91
6.3 Mark marking file X......................................................... 2-92
6.4 Set directory path ........................................................... 2-93
6.5 N text variable (see also "Set variable") ......................... 2-94
6.6 Read file name/directory ................................................ 2-95
6.7 Set variable .................................................................... 2-96
6.8 Read variable ................................................................. 2-98
6.9 Scaling/displacement ..................................................... 2-99
6.10 Rotating/displacing the marking field in MHS
systems ........................................................................ 2-100
6.11 Load marking objects into the scanner ........................ 2-101
6.12 Activate scanner list ..................................................... 2-104
6.13 Start scanner list........................................................... 2-105
6.14 Delete active VCT files ................................................. 2-106
6.15 Delete all VCT files ....................................................... 2-107
6.16 Hiding and showing the HMI ........................................ 2-108
6.17 Generating marking file for editing ............................... 2-109
6.18 Load marking file for editing ......................................... 2-110
6.19 Import CAD file ............................................................. 2-111
6.20 Save the marking file opened for editing ...................... 2-113
6.21 Adding a line................................................................. 2-113
6.22 Add an arc .................................................................... 2-115
6.23 Add a circle ................................................................... 2-116
6.24 Add a rectangle ............................................................ 2-117
6.25 Add a text ..................................................................... 2-118
6.26 Add an expanded text .................................................. 2-119
6.27 Add a variable .............................................................. 2-121
6.28 Replace laser parameter .............................................. 2-122

6.29 Replace fill parameter .................................................. 2-123
6.30 Initialize all variables .................................................... 2-124
6.31 Initialize variable ........................................................... 2-125
6.32 Set laser parameters – properties ................................ 2-126
6.33 Read laser parameter – Properties .............................. 2-127
6.34 Hide blocks ................................................................... 2-128
6.35 Add a Bitmaps (as of TruTops Mark 2.5.3) .................. 2-129
6.36 Close the TruCad Server.............................................. 2-130
6.37 Adding a polyline .......................................................... 2-131
6.38 Adding an ellipse .......................................................... 2-133
6.39 Adding an ellipse arc .................................................... 2-135
6.40 Copying a file............................................................... 2-137
6.41 Starts the adding of an assembled geometry object .... 2-138
6.42 Add an assembled geometry object to a polyline ........ 2-139
6.43 Closes the editing of an assembled geometry
object ............................................................................ 2-141
7. Unicode TLV commands ........................................... 2-142

7.1 Set variable with Unicode data ..................................... 2-142
7.2 Read variable with Unicode data ................................. 2-145
7.3 Initialize variable with Unicode data (from TruTops
Mark 2.9) ...................................................................... 2-146
8. Additional TLV commands ........................................ 2-148

8.1 External program .......................................................... 2-148
8.2 DLL function ................................................................. 2-149
8.3 Start laser calibration (LPC) or cancel (from TTM
2.7) ............................................................................... 2-150
8.4 LPC status (from TTM 2.7) ........................................... 2-152
8.5 Load camera settings ................................................... 2-154
8.6 Execute camera function .............................................. 2-155
8.7 Set tag value ................................................................ 2-156
8.8 Read tag value ............................................................. 2-158
8.9 Capture image .............................................................. 2-160
8.10 Load image in camera (not yet implemented) .............. 2-161
8.11 Save image .................................................................. 2-162
8.12 Query available cameras ............................................. 2-163
9. Sample processes for activation of the laser

marking system with TLV sequences ...................... 2-164
variables ....................................................................... 2-164
variables for which the marking has been moved
and scaled .................................................................... 2-165

9.3 Example_03 Load and mark a marking file
with three variables ...................................................... 2-166
9.4 Example_04 Create a marking file Add objects and
mark the created marking file ....................................... 2-167
9.5 Example_05 Add a rectangle and a line to an
existing marking file and mark the revised marking
file ................................................................................. 2-168
9.6 Example_06 Include a CAD file in a marking file
and mark the modified marking file .............................. 2-169
9.7 Example_07 Mark 2 points without marking file
using scanner beam monitoring ................................... 2-170
9.8 Example_08 Load, convert and activate the
marking file in the 2 scanner lists ................................. 2-171
9.9 Example _09 Load and mark a marking file with a
variable that is set with Unicode data........................... 2-172
9.10 Example_11 Load the marking file in scanner list
and set the MOF parameters ....................................... 2-173
9.11 Example_12 Demonstration of using automated
Binning ......................................................................... 2-174
9.12 Example_13 TLV conversion statuses (G2) with
variable ......................................................................... 2-175
9.13 Example_14 Execute camera function and carry
out code analysis.......................................................... 2-176

Communications
If deviations from TruTops Mark® operating software utilized

should occur, then these are indicated and explained at the
respective points.
1.1 TLV Commands
TLV means TAG/LENGTH/VALUE. A TLV Command is

made up of these three parts. The meanings of the individual
parts are listed below.
Description Data size
Designation of the
TAG 4 bytes
commands
Number of utility data
LENGTH 4 bytes
in the VALUE field
Call-up or return
parameter of the
n * bytes
VALUE command
Maximum of 64 KB
(utility data of the
command)
Table 2-1
1.2 TLV Communications
TLV Communications is structured as a sequence made up of TLV

request and TLV Response:
• The TLV request corresponds to the requirement the same
way it corresponds to a service (e.g. Set outputs/Reading
inputs)
• The TLV Response corresponds to the response to the
request for the service (e.g. Result of service
performance/Status of inputs)
TLV communication (example with laser marking system/laser marking device VectorMark Fig. 2-1
compact)

2. Structure of the TLV Command
Listings
There are basically 2 types of TLV commands available:

• With ASCII string as TLV Value in Chapters 3, 4, 5, 6, 8
• With Unicode strings as TLV Value in Chapter 7
Each of the TLV sequences available are described here in
two tables.
2.1 TLV Sequence with ASCII string as

TLV Value
General Definition of the Name of the TLV Command

TLV Sequence
Brief description of the TLV Command
TAG LENGTH VALUE Remark
Request
Number of Zero-
bytes of the terminated
TLV VALUE ASCII
string
Number of
the TLV-
Response TAG
Number of Zero-
TLV VALUE ASCII
string
Table 2-2
Display of the TAG and LENGTH

• Specification as decimal number
• The zero terminators of the ASCII string must be included in
the count for the LENGTH value.
Display of a zero-terminated ASCII string using the example of

HELLO:
• ASCII display: "HELLO"
• HEX display: 48 41 4C 4C 4F 00

Display of several zero-terminated ASCII strings using the
example of HELLO WORLD:
• ASCII display: "HELLO" + "WORLD"
• HEX display: 48 41 4C 4C 4F 00 57 45 4C 54 00
Display of the TLV Sequence Example: General ASCII Dummy Command

in a concrete example
TAG LENGTH VALUE
Request Number of the TLV TAG Number of ASCII display
bytes of the of the VALUE
TLV VALUE
HEX display of the TAG HEX display HEX display of
of the the VALUE
LENGTH
Response Number of the TLV TAG Number of ASCII display
bytes of the of the VALUE
TLV VALUE
of the the VALUE
LENGTH
Table 2-3
Example: Concrete ASCII Dummy Command

TAG LENGTH VALUE
Request 12345 12 "123" + "456" + "abc"
31 32 33 00 34 35 36 00 61 62
39 30 00 00 0C 00 00 00
63 00
Response 12345 2 "0"
39 30 00 00 02 00 00 00 30 00
Table 2-4

2.2 TLV Sequence with Unicode string as
TLV Value
General Definition of the Name of the TLV Command

TLV Sequence
Brief description of the TLV Command
Request
Number of Zero-
TLV VALUE Unicode
string
Number of
Response the TLV TAG
Number of Zero-
TLV VALUE Unicode
string
Table 2-5
Display of the TAG and LENGTH

• Specification as decimal number
• The zero terminators of the Unicode string must be included in
the count for the LENGTH value.
Display of a zero-terminated Unicode string using the example

of HELLO:
• Unicode display: "HELLO"
• HEX display: 0048 0041 004C 004C 004F 0000
Display of several zero-terminated Unicode strings using the

example of HELLO WORLD:
• Unicode display: "HELLO" + "WORLD"
• HEX display: 0048 0041 004C 004C 004F 0000 0057 0045
004C 0054 0000

Display of the TLV Sequence Example: General Dummy Command
in a concrete example
TAG LENGTH VALUE
Request Number of the TLV TAG Number of Unicode
bytes of the display of the
TLV VALUE VALUE
of the the VALUE
LENGTH
Response Number of the TLV TAG Number of Unicode
bytes of the display of the
TLV VALUE VALUE
of the the VALUE
LENGTH
Table 2-6
Example: Concrete Dummy Command

TAG LENGTH VALUE
Request 67890 24 "123" + "456" + "abc"
31 00 32 00 33 00 00 00 34 00
32 09 01 00 18 00 00 00 35 00 36 00 00 00 61 00 62 00
63 00 00 00
32 09 01 00 04 00 00 00 30 00 00 00
Table 2-7
2.3 Legend of the abbreviations used for

the zero-terminated strings
Abbreviati
Description
on Example in ASCII display
T Text string in
"Hello"
ASCII/Unicode format
G Whole number in
"1234"
D Decimal number in
"45.678"
(only decimal point permits
no commas!)
B BINARY string in
"11001100"
Table 2-8

2.3.1. Result of the TLV request (G1)
The number of possible return values has been extended for

TruTops Mark®. The following return values are currently available
here:
Result of the TLV Meaning/Remarks

request
0 Command executed correctly
1 Command could not be executed
(-> See extended error code)
2 Erroneous TLV VALUE
3 Invalid TLV LENGTH of the Request for the
active communication interface
4 Invalid TLV LENGTH of the Response for the
Table 2-9
2.3.2. Extended error code (G2)
This is supported starting with TruTops Mark® and attached to

the TLV response when the "Result of the TLV request" has
been set to "1".
It contains detailed information concerning the cause of the
error behind the incorrect execution of the TLV request and
makes this available to the external control system.
The interpretation of the expanded error code is listed in the
description of the individual TLV commands.

3. TLV commands for laser control
system
3.1 Laser/shutter
Activates/deactivates the laser and opens/closes the shutter

Request 2 "G"
G: Status for laser/shutter
0: Æ Laser OFF and
shutter closed
1: Æ Laser ON and
shutter open
Response "G1" + "G2" Extended error code:
G1: Result of the TLV request: • Is added on to the TLV
0: Æ Command executed Response when the
20201 correctly result of the
TLV Request is "1".
Number of 1: Æ Command could not be
bytes in the executed (see extended
TLV Value error code)
2: Æ Erroneous TLV VALUE
3: Æ Invalid TLV LENGTH of
the request for the active
communication interface
G2: Extended error code
> 0: Æ Internal error
Table 2-10
Example: Activate laser and open shutter
TAG LENGTH VALUE

Request 20201 2 "1"
E9 4E 00 00 02 00 00 00 31 00
E9 4E 00 00 02 00 00 00 30 00
Table 2-11

3.2 Shutter
Opens/closes the shutter

Request 2 "G"
G: Status of the shutter
0: Æ Shutter for
1: Æ Shutter open
G1: Result of the TLV request: • Is added on to the
0: Æ Command executed TLV Response when the
correctly result of the
20202 Number of 1: Æ Command could not be TLV request is "1".
bytes in executed (see extended
the TLV error code)
Value 2: Æ Erroneous TLV VALUE
3: Æ Invalid TLV-LENGTH of
the request
active communication
interface
Table 2-12
Example: Close the shutter

TAG LENGTH VALUE
Request 20202 2 "0"
EA 4E 00 00 02 00 00 00 30 00
EA 4E 00 00 02 00 00 00 30 00
Table 2-13

3.3 Pilot laser
Activates/deactivates the pilot laser

Request 2 "G"
G: Status of the shutter:
0: Æ Switch off pilot laser
1: Æ Switch on pilot laser
0: Æ Command executed TLV Response when the result
correctly of the
Number TLV request is "1".
20203 1: Æ Command could not be
of bytes
executed (see extended
in the
error code)
TLV
3: Æ Invalid TLV LENGTH of the
Request for the active
9: Æ Option not activated
G2: Extended error code:
Table 2-14
Example: Activate pilot laser

TAG LENGTH VALUE
Request 20203 2 "1"
EB 4E 00 00 02 00 00 00 31 00
EB 4E 00 00 02 00 00 00 30 00
Table 2-15

3.4 Marking
Starts the marking procedure for the loaded marking file and waits until the marking procedure has been
completed.
Request 0 No data The following conditions must
be fulfilled:
• Marking file must be
loaded
• The beam source or the
pilot laser must be
switched on
TLV request is "1".
1: Æ Command could not be
error code)
the request for the
interface
1: Æ No converted marking file
is available
20204 2: Æ No marking file is loaded
Number of 3: Æ Lasers or pilot lasers are
bytes in the switched off
TLV Value
4: Æ Marking and/or
conversion procedure by
Trigger command
already activated
5: Æ Marking procedure has
been aborted manually
10: Æ General conversion errors
11: Æ No conversion, empty
variable
12: Æ Laser font not available
13: Æ Variable from text file: all
data processed
14: Æ Serial number: end value
reached
15: Æ Execution in the case of
activated "Restart mark"
is not allowed
Table 2-16

Example: Mark loaded marking file
TAG LENGTH VALUE
Request 20204 0 No data
EC 4E 00 00 00 00 00 00
EC 4E 00 00 02 00 00 00 30 00
Table 2-17

3.5 Trigger marking
Starts the marking procedure for the loaded marking file, does not however wait until the marking
procedure has been completed, but rather jumps back at once.
be fulfilled:
loaded
• The beam source or the
pilot laser must be
switched on
TLV request is "1".
error code)
20205 1: Æ A marking procedure has
already been activated
Number of 2: Æ No converted marking file
bytes in the is available
TLV Value
3: Æ No marking file is loaded
4: Æ Lasers or pilot lasers are
switched off
variable
data processed
reached
15: Æ Execution in case of
activated "Restart mark"
is not allowed
Table 2-18

Example: Trigger marking procedure
TAG LENGTH VALUE

ED 4E 00 00 00 00 00 00
ED 4E 00 00 02 00 00 00 30 00
Table 2-19
3.6 Abort marking
Interrupts the ongoing marking procedure

Request 0 No data
Response "G1" + "G2" Note:

• After the TLV Response
G1: Result of the TLV request:
has been received, the
0: Æ Command executed actual ending of the
correctly marking must be checked
1: Æ Command could not be by means of the
Number of TLV Command "Marking
20206 bytes in the executed (see extended
error code) status" before further
TLV Value TLV commands can be
executed.
Extended error code:
0: Æ Internal error • Is added on to the
TLV Response when the
result of the
TLV request is "1".
Table 2-20
Example: Interrupt the ongoing marking procedure

TAG LENGTH VALUE
EE 4E 00 00 00 00 00 00
EE 4E 00 00 02 00 00 00 30 00
Table 2-21

3.7 Marking status
Reads the current marking status

Request 0 No data
Response "G1" + "G2" + "G3" Extended error code:

• Is added on to the TLV
correctly result of the TLV request
1: Æ Command could not be is "1".
Number of error code)
20207 bytes in the 3: Æ Invalid TLV LENGTH of
TLV Value the request for the active
0: Æ Marking procedure is not
active
1: Æ Marking procedure is
active
Table 2-22
Example: Read marking status: marking active

TAG LENGTH VALUE
EF 4E 00 00 00 00 00 00
Response 20207 4 "0" + "1"
EF 4E 00 00 04 00 00 00 30 00 31 00
Table 2-23

3.8 Laser status in Winmark format
Reads the laser status in the Winmark format

Request 0 No data
Response "G1" + "B1" + "B2" + "G2" Formatting the laser status:

0: Æ Command executed • LSB is on the right in each
correctly case in the binary string
error code)
3: Æ Invalid TLV LENGTH of Extended error code:
the request for the
active communication • Is added on to the TLV
interface Response when the result of
4: Æ Invalid TLV LENGTH of the TLV request
the response for the
active communication is "1".
interface
B1: Bit 7 – 0
Bit 7: 1Æ Pilot laser is on
Bit 6: 1Æ Laser has a
malfunction
Bit 5: 1Æ Warning laser has
Number of responded
bytes in Bit 4: 1Æ Beam expander in
20208 position
the TLV
Value Bit 3: 1Æ Shutter is open
Bit 2: 1Æ Safety circuit is
closed
Bit 1: 1Æ Laser is ready
Bit 0: 1Æ Beam source on
B2: Bit 15 – 8
Bit 15: 1Æ Marking is active
Bit 14: 1Æ Control is on
Bit 13: 1Æ Heating period laser
is on
Bit 12: 1Æ EMERGENCY
SHUTDOWN circuit is
closed
Bit 11: 1Æ Key switch laser is
closed
Bit 10: 1Æ Switch of control
manually is activated
Bit 9: 1Æ Q-Switch trigger is on
Bit 8: 1Æ Laser warning lamp is
on
0: Æ Internal error
Table 2-24

Example: Laser status query in Winmark format
TAG LENGTH VALUE
F0 4E 00 00 00 00 00 00
Response 20208 20 "0" + "00001111" + "00011000"
F0 4E 00 00 14 00 00 00 30 00 30 30 30 30 31 31 31 31 00 30 30 30 31 31 30 30 30 00
Table 2-25
3.9 Laser reset
Carries out a resetting of the laser

Request 0 No data

0: Æ Command executed Response when the result of
Number of correctly the TLV request
bytes in Æ Command could not be is "1".
20209 1:
the TLV executed (see extended
Value error code)
Table 2-26
Example: Reset the laser

TAG LENGTH VALUE
F1 4E 00 00 00 00 00 00
F1 4E 00 00 02 00 00 00 30 00
Table 2-27

3.10 Trigger conversion
Starts the conversion procedure for the loaded marking file, does not however wait until the conversion
procedure has been completed, but rather jumps back at once.
be fulfilled:
loaded
correctly result of the TLV request
is "1".
error code)
20221 G2: Extended error code:

Number of
bytes in the 1: Æ A conversion procedure is
TLV Value already active
variable
data processed
reached
Table 2-28
Example: Trigger conversion procedure

TAG LENGTH VALUE
FD 4E 00 00 00 00 00 00
FD 4E 00 00 02 00 00 00 30 00
Table 2-29

3.11 Conversion status
Reads the current conversion status

Request 0 No data
Response "G1" + "G2" + "G3" Extended error code:

TLV Request is "1".
20222 bytes in the 3: Æ Invalid TLV LENGTH of
TLV Value the request for the active
G2: Marking status:
0: Æ Conversion procedure is
not active
1: Æ Conversion procedure is
active
Table 2-30
Example: Read conversion status: conversion active

TAG LENGTH VALUE
FE 4E 00 00 00 00 00 00
Response 20222 4 "0" + "1"
FE 4E 00 00 04 00 00 00 30 00 31 00
Table 2-31
Also see page 2-141, Example_13 TLV conversion statuses (G2)

with variable

3.12 Read pilot laser mode
Reads the pilot laser mode currently set

Request 0 No data
Response "G1" + "G2" + "G3" + "G4" + "G5" + "G6"
Restart mark:
0: Æ Command executed correctly • The parameter G5 is
1: Æ Command could not be always "0".
executed (see extended The automatic start
error code) of the pilot laser can
be used only with the
3: Æ Invalid TLV LENGTH of the workstation module
request for the active
G2: Pilot laser mode:
0: Æ No pilot laser is available
Number of Extended error code:
bytes in the 1: Æ Contour mode
20231 TLV Value 2: Æ Rectangle mode • Is added on to the
TLV Response when
G3: Marking mode:
the result of the
0: Æ Once TLV Request is "1".
1: Æ Continuous
G4: Speed in mm/s
G5: Restart mark
0: Æ The pilot laser is no longer
switched on automatically
after activation
1: Æ The pilot laser is switched on
automatically after activation
Table 2-32
Example: Read pilot laser mode contour/endless/400 mm/s

TAG LENGTH VALUE
07 4F 00 00 00 00 00 00
Response 20231 10 "0" + "1" + "1" + "400" + "0"
07 4F 00 00 0C 00 00 00 30 00 31 00 31 00 34 30 30 00 30 00
Table 2-33

3.13 Set pilot laser mode
Sets the pilot laser mode

Request "G1" + "G2" + "G3"
• If the "Continuous" marking
G1: Pilot laser mode: mode is selected, the "Mark"
TVL command should not be
1: Æ Contour mode
used at the start of the marking
Number of 2: Æ Rectangle mode procedure since the marking
procedure can only be aborted
bytes in the G2: Marking mode: using the "CTRL C" standard
TLV Value GUI in that case.
0: Æ Once
• Instead, the "Trigger marking"
1: Æ Continuous TVL command should be
G3: Speed in mm/s used, which can be aborted
again using the "Abort
Valid value range: marking" TLV command.
1 to 5000
20232 G1: Result of the TLV request:
0: Æ Command executed Response when the result
correctly of the TLV Request is "1".
Number of
bytes in the error code)
TLV Value
9: Æ Option not activated
G2: Pilot laser mode:
Table 2-34
Example: Set pilot laser mode rectangle

mode/endless/200 mm/s
TAG LENGTH VALUE
Request 20232 8 "2" + "1" + "200"
08 4F 00 00 08 00 00 00 32 00 31 00 32 30 30 00
08 4F 00 00 02 00 00 00 30 00
Table 2-35

3.14 Read "Marking on the fly" parameters
Reads the "Marking on the fly" parameters currently set

Request No data The following conditions
must be fulfilled:
"Marking on the fly"
must be activated.
0
Explanations:
Additional details concerning
"Marking on the fly" can be
obtained from the associated
document.
Response "G1" + "G2" + "G3" + "D1" + "D2" + Format of the decimal
"D3" + "D4" + "D5" + "G5" numbers:
G1: Result of the TLV request: Are returned with
3 digits after the decimal
0: Æ Command executed point.
correctly
1: Æ Command could not be Extended error code:
error code)
Is added on to the TLV
Response when the
20233 communication interface
result of the
TLV Request is "1".
G2: Start delay in 1/16 pulses
Number of G3: Simulation of the external
bytes in the start signal in 1/16 pulses
TLV Value
D1: Scaling for the X encoder
D2: Scaling for the Y encoder
D3: Scaling for the rotation
encoder
D4: Displacement to the
rotation center in
X direction
rotation center in
Y direction
1: Æ "Marking on the fly" is not
activated
Table 2-36

Example:: Reading the currently set "Marking on the fly"
parameters: 10 / -5 / 1.5 / 3.0 / 0.0 / 0.0 / 0.0
TAG LENGTH VALUE
09 4F 00 00 00 00 00 00
Response "0" + "10" + "-5" + "1.500" + "3.000" + "0.0" + "0.0"
20233 32
+ "0.0"
30 00 31 30 00 2D 35 00 31 2E 35 30 30 00 33 2E
09 4F 00 00 20 00 00 00
30 30 30 00 30 2E 30 00 30 2E 30 00 30 2E 30 00
Table 2-37

3.15 Set "Marking on the fly" parameters
Temporarily sets the assigned parameters for "Marking on the fly"
Request "G1" + "G2" + "D1" + "D2" + "D3" + The following conditions
"D4" + "D5" must be fulfilled:
G1: Start delay in 1/16 pulses "Marking on the fly"
must be activated.
G2: Simulation of the external
start signal in 1/16 pulses
Explanations:
D1: Scaling for the X encoder Additional details
Number of
bytes in the D2: Scaling for the Y encoder concerning "Marking on
TLV Value the fly" can be obtained
D3: Scaling for the rotation
from the associated
encoder
document.
rotation center in Limitation:
X direction
The settings are only
D5: Displacement to the temporarily modified for the
rotation center in current session and will not
Y direction be saved.
20234
correctly
result of the
1: Æ Command could not be TLV Request is "1".
Number of executed (see extended
bytes in the error code)
TLV Value 2: Æ Erroneous TLV VALUE
1: Æ "Marking on the fly" is
not activated
Table 2-38
Example:Set the "Marking on the fly" parameters temporarily: 10 /
-5 / 1.5 / 3.0 / 0.0 / 0.0 / 0.0
TAG LENGTH VALUE
Request 20234 26 "10" + "-5" + "1.5" + "3.0" + "0.0" + "0.0" + "0.0"
31 30 00 2D 35 00 31 2E 35 00 33 2E 30 00 30
0A 4F 00 00 1A 00 00 00
2E 30 00 30 2E 30 00 30 2E 30 00
0A 4F 00 00 02 00 00 00 30 00
Table 2-39

3.16 Read RTC parameters
Reads the current RTC parameters

Request 0 No data
Response "G1" + "D1" + "G2" + "G3" + "G4" + Limitation:

"B1" + "G5" + "G6" + "G7" + "G8" The returned
G1: Result of the TLV request: parameters "Number of
commands of the active
0: Æ Command executed
list" and "Number of
correctly
markings executed
1: Æ Command could not through the
be executed (see "Restart_mark" digital
extended error code) input are only valid when
3: Æ Invalid TLV LENGTH the "Restart_mark" X230
of the request for the input is activated.
interface
Format of the decimal
D1: Marking time in seconds numbers:
G2: Number of commands of Are returned with
the active list 3 digits after the decimal
G3: Number of markings point.
executed through the
"Restart_mark" digital Formatting of the options:
interface input LSB is on the right in the
G4: RTC card type binary string.
Number of 0: Æ No RTC cards are

bytes in the available Extended error code:
20235
TLV Value 2: Æ RTC2 card
3: Æ RTC3 card Response when the
B2: Bit 15 – 0 Options for the result of the
RTC card TLV Request is "1".
Bit 15: 1Æ Reserved
: 1Æ :
: 1Æ :
Bit 2: 1Æ Reserved
Bit 1: 1Æ Multi-head
Bit 0: 1Æ "Marking on the fly"
G5: Configuration of the
"Restart_mark" digital
input
0: Æ Deactivated
1: Æ Activated
G6: Counter reading for the
X encoder in case of the
MOTF option
G7: Counter reading for the
Y encoder in case of the
MOTF option
Table 2-40

Example: Reading RTC parameters: 0.567/248/79/RTC3 card /
"Marking on the fly"/1/123/456
TAG LENGTH VALUE
0B 4F 00 00 00 00 00 00
Response "0" + "0.567" + "248" + "79" + "3" + "0000000000000001" + "1"
20235 44
+ "123" + "456"
30 00 30 2E 35 36 37 00 32 34 38 00 37 39 00 33 00 30 30 30
0B 4F 00 00 2C 00 00 00 30 30 30 30 30 30 30 30 30 30 30 30 31 00 31 00 31 32 33 00
34 35 36 00
Table 2-41
3.17 Segment info
Reads general information of the loaded, segmented marking file

Request 0 No data The following conditions
must be fulfilled:
20241
• A segmented marking
file must be loaded.

Reads general information of the loaded, segmented marking file
Response "G1" + "G2" + "G3" + "G4" + "G5" + "G6" + "D1" + Format of the decimal
"D2" + "G7" numbers:
0: Æ Command executed correctly Is returned with 3 digits
1: Æ Command could not be executed (see after the decimal point.
extended error code)
3: Æ Invalid TLV LENGTH of the request for the
4: Æ Invalid TLV LENGTH of the response for the • Is added on to the
TLV Response when
G2: Segmentation mode: the result of the
0: Æ No segmentation TLV Request is "1".
1: Æ X/Y segmentation
2: Æ Cylinder segmentation
3: Æ Free user-defined X/Y segmentation
4: Æ 3D-Z axes segmentation
Number
G3: No. of segments in the X direction
of bytes
in the G4: No. of segments in the Y direction
TLV G5: No. of segments in the Z direction
Value
G6: Axis position at the time of cylinder
segmentation
1: Æ Parallel to the X axis with direction of
rotation to the right
2: Æ Parallel to the X axis with direction of
rotation to the left
3: Æ Parallel to the Y axis with direction of
rotation to the right
4: Æ Parallel to the Y axis with direction of
rotation to the left
D1: Increment angle at the time of
cylinder segmentation
D2: Length of the cylinder at the time of
cylinder segmentation
1: Æ Segmentation not activated
3: Æ Segment info could not be read
Table 2-42
Example: Reading general information for the loaded, segmented

marking file -> X/Y-segmentation/8 segments in X direction/4
segments in Y direction
TAG LENGTH VALUE
11 4F 00 00 00 00 00 00
Response 20241 24 "0" + "1" + "8" + "4" + "0" + "0" + "0.000" + "0.000"
11 4F 00 00 18 00 00 00 30 00 31 00 38 00 34 00 30 00 30 00 30 2E 30 30 30 00 30 2E 30 30 30 00
Table 2-43

3.18 Segment data
Reads information concerning the segment assigned from the loaded, segmented marking file
Request Number of The following conditions
bytes in the must be fulfilled:
"G"
TLV Value A segmented marking file
G: Segment number must be loaded
Response Format of the decimal
"G1" + "D1" + "D2" + "D3" + "D4" + "D5" + "D6" + numbers:
G2"
• Are returned with
G1: Result of the TLV request: 3 digits after the
0: Æ Command executed correctly decimal point.
1: Æ Command could not be executed Extended error code:
(see extended error code)
2: Æ Erroneous TLV VALUE • Is added on to the
TLV Response when
3: Æ Invalid TLV LENGTH of the request the result of the
for the active communication TLV Request is "1".
interface
4: Æ Invalid TLV LENGTH of the response
for the active communication
interface
20242 Number of D1: X offset of the segment
bytes in the
TLV Value D2: Y offset of the segment
D3: Z offset of the segment
D4: Segment width (X axes direction)
D5: Segment height (Y axes direction)
D6: Absolute angle for cylinder
segmentation
2: Æ Segment data could not be read
3: Æ No segmented file has been
loaded
4: Æ Time overrun
5: Æ Segment with the assigned number
contains no marking data
Table 2-44

Example: Reading information for Segment 5, the loaded,
segmented marking file
-> X offset=2.500/Y offset=-3.125/Z offset=-
1.000/Segment width = 1.500/Segment height 0
5.725/Angle = 0.000"
TAG LENGTH VALUE
Request 20242 2 "5"
12 4F 00 00 02 00 00 00 35 00
Response 20242 40 "0" + "2.500" + "-3.125" + "-1000" + "1.500" + "5.752" + "0.000"
30 00 32 2E 35 30 30 00 2D 33 2E 31 32 35 00 2D 31 2E 30 30 30 00 31 2E
12 4F 00 00 28 00 00 00
35 30 30 00 35 2E 37 32 35 00 30 2E 30 30 30 00
Table 2-45
3.19 Mark Segment
Marks the assigned segment of the loaded, segmented marking file

Request The following conditions must be
"G1" + "G2" fulfilled:
G1: Segment number A segmented marking file must
be loaded
G2: Axis mode
Number of The beam source or the pilot
bytes in the 0: Æ Axes are not moved
20243 TLV Value laser must be switched on
1: Æ Axes are moved from the
station. The marking file must be
converted manually prior to
marking with the TLV commands
"Convert marking file"/"Trigger
conversion".
.

Marks the assigned segment of the loaded, segmented marking file
Response Extended error code:
"G1" + "G2"
correctly
Response when the
result of the TLV request
executed (-> See extended
error code)
1: Æ No segmented marking file
has been loaded
2: Æ Marking procedure is already
activated
Number of
3: Æ No converted marking file is
bytes in the available
TLV Value
5: Æ Lasers or pilot lasers are
switched off
6: Æ Marking and/or conversion
procedure by Trigger
command already activated
variable?
data processed
reached
15: Æ Execution in case of
activated "Restart mark" is
not allowed
Table 2-46
Example: Marking Segment 5 of the loaded marking

file/axes are not moved
TAG LENGTH VALUE
Request 20243 4 "5" + "0"
13 4F 00 00 04 00 00 00 35 00 30 00
13 4F 00 00 02 00 00 00 30 00
Table 2-47

3.20 Creating the matrix and binning file for
matrix segmentation
Creates a segment and binning matrix for the matrix segmentation from the offset/binning file of the customer.
Request Is only supported from TruMark
on.
"G1" + "G2" The following conditions must

be fulfilled:
G1: Name of the original matrix
file A matrix segmentation file must
Number of
G2: Name of the offset and be loaded. The offset/binning
bytes in the
20244 TLV Value binning file of the file must comply with the
customer. corresponding format.
The marking file must be

converted manually prior to
marking with the TLV
commands
"Convert marking file"/"Trigger
conversion".
.

Creates a segment and binning matrix for the matrix segmentation from the offset/binning file of the customer.
Response Is only supported from TruMark
"G1" + "G2" on.
G1: Result of the TLV request: Extended error code:
0: Æ Command executed Is added on to the TLV
correctly
Response when the
1: Æ Command could not be result of the TLV request is "1".
error code)
2: Æ No marking file has been
loaded
3: Æ No conversion data is
available.
Number of 4: Æ Header information of the

XML files could not be
bytes in the
read.
TLV Value
5: Æ Original matrix file is not
available.
6: Æ Error while reading the
original matrix.
7: Æ Used matrix file is not
available.
used matrix file.
9: Æ Offset and binning file not
available.
offset and binning file.
11: Æ Matrix file could not be
written.
12: Æ Binning file could not be
written.
13: Æ Used and original matrix
are identical.
14: Æ No matrix position to be
marked.
Table 2-48

Example: Create a new matrix and binning file for the matrix
segmentation.
TAG LENGTH VALUE
Request 20244 55 "c:\TruMark\xml\matrix.xml" + "c:\TruMark\xml\OffsetBin.xml"
63 3A 5C 54 72 75 4D 61 72 6B 5C 78 6D 6C 5C 6D 61 74 72 69 78 2E 78
14 4F 00 00 37 00 00 00 6D 6C 00 63 3A 5C 54 72 75 4D 61 72 6B 5C 78 6D 6C 5C 4F 66 66 73 65
74 42 69 6E 2E 78 6D 6C 00
14 4F 00 00 02 00 00 00 30 00
Table 2-49
3.21 Creation of a new matrix file for the

matrix segmentation
Creates a matrix file for the matrix segmentation.

Request Is only supported from TruMark
on.
"G1" + "G2" The following conditions must

Number of be fulfilled:
bytes in the G1: Name of the matrix info file
20245 TLV Value G2: Name of the matrix file A matrix info file must be
available with the specific
information for the matrix. The
format of the XML file must be
complied with.

Creates a matrix file for the matrix segmentation.
Response Is only supported from TruMark
"G1" + "G2" on.
G1: Result of the TLV request: Extended error code:
0: Æ Command executed Is added on to the TLV
correctly
Response when the
1: Æ Command could not be result of the TLV request is "1".
error code)
1: Æ Image field height or –
width could not be read
.
2: Æ Starting position from Head
A could not be read
3: Æ Starting position from Head
B
could not be read
.
4: Æ Registry could not
be read.
5: Æ Storage location could
not be allocated
Number of .
bytes in the 10: Æ Error when reading in the
TLV Value MatrixInfo file
21: Æ Number of columns or
rows
not defined
22: Æ Size of the step in x
or y direction not
defined
23: Æ Error in allocating
memory when creating
the strip
31: Æ Number of rows and
columns
are not defined
40: Æ X-Position is outside the
marking range of Head A
41: Æ y position is outside
of the marking range of
Head A
42: Æ X-Position is outside the
marking range of Head B
Head B
50. Æ X-Position is outside
Head A
Head A
Table 2-50

Example: Creation of a new matrix file for the matrix
segmentation.
TAG LENGTH VALUE
Request "c:\TruMark\xml\MatrixInfoFile_single_head.xml" +
20245 84
"c:\TruMark\xml\matrix_single_head.xml"
63 3A 5C 54 72 75 4D 61 72 6B 5C 78 6D 6C 5C 4D 61 74 72 69 78 49 6E 66
6F 46 69 6C 65 5F 73 69 6E 67 6C 65 5F 68 65 61 64 2E 78 6D 6C 00 63 3A
15 4F 00 00 54 00 00 00
5C 54 72 75 4D 61 72 6B 5C 78 6D 6C 5C 6D 61 74 72 69 78 5F 73 69 6E 67
6C 65 5F 68 65 61 64 2E 78 6D 6C 00
15 4F 00 00 02 00 00 00 30 00
Example <?xml version="1.0" standalone="true"?>
<MatrixInfoFile>
MatrixInfo <Project Binning="C:\TruMark\XML\binning_test_single_head_xml" Vlf="C:\TruMark\Vlf\vlf_test_single_head.vlf"/>
file <Matrix x_Offset="0.000" x_Pitch="5.000" No_of_columns="30" Distance_column_groups="0.000" No_of_column_groups="1"
y_Offset="0.000" y_Pitch="5.000" No_of_rows="30" Distance_row_groups="0.000" No_of_row_groups="1"/>
<Strip Height="180.000" Width="180.000"/>
<Head_A x_Offset="0.000" y_Offset="0.000" Angle="0.000"/>
<Head_B x_Offset="0.000" y_Offset="0.000" Angle="0.000"/>

</MatrixInfoFile>
Meaning of
the <MarixInfoFile> Designation of the file
parameter
<Project>
Binning Name and path of the binning file for the matrix segmentation
Vlf Name of the Vlf file
<Matrix
x_Offset Defines the offset for the x direction
y_Pitch Distance of marking in x direction
No_of_columns Number of columns per group
Distance_colum
Distance between the groups in x direction
n_groups
No_of_column_
Number of groups in x direction
groups
y_Offset Defines the offset for the y direction
y_Pitch Distance of marking in y direction
No_of_rows Number of rows per group
Distance_row_g
Distance between the groups in y direction
roups
No_of_row_gro
Number of groups in y direction
ups
y_Offset Defines the offset for the y direction
<Strip>
Height Height of the strip
Width Width of the strip
<Head_A>
x_Offset X offset from Head A
y_Offset Y offset from head A
Angle Angle offset from Head A
<Head_B>
x_Offset X offset from Head B
y_Offset Y offset from head B
Angle Angle offset from Head B
Table 2-51

3.22 Laser status
Reads the laser status

Request 0 No data
Response Formatting the laser
"G1" + "B1" + "B2" + "G2" status:
G1: Result of the TLV request: LSB is on the right in
0: Æ Command executed correctly each case in the binary
string
error code)
request for the active • Is added on to the
communication interface TLV Response
4: Æ Invalid TLV LENGTH of the when the result of
response for the active the
communication interface TLV request is "1".
B1: Bit 7- 0
Number of Bit 7: 1Æ Laser has a malfunction
bytes in Bit 6: 1Æ Warning laser has
the TLV responded
20261
Value Bit 5: 0Æ Laser stable (diode current in
the band)
Bit 4: 1Æ Beam expander in position
Bit 3: 1Æ Shutter is open
Bit 2: 1Æ Safety circuit is closed
Bit 1: 1Æ Laser is ready
Bit 0: 1Æ Beam source is on
B2: Bit 15 – 8
Bit 15: 1Æ Control is on
Bit 14: 1Æ Heating period laser is on
Bit 13: 1Æ EMERGENCY SHUTDOWN
circuit is closed
Bit 12: 1Æ Key switch laser is closed.
Bit 11: 1Æ Switch of control manually
activated
Bit 10: 1Æ Q-Switch trigger is on
Bit 9: 1Æ Laser warning lamp is on
Bit 8: 1Æ Pilot laser is on
Table 2-52
Example: Laser status query
TAG LENGTH VALUE
25 4F 00 00 00 00 00 00
Response 20261 20 "0" + "00001111" + "00011000"
25 4F 00 00 14 00 00 00 30 00 30 30 30 30 31 31 31 31 00 30 30 30 31 31 30 30 30 00
Table 2-53

3.23 Last error
Reads the error number, the short error text, the date and the time of day of the last error to occur at the laser
Request 0 No data
Response Formatting of the error
"G1" + "T1" + "T2" + "T3" + "T4" + "G2" number:
G1: Result of the TLV request: "XXYYZZZZ" (e.g.
0: Æ Command executed correctly "53011234") with:
executed (see extended XX = Error identification
error code) as HEX number
YY = Error number as
3: Æ Invalid TLV LENGTH of the HEX number
Number of request for the active ZZZZ = Error code as
bytes in communication interface HEX number
20262 the TLV 4: Æ Invalid TLV LENGTH of the
Value response for the active Extended error code:
T1: Error number • Is added on to the
TLV Response
T2: Short error text when the result of
T3: Error date the TLV Request is
"1".
T4: Error time
Table 2-54
Example: Read the last error

TAG LENGTH VALUE
26 4F 00 00 0000 00 00
Response 20262 46 "0" + "53011234" + "Short error text" + "01.01.2001" + "19:30:00"
30 00 35 33 30 31 31 32 33 34 00 46 65 68 6C 65 72 6B 75 72 7A 74
26 4F 00 00 2E 00 00 00 65 78 74 00 30 312E 30 31 2E 32 30 30 31 00 31 39 3A 33 30 3A 30
30 00
Table 2-55

3.24 Short error/warning text
Reads the short text for the assigned error/warning number

Request Formatting of the
"T1" error/warning number:
T: Error/warning number "XXYYZZZZ" (e.g.
Number of "53011234") with:
bytes in
the TLV XX = Error identification as
Value HEX number
YY = Error number as HEX

number
ZZZZ = Error/warning code
as HEX number
"G1" + "T" + "G2"
20263 G1: Result of the TLV request: • Is added on to the TLV
0: Æ Command executed correctly Response when the
1: Æ Command could not be result of the
Number of executed (see extended TLV Request is "1".
bytes in error code)
the TLV 3: Æ Invalid TLV LENGTH of the
Value request for the active
response for the active
T: Short error text
Table 2-56
Example: Reads the short text for the assigned

error/warning number "53011234"
TAG LENGTH VALUE
Request 20263 9 "53011234"
27 4F 00 00 09 00 00 00 35 33 30 31 31 32 33 34 00
Response 20263 37 "0" + "Short text for error number 53011234"
30 00 4B 75 72 7A 74 65 78 74 20 7A 75 72 20 46 65 68 6C 65 72
27 4F 00 00 25 00 00 00
6E 75 6D 6D 65 7220 35 33 30 31 31 32 33 34 00
Table 2-57

3.25 Last warning
Reads the warning number, the short warning text, the date and the time of day of the last warning to appear
at the laser
Request 0 No data
Response Formatting of the

"G1" + "T1" + "T2" + "T3" + "T4" + "G2" warning number:
G1: Result of the TLV request: "XXYYZZZZ"
0: Æ Command executed correctly (e.g. "53011234") with:
XX = Error identification
executed (see extended as HEX number
error code) YY = Error number as
HEX number
Number of 3: Æ Invalid TLV LENGTH of the ZZZZ = Warning code
bytes in request for the active as HEX number
20264
the TLV communication interface
Value Æ Extended error code:
4: Invalid TLV LENGTH of the
communication interface • Is added on to the
T1: Warning number TLV Response
when the
T2: Short warning text result of the TLV
T3: Warning date request is "1".
T4: Warning time
Table 2-58
Example: Reads the last warning

TAG LENGTH VALUE
28 4F 00 00 00 00 00 00
Response 20264 48 "0" + "53011234" + "Short warning text" + "01.01.2001" + "19:30:00"
30 00 35 33 30 31 31 32 33 34 00 57 61 72 6E 75 72 67 73 6B 75 72
28 4F 00 00 30 00 00 00 7A 74 65 78 74 0030 31 2E 30 31 2E 32 30 30 31 00 31 39 3A 33 30
3A 30 30 00
Table 2-59

3.26 Laser
Activates/deactivates the laser

Request 2
"G"
G: Status of the laser:
0: Æ Laser off
1: Æ Laser on

"G1" + "G2"
• Is added on to the
G1: Result of the TLV request: TLV Response
20281 0: Æ Command executed correctly when the
Number of result of the TLV
bytes in 1: Æ Command could not be
executed (see extended request is "1".
the TLV
Value error code)
Table 2-60
Example: Activate the laser

TAG LENGTH VALUE
Request 20281 2 "1"
39 4F 00 00 02 00 00 00 31 00
39 4F 00 00 02 00 00 00 30 00
Table 2-61

3.27 Q-switch
Activates the Q-switch for operation as an OEM beam source without an RTC card
Request 2 If no RTC card is present
"G" in the system (TM6000
beam source without PC),
G: Status of the Q-switch: use this command.
0: Æ Q-switch off Otherwise use command
20284.
1: Æ Q-switch on
At this command, the Q-

switch is activated via the
control blank CIP/CMU.
The desired laser
parameters (frequency,
pulse amplitude, power
specification) must be
preset via the TAGs
20285, 20286 and 20287
20282
"G1" + "G2"
0: Æ Command executed correctly when the
the TLV
Value error code)
Table 2-62
Example: Switch on Q-switch

TAG LENGTH VALUE
Request 20282 2 "1"
3A 4F 00 00 02 00 00 00 31 00
3A 4F 00 00 02 00 00 00 30 00
Table 2-63

3.28 Initialization of beam monitoring by the
scanner
Preparation of a list of commands for the activation/deactivation of the beam source through the scanner with
the assigned laser power and frequency for operation as the OEM beam source
Request Activation of the beam
"G1" + "G2" + "D1" + "D2" + "G3" source through:
G1: Laser power in % TLV command "Scanner
beam control" or
G2: Frequency in Hz
Restart_mark input of
D1: X-Position in the current marking the digital interface
field in mm
Deactivation of the
D2: Y position in the current marking beam source through:
field in mm
TLV command "Scanner
Number of G3: Pulse length of the Q-switch signal beam control" or
bytes in in us Abort_mark input of the
the TLV
digital interface
Value
The following conditions
must be fulfilled:
No marking procedure is
allowed to be active and
the beam source
(20284) must not be
20283 active.
When an RTC2 card is

used,
"Variable polygon delay"
must be deactivated.
"G1" + "G2"
0: Æ Command executed correctly
when the result of
Number of the TLV Request is
bytes in 1: Æ Command could not be "1".
Value error code)
Table 2-64

Example: Preparing the list of commands:
-> Laser power = 85%/-> Frequency = 10 kHz
-> X value = 25.125 mm/-> Y value = 60.00 mm
-> Pulse width of the Q-switch signal = 5 us
TAG LENGTH VALUE
Request 20283 24 "85" + "10000" + "25.125" + "60.00" + "5"
38 35 00 31 30 30 30 30 00 32 35 2E 31 32 35 00 36 30 2E 30 30 00 35
3B 4F 00 00 18 00 00 00
00
3B 4F 00 00 02 00 00 00 30 00
Table 2-65

3.29 Scanner beam monitoring
Activates/deactivates the beam source with the adjusted laser power and frequency by means of the scanner
in operation as the OEM beam source
Request 2 The following conditions
"G" must be fulfilled:
G: Status of the beam source: The list of commands of
0: Æ Beam source off the scanner must be
have been initialized in
1: Æ Beam source on advance by means of the
TLV Command
"Initialization of beam
monitoring
by the scanner"
The "Laser is ready"

laser status signal must
be active
When an RTC2 card is

used, "Variables
Polygon Delay" must be
deactivated.
20284
As OEM beam source
the "Mark active"
output is not controlled
in the laser status.

"G1" + "G2"
when the
bytes in 1: Æ Command could not be request is "1".
Value error code)
Table 2-66
Example: Switch on the beam source

TAG LENGTH VALUE
Request 20284 2 "1"
3C 4F 00 00 02 00 00 00 31 00
3C 4F 00 00 02 00 00 00 30 00
Table 2-67

3.30 Laser power
Sets the laser power for operation as an OEM beam source

Request Number of
bytes in "G"
the TLV
G: Power in %
Value
"G1" + "G2"
G1: Result of the TLV request: TLV Response when
the
result of the TLV
20285 1: Æ Command could not be request is "1".
the TLV
Table 2-68
Example: Set laser power to 90%
TAG LENGTH VALUE
Request 20285 3 "90"
3D 4F 00 00 03 00 00 00 39 30 00
3D 4F 00 00 02 00 00 00 30 00
Table 2-69

3.31 Frequency
Sets the laser frequency for operation as an OEM beam source

Request Number of
bytes in "G"
the TLV
G: Frequency in Hz
Value
"G1" + "G2"
the result of the
TLV request is "1".
the TLV
Table 2-70
Example: Set frequency to 60,000 Hz
TAG LENGTH VALUE
Request 20286 6 "60000"
3E 4F 00 00 06 00 00 00 36 30 30 30 30 00
3E 4F 00 00 02 00 00 00 30 00
Table 2-71

3.32 Defocusing
Sets the defocusing for operation as an OEM beam source

Request Number of
bytes in "D"
the TLV
D: Defocusing in mm
Value
"G1" + "G2"
the result of the
Number of TLV request is "1".
20287 bytes in 1: Æ Command could not be
Value error code)
Table 2-72
Example: Set the defocusing to –3 mm

TAG LENGTH VALUE
Request 20287 3 "-3"
3F 4F 00 00 03 00 00 00 2D 33 00
3F 4F 00 00 02 00 00 00 32 00
Table 2-73

3.33 Set laser parameters offsets
Sets the general laser parameter offsets of power, frequency, marking speed, defocus and pulse amplitude
Request Number of
bytes in "D1" + "D2" + "D3"+ "D4" + "D5"
the TLV
D1: Offset power in %
Value
D2: Offset frequency in Hz
D3: Offset speed in mm/s
D4: Offset defocus in mm
D5: Offset pulse amplitude in μs
"G1" + "G2"
• Is added to the
0: Æ Command executed correctly when the result of
the TLV request
error code)
20288 1: Æ Lower limit for offset power
too low
Number of
2: Æ Upper limit for offset power
bytes in
too high
the TLV
Value 3: Æ Lower limit for offset
frequency too low
4: Æ Upper limit for offset
frequency too high
5: Æ Lower limit for the offset
speed is too low
6: Æ Upper limit for the offset
speed is too high
7: Æ Lower limit for offset
Defocus too small
Defocus too large
9: Æ Lower limit for offset
Pulse amplitude too small
Pulse amplitude too large
Table 2-74

Example: Set the laser parameter offset to -10% power,
+5000 Hz frequency, +5 mm/s speed, +3 mm
defocus and +2 μs pulse amplitude
TAG LENGTH VALUE
Request 20288 15 "-10" + "5000" + "5" + "3" + "2"
40 4F 00 00 0F 00 00 00 2D 31 30 00 35 30 30 30 00 35 00 33 00 32 00
40 4F 00 00 02 00 00 00 30 00
Table 2-75
3.34 Switching on or switching off "Marking

on the fly"
Switches on or switches off Marking on the fly.

Request 2
"G"
G: Status "Marking on the fly":
0: Æ "Marking on the fly" not
activated
1: Æ "Marking on the fly" activated
"G1" + "G2"
the result of the
20289 TLV request is "1".
Number of 1: Æ Command could not be
bytes in executed (see extended
the TLV error code)
Value
> 0: Æ "Marking on the fly" option not
activated.
Table 2-76
Example: Switching on "Marking on the fly"
TAG LENGTH VALUE

Request 20289 2 "1"
41 4F 00 00 02 00 00 00 31 00
41 4F 00 00 02 00 00 00 30 00
Table 2-77

3.35 Switching on or switching off the
retrigger mode
Switches on or switches off the retrigger mode.

Request 2
"G"
G: Status "Marking on the fly": In the retrigger mode,
0: Æ Retrigger mode switched off the "Mark active"
output is not controlled
1: Æ Retrigger mode switched on
in the laser status.

"G1" + "G2"
20290 the result of the
Value error code)
Table 2-78
Example: Switching on the retrigger mode
TAG LENGTH VALUE

Request 20290 2 "1"
42 4F 00 00 02 00 00 00 31 00
42 4F 00 00 02 00 00 00 30 00
Table 2-79

4. TLV commands for Mechanics
SW module
4.1 Reference all axes
References all axes

Request
"G"
G: Referencing mode:
2 0: Æ Start referencing without
waiting for the end
1: Æ Start referencing and wait for
the end
"G1" + "G2"
Response when the
0: Æ Command executed correctly result of the TLV request
20101 executed (see extended
error code)
Number 2: Æ Erroneous TLV VALUE
of bytes
in the 3: Æ Invalid TLV LENGTH of the
TLV request for the active
Value communication interface
= -1: Æ Command not completed
> =1: Æ Internal error
Note: If G1:1 and G2:1, then the procedure is

not yet completed and the Command must be
repeated until G1:0
Table 2-80
Example: Referencing all axes (with waiting for the end of

the referencing)
TAG LENGTH VALUE
Request 20101 2 "1"
85 4E 00
02 00 00 00 31 00
00
85 4E 00 30 00
02 00 00 00
00
Table 2-81

4.2 Reference axis
References the assigned axis

Request
"G1" + "G2"
G1: Number of the axes to be
referenced:
1: Æ Z axis
2: Æ X axis
3: Æ A axis
4 4: Æ Y axis
5: Æ C axis
7: Æ D axis
G2: Referencing mode:
0: Æ Start referencing without
waiting for the end
1: Æ Start referencing and wait for
the end
Response 20102 Extended error code:
"G1" + "G2"
Response when the
error code)
of bytes

repeated until G1:0
Table 2-82
Example: Referencing the X axis (with waiting for the end of

the referencing)
TAG LENGTH VALUE
Request 20102 4 "2" + "1"
86 4E 00 00 04 00 00 00 32 00 31 00
86 4E 00 00 02 00 00 00 30 00
Table 2-83

4.3 Reference two axes
References the assigned axis

Request Referencing is always
"G1" + "G2" carried out without
G1: Number of the axes to be waiting.
referenced:
This command is
1: Æ Z axis
available for:
3: Æ A axis ⎯ TMS7000/VWS1200
4 4: Æ Y axis ⎯ TMS5000 NEW.
8: Æ S axis
G2: Number of the axes to be
referenced:
2: Æ X axis
5: Æ C axis
6: Æ T axis
"G1" + "G2"
20105 • Is added on to the TLV
G1: Result of the TLV request: Response when the
is "1".
error code)
of bytes

repeated until G1:0
Table 2-84
Example: Referencing the X axis and the Y axis

TAG LENGTH VALUE
Request 20105 4 "2" + "4"
89 4E 00 00 04 00 00 00 32 00 34 00
89 4E 00 00 02 00 00 00 30 00
Table 2-85

4.4 Move axis
Moves the assigned axis

Request
"G1" + "D" + "G2"
G1: Number of the axes to be moved:
1: Æ Z axis
2: Æ X axis
3: Æ A axis
4: Æ Y axis
Number 1
5: Æ C axis
of bytes 1
in the 6: Æ T axis : For rotation door
TLV 7: Æ D axis Use command 20123
Value
8: Æ S axis
D: New absolute position of the axis
in mm
G2: Number of the axes to be moved:
0: Æ Start movement without
waiting for the end
1: Æ Start movement and wait for
20103 the end
"G1" + "G2"
result of the TLV
request is "1".
error code)
of bytes

repeated until G1:0
Table 2-86

Example: Moving Z axis to absolute position 72.25 (waiting
for the end of the move)
TAG LENGTH VALUE
Request 20103 10 "1" + "72.25" + "1"
87 4E 00 00 0A 00 00 00 31 00 37 32 2E 32 35 00 31 00
87 4E 00 00 02 00 00 00 30 00
Table 2-87

4.5 Move two axes
Moves the assigned axis

Request Movement of the axes is
"G1" + "D1" + "G2" + "D2" always carried out
G1: Number of the axes to be moved: without waiting.
1: Æ Z axis
This command is
3: Æ A axis available for:
4: Æ Y axis ⎯ TMS7000/VWS1200
Number 8: Æ S axis ⎯ TMS5000 NEU
of bytes D1: New absolute position of the axis
in the in mm Important note:
TLV The numbers of the
Value G2: Number of the axes to be moved:
assigned axes for G1
2: Æ X axis and G2 must correspond
1
5: Æ C axis with the numbers in the
6: Æ T axis left table.
D2: New absolute position of the axis 1
in mm
: For rotation door
Use command 20123
20106 .
Response when the
result of the TLV
1: Æ Command could not be request is "1".
error code)
of bytes 3: Æ Invalid TLV LENGTH of the
in the request for the active
TLV communication interface
Value

repeated until G1:0
Table 2-88
Example: Move Z axis to absolute position 72.25 and Y axis

to absolute position 12.30
TAG LENGTH VALUE
Request 20106 16 "1" + "72.25" + "4" + "12.30"
8A 4E 00 00 10 00 00 00 31 00 37 32 2E 32 35 00 34 00 31 32 2E 33 30 00
8A 4E 00 00 02 00 00 00 30 00
Table 2-89

4.6 Axis position
Reads the absolute position of the assigned axis

Request
"G"
G: Number of the axes to be read:
1: Æ Z axis
2: Æ X axis
2 3: Æ A axis
4: Æ Y axis
1
5: Æ C axis 1
: For rotation door
6: Æ T axis Use command 20124
7: Æ D axis
8: Æ S axis
20104 "G1" + "D" + "G2" Is added on to the TLV
result of the
TLV Request is "1".
Number executed (see extended
error code)
of bytes
in the 2: Æ Erroneous TLV VALUE
TLV 3: Æ Invalid TLV LENGTH of the
D: Absolute position of the axis
in mm
Table 2-90
Example: Read absolute position of the Y axis

(stands at 12.34 mm)
TAG LENGTH VALUE
Request 20104 2 "4"
88 4E 00 00 02 00 00 00 34 00
Response 20104 8 "0" + "12.34"
88 4E 00 00 08 00 00 00 30 00 31 32 2E 33 34 00
Table 2-91

4.7 Recognize focal position
Defines the position starting with which the focus is to be found

Request
"D" + "G"
Number D: Defining the position for the
of bytes search
in the
G: Waiting for the command to be
TLV
executed
Value
0: Æ Do not wait
1: Æ Wait
"G1" + "G2"
20107 Response when the
0: Æ Command executed correctly result of the TLV
of bytes error code)
in the
TLV
Value 3: Æ Invalid TLV LENGTH of the
Table 2-92
Example: Moves focal point into position

(stands at 12.3 mm)
TAG LENGTH VALUE
Request 20107 7 "12.3" + "1"
8B 4E 00 00 07 00 00 00 31 32 2E 33 00 31 00
8B 4E 00 00 02 00 00 00 30 00
Table 2-93

4.8 Set segment offset for axes
Sets the axes offsets for the A/X/Y/Z axes

Request
"D1" + "D2" + "D3" + "D4" The A offset is applied to
D1: Offset A axis the cylinder.
Number
D2: Offset X axis
of bytes The X offset and Y offset
in the D3: Offset Y axis are applied to the x/y free
TLV D4: Offset Z axis rectangle.
Value
The Z offset is applied
only on 3D segmented
files.
20108 "G1" + "G2"
is "1".
Number 1: Æ Command could not be
of bytes executed (see extended
in the error code)
TLV 2: Æ Erroneous TLV VALUE
Value
Table 2-94
Example: Sets the segment offsets for the A axis to 2.3 mm,
for the X axis to 1.4 mm
TAG LENGTH VALUE
Request 20108 12 "2.3" + "1.4" + "0" + "0
8C 4E 00 00 0C 00 00 00 32 2E 33 00 31 2E 34 00 30 00 30 00
8C 4E 00 00 02 00 00 00 30 00
Table 2-95

4.9 Open door
Opens the door of the workstation

Request Limitations:
"G1" + "G2" Door positions 2 to 5
G1: Command execution mode are only available with
TMS7000/VWS 1200
0: Æ Start opening without
waiting for the end Explanation
1: Æ Start opening and wait for Door position "Pos 1"
the end corresponds to the
upper end position
G2: Door position (maximum opening
1: Æ Open door up to Pos 1 height)
2
Æ
Door position "Pos 5"
2: Open door up to Pos 2
corresponds to the
3: Æ Open door up to Pos 3 lower end position
4: Æ Open door up to Pos 4 (minimum opening
height)
5: Æ Open door up to Pos 5 The intermediate
positions "Pos 2" to
"Pos 3" are spaced
evenly between the
door positions "Pos 1"
20121 and "Pos 5"
"G1" + "G2"
request is "1".
error code)
Number of 2: Æ Erroneous TLV VALUE
bytes in 3: Æ Invalid TLV LENGTH of the
the TLV request for the active

repeated until G1:0
Table 2-96
Example: Opening the door of the workstation up to the upper end
position (waiting until the door has been completely
opened)
TAG LENGTH VALUE
Request 20121 4 "1" + "1"
99 4E 00 00 04 00 00 00 31 00 31 00
99 4E 00 00 02 00 00 00 30 00
Table 2-97

4.10 Close door
Closes the door of the workstation

Request Limitations:
"G"
With the VWS 1200, the
G: Command execution mode
door can only be closed
2 0: Æ Start closing without waiting with this command if the
for the end "Close door by software"
1: Æ Start closing and wait for the option has been set in
end Setup.
"G1" + "G2"
the result of the
TLV request is "1".
error code)
of bytes

repeated until G1:0
Table 2-98
Example: Close the door of the workstation down to the

lower end position (waiting until the door is
completely closed)
TAG LENGTH VALUE
Request 20122 2 "1"
9A 4E 00 00 02 00 00 00 31 00
9A 4E 00 00 02 00 00 00 30 00
Table 2-99

4.11 Rotate rotation door
Rotates the rotation door of the workstation

Request
"G1" + "G2"
G1: Direction of rotation
0: Æ Next position
1: Æ Left (counter-clockwise)
4 2: Æ Right (clockwise)
G2: Command execution mode
1: Æ Start rotating without waiting
for the end
2: Æ Start rotating and wait for the
end
"G1" + "G2"
20123
0: Æ Command executed correctly result of the
TLV Request is "1".
error code)
of bytes

repeated until G1:0
Table 2-100
Example: Rotating rotation door of the workstation clockwise

(waiting for the end of the rotating process)
TAG LENGTH VALUE
Request 20123 4 "2" + "1"
9B 4E 00 00 04 00 00 00 32 00 31 00
9B 4E 00 00 02 00 00 00 30 00
Table 2-101

4.12 Status rotating door
Reads the status of the rotation door

Request 0 No data
"G1" + "G2" + "G3"
0: Æ Command executed correctly the result of the
TLV Request is "1".
error code)
Number
20124 of bytes
in the communication interface
TLV
Value G2: Rotating door status:
1: Æ Right (clockwise)
2: Æ Left (counter-clockwise)
G3: Absolute position of the axis

in mm
Table 2-102
Example: Read status of the rotation door

TAG LENGTH VALUE
9C 4E 00 00 00 00 00 00
Response 20124 4 "0" + "2"
9C 4E 00 00 04 00 00 00 30 00 32 00
Table 2-103

4.13 Move foil module
Creates a feed of the foil in the foil module

Request
"D" + "G"
Number D: Feed for the foil module in mm

of bytes G: Command execution mode
in the
0: Æ Start moving without waiting
TLV
for the end
Value
1: Æ Start moving and wait for the
end

"G1" + "G2"
result of the
20141 TLV Request is "1".
error code)
of bytes

repeated until G1:0
Table 2-104
Example: Moving foil module by 43.21 mm (waiting for the

end of the move)
TAG LENGTH VALUE
Request 20141 8 "43.21" + "1"
AD 4E 00 00 08 00 00 00 34 33 2E 32 31 00 31 00
AD 4E 00 00 02 00 00 00 30 00
Table 2-105

4.14 Edge-detection
Activates/deactivates edge detection for the foil module

Request
"G"
G: New status for the edge-
2 detection
0: Æ Deactivate edge-detection
1: Æ Activate edge-detection

"G1" + "G2"
20142 result of the
TLV Request is "1".
Number 1: Æ Command could not be
in the error code)
Value
Table 2-106
Example: Activate edge-detection for the foil module

TAG LENGTH VALUE
Request 20142 2 "1"
AE 4E 00 00 02 00 00 00 31 00
AE 4E 00 00 02 00 00 00 30 00
Table 2-107

4.15 Mechanics status
Reads the status of the mechanics module

LENG
TAG TH VALUE Remark
Request 0 No data
Response "G1" + "G2" + "G3" The PLC is not
G1: Result of the TLV request: always able to
display the
0: Æ Command executed correctly status correctly
3: Æ Invalid TLV LENGTH of the at the
request for the active beginning. In
communication interface case of error
G2: Status of the mechanics module: (G2 <> 0), the
0: Æ Status OK status should
continue to be
1: Æ Status not OK
queried until G3
G3: Detail error of the axis: returns the
1: Æ X axis not referenced same value.
2: Æ X axis is at the reference
switch Please
observe:
3: Æ X axis has traveled over the
switch opposite the reference After switching
switch on the system,
4: Æ X axis has reached the
the 20161
position telegram must
be used to read
5: Æ X axis cumulative malfunction
the error
6: Æ Y axis is not referenced memory of the
7: Æ Y axis is at the reference system PLC. In
20161 switch certain cases,
8: Æ Y axis has traveled over the the telegram
switch opposite to the must be run
reference switch more than once
9: Æ Y axis has reached the until a valid
position status is
10: Æ Y axis cumulative malfunction confirmed.
If command
11: Æ Z axis is not referenced
20101 is issued
12: Æ Z axis is at the reference after that, the
switch entire TMS and
13: Æ Z axis has traveled over the both rotary
switch opposite the reference axes are
switch
referenced
14: Æ Z axis has reached the successfully.
position
15: Æ Z axis, cumulative malfunction
16: Æ A axis not referenced
17: Æ A axis is on the reference
switch
18: Æ A axis has reached the
position
19: Æ A axis cumulative malfunction
20: Æ C axis is not referenced

21: Æ C axis is on the reference

switch
22: Æ C axis has reached the
position
23: Æ C axis cumulative malfunction
24: Æ T axis is not referenced
25: Æ T axis is at the reference
switch
26: Æ T axis has traveled over the
switch opposite the reference
switch
27: Æ T axis has reached position
28: Æ T axis cumulative malfunction
29: Æ Emergency Off switch actuated
30: Æ Z axis not referenced
successfully
Numb
er of 31: Æ Z axis position invalid
bytes 32: Æ Lifting table at an end stop
in the Æ
33: Parity error
TLV
Value 34: Æ Command not interpretable
35: Æ Unable to close door
36: Æ A axis not referenced
Response successfully
37: Æ A axis position is invalid
38: Æ X axis not referenced
successfully
39: Æ X axis position is invalid
40: Æ Rotary table error
41: Æ S axis not referenced
42: Æ S axis is at the reference
switch
43: Æ S axis has traveled over the
switch opposite the reference
switch
44: Æ S axis has reached position
45: Æ S axis cumulative malfunction

Response
TMS5000 NEW (from 12.12.2008 onwards)
TMS5000Neu
G3: Detail error of the axis: Reference to:
Mech_VWS_5100.
General error codes: dll
1: Æ X axis not referenced
6: Æ Y axis is not referenced
11: Æ Z axis is not referenced
16: Æ A axis is not referenced
24: Æ T axis is not referenced
100: Æ All axis conditions OK
106: Æ Z axis EMERGENCY STOP situation
107: Æ X axis detects EMERGENCY STOP situation
108: Æ Y axis detects EMERGENCY STOP situation
109: Æ A axis detects EMERGENCY STOP situation
110: Æ T axis detects EMERGENCY STOP situation
111: Æ No access to host drive
112: Æ No access to Z-drive
113: Æ No access to X-drive
114: Æ No access to Y-drive
115: Æ No access to A-drive
Axis-specific error codes:
117: Æ X axis has approached the positive limit switch
118: Æ X axis has approached the negative limit switch
119: Æ X axis Power OFF

120: Æ X axis error
124: Æ Y axis has approached the positive limit switch
125: Æ Y axis has approached the negative limit switch
126: Æ Y axis Power OFF

127: Æ Y axis error
131: Æ Z axis has approached the positive limit switch
132: Æ Z axis has approached the negative limit switch
133: Æ Z axis Power OFF

134: Æ Z axis error
139: Æ A axis has approached the negative limit switch
140: Æ A axis Power OFF

141: Æ A axis error
146: Æ T axis has approached the negative limit switch
147: Æ T axis Power OFF

148: Æ T axis error
Table 2-108

Example: Read the status of the Mechanics module -
> Mechanics module has error (Z axis not
referenced)
TAG LENGTH VALUE
C1 4E 00 00 00 00 00 00
Response 20161 7 "0" + "1"+ "11"
C1 4E 00 00 07 00 00 00 30 00 31 00 31 31 00
Table 2-109
4.16 Mechanics error


Response
TMS5000/VWS800
G1 + "G2" + "G3" + "G4" + "G5" + "G6" + "G7"

The selected
mechanical component
G1: Result of the TLV request in the configuration is
0: Æ Command executed correctly the
1: Æ Command could not be Mech_VWS_800.dll
executed
G2: General message G2 – G7 can also be a
0: Æ No error combination of the bit
1: Æ Emergency Off switch values, as for example
actuated when "1" and "16" are
2: Æ Parity error set with G2, then the
4: Æ Command not interpretable value is "17".
8: Æ Unable to close door
16: Æ Rotary indexing table not in
position After an Emergency Off
G3: Z axis on TMS5000 and
Number of 0: Æ No error TMS5000R the status
bytes in 1: Æ No referenced of the axes is 0.
the TLV
2: Æ Reference run was not
Value
successful
4: Æ Value for position invalid Comment:
8: Æ Lifting table hitting against a When the Emergency
stop Off was activated and
G4: A axis (rotary axis) then released again,
0: Æ No error
the status of the axes is
1: Æ No referenced
0.
successful Therefore, a reference
4: Æ Value for position invalid run must be performed
after activation of an
G5: X axis
Emergency Off.
0: Æ No error
1: Æ No referenced
successful
4: Æ Value for position invalid
G6: =0
G7: =0

Response
TMS7000/VWS1200
G1 + "G2" + "G3" + "G4" + "G5" + "G6" + "G7"

The selected
mechanical component
G1: Result of the TLV request in the configuration is
1: Æ Command could not be Mech_VWS_1200.dll
executed
G2: T axis
1: Æ No referenced
2: Æ Not active
4: Æ Reference switch active
8: Æ Limit switch active G2 – G7 can also be a
16: Æ Position ok combination of the bit
32: Æ General error values, as for example
G3: Z axis when "1" and "16" are
set with G2, then the
1: Æ No referenced
value is "17".
2: Æ Not active
8: Æ Limit switch active
16: Æ Position ok
32: Æ General error
G4: A axis (rotary axis)
1: Æ No referenced
Number of 2: Æ Not active
bytes in 4: Æ Reference switch active
the TLV 8: Æ Limit switch active
Value
16: Æ Position ok
G5: X axis
1: Æ No referenced
2: Æ Not active
16: Æ Position ok
G6: C axis
1: Æ No referenced
2: Æ Not active
16: Æ Position ok
G7: Y axis
1: Æ No referenced
2: Æ Not active
16: Æ Position ok

Response
TMS5000 NEW (from 12.12.2008 onwards)
G1"+"G2"+"G3"+"G4"+"G5"+"G6"+"G7"
G1: Result of the TLV request
correctly
executed G2 – G7 can also be a
G2: T axis combination of the bit
0: Æ OK status: no error values, as for example
1: Æ No host communication
2: Æ Emergency stop pressed
when "1" and "16" are set
4: Æ No access to the drive with G2, then the value is
8: Æ No referenced "17".
16: Æ Positive limit switch is active
32: Æ Negative limit switch is
active
The selected mechanical
64: Æ Drive error component in the
128: Æ Power Off drive configuration is the
G3: Z axis Mech_VWS_5100.dll
0: Æ OK status: no error
4: Æ No access to the drive Comment 1:
8: Æ No referenced All the active axes signal
16: Æ Positive limit switch is active "1" as the error code if
32: Æ Negative limit switch is there is no existing host
active
64: Æ Drive error communication.
Number of 128: Æ Power Off drive
bytes in 256: Æ Positional limit reached Comment 2:
the TLV G4: A axis (rotary axis) In case of the "Drive error"
Value 0: OK status: no error error, 128+64+8=200 is
1: Æ No host communication always set as error code
4: Æ No access to the drive for "Power OFF" and "not
8: Æ No referenced referenced".
64: Æ Drive error
128: Æ Power Off drive
Comment 3:
G5: X axis
An axis not activated in
TruTopsMark always
2: Æ Emergency stop pressed confirms 0 as the error
4: Æ No access to the drive code.
8: Æ No referenced
Comment 4:
active There is no point in
64: Æ Drive error comparing, for example,
128: Æ Power Off drive an EMERGENCY STOP
256: Æ Positional limit reached
always with a whole-
G6: C axis
number type. It is better to
G7: Y axis
filter out non-relevant
information bit by bit
2: Æ Emergency stop pressed and/or using an arithmetic
4: Æ No access to the drive expression.
8: Æ No referenced
active
64: Æ Drive error
128: Æ Power Off drive
256: Æ Positional limit reached
Table 2-110

Example: Read the status of the Mechanics module -> Z
axis has not been referenced
TAG LENGTH VALUE
C2 4E 00 00 00 00 00 00
Response 20162 14 "0" + "0" + "1" + "0" + "0" + "0" + "0"
C2 4E 00 00 0E 00 00 00 30 00 30 00 31 00 30 00 30 00 30 00 30 00
Table 2-111
4.17 Moving axes continuously (from TTM

2.7)
Moves the axis continuously in one direction
Request The following comments
"G1" + "G2" apply to all stations with
G1: Axis no. inching mode and stop
mode.
1: Æ Z axis
2: Æ X axis Comment 1:
3: Æ
Move X, Y axis to
A axis
maximum or minimum
4: Æ Y axis position. The axis stops
G2: Direction of travel at this position.
0: Æ Negative
Comment 2:
20163 2 1: Æ Positive The Z axis must receive
a stop command
afterward (tag 20164) in
order for the brake to be
activated.
Comment 3:
The collision window

for the X, Z and A axes
is not taken into
consideration!

Moves the axis continuously in one direction
"G1" + "G2"
request is "1".
bytes in
the TLV 2: Æ Erroneous TLV VALUE
Table 2-112
Example: Moving the Z axis continuously in positive direction of
travel
TAG LENGTH VALUE
Request 20163 4 "1" + "1"
C3 4E 00 00 04 00 00 00 31 00 31 00
C3 4E 00 00 02 00 00 00 30 00
Table 2-113
4.18 Stop all axes (from TTM

2.7)
Stops all axis movement functions

Request
No data
Response
"G1" + "G2"
20164
the TLV
Table 2-114

Example: Stop all axes
TAG LENGTH VALUE
Request 20164 2
C3 4E 00 00 04 00 00 00 31 00 31 00
C3 4E 00 00 02 00 00 00 30 00
Table 2-115
4.19 Switch axis on or off
Switch axis on or off

Request "G1" + "G2" The axis mus be defined
G1: Designation of the axis on the work station.
1: Æ Z axis
2: Æ X axis
3: Æ A axis
4: Æ Y axis
5: Æ C axis
G2: Switch on or off
1 Æ On
0 Æ Off
Response 20165
"G1" + "G2"
the TLV
Table 2-116
Example: The A axis is switched on
TAG LENGTH VALUE
Request 20165 4 "3" + "1"
C3 4E 00 00 04 00 00 00 33 00 31 00
C3 4E 00 00 02 00 00 00 30 00
Table 2-117

5. TLV commands for the digital interface
5.1 Inputs of the digital interface
Reads all digital interface inputs

Request 0 No data
Response Limitation:
"G1" + "B1" + "B2" + "B3" + "G2"
The E1 to E9, E15 and
G1: Result of the TLV request: E16 inputs are used by
0: Æ Command executed correctly TruTops Mark® and are
thus unavailable.
error code) Formatting of the input
Number of information:
bytes in 3: Æ Invalid TLV LENGTH of the
20301 the TLV request for the active LSB is on the right in each
Value communication interface case in the binary string
response for the active Extended error code:
B1: Status of the E8 to E1 inputs • Is added on to the
TLV Response when
B2: Status of the E16 to E9 inputs the result of the
B3: Status of the E24 to E17 inputs TLV Request is "1".
Table 2-118
Example: Read all digital interface inputs

TAG LENGTH VALUE
4D 4F 00 00 00 00 00 00
Response 20301 29 "0" + "11001100" + "10101010" + "00001111"
30 00 31 31 30 30 31 31 30 30 00 31 30 31 30 31 30 31 30 00 30 30 30
4D 4F 00 00 1D 00 00 00
30 31 31 31 31 00
Table 2-119

5.2 X input of the digital interface
Reads the digital interface input X

Request Limitation:
"G"
The E1 to E9, E15 and
G: Æ Value range: 1 – 24 E16 inputs are used by
Number of
0: Assignment of the inputs TruTops Mark® and are
bytes in
thus
the TLV 1: Æ Input 1
unavailable.
Value :
:
24: Æ Input 24
"G1" + "G2" + "G3"
20302 0: Æ Command executed correctly the
1: Æ Command could not be result of the TLV
Number of
error code)
bytes in
the TLV 2: Æ Erroneous TLV VALUE
G2: Status of input X:
0: Æ Input is LOW
1: Æ Input is HIGH
Table 2-120
Example: Read input 13 of the digital interface

TAG LENGTH VALUE
Request 20302 3 "13"
4E 4F 00 00 03 00 00 00 31 33 00
Response 20302 4 "0" + "1"
4E 4F 00 00 04 00 00 00 30 00 31 00
Table 2-121

5.3 Digital interface outputs
Sets all digital interface outputs

Request 18 Limitation:
"B1" + "B2"
The A1 to A8 outputs are
B1: Status for the used by TruTops Mark®
A8 to A1 outputs and are thus unavailable.
B2: Status for the
Formatting the output
A16 to A9 outputs
information:
LSB is on the right in each

case in the binary string
"G1" + "G2"
20303 • Is added on to the
Value error code)
Table 2-122
Example: Set all digital interface outputs

TAG LENGTH VALUE
Request 20303 18 "11001100" + "1010101"
4F 4F 00 00 12 00 00 00 31 31 30 30 31 31 30 30 00 31 30 31 30 31 30 31 30 00
4F 4F 00 00 02 00 00 00 30 00
Table 2-123

5.4 X output of the digital interface
Sets the digital interface output X

Request Limitation:
"G1" + "G2"
Output to be set: The A1 to A8 outputs are
G1: used by TruTops Mark®
Æ Value range: 1 – 16 and are thus unavailable.
Number of
bytes in G2: Status of the output:
the TLV Arrangement of the
0: Æ Output is set to LOW
Value outputs:
1: Æ Output is set to HIGH
1 -> Output 1
: :
16 -> Output 16
20304 "G1" + "G2"
Value error code)
Table 2-124
Example: Set digital interface output 9 to HIGH

TAG LENGTH VALUE
Request 20304 4 "9" + "1"
50 4F 00 00 04 00 00 00 39 00 31 00
50 4F 00 00 02 00 00 00 30 00
Table 2-125

5.5 Inputs 1 to 8 of the digital interface
Reads the digital interface inputs 1 to 8

Request 0 No data Limitation:
The E1 to E8 inputs are

used by TruTops Mark®
and are thus unavailable.
Response Formatting of the input
"G1" + "B" + "G2" information:
G1: Result of the TLV request: LSB is on the right in the
0: Æ Command executed correctly binary string.
20305 Number of
executed (see extended Extended error code:
the TLV
Value error code)
• Is added to the
3: Æ Invalid TLV LENGTH of the TLV Response
request for the active when the result of
communication interface the TLV request
B: Status of the E8 to E1 inputs is "1".
Table 2-126
Example: Read digital interface inputs 1 to 8

TAG LENGTH VALUE
51 4F 00 00 00 00 00 00
Response 20305 11 "0" + "11001100"
51 4F 00 00 0B 00 00 00 30 00 31 31 30 30 31 31 30 30 00
Table 2-127


Request 0 No data Limitation:
The E9 to E16 inputs are

used by TruTops Mark®
and are thus unavailable.
.
20306 0: Æ Command executed correctly binary string.
Number of
executed (see extended Extended error code:
the TLV
Value error code)
3: Æ Invalid TLV LENGTH of the TLV Response when
request for the active the result of the
communication interface TLV request is "1".
B: Status of the E16 to E9 inputs
Table 2-128
Example: Read the inputs 9 to 16 of the digital interface

TAG LENGTH VALUE
52 4F 00 00 00 00 00 00
Response 20306 11 "0" + "10101010"
52 4F 00 00 0B 00 00 00 30 00 31 30 31 30 31 30 31 30 00
Table 2-129


Request 0 No data
0: Æ Command executed correctly binary string.
Number of
20307 Extended error code:
Value error code)
3: Æ Invalid TLV LENGTH of the • Is added on to the
request for the active TLV Response when
communication interface the result of the
B: Status of the E24 to E17 inputs TLV request is "1".
Table 2-130
Example: Read the 17 to 24 inputs of the digital interface

TAG LENGTH VALUE
53 4F 00 00 00 00 00 00
Response 20307 11 "0" + "00001111"
53 4F 00 00 0B 00 00 00 30 00 30 30 30 30 31 31 31 31 00
Table 2-131

5.8 Outputs 1 to 8 of the digital interface
Sets the digital interface outputs 1 to 8

Request 9 Limitation:
"B" The A1 to A8 outputs are
B: Status for the used by TruTops Mark®
A8 to A1 outputs and are thus unavailable.
Formatting of the output

information:
LSB is on the right in the

binary string.
20308 "G1" + "G2"
Number of TLV Request is " 1".
Value error code)
Table 2-132
Example: Set the 1 to 8 outputs of the digital interface

TAG LENGTH VALUE
Request 20308 9 "11001100"
54 4F 00 00 09 00 00 00 31 31 30 30 31 31 30 30 00
54 4F 00 00 02 00 00 00 30 00
Table 2-133

5.9 Outputs 9 to 16 of the digital interface
Sets the digital interface outputs 9 to 16

Request 9 Formatting of the output
"B" information:
LSB is on the right in the
B: Status for the
binary string.
A16 to A9 outputs
"G1" + "G2"
20309 Number of TLV Request is "1".
Value error code)
Table 2-134
Example: Set the 9 to 16 outputs of the X20 interface

TAG LENGTH VALUE
Request 20309 9 "10101010"
55 4F 00 00 09 00 00 00 31 30 31 30 31 30 31 30 00
55 4F 00 00 02 00 00 00 30 00
Table 2-135

6. TLV commands for the marking control
system
6.1 Load marking file

Loads and converts the assigned marking file
Request Explanations:
"T" If the file extension is not
specified, then the
T: Name of the marking file
standard extension, ".vlf",
(including directory)
is used
Number of If no directory is specified,
bytes in then the
the TLV directory of the most
Value recently loaded marking
file or the directory set by
the
TLV Command "Set
directory path"
will be used.
"G1" + "G2"
20401
error code)
Number of request for the active
bytes in communication interface
the TLV
Value G2: Extended error code:
1: Æ Marking file could not be
loaded
11: Æ No conversion,
empty variable ?
13: Æ Variable from text file: all data
processed
reached
Table 2-136
Example: Load and convert the "TEST.vlf" marking file

TAG LENGTH VALUE
Request 20401 5 "TEST"
B1 4F 00 00 05 00 00 00 54 45 53 54 00
B1 4F 00 00 02 00 00 00 30 00
Table 2-137

6.2 Convert marking file
Converts the loaded marking file

must be fulfilled:
Marking file must be
loaded
"G1" + "G2"
error code)
Number
20402 request for the active
of bytes
in the
TLV G2: Extended error code:
Value 1: Æ No marking file is loaded
variable?
processed
reached
Table 2-138
Example: Convert the loaded marking file

TAG LENGTH VALUE
B2 4F 00 00 00 00 00 00
B2 4F 00 00 02 00 00 00 30 00
Table 2-139

6.3 Mark marking file X
Loads, converts and marks the assigned marking file and waits until the marking procedure has been
completed
Request The following conditions
must be fulfilled:
"T"
The laser or the pilot laser
T: Name of the marking file
must be switched on.
(including directory)
Explanations:
If the file extension is not
Number specified, then the
of bytes standard extension ".vlf"
in the will be used
TLV If no directory is specified,
Value then the
directory of the most
recently loaded marking
file or the directory set by
the
TLV Command "Set
directory path"
will be used.
"G1" + "G2"
20403 0: Æ Command executed correctly the result of the
error code)
Number communication interface
of bytes G2: Extended error code:
in the
TLV
loaded
Value
11: Æ No conversion, empty variable
processed
reached
15: Æ Execution in case of activated
"Restart mark" is not allowed
Table 2-140

Example: Load, convert and mark the "TEST.vlf" marking
file
TAG LENGTH VALUE
Request 20403 5 "TEST"
B3 4F 00 00 05 00 00 00 54 45 53 54 00
B3 4F 00 00 02 00 00 00 30 00
Table 2-141
6.4 Set directory path
Sets the directory path from which marking files can be loaded
Request Number of After executing this TLV
bytes in command, the "Load
"T"
the TLV marking file" and/or "Mark
Value T: Directory name marking file X" commands
can be used without
specifying a directory path
for the assigned marking
file there.
Response
"G1" + "G2"
20404 0: Æ Command executed correctly
error code)
2
1: Æ Path does not exist
Table 2-142
Example: Set directory for marking files to

"C:\DATEN\ZEICH"
TAG LENGTH VALUE
Request 20404 15 "C:\DATEN\ZEICH"
B4 4F 00 00 0F 00 00 00 43 3A 5C 44 41 54 45 4E 5C 5A 45 49 43 48 00
B4 4F 00 00 02 00 00 00 30 00
Table 2-143

6.5 N text variable
(see also "Set variable")
Sets the content for several text variables

"T1" + "T2" +... + "TX"" must be fulfilled:
TX: Contents for the text - Marking file with a text
variables as variable must be
loaded Limitations:
- This TLV command
should not be used with
TruTops Mark unless,
the system is to be
Number of
operated in turns with
bytes in
20409 Winmark4 and TruTops
the TLV
Mark.
Value
- Otherwise, the TLV
Command "Set variable"
should be used.
- The variable names for
texts must meet the
requirements of the
following sequence:
- "TX" with X as number
(> 0) of the text variable
Response
"G1" + "G2"
error code)
Number of
bytes in
the TLV 3: Æ Invalid TLV LENGTH of the
1: Æ No variable exists with the
assigned ID
Table 2-144
Example: Set text variables

T1 = 123, T2 = 456, T3 = 789, T4 = abc
TAG LENGTH VALUE
Request 20409 16 "123" + "456" + "789" + "abc"
B9 4F 00 00 10 00 00 00 31 32 33 00 34 35 36 00 37 38 39 00 61 62 63 00
B9 4F 00 00 02 00 00 00 30 00
Table 2-145

6.6 Read file name/directory
Reads the file name and/or directory name of the loaded marking file
G: Function to be executed: - Marking file must be
loaded
1: Æ Return path and name of the
2 marking file
2: Æ Return path of the marking file
3: Æ Return name of the marking
file

"G1" + "T" + "G2"
the result of the
20411 TLV request is "1".
error code)
Number 3: Æ Invalid TLV LENGTH of the
of bytes request for the active
TLV
T: File name and/or directory
loaded
Table 2-146
Example: Read path and name of the loaded marking file

-> "C:\TRUMARK\VLF\TEST.VLF"
TAG LENGTH VALUE
Request 20411 2 "1"
BB 4F 00 00 02 00 00 00 31 00
Response 20411 26 "0" + " C:\TRUMARK\VLF\TEST.VLF "
30 00 63 3A 5C 74 72 75 6D 61 72 6B 5C 76 6C 66 5C 74 65 73 74 2E
BB 4F 00 00 1A 00 00 00
76 6C 66 00
Table 2-147

6.7 Set variable
Sets the content of the assigned variables

"TN1" + "TV1" (+ "TN2" + "TV2") + (...)" must be fulfilled:
TN1: Identifying variable 1 - Marking file with one
variable must be loaded
TV1: Content of variable 1 .
TN2: Identifying variable 2 - Always assign variable
Number names and content in pairs.
TV2: Content of variable 2
of bytes It is also true that only a
in the TNn: Identifying variable n pair can be assigned.
TLV TVn: Content of variable n - If the variable is defined
Value as a serial number, the
assigned value is used as
the new start value
- Data matrix – with
control character: ~dnnn
nnn = ASCII – decimal
20421 value
"G1" + "G2"
1: Æ Command could not be TLV Request is " 1".
Number error code)
of bytes 2: Æ Erroneous TLV VALUE
in the
TLV
assigned ID
Table 2-148

Example 1: Set the content of the "VAR_4" variable to "Test
text"
TAG LENGTH VALUE
Request 20421 15 " VAR_4" + "Test text"
C5 4F 00 00 0F 00 00 00 56 41 52 5F 34 00 54 65 73 74 74 65 78 74 00
C5 4F 00 00 02 00 00 00 30 00
Table 2-149
Example 2: Set the content of variables "V1" to "0" and "V2"

to "AB[cr][lf]C"
(only applies to the data matrix code)
TAG LENGTH VALUE
Request 20421 22 "V1" + "0" + "V2" + "AB~d013~d010C"
C5 4F 00 00 16 00 00 00 56 31 00 30 00 56 32 00 41 42 7E 64 30 31 33 7E 64 30 31 30 43 00
C5 4F 00 00 02 00 00 00 30 00
Table 2-150
[cr] = Carriage return (line break)
[lf] = Line feed

6.8 Read variable
Reads the content of the assigned variable

"T" must be fulfilled:
T: Identifying the variable
Number Marking file with one
of bytes variable must be
in the loaded. The content of
TLV the variable must have
Value been set in advance
and converted or
marked.

"G1" + "T" + "G2"
0: Æ Command executed correctly TLV Response when
1: Æ Command could not be the result of the
20422 executed (see extended TLV request is "1".
error code)
TLV
T: Content of the variable
loaded
Table 2-151
Example: Read variable "VAR_4" with "Test text"

TAG LENGTH VALUE
Request 20422 6 "VAR_4"
C6 4F 00 00 06 00 00 00 56 41 52 5F 34 00
Response 20422 11 "0" + "Test text"
C6 4F 00 00 0B 00 00 00 30 00 54 65 73 74 74 65 78 74 00
Table 2-152

6.9 Scaling/displacement
Scales, moves or rotates the marking around the midpoint of the image field
"D1" + "D2"+ "D3"+ "D4" must be fulfilled:
D1: Scaling factor _ Marking file must be
1: Æ Original size loaded
Explanations:
D2: Angle of rotation in ° clockwise - The settings remain in
around the mid point of the effect for the loaded
Number image field marking file
of bytes 0: Æ No rotation until they are overwritten
in the with this TLV Command
TLV D3: Displacement along the X axis
in mm or unless a different
Value marking file
0: Æ No displacement is loaded.
D4: Displacement along the Y axis - Sequence of operations:
in mm 1. Scale
0: Æ No displacement 2. Rotate around the
midpoint of the image field
20423 (+° = clockwise )
3. Move
"G1" + "G2"
TLV request is "1".
of bytes error code) Notice:
in the Æ
When this command is
2: Erroneous TLV VALUE
TLV used with the option
Value "Rotate, Move and Scale"
in the configuration under
"HW components/RTC",
G2: Extended error code: this is executed with RTC
> 0: Æ Internal error card commands, i.e. when
rotated this has no effect on
the size.
Table 2-153
Example: Modification of the marking by the following values:

-> Scaling by a factor of 2.5
-> Rotate by 1.25°
-> Displacement along the X axis by –20
mm/displacement along the Y axis by +5 mm
TAG LENGTH VALUE
Request 20423 15 "2.5" + "1.25" + "-20" + "5"
C7 4F 00 00 0F 00 00 00 32 2E 35 00 31 2E 32 35 00 2D 32 30 00 35 00
C7 4F 00 00 02 00 00 00 30 00
Table 2-154

6.10 Rotating/displacing the marking field in
MHS systems
Scales, moves or rotates the marking around the midpoint of the image field
"D1" + "D2" + "D3" must be fulfilled:
D1: Angle of rotation of the marking Explanations:
field - The marking field is
0: Æ No rotation rotated around the angle
and the displacement in X
D2: Displacement along the X axis and Y direction for Head B
in mm is calculated and taken
Number 0: Æ No displacement into account. The X or
of bytes D3: Displacement along the Y axis Y displacement is added
in the in mm in case of Head A and
TLV Head B.
0: Æ No displacement
Value
- Sequence of operations:
1. Rotate around the zero

point of the marking field
(+° = clockwise )
20424 2. Calculating the
displacement of Head B
3. Displacing Head A and
Head B
"G1" + "G2" - Only supported from
G1: Result of the TLV request: TruMark onwards.
0: Æ Command executed correctly - Is added on to the TLV
Number 1: Æ Command could not be Response when the
of bytes executed (see extended result of the TLV request
in the error code) is "1".
Table 2-155
Example: Modification of the marking by the following

values:
-> Rotate by 1.25°
-> Displacement along the X axis by –20
mm/displacement along the Y axis by +5 mm
TAG LENGTH VALUE
Request 20424 11 "1.25" + "-20" + "5"
C8 4F 00 00 0B 00 00 00 31 2E 32 35 00 2D 32 30 00 35 00
C8 4F 00 00 02 00 00 00 30 00
Table 2-156

6.11 Load marking objects into the scanner
Marking is started with the E15 start signal. The start signal must be
taken back again before the end of a marking process.
Loads a converted marking file into a scanner list in order to mark the marking file using the "Restart
mark"/"Abort mark" digital inputs

Request The following conditions must
"G1" + "G2" + "G3" be fulfilled:
- Marking file must be loaded
G1: List in which the marking and converted
objects are loaded: - The "Restart_mark /
0: Æ Only one list is available, Abort_mark" digital inputs
which is made up of list 1 must be configured
and list 2 Explanations:
1: Æ List 1 - Before starting the marking
process using the "Restart
2: Æ List 2 mark" input, one of the
100: Æ List completion (REI) two lists must be activated
using the "Activate scanner
101-115: Æ List space (REI) list" TLV command
255: Continuous mode beforehand.
- If the unavailable list number
G2: Task for the "Restart mark" 255 is specified when loading,
counter: list 1 is loaded at the end of
0: Æ Do not reset counter the list with the "Jump to Start"
command. E15=Restart Mark
1: Æ Counter reset to 0 starts the marking procedure in
G3: Laser parameters: the continuous mode. The
continuous output can be
0: Æ Laser parameter is not set, ended using at E16=Abort
i.e. the currently set laser Mark.
parameter is used for
marking Limitations:
- Only marking files with a
Number For the TruMark 6000 series, limited number of vectors can
of bytes the defocus and power be processed
20441 in the parameters are not set. All - Only one laser parameter set
TLV other laser parameters are can be processed for the
Value always set. complete marking file.
For TruMark 3000 and 5000,
this value must always be 1.
Otherwise, this can result in
an incorrect marking.
1: Æ Laser parameter is set to the
laser parameter of the first
marked object
Please note that for TruMark
3000 and 5000, there is
always only one laser
parameter in a marking file. Operation with REI card or
This is because our system IOE:
can only process a marking - 15 list spaces are available
file properly in retrigger for operation with the REI card
mode with one laser or IOE.
parameter in the file. - A maximum of 8000 list
commands are possible.
- The list spaces can be
selected and activated using
the REI card or IOE with
respect to the hardware.
- One marking file can be
loaded in every list space.
Complete the list with "100".
(See example
Sample_08_List_1-15.txt)

"G1" + "G2"
Response when the
error code)
TLV
1: Æ Invalid list number or list in
processing
2: Æ "Restart mark/Abort mark"
inputs not configured.
3: Æ Converted marking file is
too large for the list
Table 2-157
Example: Load marking objects into the scanner

-> List 1
-> "Restart mark" - reset counter
-> Do not set laser parameters
TAG LENGTH VALUE
Request 20441 6 "1" + "1" + "0"
D9 4F 00 00 06 00 00 00 31 00 31 00 30 00
D9 4F 00 00 02 00 00 00 30 00
Table 2-158

6.12 Activate scanner list
Activates one of the two scanner lists. The contents of this list will be marked by means of the "Restart mark"
input the next time that marking is started.
G: Active list selection: - A converted marking file
1: Æ List 1 needs to have been
loaded into the selected
2: Æ List 2
Number list beforehand by means
of bytes of the TLV Command
in the "Load marking objects
TLV into the scanner".
Value A converted marking file
has been loaded
- The "Restart_mark /
Abort_mark" digital inputs
must be configured

"G1" + "G2"
20442
TLV Response when
error code)
Value
processing
Table 2-159
Example: Activate scanner list 1

TAG LENGTH VALUE
Request 20442 2 "1"
DA 4F 00 00 02 00 00 00 31 00
DA 4F 00 00 02 00 00 00 30 00
Table 2-160

6.13 Start scanner list
Starts one of the two scanner lists.

A converted marking
G: Selecting the list to be started:
file needs to have been
1: Æ List 1 loaded into the
Number
2: Æ List 2 selected list before-
of bytes
in the hand by means of the
TLV TLV Command "Load
Value marking objects into
the scanner".
The "Restart_mark /
Abort_mark" digital
inputs must be
configured
"G1" + "G2" • Is added on to the TLV
Response when the
20443 result of the
0: Æ Command executed correctly TLV Request is "1".
error code)
Number 2: Æ Parameter VALUE is
unknown
of bytes
processing
Table 2-161
Example: Starting scanner list 1
TAG LENGTH VALUE
Request 20443 2 "1"
DB 4F 00 00 02 00 00 00 31 00
DB 4F 00 00 02 00 00 00 30 00
Table 2-162

6.14 Delete active VCT files
Deletes all VCT files of the loaded marking file.

must be fulfilled:
A marking file must be

loaded prior to deletion.
After deletion, the file must
be reloaded and converted.
Explanation
- During deletion, all used
CAD variables are reset.

"G1" + "G2" • Is added on to the TLV
G1: Result of the TLV request: result of the
in the 2: Æ Parameter VALUE is
TLV unknown
1: Æ No segmented marking file
has been loaded for editing
Table 2-163
Example: Deleting active VCT files

TAG LENGTH VALUE
E3 4F 00 00 00 00 00 00
E3 4F 00 00 02 00 00 00 30 00
Table 2-164

6.15 Delete all VCT files
Deletes all VCT files in the VCT directory.

must be fulfilled:

loaded prior to deletion.
After deletion, the file must
be reloaded and converted.
Explanations:
- During deletion, all used
CAD variables are reset.

20452 "G1" + "G2"
Response when the
result of the
Number 1: Æ Command could not be TLV Request is "1".
in the error code)
TLV 2: Æ Parameter VALUE is
Value unknown
Table 2-165
Example: Delete all VCT files

TAG LENGTH VALUE
E4 4F 00 00 00 00 00 00
E4 4F 00 00 02 00 00 00 30 00
Table 2-166

6.16 Hiding and showing the HMI
Hiding and showing the Standard_gui.

Request 2 "D" The following conditions
must be fulfilled:
D: Status of the HMI
0: Æ HMI is not displayed TruTops Mark must be
1: Æ HMI is displayed started.

20453 "G1" + "G2"
Number G1: Result of the TLV request: • Is added on to the TLV
of bytes Response when the
in the result of the
TLV executed (see extended
Value error code)
Table 2-167
Example: Hides the HMI

TAG LENGTH VALUE
Request 20453 2 "0"
E4 4F 00 00 00 00 00 00 30 00
E4 4F 00 00 02 00 00 00 30 00
Table 2-168

6.17 Generating marking file for editing
Generates a new, empty marking file for further editing

Request 0 No data Explanations:
- The new CAD file is

generated by loading a
template
.
- The templates are stored
in the directory
"..\VLF\Vorlagen"
and have the names of the
image field size.
- The template that
corresponds to the active
image field size of the
separator magazine is
loaded .
20461 "G1" + "G2"
request is "1".
Number error code)
1: Æ There is no template available
generated
Table 2-169
Example: Generating a new marking file

TAG LENGTH VALUE
ED 4F 00 00 00 00 00 00
ED 4F 00 00 02 00 00 00 30 00
Table 2-170

6.18 Load marking file for editing
Loads the marking file to be assigned for further editing

Request Explanations:
"T" - If the file extension is not

specified, then the
T: Name of the CAD file standard extension ".vlf" will
Number (including directory) be used
of bytes - If no directory is specified,
in the then the
TLV directory of the most
Value recently loaded marking file
or the directory set by the
TLV Command "Set
directory path"
will be used.

"G1" + "G2"
20462 G1: Result of the TLV request: Response when the
TLV Request is "1".
error code)
of bytes unknown
1: Æ Marking file does not exist
opened
Table 2-171
Example: Load marking file "TEST.VLF":

TAG LENGTH VALUE
Request 20462 9 "TEST.VLF"
EE 4F 00 00 09 00 00 00 54 45 53 54 2E 56 4C 46 00
EE 4F 00 00 02 00 00 00 30 00
Table 2-172

6.19 Import CAD file
Imports the assigned CAD file into a marking file that has already been opened for editing
Request Conditions:
"T1" + "T2" + "G" + "D1" + "D2" + "D3" + "D4" - A marking file for editing must be
opened
T1: Name of the CAD file to be (TLV commands "Generate
imported (including directory) marking file for editing" or
"Load marking file for editing").
T2: Name of the laser parameter for
the import. If no information is Explanations:
given, the original laser
parameters are used when - The following CAD formats are
importing a marking file. supported:
- VLF / DXF / HP / HPG / HPGL /
HGL / PLT
- A text file is used during DXF
G: Import mode
import
0: Æ Without displacement for allocating the DXF fonts to the
®
TruTops Mark Fonts
1: Æ With displacement (position is (selection via TruTops Mark®
defined by the lower left-hand configuration)
corner) - Structure of the text file:
D1: X value of the lower left-hand - One font allocation per line -
corner of the import in mm "Dxf_fontname:TruTopsMark_fontn
ame;"
Is taken into account only when - See also the following sample file:
Number import mode = 1 C:\TruMark\Standard_GUI\
of bytes Y value of the lower left-hand Font_to_font.txt
20463 in the D2:
corner of the import in mm - If no file extension is specified
TLV then the standard extension
Value -> Is taken into account only
when Import mode = 1 ".vlf" will be used
- If no directory is specified, then
D3: Scaling factor the directory of the
last marking file loaded or the
> 1: Æ Original size
directory set by the
D4: Angle of rotation in ° clockwise "Set directory path" TLV Command
will be used.
> 0: Æ No rotation - Laser parameter must be
specified with the complete
parameter path
(e.g. Aluminum\Marking).
- If the assigned laser parameter is
not available, then the "Standard"
laser parameter
will be used.
- The laser parameters must be
available in the source file
(C:\TruMark\VLF\Vorlagen\*.vlf)
under "In this project"
- Import position is the lower left-
hand corner of a rectangle that
encloses
all of the objects of the
CAD file to be imported.

Imports the assigned CAD file into a marking file that has already been opened for editing
"G1" + "D1" + "D2" + "D3" + "D4" + "G2"
TLV Request is "1".
error code)
2: Æ Parameter VALUE is
unknown
communications interface
D1: X value of the lower left-hand
Number corner of the import in mm
of bytes
20463 in the D2: Y value of the lower left-hand
TLV corner of the import in mm
Value D3: X value of the upper right-hand
corner of the import in mm
D4: Y value of the upper right-hand
corner of the import in mm
opened for editing
2: Æ The marking file opened is
corrupt
3: Æ Import CAD file could not be
opened
4: Æ Import CAD file is corrupt
5: Æ Import CAD file does not exist
6: Æ Import CAD file has a wrong
extension
Table 2-173
Example: Import "TEST.VLF" CAD file
-> Laser parameters: "Marking"
-> Displacement to position X=2.5 mm/Y=5 mm
-> Scaling: 200%
-> Rotate counter-clockwise by 45º
New position:
Left-hand lower corner: X=2.500/Y=5.000;
Right-hand upper corner: X=12.500/Y=15.000
TAG LENGTH VALUE

Request 20463 33 "TEST.VLF" + "Marking" + "1" + "2.5" + "5" + "2" + "-45"
54 45 53 54 2E 56 4C 46 00 4D 61 72 6B 69 65 72 65 6E 00 31 00 32 2E
EF 4F 00 00 21 00 00 00
35 00 35 0032 00 2D 34 35 00
Response 20463 28 "0" + "2.500" + "5.000" + "12.500" + "15.000"
30 00 32 2E 35 30 30 00 35 2E 30 30 30 00 31 32 2E 35 30 30 00 31 35
EF 4F 00 00 1C 00 00 00
2E 30 30 30 00
Table 2-174

6.20 Save the marking file opened for
editing
Saves the marking file currently opened for editing under the assigned name.
Request Conditions:
"T"
- A marking file must be
T: Name under which the marking opened for editing
file opened for editing should be (TLV commands "Generate
saved (including directory). marking file for editing" or
"Load marking file for
Number editing").
of bytes Explanations
in the - If no file extension is
TLV specified, then the standard
Value extension ".vlf" will be used
- If no directory has been
specified, the directory of the
last loaded marking file or the
directory set by the "Set
directory path" TLV
command
will be used.
20464
"G1" + "G2"
TLV Request is "1".
error code)
of bytes unknown
opened for
processing
saved
Table 2-175
Example: Save the marking file opened for
editing under the name "TEST_01.VLF":
TAG LENGTH VALUE
Request 20464 12 "TEST_01.VLF"
F0 4F 00 00 0C 00 00 00 54 45 53 54 5F 30 31 2E 56 4C 46 00
F0 4F 00 00 02 00 00 00 30 00
Table 2-176
6.21 Adding a line
Adds a line with the assigned geometry to the marking file currently opened for editing

Request Conditions:
"D1" + "D2" + "D3" + "D4" + "T" - A marking file for editing
must be opened
D1: X value of the start point of the (TLV commands "Generate
line in mm marking file for
D2: Y value of the start point of the editing" or "Load marking
Number line in mm file for editing").
of bytes D3: X value of the end point of the Explanations
in the line in mm - Laser parameter must be
TLV specified with the complete
Value D4: Y value of the end point of the
Parameter path
line in mm
T: Name of the laser parameter - If the assigned laser
for the line parameter is not available,
then the
"Standard" laser parameter
will be used.
"G1" + "G2"
request is "1".
error code)
Number unknown
Value
opened for editing
corrupt
Table 2-177
Example: Add a line between the points X=2.5/Y=5 and

X=4/Y=-3.2 to the marking file currently opened for
editing, while utilizing the
"Mark"laser parameter:
TAG LENGTH VALUE
Request 20471 22 "2.5" + "5" + "4" + "3.2" + "Marking"
F7 4F 00
16 00 00 00 32 2E 35 00 35 00 34 00 33 2E 32 00 4D 61 72 6B 69 65 72 65 6E 00
00
F7 4F 00 30 00
02 00 00 00
00
Table 2-178

6.22 Add an arc
Adds an arc with the assigned geometry to the marking file currently opened for editing
LENGT
TAG H VALUE Remark
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "D5" + "D6" + "T"
D1: X value of the midpoint of the arc - A marking file for editing
in mm must be opened
(TLV commands "Generate
D2: Y value of the midpoint of the arc marking file for
in mm editing" or "Load marking file
D3: Radius of the arc in mm for editing").
Number
of bytes D4: Direction of rotation of the arc Explanations
in the 0: Æ Clockwise - Laser parameter must be
TLV Æ
1: Counter-clockwise
Value parameter path
D5: Start angle of the arc in ° in the (e.g. Aluminum\Marking).
mathematical coordinate system - If the assigned laser
D6: End angle of the arc in ° in the parameter is not available,
mathematical coordinate system then the
T: Name of the laser parameter for will be used.
the arc
20472
"G1" + "G2"
error code)
of bytes unknown
in the
TLV
opened for editing
corrupt
Table 2-179
Example: Add an arc to the marking file
opened for editing with the midpoint X=2.5/Y=5,
radius 4, in the angle range of 5.3° to 45.7° by using the
"Mark" laser parameter:
TAG LENGTH VALUE
Request 20472 27 "2.5" + "5" + "4" + "5.3" + "45.7" + "Marking"
F8 4F 00 32 2E 35 00 35 00 34 00 35 2E 33 00 34 35 2E 37 00 4D 61 72 6B 69 65
1B 00 00 00
00 72 65 6E 00
F8 4F 00 30 00
02 00 00 00
00
Table 2-180

6.23 Add a circle
Adds a circle with the assigned geometry to the marking file currently opened for editing
Request Conditions:
"D1" + "D2" + "D3" + "T" - A marking file for editing
D1: X value of the midpoint of the must be opened
circle in mm (TLV commands "Generate
marking file for
D2: Y value of the midpoint of the
editing" or "Load marking file
circle in mm
Number for editing").
of bytes D3: Radius of the circle in mm
Explanations
in the T: Name of the laser parameter - Laser parameter must be
TLV for the circle specified with the complete
Value parameter path
- If the assigned laser
parameter is not available,
then the
will be used.

"G1" + "G2"
is "1".
error code)
Number
of bytes 2: Æ Parameter VALUE is
unknown
in the
opened for editing
corrupt
Table 2-181
Example: Adding a circle to the marking file

currently opened for editing with midpoint
X=2.5/Y=5, radius 4, while utilizing the "Marking"
laser parameter:
TAG LENGTH VALUE
Request 20473 18 "2.5" + "5" + "4" + "Marking"
F9 4F 00
12 00 00 00 32 2E 35 00 35 00 34 00 4D 61 72 6B 69 65 72 65 6E 00
00
F9 4F 00 30 00
02 00 00 00
00
Table 2-182

6.24 Add a rectangle
Adds a rectangle with the assigned geometry to the marking file currently opened for editing
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "D5" + "T"
- A marking file for editing
D1: X value of the lower left-hand must be opened
corner of the rectangle in mm (TLV commands "Generate
D2: Y value of the lower left-hand marking file for
corner of the rectangle in mm editing" or "Load marking file
D3: Width of the rectangle in mm
in the D4: Height of the rectangle in mm
- Laser parameter must be
TLV D5: Angle of rotation of the rectangle specified with the complete
Value in ° parameter path
T: Name of the laser parameter (e.g. Aluminum\Marking).
for the rectangle - If the assigned laser
parameter is not available,
then the
"Standard" laser
parameter will be used.
20474 Extended error code:
Response
"G1" + "G2"
request is "1".
error code)
Number
unknown
in the
opened for editing
corrupt
Table 2-183
Example: Adding a rectangle to the marking file currently

opened for editing with the lower left-hand point
X=2.5/Y=5, width 10.25 and height
15, utilizing the "Marking" laser parameter:
TAG LENGTH VALUE
Request 20474 28 "2.5" + "5" + "10.25" + "15" + "10" + "Marking"
32 2E 35 00 35 00 31 30 2E 32 35 00 31 35 00 31 30 00 4D 61 72 6B
FA 4F 00 00 1C 00 00 00
69 65 72 65 6E 00
FA 4F 00
02 00 00 00 30 00
00
Table 2-184

6.25 Add a text
Adds a text with the assigned geometry to the marking file currently opened for editing
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "T1" + "T2" + "T3"
D1: X value of the lower left-hand must be opened
corner of the text in mm (TLV commands "Generate
D2: Y value of the lower left-hand marking file for
corner of the text in mm editing" or "Load marking file
D3: Angle of rotation of the text in °
of bytes
Explanations
in the D4: Text size in mm
TLV T1: Name of the font for the text specified with the complete
Value
T2: Text that should be added parameter path
T3: Name of the laser parameter - If the assigned laser
for the text parameter is not available,
then the
will be used.

"G1" + "G2" Is added on to the TLV
TLV Request is "1".
error code)
Number
unknown
in the
opened for editing
corrupt
Table 2-185
Example: Add the "Text example" text to
the marking file opened for editing with the lower
left-hand point X=2.5/Y=5, the angle of rotation
45°, the text size 6,
the "Standard" font, by using the "Marking" laser
parameter:
TAG LENGTH VALUE

Request 20475 43 "2.5" + "5" + "45" + "6" + "Standard" + "Text example" + "Marking"
32 2E 35 00 35 00 34 35 00 36 00 54 65 78 74 62 65 69 73 70 69 65
FB 4F 00 00 15 00 00 00
6C 00 53 74 61 6E 64 61 72 64 00 4D 61 72 6B 69 65 72 65 6E 00
FB 4F 00 00 02 00 00 00 30 00
Table 2-186

6.26 Add an expanded text
Adds a text with the assigned expanded geometry to the marking file currently opened for editing
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "T1" + "T2" + "T3"
+ "D5" + "G1" + "G2" + "G3" + "G4" + "D6" + - A marking file for editing
"D7" + "D8" + "D9" + "D10" + "G5" + "D11" must be opened
+ "D12" + "T4"
marking file for
D1: X value of the lower left-hand corner editing" or "Load marking file
of the text in mm
for editing").
D2: Y value of the lower left-hand corner
of the text in mm Explanations
D3: Angle of rotation of the text in °
D4: Text size in mm parameter path
T1: Name of the font for the text (e.g. Aluminum\Marking).
T2: Text that should be added parameter is not available,
T3: Name of the laser parameter for the then the
text "Standard" laser parameter
D5: Italics text in ° (0-45) will be used.
G1: Mirrored (0=no, 1=yes)
G2: Horizontal text alignment
0 = Left
1 = Centered
2 = Right
Number
3 = Scaled
of bytes
20476 in the G3: Vertical text alignment
TLV 0 = Bottom
Value 1 = Base line
2 = Centered
3 = Top
G4: Circular text (0=no, 1=yes)
D6: Radius of the circularly displayed
text
D7: Position angle, where the circular
text starts
D8: Character width in percent
Standard equivalent to 100%
(1 equivalent to 100%)
D9: Character spacing in percent
Standard equivalent to 100%
(1 equivalent to 100%)
Comment regarding G5:
D10: Line spacing in mm
(0 equivalent to 0 mm) No box (0)
G5: Text box mode (0-4) Break (1)
Sign wrap (2)
D11: Height of the Text box Cut (3)
D12: Width of the Text box Fit (4)
T4: Variable name of an existing variable

Adds a text with the assigned expanded geometry to the marking file currently opened for editing
"G1" + "G2"
is "1".
error code)
Number
unknown
in the
opened for editing
corrupt
Table 2-187
Example: Add the text "Text example" to the marking file

currently opened for editing with the lower left-
hand point X=2.5/Y=5, the angle of rotation 45°,
the text size 6, the "Standard" font, by using the
"Marking" laser parameter (see below for more
values):
TAG LENGTH VALUE
Request "2.5" + "5" + "45" + "6" + "Standard" + "Text example" + "Marking" + "0"
20476 70 + "0" + "0" + "0" + "0" + "0" + "0" + "1" + "1" + "1"
+ "0" + "0" + "0" + ""
32 2E 35 00 35 00 34 35 00 36 00 53 74 61 6E 64 61 72 64 00 54 65
78 74 62 65 69 73 70 69 65 6C 00 4D 61 72 6B 69 65 72 65 6E 00 30
FC 4F 00 00 46 00 00 00
00 30 00 30 00 30 00 30 00 30 00 30 00 31 00 31 00 31 00 30 00 30
00 30 00 00
FC 4F 00 00 02 00 00 00 30 00
Table 2-188

6.27 Add a variable
Adds a variable to the marking file currently opened for editing

Request Conditions:
"T1" + "G1" + "T2" + "T3" + "T4" + "G2" + "G3"
+ "G4" + "G5" + "G6" + "G7" - A marking file for editing
must be opened
T1: Name of the new variable (TLV commands "Generate
G1: Data source marking file for
0: Æ Interactive editing" or "Load marking file
1: Æ File for editing").
2: Æ COM object
Explanations
3: Æ Serial number
4: Æ Keyword
5: Æ Function call
Æ
parameter path
6: External source
T2: Additional information - If the assigned laser
Depending on the data source parameter parameter is not available,
0: Æ Request text for user then the
1: Æ Path "Standard" laser parameter
Number 2: Æ Object name of COM object will be used.
of bytes 3: Æ --
in the 4: Æ Keyword
TLV 5: Æ DLL path Explanation regarding G6:
Value 6: Æ -- - The flags can also be
T3: Function name added,
e.g.: 7 all 3 flags (4+2+1)
Only with data source = 5 (function call)
are set.
T4: Bookmark/marking text
20477 G2: Number of characters
Explanation regarding
G3: Start value "decimal":
Use fill character at the
G4: Increment
beginning as ASCII character
G5: End value "32-126". Do not place the
G6: Set flag number 0 in decimal, but
rather the character 0 as
1: Æ End value: start at the start value
ASCII code (decimal = 48 as
2: Æ End value: output message
Æ
default value!)
4: Reset when calendar date changes
G7: Fill character at the start as
ASCII (decimal)
"G1" + "G2"
Response when the
Number 1: Æ Command could not be request is "1".
in the error code)
TLV 2: Æ Parameter VALUE is unknown
10: Æ Variable is already present in
the variable list
Table 2-189

Example: Add a "SERNO" serial number to the marking file
opened for editing with the start value 100,
increment 1 and end value 9999:
TAG LENGTH VALUE
Request 20477 32 "SERNO" + "3" + "0" + "0" + "0" + "6" + "100" + "1" + "9999" + "2" + "48"
FD 4F 00 53 65 72 6E 6F 00 33 00 30 00 30 00 30 00 36 00 31 30 30 00 31 00
20 00 00 00
00 39 39 39 39 00 32 00 34 38 00
FD 4F 00
02 00 00 00 30 00
00
Table 2-190
6.28 Replace laser parameter
Assigns the new laser parameter to all objects which had been assigned a particular laser parameter in the
marking file currently opened for editing
Request Conditions:
"T1" + "T2"
T1: Name of the laser parameter to must be opened
be found (TLV commands "Generate
Number marking file for
T2: New name of the laser parameter
of bytes editing" or "Load marking file
to be replaced
in the for editing").
TLV
Value Explanations
parameter path

"G1" + "G2"
is "1".
Number error code)
in the unknown
1: Æ Old parameter no found
2: Æ New parameter not found
opened for editing
Table 2-191

Example: Replace the laser parameter "Red" with "Blue":
TAG LENGTH VALUE
Request 20478 09 "Red" + "Blue"
FE 4F 00
09 00 00 00 72 65 64 00 62 6C 75 65 00
00
FE 4F 00
02 00 00 00 30 00
00
Table 2-192
6.29 Replace fill parameter
Assigns the new fill to all objects which had been assigned a particular fill in the marking file currently opened
for editing
Request Conditions:
"T1" + "T2"
T1: Name of the fill must be opened
T2: New fill for replacement (TLV commands "Generate
marking file for
for editing").
Explanations
Number
of bytes
in the
parameter path
TLV
Value
-Comment:
This command also works
with a text object with a
dynamic fill.
-Limitation:
20479 All fills that are in a group are
not taken into consideration.

"G1" + "G2"
is "1".
Number error code)
in the unknown
1: Æ Old fill not found
2: Æ New fill not found
opened for editing
Table 2-193

Example: Replacing "Red" fill with "Blue":
TAG LENGTH VALUE
Request 20479 9 "Red" + "Blue"
FF 4F 00
09 00 00 00 72 65 64 00 62 6C 75 65 00
00
FF 4F 00
02 00 00 00 30 00
00
Table 2-194
6.30 Initialize all variables
Initializes all variables with an empty character string in the marking file currently opened for editing.
Request 0 No data Conditions:

must be opened
marking file for
for editing").
Explanations
parameter path

20480 "G1" + "G2"
Response when the
TLV unknown
opened for editing
Table 2-195
Example:
TAG LENGTH VALUE
Request 20480 0
00 50 00 00 00 00 00 00 00
00 50 00 00 02 00 00 00 30 00
Table 2-196

6.31 Initialize variable
Assigns a new standard value to a variable in the marking file currently opened for editing
Request Conditions:
"T1" + "T2"
Number T1: Name of the variable must be opened
of bytes (TLV commands "Generate
T2: Value of the variable
in the marking file for
TLV editing" or "Load marking file
Value for editing").

"G1" + "G2"
error code)
of bytes
TLV unknown
1: Æ Variable not found
opened for editing
Table 2-197
Example: For the "Type" variable, set the

default value "W4237":
TAG LENGTH VALUE
Request 20484 10 "Type" + "W4237"
FF 53 00
0A 00 00 00 54 79 70 00 57 34 32 33 37 00
00
FF 53 00
02 00 00 00 30 00
00
Table 2-198

6.32 Set laser parameters – properties
Modifies the main characteristics of a laser parameter

Request Conditions:
"T1" + "D1" + "D2" + "D3" + "D4" + "D5" + "D6"
+ "G1" + "D7" + "G2" + "G3" - A marking file for editing
must be opened
T1: Name of the laser parameter (TLV commands "Generate
D1: Power in % marking file for
D2: Speed in mm/s for editing").
Number
of bytes D3: Frequency in Hz
Explanations
in the D4: Track width in mm - Laser parameter must be
TLV specified with the complete
Value D5: Z offset in mm
parameter path
D6: Defocus in mm (e.g. Aluminum\Marking).
G1: Number of pulses
D7: Pulse width in um
G2: Head A (1/0)
20481 G3: Head B (1/0)
"G1" + "G2"
is "1".
Number
error code)
of bytes
TLV unknown
1: Æ Parameter not found
opened for editing
Table 2-199
Example: Set the properties of the

laser parameter "red":
TAG LENGTH VALUE
Request 20481 37 "red"+"80"+"3000"+"20000"+"0.08"+"1" "0.4"+"1"+"5"+"1"+"0"
72 65 64 00 38 30 00 33 30 30 30 00 32 30 30 30 30 00 30 2E 30 38 00
01 50 00 00 25 00 00 00
31 00 30 2E 34 00 31 00 35 00 31 00 30 00
01 50 00 00 02 00 00 00 30 00
Table 2-200

6.33 Read laser parameter – Properties
Calls up the main characteristics of a laser parameter

Request Conditions:
"T1"
Number - A marking file for editing
of bytes T1: Name of the laser parameter must be opened
in the (TLV commands "Generate
TLV marking file for
Value editing" or "Load marking file
for editing").

"G1" + "D1" + "D2" + "D3" + "D4" + "D5" + "D6"
+ "G3" + "D7" + "G4" + "G5" + "G2" • Is added on to the TLV
result of the
error code)
unknown
20482 request for the active
Number D1: Power in %
of bytes D2: Speed in mm/s
in the
TLV D3: Frequency in Hz
Value D4: Track width in mm
D5: Z offset in mm
D6: Defocus in mm
G3: Number of pulses
D7: Pulse width in um
G4: Head A (1/0)
G5: Head B (1/0)
1: Æ Parameter not found
opened for editing
Table 2-201
Example: Read the properties for laser parameter "red":

TAG LENGTH VALUE
Request 20482 4 "red"
02 50 00 00 04 00 00 00 72 65 64 00
Response "0"+"70.000"+"400.000"+"30000.000"+"0.050"+"0.000"+"0.000"+"1" +
20482 57
"4.000"+"1"+"0"
30 00 37 30 2E 30 30 30 00 34 30 30 2E 30 30 30 00 33 30 30 30 30
02 50 00 00 39 00 00 00 2E 30 30 30 00 30 2E 30 35 30 00 30 2E 30 30 30 00 30 2E 30 30 30
00 31 00 34 2E 30 30 30 00 31 00 30 00
Table 2-202

6.34 Hide blocks
Hides certain CAD block objects in the marking file currently opened
Request Conditions:
"G1" + "T1" + "G2"
G1: Type of information must be opened
1: Æ Binning – Info (TLV commands "Generate
Number (col1;row1/col2;row2/…) marking file for
of bytes 2: Æ Block name (block1/block2/..) editing" or "Load marking file
in the for editing").
3: Æ Reject Map File (EO)
TLV
Value T1: Info (see type)
The blocks that have already
If empty, the last status is
been hidden are displayed
restored.
again G2 = 1
G2: Initialize layer
(1 = yes, 0 = no)
"G1" + "G2"
20483 Æ TLV Request is "1".
1: Command could not be
error code)
unknown
Value
1: Æ Block / EO file could not be
found
2: Æ Error in the length info
3: Æ Wrong info type
4: Æ Reject Map File could not be
opened
5: Æ Error when reading the Reject
Map File
opened for editing
Table 2-203
Example: Hiding blocks with EO – File 888888.bin:

TAG LENGTH VALUE
Request 20483 15 "3" + "888888.bin" + "0"
03 50 00 00 0F 00 00 00 33 00 38 38 38 38 38 38 2E 62 69 6E 00 30 00
Response 20483 02 "0"
03 50 00 00 02 00 00 00 30 00
Table 2-204

6.35 Add a Bitmaps
(as of TruTops Mark 2.5.3)
Adds a bitmap with the assigned geometry to the marking file currently opened for editing
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "D5" + "D6" + "D7" - A marking file for editing
+ "T1" + "T2" must be opened
D1: X-value of image center in mm marking file for
D2: Y-value of image center in mm editing" or "Load marking file
for editing").
Number D3: Image width in mm
D4: Image height in mm
in the - Laser parameter must be
TLV D5: Image angle specified with the complete
Value D6: X-resolution in dpi Parameter path
D7: Y-resolution in dpi - If the assigned laser
T1: Name of the laser parameter for parameter is not available,
the bitmap then the
T2: Path (+name) of the bitmap file "Standard" laser parameter
will be used.
Response
"G1" + "G2"
20485 0: Æ Command executed correctly
error code)
2: Æ Parameter VALUE is unknown
Number
of bytes G2: Extended error code for Extended error code:
in the TruMark: - Only supported from
TLV
1: Æ No marking file has been TruMark onwards.
Value
opened for editing
- Is added on to the TLV
2: Æ The marking file opened is Response when the
corrupt result of the TLV request
3: Bitmap not available is "1".
4: Height or width of the bitmap
is zero. The formats: JPG,
TIF and PCX have no height
and width stored in the
format.
5: Bitmap cannot be read in
Table 2-205

Example: Add a bitmap to the marking file currently opened
for editing using the
"Mark"laser parameter:
TAG LENGTH VALUE
Request 20485 48 "100.0" + "100.0" + "0" + "300" "300" + "Mark" + "C:\serial.bmp"
31 30 00 31 30 00 31 30 30 00 31 30 30 00 30 00 33 30 30 00 33 30 30
05 50 00 00 16 00 00 00 00 4D 61 72 6B 69 65 72 65 6E 00 63 3A 5C 73 65 72 69 61 6C 2E 62
6D 70 00
05 50 00 00 02 00 00 00 30 00
Table 2-206
6.36 Close the TruCad Server
Breaks the connection to the TruCad Server and removes

this program from the program memory.
The command "Close the TruCad Server" will

release the memory range used once more.
Closes the TruCad Server
Request 0 No data
Response
"G1" + "G2" Comment:
Æ
The TruCad Server does
0: Command executed correctly
not enable all of the
Number executed memory range again.
20486 of bytes 3: Æ Invalid TLV LENGTH of the
in the request for the active Recommendation:
Value Execute this command
0: Æ No extended FC
regularly!
Table 2-207
Example: Close the TruCad Server

TAG LENGTH VALUE
06 50 00 00 00 00 00 00
06 50 00 00 02 00 00 00 30 00
Table 2-208

6.37 Adding a polyline
Request Conditions:
"D1" + "T1" + "T2" + "T3" + "T4" - A marking file for editing
must be opened
D1: FLAG Not used (TLV commands "Generate
marking file for
Editing" or "Load marking
T1: Base values of the polygon in file for editing").
the format
"S=2;x0,y0;x1y1;…;xi,yi;E=0;x,y Explanations
….xiyi;" - Laser parameter must be
S 0 Straight lines Parameter path
2 B spline (e.g. Aluminum\Marking).
4 By the calibration parameter is not available,
Number points
of bytes then the
20487 in the E Not used "Standard" laser parameter
TLV will be used.
Value
Polygon consists of
calibration points in the
format: x.xxx,y.yyy
T2: Name of the laser parameter
for the polyline Ellipse arc consists of:
T3: Name of the filling for a closed Center: x,y
polygon Main axis angle: x.xx
Start angle: x.xx
T4: Name of the layer for the polyline
End angle: x.xx
Main radius: x.xx
Second radius: x.xx
Direction: x

"G1" + "G2"
request is "1".
error code)
unknown
Number request for the active
of bytes communication interface
in the G2: Extended error code:
TLV
Value 1: Æ No marking file has been
opened for editing
corrupt
3: Æ Level does not exist
4: Æ Flag value not valid
5: Æ Fill does not exist
6: Æ Polyline not closed
7: Æ Ellipse arc could not be added
Table 2-209
Example: Insert a B spline and an ellipse arc in the marking

file opened for editing. Using the laser parameter
"Green", the fill "Fill 0.05" and the level "Standard".
TAG LENGTH VALUE
Request "7" +
"S=0;20.019,96.714;19.614,104.992;9.788,102.071;1.373,107.249;5.273,
20487 186 104.859;6.601,96.096;12.339,93.279;
E=1;18.286,93.440;155.225;45.476;268.480;7.605;3.700;0;" +
" green " + "Fill 0.05" + "Standard"
37 00 53 3D 30 3B 32 30 2E 30 31 39 2C 39 36 2E 37 31 34 3B 31 39 2E 36 31 34
2C 31 30 34 2E 39 39 32 3B 39 2E 37 38 38 2C 31 30 32 2E 30 37 31 3B 31 33
2E 33 37 33 2C 31 30 37 2E 32 34 39 3B 35 2E 32 37 33 2C 31 30 34 2E 38 35 39
3B 36 2E 36 30 31 2C 39 36 2E 30 39 36 3B 31 32 2E 33 33 39 2C 39 33 2E 32
07 50 00 00 16 00 00 00
37 39 3B 45 3D 31 3B 31 38 2E 32 38 36 2C 39 33 2E 34 34 30 3B 31 35 35 2E
32 32 35 3B 34 35 2E 34 37 36 3B 32 36 38 2E 34 38 30 3B 37 2E 36 30 35 3B 33
2E 37 30 30 3B 30 3B 00 67 72 65 65 6E 00 46 69 6C 6C 20 30 2E 30 35 00 53 74
61 6E 64 61 72 64 00
07 50 00 00 02 00 00 00 30 00
Table 2-210

6.38 Adding an ellipse
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "D5" + "T1" + "T2" - A marking file for editing
+ "T3" must be opened
D1: X coordinate of the center of the marking file for
ellipse editing" or "Load marking
D2: Y coordinate of the center of file for editing").
Number ellipse
Explanations
of bytes
D3: Angle of the main axis to the - Laser parameter must be
in the
horizontal specified with the complete
TLV
D4: Length of the main axis Parameter path
Value
D5: Length of the secondary axis - If the assigned laser
T1: Name of the laser parameter parameter is not available,
for the polyline then the
T3: Name of the filling for an ellipse will be used.
T4: Layer name of the ellipse
"G1" + "G2"
20488 G1: Result of the TLV request: Response when the
request is "1".
error code)
unknown
Value 1: Æ No marking file has been
opened for editing
corrupt
4: Æ Parameter D4 and D5 are less
than 0.1 mm
5: Æ Fill does not exist
Table 2-211

Example: Insert an ellipse in the marking file opened for
editing. Which is defined by the center x=30/y=30,
the main radius = 25.5, the second radius = 9.5
and the angle to the horizontal = 10°, using the
laser parameter "Mark", the fill "Fill 0.05" and the
level "Standard".
TAG LENGTH VALUE
Request 20488 47 "30" + "30" + "25.5" +" 9.5" + "10" + "Marking" + "Fill 0.05" + "Standard"
33 30 00 33 30 00 32 35 3B 35 00 39 3B 35 00 31 32 00 4D 61 72 6B 69
08 50 00 00 16 00 00 00 65 72 65 6E 00 46 69 6C 6C 20 30 2E 30 35 00 53 74 61 6E 64 61 72 64
00
08 50 00 00 02 00 00 00 30 00
Table 2-212

6.39 Adding an ellipse arc
Request Conditions:
"D1" + "D2" + "D3" + "D4" + "D5" + "D6" + - A marking file for editing
"D7" + "D8" + "D9" + "T1" + "T2" must be opened
D1: X coordinate of the center of the marking file for
ellipse editing" or "Load marking
D2: Y coordinate of the center of file for editing").
ellipse
Explanations
D3: Length of the main axis - Laser parameter must be
D4: Length of the secondary axis specified with the complete
Number Parameter path
of bytes D5: Direction of the elliptical arc (e.g. Aluminum\Marking).
in the 0=Clockwise - If the assigned laser
TLV 1=Counterclockwise parameter is not available,
Value then the
D6: X coordinate of the starting point
D7: Y coordinate of the starting will be used.
point.
D8: X coordinate of the end point
D9: Y coordinate of the end point.
T1: Name of the laser parameter
for the polyline
20489 T2: Layer name of the ellipse

"G1" + "G2"
request is "1".
error code)
unknown
TLV
opened for editing
corrupt
4: Æ Parameter D4 and D5 are less
than 0.1 mm
Table 2-213

Example: Insert an ellipse arc in the marking file opened for
editing. Which is defined by the center
x=60.3/y=69.1, the main radius = 9.6, the second
radius = 6.6, the direction of rotation = 0, the
starting point x=51.4/y=70.7 and the end point
x=68.5/y=66.4, using the laser parameter "Mark"
and the level "Standard".
TAG LENGTH VALUE
Request "60.3" + "69.1" + "9.6" +" 6.6" + "0" + "51.4" + "70.7" + "68.5" +" 66.4" +
20489 55
"Marking" + "Standard"
36 30 3B 33 00 36 39 3B 31 00 39 3B 36 00 30 00 35 31 3B 34 00 37 30
09 50 00 00 16 00 00 00 3B 37 00 36 38 3B 35 0036 36 3B 34 00 4D 61 72 6B 69 65 72 65 6E 00
53 74 61 6E 64 61 72 64 00
09 50 00 00 02 00 00 00 30 0
Table 2-214

6.40 Copying a file
Request
Number "T1" + "T2"
of bytes
T1: Name and path of the file to be
in the
copied
TLV
Value T2: Name and path of the location
where the file will be copied
"G1" + "G2"
request is "1".
Number error code)
in the unknown
TLV
Value
1 Æ File could not be copied
Table 2-215
Example: Copies the file "c:\Temp\example.txt" to

"c:\data\example.txt".
TAG LENGTH VALUE
Request 20490 43 "c:\temp\example.txt" + "c:\data\example1.txt"
63 3A 5C 74 65 6D 70 5C 62 65 69 73 70 69 64 6C 2E 74 78 74 00 63 3A
0A 50 00 00 16 00 00 00
5C 64 61 74 65 6E 5C 62 65 69 73 70 69 64 6C 2E 74 78 74 00
0A 50 00 00 02 00 00 00 30 00
Table 2-216

6.41 Starts the adding of an assembled
geometry object
Adds a complex object of the transferred geometry to the marking file currently opened for editing
Request Conditions:
"T1" + "T2"+ "T3" - A marking file for editing
must be opened
T1: Name of the laser parameter (TLV commands "Generate
T2: Name of the fill marking file for
editing" or "Load marking
T3: Name of layer
file for editing").
Explanations
Parameter path
Number (e.g. Aluminum\Marking).
of bytes - If the assigned laser
in the parameter is not available,
TLV then the
Value "Standard" laser parameter
will be used.
With an assembled
geometry object the
commands 20494,
20495 and 20496 must
always be sent in this
sequence in order that
the object can be fully
20494 created.

"G1" + "G2"
request is "1".
error code)
unknown
TLV
Value
1 Æ Target file not opened
2 Æ Target file does not show
correct marking file.
3 Æ Layers do not exist
4 Æ Fill does not exist
5 Æ Last complex object not
completed
Table 2-217
Example: Starts the processing of a complex object with the

laser parameter, fill and layer

TAG LENGTH VALUE
Request 20494 25 "green" + "Fill 0.05" + "Standard"
67 72 65 65 6E 00 46 69 6C 6C 20 30 2E 30 35 00 53 74 61 6E 64 61 72
0A 50 00 00 16 00 00 00
64 00
0A 50 00 00 02 00 00 00 30 00
Table 2-218
6.42 Add an assembled geometry object to

a polyline
Request With an assembled
"D1" + "D2"+ "T3" geometry object the
D1: Mode commands 20494,
20495 and 20496 must
FLAG 1 Outer polygon always be sent in this
2 Extend outer sequence in order that
polygon the object can be fully
3 Outer polygon created. The command
20495 can be sent
Number 4 Extend inner multiple times in
of bytes polygon
succession. It must
20495 in the D2: Flag always be commenced
TLV
FLAG 2 B spline with the outer polygon
Value
4 Through base
values for B
spline
0 Polyline (straight
lines)
T3: GeometryList
Base values of the polygon in
the format "x0,y0;x1y1;…;xi,yi;"

"G1" + "G2"
request is "1".
error code)
of bytes unknown
1 Æ Mode not defined
2 Æ Flag not defined
3 Æ Processing of a complex
object not started
Table 2-219
Example: Creates a B spline with an island that also

consists of a B spline
TAG LENGTH VALUE
Request 20495 47 "1" + "" + "42,63;59,67;69,56;58,37;36,45;34,59;42,63;"
31 00 32 00 34 32 2C 36 33 3B 35 39 2C 36 37 3B 36 39 2C 35 36 3B 35
0A 50 00 00 16 00 00 00 38 2C 33 37 3B 33 36 2C 34 35 3B 33 34 2C 35 39 3B 34 32 2C 36 33
3B 00
0A 50 00 00 02 00 00 00 30 00
Table 2-220
TAG LENGTH VALUE

Request 20495 47 "3" + "2" + "45,55;55,59;57,51;52,45;42,48;44,53;45,55;"
33 00 32 00 34 35 2C 35 35 3B 35 35 2C 35 39 3B 35 37 2C 35 31 3B 35
0A 50 00 00 16 00 00 00 32 2C 34 35 3B 34 32 2C 34 38 3B 34 34 2C 35 33 3B 34 35 2C 35 35
3B 00
0A 50 00 00 02 00 00 00 30 00
Table 2-221

6.43 Closes the editing of an assembled
geometry object
Request With an assembled
geometry object the
commands 20494,
Number 20495 and 20496 must
of bytes
always be sent in this
in the
TLV sequence in order that
Value the object can be fully
created.

"G1" + "G2"
request is "1".
error code)
unknown
Number
TLV
1 Æ The editing of an assembled
geometry object was not
started or no geometry was
added to the object. This
means that the command
20494 or 20495 was called up
beforehand.
Table 2-222
Example: Exit editing of an assembled geometry object.

TAG LENGTH VALUE
Request 20496 0
0A 50 00 00 16 00 00 00
0A 50 00 00 02 00 00 00 30 00
Table 2-223

7. Unicode TLV commands
7.1 Set variable with Unicode data
Sets the content of the assigning variables

" TN1" + "TV1" + ("TN2" + "TV3") must be fulfilled:
+…+ ("TNn" + "TVn") Marking file with variable
must be loaded
TN1: Identifier of variable 1
The variable must be
TV1: Content of variable 1 assigned a text object as
TN2: Identifier of variable 2 a display object
Identification and
TV2: Content of variable 2
content always in pairs;
TNn: Identifier of variable n it is also true that only
TVn: Content of variable n one variable can be set
Limitations:
Number The variable identifier
of bytes may not use characters
20501 in the that are not included in
TLV the ASCII character set.
Value Unicode characters are
introduced with \u and
closed with semicolon
(;).
Multiple Unicode
characters are
transferred separately
(see Example 3).
Barcode display objects
cannot process any Unicode
data.
- Data matrix – with control
character: ~dnnn
nnn = ASCII – decimal value

Sets the content of the assigning variables
"G1" + "G2"
Response when the
error code)
of bytes unknown
assigned ID
Table 2-224

Example 1: Set the content of the "VAR_4" to "Test text"
TAG LENGTH VALUE
Request 20501 30 "VAR_4" + "Testtext"
56 00 41 00 52 00 5F 00 34 00 00 00 54 00 65 00 73 00 74 00 74 00 65
15 50 00 00 1E 00 00 00
00 78 00 74 00 00 00
15 50 00 00 04 00 00 00 30 00 00 00
Table 2-225
Example 2: Set the content of the variables "V1" to "0" and "V2"
to "AB[cr][lf]C" (only applies to the data matrix code)
TAG LENGTH VALUE
Request 20501 42 "V1" + "0" + "V2" + "AB~d013~d010C"
56 00 31 00 00 00 30 00 56 00 32 00 00 00 41 00 42 00 7E 00 64 00 30 00 31
15 50 00 00 2A 00 00 00
00 33 00 7E 00 64 00 30 00 31 00 30 00 43 00 00 00
15 50 00 00 02 00 00 00 30 00
Table 2-226
[cr] = Carriage return (line break)

[lf] = Line feed
Example 3: Set the content of the variables "VAR01" to "This is a

CJK Unified Ideograph: 慸慷"
TAG LENGTH VALUE

Request 20501 94 "VAR01" + "This is a CJK Unified Ideograph: \u0x6178; \u0x6177"
56 00 41 00 52 00 30 00 31 00 00 00 44 00 69 00 65 00 73 00 20 00 69 00 73
00 74 00 20 00 65 00 69 00 6E 00 20 00 43 00 4A 00 4B 00 20 00 55 00 6E
15 50 00 00 5E 00 00 00
00 69 00 66 00 69 00 65 00 64 00 20 00 49 00 64 00 65 00 6F 00 67 00 72 00
61 00 70 00 68 00 3A 00 20 00 78 61 20 00 77 61 20 00 00 00
15 50 00 00 02 00 00 00 30 00
Table 2-227
[慸] = 0x6178
[慷] = 0x6177

7.2 Read variable with Unicode data

"T" must be fulfilled:
Marking file with variable
T: Identifier of the variable
must be loaded
The variable must be
assigned a text object as
Number a display object
of bytes
in the Limitations:
TLV The identification of the
Value variables is not permitted
to use characters that
are not included in the
ASCII character set
data

"G1" + "T" + "G2"
20502
1: Æ Command could not be result of the TLV request
executed (see extended • is "1".
error code)
Number unknown
T: Content of the variable
assigned ID
Table 2-228
Example: Read variable "VAR_4" with "Testtext"

TAG LENGTH VALUE
Request 20502 12 "VAR_4"
16 50 00 00 0C 00 00 00 56 00 41 00 52 00 5F 00 34 00 00 00
Response 20502 22 "Testtext" + "0"
16 50 00 00 16 00 00 00 54 00 65 00 73 00 74 00 74 00 65 00 78 00 74 00 00 00 30 00 00 00
Table 2-229

7.3 Initialize variable with Unicode data
(from TruTops Mark 2.9)
Assigns a new standard value to a variable in the marking file currently opened for editing
" T1" + "T2" must be fulfilled:
T1: Name of the variable
open for editing (TLV
T2: Default value of the variable command "Generate
marking file for editing"
or "Load marking file for
editing").
Limitations:
The variable identifier
may not use characters
Number that are not included in
of bytes the ASCII character set.
in the Unicode characters are
TLV introduced with \u and
Value closed with semicolon
(;).
Multiple Unicode
characters are
transferred separately
(see Example 2).
20503 data.
- Data matrix – with control
character: ~dnnn
nnn = ASCII – decimal value

"G1" + "G2"
Response when the
error code)
of bytes unknown
1: Æ Variable not found
opened for editing
Table 2-230

Example 1: For the variable "VAR_4", set the default value to
"Testtext"
TAG LENGTH VALUE
Request 20503 30 "VAR_4" + "Testtext"
56 00 41 00 52 00 5F 00 34 00 00 00 54 00 65 00 73 00 74 00 74 00 65
17 50 00 00 1E 00 00 00
00 78 00 74 00 00 00
17 50 00 00 04 00 00 00 30 00 00 00
Table 2-231
Example 2: For the variable "VAR01", set the default value to

"This is a CJK Unified Ideograph: 慸慷"
TAG LENGTH VALUE

Request 20503 94 "VAR01" + "This is a CJK Unified Ideograph: \u0x6178; \u0x6177"
56 00 41 00 52 00 30 00 31 00 00 00 44 00 69 00 65 00 73 00 20 00 69 00 73
00 74 00 20 00 65 00 69 00 6E 00 20 00 43 00 4A 00 4B 00 20 00 55 00 6E
17 50 00 00 5E 00 00 00
00 69 00 66 00 69 00 65 00 64 00 20 00 49 00 64 00 65 00 6F 00 67 00 72 00
61 00 70 00 68 00 3A 00 20 00 78 61 20 00 77 61 20 00 00 00
17 50 00 00 02 00 00 00 30 00
Table 2-232
[慸] = 0x6178
[慷] = 0x6177

8. Additional TLV commands
8.1 External program
Starts the assigned program .exe with the assigned parameter string
"T1" + "T2" + "G" must be fulfilled:
The program to be
T1: Name of the program to be
started must be available
started
on the control system
T2: String with the call-up PC and correctly
parameters for the program installed.
Number G: Command execution mode The program name must
of bytes be specified, together
0: Æ Start the program without
in the with the directory.
waiting for the end
TLV 1: Æ Start the program and wait for
Value the end Explanations
• If no call-up
parameters are
used, then an
empty string must
be assigned for this
purpose (see
Example).
20601
"G1" + "G2"
TLV Response
0: Æ Command executed correctly when the result of
1: Æ Command could not be the TLV Request is
executed (see extended "1".
Number error code)
in the unknown
1: Æ Program does not exist
2: Æ Program could not be
started
Table 2-233
Example: Start TruTops Mark® ErrorViewer and wait till the

program has been ended
TAG LENGTH VALUE
Request 20601 44 "c:\TruMark\Fehleranzeige\ErrorViewer.exe" + " " + "1"
63 3A 5C 54 72 75 4D 61 72 6B 5C 46 65 68 6C 65 72 61 6E 7A 65 69
79 50 00 00 2C 00 00 00
67 65 5C 45 72 72 6F 72 56 69 65 77 65 72 2E 65 78 65 00 00 31 00
79 50 00 00 02 00 00 00 30 00
Table 2-234

8.2 DLL function
Executes the assigned function of the DLL specified

"T1" + "T2" + "T3" + "T4" + "G" must be fulfilled:
The DLL must be
T1: Name of the DLL
available on the control
T2: Name of the DLL function system PC.
T3: Call-up parameter 1 of the The DLL name must be
DLL function specified, together with
the directory.
T4: Call-up parameter 2 of the
A function with the
DLL function
corresponding
G: Return type of the DLL function declaration must be
0: Æ Without return parameter available:
Æ extern "C"
1: With return parameter
__declspec(dllexport) void
Number F1(char* in1, char *in2)
of bytes extern "C"
in the __declspec(dllexport) void
TLV F1(char* in, char *out)
Value extern "C"
F2(char* in)
extern "C"
F3(char *out)
extern "C"
F4(void)
20602 Explanations
• If no call-up parameters
are used, then empty
strings must be used for
this purpose (see
Example).
"G1" + "T" + "G2"
G1: Result of the TLV request: Is added on to the TLV
1: Æ Command could not be result of the
executed (see extended TLV Request is "1".
error code)
2: Æ Parameter VALUE is Explanations
Number
unknown If the DLL function has no
of bytes
in the 3: Æ Invalid TLV LENGTH of the return parameter, then an
TLV request for the active empty string will be returned
communication interface in its place.
Value
T: Return parameter of the DLL
function
1: Æ DLL does not exist
2: Æ DLL could not be loaded
3: Æ DLL function does not exist
Table 2-235

Example: Executing DLL function "DEZ_TO_BIN" from the
"Tool.Dll".
TAG LENGTH VALUE
Request 20602 45 "c:\QuickFlow\Tool_Dll.Dll" + "_DEZ_TO_BIN" + "202" + " " + "1"
63 3A 5C 51 75 69 63 6B 46 6C 6F 77 5C 54 6F 6F 6C 5F 44 6C 6C
7A 50 00 2D 00 00 00 2E 44 6C 6C 00 5F 44 45 5A 5F 54 4F 5F 42 49 4E 00 32 30 32 00
00 31 00
Response 20602 11 "0" + "11001010"
7A 50 00 0B 00 00 00 30 00 31 31 30 30 31 30 31 30 00
Table 2-236
8.3 Start laser calibration (LPC) or cancel

(from TTM 2.7)
Start laser calibration or cancel

Request 2 The following conditions
"G1" must be fulfilled:
G1: Status of the laser: 1. No marking process is
allowed to be active.
0: Æ Cancel LPC
2. No external trigger
1: Æ Start LPC signal is allowed to be
pending (Beam ON,
Beam OFF).
3. The ESU must be
initialized (safety circuit
must be closed for at least
10 seconds).
The customer control

software can start or
cancel the LPC by setting
the LPC status parameter.
20603
Digital interfaces are not
operated while the LPC is
running.
Comment 1:
The following firmware is
required for the TM6000:
CIP release from version
V2090 CLH release from
version 2080
V0080
Comment 2:
For the TM3000/TM5000
The following firmware is
required:
CMU_1070

Start laser calibration or cancel
"G1" + "G2"
0: Æ Command executed correctly when the
Number of executed (see extended request is "1".
the TLV
0: Æ OK
1: Æ LPC option not enabled
Table 2-237
Example: Switching on the LPC
TAG LENGTH VALUE
Request 20603 2 "1"
7B 50 00 00 02 00 00 00 31 00
7B 50 00 00 02 00 00 00 30 00
Table 2-238

8.4 LPC status (from TTM 2.7)
Reads the status of the calibration procedure (LPC)

TAG LENGTH VALUE
Response Information direction, laser control system -> PC
G1" + "G2" + "G3" + "G4" + "G5"

1: Æ Command could not be executed (see extended error code)
3: Æ Invalid TLV LENGTH of the request for the active
G2, G3, G4: 0
G5: As soon as the status parameter reaches a value >/= 224, this
means for the external activation or for TruDiag that the
LPC sequence is ended. From this point, it is possible to restart
the LPC sequence
For the TM Series 6000, TM Series 5000, TM Series 3000
22 Æ Laser switched on. Wait until the laser has
reached a stable condition.
24 Æ Laser is ready to perform Wait until a stable power
the calibration. measurement is present.

Reads the status of the calibration procedure (LPC)
Response Information direction, laser control system -> PC
For the TM Series 6000, TM Series 5000, TM Series 3000
32 Æ The measured laser power The laser power is
is too high. reduced.
34 Æ The measured laser power The laser power is
is too low. increased.
48 Æ Optimization of the oven The oven temperature is
temperature. reduced.
50 Æ Optimization of the oven The oven temperature is
temperature. increased.
228 Æ The laser could not be
switched on correctly.
229 Æ Saving parameters is not • The laser control
possible. system switches to
error state
• Restart system using
"Reset"
• Repeat LPC
230 Æ The required laser power The pumping current of the
Number of could not be reached. laser can not be increased
bytes in any further.
the TLV
231 Æ The required laser power The laser power can not be
Value
could not be reached. upscaled any further.
232 Æ The measured output value Repeat LPC
is outside the defined band.
234 Æ The difference between the
measured output value and
the nominal value is so great
that upscaling the power
makes no sense.
235 Æ The laser's pump power has Check LPC parameters.
reached the maximum value.
239 Æ The laser control system • Eliminate errors
has detected an error (error • Restart system using
status). "Reset"
• Repeat LPC
240 Æ LPC has been successfully The laser power value is

completed. within the defined range.
255 Æ LPC was canceled by the
user.
Table 2-239
Example: LPC status for G5 = 240.

TAG LENGTH VALUE
7C 50 00 00 00 00 00 00
Response 20604 10 "0" + "0" + "0" + "240"
7C 50 00 00 0A 00 00 00 30 00 30 00 30 00 32 34 30 00
Table 2-240

8.5 Load camera settings
Note:
The Vision pack "VisionLine Mark Traceability 2" is prerequisite for
executing the commands for the sections with the headings 8.5 to
8.12 and the example 9.13.

"G" + "T" • TTMCameraComponent
must be installed on the
Number G: Camera number device and licensed.
of bytes
0: No camera • XML camera setting file
in the
TLV available in correct format
1: Camera 1
(created with
Value
T: Name and path of the XML TTMCameraComponentCo
configuration file nfig Software)

"G1" + "G2"
Response when the result
of the TLV Request is "1".
error code)
20701
unknown
of bytes
in the response for the active
Value

1: Æ Camera number does not
exist
2: Æ Incorrect configuration file
100: Æ TTMCameraComponent not
installed
licensed
Table 2-241
Example: Load camera configuration file "Camersetting.xml"

TAG LENGTH VALUE
Request 20701 28 "1" + "C:\Temp\Camerasetting.xml"
31 00 43 3A 5C 54 65 6D 70 5C 43 61 6D 65 72 61 73 65 74 74 69
DD 50 00 00 1C 00 00 00
6E 67 2E 78 6D 6C 00
DD 50 00 00 02 00 00 00 30 00
Table 2-242

8.6 Execute camera function
Note: The Vision pack "VisionLine Mark Traceability 2" is
prerequisite for executing the commands for the sections with the
headings 8.5 to 8.12 and the example 9.13.
Request
"G" + "T"+ "G1" The following conditions
TTMCameraComponent must
G: Camera number be installed on the device and
0: No camera licensed.
1: Camera 1
Number
of bytes T: Operations function
in the • ReadDMC
TLV
Value • TrainBrightness
G1: Triggering image capture before
operations function
0: Without image capture
1: With image capture

"G1" + "G2"
error code)
unknown
Value
exist
2: Æ Erroneous command
3: Æ Code not legible
licensed
licensed
Table 2-243
Example: "Read DMC code with the camera"

TAG LENGTH VALUE
Request 20702 12 "1" + "ReadDMC" + "1"
DE 50 00 00 0C 00 00 00 31 00 52 65 61 64 44 4D 43 00 31 00
DE 50 00 00 02 00 00 00 30 00
Table 2-244

8.7 Set tag value


Request
"G" + "T1"+ "T2" The following conditions
G: Camera number
be installed on the device and
1: Camera 1 The following tag designations
apply to T1:
T1: Tag designation • ExposureTime
ExposureTime • TargetBrightness
(Exposure time) • Roi
18 – 200000 μs
TargetBrightness (grayscale)
0 – 255
Number Syntax of the Roi:
of bytes Roi (pixel coordinates)
x1 y1 x2 y2 (a space is
20703 in the (x1/y1 – x2/y2) required as separator)
TLV
Value T2: Tag value
18 – 200000 μs (exposure time)
0 – 255 (grayscale)
Roi (pixel coordinates)

x1: min: 0 max. 1536
Set the pixel coordinates
y1: min: 0 max. 1136 manually.
x2: min: 64 max. 1600

y2: min: 64 max. 1200

"G1" + "G2"
error code)
unknown
in the
TLV
Value
exist
licensed
licensed
Table 2-245
Example: "Set the exposure time" to 5000 us

TAG LENGTH VALUE
Request 20703 20 "1" + "ExposureTime" + "5000"
DF 50 00 00 14 00 00 00 31 00 45 78 70 6F 73 75 72 65 54 69 6D 65 00 35 30 30 30 00
DF 50 00 00 02 00 00 00 30 00
Table 2-246

8.8 Read tag value

Request
"G" + "T" The following conditions
• TTMCameraComponent must
G: Camera number
1: Camera 1
n: Camera >1
T: Tag designations • The following tag
CodeContent designations are valid for T
CodeResult and are described in a
ExposureTime documentation on
TargetBrightness "VisionLineMark Traceabiliy
Roi 2".
CodeSymbology
CodeModuleSize
CodeAngle
CodeSymbolContrast
Number CodeSymbolContrastGrade
of bytes CodeAxialNonUniformity
20704 in the CodeAxialNonUniformityGrade
TLV CodePrintGrowth
CodePrintGrowthGrade
Value CodeUnusedErrorCorrection
CodeUnusedErrorCorrectionGrade
CodeModulation
CodeModulationGrade
CodeFixedPatternDamage
CodeFixedPatternDamageGrade
CodeMinimumReflectance
CodeMinimumReflectanceGrade
CodeGridNonUniformity
CodeGridNonUniformityGrade
CodeExtremeReflectance
CodeExtremeReflectanceGrade
CodeEdgeContrastMin
CodeEdgeContrastMinGrade
Only the 1D codes:
CodeSingleScanInt
CodeSingleScanIntGrade
CodeMultiScanInt
CodeMultiScanIntGrade

"G1" + "T" + "G2"
error code)
Value T Tag value
exist
licensed
licensed
Table 2-247
Example: Read out the "CodeContent" tag from the camera

TAG LENGTH VALUE
Request 20704 14 "1" + "CodeContent"
E0 50 00 00 0E 00 00 00 31 00 43 6F 64 65 43 6F 6E 74 65 6E 74 00
E0 50 00 00 07 00 00 00 30 00 30 2E 31 35 00
Table 2-248

8.9 Capture image

"G" • TTMCameraComponent
Number must be installed on the
of bytes G: Camera number device and licensed.
in the 0: No camera
TLV
1: Camera 1
Value
n: Camera >1

"G1" + "G2"
error code)
20705 2: Æ Parameter VALUE is
unknown
Number
of bytes
in the
TLV
Value
exist
licensed
licensed
Table 2-249
Example: Capture image "c:\temp\Test1.bmp"

TAG LENGTH VALUE
Request 20705 02 "1"
E1 50 00 00 02 00 00 00 31 00
E1 50 00 00 02 00 00 00 30 00
Table 2-250

8.10 Load image in camera (not yet
implemented)

"G" + "T1" • TTMCameraComponent
G: Camera number device and licensed.
Number 0: No camera • Image saved in BMP
of bytes format with Cognex
1: Camera 1
Dataman is available.
in the
TLV n: Camera >1
Value T1: Name and path of the image Note:
This function is not currently (The "Load image in camera"

implemented. However, calling the function is not yet working!)
function does not lead to any error.

"G1" + "G2"
error code)
unknown
in the
TLV
Value
exist
3: Æ Name or path is incorrect
licensed
licensed
Table 2-251
Example: Load image "c:\temp\Test.bmp" in the

camera
TAG LENGTH VALUE
Request 20706 19 "1" + "c:\temp\Test.bmp"
E2 50 00 00 13 00 00 00 31 00 63 3A 5C 74 65 6D 70 5C 54 65 73 74 2E 62 6D 70 00
E2 50 00 00 02 00 00 00 30 00
Table 2-252

8.11 Save image


"G" + "T1" • TTMCameraComponent
G: Camera number device and licensed.
Number
of bytes 0: No camera • Image available in the
in the camera's memory.
1: Camera 1
TLV 20705 ("Record
TLV
n: Camera >1 picture") must have been
Value
executed without error.
T1: Name and path of the image
Save on drive for analysis.

"G1" + "G2"
error code)
20707
unknown
of bytes
in the
TLV
exist
4: Æ Read only in the directory
licensed
licensed
Table 2-253
Example: Save image "c:\temp\Test1.bmp"

TAG LENGTH VALUE
Request 20707 20 "1" + "c:\temp\Test1.bmp"
E3 50 00 00 14 00 00 00 31 00 63 3A 5C 74 65 6D 70 5C 54 65 73 74 31 2E 62 6D 70 00
E3 50 00 00 02 00 00 00 30 00
Table 2-254

8.12 Query available cameras


No data The following conditions

Request 0
licensed.

"G1" + "G2"
error code)
20708 unknown
of bytes
in the
TLV
exist
4: Æ Read only in the directory
licensed
licensed
Table 2-255
Example: Save image "c:\temp\Test1.bmp"

TAG LENGTH VALUE
Request 20708 0
E4 50 00 00 00 00 00 00 31 00 63 3A 5C 74 65 6D 70 5C 54 65 73 74 31 2E 62 6D 70 00
Response 20708 4 "0" + "1"
E4 50 00 00 04 00 00 00 30 00 31 00
Table 2-256

9. Sample processes for activation of the
laser marking system with TLV
sequences
The following prerequisites apply for the sample processes:

• Operation with TruTops Mark®
• The laser marking system has not been initialized as yet
(switch on beam source, open shutter, ...).
• The examples are only intended to display the procedural
principles for utilizing TLV Commands and will still need to be
supplemented and/or adjusted for concrete applications.
Directory reference:
C:\trumark\communication interface\Samples
9.1 Example_01
Load and mark a marking file without
variables
TLV Commands
No. Customer writes Explanation
(TAG)
1 20201 Laser/shutter (Laser on/shutter open)
2 20401 Load marking file (marking file without variables)
3 20222 Query conversion status
4 20261 Check laser status
5 20204 Start marking

File "Sample_01" Table 2-257

9.2 Example_02
Load and mark a marking file without
variables for which the marking has
been moved and scaled
TLV Commands
(TAG)
2 20401 Load marking file (marking file without variables)
4 20423 Scaling/displacement
(This change is not displayed in the Mark preview!)
5 20402 Convert marking file
9 20423 Scaling/displacement
(This change is not displayed in the Mark preview!)
Response should be: Bit 7-0=00011111 / Bit 15-8=01011011


9.3 Example_03
Load and mark a marking file
with three variables
TLV Commands
(TAG)
2 20401 Load marking file (marking file with 3 variables)
4 20421 Set variable 1


9.4 Example_04
Create a marking file Add objects and
mark the created marking file
TLV Commands
(TAG)
2 20461 Generating marking file for editing
3 20471 Adding a line
4 20473 Add a circle
5 20475 Adding a text
6 20464 Save the marking file opened for editing
7 20401 Load marking file
10 20403 Mark marking file X (with X = Name of the previously saved

marking file)

9.5 Example_05
Add a rectangle and a line to an
existing marking file and mark the
revised marking file
TLV Commands
(TAG)
2 20462 Load marking file for editing
3 20461 Generating new marking file for editing
4 20474 Adding a rectangle
5 20471 Adding a line

marking file)

9.6 Example_06
Include a CAD file in a marking file and
mark the modified marking file
TLV Commands
(TAG)
2 20462 Load marking file for editing
3 20463 Include CAD file

marking file)

9.7 Example_07
Mark 2 points without marking file
using scanner beam monitoring
TLV Commands
(TAG)
2 20283 Initialization of beam monitoring through the scanner
(setting the power, frequency, pulse width and position for
the first point)
3 20284 Scanner beam monitoring (activate beam source)
4 20284 Scanner beam monitoring (deactivate beam source after the
desired time)
5 20283 Initialization of beam monitoring through the scanner
(setting the power, frequency, pulse width and position for
the second point)
6 20284 Scanner beam monitoring (activate beam source)
7 20284 Scanner beam monitoring (deactivate beam source after the
desired time)

9.8 Example_08
Load, convert and activate the marking
file in the 2 scanner lists
TLV Commands
(TAG)
2 20401 Load marking file (marking file with 1 variable)
4 20421 Set variable
7 20441 Load marking objects in scanner list 1
-Reset Restart Counter = 1
-Load laser parameters = 1
Retrigger mode…
8 20442 Activate scanner list 1
9 --- A positive edge at X20 input = Retrigger starts the marking of
the vectors from list 1 of the Scanlab card
10 20421 Set variable
15 20207 Query marking status
16 --- A positive edge at X20 input E15 = Retrigger starts the
marking of the vectors from list 2 of the Scanlab card

9.9 Example _09
Load and mark a marking file with a
variable that is set with Unicode data
TLV Commands
(TAG)
2 20401 - Load marking file (marking file with one variable)
4 20501
This is a CJK Set Unicode variable
Unified Ideograph:


9.10 Example_11
Load the marking file in scanner list
and set the MOF parameters
TLV Commands
(TAG)
2 20401 Load marking file (marking file with 1 variable)

Activate retrigger mode and set MOF
Restart_mark / Abort_mark = 1 is activated
7 20234 Overwrite MOF parameter temporarily
Start delay =0
Simulation ext. Start = 0
Scaling X Encoder = 0.20
Scaling X Encoder = 0.20
8 --- A positive edge at X20 input E15 = Retrigger starts the

marking of the vectors from list 1 of the Scanlab card

9.11 Example_12
Demonstration of using automated
Binning
TLV Commands
(TAG)
Preparation (only perform at start):
2 20401 - Load marking file (marking file with one variable)
Loop (carry out for each marking):
4 20421 Set 'Code' variable (if any)
(only required here if variables are used)
6 20244 Bring matrix file and customer binning file together
Sample_12_matrix_copy.xml is a copy of the original matrix

file. The original matrix file is overwritten during conversion.
Sample_12_custom_binning.xml must be filled with the

current values for each marking.
custom_binning.xml has a different format than the binning

file created by the matrix generator.
EndLoop

9.12 Example_13
TLV conversion statuses (G2) with
variable
TLV Commands
(TAG)
3 20402 Carry out conversion
4 20222 Query conversion status again and when = 0, then execute

next command
5 20205 Start marking (without waiting for the end)
6 20207 Query marking status again and when = 0, then execute next
command
7 20421 Reset variable
8 20402 Carry out conversion
9 20222 Query conversion status again and when = 0, then execute

next command
(No marking status query necessary!)

9.13 Example_14
Execute camera function and carry out
code analysis.
TLV Commands
(TAG)
1 20708 Display available cameras
2 20701 Load camera settings
3 20702 Execute camera function: "ReadDMC" with image capture
4 20704 TLV value: Read "CodeResult" -> Read code [0 / 1]
5 20704 TLV value: Read "CodeContent" -> Code content [String]
6 20704 TLV value: Read "CodeSymbolContrast" -> [0…1.0]
7 20704 TLV value: Read "CodeSymbolContrastGrade" -> [A….F]
8 20704 TLV value: Read "CodeAxialNonUniformityGrade" -> [A….F]

SW TLV en PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SW TLV en PDF

Загружено:

Авторское право:

Доступные форматы

Interface description

TLV commands and interpreter

TLV commands and

Material number: 1436502

Chapter 1 Command-interpreter user interface for

1. Functional scope of the command-interpreter ........... 1-3

2. Starting the TLV command interpreter ........................ 1-5

3. Application window ....................................................... 1-5

Chapter 2 TLV Commands

1. Structure of TLV Commands/TLV

2. Structure of the TLV Command Listings..................... 2-8

3. TLV commands for laser control system .................. 2-13

SW-TLV-EN 2017-02-23 Table of contents 5

4. TLV commands for Mechanics SW module .............. 2-56

6 Table of contents 2017-02-23 SW-TLV-EN

5. TLV commands for the digital interface .................... 2-81

6. TLV commands for the marking control system ...... 2-90

SW-TLV-EN 2017-02-23 Table of contents 7

7. Unicode TLV commands ........................................... 2-142

8. Additional TLV commands ....................................... 2-148

9. Sample processes for activation of the laser

8 Table of contents 2017-02-23 SW-TLV-EN

SW-TLV-EN 2017-02-23 Table of contents 9

2. Starting the TLV command interpreter ........................ 1-5

3. Application window ....................................................... 1-5

SW-TLV-EN 2017-02-23 1-1

The supported TLV commands are described in chapter 2

SW-TLV-EN 2017-02-23 1-3

This type of communication is used together with Profibus DP

1-4 SW-TLV-EN 2017-02-23

Start TruTops Mark®.

After starting the command-interpreter successfully, it is displayed

Initial screen of the command interpreter Fig. 1-2

The user interface (GUI) of the command-interpreter basically

SW-TLV-EN 2017-02-23 1-5

The current status of the communication interface is displayed via

• The communication interface is not ready as yet to replace

• The communication interface is ready to replace TLV

• The communication interface is reset or configured at present

• Communication interface is in the error state (status color is

The statuses, causes and possible error correction measures can

1-6 SW-TLV-EN 2017-02-23

The executed TLV commands can be executed here, where

Example of a TLV sequence Fig. 1-3

• Structure of a recorded TLV sequence:

Example of an individual TLV command Fig. 1-4

• Structure of a recorded TLV command:

SW-TLV-EN 2017-02-23 1-7

The command-interpreter function can be controlled using

• Controlling the monitor

3.3.1. "F2 Monitor on/Monitor off"

Statuses of the F2 button Fig. 1-6

This button can be used to start or stop the recording of the

• Recording that has stopped

3.3.2. "F3 Clear Monitor"

This button can be used to delete the monitor recording.

1-8 SW-TLV-EN 2017-02-23

This button can be used to configure the command-

Configuration dialog box of the command-interpreter Fig. 1-7

The following configuration options are available:

Default name of the LOG file: "CMI.LOG"

SW-TLV-EN 2017-02-23 1-9

Statuses of the F5 button Fig. 1-8