SICK WebChecker MLG-2 Manual

TECHNICAL INFORMATION
MLG-2
SICK Smart Sensors / IO-Link
Device configuration – Advanced operating instructions

Product described
IO Link – MLG2
Manufacturer
SICK AG
Erwin-Sick-Str. 1
79183 Waldkirch
Germany
Legal information
This work is protected by copyright. Any rights derived from the copyright shall be reserved for SICK AG. Reproduc‐
tion of this document or parts of this document is only permissible within the limits of the legal determination of
Copyright Law. Any modification, abridgment or translation of this document is prohibited without the express writ‐
ten permission of SICK AG.
The trademarks stated in this document are the property of their respective owner.
© SICK AG. All rights reserved.
Original document
This document is an original document of SICK AG.
2T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

Contents
1 About this document........................................................................ 5
1.1 Purpose of this document........................................................................ 5
1.2 Intended use............................................................................................. 5
1.3 Symbols..................................................................................................... 5
2 Description of IO-Link....................................................................... 6
3 Accessories for visualization, configuration, and integration..... 7
4 Data repository.................................................................................. 8
5 Physical layer..................................................................................... 9
6 Process data...................................................................................... 10
6.1 PD in.......................................................................................................... 10
6.1.1 System and Q status + run length code (RLC)....................... 10
6.1.2 System and Q status + beam status...................................... 10
6.1.3 User-defined process data content........................................ 10
6.1.4 System status and output status............................................ 11
6.2 PD out........................................................................................................ 11
7 Service data....................................................................................... 12
7.1 Device identification................................................................................. 12
7.1.1 Product name and manufacturer name................................. 12
7.1.2 Product text and serial number.............................................. 12
7.1.3 Definable names..................................................................... 12
7.1.4 Hardware and firmware version.............................................. 13
7.1.5 Find me..................................................................................... 13
7.2 Teach-in / detection settings for MLG-2 devices.................................... 13
7.2.1 Teach-in and beam blanking via teach-in............................... 13
7.2.2 Beam blanking mask............................................................... 14
7.2.3 Definition of zones................................................................... 15
7.3 Performance options................................................................................ 15
7.4 Process data setting................................................................................. 17
7.5 Beam hold functions................................................................................ 19
7.6 Configuring outputs Q1 – Q4................................................................... 21
7.7 System settings......................................................................................... 22
7.8 Installation / Diagnostics......................................................................... 23
7.8.1 Process quality and teach quality........................................... 23
7.8.2 Device alignment..................................................................... 23
7.8.3 Device properties..................................................................... 24
7.8.4 Diagnostics............................................................................... 24
8 Events.................................................................................................. 25
CONTENTS
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 3
Subject to change without notice

9 Use cases............................................................................................ 26
10 List of abbreviations.......................................................................... 30
11 Index.................................................................................................... 31
CONTENTS
4T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

1 About this document
1.1 Purpose of this document
The ISDU descriptions in this document apply to IO-Link-enabled photoelectric sensors (Smart Sensors) with the
following principle of operation: MLG-2.
In some cases, functions may be described in this document which are not supported by individual sensors. The
functions in question are marked accordingly (see "Symbols", page 5).
The specific functional scope of an individual sensor is described in full in the Supplement to operating instructions on
the relevant product page under www.sick.com.
1.2 Intended use
Use IO-Link only as described in this documentation.
1.3 Symbols
NOTICE
This symbol indicates important information.
NOTE
This symbol provides additional information, e.g., dependencies / interactions between the described function and
other functions, or when individual functions are not supported by every sensor.
ABOUT THIS DOCUMENT 1
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 5
Subject to change without notice

