Sie sind auf Seite 1von 60

Gearmotors \ Industrial Gear Units \ Drive Electronics \ Drive Automation \ Services

MOVIDRIVE® MDX61B FA361530

DFD11B Fieldbus Interface


DeviceNet

Edition 11/2004
11284412 / EN Manual
SEW-EURODRIVE – Driving the world
1 Important Notes...................................................................................................... 4

2 Introduction ............................................................................................................ 5

3 Assembly / Installation Instructions..................................................................... 7


3.1 Installing the DFD11B option card ................................................................. 7
3.2 Connection and terminal assignment............................................................. 9
3.3 Setting the DIP switches .............................................................................. 11
3.4 Display of operating status DFD11B option card ......................................... 12

4 Project Planning and Startup .............................................................................. 14


I
4.1 Startup of the drive inverter.......................................................................... 14
0 4.2 Building the DeviceNet network with the RSNetWorx software ................... 17
4.3 Process data exchange ............................................................................... 18
4.4 Parameter data exchange............................................................................ 22
4.5 Return codes for parameter setting.............................................................. 28

5 Sample Application with PLC Type SLC500 ...................................................... 29


5.1 Exchange of polled I/O (process data)......................................................... 31
5.2 Exchange of bit-strobe I/O ........................................................................... 34
5.3 Exchanging explicit messages (parameter data) ......................................... 35

kVA n 6 Technical Data ...................................................................................................... 40


f
i 6.1 DFD11B option ............................................................................................ 40
P Hz

7 Appendix ............................................................................................................... 41
7.1 General error codes (error messages)......................................................... 41
7.2 Statement of Conformance .......................................................................... 42
7.3 Definitions of terminology............................................................................. 51

8 Index ...................................................................................................................... 52

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 3


Important Notes
1

1 Important Notes
Handbuch

• This manual does not replace the detailed operating instructions!


• Only specialists are allowed to perform installation and startup observing
relevant accident prevention regulations and the MOVIDRIVE® MDX60B/61B
operating instructions!

Documentation • Read through this manual carefully before you start installation and startup of
MOVIDRIVE® drive inverters with the DeviceNet DFD11B option card.
• This manual assumes that the user has access to and is familiar with the
MOVIDRIVE® documentation, in particular the MOVIDRIVE® MDX60B/61B system
manual.
• In this manual, cross references are marked with "→". For example, (→ Sec. X.X)
means: Further information can be found in section X.X of this manual.
• A requirement of fault-free operation and fulfillment of any rights to claim under
guarantee is that you observe the information in the documentation.

Bus systems General safety notes on bus systems:


This communication system allows you to adjust the MOVIDRIVE® drive inverter to your
specific application very accurately. As with all bus systems, there is a danger of invisi-
ble, external (as far as the inverter is concerned) modifications to the parameters which
give rise to changes in the inverter behavior. This may result in unexpected (not uncon-
trolled) system behavior.

Safety and Always observe the safety and warning instructions contained in this publication!
warning notes

Electrical hazard
Possible consequences: Severe or fatal injuries.

Hazard
Possible consequences: Severe or fatal injuries.

Hazardous situation
Possible consequences: Slight or minor injuries.

Harmful situation
Possible consequences: Damage to the unit and the environ-
ment.

Tips and useful information.

4 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Introduction
2

2 Introduction
Contents of this This user manual describes how to install the DeviceNet DFD11B option card in the
manual MOVIDRIVE® MDX61B drive inverter and how to start up MOVIDRIVE® with the
DeviceNet fieldbus system.
Besides explaining all settings on the fieldbus option card, this document also covers
the various DeviceNet connection variants in the form of brief startup examples.

Additional For a simple and effective connection of MOVIDRIVE® to the DeviceNet fieldbus
documentation system, you should request the following publications from SEW-EURODRIVE about
the fieldbus technology in addition to this manual:
• MOVIDRIVE® Fieldbus Unit Profile manual
• MOVIDRIVE® MDX60/61B 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 control concepts and applica-
tion options in the form of brief examples.
The parameter list is a list of all drive inverter parameters that can be read and written
via various communication interfaces such as RS-485, SBus and even the fieldbus
interface.

MOVIDRIVE® and The MOVIDRIVE® MDX61B drive inverter together with the DFD11B option and its high-
DeviceNet performance universal fieldbus interface enable the connection to higher-level automa-
tion systems via the open and standardized DeviceNet fieldbus system.

Unit profile The performance of the inverter, referred to as the unit profile, that forms the basis for
the DeviceNet operation, is fieldbus-independent and, therefore, uniform. This allows
the user to develop fieldbus-independent drive applications. This makes it much easier
to change to other bus systems, such as PROFIBUS (DFP 21B option) or INTERBUS
(DFI11B option).

Drive parameters MOVIDRIVE® offers you direct access to all drive parameters and functions via the
DeviceNet interface. The drive inverter is controlled via the fast, cyclical process data.
Via this process data channel, you have the opportunity of entering 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, standard stop, rapid
stop, etc.
At the same time you can also use this channel to read back actual values from the drive
inverter, such as actual speed, current, unit status, error number or reference signals.

Polled I/O and Bit The parameters of the inverter are set exclusively using Explicit Messages, whereas the
Strobe I/O process data exchange is replicated on the DeviceNet services Polled I/O and
Bit-Strobe I/O. This parameter data exchange enables you to implement applications in
which all the important drive parameters are stored in the master programmable control-
ler, so that there is no need to make manual parameter settings on the drive inverter it-
self.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 5


Introduction
2

Startup Every DFD11B DeviceNet option card is designed so that the fieldbus-specific MAC-ID
and baud rate settings are made using hardware switches on the option card. This man-
ual setting means the drive inverter can be integrated into the DeviceNet system and
switched on quickly.
The parameter setting process can be performed in a completely automated process by
the DeviceNet master (parameter download). This forward-looking variant shortens the
system startup time and simplifies the documentation of your application program
because all the important drive parameters can now be stored directly in your control
program.

Communication Interface

1 2 3 1 2 3
4 5 6 4 5 6
7 8 9 7 8 9
+/- 0 . +/- 0 .

MOVIDRIVE® MDX61B MOVIDRIVE® MDX61B

1 2 3

MOVIDRIVE®
4 5 6
7 8 9
+/- 0 .

MOVIDRIVE® MDX61B

SPS Node_4
[4]

55215AXX
Figure 1: DeviceNet with MOVIDRIVE® MDX61B and PLC

Monitoring The use of a fieldbus system requires additional drive system monitoring such as time
functions monitoring of the fieldbus (fieldbus timeout) or even special emergency stop concepts.
The MOVIDRIVE® MDX61B monitoring functions can be customized to your applica-
tion. You can determine, for instance, which of the drive inverter error responses 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 (for example, conveyor belt). As the
functions of the control terminals are still active in fieldbus operation, you can still imple-
ment fieldbus-independent emergency stop concepts via the terminals of the drive
inverter.

Diagnostics The MOVIDRIVE® MDX61B drive inverter offers numerous diagnostic options for start-
up and service.
For example, you can use the integrated fieldbus monitor to check both the setpoints
sent by the master control and the actual values. The MOVITOOLS® software package
offers a convenient diagnostic option that allows for a detailed display of fieldbus and
device state information in addition to the settings of all drive parameters (including field-
bus parameters).

6 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Assembly / Installation Instructions
Installing the DFD11B option card
3

3 Assembly / Installation Instructions


3.1 Installing the DFD11B option card
• MOVIDRIVE® MDX61B must have firmware status 824 854 0.11 or above. You can
display the firmware status using parameter P076.
• Only SEW-EURODRIVE engineers can install or remove option cards for
MOVIDRIVE® MDX61B size 0.
• Option cards can only be installed and removed for MOVIDRIVE® MDX61B
sizes 1 to 6.

The DFD11B option card must be plugged into the fieldbus slot [1].

[1]

54703AXX

Before you begin Observe the following notes before installing or removing an option card:
• Disconnect the inverter from power. Switch off the 24 VDC and the supply voltage.
• Take appropriate measures to protect the option card from electrostatic charge (use
discharge strap, conductive shoes, etc.) before touching it.
• Before installing the option card, remove the keypad and the front cover.
• After installing the option card, replace the front cover and the keypad.
• Keep the option card in its original packaging until immediately before you are ready
to install it.
• Hold the option card by its edges only. Do not touch any components.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 7


Assembly / Installation Instructions
3 Installing the DFD11B option card

Basic procedure for installation/removing an option card

2.
1.

3.

4.

53001AXX
Figure 2: Installing an option card in MOVIDRIVE® MDX61B sizes 1 to 6 (schematic diagram)
1. Remove the retaining screws holding the card retaining bracket. Pull the card
retaining bracket out evenly from the slot (do not twist!).
2. Remove the retaining screws of the black cover plate on the card retaining bracket.
Remove the black cover plate.
3. Position the option card onto the retaining bracket so that the retaining screws fit into
the corresponding bores on the card retaining bracket.
4. Insert the retaining bracket with installed option card into the slot, pressing slightly so
it is seated properly. Secure the card retaining bracket with the retaining screws.
5. To remove the option card, follow the instructions in reverse order.

8 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Assembly / Installation Instructions
Connection and terminal assignment
3

3.2 Connection and terminal assignment


Part number DeviceNet fieldbus interface type DFD11B: 824 972 5

The "DeviceNet interface type DFD11B" option is only possible in conjunction with
MOVIDRIVE® MDX61B, not with MDX60B.
The DFD11B option must be plugged into the fieldbus slot.

Front view of DIP switch


Description Function
DFD11B Terminal

DFD 11B
MOD/
Mod/Net = Module/network status The two-color LEDs display the current status of the
Net PIO - Polled I/O fieldbus interface and the DeviceNet system:
PIO
BIO - Bit-Strobe I/O
BUSOFF
BIO
BUS-
OFF

0 1
NA(5)
NA(4) Six DIP switches for setting of the NA(5) ... NA(0) Setting the MAC-ID (Media Access Control Identi-
NA(3) S1
NA(2) MAC-ID fier)
NA(1)
NA(0)
Five DIP switches for setting the PD(4) ... PD(0) Setting the process data length (1 ... 10 words)
DR(1) process data length
DR(0)
PD(4)
PD(3) Two DIP switches for setting the baud DR(1) ... DR(0) Setting the baud rate:
PD(2) S2
PD(1) rate 00 = 125 kBaud
PD(0) 01 = 250 kBaud
F3
F2 10 = 500 kBaud
F1 F1 ... F3: No Function 11 = Invalid

1
2 X30: DeviceNet connection X30:1 V–
X30:2 CAN_L
3
X30:3 DRAIN
4 X30:4 CAN_H
5 X30:5 V+

X30

54193AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 9


Assembly / Installation Instructions
3 Connection and terminal assignment

Pin assignment The assignment of connecting terminals is described in the DeviceNet specification
(Volume I, Appendix A).

DFD11B
DFD11B

1
2
3
4
5
X30
54075AXX

The DFD11B 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 voltage via the bus cable. The cable to be used is also described in
the DeviceNet specification (Volume I, Appendix B). The connection must be made
according to the color code specified in the following table.
Pin no. Signal Meaning Color coding
1 V– 0V24 BK
2 CAN_L CAN_L BU
3 DRAIN DRAIN Bright
4 CAN_H CAN_H WH
5 V+ 24 V RD

