SB ProfiBus ProfiNet TM1356 en

Interface description
Profibus / Profinet
Profibus / Profinet
Edition: 2013-11-28
Material number 1892890

SB-EN-245
Order Information Please specify when ordering this document:
Profibus / Profinet
2013-11-28
SB-EN-245
Material number 1892890
Address for orders
© TRUMPF Laser Marking Systems AG

Table of contents
Chapter 1 Overview of the connection
1. Connection type ............................................................. 1-3

1.1 Goal of the connection ..................................................... 1-3
1.2 Technologies and PCI card ............................................. 1-3
1.3 Software ........................................................................... 1-4
1.4 Accessories...................................................................... 1-4
1.5 Types of actuation ........................................................... 1-5
1.6 Process data interface ..................................................... 1-5
1.7 Structure of a TLV command ........................................... 1-6
1.8 Principle of the TLV communication ................................ 1-7
Chapter 2 User interface
1. Scope of functions of the interface ............................. 2-3
2. User interface ................................................................. 2-4

2.1 Menu bar .......................................................................... 2-5
1 File ........................................................................... 2-5
2 Extras....................................................................... 2-5
2.2 Status display .................................................................. 2-7
Waiting for data exchange .......................................... 2-7
Data exchange active ................................................. 2-7
Reset & configuration ................................................. 2-8
Error ............................................................................ 2-8
2.3 Monitor area ..................................................................... 2-9
Process data ............................................................... 2-9
Message data (PROFIBUS) ..................................... 2-10
DP info ...................................................................... 2-11
3. Configurations ............................................................. 2-12

3.1 PROFIBUS..................................................................... 2-12
General tab ............................................................... 2-13
Tab Profibus ............................................................. 2-14
3.2 PROFINET ..................................................................... 2-16
General tab ............................................................... 2-17
SB-EN-245 2013-11-28 Table of contents 5

Tab ProfiNet.............................................................. 2-18
4. Diagnosis ...................................................................... 2-19

4.1 PROFIBUS..................................................................... 2-19
Device tab ................................................................. 2-19
Firmware tab ............................................................. 2-20
Bus state tab ............................................................. 2-21
4.2 PROFINET ..................................................................... 2-22
Device information .................................................... 2-22
Chapter 3 The process interface

1. Introduction .................................................................... 3-3
1.1 Basic structure of the process data interface .................. 3-3
1.2 Configuration options for the process data interface ....... 3-4
1.3 Access to the process data interface............................... 3-5
2. Definitions for PBIM0 .................................................... 3-6
6. Definitions for PBOM1................................................. 3-10
Chapter 4 Logs
1. Introduction .................................................................... 4-3

Communication matrix ................................................ 4-3
2. Types of actuation of the TruMark series ................... 4-3

2.1 Actuation via TLV commands .......................................... 4-3
Definition of the employed TLV notation .................... 4-4
2.2 Additional activation via bit information ........................... 4-4
Table of contents 2013-11-28 SB-EN-245

6
3. Actuation via DP mode.................................................. 4-5
3.1 Realization concept for actuation via TLV
sequences........................................................................ 4-5
Structure of the DP data buffer ................................... 4-7
Handshake mechanism .............................................. 4-8
Error handling ........................................................... 4-11
3.2 Realization concept for the additional activation via
bit information ................................................................ 4-11
Chapter 5 Installation of the cifX card

1. General............................................................................ 5-3
2. Software installation for the Hilscher cifX card .......... 5-4
2.1 Installation of the cifX device driver ................................. 5-4
3. Hardware installation of the cifX card ......................... 5-7

3.1 General ............................................................................ 5-7
Delivery condition of the cifX card .............................. 5-7
Setting the rotary switch ............................................. 5-7
3.2 TruMark Series ................................................................ 5-9
Installation position of the cifX card ............................ 5-9
Installing the cifX card at the PCI system
interface .................................................................... 5-10
4. Configuration of the cifX card .................................... 5-11

4.1 ProfiBus ......................................................................... 5-11
Setting the slot and firmware .................................... 5-11
4.2 ProfiNet .......................................................................... 5-15
5. Expanding TruTops Mark settings ............................. 5-19

5.1 Configuring the ProfiBus ................................................ 5-26
Connect cable, green status ..................................... 5-27
5.2 Configuring ProfiNet ...................................................... 5-28
SB-EN-245 2013-11-28 Table of contents 7

Table of contents 2013-11-28 SB-EN-245
8
Chapter 1
Overview of the connection

1. Connection type ............................................................. 1-3
1.1 Goal of the connection ..................................................... 1-3
1.2 Technologies and PCI card ............................................. 1-3
1.3 Software ........................................................................... 1-4
1.4 Accessories ..................................................................... 1-4
1.5 Types of actuation ........................................................... 1-5
1.6 Process data interface ..................................................... 1-5
1.7 Structure of a TLV command ........................................... 1-6
1.8 Principle of the TLV communication ................................ 1-7
SB-EN-245_K1.DOCX Connection type 1-1

1-2 Connection type SB-EN-245_K1.DOCX
1. Connection type
You will receive information about the following subject areas:

Goal of the connection
Technology and PCI card
Software
Accessories
Types of actuation
Process data interface
Structure of a TLV command
Principle of the TLV communication
1.1 Goal of the connection
The activation of the TruMark series is done via the cifX technology
1
and by using TLV commands and/or the bit interface.
1.2 Technologies and PCI card
Technology
PC cards for real-time Ethernet and field bus on the basis
of Hilscher cifX technology
Support field bus logs
PROFIBUS DP
PROFIBUS DPV1:ÆMSAC_C1 services:
DS_Read/DS_Write
Support logs Real-time Ethernet 2
ProfiNet IO
PCI cards
cifX 50-DP(M/S): PCI card for ProfiBus DP
cifX 50-RE: PCI card for real-time Ethernet log
1
cifX communication for the PC-based automation, source: www.Hilscher.com
2
"RealTime ethernet" from the Hilscher company is used to differentiate from
the field bus variant. TRUMPF ensures no real time application.

1.3 Software
The software for the interface of the connection is available in

German and English:
User interface (BOF): for Profibus and real time Ethernet
connection
Monitoring
Configuration (e.g.: bus address, mode ...)
Diagnostics (e.g.: information about PC card, baud rate,
configuration, ...)
User interface: command interpreter
Monitoring of the TLV command and the status of the
connection
Configuration (e.g.: log mode, ...)
1.4 Accessories
The following accessories are available for the connection:

Device master file (GSD, GSDML) file for the connection in
external programming tools (such as SIEMENS Portal)
Technical documentation
User interface for interface and command interpreter
Process data interface of the bit interface
Log for TLV communication via profibus DP/DPV1
(Decentralized Periphery Version 1)
Description of the TLV command for the TruMark series
Only for the ProfiBus DP:

