Moeller DeviceNet NZM-XDMI612 User manual

NZM-XDMI612
DeviceNet Interface
Moeller GmbH
Industrieautomation
Hein-Moeller-Straße 7–11
D-53115 Bonn
E-Mail: info@moeller.net
Internet: www.moeller.net
© 2005 by Moeller GmbH
Änderungen vorbehalten
AWB1230-1527GB Doku/Doku 04/05
Printed in the Federal Republic of Germany (0x/02)
Article No.: xxxxxx
4*patpks#nycmyn*
NZM-XDMI612
User Manual
04/05 AWB1230-1572GB
A
A A
Think future. Switch to green. Think future. Switch to green.
Rückenbreite bis 10 mm (1 Blatt = 0,106 mm für XBS)

All brand and product names are trademarks or registered
trademarks of the owner concerned.
1st published 2005, edition date 04/05
© Moeller GmbH, 53105 Bonn
Author: Lothar Jagusch
Editor: Heidrun Riege
Translator: David Long
All rights reserved, including those of the translation.
No part of this manual may be reproduced in any form
(printed, photocopy, microfilm or any other process) or
processed, duplicated or distributed by means of electronic
systems without written permission of Moeller GmbH, Bonn.
Subject to alteration without notice.
Rückenbreite festlegen! (1 Blatt = 0,106 mm)

I
Before commencing the installation
• Disconnect the power supply of the device.
• Ensure that devices cannot be accidentally
restarted.
• Verify isolation from the supply.
• Earth and short circuit.
• Cover or enclose neighbouring units that
are live.
• Follow the engineering instructions (AWA)
of the device concerned.
• Only suitably qualified personnel in accordance
with EN 50110-1/-2 (VDE 0105 Part 100) may
work on this device/system.
• Before installation and before touching the
device ensure that you are free of electrostatic
charge.
• The functional earth (FE) must be connected to
the protective earth (PE) or to the potential
equalisation. The system installer is responsible
for implementing this connection.
• Connecting cables and signal lines should be
installed so that inductive or capacitive
interference does not impair the automation
functions.
• Install automation devices and related
operating elements in such a way that they are
well protected against unintentional operation.
• Suitable safety hardware and software
measures should be implemented for the
I/O interface so that a line or wire breakage
on the signal side does not result in undefined
states in the automation devices.
• Ensure a reliable electrical isolation of the low
voltage for the 24 volt supply. Only use power
supply units complying with IEC 60364-4-41
(VDE 0100 Part 410) or HD 384.4.41 S2.
• Deviations of the mains voltage from the rated
value must not exceed the tolerance limits given
in the specifications, otherwise this may cause
malfunction and dangerous operation.
• Emergency stop devices complying with
IEC/EN 60204-1 must be effective in all
operating modes of the automation devices.
Unlatching the emergency-stop devices must
not cause restart.
• Devices that are designed for mounting in
housings or control cabinets must only be
operated and controlled after they have been
installed with the housing closed. Desktop or
portable units must only be operated and
controlled in enclosed housings.
• Measures should be taken to ensure the proper
restart of programs interrupted after a voltage
dip or failure. This should not cause dangerous
operating states even for a short time. If
necessary, emergency-stop devices should be
implemented.
• Wherever faults in the automation system may
cause damage to persons or property, external
measures must be implemented to ensure a safe
operating state in the event of a fault or
malfunction (for example, by means of separate
limit switches, mechanical interlocks etc.).
Moeller GmbH
Safety instructions
Warning!
Dangerous electrical voltage!


1
04/05 AWB1230-1572GB
About This Manual 3
Target group 3
Additional manuals 3
Writing conventions 3
1 DeviceNet connection 5
System overview 6
Scope of functions 7
Commissioning the DeviceNet interface 8
Supported messages 9
– Data exchange via I/O messages 9
– Data access via explicit messages 13
– Write data 16
–Readdata 16
– Updating of process data 17
– Read diagnostics data from the circuit-breaker 18
– Circuit-breaker-specific commands 19
2Data 21
Reading circuit-breaker data 21
Writing circuit-breaker data 27
Circuit-breaker-specific commands 29
Circuit-breaker communication status 31
Circuit-breaker parameters 34
–SettingsIrand Idn 34
–SettingsIifor ZM2-... and ZM4-... 35
–SettingsIifor ZM3-... 36
–SettingsIsd 37
–SettingsTr, Tsd, Tvdn 38
Circuit-breaker identification 39
Circuit-breaker functionality 40
Contents

