SEW-Eurodrive MOVIDRIVE Series User manual

10/262/97
T
MOVIDRIVE®
Drive Inverters
DeviceNet DFD11A Fieldbus Interface
Manual
Edition 11/98
0919 6714 / 1198
Device Net

2
MOVIDRIVE
®
DeviceNet DFD11A
Important Notes
Important Notes
• Read this manual carefully before you start the installation and startup of
MOVIDRIVE®
drive inverters with the DFD11A DeviceNet option.
This manual assumes that the user has access to and is familiar with the documentation on
the MOVIDRIVE®
system, in particular the MOVIDRIVE® system manual.
•Safety notes:
Always follow the safety and warning instructions contained in this manual!
Safety notes are marked as follows:
Electrical hazard, e.g. when working on live wires.
Mechanical hazard, e.g. when working on hoists.
Important instructions for safe and fault-free operation of the driven machine/
system, e.g. pre-setting before startup.
•General safety notes on bus systems:
This communication system allows you to match the MOVIDRIVE®
drive inverter to the spe-
cifics of your application to a very high degree. As with all bus systems, there is a danger of
invisible, external (as far as the inverter is concerned) modifications to the parameters which
give rise to changes in the inverter's behavior. This may result in unexpected (not uncon-
trolled, though!) system behavior.
• Each unit is manufactured and tested to current SEW-EURODRIVE technical standards and
specifications.
The manufacturer reserves the right to make changes to the technical data and designs as
well as the user interface herein described, which are in the interest of technical progress.
A requirement of fault-free operation and fulfillment of any rights to claim under guarantee is
that this information is observed.

MOVIDRIVE
®
DeviceNet DFD11A
3
Contents
Contents
1 Introduction ...................................................................................... 4
2 Installation....................................................................................... 6
2.1 Supported unit types .............................................................................................6
2.2 Installation of the option card ................................................................................6
2.3 Pin assignment......................................................................................................6
2.4 Shielding and routing of the bus cables.................................................................7
2.5 Bus termination .....................................................................................................7
2.6 Setting the DIP switches........................................................................................8
2.7 Display elements....................................................................................................8
2.7.1 Power-up sequence.....................................................................................8
2.7.2 ModNet LED ................................................................................................9
2.7.3 PIO LED.......................................................................................................9
2.7.4 BIO LED.....................................................................................................10
2.7.5 BUSOFF LED..............................................................................................10
3 Project Planning and Startup ............................................................... 11
3.1 Inverter control mode fieldbus.............................................................................11
3.2 Setting up the DeviceNet network using the DeviceNet Manager software ..........13
3.2.1 Installing the EDS file ................................................................................13
3.2.2 Connecting the device to an existing network............................................13
3.3 Process data exchange ........................................................................................14
3.3.1 Polled I/O...................................................................................................14
3.3.2 Bit-strobe I/O.............................................................................................18
3.4 Parameter data exchange.....................................................................................20
3.4.1 The SEW parameter data channel..............................................................20
4 Sample Application with PLC Type SLC500 .............................................. 26
4.1 Exchange of polled I/O (process data) .................................................................28
4.2 Exchange of bit strobe I/O ...................................................................................30
4.3 Exchange of explicit messages (parameter data).................................................31
5 Technical Data ................................................................................ 35
6 Appendix ....................................................................................... 36
6.1 General error codes .............................................................................................36
6.2 Statement of conformance...................................................................................37
6.3 Definitions of terminology ...................................................................................46
7 Index ............................................................................................ 47