Function module for Siemens SPS: S7-300 CPU 315-2 DP
Activation of the TruMark series via TLV command with
Profibus DP
Additional activation via the bit interface with Profibus DP
Sample program
Activation of the TruMark series via TLV command with
Profibus DPV1
Integration of the function module in S7-300

1.5 Types of actuation
There is a simple activation and also a complex activation.

Simple actuation of the TruMark series via bit information (e.g.:
control inputs/outputs of the digital interface)
Use of the profibus DP (cyclical)
Use of ProfiNet IO
Additional complex activation of the TruMark series via TLV
command (e.g.: loading of a marking file)
Communication type 1: (asynchronous)
ProfiBus DP
ProfiNet IO
Communication type 2: DPV1 (asynchronous)
Only ProfiBus
Implementation via the MSAC1_Dienste:
DS_Read/DS_Write
1.6 Process data interface
The Process Data Interface (PDI) for the TruMark series is divided
into two areas with a maximum of six modules:
Area for the control of the TruMark series via bit information.
– These modules always must be configured:
Identificatio Length
Module type Contents
n (byte)
PBIM0 Laser/procedure status
2 Word Input
PBIM1 (consistent) Digital interfaces - inputs E1-
E16/E17-E24
4
PBOM0 Laser/sequence control
2 Word Output
PBOM1 (consistent) Digital interface - output A1-
A16/RFU
Tab. 1-2
Area for the control of the TruMark series via TLV command.
– These modules only have to be configured if the Profibus
DP is used for this:
Identificatio Length
Module type Contents
n (byte)
PBIM2 64 Word Input Reception buffer for TLV
commands
128
PBOM2 64 Word Output Transmit buffer for TLV
commands
Tab. 1-1
Diagram for access to the process data
interface

Fig. 1890
1.7 Structure of a TLV command
TLV stands for TAG (day) / LENGTH / VALUE

A TLV command is also built from these three parts.
Description Size of data
TAG Identification of the command
4 byte
LENGTH Number of user data in the VALUE field
VALUE Call-up or return parameter of the n* bytes
command (user data of the command) (Max. 64 Kbyte)
Tab. 1-3
TAG and VALUE are given as decimal numbers

The value is given as null-terminated ASCII string.
Example with the text "HALLO"
– ASCII representation: "HALLO"
– HEX representation: 48 41 4C 4C 4F 00

1.8 Principle of the TLV communication
The TLV communication is structured as a sequence of TLV

request and TLV response:
The TLV request corresponds to the request of a service (e.g.:
set outputs/read inputs)
The TLV response corresponds to the request of the service
(e.g.: result of the service execution/status of the inputs)
Fig. 1891
Example of the TLV commands: N text variables

TAG LENGTH VALUE
Request "123" + "456" + "abc"
12
31 32 33 00 34 35 36 00 61 62 63 00
20409
Response "0"
2
30 00
Tab. 1-4

Chapter 2
User interface
1. Scope of functions of the interface ............................. 2-3
2. User interface ................................................................. 2-4

2.1 Menu bar .......................................................................... 2-5
1 File ........................................................................... 2-5
2 Extras....................................................................... 2-5
2.2 Status display .................................................................. 2-7
Waiting for data exchange .......................................... 2-7
Data exchange active ................................................. 2-7
Reset & configuration ................................................. 2-8
Error ............................................................................ 2-8
2.3 Monitor area ..................................................................... 2-9
Process data ............................................................... 2-9
Message data (PROFIBUS) ..................................... 2-10
DP info ...................................................................... 2-11
3. Configurations ............................................................. 2-12

3.1 PROFIBUS .................................................................... 2-12
General tab ............................................................... 2-13
Tab Profibus ............................................................. 2-14
3.2 PROFINET ..................................................................... 2-16
General tab ............................................................... 2-17
Tab ProfiNet.............................................................. 2-18
SB-EN-245_K2.DOCX Scope of functions of the interface 2-1

4. Diagnosis ...................................................................... 2-19
4.1 PROFIBUS .................................................................... 2-19
Device tab ................................................................. 2-19
Firmware tab ............................................................. 2-20
Bus state tab ............................................................. 2-21
4.2 PROFINET ..................................................................... 2-22
Device information .................................................... 2-22
2-2 Scope of functions of the interface SB-EN-245_K2

1. Scope of functions of the interface
Using an interface, it is possible to control the

"TruMark series" by a fieldbus connection or the RealTime
Ethernet.
The following images and texts apply to both the PROFIBUS
as well as the RealTime Ethernet interface. This will be
called "interface" below.
For the "TruMark series", TLV commands
and, additionally, a bit interface will be used.
The structure of the TLV commands or a list of the TLV
commands can be found in the document "TLV-
Kommandos und Interpreter für das Softwareprogramm
TruTops Mark" ("TLV commands and interpreter for the
TruTops Mark program").
The description of the bit interface or the process data
interface can be found in chapter 3 "Process interface" of this
document.
The basic functions of the user interface for the Profibus

interface are:
The monitoring of the process data
Configuration of the slave card(s)
Diagnostics of the slave card and the respective bus
Different communication types are used for the

communication whose description can be found in the
document chapter 4 "Logs".
Differences which result from the use of the TruTops Mark
control program are marked at the corresponding places and
explained.
SB-EN-245_K2.DOCX Scope of functions of the interface 2-3

2. User interface
After the user interface has been successfully started with

the respective interface, you will be shown the following
application window.
Application window Fig. 1936
The user interface of the interface basically consists of three

parts which are described in detail in the following sections.
• Menu bar (3.1) for selection of different functions.
• Status display (3.2) for optical representation of the
status of the interface.
• Monitor area (3.3) with different tabs to represent the bit
interface and the process data level.
2-4 User interface SB-EN-245_K2.DOCX

2.1 Menu bar
The menu bar contains the two main menu names 1 File and
2 Extras. They are structured as follows:
1 File
Application window Fig.1937
By clicking on the command sequence 1 File > 1 Close, the

user interface of the interface is closed. The interface,
however, remains loaded in the background and is still fully
functional.
2 Extras
Different settings for each interface and the respective slave

card can be made using the 2 Extras main menu name.
An input dialog box is started for this. The individual settings
are then explained in more detail.
SB-EN-245_K2.DOCX User interface 2-5

2 Extras > 1 Configuration...
Click on the command sequence 2 Extras > 1
Configuration... An input dialog box is started. The
individual settings are explained in more detail in section 3
Configuration.
2 Extras > 2 Device info...

Click on the command sequence 2 Extras > 2 Device info...
Different diagnostics information about the interface and the
slave card can be shown.
An input dialog box is started for this. The individual
diagnostics information is explained in more detain in section
4 Diagnostics.
2 Extras > 3 Reset device

Click on the command sequence 2 Extras > 3 Reset device.
A reset of the slave card and the respective interface will be
carried out.

