Leuze electronic MSI 400 Series User manual

Translation of the original operating instructions
EN 2019/03 - 50134715 We reserve the right to make technical changes
MSI 400
Gateways

© 2019
Leuze electronic GmbH & Co. KG
In der Braike 1
D-73277 Owen / Germany
Phone: [phone]
Fax: [phone]
http://www.leuze.com
[email protected]
Leuze electronic MSI 400 2

Table of Contents
Leuze electronic MSI 400 3
Table of Contents
1 About this manual.................................................................................................6
1.1 Function of this document....................................................................................................... 6
1.2 Scope of validity and applicable documents........................................................................... 6
1.3 Target audience...................................................................................................................... 6
1.4 Information depth.................................................................................................................... 7
1.5 Abbreviations and Definitions ................................................................................................. 7
1.6 Symbols/icons and writing style/spelling standard used......................................................... 9
1.7 Copyright and right to make changes ................................................................................... 10
2 Safety ...................................................................................................................11
2.1 Qualified persons.................................................................................................................. 11
2.2 Proper use ............................................................................................................................ 11
2.3 Environmentally friendly behavior......................................................................................... 12
2.3.1 Disposal.............................................................................................................................12
2.3.2 Sorting of materials ...........................................................................................................12
3 Product description ............................................................................................13
3.1 Version, compatibility, and features...................................................................................... 13
3.2 Equipment variants ............................................................................................................... 14
3.3 Data transferred to the network (network input data sets).................................................... 14
3.3.1 Direct gateway output values ............................................................................................17
3.3.2 Module state / input and output values..............................................................................18
3.3.3 Transmission of data from a second network....................................................................18
3.3.4 Configuration test values (CRCs)......................................................................................18
3.3.5 Error and state information for the modules ......................................................................19
3.4 Data received from the network (network output data sets) ................................................. 23
4 Installation and basic configuration .................................................................24
4.1 Installing/removing ................................................................................................................ 24
4.1.1 Installing modules on hat rail.............................................................................................24
4.1.2 Removing modules from the hat rail..................................................................................28
4.2 Electrical installation ............................................................................................................. 29
4.3 Initial configuration steps ...................................................................................................... 30
5 Configuration of gateways with MSI.designer .................................................31
5.1 The graphical user interface ................................................................................................. 31
5.1.1 Activating gateway functionality ........................................................................................31
5.1.2 "Gateway" view..................................................................................................................32
5.1.3 Layout and content of the tabs ..........................................................................................34
5.1.4 "Gateway” and “Properties” docking windows...................................................................35
5.2 Function and basic settings .................................................................................................. 36
5.2.1 Routing ..............................................................................................................................36
5.2.2 Basic settings for the process data ...................................................................................37
5.3 Configuring the gateway output values (tab 1) ..................................................................... 38
5.4 Editing the gateway input values (tab 2)............................................................................... 40
5.5 Monitoring process data ....................................................................................................... 42
6 Modbus TCP gateway.........................................................................................44
6.1 Interfaces and operation ....................................................................................................... 44
6.2 Basic configuration – allocation of an IP address ................................................................. 44
6.3 Configuration of the Modbus-TCP interface to the PLC - how the data are transferred ....... 45
6.4 Diagnosis and troubleshooting ............................................................................................. 51

Table of Contents
Leuze electronic MSI 400 4
6.5 State bits............................................................................................................................... 53
7 PROFINET IO-Gateway .......................................................................................55
7.1 Interfaces and operation ....................................................................................................... 55
7.2 Basic configuration - Assigning a device name and an IP address ...................................... 55
7.3 PROFINET configuration of the gateway - how the data are transferred ............................. 58
7.4 PROFINET configuration of the gateway - which data are transferred................................. 61
7.5 Diagnostics and troubleshooting........................................................................................... 64
7.6 Deactivation of the PROFINET IO function .......................................................................... 66
7.7 State bits............................................................................................................................... 66
7.8 Optimizing performance........................................................................................................ 66
8 EtherNet/IP gateway ...........................................................................................67
8.1 Interfaces and operation ....................................................................................................... 67
8.2 Datasheet ............................................................................................................................. 67
8.3 Basic setup ........................................................................................................................... 67
8.3.1 Basic configuration of PLC ................................................................................................67
8.3.2 Basic configuration of the controller module .....................................................................71
8.3.3 Configuring the data to PLC ..............................................................................................72
8.3.4 Configuring the usage of data from PLC ...........................................................................73
8.4 Supported CIP Objects ......................................................................................................... 73
8.4.1 Identity Object ...................................................................................................................73
8.4.2 Assembly Object ...............................................................................................................75
8.4.3 Discrete Input Point Object................................................................................................76
8.4.4 Discrete Output Point Object.............................................................................................77
8.4.5 Discrete Input Group Object..............................................................................................79
8.4.6 Discrete Output Group Object ...........................................................................................79
8.4.7 PCCC Object.....................................................................................................................80
8.4.8 Vendor Object ...................................................................................................................85
8.5 Supported Assembly data..................................................................................................... 89
8.5.1 List of Assembly data ........................................................................................................89
8.5.2 Assembly Instances for Logic Output Bytes......................................................................91
8.5.3 Assembly Instances for Logic Input Bytes.........................................................................91
8.6 Accessing to CIP objects ...................................................................................................... 93
8.6.1 Explicit Messaging.............................................................................................................93
8.6.2 Implicit Messaging.............................................................................................................93
8.6.3 Symbolic Addressing.........................................................................................................94
8.7 Adjust Performance .............................................................................................................. 95
8.8 Connection with more than one PLC .................................................................................... 95
8.9 Diagnostics and troubleshooting........................................................................................... 96
8.9.1 Notifications via network....................................................................................................96
8.9.2 LED States ........................................................................................................................96
8.9.3 Diagnostic functions in the configuration software ............................................................99
8.10 State bits............................................................................................................................... 99
9 PROFIBUS DP gateway ....................................................................................100
9.1 Interfaces and operation ..................................................................................................... 100
9.2 Projecting ............................................................................................................................ 104
9.3 PROFIBUS configuration of the gateway - how the data are transferred ........................... 106
9.4 Diagnosis and troubleshooting ........................................................................................... 112
10 CANopen gateway ............................................................................................115
10.1 Interfaces and operation ..................................................................................................... 115
10.2 CANopen configuration of the gateway - how the data are transferred.............................. 119

