How it Works
Leuze electronic
Loading...
MSI-EN-IP
Series Manual
179 pgs5.6 Mb0
Table of contents
Loading...

Leuze electronic MSI 400, MSI-EN-PN, MSI-FB-PROFIBUS, MSI-EN-MOD, MSI-FB-CANOPEN Series Manual

...
Download
Page 1
MSI 400
Gateways
EN 2019/03 - 50134715
We reserve the right to
make technical changes
T r a n s l a t i o n o f t h e o r i g i n a l o p e r a t i n g i n s t r u c t i o n s
Page 2
© 2019 Leuze electronic GmbH & Co. KG In der Braike 1 D-73277 Owen / Germany Phone: +49 7021 573-0 Fax: +49 7021 573-199 http://www.leuze.com info@leuze.de
Leuze electronic MSI 400 2
Page 3

Table of Contents

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
Leuze electronic MSI 400 3
Page 4
Table of Contents
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
Leuze electronic MSI 400 4
Page 5
Table of Contents
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
Leuze electronic MSI 400 5
Page 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.
About this manual

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.
Leuze electronic MSI 400 6
Page 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.
About 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
Leuze electronic MSI 400 7
Page 8
About this manual
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
Leuze electronic MSI 400 8
Page 9
About this manual
i
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
These are notes that provide you with information regarding particularities of a device or a soft­ware function.
Leuze electronic MSI 400 9
Page 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.
About this manual
Subject to change.
Subject to technical changes for reasons of continued development.
Leuze electronic MSI 400 10
Page 11

2 Safety

i
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.
Safety
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
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.
Leuze electronic MSI 400 11
Page 12
NOTICE
i
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).
Safety
NOTICE
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
Leuze electronic MSI 400 12
Page 13

3 Product description

i
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
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.
Product description
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).
Leuze electronic MSI 400 13
Page 14

3.2 Equipment variants

i
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
Product description
MSI-EN-MOD Modbus TCP with master and
slave operation
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
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]
Client/Server on TCP Port 502
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]
Leuze electronic MSI 400 14
Page 15
Product description
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
MSI-FB-ETHER-
EtherCAT EtherCAT EtherCAT -
Modbus TCP
PROFINET IO
EtherNet/IP
Modbus TCP
PROFINET IO
EtherNet/IP
Modbus TCP
PROFINET IO
CAT
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
Project CRC Module state MSI 4xx Reserved
(I1..I8)
Byte 1 Input values for Module 0
Module state MSI 4xx
(I9..I16)
Byte 2 Input values for Module 0
(IQ1..IQ4)
Byte 3 Output values for Module 0
(Q1..Q4, IQ1..IQ4)
Byte 4 Direct data (Off) 0 System CRC
(PROFIBUS
Byte 5 Direct data (Off) 1 State of two-channel controller
DP and Eth­erCAT)
Test pulse comparison, control­ler module inputs
Test pulse comparison, control­ler module inputs
Test pulse comparison, control­ler module inputs
module inputs
Byte 6 Direct data (Off) 2 State of two-channel controller
module inputs
Byte 7 Direct data (Off) 3 Reserved
Leuze electronic MSI 400 15
Page 16
Product description
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
Byte 9 Direct data (Off) 5 Stuck-at error at controller mod-
ule outputs
Byte10Direct data (Off) 6 Reserved
Byte11Direct data (Off) 7 Reserved
Byte12Input values for Module 1 State of Module 1
Byte13Input values for Module 2 State of Module 1
Byte14Input values for Module 3 State of Module 1
Byte15Input values for Module 4 State of Module 1
Byte16Input values for Module 5 State of Module 2
Byte17Input values for Module 6 State of Module 2
Reserved
Byte18Input values for Module 7 State of Module 2
Byte19Input values for Module 8 State of Module 2
Byte20Input values for Module 9 Reserved State of Module 3 Reserved
Byte21Input values for Module 10 State of Module 3
Byte22Input values for Module 11 State of Module 3
Byte23Input values for Module 12 State of Module 3
Byte24Output values for Module 1 State of Module 4
Byte25Output values for Module 2 State of Module 4
Byte26Output values for Module 3 State of Module 4
Byte27Output values for Module 4 State of Module 4
Byte28Output values for Module 5 State of Module 5
Byte29Output values for Module 6 State of Module 5
Byte30Output values for Module 7 State of Module 5
Byte31Output values for Module 8 State of Module 5
Leuze electronic MSI 400 16
Page 17
Product description
i
i
Data set 1 Data set 2 Data set 3 Data set 4
Byte32Output values for Module 9 Not available State of Module 6 Reserved
Byte33Output values for Module 10 State of Module 6
Byte34Output values for Module 11 State of Module 6
Byte35Output values for Module 12 State of Module 6
Byte 36 …
Byte 47
Byte 48
Byte 49
Byte50Not available State of Module 10
Byte 51
Byte 52 … Byte 55
Byte 56
Byte 57
Byte 58
Not allocated State of Module 7
…
Status of Module 9
State of Module 10
State of Module 10
State of Module 10
State of Module 11
…
Status of Module 11
State of Module 12
State of Module 12
State of Module 12
Byte 59
Length 50 bytes 32 bytes 60 bytes 60 bytes
NOTICE
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
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].
State of Module 12
Leuze electronic MSI 400 17
Page 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
Product description
Input data state 2 bytes One sum bit per module for the state of
the module inputs
0 = error 1 = no error
Output data state 2 bytes One sum bit per module for the state of
the module outputs
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
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
Leuze electronic MSI 400 18
Page 19
The CRCs are each 4 bytes in length. Data set 2 can be read only.
i
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
Product description
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
Byte 1 Module
state out­put data
Byte 2 I8 vs.
T2/4 test pulse compar­ison
Module state of input data
I7 vs. T1/3 test pulse compar­ison
B1 status Configura
tion state
Reserved Reserved IQ3+IQ4
I6 vs. T2/4 test pulse compar­ison
I5 vs. T1/3 test pulse compar­ison
A1 status External
power re­quirement 0: Over­current 1: no overcur­rent
I4 vs. T2/4 test pulse compar­ison
module state
IQ1+IQ2 power re­quirement 0: Over­current 1: no overcur­rent
I3 vs. T1/3 test pulse compar­ison
Internal module state
Q3+Q4 power re­quirement 0: Over­current 1: no overcur­rent
I2 vs. T2/4 test pulse compar­ison
Reserved
Q1+Q2 power re­quirement 0: Over­current 1: no overcur­rent
I1 vs. T1/3 test pulse compar­ison
Byte 3 I16 vs.
T2/4 test pulse compar­ison or HW limit frequency I16
Byte 4 0: Cable
break at I16
1: OK or not used
Leuze electronic MSI 400 19
I15 vs. T1/3 test pulse compar­ison or HW limit frequency I15
0: Cable break at I15
1: OK or not used
I14 vs. T2/4 test pulse compar­ison or HW limit frequency I14
0: Cable break at I14
1: OK or not used
I13 vs. T1/3 test pulse compar­ison or HW limit frequency I13
0: Cable break at I13
1: OK or not used
I12 vs. T2/4 test pulse compar­ison
IQ4 vs. T2/4 test pulse compar­ison
I11 vs. T1/3 test pulse compar­ison
IQ3 vs. T1/3 test pulse compar­ison
I10 vs. T2/4 test pulse compar­ison
IQ2 vs. T2/4 test pulse compar­ison
I9 vs. T1/3 test pulse compar­ison
IQ1 vs. T1/3 test pulse compar­ison
Page 20
Product description
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
Byte 6 0: Inver-
sion error I14 vs. I16
1: OK or not used
Byte 7 0: I16
Stuck at low
1: OK or not used
Byte 8 Q4
Stuck at low
Byte 9 IQ4 (Out-
put) Stuck at low
I13/I14 dual­channel state 0: Error 1: ok or not used
0: Inver­sion error I13 vs. I15
1: OK or not used
0: I16 Stuck at high
1: OK or not used
Q4 Stuck at high
IQ4 (Out­put) Stuck at high
I11/I12 dual­channel state 0: Error 1: ok or not used
0: Fre­quency difference I14 vs. I16
1: OK or not used
0: I15 Stuck at low
1: OK or not used
Q3 Stuck at low
IQ3 (Out­put) Stuck at low
I9/I10 dual­channel state 0: Error 1: ok or not used
0: Fre­quency difference I13 vs. I15
1: OK or not used
0: I15 Stuck at high
1: OK or not used
Q3 Stuck at high
IQ3 (Out­put) Stuck at high
I7/I8 dual­channel state 0: Error 1: ok or not used
0: Phase difference I14 vs. I16 too low
1: OK or not used
0: I14 Stuck at low
1: OK or not used
Q2 Stuck at low
IQ2 (Out­put) Stuck at low
I5/I6 dual­channel state 0: Error 1: ok or not used
0: Phase difference I13 vs. I15 too low
1: OK or not used
0: I14 Stuck at high
1: OK or not used
Q2 Stuck at high
IQ2 (Out­put) Stuck at high
I3/I4 dual­channel state 0: Error 1: ok or not used
IQ3/IQ4 dual­channel state 0: Error 1: ok or not used
0: I13 Stuck at low
1: OK or not used
Q1 Stuck at low
IQ1 (Out­put) Stuck at low
I1/I2 dual­channel state 0: Error 1: ok or not used
IQ1/IQ2 dual­channel state 0: Error 1: ok or not used
0: I13 Stuck at high
1: OK or not used
Q1 Stuck at high
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-
Not used (error his­tory flag)
External module state
Internal module
state ule is valid.
Byte 1 Module
state of output data
Byte 2 Test im-
pulse compar­ison I8 vs. X2
Module state of input data
Test im­pulse compar­ison I7 vs. X1
Reserved Reserved Two-
channel evaluation of input I7–I8
Test im­pulse compar­ison I6 vs. X2
Test im­pulse compar­ison I5 vs. X1
Test im­pulse compar­ison I4 vs. X2
Two­channel evaluation of input I5–I6
Test im­pulse compar­ison I3 vs. X1
Two-
channel
evaluation
of input
I3–I4
Test im-
pulse
compar-
ison I2 vs.
X2
Not used ("execut­ing state")
Two­channel evaluation of input I1–I2
Test im­pulse compar­ison I1 vs. X1
Leuze electronic MSI 400 20
Page 21
Product description
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 3 Q4 Stuck-
at low 0: Stuck­at error 1: no stuck-at
Q4 Stuck­at high 0: Stuck­at error 1: no stuck-at
Q3 Stuck­at low 0: Stuck­at error 1: no stuck-at
Q3 Stuck­at high 0: Stuck­at error 1: no stuck-at
Q2 Stuck­at low 0: Stuck­at error 1: no stuck-at
Q2 Stuck­at high 0: Stuck­at error 1: no stuck-at
Q1 Stuck-
at low
0: Stuck-
at error
1: no
stuck-at
Q1 Stuck­at high 0: Stuck­at error 1: no stuck-at
Module state bits of the MSI-EM-IO84NP I/O module
The module state bits have the following meaning if not otherwise indicated; normally only the first byte of the total state is transmitted:
0 = error
1 = no error or reserved
Tab.3.8: Meaning of the module state bits of the MSI-EM-IO84NP expansion module
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 Reserved Reserved Power
supply Y1-Y4
Configur­ation state
Not used (error his­tory flag)
External module state
Internal
module
state
Not used ("execut-
ing state") and IY5­IY8
Byte 1 Module
state out­put data
Module state input data
Reserved Reserved Reserved Reserved Reserved Reserved
Byte 2 Reserved
Byte 3 Reserved
Module state bit of the gateways
The module state bits have the following meaning if not otherwise indicated; normally only the first byte of the total state is transmitted:
0 = error
1 = no error
Tab.3.9: Meaning of gateway module state bits
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Byte 0 Reserved Module
state out­put data
Module state in­put data
Configur­ation state
Not used (error his­tory flag)
Reserved Internal
module state
Not used ("execut­ing state")
Byte 1 Reserved
Byte 2 Reserved
Byte 3 Reserved
Example
Module 2 (MSI-EM-IO84) has a short-circuit after high (24 V) at output 3. The following module state is transmitted to the network (only the first 20 of 60 bytes are shown):
Byte address 00 01 02…031104120513061407150816091710181119…
Byte 3
Leuze electronic MSI 400 21
0
2 1 1
…
0
3 0 2 1 1 2 0 3 3 0 2
11
1 2 0 3 …
1
Page 22
Product description
i
Byte address 00 01 02…031104120513061407150816091710181119…
Value FF FF FF FF FF FF FF FF EF
FB
Meaning Status of controller mod-
ule
The first relevant byte for the module 2 error described above is module state byte 0 for module 2. This is byte 11 with the hexadecimal value FB (1111 1011):
Bit # 7 6 5 4 3 2 1 0
Value 1 1 1 1 1 0 1 1
This corresponds to the error message "Summary of bits 0.5 to 0.7 (external error)", byte 0, bit 2 in the fol­lowing table: "Meaning of module state bits of the secure I/O modules" [chapter 3.3.5]
The second relevant byte is the module state byte 3 for module 2. This is byte 08 with the hexadecimal value EF (1110 1111):
Bit # 7 6 5 4 3 2 1 0
Value 1 1 1 0 1 1 1 1
This corresponds to the error message "Short circuit monitoring of output 3, short circuit after high", byte 3, bit 4 in the following table: "Meaning of module state bits of the secure I/O modules" [chapter 3.3.5]
NOTICE
Ä Reserved (for future use) = static 1 (no state change) Ä Not used (can be 0 or 1 ), both values occur. Ä If there is no module, all values - including the reserved values - are set to logical 1.
Status of module 1 (MSI­EM-IO84)
State of module 2 (MSI­EM-IO84)
FF FF FB
EF
…
…
Leuze electronic MSI 400 22
Page 23

3.4 Data received from the network (network output data sets)

i
The data from data set 1 (max. 50 bytes) received from the network may be differently arranged, depend­ing on the protocol. For the Modbus TCP, this data set was divided into five data blocks, each with 10 bytes. In the MSI-FB-PROFIBUS gateway, output data blocks 1-4 each contain 12 bytes, while output data block 5 contains 2 bytes. CANopen only defines 4 data blocks, each with 8 bytes.
Tab.3.10: Output data block 1–5 of the various gateways
Size of output data block
Gateway Block 1 Block 2 Block 3 Block 4 Block 5
Product description
MSI-FB-PROFIBUS / PROFINET IO
MSI-FB-CANOPEN 8 bytes 8 bytes 8 bytes 8 bytes –
MSI-FB-ETHERCAT / Modbus TCP / EtherNet/IP
The content of the output data blocks can be used in the logic editor, as well as made available for another network via a second gateway within the MSI 400 system.
NOTICE
Ä In order to use network data in the logic editor or as input for another network, you must as-
sign a tag name for each bit to be used.
Ä Bits without specific tag names will not be available in the logic editor or for routing via a
second gateway. Detailed information about how to assign tag names for the data received may be found in the corresponding sections of the chapters on the various gateways.
Ä You can monitor current communication with the network with the aid of input data state bits
for receiving data from the network and the output data state bit for transmitting data to the network in the logic editor. When the gateway detects a communication error, both the con­tent of the data sets and the associated state bit are set to zero (logical 0).
Ä When all communication fails, the data of the output data sets and the input data state bit
are set to zero (logical 0).
Ä When a connection is closed while others remain available, the LED MS or LED state will
flash red/green for a total of 10 seconds and an entry will be made in the error log. In this case the state bits are not affected.
12 bytes 12 bytes 12 bytes 12 bytes 2 bytes
10 bytes 10 bytes 10 bytes 10 bytes 10 bytes
WARNING
Do not use the same output data block number for two different PLC connections or TCP/ IP sockets!
The output data block of the Ethernet gateways can be described in parallel via all communica­tion interfaces or TCP/IP sockets (e.g. Modbus TCP/IP and Ethernet TCP/IP) if they make use of the same output data block number. In this case the last message will always overwrite the data received earlier.
Leuze electronic MSI 400 23
Page 24

4 Installation and basic configuration

4.1 Installing/removing

4.1.1 Installing modules on hat rail

WARNING
This is only for switch boxes with protection class IP 54 or higher!
The MSI 400 system is only suitable for installations in a switchbox having at least protection class IP 54.
Notes
• Basic safety Gateways and extension modules may not be removed or added when the operating voltage is switched on.
• Grounding The hat rail must be conductively connected to the protective conductor (PE).
• ESD protection measures Note the suitable ESD protection measures during installation. Failure to do so could result in damage to the internal safety bus.
• Protect connector openings Undertake suitable measures so that no foreign bodies can penetrate connector openings, particularly those for the program removable storage.
• Module width: The modules are placed in a mounting box that is 22.5 mm or 45 mm wide depending on type.
• Quality of hat rail The mounting boxes are suitable for 35 mm hat rails as per EN60715.
• Sequence of modules: The MSI 400 system has the controller module on the far left. The two optional gateways follow directly to the right next to the controller module. The expansion modules only follow thereafter.
• Save space for subsequent model replacement The modules are connected via the plug connection integrated into the housing. Note that the MSI 400 modules must be pulled about 10 mm apart before a module replacement so that the corresponding module can be removed from the hat rail.
• Standards to be considered Installation according to EN50274
Installation and basic configuration
Step 1: Installing a controller module
Ä Using a screwdriver, pull the snap-on foot outward.
Ä Hang the module on the hat rail.
Important! Make sure that the shielding spring fits correctly. The shielding spring of the module must be placed onto the hat rail so that it is secure and has good electrical contact.
Leuze electronic MSI 400 24
Page 25
Ä Fold the module onto the hat rail.
Installation and basic configuration
Ä Using a screwdriver, move the snap-on foot against the hat rail until the snap-on foot latches into posi-
tion with an audible click.
Ä Make sure that the module is securely seated on the hat rail.
Attempt to pull the module from the hat rail using slight pressure. If the module stays connected to the hat rail during this test, then the installation is correct.
Step 2: Installation of gateways or expansion modules
Ä Using a screwdriver, pull the snap-on foot outward.
Ä Hang the module on the hat rail.
Important! Make sure that the shielding spring fits correctly. The shielding spring of the module must be placed onto the hat rail so that it is secure and has good electrical contact.
Leuze electronic MSI 400 25
Page 26
Ä Fold the module onto the hat rail.
Installation and basic configuration
Ä Using a screwdriver, move the snap-on foot against the hat rail until the snap-on foot latches into posi-
tion with an audible click.
Ä Make sure that the module is securely seated on the hat rail.
Attempt to pull the module from the hat rail using slight pressure. If the module stays connected to the hat rail during this test, then the installation is correct.
Ä If you are installing multiple modules:
Push the individual modules together in the direction of the arrow until the lateral plug connection between the modules audibly latches into position.
Ä Install an end terminal into the module furthest to the left and another end terminal into the module fur-
thest to the right.
After installation
Once you have installed the modules, the following steps are required:
Leuze electronic MSI 400 26
Page 27
• Connect the modules electrically.
• Configure modules (see: software manual).
• Check the installation before first commissioning.
Installation and basic configuration
Leuze electronic MSI 400 27
Page 28

4.1.2 Removing modules from the hat rail

End terminal
End terminal
Plug-in terminal
Step 1: Removing a controller module
Ä Deenergize the MSI 400 system. Ä Remove plug-in terminals with wiring and remove the end terminal.
Installation and basic configuration
Ä If expansion modules or gateways are used:
Slide the controller module in the direction of the arrow until the lateral plug connection is disconnected.
Ä Unlock the module.
To do this, pull the snap-on foot of the module outward using a screwdriver.
Ä Fold the module away from the hat rail and remove it from the rail.
Step 2: Removing gateways and expansion modules
Ä Deenergize the MSI 400 system. Ä Remove any plug-in terminals with wiring and remove the end terminals.
Leuze electronic MSI 400 28
Page 29
Installation and basic configuration
End terminal End terminal
Plug-in terminal
Ä Pull the modules apart from one another individually in the direction of the arrow until the lateral plug
connection is disconnected.
Ä Unlock the module.
To do this, pull the snap-on foot of the module outward using a screwdriver.
Ä Fold the module away from the hat rail and remove it from the rail.

4.2 Electrical installation

Switch off the power supply to the system!
It is possible for the system to be unexpectedly started while you are connecting the devices.
WARNING
Leuze electronic MSI 400 29
Page 30
Installation and basic configuration
i
NOTICE
Ä MSI 400 gateways meet EMC conditions as set out in the EN 61000-6-2 specification for
use in an industrial environment.
Ä In order to ensure complete EMC safety, the hat rail must be connected to functional earth
(FE).
Ä The switch box or installation housing for the MSI 400 system must meet at least the re-
quirements of protection class IP 54.
Ä Installation according to EN 50274. Ä Electrical installation as per EN 60204-1. Ä The external power supply of the devices must be able to bridge a short-term power outage
of 20 ms in accordance with EN 60204-1.
Ä The power supply must meet the regulations for low-voltage with safe disconnection (SELV,
PELV) in accordance with EN60664 and EN50178 (equipping high-voltage systems with electronic equipment).
Ä Ensure that all modules of the MSI 400 system, the connected protective devices and the
power supplies are connected to the same ground connection. The ground of the RS‑232 in­terface is internally connected to the ground of the power supply for the controller module (A2).
Ä Connect the shielding of all field bus and Ethernet cables to functional earth (FE) just before
they lead into the switch box.

4.3 Initial configuration steps

How do you configure gateways? This chapter provides some brief guidelines.
Tab.4.1: Guidelines for gateway configuration
Step Description
1 Establishing a link between the gateway and PC
See here for more detailed information: Software manual, chapter "Connecting to the safety controller"
2 Configure gateway
You will find detailed information in this regard at the following points in the gateway manual:
• Modbus TCP gateway [chapter 6]
• PROFINET IO-Gateway [chapter 7]
• EtherNet/IP gateway [chapter 8]
• PROFIBUS DP gateway [chapter 9]
• CANopen gateway [chapter 10]
• EtherCAT Gateway [chapter 11]
3 Transmitting and verifying the configuration
See here for more detailed information: Software manual, chapter "Transferring the system configuration"
Leuze electronic MSI 400 30
Page 31

5 Configuration of gateways with MSI.designer

i
This chapter gives you an overview of how to configure gateways in MSI.designer. It explains
• how the graphical user interface is laid out for the gateway configuration inMSI.designer,
• how you can carry out typical configuration tasks connected to gateways in MSI.designer.
NOTICE
You will find more detailed information about the graphical user interface of MSI.designer in the Software manual.

5.1 The graphical user interface

You can edit the configuration for gateways in the graphical user interface of MSI.designer in the following windows:
Window Brief explanation
Gateway view Depending on module configuration, shows two or three tabs
with the routing tables and additional gateway functionalities.
Details: Layout and content of the tabs [chapter 5.1.3]
Configuration of gateways with MSI.designer
Gateway docking window Show inputs and outputs available for the gateway configura-

5.1.1 Activating gateway functionality

The Gateway view is only available in MSI.designer when you actively use the gateway functionality. Ba­sically you can set up the gateway functionality in two ways:
Scenario 1: You are using a gateway module
You implement the gateway functionality via a supplementary module, as indicated in the following ex­ample. Here the MSI-FB-CANOPEN module is used:
tion as a hierarchical tree structure.
Details: "Gateway” and “Properties” docking windows
[chapter 5.1.4]
Fig.5.1: Module configuration with gateway module
Leuze electronic MSI 400 31
Page 32
Configuration of gateways with MSI.designer
Scenario 2: You are using the gateway function on the module MSI 430
You implement the gateway functionality via the controller module. In this case you must use the MSI 430 module as the controller module for the controller and explicitly set the gateway functionality there.
How to activate the gateway function on the MSI 430 module:
Ä Open the Modules docking window. Ä Select the MSI 430 module.
Ä Open the Properties docking window. Ä Select the desired gateway function from the Gateway selection list.
Fig.5.2: MSI 430 module with activated gateway function

5.1.2 "Gateway" view

If you have activated the gateway functionality in MSI.designer automatically the Gateway view is active. There you can edit the gateway configuration.
Setup
Depending on module configuration, in the Gateway view, you will see two or three tabs:
Module configuration Setup
You use a gateway module for gateway configuration
In the Gateway view you see two tabs with the routing tables for the in­put and output values.
Example: MSI-FB-ETHERCAT module
Leuze electronic MSI 400 32
Page 33
Module configuration Setup
Configuration of gateways with MSI.designer
You are using the gateway function of the MSI 430 mod­ule
In the Gateway view you see an additional third tab Gateway configura- tion.
It contains the basic settings for the gateway function of the MSI 430 module:
Visualization
• If you are using several gateways
The Gateway view always only shows one gateway configuration. If you are using several gateways, you can toggle between the configurations by making use of the Select data set view menu:
• When the program window is very small
If the window in which you have opened MSI.designer is very small, not all tabs may be shown. In this case an arrow symbol will appear, allowing you to toggle between the tabs:
Commands
Via the command bar of the Gateway view, you have access to the following view-specific features:
Tab.5.1: Key
Element Description
Only with a connection to the controller: Stops the controller.
Only with a connection to the controller: Starts a stopped controller.
Zoom
This determines the size of the display in the Gateway view work area.
Undo
This renders the last action undone.
Redo
This makes an action that has been undone redone.
Standard
This resets the configuration of the gateways to the basic settings.
Also see: Basic settings for the process data [chapter 5.2.2]
Leuze electronic MSI 400 33
Page 34
Element Description
Data set view selection
When you are using several gateways: Changes between the gateway con­figurations.
Importing/exporting
Allows for the import/export of the configuration defined in the Gateway view.
Notes:
• Caution: When you import a configuration, all changes made before that have not been saved will be lost. You cannot undo this command.
• Available storage formats: SPG, XML, CSV You can use the import/export function to import the tag names used for a project into a PLC program, or to export them from a PLC program into MSI.designer.
Delete
This deletes the currently selected element.
Configuration of gateways with MSI.designer
Also see about this
2 Basic settings for the process data [}37]

