7 - Operating Instruction - Digital Interface DI B000, Profibus Interface - BEA - 250859-En-01

Description I
Digital interface DI B000 en

Profibus interface
Interface protocol specification for software

ZC4085-8012F_ZC
1 General 4
1.1 Interface structure 4
1.2 Objects 5
1.2.1 Overview of receive objects 6
1.2.2 Overview of transmit objects 7
2 Parameters and commissioning 8
2.1 General configuration block 8
2.1.1 Parameter ‘OwnNodeNr‘ 8
2.1.2 Parameter 'data format' 8
2.1.3 ‘Baud rate‘ parameter 9
2.1.4 Parameter error EL_Net intf. 9
2.2 Configuration block for receive data 9
2.2.1 'rec. obj.0xFF key' parameter 9
2.2.2 'rec. object xx' parameter 10
2.3 Configuration block for transmit data 11
2.3.1 'form.contr.obj.no.' parameter 11
2.3.2 'tr. object xx' parameter 11
2.4 Examples of configuration - DI B000 and SPS 13
2.4.1 Configuration of the receipt and send objects 13
2.4.2 Example 15
2.4.3 Defect diagnosis if there are problems
with the connection. 16
2.5 Display block for receive data 18
2.5.1 'rec. displ.obj.no.' parameter 19
2.5.2 'rec. byte xx' parameter 19
2.6 Display block for transmit data 19
2.6.1 'tr. displ.obj.no.' parameter 20
2.6.2 'tr. byte xx' parameter 20
2.7 Parameter block for 'mount positions' 20
2.8 Parameter blocks with commissioning supports 23
BEA--250859-EN-01
Digital Interface DI B000
2.8.1 'rec.obj.no. error' parameter 24

2.8.2 'tr.obj.no. error' parameter 24
2.8.3 'state re.tr obj.no' and 'state CAN command' parameter 24
2.8.4 'db_level' parameter 25
2.9 Parameter block with general information 25
2.9.1 'rec. data len word' parameter 26
2.9.2 'tr. data len word' parameter 26
2.9.3 '... cycletime' parameter 26
3 Receive objects 27
3.1 Object code 01 hex 1 byte empty object 27
3.3 Object code 03 hex Setting digital outputs 28
3.4 Object code 06 hex 6 byte or 3 byte empty object 29
3.5 Length 6 bytes Data format fixed number 30
3.6 Object code 0C hex Control word for web guider
and support beams 30
3.7 Object code 16 hex left support beam position 32
3.8 Object code 17 hex right support beam position 33
3.9 Object code 18 hex position actuator 34
3.10 Object code 19 hex set web offset 36
3.11 Objektcode 20 hex set guide position
(New DATA RECORD only) 37
3.12 Object code 21 hex set oscillation 39
3.13 Object code 1C hex set width control 42
3.14 Objektcode A0 hex Controls the web tension controller DC 6...
44
3.15 Object code F0 hex Transparent object for Data master
module 47
3.16 Object code FF hex read/write parameters 48
3.16.1 Function sequence 49
3.16.2 Protected parameters 50
4 Transmit objects 52
4.3 Object code 03 hex read digital inputs 53
4.4 Object code 06 hex 6 byte or 3 byte empty object 54
4.5 Object code 07 hex Read object virtual digital outputs LK4203
55
4.7 Object code 0C hex Status word of the web guider
and support beams 55
2
4.8 Object code 14 hex Left sensor signal (x.2) Object code 15 hex
Right sensor signal (x.1) Object code 24 hex Left sensor signal
(x.4) Object code 25 hex Right sensor signal (x.3) 57
4.9 Object code 16 hex Left support beam position (x.7) Object
code 17 hex Right support beam position (x.6) Objektcode 26
hex Left support beam position (x.9) Objektcode 27 hex Right
support beam position (x.8) 59
4.10 Object code 18 hex Actuator position 61
4.11 Object code 19 hex read web offset 62
4.12 Object code 20 hex Read guiding position (NEW DATA
PROTOCOL ONLY) 63
4.13 Object code 21 hex read oscillion data 64
4.14 Object code 1A hex Left web edge position (x.2 & x.7) Object
code 1B hex Right web edge position (x.1 & x.6) Object code
2A hex Left web edge position (x.4 & x.9) Object code 2B hex
Right web edge position (x.3 & x.8) 65
4.15 Object code 1C hex Read web width/width monitoring Object
code 2C hex Read web width 67
4.16 Object code A0 hex Status of web tension controller DC 6... 69
4.17 Object code EE hex 1-2-web width measuring 72
4.18 Object code F0 hex transparent object for data master module
74
4.19 Object code FF hex read/write parameters 75
5 Viewing the objekt data 77
5.1 Trace object 79
6 Displays 81
6.1 CAN address 81
6.2 LED’s 81
6.2.1 Supply voltage 81
6.2.2 Data exchange 82
6.2.3 Module state LEDs 82
7 Connectors 83
7.1 Profibus 83
3
1 General
This interface series with the ‘object-oriented protocol’ is the link between the customer
network and the CAN network from Erhardt+Leimer with the standard (earlier) CAN
protocol. Interfaces to the customer networks are available for the following protocols:
Profibus DP, ControlNet, DeviceNet, CanOpen, EtherNet/IP and EGD.
The protocol implemented in the interface combines the simplicity of a process image
with high flexibility with regard to data type and quantity. The data record to be trans-
mitted and received comprises smaller individual data records (objects). Which objects
the data record consists of depends on the customer application and is defined in the
interface via the parameter list.
The object definition is designed so that the interface may be extended by new types of
object. A software update is required for this purpose.
When transmit and receive objects are mentioned in the following documentation it is
from the point of view of the interface itself and not of the scanner.
In the case of object numbers it must be distinguished whether the object number is for
a transmit or a receive object. An object number for a transmit object does not always
have the same significance as the same number for the receive object.
1.1 Interface structure

The interface is divided into logical parts. The structure is indicated in the following fig.
(extract from CANMON program using as example a Profibus interface):
Modules in rounded brackets are physically featured and modules in square brackets
represent logical modules. The ZC4085 module (here with the CAN address 0.B) is the
CPU itself. Depending on the type of interface the CPU module can also report with
ZC4080, PC0016, etc. To this module are linked the logical modules 'config module',
object module'‚ ObjPar-module’ and 'mount position'. If the field bus module is an inde-
pendent module yet another module may report. Example: with the ControlNet-
Interface module 'COM-CNS' is also on display.
Field bus specific parameters are assigned to the 'Config-Module', the data records re-
quired can be compiled (configured) and displayed in 'Object-Module', for some objects
in ‘Object-Module’ additional parameters may be specified in “ObjPar-Module”, offset
values are entered in module 'Mount Position'.
4
Note: For the parameterization of the logical modules the CANMON program (PC)
or DO 2000 is required.
For displaying the logical modules a version from 'PC001-0004MxZG' on-
wards is required for the CANMON program and on the DO 2000 a version
from 'ZC4070-0002F_ZJ' onwards.
1.2 Objects
On the E+L side the interface is object-controlled and is configured for its application
(data quantity) in that the required object codes are written into the relevant parameter
block in the 'object module'. There is one parameter block for the data to be transmit-
ted and one parameter block for the data to be received. The object lists for transmit-
ting and receiving are respectively completed with a parameter that contains the value
zero. Each object performs a job or supplies a value and the corresponding status.
Most objects are programmed so that each may be used on its own and signals in dif-
ferent objects are not dependent on one another. An exception is e.g. the writing and
reading of parameter values. Here the receive and transmit objects operate together.
The individual objects feature different data lengths that may be 1, 2, 6 or 8 bytes long.
Objects with control bits lead to problems if they are created twice in an object list for
the same CAN group. If, after starting, the interface detects a double or unknown ob-
ject it is internally „replaced by an empty object“ and the entry number of the object in
question is displayed in a parameter.
The creation of objects is the responsibility of the start-up engineer.
For many receive objects (commands from the host or scanner) an accept bit is used
that triggers the command (accept value or function). Acceptance is performed when
the accept bit (bit 14 in the control word; 6-byte object) is set from “0” to “1” (positive
edge).
To assure that these edges are reliably detected the minimum times for the accept bit
should be observed:
• control bit to HIGH (1-signal) 4 x mainloopmaxtime (control parameter)
• control bit to LOW (0-signal) 4 x mainloopmaxtime (control parameter)
5
1.2.1 Overview of receive objects
Object no. Obj. length Object function

[hex] [bytes]
0 0 This object number is used as end identifier for the object list.
1 1 Empty object
2 2 Empty object
3 2 Object for setting digital outputs (LK usage 4)
6 6 Empty object
8 8 Empty object
C 2 Object for controlling a web guider and the support beams.
16 6 Object for positioning the left support beam (Device x.7).
17 6 Object for positioning the right support beam (Device x.6).
18 6 Object for positioning the actuator (Device x.5).
19 6 Object for setting the web offset (Device x.5).
20 6 Object for setting the guiding position (Device x.5).
21 6 Object for setting the oscillating functions (Device x.5)
1C 6 Object for setting width monitoring
60 8 Reserved for VB3 data master modules (transparent object)
..
69
A0 8 Object for controlling the web tension controller DC 6...
F0 8 Object for data master modules (transparent object)
F1
.. 8 Reserved for object for data master modules (transparent objects)
FE
FF 8 Reading and writing of parameters. This object is not autonomous
but operates together with the transmit object 'FF'.
6
1.2.2 Overview of transmit objects
Object no. Object Function

[hex] length
[Bytes]
0 0 This object number is used as end identifier for the object list.
1 1 Empty object
2 2 Empty object
3 2 Object for reading digital inputs (LK usage 4)
6 6 Empty object
7 2 Object read virtual digital outputs LK4203
8 8 Empty object
C 2 Object supplies status of a web guider and the support beams.
12 6 Object supplies signal of line sensor FE5002 (Device x.3)
14 6 Object supplies left sensor signal (Device x.2).
15 6 Object supplies right sensor signal (Device x.1).
16 6 Object supplies left support beam position (Device x.7).
17 6 Object supplies right support beam position (Device x.6).
18 6 Object supplies actuator position (Device x.5).
19 6 Object supplies web guider web offset (Device x.5).
20 6 Object supplies controller guiding position (Device x.5).
21 6 Object supplies status of oscillating functions (Device x.5)
1A 6 Object supplies left web edge position (Device x.2 and x.7).
1B 6 Object supplies right web edge position (Device x.1 and x.6).
1C 6 Object supplies web width (Device x.1 and x.2).
or width monitoring status
24 6 Object supplies left sensor signal (Device x.4)
25 6 Object supplies right sensor signal (Device x.3)
26 6 Object supplies position of l.h. support (Device x.9).
27 6 Object supplies position of r.h. support (Device x.8).
2A 6 Object supplies position of l.h. web edge (Device x.4 und x.9).
2B 6 Object supplies position of r.h. web edge (Device x.3 und x.8).
2C 6 Object supplies the alternative web width (Device x.3 und x.4).
60 8 Objects for VB3 data master modules (transparent object)
..
69
A0 8 Object for web tension controller DC 6...
EE 12 Object supplies 1-2-web width measuring
F0 8 Object for data master modules (transparent object)
F1
.. 8 Reserved for object for data master modules (transparent objects)
FE
FF 8 Reading and writing of parameters. This object is not autonomous
7
2 Parameters and commissioning

The interface contains parameters for configuring the interface and displaying data.
The parameters are divided into several function blocks, the function of which is ex-
plained in the following:
2.1 General configuration block

This parameter block is located in the logical 'config module':
No. Name Value Default Min. Max. Unit Description
5 OwNodeNr 6 6 0 125 Profibus-address

6 data format 1 1 0 1 0 Data transmission for-
mat
0 = Motorola-Format
1 = Intel-Format
7 Baudrate -- -- -- -- -- Baud rate Profibus
(display section only)
0= 12 MBaud
1= 6 Mbaud
2= 3 MBaud
3= 1,5 MBaud
4= 500 kBaud
5 = 187,5 kBaud
6 = 93,75 kBaud
7 = (45,45 kBaud)
8= 19,2 kBaud
9= 9,6 kBaud
8 gen. service field General field for com-
missioning
9 error EL_Net intf. -- -- -- -- -- Error code for initiali-
zation of Profibus
board
(display section only)
0 = o.k.
1 = Parameter field
2 = Configurations error
4 = No Master
2.1.1 Parameter ‘OwnNodeNr‘

In this parameter the equipment address for the Profibus is set. If at some time the ad-
dress is changed, the module must be restarted for internal acceptance.
2.1.2 Parameter 'data format'

This parameter is used to configure how the data is transferred in case a value ex-
ceeds 1 Byte.
With Profibus the data is transmitted in the 'Motorola-Format' (big endian). The bus
transfers the 'high Byte' before it transfers the ‘low Byte’. With other types of fieldbuses
(for example with ControlNet or DeviceNet) the data is transferred in the 'Intel-Format'.
In this cse the 'low Byte' is transferred before the 'high Byte'.
This value should be left at its ‘default value’. Should it be necessary to change this
value, the interface does not require a restart.
8
2.1.3 ‘Baud rate‘ parameter

With Profibus interface DIB000 the Baud rate adjusts automatically to the Baud rate of
the Masters. The parameter is only used as a display, i.e. the baud rate set in the mas-
ter (PLC) may be read off in this parameter. The exact assignment of value to baud
rate may be found in the parameter list. The baud rate for DeviceNet and CanOpen
must be set to the same rate as set in the master.
2.1.4 Parameter error EL_Net intf.

In this parameter error codes may be read out for commissioning. The communication
status of the interfaces may be read off here.
For the Profibus make sure before hand that the addresses in the slave (DI B000) and
in the Master are configured the same. Otherwise errors cananot be displayed. If the
master (PLC) has detected the module then this parameter indicates the communica-
tion status.
Value 0 means that communication is taking place.
Value 1 means no communication due to parameter setting errors.
Value 2 means no communication due to configuration errors. The input and/or output
data do not match with that of the master.
Value 4 is the initial status. It changes as soon as the module is operated by a master.
2.2 Configuration block for receive data

This parameter block is assigned to the logical 'object module':
5 receive obj. list Settings for rec. data

(as seen from interface)
6 rec. obj.0xFF key -1 -1 -1 1 hex Protective parameter
(key) for parameter writ-
ing
7 rec. object 1 0000 0000 0000 FFFF hex Entry for
1st receive object
2nd receive object
.... ... ... ... ... ... ... ...
32nd receive object
2.2.1 'rec. obj.0xFF key' parameter

This parameter controls the writing of parameters by the 'FF' object. It may be re-
garded as an enable or protective parameter.
The values have the following meaning:
• '-1' means that writing on parameters is not allowed.
• '0' means that writing on unprotected parameters is allowed.
• '1' means that writing on a protected parameter is allowed (at one’s own risk).
9
2.2.2 'rec. object xx' parameter