Table of Contents
Leuze electronic MSI 400 5
10.3 CANopen configuration of the gateway - which data are transferred ................................. 121
10.4 NMT – network management ............................................................................................. 122
10.5 SYNC .................................................................................................................................. 123
10.6 Emergency.......................................................................................................................... 123
10.7 Node guarding .................................................................................................................... 127
10.8 PDO communication........................................................................................................... 128
10.9 SDO communication........................................................................................................... 131
10.10 SDO object directory........................................................................................................... 132
10.11 Guarding protocols ............................................................................................................. 138
10.12 Error objects........................................................................................................................ 140
10.13 CANopen diagnostic examples........................................................................................... 142
10.14 Diagnosis and troubleshooting ........................................................................................... 145
11 EtherCAT Gateway............................................................................................149
11.1 Interfaces and operation ..................................................................................................... 149
11.2 EtherCAT basics................................................................................................................. 151
11.3 EtherCAT state machine..................................................................................................... 154
11.4 Bus topology and cabling.................................................................................................... 155
11.5 Data transferred into the network ....................................................................................... 156
11.5.1 Data set 1 ........................................................................................................................156
11.5.2 Data set 2 ........................................................................................................................161
11.5.3 Data set 3 ........................................................................................................................162
11.6 Data received from the network.......................................................................................... 164
11.7 Configuring an EtherCAT network ...................................................................................... 165
11.8 EtherCAT configuration of the gateway - how the data are transferred.............................. 165
11.9 Diagnostic LEDs on the gateway and troubleshooting ....................................................... 168
12 Technical data ...................................................................................................171
12.1 Modbus TCP, PROFINET IO and EtherNet/IP gateway..................................................... 171
12.2 EtherCAT gateway.............................................................................................................. 171
12.3 PROFIBUS DP.................................................................................................................... 171
12.4 CANopen gateways ............................................................................................................ 171
12.5 Technical data for supply circuit ......................................................................................... 172
12.6 General technical data........................................................................................................ 172
12.7 Dimensional drawings......................................................................................................... 173
12.7.1 Controller module ............................................................................................................173
12.7.2 CANopen and PROFIBUS gateways (old housing) ........................................................175
12.7.3 EtherCAT gateway ..........................................................................................................176
13 Order data..........................................................................................................177
13.1 Hardware modules and accessories................................................................................... 177
13.2 Modules for contact expansion ........................................................................................... 178

About this manual
Leuze electronic MSI 400 6
1 About this manual
Please read this section carefully before you work with these operating instructions and the MSI 400 gate-
ways.
1.1 Function of this document
There are three manuals for the MSI 400 system with clearly delineated areas of application as well as in-
stallation instructions and brief instructions for each module.
• This gateway manual describes all MSI 400 gateways and their functions in detail. It instructs the tech-
nical staff of the machine manufacturer or machine operator in the safe installation, configuration, elec-
trical installation, commissioning, operation and maintenance of the MSI 400 gateways.
This manual does not provide operating instructions for the machine, which incorporates modular MSI
400 safety controls and a MSI 400 gateway. Information in this regard is provided in the operating in-
structions for each machine.
This manual is only valid in combination with the other MSI 400 manuals (see Scope of validity and ap-
plicable documents [chapter 1.2]).
• The software manual describes the software-supported configuration and parameterization of the MSI
400 safety control. In addition, the software manual contains a description of the important diagnostic
functions for operation and detailed information for identifying and eliminating errors. Use the software
manual mainly when configuring, commissioning and operating MSI 400 safety controls.
• The Hardware manual describes all of the modules and their functions in detail. Use the hardware
manual mainly for designing devices.
• Each module contains the installation instructions/brief instructions. These instructions provide in-
formation on the fundamental technical specifications of the modules and contain simple installation in-
structions. Use the installation instructions/brief instructions when installing the MSI 400 safety control.
This manual contains original operating instructions in accordance with the Machinery Directive.
1.2 Scope of validity and applicable documents
This manual applies to the following gateway modules:
• MSI-EN-MOD
• MSI-EN-PN
• MSI-EN-IP
• MSI-FB-PROFIBUS
• MSI-FB-CANOPEN
• MSI-FB-ETHERCAT
Tab.1.1: Overview of the MSI 400 documentation
Document Title Item number
Software manual MSI.designer Software 50134713
Hardware manual MSI 400 Hardware 50134711
Gateway manual MSI 400 Gateways 50134715
Operating instructions MSI 400 50134613
Operating instructions MSI-EM-IO84-xx / MSI-EM-I8-xx 50134614
Operating instructions MSI-EM-IO84NP-xx 50134615
Operating instructions MSI-FB-CANOPEN 50134616
Operating instructions MSI-FB-PROFIBUS 50134617
Operating instructions MSI-FB-ETHERCAT 50134618
1.3 Target audience
This manual is aimed at the planners, developers and operators of systems that incorporate modular
MSI 400 safety controls and that want to exchange data with a field bus (controls) via a gateway.