2 Description of IO-Link
IO-Link and control integration
IO-Link is a non-proprietary internationally standardized communication technology, which makes it possible to
communicate with sensors and actuators in industrial environments (IEC 61131-9).
IO-Link devices communicate with higher-level control systems via an IO-Link master. The IO-Link devices (slaves)
are connected to these via a point-to-point connection.
Different variants of IO-Link master are available. In most cases, they are remote fieldbus gateways or input cards
for the backplane bus of the control used.
To make it possible for an IO-Link sensor to communicate with the control, both the IO-Link master and the
IO-Link sensor must be integrated in the hardware configuration in the control manufacturer’s Engineering Tool.
To simplify the integration process, SICK provides sensor-specific device description files (IODD = IO-Link Device
Description) for IO-Link devices.
You can download these device description files free of charge: www.sick.com/[device-part number].
Not all control system manufacturers support the use of IODDs. If third-party IO-Link masters are used, it is possi‐
ble to integrate the IO-Link sensor by manually entering the relevant sensor parameters directly during the hard‐
ware configuration.
To ensure that the IO-Link sensor can be easily integrated into the control program, SICK also provides function
blocks for many control systems. These function blocks make it easier to read and write the individual
sensor parameters, for example, and provide support when it comes to interpreting the process data supplied by
the IO-Link sensor. You can also download them free of charge from the homepage: www.sick.com/[device-part
number].
On SICK’s YouTube channel, you can find some tutorials, which will help you to integrate SICK IO-Link masters:
www.youtube.com/SICKSensors.
If you have any questions, SICK’s Technical Support is available to help all over the world.
2 DESCRIPTION OF IO-LINK
6T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

3 Accessories for visualization, configuration, and integration
Using the , you can easily connect IO-Link sensors from SICK to a PC or a laptop via USB. You can then quickly and
easily test or configure the connected sensors using the SOPAS ET program (SICK Engineering Tool with graphic
user navigation and convenient visualization).
The corresponding visualization files (SDD = SOPAS Device Description) are available for many devices so that you
can operate the IO-Link sensors using SOPAS ET.
You can download SOPAS ET and the device-specific SDDs directly and free of charge from the SICK homepage:
www.sick.com.
Various IO-Link masters are available from SICK for integrating IO-Link masters using fieldbus. For more details,
see: www.sick.com.
ACCESSORIES FOR VISUALIZATION, CONFIGURATION, AND INTEGRATION 3
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 7
Subject to change without notice

4 Data repository
When the current IO-Link standard V1.1 was introduced, the automatic data repository (Data Storage) was added
to IO-Link’s range of functions. The data repository allows the machine operator to replace defective IO-Link
devices with corresponding replacement devices without having to reconfigure these manually.
When the data repository is activated, the IO-Link 1.1 master always saves the last valid setting parameters of all
connected IO-Link 1.1 devices in its local memory. If you replace one of the connected IO-Link devices with
another device which is compatible with the function, the IO-Link master will transfer the last valid parameter set
of the previous sensor to the new sensor automatically.
The data repository therefore means that devices can be replaced in a plug-and-play manner within a matter of
seconds – without complex reconfiguration, special hardware or software tools, and specific specialist knowledge.
NOTE
•To use the data repository, you must activate it in the IO-Link master.
•When the conversion of one or several sensor parameters is initiated via the control, then the control must
activate the Data Storage Upload Request-Flag as the final command in the sensor. Only this initiates the data
repository.
•Uploading / downloading sensor parameters using the data repository function can take between a few hun‐
dred milliseconds and three seconds depending on the volume of data and the IO-Link master used (typical
values; values can differ in practice).
•For details on using the data repository, see IO-Link Interface and System Specification, V1.1.2, chapter 10.4
Data Storage (DS) at www.io-link.com, Downloads menu item.
4 DATA REPOSITORY
8T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

5 Physical layer
The physical layer describes the basic IO-Link device data (see table below). The device data is automatically
shared with the IO-Link master. It is important to ensure that the used IO-Link master supports this performance
data.
NOTICE
The maximum current consumption of the IO-Link sensor (including load at the outputs) must not exceed the per‐
missible output current of the relevant port on the IO-Link master.
Table 1: Physical layer – IO-Link device data
SIO mode Yes
Min. cycle time 3 ms
Baud rate COM 3 (230.4 kbit/s)
Process data length PD in (from device to master) 32 bytes
Process data length PD out (from master to device) 1 byte
IODD version V1.0.1
Supported IO-Link version IO-Link V1.1
PHYSICAL LAYER 5
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 9
Subject to change without notice