4
MOVIDRIVE
®
DeviceNet DFD11A
1 Introduction
1 Introduction
This user manual for the DeviceNet (DFD11A) option describes how to install the DFD11A
DeviceNet option card in the drive inverter and how to start up the MOVIDRIVE®
on the DeviceNet
fieldbus system.
As well as explaining all settings on the fieldbus interface, this document also deals with the vari-
ous DeviceNet connection variants in the form of brief startup examples.
As well as this manual on the DeviceNet option, you should request the following publications deal-
ing with the topic of fieldbuses in more detail, so as to permit MOVIDRIVE®
to be connected to the
DeviceNet fieldbus system in a straightforward and effective fashion:
• “MOVIDRIVE®
Fieldbus Unit Profile” manual
• “MOVIDRIVE®
” system manual
The manual for the MOVIDRIVE®
fieldbus unit profile describes the fieldbus parameters and their
coding, as well as explaining the whole range of various control concepts and application options
in the form of brief examples.
The “MOVIDRIVE®
” system manual contains a listing of all parameters of the drive inverter which
can be read and/or written via the various communications interfaces such as RS-485 and also via
the fieldbus interface.
The MOVIDRIVE®
drive inverter in conjunction with the DFD11A option enables you to make the
connection to master automation systems via DeviceNet, thanks to the high-performance, univer-
sal fieldbus interface of the DFD11A option.
MOVIDRIVE®
and DeviceNet
The device behavior of the inverter which forms the basis of DeviceNet operation is referred to as
the device profile. It is independent of any particular fieldbus and is therefore a uniform feature.
This provides you, the user, with the opportunity of developing applications irrespective of the
fieldbus. As a result, it is very easy to change over to other bus systems such as INTERBUS
(DFI11A option), PROFIBUS (DFP11A option) or CAN bus (DFC11A).
MOVIDRIVE®
offers you direct access to all drive parameters and functions via the DeviceNet inter-
face. The drive inverter is controlled via the high-speed, cyclical process data. Via this process data
channel, you can enter setpoints such as the setpoint speed, ramp generator time for acceleration/
deceleration, etc. as well as triggering various drive functions such as enable, control inhibit, nor-
mal stop, rapid stop, etc. However, at the same time you can also use this channel to read back
actual values from the drive inverter, such as the actual speed, current, device status, fault number
and also reference signals.
The parameters of the inverter are set exclusively by using Explicit Messages, whereas the process
data exchange is replicated on the DeviceNet services of Polled I/O or Bit-Strobe I/O. This parame-
ter data exchange enables you to implement applications in which all the important drive parame-
ters are stored in the master programmable controller, so that there is no need for manual
parameter settings on the drive inverter itself.

MOVIDRIVE
®
DeviceNet DFD11A
5
Introduction 1
Every DeviceNet option card is designed so the fieldbus-specific MAC-ID and baud rate settings are
made using hardware switches on the option card. This manual setting means the drive inverter
can be integrated into the DeviceNet environment and switched on within a very short period of
time. The parameter setting process can be performed in a completely automated fashion by the
DeviceNet master (parameter download). This future-oriented variant offers the advantages of
shortening the system startup time and simplifying the documentation of your application pro-
gram, because all the important drive parameters can now be stored directly in your control pro-
gram.
01922AEN
Fig. 1: DeviceNet with MOVITRAC
®
31C, MOVIDRIVE
®
, MOVIDYN
®
and PLC
Using a fieldbus system requires additional monitoring functions in the drive engineering, e.g. time
monitoring of the fieldbus (fieldbus timeout) as well as rapid stop concepts. For example, you can
specifically adapt the monitoring functions of MOVIDRIVE®
to your application. You can determine,
for instance, which fault reaction of the drive inverter should be triggered in the event of a bus
error. A rapid stop is a good idea for many applications, although this can also be achieved by
“freezing” the last setpoints so the drive continues operating with the most recently valid setpoints
(e.g. conveyor belt). The range of control terminal functions is also ensured in fieldbus mode, so
you can continue to implement rapid stop concepts independent of the fieldbus by means of the
drive inverter terminals.
The MOVIDRIVE®
drive inverter offers you numerous diagnostic options for startup and service
purposes. For example, you can use the integrated fieldbus monitor to check both the setpoints
sent by the master control and the actual values.
Furthermore, you are supplied with numerous additional items of information about the status of
the fieldbus option card. The fieldbus monitor function in conjunction with the MX_SHELL PC soft-
ware offers you an easy-to-use diagnostic facility permitting all drive parameters to be set (includ-
ing the fieldbus parameters) as well as displaying the fieldbus and device status information in
detail.
MOVITRAC 31C
®MOVIDRIVE®
MOVIDYN®
SPS
Communication Interface