3
04/05 AWB1230-1572GB
About This Manual
Target group This manual has been produced for automation technicians
and engineers. Fundamental knowledge concerning the
DeviceNet fieldbus and programming of a DeviceNet master
control is assumed. Furthermore, you should be familiar with
the handling of the easy control relay and the
communication system NZM-XDMI612.
Additional manuals The following operating manuals should be followed:
• “Circuit-Breaker Communication System”
(AWB1230-1441GB),
• “EASY222-DN, DeviceNet Slave Interface"
(AWB2528-1427GB).
All manuals are available on the Internet for download as
PDF files. For a fast search enter the documentation number
as the search criterion at http://www.moeller.net/support:
Writing conventions Except for the first page of chapters and empty pages at the
end, the top left of the page shows the chapter title and the
top right of the page shows the current section for greater
clarity.
Xindicates actions to be taken.
hIndicates interesting tips and additional information
hCaution!
Warns of a danger of minor damage.

About This Manual
4
04/05 AWB1230-1572GB
Abbreviations and symbols used in this manual have the
following meanings:
AE Distribution circuit protection Electronic
AEF Distribution circuit protection Electronic, Fixed
setting
DMI Data Management Interface
HEX Hexadecimal (Number system based on 16)
ID Identifier
ME Motor protection Electronic
MS-LED ModuleStatus LED
NS-LED Network-Status LED
NZM Circuit-breaker in general
SE Short circuit protection Electronic
VE Full protection Electronic
VEF Full protection Electronic, Fixed setting

5
04/05 AWB1230-1572GB
1 DeviceNet connection
In this manual the exchange of data between the circuit-
breaker NZM with DMI and a DeviceNet system is described.
The interface that is used is the EASY222-DN communication
module, which provides several functions specifically for
operation with the DMI.
The description in this manual is restricted to the functions
that are typical for power circuit-breakers. Detailed
information can be found in asection “Additional
manuals”, page 3.

DeviceNet connection
6
04/05 AWB1230-1572GB
System overview The communication module EASY222-DN has been
developed for automation tasks with the DeviceNet fieldbus.
Figure 1: Integration of EASY222-DN in the DeviceNet
aMaster area, PLC (e.g.: SLC 500) or PC with CAN card
bSlave area e.g.: DMI or control relay easy with DeviceNet
connection
cCircuit-breaker area
a
b
c

Scope of functions
7
04/05 AWB1230-1572GB
Scope of functions EASY222-DN supports the I/O messages and explicit
messages of the predefined master/slave connection setting.
EASY222-DN enables the following functions in conjunction
with the DMI:
• Reading of the NZM status and DMI inputs via
I/O messages
asection “Read NZM status and DMI inputs”, page 9,
• Setting the DMI outputs via I/O messages
asection “Setting the DMI outputs”, page 12,
• Access to all data of the circuit-breaker and the DMI via
explicit messages
asection “Data access via explicit messages”, page 13.