Shielding and The DeviceNet interface supports RS-485 communications protocol and requires cable
routing of bus type A specified for DeviceNet in accordance with EN 50170 as shielded, twisted-pair
cables cable for the physical connection.
Correct shielding of the bus cable attenuates electrical interference that may occur in
industrial environments. The following measures ensure the best possible shielding:
• Tighten the mounting screws on the connectors, modules and equipotential bonding
conductors by hand.
• Attach the shielding of the bus line over a large surface on both sides.
• Do not route signal and bus cables parallel to power cables (motor leads). They must
be routed in separate cable ducts.
• Use metallic, grounded cable racks in industrial environments.
• Route the signal cable and the corresponding equipotential bonding in close proxim-
ity using the shortest way possible.
• Avoid using plug connectors to extend bus cables.
• Route the bus cables closely along existing grounding surfaces.
In case of fluctuations in the earth potential, a compensating current may flow via the
bilaterally connected shield that is also connected to the protective earth (PE). Make
sure you supply adequate equipotential bonding according to relevant VDE regulations
in such a case.
Bus termination In order to avoid disruptions in the bus system due to reflections, each DeviceNet seg-
ment must be terminated with 120 Ω bus terminating resistors at the first and last phys-
ical station. Connect the bus terminating resistor between connections 2 and 4 of the
bus plug.

10 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Assembly / Installation Instructions
Setting the DIP switches
3

3.3 Setting the DIP switches

Before changing a DIP switch setting, disconnect the drive inverter from power (supply
voltage and 24 V backup operation). The DIP switch settings are adopted during initial-
ization of the driver inverter only.

Setting the The MAC-ID (Media Access Control Identifier) is set on the DFD11B option card with
MAC-ID DIP switches S1-NA0...S1-NA5. The MAC-ID represents the node address of the
DFD11B. MOVIDRIVE® supports the address range 0 ... 63.

Setting the baud The baud rate is set with DIP switches S2-DR0 and S2-DR1.
rate
DIP switch S2
Baud rate
DR1 DR0
0 0 125 kBaud
0 1 250 kBaud
1 0 500 kBaud
1 1 Obsolete

Setting the pro- Up to ten DeviceNet data words can be exchanged between the DeviceNet interface
cess data length module and the DFD11B; these data words can be distributed to the process data chan-
nel with DIP switches S2-PD0 to S2-PD4.

0 1
NA5
NA4
[1]
NA3 S1 [1] Setting the MAC-ID
NA2
NA1 [2] Setting the baud rate
NA0

DR1
[3] Setting the process data length
[2]
DR0
PD4
[4] No Function
PD3 S2
[3] PD2 The figure depicts the following settings:
PD1
PD0 MAC-ID: 4
F3
[4] F2 Baud rate: 125 kBaud
F1
Process data length: 8 PD

54078AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 11


Assembly / Installation Instructions
3 Display of operating status DFD11B option card

3.4 Display of operating status DFD11B option card


The DFD11B option card is equipped with four two-color LEDs for diagnostics of the
DeviceNet system; these indicate the current status of the DFD11B and the DeviceNet
system.
LED abbreviation Complete LED designation
Mod/Net Module/Network Status
PIO Polled I/O
BIO Bit-Strobe IO
BUS-OFF BusOff

LED Mod/Net The function of the LED Mod/Net described in the following table is contained in the
DeviceNet specification.
State Status Meaning
Off Not switched on / OffLine • Unit is offline
• Unit is performing DUP-MAC check
• Unit is switched off
Flashes Online and in operational • The unit is online and no connection has been
green mode established
(1 s cycle) • DUP-MAC check was performed successfully
• A connection has not yet been established with a
master
• Missing, incorrect or incomplete configuration
Green light Online, operational mode • Online
and connected • Connection has been established with a master
• Connection is active (established state)
Flashes red Minor fault or connection • A correctable error has occurred
(1 s cycle) timeout • Polled I/O or/and bit-strobe I/O connections are in
timeout state
• DUP-MAC check has detected an fault
Red light Critical fault or critical link • A correctable error has occurred
failure • BusOff
• DUP-MAC check has detected an fault

PIO LED The PIO LED checks the polled I/O connection.
State Status Meaning
Flashes green DUP-MAC check Unit is performing DUP-MAC check
(125 ms
cycle)
Off Not switched on / offline but • Unit is offline
not DUP-MAC check • Unit is switched off
Flashes green Online and in operational • Unit is online
(1 s cycle) mode • DUP-MAC check was performed successfully
• A PIO connection is being established with a master
(configuring state)
• Missing, incorrect or incomplete configuration
Green light Online, operational mode • Online
and connected • A PIO connection has been established (established
state)
Flashes red Minor fault or connection • A correctable error has occurred
(1 s cycle) timeout • Polled I/O connection is in timeout state
Red light Critical fault or critical link • A non-correctable fault has occurred
failure • BusOff
• DUP-MAC check has detected an fault

12 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Assembly / Installation Instructions
Display of operating status DFD11B option card
3

LED BIO The BIO LED checks the bit-strobe I/O connection.
State Status Meaning
Flashes green DUP-MAC check Unit is performing DUP-MAC check
(125 ms
cycle)
Off Not switched on / offline but • Unit is offline
not DUP-MAC check • Unit is switched off
Flashes green Online and in operational • Unit is online
(1 s cycle) mode • DUP-MAC check was performed successfully
• A BIO connection is being established with a master
(configuring status)
• Missing, incorrect or incomplete configuration
Green light Online, operational mode • Online
and connected • A BIO connection has been established (established
state)
Flashes red Minor fault or connection • A correctable error has occurred
(1 s cycle) timeout • Bit-strobe I/O connection is in timeout state
Red light Critical fault or critical link • A non-correctable fault has occurred
failure • BusOff
• DUP-MAC check has detected an fault

BUS-OFF LED The BUS-OFF LED displays the physical status of the bus node.
State Status Meaning
Off NO ERROR The number of bus errors is in the normal range (error
active status).
Flashes red The unit is performing a DUP-MAC check and cannot
(125 ms send any messages because no other stations are
cycle) connected to the bus (error passive state).
BUS WARNING
Flashes red The number of physical bus errors is too high. No more
(1 s cycle) error telegrams are actively written to the bus (error pas-
sive state).
Red light BUS ERROR • BusOff status
• The number of physical bus errors has increased
despite a switch to the error-passive state. Access to
the bus is deactivated.
Yellow light POWER OFF External voltage supply has been turned off or is not con-
nected.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 13


I Project Planning and Startup
4 Startup of the drive inverter
0

4 Project Planning and Startup


This section describes how to configure and start up the MOVIDRIVE® MDX61B drive
inverter with the DFD11B option.

4.1 Startup of the drive inverter


You can immediately configure the MOVIDRIVE® drive inverter after installation of the
DFD11B option and setting of the baud rate and MAC-ID via the fieldbus system without
additional manual settings. In this way, you can download all drive parameters from the
master programmable controller directly via DeviceNet after the power is switched on.
However, to control the drive inverter via the DeviceNet system, you must first switch
the drive inverter to the control signal source and setpoint source = FIELDBUS. The
FIELDBUS setting means the inverter parameters are set for control and setpoint trans-
fer from the fieldbus. The drive inverter then responds to the process output data sent
by the master programmable controller.
Activation of the control signal source/setpoint source FIELDBUS is signaled to the
higher-level controller using the "Fieldbus mode active" bit in the status word. For safety
reasons, the drive inverter must also be enabled at the terminals for control via the field-
bus system. Consequently, the terminals must be wired or programmed in such a way
that the inverter is enabled via the input terminals.
The simplest way of enabling the drive inverter at the terminals is to connect the DIØØ
(function /CONTROLLER INHIBIT) input terminal to a +24 V signal and to program input
terminals DIØ1 ... DIØ5 to NO FUNCTION. The following illustration shows by way of
example how to startup the MOVIDRIVE® drive inverter with fieldbus interface.

14 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Startup of the drive inverter
4
0

Procedure for 1. Enable the power output stage at the terminals.


startup of the Connect the input terminal DIØØ / X13.1 (function /CONTROLLER INHIBIT) to a
MOVIDRIVE® +24 V signal (for example, using a device jumper).
MDX61B
DI00 = Controller inhibit
DI01 = no function
X13: DI02 = no function
1 DI00
DI03 = no function
2 DI01
3 DI02 DI04 = no function
4 DI03 DI05 = no function
5
[1]
DI04 DCOM = Reference X13:DI00 ...
6 DI05 DI05
7 DCOM VO24 = + 24 V
8 VO24
DGND = Reference pot. for binary
9 DGND signals
10 ST11
ST11 = RS-485 +
11 ST12
ST12 = RS-485 -
TF1 = TF input
X10:
DGND = Reference pot. for binary
1 TF1 signals
2 DGND
DB00 = Brake
3 DB00
- 4 DO01-C DO01-C = Relay contact
- 5 DO01-NO DO01-NO = Normally open contact
- 6 DO01-NC relay
7 DO02 DO01-NC = Normally closed contact
8 VO24 relay
9 VI24 + DO02 = /Malfunction
24 V ext.
10 DGND - VO24 = + 24 V
VI24 = + 24 V (external supply)
DGND = Reference pot. for binary
signals
Enabling the power output stage via unit jumper [1]
54095AXX

2. Turn on the external 24 V voltage supply (not mains voltage supply!).


You can now configure the drive inverter.
3. Setpoint source = FIELDBUS / control signal source = FIELDBUS.
Set the setpoint source and control signal source parameters to FIELDBUS to control
the drive inverter via a fieldbus.
P100 Setpoint source = FIELDBUS
P101 Control signal source = FIELDBUS

4. Input terminals DIØ1 ... DIØ5 = NO FUNCTION.


Set the function of the input terminals to NO FUNCTION.
P600 Terminal programming DIØ1 = NO FUNCTION
P601 Terminal programming DIØ2 = NO FUNCTION
P602 Terminal programming DIØ3 = NO FUNCTION
P603 Terminal programming DIØ4 = NO FUNCTION
P604 Terminal programming DIØ5 = NO FUNCTION

For more information on startup and control of the MOVIDRIVE® drive inverter, refer to
the "MOVIDRIVE® Fieldbus Unit Profile" manual.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 15


I Project Planning and Startup
4 Startup of the drive inverter
0

Power-UP test A power-up test of all LEDs takes place once the drive inverter has been switched on.
The LEDs are switched on in the following sequence as part of the test:
Time in [ms] LED Mod/Net PIO LED LED BIO BUS-OFF LED
0 Green Off Off Off
250 red Off Off Off
500 Off Green Off Off
750 Off red Off Off
1000 Off Off Green Off
1250 Off Off red Off
1500 Off Off Off Green
1750 Off Off Off red
2000 Off Off Off Off

If there is no 24 V supply voltage at the fieldbus (X30:1, X30:5), the LED BUS-OFF will
be yellow (→ Operating displays of DFD11B option).

16 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Building the DeviceNet network with the RSNetWorx software
4
0

4.2 Building the DeviceNet network with the RSNetWorx software


Installing the EDS Install the following files with the RSNetWorx software to build the DeviceNet network
file with the DFD11B option:
• EDS file: DFD11B.eds
• Icon file: DFD11B.ico

54173AXX
Figure 3: EDS file list
Proceed as follows:
• Select the menu item <Tools/EDS-Wizard> in RSNetWorx. You will be prompted to
enter the names of the EDS and Icon file.
• The files will be installed. More details on the installation of the EDS file can be found
in the Allen Bradley documentation for RSNetWorx.
• After installation, the device is available in the device list under the entry SEW Device
Profile/SEW-EURODRIVE DFD11B.