About this manual
Leuze electronic MSI 400 7
It is also aimed at persons commissioning a MSI 400 gateway system for the first time or maintaining such
a system.
1.4 Information depth
This manual contains information about the following topics related to MSI 400 gateways:
• Installation
• Integration into the network
• Configuration with the MSI.designer software
• Data transmission to and from the network
• State information, projection and associated mapping
• Item numbers
Important information
WARNING
Observing safety information and protective measures
Observe the safety information and protective measures for the MSI 400 gateways described in
this manual.
Downloads are provided on the Internet
Also consult our website on the Internet. At the following link http://www.leuze.com, you will find:
• the MSI.designer software
• The MSI 400 manuals available for display and printing in various languages:
• This gateway manual (50134715)
• The hardware manual (50134711)
• The software manual (50134713)
• The GSD file of the MSI-FB-PROFIBUS for PROFIBUS-DP
• The EDS file of the MSI-FB-CANOPEN for CANopen
1.5 Abbreviations and Definitions
Term Explanation
{ } An element array or an element structure
0b The following are specified in binary format
0x The following are specified in hexadecimal format
Procedure error A procedure error occurs if, in redundant input circuits, the two input signals
are not equal. Monitoring of inequality is frequently carried out within a toler-
ated time window.
ACD Address Collision Detection
ANSI American National Standards Institute, specified character coding
AOI Add On Instruction
AOP Add On Profile
API Actual Packet Interval
AR Application Relation, unique communication relationship in PROFINET IO
between the PLC and the device
Attribute Characteristic or property of an object
Bit Data unit with a value of 0 or 1
BOOL Data type specified for CIP devices; stands for a value of 1 byte, in which
each of the 8 bits is viewed individually

About this manual
Leuze electronic MSI 400 8
Term Explanation
Byte, BYTE Data unit, representing a sequence of 8 bits; without a plus/minus sign, if not
specified
CIP Common Industrial Protocol
Controller module Controller from the MSI 400 product family
CRC Cyclic Redundancy Check, a type or the result of a hash function for reveal-
ing errors in the area of data storage or transmission
Data block A data block contains 2-12 bytes of the relevant data set (depending on the
gateway used).
Data set Describes a quantity of associated data, e.g. logic values or system state
data. A data set can consist of several data blocks.
I/O Input/output
EPATH Encoded Path, especially for CIP applications
EtherNet/IP Industrially-used Ethernet network, combines standard Ethernet technologies
with CIP
Gateway Connection module for industrially-used networks, such as EtherNet/IP,
PROFIBUS DB, CANopen, Modbus TCP, etc.
ID An identifier or an identity
Instance The physical representation of an object within a class. It stands for one of
several objects within the same object class. (Reference: CIP specification,
version 3.18)
IP Internet protocol
Class A series of objects representing a similar system component. A class is a
generalization of the object, a template for defining variables and methods.
All the objects within a class are identical with regard to function and beha-
vior. However, they may have differing attribute values. (Reference: CIP spe-
cification, version 3.18)
LSB Low Significant Byte
MPI Measured Packet Interval; shows the API at the time of measurement
MSB Most Significant Byte
O→T Originator to Target (sender to target device)
ODVA Open Device Vendor Association
PC Personal Computer
PCCC Programmable Controller Communication Command
PLC Programmable Logic Controller
RPI Requested Packet Interval
RX Receive
S/N Serial number
MSI.designer Configuration software for controller modules of type MSI 4xx. The software
can be run on a PC and communicates with the controller modules.
Service Service to be performed
Examples: GetAttributeSingle, SetAttributeSingle
SHORT_STRING Data type specified for CIP devices; stands for a character string (1 byte per
character, 1 byte length code)
SINT Short integer = 1 byte

About this manual
Leuze electronic MSI 400 9
Term Explanation
MSI 4xx Safety controller consisting of a controller module of the MSI 400 product
family, as well as optionally connectable expansion gateways and I/O mod-
ules.
MSI 430 Controller module, which is equipped with safety inputs and outputs and
gateway functions, amongst other things
PLC Programmable Logic Controller
( PLC)
Stuck-at high Stuck-at high is an error in which the input or output signal gets stuck at On.
The causes for a Stuck-at high can be short-circuits to other input and output
lines, often called cross-references, or defective switching elements. Stuck-at
high errors are discovered through plausibility tests, such as sequence errors
in two-channel input circuits or using test pulses in input and output circuits.
Stuck-at low Stuck-at low is an error in which the input or output signal gets stuck at Off.
The causes of a stuck-at low can be line interruptions in input circuits or de-
fect switching elements. Stuck-at low errors are discovered through plausibil-
ity tests and usually do not require immediate error recognition.
T→O Target to Originator
TCP Transmission Control Protocol, Internet standard protocol for the transport
layer specified in RFC 793
Test pulses or scan gaps Test pulses or scan gaps are brief switch-offs / interruptions in input and out-
put circuits, which are generated in a targeted manner to detect stuck-at high
errors quickly. Test pulses check the switch-off ability of switching elements
during operation on an almost continuous basis.
Test pulse error Test pulse errors are undetected test pulses, which lead to a negative test
result and thus switch-off of the affected safety circuits.
TX Transmit / Send
UCMM Unconnected Message Manager
UDINT Unsigned double integer = 4 Bytes = 2 Words
Data type specified for CIP applications
UDP User Datagram Protocol, Internet standard protocol for the transport layer
specified in RFC 793
UDT User Defined Type
UINT Unsigned double integer = 2 Bytes = 1 Word
Data type specified for CIP applications
USINT Data type specified for CIP applications, which stands for 1 byte without a
plus/minus symbol
1.6 Symbols/icons and writing style/spelling standard used
NOTICE
i
These are notes that provide you with information regarding particularities of a device or a soft-
ware function.