DeviceNet connection
8
04/05 AWB1230-1572GB
Commissioning the
DeviceNet interface
Detailed information concerning the installation and design
of the EASY222-DN can be found in aAWB2528-1427GB,
sections 1 and 2.
The following steps are necessary for commissioning of the
EASY222-DN interface:
XConnect the EASY222-DN via the “EASY-Link” connector
to the DMI (basic unit).
To plug the connector into the DMI, push up the cover flap
on the right side of the housing.
XConnect the 24 V DC power supply for the EASY222-DN
(Do not switch it on just yet!).
XConnect the 5-pole DeviceNet connector to the
EASY222-DN.
The pin assignments can be found in
aAWB2528-1427GB.
XCheck that all connections are correct.
XSwitch on the power supply for the DMI and the interface.
XSet the required bus node address via the display and the
keypad on the DMI.
The procedure can be found in aAWB1230-1441GB.
XConfigure the DeviceNet system with the EASY222-DN as
a new station.
XStart the DeviceNet system.
After these steps the EASY222-DN interface should be in the
“not online” (MS-LED lights continuously green, NS-LED is
off) or “online without active communication connection“
(MS-LED lights continuously green, NS-LED flashes green)
state.
hA complete overview of all LED status displays to assist
quick analysis of the problem can be found in a
AWB2528-1427GB, section 3.

Supported messages
9
04/05 AWB1230-1572GB
Supported messages Data exchange via I/O messages
The exchange of the process data is implemented in
DeviceNet with the assistance of I/O messages.
The most important I/O messages can be used to quickly
access the most important status data of the circuit-breaker
or to change the outputs of the DMI.
Read NZM status and DMI inputs
The data is output via polled I/O messages.
3 data bytes are transmitted, which are arranged as follows:
Byte 0:
hBefore data can be read or set using I/O messages an
active communication connection must be established to
the DeviceNet interface. Detailed information can be
found in aAWB2528-1427GB, Section “Management
objects”.
Meaning Bit
7 6 5 4 3 2 1 0
not used –
Input 5 1/0
Input 4 1/0
not used –
not used –
not used –
not used –
not used –

DeviceNet connection
10
04/05 AWB1230-1572GB
Byte 1:
1) Without motor starter function.
2) With reversing starter.
Byte 2:
Inputs 0 to 3 of the DMI can be assigned to 24 V signals as required.
1) Without motor starter function.
2) With reversing starter.
3) With DOL starter.
Meaning Bit
7 6 5 4 3 2 1 0
Overload 1 1/0
Input 2 1/0
Input 31)/clockwise)1/0
Ready to switch on 1/0
NZM status 1/0 1/0
NZM position 1/0 1/0
Meaning Bit
7 6 5 4 3 2 1 0
Load warning 1/0
Cause of tripping 1/0 1/0 1/0
Input 0 1/0
Reserved 0
Central warning 1/0
Input 11)/anti-clockwise2) or
ON/OFF3)
1/0

Supported messages
11
04/05 AWB1230-1572GB
Meaning of data
1) Precondition: auxiliary contacts are connected to the NZM.
Cause of
tripping
Indicates the cause of the trip present at the moment.
000 No trip
001 Trip Ir
010 Trip Ii
011 Trip Isd
100 Trip Idn
101 Trip Com or Trip Temp (detail can be read out through diagnostics)
110 Overcurrent on neutral pole
Ready to
switch on
The circuit breaker is switched off (not tripped!)
Inputs 0 to 5 Status of the digital inputs on the DMI
Load warning At least one phase current is over the load warning limit (Ir= 70 %).
Reserved Used for internal purposes. Must not be used by the user!
Central
warning
Set if the circuit-breaker reported either a warning or a trip.
NZM status Indicates the actual status of the circuit-breaker
00 Initialisation in progress
01 Circuit-breaker is OFF1)
10 Circuit-breaker is ON1)
11 Circuit-breaker has tripped1)
NZM position 01 Normal operation of the circuit-breaker
11 Circuit-breaker faulty or not present
Overload 1 At least one phase current is above the overload 1 limit
(Ir= 100 %)

DeviceNet connection
12
04/05 AWB1230-1572GB
Setting the DMI outputs
The outputs of the DMI can be controlled directly via I/
Omessages.
3 data bytes are transmitted, which are arranged as follows:
Byte 0: always 14hex
Byte 1:
1) With reversing star/delta starter.
2) With star/delta DOL starter.
3) With reversing starter.
4) Without motor starter function.
5) With DOL starter.
Byte 2:
Meaning Bit
7 6 5 4 3 2 1 0
Output 4 1/0
Output 3/reserved)1/0
Output 2/reserved2) 1/0
Output 1/anti-clockwise 3) 1/0
Output 04)/ON5)/clockwise5) 1/0
Reserved 0
Actuate circuit-breaker 1/0 1/0
Meaning Bit
7 6 5 4 3 2 1 0
Remote operator mode 1/0
Reserved 1/0
Output 5 1/0
Reserved 0
Reserved 0
Reserved 0