Additional information on current EDS files as well as information on DeviceNet are


available at the following Internet addresses:
• SEW-EURODRIVE: www.sew-eurodrive.com
• Allen Bradley: www.ab.com
• Open Device Net Vendor Association: www.odva.org

Connecting the All EDS files are automatically read in after the RSNetWorx software is started. The
device to an device list contains all devices which have been defined by an EDS file.
existing network

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 17


I Project Planning and Startup
4 Process data exchange
0

4.3 Process data exchange


Polled I/O The polled I/O messages correspond to the process data telegrams of the SEW fieldbus
profile. Up to ten process data words can be exchanged between the control and the
inverter in this case. The process data length is set via DIP switches S2-PD0 ... S2-PD4.

The set process data length influences the process data lengths of both the polled I/O
and the bit-strobe I/O messages.
The process data length of the bit-strobe I/O messages can include up to four process
data words. If the value for the process data length set via DIP switches is less than four,
it will be accepted. If the value set via DIP switches is greater than four, the process data
length will be automatically limited to four.

Configuration for The process data length for the process data configuration is set to 3 at the factory. The
1 ... 10 process value can be set via DIP switches S2-PD0 ... S2-PD4.
data words This setting is displayed via the parameters DeviceNet PD configuration = 3PD or 3PD
+ Param in MOVITOOLS® or via the DBG60B keypad. This means 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 ten pro-
cess output 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.

PLC
address range

Output file

O:3.10 PD 1

O:3.11 PD 2
MOVIDRIVE® MDX61B
O:3.12 PD 3

PD 1 PD 2 PD 3 PD 10
...

1 2 3

Input file 4
7
+/-
5
8
0
6
9
.

PD 1 PD 2 PD 3 PD 10
...
PD 1
I:3.10 PD 2
PD 3
I:3.11

I:3.12

54191AEN
Figure 4: Three process data words in the PLC memory

18 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Process data exchange
4
0

The process output data are stored in the output file of the PLC 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 pro-
cessed by the inverter. The inverter sends back three process input data words that are
copied into input data words I:3.10, I:3.11 and I:3.12 of the PLC.

If you select a different process data length, you will have the expand the memory to be
managed in the PLC as well. If the process data length is set to 10, you will have to
configure 10 process output data words and 10 process input data words.

Timeout The timeout is triggered by the DFD11B option. The timeout time must be set by the
response with master after the connection has been established. The DeviceNet specification refers to
polled I/O an "expected packet rate" rather than a timeout time in this case. The expected packet
rate is calculated on the basis of the timeout interval using the following formula:
tTimeout_inverter = tTimeout interval_PolledIO = 4 x tExpected_Packet_Rate_PolledIO

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 MOVITOOLS® or the
DBG60B keypad, because it can only be activated via the bus.
If a timeout occurs for the polled I/O messages, this connection type enters timeout
status. Incoming polled I/O messages are no longer accepted.
The timeout causes the timeout reaction set in the inverter to be carried out.
The timeout can be reset with DeviceNet by means of the reset service of the connection
object (class 0x05, instance 0x02, undetermined attribute), by disconnecting the
connection, by means of the reset service of the identity object (class 0x01, instance
0x01, undetermined attribute) or with the reset bit in the control word.

Bit-strobe I/O Bit-strobe I/O messages are not contained in the SEW fieldbus profile. The messages
represent a DeviceNet-specific process data exchange. The master sends a broadcast
message that is 8 bytes (= 64 bits) long. One bit in this message is assigned to each
station in accordance with its station address. The value of this bit may be 0 or 1, and
thereby trigger two different reactions in the recipient.
Bit Meaning LED BIO
value
0 Send back the process input data only Green light
1 Trigger fieldbus timeout reaction and send back process input data Green light

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 19


I Project Planning and Startup
4 Process data exchange
0

Important:
The BIO LED on the front of the DFD11B option can be used for distinguishing between
the timeout triggered by the bit-strobe telegram and a real timeout in the connection. It
remains continuously green if the timeout is triggered by the bit-strobe telegram.
If the BIO LED flashes red, this means there is a timeout in the bit-strobe connection and
no more bit-strobe telegrams are accepted. Each station that has received this bit-strobe
I/O message responds with its current process input data. The length of the process in-
put data corresponds to the process data length for the polled I/O connection. The pro-
cess input data length can be up to four process data.
The following table shows the data area of the bit-strobe request telegram which repre-
sents the allocation of stations (= station address) to data bits.
Example: For example, the station with station address (MAC-ID) 16 only processes bit
0 in data byte 2.
Byte off- 7 6 5 4 3 2 1 0
set
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

PLC
address range
Output file
Station
O:3.10 address
O:3.11 1 Bit 16 (MAC-ID) = 16
O:3.12
O:3.13
1

Input file
PD 1 PD 2 PD 3 1 2 3
4 5 6
7 8 9

PD 1 PD 2 +/- 0 .

I:3.10
PD 3
I:3.11
I:3.12

54192AEN
Figure 5: 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. The inverter sends three process input data words to the PLC; these are stored
in the input file in input data words I:3.10 to I:3.12.

Important:
The process data length set via DIP switches influences the process data lengths of both
the polled I/O and the bit-strobe I/O messages. The process data length of the bit-strobe
I/O messages can include up to four process data words.

20 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Process data exchange
4
0

Timeout The timeout is triggered by the DFD11B option. The timeout time must be set by the
response with bit- master after the connection has been established. The DeviceNet specification refers to
strobe I/O an "expected packet rate" rather than a timeout time in this case. The expected packet
rate is calculated on the basis of the timeout interval using the following formula:
tTimeout_BitStrobeIO = 4 x tExpected_Packet_Rate_BitStrobeIO

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 is not
passed on to the inverter.
The timeout reset takes place as follows:
• via DeviceNet with the reset service of the connection object (class 0x05, instance
0x03, undetermined attribute)
• by interrupting the connection
• via reset service of the identity object (class 0x01, instance 0x01, undetermined
attribute)

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 21


I Project Planning and Startup
4 Parameter data exchange
0

4.4 Parameter data exchange


The SEW parame- The SEW parameter data channel represents a connection you can use to change or
ter data channel read parameters in the inverter. It is represented on the DFD11B option in form of
Explicit Messages.
Access to the SEW parameter data channel is by means of the register object (class 7)
and the parameter object (class 15).

Register object You address the SEW parameter data channel with the Get_Attribute_Single and
class (class 7) Set_Attribute_Single services. The following possibilities for addressing the parameter
data channel derive from the way the register object is specified by DeviceNet so that
INPUT objects can only be read and OUTPUT objects can be read and written.
Resulting MOVILINK® service with
Instance INPUT / OUTPUT
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
9 INPUT READ EEPROM Invalid

22 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Parameter data exchange
4
0

Input
Get_Attribut_Single (Instance 1) READ

Get_Attribut_Single
Output
(Instance 2)
Set_Attribut_Single WRITE

Get_Attribut_Single
Output
(Instance 3)
Set_Attribut_Single WRITE VOLATILE

Input
Get_Attribut_Single READ MINIMUM
(Instance 4)

DPRAM

Input
Get_Attribut_Single READ MAXIMUM
(Instance 5)

Input
Get_Attribut_Single (Instance 6) READ DEFAULT

Get_Attribut_Single
Input READ SCALING
(Instance 7)

Get_Attribut_Single
Input
READ ATTRIBUTE
(Instance 8)

Get_Attribut_Single
Input
READ EEPROM
(Instance 9)

DeviceNet SEW fieldbus profile

54185AEN
Figure 6: Description of the parameter channel

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 23


I Project Planning and Startup
4 Parameter data exchange
0

The following table shows the attributes (column "Attribute") of the eight instances (col-
umn "Instance") of the register object.
Class Instance Attribute Get Set Type Type/Value Meaning
0x07 0x01 1 X BOOL 0/1 Bad Flag
(Read)
2 X BOOL 0 (Input) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x02 1 X BOOL 0/1 Bad Flag
(Read /Write)
2 X BOOL 1 (Output) Direction
3 X UINT 48 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x03 1 X BOOL 0/1 Bad Flag
(Read/Write-Volatile)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x04 1 X BOOL 0/1 Bad Flag
(Read Minimum)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x05 1 X BOOL 0/1 Bad Flag
(Read Maximum)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x06 1 X BOOL 0/1 Bad Flag
(Read Default)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x07 1 X BOOL 0/1 Bad Flag
(Read Scaling)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x08 1 X BOOL 0/1 Bad Flag
(Read Attribute)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data
0x09 1 X BOOL 0/1 Bad Flag
(Read EEPROM)
2 X BOOL 1 (Output) Direction
3 X UINT 16 bit Size
4 X X ARRAY 2 byte index Data
BITS 4 byte data

24 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Parameter data exchange
4
0

Explanation of • Attribute 1 Bad flag signals whether an error occurred in the previous service.
attributes • Attribute 2 represents the direction of the instance
• Attribute 3 indicates the data length in bits
• Attribute 4 represents the parameter data. They are made up of the index (2 bytes)
and the data (4 bytes).

You transmit the values with the Get_Attribute_Single and Set_Attribute_Single servic-
es.
Service Coding Meaning
Get_Attribut_Single 0x0E Read attribute
Set_Attribut_Single 0x10 Write attribute

Example Parameter Setpoint description PO1 (index 8304 = 2070hex) is to receive the value
CONTROL WORD1 (9). The following table shows the file format for the parameter re-
quest telegram.
Byte offset
0 1 2 3 4 5 6 7 8 9 10
Function MAC-ID Service Class Instance Attribut Index Data
es
Signifi- Low High LSB MSB
cance
Exam- 01hex 10hex 07hex 02hex 04hex 70hex 20hex 09hex 00hex 00hex 00hex
ple

The following table shows the file format for the parameter response telegram.
Byte offset
0 1 2 3 4 5 6 7
Function MAC-ID Service Index Data
Significance Low High LSB MSB
Example 01hex 90hex 70hex 20hex 09hex 00hex 00hex 00hex

PLC
address range
Output data

Header Header
(Service, Class...)
Index = 2070h Index
Data Low-word Data Low-Word
=0009h
Data High-word Data High-Word
=0000h
Header Index Data

Input data
Header Index Data 1 2 3
4 5 6

Header Header 7
+/-
8
0
9
.

(Service, Class...)
Index
Index = 2070h
Data Low-word Data Low-Word
=0009h
Data High-word Data High-Word
=0000h

54183AEN
Figure 7: Parameter data exchange

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 25


I Project Planning and Startup
4 Parameter data exchange
0

Parameter object The fieldbus parameters of the inverter can be addressed directly via the instance with
class (class 15) the parameter object. The data format for these instances deviates from the SEW field-
bus profile to meet the DeviceNet specification. It is possible to address all parameters
of the inverter via the parameter object. Instances 1 to 9 have been reserved for this
purpose.

General SEW You can use the RSNetWorx software to set the inverter parameters via the parameter
parameter data object. Because not all parameters are listed in the EDS file, instances have been
channel defined in the parameter object 2 that emulate the SEW parameter data channel with its
MOVILINK® services.
No Group Name Comment
.
1 SEW Parameter Channel SEW param. index Index of the parameter
2 SEW Parameter Channel SEW-Read/Write Read or write the value of the parameter

You will first have to write the desired index to the SEW-Param.-Index before you can
read or write a parameter. You can then read or write the SEW parameter data via
instance 2. That means you have to perform two services to read or write a parameter.
The file format of the SEW-Read/Write, SEW-Read/WriteVo, SEW-Minimum,
SEW-Maximum, SEW-Default, SEW-Scaling and SEW-Attribute services corresponds
to the SEW communication profile MOVILINK®.