In the list the structure and meaning of the data record transmitted by the host or scan-
ner to the interface is determined. In these parameters a maximum of 32 objects may
be grouped. The content of a parameter represents a selected object. The objects are
combined in the sequence of the entries to form a data record. The list is ended by a
zero word. The length of the configured data record is displayed in the ' rec. data len
word' parameter.
The objects are designated as receive objects as seen by the interface.
The structure of the object codes for the parameter is as follows:

HIGH byte LOW byte
1 Bit 3 Bit 1 Bit 3 Bit 8 Bit
(15) (14, 13, 12) (11) (10, 9, 8) (7, 6, 5, 4, 3, 2, 1, 0)
reserved CAN group reserved reserved Object type for transmission
• the bits (reserved) are not used at present. These bits should always be set with
the value '0'.
• Wit the 3 bits (GRP) the CAN group applicable for the object is set.
• The 8 bits (object type) determines the function of the object. The individual ob-
jects themselves will be described in the document later on.
Example: in CAN group 5, position left support beam

CAN group = 5, receive object 'position left support beam' = 16 hex;
Value to be entered for parameter: 5016 (hex)
Attention: Objects of the same type may be addressed a max. of 1 time per CAN
group (for 8 groups 8 times).
This restriction does not apply to empty objects '01', ‘06’ and '08'.
If a defective object is detected in the object list the number (pointer) of the object entry
(1..32) is stored in the 'rec.obj.no.error' parameter (P 136). The object itself is treated
like an empty object for 2 bytes (Code 02 hex).
If the object list is changed, the change is only accepted when the interface is started
anew (reset).
10
2.3 Configuration block for transmit data

This parameter block is assigned to the logical 'object module':
39 . transmit obj. list Settings for

transmit objects
40 form.contr.obj.no. 00 00 -1 64 Transmit object entry
number is sent by for-
mat control
-1 = all objects
0 = no object
n = number (list) of object
sent by format control
41 tr. object 1 0000 0000 0000 FFFF hex Entry for
1st transmit object
2nd transmit object
.... ... ... ... ... ... ... ...
64th transmit object
2.3.1 'form.contr.obj.no.' parameter

If this parameter is set unequal to '0', one or all 'format control' transmit objects are set.
With the format control not the data of the object itself are sent but bytes with ascend-
ing values. The first byte (left byte in the doc) is sent as '01' or '81', the second byte as
'02', the third byte as '03', etc. This is so that in the scanner (host) it may be detected in
which sequence (high or low byte) the date is read in relation to the documentation.
The exact byte values for the format control are listed in the description of the individ-
ual transmit objects.
The parameter values have the following meaning:
• '-1' means: all transmit objects are switched to format control.
• '0' means: all transmit objects are switched to normal mode
• '1' .. '64' means: the specified object (pointer) are switched to format control.
This parameter is reset to 0 on each interface restart.
2.3.2 'tr. object xx' parameter

In the list the structure and meaning of the data record transmitted by the interface to
the host or scanner is determined. In these parameters a maximum of 64 objects may
be grouped. The content of a parameter represents a selected object. The objects are
combined in the sequence of the entries to form a data record. The list is ended by a
zero word. The length of the configured data record is displayed in the 'tr. data len
word' parameter.
The objects are designated as transmit objects as seen by the interface.
11
The structure of the object code for the parameters is as follows:

HIGH byte LOW byte
1 bit 3 bits 1 bit 3 bit 8 bits
(15) (14, 13, 12) (11) (10, 9, 8) (7, 6, 5, 4, 3, 2, 1, 0)
reserved CAN group Mean time Object type for transmission
value
• The bits (reserved) are not in use at present. These bits should always be set with
the value '0’.
• With the 3 bits (GRP) the CAN group valid for the object is set.
• With the bit mean value the mean value calculation can be activated. The mean
value calculation is linear within a time cycle which is set in the following 3 bits.
This bit is not supported by all send objects. If no support is given this is men-
tioned in the object description.
• The three bits (time) set the time cycle for how often the output value is refreshed.
These bits are only supported by some transmit objects. If this is the case, refer-
ence will be made accordingly in the object description.
(Bin) 000 = refreshing in each MAINLOOP
(Bin) 001 = refreshing approx. every 10 ms (milliseconds)
• The 8 bits (object type) determine the object function. The individual objects
themselves will be described at a later stage in this doc.
Example: read the web width from CAN group 0

CAN group = 0, transmit object 'web width' = 1C hex;
Value to be entered for parameter: 001C (hex)
Attention: the objects ‘03’ and 'FF' may be addressed a maximum of 1 time per
CAN group (for 8 groups 8 times).
Other objects may be set several times.
If a defective object is detected in the object list, the number (pointer) of the object en-
try (1..64) is stored in the 'tr. obj.no. error' parameter (P 137). The object itself is
treated as an empty object for 2 bytes (Code 02 hex).
If the object list is changed, the change will only be accepted once the interface is re-
started (reset).
12
2.4 Examples of configuration - DI B000 and SPS
2.4.1 Configuration of the receipt and send objects

In the Profibus interface configuration each data length and format is assigned a spe-
cial identification number. A receive object with 2 bytes for instance has the output
identifier number 161 dez. A 2 BYTE transmit object has the identifier number 145 dez.
For the Profibus master it is important that the receive objects are configured first and
only then the transmit objects (from the point of view of the interface). They may only
be configured with output identifiers in the PLC. Output data in the PLC are the receive
objects in the interface!
The transmit objects (from the point of view of the interface) may only be configured
with input identifiers in the PLC. Input data in the PLC are sent by the interface (trans-
mit objects).
Survey of the output identifiers with respect to the Profibus receive objects:
Object no. Object Object function Identifier

[hex] length number
[Bytes]
0 0 This object number is used as end identifier for the object list. ---
1 1 BYTE Empty object 160dez
2 2 BYTES Empty object 161dez
3 2 BYTES Object for setting digital outputs (LK usage 4) 161dez
6 3 WORDS Empty object 226dez
C 2 BYTES Object for controlling a web guider and support beams. 161dez
16 3 WORDS Object for positioning the left support beam (Device x.7). 226dez
17 3 WORDS Object for positioning the right support beam (Device x.6). 226dez
18 3 WORDS Object for positioning the actuator (Device x.5). 226dez
19 3 WORDS Object for setting the web offset (Device x.5). 226dez
20 3 WORDS Object for setting the guiding position (Device x.5). 226dez
21 3 WORDS Object for setting the oscillating functions (Device x.5) 226dez
1C 3 WORDS Object for setting width monitoring 226dez
60 8 BYTE Reserved for VB3 data master modules (transparent object) 167 dez
..
69
A0 8 BYTES Object to control the web tension controller DC 6... 167dez
F0 8 BYTES Object for data master modules (transparent object) 167dez
F1 8 BYTES Reserved for data master module object (transparent objects) 167dez
..
FE
FF 8 BYTES Reading and writing of parameters. This object is not autono- 167dez
mous but operates together with the transmit object 'FF'.
13
Survey of the input identifiers with respect to the Profibus transmit objects:
Object no. Object Function Function

[hex] length
[Bytes]
0 0 This object number is used as end identifier for the object list. ---
1 1 BYTE Empty object 144dez
3 2 BYTES Object for setting digital outputs (LK usage 4) 145dez
6 3 WORDS Empty object 210dez
7 2 BYTES Object read virtual digital outputs LK4203 (especially OL81) 145dez
C 2 BYTES Object supplies status of a web guider and support beams. 145dez
12 3 WORDS Object supplies line sensor FE5002 signal (Device x.3). 210dez
14 3 WORDS Object supplies left sensor signal (Device x.2). 210dez
15 3 WORDS Object supplies right sensor signal (Device x.1). 210dez
16 3 WORDS Object supplies left support beam position (Device x.7). 210dez
17 3 WORDS Object supplies right support beam position (Device x.6). 210dez
18 3 WORDS Object supplies actuator position (Device x.5). 210dez
19 3 WORDS Object supplies guider web offset (Device x.5). 210dez
1A 3 WORDS Object supplies left web edge position (Device x.2 und x.7). 210dez
1B 3 WORDS Object supplies right web edge position (Device x.1 und x.6). 210dez
1C 3 WORDS Object supplies the web width (Device x.1 und x.2) or width moni- 210dez
toring status.
20 3 WORDS Object supplies the controller guiding position (Device x.5). 210dez
21 3 WORDS Object supplies the status for oscillation 210dez
24 3 WORDS Object supplies left sensor signal (Device x.4) 210dez
25 3 WORDS Object supplies right sensor signal (Device x.3) 210dez
26 3 WORDS Object supplies the position of the l.h. support (Device x.9). 210dez
27 3 WORDS Object supplies the position of the r.h. support (Device x.8). 210dez
2A 3 WORDS Object supplies the position of the l.h. web edge (Device x.4 and 210dez
x.9).
2B 3 WORDS Object supplies the position of the r.h. web edge (Device x.3 and 210dez
x.8).
2C 3 WORDS Object supplies the web width (Device x.3 and x.4). 210dez
A0 8 BYTES Object for web tension controller DC 6... 151dez
EE 12 BYTES Object supplies 1-2web width measuring 155dez
F0 8 BYTES Object for data master modules (transparent object) 151dez
F1 151dez
.. 8 BYTES Reserved for data master module objects (transparent objects)
FE
FF 8 BYTES Reading and writing of parameters. This object is not autonomous 151dez
14
2.4.2 Example
The following objects have been configured in interface DI B000 for a project:
Configuration of the receive objects of the slave (DI B000):
Altogether 7 objects have been configured. For each object an output identifier must be
entered into the hardware configuration of the PLC.
Configuration of the transmit objects of the slave (DI B000):
Altogether 11 objects have been configured. For each object an input identifier must be
entered into the hardware configuration of the PLC.
15
The compatible hardware configuration of the master (S7-SPS):
Altogether 18 objects have been configured in the slave. Therefore, exactly 18 DP

identifiers must have been entered into the master.
2.4.3 Defect diagnosis if there are problems with the connection.

To communicate with a PLC 4 conditions must be met:
(1) DI B000 must be connected to the PLC via a Profibus cable.
(2) The Profibus address of the DI B000 (Slave) must correspond to the address con-
figured in the master (PLC).
(3) The correct GSD files for DI B000 must be installed in the PLC.
(4) The configuration of Master and Slave must be identical.
In case you are experiencing communication problems between PLC and DI B000 pro-
ceed as follows:
1. Refer to the parameter listing of ‘Config-Module’ of DI B000:
16
2. Check parameters No. 7 (Baud rate):

Following ‘Power ON’ the interface tries to synchronize to the correct Baud rate of
the Profibus net. To do so the interface changes its own Baud rate continuously
until the correct Baud rate has been found. This can be seen from the parameter
value of the ‘Baud rate.
If this value changes check whether the DI B000 is connected to the Master by a
Profibus cable. A frequent reason for such a condition is that the individual wires of
the Profibus cable have been mixed up in the plug.
If this parameter shows a constant value then DI B000 has a physical connection
to the Profibus and can intertpret the data. In this case continue with item 3.
3. Check parameters No. 9 (error EL_Net intf.):
3.1 The parameter shows value 4 (No Master):

The interface is not addressed by the master. This indicates that the address for
DI B000 as configured in the master (PLC) does not coincide with the Profibus ad-
dress of DI B000. Correct the Profibus address in the PLC or in the Config-Module
of the interface (DI B000) in parameter No. 5 „OwnNodeNr“. If the Profibus address
in the interface is changed, a restart is required for the interface (reset). Otherwise
the new address will not be accepted.
3.2 The parameter shows value 1 (Param. Error):

Check whether the correct Profibus module (GSD file) for the DI B000 has been
included in the PLC.
3.3 The parameter shows value 2 (Config Error):

Wrong communication data are yet another reason why the PLC refuses to com-
municate with DI B000.
With DI B000 the desired data records (objects) may be configured freely as re-
quired by the given application. This configuration (collection of objects in DI B000)
must correspond to the configuration data in the PLC. When the connection is set-
up the configuration data of the PLC are compared to the configuration data (col-
lection of objects) in the DI B000. The master (PLC) will refuse a communication
setup if both are not exactly the same.
To do: compare the configuration in the master (PLC) to the object setup in the
slave (DI B000). See above section Fehler! Verweisquelle konnte nicht gefun-
den werden. and the example in section Fehler! Verweisquelle konnte nicht ge-
funden werden.
If all the configurations have been carefully checked and if still no data exchange is
possible, an object which does not exist could have been configured in DI B000 or
eventually objects have been entered which require further objects. In both cases a
value will be displayed in Object-Module parameter 136 and 137 of DIB000. This
value indicates the object of the error. The following figure shows an error in the
parameter entry for ‚rec.object 2’:
17
After correcting the error and restarting the interface (reset) both parameters must
display value 0.
3.4 The parameter shows value 0 (no Error):

In this case the data exchange between master (PLC) and DI B000 is already ac-
tive. The LED for ‘Data Exchange’ on DI B000 shines green.
4. In case the LED for ‘Data Exchange’ shines and data which has (presumably)
been sent from the PLC to DI B000 have not arrived / you do not see the data sent
from DI B000 in the PLC, then, in most cases, a problem with data handling has
occurred in the PLC. You may check the data in the ‘display parameters’ of the in-
terface. See section Fehler! Verweisquelle konnte nicht gefunden werden. and
Fehler! Verweisquelle konnte nicht gefunden werden.
With S7 from Siemens it is often necessary to use special function modules (inte-
grated into the PLC) for reading and writing the ‘consistent’ Profibus data. This de-
pends on the firmware of the PLC.
If the Profibus interface is integrated into S7 (compact PLC), the integrated mod-
ules ‘SFC14’ and ‘SFC15’ will have to be used. If the Profibus interface can be
stretched the corresponding functions are called ‘dp_send’ and ‘db_receive’.
2.5 Display block for receive data

In the following parameter block the data content of a receive object may be displayed.
The output may be performed directly with most receive objects (from the scanner) by
setting the format control bit in the control word or by entering an object entry number.
105. receive data Data content of a