2.2 Status display
An LED is used here to show the current status of the

interface is displayed. The arrangement of the individual
statuses/colors is described below.
Waiting for data exchange
Gray status display Fig.1939
Status (LED is gray) The slave card waits until it can change to the "Data
exchange active" status. No data is exchanged with the
controlling master.
Reason
The slave card waits until a connect connection with the
assigned master has been established.
Remedy
Check the following points and perform a reset of the two
participants:
• Has the master been started?
• Is the slave correctly connected to the respective bus?
• Has the slave received the correct bus address or correct
device names?
• Do the configurations of the master and the slave match?
Data exchange active
Light green status display Fig. 1940
Status (LED is light green) The slave card is in its normal operating status. A data
exchange is taking place with the assigned controlling
master.

Reset & configuration
Yellow status display Fig. 1941
Status (LED is yellow) The slave card performs a reset. No data exchange is taking
place with the assigned controlling master.
Reason
You have caused a reset of the slave card by either by the
command sequence 2 Extras > 3 Reset device or by
changing the configuration.
Error
Red status display Fig. 1942
Status (LED is red) The interface is waiting until a previously reported error has
been eliminated. No data exchange is taking place with the
assigned controlling master.
Reason
The interface has detected an error (for example, the slave
card, device drivers, or the manufacturer's CifX driver). The
exact details can be found in the displayed error message.
Remedy
Correct the cause of error and perform a reset of the slave
card by using the command sequence 2 Extras > 3 Reset
device.

2.3 Monitor area
The monitor area contains three tabs to display the data

exchange. The "Message data" tab is used only for
PROFIBUS. The structure of the individual tabs is discussed
in detail below.
Process data
In the Process data tab, the current data of the process data
interface is recorded with the configured modules (also see
chapter 3, "Process - Interface") for DP communication.
The "Process data" tab is divided into two areas:

Received data with the three modules PBOM0 / PBOM1 /
PBOM2
Sent data with the three modules PBIM0 / PBIM1 / PBIM2

Message data (PROFIBUS)
The received/sent DPV1 messages for PROFIBUS-DPV1

communication are recorded in the Message data tab.
The "Message data" tab is divided into two areas:

Received DPV1 messages with the individual DPV1 message
components.
Sent DPV1 messages with the individual DPV1 message
components.

DP info
The statuses of the receive/send handshake counter are

recorded in the DP info tab for asynchronous DP
communication.

3. Configurations
3.1 PROFIBUS
The dialog for the configuration of the PROFIBUS interface

is divided into the two tabs, Profibus and General, which
are described in detail below for the TruTops Mark control
software.
General parameter In the bottom part of the Profibus -> Configuration dialog box,
there are three buttons with the following meaning:
OK: The configuration dialog box is complete and
modifications will be saved.
Cancel: The configuration dialog box will be ended and
modifications discarded.
Reset: The configuration parameters will be set to their
default values.
2-12 Configurations SB-EN-245_K2.DOCX

General tab
The possible settings in the General tab are listed in the following
table.
Parameter Selection options Description
Card selection Automatic selection • The installed PROFIBUS device card with the
lowest card number is used.
Card number • Only visible when "Automatic selection" is not
selected.
• Card number of the installed PROFIBUS slave
card
• Value range: 0 to 3
Error output Normal • A general error number is displayed for errors that
are caused by the PROFIBUS slave card.
Detailed • The manufacturer-specific error number is
displayed for errors that are caused by the
PROFIBUS slave card.
Word module handling Swap low/high byte • Low and high bytes of the Word module will be
swapped after receipt.
Master/slave Compare configuration • The configuration received from the master is
configuration compared with the slave configuration.
If there is a difference, the PROFIBUS interface
will go into error status.
TLV response handling Synchronous • VMC triggers the sending of
"MSAC_C1_Read_Res" when the TLV response
is received.
Polling • Sending "MSAC_C1_Read_Res" when the TLV
response is received must be poled from the
PROFIBUS master (see chapter 4 "Control via
PROFIBUS-DPV1").
Tab. 1
SB-EN-245_K2.DOCX Configurations 2-13

Tab Profibus
The possible settings in the Profibus tab are listed in the following
table.
Communication mode DP mode 1 • Control with TLV commands via PROFIBUS-DP.
• In addition, activation with a bit interface is
possible via PROFIBUS DP.
• For this, the configured modules PBIM2 and
PBOM2 are used.
(Also see the log description)
• The module size from PBIM2 and PBOM2 can be
selected using the "Module size PBIM2 / PBOM2"
setting.

DPV1 mode • Control with TLV commando via Profibus DPV1.
(Also see log description)
• In addition, activation with a bit interface is
possible via PROFIBUS DP.
Module size PBIM2 / 64 Word • Only visible when "DP mode 1" has been selected
PBOM2
as communication mode.
32 Word • Observe the maximum TLV length that results
from the set module size.
20 Word
max. PBOM2 size • Asymmetrical configuration:

Reception buffer for TLV request: 236 bytes
Miscellaneous Bus address of the slave • The PROFIBUS address of the PROFIBUS device
card can be configured here.
DPV1 data size • Only visible when "DPV mode 1" has been
selected
as communication mode.
• The maximum number of data bytes of a DPV1
message can be configured here.
Tab. 2

3.2 PROFINET
The dialog for the configuration of the PROFINET interface is

divided into the two tabs, ProfiNet and General, which are
described in detail below for the TruTops Mark control
software.
Dialog box. Fig. 1948
General parameter In the bottom part of the ProfiNet -> Configuration dialog box,
there are three buttons with the following meaning:
OK: The configuration dialog box is complete and
modifications will be saved.
Cancel: The configuration dialog box will be ended and
modifications discarded.
Reset: The configuration parameters will be set to their
default values.

General tab
The possible settings in the General tab are listed in the following
table.
Card selection Automatic selection • The installed slave card with the lowest card
number is used.
Card number Not supported at the moment
Error output Normal • A general error number is displayed for errors that
are caused by the slave card.
Detailed • The manufacturer-specific error number is
displayed for errors that are caused by the slave
card.
Word module handling Swap low/high byte • Low and high bytes of the Word module will be
swapped after receipt.
Tab. 3

Tab ProfiNet
Fig. 1949
The possible settings in the ProfiNet tab are listed in the following
table.

Device name None Final device name which is used in the controller
application.
Modele size None Display which process data size is supported.
Tab. 4

4. Diagnosis
4.1 PROFIBUS
The dialog box for the diagnostics is divided into three tabs which
are described below.
Device tab
The hardware-specific information for the installed

PROFIBUS slave card is shown in the Device tab:
• Device date (date of manufacturer)

• Device type
• Device number
• Device model
• Series number
• Device identifier (device ID)
SB-EN-245_K2.DOCX Diagnosis 2-19

Firmware tab
The software-specific information for the installed

PROFIBUS slave card is shown in the Firmware tab:
• Name of the PROFIBUS slave card

• Firmware version of the PROFIBUS slave card
2-20 Diagnosis SB-EN-245_K2.DOCX

Bus state tab
Profibus-specific information is shown in the bus state tab.
• Baud rate and bus address

• PROFIBUS "Ident number" and "Task state"
• Total number of input and output bytes of the slave
configuration
• Configuration of the slave and the configuration which
the master has sent to the slave.
• Standard and user parameters which the master has
sent to the slave
SB-EN-245_K2.DOCX Diagnosis 2-21

4.2 PROFINET
The dialog for the diagnostics is described below.
Device information
The hardware-specific information for the installed

PROFINET IO device card is in the application window.
2-22 Diagnosis SB-EN-245_K2.DOCX

Chapter 3
The process interface

1. Introduction .................................................................... 3-3
1.1 Basic structure of the process data interface .................. 3-3
1.2 Configuration options for the process data interface ....... 3-4
1.3 Access to the process data interface............................... 3-5
SB-EN-245_K3.DOCX Introduction 3-1

3-2 Introduction SB-EN-245_K3.DOCX
1. Introduction
In this document, the structure of the process data interface

(PDI) for the control of the "TruMark series" via field bus and
real-time Ethernet is described.
1.1 Basic structure of the process data

interface
The process data interface for the "TruMark series" is divided up

into two areas and consists of no more than six modules:
The data area for easy control of the "TruMark series" via
"commands without call-up parameters"
(-> Representing individual commands on bit information).
- These four modules always must be configured.
Identification Length Module type Contents

[byte]
PBIM0 2 Word Input (consistent) Laser/procedure status
PBIM1 Digital interface E1-E16 / E17-E24
4
PBOM0 2 Word Output (consistent) Laser/sequence control
PBOM1 Digital interface A1-A16 / RFU
PBIM0,PBIM1, PBOM0 and PBOM1 bit interface PDI Tab. 1
Data area for complex control of the "TruMark series" via

commands with various call-up parameters (-> representation
of the commands in TLV notation):
- These two modules only have to be configured if TLV
commands are used.
Length
Identification Module type Contents
[byte]
PBIM2 nx2 n Word Input Reception buffer for TLV commands
PBOM2 nx2 n Word Output Transmit buffer for TLV commands
PBIM2, PBOIM2 of the PDI Tab. 2
Module sizes: 20 / 32 / 64 Word (depending on the configured

module for PBIM2 or PBOM2)

1.2 Configuration options for the process
data interface
The final structure of the process data interface depends on the

communication mode that is used and configured and is described
in the following two sections.
See the document chapter 2 "User interface"
Structure of the PDI for "DP In the "DPV1 mode" communication mode, the PBIM2 and
mode 0" or "DPV1 mode" PBOM2 modules are not needed must therefore not be
configured.
Module Identificatio
Identification Contents Module type
no. n bytes
1 PBIM0 Laser/procedure status 2 Word Input (consistent) 0xD1
2 PBIM1 Digital inputs E1-E16 / E17-E24 0xD1
3 PBOM0 Laser/sequence control 2 Word Output (consistent) 0xE1
4 PBOM1 Digital outputs A1-A16 / RFU 0xE1
Process data interface "DPV1 mode" for ProfiBus Tab. 3
Structure of the PDI for In this mode, the PBIM2 and PBOM2 modules are also needed
"DP mode" had must therefore be configured.
This results in the following structure for the process data interface.
Module Identificatio
Identification Contents Module type
no. n bytes
1 PBIM0 Laser/procedure status 0xD1
2 PBIM1 Digital inputs E1-E16 / E17-E24 2 Word Input (consistent) 0xD1
3 PBIM2 Reception buffer for TLV commands n Word Input 0x40, ZZ
4 PBOM0 Laser/sequence control 0xE1
5 PBOM1 Digital outputs A1-A16 / RFU 2 Word Output (consistent) 0xE1
6 PBOM2 Transmit buffer for TLV commands n Word Output 0x40, ZZ
Process data interface for "DP mode 1" Tab. 4
n = 20 / 32 / 64
(depending on the configured module size for PBIM2 or PBOM2)
n ->ZZ = 0x53/0x5F/0x7F
20 0 x 53
32 0 x 5F
64 0 x 7F
(depending on the configured module size for PBIM2 or PBOM2)

1.3 Access to the process data interface
Access to the PDI from the two participants

Master/Controller (external control application) and the
Slave/Device TruMark (control computer) is shown below as
a diagram:
Access diagram for the process data interface Fig. 1890

2. Definitions for PBIM0
This module is used for the status query of the "TruMark series"
and is defined as follows:
Laser status (TruMark Æ field bus)

Bit pos. Function Description
0 -> Laser is off
0.0 Laser
1 -> Laser is on
0 -> The laser is not ready
0.1 Laser ready
1 -> The laser is ready
0 -> SAC is open
0.2 SIK
1 -> SAC is closed
0 -> Shutter closed
0.3 Shutter
1 -> Shutter is open
0 -> Beam expander is not in position
0.4 Beam expander
1 -> Beam expander is in position
0 -> Not responded
0.5 Laser monitoring
1 -> Has responded
0 -> No malfunction
0.6 Laser malfunction
1 -> Malfunction is present
0 -> Pilot laser is off
0.7 Pilot laser status
1 -> Pilot laser is on
0 -> Laser warning lamp is off
0.8 Laser warning lamp
1 -> Laser warning lamp is on
0 -> Trigger is off
0.9 Q switch trigger
1 -> Trigger is on
0 -> Is activated
0.10 Switch off the control yourself
1 -> Is not activated
0 -> Is open
0.11 Key switch, laser disable
1 -> Is closed
0 -> EMERGENCY-STOP is open
0.12 EMERGENCY STOP
1 -> EMERGENCY STOP is closed
0 -> Is off
0.13 Laser heating phase
1 -> Is on
0 -> Is off
0.14 Control unit
1 -> Is on
0 -> Marking is not active
0.15 Mark active
1 -> Marking is active
0 -> Conversion process not active
0.16 Conversion is only available after TruMark
1 -> Conversion process active
0.17 RFU Reserved for future use
: .....: :

Definition for bit 0 to bit 31 from PBIM0 Tab. 5
3-6 Definitions for PBIM0 SB-EN-245_K3.DOCX

This module is used for the status query of the inputs at the digital
interface of the "TruMark series" and is defined as follows:
Digital inputs E1-E24 (TruMark Æ field bus)

1.0 E1
1.1 E2
1.2 E3
1.3 E4
1.4 E5 These inputs are used by TruTops Mark and are therefore
not freely available.
1.5 E6
1.6 E7
1.7 E8
1.8 E9
1.9 E10
1.10 E11 These inputs are freely available.
1.11 E12 0 -> Input, X low level
1.12 E13 1 -> Input, X high level
1.13 E14
1.14 E15
See inputs E1 to E9
1.15 E16
1.16 E17
1.17 E18
1.18 E19 These inputs are freely available.
1.19 E20
1.20 E21 0 -> Input, X low level
1.21 E22 1 -> Input, X high level
1.22 E23
1.23 E24
: ...: :
Definition for bit 0 to bit 31 from PBIM1 Tab. 6
SB-EN-245_K3.DOCX Definitions for PBIM1 3-7

This module is used as reception buffer for TLV commands for TLV
communication with the "TruMark series" and is defined as follows:
Reception buffer for TLV commands (TruMark series Æ field bus)

Byte Arrangement Description
1 Low byte
Handshake counter (16 bit)
2 High byte
3 Lowest byte
: : DAY (32 bit)
6 Highest byte
7 Lowest byte
: : LENGTH (32 bit)
10 Highest byte
11 Data byte 1
: : VALUE (n byte)
n + 10 Data byte n
Definition for bit 1 to bit X from PBIM2 Tab. 7
3-8 Definitions for PBIM2 SB-EN-245_K3.DOCX

This module is used for the control of the "TruMark series" and is
defined as follows:
Laser control (field bus Æ TruMark series)

0 -> Laser off / shutter closed
0.0 Laser / shutter
1 -> Laser on / shutter open
0 -> Shutter closed
0.1 Shutter
1 -> Shutter open
0.2 Laser reset 0 / 1 -> Activate reset
0 -> Pilot laser off
0.3 Pilot laser
1 -> Pilot laser on
: : :
0.7 Start converting (available after TruMark) 0 / 1 -> Start the conversion process
0.8 Start marking 0 / 1 -> Start marking process
Scanner beam check (available after 0 -> Laser beam off (via scanner)
0.9
TruMark) 1 -> Laser beam on (via scanner)
: :
0 / 1 -> Cancels the active
0.15 Cancel marking (available after TruMark)
Marking process
: :
Definition for bit 0 to bit 31 from PBOM0 Tab. 8
SB-EN-245_K3.DOCX Definitions for PBIM0 3-9

6. Definitions for PBOM1
This module is used for the control of the outputs at the digital
interface of the "TruMark series" and is defined as follows:
Digital outputs A1-A16 (field bus Æ digital interface)

1.0 A1
1.1 A2
1.2 A3
1.3 A4 These outputs are used by TruTops Mark and are
1.4 A5 therefore not freely available.
1.5 A6
1.6 A7
1.7 A8
1.8 A9
1.9 A10
1.10 A11 These outputs are freely available.
1.11 A12
1.12 A13
0 -> Output, X low level
1.13 A14 1 -> Output, X high level
1.14 A15
1.15 A16
: : :
Definition for byte 1 to byte 40 / 64 / 128 from PBOM2 Tab. 9
3-10 Definitions for PBOM1 SB-EN-245_K3.DOCX

7. Definitions for PBOM2
This module is used as transmit buffer for TLV commands for TLV
communication via PROFIBUS DP with the "TruMark series" and is
defined as follows:
Transmit buffer for TLV commands (field bus Æ TruMark series)

1 Low byte
Handshake counter (16 bit)
2 High byte
3 Lowest byte
: : DAY (32 bit)
6 Highest byte
7 Lowest byte
: : LENGTH (32 bit)
10 Highest byte
11 Data byte 1
: : VALUE (n byte)
n + 10 Data byte n
Definition for bit 0 to bit 31 from PBOM1 Tab. 10
SB-EN-245_K3.DOCX Definitions for PBOM2 3-11

3-12 Definitions for PBOM2 SB-EN-245_K3.DOCX
Chapter 4
Logs
1. Introduction .................................................................... 4-3
Communication matrix ................................................ 4-3
2. Types of actuation of the TruMark series ................... 4-3

2.1 Actuation via TLV commands .......................................... 4-3
Definition of the employed TLV notation .................... 4-4
2.2 Additional activation via bit information ........................... 4-4
3. Actuation via DP mode.................................................. 4-5

3.1 Realization concept for actuation via TLV
sequences........................................................................ 4-5
Structure of the DP data buffer ................................... 4-7
Handshake mechanism .............................................. 4-8
Error handling ........................................................... 4-11
3.2 Realization concept for the additional activation via
bit information ................................................................ 4-11

1. Introduction
In this document, the structure and sequence of the transfer

logs used in chapter 3 "Process interface" are described in
detail.
Communication matrix
The following field busses are currently used by TruTops

Mark:
Type of field bus Control unit Field device
PROFIBUS Master Slave
PROFINET Controller Device
…
Tab. 1
Depending on need, other types of field busses can be used,

for example, SERCOS.
2. Types of actuation of the TruMark

series
In the current version, the following types of actuation of the

TruMark series are realized via field bus and real-time Ethernet:
Activation by means of TLV commands
Additional activation via bit information
2.1 Actuation via TLV commands
This permits is a complex actuation of the TruMark series, which

includes actions such as:
Loading of marking file.
Setting or changing text variables in a loaded marking file.
The individual actions for this are mapped to TLV sequences

(see section "Definition of employed TLV notation").
There are two different ways the actuation of the TruMark series by
a master via TLV sequences can be realized:
DP (real-time Ethernet and field bus interface).
PROFIBUS DPV1 (only PROFIBUS).

Definition of the employed TLV notation
The general structure and the available TLV commands are

described in detail in the document "TLV commands and
interpreter for TruMark".
For the use of TLV commands with a field bus, the following
limitations for the number of user data sets in the VALUE field of
the TLV command:
Max. n byte for realization via DP (structure of the DP data
buffer).
– n = 30 / 54 / 118 byte (depending on the configured
module size for PBIM2 or PBOM2)
Max. 65504 byte for realization via Profibus DPV1
(64 Kbyte buffer size - 4 byte DAY - 4 byte LENGTH - 2 TLV
commands with 4 byte user data).
2.2 Additional activation via bit

information
This expands the actuation of the TruMark series by TLV

commands to a very simple kind of actuation and includes the
following actions:
Read inputs of the digital interface and set outputs of the digital
interface.
Reading the laser status or simple control of the laser
This actuation is realized by using the DP mode.
4-4 Types of actuation of the TruMark series SB-EN-245_K4.DOCX

3. Actuation via DP mode
The communication is carried out for DP mode via the

process data interface (PDI). To do this, communication is
divided into six different modules (see document: chapter 3).
• For the control of the TruMark series via TLV sequences,
one module, each with n bytes, is reserved in the PDI in
each direction.
– n = 40 / 64 / 128 byte (depending on the configured

module size for PBIM2 or PBOM2)
• For the additional actuation of the TruMark series via bit
information, two modules, each with 4 bytes, are
reserved in the PDI in each direction.
3.1 Realization concept for actuation via

TLV sequences
PBIM2 and PBOM2 are used as the reception and/or transmit

buffers for the TLV sequences. The communication sequence is
controlled by a handshake mechanism.
The length of the TLV commands is limited by the module size of
PBIM2 or PBOM2.
SB-EN-245_K4.DOCX Actuation via DP mode 4-5

You can see the basic system structure in the following illustration:
Concept for the actuation of the TruMark series via Fig. 1955
field bus DP with TLV sequences
*: The field bus includes all the employed master/slave devices.

Field bus stands for all supported field bus types 1 .
A TLV request received from the view of the slave:

– The content of the PBOM2 is cyclically read and compared
with the last content.
– If the content has changed, the handshake mechanism is
performed and the TLV query is forwarded to the higher-
level software module.
A TLV response sent from the view of the slave:

– If a TLV response is to be sent, this is sent from the higher
level software module to the field bus or real-time Ethernet
interface.
– A handshake mechanism is also performed and the TLV
response taken over in the PBIM2.
– The data from PBIM2 is sent until a new TLV response
from the lower-level software module is sent to the
interface.
1
also see the communication matrix
4-6 Actuation via DP mode SB-EN-245_K4.DOCX

Structure of the DP data buffer

1 Low byte Handshake counter (16 bit)
2 High byte
3 Data byte 1 Available buffer for a TLV command Æ
(x-2) byte
: :
x Data byte (x-2)
x = 40 / 64 / 128 byte (depending on the
configured module size for PBIM2 or
PBOM2)
Structure of the DP data buffer Tab. 2
Since 4 byte is required for both the TLV DAY and the TLV
LENGTH, the following condition results for the TLV
commands:
Number of user data sets in the TLV VALUE <= n byte
– TruTops Mark: n = 30 byte / 54 byte / 118 byte
(depending on the configured module size for PBIM2
or PBOM2)

Handshake mechanism
A handshake mechanism is used for the following reasons:

TLV sequences consisting of a TLV query and a TLV response
are used.
Recognition of the same TLV requests which are sent x times
in a row from the master.
The handshake mechanism is realized by a simple counter for
which the following conditions apply 2 :
General
– Valid value range of the handshake counter: from 2 to 255
for correct handshakes.
– If there is an overflow, the handshake counter is reset to
the start value (2).
– If the handshake condition is fulfilled, then a TLV command
is correctly transfered.
For the master
– The master must count the handshake counter up by 1 for
every transmitted TLV request.
– The master may only send a TLV request again when it
has received a TLV response from the slave to the
previous TLV request.
– Condition for a correct TLV sequence:
The received handshake counter must be identical to the
transmitted handshake counter.
For the slave
– Recognition of a new TLV request via a changed
handshake counter.
– Accepts the received handshake counter and sends it back
together with the TLV response to the received TLV
request.
– Condition for a correct TLV request:
The currently received handshake counter must match the
handshake counter which has been counted up by 1 of the
last TLV request (unless there is an overflow).
2
The master/slave differentiation applies to all products (also see the
communication matrix)

Behavior after a reset (e.g. via the digital interface)
– The respective field bus or real-time Ethernet interface is
reset.
– The most recently received handshake counter value is
reset in the PDI (input buffer) at the slave.
– The HS value that was set at the master (output buffer)
– The handshake error warning (5301030A) is output.
– The warning message can be suppressed every time if the
HS value is set to HS_INIT, that is "0", before or at the time
of the "Reset" at the master.
Status Valu Description

e
HS_INT 0 Value of the handshake counter which is sent to the
interface after a reset of the TruMark series. (For this,
the entire content of PBIM0, PBIM1 and PBIM2 is set
to 0x00).
HS_ERROR 1 Response of the TruMark interface to handshake error
HS_START 2 Start value of the handshake counter which has to be
sent from the master for the following conditions:
• Start of the TLV communication after the start of
the interface at the control computer (slave)
• After an overflow of the handshake counter
• Restart of TLV communication after a reset of the
interface
• Restart of TLV communication when the control
computer (slave) interface has sent an
HS_ERROR to the master after a detected
handshake error
HS_STOP 255 End value of the handshake counter
Description of the statuses of the handshake counter Tab. 3

The handshake mechanism is shown here as a diagram:
Handshake mechanism for a TLV sequence via DP Fig. 1954

mode
(1) The master sends a TLV request.

(2) The master counts the handshake counter up by 1.
(3) The TruMark series (slave) interface checks the
handshake.
(4) The TruMark series interface extracts the TLV request
and sends it to the TruMark control software.
(5) The TruMark control software creates a TLV response
and sends it to the TruMark series interface.
(6) The TruMark series interface accepts the handshake
counter of the TLV request and sends it together with
the TLV response to the master.
(7) The master checks the handshake counter for identical
values.
(8) The master recognizes whether the TLV sequence has
been correctly transferred and is ready for the next TLV
request.

Error handling
Type of error Description Communication User interface

Handshake error Æ HS_INT received after Æ Abortion of the Issuing of a warning for
correct handshake conditions communication process the first occurrence
Æ HS_ERR received Æ Sending of HS_ERR until
Æ Handshake conditions a correct handshake is
violated received
Error handling Tab. 4
3.2 Realization concept for the additional

activation via bit information
For this purpose, the PBIM0, PBIM1, PBOM0 and PBOM1

modules of the process data interface are used which always
have to be configured in the master.
In compliance with the bit assignments defined in the
process data interface, a very simple actuation of the
TruMark series can also be realized for the named modules.

Chapter 5
Installation of the cifX card

1. General............................................................................ 5-3
2. Software installation for the Hilscher cifX card .......... 5-4
2.1 Installation of the cifX device driver ................................. 5-4
3. Hardware installation of the cifX card ......................... 5-7

3.1 General ............................................................................ 5-7
Delivery condition of the cifX card .............................. 5-7
Setting the rotary switch ............................................. 5-7
3.2 TruMark Series ................................................................ 5-9
Installation position of the cifX card ............................ 5-9
interface .................................................................... 5-10
4. Configuration of the cifX card .................................... 5-11

4.1 ProfiBus ......................................................................... 5-11
4.2 ProfiNet .......................................................................... 5-15
5. Expanding TruTops Mark settings ............................. 5-19

5.1 Configuring the ProfiBus ................................................ 5-26
SB-EN-245_K5.DOCX General 5-1

5.2 Configuring ProfiNet ...................................................... 5-28
5-2 General SB-EN-245_K5.DOCX

1. General
This chapter describes the software and hardware

installation of the Hilscher cifX card in the "TruMark Series"
control computer.
Note
The Hilscher cifX card from TRUMPF is installed in the
integrated control computer of the TruMark Series 1000
because the control computer is not accessible. The
following description therefore only applies to the following
series.
The cards can be replaced in the following "TruMark Series"

control computers:
• TruMark 3000 series
To do this, the following components are needed:

Driver: Setup file "cifX Device Driver Setup" in the
directory c:\Trumark\Doku\cifX
cifX card ProfiBus
– Name: CIFX 50E-DP
– Hilscher item number: 1251.410
– With 9-pole SubD connection
cifX card ProfiNet
– Name: CIFX 50-RE
– Hilscher item number: 1250.100
– With real-time Ethernet connection
Firmware
– ProfiBus: cifxdps.nxf
– ProfiNet: cifxpns.nxf
– Directory c:\Trumark\Doku\cifX\Firmware
Control program TruTops Mark from Version 2.8
Operating system Windows XP or Windows 7
Note
The hardware in use currently does not use any other cards.
SB-EN-245_K5.DOCX General 5-3

2. Software installation for the Hilscher
cifX card
2.1 Installation of the cifX device driver
The driver for the current supported cards must be installed

via the Hilscher internal driver software. To do this, only the
driver setup file must be installed:
• Installation file: C:\TruMark\Doku\cifX\ cifX Device

Driver Setup.exe
Fig.1970
Perform the cifX Device Driver Setup.exe.
5-4 Software installation for the Hilscher cifX card SB-EN-245_K5.DOCX

The following message will be shown.
Fig. 1971
Agree to the conditions for the licence
agreement and click on the "Install" button.
Keep clicking on the "Continue installation" button until the

following message is shown.
Fig. 1972
Click on the "Finish" button. The setup assistant is ended.

Now restart the PC so that that the data will be applied.
SB-EN-245_K5.DOCX Software installation for the Hilscher cifX card 5-5

- Installation sequence: C:\TruMark\Doku\cifX\Hilscher\
PC cards cifX installation of the software UM 34
DE.pdf chapter 2.5
Fig. 1973
You can access Hilscher documentation in German and

English via your PC if you want to read any background
information. Different procedures by TRUMPF are also
presented.
Note
If you make settings that deviate from the TRUMPF
specifications, you will receive no support for any inquiries.
5-6 Software installation for the Hilscher cifX card SB-EN-245_K5.DOCX

3. Hardware installation of the cifX card
First switch off the operating voltage of your "TruMark

Series" control computer and all connected laser marking
systems.
3.1 General
Electrostatically sensitive components!

ATTENTION Damage to the "TruMark Series" control computer and the cifX
card
¾ Discharge yourself on the metal housing of the "TruMark
Series" control computer.
¾ Wear an ESD wrist strap during he installation.
Delivery condition of the cifX card
Detail zu 2
3 2 1
1 cifX card in installed state

2 Rotary switch of the cifX card
3 Detail of the delivery condition, rotary switch at "0"
Fig. 1976
Setting the rotary switch
Before the installation of the cifX card, you have to set the rotary
switch as follows:
• To 5 for ProfiNet (corresponds to slot 5, channel 0)
• To 6 for ProfiBus (corresponds to slot 6, channel 0)
SB-EN-245_K5.DOCX Hardware installation of the cifX card 5-7

Note
The slot or the switch position is set using the rotary switch.
The Hilscher card further divides the switch positions (0-9)
by software into different channels (CH#0 to #CH5).
TRUMPF always uses CH#0.
If you want to install two cifX cards, make sure the rotary
switch is not set to "0" and, depending on which field bus you
are using (for example, Profibus, Profinet, ...), that the rotary
switch is set accordingly.
Rotary switch set to "5" for ProfiNet
2 1
1 Rotary switch 2 Rotary switch set to slot 5
Fig. 1977
5-8 Hardware installation of the cifX card SB-EN-245_K5.DOCX

3.2 TruMark Series
Installation position of the cifX card
Supply unit for the TruMark

3000/5000 series
1 2
1 Control computer in the supply unit for the TruMark 3000/5000 series
2 Installation position of the cifX card
Fig. 1974
Supply unit of the TruMark

6000 series
1 2
1 Control computer in the supply unit for the TruMark 6000 series
2 Installation position of the cifX card
Fig. 1975
SB-EN-245_K5.DOCX Hardware installation of the cifX card 5-9

interface
Prerequisite
Covers at the supply unit have been removed so that there is
access for the installation of the cifX card.
Remove the diaphragm at the "TruMark Series" control

computer from the place where you want to insert the cifX
card. To do this, unscrew the diaphragm's mounting screw,
remove the screw with the diaphragm and insert the cifX
card in the free PCI slot. Fasten the cifX card to the
designated bore hole.
1 Cover of the supply unit

2 Frame of the supply unit
3 Diaphragm
4 cifX card connected with the PCI slot and attached at the designated
bore hole
Sample installation for the 3000/5000 series Fig. 1978
Close the housing of the "TruMark Series" control computer

again at the supply unit and switch the system on.
5-10 Hardware installation of the cifX card SB-EN-245_K5.DOCX

4. Configuration of the cifX card
4.1 ProfiBus
Setting the slot and firmware

When using the cifX cards from Hilscher, the following
installations must be carried out. These are independent of
the transfer log. Protocol-specific installation steps are
indicated under the corresponding paragraph.

Prerequisites
1. cifX card 50E-DP for ProfiBus is used
2. PCI system interface is connected with the cifX card
3. Installation of the device driver is concluded

Windows XP operating 1. The following message is shown via "Windows – Start
system Button – Control Panel".
1 run cifX Setup
Fig. 1979
Also see the Hilscher document "cifX
Device Driver setting and configuring".
SB-EN-245_K5.DOCX Configuration of the cifX card 5-11

The following window is shown.
1 Select the "SlotNr" tab

2 Slot 6 corresponds to rotary switch setting 6 at the cifX card
3 Add the respective firmware
Fig. 1985
4 Mark Profibus firmware

5 Click in the "Open" button
Fig. 1986
5-12 Configuration of the cifX card SB-EN-245_K5.DOCX

6.
6 Display of all downloaded modules or firmware files

7 Click on the "Apply" button
Fig. 1987
Fig. 1983
2. Confirm the message with "Yes" (Ja).
By confirming with "Yes," the data will be applied and saved.
For the slave, note that NO configuration files in "cifX Setup"

have been loaded at the corresponding slot (same number
as the rotary switch) and communication channel CH#0:
Fig. 1984
This area must remain empty because it is
intended for the customer (master).

3. For the master, the corresponding configuration must be
downloaded to the card with the Sycon.Net tool. If this has
been done successfully, then the appropriate configuration
files have to appear at "Assigned Configuration Files" in "cifX
Setup".

4.2 ProfiNet
Setting the slot and firmware
When using the cifX cards from Hilscher, the following

installations must be carried out. These are independent of
the transfer log. Protocol-specific installation steps are
indicated under the corresponding paragraph.

Prerequisites
1. The cifX-Karte 50-RE for ProfiNet is used
2. PCI system interface is connected with the cifX card
3. Installation of the device driver is concluded

Windows XP operating 1. The following message is shown via "Windows – Start
system Button – Control Panel".
1 run cifX Setup
Fig. 1979

Also see the Hilscher document "cifX Device Driver setting
and configuring".

3
2
1 Select the "Slot" tab

2 Slot 5 corresponds to rotary switch setting 5 at the cifX card
3 Add the respective firmware
Fig. 1980
4 Mark Profinet firmware

5 Click in the "Open" button
Fig. 1981

6.
6 Display of all downloaded modules or firmware files

7 Click on the "Apply" button
Fig. 1982
The following message will be shown.
Fig. 1983
2. Confirm the message with "Yes".
By confirming with "Yes," the data will be applied and saved.
For the device, note that NO configuration files in "cifX

Setup" have been loaded at the corresponding slot (same
number as the rotary switch) and communication channel
CH#0:
Fig. 1984
This area must remain empty
because it is intended for the customer (controller).

3. For the controller, the corresponding configuration
must be downloaded to the card with the Sycon.Net
tool. If this has been done successfully, then the
appropriate configuration files have to appear at
"Assigned Configuration Files" in "cifX Setup".

5. Expanding TruTops Mark settings
You can add communication to TruTops Mark with ProfiBus

or ProfiNet.
TruTops Mark "Options" for 1. Activate the Profibus using the activation code in
Profibus "Options" at TruTops Mark.
Fig. 2000

SB-EN-245_K5.DOCX Expanding TruTops Mark settings 5-19

2. Select the "6 Profibus" module in the "3 Module" menu in
TruTops Mark.
Fig. 1994

5-20 Expanding TruTops Mark settings SB-EN-245_K5.DOCX

The following window opens.
1 Click on F4 configuration
Fig. 1996

If you have established the Profibus communication (see
next page), proceed to "F7 interface configuration". To do
this, you have to continue to section 5.1 "Configure profibus".
The individual parameters to be set are described in chapter

2 at section "3 Configuration".

1 Activate Profibus communication by putting the check mark

at "CifX installed".
Fig. 1995

or

TruTops Mark "Options" for 1. Activate the Real-Time-Ethernet using the activation
Profinet code in "Options" at TruTops Mark.
Fig. 1988


2. Select the "7 Real time Interface" module in TruTops
Mark in the "3 Module" menu.
Fig. 1989


Fig. 1990

Now select "F7 Configure interface" and proceed to section
5.2 "Configure ProfiNet".

5.1 Configuring the ProfiBus
The individual parameters to be set are described in chapter

2 at section "3 Configuration".
1. Open the configuration via "F7 Configure interface".
Fig. 1997
Fig. 1998

Connect cable, green status
When leaving the menu with "OK", the Profibus interface will
be configured.
If the master and slave are correctly configured, the status

LED will light up in light green after a few seconds.
Fig. 1999
Note
The status remains gray until the card is connected with the
SubD- 9-poled cable. After that, the status LED switches to
green.

5.2 Configuring ProfiNet
1. Open the configuration via "F7 Configure interface".
Fig. 1949
The name must be specified that was defined in the

controller for "Device model". The default from TRUMPF is
"cifx".

Fig. 1948
Connect cable, green status
When leaving the menu with "OK", the ProfiNet

interface will be configured.
If the controller and device are correctly configured, the

status LED will light up in light green after a few seconds.
Fig. 1993
Note
The status remains gray until the card is connected with the
Ethernet cable. After that, the status LED switches to green.


SB ProfiBus ProfiNet TM1356 en

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SB ProfiBus ProfiNet TM1356 en

Caricato da

Copyright:

Formati disponibili

Interface description

Material number 1892890

Address for orders

© TRUMPF Laser Marking Systems AG

Chapter 1 Overview of the connection

1. Connection type ............................................................. 1-3

Chapter 2 User interface

1. Scope of functions of the interface ............................. 2-3

2. User interface ................................................................. 2-4

3. Configurations ............................................................. 2-12

SB-EN-245 2013-11-28 Table of contents 5

4. Diagnosis ...................................................................... 2-19

Chapter 3 The process interface

2. Definitions for PBIM0 .................................................... 3-6

3. Definitions for PBIM1 .................................................... 3-7

4. Definitions for PBIM2 .................................................... 3-8

5. Definitions for PBIM0 .................................................... 3-9

6. Definitions for PBOM1................................................. 3-10

7. Definitions for PBOM2................................................. 3-11

1. Introduction .................................................................... 4-3

2. Types of actuation of the TruMark series ................... 4-3

Table of contents 2013-11-28 SB-EN-245

Chapter 5 Installation of the cifX card

3. Hardware installation of the cifX card ......................... 5-7

4. Configuration of the cifX card .................................... 5-11

5. Expanding TruTops Mark settings ............................. 5-19

SB-EN-245 2013-11-28 Table of contents 7

Overview of the connection

SB-EN-245_K1.DOCX Connection type 1-1

You will receive information about the following subject areas:

1.1 Goal of the connection

1.2 Technologies and PCI card

SB-EN-245_K1.DOCX Connection type 1-3

The software for the interface of the connection is available in

The following accessories are available for the connection:

Only for the ProfiBus DP:

1-4 Connection type SB-EN-245_K1.DOCX

There is a simple activation and also a complex activation.

1.6 Process data interface

SB-EN-245_K1.DOCX Connection type 1-5

1.7 Structure of a TLV command

TLV stands for TAG (day) / LENGTH / VALUE

 TAG and VALUE are given as decimal numbers

1-6 Connection type SB-EN-245_K1.DOCX

The TLV communication is structured as a sequence of TLV

 Example of the TLV commands: N text variables

SB-EN-245_K1.DOCX Connection type 1-7

2. User interface ................................................................. 2-4

3. Configurations ............................................................. 2-12

SB-EN-245_K2.DOCX Scope of functions of the interface 2-1

2-2 Scope of functions of the interface SB-EN-245_K2

Using an interface, it is possible to control the

The basic functions of the user interface for the Profibus

Different communication types are used for the

SB-EN-245_K2.DOCX Scope of functions of the interface 2-3

After the user interface has been successfully started with

Application window Fig. 1936

The user interface of the interface basically consists of three

2-4 User interface SB-EN-245_K2.DOCX

Application window Fig.1937

By clicking on the command sequence 1 File > 1 Close, the

Application window Fig. 1938

Different settings for each interface and the respective slave

TAG and VALUE are given as decimal numbers

Example of the TLV commands: N text variables

Data area for complex control of the "TruMark series" via

Module sizes: 20 / 32 / 64 Word (depending on the configured