5.1.3 Layout and content of the tabs

The tabs of the Gateway view contain the following data and features:
Tab 1: Routing table with output values (data bytes)
Transmission direction: MSI 400 -> Network/field bus
The mapping is shown in tabular form. Bits which have been used appear on a dark blue background. In online mode, the input data of the relevant gateway is displayed (byte display 0x00 at the start of the relev­ant line).
Fig.5.3: Routing table with output values
Tab 2: Routing table with input values (data bytes)
Transmission direction: Network/field bus -> MSI.designer
Visualization: as per Tab 1
Leuze electronic MSI 400 34
Page 35
Configuration of gateways with MSI.designer
i
Fig.5.4: Routing table with input values
Tab 3: "Gateway configuration"
Tab 3 only appears if you have activated MSI-EN-MOD or MSI-EN-IP.
Fig.5.5: "Gateway configuration" tab for MSI-EN-MOD
NOTICE
Allocation of input and output data
The output and input data listed here refer directly to the data blocks in tab 1 and tab 2.
Ä Output data group (to the PLC):
Only data set 1 can be configured. This refers directly to Output data block 1 in tab 1.
Ä Input data (from PLC) group:
Data set 1 to data set 5 refer directly to input data block 1 to input data block 5 in tab 2.

5.1.4 "Gateway” and “Properties” docking windows

In addition to the Gateway view, in the gateway configuration in MSI.designer you work with the following windows:
"Gateway” docking window
From the Gateway docking window you can drag hardware data bytes into empty cells in the routing table (Gateway view).
Leuze electronic MSI 400 35
Page 36
Configuration of gateways with MSI.designer
i
Fig.5.6: Drag data bytes into the routing table using drag & drop
NOTICE
You can make use of the same data byte several times in the routing table.
"Properties” docking window
In the Properties docking window, the configuration dialog appears for the data byte which you have selec­ted in the Gateway view.
Depending on the data byte, you can configure individual parameters. You can also allocate tag names here.
Fig.5.7: Configuration dialog in the “Properties” docking window

5.2 Function and basic settings

5.2.1 Routing

The process diagram, transferred to the network from the MSI 400 gateway, comprises the operating data (e.g. logic results, state of inputs and outputs) and the diagnostic data (e.g. module status, CRCs). This data have been arranged in 4 data sets.
Tab.5.2: Content of data sets 1–4
Data set Content Size Configurable
1 Process data 50 bytes Yes
2 CRCs 32 bytes No
3 State and diagnosis 60 bytes No
4 Reserved 60 bytes No
Leuze electronic MSI 400 36
Page 37
The process data in Data Set 1 may consist of up to 50 bytes, irrespective of the network protocol used. These 50 bytes have been divided into one or several data blocks, depending on the network protocol. De­tailed information about the modularization of the data sent to the network may be found in the section on the relevant gateway and in the following table: "Preset configuration for process data transmitted in the
network" [chapter 5.2.2]
The content of data set 1 has been pre-configured with the addition of a gateway module or a gateway function, but can be freely configured with a granularity of 1 byte (see Basic settings for process data [chapter 5.2.2] and Configuring the gateway output values (tab 1) [chapter 5.3]).
The diagnostic data in data sets 2-4 depends on the network protocol used and is described in the chapter on the relevant gateway.

5.2.2 Basic settings for the process data

After the addition of the gateway, the process data is pre-configured. Depending on the gateway used, this data is divided into several data blocks.
The following table provides an overview of which bytes have been allocated to the preset configuration and how the data at the various gateways are modularized.
Tab.5.3: Preset configuration for the process data transmitted in the network
Modbus TCP PROFIBUS DP
Configuration of gateways with MSI.designer
Byte Preset allocation Initial data
Preset allocation Initial data
set
0 Input values for Module 0
(I1..I8)
1 Input values for Module 0
(I9..I16)
2 Input values for Module 0
(IQ1..IQ4)
3 Output values for Module 0
(Q1..Q4,IQ1-IQ4)
#1 (50 bytes)
Input values for Module 0 (I1..I8)
Input values for Module 0 (I9..I16)
Input values for Module 0 (IQ1..IQ4)
Output values for Module 0 (Q1..Q4,IQ1-IQ4)
4 Direct data (Off) 0 Direct data (Off) 0
5 Direct data (Off) 1 Direct data (Off) 1
6 Direct data (Off) 2 Direct data (Off) 2
7 Direct data (Off) 3 Direct data (Off) 3
8 Direct data (Off) 4 Direct data (Off) 4
9 Direct data (Off) 5 Direct data (Off) 5
10 Direct data (Off) 6 Direct data (Off) 6
11 Direct data (Off) 7 Direct data (Off) 7
block
#1
(12 bytes)
Leuze electronic MSI 400 37
Page 38
Configuration of gateways with MSI.designer
Modbus TCP PROFIBUS DP
Byte Preset allocation Initial data
Preset allocation Initial data
set
12 Inputs for Module 1 Continued
13 Inputs for Module 2 Inputs for Module 2
#1
Inputs for Module 1 #2
(50 bytes)
14 Inputs for Module 3 Inputs for Module 3
15 Inputs for Module 4 Inputs for Module 4
16 Inputs for Module 5 Inputs for Module 5
17 Inputs for Module 6 Inputs for Module 6
18 Inputs for Module 7 Inputs for Module 7
19 Inputs for Module 8 Inputs for Module 8
20 Inputs for Module 9 Inputs for Module 9
21 Inputs for Module 10 Inputs for Module 10
22 Inputs for Module 11 Inputs for Module 11
23 Inputs for Module 12 Inputs for Module 12
24 Outputs for Module 1 Continued
25 Outputs for Module 2 Outputs for Module 2
#1
Outputs for Module 1 #3
(50 bytes)
26 Outputs for Module 3 Outputs for Module 3
block
(12 bytes)
(12 bytes)
27 Outputs for Module 4 Outputs for Module 4
28 Outputs for Module 5 Outputs for Module 5
29 Outputs for Module 6 Outputs for Module 6
30 Outputs for Module 7 Outputs for Module 7
31 Outputs for Module 8 Outputs for Module 8
32 Outputs for Module 9 Outputs for Module 9
33 Outputs for Module 10 Outputs for Module 10
34 Outputs for Module 11 Outputs for Module 11
35 Outputs for Module 12 Outputs for Module 12
36-47 Not allocated Continued
#1
48-49 Not allocated Not allocated #5
(50 bytes)
The preset allocation of the bytes can be freely configured, as shown in the following section.

5.3 Configuring the gateway output values (tab 1)

You can use the following settings for the output values of a gateway in tab 1:
Basic setting
Depending on the gateway function selected, you will find four or eight bytes in tab 1, which are reserved as direct gateway output values. You can also see these bytes in the Logic docking window.
Example: MSI-FB-CANOPEN module with eight predefined outputs for gateways:
Not allocated #4
(12 bytes)
(2 bytes)
"Logic” docking window "Gateway" view
In the Logic docking window you see
In the Gateway view these four outputs appear in the first tab:
these four bytes Outputs:
Leuze electronic MSI 400 38
Page 39
"Logic” docking window "Gateway" view
Configuration of gateways with MSI.designer
Change tag names of a predefined output value
Tag names have already been pre-assigned to the predefined output values (bytes). You can change these tag names:
Ä In the Gateway view click on the byte, whose tag name you want to change.
Ä Open the Properties docking window. Ä If you wish to change the tag name of the byte:
Overwrite the pre-allocated tag name of the byte with the desired new value in the configuration dialog.
Ä If you also want to change the tag names of individual bits:
Overwrite the pre-allocated values with the desired new value under Parameters in the configuration dialog.
In the Logic view, these bits will appear with the corresponding tag names.
Leuze electronic MSI 400 39
Page 40
Configuration of gateways with MSI.designer
Configuring additional direct gateway output values
You can add new output values (bytes) in addition to the pre-allocated output values in the Gateway view.
Ä Click on an empty byte in the Gateway view.
Ä Open the Properties docking window and assign a tag name for the byte in the configuration dialog.
ð Tag names for all bits are automatically pre-allocated under Parameters.
Ä If you also want to change the tag names of individual bits:
Overwrite the pre-allocated values with the desired new value under Parameters in the configuration dialog.
In the Logic view, these bits will appear with the corresponding tag names.

5.4 Editing the gateway input values (tab 2)

You can use the following settings for the output values of a gateway in tab 2:
Basic setting
Depending on the gateway function selected, you will find four or eight bytes in tab 2, which are reserved as direct gateway input values. You can also see these bytes in the Logic docking window.
Example: MSI-FB-CANOPEN module with four predefined inputs for gateways:
"Logic” docking window "Gateway" view
In the Logic docking window you see these four bytes under Inputs:
In the Gateway view, these four inputs appear in tab 2:
Leuze electronic MSI 400 40
Page 41
Configuration of gateways with MSI.designer
"Logic” docking window "Gateway" view
Change tag names of a predefined input value
Tag names have already been pre-assigned to the predefined input values (bytes). You can change these tag names:
Ä In the Gateway view click on the byte, whose tag name you want to change.
Ä Open the Properties docking window. Ä If you wish to change the tag name of the byte:
Overwrite the pre-allocated tag name of the byte with the desired new value in the configuration dialog.
Ä If you also want to change the tag names of individual bits:
Overwrite the pre-allocated values with the desired new value under Parameters in the configuration dialog.
In the Logic view, these bits will appear with the corresponding tag names.
Configuring additional gateway input values
You can add new output values (bytes) in addition to the pre-allocated output values in the Gateway view.
Ä Click on an empty byte in the Gateway view.
Leuze electronic MSI 400 41
Page 42
Configuration of gateways with MSI.designer
i
Ä Open the Properties docking window and assign a tag name for the byte.
ð Tag names for all bits are automatically pre-allocated under Parameters.
Ä If you also want to change the tag names of individual bits:
Overwrite the pre-allocated values with the desired new value under Parameters.
In the Logic view, these bits will appear with the corresponding tag names.