6 Process data
Process data is transmitted cyclically. There is no confirmation of receipt.
The master determines the cycle time; however, this must not be less than the minimum cycle time of the sensor
(see table 1, page 9).
Note: The service data (acyclic data) does not influence the cycle time.
There is PD-in and PD-out data:
•PD in
Data from the IO-Link sensor to the IO-Link master – the current status of the sensor is displayed as quickly
as possible (incoming process data).
•PD out
Commands from the IO-Link master to the IO-Link sensor – for the quickest possible transmission of system
commands (outgoing process data).
6.1 PD in
The PD-in process data, which is transmitted cyclically from the MLG-2 to the IO-Link master, can be configured
depending on the application. 3 different types of data content can be selected using ISDU 120.
6.1.1 System and Q status + run length code (RLC)
Table 2: Process data selection, can be set using ISDU 120; value 0
System and Q status + run length code (RLC)
Byte
Off‐
set
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
RLC 15 RLC 14 RLC 13 RLC 12 RLC 11 RLC 10 RLC 9 RLC 8 RLC 7 RLC 6 RLC 5 RLC 4 RLC 3 RLC 2 RLC 1 SS
1
AS
2
1SS = system status (description: see table 5)
2AS = output status (description: see table 5)
6.1.2 System and Q status + beam status
Process data selection, can be set using ISDU 120; value 1
Table 3: Process data selection, can be set using ISDU 120; value 1
System and Q status + beam status
Byte
off‐
set
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
beam
225 ...
240
beam
209 ...
224
beam
193 ...
208
beam
177
192
beam
161 ...
176
beam
145 ...
160
beam
129 ...
144
beam
113 ...
128
beam
97 ...
112
beam
81 ...
96
beam
65 ...
80
beam
49 ...
64
beam
33 ...
48
beam
17 ...
32
beam
1 ...
16
SS
1
AS
2
1SS = system status (description: see table 5)
2AS = output status (description: see table 5)
6.1.3 User-defined process data content
Process data selection, can be set using ISDU 120; value 2
Table 4: Process data selection, can be set using ISDU 120; value 2
User-defined process data
Byte
off‐
set
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
6 PROCESS DATA
10 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

User-defined process data
pre‐
set‐
ting
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion
no func‐
tion IDI ODI FBB LBB NBB SS
1
AS
2
1SS = system status (description: see table 5)
2AS = output status (description: see table 5)
6.1.4 System status and output status
Table 5: Description of system status and output status
System status (HIGH byte) Output status (LOW byte) 1
Bit
offset 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Sync
error
Teach
fail
Hard‐
ware
error
Contami‐
nation
alarm
Teach
active
Over-
tempera‐
ture
Process
data
invalid
Q
short-cir‐
cuit
not used not used not used not used Q4 Q3 Q2 Q1
0 = False, 1 = True 0 = OFF, 1 = ON
1Q1 ... Q4 outputs can be configured using ISDU 183 ... 186
6.2 PD out
Using the PD-out process data, control commands can be sent cyclically from the IO-Link master to the MLG-2.
Outgoing process data, control byte
Bit
offset 7 6 5 4 3 2 1 0
Test Teach-in BBH Reserved STANDBY Reserved
TEST Switch off all sender LEDs.
Used to force a reaction from the receiver and therefore test for correct functionality.
Teach-in Used primarily to set the transmitting power and switching threshold for all light beams to the cur‐
rent installation situation / sensing range. Same functionality as for service data -see "PD out",
page 11.
BBH Block beams hold: All blocked beams are held.
This function is only effective if the BBH function has been activated via the service data - see
"Beam hold functions", page 19.
STANDBY Switches the MLG-2 into the energy-saving sleep mode. Same as ISDU 75 - see "Performance
options", page 15.
PROCESS DATA 6
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 11
Subject to change without notice

