SICK microScan3 - PROFINET Manual

TECHNICAL INFORMATION
microScan3 - PROFINET
Safety laser scanner
TIA Portal

Described product
microScan3 - PROFINET
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. Reproduction of this document or parts of this document is
only permissible within the limits of the legal determination of Copyright Law. Any modi‐
fication, abridgment or translation of this document is prohibited without the express
written 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 | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

Contents
1 About this document........................................................................ 4
1.1 Purpose of this document........................................................................ 4
1.2 Scope......................................................................................................... 4
1.3 Target groups............................................................................................ 4
1.4 Symbols and document conventions...................................................... 4
2 Integration.......................................................................................... 6
2.1 Preparing for the integration.................................................................... 6
2.2 Installing microScan3 - PROFINET GSDML............................................. 6
2.3 Integrating the safety laser scanner........................................................ 7
3 Overview of the PROFIsafe parameters......................................... 11
4 Overview of the process images..................................................... 12
5 Notes on implementing the process images................................ 16
6 Troubleshooting................................................................................. 18
CONTENTS
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 3
Subject to change without notice

1 About this document
1.1 Purpose of this document
This integration example guides you step by step through the process of integrating a
safety laser scanner of type microScan3 – PROFINET (all variants) into a Siemens TIA
Portal project.
Depending on the application, it is possible that this example may not suit your specific
application case. The experts at SICK can, on request, assist you with the integration.
SICK cannot guarantee that the following integration example will be error-free when
implemented, e.g., due to future changes to SIMATIC Manager STEP 7. SICK assumes
no liability for any damage that may result from the use of this integration example.
This example was created using version V14 + SP1 of TIA Portal. The descriptions in
this document may therefore vary for future versions of the software.
1.2 Scope
Product
This document applies to the following products:
•Product designation: microScan3 - PROFINET
Document identification
Document part number:
•This document has the following part number: 8026545
•All available language versions of this document are available under the following
part number: 8026531
You can find the current version of all documents at www.sick.com.
1.3 Target groups
This document is intended for system integrators who want to integrate the safety laser
scanner into their application.
1.4 Symbols and document conventions
The following symbols and conventions are used in this document:
Safety notes and other notes
DANGER
Indicates a situation presenting imminent danger, which will lead to death or serious
injuries if not prevented.
WARNING
Indicates a situation presenting possible danger, which may lead to death or serious
injuries if not prevented.
CAUTION
Indicates a situation presenting possible danger, which may lead to moderate or minor
injuries if not prevented.
1 ABOUT THIS DOCUMENT
4T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

NOTICE
Indicates a situation presenting possible danger, which may lead to property damage if
not prevented.
NOTE
Indicates useful tips and recommendations.
Instructions to action
bThe arrow denotes instructions to action.
1. The sequence of instructions for action is numbered.
2. Follow the order in which the numbered instructions are given.
✓The check mark denotes the result of an instruction.
ABOUT THIS DOCUMENT 1
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 5
Subject to change without notice

2 Integration
2.1 Preparing for the integration
Approach
1. Update Safety Designer and TIA Portal to the latest release (version and, if applica‐
ble, hotfix).
2. Configure the safety laser scanner using Safety Designer. Some parameters can
only be specified via Safety Designer.
2.2 Installing microScan3 - PROFINET GSDML
Overview
The GSDML file contains the device description of the safety laser scanner for the
controller. It only needs to be installed once.
Important information
NOTE
Always install the latest GSDML file in the controller.
Approach
1. The current GSDML file for integrating the safety laser scanner into the controller
can be downloaded at www.sick.com.
2. In TIA Portal: Options > Manage general station description files
3. Select the folder containing the GSDML file.
4. Select the GSDML file checkbox and click on Install.
2 INTEGRATION
6T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

✓
2.3 Integrating the safety laser scanner
Approach
1. In the Network view tab: Double-click on microScan3. Alternatively, use drag and drop
to drag microscan3 into the working range. You will find microScan3 under Other field
devices > PROFINET IO > Sensors > SICK AG.
2. Right-click on Not assigned and select Assign to new IO controller.
INTEGRATION 2
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 7
Subject to change without notice

3. Select a suitable IO controller and click OK to confirm.
4. In the Network view tab, double-click on microScan3.
5. Properties > General > Ethernet addresses
6. Enter the IP address and Converted name (=PROFINET device name). The entered
values must match the values configured in Safety Designer.
7. Expand the Device overview and Hardware catalog and select a suitable module.
see "Overview of the process images", page 12
8. If applicable, right-click on the standard module (highlighted in yellow) and select
Delete to remove it.
2 INTEGRATION
8T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