5.5 Monitoring process data

You can monitor your gateway configuration directly in MSI.designer. This can be done in simulation mode (limited monitoring option) or by means of an active link to a MSI 400 system.
NOTICE
The MSI 400 gateways always show the actual physical state of the inputs and outputs of the connected modules and equipment. This means that even when the force mode is active and in­puts that are physically Low are forced to High (or vice versa), the actual physical state of these inputs is transmitted to the PLC and not the (virtual) forced state. However, if one or several out­puts change their state as a result of one or several inputs being forced, the changed state of these outputs will also be transmitted to the PLC, as the actual physical state of the equipment outputs has changed.
Simulation mode (offline mode)
You can test a gateway configuration offline in simulation mode. Use the logic analyzer for this purpose and manually set the desired inputs to High or Low.
Leuze electronic MSI 400 42
Page 43
Configuration of gateways with MSI.designer
i
Read here how to work with the simulation mode and logic analyzer: Software manual, chapter "Simulating logic programming"
Monitoring with an active connection (online mode)
You can also test a gateway configuration online by establishing a link between MSI.designer and a MSI 400 system.
Read here how to activate the online mode and what you need to take into account: Software manual, chapter "Connecting to the safety controller"
NOTICE
LED behavior for active connections
If you are linked to a MSI 400 installation, the status LEDs in the Modules view of MSI.designer will light up in the same way as for the connected system.
Further information about the status LEDs may be found in the documentation for the relevant module:
Ä Modbus TCP gateway [chapter 6.4] Ä PROFIBUS-DB gateway [chapter 9.4] Ä CANopen gateway [chapter 10.14]
Leuze electronic MSI 400 43
Page 44

6 Modbus TCP gateway

8 input LEDs
LED PWR/EC MS LED CV LED
8 input LEDs 4 output/
4 input LEDs
LED NET
Mini-USB connection
RJ45 connection
SD slot for MSI-SD-CARD
The controller module MSI 430 can be used for Modbus TCP. The internal MSI-EN-MOD (Modbus TCP Gateway) is a component of the MSI 430 device and is activated by the gateway configuration:
Fig.6.1: Activation of Modbus TCP on the MSI 430 module
The Modbus TCP gateway supports the following:
• Modbus TCP with master and slave operation
• Ethernet TCP/IP socket interface, polling and auto-update function

6.1 Interfaces and operation

The MSI 430 is equipped with a RJ-45 socket.
Modbus TCP gateway
Fig.6.2: Interfaces and display elements
Further information
• Here in this manual:
Diagnostics and troubleshooting [chapter 6.4]
• In the hardware manual: Device state and LED displays in the controller modules

6.2 Basic configuration – allocation of an IP address

The MSI 430 module is configured with the help of the MSI.designer configuration software.
Step 1: Insert module MSI 430
Ä Start MSI.designer and open the Modules docking window. Ä Add the controller module MSI 430.
Instructions: Software manual, chapter "Adding modules"
Step 2: Open configuration dialog
Ä Switch to the Project structure docking window. Ä Click on the top element, which represents the controller.
Leuze electronic MSI 400 44
Page 45
Ä Open the Properties docking window.
ð You will see the controller configuration dialog.
Modbus TCP gateway
Step 3: Store configuration
Ä Enter the following values under Control configuration:
- valid IP address
- subnet mask
- if required: valid IP address for a default gateway OR: Alternatively activate DHCP.
Ä Ensure that MSI.designer is connected to the MSI 400 system.
The MSI 400 system must not be in Run (Execute) mode. The Start/Stop button in the command bar of the Modules view must be set to Start.
More detailed information on the link to the controls: Software manual, chapter "Connecting to the safety controller"
Ä Click Send in the Properties docking window to transfer the configuration to the MSI 400 system.

6.3 Configuration of the Modbus-TCP interface to the PLC - how the data are transferred

Application characteristics for Modbus TCP
• Support of standard addressing conventions for Modbus TCP
• Master and slave operation
Requirements for the PLC for Modbus TCP
• The PLC must support the Modbus TCP protocol.
• The PLC must either support the Read Holding Registers and Write Multiple Registers commands or the Read/Write Multiple Registers command.
The configuration steps in this section determine how the data are to be transmitted to the higher-level PLC.
There are two different methods of transmission for each transmission direction, i.e. MSI 400 to network and network to MSI 400:
• Receiving method Polling/PLC requests (gateway as slave)
This method allows the PLC regularly to request data using polling.
Leuze electronic MSI 400 45
Page 46
Modbus TCP gateway
i
When this method is used, the data are returned in the response to the data request. The PLC requests data by accessing the receiving data address of the MSI 430 module via a read-holding-register tele­gram.
• The master receiving method gateway writes to the PLC (auto-update, gateway as master)
When the MSI-EN-MOD module sends data to the PLC, these are immediately written to a memory loc­ation in the PLC.
• Slave transmission method - PLC writes (gateway as slave)
With this method, the PLC sends telegrams to the MSI 430 module to write to the output data sets. For this purpose, the PLC writes data into defined addresses.
• The master transmission method gateway reads from the PLC (auto-update, gateway as master)
With the master transmission method, the MSI 430 module polls the PLC for the output data sets.
NOTICE
The configuration is regarded as faulty when the IP address of the PLC is zero and the read transfer mode and/or write transfer mode has been set for the master.
The number of possible connections to the PLC depends on whether the MSI 430 module is operated as a master or as a slave. Depending on the setting, up to 6 PLCs can simultaneously address the MSI 430 module.
Tab.6.1: Maximum number of possible Modbus TCP connections for the individual operating modes
Operating mode of the MSI 430 module Maximum number of connections
Output data (to PLC): Gateway writes Input data (from PLC): Gateway reads
Output data (to PLC): Gateway writes Input data (from PLC): PLC writes
Output data (to PLC): PLC reads Input data (from PLC): Gateway reads
Output data (to PLC): PLC reads Input data (from PLC): PLC writes
The following table describes the configuration, depending on the transmission method:
Gateway is master
Tab.6.2: Configuration directive – gateway as master
Essential settings in the gateway configuration (via MSI 430)
Choose Gateway writes to tag/file and/or Gate­way reads from register to configure the gateway
as a master.
1 outgoing connection
1 incoming connection
1 outgoing connection
6 incoming connections
6 outgoing connections
1 incoming connection
6 outgoing connections
6 incoming connections
Settings required for the PLC program and/or in the Modbus TCP configuration tool
–
Select which data are to be written to the PLC or read from it.
Define where the selected data in the PLC memory are to be written to: Enter the register address(es).
Example: "40001" and/or you can determine from which location in the PLC memory the selected data are to be read: Enter the register addresses.
Choose how often these data are to be transmitted. –
Leuze electronic MSI 400 46
–
Ensure that the addresses allocated in the MSI 400 are available and that they contain the data inten­ded for the MSI 400- system.
Page 47
Modbus TCP gateway
i
Essential settings in the gateway configuration (via MSI 430)
Define from and to where the data in the Modbus­TCP network are to be read and written: Enter the IP address and the slot number of the PLC control­ler.
Gateway as slave
Tab.6.3: Configuration directive – gateway as slave
Essential settings in the gateway configuration (via MSI 430)
Select PLC requests and PLC writes in the gate­way configuration dialog.
– Select which data are to be written to the gateway
NOTICE
Settings required for the PLC program and/or in the Modbus TCP configuration tool
–
Settings required for the PLC program and/or in the Modbus TCP configuration tool
–
or read from it.
Ensure that the PLC program writes the data into the addresses allocated to the gateway (see Table "Data addressing for the MSI 430 as recipient [chapter 6.3]").
The address settings for the Modbus TCP gateway are 1-based. Please subtract 1 from the re­gister address set in MSI.designer for a 0-based address setting.
Example: Register 1100 corresponds to the Modbus address 1099.
Master mode: MSI 430 reads from/writes to the PLC
Carry out the following steps to configure the gateway as a master:
Ä Change to the Gateway view and click on the Gateway configuration tab. Ä Select the MSI 400 is Master/Client option at the very bottom of the Modbus mode section.
ð The settings required for master mode are activated automatically in the Output data (to PLC) and In-
put data (from PLC) sections.
Quick reference
You can make the following additional settings:
“Output data (to PLC)” section
Area highlighted in gray
Leuze electronic MSI 400 47
Page 48
Modbus TCP gateway
“Output data (to PLC)” section
Selection list Set automatically: Determines the transmission method.
Value required for master mode:
Gateway writes to tag/file
All data sets in one tag Optional
Defines that all data sets are to be written to a single address in the PLC memory.
In this case the register address defined for Data Set 1 will be used.
Note:
The following two settings can be activated simultaneously. They determine the frequency of data transmission.
Activating updates following changes
Recommended
Determines that the MSI 430 module immediately updates the data in the PLC as soon as changes are made to the data sets.
Activate heartbeat interval Recommended
Use the heartbeat intervals which you defined in the Heartbeat
interval column to activate the update of the selected data sets.
Columns highlighted white
Data set Determines which data are to be written to the PLC or read from
it.
Select the checkboxes for the desired data sets.
You will find a detailed description of the data sets here: Data
transferred to the network (network input data sets) [chapter 3.2]
Register Define from and to where in the PLC memory the selected data
should be read and written.
Heartbeat interval (ms) Defines how often the data sets are to be updated.
Requirement: You have selected the option Activate heartbeat
interval (see above).
Register range Shows the registers in the PLC to which the process data is writ-
ten.
“Input data (from PLC)” section
Selection list 1 Set automatically: Determines the transmission method.
Value required for master mode: Gateway reads from register
Selection list 2 Defines which of the two modbus commands is used:
• Read holding registers: Activates the Read holding registers command (see "Mod­ule commands" table below).
• Read input registers: Activates the Read input registers command (see "Module commands" table below).
Data set column Determines which data are to be written to the PLC or read from
it.
Mark the control boxes for the desired data sets for this purpose.
You will find a detailed description of the data sets here: Data
transferred to the network (network input data sets) [chapter 3.2]
Register column Define from and to where in the PLC memory the selected data
should be read and written.
Leuze electronic MSI 400 48
Page 49
Modbus TCP gateway
i
i
“Input data (from PLC)” section
Column heartbeat interval Defines how often the data sets are to be updated.
"Modbus mode” section
PLC IP address
Device ID
Maximum refresh time for PLC Define the maximum rate (or the minimum time interval) for trans-
Ä Combine MSI.designer with the MSI 400 system and transmit the configuration.
More detailed information on the link to the controls: Software manual, chapter "Connecting to the safety controller"
Write to the PLC
NOTICE
The following restrictions apply when the gateway operates as a master and writes the input data sets to the PLC:
• The address of the input data sets (preset in MSI.designer) must be the same as defined in the PLC.
• The PLC variable that is to incorporate the data must meet the following conditions:
• in the address range 40xxxx (for Schneider Modicon PLC),
• an array of 16-bit words,
• long enough to contain the defined input data set array.
• All input data sets are transmitted to the PLC in 16-bit word format, with the first byte having the lowest value, i.e. on the far right of the integer, while the second byte has the highest value, i.e. on the very left of the integer.
The parameters define from and to where the data in the Mod­bus-TCP network are to be read and written:
mitting the data sets to the PLC. This setting depends on the pro­cessing speed of the PLC. Minimum = 10 ms, maximum = 65535 ms. The basic setting of 40 ms is suitable for most PLC
Note: When these values are greater than the heartbeat interval, the heartbeat interval will be slowed down to this value.
Reading from the PLC
NOTICE
The following restrictions apply when the gateway operates as a master and reads the output data sets from the PLC:
• The address of the output data sets must be the same as defined in the PLC. Please note: The value of the Modbus addresses must be 1 lower than the register data. See also: "Figure 8" in "MODBUS Application Protocol V1.1b3"
• The PLC variable from which the data are requested must meet the following conditions:
• They fall into the address range 40xxxx (for Schneider Modicon PLCs).
• There is an array of 16-bit words for the output data sets that is long enough to accommodate the entire output data set.
• All output data sets are transmitted to the PLC in 16-bit word format, with the first byte having to be placed as the lowest value, i.e. on the far right of the integer, while the second byte will have the highest value, i.e. on the very left of the integer.
Slave/server mode - PLC reads from / writes to MSI 430
In this operating mode, the MSI 430 module provides the data as a slave at the request of the PLC. If this operating mode is desired:
Ä Launch MSI.designer. Ä Change to the Gateway view and click on the Gateway configuration tab.
Leuze electronic MSI 400 49
Page 50
Modbus TCP gateway
i
i
Ä Select the MSI 400 is Slave/Server option at the very bottom of the Modbus mode section.
ð The minimum settings required for slave mode are activated automatically in the Output data (to PLC)
and Input data (from PLC) sections.
ð Unavailable options are grayed out.
You can make the following additional settings:
Tab.6.4: "Output data (to PLC)" and "Input data (from PLC)” sections
Setting Description/procedure
Data set column Determines which data can be written to the PLC or read from it.
Mark the control boxes for the desired data sets for this purpose.
You will find a detailed description of the data sets here: Data
transferred to the network (network input data sets) [chapter 3.2]
Size (bytes) column Exact number of bytes to be read out or written. The number of
16-bit data types usual for TCP modbus is exactly half.
Register range column Registers to be addressed in MSI 430
Ä Combine MSI.designer with the MSI 400 system and transmit the configuration.
More detailed information on the link to the controls: Software manual, chapter "Connecting to the safety controller"
PLC writes output data sets
The following restrictions apply when the PLC writes the output data sets:
• The equipment index must not be equal to zero.
• The telegram must be sent in Word format.
• All output data sets are transmitted to the PLC in 16-bit word format, with the first byte having to be placed as the lowest value, i.e. on the far right of the integer, while the second byte will have the highest value, i.e. on the very left of the integer.
PLC polls the input data sets
• The following restrictions apply:
• The equipment index must not be equal to zero.
• The PLC variable that is to incorporate the data must meet the following conditions:
• It falls into the address range 40xxxx (for Schneider Modicon PLCs).
• There is an array of 16-bit words that is long enough to accommodate the entire output data set.
• All input data sets are transmitted to the PLC in 16-bit word format, with the first byte having the lowest value, i.e. on the far right of the integer, while the second byte has the highest value, i.e. on the very left of the integer.
NOTICE
Configure the PLC data polling in such a way that a data telegram is exchanged at least every minute between MSI 430 and the PLC. The TCP connection will otherwise be interpreted as not used and terminated.
NOTICE
The data from the PLC to the MSI 430 module assumes the value zero in the MSI.designer logic program if the Modbus TCP connection is terminated by the PLC itself or by a timeout.
Leuze electronic MSI 400 50
Page 51
MSI 430 as slave – data addressing
The following table lists the addresses for reading out the data sets.
Unit ID 1
Tab.6.5: Data addressing for the MSI 430 as recipient
Modbus TCP gateway
Register
Description Access Scope (words)
(Base 1)
1000 Request data for all activated input data sets Reading 1..101
1)
1100 Request data from input data block 1-5 Reading 1..25
1200 Request CRC data Reading 1..16
1300 Request diagnostic data Reading 1..30
1400 Reserved Reading 1..30
2000 Write all activated output data sets Read, write 1..25
2)
2100 Write data from output data set 1 Read, write 1..5
2200 Write data from output data set 2 Read, write 1..5
2300 Write data from output data set 3 Read, write 1..5
2400 Write data from output data set 4 Read, write 1..5
2500 Write data from output data set 5 Read, write 1..5
1)
Corresponds to all activated input data sets.
2)
Must correspond to all activated output data sets. Example: If only output data sets 1 and 2 have been activated, 10 words (20 bytes) must be written. If all output data sets have been activated, 25 words (50 bytes) must be written.
Modbus commands and error messages
The MSI 430 module supports the following Modbus commands and error messages:
Tab.6.6: Modbus commands
Modbus command Value
Read holding registers 3
Read input1) registers 4
Write single register 6
Write multiple registers 16 (10hex)
Read/write multiple registers 23 (17hex)
1)
starting with module version A-03
Tab.6.7: Modbus error messages
Modbus error response Description
1 Function not permitted The requested function is not supported
2 Data address not permitted Undefined data address received
3 Data value not permitted Request with prohibited data values, e.g. insufficient
4 server errors An error occurred during execution of the server.

6.4 Diagnosis and troubleshooting