6
MOVIDRIVE
®
DeviceNet DFD11A
2 Installation
2 Installation
2.1 Supported unit types
The DFD11A option for the DeviceNet connection can be operated with all drive inverters in the
MOVIDRIVE®
series.
2.2 Installation of the option card
Before you begin:
• Take suitable measures to dissipate any electrical charge in your body before you touch the
option card (discharge strap, conductive shoes, etc.).
• Keep the option card in its original packaging and do not remove it until it is to be installed.
• Do not touch the option card more than necessary, and only hold it by the edge of the circuit
board. Do not touch any components.
Installing the option card:
• De-energize the inverter. Switch off the mains and the 24 V supply, if used.
• Remove the lower hood cover from the control module.
• Unscrew the electronics shield clamp.
• Remove the black cover plate.
• Insert the option card into the guide rails of the OPTION1 slot and push it in.
• Insert option card by applying moderate pressure on the front panel. The option card has been
installed correctly when it is flush with the control card.
• Screw the electronics shield clamp back on.
• Put the hood cover of the control module back on.
• The DFD11 option card is now fully installed.
2.3 Pin assignment
The assignment of connecting terminals is described in the DeviceNet
specification Volume I, Appendix A.
02119AEN
Fig. 2: Pin assignment
Pin no. Abbrev. Meaning Color
1V- 0V24black
2 CAN_L CAN_L blue
3 DRAIN DRAIN shiny
4 CAN_H CAN_H white
5 V+ 24V red
Table 1: Connection terminal CAN bus
1
2
3
4
5
DFD11A
option card

MOVIDRIVE
®
DeviceNet DFD11A
7
Installation 2
The DeviceNet option card is opto-decoupled on the driver side in accordance with the DeviceNet
specification (Volume I, Chapter 9). This means the CAN bus driver must be powered with 24 V via
the bus cable.
The required cable is also described in the DeviceNet specification (Volume I, Appendix B). The
connection must be made according to the color code specified in Table 1.
2.4 Shielding and routing of the bus cables
Having the bus cable correctly shielded reduces electrical interference which can occur in an indus-
trial environment. The following measures ensure the best possible shielding:
• Fasten the retaining screws of plugs, modules and potential compensating cables until finger-
tight.
• Apply the bus cable shielding on both ends.
• Do not route the signal and bus cables in parallel to the power cables (motor leads); use sepa-
rate cable ducts if at all possible.
• Use only metal, grounded cable racks in industrial environments.
• Route the signal cables and the associated potential compensation closely to each other at the
shortest distance.
• Avoid using plug connections to extend bus cables.
• Route the bus cables in close proximity to existing grounding surfaces.
• Use bus connectors with a metal-plated or metal housing.
IMPORTANT!
In the event of fluctuations in the ground potential, a compensating current may flow along the
shield which is connected at both ends and to the ground potential (PE). In this case, make ade-
quate provision for potential compensation in accordance with the relevant VDE regulations.
2.5 Bus termination
In order to avoid disruptions in the bus system due to reflections etc., each DeviceNet segment
must be terminated with 120 Ωbus terminating resistors at the first and last physical participant.
The bus terminating resistor must be wired between terminals 2 and 4 of the bus connector.

8
MOVIDRIVE
®
DeviceNet DFD11A
2 Installation
2.6 Setting the DIP switches
There are two DIP switch blocks of 4 DIP switches each on the DFD11A DeviceNet card. Two DIP
switches are used for setting the baud rate and 6 for setting the MAC-ID (Media Access Control
Identifier). The MAC-ID represents the node address of the DFD11A.
2.7 Display elements
The display elements comprise 4 bicolor LEDs.
2.7.1 Power-up sequence
All LEDs are tested after the unit is switched on. The LEDs are switched on in the following
sequence as part of the test:
The power-up test is always performed unless the fieldbus is powered with 24 V!
Function Abbrev. Number of bits Representation Labeling Meaning
MAC-ID NA 6 bits
e.g. MAC-ID = 2
NA5..0 0..63
Baud rate DR 2 bits
e.g. 10: 500 kbaud
DR1..0 00: 125 kbaud
01: 250 kbaud
10: 500 kbaud
11: Invalid
Table 2: MAC-ID and baud rate setting
Function Abbreviation
Module/network status LED ModNet
Polled I/O PIO
Bit-strobe I/O BIO
Bus off BUSOFF
Table 3: Display elements
Time ModNet LED PIO LED BIO LED BUSOFF LED
0 ms Green Off Off Off
250 ms Red Off Off Off
500 ms Off Green Off Off
750 ms Off Red Off Off
1000 ms Off Off Green Off
1250 ms Off Off Red Off
1500 ms Off Off Off Green
1750 ms Off Off Off Red
2000 ms Off Off Off Off
Table 4: Power-up LED test
S1
S2
NA5
NA4
NA3
NA2
NA1
NA0
01
S1
S2 DR1
DR0
01