Supported messages
13
04/05 AWB1230-1572GB
Outputs 0 to 3 of the DMI can be written according to the
motor starter function that has been selected.
Outputs 4 and 5 can either be set as freely addressable
(Remote operator mode = 1), or controlled via “Actuate
circuit-breaker” (Remote operator mode = 0).
Data access via explicit messages
Explicit messages serve reading or writing access to all
supported data objects such as
• Management objects,
• Connection objects,
• Application-specific objects.
The management objects (identity object and message
router object) and the connection objects (DeviceNet object
and connection object) incorporate general services, which
are necessary for operation of the device on the DeviceNet.
The application-specific objects (assembly object and easy
object) enable application-specific preparation of the data.
For communication with the circuit-breaker or with the DMI,
a portion of the easy object is used.
Reserved 0
Reserved 0
Meaning Bit
7 6 5 4 3 2 1 0

DeviceNet connection
14
04/05 AWB1230-1572GB
Table 1: Overview of the supported objects
hThe detailed description of the individual objects can be
found in aAWB2528-1427GB, section 4.
Object Class ID Instance ID Attribute ID Note
[hex] [hex] [hex]
Management objects
Identity Object 01 01 01 to 07,
9.0 A
aAWB2528-1427
Message Router
Object
02 01 –
Connection object
DeviceNet Object 03 01 01 to 04
Connection Object 05 01 to 14 –
Application-
specific objects
Assembly Object 04 100 to 102 –
easy Object 64 01 02
03 aNZM status and
DMI inputs, page 9
04 aDMI outputs,
page 12
61, 62, 69 extended access via
command code;
service code: 32hex
hCaution!
easy-specific objects may not be used for operation with
the DMI. Only objects from Table 1 are permissible.

Supported messages
15
04/05 AWB1230-1572GB
In the following only the use of the easy object for scanning
and entering the NZM and DMI data is described.
All data of the circuit-breaker or the DMI can be accessed or
modified by use of the easy object. The easy object with
Class ID: 64hex, Instance ID 01 and Service Code: 32hex is
used.
The attribute defines if it is a read access on one or two bytes
or a write access on one byte. In the data field the details of
the address to which the attribute refers (achapter 2,
page 21), and if applicable, the byte to be written, are
contained.
The following table makes the association clear.
Table 2: Attributes for explicit message accesses to the data
memory of the DMI
Attribute Command Operand
Address H byte Address L byte Date
61hex Read 1 byte 0Address in the DMI
data rangea
page 21.
–
62hex Read 2 bytes –
69hex Write 1 byte Value

DeviceNet connection
16
04/05 AWB1230-1572GB
Write data
Using the easy object and the command code described in
atable 1, the DeviceNet telegram can write a byte to the
EASY222-DN. The telegram has the following content:
The EASY222-DN responds with the value “00” in the
telegram data fields.
Read data
Using the easy object and the command code described in
atable 1, the DeviceNet telegram can request one or two
bytes from the EASY222-DN. The telegram has the following
content:
The EASY222-DN responds with a telegram, which feeds
back the used address in the first two data fields, followed
by the data actually requested (1 or 2 bytes, depending on
the attribute).
Class ID: 64hex
Instance ID: 01
Attribute: 69hex
Service Code: 32hex (extended access)
1st or 2nd data byte: Address
3rd data byte: Value to be written
Class ID: 64hex
Instance ID: 01
Attribute: 61hex (1 Byte), 62hex (2 bytes)
Service Code: 32hex (extended access)
1st or 2nd data byte: Address
Other manuals for DeviceNet NZM-XDMI612
1
Table of contents
Other Moeller Recording Equipment manuals