You can find information on diagnosis of the MSI 400 system in the software manual.
data requested for a data set
Leuze electronic MSI 400 51
Page 52
Tab.6.8: Troubleshooting on the MSI 430
Error Possible cause Possible remedy
Key: LED off / LED flashes / LED lights up
Modbus TCP gateway
MSI.designer cannot set up a connection to the MSI 400 gateway.
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED ACT
Orange
• The MSI 430 module has no power supply.
• The MSI 430 module is not in the same physical network as the PC.
• A different subnet mask has been set in the TCP/IP settings for the PC.
• The module was been preconfigured and has a permanently set IP ad­dress or an IP address allocated to a DHCP server that has not been allocated.
• The MSI 430 module has been configured for data transmission to the PLC, but no Ethernet communication has been established or the communication is faulty.
• Duplicate IP address detected. Another net­work device has the same IP address.
• Switch on the power supply. Check the Eth­ernet wiring and the net­work settings of the P and correct them where necessary.
• Set the PC to a network address 192.168.1.0 (The delivery state of the MSI 430 module has the address
192.168.1.4, which may not be used for the PC).
• Alternatively activate DHCP on the PC and link the MSI 430 module and the PC to a net­work, using an active DHCP server.
• Check the communica­tion settings in MSI.de­signer.
At least one Ethernet link must be established.
• Set up the Ethernet link on the PC, check the Ethernet wiring, check the Ethernet settings in the PLC and in MSI.de­signer.
• If no Ethernet commu­nication is required, de­activate the Ethernet connections / PLC inter­faces on the MSI 430.
• Correct the IP address and switch the system off and on again.
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED ACT
Orange
• Configuration required.
• The configuration has not yet been fully trans­mitted.
• The module version of the controller module does not support the gateway function.
• Configure the MSI 430 module and transfer the configuration to the sys­tem.
• Wait until the configura­tion has been fully trans­ferred.
• Use the controller mod­ule with the required module version.
MS LED
Red
(1 Hz)
Leuze electronic MSI 400 52
Page 53
Error Possible cause Possible remedy
Modbus TCP gateway
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED ACT
Orange
MS LED
Green
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
MS LED
Green
(1 Hz)
The MSI 430 module func­tioned correctly after config­uration but suddenly provides no more data.
LED PWR/
Green
EC
LED LINK
Green
LED ACT
Orange
MS LED
Green
• No data set was activ­ated.
• No Ethernet communic­ation interface was ac­tivated.
The MSI 430 module is in the “Stop” state.
• The MSI 430 module is operated in slave mode, the IP address is alloc­ated by a DHCP server.
• Following a restart of the MSI 430 module or the DHCP server, an­other address was alloc­ated to the MSI 430 module, which is un­known to the PLC.
• Activate at least one data set.
The controller module is stopped.
• Start the controller mod­ule (switch to Run mode).
• Allocate a fixed IP ad­dress to the MSI 430 module.
or
• Reserve a fixed IP ad­dress for the MSI 430 module in the DHCP server (manual assign­ment using the MAC ad­dress of the MSI 430 module).
The MSI 430 / the MSI 400 system is in the “Critical er­ror” state.
LED PWR/ EC
LED LINK
LED ACT
MS LED

6.5 State bits

The Modbus TCP Gateway MSI-EN-MOD sets status bits, which are available in the logic editor of MSI.de­signer for processing.
Tab.6.9: Meaning of the state bits MSI-EN-MOD[0] in the logic editor
Name of the state bits Set to 1, if ... Reset to 0 ...
Output status ... At least one output data byte was
Red
Green
Orange
Red
• The MSI 430 module is not properly connected to the other modules.
• The module connection plug is dirty or dam­aged.
• Another module in the MSI 400 system has an internal critical error.
• The voltage supply for the MSI 430 module is or was outside the spe­cifications.
sent without error.
• Plug the MSI 430 mod­ule in correctly.
• Clean the connection plug and socket.
• Switch on the power supply again.
• Check the power sup­ply.
• Check the other mod­ules of the MSI 400 sys­tem.
... If there is a missing Modbus TCP connection to the PLC.
Input status ... At least one input data byte was
sent without error.
Leuze electronic MSI 400 53
... If there is a missing Modbus TCP connection to the PLC.
Page 54
Name of the state bits Set to 1, if ... Reset to 0 ...
Modbus TCP gateway
Internal state … The Modbus function in MSI 430
is ready for communication
From module version E-01.01: If the Modbus function in MSI 430 is ready for communication or if at least one input or output byte was downloaded or transmitted without errors.
... If an error has occurred in the Modbus function.
Leuze electronic MSI 400 54
Page 55

7 PROFINET IO-Gateway

i
The MSI 430 module can be used for PROFINET IO.
You will find the GSDM file and the equipment symbol for integration in a PLC of the product website of the MSI 430 module on the Internet (http://www.leuze.com).
The internal MSI-EN-PN (PROFINET IO Gateway) module is part of the device MSI 430. You can activate it in the configuration dialog of the MSI 430 module in the Properties docking window:
PROFINET IO-Gateway
Supported features
The MSI 430 module supports:
• PROFINET IO Conformance Class A
• Cyclical EA communication (RT)
• LLDP
• DCP
Currently not supported:
• SNMP
• Shared Input, Shared Device
• FSU
The number of PROFINET controllers (PLCs) which can simultaneous connect to a MSI 430 device via PROFINET is limited to one.
• Auto MDI
• Auto negotiation
• I&M 1-4
• Equipment diagnostics, alarms
• MIB II
• Port statistics

7.1 Interfaces and operation

Interfaces and operation are identical to that of the Modbus TCP Gateway.
Read the following section: Interfaces and operation [chapter 6.1]

7.2 Basic configuration - Assigning a device name and an IP address

Configuration and diagnostics of the MSI 430 is possible both with the help of the MSI.designer configura­tion software and the PROFINET IO network programming tool (e.g. SIEMENS TIA Portal).
Configuration using PROFINET IO
In the delivery state, a MAC address is stored in every PROFINET IO field device such as the MSI 430 module. The symbolic name (NameOfStation) Test station is stored on the SD card in the delivery state.
NOTICE
Ä In accordance with IEC 61158-6-10 no capital letters are permitted for the symbolic name
(NameOfStation).
Ä This NameOfStation is used by the I/O controller (e.g. the PLC) to assign an IP address to
the field device.
Ä If the IP address is also used for other communication via Ethernet, such as TCP/IP or for
the configuration via Ethernet, please note that the PLC changes the IP address and can thus interrupt the other communication.
Leuze electronic MSI 400 55
Page 56
PROFINET IO-Gateway
i
The IP address is assigned in two steps.
Ä Assign a unique system-specific name to the Gateway, using either the network configuration tool such
as SIEMENS TIA Portal, or using the MSI.designer software. In MSI.designer this is the Connection name. Where do you edit the connection name in MSI.designer? Open the Project structure docking window and there click on the Controller entry right at the top. Additionally open the Properties docking win­dow and enter the desired value there in the configuration dialog under Connection name.
Ä A (unique) system-specific name can be used by the I/O-Controller (i.e. the PLC) to assign the IP ad-
dress to the gateway now before the system is booted.
NOTICE
The MAC address of the MSI 430 module is printed on the device's nameplate (Example: 00:07:17:02:03:05).
Using the Siemens TIA Portal to assign device names
In the Online accesses area, select the network card connected to the network which can be used to ac­cess the MSI 430 device. In the Assign name function area, edit the PROFINET device name field and then select Assign name.
This will permanently assign the new device name to the MSI 430 device.
Fig.7.10: Assigning device names with the TIA portal
Assign device name via the software
Ä Launch MSI.designer and connect to the controller module MSI 430. Ä Press the Stop button in the Modules view to stop the application. Ä In the Modules view click on the blue background and open the Properties docking window.
ð You will see the controller configuration dialog.
Ä Edit the connection name and click the Send button.
Fig.7.1: Configuration dialog for the IP data and the device name
Leuze electronic MSI 400 56
Page 57
PROFINET IO-Gateway
i
NOTICE
Ä The format of the device name must correspond to the specification of the PROFINET
standard.
Ä Ensure that the address for the default gateway matches the address set by the PLC for the
gateway. If no router is used, then Siemens Step 7 uses the same IP address for the default gateway as for the MSI 430 module.
Ä If a project file with an active PROFINET IO is provided on the MSI 430 module, then only
one device in MSI.designer can be found by USB. If you would like to use the Ethernet to connect with the MSI 430 module then select Edit in the Connect dialog, where you then set the IP address of the MSI 430 module.
Set the IP address using the software
The IP address is typically assigned by the PROFINET IO controller (e.g. PLC). The MSI 430 module, how­ever, also allows the configuration of the entire MSI 400 system via Ethernet TCP/IP. It can be necessary in this case to already assign an IP address to the MSI 430 before the PROFINET IO network is set up. This can also be done in the configuration dialog shown above.
Leuze electronic MSI 400 57
Page 58

7.3 PROFINET configuration of the gateway - how the data are transferred

i
The following steps are required to configure the communication between the PLC and the gateway.
NOTICE
This documentation does not address the installation of the PROFINET IO network or the other components of the automation system project in the network configuration tool. It is assumed that the PROFINET project in the configuration program, e.g. the SIEMENS TIA Portal, has already been set up. The examples presented are based on configurations created with the help of the SIEMENS TIA Portal.
Step 1: Install the device master file (GDSML file)
Before the MSI 430 module can be used for the first time as part of the network configuration tool, e.g. the SIEMENS TIA Portal, the device master file (GSDML file) of the gateway must first be installed in the hard­ware catalog of the tool.
Ä Download the GSDML file and the equipment symbol from the product site of the MSI 430 module
(http://www.leuze.com).
Ä Follow the instructions for the installation of GSD files in the online help section or in the user manual
for the PROFINET network configuration tool.
If you are using SIEMENS TIA Portal, then the MSI 430 module appears in the following location in the hardware catalog:
PROFINET IO-Gateway
Step 2: Add the gateway to the project
To make the system of the MSI 400 system available in the process diagram of the PLC, the gateway must first be added to the hardware configuration. The procedure to be used depends on the hardware configur­ation software of the PLC used. Please also read the documentation for the corresponding software in this regard.
The example below shows how the gateway is added to a SIEMENS TIA Portal project.
Ä Use Drag & Drop in the Network view to drag the device to the Ethernet PROFINET IO network.
Example:
Leuze electronic MSI 400 58
Page 59
PROFINET IO-Gateway
Step 3: Configure the gateway properties
Ä Double-click the hardware symbol of the MSI 430 module. Ä Configure the IP address, the device name, and the update interval of the cyclical I/O data exchange.
Select the Properties tab for this.
Leuze electronic MSI 400 59
Page 60
PROFINET IO-Gateway
i
NOTICE
The PLC can only communicate with the MSI 430 module if the PLC software and the gateway use the same gateway name. In accordance with IEC 61158-6-10 no capital letters are permitted for the symbolic name (NameOfStation).
Leuze electronic MSI 400 60
Page 61

7.4 PROFINET configuration of the gateway - which data are transferred

i
Cyclical data
The physical I/O modules are not presented in the PROFINET IO hardware catalog as typical hardware modules in the network. Instead, the data provided by the MSI 400 system has been arranged in various data blocks. Every data block represents a module in the PROFINET IO hardware catalog. The GSDML supports 13 Slots in which the modules can be placed. This makes is possible to use each data set one time (see illustration "Configuration" [chapter 7.4]).
Process data from module to PLC
The MSI 430 module provides 5 input data blocks (virtual device modules) which contain the process im­age. These can be exclusively placed in each corresponding slot 16 to 20.
NOTICE
Input data blocks 1 to 4 each contain 12 bytes, while input data block 5 contains 2 bytes.
The content of the input data blocks can be freely selected. The data assignment in MSI.designer is pre­configured in accordance with the following:
Tab.7.1: Predefined content of input data block 1 to 5 of the MSI 430 module
PROFINET IO-Gateway
Data block 1 Data block 2 Data block 3 Data block 4 Data block 5
Byte no. per data block
Byte 0 Input values
Byte 1 Input values
Byte 2 Input values
Byte 3 Output values
Byte 4 Logic data val-
Byte 5 Logic data val-
Byte 6 Logic data val-
Byte 7 Logic data val-
Byte 8 Logic data val-
Input data Input data Input data Input data Input data
MSI 430
MSI 430
MSI 430
MSI 430
ues
ues
ues
ues
ues
I/O module 1 input values
I/O module 2 input values
I/O module 3 input values
I/O module 4 input values
I/O module 5 input values
I/O module 6 input values
I/O module 7 input values
I/O module 8 input values
I/O module 9 input values
I/O module 1 output values
I/O module 2 output values
I/O module 3 output values
I/O module 4 output values
I/O module 5 output values
I/O module 6 output values
I/O module 7 output values
I/O module 8 output values
I/O module 9 output values
Not allocated Not allocated
Not allocated Not allocated
Not allocated Not available
Not allocated
Not allocated
Not allocated
Not allocated
Not allocated
Not allocated
Byte 9 Logic data val-
ues
Byte 10 Logic data val-
ues
Byte 11 Logic data val-
ues
Length 12 bytes 12 bytes 12 bytes 12 bytes 2 bytes
Byte offset 0 12 24 36 48
Leuze electronic MSI 400 61
I/O module 10 input values
I/O module 11 input values
I/O module 12 input values
I/O module 10 output values
I/O module 11 output values
I/O module 12 output values
Not allocated
Not allocated
Not allocated
Page 62
PROFINET IO-Gateway
i
i
1 byte for data set 1 is available for every expansion module. The input values show the state of the prelim­inary evaluation of the I/O module. This corresponds to the state of the element in the controller module lo­gic. 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 detection 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 repres­ents 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
Further information
You will find information about how to configure the process diagram in the description of the (The graph- ical user interface [chapter 5.1]) user interface.
Data from the PLC to the MSI 430 module
There are 5 output data blocks having 10 bytes each. These can be exclusively placed in each correspond­ing slot 21 to 25.
The content of these data blocks can be used as input in the MSI.designer logic editor or forwarded to an­other network by a second gateway. Every bit to be used must be assigned a tag name in order to provide the desired bits in the logic editor or for forwarding. Bits without tag names are not available.
Detailed information about how you can assign and adapt the tag names of the input and output data can be found here: Software manual, chapter "Adapting display names of project components"
NOTICE
The standard value of the gateway data bit is zero following activation of the MSI 430 device.
If the connection to PLC is terminated, then all of the gateway data bits in the MSI.designer logic editor assume the value zero.
NOTICE
For output data with IOPS=Bad, all of the gateway data bits in the MSI.designer logic editor as­sume the value zero. This is the case, for example, if the PLC is stopped.
Settings in the PROFINET IO network configuration tool
Ä Only drag the required data blocks from the hardware catalog of the SIEMENS TIA Portal to the corres-
ponding slots of the MSI 430 module within the configuration table.
Leuze electronic MSI 400 62
Page 63
PROFINET IO-Gateway
i
i
Fig.7.12: Configuration of the MSI 430 module
NOTICE
The input and output addresses indicate the location of the cyclical data in the memory. These can be addressed via the absolute addresses %I and %Q in the SIEMENS TIA portal.
Acyclical data and alarms
Read out data
The PLC can read out the diagnostic data of the MSI 400 system. The diagnostic information is provided in three data sets, data sets 2, 3, and 4:
Data set 2 comprises 32 bytes and contains the project file's CRC 32. This can only be placed in slot 32.
Data set 3 comprises 60 bytes and contains the status of MSI 430 module and the individual I/O modules. This can only be placed in slot 33. See the following to interpret the status bits in data set 3: Table "Mean-
ing of the module status bits of the controller module" [chapter 3.3.5] and Table "Meaning of the module status bits of the I/O modules" [chapter 3.3.5]
Data set 4 (auxiliary data) comprises 60 bytes and is currently filled with reserved values. This can only be placed in slot 34.
NOTICE
Type and source of danger
Data set 4 in Slot 34 does not function with all versions of the SIEMENS TIA portal.
Information & Management
The MSI 430 module supports the I&M information defined in the PROFINET IO specification. The follow­ing I&M information can be read out:
Leuze electronic MSI 400 63
Page 64
PROFINET IO-Gateway
i
Tab.7.2: Readable I&M information
Name Size Value range I&M Storage loca-
tion
MANUFACTURER_ID (Vendor ID)
ORDER_ID (Order ID) 64 bytes "50132988 + 51 blank spaces and
SERIAL_NUMBER (IM_Serial_Number)
HARDWARE_REVISION (IM_Hardware_Revision)
SOFTWARE_REVISION (IM_Software_Revision)
Device ID 05001 0 MSI 430
REV_COUNTER (IM_Revision_Counter)
PROFILE_ID (IM_Pro­file_ID)
PROFILE_SPE­CIFIC_TYPE (IM_Pro­file_Specific_Type)
IM_VERSION (IM_Ver­sion)
2 bytes 397 = 0x18D 0 MSI 430
0 MSI 430
"50132989 " + 51 blank spaces
8 bytes "16010001" to "99129999" 0 MSI 430
2 bytes 101 to 9999 0 MSI 430
6 to 9 Bytes
2 bytes 0 to 65535 0 SD card
2 bytes 0x0000 (Non-profile) 0 MSI 430
2 bytes 0x0003 (IO modules) 0 MSI 430
2 bytes 1 0 MSI 430
"V0.1.0" to "V99.99.99" 0 MSI 430
IM_SUPPORTED (IM_Supported)
TAG_FUNCTION 32 bytes 32 Bytes à 0x20..0x7E 1 SD card
TAG_LOCATION 22 bytes 32 Bytes à 0x20..0x7E 1 SD card
INSTALLATION_DATE (IM_Date)
DESCRIPTOR (IM_Descriptor)
IM_Signature 54 bytes 54 Byte à 0x00..0xFF 4 SD card
1)
Subject to changes
Alarms
Alarms can be acyclically read using the PROFINET IO alarm infrastructure. When an error in the MSI 400 system occurs, the PROFINET IO gateway sends a corresponding diagnostics alarm to the network. The details of the diagnostics alarm (text and help) are then available through the SIMATIC PLC interface. The RALRM (SFB54) function block in OB82 (diagnostics interrupt) allows you to make the details of the sent alarm directly available in the PLC program.
NOTICE
All alarms are output to module 0.
The cause of the alarm is displayed by an error message from the GSDML file.
The possible causes of an alarm can be found in the software manual, Section "List of all error messages".
2 bytes 10 (= 0b1010) 0 MSI 430
16 bytes 2 SD card
54 bytes 54 Byte à 0x00..0xFF 3 SD card
1)

7.5 Diagnostics and troubleshooting