MOVIDRIVE
®
DeviceNet DFD11A
9
Installation 2
2.7.2 ModNet LED
The range of functions of the ModNet LED (module/network status LED) is defined in the DeviceNet
specification. Its range of functions is described in Table 5.
2.7.3 PIO LED
The PIO LED checks the polled I/O connection (process data channel). Its range of functions is
described in Table 6.
Status LED Message
Not switched on/
off-line Off • Unit is in off-line status • Unit is performing DUP-MAC check
• Unit is switched off
On-line and in
operational mode Flashes green (1 s cycle) • The unit is on-line and no connection has been set up • DUP-MAC check was performed successfully
• No connection has yet been established with a master
• No configuration, wrong configuration or configuration not complete
On-line, operational
mode and connected
Green • On-line
• Connection has been established with a master
• Connection is active (established state)
Minor fault or
connection timeout
Flashes red
(1 s cycle)
• A correctable error has occurred
• Polled I/O or/and bit-strobe I/O connections are in timeout status
• A correctable error has occurred in the unit
Critical fault or
critical link failure
Red • A non-correctable error has occurred
•BusOff
• DUP-MAC check has detected an error
Table 5: Status table of the ModNet LED
Status LED Message
DUP-MAC check Flashes green
(125 ms cycle)
• Unit is performing the DUP-MAC check
Not switched on/
off-line but not DUP-
MAC check
Off • Unit is in off-line status
• Unit is switched off
On-line and in
operational mode Flashes green (1 s cycle) • The unit is on-line • DUP-MAC check was performed successfully
• A PIO connection is being established with a master (configuring status)
• No configuration, wrong configuration or configuration not complete
On-line, operational
mode and connected
Green • On-line
• A PIO connection has been established (established status)
Minor fault or
connection timeout
Flashes red
(1 s cycle)
• A correctable error has occurred
• Polled I/O connection is in timeout status
Critical fault or
critical link failure
Red • A non-correctable error has occurred
•BusOff
• DUP-MAC check has detected an error
Table 6: Status table of the PIO LED

10
MOVIDRIVE
®
DeviceNet DFD11A
2 Installation
2.7.4 BIO LED
The BIO LED checks the bit-strobe I/O connection. Its range of functions is described in Table 7.
2.7.5 BUSOFF LED
The BUSOFF LED displays the physical status of the bus node. Its range of functions is described in
Table 8.
Status LED Message
DUP-MAC check Flashes green
(125 ms cycle)
• Unit is performing the DUP-MAC check
Not switched on/
off-line but not DUP-
MAC check
Off • Unit is in off-line status
• Unit is switched off
On-line and in opera-
tional mode Flashes green (1 s cycle) • The unit is on-line • DUP-MAC check was performed successfully
• A BIO connection is being established with a master (configuring state)
• No configuration, wrong configuration or configuration not complete
On-line, operational
mode and connected
Green • On-line
• A BIO connection has been established (established state)
Minor fault or connec-
tion timeout Flashes red (1 s cycle) • A correctable error has occurred • Bit-strobe I/O connection is in timeout state
Critical fault or critical
link failure
Red • A non-correctable error has occurred
• BusOff
• DUP-MAC check has detected an error
Table 7: Status table of the BIO LED
Status LED Message
NO ERROR Off • The number of bus errors is in the normal range (error active
state).
BUS WARNING
Flashes red
(125 ms
cycle)
• The unit is performing a DUP-MAC check and cannot send
any messages because no other participants are connected to
the bus (error passive state).
Flashes red
(1 s cycle)
•The number of physical bus errors is too high. No more error
telegrams are actively written to the bus (error passive state).
BUS ERROR
Red • BusOff status
• The number of physical bus errors has continued to grow
despite the switch to the error passive state. Access to the
bus is deactivated.
Table 8: Status table of the BUSOFF LED