receive object
(as seen from interface
106 rec. displ.obj.no. 0 0 0 32 Receive object entry
number the object data
of which are
displayed
107. rec. byte 1 00 00 00 FF hex Byte 1
(display field only;
structure as in doc)
.... ... ... ... ... ... ... ...
18
2.5.1 'rec. displ.obj.no.' parameter

This parameter indicates which receive object is displayed in the following parameters. The
value is a pointer in the receive object table. It lists the type of object concerned.
• 0 means that no receive object is selected for the display.
• 1.. 32 means that the data of the specified object pointer are output.
Many receive objects may be directly set by the customer’s PLC to format control. The first
object in the mainloop (continuous cycle) which is input with the set Format control con-
trol bit is indicated in the parameters display and the object pointer entered online in pa-
rameter 106. If two objects are set with the Format control control bits the second is ig-
nored. If no control bit is set in the object the numbered object is displayed online in pa-
rameter 106. If the control bits for the display are reset, the object most recently selected
will be output.
In the case of receive objects in which the format control may be set via a control bit, this is
possible independently of the accept bit in the control word.
2.5.2 'rec. byte xx' parameter

These parameters are display parameters. Output is byte by byte.
• 1st byte byte on the left after document
• 10th byte byte on right after document
From the selected receive data record a max. of 10 bytes are displayed. If the object
has less bytes the value in the unused parameter will be displayed as '00'. The se-
quence of the display corresponds to the sequence of the bytes in the documentation
(from left to right) and not the sequence in which they are transmitted to the network.
The customer may thus check whether the data record is transmitted in the correct
byte sequence.
2.6 Display block for transmit data

In the following parameter block the data content of a transmit object may be dis-
played. Output may be initiated by entering an object entry number.
117. transmit data Data content of a

transmit object
118 tr. displ.obj.no. 0 0 0 64 Transmit object entry
number the object data
of which are displayed
119. tr. byte 1 00 00 00 FF hex Byte 1
.... ... ... ... ... ... ... ...
19
2.6.1 'tr. displ.obj.no.' parameter

This parameter indicates which transmit object is displayed in the following parame-
ters. The value is a pointer in the transmit object table. It lists the type of object con-
cerned.
• 0 means that no transmit object is selected for the display.
• 1.. 64 means that the object data indicated by the object pointer are output.
2.6.2 'tr. byte xx' parameter

These parameters are display parameters. Output is byte by byte.
• 1st byte byte to the left after document
• 10th byte byte to the right after document
For each object only the existing number of bytes, starting from the left, are written.
The value '00' is output in unused parameters.
2.7 Parameter block for 'mount positions'

For some objects the system also requires ‘offset values’ that specify the distance be-
tween a reference point in the machine and the left and right sensor or support beam.
The transmit objects concerned are:
• Object 16 hex (left support beam position)
• Object 17 hex (right support beam position)
• Object 1A hex (left web edge position)
• Object 1B hex (right web edge position)
• Object 1C hex (web width)
The receive objects concerned are:

• Object 16 hex (left support beam position; only if 'with mountposition' )
• Object 17 hex (right support beam position; only if 'with mountposition' )
These distance values are located in the 'mount position' logical module. The values
are entered in this module in parameters 7..22. 2 parameter fields respectively are
available for each CAN group. 1 value specifies the offset of the left sensor or support
beam to the reference point and 1 value specifies the offset of the right sensor or sup-
port beam to the reference point. The machine center is frequently used as the refer-
ence point. Offset values to the left of the reference point are entered as negative
numbers.
If the sensors are mounted on support beams, the offset value is the distance between
the reference point and sensors when the support beams are at their zero position.
In order for these ‘offset values’ to be transmitted in the DCS system, parameter 6
(send mount pos.) of the interface must be set. This parameter is designed as a bit
field. Each bit represents one of the 8 groups for transmitting the ’offset values’
whereby bit 0 corresponds to group 0.
20
5. mount positions Mount offsets

6 send mount pos. 00 00 00 FF hex Transmit activation
of following
‘MountPositions’
Bit field; in the CAN network
each group may only be
transmitted once
7 mount pos. left 0 0.0 0.0 -3000.0 3000.0 mm MountPosition for left
sensor / support beam
from grp. 0
Distance of reference point
(e.g. machine center) to the
sensor/support beam signal ‘0’
8 mount pos. right 0 0.0 0.0 -3000.0 3000.0 mm MountPosition for
right sensor / support
beam from grp. 0
Distance of reference point
(e.g. machine center) to the
sensor/support beam signal ‘0’
from grp. 1
beam from grp. 1
from grp. 2
beam from grp. 2
from grp. 3
beam from grp. 3
from grp. 4
beam from grp. 4
from grp. 5
beam from grp. 5
from grp. 6
beam from grp. 6
21
from grp. 7
beam from grp. 7
‘send mount pos’ parameter structure:

Bit 7 Bit 0
Grp.7 Grp.6 Grp.5 Grp.4 Grp.3 Grp.2 Grp.1 Grp.0
|<--------------------------------------- Bitfeld ------------------------------------>|
If only 1 physical sensor is available in a group for width measuring (e.g. camera with
virtual sensor) parameter 6 (‘send mount pos.) must also be set. In this case, the offset
values are set to ‘0’.
Example: Maschine
center
Left sensor Right sensor
Dev. 0.2 Dev. 0.1
-250 mm
+250 mm
500 mm
Settings:
• Par. 6 (‘send mount. pos’) : 00000001 -> 1
• Par. 7 (‘mount pos. left 0’) : -250.0 mm
• Par. 8 (‘mount pos. right 0’) : 250.0 mm
In practice, the above values are estimated and corrected subsequently (difference be-
tween measured and actual web width).
Note: Various E+L sensors (e.g. CCD camera OL 80) can transmit their
‘mount position’ to the CAN-Bus themselves. This means that the
sensor ‘mount position’ may either be entered on sensor or interface
commissioning.
If the sensor is to transmit the ‘mount position’ the sensor ‘send
mount position’ parameter must be set to 1 (0= do not transmit,
1=transmit). At the same time ‘mount position’ transmitting must be
inhibited on the interface. This is performed via parameter 133 of the
interface.
22
2.8 Parameter blocks with commissioning supports

The parameter 'error EL_Net intf.' is available in the logic 'Config-Module'. This is the
parameter where Profibus-specific status numbers and error numbers are saved which
occur during Profibus initialization.
See section Fehler! Verweisquelle konnte nicht gefunden werden. Fehler! Ver-
weisquelle konnte nicht gefunden werden..
A further block is assigned to the logical 'object module'. This parameter block mainly
consists of display fields and serves as a support on interface commissioning.
135. gen. service field General field for com-

missioning
136. rec. obj.no. error 0 0 0 32 Receive object entry
number the object entry
value of which is not o.k.
(display field only)
137. tr. obj.no. error 0 0 0 62 Transmit object entry
number the object
entry value of which is
not o.k.
138. state re.tr obj.no 0.00 0.00 0.00 32.64 Object entry number
for 'state CAN com-
mand' parameter
(display field only, is being
displayed for approx. 3 sec)
1.00 .. 32.00 = Receive object
entry number
00.01 .. 00.64 = Transmit
object entry number
139. state CAN command 0 0 0 255 Status, error code in
CAN interface sector
(display field only, is being
displayed for approx. 5 sec)
0 = o.k.
140 db_level 0000 0000 0000 FFFF hex for internal use only
(development and service aid)
23
2.8.1 'rec.obj.no. error' parameter

On starting the interface the configuration block for the receive data is checked. If an
error is established in the object configuration the entry number of the defective object
entry is displayed in this parameter. The object itself is treated as an empty object for
2bytes. If several incorrect entries are featured in the configuration block, the first in-
correct entry is displayed. If the value '0' is entered, no error has been found.
2.8.2 'tr.obj.no. error' parameter

In this parameter the entry number of an incorrect object entry for the transmit data is
displayed. See also section 2.8.1.'rec.obj.no. error' parameter
2.8.3 'state re.tr obj.no' and 'state CAN command' parameter

Status or error numbers that may be assigned to the CAN interface are stored here. In
the 'state re.tr obj.no' parameter the entries made for which object entry number in the
'state CAN command' parameter are entered. In the 'state re.tr obj.no' parameter a
decimal point is displayed to separate the numbers of the two object entry fields. The
receive object entry numbers are entered to the left of the decimal point, the transmit
object numbers to the right.
Errors or notes that occur during data exchange are entered. If an error occurs etc. the
corresponding object entry number with the relevant error number is displayed for ap-
prox. 5 seconds.
Error table
Error no. Error type
[decimal]
4 addressed CAN group not featured or no longer active
7 internal buffer overflow for command processing
17 command cannot be transmitted; no CAN connection;
18 addressed CAN device refuses command; (not host interface);
24
2.8.4 'db_level' parameter

This parameter is used to initiate outputs from internal data fields. This serves as an
additional commissioning support. Outputs are via the integrated serial interface. The
CANMON program (PC) or a terminal may be used as output device. See also section
“Fehler! Verweisquelle konnte nicht gefunden werden. Fehler! Verweisquelle
konnte nicht gefunden werden.”. The RS232-specific settings are permanently set:
• 115200 baud
• 8 data bits
• 1 stop bit
• no parity
A modem cable is required as PC cable (not crossed). A minimum of pins 2 and 5 of

the 9-pole sub-D connector are needed for outputting.
The following data fields may be output:

• defined 'receive objects'
• defined 'transmit objects
• data change of objects
• software versions
2.9 Parameter block with general information

This parameter block consists of display fields.
129. general info field General information field

130. rec. data len word 0 0 0 240 Data length of the
receive object data
in words
without header)
131. tr. data len word 0 0 0 240 Data length of the
transmit object data
in words
132. shortest cycletime 0 0 0 255 ms Shortest processing
time of a receive and
transmit data record
within one second
133. longest cycletime 0 0 0 255 ms longest processing time
of a receive and trans-
mit data record within
one second
134. average cycletime 0 0 0 255 ms average processing
time of a receive and
transmit data record
within one second
25
2.9.1 'rec. data len word' parameter

The length of the receive data block (scanner -> E+L interface) is displayed in words
(16 bits) in this parameter. This is the total length of all configured objects in the con-
figuration block for receive data.
If the object list is changed it will only be accepted on restarting the interface. The 'rec.
data len word' parameter is then also reset.
This value may be used for the scanner configuration. With the ControlNet scanner
please note that with it 2 additional words must be configured. In these 2 words the
scanner additionally transmits a 'header' in front of the actual data block.
2.9.2 'tr. data len word' parameter

The length of the transmit data block (E+L-interface -> Scanner) is displayed in words
(16 bits) in this parameter. This is the total length of all configured objects in the con-
figuration block for transmit data.
If the object list is changed the change will only be accepted on the restart of the inter-
face. The 'tr. data len word' parameter will also be reset.
This value may be used directly for the scanner configuration.
2.9.3 '... cycletime' parameter

To check how much time the interface requires in order to process the receive and
transmit object list (1 mainloop) every second the slowest, fastest and average proc-
essing time in milliseconds is displayed. Measuring is repeated anew each second.
26
3 Receive objects
The individual objects from the HOST (customer control) to the E+L device are de-
scribed on the following pages. A maximum of 32 objects may be stored in the 'receive
obj. list' parameter block.
These objects are described as receive objects as seen from the E+L interface.
3.1 Object code 01 hex 1 byte empty object
The object is used as a place holder in the receive data record. It is used if another ob-
ject has an odd length (bytes) and the customer’s control can only process and write
data word by word (2 bytes) or there is a restriction that the start address of the data
words must always be even or odd.
The empty object is not processed by the interface.
For the empty objects (object 01 and 02) the CAN group etc. is not assessed in the ob-
ject information. Empty objects may be created several times in the object list
Length 1 byte data format fixed number
LOW byte
Byte (1)

The object is used as a place holder in the receive data record. It is used if the cus-
tomer’s control can only process and read data as a double word (4 bytes) or there is a
restriction that the start address of the data words must be set to a double word ad-
dress.
This object may also be used to 'reserve' data bytes. If e.g. several such objects are
created at the end of the object list they may b e written on by other objects without
changing the length of the overall receive data record. In this case the scanner need
not be configured again.
The CAN group etc. in the object information is not assessed for the empty objects (ob-
ject 01 and 02). Empty objects may be created several times in the object list.
Length 2 bytes Data format fixed number
HIGH byte LOW byte

Byte (1) Byte (2)
27
3.3 Object code 03 hex Setting digital outputs

This object transmits two bytes which are directly passed on to the outputs of 2 inde-
pendent logic modules type 'LK 4002’ or 'LK 4203' by the interface. The interface itself
does not evaluate the data which is at the free disposal of the user. Both output bytes
(Byte 1 and Byte 2) are not consistent to each other on the CAN bus.
The CAN addresses of the LK modules are indicated in the logic module ’ObjPar-
Modul’. In is possible to indicate either just one address for the object or two ad-
dresses. If only 1 data byte is being used, enter value '00’ as address of the other data
byte which will then not be considered. These addresses are independent from the ad-
dresses which read the inputs (send object 03). If no address is indicated for the object
or if an address is transmitted which has already been used earlier for a receive object
'03’, this is shown in parameter 'rec. obj,no. error’ (See also section 2.8.1).
For the I/O modules ‘LK4002’ or LK4203’ used for the output, parameter No. 5 (IO
card usage) must be set to value ‘4’.
Length 2 Byte Data format fixed figure
HIGH Byte LOW Byte