9. To add a new module, double-click on the desired module in the Catalog. Alterna‐
tively, use drag and drop to drag the desired module into Device overview.
10. Click on the module (e.g., mS3 6Byte In/Out…)
11. Properties > General > PROFIsafe
12. Enter the F_Dest_Add and, if applicable, F_iPar_CRC F_WD_Time. The entered values
must match the values configured in Safety Designer.
13. If applicable, enter the f_WD_Time.
see "Overview of the PROFIsafe parameters", page 11
INTEGRATION 2
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 9
Subject to change without notice

14. Properties > General > I/O addresses
15. Enter the Start address. The value is generated automatically in TIA Portal but can
be modified if necessary.
✓The safety laser scanner has been successfully integrated into the hardware con‐
figuration.
2 INTEGRATION
10 T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

3 Overview of the PROFIsafe parameters
Several PROFIsafe parameters are available. Of these parameters, the following are
relevant for integrating the device.
•F_Dest_Add
F destination address. For PROFIsafe communication, the safety laser scanner
needs a clear F_Dest_Add. You need to enter the same value as the one config‐
ured in Safety Designer.
•F_WD_Time
Watchdog time (monitoring time) for the cyclical service. The watchdog time should
be long enough to tolerate short delays in communication. It does, however, have
an effect on the response time of the overall system (for example in the event of a
fault) and is therefore safety-relevant.
The default value is 150 ms. This is adequate in many cases. The integrator needs
to check the value and, if necessary, adjust it to avoid errors at a later time.
•F_iPar_CRC
Checksum of the safety configuration. Is used to check whether the safety-relevant
settings were changed. The entered value must match the value configured in
Safety Designer for the configuration checksum (function and network). It is only
needed if a process image is used where F_iPar_CRC is checked (module with
the suffix –iParCRC). This parameter must be updated if the configuration of the
safety laser scanner is modified in any way. If the parameter is not updated (e.g.,
due to an unauthorized modification of the configuration), the controller goes into
the safe state.
OVERVIEW OF THE PROFISAFE PARAMETERS 3
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 11
Subject to change without notice

4 Overview of the process images
Variants
The microScan3 - PROFINET supports 8 PROFIsafe process images (in the controller:
modules). The 8 process images can be divided into 2 groups depending on the PROFI‐
safe version (2.4 or 2.6.1). Which process images to use depends on the version of
PROFIsafe that the controller supports. If you do not know which PROFIsafe version your
controller supports, use the process images for PROFIsafe version 2.4.
PROFIsafe version 2.4 PROFIsafe version 2.6.1
12-byte
12-byte with iParCRC
6-byte
6-byte with iParCRC
12-byte
12-byte with iParCRC
6-byte
6-byte with iParCRC
The process images differ with regard to their size (6 bytes or 12 bytes) and the
incorporation of the iParCRC parameter.
6-byte process images must be used in the following cases:
•Only a limited range of peripheral addresses are available in your application.
•The microScan3 PROFINET is replacing a safety laser scanner of type S3000
PROFINET.
•The safety software for your S7 does not support 12-byte process images.
If your application requires constant monitoring of the checksums of the sensor config‐
uration, use a process image with iParCRC.
Structure of the process image (12 bytes)
Table 1: Safety-related PROFIsafe process image: input of the device, output of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved ActivateS‐
tandbyMode
StopAlarm‐
Detection
Reserved TriggerRun‐
Mode
1 SetMonitoringCaseNoTable1
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 Reserved
9 1) TriggerReset‐
CutOff‐
Path08
TriggerReset‐
CutOff‐
Path07
TriggerReset‐
CutOff‐
Path06
TriggerReset‐
CutOff‐
Path05
TriggerReset‐
CutOff‐
Path04
TriggerReset‐
CutOff‐
Path03
TriggerReset‐
CutOff‐
Path02
TriggerReset‐
CutOff‐
Path01
10 Reserved
11 Reserved TriggerDevi‐
ceReboot‐
WithNetwork
TriggerDevi‐
ceRebootWi‐
thoutNet‐
work
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
4 OVERVIEW OF THE PROCESS IMAGES
12 T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