MOVIDRIVE
®
DeviceNet DFD11A
11
Project Planning and
Startup 3
3 Project Planning and Startup
This chapter describes how to start up the MOVIDRIVE® inverter with the DFD11A option, using
MX_SHELL (from version 1.30) or the DBG11A keypad (from version .13).
3.1 Inverter control mode fieldbus
After the DeviceNet option card has been installed and the baud rate and MAC-ID have been set
(using the DIP switches), the parameters for the MOVIDRIVE®
inverter can be set immediately via
the fieldbus system without further manual adjustment. All drive parameters can be downloaded in
this manner from the master programmable controller directly via DeviceNet after the power is
switched on.
The inverter has to be switched to the appropriate
control mode prior to control via DeviceNet. This
can be done with parameter P100
Setpoint source and P101 Control signal source . The factory set-
tings for these parameters are the values
Bipol./Fix. setp. or Terminals (setpoint processing via
analog setpoint and control via input terminals). The setting P100 Setpoint source =
FIELDBUS
causes the inverter to get its setpoints from the fieldbus; if P101 = FIELDBUS , the inverter is con-
trolled via the fieldbus (i.e. enable, rapid stop, normal stop, controller inhibit, etc.). MOVIDRIVE®
will now respond to the process output data transmitted from the master programmable controller.
Activation of the
fieldbus control mode is signalled to the master control by the PA data enabled bit
in the status word.
For safety reasons, the inverter must also be enabled on the terminal side for control via the field-
bus system. Accordingly, the terminals must be wired up or programmed in such a way that the
inverter is enabled via the input terminals. The easiest way of enabling the inverter on the terminal
side is to wire input terminal DI00 (/CONTROLLER INHIBIT function) to the +24 V signal and pro-
gram input terminals DI01 to DI05 to NO FUNCTION.

12
MOVIDRIVE
®
DeviceNet DFD11A
3Project Planning and
Startup
Procedure for startup of the MOVIDRIVE® inverter with fieldbus interface:
1. Switch the drive inverter to ENABLE on the terminal side
Wire input terminal DI00 (/CONTROLLER INHIBIT function) to the +24 V signal (e.g. with a
jumper).
01267AEN
2. Control mode = FIELDBUS
Use parameters P100 and P101 to switch control and setpoint processing of the servo inverter
to FIELDBUS.
3. Input terminal DI01 = NO FUNCTION
Input terminal DI02 = NO FUNCTION
Input terminal DI03 = NO FUNCTION
Input terminal DI04 = NO FUNCTION
Input terminal DI05 = NO FUNCTION
Program the function of input terminals DI01 to DI05 to NO FUNCTION with parameters P600
to P604.
P100 Setpoint source FIELDBUS
P101 Control signal source FIELDBUS
P600 Binary input DI01 NO FUNCTION
P601 Binary input DI02 NO FUNCTION
P602 Binary input DI03 NO FUNCTION
P603 Binary input DI04 NO FUNCTION
P604 Binary input DI05 NO FUNCTION
X13:
DI00
DI01
DI02
DI03
DI04
DI05
V024
DCOM
DNDG
ST11
ST12
X10:
VI24
DGND
TF1
DGND
DB00
DO02
VO24
DO01-C
DO01-NO
DO01-NC +
-
/Controller inhibit
No function
No function
No function
No function
No function
Reference X13: DI00-05
+24V
Reference potential binary signals
RS-485+
RS-485-
Use this jumper to enable the
drive inverter via the terminals!
Control head
TF input
/Fault*
+24V
Reference potential binary signals
+24V (external)
/Brake
Relay contact
Relay NO
Relay NC
Reference potential binary signals
24V (external)