7 Service data
Service data is only exchanged between the control and IO-Link sensor via the IO-Link master on request by the
control (acyclically). The service data is designated as ISDUs. Using an ISDU, you can change the configuration or
read out information about the status of the sensor.
The respective counterpart confirms receipt of the data.
If the sensor does not answer within five seconds, the master reports a communication error.
7.1 Device identification
7.1.1 Product name and manufacturer name
Table 6: Device identification
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
16 10
-
Vendor name
String
- 32 bytes
ro 1)
SICK AG
18 12 Product name - 18 bytes MLGXXA-
XXXXXXXXX
219 DB
1 Product ID system
Record
- 7 bytes 1xxxxxx Order no. System, consisting of system &
receiver
2 Product ID receiver - 7 bytes 2xxxxxx Order no. Receiver
1) ro = Read only
rw = Read/write
wo = Write only
The Product ID is also the part number of the connected IO-Link device.
To make it possible to provide a family IODD for a device family, the Product ID can be found under Device identifica‐
tion (ISDU 219) for SICK IO-Link devices.
Furthermore, the part numbers for the components associated with the system are filed in sub-index 2…x for sen‐
sors (e.g., a light grid).
7.1.2 Product text and serial number
Table 7: Device identification – Product text / serial number
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
20 14
-
Product text
String -
64 bytes
ro
MLG-2 Pro
21 15 Serial number 8 bytes
Format of the serial number:
YYWWnnnn (Y = year, W = week, n = sequential numbering)
7.1.3 Definable names
Table 8: Device identification – Specific tag / name
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
24 18 - Application-specific tag
String
yes
32 bytes rw
64 40 - Device-specific name no
In Application-specific tag, you can write any text with a maximum of 32 characters. This can be useful for describing
the exact position or task of the sensor in the overall machine. The Application-specific tag is saved via the Data repos‐
itory.
In Device-specific name, you can also write any text with a maximum of 32 characters. This name is NOT saved via
the Data repository and is therefore available for information which is valid temporarily or for information which is
only applicable to this sensor.
7 SERVICE DATA
12 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

7.1.4 Hardware and firmware version
Table 9: Device identification – Version
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
22 16
-
Hardware version
String -
4 bytes
ro
xxxx
23 17 Firmware version 12 bytes Vxxx.xxx.xxx
This ISDU indicates the hardware and software versions.
7.1.5 Find me
Table 10: Device identification – Find me
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
204 CC - Find me UInt no 8 bits rw 0 0 = Find me deactivated
1 = Find me activated
The sensor can be uniquely identified using Find me. For machines with several identical sensors, it is therefore
possible to uniquely identify the device with which communication is currently taking place.
When Find me is activated, the yellow indicator LED of the sensor flashes at 1 Hz.
To identify the switching output (pin 2) in the control cabinet, you can also activate or deactivate the digital output
at pin 2 by writing the value 16.
NOTICE
Observe the effect of the output activation and deactivation on the connected system.
7.2 Teach-in / detection settings for MLG-2 devices
7.2.1 Teach-in and beam blanking via teach-in
Table 11: Teach-in / detection – Teach-in
ISDU
Name Data
type
Data
reposi‐
tory
Length Acc-
ess
Default
value Value/rangeIndex Sub-
index
DEC HEX
2 02
-
System
command
UInt
-
8 bits
wo 160 = Teach-in
98 62 Teach
result ro
0
Bit no.
76543210
AutoTeach
not possi‐
ble
Teach-in
failure,
beam
blanking
High-
speed
mode not
possible
Teach-in
failure,
cross-
beam
mode
Warning,
beam sig‐
nal over‐
drive
Teach-in
failure,
low beam
signal
Teach-in
failure,
parallel
beam
mode
Teach-in
failure,
general
0 = False
1 = True
70 46
Blanking
teach
enable
yes
rw 0 = Blanking teach inactive
1 = Blanking teach active
188 BC
Blank all
currently
blocked
beams
-
wo 1 = Execute
189 BD
Blank all
currently
made
beams
wo 1 = Execute
SERVICE DATA 7
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 13
Subject to change without notice