Table 2: Safety-related PROFIsafe process image: output of the device, input of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved Manipula‐
tionStatus
Reference‐
ContourSta‐
tus
Contamina‐
tionError
Contamina‐
tionWarning
Standbymo‐
deActive
RunModeac‐
tive
1 1) SafeCutOff‐
Path08
SafeCutOff‐
Path07
SafeCutOff‐
Path06
SafeCutOff‐
Path05
SafeCutOff‐
Path04
SafeCutOff‐
Path03
SafeCutOff‐
Path02
SafeCutOff‐
Path01
2 Reserved
3 1) NonsafeCu‐
tOffPath08
NonsafeCu‐
tOffPath07
NonsafeCu‐
tOffPath06
NonsafeCu‐
tOffPath05
NonsafeCu‐
tOffPath04
NonsafeCu‐
tOffPath03
NonsafeCu‐
tOffPath02
NonsafeCu‐
tOffPath01
4 Reserved
5 1) ResetRequir‐
edCutOff‐
Path08
ResetRequir‐
edCutOff‐
Path07
ResetRequir‐
edCutOff‐
Path06
ResetRequir‐
edCutOff‐
Path05
ResetRequir‐
edCutOff‐
Path04
ResetRequir‐
edCutOff‐
Path03
ResetRequir‐
edCutOff‐
Path02
ResetRequir‐
edCutOff‐
Path01
6 Reserved
7 CurrentMonitoringCaseNoTable1
8 Reserved
9 Reserved
10 Reserved
11 Reserved DeviceError Applicatio‐
nError
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
Table 3: Non-safety-related PROFINET process image: output of the device, input of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved Manipula‐
tionStatus
Reference‐
ContourSta‐
tus
Contamina‐
tionError
Contamina‐
tionWarning
Standbymo‐
deActive
RunModeac‐
tive
1 1) StatusSafe‐
CutOff‐
Path08
StatusSafe‐
CutOff‐
Path07
StatusSafe‐
CutOff‐
Path06
StatusSafe‐
CutOff‐
Path05
StatusSafe‐
CutOff‐
Path04
StatusSafe‐
CutOff‐
Path03
StatusSafe‐
CutOff‐
Path02
StatusSafe‐
CutOff‐
Path01
2 Reserved
3 1) NonsafeCu‐
tOffPath08
NonsafeCu‐
tOffPath07
NonsafeCu‐
tOffPath06
NonsafeCu‐
tOffPath05
NonsafeCu‐
tOffPath04
NonsafeCu‐
tOffPath03
NonsafeCu‐
tOffPath02
NonsafeCu‐
tOffPath01
4 Reserved
5 1) ResetRequir‐
edCutOff‐
Path08
ResetRequir‐
edCutOff‐
Path07
ResetRequir‐
edCutOff‐
Path06
ResetRequir‐
edCutOff‐
Path05
ResetRequir‐
edCutOff‐
Path04
ResetRequir‐
edCutOff‐
Path03
ResetRequir‐
edCutOff‐
Path02
ResetRequir‐
edCutOff‐
Path01
6 Reserved
7 CurrentMonitoringCaseNoTable1
8 Reserved
9 Reserved
10 Reserved
11 Reserved DeviceError Applicatio‐
nError
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
OVERVIEW OF THE PROCESS IMAGES 4
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 13
Subject to change without notice