MOVIDRIVE
®
DeviceNet DFD11A
13
Project Planning and
Startup 3
3.2 Setting up the DeviceNet network using the DeviceNet Manager software
3.2.1 Installing the EDS file
01908AXX
Fig. 3: EDS file list
There is an EDS file MDX.eds and a bitmap file MDX.bmp for the DFD11A option card. These files
must be installed using the DeviceNet Manager software.
To do this, select
Utilities/Install EDS File from the menu. The program then prompts you for the
EDS file name and the bitmap file. The EDS file is then installed. More details on the installation of
the EDS file can be found in the Allen Bradley documentation for the DeviceNet Manager.
After installation, the device is available in the device list under the entry
SEW Geräteprofil/SEW-
Eurodrive GmbH/SEW-MOVIDRIVE-DFD11A
.
You can use the following Internet addresses for obtaining current EDS files and for further infor-
mation about DeviceNet.
• SEW-EURODRIVE: www.sew-eurodrive.de
• Allen Bradley: www.ab.com
• Rockwell: www.rockwell.com
• Open Device Net Vendor Association: www.odva.org
3.2.2 Connecting the device to an existing network
All EDS files are automatically read in after the DeviceNet Manager software is called up. The device
list contains all devices which have been defined by an EDS file.

14
MOVIDRIVE
®
DeviceNet DFD11A
3Project Planning and
Startup
3.3 Process data exchange
3.3.1 Polled I/O
The polled I/O messages correspond to the process data messages of the SEW fieldbus profile and
up to three process data words can be exchanged between the control and the inverter.
The process data length can be set with MX_SHELL (version 1.30 or later) and DBG (version .13 or
later) using the parameter
P877 DeviceNet PD Configuration . The inverter must be switched off
and on again after this parameter has been changed, in order to activate the set process data
length.
The process data length can also be set using the parameter data channel of DeviceNet. The pro-
cess data configuration takes effect immediately, if the process data length is set using the param-
eter data channel.
IMPORTANT:
The set process data length determines the process data lengths of both the polled I/O and the bit-
strobe I/O messages, i.e. the settings for the process data lengths of both the polled I/O and the
bit-strobe I/O always have to be identical in the control.

MOVIDRIVE
®
DeviceNet DFD11A
15
Project Planning and
Startup 3
Project planning for three process data words
The factory setting of the process data configuration is process data length = 3. This setting be
altered using the
DeviceNet PD Configuration parameter.
In MX_SHELL or DBG, the setting is displayed via the parameter
DeviceNet PD configuration = 3
PD
or 3PD + Param . As a result, three process data words (6 bytes) are processed in the inverter
and three process input data words are sent to the control.
No process data are processed or sent back, if the control transmits more than three process out-
put data words.
Three process data words are processed, and three process input data words are sent from the
inverter to the control, if the control transmits three process output data words.
02120AEN
Fig. 4: Representation of three process data words in the PLC memory area
The process output data are stored in the PLC output file and the process input data of the PLC are
stored in the input file. In the example above, the output data words O:3.10, O:3.11 and O:3.12 are
copied to process output data words 1, 2 and 3 and processed by the inverter. The inverter sends
back three process input data words which are copied into input data words I:3.10, I:3.11 and
I:3.12 of the PLC.
PD 1
PD 1
PD 1
PD 1
PD 2
PD 2
PD 2
O:3.10
O:3.11
O:3.12
I:3.10
I:3.11
I:3.12
PD 2
PD 3
PD 3
PD 3
PD 3
EQ
PLC
Address range
Output file
Input file

16
MOVIDRIVE
®
DeviceNet DFD11A
3Project Planning and
Startup
Project planning for two process data words
Process data length = 2 can be set using the
DeviceNet PD Configuration parameter. In this case,
the setting
2 PD or 2PD + Param must be selected in MX_SHELL or DBG. As a result, two process
data words (4 bytes) are processed in the inverter and two process input data words are sent to the
control.
No process data are processed or sent back, if the control transmits more than two process output
data words.
Two process data words are processed, and two process input data words are sent from the
inverter to the control, if the control transmits two process output data words.
02121AEN
Fig. 5: Representation of two process data words in the PLC memory area
The process output data are stored in the PLC output file and the process input data of the PLC are
stored in the input file. In the example above, the output data words O:3.10 and O:3.11 are copied
to process output data words 1 and 2 and processed by the inverter. The inverter sends back two
process input data words which are copied into input data words I:3.10 and I:3.11 of the PLC.
PD 1
PD 1
PD 1
PD 1
PD 2
PD 2
PD 2
O:3.10
O:3.11
I:3.10
I:3.11
PD 2
EQ
PLC
Address range
Output file
Input file