Information on the diagnosis of the MSI 400 system can be found in the software manual, Section "List of all error messages".
Leuze electronic MSI 400 64
Page 65
Tab.7.3: Troubleshooting on the MSI 430 module
Error Possible cause Possible remedy
Key: LED off / LED flashes / LED lights up
PROFINET IO-Gateway
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
MS LED
Green
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
• The MSI 430 has been configured for data transmission to the PLC, but no Ethernet commu­nication has been estab­lished or the communic­ation is faulty.
• Duplicate IP address detected. Another net­work device has the same IP address.
• Incorrectly formatted PROFINET device name
• Configuration required.
• The configuration has not yet been fully trans­mitted.
• The module version does not support any PROFINET IO.
• PROFINET IO must be ac­tivated in the project file. At least one Ethernet link must be established. Check the Ethernet wiring, check the Ethernet settings in the PLC and in MSI.designer.
• Correct the IP address and switch the system off and on again.
• Compare the device name between the PROFINET master and the MSI 430 module.
• Configure the MSI 430 module with a project file in which PROFINET IO is ac­tivated and transfer the configuration to MSI 430 module.
• Use an MSI 430 device starting with module ver­sion B-xx.
MS LED
/
Red/green
The MSI 430 module does not provide any data.
LED PWR
LED LINK
Green
Green
LED /ACT
Yellow
MS LED
Green (1 Hz)
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
MS LED
Green
• The MSI 400 system is in the stop state.
• The IP address for the MSI 430 module is as­signed by a DHCP server. Following a re­start of the MSI 430 module or the DHCP server, another address was allocated to the MSI 430 module, which is unknown to the PLC.
• Start the controller module (switch to Run mode).
• Either assign the MSI 430 module a permanent IP ad­dress or reserve a perman­ent IP address for the MSI 430 module in the DHCP server (manual assignment using the MAC address of the MSI 430 module).
Leuze electronic MSI 400 65
Page 66
Error Possible cause Possible remedy
PROFINET IO-Gateway
The MSI 430 / the MSI 400 system is in the “Critical error” state.
LED PWR
LED LINK
LED /ACT
MS LED
Green
Green
Yellow
Red
• The MSI 430 module is not properly connected to the MSI 400 modules.
• The module connection plug is dirty or dam­aged.
• Another MSI 400 mod­ule has an internal crit­ical error.

7.6 Deactivation of the PROFINET IO function

If the MSI 430 device is started with an activated PROFINET IO function, then this function remains active until the device is switched off.
For this reason, switch the device off after sending a project without PROFINET IO function. This is re­quired, for example, if you convert the gateway function in the MSI 400 project from PROFINET IO to Mod­bus TCP.

7.7 State bits

The PROFINET IO gateway MSI-EN-PN sets state bits, which are available in the logic editor of MSI.de­signer for processing.
Tab.7.4: Meaning of the state bits MSI-EN-PN[0] in the logic editor
• Insert the I/O module cor­rectly. Clean the connection plug and socket.
• Switch on the power supply again.
• Check the other MSI 400 modules.
Name of the state bits Set to 1, if ... Reset to 0 ...
Output state … Data from slot 16, 17, 18, 19, 20,
Input state … Data from slot 21, 22, 23, 24 or
Internal state … An AR (Application Relation) is
An Application Relation (AR) is a clear communication relationship between two communication partners, for example a PLC and a device. The AR is initialized during PLC start-up. Cyclical input and output data, acyclical data using read/write services and alarms are exchanged bidirectionally between the PLC and the device within this AR.

7.8 Optimizing performance

Only use the data blocks from the hardware catalog of the module that you actually need for your applica­tion.
Sequence the process data in the routing tables within a data block without gaps (see Layout and content of the tabs [chapter 5.1.3]). Then check whether this will enable you to do without the use of individual data blocks from the hardware catalog. This helps to reduce the number of data bytes periodically exchanged in the network.
32 or 33 was transmitted without er­ror.
25 was downloaded from a PLC without error.
active.
… No AR (Application Relation) exists.
… No AR (Application Relation) exists.
... No AR exists.
Leuze electronic MSI 400 66
Page 67

8 EtherNet/IP gateway

i
This chapter describes the "EtherNet/IP-Gateway" function of the MSI 430 module.
The EtherNet/IP protocol is not described in this chapter. If you have little or no experience with this, please refer to the ODVA documentation for more information. Some content can be found in the glossary (see Abbreviations and Definitions [chapter 1.5]).
NOTICE
Use of the term “Device” in this chapter
This chapter uses the term “Device” as a synonym for the controller module MSI 430.

8.1 Interfaces and operation

Interfaces and operation are identical to that of the Modbus TCP Gateway.
Read the following section: Interfaces and operation [chapter 6.1]

8.2 Datasheet

The MSI 430 module supports EtherNet/IP from product version D-01.01. The following functions are integ­rated:
• Implicit message transmission (transport class 1)
• Explicit message transmission (transport class 3, connected)
• Device profile: Discrete universal I/O device
• UCMM Message Server (no connection)
• Supported objects: Message router, connection manager, port, identity, Ethernet link, TCP/IP, I/O point and group (discrete), vendor class 0x78, assembly
• Up to five simultaneous encapsulation sessions (input and output)
• Assemblies of a variable size
• Supported addressing: Class/instance/attribute and symbol tag
• Agreement with CIP (Common Industrial Protocol) specification and with EtherNet/IP CIP specification, according to table Module versions and referenced specification versions for EtherNet/IP [chapter 8.2]
• Details EDC file with ODVA conformity test
• Supported PCCC commands: Read and write word range, read and write input, read and write protec­ted logic input with two and three address fields for connection to PLC 3, PLC 5, PLC 5/250, PLC 5/ VME, SLC 500, SLC 5/03, SLC 5/04 and MicroLogix-1000
• Automatic configuration of semi and full duplex connections as well as of connections with 10 and 100 Mbit/s.
• MS (module state) and NET (network) LED
EtherNet/IP gateway
Tab.8.1: Module versions and referenced specification versions for EtherNet/IP
Module version CIP (Common Industrial Pro-
tocol) specification
up to D-01 Version 3.18 Version 1.19
from D-03 Version 3.21 Version 1.22
EtherNet/IP CIP specification

8.3 Basic setup

8.3.1 Basic configuration of PLC

This chapter briefly describes the basic configuration of the PLC.
Firstly, install the current EDS file for the MSI 430 module in your PLC configuration program. You can find the current EDS file on the Internet at http://www.leuze.com. The following diagram shows you how you can make the setting using the Logix Designer.
Leuze electronic MSI 400 67
Page 68
EtherNet/IP gateway
Fig.8.13: Register the EDS file using the ESD Wizard in the Logix Designer
The article number is "50132988,50132989,50134315,50134316" and can be filtered according to the vendor name "Leuze electronic" or a part of this name.
Fig.8.14: Selection of the module type in the Logix Designer
In the Internet Protocol tab in the Logix Designer, select Manually configure IP settings. Select the re­quired IPv4 address and the appropriate network mask.
Leuze electronic MSI 400 68
Page 69
EtherNet/IP gateway
Fig.8.15: IPv4 setting for the device in the Logix Designer
The MSI 430 module is a General Purpose Discrete I/O Device. For quick installation, use the connection Logic Output (1 to 400) and Logic/Physical Input, if your PLC supports implicit message transmission. The following figure shows the appropriate dialog in the Logix Designer.
Leuze electronic MSI 400 69
Page 70
EtherNet/IP gateway
Fig.8.16: Basic connection selected in the Logix Designer
This connection comprises up to 50bytes for data transmission from the PLC to the MSI 430 module (as­sembly instance 37). This connection comprises up to 67bytes for data transmission from the MSI 430 module to the PLC (assembly instance 57). The following table offers an overview of these data bytes.
Tab.8.2: Data of the class 1 connection “Logic output (1 to 400) and logic/physical input”
Instance Byte Access Data type Description Size Data range
37 0to49 Write,
read
BYTE[50] Output bytes, configuration
via Input data block 1 to 5
1 to 50 Bytes 0 to 0xff
in MSI.designer
(More [chapter 8.5.2.1])
57 0to49 Read BYTE[50] Input bytes, configuration
1 to 50 Bytes 0 to 0xff via Output data block 1 in MSI.designer
(More [chapter 8.5.3.1])
50to65 Read BYTE[16] Bits of the input terminals
1 to 16 Bytes 0 to 0xff (instance 401 to 528 of at­tribute 3 class 8, currently not listed in MSI.designer)
(More [chapter 8.5.3.1])
66 Read BYTE Bit7: Input state
Bit6: Output state
1 byte 0x00, 0x40,
0x80, 0xc0 (currently not listed in MSI.designer)
Other connections supported by the MSI 430 module are listed in the following table. You can find informa­tion on these assembly instances in the table "Overview of assembly databytes [chapter 8.5.1]".
Leuze electronic MSI 400 70
Page 71
Tab.8.3: Class 1 connections supported by the MSI 430 module
EtherNet/IP gateway
Name of the connection Assembly for data
from the PLC to MSI 4xx (O→T)
Assembly for data from MSI 4xx to the PLC (T→O)
Logic output (1 to 400) and logic/physical input 37 57
Logic output (1 to 400) and logic/state/system mode as-
37 167
sembly
Logic output (81 to 400) and logic/physical input 138 57
Logic output (81 to 400) and logic/state/system mode
138 167
assembly
Logic output (161 to 400) and logic/physical input 139 57
Logic output (161 to 400) and logic/state/system mode
139 167
assembly
Logic output (241 to 400) and logic/physical input 140 57
Logic output (241 to 400) and logic/state/system mode
140 167
assembly
Logic output (321 to 400) and logic/physical input 141 57
Logic output (321 to 400) and logic/state/system mode
141 167
assembly
Logic/physical input (“Listen only”) 199 57
Logic/state/system mode assembly (“Listen only”) 199 167
Logic/physical input (“Input only”) 198 57
Logic/state/system mode assembly (“Input only”) 198 167
Connection point 199(=0xc7) is used for Listen Only and connection point 198(=0xc6) for Input Only. Both possess a data size of zero. This means that the PLC does not make any data available for the MSI 430 module.
If the PLC only requires process data from the MSI 4xx module, the user is recommended to use a connec­tion with Input Only.

8.3.2 Basic configuration of the controller module

The integrated gateway MSI-EN-IP (EtherNet/IP gateway) is a constituent part of the MSI 430 module.
Activating the gateway
You can activate the integrated gateway in the configuration dialog of the MSI 430 module in the Proper­ties docking window:
Fig.8.1: Activation of EtherNet/IP in MSI.designer
Leuze electronic MSI 400 71
Page 72
EtherNet/IP gateway
i
NOTICE
Selection of the MSI-EN-IP gateway is possible for modules of type MSI 430 from version D-01.01.
Adapting the IPv4 data
The IPv4 data of the MSI 430 module can be adapted to the PLC settings in MSI.designer.
Requirement
During transmission of the IPv4 data, the device must not be in Run (Execute) mode. The command bar must be displayed on the left above the Start command, as shown in the following illustrations. If this is not the case, stop the device via the Stop button.
Required window layout
Fig.8.2: Setting of the IPv4 device data in MSI.designer

8.3.3 Configuring the data to PLC

The data transferred to the PLC and thus from the target device to the sender (Target to Originator, T→O) can be adapted in the "MSI 400 →MSI-EN-IP[0]" tab of the gateway configuration in MSI.designer. By de­fault, the first three bytes contain data for the input terminals I1 to I16 (and IQ1 to IQ4 in the appropriate configuration as an input). Byte 4 comprises data of the output terminals Q1 to A4 (and IQ1 to IQ4 in the appropriate configuration as an output).
Bytes 12 to 23 comprise data for the input terminals I1 to I8 of the input/output expansion modules. Bytes 24 to 35 comprise data for the output terminals Q1 to Q4 of the expansion modules MSI-EM-IO84 or MSI­EM-IO84NP. Bytes 4 to 11 comprise data of the logic editor and are called Direct Off.
This standard configuration can be adapted as shown here using drag & drop from the Gateway docking window in the tabs for the gateway configuration:
Fig.8.19: Adding of bytes to the gateway process image (T→O) using drag-and-drop in MSI.designer
In addition, the tag names of all the bytes in MSI.designer can be added or edited, in order to be able to use them in the Logic view of MSI.designer. User-defined names improve program legibility and troubleshooting. Tag names can be configured in the Parameters section of the Properties docking win­dow.
Leuze electronic MSI 400 72
Page 73
Fig.8.20: Adding new data bytes (T→O) for use in the "Logic" view by configuring tag names

8.3.4 Configuring the usage of data from PLC

Data transmitted by the PLC and thus by the sender to the target device (Originator to Target, O→T) can be named in the "MSI-EN-IP [0]→MSI 400" tab for the gateway configuration in MSI.designer. By default, the logic values Direct On0 to Direct On3 are assigned to the four first bytes. The names Data bit 0 to Data bit 7 are assigned to each bit as standard. Each bit can be used in the Logic view of MSI.designer as an unsafe input element, such as a Restart button or as a signal lamp.
Additional input elements for gateway data can be added as necessary by the configuration of additional tag names.
EtherNet/IP gateway
Fig.8.21: Adding of a new data byte (T→O) for use in the logic editor by configuring the tag name.
Fig.8.3: Adding gateway data elements to the logic editor in MSI.designer via drag & drop

8.4 Supported CIP Objects

8.4.1 Identity Object

The identity object is required for all EtherNet/IP-based products. Instance 1, attribute 1 stands for the Vendor ID. Leuze electronic GmbH is listed by the ODVA using the value 524.
Leuze electronic MSI 400 73
Page 74
EtherNet/IP gateway
Instance 1, attribute 2 stands for the device types. The Open Type Code 0x07 stands for a discrete uni­versal I/O device.
Instance 1, attribute 3 stands for the product code. It is of the type UNIT and thus comprises 2 bytes.
Instance 1, attribute 4 stands for the revision, that means the main and supplementary firmware version of the MSI 430 module, which you can find in the MSI.designer software as the Diagnostics version. You can see both details in the Properties docking window, if you select the controller module in the Modules docking window after you have connected to the station.
Fig.8.4: Display of diagnostic version and hardware version in configuration dialog of the controller module
Instance 1, attribute 5 standard for the current state of the overall device. The data range is listed in the Device state values table in class 1, instance 1, attribute 5 [chapter 8.4.1].
Instance 1, attribute 6 stands for the serial number of the device, which can be found under the hardware configuration in MSI.designer. Instance 1, attribute 7 stands for the product name MSI 430.
Tab.8.4: Overview of the identity class (0x01) supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
1 0 = Class 1 Read UINT Revision 1
1 0 = Class 2 Read UINT Max. instance 1
1 0 = Class 3 Read UINT Number of instances 1
1 0 = Class 6 Read UINT Max. class attribute ID 7
1 0 = Class 7 Read UINT Max. instance attribute ID 7
1 1 1 Read UINT Vendor ID 524 = 0x20c
1 1 2 Read UINT Device type 0x07
1 1 3 Read UINT Product code [chapter
05001
8.4.8.3]
1 1 4 Read USINT[2] Revision, software version
{1, 1} to {99,99}
The “left” byte is the main section and is transmitted first
1 1 5 Read WORD Device state See next table
1 1 6 Read UDINT Serial number 16010001 to
99539999
1 1 7 Read SHORT_
Product name MSI 430
STRING
Leuze electronic MSI 400 74
Page 75
EtherNet/IP gateway
Tab.8.5: Device state values of the MSI 430 module in class 1, instance 1, attribute 5
State value Description Possible system mode
0b0000 xxxx xxxx 0x01 There is at least one EtherNet/IP connection
0b0000 xxxx 0000 010x Device is configured 4 = Idle
0b0000 0001 0000 0x0x Low, removable error 4 = Idle
0b0000 0010 0000 0x0x Low, non-removable error 4 = Idle
0b0000 0100 0000 0x0x Serious, removable error 1 = Init
0b0000 1000 0000 0x0x Serious, non-removable error 7 = Critical error

8.4.2 Assembly Object

All the data of the Class 1 connections are also provided by the Assembly object. The following table offers an overview of this assembly object.
Further information:
• Table Overview of assembly databytes of the MSI 430 module [chapter 8.5.1]
• Figure Data flow with usage of Assembly Instances [chapter 8.6.2] (Shows the data flow in front of the PLC to the module MSI 430 and back from the point of view of the individual assemblies.)
to a PLC (owner of the connection)
4 = Idle 5 = Run 7 = Critical error 21 = Force mode
5 = Run 7 = Critical error 21 = Force mode
5 = Run 21 = Force mode
5 = Run 21 = Force mode
2 = Configuration required 3 = Configuration running
Tab.8.6: Overview of the assembly class (0x04) supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
4 0 = Class 1 Read UINT Revision of the class 2
4 0 = Class 2 Read UINT Max. instance 167
4 0 = Class 3 Read UINT Number of instances 7
4 0 = Class 6 Read UINT Max. class attribute ID 7
4 0 = Class 7 Read UINT Max. instance attribute ID 4
4 37 1 Read UINT Number of members 0
4 37 3 Read,
write
BYTE[50] Bits of the logic outputs [chapter
8.5.2] (Instance 1 to 400 of Class
See
1)
9)
4 37 4 Read UINT Number of data bytes 50
4 57 1 Read UINT Number of members 0
4 57 3 Read BYTE[67] Input bits (Instance 1 to 528 of
See
1)
Class 8)
4 57 4 Read UINT Number of data bytes 67
4 138 1 Read UINT Number of members 0
Leuze electronic MSI 400 75
Page 76
EtherNet/IP gateway
Class Instance Attribute Access Data type Description Data range
4 138 3 Read,
write
BYTE[40] Bits of the logic outputs [chapter
8.5.2] (Instance 81 to 400 of
See
1)
Class 9)
4 138 4 Read UINT Number of data bytes 40
4 139 1 Read UINT Number of members 0
4 139 3 Read,
write
BYTE[30] Bits of the logic outputs [chapter
8.5.2] (Instance 161 to 400 of
See
1)
Class 9)
4 139 4 Read UINT Number of data bytes 30
4 140 1 Read UINT Number of members 0
4 140 3 Read,
write
BYTE[20] Bits of the logic outputs [chapter
8.5.2] (Instance 241 to 400 of
See
1)
Class 9)
4 140 4 Read UINT Number of data bytes 20
4 141 1 Read UINT Number of members 0
4 141 3 Read,
write
BYTE[10] Bits of the logic outputs [chapter
8.5.2] (Instance 321 to 400 of
See
1)
Class 9)
4 141 4 Read UINT Number of data bytes 10
4 167 1 Read UINT Number of members 0
4 167 3 Read BYTE[112] Bits of the logic inputs, mode and
4 167 4 Read UINT Number of data bytes 112
1)
See: Table Overview of assembly databytes of the MSI 430 module [chapter 8.5.1]