2 Setting the command value 160 triggers a teach-in.
As a result, the relevant switching thresholds are assigned to all light
beams and with senders, the appropriate transmitting power for the sens‐
ing range is set.
For a successful teach-in, the light path for all light beams must be free
(exception: Blank teach-in active).
For further options, see ISDU 70.
98 For diagnostic purposes, it is possible to read out whether the teach-in
was successful in this ISDU.
In addition, the bits indicate the causes of a possible error during the
teach-in.
70 This ISDU specifies whether blocked light beams are blanked by the light
grid during teach-in via the system command with value 160 (see above).
This is then useful, for example, when machine parts permanently project
into the detection zone.
Note:
When this function is active, teach-in errors can no longer be signaled. If,
for example, a detection object has been unintentionally left in the beam
path during a teach-in, all light beams blocked by this are blanked without
warning as a result.
188 With this ISDU, the currently blocked beams can be blanked immediately;
the set switching thresholds remain unchanged.
Unlike the Blank teach-in option, this happens directly – without a teach-in
system command – and just once in ISDU 70.
189 With this ISDU, the currently free beams can be blanked immediately; the
set switching thresholds remain unchanged.
Unlike the Blank teach-in option, this happens directly – without a teach-in
system command – and just once in ISDU 70.
7.2.2 Beam blanking mask
Table 12: Teach-in / detection – Beam blanking mask
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
72 48 -
Beam blanking mask 1) Record yes 64 bytes rw
Beam 1 … 32
Offset -
480 bits FFFFFFFF
0 = Beam inactive
1 = Beam active
Beam 33 ... 64 448 bits FFFFFFFF
Beam 65 ... 96 416 bits FFFFFFFF
Beam 97 ... 128 384 bits FFFFFFFF
Beam 129 ... 160 352 bits FFFFFFFF
Beam 161 ... 192 320 bits FFFFFFFF
Beam 193 ... 224 288 bits FFFFFFFF
Beam 225 ... 256 256 bits FFFFFFFF
Beam 257 ... 288 224 bits FFFFFFFF
Beam 289 ... 320 192 bits FFFFFFFF
Beam 321 ... 352 160 bits FFFFFFFF
Beam 353 ... 384 128 bits FFFFFFFF
Beam 385 ... 416 96 bits FFFFFFFF
Beam 417 ... 448 64 bits FFFFFFFF
Beam 449 ... 480 32 bits FFFFFFFF
Beam 481 ... 512 0 bits FFFFFFFF
1) Freely adjustable bit mask for blanking light beams
Using the beam blanking mask, you can manually blank any light beams (without teach-in).
This is done using binary-coded beam masks.
The beam mask contains a unique 64-byte string 0xFF FF FF FF ... by default, i.e., all light beams are active.
The actual number of beams of the MLG-2 must be observed.
7 SERVICE DATA
14 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

7.2.3 Definition of zones
Table 13: Teach-in / detection – Definition of zones
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
207 0CF Zone 1 Record
yes
32 bits
rw
1Lower limit
16 bits 1
1 … 510 = Lower limit zone 1
2 Upper limit 1 … 510 = Upper limit zone 1
208 0D0 Zone 2 Record 32 bits
1 Lower limit
16 bits 1
1 … 510 = Lower limit zone 2
2 Upper limit 1 … 510 = Upper limit zone 2
209 0D1 Zone 3 Record 32 bits
1 Lower limit
16 bits 1
1 … 510 = Lower limit zone 3
2 Upper limit 1 … 510 = Upper limit zone 3
210 0D2 Zone 4 Record 32 bits
1 Lower limit
16 bits 1
1 … 510 = Lower limit zone 4
2 Upper limit 1 … 510 = Upper limit zone 4
207 – 210 These ISDUs allow you to define 4 zones within the MLG-2.
Every zone can be individually assigned with beam functions (see ISDU 67).
For each zone, the upper and lower limit must be specified in beam numbers.
7.3 Performance options
Table 14: Performance options
ISDU
Name Data type Data reposi‐
tory Length Access Default value Value/rangeIndex Sub-
index
DEC HEX
65 41
-
Device mode
UInt yes
8 bits
rw
0
0 = Standard mode
1 = Transparent mode
2 = Sunlight-resistant mode
66 42 Performance options
0 = Standard resolution
1 = High resolution
2 = High operating reserve
3 = Cross-beam mode
4 = Cross-beam mode with high operating
reserve
5 = High-speed scan
6 = High-speed scan with high resolution
7 = High-speed scan with high operating
reserve
68 44 Transparent mode
0 = Attenuation 30%
1 = Attenuation 15%
2 = Attenuation 10%
75 4B Standby 0 0 = Standby inactive
1 = Standby active
206 CE Cross-beam measuring 1 bit False False = Cross-beam measuring inactive
True = Cross-beam measuring active
SERVICE DATA 7
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 15
Subject to change without notice