About this manual
Leuze electronic MSI 400 10
WARNING
Warning!
A warning lets you know about specific or potential hazards. It is intended to protect you from
accidents and help prevent damage to devices and systems.
ÄPlease read and follow the warnings carefully!
Failure to do so may negatively impact the safety functions and cause a hazardous state to
occur.
Menus and commands
The names of software menus, submenus, options, and commands, selection fields, and windows are writ-
ten in bold font. Example: Click on Edit in the File menu.
1.7 Copyright and right to make changes
Copyright
This document is copyright-protected. The rights derived from this copyright are reserved for Leuze elec-
tronic. Reproduction of this document or parts of this document is only permissible within the limits of the
statutory provision of the Copyright Act. Any modification or abridgment of the document is prohibited
without the express written agreement of Leuze electronic.
Allen-Bradley, CompactBlock Guard I/O, CompactLogix, ControlFLASH, ControlLogix, DH+, FactoryTalk,
FLEX, GuardLogix, Kinetix, Logix5000, MicroLogix, PanelBuilder, PanelView, PhaseManager, PLC-2,
PLC-3, PLC-5, POINT I/O, POINT Guard I/O, Rockwell Automation, Rockwell Software, RSBizWare,
RSFieldbus, RSLinx, RSLogix 5000, RSNetWorx, RSView, SLC, SoftLogix, Stratix, Stratix 2000, Stratix
5700, Stratix 6000, Stratix 8000, Stratix 8300, Studio 5000, Studio 5000 Logix Designer, SynchLink, and
Ultra are registered trademarks of Rockwell Automation, Inc.
ControlNet, DeviceNet, and EtherNet/IP are registered trademarks of ODVA, Inc.
TwinCAT is a registered trademark of Beckhoff Automation GmbH.
EtherCAT is a registered trademark and a patented technology licensed by Beckhoff Automation GmbH.
Microsoft, Windows 98, Windows NT, Windows 2000, Windows XP, Windows 7, Windows 8, Windows 8.1,
Windows 10 and .NET Framework are registered trademarks of the Microsoft Corporation.
Any other product or trade names listed in this manual are the trademarks or registered trademarks of the
respective owners.
Subject to change.
Subject to technical changes for reasons of continued development.

Safety
Leuze electronic MSI 400 11
2 Safety
This section is intended to support your safety and the safety of the system users.
ÄPlease read this section carefully before you work with a MSI 400 system.
2.1 Qualified persons
A safety controller with MSI 400 gateways may only be installed, commissioned, and maintained by quali-
fied persons.
Qualified persons are those who
• have suitable technical training and
• have been trained by the machine operator in the operation and applicable safety guidelines and
• have access to the MSI 400 system operating instructions and have read them and duly noted their
contents.
2.2 Proper use
The MSI 400 gateways can only be operated in conjunction with a MSI 400 safety controller. The firmware
version of the connected controller modules must be at least V1.0.0 and the version of the MSI.designer
configuration software must be at least 1.0.0.
The MSI 400 gateways do not have their own power supply.
Specifications for use
WARNING
Do not operate a MSI 400 gateway on a safety field bus!
The gateway modules are not suitable for operation with a safety field bus!
They do not only generate safety-related field bus data (state bytes) for control and diagnostic
purposes. They do not support any safety mechanisms that would be required for communica-
tion within a safety network.
WARNING
Do not use data from a MSI 400 gateway for safety-related applications!
The MSI 400 gateways can be used to integrate non-safety-related data into the logic editor in
such a way that the safety function of the MSI 400 system may be adversely affected.
ÄNever integrate a gateway into a MSI 400 system without having this source or risk checked
by a safety specialist.
NOTICE
i
Requirements for domestic use
If you wish to use the MSI 400 system for domestic purposes, you need to take additional steps
to prevent the emission of radio frequency interference in limit class B according to EN 55011.
Here are some steps you might take:
ÄThe use of interference suppressor filters in the supply circuit
ÄInstallation in grounded switch cabinets or boxes
Specifications for installation
These modules may only be operated by qualified staff and may only be used on a machine on which they
have been installed and commissioned for the first time by a qualified person in accordance with this
manual.
WARNING
The safety instructions and precautions for use of MSI 400 gateways must be adhered to!
In the event of any other use or any changes to the device – including within the scope of install-
ation – this shall nullify any warranty claim with respect to Leuze electronic GmbH.