Writing or read- The parameters required for operating the fieldbus have been directly incorporated into
ing the fieldbus the parameter object. They can be addressed directly via the instance.
parameters
No. Group Name Meaning
3R Device Identification Part number device
4 Control source Control signal source
5 Setpoint source Setpoint source
6R PD configuration Process data configuration
7 Setp.descr.PO1 Process output data assignment for PD1
8 Setp.descr.PO2 Process output data assignment for PD2
9 Setp.descr.PO3 Process output data assignment for PD3
10 Device parameter Act.v.descr. PI1 Process input data assignment for PD1
11 Act.v.descr. PI2 Process input data assignment for PD2
12 Act.v.descr. PI3 Process input data assignment for PD3
13 PO Data Enable Enable process data
14 Timeout response Timeout response
15R Fieldbus type Fieldbus type
16R Baud rate Baud rate via DIP switches
17R Station address MAC-ID via DIP switches

R = Read only

26 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Project Planning and Startup I
Parameter data exchange
4
0

Process output Use these parameters to monitor the process output data sent by the control.
data monitor (PO
No. Group Name Meaning
monitor)
18R PO1 setpoint Monitor of process output data word 1
19R PO2 setpoint Monitor of process output data word 2
20R PO3 setpoint Monitor of process output data word 3
21R PO4 setpoint Monitor of process output data word 4
22R PO5 setpoint Monitor of process output data word 5
PO monitor
23R PO6 setpoint Monitor of process output data word 6
24R PO7 setpoint Monitor of process output data word 7
25R PO8 setpoint Monitor of process output data word 8
26R PO09 setpoint Monitor of process output data word 9
27R PO10 setpoint Monitor of process output data word 10

R = Read only

Process input Use these parameters to monitor the process input data sent to the control.
data monitor (PI
No. Group Name Meaning
monitor)
28R PI1 actual value Monitor of process input data word 1
29R PI2 actual value Monitor of process input data word 2
30R PI3 actual value Monitor of process input data word 3
31R PI4 actual value Monitor of process input data word 4
32R PI5 actual value Monitor of process input data word 5
PI monitor
33R PI6 actual value Monitor of process input data word 6
34R PI7 actual value Monitor of process input data word 7
35R PI8 actual value Monitor of process input data word 8
36R PI9 actual value Monitor of process input data word 9
37R PI10 actual value Monitor of process input data word 10

R = Read only
Scaling and representation within the telegram correspond to the DeviceNet specifica-
tion and are identical to the SEW communication profile.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 27


I Project Planning and Startup
4 Return codes for parameter setting
0

4.5 Return codes for parameter setting


SEW-specific The return codes which the inverter sends back in the event of incorrect parameter set-
return codes ting are described in the manual for the "SEW Fieldbus Device Profile" and do not form
part of this documentation. However, the return codes are sent back in a different format
in conjunction with DeviceNet. The following table shows the data format for a parameter
response telegram.
Byte offset
0 1 2 3
Function MAC-ID Service code [=94hex] General Error Code Additional code
Example 01hex 94hex 1Fhex 10hex

• The Service code of an error telegram is always 94hhex


• The General Error Code of an inverter-specific return code is always 1Fhex = propri-
etary error
• The additional code is identical to the additional code described in the SEW fieldbus
device profile manual.
• The table shows the proprietary error10hex = Illegal parameter index.

Return codes DeviceNet-specific return codes are sent in the error telegram if the data format is not
from DeviceNet maintained during the transfer or if a service is performed which has not been imple-
mented. The coding of these return codes is described in the DeviceNet specification
(→ section " Appendix").

Timeout of The timeout is triggered by the DFD11B option. The timeout time must be set by the
explicit mes- master after the connection has been established. The DeviceNet specification refers to
sages an expected packet rate" rather than a timeout time in this case. The expected packet
rate is calculated on the basis of the timeout interval using the following formula:
tTimeout_ExplicitMessages = 4 x tExpected_Packet_Rate_ExplicitMessages

It can be set using connection object class 5, instance 1, attribute 9. The range of values
runs from 0 ms to 65535 ms in 5 ms steps.
If a timeout is triggered for the explicit messages, the connection for the explicit messag-
es is automatically dropped providing the polled I/O or bit-strobe I/O connections are not
in the ESTABLISHED state. This is the default setting for DeviceNet. The connection for
explicit messages must be re-established to communicate with these messages again.
The timeout is not forwarded to the inverter.

28 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Return codes for parameter setting
5

5 Sample Application with PLC Type SLC500


RSLogic500 for SLC System configuration
9324-RL0300END DeviceNet

Power section
PC PC
RS232C RS232C
MAC-ID MAC-ID MAC-ID
1747-CP3 1747-CP3
1 11 10
16 16 DeviceNet 16 16
Power section SLC500 outputs inputs Scanner Adapter inputs Adapter inputs
Chassis 1746-A7

Terminal module

Terminal module
1794-TB2

1794-TB2
1

1746-P2 1747-L542 1747-SDN 1746-IB16 1746-OB16 1794-ADN 1794-IB16 1794-ADN 1794-OV16

Terminating Terminating
resistor DeviceNet (remote line 1485C-P1-A50) resistor

1485A-C2 1485A-C2

MAC-ID MAC-ID MAC-ID


0 8 4

1 2 3 1 2 3 1 2 3
4 5 6 4 5 6 4 5 6
7 8 9 7 8 9 7 8 9
+/- 0 . +/- 0 . +/- 0 .

54179AEN
Figure 8: PLC equipment configuration
The following devices are employed:
Device MAC-ID
SLC5/04 -
DeviceNet scanner 1747-SDN 1
INPUT module with 32 inputs -
OUTPUT module with 32 outputs -
DeviceNet adapter with input module with 16 inputs 11
DeviceNet with output module 16 outputs 10
MOVIDRIVE® MDX61B with DFD11B 8
MOVIDRIVE® MDX61B with DFD11B 0
MOVIDRIVE® MDX61B with DFD11B 4

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 29


Sample Application with PLC Type SLC500
5 Return codes for parameter setting

The following memory areas have been specified with the DeviceNet manager software:
*******************************************************************
1747-SDN Scanlist Map
******************************************************************
Discrete Input Map:
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

I:3,000 R R R R R R R R R R R R R R R R Status word of the scanner


I:3,001 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process data from device 11
I:3,002 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process data from device 11
I:3,003 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data from device 10
I:3,004 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data from device 10
I:3,005 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID1 device 8 Polled IO
I:3,006 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID2 device 8 Polled IO
I:3,007 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID3 device 8 Polled IO
I:3,008 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID1 device 8 Bit-Strobe I/O
I:3,009 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID2 device 8 Bit-Strobe I/O
I:3,010 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 PID3 device 8 Bit-Strobe I/O
I:3,011 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID1 device 0 Polled IO
I:3,012 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID2 device 0 Polled IO
I:3,013 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID3 device 0 Polled IO
I:3,014 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID1 device 0 Bit-Strobe I/O
I:3,015 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID2 device 0 Bit-Strobe I/O
I:3,016 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 PID3 device 0 Bit-Strobe I/O
I:3,017 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID1 device 4 Polled IO
I:3,018 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID2 device 4 Polled IO
I:3,019 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID3 device 4 Polled IO
I:3,020 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID1 device 4 Bit-Strobe I/O
I:3,021 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID2 device 4 Bit-Strobe I/O
I:3,022 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 PID3 device 4 Bit-Strobe I/O

Discrete Output Map:


15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

O:3,000 R R R R R R R R R R R R R R R R Status word of the scanner


O:3,001 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Process data to device 11
O:3,002 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Process data to device 10
O:3,003 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 POD1 device 8 Polled IO
O:3,004 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 POD2 device 8 Polled IO
O:3,005 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 POD3 device 8 Polled IO
O:3,006 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 POD1 device 0 Polled IO
O:3,007 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 POD2 device 0 Polled IO
O:3,008 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 POD3 device 0 Polled IO
O:3,009 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 POD1 device 4 Polled IO
O:3,010 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 POD2 device 4 Polled IO
O:3,011 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 POD3 device 4 Polled IO
O:3,012 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Bit-Strobe for device 8

The Bit-Strobe data are contrasted to the Polled I/O data in bold.

30 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Exchange of polled I/O (process data)
5

5.1 Exchange of polled I/O (process data)


Objective In the following program, process data are to be sent to a MOVIDRIVE® MDX61B and
the motor should run at a different speed. The program sequence is shown in the follow-
ing figure.

Cycle 0
START Speed = 1000 rpm,
Enable

Cycle 1

Speed = 0 rpm,
Rapid stop

Cycle 2

Speed = -400 rpm,


Enable

Cycle 3

Speed = 0 rpm,
Rapid stop

54178AEN
Figure 9: Program sequence

The parameters listed in the following table must be set in the MOVIDRIVE® MDX61B
drive inverter for exchange of the process data.
Menu no. Index Parameter Value
100 8461 Setpoint source Fieldbus
101 8462 Control signal source Fieldbus
870 8304 Process output data description 1 Control word 1
871 8305 Process output data description 2 Speed
872 8306 Process output data description 3 No function
873 8307 Process output data description 1 Status word 1
874 8308 Process output data description 2 Speed
875 8309 Process output data description 3 No function
876 8622 PO data enable YES

MOVIDRIVE® MDX61B now works in fieldbus mode and can receive process data. The
program can now be written for the SLC500.

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 31


Sample Application with PLC Type SLC500
5 Exchange of polled I/O (process data)

Start DeviceNet communication

Status engine for control of sense of rotation

Output of the status engine

If status > 3, change to status 0

01912AEN

Output bit O:3.0/0 is set in rung 0 (program line 0), thereby starting DeviceNet commu-
nication (→ description of the DeviceNet scanner).
Rungs 1 and 3 implement the status engine with which states 0... 3 are implemented.
The current status is written to the outputs O:1.0 of the output module of the SLC500 in
rung 2.
The process data values are output to the scanner memory area in the following figure.
If status > 3, change to status 0

Status 0: Start motor, speed = 1000 rpm

Status 1: Stop motor

01913AEN

32 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Exchange of polled I/O (process data)
5

Status 0 is created in rung 4. In this status, a 6 (ENABLE) is written to memory area


O:3.3 which represents process output data word 1. A 5000 is written to memory area
O:3.4 (process output data word 2), which represents 1000 min–1. This means the motor
runs at 1000 revolutions.
Status 1 is created in rung 5. In this status, a 0 (RAPID STOP) is written to memory area
O:3.3 which represents process output data word 1. A 0 is written to memory area O:3.4
(process output data word 2), which represents the value 0 min–1. This means the motor
is stopped with the rapid stop. States 2 and 3 are treated similarly to states 0 and 1, and
are thus not explained any further.

In the figure above, the current actual value of the device with address 8, which is locat-
ed in memory area I:3.6 (process input data word 2), is multiplied by a constant factor
(in this case, by 1) and written to output memory area O:3.7 (process output data word
2 of the device with address 0).
In addition, the value 6 (ENABLE) is written to the process output data word 1 of the
device with address 0 (O:3.6). Thus, the device with address 0 follows the actual speed
with enable signal from the device with address 8.

Transmit actual position from motor 1 to motor 2

01914AEN

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 33


Sample Application with PLC Type SLC500
5 Exchange of bit-strobe I/O