65 MLG-2 operating mode selection:
Standard mode Reliable operating mode with normal operating reserve.
Suitable for most applications.
Transparent mode Suitable for detecting transparent objects. The required minimum attenuation
of the object to be recorded can be set via ISDU 68.
In Transparent mode, process quality (ISDU 225) is not available.
Transparent mode is only available together with Standard measurement accuracy
(ISDU 66, value 0).
Sunlight-resistant mode Operating mode to prevent faults due to sunlight shining directly into the
receiver.
Dust and sunlight-resistant operating mode reduces the maximum sensing
range.
– To 1.2 m for devices with a 2 m operating range
– To 3 m for devices with a 5 m operating range
– To 5 m for devices with an 8.5 m operating range
This operating mode can only be configured on an MLG-2 with fewer than 240
beams.
66 It is possible to choose between different beam analysis methods for the “Normal” and “Sunlight-resis‐
tant” operating modes via the performance options:
Standard measurement accu‐
racy
Reliable operating mode.
Requires 3/4 beam coverage to detect a beam as blocked.
High measurement accuracy For applications in a clean environment.
Process quality not available.
Requires 1/2 beam coverage to detect a beam as blocked.
High operating reserve Maximum transmitting power.
For applications in a dirty environment or for applications in which semi-trans‐
parent films (with short sensing range) need to be penetrated.
Requires full beam coverage to detect a beam as blocked.
Cross-beam mode The cross-beam function increases the measurement accuracy and enables
the detection of smaller objects.
A sender LED projects beams to several receiver diodes. For further details,
see operating instructions, chapter 3.6.3.
High-speed scan The High-speed scan reduces the scan time by a variable factor.
Several light beams are active in each cycle. Operating mode is only effective
after teach-in via system command or teach key.
For further details, see operating instructions, chapter 3.5.3.
68 Selection of the suitable setting for objects with different transparency.
Only effective in conjunction with the “Transparent” operating mode.
The object to be detected must dim the infrared light of the MLG-2 by at least the specified percentage in
order to be detected.
In addition, observe the dependency of the minimum attenuation via the sensing range. See operating
instructions, chapter 13.2.5.
75 Standby mode is suitable for longer operating breaks.
The MLG-2 is in the energy-saving sleep mode here.
No measurements are possible in this mode.
Alternatively, Standby mode can also be controlled via an external input.
206 Only effective in the middle position between the sender and receiver. Cross-beam measuring is suitable
for measurement functions, such as height measurement.
With this function, a group of crossed beams is combined into a single virtual beam. The real and virtual
beams are renumbered and, as a result, the number of beams is nearly doubled.
This function is only effective if Cross-beam mode is active (see ISDU 66).
The response time of the MLG-2 doubles.
7 SERVICE DATA
16 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