MOVIDRIVE
®
DeviceNet DFD11A
17
Project Planning and
Startup 3
Project planning for one process data word
Process data length = 1 can be set using the
DeviceNet PD Configuration parameter. In this case,
the setting
1 PD or 1PD + Param must be selected in MX_SHELL or DBG. As a result, one process
output data word (1 byte) is processed in the inverter and one process input data word is sent to
the control. The control is permitted to send only one process output data word. No process data
are processed or sent back if more than one process output data word is sent by the control.
02122AEN
Fig. 6: Representation of one process data word in the PLC memory area
The process output data are stored in the PLC output file and the process input data of the PLC are
stored in the input file. In the example above, output data word O:3.10 is copied to process output
data word 1 and processed by the inverter. The inverter sends back one process input data word
which is copied to input data word I:3.10 of the PLC.
Timeout response with polled I/O
The timeout response is triggered by the DeviceNet option card. The timeout interval must be set
by the master after the connection has been established. The DeviceNet specification refers to an
“expected packet rate” rather than a timeout interval. The expected packet rate is calculated on the
basis of the timeout interval using the following formula:
The expected packet rate can be set using the connection object class 5, instance 2, attribute 9. The
range of values runs from 0 ms to 65535 ms in 5 ms steps.
The expected packet rate for the polled I/O connection is converted into the timeout interval and
displayed in the device and the timeout interval in parameter
P819 .
This timeout interval is retained in the device whenever the polled I/O connection is dropped, and
the device switches to timeout status after the timeout interval has elapsed.
The timeout interval must not be altered in the inverter using MX_SHELL or the DBG, because it
can only be activated via the bus.
O:3.10
I:3.10
PD 1
PD 1
PD 1
PD 1
EQ
PLC
Address range
Output file
Input file
Timeout_Inverter tTimeout_Interval_PolledIO 4t Expected_Packet_Rate_PolledI
O
⋅
==

18
MOVIDRIVE
®
DeviceNet DFD11A
3Project Planning and
Startup
If a timeout occurs for the polled I/O messages, this connection type enters timeout status. Incom-
ing polled I/O messages are no longer accepted.
The timeout response triggers timeout reaction set in the inverter.
The timeout response can be reset with DeviceNet by using the reset service of the connection
object (class 0x05, instance 0x02, undetermined attribute), by dropping the connection, by using
the reset service of the identity object (class 0x01, instance 0x01, undetermined attribute) or with
the reset bit in the control word.
3.3.2 Bit-strobe I/O
Bit-strobe I/O messages are not contained in the SEW fieldbus profile. They represent a process
data exchange which is specific to DeviceNet.
The master sends out a broadcast message that is 8 bytes = 64 bits long. One bit in this message
is assigned to each participant in accordance with its station address. The value of this bit may be
0 or 1, triggering two different reactions in the recipient.
Table 9: Bit strobe signal messages
IMPORTANT:
The BIO LED can be consulted to distinguish between the timeout triggered by the bit-strobe mes-
sage and a real timeout in the connection. It remains continuously green if the timeout is triggered
by the bit-strobe message.
If the BIO LED flashes red, there is a timeout in the bit-strobe connection and no additional
bit-strobe messages are accepted.
Table 10 shows the data area of the bit-strobe request message which represents the allocation of
participants (= station address) to data bits.
For example, the participant with station address (MAC-ID) 16 only processes bit 0 in data byte 2.
Table 10: MAC-ID assignment in the bit-strobe I/O message request
Bit value Message BIO LED
0 Only send back the process input data Continuously green
1 Trigger fieldbus timeout response and send back process input data Continuously green
Byte offset 7 6 5 4 3 2 1 0
0 ID 7 ID 6 ID 5 ID 4 ID 3 ID 2 ID 1 ID 0
1 ID 15 ID 14 ID 13 ID 12 ID 11 ID 10 ID 9 ID 8
2 ID 23 ID 22 ID 21 ID 20 ID 19 ID 18 ID 17 ID 16
3 ID 31 ID 30 ID 29 ID 28 ID 27 ID 26 ID 25 ID 24
4 ID 39 ID 38 ID 37 ID 36 ID 35 ID 34 ID 33 ID 32
5 ID 47 ID 46 ID 45 ID 44 ID 43 ID 42 ID 41 ID 40
6 ID 55 ID 54 ID 53 ID 52 ID 51 ID 50 ID 49 ID 48
7 ID 63 ID 62 ID 61 ID 60 ID 59 ID 58 ID 57 ID 56