Structure of the process image (6 bytes)
Table 4: Safety-related PROFIsafe process image: input of the device, output of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved ActivateS‐
tandbyMode
StopAlarm‐
Detection
Reserved TriggerRun‐
Mode
1 SetMonitoringCaseNoTable1
2 Reserved
3 1) TriggerReset‐
CutOff‐
Path08
TriggerReset‐
CutOff‐
Path07
TriggerReset‐
CutOff‐
Path06
TriggerReset‐
CutOff‐
Path05
TriggerReset‐
CutOff‐
Path04
TriggerReset‐
CutOff‐
Path03
TriggerReset‐
CutOff‐
Path02
TriggerReset‐
CutOff‐
Path01
4 Reserved
5 Reserved TriggerDevi‐
ceReboot‐
WithNetwork
TriggerDevi‐
ceRebootWi‐
thoutNet‐
work
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
Table 5: Safety-related PROFIsafe process image: output of the device, input of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved Manipula‐
tionStatus
Reference‐
ContourSta‐
tus
Contamina‐
tionError
Contamina‐
tionWarning
Standbymo‐
deActive
RunModeac‐
tive
1 1) SafeCutOff‐
Path08
SafeCutOff‐
Path07
SafeCutOff‐
Path06
SafeCutOff‐
Path05
SafeCutOff‐
Path04
SafeCutOff‐
Path03
SafeCutOff‐
Path02
SafeCutOff‐
Path01
2 1) NonsafeCu‐
tOffPath08
NonsafeCu‐
tOffPath07
NonsafeCu‐
tOffPath06
NonsafeCu‐
tOffPath05
NonsafeCu‐
tOffPath04
NonsafeCu‐
tOffPath03
NonsafeCu‐
tOffPath02
NonsafeCu‐
tOffPath01
3 1) ResetRequir‐
edCutOff‐
Path08
ResetRequir‐
edCutOff‐
Path07
ResetRequir‐
edCutOff‐
Path06
ResetRequir‐
edCutOff‐
Path05
ResetRequir‐
edCutOff‐
Path04
ResetRequir‐
edCutOff‐
Path03
ResetRequir‐
edCutOff‐
Path02
ResetRequir‐
edCutOff‐
Path01
4 CurrentMonitoringCaseNoTable1
5 Reserved DeviceError Applicatio‐
nError
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
Table 6: Non-safety-related PROFINET process image: output of the device, input of the control
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Reserved Manipula‐
tionStatus
Reference‐
ContourSta‐
tus
Contamina‐
tionError
Contamina‐
tionWarning
Standbymo‐
deActive
RunModeac‐
tive
1 1) StatusSafe‐
CutOff‐
Path08
StatusSafe‐
CutOff‐
Path07
StatusSafe‐
CutOff‐
Path06
StatusSafe‐
CutOff‐
Path05
StatusSafe‐
CutOff‐
Path04
StatusSafe‐
CutOff‐
Path03
StatusSafe‐
CutOff‐
Path02
StatusSafe‐
CutOff‐
Path01
2 1) NonsafeCu‐
tOffPath08
NonsafeCu‐
tOffPath07
NonsafeCu‐
tOffPath06
NonsafeCu‐
tOffPath05
NonsafeCu‐
tOffPath04
NonsafeCu‐
tOffPath03
NonsafeCu‐
tOffPath02
NonsafeCu‐
tOffPath01
3 1) ResetRequir‐
edCutOff‐
Path08
ResetRequir‐
edCutOff‐
Path07
ResetRequir‐
edCutOff‐
Path06
ResetRequir‐
edCutOff‐
Path05
ResetRequir‐
edCutOff‐
Path04
ResetRequir‐
edCutOff‐
Path03
ResetRequir‐
edCutOff‐
Path02
ResetRequir‐
edCutOff‐
Path01
4 CurrentMonitoringCaseNoTable1
5 Reserved DeviceError Applicatio‐
nError
1) Cut-off paths 5 to 8 are only available for the Pro performance package.
4 OVERVIEW OF THE PROCESS IMAGES
14 T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

Addressing the bits in the controller
The bits of the process images can be accessed in the logic using the following
scheme: Ix.x and Qx.x. The start byte (byte 0) is relative to the specified Start address.
If Start address is set to the value 17, then the output bit 0.0 in the logic can be
accessed as Q17.0. The input bit 3.1 then corresponds to I20.1.
OVERVIEW OF THE PROCESS IMAGES 4
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 15
Subject to change without notice

5 Notes on implementing the process images
Safety-related cut-off paths and non-safety-related cut-off paths
In the following example, cut-off paths 1 (protective field) and 4 (contour detection field)
are safety-related. Cut-off paths 2 and 3 (warning fields) are non-safety-related.
When incorporating the cut-off paths into the logic, the user can select a suitable byte
from the assembly. A cut-off path with a protective field or contour detection field is
always regarded as safety-related. A cut-off path with a warning field is always regarded
as non-safety-related.
Table 7: Example 6-byte process image
Function
(Safety Designer)
Field type Allocation in the
process image
Data Safe
Cut-off path 1 Protective field Safety-related cut-off
path 1
I1.0 Yes
Cut-off path 2 Warning field Non-safety-related
cut-off path 2
I2.1 No
Cut-off path 3 Warning field Non-safety-related
cut-off path 3
I2.2 No
Cut-off path 4 Contour detection
field
Safety-related cut-off
path 4
I1.3 Yes
Behavior with mixed field types
When a cut-off path with safe and non-safe fields (e.g., protective field and warning
field) is used in different monitoring cases and the monitoring case with the warning
field is active, then the safe cut-off path is deactivated. As a result, the bit for this safe
cut-off path is LOW and the display of the safety laser scanner indicates the OFF state.
The following example illustrates this behavior in the configuration and in the display of
the device. All fields are clear in this example (no field detection).
5 NOTES ON IMPLEMENTING THE PROCESS IMAGES
16 T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