5.2 Exchange of bit-strobe I/O


Objective In the following program the process input data are to be requested from the
MOVIDRIVE® drive inverter. Set the parameters listed in the following table in the invert-
er for process data exchange.
Menu no. Index Parameter Value
100 8461 Setpoint source Fieldbus
101 8462 Control signal source Fieldbus
870 8304 Process output data description 1 Control word 1
871 8305 Process output data description 2 Speed
872 8306 Process output data description 3 No function
873 8307 Process output data description 1 Status word 1
874 8308 Process output data description 2 Speed
875 8309 Process output data description 3 No function
876 8622 PO data enable YES
831 8610 Response FIELDBUS TIMEOUT Rapid st. / Warn.

MOVIDRIVE® now works in fieldbus mode and can receive process data. The program
can now be written for the PLC of the SLC500.

Send Bit-Strobe message


Start DeviceNet communication

Set / reset Strobe bit

Transmit actual values from the device to the output module

01915AEN

DeviceNet communication is enabled again in rung 0.


In rung 1, the strobe-bit of device 8 is set in relationship to the input bit I:3.2/0 (from the
DeviceNet input module).
In rung 2, process input data word 1 (I:3.8) is copied to the DeviceNet output module via
memory word O:3.12 and process input data word 2 (I:3.9) is copied to the SLC500 out-
put module via memory word O:1.0.

34 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Exchanging explicit messages (parameter data)
5

5.3 Exchanging explicit messages (parameter data)


Objective In this program, parameter data are exchanged between the control and the inverter.
Exchange of parameter data between inverter and SLC500 takes place via M-Files (→
Installations instructions on DeviceNet scanner module).
A memory area from word 224 to 255 in these M-files is reserved for explicit messages.
The structure of this memory area is shown in the following figure.

TXID cmd/status
Transmission

Word 224
header

Connection Size Word 225

Service MAC-ID Word 226

Class Word 227


Explicit Message Body

Instance Word 228

Attribute Word 229

Word 230

Data ...

Word 255

54172AEN

This memory area is split up into two areas:


• Transmission header (three words)
• Explicit message body
The memory areas in the M-Files are described in more detail in the following overview.
Memory area Function Length Value Description
Transmission header cmd/status → follow- cmd: Entry of command code
ing table status: Entry of transmission status
TXID 1 ... 255 During creation or downloading of a
request to the scanner, the contact
plan program of the SLC5 processor
assigns a TXID to the transfer.
Size 3 ... 29 Size of the explicit message body (in
1/2 word
bytes!)
each
Connec- 0 DeviceNet connection (= 0)
tion
Service 0Ehex Get_Attribute_Single (Read)
10hex Set_Attribute_Single (Write)
05hex Reset
etc. see DeviceNet specification for more
services
Explicit message body Class DeviceNet class
Instance 1 word each 0 ... 255 DeviceNet instance
Attributes DeviceNet attribute
Data 0 ... 26 words 0 ... 65535 Data content

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 35


Sample Application with PLC Type SLC500
5 Exchanging explicit messages (parameter data)

The following overviews offer a description of the command and status codes.
Command codes:
Command code Description
(cmd)
0 Ignore transmission block
1 Execute transmission block
2 Receive transmission status
3 Reset all client/server transmissions
4 Delete transmission from queue
5 ... 255 Reserved

Status codes:
Network node status (sta- Description
tus)
0 Ignore transmission block
1 Transmission completed successfully
2 Transmission in progress
3 Error – Slave device not in the scan list
4 Error – Slave is offline
5 Error – DeviceNet network connection deactivated (offline)
6 Error – Unknown transmission TXID
7 Not used
8 Error – Invalid command code
9 Error – Scanner buffer full
10 Error – Other client/server transmission in progress
11 Error – No connection to slave device
12 Error – Response data are too long for the block
13 Error – Invalid connection
14 Error – Invalid size specified
15 Error – Busy
16 ... 255 Reserved

36 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Exchanging explicit messages (parameter data)
5

The M-files are divided into a request file (M0-file) and a response file (M1-file). Data
transmission takes place as shown in the following figure.

PLC

SLC500 Scanner 1747-SDN

Request of a Scanner MOVIDRIVE® MDX61B


transmission 1.M0-File request 2. D
evic
waiting loop eNe
block t Exp
licit M
essa
ge R
eque
st

Execute
Process requests
Contact plan scanning
and responses

Ready

Error
1 2 3

or
se 4 5 6

es pon 7 8 9

ge R
+/- 0 .

Me ssa
it
plic
t Ex
Response of a Scanner eNe
evic
transmission 4.M1-File response 3. D
block waiting loop

54175AEN
Figure 10: Transmission of an explicit message

Register object class (7hex) must be used in order to read (instance 1 to 9) or write (in-
stance 2 and 3) parameters from the inverter via the SEW parameter data channel. The
data range is divided into the index (1 word) and the parameter data (2 words).
Transimission

TXID cmd/status Word 224


header

Connection Size Word 225

Service MAC-ID Word 226

Class Word 227


Explicit Message Body

Instance Word 228

Attribute Word 229

Index Word 230

Data word Low (HEX) Word 231

Data word High (HEX) Word 232

54177AEN

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 37


Sample Application with PLC Type SLC500
5 Exchanging explicit messages (parameter data)

In the sample program, a data area is reserved in the integer file (N-file, following figure),
into which the data of the M0/M1 files are written.

02149AXX

The data telegram to be used is written in N7:0 to N7:8. N7:10 to N7:15 hold the data
that are to be received.

Word length Request


Function Value
TXID 1
1
cmd: 1 = Start
Connection 0
2
Size 8
Service Ehex = Read Request
3
MAC_ID 8
4 Class 7
5 Instance 1
6 Attributes 4
7 Data 1 2070hex
8 Data 2 0hex
9 Data 3 0

Word length Response


Function Value
TXID 1
1
status 1 = successful
Connection 0
2
Size 6
Service 8hex = Read Response
3
MACID 8
4 Data 1 2070hex
5 Data 2 9hex
6 Data 3 0

38 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Sample Application with PLC Type SLC500
Exchanging explicit messages (parameter data)
5

The SEW parameter data channel can be addressed via Class 7, Instance 1 ... 9 and
Attribute 4 (→ Statement of Conformance).
In rung 5, the 9 bytes starting from N7:0 are copied into the M0-file with a rising edge of
bit B3:0/1. This starts the reading of parameter 8304 (2070hex). In rung 6, the system
waits for the rising edge of scanner bit I:3.0/15. I:3.0/15 shows that the data are present.
Request profile B3:0/1 can then be reset.
At this point, the received data still have to be written into the N-file. To this end, nine
words of the M1-files N7:10...19 are written.

Write transmit data

Read receive data

01921AEN

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 39


kVA n Technical Data
6 f
DFD11B option
i
P Hz

6 Technical Data
6.1 DFD11B option

DFD11B option
Part number 824 972 5
Power consumption P=3W
Communication protocol Master/slave connection set acc. to DeviceNet specification version 2.0
Number of process data Adjustable via DIP switches:
words • 1 ... 10 process data words
• 1 ... 4 process data words with Bit-Strobe I/O
Baud rate 125, 250 or 500 kBaud, to be set via DIP switches
Bus cable length For thick cable according to DeviceNet specification 2.0 Appendix B
• 500 m at 125 kbaud
• 250 m at 250 kbaud
• 100 m at 500 kbaud
Transmission level ISO 11 98 - 24 V
Connection technology • 2-wire bus and 2-wire supply voltage 24 VDC with 5-pole Phoenix
terminal
• Pin assignment acc. to DeviceNet specification
MAC-ID 0 ... 63, can be set using DIP switch
Max. 64 stations
Supported services • Polled I/O: 1 ... 10 words
• Bit-Strobe I/O: 1 ... 4 words
• Explicit messages:
– Get_Attribute_Single
– Set_Attribute_Single
– Reset
– Allocate_MS_Connection_Set
– Release_MS_Connection_Set
Tools for startup • MOVITOOLS® software package from version 4.20
• DBG60B keypad
Firmware status of Firmware status 824 854 0.11 or above (→ display with P076)
MOVIDRIVE® MDX61B

40 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
General error codes (error messages)
7

7 Appendix
7.1 General error codes (error messages)

General error Error name Description


code (hex)
00 - 01 Reserved for DeviceNet
02 Resource unavailable The source required for performing the service is unavailable
03 - 07 Reserved for DeviceNet
08 Service not supported The service is not supported for the selected class/instance
09 Invalid attribute value Invalid attribute data have been sent
0A Reserved for DeviceNet
0B Already in requested The selected object is already in the requested mode/state
mode/state
0C Object state conflict The selected object cannot perform the service in its current
status
0D Reserved for DeviceNet
0E Attribute not settable It is not possible to access the selected object for writing.
0F Pivilege violation Violation of access entitlement
10 Device state conflict The current status of the device makes it impossible to perform
the required service
11 Reply data too large The length of the transmitted data is longer than the size of the
receive buffer
12 Reserved for DeviceNet
13 Not enough data The length of the transferred data is too short for the service to
be performed
14 Attribute not supported The selected attribute is not supported
15 Too much data The length of the transferred data is too long for the service to
be performed
16 Object does not exist The selected object is not implemented in the device
17 Reserved for DeviceNet
18 No stored attribute data The requested data have not been stored previously
19 Store operation failure The data could not be stored because an error occurred while
saving them
1A - 1E Reserved for DeviceNet
1F Vendor specific error Vendor specific error (→Manual"SEW Fieldbus Device Profile")
20 invalid parameter Invalid parameter
This error message is used when a parameter does not satisfy
the requirements of the specification and/or the requirements of
the application.
21 - CF Future extensions Reserved by DeviceNet for additional definitions
D0 - DF Reserved for Object Use this area if an occurring error cannot be entered in one of
Class and service the error groups listed above.
errors

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 41


Appendix
7 Statement of Conformance

7.2 Statement of Conformance

Device Net Statement of Conformance

SOC data as of 6 - 3 - 2004


Fill in the blank or X the appropriate box

General Conforms to DeviceNet Specification Volume I - Release 2.0 Volume II - Release 2.0
Device Errata
Data Vendor Name SEW Eurodrive GmbH
Device Profile Vendor Specific
Product Name SEW-MOVIDRIVE-DFD11B
Product Code 10
Product Revision 1.01
DeviceNet Physical Network Power Consumption (Max) 0,4 A @ 11V dc (worst case)
Conformance Data
Connector Style Open-Hardwired Sealed-Mini
Open-Pluggable X Sealed-Micro
Isolated Physical Layer Yes
No
LEDs Supported Module Combo Mod/Net X
None Network I/O
MAC ID Setting DIP Switch X Software Settable
Other
Default MAC ID 63
Communication Rate Setting DIP Switch X Software Settable
Other
Communication Rates Supported 125k bit/s X 500k bit/s X
250k bit/s X
DeviceNet Device Network Behavior Group 2 Client Group 2 Only Client
Communication Check All That Apply Group 2 Server Group 2 Only Server X
Data Peer-To-Peer Tool (not a Device)

UCMM Explicit Message Groups Supported Group 1 Group 2 Group 3


Dynamic I/O Message Groups (Peer to Peer) Group 1 Group 2 Group 3
Default I/O Data Address Path Input: Class 4 Inst. 64 Attr. 3
Output: Class 4 Inst. 64 Attr. 3

Fragmented Explicit Messaging Supported Yes No