7.4 Process data setting
In the following section, the process data, which is required for the application and is described under chapter 6.1,
can be set.
Table 15: Process data
ISDU
Name Data
type
Data
repo
sitor
y
Length Acce
ss
Defa
ult
valu
e
Value/range
Index Sub-
inde
x
DEC HEX
120 78
-
Process data select UInt
yes
8 bits
rw
0
0 = System status, Q status, and run length code
1 = System status, Q status, and beam status (for value 1 max. no. of beams = 240)
2 = User-defined process data
67 43 Process data user def‐
inition Record 16 byt es
User-defined output
function 1
Offset
120 bi
ts 20 0 = No function
1 = RLC 1 – 1st value of the run length code
2 = RLC 2 – 2nd value of the run length code
3 = RLC 3 – 3rd value of the run length code
4 = RLC 4 – 4th value of the run length code
5 = RLC 5 – 5th value of the run length code
6 = RLC 6 – 6th value of the run length code
7 = RLC 7 – 7th value of the run length code
8 = RLC 8 – 8th value of the run length code
9 = RLC 9 – 9th value of the run length code
10 = RLC 10 – 10th value of the run length code
11 = RLC 11 – 11th value of the run length code
12 = RLC 12 – 12th value of the run length code
13 = RLC 13 – 13th value of the run length code
14 = RLC 14 – 14th value of the run length code
15 = RLC 15 – 15th value of the run length code
16 = RLC 16 – 16th value of the run length code
17 = System status (high byte) and Q status (low
byte)
18 = Number of beams blocked
19 = Number of beams made
20 = First beam blocked
21 = First beam made
22 = Last beam blocked
23 = Last beam made
24 = Number of consecutive beams blocked
25 = Number of consecutive beams made
26 = Central beam blocked
27 = Central beam made
28 = Outside dimension
29 = Inside dimension
30 = Virtual outputs (VQs)
31 = Teach quality
32 = Process quality
33 = Data update counter
Selection of beam functions, zone 1
34 = NBB Z1 – Number of beams blocked,
zone 1
35 = FBB Z1 – First beam blocked, zone 1
36 = LBB Z1 – Last beam blocked, zone 1
37 = NCBB Z1 – Number of consecutive
beams blocked, zone 1
38 = CBB Z1 – Central beam blocked, zone 1
Selection of beam functions, zone 2
39 = NBB Z2 – Number of beams blocked,
zone 2
40 = FBB Z2 – First beam blocked, zone 2
41 = LBB Z2 – Last beam blocked, zone 2
42 = NCBB Z2 – Number of consecutive
beams blocked, zone 2
43 = CBB Z2 – Central beam blocked, zone 2
Selection of beam functions, zone 3
44 = NBB Z3 – Number of beams blocked,
zone 3
45 = FBB Z3 – First beam blocked, zone 3
46 = LBB Z3 – Last beam blocked, zone 3
47 = NCBB Z3 – Number of consecutive
beams blocked, zone 3
48 = CBB Z3 – Central beam blocked, zone 3
Selection of beam functions, zone 4
49 = NBB Z4 – Number of beams blocked,
zone 4
50 = FBB Z4 – First beam blocked, zone 4
51 = LBB Z4 – Last beam blocked, zone 4
52 = NCBB Z4 – Number of consecutive
beams blocked, zone 4
53 = CBB Z4 – Central beam blocked, zone 4
User-defined output
function 2
112 bi
ts 18
User-defined output
function 3
104 bi
ts 22
User-defined output
function 4 96 bits 20
User-defined output
function 5 88 bits 28
User-defined output
function 6 80 bits 29
User-defined output
function 7 72 bits 0
User-defined output
function 8 64 bits 0
User-defined output
function 9 56 bits 0
User-defined output
function 10 48 bits 0
User-defined output
function 11 40 bits 0
User-defined output
function 12 32 bits 0
User-defined output
function 13 24 bits 0
User-defined output
function 14 16 bits 0
User-defined output
function 15 8 bits 0
User-defined output
function 16 0 bits 0
SERVICE DATA 7
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 17
Subject to change without notice

120 The 32-byte process data of the MLG-2 can be assigned different functions in
accordance with the application.
You can choose between fixed pre-assignment (value 0 or 1) or individual selec‐
tion (see ISDU 67).
Value 0 System status, Q status and Run length code:
Pre-assignment with RLC for flexible applications.
For further details, see operating instructions, chapter 3.9.1.
Example: see "Use cases", page 26.
Value 1 System status, Q status and Beam status:
Binary-coded output of the beam status:
0 = Beam made
1 = Beam blocked
This function is limited to 240 beams.
Value 3 Freely defined process data:
Individual selection from all available functions.
You must make the selection using ISDU 67.
67 The content of the freely definable process data is determined using this ISDU.
Each selectable function is 2 bytes in size.
16 different functions can be mapped on the process data via sub-index 1 ... 16.
7 SERVICE DATA
18 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice

7.5 Beam hold functions
Table 16: Beam functions
ISDU
Name Data
type
Data
repo
sitor
y
Length Acce
ss
Default
value Value/range MeaningIndex Sub-
index
DEC HEX
272 110
-
Selection for beams hold mode UInt
yes
8 bits
rw
0
0 = None
1 = Blocked beams hold BBH
2 = Lost beams hold LBH
Selection for 2 different beam hold func‐
tions BBH = trigger via control byte (PD
out)
256 100 Beam hold function – NBB
Bool 1 bit False False = Inactive
True = Active
Activation for NBB = Number of beams
blocked
257 101 Beam hold function – NBM Activation for NBM = Number of beams
made
258 102 Beam hold function – FBB Activation for FBB = First beams blocked
259 103 Beam hold function – FBM Activation for FBM = First beams made
260 104 Beam hold function – LBB Activation for LBB = Last beams blocked
261 105 Beam hold function – LBM Activation for LBM = Last beams made
262 106 Beam hold function – NCBB & CBB
Activation for NCBB & CBB = Number of
consecutive beams blocked & central
beams blocked
263 107 Beam hold function – NCBM &
CBM
Activation for NCBM & CBM = Number of
consecutive beams made & central
beams made
264 108 Beam hold function – ODI Activation for ODI = Outside dimension
265 109 Beam hold function – IDI Activation for IDI = Inside dimension
266 10A Beam hold function – RLC Activation for RLC = Run length code
267 10B Beam hold function – BS Activation for BS = Beam status
268 10C Beam hold selection for zone –
NBB Record 8 bits Number of beams blocked for zones
1 Beam hold function zone 1 – NBB
1 bit False False = Inactive
True = Active
Activation for zone 1
2 Beam hold function zone 2 – NBB Activation for zone 2
3 Beam hold function zone 3 – NBB Activation for zone 3
4 Beam hold function zone 4 – NBB Activation for zone 4
269 10D Beam hold selection for zone – FBB Record 8 bits First beam blocked for zones
1 Beam hold function zone 1 – FBB
1 bit False False = Inactive
True = Active
Activation for zone 1
2 Beam hold function zone 2 – FBB Activation for zone 2
3 Beam hold function zone 3 – FBB Activation for zone 3
4 Beam hold function zone 4 – FBB Activation for zone 4
270 10E Beam hold selection for zone – LBB Record 8 bits Last beam blocked for zones
1 Beam hold function zone 1 – LBB
1 bit False False = Inactive
True = Active
Activation for zone 1
2 Beam hold function zone 2 – LBB Activation for zone 2
3 Beam hold function zone 3 – LBB Activation for zone 3
4 Beam hold function zone 4 – LBB Activation for zone 4
271 10F Beam hold selection for zone –
NCBB/CBB Record 8 bits Number of consecutive beams blocked and central beam blocked for zones
1Beam hold function zone 1 –
NCBB/CBB
1 bit False False = Inactive
True = Active
Activation for zone 1
2Beam hold function zone 2 –
NCBB/CBB
Activation for zone 2
3Beam hold function zone 3 –
NCBB/CBB
Activation for zone 3
4Beam hold function zone 4 –
NCBB/CBB
Activation for zone 4
SERVICE DATA 7
8022573/2018-01-19 | SICK T E C H N I C A L I N F O R M A T I O N | MLG-2 19
Subject to change without notice

272 The MLG-2 can save the state of blocked beams. The following two hold func‐
tions can be selected:
BBH BBH (Blocked beams hold) can be used to measure the height of items
which pass through the light grid, for example.
For this, BBH is started before the detection item enters (via input or
PD out).
Once the detection item has passed through, the corresponding func‐
tion (for height measurement, e.g., LBB) is read out and BBH is deacti‐
vated again.
All blocked beams are held.
This function can be started and ended in 2 ways.
•Either via an external input – assigned with BBH function
•Or via the PD-out control byte by setting / resetting bit 5 (see PD
out).
The functions, on which BBH is to work, must be defined in ISDUs 256
to 267.
Furthermore, you can specify the zones (see Definition of zones) for
which BBH is to work (ISDUs 268 to 271).
For further details, see operating instructions, chapter 7.11.1.
LBH The LBH (Lost beams hold) function works by holding the last beam
when an object leaves the last / the only remaining active light beam.
As a result, the last blocked beam is always marked as blocked until a
new beam is blocked.
Unlike BBH, the LBH function is effective globally on all beam func‐
tions. Example: see "Use cases", page 26.
256 –
267
Selection of the beam function on which the BBH function is to work.
268 –
271
Selection of the zones on which the BBH function is to work.
7 SERVICE DATA
20 T E C H N I C A L I N F O R M A T I O N | MLG-2 8022573/2018-01-19 | SICK
Subject to change without notice