NOTES ON IMPLEMENTING THE PROCESS IMAGES 5
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 17
Subject to change without notice

6 Troubleshooting
Error indicators in TIA Portal
CPU error Possible causes
Hardware component not available due to type
mismatch
•Incorrect microScan3 PROFIsafe module
configured in TIA Portal.
•Incorrect process image selected in Safety
Designer.
Safety Program: Error in PROFIsafe communi‐
cation with F-IO
F_WD_Time set too short.
IO device failure - IO device not found •Incorrect PROFINET device name
•Faulty connection between the safety laser
scanner and the controller (e.g., defective
cable)
•Voltage supply to the safety laser scanner
is interrupted
Mismatch of failsafe destination address
(F_Dest_Add)
F_Dest_Add does not match the configuration
in Safety Designer.
Inconsistent iParameters (iParCRC error) F_iPar_CRC does not match the configuration
in Safety Designer.
Error indicators on the microScan3 – network LEDs
The safety laser scanner has two PROFINET LEDs in addition to the Ethernet LEDs.
Table 8: Bus error LED, inscription: BF
LED status Meaning Troubleshooting
oNo supply voltage
or PROFINET commu‐
nication not active or
device is not config‐
ured
bCheck power supply, wiring and connected
communication partners.
bRestart device.
bCheck the configuration of the device.
O Green PROFINET communi‐
cation is active
–
Ö Green No connection to con‐
trol unit
bCheck PROFINET names.
bCheck the control unit.
bStart the controller.
O Red Serious error, device
not ready
bCheck device.
bRestart device.
bReplace device.
Ö Red Incorrect PROFINET
configuration
bCheck the PROFINET configuration, in par‐
ticular F_Dest_Add.
Ö Red/green PROFINET alarm is
active
bCheck the cause of the error in the con‐
figuration program of the controller and
observe the help text.
bCheck the alarm in the Safety Designer.
Table 9: System error LED, inscription: BF
LED status Meaning Troubleshooting
oNo supply voltage
or PROFIsafe commu‐
nication not initialized
or not active or incor‐
rect process image
selected
bTrigger or launch PROFIsafe communica‐
tion.
bCheck whether the same process image is
selected in the controller and in the device
(6 bytes or 12 bytes)
6 TROUBLESHOOTING
18 T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 8026545/2021-03-15 | SICK
Subject to change without notice

LED status Meaning Troubleshooting
O Green PROFIsafe communi‐
cation is active
–
Ö
0.5 Hz, green
Passivation of the
device has been com‐
pleted, e.g. after
communication error
or connection termina‐
tion
bPerform reintegration of the device.
Ö
2 Hz, green
A process image with
F_iPar_CRC is used,
but value 0 is speci‐
fied as F_iPar_CRC.
bEnter the correct F_iPar_CRC in the config‐
uration program of the controller.
bUse process image without F_iPar_CRC.
O Red Serious error, device
not ready
bCheck and restart the device.
bReplace device.
Ö Red Incorrect PROFIsafe
configuration
bCheck the PROFIsafe parameters, in partic‐
ular, F_Dest_Add, WD_Time, F_iPar_CRC.
bCheck the PROFINET connection (see
table 8, page 18).
Diagnostics using the display
You can use the buttons at the front of the safety laser scanner to display the PROFI‐
NET alarms.
1. Press the OK button twice.
2. Diagnostics > PROFINET alarms
NOTE
Note: Active alarms are also displayed in the CPU diagnostics buffer in Safety Designer
and in TIA Portal.
Why does “Waiting for input” appear on the display?
•The safety laser scanner has not yet received a valid bit from the controller for
selecting a monitoring case.
•There is an error in the PROFINET/PROFIsafe parameters.
S3000 PROFINET vs microScan3 - PROFINET
If the microScan3 - PROFINET is replacing a safety laser scanner of type S3000 PRO‐
FINET, take into consideration that the process image has a different structure even
though the size of the process image remains the same at 6 bytes.
TROUBLESHOOTING 6
8026545/2021-03-15 | SICK T E C H N I C A L I N F O R M A T I O N | microScan3 - PROFINET 19
Subject to change without notice