Safety
Leuze electronic MSI 400 12
NOTICE
i
ÄPlease follow the standards and guidelines valid in your country when installing and operat-
ing the MSI 400 gateways.
ÄThe national/international legal regulations apply to the installation and use of the modular
MSI 400 safety controls as well as for the commissioning and repeated technical testing,
particularly the following:
– EMC Directive 2014/30/EU,
– the Use of Work Equipment Directive 2009/104/EC,
– the accident prevention/safety regulations.
ÄThe manual must be provided to the operator of the machine on which the MSI 400- system
is to be used. The machine operator must be trained by qualified persons and is required to
read this manual.
2.3 Environmentally friendly behavior
The modular MSI 400 safety control and the corresponding modules are designed such that they stress the
environment as little as possible. They use only a minimum of power and resources.
ÄMake sure that you also carry out work while always considering the environment.
2.3.1 Disposal
The disposal of unusable or irreparable devices should always be done in accordance with the respectively
valid country-specific waste-elimination guidelines (e.g. European Waste Code 16 02 14).
NOTICE
i
We will be happy to help you in disposing of these devices.
Simply contact us.
2.3.2 Sorting of materials
WARNING
Important information
ÄThe sorting of materials may only be carried out by qualified persons!
ÄCare must be used when disassembling the devices. There is a risk of injuries during this
process.
Before you can route the devices to the environmentally-friendly recycling process, it is necessary to sort
the various materials of the MSI 400 devices.
ÄSeparate the housing from the rest of the components (particularly from the PC board).
ÄPlace the separated components into the corresponding recycling containers (see the following table).
Tab.2.1: Overview of disposal according to components
Components Disposal
Product
Housing
PC boards, cables, connectors, and
electric connecting pieces
Plastic recycling
Electronics recycling
Packaging
Cardboard, paper Paper/cardboard recycling

Product description
Leuze electronic MSI 400 13
3 Product description
MSI 400 gateways allow a MSI 400 system to transmit non-safety-related data for control and diagnostic
purposes to the external field bus system and to receive them.
Important safety information
WARNING
Do not operate a MSI 400 gateway on a safety field bus!
The gateway modules are not suitable for operation with a safety field bus!
They do not only generate safety-related field bus data (state bytes) for control and diagnostic
purposes. They do not support any safety mechanisms that would be required for communica-
tion within a safety network.
Information on the function, configuration and designations
NOTICE
i
Where not otherwise indicated, this manual always considers the data exchanged between the
MSI 400 system and the relevant network from the point of view of the network master (PLC).
Thus data sent to the network from the MSI 400 system is termed input data, while data re-
ceived from the network is termed output data.
Configuration of MSI 400 gateways takes place via the MSI.designer configuration software, using a PC or
Notebook connected to the MSI 4xx main module via the USB interface or RJ45 Ethernet interface.
The safety-related logic of the MSI 400 system works independently of the gateway. However, if the system
has been configured in such a way that non-safety-related information from the field bus can be integrated
into the logic editor, switching off the gateway may result in availability problems.
A MSI 400 gateway can only be operated on a MSI 400 system. It does not have its own power supply. A
maximum of two MSI 400 gateways can be operated simultaneously for each system.
The gateway for Modbus TCP, PROFINET IO or EtherNet/IP is integrated into the MSI 430 controller mod-
ule, while the gateways for Profibus-DP, CANopen or EtherCAT are housed in a 22.5 mm wide installation
housing for 35 mm hat rails in accordance with EN60715.
Order information: Order data [chapter 13]
3.1 Version, compatibility, and features
There are various module versions and function packages for the MSI400 product family that enable vari-
ous functions. This section will give you an overview as to which module version you will need to be able to
use a certain function or a certain device.
Tab.3.1: Versions of the gateway modules
Gateway Module name Version
EtherCAT MSI-FB-ETHERCAT A-02
PROFIBUS DP MSI-FB-PROFIBUS A-03
CANopen MSI-FB-CANOPEN A-02
Info
• You can find the module version on the type plate of the modules.
• You will find the MSI.designer software version in the main menu.
• The latest software version is available in the Internet at the following address http://www.leuze.com.
• Newer modules are backwards-compatible, which means that each module can be replaced with a
module having a higher module version.
• You can find the date of manufacture for a device on the type plate in the S/N field in the format
<Product no.>yywwnnnnn (yy = year, ww = calendar week).

Product description
Leuze electronic MSI 400 14
3.2 Equipment variants
There are three MSI 400 gateways for various network types.
The Modbus TCP / PROFINET IO and EtherNet/IP gateway of the MSI 430 controller module or the ex-
ternal MSI-FB-ETHERCAT gateway are suitable for Ethernet networks. The MSI-FB-PROFIBUS gateway
and the MSI-FB-CANOPEN gateway are external field bus gateways without an Ethernet function.
WARNING
Restrictions for Ethernet connections
ÄThe Ethernet connection can only be linked to autonomous networks or demilitarized zones
(DMZ).
ÄThe device must never be connected directly to the Internet.
ÄAlways use secure data tunnels (VPN) to exchange data via the Internet.
Tab.3.2: Equipment variants and their main characteristics
Gateway Network type Ethernet IP socket interface
MSI-EN-MOD Modbus TCP with master and
slave operation
Client/Server on TCP Port 502
MSI-EN-PN PROFINET IO device UDP ports 34964, 49152
MSI-EN-IP EtherNet/IP device TCP port 44818, UDP port 2222
MSI-FB-PROFIBUS PROFIBUS DP slave - -
MSI-FB-CANOPEN CANopen slave - -
MSI-FB-ETHERCAT EtherCAT slave - -
NOTICE
i
You will find the manufacturing date of a device on the type label in the S/N field in the format
yywwnnnn (yy = year, ww = calendar week, nnnn = sequential serial number within a calendar
week).
3.3 Data transferred to the network (network input data sets)
Available data
The MSI 400 gateways can provide the following data:
• Operating data
•Logic results from the MSI 400 safety controller (see Routing table [chapter 5.1.3])
•Input values (HIGH/LOW) for all MSI 400 input expansion modules in the system
•Output values (HIGH/LOW) for all MSI 400 input/output expansion modules (see Module state / in-
put and output values [chapter 3.3.1])
•Output data from another network, i.e. data received from a second gateway in the MSI 400 sys-
tem (see Transmission of data from a second network [chapter 3.3.3])
• Diagnostics
•Test values (CRCs): (see Configuration test values (CRCs) [chapter 3.3.4])
•Error and state information: Error and state information for the modules [chapter 3.3.5]
Data sets
The physical modules are not presented as typical hardware modules in the network. Instead, the data
provided by the MSI 400 system has been arranged in four input data sets.
•Data set1 (max. 50 bytes) contains the operating data. It can be compiled with the aid of MSI.de-
signer. In the form in which it is delivered, the content of data set 1 is preconfigured; it can be freely
modified.
Details: see table "Overview of input data sets" [chapter 3.3]