MOVIDRIVE
®
DeviceNet DFD11A
19
Project Planning and
Startup 3
Each participant which has received this bit-strobe I/O message responds with its current process
input data. The length of the process input data corresponds to the process data length for the
polled I/O connection. It can also be set using the
DeviceNet PD Configuration parameter.
02123AEN
Fig. 7: Bit-strobe I/O messages
In the example above, the bit-strobe I/O message is stored in memory words O:3.10 to O:3.13 and
Bit 16 is assigned to the device with station address 16. This bit corresponds to bit 0 of output data
word O:3.11 in the PLC. Since this bit was set to the value 1, a fieldbus timeout is triggered in the
inverter with station address 16. However, the BIO LED remains continuously green to indicate that
the bit-strobe connection is not in timeout status.
The inverter sends three process input data words to the PLC; these are stored in input data words
I:3.10 to I:3.12 in the input file.
IMPORTANT:
The set process data length determines the process data length of both the bit-strobe I/O and the
polled I/O messages, i.e. the settings for the process data length of both the polled I/O and the bit-
strobe I/O always have to be identical in the control.
Timeout response with bit-strobe I/O
The timeout response is triggered by the DeviceNet option card. The timeout interval must be set
by the master after the connection has been established. The DeviceNet specification refers to an
“expected packet rate” rather than a timeout interval. The expected packet rate is calculated on the
basis of the timeout interval using the following formula:
It can be set using connection object class 5, instance 3, attribute 9. The range of values runs from
0 ms to 65535 ms in 5 ms steps.
If a timeout occurs for the bit-strobe I/O messages, this connection type enters timeout status.
Incoming bit-strobe I/O messages are no longer accepted.
The timeout response is not transmitted to the inverter.
Input file PD 1
PD 1
PD 2
PD 2
O:3.10
O:3.11
O:3.12
I:3.10
I:3.11
I:3.12
Bit 16
PD 3
PD 3
O:3.13 1
1
EQ
PLC
Address range
Output file Station
Address
(MAC-ID) = 16
t
Timeout_Interval_BitStrobeIO 4t Expected_Packet_Rate_BitStrobeIO
⋅
=

20
MOVIDRIVE
®
DeviceNet DFD11A
3Project Planning and
Startup
The timeout response can be reset with DeviceNet using the reset service of the connection object
(class 0x05, instance 0x03, undetermined attribute), by dropping the connection or by using the
reset service of the identity object (class 0x01, instance 0x01, undetermined attribute).
3.4 Parameter data exchange
3.4.1 The SEW parameter data channel
The SEW parameter data channel represents a connection via which parameters in the inverter can
be changed or read. This channel is represented by explicit messages on the DFD11A DeviceNet
option card.
Access to the SEW parameter data channel is by means of the register object (class 7) and the
parameter object (class 15).
Register object class (class 7)
The SEW parameter data channel can be addressed using the services
Get_Attribute_Single and
Set_Attribute_Single . The following possibilities for addressing the parameter data channel derive
from the way the register object is specified by DeviceNet so INPUT objects can only be read and
OUTPUT objects can be read and written.
Instance INPUT/OUTPUT Resulting MOVILINK service with
Get_Attribut_Single Set_Attribut_Single
1 INPUT READ Invalid
2 OUTPUT READ WRITE
3 OUTPUT READ WRITE VOLATILE
4 INPUT READ MINIMUM Invalid
5 INPUT READ MAXIMUM Invalid
6 INPUT READ DEFAULT Invalid
7 INPUT READ SCALING Invalid
8 INPUT READ ATTRIBUTE Invalid