8.4.3 Discrete Input Point Object

The discrete input point objects are part of the device profile Discrete universal I/O device.
If an error occurs at the terminal input of a specific instance between 401 and 528 and the MSI 430 module is in Run mode, the value of the instance attribute 4 equals 1. In all other cases, the value equals 0.
Tab.8.7: Overview of the discrete input point objects (0x08) supported by the MSI 430 module
Class Instance Attrib-
ute
8 0 = Class 1 Read UINT Revision of the class 2
8 0 = Class 2 Read UINT Max. instance 584
8 0 = Class 3 Read UINT Number of instances 400 + 128 +
1)
See
state bytes
(More [chapter 8.5.3.2])
Access Data type Description Data range
56 Logic + input + output
8 0 = Class 6 Read UINT Max. class attribute ID 7
8 0 = Class 7 Read UINT Max. instance attribute ID 4
8 1 to 400
1 Read USINT Number of attributes 3 and 529 to 584
8 401 to 528 1 Read USINT Number of attributes 4
8 1 to 528 2 Read USINT[4] List of support attributes {1, 2, 3, 4}
Leuze electronic MSI 400 76
Page 77
EtherNet/IP gateway
Class Instance Attrib-
Access Data type Description Data range
ute
8 529 to 584 2 Read USINT[3] List of support attributes {1, 2, 3}
8 1 to 400 3 Read BOOL The value of the input bit, con-
figured by the output data set1 in
0 = Off,
1 = On MSI.designer, stands for the data transferred by the logic of the con­troller module to the PLC.
8 1 to 400 4 Read BOOL State of output data set 1 0 = OK
8 401 to 416 3 Read BOOL Value of terminals I1 to I16 of the
0, 1 MSI 430 module
8 401 to 416 4 Read BOOL State of terminals I1 to I16 of the
0, 1 MSI 430 module
8 417 to 420 3 Read BOOL Value of terminals IQ1 to IQ4 of the
0, 1 MSI 430 module when configured as an input
8 417 to 420 4 Read BOOL State of terminals IQ1 to IQ4 of the
0, 1 MSI 430 module when configured as an input
8 421 to 430 3 Read BOOL Reserved 0
8 431 3 Read BOOL Value of B1 Voltage is...
0 = Outside
the tolerance
1 = Within
the tolerance
8 432 3 Read BOOL Value of B2 Voltage is...
0 = Outside
the tolerance
1 = Within
the tolerance
8 421 to 432 4 Read BOOL Reserved 0
8 425 + 8xn
to 432 + 8xn
3 Read BOOL Value of terminals I1 to I8 of the
MSI-EM-I8[n] / MSI-EM-IO84[n] module,
0, 1
with n = 1 to 12
8 425 + 8xn
to 432 + 8xn = 528
8 529 to 532 3 Read BOOL Value of terminals Q1 to Q4 of the
4 Read BOOL State of terminals I1 to I8 of the
MSI-EM-I8[n] / MSI-EM-IO84[n] module, where n = 1 to 12
0, 1
0, 1 MSI 430 module
8 533 to 536 3 Read BOOL Value of terminals IQ1 to IQ4 of the
0, 1 MSI 430 module when configured as an output
8 533 + 4xn
to 536 + 4xn
3 Read BOOL Value of terminals Q1 to Q4 of the
MSI-EM-IO84[n] module, where n = 1 to 12
0, 1
= 584

8.4.4 Discrete Output Point Object

The discrete output point objects are part of the device profile Discrete universal I/O device.
Leuze electronic MSI 400 77
Page 78
EtherNet/IP gateway
The MSI 400 system does not permit direct influencing of the security-oriented output terminals. Instead, up to 400 databits can be specified. In this way, it is possible to use the input data blocks1 to5 in MSI.de­signer for bit-wise access. The simplest way to control output terminals with a PLC is by connecting the ap­propriate gateway bit to an output in the logic editor of MSI.designer. The following figure shows an ex­ample:
Fig.8.5: Direct connection of a gateway input bit to an output terminal of the MSI 430 module
WARNING
Check your application thoroughly for correctness!
Because the MSI.designer only checks for logic-internal connection errors, you have to check the following aspects systematically yourself:
Ä Does your application agree with the results from the risk analysis and the avoidance
strategy?
Ä Have all of the applicable standards and guidelines been complied with?
If not, you are placing the machine's operator in danger.
Note that the output terminal is set to Off as standard and thus stands for the value “0”. This value is al­ways used when the controller module is not in Run mode or it the output is not configured via the logic ed­itor in MSI.designer.
The standard value of gateway output bits can be configured using attributes 5 and 6.
If there is a loss of connection between the PLC and the controller module, instance attribute 5 controls whether the gateway data bit is set or not. The specified value is controlled by instance attribute 6.
A write request to attribute 3 of instances 1 to 400 is refused if the Assembly instance 37 [chapter 8.5.2.1] is already linked to an active connection to a PLC.
A write request to attribute 3 of instances 81 to 400 is refused if the Assembly instance 138 [chapter 8.5.2] is already linked to an active connection to a PLC.
A write request to attribute 3 of instances 161 to 400 is refused if the Assembly instance 139 [chapter 8.5.2] is already linked to an active connection to a PLC.
A write request to attribute 3 of instances 241 to 400 is refused if the Assembly instance 140 [chapter 8.5.2] is already linked to an active connection to a PLC.
A write request to attribute 3 of instances 321 to 400 is refused if the Assembly instance 141 [chapter 8.5.2] is already linked to an active connection to a PLC.
Tab.8.8: Overview of the discrete output point objects (0x09) supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
9 0 = Class 1 Read UINT Revision of the class 1
9 0 = Class 2 Read UINT Max. instance 400
9 0 = Class 3 Read UINT Number of instances 400
9 0 = Class 6 Read UINT Max. class attribute ID 7
9 0 = Class 7 Read UINT Max. instance attribute ID 6
9 1 to 400 1 Read USINT Number of attributes 5
9 1 to 400 2 Read USINT[5] List of support attributes {1, 2, 3, 5, 6}
9 1 to 400 3 Write,
read
BOOL The value of the logic output bit,
which is configured by the intput
0 = Off,
1 = On data blocks 1 to 5 in MSI.de­signer, stands for the data trans­ferred by the PLC to the logic of the controller module.
Leuze electronic MSI 400 78
Page 79
EtherNet/IP gateway
Class Instance Attribute Access Data type Description Data range
9 1 to 400 5 Write,
9 1 to 400 6 Write,

8.4.5 Discrete Input Group Object

The discrete input group objects are part of the device profile Discrete universal I/O device.
The object of class 29 plays a role with regard to the alarm bit. It collects the process alarms of all the input terminals of the MSI 430 module as well as the safe input/output expansion modules in one bit. If an error occurs at at least one input terminal and the MSI 430 module is in Run mode, the value of the attribute 5 of instance 1 equals 1. In all other cases, the value equals 0.
Tab.8.9: Overview of the discrete input group object (0x1D) supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
29 0 = Class 1 Read UINT Revision of the class 1
29 0 = Class 2 Read UINT Max. instance 1
29 0 = Class 3 Read UINT Number of instances 1
29 0 = Class 6 Read UINT Max. class attribute ID 7
read
read
BOOL Error action (specified value on
loss of connection to the PLC)
0 = Interfer-
ence value,
1 = Last
state
BOOL Interference value 0 = Off, 1 =
On
29 0 = Class 7 Read UINT Max. instance attribute ID 5
29 1 1 Read USINT Number of attributes 5
29 1 2 Read USINT[5] List of support attributes {1, 2, 3, 4, 5}
29 1 5 Read BOOL Group state of all input terminals

8.4.6 Discrete Output Group Object

The discrete output group objects are part of the device profile Discrete universal I/O device.
The object of class 30 plays a role with regard to the alarm bit. It collects the process alarms of all the out­put terminals of a MSI 430 or MSI-EM-IO84 module in one bit. If an error occurs at at least one output ter­minal and the MSI 430 module is in Run mode, the value of the attribute 5 of instance 1 equals 1. If the MSI 430 module is in Critical error mode, the attribute value is also 1. In all other cases, the value equals
0.
Tab.8.10: Overview of the discrete output group object (0x1D) supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
30 0 = Class 1 Read UINT Revision of the class 1
30 0 = Class 2 Read UINT Max. instance 1
30 0 = Class 3 Read UINT Number of instances 1
(state of instances 401 to 420 of class 8)
0 = No error,
1 = Error
30 0 = Class 6 Read UINT Max. class attribute ID 7
30 0 = Class 7 Read UINT Max. instance attribute ID 6
30 1 1 Read USINT Number of attributes 6
30 1 2 Read USINT[6] List of support attributes {1, 2, 3, 4, 5,
6}
30 1 3 Read USINT Number of bound instances 56
30 1 4 Read UINT[56] Bound instances {1, ..., 56}
Leuze electronic MSI 400 79
Page 80
EtherNet/IP gateway
Class Instance Attribute Access Data type Description Data range
30 1 5 Read BOOL Group state of all output termin-

8.4.7 PCCC Object