Product description
Leuze electronic MSI 400 15
For the MSI-FB-PROFIBUS gateway, data set 1 was divided into five input data blocks, with data
blocks 1–4 each containing 12 bytes and data block 5 two bytes.
For the MSI-FB-CANOPEN gateway, data set 1 was divided into four blocks, each with 8 bytes.
You will find more detailed information in the corresponding section for each gateway.
•Data set 2 (32 bytes) contains the test values (CRCs) for the system configuration.
See table "Overview of input data sets 1-3 (basic settings for Modbus TCP)" below
•Data set 3 (60 bytes) contains the state and diagnostic data for the various modules, with four (4) bytes
per module, with the controller module comprising 3 x 4 bytes. Details: see table "Meaning of module
state bits" [chapter 3.3.5]
•Data set 4 (60 bytes) is currently filled with reserved values.
The following table provides an overview of which data sets are provided by which gateway.
Tab.3.3: Availability of data sets 1–4
Data set 1 Data set 2 Data set 3 Data set 4
MSI 430 Modbus TCP
PROFINET IO
EtherNet/IP
Modbus TCP
PROFINET IO
EtherNet/IP
Modbus TCP
PROFINET IO
EtherNet/IP
Modbus TCP
PROFINET IO
MSI-FB-ETHER-
CAT
EtherCAT EtherCAT EtherCAT -
MSI-FB-PROFIBUS PROFIBUS DP – – –
MSI-FB-CANOPEN CANopen CANopen (SDOs)1) CANopen (SDOs)1) –
1) The MSI-FB-CANOPEN is used to provide diagnostic data via CANopen SDO (service data objects).
More information about how to provide state and diagnostic data with the aid of the CANopen gateway
may be found here: CANopen gateway [chapter 10]
2) Readable with instance 2 of class 120
3) Readable with instance 3 of class 120 and byte 52 to 111 of assembly 167
Tab.3.4: Overview of input data sets 1–3 (basic setting for Modbus TCP)
Data set 1 Data set 2 Data set 3 Data set 4
Byte 0 Input values for Module 0
(I1..I8)
Project CRC Module state MSI 4xx Reserved
Byte 1 Input values for Module 0
(I9..I16)
Module state MSI 4xx
Byte 2 Input values for Module 0
(IQ1..IQ4)
Test pulse comparison, control-
ler module inputs
Byte 3 Output values for Module 0
(Q1..Q4, IQ1..IQ4)
Test pulse comparison, control-
ler module inputs
Byte 4 Direct data (Off) 0 System CRC
(PROFIBUS
DP and Eth-
erCAT)
Test pulse comparison, control-
ler module inputs
Byte 5 Direct data (Off) 1 State of two-channel controller
module inputs
Byte 6 Direct data (Off) 2 State of two-channel controller
module inputs
Byte 7 Direct data (Off) 3 Reserved

Product description
Leuze electronic MSI 400 16
Data set 1 Data set 2 Data set 3 Data set 4
Byte 8 Direct data (Off) 4 Reserved Stuck-at error at controller mod-
ule outputs
Reserved
Byte 9 Direct data (Off) 5 Stuck-at error at controller mod-
ule outputs
Byte
10
Direct data (Off) 6 Reserved
Byte
11
Direct data (Off) 7 Reserved
Byte
12
Input values for Module 1 State of Module 1
Byte
13
Input values for Module 2 State of Module 1
Byte
14
Input values for Module 3 State of Module 1
Byte
15
Input values for Module 4 State of Module 1
Byte
16
Input values for Module 5 State of Module 2
Byte
17
Input values for Module 6 State of Module 2
Byte
18
Input values for Module 7 State of Module 2
Byte
19
Input values for Module 8 State of Module 2
Byte
20
Input values for Module 9 Reserved State of Module 3 Reserved
Byte
21
Input values for Module 10 State of Module 3
Byte
22
Input values for Module 11 State of Module 3
Byte
23
Input values for Module 12 State of Module 3
Byte
24
Output values for Module 1 State of Module 4
Byte
25
Output values for Module 2 State of Module 4
Byte
26
Output values for Module 3 State of Module 4
Byte
27
Output values for Module 4 State of Module 4
Byte
28
Output values for Module 5 State of Module 5
Byte
29
Output values for Module 6 State of Module 5
Byte
30
Output values for Module 7 State of Module 5
Byte
31
Output values for Module 8 State of Module 5