Byte 1 Byte 2
Bit 7 .. Bit 0 Bit 7 .. Bit 0
Example: Parameter setting for data output to modules with CAN-address 1.A and 1.B:
In the following print value 1003 is entered into ‚Objekt-Modul’ / 'rec. Object 2’. Object
'03’ for 'define digital outputs’ is activated for CAN-Group 1:
28
It is further necessary to indicate the CAN addresses of the output modules to which
the data is to be sent in 'ObjPar-Modul’. In the example below 'Byte 1’ is transmitted to
the output module having CAN-address 1.A and 'Byte 2’ to the output module having
CAN address 1.B. Address input is the parameter associated to the given object ('rec.
object 2’ -> 'par. rec.obj. 2’):
Note: For easier handling we suggest to use the group which is indicated in the ob-
ject code for the address (in the example above it is CAN group 1).
Input, however, has not been limited to the group in the object specification.
This allows to describe 2 output modules in different CAN groups with just
one object or to use more than 2 output modules in one CAN group.
For the second possibility different groups must be used in the object specifi-
cation because the same objects may not be used more than once within a
Can group.
3.4 Object code 06 hex 6 byte or 3 byte empty object

The object is used as a place retainer in the receive data record. This object may also
be used to 'reserve' data bytes. If e.g. several such objects are featured at the end of
the object list they may be written with other objects without changing the length of the
overall receive data record. In this case the scanner need not be reconfigured.
In the case of empty objects the CAN group etc. will not be evaluated in the object in-
formation. Empty objects may be created many times in the object list.
29
3.5 Length 6 bytes Data format fixed number
HIGH Byte LOW Byte High Byte LOW Byte High Byte LOW Byte
Byte (1) Byte (2) Byte (3) Byte (4) Byte (5) Byte (6)
Object code 08 hex 8 byte empty object

The object is used as a place retainer in the receive data record. This object may also
be used to 'reserve' data bytes. If e.g. several such objects are featured at the end of
the object list they may be written with other objects without changing the length of the
overall receive data record. In this case the scanner need not be reconfigured.
In the case of empty objects the CAN group etc. will not be evaluated in the object in-
formation. Empty objects may be created many times in the object list.
Length 8 bytes Data format fixed number

HIGH Byte LOW Byte High Byte LOW Byte High Byte LOW Byte High Byte LOW Byte
Byte (1) Byte (2) Byte (3) Byte (4) Byte (5) Byte (6) Byte (7) Byte (8)
3.6 Object code 0C hex Control word for web guider and support
beams
With this object a web guider (with or without positioning supports for sensors) may be con-
trolled. The accompanying status is supplied by the transmit object '0C hex'. The receive and
transmit object are processed independently from one another by the interface.
The object features the 'action' bit. If this bit is set the interface takes over the control of the
guider and constantly monitors the transmitted set status with the guider status. If the guider
status is changed by a further command station (DI ... or DO ...), the interface resets the
guider to its set status. If the 'action' bit is reset, the interface relinquishes guider controlling.
The guider may then be controlled via another command unit.
Attention: this object may only be created once per CAN group.
Length 2 bytes data format bit-oriented

Word
HIGH byte (1) LOW byte (2)
Bit 15 ... Bit 0
Bit Name Property Function

0 Action Static If 'action' is set the control word is processed. (6).
1 Guider enable Static 0 = guider blocked 1 = guider enabled (the guider
enable is only effective in automatic mode) (7)
2 Auto/Manual Static Switch guider ( 0 = manual / 1 = automatic) (5) (7)
3 Centering Static Switch guider to centering mode
4 Right sensor Performance by Right sensor is selected (1) (4)
automatic mode
5 Left sensor Performance by Left sensor is selected (1) (4)
automatic mode
6 Right offset Static 1 signal Direct drive adjustment in positioning range (manual)
Key code (3)
Web offset in 1/10 mm from set value (automatic) (3)
30
7 Left offset Static 1 signal Direct drive adjustment in positioning range (manual)
Key code Web offset in 1/10 mm from set value (automatic)
8 Right support Static Right support beam selected (2) (4)
beam
9 Left support Static Left support beam selected (2) (4)
beam
10
11 Edge search Static Sensors search for the web edge (5) (7)
12
13 Parking Static The support beam moves the sensors to the outside
(park position)
14 Right support Static Support beam(s) offset to right (3)
beam adjust- Key code
ment
15 Left support Static Support beam(s) offset to left (3)
beam adjust- Key code
ment
(1) If both sensor bits are set (bit 4;5 = 1), center guiding is selected. If neither of the
two bits is set (bit 4;5 = 0) the currently selected guider mode is retained.
If TxObjekt 20 is used for starting the guiding process these bits should be set to
‚0’ (inactive).
(2) If both support beam bits are set (bit 8;9 = 1), both support beams are selected
and the offset bits affect both support beams. If neither of the bits is set (bit 8;9 =
0), the current support beam selection in the guider is retained.
(3) The offset bits for the support beams and guider must not be set when changing
the operating mode (auto, manual, centering, edge search, parking).
(4) If the guider is operated in hybrid mode (control mode = 1), on changing to auto-
matic the guider itself selects the two support beams and sensors. On changing
from auto to manual the specified sensor and support beam facility is effective.
(5) If the guider is operated in hybrid mode (control mode = 1), the guider enters the
'automatic' and 'edge search' status with the 'automatic' or 'edge search' control
bit.
(6) If the 'action' bit is reset and a 'KeyCode' is set (triggered via offset bits) a 'release code' is
also subsequently transmitted.
No other commands concerning this object are being sent to the controller after the bit re-
set. This means that there is a defined "´'Cut-off point'.
(7) If the controller uses the CAN protocol 1.0 (for example RK4004-0003F_ZO) and
the operating mode of the controller (Par. 'controller operate') is set to value 1
(guiding by the machine center line), then ‘edge search’ has the effect of 'auto-
matic'. If ’controller enable“ is reset the actuator (pivoting frame) as well as the
sensor support beams freeze.
If the control mode is set to 1 (guiding by the machine center line), the setting will
be effective only if the the controller has selected 2 sensors.
The Park and Center, Automatic and Edge search signals may be set at the same
time.
If the signals are set at the same time and if immediately after the bit 'action' is to be
reset, check whether the necessary commands have already been sent to the control-
ler. This can be done via send object '0C hex (web guider status word)'.
31
3.7 Object code 16 hex left support beam position
With this object the left support beam may be positioned with device address x.7. Posi-
tion values to the left of the reference point are transmitted as negative numbers.
With the control word various reference points related to the position value may be se-
lected. These are bits 0 to 4. With bit 5 a current positioning action may be terminated.
Attention: For positioning purposes the guider must be in manual mode. See here re-
ceive object '12 hex'.
If, with Accept edge change no further bit (bit 0 to bit 5) is set the com-
mand will not be performed.
This object may only be created once per CAN group.
Length 6 bytes data format control word (bit-oriented), value (binary in 1/100 mm)
Double word
Control word HIGH word LOW word
HIGH byte LOW Byte HIGH Byte LOW Byte HIGH byte LOW byte
(1) (2) (3) (4) (5) (6)
Bit 15 .. Bit 0 Value in 1/100 mm
Control word:
Bit Name Function Value
0 absolute Reference point is the support beam’s own 0-position. in 1/100 mm
1 relative Reference point is the momentary support beam posi- in 1/100 mm
tion.
2 absolute in Reference point is the support beam’s own 0-position. in steps
steps The value is transferred in the support beam’s own
resolution. This positioning mode is not required for
normal applications.
relative in steps Reference point is the momentary support beam posi- in steps
tion. The value is transferred in the support beam’s
own resolution. This positioning mode is not required
for normal applications.
4 absolute with Reference point is the machine reference point de- in 1/100 mm
mountposition termined via 'mount position'. (*)
5 Terminate This command is used to terminate a current position- ---
ing action. The transferred value is not used.
6 Reserved (1)
.. ... ...
13 Reserved (1)
14 Accept bit On a signal change from '0' to '1 the position value is
accepted and positioning started.
15 Format control The incoming data of this object are displayed in the
sequence specified above.
(*) For this positioning mode a 'mount position' must be available on the CAN bus. See
section 2.7.
(1) These bits should be written with '0' in order to assure compatibility in the event of
expansions.
32
Example: absolute support beam positioning to position 2910.88 mm:

0100 0000 0000 0001 00 04 71 10
40 01 00 04 71 10
3.8 Object code 17 hex right support beam position
With this object the right support beam may be positioned with device address x.6. Po-
sition values to the left of the reference point are transmitted as negative numbers.
With the control word different reference points related to the position value may be se-
ceive object 12 hex.
If, with Accept edge change no further bit (bit 0 to bit 5) is set the command
will not be performed.
Double word
HIGH byte LOW byte HIGH byte LOW byte HIGH byte LOW byte
(1) (2) (3) (4) (5) (6)
Control word:
0 absolute Reference point is the support beam’s own 0-position. in 1/100 mm
1 relative Reference point is the momentary support beam posi- in 1/100 mm
tion.
2 absolute in Reference point is the support beam’s own 0-position. in steps
steps The value is transferred in the support beam’s own
resolution. This positioning mode is not required for
normal applications.
relative in steps Reference point is the momentary support beam posi- in steps
tion. The value is transferred in the support beam’s
own resolution. This positioning mode is not required
for normal applications.
4 absolute with Reference point is the machine reference point de- in 1/100 mm
mountposition termined via 'mount position'. (*)
6 Reserved (1)
.. ... ...
13 Reserved (1)
33
(*) For this positioning mode a 'mount position' must be available on the CAN bus. See
section 2.7.
expansions.
Example: relatively position support beam to position –40.50 mm (to left):

0100 0000 0000 0010 FF FF F0 2E
40 02 FF FF F0 2E
3.9 Object code 18 hex position actuator

With this object the actuator may be positioned with device address x.5. Position val-
ues to the left of the reference point are transmitted as negative numbers.
With the control word various reference points related to the position value may be se-
ceive object 12 hex.
If, with Adopt edge change no further bit (bit 0 to bit 3 or bit 5) is set the
command will not be performed.
Length 6 bytes Data format control word (bit oriented), value (binary in 1/100 mm)
Double word
(1) (2) (3) (4) (5) (6)
34
Control word:
0 absolute Reference point is the actuators own 0-position. in 1/100 mm
1 relative Reference point is the momentary actuator position. in 1/100 mm
2 absolute in Reference point is the actuator’s own 0-position. The in steps
steps value is transferred in the actuator’s own resolution.
This positioning mode is not required for normal appli-
cations.
relative in steps Reference point is the momentary actuator position. in steps
The value is transferred in the actuator’s own resolu-
tion. This positioning mode is not required for normal
applications.
4 Reserve Reference point is the machine reference point de-
termined via 'mount position'. (*)
6 Reserve (1)
.. ... ...
13 Reserve (1)
expansions.
Example: relative actuator positioning to position –10.00 mm (to left):

0100 0000 0000 0010 FF FF FC 18
40 02 FF FF FC 18
35
3.10 Object code 19 hex set web offset
With this object a web offset may be set in the guider. The value is transmitted in bi-
nary form (two’s complement) in 1/100mm. As seen from the direction of web travel
more positive values effect a web offset to the right and smaller or more negative val-
ues a web offset to the left. The web offset is also adopted when the guider is in ‘man-
ual’. The offset only become effective in ‘automatic’ mode.
The control word may be used to select whether the web offset should be set as abso-
lute or relative.
Attention: If, on Accept edge change no further bit (bit 0 to bit 1) is set, the command
will not be performed. The accept bit is hereby adopted internally for edge
detection (safety function against unintentional setting of the web offset).
Double word
(1) (2) (3) (4) (5) (6)
Control word:
0 absolute Reference point is the actuator’s own 0-position. in 1/100 mm
1 relative Reference point is the momentary actuator position. in 1/100 mm
2 Reserve (1)
.. ... ...
13 Reserve (1)
14 Accept bit On a signal change from '0' to '1 the web offset value
is accepted and set.
display parameter block in the sequence specified
above.
expansions.
Example: change relative web offset by +3 mm (web offset to right):

0100 0000 0000 0010 00 00 01 2C
40 02 00 00 01 2C
36
3.11 Objektcode 20 hex set guide position (New DATA RECORD only)
Important: If no other bit (bit 4 to bit 7) is set at edge change acceptance the com-
mand will not be executed. The acceptance bit will be used internally for edge recogni-
tion (to protect against the unintentional setting of the guiding position).
This object may be defined only once per CAN group.
Length 6 Byte Data format control word (Bit oriented), value (binary in 1/100 mm)
Double word
Control word HIGH Word LOW Word
HIGH Byte LOW Byte HIGH Byte LOW Byte HIGH Byte LOW Byte
(1) (2) (3) (4) (5) (6)
Bit 15 .. Bit 0 value in 1/100 mm
Control word:
Bit Name Function value
0
1
2
3
4 SetBit0 Encoding value definition Bit 0 default value
8 Reserve (1)
9 Reserve (1)
10 Reserve (1)
11 Reserve (1)
12
13
14 Acceptance bit At signal change from '0' to '1' the default values
(SetBit_; CodeBit_) will be accepted and the value
which belongs to the SetBits will be sent to the data
master.
15 Format check The incoming data of this object will be displayed on
the display parameter block in the sequence men-
tioned above.
(1) These bits should be described with a '0' in order to maintain the compatibility in
case of expansion.
37
Encoding Value definition Default value
The selected parameter with the default value is set via the bit combination.
0000(0) No selection
0001(1) Guiding left with support positioning
0010(2) Guiding right with support positioning
0011(3) Guiding center with support positioning
0100(4) Guiding left without support positioning
0101(5) Guiding right without support positioning
0110(6) Guiding center without support positioning
0111(7) RESERVE
1000(8) Guiding by actual position with actually selected sensors
1001(9) Guiding left alternative sensor (x.4) with support positioning
1010(10) Guiding right alternative sensor (x.3) with support positioning
1011(11) Guiding center alternative pair of sensors (x.3&x.4) with support positioning
1100(12) Guiding left alternative sensor (x.4) without support positioning

1101(13) Guiding right alternative sensor (x.3) without support positioning
1110(14) Guiding center alternative pair of sensors (x.3&x.4) without support
positioning
1111(15) RESERVE
Important:
For the defaults 0001..0110 and 1001..1110 the bits for sensor selection in
TxObjekt 0x0C must be inaktive because these rival the above commands.
Example: Guidposition
Guiding by center line with support positioning to 100.00mm
0100 0000 0011 0000

40 30 00 00 27 10
38
3.12 Object code 21 hex set oscillation

This object is functional as off software version RK4004-8003f_zL and
RK4004_0003f_zt. It is not functional on its own but cooperates with the send ob-
ject '21 hex'. It is further necessary that par. 11 „osc. Triggermode“ in the con-
troller is set to 0 „time-osc-ext-cmd.
Important: If no other bit is set at edge change accetance (bit 4 to bit 7), the com-
mand will not be executed. The acceptance bit will be acquired internally for edge de-
tection (protective function againt accidental settings).
This object may be created only once per CANgroup.
Length 6 Byte data format 1 control word (bit oriented), value
Double word
(1) (2) (3) (4) (5) (6)
Control word:
0 Oscillation On/Off Switch ON oscillation Setbits must
Switch OFF oscillation be set with
value 4
0=Off
1=ON
1 Oscillation basics Time or pulse base Setbits must
be set with
value 4
0=time base
1=puls base
2
3
4 SetBit0 Coding value definition Bit 0 default value
8 CodeBit0 Coding bit 0 default value for send object
12
13
14 Acceptance bit At signal change from '0' to '1' the value defaults
pertaining to the SetBits will be sent to the data
master.
39
15 Format check The incoming data of this object is displayed on the

display parameter block in the sequence shown
above..
Coding vaue definition default value: SetBit0-SetBit3
Based on the bit combination the selected parameter will be set with the default value.
0001(1) Set oscillion time ( in s) min=1, max=700
0010(2) Set oscillation amplitude (in 1/100 mm) min=0, max=500mm
0011(3) Set oscillation wave shape (in %)
min=5 ! square shape, max=95!delta shape
0100(4) Set oscillation control
0101(5)
0110(6)
0111(7)
1000(8)
1001(9)
1010(10)
1011(11)
1100(12)
1101(13)
1110(14).
1111(15)
Coding value definition for send object: CodeBit0-CodeBit3

The output in the send object will be set based on the bit combination
0001(1) Read oscillation time (in s)
0010(2) Read oscillation amplitude (in 1/100 mm)
0011(3) Red oscillation wave shape (in %)
0100(4)
0101(5)
0110(6)
0111(7)
1000(8)
1001(9)
1010(10)
1011(11)
1100(12)
1101(13)
1110(14).
1111(15)
40
Example:
0100 0000 0100 0001
40 41 00 00 00 00
Control: oscillation ON 0,00 mm
Example:
0100 0000 0001 0000
40 10 00 00 00 0A
Control: set oscillation 10s
41
3.13 Object code 1C hex set width control

This object is used to set the width control data (target width, tolerance limits
plus/minus for alarm and early warning). A four digit bit combination (SetBitx -- encod-
ing value definition) specifies which value is being set.
For the width control as such there must be another device available in the E+L CAN-
net. This is either a ZC 4013 – module (software ZC 4013-9029U_Z.) or a ZC 4081 –
module (software ZC 4081-9001F_Z.).
This objects works with send object 028 (1C hex )

Per CAN group this object may be applied only once.
This object is implemented in the software versions from October 20, 2003:
Length 6 Byte Data format control word (Bit oriented), value (binary in 1/100 mm)
Double word
(1) (2) (3) (4) (5) (6)
Control word:
0 Width control ON
1 Width control OFF
2 Target width = set actual width
3 Min/Max value delete memory
(not yet realized)
8 CodeBit0 Encoding value definition Bit 0 for send object 028
12
13
14 Acceptance bit At signal change from '0' to '1' the default values
which belongs to the SetBits will be sent to the data
master.
15 Format check The incoming data of this object are shown on the
display parameter block in the sequence indicated
above.
42
Encoding value definition default value
Using the bit combination the default value is set for the selected parameter.
0000 No selection
0001 Target width
0010 Tolerance plus alarm
0011 Tolerance minus alarm
0100 Tolerance plus early warning
0101 Tolerance minus early warning
0110 Hysteresis for switching procedure
Example: Target width = actual width

0100 0000 0000 0101
4 05 00 03 B2 12
0
Status: value available width: +2421,94 mm
Target width = actual width is set only when width control is activated and measuring
signal is valid.
Encoding value definition for send object 028
Using the bit combination the output is set in the send object.
0000 The send object is switched to internal width measurement camera or/
support(*)
0001 The send object is switched to output web width of the external width control
ZC4081(*)
0010 The send object is switched to output target width
0011 The send object is switched to output tolerance plus alarm
0100 The send object is switched to output tolerance minus alarm
0101 The send object is switched to output tolerance plus early warning
0110 The send object is switched to output tolerance minus early warning
0111 The send object is switched to output hysteresis for switch procedure (1)
1000 The send object is switched to output of the maximum difference (1)
1001 The send object is switched to output of the minimum difference (1)
1010 The send object is switched to output of the max. actual width (1)
1011 The send object is switched to output of the min. actual width (1)
(*) if width monitoring is used, the width value should be taken from width monitoring.
(1) not yet realized
43
3.14 Objektcode A0 hex Controls the web tension controller DC 6...

This object can control web tension controller DC 6... . The web tension controller will
operate either as controller type 0 (actuator brake) or as controller type 1 (actuator e-
lectric drive)..
If this object is used, it becomes necessary to define in addtition send object 'A0
hex' with which it is cooperating (see section : 4.16).
Important: This object may be defined only once per CAN group.
In normal operation the web tension controller is controlled by digital machine contacts.
The digital signals have highest priority, they cannot be eliminated via the interface. A
bit in the control word (Bit 0) signals to the interface whether the control bits for the op-
erational mode of the web tension controller (BKR) must be activated. If the web ten-
sion controller (BKR) is controlled via the interface the digital machine contact should
not be connected. Bit 0 activates the bits 1 to 5.
In some cases parallel operation via machine signals and interface (receive object) is
asked for. This is a rather difficult request as only one “OR“ function of the same type
of signals can be realized. Some operational modes exclude certain control modes for
safety reasons, which means that the requested operation cannot be started. The send
object the actual operational mode.
Length 8 Byte Data format 2 control words (Bit oriented), value (binary)
Control word Control word 2 Double word
HIGH LOW Byte HIGH LOW Byte HIGH Byte Byte LOW Byte
Byte (1) (2) Byte (3) (4) Byte (3) (4) (5) (6)
Bit 31 .. Bit 16 Bit 15 .. Bit 0 value
Control word 1:
16 --- (1)
.. .. (1)
19 --- (1)
24 CodeBit0 Encoding value definition Bit 0 for send object A0 hex
28 --- (1)
29 --- (1)
30 Acceptance At signal change from '0' to '1' the default values (Set-
Bit_; CodeBit_) will be accepted and the value which
belongs to the SetBits will be sent to the data master.
31 Format check The incoming data of this object are shown on the dis-
play parameter block in the sequence indicated above.
44
case of expansion.
Encoding value definition default value (SetBit3 .. SetBit0)
Via the bit combination and after data acceptance (acceptance bit; Bit 30) the parame-
ter selected will be set with the default value.
0000 (00) No selection (value in double word will be ignored)

0001 (01) ---
0010 (02) ---
0011 (03) Diameter at start (actual data record) (value in 1/100 mm)
0100 (04) Web tension target value (actual data record)
0101 (05) Web tension target value with diameter = 0 % (actual data record)
1011 (11) P-term in percent (actual data record)
1100 (12) I -term in ms (actual data record)
1101 (13) D-term in ms (actual data record)
1110 (14) Parameter record “x“ (0 ..7) go actual (1)
1111 (15) ---
(1) The previously actual parameter record (recipe block) is being copied back to its
place of origin. For further details refer to the description of the web tension con-
troller DC 6...
Encoding value definition for send object A0 (CodeBit3 .. CodeBit0)
Via the bit combination and after data acceptance (acceptance bit; Bit 30) the output in
the send object will be set.
0000 (00) Web tension F–IST

0001 (01) Diameter D–IST in 1/100 mm
0010 (02) Positioning signal for controller in 1/1000 V (0-10V or +/-10V) (1)
0011 (03) Diameter at start (actual data record) in 1/100 mm
0100 (04) Web tension target value (actual data record)
1011 (11) P-term in percentage (actual data record)
1100 (12) I -term in ms (actual data record)
1101 (13) D-term in ms (actual data record
1110 (14) ---
1111 (15) Outpur Errorcode (Par. No. 5 of web tension controller)
(1) this value is available in the software versions from March 23, 2007.
45
Control word 2:
0 Action Operation: 0 = machine contact; 1 = control bits
1 Manual
2 Automatic
3 Controlled stop Control up to standstill (bit is valid only for controller
type 0 ) (2)
4 Release brake Releases the brake (bit is valid only for controller type
0 ) (2)
5 Synchronous Activate synchronous run (bit is valid only for controller
run type 1) (2)
6 --- (1)
7 --- (1)
8 Batch change At signal change from '0' to '1'
9 --- (1)
.. .. (1)
15 --- (1)
case of expansion.
(3) The controller type is set in the web tension controller in parameter No. 33.
If the bit ‘Action’ has been set in control word 2, the web tension controller will be con-
trolled by the bits 1 to 5. Only one of these bits may be set at a time.
At batch change the web tension controller must be in the ‘manual’ mode. At the
change the web tension controller will backout the diameter computation. The bit for
the batch change is independend from the other bits. It may be set in parallel to one of
the other bits.
The batch change may also be activated independently from the ‘Action’ bit by a ma-
chine contact at the web tension controller. In this case there will be no feedback in the
status word of the relevant send object of the interface.
Example: The required output value of the send object is ‘web tension F-Actual’;
Set the start diameter to 800 mm;
Operation activated via interface, set web tension controller to ‘manual’.
0100 0000 0011 0000 0000 0000 0000 0011 00 01 38 80 (hex)

Bit 31 .. Bit 16 Bit 15 .. Bit 0 Wert
40 30 00 03 00 01 38 80
46
3.15 Object code F0 hex Transparent object for Data master module
With this object data from the customer (e.g. PLC) are transferred directly to an E+L
data master with special customer application software. Only bits 14 and 15 in the con-
trol word have a fixed meaning. Otherwise the contents of the data block, including the
control bits are directly (transparently) transmitted via 8 bytes or 4 words. The structure
and meaning of the data varies and may be found in the application description. This
object is unable to function on its own. It operates together with the transmit ob-
ject 'F0 hex'.
Attention: this object may only be created once per CAN group.
Length 8 bytes Data format depends on the application
Control word Word 2 Word 3 Word 4

HIGH LOW byte HIGH LOW byte HIGH LOW byte HIGH LOW byte
byte (1) (2) byte (3) (4) byte (5) (6) byte (7) (8)
Bit 15 .. Bit 0 application-dependent
Control word:
0 ---
.. ..
13 ---
14 Accept bit At signal change from '0' to '1' the data will be ac-
cepted and will be sent to the data master.
15 Format control The incoming data of the object will be displayed on
the display parameter block in the sequence specified
above.
If parameter 'data format' (see paragraph Fehler! Verweisquelle konnte nicht ge-
funden werden.) is in 'Intel-Format', the high byte and the low byte of each word (2
bytes) of the above data block are interchanged for the transmission.
6 data format 1 1 0 1 0 Format of data trans-

mission
0 = Motorola-Format
1 = Intel-Format
47
3.16 Object code FF hex read/write parameters
With this object parameters may be read and written. Some parameters feature protec-
tion against unintentional writing. On writing these parameter a special sequence is
necessary that will be described as follows This object is unable to function on its
own. It operates together with the transmit object 'FF hex' (see section: 4.195).
On writing parameters in the interface parameter ' rec. obj.0xFF key' should be noted!
See section '2.2.1 'rec. obj.0xFF key' on this subject.
Attention: If, on Accept edge change no further bit (bit 0 to bit 1) is set, the command
will not be performed. The accept bit is adopted internally for edge detection
(safety function against unintentional triggering of the command).
When writing parameters functions may be triggered or parameter
values changed that impair the function of the system or devices. In
the case of some functions, devices may even have to be sent into
E+L. For this reason no parameters should be written without prior
consultation with E+L.
Length 8 bytes data format bit field, number, values
Double word Double word

Control word Address word HIGH word HIGH word
HIGH LOW HIGH LOW byte HIGH LOW HIGH byte LOW byte
byte (1) byte (2) byte (3) (4) byte (5) byte (6) (7) (8)
Bit field Mother Target Parameter no. New value
address address
Bit field control bits for the action

Mother add. the group no. and device no. of the device to which the target device is
connected. If the target device is directly linked to the CAN network, the
address of the target device and mother device are the same.
Target add. is the group no. and device no. of the device to be edited (35 is e.g.
group 3, device 5)
PARAM no. is the parameter number that is to be edited
VALUE is the new value to be written in the parameter
Note: The ‚mother add.‘ and ‚target add.‘ bytes are treated as a word during trans-
mission. If transmission is in Intel format (ControlNet) these bytes will be
swapped for transmission.
48
Control word:
0 read parameter is read. depends
on the
parameter
1 write parameter is written. depends
on the
parameter
2 reserved (1)
.. ... ...
13 reserved (1)
14 accept bit On signal change from '0' to '1'read / write parameter
is performed.
15 format control The incoming data of the object will be displayed on
the display parameter block in the sequence specified
above.
expansions.
3.16.1 Function sequence

Writing or reading a parameter is performed via the following sequence (as seen from
the customer’s PLC).
• In the object specify the read/write parameter, mother address, target address pa-
rameter, parameter no. of the target device, the new parameter value (only for
writing) and the function (reading or writing); then trigger operation via the accept
bit.
• In the Answer object the read/write parameter is displayed by setting the ac-
knowledgement that an answer is available. Now, via the remaining bits it may be
checked whether the command could be performed.
If a parameter value was written the transmitted and received values may be
compared. If these differ the value has been limited by the parameter limit values.
• The accept bit may now be reset.
• The E+L interface then also resets the acknowledge bit in the answer.
• The read/write parameter sequence cycle is completed. Only once the value valid
acknowledge bit has accepted the 0 signal again, can (may) a new parameter be
written or read.
This handshake is indispensable for designing transmission with greater reliability and
exclude the possibility of incorrect operation.
49
Example: read value of parameter no. 5, from a passive (virtual) device with the
address 1.E that is connected to the CPU with the address 1.8:
The table illustrates the sequence from top to bottom.
Receive object FF hex from scanner: Transmit object FF from E+L interface:
Bit Mot Tar- Par. no. New value Bit Mot Tar- Par. no. New
field her get field her get value
DEV Add. DEV Add.
40 01 18 1E 00 05 00 00
40 01 18 1E 00 05 00 08
00 01 18 1E 00 05 00 00
00 01 18 1E 00 05 00 08
3.16.2 Protected parameters

In the DCS system / devices there are functions and parameter that, once performed
or once changed incorrectly, may cause irreparable damage in the CAN devices
(guider, sensor, etc.) and even make a repair by E+L essential.
In order to counteract this danger specific parameters and functions are protected so
that on first-time commissioning no damage is caused to individual devices uninten-
tionally. Protected parameters include:
• generally parameter 2 and 3 of each CAN device
• object list parameters inside the interface
• interface function parameters (bus addresses)
For writing parameters the 'rec. obj.0xFF key' parameter is stored in the interface, its
values feature the following properties:
• – 1: this value prohibits every write process with object 255 (reading is per-
mitted)
• 0: this value permits writing on unprotected parameters as well as via a
handshake (enable sequence) writing on protected parameters
• 1: this value permits write attempts on a protected parameter
In order to be able to change a protected parameter, the enable must first be fetched.
This is performed by writing the value 1 in the 'rec. obj.0xFF key' parameter in the in-
terface. The enable only applies for the following cycle and is automatically relocked.
The enable is also reset if the next cycle is 'Read parameter'. Unprotected parameters,
insofar as the 'rec. obj.0xFF key' parameter is set to 0 may be written at any time.
Generally the write parameter function is always the responsibility of the respec-
tive user and must also be explicitly enabled by the latter (change parameter
'rec. obj.0xFF key' from –1 to 0). On delivery, the default value –1 is always set in
the 'rec. obj.0xFF key' parameter. The exception being when the interface is de-
livered in systems designed and manufactured by E+L.
If the parameter is set to value 1 it will be reset to value 0 by an interface RESET.
The user himself/herself must bear the responsibility for write operation and the
possible consequences in the event of incorrect application.
50
Example: start web guider initialization run in CAN group 4 (via gear constant):
The table illustrates the sequence from top to bottom. The interface has the address
1.B with virtual address 8.2 for the object module in which the 'rec. obj.0xFF key' pa-
rameter is stored. First writing on a protected parameter is enabled in the interface ob-
ject module and then the initialization run is started by writing the value 12 decimal (0C
hex) in parameter no. 3 of the web guider.
Receive object FF hex Transmit object FF hex

(Data from scanner): (Data from E+L interface):
Bit Mot Tar- Par.no. New value Bit Mot Tar- Par.no. New
field her get field her get value
DEV add. DEV add.
40 02 1B 82 00 06 00 01
40 02 1B 82 00 06 00 01
00 02 1B 82 00 06 00 01
00 02 1B 82 00 06 00 01
40 02 45 45 00 03 00 0C
40 02 45 45 00 03 00 0C
00 02 45 45 00 03 00 0C
00 02 45 45 00 03 00 0C
Note: In the case of this object parameter reading and writing is not limited to the
CAN group defined in the object code. The option of operating in all groups in
a CAN network with one object pair (transmit and receive object) is thus pro-
vided. This object pair may nevertheless be defined 8 times (group 0..7)
whereby the transmit and receive object operate together with the same de-
fined CAN group respectively.
51
4 Transmit objects
The individual objects from the E+L device to the HOST (customer control) will be de-
scribed below. In the 'transmit obj. list' parameter block a maximum of 64 objects may
be created.
These objects are designated as transmit objects as seen from the E+L interface.
The object is used as a place holder in the transmit data record. It is used if another
object has an odd length (bytes) and the customer’s control can only process and read
data word by word (2bytes) or features a restriction that the start address of the data
words must always be even or odd. The empty object is transmitted by the interface
with the value '00'.
In the case of the empty objects (object 01 and 02) the CAN group etc. will not be as-
sessed in the object information. Several empty objects may be created in the object
list.
Length 1 byte data format fixed number
LOW byte
Byte (1)

The object is used as a place holder in the transmit data record. It is used if the cus-
tomer’s control can only process and read data as a double word (4 bytes) or features
a restriction that the start address of the data words must be set to a double word ad-
dress. This object may also be used to 'reserve' data bytes. If e.g. several such objects
are created at the end of the object list, they may be written on by other objects without
changing the total length of the transmit data record. In this case the scanner need not
be reconfigured.
The empty object is transmitted by the interface with the value '00 00'.
In the case of the empty objects (object 01 and 02) the CAN group etc. will not be as-
sessed in the object information. Several empty objects may be created in the object
list.
Length 2 bytes data format fixed number
HIGH byte LOW byte

Byte (1) Byte (2)
52
4.3 Object code 03 hex read digital inputs

This object is used to read 2 bytes which originate directly from the inputs of 2 inde-
pendent logic modules type ‘LK 4002’ or 'LK 4203'. The interface itself does not evalu-
ate the input data which is passed on directly. The data is thus at the free disposal of
the user. Both bytes (InByte 1 and InByte 2) are not consistent to each other.
The CAN addresses of the LK modules are indicated in the logic module ‚ObjPar-
Modul’. It is possible to indicate either just one address for the object or two addresses.
If only one data byte is being used, enter value '00' as address to the other data byte.
The addresses are independent from the addresses for writing the outputs (receive ob-
ject '03'). If no address is indicated for the object or if an address is indicated which has
already been used earlier for a send object ‚03’, this is shown in parameter 'tr. obj.no.
error’ (See also section 2.8.2).
For the I/O-modules ‘LK 4002’ or 'LK 4203’ used for the output, parameter No. 5
(IO card usage) must be set to value ‘4’.
The digital input data is made available by the input modules cyclically; in case of
modifications it is made available immediately.
The interface comprises 'timeout-monitoring’ for the input data. If no value is received
by an input module defined in the object list for 10 seconds an error will be displayed in
'gen. service field' (see also section 2.8.3).
Length 2 Byte Data format fixed figure
HIGH Byte LOW Byte

Byte (1) Byte (2)
Example: Parameter setting for data output to modules with CAN-address 1.A and 1.B:
In the following print value 1003 is entered into ‚Object-Module’ / 'tr. object 3’. Object
'03’ for ‘read digital inputs’ is activated for CAN group 1:
53
It is further necessary to indicate the CAN addresses of the input modules which read
the data in 'ObjPar-Modul’. In the example below the 8 inputs of the input module with
CAN address 1.A are shown on 'Byte 1’ and the inputs of the input module CAN ad-
dress 1.B are shown on 'Byte 2’. Address input is in the parameters associated to the
given object ('tr. object 3’ -> 'par. tr. obj. 3’).
Note: For easier handling we suggest to use the group which is indicated in the ob-
ject code for the address (in the example above it is CAN group 1).
Input, however, has not been limited to the group in the object specification.
This allows to enter 2 input modules into different CAN groups with one ob-
ject only or to use more than 2 input modules in one CAN group. For the sec-
ond possibility different groups must be used in the object specification be-
cause with this object ('03') the same objects may not be defined more than
once within a CAN group.
4.4 Object code 06 hex 6 byte or 3 byte empty object

The object is used as a space retainer in the transmit data record. This object may also
be used to 'reserve' databytes. If e.g. several such objects are featured at the end of
the object list these may be written with other objects without changing the overall
transmit data record length. In this case the scanner need not be reconfigured.
In the case of empty objects the CAN group etc. is not evaluated in the object informa-
tion.
HIGH Byte LOW Byte High Byte LOW Byte High Byte LOW Byte
Byte (1) Byte (2) Byte (3) Byte (4) Byte (5) Byte (6)
54
4.5 Object code 07 hex Read object virtual digital outputs LK4203
This object reads 2 bytes which come directly from the outputs of 2 independent logic
modules type 'LK 4203'. The output data is not evaluated by the interface but passed
on directly. It is at the free disposal of the user. The two bytes (OutByte 1 and OutByte
2) are not consistent to each other.
The CAN addresses of the LK modules are shown in the logic module ‘ObjPar-Modul’.
Either only one address or two addresses may be indicated there for the object. If only
1 data byte is used then value ‚00’ is entered as address for the other data byte. Value
‘00’ is then transferred for the relevant data byte.
'timeout-control’ for the input data is available in the interface. If no value is received for
10 seconds by one of the input modules defined in the object list then the correspond-
ding defects are set in 'gen. service field' (see section 2.8.3 'state re.tr obj.no' and
'state CAN command' parameter).
Length 2 byte Data format Fixed figure
HIGH Byte LOW Byte

Byte (1) Byte (2)

The object is used as a space retainer in the transmit data record. This object may also
be used to 'reserve' databytes. If e.g. several such objects are featured at the end of
the object list these may be written with other objects without changing the overall
transmit data record length. In this case the scanner need not be reconfigured.
tion.
tion. Empty objects may be created many times in the objects.
HIGH Byte LOW Byte High Byte LOW Byte High Byte LOW Byte High Byte LOW Byte
Byte (1) Byte (2) Byte (3) Byte (4) Byte (5) Byte (6) Byte (7) Byte (8)
4.7 Object code 0C hex Status word of the web guider and support
beams
This object supplies the function status of the web guider including the support beams
for the sensors. The corresponding control word supplies the '0C hex' receive object.
The transmit and receive objects are processed independently of one another by the
interface.
This object may be created several times per CAN group.
55
Length 2 bytes data format bit-oriented
Word
HIGH byte (1) LOW byte (2)
Bit 15 ... Bit 0
Bit Name Property Function

0 Guider enable Static 0 = guider blocked 1 = guider enabled (*)
1 Automatic Static 1 Signal Guider in automatic mode
2 Manual Static 1 Signal Guider in manual mode
3 Centering Static 1 Signal Guider is centered (center position) (3)
4 Right sensor Static 1 Signal Sensor is selected (1)
5 Left sensor Static 1 Signal Sensor is selected (1)
6 Right offset Static 1 Signal Continuous signal as long as right offset is pressed
(manual)
7 Left offset Static 1 Signal Continuous signal as long as left offset is pressed
(manual)
8 Right support Static 1 Signal Right support beam is selected
beam
9 Left support Static 1 Signal Left support beam is selected
beam
10 Edge found Static 1 Signal Sensors of the selected support beams have found
the web edge (2)
11 Edge search Static 1 Signal Sensors of the selected support beams are search-
ing for the web edge and 'Edge search' is active (4)
12 Parked Static 1 Signal Selected support beams have been parked (park
position reached)
13 Park support Static 1 Signal Selected support beams are parked
beam
14 Support beam Continuous signal as long as right offset is pressed
right offset (manual)
15 Support beam Continuous signal as long as left offset is pressed
left offset (manual)
(*) This bit may only be reliably determined and displayed by the interface in auto-
matic mode.
(1) If both sensor bits (bits 4 and 5) are set, guiding by the center is selected.
(2) 'Edge found' is only displayed briefly. If the guider goes into automatic mode this
information is reset.
(3) This bit is set in addition in software versions from August 04, 2003, if the controller is in a
mode where it is at a standstill and is close to the centering point.
(4) With software versions from 03.2005 this bit stays set when the edge has been
found but the support is still in the ‘edge search’ operating mode. The bit 'Edge-
Found' will be set in addition to 'EdgeSearch'.
56
4.8 Object code 14 hex Left sensor signal (x.2)

Object code 15 hex Right sensor signal (x.1)
Object code 24 hex Left sensor signal (x.4)
Object code 25 hex Right sensor signal (x.3)
With these objects the signal from the left sensor with device address x.2 and x.4 or
right sensor (dev.add. x.1 and x.3) may be read out. Signal values to the left of the
sensor zero point are transmitted as negative numbers. This zero point is typically the
sensor center.
In addition to the sensor signal a status field is supplied that, depending on the sensor
type, contains status information on the sensor.
For software versions from 22.12.2005 the mean value generation and the cycle time
may be activated in the object entry for objects 14 and 15 (see section 2.3.2 'tr. object
xx').
For software versions from 12.04.2006 the object 0x12 for line sensor FE5002 has
been integrated.
Length 6 bytes data format status word (bit-oriented), value (binary in 1/100 mm)
Double word
Status word HIGH word LOW word
(1) (2) (3) (4) (5) (6)
Status word:
The status bits depend on the sensor type, i.e. some will be interpreted differently or
not supported.
Bits 0 to 7 supply the main status for the sensor signal. In their case only 1 bit is al-
ways set. In bits 8 to 14 additional information is provided that is supported depending
on the sensor type.
Bit Name Meaning
0 NoDevice There is no left sensor (Dev. x.2) or right sensor (Dev. x.1)
in the CAN group assigned to the object.
1 RangeOK The signal is in the sensor operating range.
2 RightSide The web edge is located to the right outside the scanning
range (if the bit is set, the value “0“ is transmitted). (*)
LeftSide The web edge is located to the left outside the scanning
range (if the bit is set, the value “0“ is transmitted). (*)
4 NearRightSide The web edge is located in the right near side of the sensor
range. (*)
5 NearLeftSide The web edge is located in the left near side of the sensor
range. (*)
6 Invalid The sensor signal is invalid.
7 Warning Warning (the sensor signal is still valid!)
57
8 soiled Additional status: 'sensor is soiled' (CCD camera and sen-

sor FR 5001). Depending on the sensor the signal has a
different meaning:
CCD camera: too little light
FR 5001: two edges in view field
9 under-exposed Additional status: 'sensor is under-exposed'
(CCD camera and sensor FR 5001).
10 over-exposed Additional status: 'sensor is over-exposed'
(CCD camera only).
11 temperature Additional status: 'temperature in the sensor too
high'.
12 emergency Additional status: 'sensor emergency guiding activated'
guiding (CCD camera only).
reserve
14 calibrated Additional status: 'sensor calibrated' (not yet implemented).

15 format control The format control is activated for this object. The data se-
quence '81 02 03 04 05 06' is transmitted to the above
bytes.
(*) These main status are not supported by all sensors.
Example:
00 02 00 00 02 30
Status: RangeOK Value: 5.60 mm
58
4.9 Object code 16 hex Left support beam position (x.7)

Object code 17 hex Right support beam position (x.6)
Objektcode 26 hex Left support beam position (x.9)
Objektcode 27 hex Right support beam position (x.8)
With these objects the position of the left support beam with device address x.7 & x.9
or right support beam (dev.add. x.6 and Dev.Adr. x.8) may be read out. The position
values are in relation to the machine reference point (including ‚mount position‘! see
section 2.7). The reference point is normally the machine center. Position values to the
left of the machine reference point are transmitted as negative numbers and position
value to the right of the reference point are transmitted as positive numbers. For this
reason the position value of the left support beam typically features a negative value.
In addition to the position value a status field is supplied that contains status informa-
tion on the support beam.
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bits 0 to 6 supply the support beams’ main status. In their case only 1 bit is always set.
Bits 7 to 14 provide additional information.
Bit Name Meaning
0 NoDevice No left (Dev. x.7) or right support beam (Dev. x.6) is fea-
tured in the CAN group assigned to the object.
1 RangeOK The support beam position is in the operating range.
2 RightSide The support beam is located at the right end position. (4)
LeftSide The support beam is located at the left end position. (4)
4 NearRightSide The support beam is located at the right near side of the
support beam range. (*)
5 NearLeftSide The support beam is located at the left near side of the sup-
port beam range. (*)
6 Invalid The position value is invalid. (1)
7 SupMove Additional status: support beam moves (manual) (5)
8 EdgeFound Additional status: sensor has not found edge (3)
9 EdgeSearch Additional status: support beam in edge search mode (6)
10 SensorIsFree Additional status: support beam is parked (position reached)
11 SensorFree Additional status: support beam is being parked.
12 SupSelect Additional status: support beam is selected.
13 SupSetup Additional status: support beam is in initialization run
14 Calibrated Additional status: 'support beam calibrated' (2)
59
15 Format control Format control is activated for this object. The data se-
bytes.
(*) Reserved; signal is not issued by support beam; for this position the status 'Range
OK' is issued;
(1) e.g. mountposition missing: transmitting of the ‚mount position‘ is set in the inter-
face. It is important that ‚mount position‘ is transmitted. This may be individually
activated for each CAN group via the “send mount pos.“ parameter.
(2) Reserved; not yet implemented;
(3) The 'EdgeFound' bit is only continuously set in 'control mode' '0' of the guider dur-
ing the edge search. If the guider operates in 'control mode' '1' (hybrid mode), it is
only a brief intermediate state.
(4) If the support beams are moved in manual mode, the support beams (sensors)
move only to the web edge. In this case the 'RightSide' bits on the left support
beam and 'LeftSide' bits on the right support beam are not set.
(5) This signal is issued if the support beam is moved in manual mode;
(6) With software versions from 03.2005 this bit stays set when the edge has been
found but the support is still in the ‘edge search’ operating mode. The bit 'Edge-
Found' will be set in addition to 'EdgeSearch'
During the calibration run the ' SupSetup' and 'Invalid' bits are set. In addition, e.g. on
object 16 hex 'LeftSide' is issued and displayed by the support beam. The position val-
ues are transmitted. If no calibration run has as yet taken place (incorrect calibration
values) the position values are not correct.
Example left support beam:

00 04 FF FF D1 20
Status: RightSide Position value: -120.00 mm
Example right support beam:

00 02 00 00 A4 74
Status: RangeOK Position value: +421.00 mm
60
4.10 Object code 18 hex Actuator position
With this object the position of the actuator with device address x.5 may be read out.
The reference point for the position values is the actuator’s own 0-position. For this ob-
ject no 'mount position' is used. Position values to the left of the reference point are
transmitted as negative numbers and position values to the right are transmitted as
positive numbers.
tion on the actuator.
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bits 0 to 6 supply the main status of the actuator. In their case only 1 bit is always set.
In bits 7 to 14 addition information is provided.
Bit Name Meaning
0 NoDevice In the CAN group assigned to the object there is no actuator
(Dev. x.5).
1 RangeOK The actuator is located in the operating range.
2 RightSide The actuator is located at the right end position.
LeftSide The actuator is located at the left end position.
4 NearRightSide The actuator is located at the right near side of the range.
5 NearLeftSide The actuator is located at the left near side of the range.
6 Invalid The position value is invalid. (1)
7 Move Additional status: actuator moves (manual mode) (2)

8 Reserved ---
.. ... ...
12 Reserved ---
13 Setup Additional status: actuator is in the initialization run
14 Calibrated Additional status: actuator calibrated (3)
bytes.
(1) Reserved; this signal is not currently supported;

(2) This signal is issued if the actuator is moved in manual mode;
(3) Reserved; calibrated message is not currently supported;
61
During the calibration run the ' Invalid ' bit is additionally set. The position values con-
tinue to be transmitted. If no calibration run has yet been performed (incorrect calibra-
tion values) the position values are not correct.
Example:
00 02 FF FF FF 21
Status: RangeOK Position value: -2.23 mm
4.11 Object code 19 hex read web offset
With this object the current web offset may be read out by the guider.
A positive web offset means an offset of the web to the right and a negative value an
offset to the left.
In addition to the web offset a status field is supplied that contains status information
on the web offset.
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bit Name Meaning
0 NoWebOffset No valid web offset featured.
1 Reserved ---
.. ... ...
14 Reserved ---
bytes.
Example:
00 00 00 00 01 F4
Status: value featured Web offset: +5.00 mm
62
4.12 Object code 20 hex Read guiding position (NEW DATA

PROTOCOL ONLY)
This object is used to read out the actual “guide position“ of the web guider.
A status field is available in addition to the guide position to provide status information
concerning the guide position.
This object may be defined only once per CAN group.
Length 6 Byte Data format status word (bit oriented), value (binary in 1/100 mm)
Double word
(1) (2) (3) (4) (5) (6)
Statuswort:
Bit Name Meaning
0 Support right Support right (x.6) selected (1)
1 Support right 1 Alternative support right (x.8) selected (1)
2 Support left Support left (x.7) selected (1)
3 Support left 1 Alternative support left (x.9) selected (1)
4 Sensor right Sensor right (x.1) selected (2)
5 Sensor right 1 Alternative sensor right (x.3) selected (2)
6 Sensor left Sensor left (x.2) selected (2)
7 Sensor left 1 Alternative sensor left (x.4) selected (2)
8 Guide OK Guiding position OK
9 NOGUIDE DR blocked
10 NoDevice No equipment present
11 Target Changed The guiding value has changed (is available only for a short
time)
12 Command error Invalid command
13
14
15 Format check Format check is active for this object. Data sequence '81 02
03 04 05 06' is transmitted to the above bytes.
Example:
00 20 00 00 27 10
Status: Value available Web offset: +100,00 mm
(1) If support bits (Bit0 and Bit2) are set, guiding is by the support center line de-
vice x.6 and x.7
If support bits (Bit1 and Bit3) are set, guiding is by the alternative support de-
vice x.8 and x.9
63
(2) If sensor bits (Bit4 and Bit6) are set, guiding is by the sensor center line device
x.1 and x.2
If sensor bits (Bit5 and Bit7) are set, guiding is by the alternative sensor center
line device x.3 and x.4
4.13 Object code 21 hex read oscillion data

This object is operational from software version RK4004-8003f_zL and
RK4004_0003f_zt. It is not operational on its own but cooperates with the receive
object '21 hex'.
Important: This object may be created only once per CAN group.
Length 6 Byte data format status word (bit oriented), value (binary in 1/100 mm)
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bit Name Meaning Value
0 Oscillation Oscillation is ON or OFF 0=Off
ON/OFF
1=On
1 Oscillation basics Time base or pulse base 0=time base
1=pulse base
2
3
4
5
6
7
8 Codebit0 Coding bit 0 default value for send object
12 Time_out
13 No_Device
14
15 Format check Format check is activated for this object. The data
sequence '81 02 03 04 05 06' is transferred to the
above Bytes.
64
Coding value definition for send object: CodeBit0-CodeBit3
The output in the send object will be set based on the bit combination.
0001(1) Read oscillation time (in s)
0010(2) Read oscillation amplitude (in 1/100 mm)
0011(3) Read oscillation wave shape (in %)
0100(4)
0101(5)
0110(6)
0111(7)
1000(8)
1001(9)
1010(10)
1011(11)
1100(12)
1101(13)
1110(14).
1111(15)
Example:
01 01 00 00 00 14
Status: oscill.On Value: 20 s
Time base
Read oscill. time
4.14 Object code 1A hex Left web edge position (x.2 & x.7)
Object code 1B hex Right web edge position (x.1 & x.6)
Object code 2A hex Left web edge position (x.4 & x.9)
Object code 2B hex Right web edge position (x.3 & x.8)
With these objects the left and right web edge positions may be read. In the case of the
web edge positions the sensor, support beam values and the 'mount positions' are
calculated. The interface detects by itself whether no support beam, only one support
beam at the other side (1-motor with 2 carriages) or one support beam at the side to be
measured is featured for measuring the web edge. On a 1-motor support beam with 2
sensors the support beam position at the other side is read and calculated.
The position values are in relation to the machine reference point (including ‚mount
position‘ ! see section 2.7). Normally the reference point is the machine center. Posi-
tion values to the left of the machine reference point are transmitted as negative num-
bers and position values to the right of the reference point as positive numbers. For
this reason the left edge position typically features a negative value and the right web
edge a positive one.
tion on the position value.
65
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bit Name Meaning
0 NoValue No valid value available. (*)
1 NoSensorValue Sensor position value is invalid or there is no sensor avail-
able. (1)
2 NoMountPos 'mount position' missing (1)
3 Reserved ...
.. ... ...
14 Reserved ---
15 Format control Format control for this object is activated. The data se-
bytes.
(*) The cause of an invalid value may be a missing 'mount position' or that the sensor
detects no web edge.
(1) Additional information if bit 0 (NoValue) is set.
Example left web edge:
00 00 FF FE 34 7E
Status: value available Web edge position: -1176,34 mm
Example right web edge:

00 00 00 01 E6 90
Status: value available Web edge position: +1245.60 mm
66
4.15 Object code 1C hex Read web width/width monitoring

Object code 2C hex Read web width
If the receive object 028 (1C hex) is not featured this transmit object automatically
switches to internal width measuring. The width monitoring functions are then not avai-
lable.
With object 2C hex ONLY width measurement is functional. The alternative sensor da-
ta (x.3 & x.4) and support data (x.8 & x.9) is absorbed.
This object may be used to read the web width and width monitoring setting data. The
sensor values, the support values and the 'mount positions' are considered for the web
width. The interface recognizes by itself whether no sensor support, only one sensor
support (one motor, two slides) or two sensor supports are available for measuring the
web width. In case of a one-motor support with two sensors the support position of the
other side is being read and considered.
To set the 'mount position' values refer to section 2.7.
A status field providing status details on the web width is available In addition to the
web width.
Double word
(1) (2) (3) (4) (5) (6)
Status word:
Bit Name Meaning
0 NoValue No valid value available. (*)
1 NoRightValue Right side position value is invalid. (1)
2 NoLeftValue Left side position value is invalid. (1)
3 Status o.k. GO-range (setpoint/actual value comparison within the
tolerance range) (2) (3)
4 Status alarm Alarm overwidth (2) (3)
5 Status alarm Alarm underwidth (2) (3)
6 Status early w. Early warning overwidth (2) (3)
7 Status early w. Early warning underwidth (2) (3)
8 CodeBit0 Encoding value definition Bit 0 for output value (2) (3)
12 Active Width control active (2) (3)
13 No Device Width control module ZC 40.. is not being recognized (3)
14 Lamp test Lamp test ON
15 Format control Format control for this object is activated. The data se-
bytes.
67
(*) The cause of an invalid value may be a missing 'mount position', that no 2 sensors
(Dev. x.1 and x.2) are featured or that a sensor detects no web edge.
(1) Additional information if bit 0 (NoValue) is set.
(2) This object data has been included in the interface from the following software ver-
sions onwards:
DI B000 Profibus-interface ZC 4080-0012F_ZC
DI D000 ControlNet-interface ZC 4080-0009F_ZC
DI E000 DeviceNet-interface ZC 4080-0010F_ZD
DI F000 CanOpen- interface ZC 4080-0013F_ZA
(3) This is important only if there is width monitoring.
Encoding value definition for send object 028
Using the bit combination the output is set in the send object.
0000 The send object is switched to internal width measurement (*)

0001 The send object is switched to output web width of the external width monitoring (*)
0010 The send object is switched to output target width
0011 The send object is switched to output tolerance plus alarm
0100 The send object is switched to output tolerance minus alarm
0101 The send object is switched to output tolerance plus early warning
0110 The send object is switched to output tolerance minus early warning
0111 The send object is switched to output hysteresis for switch procedure (1)
1000 The send object is switched to output of the maximum difference (1)
1001 The send object is switched to output of the minimum difference (1)
1010 The send object is switched to output of the max. actual width (1)
1011 The send object is switched to output of the min. actual width (1)
(*) if width monitoring is used, the width value should be taken from width monitoring.
(1) not yet realized
Example: Web width with width control

0100 0001 0000 0001
4 01 00 03 B2 12
1
Status: value featured Web width: +2421.94 mm
68
4.16 Object code A0 hex Status of web tension controller DC 6...
This object is in cooperation with the receive object 'A0 hex' (see section 3.14). It ma-
kes available operational messages (status) and data of web tension controller DC 6....
The type of data (output value) is defined via 'CodeBits' in the receive object. The cor-
responding value with the CodeBits is returned as confirmation via the send object.
The cycle time of the output value is defined with the object entry (see section 2.3.2 'tr.
object xx'). The minimum allowable cycle time is 20 ms. In case a value smaller 20 ms
has been entered into the object, the interface will all by itself change the value to 20
ms.
The mean value generation can be activated in the object entry for this object. It is ap-
plied to the values ‘web tension F-ACTUAL and diameter D-ACTUAL'.
Important: This object alone is not functional. It may be defined only once per CAN
group.
Length 8 Byte Data format 2 status words (Bit oriented), value (binary)
Status word 1 Status word 2 Double word

HIGH LOW Byte HIGH LOW Byte HIGH Byte Byte LOW Byte
Byte (1) (2) Byte (3) (4) Byte (3) (4) (5) (6)
Bit 31 .. Bit 16 Bit 15 .. Bit 0 Value
Status word 1:
16 ---
.. ..
23 ---
24 CodeBit0 Encoding value definition Bit 0 for output value
28 ---
29 ---
30 ---
31 Format check Format check is activated for this object. Data se-
bytes.
69
Encoding value definition for value (CodeBit3 .. CodeBit0)
If a new assignment is being defined with Bits CodeBit3 .. CodeBit0 in the receive object
for the send object, these new assignments are being mirrored in the send object. The
bits show the assignment type of the value. After data acceptance (acceptance bit, bit 30)
the output in the send object is set accordingly on the basis of the bit combination.
The bits in this send object have the same significance as in the receive object.
0000 (00) Web tension F–ACTUAL

0001 (01) Diameter D–ACTUAL (value in 1/100 mm)
0010 (02) Positioning signal for controller in 1/1000 V (0-10V or +/-10V) (1)
0011 (03) Diameter at start (act. data record); (value in 1/100 mm)
0100 (04) Web tension target value (act. data record)
0101 (05) Web tension target value at diameter = 0 % (act. data record)
1011 (11) P-Item in percentage (act. data record)
1100 (12) I –item in ms (act. data record)
1101 (13) D-Item in ms (act. data record
1110 (14) ---
1111 (15) Output Error code (Par. No. 5 web tension controller)
(1) This value is available in software versions from March 23, 2007.
Status word 2:
Bit Name Function Wert
0 ---
1 Manuel Web tension controller is in manual mode
2 Automatic Web tension controller is in automatic mode
3 Controlled stop Control up to standstill (Bit is available only with
controller type 0)
4 Release brake Releases the brake (Bitt is available only with controller
type 0)
5 Synchronous Synchronous run activated (Bit is available only with
run controller type 0)
6 ---
7 ---
8 Batch change Batch change is being performed (1)
9 System OK Web tension controller is operational; no failure identi-
fied; controller is calibrated;
10 Ø batch OK Batch diameter is o.k.
11 V web not OK Web speed falls below the lower limit value
12 N batch not OK Batch r.p.m. falls below the lower limit value
13 F-ACTUAL not Web tension falls below the lower limit value
OK
14 NoDevice No controller present in the CAN group
15 TimeOut Command has not been accepted by the web tension
controller or no answer has been received at the
command of the controller.
70
(1) If a batch change is initiated via the receive object of the interface, this bit will be
set for 5 seconds. If a batch change is initiated via the machine contact directly at
the web tension controller, there is no feedback vis this bit.
Example: Type of output is ‘web tension F-ACTUAL;

Web tension controller and batch diameter are o.k.;
Web tension controller is in manual mode;
Value of F-ACTUAL is 250 Newton;
0000 0000 0000 0000 0000 0000 0110 0010 00 00 00 FA (hex)

Bit 31 .. Bit 16 Bit 15 .. Bit 0 Value
00 00 00 03 00 00 00 FA
71
4.17 Object code EE hex 1-2-web width measuring
The web(s) may be scanned by one or two CCD cameras. The object does not operate
with edge sensors Fr 5001 and support beam VS 35...
The transmit object is configured in the group in which the CCD cameras are addressed.
The object detects the camera configuration autonomously on the basis of the mount posi-
tion and its values or on the basis of the visual ranges with CAN protocol 2.0. On the basis
of the number of valid edges featured it detects how many webs are located in the camera
view range and returns this information in bit combination form.
The cycle time of the output value is determined in the object entry (see section 2.3.2 'tr.
object xx'). The acceptable minimum cycle time is 20 ms. If a cycle time smaller 20 ms is
entered into the object input, the interface will change the entry to 20 ms on its own.
This object data is implemented in the interface from the following software versions on-
wards:
DI B000 Profibus interface ZC 4080-0012F_ZD
DI D000 ControlNet interface ZC 4080-0009F_ZC
DI E000 DeviceNet interface ZC 4080-0010F_ZD
DI F000 CanOpen interface ZC 4080-0013F_ZA
With software versions from 26.10.2005 this object can also cooperate with cameras which
send the data in CAN protocol 2.0.
This object supplies 12 bytes as follows:

Length 12 Byte Data format 2 status words (Bit oriented), 2 values (binary in 1/100 mm)
Status word 1 Status word 2 Double word 1 Double word 2

HIGH LOW HIGH LOW 32 Bit Long value 32 Bit Long value
Byte (1) Byte (2) Byte (3) Byte (4) Byte (5) – Byte (8) Byte (9 ) - Byte (12)
Bit 31 .. Bit 16 Bit 15 .. Bit 0 ACTUAL width ACTUAL width
1 strip right in 1/100 2 strips left in 1/100
mm mm
Status word:
Bit Name Meaning
0 NoRightValue Grpx Error on right camera (CCD x.1). (1)
1 NoLeftValue Grpx Error on left camera (CCD x.2). (1)
2 NoRightValue1 Grpx Error on right camera (CCD x.3). (1)
3 NoLeftValue1 Grpx Error on left camera (CCD x.4). (1)
4 NOT USED
5 NOT USED
6 NOT USED
7 NOT USED
8 Soiled Status:‘CCD camera is soiled‘ (1)
9 Under-exposed Status:‘CCD camera is under-exposed‘ (1)
10 Over-exposed Status:‘CCD camera is over-exposed‘ (1)
11 Invalid Status:‘SensorSignal is invalid‘ (1)
72
12 Reserved ---
13 No Device Status:‘CCD camera no device featured‘ (1)
14 Calibrated(not im- ---
plemented)
15 Malfunction Group malfunction in case of errors
16 No. of webs Bit0 Binary code for no. of webs Bit0
19 Reserved ---
20 Signal error Will be set if the assignment of the edge positions is
not correct (2)
21 Width error Different no. of edges are featured for selected mode
22 MountposError Group mount positions is not activated
23 Reserved ---
24 Sensor mode 0 Binary code for camera configuration Bit0
27 Reserved ---
28 Reserved ---
29 Reserved ---
30 Reserved ---
31 Format check The format check is activated for this object. The data
sequence '81 02 03 04 05 06 07 08 09 0A 0B 0C'' is
transmitted for the above bytes.
Coding for sensor mode (SensorModus2 .. SensorModus0
000 (0) one physical CCD camera + one virtual camera

001 (1) one physical CCD camera + three virtual cameras
010 (2) two physical CCD cameras + no virtual camera
011 (3) two physical CCD cameras + two virtual cameras
100 (4)
101 (5)
111 (7) Sensor configuration not correct
Binary code for no. of webs value definition for transmit object EE
000 (0) no web featured

001 (1) one-web
010 (2) two-web
(1) Logical assignment of error messages ‘soiled, under-exposed, over-exposed,

invalid and No Device’.
The respective errors are transmitted together with the corresponding camera bits
(Bit0-4). If there are several errors in different cameras the corresponding errors
will be clocked through cyclically every three seconds.
(2) This points to a wrong configuration of the sensors. This is the case, for example, if
an internal edge features a position value which is to the right of the right hand
outer edge.
73
Additional remarks:
• If only one r.h. sensor (Adr. x.1) and one l.h. sensor (Adr. x.2) are detected then
the sensor mode is displayed correctly.
The bits ‚Error, ‚No Device’, ‚Defect with camera x.3’ and ‚Defect with camera x.4’
are set because a two-web width measurement system expects the these sensor
signals.
• If all sensor signals are available (x.1 .. x.4) but only 1web is detected then this
web width is supplied and the missing edges are displayed as ‚defect.
4.18 Object code F0 hex transparent object for data master module
With this object data are read by a E+L data master with special customer application
software. The data are transmitted directly (transparently). Only bit 15 in the control word
has a fixed meaning. Otherwise the structure and meaning of the data is varied and may
be found in the application description. The data are sent and provided cyclically. The
cycle time is determined on entering the object (see section 2.3.2 'tr. object xx').
This object is unable to function alone. It operates together with the receive object
'F0 hex'.
Important:This object may only be created once per CAN group.
Length 8 bytes data format depends on the application
Control word Word 2 Word 3 Word 4

HIGH LOW byte HIGH LOW byte HIGH LOW byte HIGH LOW byte
byte (1) (2) byte (3) (4) byte (5) (6) byte (7) (8)
Bit 15 .. Bit 0 application-dependent
Control word:
0 ---
.. ..
14 ---
display parameter block in the sequence specified
above.
If parameter 'data format' (see paragraph Fehler! Verweisquelle konnte nicht ge-
funden werden.) is in 'Intel-Format', the high byte and the low byte of each word (2
bytes) of the above data block are interchanged for the transmission.
6 data format 1 1 0 1 0 Format of data

transmission
0 = Motorola-Format
1 = Intel-Format
74
4.19 Object code FF hex read/write parameters

This object supplies the answer to the receive object 'FF hex' (see section: 3.13) for
reading and writing parameters. This object is unable to operate on its own.
The operating principle of the objects is described in section “3.16 Object code FF hex
read/write parameters”
Important:This object may only be created once per CAN group.
Length 8 bytes data format bit field, number, values
Double word Double word

Status word Address word HIGH word LOW word
HIGH LOW HIGH LOW byte HIGH LOW HIGH byte LOW byte
byte (1) byte (2) byte (3) (4) byte (5) byte (6) (7) (8)
Bit field Mother Target Parameter no. New value
Add. add.
Bit field control bits for the action

Mother add. group no. and device no. of the device to which the target device is con-
nected. If the target device is directly connected to the CAN network, the
address specification is the same from the target and mother devices.
Target addr. is the group no. and device no. of the device to be edited (35 is e.g.
group 3, device 5)
PARA no. is the parameter number that is to be edited
VALUE is the read or newly set parameter value
Note: The ‚Mother Dev‘ and ‚Target Add.‘ bytes are treated as a word during trans-
mission. If transmitting is in Intel format (ControlNet) these two bytes will be
swapped for transmission.
Status word:
0 Parameter Parameter has been read. (1) depends on
read parameter
1 Parameter Parameter has been written. The required default depends on
written value (receive data record) may have been limited. In parameter
this case the new address of this object deviates from
the default value. (1)
2 Reserved ---
3 Reserved ---
4 Command error is e.g. set if the command bits for reading and writing
were set at the same time in the receive object. (3)
5 WriteProtect Writing parameters is not possible or not permissible
(4)
6 Reserved ---
.. ... ...
13 Reserved ---
75
14 Accept this bit is set if an answer is supplied. (1)

handshake
15 Format checkl format check is activated for this object. The data
sequence '81 02 03 04 05 06 07 08' is transferred to
the above bytes. (2)
(1) If the handshake bit is set and none of the Parameter has been read or Parame-
ter has been written bits are set then an error has occurred. In this case, the re-
maining data are unchanged.
(2) If format control transmission is activated for this object and then taken back
again, the 'Format control data bytes' are retained. Not until a new receive object
'FF hex' is transmitted that triggers the writing of the transmit object are the 'format
control bytes' replaced by new data.
(3) This bit is set if:
- the command bits for reading and writing were set at the same time in the re-
ceive object.
- writing is to be on a parameter in the interface to which it belongs or reading
from a parameter in the interface to which it belongs and the target address is
not available.
- writing is to be on a parameter in the interface to which it belongs or reading is
to be from a parameter in the interface to which it belongs and the parameter
number indicated is bigger than then total number of parameters.
(4) ‘Enable’ is missing for protective parameter 'rec. obj.0xFF key'
A further possibility is if writing is to be on an interface parameter (mother
address). In this case the following is additionally checked:
- whether the 'rec. obj.0xFF key' parameter is set to 0 and the parameter to be
written on is protected
- the parameter value may be changed
Example:
See sections '3.16.1 Function sequence' and '3.16.2 Protected parameter'.
76
5 Viewing the objekt data

Various options were created in the interface for viewing the objects’ data records.
One possibility is viewing via the 'receive data' and 'transmit data' parameter blocks in
the 'object module' (see also sections: 2.5 und 2.6). In these fields the data bytes are
arranged in the sequence in which they are described in the documentation and evalu-
ated by the interface. If the sequence here does not match that of the documentation
(bytes from left to right), then the data have been turned around.
A further possibility is the output of the defined objects and the current data belonging
to them via the RS232 interface. Triggering of the data output is performed via the
'db_level' parameter in the 'object module' (see also section: 0
'db_level' ). Here, data are output byte-by-byte in the sequence in which they were
transmitted to the overall data record.
A terminal or the CANMON program (PC) may be used to display data.
A MODEM cable is to be used as interface cable. For data output only pins 2 and 5 are
needed.
Note: In case of a MODEM cable these pins are connected in the cable without
‘logic crossing’.
Preparation of the CANMON as output device:
First of all a COM window is opened in the CANMON. This is performed via ' Debug-
ger' -> 'open COM window':
After the above window the COM port used must also be selected:
77
A window is then displayed in which the data are output. For this window the RS232-
interface parameters must still be set. This is performed via 'Debugger' -> 'COM set-
tings' or a 'double click' by the mouse on the window. Set the parameters as follows:
Data output:
Outputting may then commence. Triggering is via the 'db_level' parameter. Here, indi-
vidual bits are set that are automatically reset again following output:
Example:
In the following example the 'receive objects' data is output. 2 objects are defined in
the object module:
Output to the COM window is via the 'db_level' parameter 'Rx objects' trigger.
The address offset specifies after how many bytes the corresponding data record be-
gins in relation to the start of the overall data block.
78
The data itself is output byte-by-byte in the sequence it was transmitted by the inter-
face.
See the corresponding illustration in the RSLogix (ControlNet Scanner) below:
If the data are to be in the correct sequence format described in the documentation,
this may be performed in the 'receive data' parameter of the object module:
In the above case the data of the second object are viewed.
5.1 Trace object

With this setting data changes within a receiving and / or transmit object can be re-
corded. There is an output for each change of the data record. The output is made in
the logically correct sequence as shown in the display block for the receive / transmit
data. The object which will be output is determined in parameters 'rec. displ.obj.no.'
and 'tr. displ.obj.no' via the object record number.
Selection 'trace object' with CANMON:
The selection is active until it is reset. In case of a new start of the interface (for exam-
ple Reset) the selection in parameter 'db_level' is automatically backed out.
79
Example:
A receive and a transmit object are to be recorded.
The objects for parameter read and write are each defined under the object record
number 2:
Object record number 2 is entered into the display blocks:
The COM-window of CANMON then shows the following information
In the above example the value of a 'mount position' is set in the interface.
st
1 line: Write in parameter No. 11 of destination address 8.3, mother address 0.5.
The value is 100,0 mm.
nd
2 line: Answer from interface with acknowledgement of takeover bit and of status bit
'parameter written'.
rd
3 line: The takeover bit is backed out by the scanner.
th
4 line: The interface also backs out the takeover bit.
'Rx:' and 'Tx:' indicates whether the data are from the receive object (Rx) or from the
transmit object (Tx). The classification is from the point of view of the interface. The
data are then shown in hexadecimal format, in this case each 8 Byte, and finally there
is a 'timestamp' (brackets).
The output of the 'timestamp' is decimal in ms. It is a time meter which goes from 0 to
65535 and then starts again at 0. The 'timestamp' shows the time of the data output.
The output is done immediately after each processing cycle of the receive and of the
transmit objects.
80
6 Displays
There is a common L.E.D. field for types of interfaces with Hilscher COM – Modules.
This field is on the bottom-most circuit board. Its set-up is as follows:
6.1 CAN address

The CAN address of the module is displayed in H2 and H3.
It can be changed via keys S2 and S3. To do so press both keys simultaneously until
the displays are flashing. Now the group address may be set via key S2 and the device
address via key S3.
6.2 LED’s
Display Signal Color - LED Status Meaning

H4 U1 green ON Supply logic side OK
OFF Supply logic side missing
H5 U2 green ON Supply Profibus side OK
OFF Supply Profibus side missing
H6 DATA green ON Communication OK
OFF No communication
H7 CAN green ON Perfect module start
H8 CAN red ON Error
H9 4 * green These LEDs are not used.
.. --- 2 * red ---
H14
6.2.1 Supply voltage

• U1 supply voltage on ‘logic side’
• U2 supply voltage on 'Profibus side' (separation of potential)
LEDs 'U1' and 'U2' shine immediately after voltage has been applied to the module.
81
6.2.2 Data exchange

• DATA display for Profibus data exchange
If the LED 'DATA' shines, the Profibus module is in the data exchange state (Data Ex-
change). The parameter assignment and the configuration of the DI B000 – firmware
has been accepted as being correct and the module exchanges the user data with the
master (PC, PLC).
6.2.3 Module state LEDs

These LEDs (H7 and H8) correspond to the 2-color LED between the CAN plug-in
connectors. When the module is started it briefly changes to red and then again to
green. These LEDs are independend of the Profibus.
82
7 Connectors
7.1 Profibus
Potential free RS 485 interface acc. to EN 50 170.

Note that there are terminating resistors at both cable ends. If special Profibus plugs
are used, resistances can quite often be activated / deactivated within the plug. For
Baud rates exceeding 1.5Mbaud be sure to use only plugs with additional inductances.
Given the high Baud rates, stubs are not allowed. Cables must have Profibus-DP ap-
proval.
83
The max. length of a bus segment depends on the Baud rate used. Be sure to use only
cables which are explicitly approved for Profibus.
84

7 - Operating Instruction - Digital Interface DI B000, Profibus Interface - BEA - 250859-En-01

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

7 - Operating Instruction - Digital Interface DI B000, Profibus Interface - BEA - 250859-En-01

Caricato da

Copyright:

Formati disponibili

Description I

Digital interface DI B000 en

Interface protocol specification for software

2.8.1 'rec.obj.no. error' parameter 24

1.1 Interface structure

1.2.1 Overview of receive objects

Object no. Obj. length Object function

1.2.2 Overview of transmit objects

Object no. Object Function

2 Parameters and commissioning

2.1 General configuration block

No. Name Value Default Min. Max. Unit Description

5 OwNodeNr 6 6 0 125 Profibus-address

2.1.1 Parameter ‘OwnNodeNr‘

2.1.2 Parameter 'data format'

2.1.3 ‘Baud rate‘ parameter

2.1.4 Parameter error EL_Net intf.

2.2 Configuration block for receive data

No. Name Value Default Min. Max. Unit Description

5 receive obj. list Settings for rec. data

2.2.1 'rec. obj.0xFF key' parameter

2.2.2 'rec. object xx' parameter

The structure of the object codes for the parameter is as follows:

Example: in CAN group 5, position left support beam

2.3 Configuration block for transmit data

No. Name Value Default Min. Max. Unit Description

39 . transmit obj. list Settings for

2.3.1 'form.contr.obj.no.' parameter

2.3.2 'tr. object xx' parameter

The structure of the object code for the parameters is as follows:

Example: read the web width from CAN group 0

2.4 Examples of configuration - DI B000 and SPS

2.4.1 Configuration of the receipt and send objects

Object no. Object Object function Identifier

Object no. Object Function Function

Configuration of the transmit objects of the slave (DI B000):

The compatible hardware configuration of the master (S7-SPS):

Altogether 18 objects have been configured in the slave. Therefore, exactly 18 DP

2.4.3 Defect diagnosis if there are problems with the connection.

1. Refer to the parameter listing of ‘Config-Module’ of DI B000:

2. Check parameters No. 7 (Baud rate):

3. Check parameters No. 9 (error EL_Net intf.):

3.1 The parameter shows value 4 (No Master):

3.2 The parameter shows value 1 (Param. Error):

3.3 The parameter shows value 2 (Config Error):

3.4 The parameter shows value 0 (no Error):

2.5 Display block for receive data

No. Name Value Default Min. Max. Unit Description

105. receive data Data content of a

2.5.1 'rec. displ.obj.no.' parameter

2.5.2 'rec. byte xx' parameter

2.6 Display block for transmit data

No. Name Value Default Min. Max. Unit Description

117. transmit data Data content of a

2.6.1 'tr. displ.obj.no.' parameter

2.6.2 'tr. byte xx' parameter

2.7 Parameter block for 'mount positions'

The receive objects concerned are:

No. Name Value Default Min. Max. Unit Description

5. mount positions Mount offsets

‘send mount pos’ parameter structure:

2.8 Parameter blocks with commissioning supports

No. Name Value Default Min. Max. Unit Description