PCCC (pronounced “P C Cube”) is used in several PLCs from Rockwell Automation/Allen Bradley, which still continue to be used. It was developed before CIP and EtherNet/IP were defined. PCCC telegrams are either:
a) Encapsulated in CIP packages (e.g. via EtherNet/IP)
b) The encapsulation of CIP packages.
The MSI 430 module supports the encapsulation of PCCC data in CIP packages, as described above un­der b). For this, the class ID 0x67 = 103 was specified.
The PCCC commands listed in the following table are supported by the MSI 430 module.
All PCCC-related data with a size of 16 bits (word) are available in the “Little Endian” format. This means that the byte with the lowest value is executed first.
Tab.8.11: PCCC commands supported by the MSI 430 module
Type CMD FNC Description Command supported by
PLC-5 0x0f 0x00 Word Range Write [chapter 8.4.7.2] PLC‑3, PLC‑5, PLC‑5/250
PLC-5 0x0f 0x01 Word Range Read [chapter 8.4.7.3] PLC‑3, PLC‑5, PLC‑5/250
als (state of instances 529 to 584 of class 8)
0 = No error, 1 = Error
PLC-5 0x0f 0x67 Typed Write [chapter 8.4.7.4] SLC5/03, SLC5/04, PLC5,
PLC‑5/250, PLC‑5/VME
PLC-5 0x0f 0x68 Typed Read [chapter 8.4.7.5] SLC5/03, SLC5/04, PLC5,
PLC‑5/250, PLC‑5/VME
SLC 0x0f 0xa1 Protected Typed Logical Read with 2 Address
Fields [chapter 8.4.7.6]
SLC 0x0f 0xa2 Protected Typed Logical Read with 3 Address
Fields [chapter 8.4.7.8]
MicroLogix-1000, SLC500, SLC5/03, SLC5/04, PLC5
SLC 0x0f 0xa9 Protected Typed Logical Write with 2 Address
Fields [chapter 8.4.7.7]
SLC 0x0f 0xaa Protected Typed Logical Write with 3 Address
Fields [chapter 8.4.7.9]
MicroLogix-1000, SLC500, SLC5/03, SLC5/04
8.4.7.1 PCCC Telegram Structure
Each request telegram comprises 7+5 header bytes.
Tab.8.12: PCCC request header
Name Data type Description Size Data range
Length USINT Header size 1 byte 7
Vendor UINT Vendor ID of the requester 2 byte
S/N UDINT Serial number of the requester 4 byte 0 to 232-1
CMD USINT Command 1 byte 0x0f
STS USINT State 1 byte 0
TNSW UINT Transport sequence number 2 byte 1 to 65535
FNC USINT Function code 1 byte 0x67, 0x68,
0xa2, 0xaa
Each answer telegram comprises 7+4 header bytes or 7+4+1 header bytes, if the state byte is 0xf0.
Leuze electronic MSI 400 80
Page 81
EtherNet/IP gateway
Tab.8.13: PCCC reply header
Name Data type Meaning Size Data range
Length USINT Header size 1 Byte 7
Vendor UINT Vendor ID of requester 2 Byte
S/N UDINT Serial number of requester 4 Byte 0 to 232-1
CMD USINT Command of requester plus Bit 6 set 1 Byte 0x4f
STS USINT Status 1 Byte 0x00, 0x10,
0xf0
TNSW UINT Transport sequence number 2 Byte 1 to 65535
EXT STS USINT Extended Status, only present if STS=0xf0 0 to 1
Byte
8.4.7.2 Word Range Write
The MSI 430 module supports “Write PLC-5 word range” according to the following table:
Tab.8.14: Data structure of PLC-5 Word Range Write
Name Data type Meaning Data range
Packet offset UINT Offset in number of elements
Total Transaction UINT number of elements in transaction
Address BYTE[m] PLC-5 system address, m >= 2
Payload UINT[n] 2xn = Data byte count 0 to 65535
The answer of the MSI 430 module does not contain any data, only a state.
8.4.7.3 Word Range Read
The MSI 430 module supports “Read PLC-5 word range” according to the following table:
Tab.8.15: Read request data structure of PLC-5 word range
Name Data type Description Data range
Packet offset UINT Offset as number of elements
Total Transaction UINT Number of elements in the transaction 0 to value dependent
on the assembly size
Address BYTE[m] PLC-5 system address, m >= 2 “0” to “:”, “A” to “Z”,
“a” to “z”
Size UINT Number of elements to be returned
Tab.8.16: Feedback to the MSI 430 module of Read PLC-5 word range
Name Data type Description Data range
Payload UINT[n] 2•n = number of data bytes (up to 244 bytes) 0to65535
8.4.7.4 Typed Write
The MSI 430 module supports “Write PLC-5 input” according to the following table:
Tab.8.17: Write data structure of PLC-5 input
Name Data type Description Data range
Packet offset UINT Offset as number of elements
Leuze electronic MSI 400 81
Page 82
EtherNet/IP gateway
Name Data type Description Data range
Total Transaction UINT Number of elements in the transaction
Address BYTE[m] PLC-5 system address, m >= 2 See next table
Type ID BYTE[n] Data type and size, n >= 1
The answer of the MSI 430 module does not contain any data, only a state, see table PCCC reply header [chapter 8.4.7.1]. The UINT data format corresponds to writing the format of the word range.
Tab.8.18: Write address structure of PLC-5 input
Address Data type Number of
Description Data range
elements
$N37:x UINT[n] n Output assembly of the device profile Discrete
0to65535
universal I/O device, x = 0 to 24, n = 25 - x
$N138:x UINT[n] n Output assembly of the logic output, con-
0to65535 figured via the input data block 2 to 5 in MSI.designer, x = 0 to 19, n = 20 – x
$N139:x UINT[n] n Output assembly of the logic output, con-
0to65535 figured via the input data block 3 to 5 in MSI.designer, x = 0 to 14, n = 15 – x
$N140:x UINT[n] n Output assembly of the logic output, con-
0to65535 figured via the input data block 4 to 5 in MSI.designer, x = 0 to 9, n = 10 – x
$N141:x UINT[n] n Output assembly of the logic output, con-
0to65535 figured via the input data block 4 to 5 in MSI.designer, x = 0 to 4, n = 5 – x
The data range of the number of elements is relative to the assembly sizes. See the table Overview of as-
sembly databytes of the MSI 430 module [chapter 8.5.1]
8.4.7.5 Typed Read
The MSI 430 module supports “Read PLC-5 input” according to the following table:
Tab.8.19: Read request data structure of PLC-5 word range
Name Data type Description Data range
Packet offset UINT Offset in number of elements
Total Transaction UINT Number of elements in the transaction 0 to value dependent on the
assembly size
Address BYTE[m] PLC-5 system address, m >= 2 “0” to “:”, “A” to “Z”, “a” to “z”
Size UINT Number of elements to be returned
The answer of the MSI 430 module is listed in the following table. The first byte of the type ID is 0x9a = 0b1001 1010, meaning that the data type is given in the following byte and the data size in the byte after that. The fourth byte of the type ID is 0x42 = 0b01000010, standing for an integer data type of size 2.
Leuze electronic MSI 400 82
Page 83
EtherNet/IP gateway
Tab.8.20: Feedback to the MSI 430 module for reading the data structure of the PLC-5 input
Name Data type Description Data range
Type ID BYTE Data type and size Bit0 to 3: 10 = Size specific-
ation in the next but one byte
Bit4 to 7: 9 = Type in the next byte
Type ID BYTE Data type 9 = Field of the same ele-
ments
Type ID BYTE Number of following bytes 1ton+1
Type ID BYTE Data type and size Bit0 to 3: 2 = UINT
Bit4 to 7: 4 = Integer
Payload UINT[n] 2⋅n = Number of data bytes 0to65535
The command data of all assembly instances can be recorded using “Read input”.
In contrast to native addressing of EtherNet/IP assembly instances, the PLC-5 system address contains an element offset which can be used.
The MSI 430 module supports fields (arrays) of UINT as PCCC data types. Due to the odd size of the as­sembly instance 57, the firmware contained in the MSI 430 module assigns an additional byte, to provide an even number of bytes.
The address scheme supported by the MSI 430 module for Read PLC-5 input is shown in the following table:
Tab.8.21: Read address structure of PLC-5 input
Address Data type Number
Description Data range of ele­ments
$N57:x UINT[n] n Input assembly of the device profile Dis-
crete I/O device ,
x = 0 to 33, n = 34 - x
$N167:x UINT[n] n Input assembly of:
Logic input bits
(n = 1-x to 25-x, x = 0 to 24)
System state and system mode
(n = 26-x, x = 0 to 25)
State bytes of the controller module
(n = 27-x to 56-x, x = 26 to 55)
Element 1 to 33: 0to65535
Element 34 Bit 0 to 7 (LSB): 0x00, 0x40, 0x80, 0xc0
Element 34 Bit 8 to 15 (MSB): 0
0to65535
Bit 0 to 7 (LSB): System mode (1, 2, 3, 4, 5, 7, 21)
Bit 8 to 15 (MSB): Sys­tem state (0x00, 0x40, 0x80, 0xc0)
0to65535
Example: “$N57:10” and “Total Transaction = 24” address elements 11 to 34 correspond to bytes 20 to 66 of assembly instance 57.
Note: Byte 67, which is not specified in assembly instance57, is also transferred.
Note: The position of the word data with system state and system mode are dependent on the requested amount of data “x”.
8.4.7.6 Protected Typed Logical Read with 2 Address Fields
The MSI 430 module supports “Read SLC-protected logic input” according to the following table:
Leuze electronic MSI 400 83
Page 84
Tab.8.22: Request data structure for Read SLC-protected logic input with two address fields
Name Data type Description Data range
EtherNet/IP gateway
Byte size USINT Number of data bytes to be
read
Assembly instance 37: 0to50
Assembly instance 57: 0to67
Assembly instance 167: 0to112
File number USINT Assembly instance ID 37, 57, 167
File type USINT Data type 0x89 = Integer data
Element number USINT Offset = ID of the first ele-
ment of the answer
Assembly instance 37: 0 to 24 – Size/2
Assembly instance 57: 0 to 33 – Size/2
Assembly instance 167: 0 to 55 – Size/2
Tab.8.23: Feedback to the MSI 430 module for Read SLC-protected logic input with two address fields
Name Data type Description Data range
Payload UINT[n] 2⋅n = Number of data bytes 0to65535
8.4.7.7 Protected Typed Logical Write with 2 Address Fields
The MSI 430 module supports “Write SLC-protected logic input” according to the following table:
No support is required for assembly instances 138 to 141. The offset, i.e. the first byte, is instead specified by the element number.
Tab.8.24: Request data structure for Write SLC-protected logic input with two address fields
Name Data type Description Data range
Byte size USINT Number of data bytes to be written 0to50
File number USINT Assembly instance ID 37
File type USINT Data type 0x89 = Integer data
Element number USINT Offset = ID of the first element to be sent back 0 to 24 – Size/2
Payload UINT[n] n = Size/2 0to65535
8.4.7.8 Protected Typed Logical Read with 3 Address Fields
The MSI 430 module supports “Read SLC-protected logic input” according to the following table:
Tab.8.25: Request data structure for Read SLC-protected logic input with three address fields
Name Data type Description Data range
Size USINT Number of data bytes to be
read
Assembly instance 37: 0to50
Assembly instance 57: 0to67
Assembly instance 167: 0to112
File number USINT Assembly instance ID 37, 57, 167
File type USINT Data type 0x89 = Integer data
Element number USINT Offset = ID of the first ele-
ment of the answer
Assembly instance 37: 0 to 24 – Size/2
Assembly instance 57: 0 to 33 – Size/2
Assembly instance 167: 0 to 55 – Size/2
Subelement USINT Doesn’t matter 0 to 254 (for number of bytes 1)
8.4.7.9 Protected Typed Logical Write with 3 Address Fields
The MSI 430 module supports “Write SLC-protected logic input” according to the following table:
Leuze electronic MSI 400 84
Page 85
EtherNet/IP gateway
Tab.8.26: Request data structure for Write SLC-protected logic input with three address fields
Name Data type Description Data range
Size USINT Number of data bytes to be written 0to50
File number USINT Assembly instance ID 37
File type USINT Data type 0x89 = Integer data
Element number USINT Offset = ID of the first element of the an-
Subelement USINT Doesn’t matter 0 to 254 (for number of
Payload UINT[n] n = Size/2 0to65535

8.4.8 Vendor Object

The Vendor Object with class ID = 0x78 provides CRC, status and diagnostic data which are not covered by device profile General Purpose Discrete I/O Device. Furthermore it supplies an interface to input and output data in a compressed and therefore network traffic saving format.
Note that several instances have different attribute types and numbers. Packing several data together into this vendor object class is made for legacy reasons.
8.4.8.1 Instance 1
Instance 1, attributes 1 to 50, supply input bytes configured by the output data set1 in MSI.designer. This is data transferred by the logic of the controller module to the PLC.
8.4.8.2 Instance 2
Instance 2, attribute 1, supplies the CRC of the active project file created by MSI.designer. Instance 2, at­tributes 2 to 8 are reserved for future applications.
0 to 25 – Size/2
swer
bytes 1)
8.4.8.3 Instance 3
Instance 3, attributes 1 to 60 make state bytes available. The descriptions for each bit are listed in the table State bytes of the controller module MSI 420/430 [chapter 8.4.8.7]. This data corresponds to data set 3, which is described at various points in this document.
A value = 1 for bits in instance 3, attributes 1 to 60, stands for “OK”/”Not used”/”Reserved”. A value = 0 stands for “Fault” or “Error” or “Outside the limit”. “Doesn’t matter” means that the value can be equal to 0 or 1.
"EA module at Pos. n" with n = 1 .. 12 stands for the first to twelfth safe or unsafe expansion module.
8.4.8.4 Instance 4
The instance 4, attributes 1 to 60 are reserved for future use. Values are zero and changes are reserved.
8.4.8.5 Instance 5
Attribute 1 of instance 5 makes the system state/mode of the controller module available. The values are listed in the following table:
Tab.8.27: System state/modes of the MSI 430 module
System state/mode Value
Supply voltage A1/2 available 0
Initialization 1
Configuration / project file required 2
Configuration running / project file being downloaded 3
Idle 4
Leuze electronic MSI 400 85
Page 86
EtherNet/IP gateway
i
System state/mode Value
Run 5
Critical error 7
Force mode 21
8.4.8.6 Instance 6
Attribute 1 of instance 6 makes the error code of the most recent error of the controller module available. A value = 0 means that no error has occurred. Attribute 2 supplies the error code of the previous error, etc., up to and including attribute 5.
8.4.8.7 Instance 7
Attributes 1 to 50 of instance 7 represent the input data blocks 1 to 5 in MSI.designer. They represent the data transferred by the PLC to the logic of the controller module.
Attributes 1 to 50 of instance 7 possess the same data as assembly instance 37, byte 0 to 49.
NOTICE
You can find an explanation of the technical terms used below here: Abbreviations and Defini­tions [chapter 1.5]
Tab.8.28: Overview of th vendor-specific object (Leuze electronic, 0x78), supported by the MSI 430 module
Class Instance Attribute Access Data type Description Data range
120 0 = Class 1 Read UINT Revision of the class 1
120 0 = Class 2 Read UINT Max. instance 4
120 0 = Class 3 Read UINT Number of instances 4
120 0 = Class 5 Read UINT[3] List of optional services {2, 0x4c, 0x4d}
120 0 = Class 6 Read UINT Max. class attribute ID 7
120 0 = Class 7 Read UINT Max. instance attribute ID 60
120 1 n+1 Read USINT The input byte “n”, con-
figured by the output data set1 in MSI.designer, stands for the data trans­ferred by the logic of the controller module to the PLC. n = 0 to 49.
120 2 1 Read UDINT Project file CRC (data set 2) 0 to 232-1
120 2 2to8 Read UDINT Reserved (data set 2) 0
120 3 n+1 Read BYTE State byte“n” of the control-
ler module, for which n = 0 to 59
0to255
0to255
120 4 n+1 Read BYTE Additional byte“n” of the
controller module, for which n = 0 to 59
120 5 1 Read USINT MSI 430 System mode
(See [chapter 8.4.8.5])
Leuze electronic MSI 400 86
0
1, 2, 3, 4, 5, 7, 21
Page 87
EtherNet/IP gateway
Class Instance Attribute Access Data type Description Data range
120 6 n Read UDINT Error code in the controller
0 to 232-1 module, with n=1 for the most re­cently occurred error, n=2 for the previous error, etc., with n = 1 to 5
120 6 1 Write UDINT Clear error list in instance 6 0
120 7 n+1 Write,
read
BYTE Output bit “n”, which is con-
figured by the input data
0to255
blocks 1 to 5 in MSI.de­signer, stands for the data transferred by the PLC to the logic of the controller mod­ule. n = 0 to 49.
Tab.8.29: State bytes of the controller module MSI 420/430
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 Control-
ler mod­ule State, voltage
Controller module Collective error fast shut-off
Controller module State, voltage B1
Controller module Configura­tion state
Controller module State, voltage A1/2
Controller module External module state
Controller module Internal module state
Reserved
B2
1 Control-
ler mod­ule Output data state
2 Control-
ler mod­ule I8 Test pulse er­ror
3 Control-
ler mod­ule I16 Test pulse er­ror or HW limit fre­quency I16
4 Cable
break at I16
Controller module Input data state
Controller module I7 Test pulse error
Controller module I15 Test pulse error or HW limit frequency I15
Cable break at I15
Reserved Reserved Controller
module IQ3+IQ4 overcur­rent
Controller module I6 Test pulse error
Controller module I14 Test pulse error or HW limit frequency I14
Cable break at I14
Controller module I5 Test pulse error
Controller module I13 Test pulse error or HW limit frequency I13
Cable break at I13
Controller module I4 Test pulse error
Controller module I12 Test pulse error
Controller module IQ4 (input) Test pulse error
Controller module IQ1+IQ2 overcur­rent
Controller module I3 Test pulse error
Controller module I11 Test pulse error
Controller module IQ3 (input) Test pulse error
Controller module Q3+Q4 overcur­rent
Controller module I2 Test pulse error
Controller module I10 Test pulse error
Controller module IQ2 (input) Test pulse error
Controller module Q1+Q2 overcur­rent
Controller module I1 Test pulse error
Controller module I9 Test pulse error
Controller module IQ1 (input) Test pulse error
Leuze electronic MSI 400 87
Page 88
EtherNet/IP gateway
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
5 Control-
ler mod­ule I15/ I16 Dual channel state
6 Inversion
error I14 vs. I16
7 I16 Stuck
at low
8 Control-
ler mod­ule Q4 Stuck at low
9 Control-
ler mod­ule IQ4 (output) Stuck at low
Controller module I13/I14 Dual channel state
Inversion error I13 vs. I15
I16 Stuck at high
Controller module Q4 Stuck at high
Controller module IQ4 (out­put) Stuck at high
Controller module I11/I12 Dual channel state
Frequency difference I14 vs. I16
I15 Stuck at low
Controller module Q3 Stuck at low
Controller module IQ3 (out­put) Stuck at low
Controller module I9/ I10 Dual channel state
Frequency difference I13 vs. I15
I15 Stuck at high
Controller module Q3 Stuck at high
Controller module IQ3 (out­put) Stuck at high
Controller module I7/ I8 Dual channel state
Phase dif­ference I14 vs. I16 too low
I14 Stuck at low
Controller module Q2 Stuck at low
Controller module IQ2 (out­put) Stuck at low
Controller module I5/ I6 Dual channel state
Phase dif­ference I13 vs. I15 too low
I14 Stuck at high
Controller module Q2 Stuck at high
Controller module IQ2 (out­put) Stuck at high
Controller module I3/ I4 Dual channel state
Controller module IQ3/IQ4 Dual channel state
I13 Stuck at low
Controller module Q1 Stuck at low
Controller module IQ1 (out­put) Stuck at low
Controller module I1/ I2 Dual channel state
Controller module IQ1/IQ2 Dual channel state
I13 Stuck at high
Controller module Q1 Stuck at high
Controller module IQ1 (out­put) Stuck at high
10 Re-
served
11 Re-
served
8 + 4⋅n
9 + 4⋅n
Re­served
IO mod­ule at pos. n Output data state
1. Gate­way mod­ule Output data state
2. Gate­way mod­ule Output data state
IO module at pos. n Collective error fast shut-off
IO module at pos. n Input data state
1. Gate­way mod­ule Input data state
2. Gate­way mod­ule Input data state
IO module at pos. n State, voltage
1. Gate­way mod­ule Configura­tion state
2. Gate­way mod­ule Configura­tion state
IO module at pos. n Configura­tion state
Doesn’t matter
Doesn’t matter
Doesn’t matter
A1/2 (power supply for Q1 to Q4)
Reserved Reserved IO module
at pos. n I7/I8 Dual channel state
Reserved 1. Gate-
way mod­ule Internal module state
Reserved 2. Gate-
way mod­ule Internal module state
IO module at pos. n External module state
IO module at pos. n I5/I6 Dual channel state
IO module at pos. n Internal module state
IO module at pos. n I3/I4 Dual channel state
Doesn’t matter
Doesn’t matter
Doesn’t matter
IO module at pos. n I2/I1 Dual channel state
Leuze electronic MSI 400 88
Page 89
EtherNet/IP gateway
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
10 + 4⋅n
IO mod­ule at pos. n I8 test pulse er-
IO module at pos. n I7 test pulse er­ror
ror
11 + 4⋅n
IO mod­ule at pos. n Q4 Stuck-at
IO module at pos. n Q4 Stuck-at high
low

8.5 Supported Assembly data

Assemblies are collections of data attributes and are optimized for high performance and a low telegram overhead. The MSI 430 module supports a series of predefined, static assembly instances for input and output data. Access is possible via various instances of the CIP assembly object. In addition, access is possible both via the implicit and explicit message transmission. The assembly size is variable. It is thus possible to request parts of an assembly. The following table (Overview of assembly databytes of the MSI 430 module [chapter 8.5.1]) offers an overview of the supported assembly instances and the meaning of the transmitted data.

8.5.1 List of Assembly data

IO module at pos. n I6 test pulse er­ror
IO module at pos. n Q3 Stuck-at low
IO module at pos. n I5 test pulse er­ror
IO module at pos. n Q3 Stuck-at high
IO module at pos. n I4 test pulse er­ror
IO module at pos. n Q2 Stuck-at low
IO module at pos. n I3 test pulse er­ror
IO module at pos. n Q2 Stuck-at high
IO module at pos. n I2 test pulse er­ror
IO module at pos. n Q1 Stuck-at low
IO module at pos. n I1 test pulse er­ror
IO module at pos. n Q1 Stuck-at high
Tab.8.30: Overview of assembly databytes of the MSI 430 module
Instance Byte Access Data type Description Size Data range
37 0to49 Write,
read
BYTE[50] Logic output bytes, configura-
tion via Input data block 1 to 5
1 to 50 Bytes
0 to 0xff
in MSI.designer (see [chapter
8.5.2])
138 10to49 Write,
read
BYTE[40] Logic output bytes, configura-
tion via Input data block 2 to 5
1 to 40 Bytes
0 to 0xff
in MSI.designer (see [chapter
8.5.2])
139 20to49 Write,
read
BYTE[30] Logic output bytes, configura-
tion via Input data block 3 to 5
1 to 30 Bytes
0 to 0xff
in MSI.designer (see [chapter
8.5.2])
140 30to49 Write,
read
BYTE[20] Logic output bytes, configura-
tion via Input data block 4 and
1 to 20 Bytes
0 to 0xff
5 in MSI.designer (see [chapter
8.5.2])
141 40to49 Write,
read
BYTE[10] Logic output bytes, configura-
tion via Input data block 5 in
1 to 10 Bytes
0 to 0xff
MSI.designer (see [chapter
8.5.2])
57 0to49 Read BYTE[50] Logic output bytes, configura-
tion via Output data block 1 in
1 to 50 Bytes
0 to 0xff
MSI.designer (see [chapter
8.5.3])
50to65 Read BYTE[16] Values of the input terminals Ix 1 to 16
0 to 0xff
Bytes
66 Read BYTE Input and output state 1 byte 0x00, 0x40,
0x80, 0xc0
Leuze electronic MSI 400 89
Page 90
EtherNet/IP gateway
Instance Byte Access Data type Description Size Data range
167 0to49 Read BYTE[50] Logic output bytes, configura-
tion via Output data block 1 in
1 to 50 Bytes
0 to 0xff
MSI.designer (see [chapter
8.5.3])
50 Read BYTE Bit7: Input state
Bit6: Output state
1 byte 0x00, 0x40,
0x80, 0xc0
Bit5: Error code ≠ 0
51 Read BYTE System mode 1 byte 1, 2, 3, 4, 5,
7, 21
52to111 Read BYTE[60] State bytes of the controller
60 byte 0 to 0xff
module (Instance 3 of class 120
[chapter 8.4.8.3]), output data set 3 (siehe [chapter 8.5.3])
The data type of supported assemblies is BYTE which means strings of 8 bits each. The naming in Logix Designer is SINT, which has the same size of 8 bits each.
If PLC requires a configuration assembly, any value or blank can be used for assembly instance. Size of the configuration assembly shall be zero.
Please use assembly instances from Table "Overview of Assembly data bytes [chapter 8.5.1]" for Input and Output. These settings can be used in generic EtherNet module configuration in Logix Designer which can be seen in the illustration below.
Fig.8.25: Generic Ethernet module configuration
Leuze electronic MSI 400 90
Page 91

8.5.2 Assembly Instances for Logic Output Bytes