If yes, Acknowledge TimeOut 1000 ms
Typical Target Addresses
Consumption Service 16 Class 1 Inst. 1 Attr. 7
Production Service 14 Class 1 Inst. 1 Attr. 7

1 of 9

54129AXX

42 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
Statement of Conformance
7

Device Net Statement of Conformance

DeviceNet Identity Object 0x01


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation 2 Max instance
X None Supported 3 Number of Instances
4 Optional attributes list
5 Optional services list
6 Max Id of class attributes
7 Max Id of instance attributes
DeviceNet Services Parameter Options
Services Get_Attributes_All
Reset
X None Supported Get_Attribute_Single
Find_Next_Object_instance
Object Instance ID Description Get Set Value Limits
Attributes Open 1 Vendor X =(315)
2 Device type X =(100)
3 Product code X =(10)
4 Revision X =(1.01)
5 Status (bits supported) X
6 Serial number X
7 Product name X SEW-MOVIDRIVE-DFD11B

8 State
9 Config. Consistency Value
10 Heartbeat Interval
DeviceNet Services Parameter Options
Services Get_Attributes_All
X Reset 0
X Get_Attribute_Single
Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 2 of 9
54130AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 43


Appendix
7 Statement of Conformance

Device Net Statement of Conformance

DeviceNet Message Router Object 0x02


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation 2 Max instance
X None Supported 3 Number of Instances
4 Optional attribute list
5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
Services Get_Attributes_All
Get_Attribute_Single
X None Supported
Object Instance ID Description Get Set Value Limits
Attributes Open 1 Object list
2 Maximum connections supported
X None Supported 3 Number of active connections
4 Active connections list
DeviceNet Services Parameter Options
Services Get_Attributes_All
Get_Attribute_Single
X None Supported Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 3 of 9
54132AXX

44 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
Statement of Conformance
7

Device Net Statement of Conformance

DeviceNet DeviceNet Object 0x03


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision X =(2)
Implementation 2 Max instance
None Supported 3 Number of Instances
4 Optional attribute list
5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
Services Get_Attribute_Single
X None Supported
Object Instance ID Description Get Set Value Limits
Attributes Open 1 MAC ID X =(0..63)
2 Baud rate X =(0..2)
None Supported 3 BOI X =(0)
4 Bus-off counter X X =(0..255)
5 Allocation information X
6 MAC ID switch changed X =(0)
7 Baud rate switch changed X =(0)
8 MAC ID switch value X =(0..63)
9 Baud rate switch value X =(0..2)

DeviceNet Services Parameter Options


Services X Get_Attribute_Single
X Set_Attribute_Single
None Supported X Allocate M/S connection set
X Release M/S connection set

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 4 of 9
54133AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 45


Appendix
7 Statement of Conformance

Device Net Statement of Conformance

DeviceNet Connection Object 0x05


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation X None Supported 2 Max instance
3 Number of Instances
Complete this sheet for 4 Optional attribute list
each connection supported. 5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
X None Supported Reset
Create
Delete
Get_Attribute_Single
Find_Next_Object_Instance

Object Instance Connection Type Max Connection Instances


M/S Explicit Message 1 Server Client 1 Total

Complete this section for Production trigger(s) Cyclic COS App. trig.
Dynamic I/O connections Transport type(s) Server X Client
Transport class(es) 2 X 3

ID Description Get Set Value Limits


Attributes Open 1 State X
2 Instance type X
3 Transport Class trigger X
4 Produced connection ID X
5 Consumed connection ID X
6 Initial comm. characteristics X
7 Produced connection size X
8 Consumed connection size X
9 Expected packet rate X X =(0..65530)
12 Watchdog time-out action X
13 Produced connection path len X
14 Produced connection path X
15 Consumed connection path len X
16 Consumed connection path X
17 Production inhibit time X =(0)
DeviceNet Services Parameter Options
Services X Reset
Delete
Apply_Attributes
X Get_Attribute_Single
X Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 5 of 9
54134AXX

46 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
Statement of Conformance
7

Device Net Statement of Conformance

DeviceNet Connection Object 0x05


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation X None Supported 2 Max instance
3 Number of Instances
Complete this sheet for 4 Optional attribute list
each connection supported. 5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
X None Supported Reset
Create
Delete
Get_Attribute_Single
Find_Next_Object_Instance

Object Instance Connection Type Max Connection Instances


M/S Poll 1 Server Client 1 Total

Complete this section for Production trigger(s) Cyclic COS App. trig.
Dynamic I/O connections Transport type(s) Server X Client
Transport class(es) 2 X 3

ID Description Get Set Value Limits


Attributes Open 1 State X
2 Instance type X
3 Transport Class trigger X
4 Produced connection ID X
5 Consumed connection ID X
6 Initial comm. characteristics X
7 Produced connection size X
8 Consumed connection size X
9 Expected packet rate X X =(0..65530)
12 Watchdog time-out action X
13 Produced connection path len X
14 Produced connection path X
15 Consumed connection path len X
16 Consumed connection path X
17 Production inhibit time X =(0)
DeviceNet Services Parameter Options
Services X Reset
Delete
Apply_Attributes
X Get_Attribute_Single
X Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 6 of 9

54135AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 47


Appendix
7 Statement of Conformance

Device Net Statement of Conformance

DeviceNet Connection Object 0x05


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation X None Supported 2 Max instance
3 Number of Instances
Complete this sheet for 4 Optional attribute list
each connection supported. 5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
X None Supported Reset
Create
Delete
Get_Attribute_Single
Find_Next_Object_Instance

Object Instance Connection Type Max Connection Instances


M/S Bit Strobe 1 Server Client 1 Total

Complete this section for Production trigger(s) Cyclic COS App. trig.
Dynamic I/O connections Transport type(s) Server X Client
Transport class(es) 2 X 3

ID Description Get Set Value Limits


Attributes Open 1 State X
2 Instance type X
3 Transport Class trigger X
4 Produced connection ID X
5 Consumed connection ID X
6 Initial comm. characteristics X
7 Produced connection size X
8 Consumed connection size X
9 Expected packet rate X X =(0..65530)
12 Watchdog time-out action X
13 Produced connection path len X
14 Produced connection path X
15 Consumed connection path len X
16 Consumed connection path X
17 Production inhibit time X =(0)
DeviceNet Services Parameter Options
Services X Reset
Delete
Apply_Attributes
X Get_Attribute_Single
X Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 7 of 9
54136AXX

48 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
Statement of Conformance
7

Device Net Statement of Conformance

DeviceNet Register Object 0x07


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation 2 Max instance
X None Supported 3 Number of Instances
4 Optional attribute list
5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
DeviceNet Services Parameter Options
Services Get_Attribute_Single

X None Supported
Object Instance ID Description Get Set Value Limits
Attributes Open 1 Bad Flag X
2 Direction X
None Supported 3 Size X
4 Data X X
DeviceNet Services Parameter Options
Services X Get_Attribute_Single 84520000000000
None Supported X Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 8 of 9
54137AXX

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 49


Appendix
7 Statement of Conformance

Device Net Statement of Conformance

DeviceNet Parameter Object 0x0F


Required Object Class ID Description Get Set Value Limits
Object Attributes Open 1 Revision
Implementation 2 Max instance X
None Supported 3 Number of Instances
4 Optional attribute list
5 Optional service list
6 Max ID of class attributes
7 Max ID of instance attributes
8 Parameter class descriptor X
9 Configuration assembly instance X
10 Native language
DeviceNet Services Parameter Options
Services Get_Attributes_All
Reset
None Supported X Get_Attribute_Single
Set_Attribute_Single
Restore Save
Object Instance ID Description Get Set Value Limits
Attributes Open 1 Parameter value X X =(0..4294967294)
2 Link Path size X
None Supported 3 Link path X
4 Descriptor X
5 Data type X
6 Data size X =(4)
7 Parameter name string
8 Units string
9 Help string
10 Minimum value
11 Maximum value
12 Default value
13 Scaling multiplier
14 Scaling divisor
15 Scaling base
16 Scaling offset
17 Multiplier link
18 Divisor link
19 Base link
20 Offset link
21 Decimal precision
DeviceNet Services
Services Get_Attribute_All
None Supported X Get_Attribute_Single X Set_Attribute_Single

Vendor Specific Additions Yes If yes, fill out the Vendor Specific Additions form. No X
X Get indicates attribute value is returned by the Get_Attribute_Single service.
X Set indicates attribute value is written to by the Set_Attribute_Single service. 9 of 9
54138AXX

50 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Appendix
Definitions of terminology
7

7.3 Definitions of terminology

Term Description
Allocate Provides a service for setting up a connection.
Attributes Attribute of an object class or instance. Describes the characteristics of the
object class or instance in more detail.
BIO - Bit-Strobe I/O All stations can be addressed with a broadcast telegram. The addressed
stations respond with the process input data.
Class DeviceNet object class
Device-Net scanner Plug-in module for the Allen Bradley PLC which connects the PLC fieldbus to
the peripheral devices.
DUP-MAC check Duplicate MAC-ID test
Explicit message body Includes the class no., instance no., attribute no. and the data.
Explicit message Parameter data message; assists in addressing the DeviceNet objects.
Get_Attribute_Single Read service for a parameter.
Instance Instance of an object class. Divides the object classes into additional sub-
groups.
MAC-ID Media Access Control identifier: node address of the device.
M-file Provides the data range between the PLC and the scanner module.
Mod/Net Module/Network
Node ID Node address = MAC-ID
PIO - Polled I/O Process data channel of DeviceNet; allows process output data to be sent and
process input data to be received.
Release Provides a service for setting up a connection.
Reset Provides a service for resetting an error.
Rung SLC500 program line
Service Service performed via bus, e.g. read service, write service, etc.
Set_Attribute_Single Write service for a parameter.
SLC500 Allen Bradley PLC

Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet 51


8 Index

8 Index
A Setting the DIP switches .................................... 11
Additional documentation ......................................5 Setting the baud rate ................................... 11
Setting the MAC-ID ...................................... 11
B Setting the process data length ................... 11
Baud rate ..................................................... 11, 40 SEW parameter data channel ............................ 22
Building the DeviceNet network with RSNetWorx ... Startup of the drive inverter ................................ 14
17 Power-UP test .............................................. 16
Bus terminating resistor ......................................10 Statement of Conformance ................................ 42
BUS-OFF LED ....................................................13
T
C Technical data DFD11B ..................................... 40
Connection and terminal assignment DFD11B .....9
D
Definitions of Terminology ..................................51
Display of operating status DFD11B option card 12
E
Error messages ...................................................41
I
Important Notes ....................................................4
Installing the DFD11B option card ........................7
Installing the DFE11B option card
Basic procedure ..............................................8
L
LED BIO ..............................................................13
LED Mod/Net ......................................................12
N
Notes on routing of bus cables ...........................10
O
Operating displays of DFD11B option card
LED BIO .......................................................13
LED Mod/Net ................................................12
PIO LED .......................................................12
P
Parameter data exchange ...................................22
PCP length ..........................................................11
Pin assignment ...................................................10
PIO LED ..............................................................12
Process data exchange ......................................18
Bit-strobe I/O ................................................19
Polled I/O ......................................................18
Timeout response with bit-strobe I/O ............21
Timeout response with polled I/O .................19
Process data length ............................................11
R
Return codes for parameter setting ....................28
S
Safety Notes .........................................................4
Safety notes on bus systems ................................4
Sample Application with PLC Type SLC500 .......29

52 Manual – MOVIDRIVE® MDX61B DFD11B Fieldbus Interface DeviceNet


Address List