Product description
Leuze electronic MSI 400 17
Data set 1 Data set 2 Data set 3 Data set 4
Byte
32
Output values for Module 9 Not available State of Module 6 Reserved
Byte
33
Output values for Module 10 State of Module 6
Byte
34
Output values for Module 11 State of Module 6
Byte
35
Output values for Module 12 State of Module 6
Byte
36 …
Byte
47
Not allocated State of Module 7
…
Status of Module 9
Byte
48
State of Module 10
Byte
49
State of Module 10
Byte
50
Not available State of Module 10
Byte
51
State of Module 10
Byte
52 …
Byte
55
State of Module 11
…
Status of Module 11
Byte
56
State of Module 12
Byte
57
State of Module 12
Byte
58
State of Module 12
Byte
59
State of Module 12
Length 50 bytes 32 bytes 60 bytes 60 bytes
NOTICE
i
When two-channel input or output elements have been configured for an I/O module, only the
lowest bit constitutes the input or output state (on/off) for the corresponding element. It is repres-
ented by the tag name of the element. The highest bit represents the state of this input/output.
NOTICE
i
The input values in data set 1 do not represent the physical state at the input terminals, but the
pre-processed input values that are used for logic processing.
3.3.1 Direct gateway output values
It is possible to write values directly from the Logic view to a gateway. Four bytes have been reserved for
this purpose in the basic settings for data set 1; however, up to the total number of 50 bytes of data set 1
may be configured as direct gateway output values. You can obtain additional information at: Direct gate-
way output values [chapter 5.3].

Product description
Leuze electronic MSI 400 18
3.3.2 Module state / input and output values
The MSI 400 gateways can transmit the input and output states of all modules connected to the MSI 400
system to the network. Data set 3 contains a non-modifiable configuration. Moreover, data set 1 can be ad-
apted to contain up to 4 bytes of collective state information. Only the input and output values for data set 1
have been predefined and these can be freely adapted. You will find more detailed information in the sec-
tion on the relevant gateway, as well as in the following section: Configuration of gateways with MSI.de-
signer [chapter 5]
Module state
The MSI 400 gateways can transfer the state of the linked modules to the network. A total of 4 bytes are
available for this purpose.
Tab.3.5: Module state
Module state Size Meaning Assignment
Input data state 2 bytes One sum bit per module for the state of
the module inputs
0 = error 1 = no error
Bit 0 = MSI 4xx
Bit 1 = 1.
Extension module
Bit 2 = 2.
Expansion module … Bit
13 = 1.
Gateway Bit 14 = 2. Gate-
way Bit 15 = reserved
Output data state 2 bytes One sum bit per module for the state of
the module outputs
0 = error 1 = no error
You will find information about the meaning of the state bits at: software manual, Internal inputs for control-
ler modules
Input and output values for the modules
•Input values for I/O modules
1 byte for data set 1 is available for every expansion module. The input values show the state of the
preliminary evaluation of the I/O module. This corresponds to the state of the element in the controller
module logic. The level at the associated terminal cannot be clearly detected from this, as the data may
be set to low, irrespectively of the level at the input terminal, by means of the cross-connection detec-
tion or two-channel evaluation (e.g. I1-18).
When two-channel input elements have been configured for an I/O module, only the lower-value bit
represents the pre-evaluation state of the corresponding element (e.g. bit 0 for I1 and I2, bit 2 for I3 and
I4, bit 4 for I5 and I6, bit 6 for I7 and I8). The higher-value bit (bit 1, 3, 5 and 7) is used as follows in this
case:
0 = error 1 = no error
•Output values for I/O modules
1 byte for data set 1 is available for every module with outputs. The output values indicate the state of
the control information from the logic of the controller module for the relevant element of the I/O mod-
ule. The level of the associated terminals cannot be clearly detected from this, as the output may be
switched off via the cross-connection detection or the overload connection function.
When two-channel output elements have been configured for an I/O module, only the lower-value bit
represents the control information (e.g. bit 0 for Q1 and Q2, bit 2 for Q3 and Q4, bit 4 for Q5 and Q6, bit
6 for Q7 and Q8). The higher-value bit (bit 1, 3, 5 and 7) is not used as follows in this case (low):
3.3.3 Transmission of data from a second network
If your MSI 400 system contains two gateways, it is possible to forward information which the first gateway
receives from a network (e.g. from a Modbus PLC) via the second gateway to a second network (e.g. to a
PROFIBUS master) and vice versa.
3.3.4 Configuration test values (CRCs)
Data set 2 contains the following configuration check values of the MSI 400 system:
• Project CRC of the project file created with MSI.designer
• System-CRC, uniquely assigned to a module version, consisting of internal software and hardware ver-
sion