8.5.2.1 Assembly Instance 37 = 0x25
Assembly instance 37 belongs to the device profile discrete universal I/O device. It contains output data (O→T) with a scope of up to 50 bytes.
Assembly instance 37 corresponds to input data block1 to 5 of the logic data of the MSI 430 module with a total scope of 50 bytes.
8.5.2.2 Assembly Instances 138 = 0x8a to 141 = 0x8d
Assembly instances 138 to 141 are provided to make more than one output data connection available. In Class 1 connections, output data from the PLC to the controller module can only be sent using “Exclusive Owner” rights. If, for example, a PLC “possesses” the assembly instance 138, then it “possesses” the out­put bytes 10 to 49. By contrast, output bytes 0 to 9 are freely available and can be used by another PLC (O→T).
In a further example, the first PLC “possesses” 10 output bytes of the assembly instance 37, whilst the second PLC “possesses” 10 output bytes of assembly instance 138 and the third assembly instance 139 with 30 output bytes. Here, three PLCs possess “Exclusive Owner” connections with output data. In total, up to five PLCs can share the output data range, each with 10 bytes.
Assembly instance 138 comprises data with a scope of up to 40 bytes, assembly instance 139 comprises data with a scope of up to 30 bytes, assembly instance 140 comprises data with a scope of up to 20 bytes and assembly instance 141 comprises data with a scope of up to 10 bytes.
The first byte of assembly instance 138 is the eleventh byte of the logic data of the MSI 430 module. In MSI.designer, it has the designation input data block2. The first byte of assembly instance 139 is 21. Byte of the logic data of module MSI 430. In MSI.designer, it has the designation input data block3. The first byte of assembly instance 140 is 31. Byte of the logic data of module MSI 430. In MSI.designer, it has the designation input data block4. The first byte of assembly instance 141 is 41. Byte of the logic data of module MSI 430. In MSI.designer, it has the designation input data block5.
Write requests are refused if the assembly is already used by an active I/O connection.
EtherNet/IP gateway

8.5.3 Assembly Instances for Logic Input Bytes

8.5.3.1 Assembly Instance 57 = 0x39
Assembly instance 57 belongs to the device profile discrete universal I/O device. It contains output data (T→O) with a scope of up to 67 bytes.
The first 50 bytes of assembly instance 57 correspond to the output data set1 of the logic data of the MSI 430 module. The following table explains the meaning of bytes 50 to 66. Data of the class 1 connection
“Logic output (1 to 400) and logic/physical input” [chapter 8.3.1]
Leuze electronic MSI 400 91
Page 92
EtherNet/IP gateway
Fig.8.26: Example of the display of assembly instance 57 in the Logix Designer
8.5.3.2 Assembly Instances 167 = 0xa7
Assembly instance 167 possesses a different data structure to instance 57. Instance 167 makes the data available in the MSI 400 system in more detail.
Assembly instance 167 in the MSI 400 system comprises data (T→O) with a scope of up to 112 bytes.
8.5.3.2.1 Byte 0 to 49
Assembly instance 167 corresponds to output data block1 to 5 of the logic data of the MSI 430 module with a total scope of 50 bytes.
Here, attributes 1 to 50 are represented as with instance 57.
8.5.3.2.2 Byte 50
Bit 7 of byte 50 of assembly instance 167 has the same value as the class 29 instance 1 attribute5, which represents the group status of all physical inputs.
Bit 6 of byte 50 of assembly instance 167 has the same value as the class 30 instance 1 attribute5, which represents the group status of all physical outputs.
Bit 5 of byte 50 of assembly instance 167, if set, indicates that an error code in class120 instance6 attrib­ute1 is non-zero.
Bits 0 to 4 of byte 50 of assembly instance 167 byte are reserved for future use.
8.5.3.2.3 Byte 51
Byte 51 of assembly instance 167 supplies the system mode of the controller modules. It shows the same value as attribute 1 of instance 5 in class 120.
8.5.3.2.4 Byte 52 to 111
Bytes 52 to 111 of assembly instance 167 make the corresponding state bytes of the controller mode avail­able. They show the same value as attributes 1 to 60 of instance 3 in class 120.
Leuze electronic MSI 400 92
Page 93

8.6 Accessing to CIP objects

8.6.1 Explicit Messaging

Explicit message transmission uses the TCP/IP protocol as well as an EtherNet/IP-specific encapsulation layer. Explicit message transmission can be connection-free (UCMM) and connected, e.g. session-based. The latter is termed Class 3 Messaging. Both UCMM and Class 3 use an EPATH to address the required data. An EPATH is made up of the service, class, instance and attribute ID.
With explicit message transmission, each attribute of the following objects can be accessed:
• Identity class (0x01) [chapter 8.4.1]
• Assembly class (0x04) [chapter 8.4.2]
• Discrete input point object (0x08) [chapter 8.4.3]
• Discrete output point object [chapter 8.4.4]
• Discrete einput group object (0x1D) [chapter 8.4.5]
• Discrete output group object (0x1D) [chapter 8.4.6]
• Vendor-specific object (0x78) [chapter 8.4.8.7]
Each request must possess a valid EPATH referring to the required object/attribute. The appropriate attrib­ute can be read using the GetAttributeSingle service, if it is labeled as Read in these tables. The appropri­ate attribute can be written using the SetAttributeSingle service, if it is labeled as Write in these tables.
EtherNet/IP gateway

8.6.2 Implicit Messaging

Implicit message transmission uses EtherNet/IP, the UDP/IP protocol as well as an EtherNet/IP-specific en­capsulation layer. Implicit message transmission is also termed Transport Class 1. The PLC can set up a Class 1 connection with the MSI 430 module, by placing the service request Forward_Open with it. This configures connection information for the exchange of input/output data, e.g. the RPI unicast or multicast connections, amongst other things. Class 1 connections only support assemblies for the exchange of input/ output data or “wild cards” to signal data-free heartbeat connections. Configuration assemblies are accep­ted as part of the Forward_Open-Service, with the exception of TCP/IP objects (Class 0xF5), although are not processed by the MSI 430 module.
As the configuration details of the connection are only sent once in the Forward_Open-Frame, implicit mes­sage transmission is aligned to performance and has a lower telegram overhead than explicit message transmission. Assembly instances possess predefined attributes in a specific order. Nonetheless, the sender, i.e. the PLC; specifies the data size in Forward_Open during the setup of the Class 1 connection. This means that only data byte from the beginning of the instance up to the specified size are exchanged.
The MSI 430 module supports seven static assembly instances. These are listed in the table Overview of the assembly class (0x04) supported by the MSI 430 module [chapter 8.4.2]. All data members of the in­stance has fixed coding. Dynamic assembly instances are not currently supported by the MSI 430 module.
An I/O assembly contains either input or output data, but not both at the same time. The following figure shows the data flow when multiple assembly instances are used. Predefined assemblies are interconnec­ted by blue lines, vendor-specific assemblies by black lines. The controller module is shown as a hatched rectangle.
Leuze electronic MSI 400 93
Page 94
EtherNet/IP gateway
Assembly instance 138
Assembly instance 37
Assembly instance 139
Assembly instance 140
Assembly instance 141
Assembly instance 57
Assembly instance 167
Input terminals
Input state
Logic inputs
System mode
System state bits
Logic outputs
Output
state
Output terminals
External sensors
External actuators
Fig.8.27: Data flow when using assembly instances of the MSI 430 module

8.6.3 Symbolic Addressing

In addition to the addressing of assembly instances, symbolic addressing by name is also possible by se­lecting connections.
In MSI.designer, tag names can be changed in the Gateway configuration tab.
Leuze electronic MSI 400 94
Page 95
EtherNet/IP gateway
i
Fig.8.28: Configuration of symbolic names for assemblies in MSI.designer
NOTICE
The functions of the UCMM Message Client (unconnected), which can also be configured in MSI.designer, are not available in the module version D-01.01.

8.7 Adjust Performance

A configuration of the number of process data bytes exactly matching the application helps to reduce the volume of periodically exchanged data bytes.
The PLC specifies the number of output bytes in the form of specific Forward_Open Service data as Con- nection Size for O→T. The PLC should set the Fixed/Variable bit to 1, meaning variable.
The PLC also specifies the number of input bytes. The controller module cyclically transfers data in the scope of the connection size for T→O through RPI in the value specified in Forward_Service. If the fixed/
variable bit is set by the PLC, meaning variable, then not all the assembly bytes must be transmitted.

8.8 Connection with more than one PLC

The EtherNet/IP function of the MSI 430 module allows access by more than one PLC. Up to five encapsu­lation sessions with input and output data can be set up simultaneously.
If only reading of the process data of the MSI 430 module is required, “Input only” or “Listen only” connec­tions can also be used. Note that a “Listen only” connection is closed automatically by the MSI 430 module when the owner, who has set up the “Exclusive” or “Input Only” connection, terminates the connection.
If process data from multiple PLCs are to be transmitted to the MSI 430 module, the other PLCs can ac­cess the assembly instances 138 to 141 for Class 1 connections. Class 3 connections can be set up in par­allel, provided that there is no conflict with regard to the owner. Please see the following for more informa­tion: List of Assembly data [chapter 8.5.1]
Leuze electronic MSI 400 95
Page 96

8.9 Diagnostics and troubleshooting

8.9.1 Notifications via network

8.9.1.1 Explicit Message Connection
Device Status is available by reading Class 1, instance 1, attribute 5. Vendor specific interface for alarms and diagnostic for Explicit Message Connections is defined as follows:
Presence of process alarm can be detected by reading class 29, instance 1, attribute 5 and class 30, in­stance 1, attribute 5. The module mode (Run or another state) has to be checked, because the alarm bit is set to 0 = OK every time the module is not in Run mode.
The module mode can be detected by reading class 120 Instance 5 Attribute 1.
The presence of module diagnostic events can be detected by reading class 120 Instance 6 Attribute 1.
Detailed reasons for process alarms and system diagnostic events can be found out by reading all 60 at­tributes of Class 120 Instance 3 which contains the dedicated system status bytes.
8.9.1.2 Implicit Message Connection
If assembly instance 57 is used, Bit 6 and 7 of Byte 66 signal a process alarm when set.
If assembly instance 167 is used, Bit 6 and 7 of Byte 66 signal a process alarm when set. Bit 5 signals dia­gnostic events or process alarms when set.
Event details can be queried by Explicit Message requests as described here: Explicit Messaging [chapter
8.6.1]
EtherNet/IP gateway

8.9.2 LED States

8.9.2.1 MS (Module Status)
The MSI 430 module possesses a two-color (red/green) LED with the designation MS. This is the Module Status Indicator.
The Module Status Indicator is dark, if no power supply is connected. It flashes green if the device has not been configured. It turns green if the device is running correctly. It flashes green/red if the device is per­forming a switch-on test.
The Module Status Indicator flashes red if EtherNet/IP is activated and the device has detected a serious, eliminable error. A faulty project file or one which does not match the hardware is classified as a serious, eliminable error. The display turns red if EtherNet/IP is activated and the device has detected a serious, non-eliminable error and there is a Critical Fault.
Tab.8.31: MS-LED state (Selection)
Project file System mode Ext. Error MS-LED state
Doesn’t matter Switch on Doesn’t matter Green -> Red
Deleted Init Doesn’t matter Flashing green
Invalid Init Doesn’t matter Flashing red
Valid Idle mode Doesn’t matter Flashing green
Valid Run No Turns green
Valid Run Yes Turns green/red or flashes red
Valid Critical error Doesn’t matter Turns red
8.9.2.2 NET (Network Status)
The MSI 430 module possesses a two-color (red/green) LED with the designation NET. This is the Net­work Status Indicator.
Leuze electronic MSI 400 96
Page 97
Tab.8.32: Meaning of the NET LED (used as EtherNet/IP gateway)
NET LED Meaning / reason
EtherNet/IP gateway
LED off
• Power supply not connected. or
• Power supply connected but IP address not configured.
EtherNet/IP has been activated and an IP address has been configured but
Green (1
there is no CIP connection and an “Exclusive Owner” connection has not yet shown a time-out.
Hz)
Green
An IP address has been configured, there is at least one CIP connection (of any transport class) and an “Exclusive Owner” connection has not yet shown a time-out.
During power-on test
/
Red/green
EtherNet/IP has been activated, an IP address has been configured and an
Red
“Exclusive Owner” connection, for which the device is the target device, has shown a time-out.
The Network Status Indicator is dark if no power supply is connected or a power supply is connected but no IP address is configured (interface configuration attribute of the TCP/IP interface object). It flashes green if EtherNet/IP is activated and an IP address has been configured but no CIP connection is available and an “Exclusive Owner” connection has not yet shown a time-out. It turns green if an IP address has been con­figured, there is at least one CIP connection (of any transport class) and an “Exclusive Owner” connection has not yet shown a time-out. It flashes green/red if the device is performing a switch-on test.
The Network Status Indicator flashes red if EtherNet/IP is activated, an IP address has been configured and an “Exclusive Owner” connection, for which the device is the target device, has shown a time-out. The Network Status Indicator only turns green again when all the expired “Exclusive Owner” connections have been restored. The Network Status Indicator switches from flashing red to being lit in green if all the con­nections of the previously expired O->T connection points have been restored. Time-outs in other connec­tions than the "Exclusive Owner” connections do not result in the indicator flashing red. The “flashing red” state only applies to connections with the target device. PLCs and CIP routers do not instigate a transition to this state if a created or routed connection shows a time-out.
Tab.8.33: Troubleshooting on the MSI 430 module (use as EtherNet/IP gateway)
Error Possible cause Possible remedy
Key: LED off / LED flashes / LED lights up
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
MS LED
Green
• The MSI 430 has been configured for data transmission to the PLC, but no Ethernet commu­nication has been estab­lished or the communic­ation is faulty.
• Duplicate IP address detected. Another net­work device has the same IP address.
• Incorrectly formatted PROFINET device name
• PROFINET IO must be ac­tivated in the project file. At least one Ethernet link must be established. Check the Ethernet wiring, check the Ethernet settings in the PLC and in MSI.designer.
• Correct the IP address and switch the system off and on again.
• Compare the device name between the PROFINET master and the MSI 430 module.
Leuze electronic MSI 400 97
Page 98
Error Possible cause Possible remedy
EtherNet/IP gateway
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
MS LED
/
Red/green
The MSI 430 module does not provide any data.
LED PWR
LED LINK
Green
Green
LED /ACT
Yellow
MS LED
Green (1 Hz)
• Configuration required.
• The configuration has not yet been fully trans­mitted.
• The module version does not support any PROFINET IO.
• The MSI 400 system is in the stop state.
• Configure the MSI 430 module with a project file in which PROFINET IO is ac­tivated and transfer the configuration to the MSI 430 module.
• Use an MSI 430 device starting with module ver­sion B-xx.
• Start the controller module (switch to Run mode).
The MSI 430 module does not provide any data.
LED PWR/
Green
EC
LED LINK
Green
LED /ACT
Yellow
MS LED
Green
The MSI 430 / the MSI 400 system is in the “Critical error” state.
• The IP address for the MSI 430 module is as­signed by a DHCP server. Following a re­start of the MSI 430 module or the DHCP server, another address was allocated to the MSI 430 module, which is unknown to the PLC.
• The MSI 430 module is not properly connected to the MSI 400 modules.
• The module connection plug is dirty or dam­aged.
• Another MSI 400 mod-
• Either assign the MSI 430 module a permanent IP ad­dress or reserve a perman­ent IP address for the MSI 430 module in the DHCP server (manual assignment using the MAC address of the MSI 430 module).
• Insert the I/O module cor­rectly. Clean the connection plug and socket.
• Switch on the power supply again.
• Check the other MSI 400 modules.
ule has an internal crit­ical error.
8.9.2.3 LINK
The MSI 430 module possesses a green LED with the designation LINK. If there is no Ethernet connection, it stays dark. If there is a connection, it switches on.
8.9.2.4 ACT (Activity Status)
The MSI 430 module possesses a green LED with the designation ACT. If no port activity can be detected, it stays dark. If port activity is detected, it switches on.
Leuze electronic MSI 400 98
Page 99

8.9.3 Diagnostic functions in the configuration software

i
Additional diagnostic functions are available on the SD card using a log file with the name history.csv. In addition, the last entries are available in MSI.designer in the Diagnostics view. The timestamp in the Local
time column provides information about how long the device has been switched on in total.
Synchronize time
With the safety controller connected you can synchronize the time on the safety controller with the time on the connected diagnostics computer. Even if you disconnect the connection to the controller, the Dia- gnostics view remains active, as long as the associated MSI.designer project is open.
NOTICE
Instructions in software manual
You can find step-by-step instructions on how to synchronize the time here:
Software manual, chapter "Synchronize time for diagnostic purposes"
EtherNet/IP gateway

8.10 State bits

The EtherNet/IP gateway MSI-EN-IP sets state bits, which are available in the logic editor of MSI.designer for processing.
Tab.8.34: Meaning of the state bits MSI-EN-IP[0] in the logic editor
Name of the state bits Set to 1, if ... Reset to 0 ...
Output state ... a GetAttribute command was
Input state ... a SetAttribute command was
Internal state ... the EtherNet/IP function of the
processed successfully,
or
... data of transport class 1 were sent to a PLC without errors.
processed successfully,
or
... data of transport class 1 received without error (consumed), whereby heartbeat data of connection point 198 from the PLC does not count
module is ready for communication.
... if a connection of transport class 1 (implicit connection) was terminated and no further connec­tion exists.
... a connection of transport class 1 (implicit connection) was termin­ated for one of the connection points 57, 138, 139, 140 or 141 and no further connection exists to these connection points.
... the EtherNet/IP function of the module is not ready for communic­ation.
Leuze electronic MSI 400 99
Page 100

9 PROFIBUS DP gateway

LED BF (red)
LED MS (red/green)
LED PWR (red/green)
Address switch 1
PROFIBUS connection
Address switch 2
The following MSI 400 gateway can be used for PROFIBUS DP:
• MSI-FB-PROFIBUS

9.1 Interfaces and operation

Operating and display elements
PROFIBUS DP gateway
Fig.9.1: Operating and display elements of the MSI-FB-PROFIBUS module
Tab.9.1: Meaning of the state LEDs on the MSI-FB-PROFIBUS module
LED Meaning
Key: LED off / LED flashes / LED lights up
BF
Off
Red
Connection to the DP master established
No bus connection: Field bus cabling interrupted, ad­dress error or the master is no longer transmitting to the bus
MS
Off
Green
Green
Power supply switched on, waiting for bus-off
Run
Stop
Run, but the gateway has a fault
/
Red / green
1 Hz: Configuration required or is taking place right
Red
now
2 Hz: Critical error on the gateway
Leuze electronic MSI 400 100
Red
Critical error on another module
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use