Address List
Germany
Headquarters Bruchsal SEW-EURODRIVE GmbH & Co KG Tel. +49 7251 75-0
Production Ernst-Blickle-Straße 42 Fax +49 7251 75-1970
Sales D-76646 Bruchsal http://www.sew-eurodrive.de
P.O. Box sew@sew-eurodrive.de
Postfach 3023 · D-76642 Bruchsal
Service Central SEW-EURODRIVE GmbH & Co KG Tel. +49 7251 75-1710
Competence Center Gear units / Ernst-Blickle-Straße 1 Fax +49 7251 75-1711
Motors D-76676 Graben-Neudorf sc-mitte-gm@sew-eurodrive.de
Central SEW-EURODRIVE GmbH & Co KG Tel. +49 7251 75-1780
Electronics Ernst-Blickle-Straße 42 Fax +49 7251 75-1769
D-76646 Bruchsal sc-mitte-e@sew-eurodrive.de
North SEW-EURODRIVE GmbH & Co KG Tel. +49 5137 8798-30
Alte Ricklinger Straße 40-42 Fax +49 5137 8798-55
D-30823 Garbsen (near Hannover) sc-nord@sew-eurodrive.de
East SEW-EURODRIVE GmbH & Co KG Tel. +49 3764 7606-0
Dänkritzer Weg 1 Fax +49 3764 7606-30
D-08393 Meerane (near Zwickau) sc-ost@sew-eurodrive.de
South SEW-EURODRIVE GmbH & Co KG Tel. +49 89 909552-10
Domagkstraße 5 Fax +49 89 909552-50
D-85551 Kirchheim (near München) sc-sued@sew-eurodrive.de
West SEW-EURODRIVE GmbH & Co KG Tel. +49 2173 8507-30
Siemensstraße 1 Fax +49 2173 8507-55
D-40764 Langenfeld (near Düsseldorf) sc-west@sew-eurodrive.de
Drive Service Hotline / 24 Hour Service +49 180 5 SEWHELP
+49 180 5 7394357
Additional addresses for service in Germany provided on request!

France
Production Haguenau SEW-USOCOME Tel. +33 3 88 73 67 00
Sales 48-54, route de Soufflenheim Fax +33 3 88 73 66 00
Service B. P. 20185 http://www.usocome.com
F-67506 Haguenau Cedex sew@usocome.com
Assembly Bordeaux SEW-USOCOME Tel. +33 5 57 26 39 00
Sales Parc d’activités de Magellan Fax +33 5 57 26 39 09
Service 62, avenue de Magellan - B. P. 182
F-33607 Pessac Cedex
Lyon SEW-USOCOME Tel. +33 4 72 15 37 00
Parc d’Affaires Roosevelt Fax +33 4 72 15 37 15
Rue Jacques Tati
F-69120 Vaulx en Velin
Paris SEW-USOCOME Tel. +33 1 64 42 40 80
Zone industrielle Fax +33 1 64 42 40 88
2, rue Denis Papin
F-77390 Verneuil I’Etang
Additional addresses for service in France provided on request!

Algeria
Sales Alger Réducom Tel. +213 21 8222-84
16, rue des Frères Zaghnoun Fax +213 21 8222-84
Bellevue El-Harrach
16200 Alger

Argentina
Assembly Buenos Aires SEW EURODRIVE ARGENTINA S.A. Tel. +54 3327 4572-84
Sales Centro Industrial Garin, Lote 35 Fax +54 3327 4572-21
Service Ruta Panamericana Km 37,5 sewar@sew-eurodrive.com.ar
1619 Garin

11/2004 53
Address List

Australia
Assembly Melbourne SEW-EURODRIVE PTY. LTD. Tel. +61 3 9933-1000
Sales 27 Beverage Drive Fax +61 3 9933-1003
Service Tullamarine, Victoria 3043 http://www.sew-eurodrive.com.au
enquires@sew-eurodrive.com.au
Sydney SEW-EURODRIVE PTY. LTD. Tel. +61 2 9725-9900
9, Sleigh Place, Wetherill Park Fax +61 2 9725-9905
New South Wales, 2164 enquires@sew-eurodrive.com.au

Austria
Assembly Wien SEW-EURODRIVE Ges.m.b.H. Tel. +43 1 617 55 00-0
Sales Richard-Strauss-Strasse 24 Fax +43 1 617 55 00-30
Service A-1230 Wien http://sew-eurodrive.at
sew@sew-eurodrive.at

Belgium
Assembly Brüssel CARON-VECTOR S.A. Tel. +32 10 231-311
Sales Avenue Eiffel 5 Fax +32 10 231-336
Service B-1300 Wavre http://www.caron-vector.be
info@caron-vector.be

Brazil
Production Sao Paulo SEW-EURODRIVE Brasil Ltda. Tel. +55 11 6489-9133
Sales Avenida Amâncio Gaiolli, 50 Fax +55 11 6480-3328
Service Caixa Postal: 201-07111-970 http://www.sew.com.br
Guarulhos/SP - Cep.: 07251-250 sew@sew.com.br
Additional addresses for service in Brazil provided on request!

Bulgaria
Sales Sofia BEVER-DRIVE GmbH Tel. +359 2 9532565
Bogdanovetz Str.1 Fax +359 2 9549345
BG-1606 Sofia bever@fastbg.net

Cameroon
Sales Douala Electro-Services Tel. +237 4322-99
Rue Drouot Akwa Fax +237 4277-03
B.P. 2024
Douala

Canada
Assembly Toronto SEW-EURODRIVE CO. OF CANADA LTD. Tel. +1 905 791-1553
Sales 210 Walker Drive Fax +1 905 791-2999
Service Bramalea, Ontario L6T3W1 http://www.sew-eurodrive.ca
l.reynolds@sew-eurodrive.ca
Vancouver SEW-EURODRIVE CO. OF CANADA LTD. Tel. +1 604 946-5535
7188 Honeyman Street Fax +1 604 946-2513
Delta. B.C. V4G 1 E2 b.wake@sew-eurodrive.ca
Montreal SEW-EURODRIVE CO. OF CANADA LTD. Tel. +1 514 367-1124
2555 Rue Leger Street Fax +1 514 367-3677
LaSalle, Quebec H8N 2V9 a.peluso@sew-eurodrive.ca
Additional addresses for service in Canada provided on request!

Chile
Assembly Santiago de SEW-EURODRIVE CHILE LTDA. Tel. +56 2 75770-00
Sales Chile Las Encinas 1295 Fax +56 2 75770-01
Service Parque Industrial Valle Grande ventas@sew-eurodrive.cl
LAMPA
RCH-Santiago de Chile
P.O. Box
Casilla 23 Correo Quilicura - Santiago - Chile

China
Production Tianjin SEW-EURODRIVE (Tianjin) Co., Ltd. Tel. +86 22 25322612
Assembly No. 46, 7th Avenue, TEDA Fax +86 22 25322611
Sales Tianjin 300457 gm-tianjin@sew-eurodrive.cn
Service http://www.sew.com.cn

54 11/2004
Address List

China
Assembly Suzhou SEW-EURODRIVE (Suzhou) Co., Ltd. Tel. +86 512 62581781
Sales 333, Suhong Middle Road Fax +86 512 62581783
Service Suzhou Industrial Park suzhou@sew.com.cn
Jiangsu Province, 215021
P. R. China

Colombia
Assembly Bogotá SEW-EURODRIVE COLOMBIA LTDA. Tel. +57 1 54750-50
Sales Calle 22 No. 132-60 Fax +57 1 54750-44
Service Bodega 6, Manzana B sewcol@andinet.com
Santafé de Bogotá

Croatia
Sales Zagreb KOMPEKS d. o. o. Tel. +385 1 4613-158
Service PIT Erdödy 4 II Fax +385 1 4613-158
HR 10 000 Zagreb kompeks@net.hr

Czech Republic
Sales Praha SEW-EURODRIVE CZ S.R.O. Tel. +420 a220121236
Business Centrum Praha Fax +420 220121237
Luná 591 http://www.sew-eurodrive.cz
CZ-16000 Praha 6 - Vokovice sew@sew-eurodrive.cz

Denmark
Assembly Kopenhagen SEW-EURODRIVEA/S Tel. +45 43 9585-00
Sales Geminivej 28-30, P.O. Box 100 Fax +45 43 9585-09
Service DK-2670 Greve http://www.sew-eurodrive.dk
sew@sew-eurodrive.dk

Estonia
Sales Tallin ALAS-KUUL AS Tel. +372 6593230
Paldiski mnt.125 Fax +372 6593231
EE 0006 Tallin veiko.soots@alas-kuul.ee

Finland
Assembly Lahti SEW-EURODRIVE OY Tel. +358 201 589-300
Sales Vesimäentie 4 Fax +358 3 780-6211
Service FIN-15860 Hollola 2 http://www.sew-eurodrive.fi
sew@sew.fi

Gabon
Sales Libreville Electro-Services Tel. +241 7340-11
B.P. 1889 Fax +241 7340-12
Libreville

Great Britain
Assembly Normanton SEW-EURODRIVE Ltd. Tel. +44 1924 893-855
Sales Beckbridge Industrial Estate Fax +44 1924 893-702
Service P.O. Box No.1 http://www.sew-eurodrive.co.uk
GB-Normanton, West- Yorkshire WF6 1QR info@sew-eurodrive.co.uk

Greece
Sales Athen Christ. Boznos & Son S.A. Tel. +30 2 1042 251-34
Service 12, Mavromichali Street Fax +30 2 1042 251-59
P.O. Box 80136, GR-18545 Piraeus http://www.boznos.gr
info@boznos.gr

Hong Kong
Assembly Hong Kong SEW-EURODRIVE LTD. Tel. +852 2 7960477 + 79604654
Sales Unit No. 801-806, 8th Floor Fax +852 2 7959129
Service Hong Leong Industrial Complex sew@sewhk.com
No. 4, Wang Kwong Road
Kowloon, Hong Kong

11/2004 55
Address List

Hungary
Sales Budapest SEW-EURODRIVE Kft. Tel. +36 1 437 06-58
Service H-1037 Budapest Fax +36 1 437 06-50
Kunigunda u. 18 office@sew-eurodrive.hu

India
Assembly Baroda SEW-EURODRIVE India Pvt. Ltd. Tel. +91 265 2831086
Sales Plot No. 4, Gidc Fax +91 265 2831087
Service Por Ramangamdi · Baroda - 391 243 mdoffice@seweurodriveindia.com
Gujarat
Technical Offices Bangalore SEW-EURODRIVE India Private Limited Tel. +91 80 22266565
308, Prestige Centre Point Fax +91 80 22266569
7, Edward Road sewbangalore@sify.com
Bangalore
Mumbai SEW-EURODRIVE India Private Limited Tel. +91 22 28348440
312 A, 3rd Floor, Acme Plaza Fax +91 22 28217858
Andheri Kurla Road, Andheri (E) sewmumbai@vsnl.net
Mumbai

Ireland
Sales Dublin Alperton Engineering Ltd. Tel. +353 1 830-6277
Service 48 Moyle Road Fax +353 1 830-6458
Dublin Industrial Estate
Glasnevin, Dublin 11

Israel
Sales Tel-Aviv Liraz Handasa Ltd. Tel. +972 3 5599511
Ahofer Str 34B / 228 Fax +972 3 5599512
58858 Holon lirazhandasa@barak-online.net

Italy
Assembly Milano SEW-EURODRIVE di R. Blickle & Co.s.a.s. Tel. +39 2 96 9801
Sales Via Bernini,14 Fax +39 2 96 799781
Service I-20020 Solaro (Milano) sewit@sew-eurodrive.it