Product description
Leuze electronic MSI 400 19
The CRCs are each 4 bytes in length. Data set 2 can be read only.
The project CRC with Modbus/TCP is transmitted in Big Endian format.
The system CRC is available from module version B-01.01 for PROFIBUS DP and EtherCAT.
3.3.5 Error and state information for the modules
Data set 3 and 4 contain the state information for the modules that will be transferred to the network.
Ten bytes are transmitted for MSI 4xx controller module. For each MSI-EM-I8 and MSI-EM-IO84 I/O mod-
ule, four bytes are transmitted in the Little Endian format, e.g. as a 32-bit word, with the first byte being
placed into the least significant byte of the whole number (extreme left) and the fourth byte into the most
significant byte of the whole number (extreme right).
Data sets 3 and 4 cannot be adapted.
Module status bits of the controller module MSI 4xx
The module state bits have the following meaning, if not otherwise indicated:
0 = error
1 = no error
Reserved bits have the value 1
NOTICE
i
You can find an explanation of the technical terms used below here: Abbreviations and Defini-
tions [chapter 1.5]
Tab.3.6: Meaning of module state bits of controller module MSI 4xx (only for Modbus)
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 B2 status Collective
error fast
shut-off
B1 status Configura
tion state
A1 status External
module
state
Internal
module
state
Reserved
Byte 1 Module
state out-
put data
Module
state of
input data
Reserved Reserved IQ3+IQ4
power re-
quirement
0: Over-
current
1: no
overcur-
rent
IQ1+IQ2
power re-
quirement
0: Over-
current
1: no
overcur-
rent
Q3+Q4
power re-
quirement
0: Over-
current
1: no
overcur-
rent
Q1+Q2
power re-
quirement
0: Over-
current
1: no
overcur-
rent
Byte 2 I8 vs.
T2/4 test
pulse
compar-
ison
I7 vs.
T1/3 test
pulse
compar-
ison
I6 vs.
T2/4 test
pulse
compar-
ison
I5 vs.
T1/3 test
pulse
compar-
ison
I4 vs.
T2/4 test
pulse
compar-
ison
I3 vs.
T1/3 test
pulse
compar-
ison
I2 vs.
T2/4 test
pulse
compar-
ison
I1 vs.
T1/3 test
pulse
compar-
ison
Byte 3 I16 vs.
T2/4 test
pulse
compar-
ison or
HW limit
frequency
I16
I15 vs.
T1/3 test
pulse
compar-
ison or
HW limit
frequency
I15
I14 vs.
T2/4 test
pulse
compar-
ison or
HW limit
frequency
I14
I13 vs.
T1/3 test
pulse
compar-
ison or
HW limit
frequency
I13
I12 vs.
T2/4 test
pulse
compar-
ison
I11 vs.
T1/3 test
pulse
compar-
ison
I10 vs.
T2/4 test
pulse
compar-
ison
I9 vs.
T1/3 test
pulse
compar-
ison
Byte 4 0: Cable
break at
I16
1: OK or
not used
0: Cable
break at
I15
1: OK or
not used
0: Cable
break at
I14
1: OK or
not used
0: Cable
break at
I13
1: OK or
not used
IQ4 vs.
T2/4 test
pulse
compar-
ison
IQ3 vs.
T1/3 test
pulse
compar-
ison
IQ2 vs.
T2/4 test
pulse
compar-
ison
IQ1 vs.
T1/3 test
pulse
compar-
ison

Product description
Leuze electronic MSI 400 20
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 5 I15/I16
dual-
channel
state
0: Error
1: ok or
not used
I13/I14
dual-
channel
state
0: Error
1: ok or
not used
I11/I12
dual-
channel
state
0: Error
1: ok or
not used
I9/I10
dual-
channel
state
0: Error
1: ok or
not used
I7/I8
dual-
channel
state
0: Error
1: ok or
not used
I5/I6
dual-
channel
state
0: Error
1: ok or
not used
I3/I4
dual-
channel
state
0: Error
1: ok or
not used
I1/I2
dual-
channel
state
0: Error
1: ok or
not used
Byte 6 0: Inver-
sion error
I14 vs. I16
1: OK or
not used
0: Inver-
sion error
I13 vs. I15
1: OK or
not used
0: Fre-
quency
difference
I14 vs. I16
1: OK or
not used
0: Fre-
quency
difference
I13 vs. I15
1: OK or
not used
0: Phase
difference
I14 vs. I16
too low
1: OK or
not used
0: Phase
difference
I13 vs. I15
too low
1: OK or
not used
IQ3/IQ4
dual-
channel
state
0: Error
1: ok or
not used
IQ1/IQ2
dual-
channel
state
0: Error
1: ok or
not used
Byte 7 0: I16
Stuck at
low
1: OK or
not used
0: I16
Stuck at
high
1: OK or
not used
0: I15
Stuck at
low
1: OK or
not used
0: I15
Stuck at
high
1: OK or
not used
0: I14
Stuck at
low
1: OK or
not used
0: I14
Stuck at
high
1: OK or
not used
0: I13
Stuck at
low
1: OK or
not used
0: I13
Stuck at
high
1: OK or
not used
Byte 8 Q4
Stuck at
low
Q4
Stuck at
high
Q3
Stuck at
low
Q3
Stuck at
high
Q2
Stuck at
low
Q2
Stuck at
high
Q1
Stuck at
low
Q1
Stuck at
high
Byte 9 IQ4 (Out-
put)
Stuck at
low
IQ4 (Out-
put)
Stuck at
high
IQ3 (Out-
put)
Stuck at
low
IQ3 (Out-
put)
Stuck at
high
IQ2 (Out-
put)
Stuck at
low
IQ2 (Out-
put)
Stuck at
high
IQ1 (Out-
put)
Stuck at
low
IQ1 (Out-
put)
Stuck at
high
Module state bits of the I/O modules MSI-EM-I8 and MSI-EM-IO84
The module state bits have the following meaning, if not otherwise indicated:
0 = error
1 = no error
Tab.3.7: Meaning of the module state bits of the safe I/O modules MSI-EM-I8 and MSI-EM-IO84
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 Reserved Collective
error fast
shut-off
Power
supply for
Q1 .. Q4
Configur-
ation of
this mod-
ule is
valid.
Not used
(error his-
tory flag)
External
module
state
Internal
module
state
Not used
("execut-
ing state")
Byte 1 Module
state of
output
data
Module
state of
input data
Reserved Reserved Two-
channel
evaluation
of input
I7–I8
Two-
channel
evaluation
of input
I5–I6
Two-
channel
evaluation
of input
I3–I4
Two-
channel
evaluation
of input
I1–I2
Byte 2 Test im-
pulse
compar-
ison I8 vs.
X2
Test im-
pulse
compar-
ison I7 vs.
X1
Test im-
pulse
compar-
ison I6 vs.
X2
Test im-
pulse
compar-
ison I5 vs.
X1
Test im-
pulse
compar-
ison I4 vs.
X2
Test im-
pulse
compar-
ison I3 vs.
X1
Test im-
pulse
compar-
ison I2 vs.
X2
Test im-
pulse
compar-
ison I1 vs.
X1