Ivory Coast
Sales Abidjan SICA Tel. +225 2579-44
Ste industrielle et commerciale pour l’Afrique Fax +225 2584-36
165, Bld de Marseille
B.P. 2323, Abidjan 08

Japan
Assembly Toyoda-cho SEW-EURODRIVE JAPAN CO., LTD Tel. +81 538 373811
Sales 250-1, Shimoman-no, Fax +81 538 373814
Service Toyoda-cho, Iwata gun sewjapan@sew-eurodrive.co.jp
Shizuoka prefecture, 438-0818

Korea
Assembly Ansan-City SEW-EURODRIVE KOREA CO., LTD. Tel. +82 31 492-8051
Sales B 601-4, Banweol Industrial Estate Fax +82 31 492-8056
Service Unit 1048-4, Shingil-Dong master@sew-korea.co.kr
Ansan 425-120

Latvia
Sales Riga SIA Alas-Kuul Tel. +371 7139386
Katlakalna 11C Fax +371 7139386
LV-1073 Riga info@alas-kuul.ee

Lebanon
Sales Beirut Gabriel Acar & Fils sarl Tel. +961 1 4947-86
B. P. 80484 +961 1 4982-72
Bourj Hammoud, Beirut +961 3 2745-39
Fax +961 1 4949-71
gacar@beirut.com

56 11/2004
Address List

Lithuania
Sales Alytus UAB Irseva Tel. +370 315 79204
Merkines g. 2A Fax +370 315 79688
LT-4580 Alytus irmantas.irseva@one.lt

Luxembourg
Assembly Brüssel CARON-VECTOR S.A. Tel. +32 10 231-311
Sales Avenue Eiffel 5 Fax +32 10 231-336
Service B-1300 Wavre http://www.caron-vector.be
info@caron-vector.be

Malaysia
Assembly Johore SEW-EURODRIVE SDN BHD Tel. +60 7 3549409
Sales No. 95, Jalan Seroja 39, Taman Johor Jaya Fax +60 7 3541404
Service 81000 Johor Bahru, Johor kchtan@pd.jaring.my
West Malaysia

Morocco
Sales Casablanca S. R. M. Tel. +212 2 6186-69 + 6186-70 + 6186-
Société de Réalisations Mécaniques 71
5, rue Emir Abdelkader Fax +212 2 6215-88
05 Casablanca srm@marocnet.net.ma

Netherlands
Assembly Rotterdam VECTOR Aandrijftechniek B.V. Tel. +31 10 4463-700
Sales Industrieweg 175 Fax +31 10 4155-552
Service NL-3044 AS Rotterdam http://www.vector.nu
Postbus 10085 info@vector.nu
NL-3004 AB Rotterdam

New Zealand
Assembly Auckland SEW-EURODRIVE NEW ZEALAND LTD. Tel. +64 9 2745627
Sales P.O. Box 58-428 Fax +64 9 2740165
Service 82 Greenmount drive sales@sew-eurodrive.co.nz
East Tamaki Auckland
Christchurch SEW-EURODRIVE NEW ZEALAND LTD. Tel. +64 3 384-6251
10 Settlers Crescent, Ferrymead Fax +64 3 384-6455
Christchurch sales@sew-eurodrive.co.nz

Norway
Assembly Moss SEW-EURODRIVE A/S Tel. +47 69 241-020
Sales Solgaard skog 71 Fax +47 69 241-040
Service N-1599 Moss sew@sew-eurodrive.no

Peru
Assembly Lima SEW DEL PERU MOTORES REDUCTORES Tel. +51 1 3495280
Sales S.A.C. Fax +51 1 3493002
Service Los Calderos, 120-124 sewperu@sew-eurodrive.com.pe
Urbanizacion Industrial Vulcano, ATE, Lima

Poland
Assembly Lodz SEW-EURODRIVE Polska Sp.z.o.o. Tel. +48 42 67710-90
Sales ul. Techniczna 5 Fax +48 42 67710-99
Service PL-92-518 Lodz http://www.sew-eurodrive.pl
sew@sew-eurodrive.pl

Portugal
Assembly Coimbra SEW-EURODRIVE, LDA. Tel. +351 231 20 9670
Sales Apartado 15 Fax +351 231 20 3685
Service P-3050-901 Mealhada http://www.sew-eurodrive.pt
infosew@sew-eurodrive.pt

Romania
Sales Bucuresti Sialco Trading SRL Tel. +40 21 230-1328
Service str. Madrid nr.4 Fax +40 21 230-7170
011785 Bucuresti sialco@sialco.ro

11/2004 57
Address List

Russia
Sales St. Petersburg ZAO SEW-EURODRIVE Tel. +7 812 5357142 +812 5350430
P.O. Box 263 Fax +7 812 5352287
RUS-195220 St. Petersburg http://www.sew-eurodrive.ru
sew@sew-eurodrive.ru

Senegal
Sales Dakar SENEMECA Tel. +221 849 47-70
Mécanique Générale Fax +221 849 47-71
Km 8, Route de Rufisque senemeca@sentoo.sn
B.P. 3251, Dakar

Serbia and Montenegro


Sales Beograd DIPAR d.o.o. Tel. +381 11 3046677
Kajmakcalanska 54 Fax +381 11 3809380
SCG-11000 Beograd dipar@yubc.net

Singapore
Assembly Singapore SEW-EURODRIVE PTE. LTD. Tel. +65 68621701
Sales No 9, Tuas Drive 2 Fax +65 68612827
Service Jurong Industrial Estate sewsingapore@sew-eurodrive.com
Singapore 638644

Slovakia
Sales Sered SEW-Eurodrive SK s.r.o. Tel. +421 31 7891311
Trnavska 920 Fax +421 31 7891312
SK-926 01 Sered sew@sew-eurodrive.sk

Slovenia
Sales Celje Pakman - Pogonska Tehnika d.o.o. Tel. +386 3 490 83-20
Service UI. XIV. divizije 14 Fax +386 3 490 83-21
SLO – 3000 Celje pakman@siol.net

South Africa
Assembly Johannesburg SEW-EURODRIVE (PROPRIETARY) LIMITED Tel. +27 11 248-7000
Sales Eurodrive House Fax +27 11 494-3104
Service Cnr. Adcock Ingram and Aerodrome Roads dross@sew.co.za
Aeroton Ext. 2
Johannesburg 2013
P.O.Box 90004
Bertsham 2013
Capetown SEW-EURODRIVE (PROPRIETARY) LIMITED Tel. +27 21 552-9820
Rainbow Park Fax +27 21 552-9830
Cnr. Racecourse & Omuramba Road Telex 576 062
Montague Gardens dswanepoel@sew.co.za
Cape Town
P.O.Box 36556
Chempet 7442
Cape Town
Durban SEW-EURODRIVE (PROPRIETARY) LIMITED Tel. +27 31 700-3451
2 Monaceo Place Fax +27 31 700-3847
Pinetown dtait@sew.co.za
Durban
P.O. Box 10433, Ashwood 3605

Spain
Assembly Bilbao SEW-EURODRIVE ESPAÑA, S.L. Tel. +34 9 4431 84-70
Sales Parque Tecnológico, Edificio, 302 Fax +34 9 4431 84-71
Service E-48170 Zamudio (Vizcaya) sew.spain@sew-eurodrive.es

Sweden
Assembly Jönköping SEW-EURODRIVE AB Tel. +46 36 3442-00
Sales Gnejsvägen 6-8 Fax +46 36 3442-80
Service S-55303 Jönköping http://www.sew-eurodrive.se
Box 3100 S-55003 Jönköping info@sew-eurodrive.se

58 11/2004
Address List

Switzerland
Assembly Basel Alfred lmhof A.G. Tel. +41 61 41717-17
Sales Jurastrasse 10 Fax +41 61 41717-00
Service CH-4142 Münchenstein bei Basel http://www.imhof-sew.ch
info@imhof-sew.ch

Thailand
Assembly Chon Buri SEW-EURODRIVE (Thailand) Ltd. Tel. +66 38 454281
Sales Bangpakong Industrial Park 2 Fax +66 38 454288
Service 700/456, Moo.7, Tambol Donhuaroh sewthailand@sew-eurodrive.co.th
Muang District
Chon Buri 20000

Tunisia
Sales Tunis T. M.S. Technic Marketing Service Tel. +216 1 4340-64 + 1 4320-29
7, rue Ibn EI Heithem Fax +216 1 4329-76
Z.I. SMMT
2014 Mégrine Erriadh

Turkey
Assembly Istanbul SEW-EURODRIVE Tel. +90 216 4419163 + 216 4419164 +
Sales Hareket Sistemleri Sirketi 216 3838014
Service Bagdat Cad. Koruma Cikmazi No. 3 Fax +90 216 3055867
TR-34846 Maltepe ISTANBUL sew@sew-eurodrive.com.tr

USA
Production Greenville SEW-EURODRIVE INC. Tel. +1 864 439-7537
Assembly 1295 Old Spartanburg Highway Fax Sales +1 864 439-7830
Sales P.O. Box 518 Fax Manuf. +1 864 439-9948
Service Lyman, S.C. 29365 Fax Ass. +1 864 439-0566
Telex 805 550
http://www.seweurodrive.com
cslyman@seweurodrive.com
Assembly San Francisco SEW-EURODRIVE INC. Tel. +1 510 487-3560
Sales 30599 San Antonio St. Fax +1 510 487-6381
Service Hayward, California 94544-7101 cshayward@seweurodrive.com
Philadelphia/PA SEW-EURODRIVE INC. Tel. +1 856 467-2277
Pureland Ind. Complex Fax +1 856 845-3179
2107 High Hill Road, P.O. Box 481 csbridgeport@seweurodrive.com
Bridgeport, New Jersey 08014
Dayton SEW-EURODRIVE INC. Tel. +1 937 335-0036
2001 West Main Street Fax +1 937 440-3799
Troy, Ohio 45373 cstroy@seweurodrive.com
Dallas SEW-EURODRIVE INC. Tel. +1 214 330-4824
3950 Platinum Way Fax +1 214 330-4724
Dallas, Texas 75237 csdallas@seweurodrive.com
Additional addresses for service in the USA provided on request!

Venezuela
Assembly Valencia SEW-EURODRIVE Venezuela S.A. Tel. +58 241 832-9804
Sales Av. Norte Sur No. 3, Galpon 84-319 Fax +58 241 838-6275
Service Zona Industrial Municipal Norte sewventas@cantv.net
Valencia, Estado Carabobo sewfinanzas@cantv.net

11/2004 59
Gearmotors \ Industrial Gear Units \ Drive Electronics \ Drive Automation \ Services

How we’re driving the world

With people who With comprehensive With uncompromising


think fast and With a worldwide With drives and controls knowledge in virtually quality that reduces the
develop the service network that is that automatically every branch of cost and complexity of
future with you. always close at hand. improve your productivity. industry today. daily operations.

SEW-EURODRIVE
Driving the world

With a global presence With innovative With online information


that offers responsive technology that solves and software updates, via
and reliable solutions. tomorrow’s problems the Internet, available
Anywhere. today. around the clock.

SEW-EURODRIVE GmbH & Co KG


P.O. Box 3023 · D-76642 Bruchsal / Germany
Phone +49 7251 75-0 · Fax +49 7251 75-1970
sew@sew-eurodrive.com
→ www.sew-eurodrive.com

Das könnte Ihnen auch gefallen