EMF2180IB-EMF2181IB Remote Maintenance v2-0 en

EDSFEW
!!!!
!
!
!
!
Communication Manual
EthernetCAN
l
EMF2180IB
Communication module

2180 communication module (EthernetCAN) 5
l 54 EDSFEW EN 4.0
5 Communication module 2180 EthernetCAN
5.1 Before you start 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Your opinion is important to us 5.11 . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Document history 5.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 General information 5.21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Technical data 5.31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 General data and operating conditions 5.31 . . . . . . . . . . . . . . . . .
5.3.2 Protective insulation 5.32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.3 Dimensions 5.33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Installation 5.41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Elements of the communication module 5.41 . . . . . . . . . . . . . . . .
5.4.2 Mechanical installation 5.42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3 Electrical installation 5.43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Commissioning 5.51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Commissioning with the system bus configurator 5.51 . . . . . . . .
5.5.2 Commissioning with the web server 5.56 . . . . . . . . . . . . . . . . . . .
5.5.3 Before switching on 5.514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4 First switchon 5.515 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Data transfer 5.61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Data transfer via CAN 5.61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 Data transfer via Ethernet 5.63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Lenze codes and CANopen objects 5.71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 Description of the codes relevant for CAN 5.74 . . . . . . . . . . . . . . .
5.7.2 Description of the CANopen objects implemented 5.716 . . . . . . . .
5.7.3 Description of the general codes 5.718 . . . . . . . . . . . . . . . . . . . . . . .
5.7.4 Description of the codes important for Ethernet 5.720 . . . . . . . . . .
5.8 Troubleshooting 5.81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.1 Signalling of the CANopen RUN LED and ERROR LED 5.81 . . . . . . .
5.9 Index 5.91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2180 communication module (EthernetCAN)
Before you start
Your opinion is important to us
5
5.1
5.1.1
l 5.11 EDSFEW EN 4.0
5.1 Before you start
I Tip!
Information and auxiliary devices related to the Lenze products
can be found in the download area at
http://www.Lenze.com
5.1.1 Your opinion is important to us
These instructions were created to the best of our knowledge and belief to
give you the best possible support for handling our product.
If you have suggestions for improvement, please email us to:
feedbackdocu@Lenze.de
Thank you for your support.
Your Lenze documentation team
5.1.2 Document history
Edition date Revised chapters Notes
04 / 2005 First edition
09 / 2012 5.5.2 Commissioning with the web server supplemented
General information
5
5.2
5.2 General information
These instructions are valid for
Communication module Type designation from hardware
version
from software
version
EthernetCAN EMF2180IB 1x 1x
These instructions are only valid together with the documentation for the
standard devices permitted for the application.
2180FEW099
Type code W 33.2180IB 1x 1x
Device series
Hardware version
Software version
The communication module can be used with the following Lenze devices:
Servo Drives 9400
Inverter Drives 8400
9300 servo inverter
9300 vector
9300 Servo PLC
ECS servo system
8200 motec motor inverter
8200 vector frequency inverter
82XX frequency inverter
Drive PLC
Terminal extension 9374
Control / display unit (EPMHXXX)
I/O system IP20 (EPMTXXX)
The communication module is used for setting parameters during remote
maintenance or programming and commissioning the usable devices:
Validity information
Identification
Application range
Features
Technical data
General data and operating conditions
5
5.3
5.3.1
5.3 Technical data
5.3.1 General data and operating conditions
Range Values
Order designation EMF2180IB
Communication media
(system)
CAN (DIN ISO 11898)
Ethernet (100 Base TX, IEEE802.3u)
Number of nodes at the CAN
bus
Max. 100
Baud rate l when communicating via CAN
20 kbit/s
50 kbit/s
125 kbit/s
250 kbit/s
500 kBit/s
1000 kbps
l when communicating via Ethernet
10 Mbit/s
100 Mbit/s
Voltage supply (external) via
separate power supply
18 30 V DC, max. 100 mA (in accordance with EN 611312)
Operating conditions Values Deviations from the standard
Climatic conditions
Storage 1 K3 to IEC/EN 6072131 10 ... + 60 C
Transport 2 K3 acc. to IEC/EN
6072132
10 ... + 70 C
Operation 3 K3 acc. to IEC/EN
6072133
0 ... + 60 C
Enclosure of attached
module
IP20
Degree of pollution 2 acc. to IEC/EN 6180051
Technical data
Protective insulation
5
5.3
5.3.2
5.3.2 Protective insulation
2180FEW001F
Terminal Type of insulation (according to EN 6180051)
4
Ethernet Functional insulation
5
CAN bus Functional insulation
6
Voltage supply No insulation
Technical data
Dimensions
5
5.3
5.3.3

5.3.3 Dimensions
2180FEW001B
a 117 mm
b 99 mm
e 22.5 mm
Installation
Elements of the communication module
5
5.4
5.4.1
5.4 Installation
5.4.1 Elements of the communication module
2180FEW001D
Fig. 5.41 Communication module EthernetCAN 2180
Pos. Name Description
4 Ethernet connection RJ45 socket
5 CAN connection SubD socket
6 Connection for voltage supply Plug connector with spring connection, 4pole
7 PE connection When fitted, the communication module is
automatically connected to the DIN rail.
The DIN rail must be connected to PE!
Pos. Colour State Description
0
(B)
Yellow Off Baud rate: 10 Mbits/s
On Baud rate: 100 Mbits/s
Blinking The IP address of the module is not assigned
yet; it is currently being detected.
1
(E)
Red See ^ 5.517 ERR LED
2
(R)
Green RUN LED
3
(P)
Green On 2180 EthernetCAN is supplied with power.
8
green on The connection to the Ethernet network is
established (LINK).
:
green On or blinking
Data are being transmitted or received
(ACTIVITY).
) Note!
Refer to the instructions on the signals provided by the ERROR
LED and RUN LED in the Troubleshooting chapter ( 5.81).
Connections
Displays
Installation
Mechanical installation
5
5.4
5.4.2

5.4.2 Mechanical installation
2181FEW002B
Fig. 5.42 Snap communication module to DIN rail
2181FEW001E
Fig. 5.43 Unlock communication module and lift off DIN rail .
Mounting
Dismounting
Installation
Electrical installation
5
5.4
5.4.3

5.4.3 Electrical installation
2180FEW008
Fig. 5.44 Communication via Ethernet and CAN
Step Activity Terminal
(see graphic)
Additional
information
1. Establish a connection to the CAN bus:
Plug the SubD plug ("EWZ0046", see
accessories) into the communication
module.
5 ^ 5.45
2. Connect the following components via
Ethernet with each other:
^ 5.47
l Communication module 4
l PC ;
l Servo Drives 9400 <
l Other Ethernet nodes
3. Connect voltage supply to the plug
connector
6 ^ 5.44
Installation steps
Installation
5
5.4
5.4.3

5.4.3.1 Voltage supply
2181FEW001G
Terminal data
Electrical connection Plug connector with spring connection
Possible connections rigid: 2.5 mm
2
(AWG 12)
flexible:
without wire end ferrule
2.5 mm
2
(AWG 12)
with wire end ferrule, without plastic sleeve
2.5 mm
2
(AWG 12)
with wire end ferrule, with plastic sleeve
2.5 mm
2
(AWG 12)
Stripping length 10 mm
( Stop!
In order to avoid damages to the pluggable terminal strips and
the contacts:
The terminal strips must be wired before plugging them in!
Pluggable terminals strips that are not assigned must be
plugged on as well.
E82ZAFX013
Terminal data
Handling of pluggable
terminal strips
Use of pluggable terminal
strip with spring connection
Installation
5
5.4
5.4.3

5.4.3.2 CAN bus connection
2180FEW001K
View Pin Assignment
1 6
5
9
1, 4, 5, 6, 8, 9
2 CANLO
3 CANGND
7 CANHI
Between CAN_LOW and CANHIGH the CAN bus has to be terminated by
resistors (120W). The SubD plug with an integrated terminating resistor
(order no. EWZ0046, not included in the scope of supply) complies with the
recommendation DS 1021 of CiA.
L
EW
Z0046
OFF
ON
O
F
F
O
N
ON
OFF

OUT IN IN IN
On Off On 120 120 120
L
EWZ0046
L
EWZ0046
L
EWZ0046
2181FEW004
We recommend the use of CAN cables in accordance with ISO 118982:
CAN cable in accordance with ISO 118982
Cable type Paired with shielding
Impedance 120 W (95 ... 140 W)
Cable resistance/crosssection
Cable length 300 m 70 mW/m / 0.25 0.34 mm
2
(AWG22)
Cable length 301 1000 m 40 mW/m / 0.5 mm
2
(AWG20)
Signal propagation delay 5 ns/m
Assignment of the SubD plug
connector
Specification of the
transmission cable
Installation
5
5.4
5.4.3
It is absolutely necessary to comply with the permissible cable lengths.
1. Check the compliance with the total cable length in Tab. 5.41.
The total cable length is determined by the baud rate.
Baud rate [kbit/s] Max. bus length [m]
20 3600
50 1400
125 550
250 250
500 110
1000 20
Tab. 5.41 Total cable length
2. Check the compliance with the segment cable length in Tab. 5.42.
The segment cable length is determined by the cable crosssection used and
by the number of nodes. Without repeaters the segment cable length
corresponds to the total cable length.
Nodes
Cable crosssection
0.25 mm
2
0.5 mm
2
0.75 mm
2
1.0 mm
2
2 240 m 430 m 650 m 940 m
5 230 m 420 m 640 m 920 m
10 230 m 410 m 620 m 900 m
20 210 m 390 m 580 m 850 m
32 200 m 360 m 550 m 800 m
63 170 m 310 m 470 m 690 m
100 150 m 270 m 410 m 600 m
Tab. 5.42 Segment cable length
3. Compare both values.
If the value given in Tab. 5.42 is smaller than the required total cable length
from Tab. 5.41, repeaters must be used. Repeaters divide the total cable
length into segments.
Bus cable length
Installation
5
5.4
5.4.3

5.4.3.3 Connecting the Ethernet cable
2181FEW004A
) Note!
Only use common prefabricated cables (according to ISO/IEC
11801 or EN 50173) of category CAT5e.
Ethernet cable specifications
Ethernet standard Standard Ethernet (according to IEEE 802.3), 100base TX (fast
Ethernet)
Cable type S/FTP (Screened Foiled Twisted Pair), ISO/IEC 11801 or
EN 50173, CAT 5e
Damping 23.2 dB (at 100 MHz and per 100 m)
Crosstalk damping 24 dB (at 100 MHz and per 100 m)
Return loss 10 dB (per 100 m)
Surge impedance
100 W
100BaseTX CrossOver Cable 100BaseTX Standard Patch Cable
1 Tx+ Tx+ 1
2 Tx- Tx- 2
3 Rx+ Rx+ 3
4 4
5 5
6 Rx- Rx- 6
7 7
8 8
1 Tx+ Tx+ 1
2 Tx- Tx- 2
3 Rx+ Rx+ 3
4 4
5 5
6 Rx- Rx- 6
7 7
8 8
E94YCEI002
The "100BaseTX CrossOver Cable" is used for direct coupling of PC and
communication module.
The "100BaseTX Standard Patch Cable" is used in conjunction with
hubs and switches.
transmission cable
Pin assignment
Use of cables
Commissioning
Commissioning with the system bus configurator
5
5.5
5.5.1
5.5 Commissioning
5.5.1 Commissioning with the system bus configurator
5.5.1.1 Installing the software
The following minimum requirements of hardware and software must be
met to work with the communication module:
MicrosoftR WindowsR 2000/XP
IBMRcompatible PC with IntelRPentiumR266 processor or higher
128 MB main memory with Windows2000/XP
The following Lenze programs allow for a communication via the
communication module :
Drive Server
Global Drive Control (GDC version 4.7 or higher)
Global Drive Loader
Global Drive PLC Developer Studio (DDS version 1.4 or higher)
Lforce Engineer
) Note!
One of the programs mentioned offer alternative
communication paths for CAN. In this case, please always select
the communication path "OPC".
System requirements
Available Lenze programs
Commissioning
5
5.5
5.5.1
) Note!
The driver installation under Windows 2000/XP requires
administrator rights!
For a perfect operation of the communication module, install the "CAN"
communication software with a version 2.0. It is included in the Lenze
programs and is loaded on the PC during the installation.
) Note!
The following program version do not contain the required
minimum version of the CAN communication software:
Drive Server, version 1.1
Global Drive Control, version 4.7
Global Drive Loader, version 2.2
Global Drive PLC Developer Studio, version 2.2
The current communication software can be found in the
download area of the Lenze homepage
For this purpose proceed the following steps:
Save the data of the Lenze homepage to your local hard disk.
Install the Lenze programs that will communicate via the
2180 communication module.
Install the communication software by following the
instructions of the installation program.
) Note!
The current version of the CAN communication software is
displayed in the information dialogue of the system bus
configurator and other Lenze programs.
The Lenze system bus configurator for the comfortable configuration of the
communication modules used is installed together with the CAN
communication software.
Installing the required driver
System bus configurator
Commissioning
5
5.5
5.5.1

5.5.1.2 Configuring the communication module
Before the Lenze tools can communicate via communication module, it
must be configured accordingly.
To open the system bus configurator, select the following in the start menu
ProgramsWLenzeWCommunicationWSystem bus configurator.
The following parameters must be set:
CAN parameters
These are saved in the communication module and contain specific
data for the CAN bus, as for instance, baud rate, parameter data
channel or timeout.
Parameters for access to the communication module
The communication module is an Ethernet node. Each Ethernet node
has two addresses A MAC address and IP address.
The MAC address serves to unambiguously identify a device worldwide.
Observe the corresponding entry of the MAC address in the relevant
nameplate. The MAC address is firmly burnt into the device and cannot
be changed. If an Ethernet connection to the communication module
already exists, the MAC address can be read out online.
The IP address is a logical address which must be adapted to the
corresponding Ethernet network.
Commissioning
5
5.5
5.5.1
1. Press the button "Add" and select the 2180 communication module.
2. Select the communication module from the list in the system bus
configurator.
3. Select the index card "Settings".
4. Enter the CAN parameters.
This function extension is available from version 1.7 onwards!
In order to be able to give the communication module an alphanumeric
name, use the possible setting
via code C1216 ( 5.710) or
via the web interface:
2180FEW016
5. Enter the MAC address of the nameplate or detect the MAC address
online.
6. Enter the desired IP address and transfer this online to the
communication module. This then carries out a reset which may last a
few seconds (observe LEDs!).
7. When the communication module is ready again for operation, change
to the index card "General".
8. Press the button "Diagnostics". Then, a connection to the
communication module is tried to be established. First, it is compared
whether the configured CAN parameters are identical with those in the
device. If not, an adjustment is carried out.
9. Afterwards the CAN bus can be searched for connected nodes. Confirm
the safety note with "Yes" or select "No" to interrupt the diagnostics.
Steps to be taken for
configuring the
communication module
Commissioning
5
5.5
5.5.1
When the communication module succeeded in communicating with the
corresponding bus nodes, the system bus node addresses of the bus nodes
found are listed in the field "Device status".
If the communication module is not able to communicate with the bus
nodes, an error message is displayed.
The communication module answers with its CAN address or with "0" if no
address exists (dependent on C00350). The data telegrams for
communicating with the communication module itself, however, are not
visible on the CAN bus.
) Note!
Additional information about the configuration of the
communication module can be found in the online help of the
system bus configurator.
If the configuration of a communication module is successful, the Lenze
tools can use it for communication.
Only the selection of the bus system used is performed in the Lenze tools, all
system busspecific settings and the selection of the communication
module are carried out exclusively via the system bus configurator.
) Note!
While some of the older program versions of the Lenze tools still
offer setting options for interrupt and I/O address, they are
meaningless in the context of the communication module 2180.
After completing the
configuration
Commissioning
Commissioning with the web server
5
5.5
5.5.2

5.5.2 Commissioning with the web server
The commissioning via the integrated web server is an alternative to the
commissioning with the system bus configurator.
The integrated web server enables the device to be configured by a simple
web browser.
When the DHCP function is activated, the DHCP server automatically assigns
an IP address to the device.
If an invalid combination of IP address and subnet mask is detected, an
error message is output via the website:
2180FEW019
In this case, both values (IP address / subnet mask) will not be saved in
the EEPROM of the communication module.
The gateway IP will only be accepted as valid if it is inside the own
network (exception: Gateway IP: 0.0.0.0).
Commissioning
5
5.5
5.5.2
This function is valid for versions < 1.7!
Prerequisite for commissioning via web server:
First, the IP address of the device must be assigned by the system bus
configurator.
The IP address must be located in the range that can be addressed by
the connected PC.
If one of the two prerequisites is not met, the IP address must be
reconfigured using the system bus configurator:
2180FEW017
Commissioning
5
5.5
5.5.2
) Note!
The Lenze setting of the IP address is "0.0.0.0". With this (invalid)
IP address the communication module automatically searches
during the start an own IP address in the range 169.254.xxx.xxx
according to APIPA.
Start your web browser and then enter as URL the IP address of the 2180
communication module:
2180FEW010
Fig. 5.51 Entering the IP address (instead of "xxx.xxx.xxx.xxx")
The homepage of the communication module appears. You can perform all
additional configurations from this location.
2180FEW011
Assigning a fixed IP address
Commissioning
5
5.5
5.5.2
The 2180 communication module can also dynamically obtain its IP address
from the DHCP server with the help of the web server using the
corresponding configuration.
2180FEW013
) Note!
Since the procedure for the dynamically assigned IP address
can seldom be found in industrial environments, its use is not
recommended.
Additional information for the configuration of an Ethernet
network can be found in the Lenze Ethernet Communication
Manual.
Assigning a dynamic IP
address
Commissioning
5
5.5
5.5.2
DHCP can be activated via code C1228 ( 5.713):
2180FEW018
Up to now, this was only possible via a check box on the TCP/IP Settings
web page. A static IP configuration already configured continues to exist and
after DHCP is deactivated plus mains switching or reset it can still be used.
Commissioning
5
5.5
5.5.2
All settings that can be performed under the category "Configuration" are
protected by a combination of user name and password. The default setting
at delivery is as follows:
User name: Lenze
Password: Lenze
The user name and the password can be changed any number of times and
are casesensitive.
Submit serves to store the changed data in the EEPROM of the 2180
communication module (EthernetCAN). They will be active after the next
restart.
2180FEW012
) Note!
This page is only used for Lenzeinternal purposes and cannot be
accessed freely.
Entering user name and
password
Firmware update
("FW update")
Commissioning
5
5.5
5.5.2
The following statistics are displayed:
Current transfer rate (10/100 Mbit/s)
Transmission mode (half/full duplex)
MACID of the 2180 communication module
Static parameter of the Ethernet connection
2180FEW014
Displaying Ethernet statistics
Commissioning
5
5.5
5.5.2
After starting the 2180 communication module, alarms and events are
registered.
The user can display the contents of the list.
Events are classified by severity into
Error
Warning
Info
2180FEW015
The list also contains the time when the alarm or the event occurred.
) Note!
The list is deleted with every restart of the communication
module.
Date and time are only correct if a time server is configured.
Without configuration of the time server, the time count
always starts with the restart of the communication module
on 01.01.1970 at 0.00h.
Displaying alarms and events
Commissioning
Before switching on
5
5.5
5.5.3

5.5.3 Before switching on
( Stop!
Prior to switching on the mains voltage, check the wiring for
completeness, shortcircuit and earth fault.
The device is equipped with the following functions:
Automatic address assignment
Automatic detection of the baud rate
Both functions are used to prevent malfunctions in operation due to
incorrectly set user addresses and baud rate.
) Note!
In default setting these functions are not activated.
Please refer to the related instructions on the codes
C0350: "General address assignment" ( 5.74)
C0351: "Set baud rate" ( 5.75)
Automatic address
assignment and automatic
detection of the baud rate
Commissioning
First switchon
5
5.5
5.5.4

5.5.4 First switchon
2180FEW001H
Fig. 5.52 Signalling on the front of the communication module
0
(B)
Yellow Off Baud rate: 10 Mbits/s
On Baud rate: 100 Mbits/s
Blinking The IP address of the module is not assigned
yet; it is currently being detected.
1
(E)
Red See ^ 5.517 ERR LED
2
(R)
Green RUN LED
3
(P)
Green On 2180 EthernetCAN is supplied with power.
8
green on The connection to the Ethernet network is
established (LINK).
:
green On or blinking
Data are being transmitted or received
(ACTIVITY).
Signalling
Commissioning
First switchon
5
5.5
5.5.4

1. The initialisation phase of the periphery starts:
LED 3 (voltage supply, green) is lit.
2. After the initialisation of the CAN controller:
LED 2 (RUNLED, green) is blinking.
3. Ethernet connection is established:
LED 8 is lit.
LED 0 displays whether the baud rate of the Ethernet connection
amounts to 10Mbits/s or 100 Mbits/s.
If the LED 0 is blinking, the communication module is detecting its IP
address. The communication via Ethernet is only then possible if this
process is completed.
The device is now ready for operation.
Signalling sequence after
switch on
Commissioning
First switchon
5
5.5
5.5.4

Status display (LED) Explanation
Connection status to the bus with the following signalling:
off No connection to the master
green
CANopen status ("S")
red
CANopen fault ("F")
Constant red
F: bus off
Flickering Automatic detection of the baud rate is active
Green blinking every 0.2 s
S: preoperational, F: none
Red blinking 1 x, 1 s OFF
S: preoperational, F: warning limit reached
S: preoperational, F: node guard event
Constant green
Z: operational, F: no errors
Constant green
Z: operational, error: warning limit reached
Constant green
Z: operational, F: node guarding event
Constant green
Z: operational, F: sync message error
Green blinking every 1 s
Z: stopped, F: no errors
S: stopped, F: warning limit reached
S: stopped, F: node guard event
Tab. 5.51 Signalling according to DR3033
Signalling acc. to DR3033
Data transfer
Data transfer via CAN
5
5.6
5.6.1
5.6 Data transfer
5.6.1 Data transfer via CAN
2180FEW008
Master and drive controller communicate with each other by exchanging
data messages via the CAN bus. The data area in the data message contains
either network management data, parameter data or process data.
In the drive controller, different communication channels are allocated to
the parameter data and process data.
The communication module is suitable (apart from the transfer of IEC61131
programs and application data, e.g. curve data) only for the transfer of
parameter data.
Parameter data (SDO, Service Data Objects) Parameter data channel
These are e. g.
l Operating parameters
l Diagnostics information
l Motor data
As a rule the transfer of parameters is not as
timecritical as the transfer of process data.
l Provide access to all Lenze codes and all
CANopen indices.
l Changes to parameters are normally stored
automatically in the drive controller (note
C0003).
The structure of the CAN messages is described in the CAN communication
manual.
Data transfer
5
5.6
5.6.1
) Note!
For the value range of the Lenze code, please refer to the
operating instructions for the drive controller (see Code list).
When communication modules are used, the properties and the behaviour
of a drive controller integrated into the network can be changed by a higher
level master (e. g. a PLC).
The parameters to be changed are contained in the codes of Lenze drive
controllers.
The drive controller codes are addressed using the index on access via the
communication module .
The index for the Lenze code number is in the range between 16576 (40C0
hex
)
and 24575 (5FFF
hex
).
Conversion formula:
Index [dec] = 24575 Lenze code number
dec hex
Index = 24575 Lenze code Index
hex
= 5FFF
hex
(Lenze code)
hex
Index = 24575 1 = 24574 Index
hex
= 5FFF
hex
1 = 5FFE
hex
The communication module has two parameter data channels which are
both activated in the Lenze setting.
) Note!
In order to establish the compatibility with CANopen, the second
parameter data channel must be switched off via code C1200,
see ( 5.78).
Access to the drive controller
codes
Indexing of codes using the
example
C0001 (operating mode)
CANopen parameter channels
Data transfer
Data transfer via Ethernet
5
5.6
5.6.2

5.6.2 Data transfer via Ethernet
The communication between PC and the communication module 2180 is
carried out using a proprietary protocol that is based on TCP/IP. The port
number 22080 is used for the communication module.
The port number may have to be cleared if a firewall or something similar is
used.
Port 3677 is used to search for communication modules.
Port 80 is used to operate the web server.
I Tip!
The search via Ethernet is only possible within one network. The
telegrams are not transmitted via routers.
Lenze codes and CANopen objects
5
5.7
5.7 Lenze codes and CANopen objects
The behaviour of the communication module is defined by setting
parameters for (Lenze) codes. These codes are exchanged as part of a
message via the CAN bus.
In the following table you will find an overview of codes relevant for the
communication module and the CAN objects implemented. Please note the
references to additional information.
) Note!
Convention for differentiating between the implemented
CANopen indices and Lenze codes:
CANopen index: I + (index)
Lenze code: C + (code number)
5
5.7

Sample of a code table
Code Name Index:
Subcode Lenze Values Access Data type
RSP PS transfer CANopen:
Meaning
Headers Meaning
Code Number of the parameter Cxxxxx. Name: (Lenze) "code"
Name Name of the parameter (display text in the Engineer and in the keypad)
Index Information on addressing the code in hexadecimal and decimal notation
(decimal value in brackets)
Leading
columns
Meaning
Subcode Number of the subcode
Lenze Lenze setting ("default setting) of the code
g Display code
The configuration of the code is not possible.
Values minimum value [smallest increment/unit] maximum value
For a display code, the displayed values are given.
Access ro: The parameter can only be read (display code)
rw: The parameter can be written.
Data type l FIX32 32 bit value with sign; decimal with 4 decimal positions
l S8 8 bit value with sign
l U8 8 bit value without sign
l VS Visible string, string with given length
Footer Meaning
RSP The parameter can only be changed when the controller is inhibited (CINH) () /
not possible ().
PS transfer When the "Download parameter set" command is executed, the parameter is
transferred to the controller () / not transferred ().
CANopen The reference to the corresponding CANopen object (according to CANopen
specification DS301V402) is given () / not given ().
How to read the code table
5
5.7

Code Subcode Index [hex] Name see
C0002 5FFD Parameter set management ^ 5.718
C0093 5FA2 Type ^ 5.718
C0099 5F9C Software version ^ 5.718
C0150 5F69 Drive controller status word ^ 5.718
C0200 5F37 Software manufacturers product
code
^ 5.719
C0202 1
2
3
4
5F35 MPC ^ 5.719
C0350 5EA1 CAN node address ^ 5.74
C0351 5EA0 CAN baud rate ^ 5.75
C0358 5E99 Reset node ^ 5.75
C0359 5E98 CAN status ^ 5.76
C0360 1
2
5E97 Telegram counter ^ 5.77
C0361 1
2
5E96 Bus load ^ 5.77
C1200 5B4F Parameter data channel operating
mode
^ 5.78
C1201 5B4E Communication timeout (CAN) ^ 5.78
C1202 5B4D Time limit for node search ^ 5.78
C1203 5B4C Repeat tests ^ 5.79
C1209 5B46 Detection of the baud rate ^ 5.79
C1210 5B45 IP address ^ 5.720
C1211 5B44 Subnet mask ^ 5.721
C1214 5B41 MACID ^ 5.722
C1215 5B40 Time exceeded during automatic baud
rate detection
^ 5.79
C1216 5B3F Userspecific device name ^ 5.710
C1217 5B3E Cycle time of CAN device monitoring ^ 5.710
C1219 5B3C Activation of CAN device monitoring ^ 5.711
C1220 5B3B CAN device monitoring ^ 5.712
C1224 5B37 Gateway ^ 5.722
C1227 5B34 Delay time for search telegrams ^ 5.713
C1228 5B33 Activation DHCP ^ 5.713
C1229 5B32 Activation of IP settings, device reset ^ 5.714
C1230 5B31 IP address ^ 5.714
C1231 5B30 Subnet mask ^ 5.715
C1232 5B2F Default gateway ^ 5.715
Index [
hex
] Subindex Name See
I1000 0 Device type ^ 5.716
I1001 0 Error register ^ 5.716
I1017 0 Producer heartbeat time ^ 5.716
I1018 0...4 Identity object ^ 5.717
Overview
CANopen objects
implemented
Description of the codes relevant for CAN
5
5.7
5.7.1

5.7.1 Description of the codes relevant for CAN
Code
C0350
Name
CAN node address
Index: 0x5EA1 (24225)
0 1 [1] 63 (127) rw I32
The node address can be set via the CAN bus using the code C0350.
If zero is used as the address, the communication module does not have a
dedicated node address. It can then not be addressed from the CAN bus (no
parameter setting, node guarding etc.), but only serves as a diallingin
feature for reading parameters via the CAN bus.
If the communication module should have an address, check, after the baud
rate has been detected, whether this address is still free. Then, the
implemented CANopen object 1000 is tried to be read. If another node
already has this address, another free address is selected automatically.
) Note!
Node addresses in the range of 64 ... 127 can only be assigned if
the code C1200 is set to the value"0" (CANopen conformity).
Changes to the setting are applied after
Reconnection to the mains
"Reset node" or "Reset communication" via the bus system
"Reset node" using the code C0358
C0350:
CAN node address
5
5.7
5.7.1
Code
C0351
Name
CAN baud rate
Index: 0x5EA0 (24224)
0 0 500 kbit/s rw I32
1 250 kbit/s
2 125 kbit/s
3 50 kbit/s
4 1000 kbps
5 20000 kbps
16 Automatic detection
The baud rate over the CAN bus can be set using this code.
Changes to the setting are applied after:
A "reset node" command via the bus system
A reset node using the code C0358
Prior to accessing the CAN bus, the baud rate used is determined by the
communication module and compared with the baud rate configured.
If the two values are different, the baud rate determined is used. The baud
rate detected by the communication module can be read using code C1209.
If there is no data traffic on the CAN bus, the baud rate cannot be
determined. The subsequent behaviour of the communication module
depends on the selection configured in code C0351:
Selection 0 ... 5
After a timeout that can be configured using code C1215, the CAN bus
is accessed with the baud rate configured.
Selection 16 (automatic detection of the baud rate)
The communication module does not access the bus until a baud rate
can be detected.
Code
C0358
Name
Reset node
Index: 0x5E99 (24217)
0 0: No function rw I32
1: CAN reset
After a reset any changes to communication parameters such as baud rate
or node address are applied.
Entries with new baud rates or changes to the node address only become
valid after a node reset.
A node reset can be performed by:
Reset node via the bus system
Reset node using code C0358
C0351:
Set baud rate
C0358:
Reset node
5
5.7
5.7.1
Code
C0359
Name
Diagnostics of the bus status
Index: 0x5E98 (24216)
g
0: Operational ro I32
1: PreOperational
2: Warning
3: BusOff
4: Stopped
This code displays the current operating status of the CAN controller. Here
a differentiation is made between 4 states:
Selection 0: Operational
In this state the bus system is fully functional.
Selection 1: PreOperational
In this state only parameters (codes) can be transferred via the bus system.
It is not possible to exchange process data. To change to the "Operational"
state a network management message must be output on the bus.
A state change from "Preoperational" to "Operational" can be made with
the following actions:
A drive is defined as the master using code C0352. When connecting
to the mains an automatic state change for the entire drive system is
performed after the defined bootup time C0356/1.
Using code C0358 reset node (prerequisite: C0352 = 1).
Using the binary reset node input signal that can be set, e. g. using
the code C0364 via a terminal given an appropriate configuration
(prerequisite: C0352 = 1).
A network management message from a CAN master.
Selection 2: Warning
Error messages have been received if the state is "Warning". The CAN node
is now only passive; no more data are sent from the drive controller.
The reason for this situation can be:
A missing bus terminator
Inadequate shielding
Potential differences at the ground connection for the control
electronics
An excessively high bus load
CAN node is not connected to the bus
C0359:
Diagnostics of the bus status
5
5.7
5.7.1
Selection 3: Bus Off
The frequency of the erroneous messages has resulted in the CAN node
decoupling itself from the bus. It is possible to switch to the
"PreOperational" state with:
A trip reset
A reset node
Selection 4: Stopped
Only NMT telegrams can be received.
The state can be changed to "PreOperational" by:
Reset node via the code C0358
Code
C0360
Name
Diagnostics of the telegram counter
Index: 0x5E97 (24215)
1, 2 (see table below)
g
0 [1] 4294967295 ro I32
Subcode Meaning
Messages
l Message counter (number of messages)
l Counter value > 4294967295: Start again at 0
1 Message OUT all sent
2 Message IN all received
All CAN telegrams transmitted and received of this node are counted.
The counters have 32 bits, i. e. when a value of 4294967295 is exceeded, the
counting process starts again at 0.
Code
C0361
Name
Diagnostics of the bus load
Index: 0x5E96 (24214)
g
0 [1 %] 100 ro I32
Using this code the percentage total bus load can be determined. Erroneous
messages are not taken into account here.
) Note!
The bus load for all devices involved should not exceed 80 %.
If other devices, e. g. decentralised inputs and outputs are
connected, these messages are also to be taken into account.
C0360:
Diagnostics of the telegram
counter
C0361:
Diagnostics of the bus load
5
5.7
5.7.1
Code
C1200
Name
Operating mode parameter data channel
Index: 0x5B4F (23375)
2 0 [1] 2 rw I32
This code indicates which of the two parameter data channels is used to
communicate with other nodes. The unused parameter data channels can
be switched off, if required.
All Lenze controllers have two parameter data channels with different
addressing. The address of the parameter channel2 is calculated as follows:
Address of parameter data channel 2 =
Address of parameter data channel 1 + offset 64
Selection Accessible address range Active parameter data channels
0 1...127 SDO 1
1 1 ... 63 SDO1 / SDO2
2 65 ... 127 SDO1 / SDO2
) Note!
The selection 0 means that the bus is operating in compliance
with CANopen and there is no limitation on the address space.
In this case, the parameter data channel SDO2 is inactive.
Code
C1201
Name
Communication timeout (CAN)
Index: 0x5B4E (23374)
1500 0 [1 ms] 10000 rw I32
The time set defines the time frame within which a CAN node must respond
to a request.
If there is no response of the node, the requesting module assumes that the
node is not available.
Code
C1202
Name
Time limit for node search
Index: 0x5B4D (23373)
1000 0 [1 ms] 10000 rw I32
For node search, the time set is regularly maintained. It must be selected
high enough to enable the nodes to have enough time to respond.
Otherwise, a too high value delays the search.
) Note!
If required, the settings in C1202 must be adapted if the delay
time for search telegrams increased with code C1227.
C1200:
Parameter data channel
operating mode
C1201:
Communication timeout
(CAN)
C1202:
5
5.7
5.7.1
Code
C1203
Name
Repeat tests
Index: 0x5B4C (23372)
0 0 [1] 10 rw I32
The value to be set in code C1203 indicates the number of repetitions of
those CAN telegrams which have not reached the receiver.
The condition for this functionality is the activation of the device
identification with code C1219 ( 5.711).
The Lenze setting of the repeat tests was changed from 1 to 0 in order to
obtain a corresponding return value from the comunication module if a bus
node is not available ("DEVICE_NOT_PRESENT").
Code
C1209
Name
Read out baud rate
Index: 0x5B46 (23366)
g
0
1
2
3
4
16
500 kbit/s
250 kbit/s
125 kbit/s
50 kbit/s
1000 kbps
nothing
detected
ro I32
Code C1209 can be used to determine which transfer rate was detected on
the CAN bus.
When "16" is indicated, there is no data traffic on the CAN bus.
Code
C1215
Name
Timeout
Index: 0x5B40 (23360)
1000 0 [1] 60000 rw I32
By defining a timeout in code C1215, the baud rate (display with code
C1209) on the CAN bus can be detected.
The baud rate is not checked if the value configured in code C1215 is set to
zero.
When the timeout configured in code C1215 elapses, the CAN bus is
accessed (for further information and limitations: see description of code
C0351).
C1203:
Repeat tests
C1209:
Read out baud rate
C1215:
Timeout (automatic baud
rate detection)
5
5.7
5.7.1
Code
C1216
Name
Userspecific device name
Index: 0x5B3F (23359)
<leer> see description rw VS
The device name can be defined with maximally 25 characters by the user.
When the name is created or changed, the following characters are possible
(deviating characters will be replaced by a dot):
Letters: A ... Z or a ... z
Numbers: 0 ... 9
Special characters: Dot and hyphen
The Gertename is stored safe against mains failure in the communication
module.
) Note!
The automatic transfer of the device name to a DNS server does
not take place.
When the Lenze setting is loaded (C0002), the device name is not
reset or changed.
I Tip!
This code can also be configured via the gateway configuration
website of this communication module.
Code
C1217
Name
Cycle time of CAN device monitoring
Index: 0x5B3E (23358)
5000 1000 [ms] 30000 rw U32
This code serves to the set the cycle time for the CAN device monitoring
(C1220).
I Tip!
website of the 2180 communication module (EthernetCAN).
C1216:
Userspecific device name
C1217:
Cycle time of CAN device
monitoring
5
5.7
5.7.1
Code
C1219
Name
Activation of CAN device monitoring
Index: 0x5B3C (23356)
1 0: not activated
1: activated
rw U32
This code serves to activate the device monitoring.
The activated device monitoring enables the detection of bus nodes with
disturbed bus communication.
I Tip!
website of the 2180 communication module (EthernetCAN).
C1219: Activation of CAN
device monitoring
5
5.7
5.7.1
Code
C1220
Name
CAN device monitoring
Index: 0x5B3B (23355)
0 0 0 [1] 60000 rw U8
1 ... 4 (see table ) 0 0 [1] 60000 rw U8
This code serves to
activate the CAN device monitoring.
detect the CAN communication disturbed for each bus node and record
it in a bit mask when the CAN device monitoring is activated.
Activation of the CAN device monitoring
Subcode Meaning
0 Activation of the CAN device monitoring
l 0: not activated
l 1: activated
Recording disturbed bus nodes
For this purpose, the code contains a bit mask in its subcodes 1 ... 4 in which
every bus node (maximum number: 127) with disturbed bus
communication or when being missing is recorded by the value "1".
#The status bit immediately changes to the "0" status when the
communication of the bus node has been reestablished.#
Subcode Node mask
MSB LSB
1 31 ... ... 0
2 63 ... ... 32
3 95 ... ... 64
4 127 ... ... 96
I Tip!
For test purposes, the bit mask can be described by the user.
The values written in C1220 are accepted at the end of the
cycle time of the CAN device monitoring (C1217).
In the Engineer, we recommend to switch over to
hexadecimal view.
C1220: CAN device
monitoring
5
5.7
5.7.1
Code
C1227
Name
Delay time for search telegrams
Index: 0x5B34 (23348)
0 0 [1 ms] 100 rw I32
Selection Meaning
0 Quickest possible search
1 ... 10 Delay time 1 ms
... ...
... ...
90...100 Delay time 90 ms
Searching the CAN bus during the start of a PC program can lead to faults if
a bus is heavily loaded. In order to prevent this, a delay time between the
transmission telegrams can be set. This, however, leads to an increase of the
total search time. If required, C1202 must be adapted accordingly.
Code
C1228
Name
Activation DHCP
Index: 0x5B33 (23347)
0 0: not activated
1: activated
rw U32
This code enables the access to the CAN bus system via DHCP.
The settings of this codes will be valid
after switching the mains of the communication module or
after resetting the communication module,
see C1229 ( 5.714), value "2" or "3".
The parameter setting of this code is stored immediately safe against mains
failure in the communication module.
C1227:
Delay time for search
telegrams
C1228: Activation of DHCP
5
5.7
5.7.1
Code
C1229
Name
Activation of IP settings, device reset
Index: 0x5B32 (23346)
0 0 [1] 4 rw U32
The code
stores the IP adress, the network mask and the gateway address safe
against mains failure.
executes a device reset.
enables the combination of the two actions mentioned first.
Values Meaning INFO
0 No function
1 Save IP settings The IP address, the network mask and the gateway
address are stored safe against mains failure in the
communication module.
2 Device reset Reset of the communication module
3 Saving IP settings and device
reset
First the IP adress, the network mask and the
gateway address are stored.
The a device reset is executed.
I Tip!
The separate storage safe against mains failure of the IP settings
can be achieved by writing subcode 4 of the following codes:
IP address: C1210 ( 5.720)
Network mask: C1211 ( 5.721)
Gateway address: C1224 ( 5.722)
Code
C1230
Name
IP address
Index: 0x5B31 (23345)
g
0 [1] 60000 ro U32
This code shows the currently active IP address.
I Tip!
An IP address changed with code C1210 ( 5.720) will only be
active after mains switching. Up to then, the active IP address
differs from the configured IP address.
C1229: Activation of IP
settings, device reset
C1230: IP address
5
5.7
5.7.1
Code
C1231
Name
Subnet mask
Index: 0x5B30 (23344)
g
0 [1] 60000 ro U32
This code shows the currently active network mask.
I Tip!
A network mask changed with code C1211 ( 5.721) will only
be active after mains switching. Up to then, the active network
mask differs from the configured network mask.
Code
C1232
Name
Default gateway
Index: 0x5B2F (23343)
g
0 [1] 60000 ro U32
This code shows the currently active gateway address.
I Tip!
A gateway address changed with code C1224 ( 5.722) will
only be active after mains switching. Up to then, the active
gateway address differs from the configured gateway address.
C1231:
Subnet mask
C1232:
Default gateway
Description of the CANopen objects implemented
5
5.7
5.7.2

5.7.2 Description of the CANopen objects implemented
I1000: Device type
Index
1000hex
Name
Device type
Subindex Default
setting
Values Access Data type
0 0 ... 2
32
1 ro U32
The CANopen object I1000 indicates the device profile for this device. It is
also possible to include additional information here that is defined in the
device profile itself. If a specific device profile is not used, the content is
"0x0000".
Data telegram assignment
Byte 8 Byte 7 Byte 6 Byte 5
U32
Device profile number Additional information
Reading the error register
Index [
hex
] Subindex Name Data type Value range Rights
I1001 0 Error register U8 0...255 ro
Error status for the following bit assignment in the data byte (U8):
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Error status
0 0 0 0 0 0 0 0 No error
0 0 0 0 0 0 0 1 Error in the
0 0 0 1 0 0 0 1 Communication error
Index [
hex
I1017 Producer heartbeat
time
U32 U 16 rw
The heartbeat message is sent cyclically by the heartbeat generator
(producer) to one or more recipients (consumers).
After configuring the heartbeat producer time, the heartbeat protocol starts
at the transition from the NMT state INITIALISATION to the NMT state
PREOPERATIONAL (if predefined value > 0).
) Note!
Unlike "node / life guarding" monitoring, the heartbeat protocol
does not contain a Remote Transmit Request" (RTR).
It is therefore not necessary for the recipient to answer after a
heartbeat.
I1001
hex
:
Error register
I1017
hex
:
Producer heartbeat time
5
5.7
5.7.2
I1018: Module device description
Entry of vendor ID
Index [
hex
] Subindex Name Data type Value range Authorisati
on
I1018 0 ... 4 Module device
description
Identity Modulespecific ro
Subindices
Subindex Meaning
0 Highest subindex
1 Vendor ID = ID assigned to Lenze by the organisation "CIA"
2 Product code
3 Revision number
4 Serial number
Description of the general codes
5
5.7
5.7.3

5.7.3 Description of the general codes
Code
C00002
Name
Device commands
Index: 0x5FFD (24573)
0 0, 1 rw I32
RSP PS transfer PLCSTOP CANopen:
C0002 shows the status of the device command executed last. C00150 can
be used to enquire the current status of the device control.
Values
(extract)
Designation Info
0 Load Def. Load Lenze setting
l Only possible with controller inhibit and
stopped user program.
1 Load PS Load parameter set
The parameter set stored in the memory
module is loaded
l Only possible with controller inhibit and
stopped user program.
Code
C0093
Name
Type
Index: 0x5FA2 (24482)
g
ro FIX32
The display for communication module 2180 is "21800000".
Code
C0099
Name
Software version
Index: 0x5F9C (24476)
g
x.y
(x: major version, y: index)
ro FIX32
Code
C0150
Name
CAN node address
Index: 0x5F69 (24425)
g
ro B16
The binary interpretation of the displayed decimal value reflects the bit
statuses of the status word:
Bit 0: Ready for operation
Bit 1: Dialup connection is available
Bit 2: Internal error
C0002 (extract):
Device commands
C0093:
Device type
C0099:
Software version
C0150:
Status word
5
5.7
5.7.3
Code
C0200
Name
Software manufacturers product code
Index: 0x5F37 (24375)
g
ro VS
During initialisation of the module it is determined which device is
connected as a user based on the manufacturers product code.
Value displayed for the communication module 2180:
"33S2180F_10000".
Code
C0202
Name
EKZn
Index: 0x5F35 (24373)
1 ... 4
g
ro FIX32
The corresponding octet of the manufacturers product code (MPC) is
displayed dependent upon the subcode digit (n=1...4).
C0200:
Software ID
C0202:
EKZn
Description of the codes important for Ethernet
5
5.7
5.7.4

5.7.4 Description of the codes important for Ethernet
Code
C1210
Name
IP address
Index: 0x5B45 (23365)
0 0 [1] 255 rw FIX32
The IP address is the identification number of a node (or a device) in the
network. Every network node receives a unique address in the network.
Compared to the MACID, the IP address is a logic address that can be
changed via software.
) Note!
The IP adress 0.0.0.0 is set as standard.
When the device is started, a free device address is searched in
the 169.254.xxx.xxx subnet according to the APIPA system.
The IP addresses always consist of 4 octets (4 x 2
8
). To make the octets more
readable, they are divided by periods (e.g. 128.133.10.123).
The first octet determines the network class. The network class specifies the
number of available hosts in a network.
Each octet is mapped on a subcode.
Class IP address classes Maximum number of hosts
a 01.x.x.x 126.x.x.x 16.777.214
B 128.x.x.x 191.x.x.x 65.534
C 192.x.x.x 223.x.x.x 254
"x": complete octet
After the codes C1210 and/or C1211 have been changed, the combination
of IP address and subnet mask is checked for validity.
Wenn eine Ungltigkeit vorliegen sollte, wird das Gateway auf die
IPAdresse 0.0.0.0 gesetzt und DHCP auf das dynamische Zuweisen der
IPAdresse gestellt.
C1210:
IP address
5
5.7
5.7.4
Code
C1211
Name
Subnet mask
Index: 0x5B4D (23373)
1 ... 4 0 0 [1] 255 rw FIX32
The IP address, see C1210 ( 5.720), is superimposed by the subnet mask.
The subnet mask serves to identify which part of the IP address is marked by
the network and which part represents the device in the network.
All bits of the network part of the subnetwork mask are set to the value "1
" and all bits of the device part are set to the value "0".
A logic AND operation of both binary codes provides information on
the network ID
In areas with the value "0", devices (values from "1" to "254") can be
entered. The values "0" and "255" must not be used.
the corresponding network
the computer ID
The TCP/IP protocol is used to determine the path of the message:
Same network: communication via broadcast
Other network: communication via router
The standard subnet masks are divided into 3 classes:
Class Subnet mask
a 255.0.0.0
B 255.255.0.0
C 255.255.255.0
) Note!
The data are only accepted after the subcode 4 has been written.

After the codes C1210 and/or C1211 have been changed, the combination
of IP address and network mask is checked for validity.
Wenn eine Ungltigkeit vorliegen sollte, wird das Gateway auf die
IPAdresse 0.0.0.0 gesetzt und DHCP auf das dynamische Zuweisen der
IPAdresse gestellt.
C1211:
Subnet mask
5
5.7
5.7.4
Code
C1214
Name
MACID
Index: 0x5B41 (23361)
g
ro VS
Each module has a 48bit identification, the socalled MACID (Media Access
Control). The MACID is stored nonvolatilely in the memory of the module.
On principle, the identification of the module is assigned by the IEEE
(Institute of Electrical and Electronic Engineers). The IEEE assigns each
manufacturer a socalled OUI (Organisationally Unique Identifier). The OUI
represents the first 24 bits of the card address. The remaining bits of the
address are assigned by the manufacturer for each card. The numbering of
each card must be unique.
Code
C1202
Name
Gateway
Index: 0x5B37 (23351)
1 ... 4 0 0 [1] 255 rw FIX32
If the communication module is in another subnetwork than the PC, the IP
address of the corresponding router must be entered into this code.
) Note!
The data are only accepted after the subcode 4 has been written.
C1214:
MACID
C1224:
Gateway
Troubleshooting
Signalling of the CANopen RUN LED and ERROR LED
5
5.8
5.8.1
5.8 Troubleshooting
Possible cause of error Diagnostics Remedy
The device is not switched on Power LED is not lit Check external voltage supply
CAN bus error ERR LED is lit or blinking Check CAN wiring
Ethernet wiring error LINK LED is not lit Check Ethernet wiring
5.8.1 Signalling of the CANopen RUN LED and ERROR LED
The CANopen ERROR LED displays the status of the physical CAN level and
shows errors on the basis of missing CAN messages (SYNC, GUARD or
HEARTBEAT). It is lit red.
No. ERROR LED STATUS Description
1 OFF No error The device is ready for operation.
2 Single
lighting up
Warning limit is
reached
At least one of the error counters of the CAN
controller has reached or exceeded the warning
level (too many error frames).
3 Flicker AutoBaud/LSS The automatic baud rate detection or LSS services
are running. (ERROR LED and RUN LED flicker
alternately).
4 Double
lighting up
Error control
event
A guard event (NMT slave or NMT master) or
heartbeat event (heartbeat consumer) has
occurred.
5 Triple lighting
up
Sync error The sync message has not been received within
the time configured for the time monitoring of
the communication cycle..
6 On Bus Off The CAN controller is in the busoff state.
The CANopen RUN LED displays the CANopenNMT status. It is lit up green.
No. CAN RUN LED STATUS Description
are running. (ERROR LED and RUN LED flicker
alternately). Optional
2 Single
lighting up
STOPPED The device in the STOPPED state.
3 Blinking PREOPERATION
AL
The device is in the PREOPERATIONAL state.
4 On OPERATIONAL The device is in the OPERATIONAL state.
CANopen ERROR LED
CANopen RUN LED
Troubleshooting
5
5.8
5.8.1
The following message states are distinguished:
Signalling Meaning
LED is lit On
LED is not lit OFF
LED flickers Isophase on and off with approx. 10 Hz: on for approx. 50 ms and off
for approx. 50 ms.
LED is blinking Isophase on and off with approx. 2.5 Hz: on for approx. 200 ms,
followed by off for approx. 200 ms.
Single lighting up of the
LED
A short lighting up (approx. 200 ms) followed by a long off phase
(approx. 1000 ms).
Double lighting up of
the LED
LED shortly lights up twice in one sequence (approx. 200 ms),
interrupted by an off phase (approx. 200 ms). The sequence is
completed by a long off phase (approx. 1000 ms).
Triple lighting up of the
LED
LED shortly lights up thrice in one sequence (approx. 200 ms),
5.8.1.1 Operating mode diagnostic interface
) Note!
In this operating mode, the CANopen ERR LED is lit if no device is
connected.
Message states and lighting
rates
Index
5
5.9
5.9 Index
A
Application range, 5.21
B
Bus cable length, 5.46
C
C0002: Device commands, 5.718
C0093: Device type, 5.718
C0099: Software version, 5.718
C0150: Status word, 5.718
C0200: Software ID, 5.719
C0202: EKZn, 5.719
C0350: CAN node address, 5.74
C0351: CAN baud rate, 5.75
C0351: Set baud rate, 5.75
C0358: Reset node, 5.75
C0359: Diagnostics of the bus status, 5.76
C0360: Diagnostics of the telegram counter, 5.77
C0361: Diagnostics bus load, 5.77
C1200: Parameter data channel operating mode, 5.78
C1201: Communication timeout (CAN), 5.78
C1202: Time limit for node search, 5.78
C1203: Repeat tests, 5.79
C1209:Read out baud rate, 5.79
C1210: IP address, 5.720
C1211: Subnet mask, 5.721
C1214: MACID, 5.722
C1215: Automatic baud rate detection, 5.79
C1216: Userspecific device name, 5.710
C1217: Cycle time of CAN device monitoring, 5.710
C1219: Activation of CAN device monitoring, 5.711
C1220: CAN device monitoring, 5.712
C1224: Gateway, 5.722
C1227: Delay time for search telegrams, 5.713
C1228: Activation of DHCP, 5.713
C1229: Activation of IP settings, device reset, 5.714
C1230: IP address, 5.714
C1231: Subnet mask, 5.715
C1232: Default gateway, 5.715
Cable crosssection, 5.46
Cable length, 5.46
Cable specification, 5.45, 5.47
CANopen objects, 5.71
CANopen objects implemented, 5.73
CANopen parameter channels, 5.62
Code numbers, Access via the communication module,
5.62
Code numbers / index, Conversion, 5.62
Commissioning, 5.51
before you start, 5.11
Commissioning with the system bus configurator, 5.51
Commissioning with the web server, 5.56
Connections, 5.41
D
Data transfer, 5.61
Data transfer via Ethernet, 5.63
Description of the CANopen objects implemented, 5.716
Description of the codes important for the Ethernet
interface, 5.720
Description of the codes relevant for CAN, 5.74
Description of the general codes, 5.718
Device type (I1000), 5.716
Dimensions, 5.33
E
Electrical installation, 5.43
Elements of the communication module, 5.41
Error register, 5.716
Examples, Indexing of Lenze codes, 5.62
F
First switchon, 5.515
G
General data, 5.31
H
Hardware version, type code, 5.21
Index
5
5.9
I
I1000: Device type, 5.716
I1001, Error register, 5.716
I1017, Producer heartbeat time, 5.716
I1018: Module device description, 5.717
Identification, 5.21
Index, Conversion, 5.62
Indexing of Lenze codes, 5.62
Installation, 5.41
electrical, 5.43
mechanical, 5.42
Installation of required drivers, 5.52
L
Lenze Codes, C1227, 5.713
Lenze codes, 5.71
C00002, 5.718
C0093, 5.718
C0099, 5.718
C0150, 5.718
C0200, 5.719
C0350, 5.74
C0351, 5.75
C0358, 5.75
C0359, 5.76
C0360, 5.77
C0361, 5.77
C1200, 5.78
C1201, 5.78
C1202, 5.78
C1203, 5.79
C1209, 5.79
C1210, 5.720
C1211, 5.721
C1214, 5.722
C1215, 5.79
C1216, 5.710
C1217, 5.710
C1219, 5.711
C1220, 5.712
C1224, 5.722
C1228, 5.713
C1229, 5.714
C1230, 5.714
C1231, 5.715
C1232, 5.715
LenzeCodestellen, C0202, 5.719
M
Mechanical installation, 5.42
Module device description (I1018), 5.717
O
Operating conditions, 5.31
P
Pluggable terminal strip, Use, spring connection, 5.44
Pluggable terminal strips, handling, 5.44
Producer heartbeat time, 5.716
Protective insulation, 5.32
S
Segment cable length, 5.46
Signalling, 5.515
Signalling acc. to DR3033, 5.517
Software version, type code, 5.21
Specification of the transmission cable, 5.45, 5.47
System bus configurator, 5.52
System requirements, 5.51
T
Technical data, 5.31
Terminal data, 5.44
Total cable length, 5.46
Transmission cable, specification, 5.45, 5.47
Troubleshooting, 5.81
Type code, 5.21
V
Validity of the documentation, 5.21
Voltage supply, 5.44
EDSFEW
.%g%
.
%
g
%
Remote maintenance
Preface and general information

Introduction
1
1.1
1.1-1 EDSFEW EN 04/2005
1 Preface
1.1 Introduction
The competitive environment of machine and systemengineering calls for
solutions which optimise production costs. Thus, modular machine and
system engineering is becoming ever more popular, as it allows individual
solutions to be developed easily and cost-effectively through the use of
modular building blocks. In addition, the remote maintenance option is
alsoindemandtoday. It offers better support of commissioningor operating
personnel across almost all phases of the product life cycle, and helps to
further reduce costs.
Choosing the right remote maintenance software and hardware
components depends to a large extent on the field in which they are to be
used. It is important to consider how much integration is required into
available systems and whether or not any existing remote connections can
also be employed. The chapter Scenarios of remote maintenance in this
Communication Manual provides an overview of the different scenarios.
Decision support
About this Communication Manual
1
1.2
1.2-2 EDSFEW EN 04/2005
1.2 About this Communication Manual
This Manual is intended for all persons who install, commission and
maintain the networking and remote service of a machine.
The manual exclusively contains descriptions of LENZE communication
modules and software for the remote maintenance. Details on the
respective bus systems can be found in the corresponding Communication
Manuals.
The Manual is meant as anaddition tothe Mounting Instructions whichare
part of the scope of supply.
The features and functions of the communication modules are
described in detail.
Examples illustrate typical applications.
Moreover, it contains the following:
Safety instructions which must be strictly observed.
The most important technical data.
Information on versions of the Lenze basic devices to be used. Basic
devices are servo inverters, frequency inverters, drive PLC and motor
starters (starttec).
Notes on troubleshooting and fault elimination.
The manual does not describe the software of an original equipment
manufacturer. No responsibility is taken for corresponding information
given in this manual. Information on how to use the software can be
obtained from the documents of the master system.
Thetheoretical connectionsareonlyexplainedinsofar astheyarenecessary
for comprehending the function of the corresponding communication
module.
Eachchapter is acompleteunit andprovides comprehensiveinformationon
the relevant topic.
The Contents and Index help you to find all information about a certain
topic.
Descriptions and data of other Lenze products (controllers, drive PLC,
Lenze geared motors, Lenze motors) can be found in the corresponding
catalogues, Operating Instructions and Manuals. The required
information can be ordered at your Lenze sales partner or downloaded
as PDF file from the Internet.
Target group
Content
Howto find information
About this Communication Manual
1
1.2
1.2-3 EDSFEW EN 04/2005
The Manual is designed as a loose-leaf collection so that we are able to
inform you quickly and specifically about news and changes. Each page is
marked by the publication date.
Tip!
Current documentation and software updates for Lenze products
can be found on the Internet in the Downloads area under
Paper or PDF
Legal regulations
1
1.3
1.3-4 EDSFEW EN 04/2005
1.3 Legal regulations
Lenze communication modules are unambiguously designated by the
contents of the nameplate.
Lenze Drive Systems GmbH, Postfach 101352, D-31763 Hameln
Conforms to the EC Low voltage Directive
The communication module or function module
must only be operated under the operating conditions prescribed in
this Communication Manual.
is an accessory module which is used as an option for the Lenze
controllers or Lenze drive PLC. Detailed information on the application
range can be found in the chapter General information.
must be mounted and installed so that it fulfils its function and does
not bear any risks for persons in applications as directed.
Please observe all notes in the chapter Safety instructions.
Please observe all notes concerning the corresponding communication
module and function module in this Communication Manual. This means:
Before you start working, read this part of the Communication Manual
carefully.
Always keep the Communication Manual close to the communication
module/function module during operation.
Any other use shall be deemed inappropriate!
Labelling
Manufacturer
CE conformity
Application as directed
Legal regulations
1
1.3
1.3-5 EDSFEW EN 04/2005
The information, data, and notes met the state of the art at the time of
printing. Claims referring to communication modules/function modules
which have already been supplied cannot be derived fromthe information,
illustrations, and descriptions given in this Communication Manual.
Thespecifications, processes, andcircuitrydescribedinthis Communication
Manual are for guidance only andmust be adaptedtoyour ownapplication.
Lenzedoesnot takeresponsibilityfor thesuitabilityof theprocessandcircuit
proposals.
The specifications in this Communication Manual describe the product
features without guaranteeing them.
Lenze does not accept any liability for damage and operating interference
caused by:
Disregarding this Communication Manual
Unauthorised modifications to the communication module/function
module
Operating errors
Improper working on and with the communication module/function
module
See terms of sales and delivery of the Lenze Drive Systems GmbH.
Warranty claims must be made to Lenze immediately after detecting the
deficiency or fault.
The warranty is void in all cases where liability claims cannot be made.
Material Recycle Dispose
Metal D -
Plastics D -
Assembled PCB - D
Short instructions/Operating
Instructions
D -
Liability
Warranty
Disposal
Guide
Glossary
2
2.1
2.1-1 EDSFEW EN 04/2005
2 Guide
2.1 Glossary
A
APIPA Automatic Private IP-Addressing
This standardised mechanismenables an Ethernet device to get an IP
address on its own.
The following IP address area is reserved for APIPA : 169.254.xxxx.xxxx.
ASP Application Service Provider: ASPs manage the communication
infrastructure in the company.
AT Most of the modems (Hayes-compatible) are addressed via the AT
operations set. The AT commands serve to initialise the modemand to
establish and terminate the connection.
B
BOOTP Protocol for assignment of IP addresses
Broadcast The act of sending a frame to all stations. Is not transmitted via
gateways or routers
Bus server Fieldbus-specific OPC server to DRIVECOMspecification.
C
CAL CANApplication Layer
Communication standard (CiA DS 201-207), which provides the objects,
protocols, and services for the event or polling-controlled transmission
of CANmessages and the transmission of greater data ranges between
CANnodes. Furthermore, CAL offers effective processes for an
automatic assignment of message identifiers, the initialisation and
monitoring of network nodes and the assignment of an individual
identification to network nodes.
CAN Controller Area Network
Serial, message-oriented and not node-oriented bus systemfor max. 63
nodes.
CANopen Communication profile (DS301, version 4.01), which has been developed
in conformity with the CAL under the umbrella association of the CiA
(CANin Automation).
CiA CANin Automation (e. V.)
International users and manufacturers organisation which has the
target to impart knowledge on the internationally standardised CAN
bus system(ISO11898) worldwide and advance the technical
development.
Internet: http://www.can-cia.org
Code Parameters of Lenze devices for setting the device functions.
COM Component Object Model
Windows-based technology which enables the communication between
software components via standard interfaces
Controller Generic termfor Lenze frequency inverter, servo inverter and PLCs.
Guide
Glossary
2
2.1
2.1-2 EDSFEW EN 04/2005
D
DCOM Distributed Component Object Model
COMserves to distribute the objects to be executed to various
computers within on local area network.
DHCP Dynamic Host Configuration Protocol
The parameters IP address, subnet mask and gateway can be centrally
filed within one network. This can lead to simplification in case of great
networks. When a device is started, it gives its MAC address to the DHCP
server and requests the other parameters. This type of network
configuration is very common in the office world, but still rather
unusual in the field of industrial communication. Reason: Some DHCP
servers assign the IP addresses dynamically, i. e. at each start the same
device can be assigned with another IP address. This may cause the
devices to not be identified via their IP addresses anymore. However,
there are DHCP servers the IP addresses of which can be reserved for
special terminals. Such DHCP servers are also useful in the industrial
field.
DNS Domain Name System
It is also possible to work with names instead of an IP address within a
network. Each IP address can be assigned with a name. The names are
managed via a DNS server.
DRIVECOMUser
Group e.V.
Is an association of international drive manufacturers, universities, and
institutes which has the target to develop a simple integration of drives
in open automation systems.
DriveServer Lenze software which serves to implement a simple integration of
drives into open automation structures based on OPC.
G
Gateway Normally, there is not only one Ethernet segment but a network of
several segments that are coupled via defined transitions, gateways or
routers. With a change fromone segment to another, the mediumcan
also change, e. g. when routing via a telephone network. The net ID,
which is part of the IP address and the subnet mask showthat there are
different segments. If it is noticed that an addressed receiver is not
located in the same segment, the message is transmitted to the
configured gateway address, which is responsible for the forwarding.
H
HTML Hyper Text Markup Language. Text-based file format used for web
pages. It includes the text itself and instructions for representations and
references to other documents.
HTTP Hypertext Transfer Protocol. Protocol for transmitting HTML documents.
I
IP address Internet Protocol
Each network node has one IP address which must be definite within a
network. It is a logic address which can be changed per software (cp.
MAC address). It consists of 32 bits. It is always indicated by four
decimal numbers separated by a dot (dot notation) for better
readability.
The IP address consists of a net ID and a host ID. The net ID describes the
network segment and the host ID describes the node. The division of the
32 bits into net ID and host ID depends on the class of the IP address,
which can be detected fromthe first byte.
L
LECOM Lenze bus systembased on RS232, RS485 or optical fibre
Guide
Glossary
2
2.1
2.1-3 EDSFEW EN 04/2005
M
MAC address Media Access Control
The MAC address is unequivocal worldwide and cannot occur twice. It is
often printed on the device and cannot be changed. This unequivocal
address enables the device to be addressed at any rate, independent of
the other Ethernet devices on the bus. An address conflict cannot occur.
Since the address must always be changed when the device is replaced,
there is a logic addressing via the IP address in addition. The MAC
address is represented by six bytes in hexadecimal form, the single
bytes being separated by dots. The first three bytes refer to the
manufacturer, the other bytes serve to identify the device.
MIB Management Information Base
MPI Multi-Point-Interface
Bus systemwhich is integrated for instance into Siemens PLC.
N
NMT Network management
The service element network management (NMT) provides functions for
configuration, initialisation and monitoring of the network nodes in the
distributed system.
O
OLE Object Linking and Embedding
Inserting functional objects in other applications, e. g. a Microsoft
Excel table in a MicrosoftWord document.
OPC OLE for Process Control
Defines an interface based on the MicrosoftWindowstechnologies
OLE, COMand DCOM, which enables a data exchange between the
different automation devices and PC programs without driver and
interface problems.
Internet: http://www.opcfoundation.org
P
PDF Portable Document Format
This file format is developed by the Adobe company for exchanging
electronic documents. Adobes freely available software Adobe
Readerserves to display and print PDF files, independent of the
application and platformused.
PLC Programmable logic controller.
Port number The TCP telegramcontains a port number. It shows which application
programis to obtain the data.
Example: Port number 80 stands for the HTTP protocol which is used for
the transmission of HTML documents that can be displayed with a web
browser.
Guide
Glossary
2
2.1
2.1-4 EDSFEW EN 04/2005
S
SNMP Simple Network Management Protocol
SOAP Simple Object Access Protocol
Defines XML messages that can be exchanged between heterogeneous
applications per Internet by means of HTTP.
Subnet mask Network segments are described via the net ID (cp. IP address). If the
number of the network segments is not enough, a segment can be
further divided. If, for instance, the class of the IP address permits the
net ID to have a length of 16 bits, the 16-bit net ID can be further
divided. The subnet mask consists like the IP address of 32 bits which
are represented in four decimal numbers separated by dots. Those bits
that are to be used to distinguish a network segment must be set to 1 in
the subnet mask, the others must be set to 0. The subnet mask
255.255.255.0, for instance, would cause the IP address with a net ID of
only 16 bits to be continued to be used with 8 bits to identify different
network segments. If the receiver of an IP telegramis located in another
network segment, the gateway address is activated (cp. gateway).
Systembus (CAN) Lenze bus systemfollowing the communication profile CANopen
(DS301, version 4.01).
T
TCP Transport Control Protocol
The data transmission based on IP protocols is not secured, i. e. errors
may occur during the transmission. Therefore a master protocol is
required which recognises and corrects these faults and ensures that the
telegramwill be repeated. The TCP is a connection-oriented protocol
which provides the user data with a check sum. Moreover, each data
package gets a sequence number. If bigger data volumes are
transmitted, a segmentation is done and the data are distributed to
several telegrams. In order to recover the original data the sequence
number is used.
U
UDP User DatagramProtocol
Like the TCP, the UDP is a protocol based on IP. It uses a connectionless
service and is therefore faster than TCP. The disadvantage is that no
feedback is created with regard to a successful data transmission. Thus,
another check through the application programis required. Sequences
of longer data are neither supported.
V
VPN Virtual Private Network
A technology which enables confidential data to be transported via
open networks such as the Internet.
X
XML Extensible Markup Language
is similar to HTML but with user-definable structures.
Safety instructions
Contents
3
3-1 EDSFEW EN 04/2005
3 Safety instructions
Contents
3.1 Persons responsible for safety 3.1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 General safety instructions 3.2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Definition of notes used 3.3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety instructions
Persons responsible for safety
3
3.1
3.1-1 EDSFEW EN 04/2005
3.1 Persons responsible for safety
An operator is any natural or legal person who uses the drive system or on
behalf of whom the drive system is used.
The operator or his safety personnel is obliged
to ensure the compliance with all relevant regulations, instructions and
legislation.
to ensure that only qualified personnel works on and with the drive
system.
to ensure that the personnel has the Operating Instructions available
for all work.
to ensure that all unqualified personnel are prohibited from working
on and with the drive system.
Qualified personnel are persons who - due to their education, experience,
instructions, and knowledge about relevant standards and regulations,
rules for the prevention of accidents, and operating conditions - are
authorised by the person responsible for the safety of the plant to perform
the required actions and who are able to recognise potential hazards.
(Definition for skilled personnel to VDE 105 or IEC 364)
Operator
Qualified personnel
Safety instructions
General safety instructions
3
3.2
3.2-1 EDSFEW EN 04/2005
3.2 General safety instructions
These safety instructions do not claim to be complete. If you have any
questions or problems please contact your Lenze representative.
The communication module meets the state of the art at the time of
delivery and generally ensures safe operation.
The data in this manual refer to the stated hardware and software
versions of the communication modules.
The communication module may create a hazard for personnel, for the
equipment itself or for other property of the operator, if:
non-qualified personnel work on and with the communication
module.
the communication module is used improperly.
The specifications, processes, and circuitry described in this Manual are
for guidance only and must be adapted to your own specific
application.
Provide appropriate measures to prevent injury to persons or damage
to material assets.
The drive system must only be operated when it is in perfect condition.
Retrofitting or changes of the communication module are generally
prohibited. In any case, Lenze must be contacted.
The communication module is a device intended for use in industrial
power systems. During operation, the communication module must be
firmly connected to the corresponding controllers. In addition, all
measures described in the Manual of the controller used must be
taken. Example: Mounting of covers to ensure protection against
accidental contact.
Safety instructions
Definition of notes used
3
3.3
3.3-1 EDSFEW EN 04/2005
3.3 Definition of notes used
The following signal words and symbols are used in this documentation to
indicate dangers and important information:
Structure of safety instructions:
@ Danger!
(characterises the type and severity of danger)
Note
(describes the danger and gives information about how to
prevent dangerous situations)
Pictograph and signal word Meaning
@ Danger!
Danger of personal injury through dangerous
electrical voltage.
Reference to an imminent danger that may result in
death or serious personal injury if the corresponding
measures are not taken.
@ Danger!
Danger of personal injury through a general source
of danger.
Reference to an imminent danger that may result in
death or serious personal injury if the corresponding
_ Stop!
Danger of property damage.
Reference to a possible danger that may result in
property damage if the corresponding measures are
not taken.
Pictograph and signal word Meaning
@ Note!
Important note to ensure trouble-free operation
Tip!
Useful tip for simple handling
Reference to another documentation

Safety instructions
Application notes
Remote maintenance scenarios
Contents
4
4-1 EDSFEW EN 04/2005
4 Remote maintenance scenarios
Contents
4.1 Introduction 4.1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Customer benefit by remote maintenance 4.1-1 . . . . . . . . . . . . . . .
4.1.2 Internal and external remote maintenance 4.1-2 . . . . . . . . . . . . . .
4.1.3 Terminal access 4.1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Transparent data connection 4.1-5 . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Control access 4.1-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Technical scenarios 4.2-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Solution overview 4.2-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Switched connections 4.2-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Ethernet connection 4.2-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Connection via the Internet 4.2-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction
Customer benefit by remote maintenance
4
4.1
4.1.1
4.1-1 EDSFEW EN 04/2005
4.1 Introduction
4.1.1 Customer benefit by remote maintenance
Remote maintenance inthe different life cycle phases of a product provides
the following customer benefit:
Advantage Customer benefit
More efficient problemsolving by fast remote
support fromthe systemmanufacturer or
component supplier
Faster response times, shorter development time
Design engineers are available in the central office
Better availability of the specialists of the systemand
component manufacturer
Know-howtransfer between mounting site and
company and company headquarters
Time saving, production can begin
earlier
Faster error diagnosis, measures for eliminating
errors are implemented faster, short response time
Lower travel costs, better applications planning
Increase of the customer loyalty, developing new
business areas
Service can be better prepared - The right man with
the right spare part
Shorter standstill times, lower
costs
Increase of productivity
Increase of competitiveness
Direct control of the functions without on-site
presence
Cost savings
Increase of productivity thanks to
improved process control
Phase: Project planning
Configuration
Parameter setting
Programming
Phase: Service / maintenance
Diagnostics
Troubleshooting
Fault elimination
Systemmaintenance
Software updates
Phase: Production
Process optimisation
Production monitoring
Quality assurance
Recipe change
Introduction
Internal and external remote maintenance
4
4.1
4.1.2
4.1-2 EDSFEW EN 04/2005
4.1.2 Internal and external remote maintenance
4.1.2.1 Internal remote maintenance
In industrial sectors like materials handling technology, automobile
industry, packaging technology, or process engineering, great
communicationsystems are designed for the manufacturing plant withina
building.
The components and networks required for the infrastructure are installed
for it:
Control (PLC or PC)
Fieldbuses
Sensors/actuators (controllers, HMI, encoders)
Local company network on Ethernet basis
The equipment available serves to fulfill the requirements of the plant
operators:
Visualisation of the plant situation down to the lowest level from a
control room.
Influence on the process and the system components down to the
lowest level from a control room.
Tip!
Visualisation means
diagnostics with regard to service
display of the current plant status
Influence means
controlling (defining new setpoints, starting/stopping the
system)
changing parameters
changing programs
changing firmware/operating system of the devices
The customer requirements result in the following technical requirements:
Transparent data exchange between the office level (Ethernet) and the
field level (fieldbus)
Control access to secondary devices
Customer requirements
Technical requirements
Introduction
Internal and external remote maintenance
4
4.1
4.1.2
4.1-3 EDSFEW EN 04/2005
4.1.2.2 External remote maintenance
Theclassical expressionremotemaintenance describes theremoteaccess
via the telephone network.
Control (PLC or PC)
Fieldbuses
Sensors/actuators (controllers, HMI, encoders)
Ethernet within the plant or within the single buildings
Telephone network (analogue, ISDN or GSM)
Internet
Visualisation of the plant situation down to the lowest level from a
distance.
Influence on the process and the system components down to the
lowest level from a control room.
Thecustomer requirements gives risetothetechnical requirement that is to
makethedataexchangetransparent fromthedistanceviaanytelephoneor
Internet connections to the plant.
Connection to the plant means
A control is the communication partner of the remote connection. A
control access takes place, cp. (L 4.1-6).
A controller is the communication partner of the remote connection.
Further controllers are interconnected via an internal bus. Gateway
functions in the controller is required.
Infrastructure
Customer requirements
Technical requirement
Introduction
Terminal access
4
4.1
4.1.3
4.1-4 EDSFEW EN 04/2005
4.1.3 Terminal access
This method serves to redirect the terminal. The maintenance PC has the
same interface as the system PC. One of the first solutions for this method
in WindowsRenvironment was the PC program pcAnywhereR.
This method is unfavourable when, for instance, the maintenance staff has
to set another interface than the one the machine operator requires to
operate his system for reading out the drive information. Furthermore, all
software packages must be installed on the machine computer. A free
information access to data, e. g. of a drive is typically not given (e. g. OPC
DriveServer is required).
Another method is applied for the MicrosoftR Terminal Server. It provides
the opportunity to start and operate the application from a client
(e. g. maintenance PC) on which the software is not installed. Every user of
the Terminal Server starts an own application entity. Thus, the application
does not need to fulfill any special requirements in terms of the
implementation except that it must provide the option to enable several
users to process the same data at the same time.
Adisadvantage is that a PCmust be available inthe machine. Moreover, the
transparent data access cannot be guaranteed without further measures
(e. g. OPC-DriveServer) and the complete maintenance software must be
installed on the machine PC.
WindowsRXPR supports the remote desktop connection. Here, the entire
content of thescreenis forwardedtoanother PCwithinalocal areanetwork.
Redirecting the terminal
Microsoft Terminal Server
Remote desktop connection
Introduction
Transparent data connection
4
4.1
4.1.4
4.1-5 EDSFEW EN 04/2005
4.1.4 Transparent data connection
The transmission of complete user interfaces is affected by considerable
delay times withregardtooperationdue tothe toohighdata volumes tobe
transmitted. Therefore, it is more efficient to only transmit the user data.
Depending on the connecting path, the solutions partly differ considerably.
The following connecting paths are considered in the remote maintenance
scenarios:
Connecting path
1. Classical fieldbuses
2. Ethernet
3. Modem
4. ISDN
5. GSM
6. Internet
The transparent transmission of fieldbuses via remote connections are
indispensable for current mechanical engineering applications. In the
general DV environment, however, special solutions are required. For
coupling Ethernet components, standard devices which have already
become established in the office communication.
The implementation of different solutions requires a varying degree of
special know-how. Many of the solutions shown here do not demand more
know-howthan usually required for the fieldbus-based applications. Those
solutions which require further IT knowledge are marked correspondingly.
Introduction
Control access
4
4.1
4.1.5
4.1-6 EDSFEW EN 04/2005
4.1.5 Control access
Fieldbus
Fieldbus
Fieldbus
2180FEW100 2180FEW101
Often, there is no direct connection between the PC and the devices to be
remote-maintained. This is thecasewhen, for instance, acontrol is provided
with the exclusive bus access to a device. If so, the control must provide the
higher-level system with the transparent access to the lower-level system.
This access, however, is not available in all cases.
Advantages of access
Only one central point of application, the same interface for the
access on control and lower-level devices
Only one remote maintenance / PC card
Disadvantages of access
Not available for every control
Slower action since delays occur due to forwarding.
Technical scenarios
Solution overview
4
4.2
4.2.1
4.2-7 EDSFEW EN 04/2005
4.2 Technical scenarios
4.2.1 Solution overview
Switched connection L 4 2-8 Switched connection L 4.2-8
CANvia modem L 4 2-9 CANvia modem L 4.2-9
Diagnostic interface 9400 via modem L 4 2-10 Diagnostic interface 9400 via modem L 4.2-10
CANvia ISDNor GSM L 4 2-11 CANvia ISDNor GSM L 4.2-11
Teleservice with S7 control L 4 2-12 Teleservice with S7 control L 4.2-12
Ethernet connection L 4 2-13 Ethernet connection L 4.2-13
Direct Ethernet connection L 4 2-14 Direct Ethernet connection L 4.2-14
CAN via Ethernet L 4 2-14 CAN via Ethernet L 4.2-14
9400 Ethernet communication module L 4 2-16 9400 Ethernet communication module L 4.2-16
S7 Ethernet connection L 4 2-16 S7 Ethernet connection L 4.2-16
S7 via IBHLink L 4 2-17 S7 via IBHLink L 4.2-17
Motion Control ETC L 4 2-17 Motion Control ETC L 4.2-17
Connection via PC L 4 2-18 Connection via PC L 4.2-18
Systembus (CAN) L 4 2-18 Systembus (CAN) L 4.2-18
LECOM L 4 2-19 LECOM L 4.2-19
S7 via MPI / PROFIBUS L 4 2-20 S7 via MPI / PROFIBUS L 4.2-20
PROFIBUS L 4 2-21 PROFIBUS L 4.2-21
Internet connection L 4 2-22 Internet connection L 4.2-22
Technical scenarios
Switched connections
4
4.2
4.2.2
4.2-8 EDSFEW EN 04/2005
4.2.2 Switched connections
The direct switched connection serves to carry out the simplest way of
remote maintenance.
The installation expenses are low due to the laying of a simple analogue
telephonelinetothesystem. Theaccess protectioncanbeeasilyachievedby
means of passwordmechanismandcallback. Alockableswitch, for instance,
is a further protective measure by activating the telephone line only in case
of need.
Isolated applications relating to the single components are
disadvantageous. This, inturn, couldincrease the installation expenses and
complexity of the remote maintenance due to the remote maintenance
with devices of different manufacturers (and thus different modems).
Connecting the single components to be remote-maintained to a
higher-level system put things right. Therefore, however, comprehensive
considerationsconcerningsafetyarerequired. Often, suchtasks cannot only
be solved by the systemmanufacturer but need to be coordinated with the
responsible IT department. For this reason, the switched connections are a
common and preferred solution.
Technical scenarios
4
4.2
4.2.2
4.2-9 EDSFEW EN 04/2005
4.2.2.1 CAN via modem
ModemCAN2181
Systembus (CAN)
Analog telephone
network
2180FEW102
The communication module 2181 ModemCAN enables the CAN bus to be
connected to an analog telephone line. The communication module is
provided with an analog modemwhich is approved in all countries that are
internationally relevant and thus permits a worldwide remote
maintenance. If required, an external modem can be connected if the
internal modem is not suitable in the corresponding country or a GSM or
ISDN modem is needed.
The communication module offers a password function as access
protection. Furthermore, it is possible to configure the device so that a
connection can only be established after calling back a preconfigured
telephone number.
Telephone CAN
Diagnostic
interface 9400
Internal
modem
External
modem
2180FEW103
Technical scenarios
4
4.2
4.2.2
4.2-10 EDSFEW EN 04/2005
4.2.2.2 Diagnostic interface 9400 via modem
ModemCAN2181
Systembus (CAN)
Analog telephone
network
ETHERNET Powerlink
2180FEW104
In addition to the system bus (CAN) interface the communication module
2181 ModemCAN offers a diagnostic interface which can be directly
connected with the controllers of the 9400 series. It is particularly suitable
for the temporary connection to a system. The Gateway function in the
9400 serves to access all other devices which are interconnected via the
system bus (CAN) or ETHERNET Powerlink. In case of a fixed installation, a
direct connection to the system bus (CAN) is to be preferred.
Technical scenarios
4
4.2
4.2.2
4.2-11 EDSFEW EN 04/2005
4.2.2.3 CAN via ISDN or GSM
Telephone network
ISDN
GSM
ISDN
GSM
Systembus (CAN)
ModemCAN2181
2180FEW105
In connection with modems of original equipment manufacturers it is
possible to use the communication module 2181 ModemCAN also for
remote maintenance via GSM or ISDN systems. A condition for this is that
these modems canbe addressedviaa RS232interface andreact tostandard
AT commands.
Technical scenarios
4
4.2
4.2.2
4.2-12 EDSFEW EN 04/2005
4.2.2.4 Teleservice with S7 control
Analog telephone network
TS adapter
MPI
PROFIBUS
S7
2180FEW106
Often, Lenze controllers are used in connection with S7 control systems of
Siemens. If the Siemens control is already provided with a remote
maintenanceconnection, it is useful touse it for remotemaintenance of the
controllers as well.
The remote connection is established via an analog telephone line with a
modemwhichisconnectedtotheteleserviceadapter. Thisisthenconnected
to the MPI interface to the S7 control.
To implement this solution no special hardware of Lenze is required.
The software OPC DriveServer S7 is used. This includes program parts
whichmust beinstalledonthePCwhichisusedfor remotemaintenanceand
alibrarywithfunctionblocks whichmust beintegratedintotheS7program
(this solution corresponds to the concept control access, see (L 4.1-6)).
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-13 EDSFEW EN 04/2005
4.2.3 Ethernet connection
The simplicity and comprehensibility of the solutions described before are
advantageous for smaller systems. For bigger systems, however, it is
unfavourable that single machine parts or even single devices require an
independent telephoneline. Suchsystems requireasolutionwithauniform
accesspathviawhichall componentscanberemote-maintained, if possible.
The access to remote-maintained components via Ethernet is favourable.
For remoteaccess toEthernet networks tried-and-testedstandardsolutions
exist which can be selected according to the demands required in terms of
safety, availability and different transmission media.
Many devices already have Ethernet interfaces on board. If these are not
available, theEthernetconnectioncanbeimplementedbymeansof fieldbus
converters. The corresponding solutions are described in the following.
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-14 EDSFEW EN 04/2005
4.2.3.1 Direct Ethernet connection
Ethernet
EthernetCAN2180
Systembus (CAN)
2180FEW107
The communication module 2180 EthernetCAN connects the system bus
(CAN) to a higher-level Ethernet network. Thus, the fieldbus nodes can be
integrated into higher-level systems. This enables already available
networks (in-house network) to be used for data transmission and the use
of central remote maintenance accesses (Remote Access Services).
CAN via Ethernet
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-15 EDSFEW EN 04/2005
Example of remote maintenance via ISDN:
ISDNtelephone
network
ISDN
Systembus (CAN)
Ethernet
Systembus (CAN)
EthernetCAN2180
2180FEW108
For this solution, standard ISDN routers or PC cards are used.
Besides the applications already described, the communication module
2180 EthernetCAN also provides for the implementation of the concept
without considering the control, see (L 4.1-6). If the control has an
Ethernet connection, a central remote maintenance of control and
controllers is possible via Ethernet. In contrast to the control access which
requires the exact knowledge of the control andspecial functionblocks, this
solution is independent of the type of control.
Ethernet
Systembus (CAN)
Fieldbus
EthernetCAN2180
2180FEW109
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-16 EDSFEW EN 04/2005
The 9400 device series already offers a direct connection to Ethernet via an
option module. This serves to directly remote-maintain these devices by
means of standardinfrastructural components as ISDNrouters (cp. 3.2.3.1).
The gateway function integrated in the 9400 serves to access the
components connected to the system bus (CAN).
Ethernet
Systembus (CAN)
2180FEW110
The S7 controls of Siemens can be equipped with an Ethernet interface via
a communicationprocessor. This interface module provides the integration
intohigher-level systems. The OPCDriveServer S7serves toaccess theLenze
controllers connectedtoPROFIBUSthroughthecontrol andtoconnect them
indirectly with the Ethernet and the higher-level remote maintenance
system.
Ethernet
PROFIBUS PROFIBUS
OPC DriveServer
Bus server S7
2180FEW111
9400 Ethernet
S7-Ethernet connection (CP)
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-17 EDSFEW EN 04/2005
The IBHLink of the IBHSoftec company is a simple alternative to the S7
communication processor. It is a cable which has an Ethernet connector on
one side and an MPI connector on the other side. This is the slower solution
than via the communication processor but less expensive. Basically,
however, the architecture is the same for remote maintenance purposes.
The Motion Control ETC has an Ethernet connection on board. Moreover, it
has twoCANconnections onwhichtheaxis or further I/Oterminals andCAN
devices are located. The integratedgateway functioninthe ETCcontrol also
enables the access tothe lower-level devices at the CANbus. Aconditionfor
this is the installation of the OPC bus server for the ETC control on the PC.
Ethernet
CANI/O
CANDrive
ETC
2180FEW112
S7 via IBHLink
Motion Control ETC
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-18 EDSFEW EN 04/2005
4.2.3.2 Connection via PC (connection via Ethernet technology)
Inorder tousethe advantages (L 4.2-13ff.) of theEthernet, it is requiredto
provide devices with an Ethernet interface or
use special gateways which have an Ethernet connection (as separate
devices or implicitly by a control).
An alternative to this are the PC-based systems. Here, the PC assumes the
implementation of the fieldbus protocol with a software interface suitable
for the Ethernet. In this connection, the OPC specification (OLE for Process
Control) has developed into the industry standard. If an industry PC with a
corresponding fieldbus card is available in a system, the PC can be used as
Ethernet gateway based on an OPC server:
LenzeoffersOPCserversintheformof packages. TheOPCDriveServer issuch
apackage. It contains, amongother things, abus-specific OPCserver for CAN
which is complemented by the device-specific OPC server (DriveServer).
The OPC protocol which has priority over the DriveServer, is suitable for the
Ethernet networks. Each computer connected to the Ethernet principally
allows the access to the DriveServer. The access protection concerning the
DriveServer is controlled via Windows mechanisms (DCOM).
OPC DriveServer
Bus server - systembus
LANor remote connection
Systembus (CAN)
2180FEW113
Both computers can be directly connected via Ethernet which results in a
better structuring within a large system. Furthermore, it is also possible to
couple the computers via a remote connection (Remote Access Service).
Basically, all options described in (L 4.2-13 ff.) apply.
Systembus (CAN) ,
OPC DriveServer
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-19 EDSFEW EN 04/2005
In addition to the bus server for the system bus (CAN) the DriveServer
packagecontainsabusserver whichsupportstheserial LECOMprotocol. The
resultingarchitecturefullycorrespondstotheonedescribedbefore, onlythe
bus system is different.
OPC DriveServer
Bus server LECOM
Ethernet
2180FEW114
LECOM(DriveServer)
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-20 EDSFEW EN 04/2005
If S7 controls are involved in the communication system, the OPC
DriveServer in the S7 variant can also be used.
As mentioned before, there are several options of remote maintenance in
connection with S7 controls, as for instance the direct switched connection
(L 4.2-8) or the access via Ethernet interface modules (L 4.2-13). All
options basically needthe OPCDriveServer S7. The controller andS7control
are always connectedvia the PROFIBUS. If the systemincludes a PC, it is also
possible to establish a remote maintenance with OPC technology. In this
case, you are independent of the communication system between the PC
andS7. MPI or PROFIBUS canalsobe used. Noother hardware is usedfor the
Ethernet connection, except for the PC.
OPC DriveServer
Bus server S7
MPI or PROFIBUS
PROFIBUS PROFIBUS
2180FEW115
S7 via MPI / PROFIBUS
Technical scenarios
Ethernet connection
4
4.2
4.2.3
4.2-21 EDSFEW EN 04/2005
Unlike the systembus (CAN), PROFIBUS is a centrally controlledsystem. This
means that basically only the bus master can access the single nodes. It
follows that the control access is required, see (L 4.1-6).
In addition to the control master (class 1), the PROFIBUS defines another
master (class 2) which can be used for diagnostic purposes. Irrespective of
the control it is possible to establish a connection with the bus via a further
PROFIBUS interface module for diagnostic purposes.
Conditions for such a solutions are that
the control accepts a class-2-master (set corresponding parameters, if
required)
the PROFIBUS stations accept the access to a class-2-master. For this,
check if the corresponding communication module supports the acyclic
DP-V1 services of the PROFIDrive profile V3.1 for parameter setting.
PROFIBUS
2180FEW116
PROFIBUS
Technical scenarios
Connection via the Internet
4
4.2
4.2.4
4.2-22 EDSFEW EN 04/2005
4.2.4 Connection via the Internet
The importance of the Internet is ever increasing. Already today, there are
countries whichcanbeaccessedmoreeasilyviaInternet thanviatelephone.
This results in the demand to use the Internet as a remote maintenance
connection as well.
Basically, this demand is no problem since Ethernet connections can be
imagedontheInternet inatransparent way. However, it is problematic that
a permanent connection to an open network involves considerable risks. In
addition to the technical conversion of the data with regard to the Ethernet
requires measures in terms of access protection to be protected against
hackers or viruses.
Thus, the main task is to complement the solutions described in chapter
4.2.2 to 4.2.3.2 by the safety requirements and co-ordinate this with the
respective IT departments of the plant operators. This task is not the focus
of Lenze.
The following subchapters are suggestions of how a remote maintenance
could be realised via the Internet and which elements play a role. The
concrete structure, however, must be specially adjusted. For this purpose,
Lenze can give the names of suitable service providers, who carry out such
adjustment between the IT departments involved, suggest suitable
infrastructural components and commission the networks.
In the following, some terms are explained which play a role in the field of
access protection. Then, the network planning is described in detail.
@ Note!
Remote maintenance solutions via the Internet
require an intensive consultation by IT service providers
can under no circumstances be established without consulting
the IT service providers involved.
4.2.4.1 Authenticity
Theglobal accessoptionsviaInternet requireasophisticatedsafetyconcept.
The significance of the data integrity in a company depends on the type of
data to be transmitted. Customer and development data are much more
sensitive than mere product data sheets for sales purposes. If a high safety
step is required, integrity and data confidentiality must be ensured in
addition to authenticity.
Authenticity means to be assured of the identity of a communication
partner. The user is identified via the name and password. Moreover, the
access via the Internet offers various further authentication mechanisms.
Among other things, the protocols PAP (Password Authentication Protocol)
and CHAP (Challenge Handshake Authentication Protocol) are supported.
Technical scenarios
4
4.2
4.2.4
4.2-23 EDSFEW EN 04/2005
4.2.4.2 Integrity
In order to ensure integrity (i. e. to be assured to have received data in an
unmodified form) and communication confidentiality, different
cryptographic methods are used. The approach via a VPN (Virtual Privat
Network) uses suchencryptiontechniques. AVPNenables privatedatatobe
transmitted safely via a public, unsecure medium such as the Internet. A
secure transmission is achieved by Tunnelling technology and different
safety procedures. Tunnelling means the integration of a protocol into
another. This enables the transport of any protocol via IP. Knowntunnelling
protocols are, for example, PPTP (Point-to-Point Tunnelling Protocol) and
L2TP(Layer 2TunnellingProtocol). Themechanismsfor VPNsafetywhichare
definedintheIP-sec standard, areintegratedintotheseprotocols. Theresult
is a safe communication tunnel between automation site and mobile
service staff.
4.2.4.3 Firewalls
VPN systems are available as dedicated solutions or in connection with a
firewall system. As soon as a local network is connected to the Internet, a
firewall system should be an integral part of the safety concept. The basic
task of a firewall systemis to ensure an uninterrupted access of the user of
the private network (Intranet) to the public network (Internet) and, at the
sametime, protect theowndatanetworkfromexternal violations. Basically,
a firewall consists of hardware and software components which are
individually configured according to the requirements of the services
availablefor theinternal users andthesafetytobeguaranteed. This enables
the firewall toprevent non-authenticatedaccesses tothelocal networkand
the controlled access to the distributed data bases and network resources
with a simultaneous logging of the access activities.
Firewallscanalsobereasonablewithinonecompany, e. g. for decouplingthe
production area of the office Ethernet.
Technical scenarios
4
4.2
4.2.4
4.2-24 EDSFEW EN 04/2005
4.2.4.4 Router
A router is a coupling element between two different Ethernet networks.
The router decides on the basis of rules which telegrams with which target
may pass. It uses the following mechanisms:
Authentication
Package filtering: Decision on the basis of the data contents of the
packages
Access list: Definition via IP addresses
Restriction of ports: Do not admit all telegram types (e. g. http, FTP,)
Only the combination of different mechanisms guarantees maximum
safety. Therefore, it is recommended to use an adaptive network safety
strategy which is adjusted to the individual safety requirements of the
respective company.
Tip!
A PC can also be a firewall. A PC which undertakes this task
should then, however, not perform other tasks. It is
recommendable to use enclosed devices.
Technical scenarios
4
4.2
4.2.4
4.2-25 EDSFEW EN 04/2005
4.2.4.5 Architecture example
Basically,there are two different scenarios:
1. Remote maintenance from a standalone computer to a company
network
2. Remote maintenance from one company network to another
Field service
Encrypted
Ethernet
Company
Unencrypted
Gateway with VPN
ISP with VPN
ISP
Notebook with VPN
Notebook without
VPN
2180FEW117
Fig. 4.2-1 Remote maintenance froma standalone computer to a company network
The PC from which the remote maintenance is to be operated, has an
Internet access via DSL, ISDN or other modems. It is recommendable to
operate a VPNon this PC to secure the connection between PC and Internet
serviceprovider (ISP). Onthecompanyside, aVPNgatewayisrequiredfor the
devices to be remote-maintained. The VPNgateway can both be a separate
device and a combination of VPN, firewall and router.
Remote maintenance froma
standalone computer to a
company network
Technical scenarios
4
4.2
4.2.4
4.2-26 EDSFEW EN 04/2005
Site A
Internet
Encrypted
Ethernet
Gateway with VPN
Site B
Ethernet
Gateway with VPN
2180FEW118
Fig. 4.2-2 Remote maintenance fromone company network to another
The architecture of this application also requires VPN, router and firewall.
It is recommendable that the service PC, which is used for maintenance
purposes, has no access to its local network during the maintenance. This
ensures that it cannot be misused as a tunnel into the entire company
network. Often the service PCs are separated from the other company
network by firewalls. Within the companies, firewalls can e. g. be used for
separating the office andmachine network. The entire scenario depends on
the respective application.
Ethernet Internet access
Router
Ethernet
Ethernet
2180FEW119
Remote maintenance from
one company network to
another
EDSFEW
!!!!
!
!
!
!
ModemCAN
EMF2181IB
Communication module
2181 communication module (ModemCAN)
Contents
6
6-1 EDSFEW EN 04/2005
6 Communication module 2181 ModemCAN
Contents
6.1 Before you start 6.1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Your opinion is important to us 6.1-1 . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 What is new / what has changed in these Instructions? 6.1-1 . . . .
6.2 General information 6.2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Technical data 6.3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 General data and operating conditions 6.3-1 . . . . . . . . . . . . . . . . . .
6.3.2 Climatic conditions 6.3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Rated data 6.3-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4 Dimensions 6.3-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Installation 6.4-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 Elements of the communication module 6.4-1 . . . . . . . . . . . . . . . . .
6.4.2 Mechanical installation 6.4-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.3 Electrical installation 6.4-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Commissioning 6.5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.1 Before switching on 6.5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.2 Commissioning with the system bus configurator 6.5-2 . . . . . . . . .
6.5.3 First switch-on 6.5-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 Data transfer 6.6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.1 Data transfer via CAN 6.6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.2 Data transfer via the diagnostics interface 6.6-3 . . . . . . . . . . . . . . . .
6.6.3 Data transfer via modem 6.6-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7 Lenze codes and CANopen objects 6.7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7.1 Description of the codes relevant for CAN 6.7-3 . . . . . . . . . . . . . . . .
6.7.2 Description of the CANopen objects implemented 6.7-11 . . . . . . . . .
6.7.3 Description of the general codes 6.7-13 . . . . . . . . . . . . . . . . . . . . . . . .
6.7.4 Description of the codes relevant for the modem 6.7-14 . . . . . . . . . .
6.8 Troubleshooting 6.8-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.8.1 Signalling of the CANopen RUN LED and ERROR LED 6.8-1 . . . . . . . .
6.9 Appendix 6.9-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9.1 Modem standards 6.9-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9.2 Country list 6.9-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9.3 AT commands 6.9-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10 Index 6.10-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before you start
6
6.1
6.1.1
6.1-1 EDSFEW EN 04/2005
6.1 Before you start
Tip!
Current documentation and software updates for Lenze products
can be found on the Internet in the Downloads area under
6.1.1 Your opinion is important to us
These Instructions were created to the best of our knowledge and belief to
give you the best possible support for handling our product.
If you have suggestions for improvement, please e-mail us to:
feedback-docu@Lenze.de
6.1.2 What is new/ what has changed in these Instructions?
Edition date Revised chapters Notes
04 / 2005 - First edition
General information
6
6.2
6.2-1 EDSFEW EN 04/2005
6.2 General information
These Instructions are valid for
2181 communication modules (ModemCAN) as of version 1x. 1x.
These Instructions are only valid together with the Operating Instructions
for the basic devices permitted for the application.
92181FEW099
Type code 33.2181IB Vx 1x
Series
Hardware version
Software version
The communication module can be used with the following Lenze devices:
L-force I 9400
9300 servo inverter
9300 Servo PLC
ECS servo system
8200 motec motor inverter
8200 vector frequency inverter
Drive PLC
82XX frequency inverter
starttec motor starter
Terminal extension 9374
Control / display unit (EPM-HXXX)
Digital input/output module (EPM-TXXX)
The internal modem supports a series of international specifications and
standards.
If the internal modem cannot be used, it is possible to connect an external
modem using the RS232 interface.
The communication module is used for setting parameters during remote
maintenance or programming and commissioning the usable Lenze
devices.
Validity
Identification
Application range
Features
Technical data
General data and operating conditions
6
6.3
6.3.1
6.3-1 EDSFEW EN 04/2005
6.3 Technical data
6.3.1 General data and operating conditions
Range Values
Order designation EMF2181IB
Communication media
(system)
CAN(DINISO11898)
Lenze diagnostic interface
Communication media
(external)
Telephone, analogue, 33.6 kbits/s, (V34)
Number of nodes at the CAN
bus
Max. 100
Baud rate For communication via the CANbus
20 kbits/s
50 kbits/s
125 kbits/s
250 kbits/s
500 kbits/s
1000 kbits/s
For communication via diagnostic interface
230.4 kbit/s
Voltage supply (external) via
separate power supply
18 - 30 V DC, max. 100 mA (in accordance with EN61131-2)
6.3.2 Climatic conditions
Reference Values
Type of protection IP20
Ambient temperature during operation: 0C ... +60 C p
during transport: - 10C ... +70 C
during storage - 10C ... +60 C
Climatic conditions Class 3K3 to EN50178 (without condensation, average relative
humidity 85 %)
Pollution degree EN50178, pollution degree 2
Technical data
Rated data
6
6.3
6.3.3
6.3-2 EDSFEW EN 04/2005
6.3.3 Rated data
2181FEW001F
Connection Type of insulation (to EN 61800-5-1)
1 Telephone Functional insulation
Diagnostic interface Functional insulation
CANbus Functional insulation
Voltage supply No insulation
1 External modem No insulation
Technical data
Dimensions
6
6.3
6.3.4
6.3-3 EDSFEW EN 04/2005
6.3.4 Dimensions
2181FEW001B
a 117 mm
b 103 mm
b1 99 mm
e 22.5 mm
Installation
Elements of the communication module
6
6.4
6.4.1
6.4-1 EDSFEW EN 04/2005
6.4 Installation
6.4.1 Elements of the communication module
2181FEW001D
Fig. 6.4-1 Communication module ModemCAN2181
Pos. Name Description
1 Telephone connection Socket (RJ11)
Connection at diagnostic interface
of the 9400 drive controller
(in preparation)
Socket (RJ69)
CANconnection Socket (RS232, male)
Connection for voltage supply Terminal strip with spring connection, 4-pole
1 External modemconnection Socket (RS232, male)
PE connection The plugged communication module is
automatically connected to the DINrail.
The DINrail must be connected with PE!
A
( )
YELLOW On The ModemCANis ready
(M)
Blinking Active communication over the telephone,
the ModemCANhas answered.
(E)
RED See L 6.5-7 ERR LED
(R)
GREEN RUNLED or diagnostic interface active
(P)
GREEN On The ModemCANis supplied with voltage.
@ Note!
Refer to the instructions on the signals provided by the ERROR
LED and RUN LED in the Troubleshooting chapter (L 6.8-1).
Connections
Displays
Installation
Mechanical installation
6
6.4
6.4.2
6.4-2 EDSFEW EN 04/2005
6.4.2 Mechanical installation
2181FEW002B
Fig. 6.4-2 Snap communication module to DINrail
2181FEW001E
Fig. 6.4-3 Unlock communication module and lift off DINrail .
Mounting
Dismounting
Installation
6
6.4
6.4.3
6.4-3 EDSFEW EN 04/2005
6.4.3 Electrical installation
6.4.3.1 Communication via CAN
2181FEW008
Fig. 6.4-4 Communication via the CANbus
Step Activity Connection
(see graphic)
Additional
information
1. Connect voltage supply to the plug connector L 6.4-5
2. Insert SUB-D plug (EWZ0046, see Accessories) in
ModemCAN
L 6.4-6
3. If it is not possible to use the internal modem:
Connect external modem
1 L 6.4-8
4. Connect drive controller to CANbus 1 -
5. Connect ModemCAN2181 to telephone network 1 L 6.4-9
Installation steps
Installation
6
6.4
6.4.3
6.4-4 EDSFEW EN 04/2005
6.4.3.2 Communication via the diagnostics interface (9400)
2181FEW007
Fig. 6.4-5 Communication via the diagnostic interface (only 9400)
Step Activity Connection
(see graphic)
Additional
information
1. Connect voltage supply to the plug connector L 6.4-5
2. Connect diagnostic interface to drive controller 9400
(use prefabricated cable)
L 6.4-10
3. If it is not possible to use the internal modem:
Connect external modem
1 L 6.4-8
4. Connect drive controller to CANbus 1 -
5. Connect ModemCAN2181 to telephone network 1 L 6.4-9
Communicating via the diagnostic interface is especially recommended if
the 2181 communication module is only connected temporarily.
In case of a fixed installation the communication via CAN should be
preferred, see (L 6.4-3).
Installation steps
Installation
6
6.4
6.4.3
6.4-5 EDSFEW EN 04/2005
6.4.3.3 Voltage supply
2181FEW001G
Terminal data
Electrical connection Plug connector with spring connection
Possible connections rigid: 2.5 mm
2
(AWG 12)
flexible:
without wire end ferrule
2.5 mm
2
(AWG 12)
with wire end ferrule, without plastic sleeve
2.5 mm
2
(AWG 12)
with wire end ferrule, with plastic sleeve
2.5 mm
2
(AWG 12)
Bare end 10 mm
_ Stop!
In order to avoid damages to the pluggable terminal strips and
the contacts:
The terminal strips must be wired before plugging them in!
Pluggable terminals strips that are not assigned must be
plugged on as well.
E82ZAFX013
Terminal data
Handling of pluggable
terminal strips
Use of pluggable terminal
strip with spring connection
Installation
6
6.4
6.4.3
6.4-6 EDSFEW EN 04/2005
6.4.3.4 CAN bus connection
2181FEW001K
1 6
5
9
Pin Plug assignment
1 6
5
9
1, 4, 5, 6, 8, 9 Not assigned
1 6
5
9
2 CAN-LO
1 6
5
9
3 CAN-GND
1 6
5
9
7 CAN-HI
TheCANbusmustbeterminatedbyresistors(120 )betweenCAN-LOWand
CAN-HIGH). The Sub-Dplug with integrated terminating resistor (order no.
EWZ0046, not included in the scope of supply) corresponds to the
recommendation DS 102-1 of CiA.
L
EW
Z0046
OFF
ON
O
F
F
O
N
ON
OFF

OUT IN IN IN
On Off On 120 120 120
L
EWZ0046
L
EWZ0046
L
EWZ0046
2181FEW004
Please observe our recommendations for signal cables:
Specification for the transmission cable
Total length 300 m 1000 m
Cable type LIYCY 2 x 2 x 0.5 mm
2
(twisted in pairs with shield)
CYPIMF 2 x 2 x 0.5 mm
2
(twisted in pairs with shield)
Cable resistance 80 /km 80 /km
Capacitance per unit
length
130 nF/km 60 nF/km
Assignment of the Sub-D plug
transmission cable
Installation
6
6.4
6.4.3
6.4-7 EDSFEW EN 04/2005
It is imperative that you comply with the permissible cable lengths.
1. Check for compliance with the overall cable length in Tab. 6.4-1.
The total cable length is specified by the baud rate.
Baud rate [kbit/s] Max. bus length [m]
20 3600
50 1400
125 550
250 250
500 110
1000 20
Tab. 6.4-1 Total cable length
2. Check for compliance with the segment cable length in Tab. 6.4-2.
The segment cable length is defined by the applied cable cross-section and
the number of participants. Without any repeaters, the segment cable
length corresponds to the total cable length.
Cable cross-section
Participant 0.25 mm
2
0.5 mm
2
0.75 mm
2
1.0 mm
2
2 240 m 430 m 650 m 940 m
5 230 m 420 m 640 m 920 m
10 230 m 410 m 620 m 900 m
20 210 m 390 m 580 m 850 m
32 200 m 360 m 550 m 800 m
63 170 m 310 m 470 m 690 m
100 150 m 270 m 410 m 600 m
Tab. 6.4-2 Segment cable length
3. Please compare both detected values.
If the value given in Tab. 6.4-2 is smaller than the total cable length givenin
Tab. 6.4-1, repeatersmust beapplied. Repeatersdividethetotal cablelength
into segments.
@ Note!
You will find more information on the structure of a CAN
network in the CAN communication manual.
Bus cable length
Installation
6
6.4
6.4.3
6.4-8 EDSFEW EN 04/2005
6.4.3.5 External modem connection
1 6
5
9
Name
1 6
5
9
Pin V.24 RS232 Signal Signal name Direction
1 6
5
9
1 109 CF DCD Data Carrier Detector Output
1 6
5
9
2 104 BB RD Received Data Output
1 6
5
9
3 103 BA TD Transmitted Data Input
1 6
5
9
4 108/2 CD DTR Data Terminal Ready Input
1 6
5
9
5 102 AB SG Signal Ground -
1 6
5
9
6 107 CC DSR Data Set Ready Output
1 6
5
9
7 105 CA RTS Request To Send Input
1 6
5
9
8 106 CB CTS Clear To Send Output
1 6
5
9
9 125 CE - Ring Indicator Output
Assignment for the RS232
interface
Installation
6
6.4
6.4.3
6.4-9 EDSFEW EN 04/2005
6.4.3.6 Telephone connection
2181FEW003C
Pin Name
2 Not assigned
3 TIP
4 RING
5 Not assigned
Assignment of telephone
Installation
6
6.4
6.4.3
6.4-10 EDSFEW EN 04/2005
6.4.3.7 Diagnostics interface
@ Note!
Please use only prefabricated cable.
Pin Name Signal
1 +UB18_DIAG Supply (keypad, PC coupler)
2 RTS+
Handshake basic device diagnostic device
3 RTS-
Handshake, basic device - diagnostic device
4 Tx+
Data basic device diagnostic device
5 Tx-
Data, basic device - diagnostic device
6 Rx+
Data diagnostic device basic device
7 Rx-
Data, diagnostic device - basic device
8 CTS+
Handshake diagnostic device basic device
9 CTS-
Handshake, diagnostic device - basic device
10 GND Supply (keypad, PC coupler)
Housing Shielding Shielding (connected to metal housing)
Assignment of the diagnostic
connector
Commissioning
Before switching on
6
6.5
6.5.1
6.5-1 EDSFEW EN 04/2005
6.5 Commissioning
6.5.1 Before switching on
_ Stop!
Prior to switching on the mains voltage, check the wiring for
completeness, short-circuit and earth fault.
The device is equipped with the following functions:
Automatic address assignment
Automatic detection of the baud rate
Both functions are used to prevent malfunctions in operation due to
incorrectly set user addresses and baud rate.
@ Note!
In default setting these functions are not activated.
Please refer to the related instructions on the codes
C0350: General address assignment (L 6.7-3)
C0351: Set baud rate (L 6.7-4)
Before the 2181 communication module is connected with the telephone
network, the country-specific code must be configured, if required.
@ Note!
The description of code C1208 must be observed (L 6.7-16).
Automatic address
assignment and automatic
detection of the baud rate
Configuration of
country-specific code
Commissioning
6
6.5
6.5.2
6.5-2 EDSFEW EN 04/2005
6.5.2 Commissioning with the system bus configurator
@ Note!
A window-compatible modem must be installed in the windows
system control.
The communication is executed via the TAPI interface.
6.5.2.1 Installing the software
The following minimum requirements of hardware and software must be
met to work with the communication module:
MicrosoftRWindowsR2000/XP
IBMR-compatible PC with IntelRPentiumR-266 processor or higher
128 MB main memory with Windows 2000/XP
The following Lenze programs allow for a communication via the
communication module :
Drive Server
Global Drive Control (GDC version 4.7 or higher)
Global Drive Loader
Global Drive PLC Developer Studio (DDS version 1.4 or higher)
@ Note!
One of the programs mentioned offer alternative
communication paths for CAN. In this case, please always select
the communication path OPC.
Systemrequirements
Available Lenze programs
Commissioning
6
6.5
6.5.2
6.5-3 EDSFEW EN 04/2005
@ Note!
The driver installation under Windows 2000/XP requires
administrator rights!
In order to introduce the 2180 communication module to the operating
system, it is necessary to install a driver.
The driver is bothincluded ineach of the Lenze programs mentionedbefore
and in the system bus configurator as of version 1.2. It is automatically
loaded during the installation or can be selected manually during the
installation.
@ Note!
The driver must always be installed separately if you use the
following program version:
Drive Server, version 1.1
Global Drive Control, version 4.7
Global Drive Loader, version 2.2
Global Drive PLC Developer Studio, version 2.2
The current driver can be found under the name Update
system bus configurator Vxx (xx: version number) in the
download area of the Lenze homepage
For this purpose proceed the following steps:
Save the driver of the Lenze homepage to your local hard
disk.
Install the Lenze programs that will communicate via the
2180 communication module.
Install the driver by following the instructions of the
installation program.
The Lenze system bus configurator for the convenient configuration of the
utilised system bus adapters is installed together with the driver for the
2180 communication module so that no additional installation is required.
Installing the required driver
Installation of the systembus
configurator
Commissioning
6
6.5
6.5.2
6.5-4 EDSFEW EN 04/2005
6.5.2.2 Configuring the communication module
Before the Lenze tools can communicate via communication module, it
must be configured accordingly.
To open the systembus configurator, select the following in the start menu
ProgramsLenzeCommunicationSystem bus configurator.
In contrast to the other communication modules the individual parameters
are not included in the index card Settings. Instead, an entry can be made
in the telephone book for each system to be remote-maintained. The
standard parameters as baud rate, parameter channel, andtime-out canbe
found there as well.
1. Select the communication module from the list in the system bus
configurator.
2. Double-click the corresponding line.
3. If you start the telephone book for the first time, some configurations
and the entries for all modems configured on the PC are executed.
4. Create an entry in the telephone book now appearing.
5. Here, enter the CAN parameters
6. Enter user name and password:
Standard user: Lenze
Standard password: Lenze
7. Enter the telephone number to be called.
Tip!
Some private branch exchanges and countries require a pause
during dial-up. The corresponding settings are included in the
documentations of the private branch exchange and PC modem.
8. Select the modem to be used.
9. Close the setting dialogue.
Steps to be taken for
configuring the
Commissioning
6
6.5
6.5.2
6.5-5 EDSFEW EN 04/2005
Now, the first dial-up of the communication module can be made fromthe
telephone book.
1. For this purpose, press the button Connect. Check the indicated
values and again select Connect.
2. Now, a dial-up and user authentication are executed.
3. After a successful dial-up it is checked whether the CAN parameters
configured on the PC are identical with those in the device. If not, an
adjustment will be executed.
4. After this, a small status window appears which displays the
connection status and the connection time. Via this window the
connection can also be separated again.
5. Return to the system bus configurator, select the index card General
and press the button Diagnostics. Now, the CAN bus can be searched
for nodes connected.
6. Confirm the safety instruction with Yes or select No to abort the
diagnostics.
When the communication module succeeded in communicating with the
corresponding bus nodes, the system bus node addresses of the bus nodes
found are listed in the field Device status.
If the communication module is not able to communicate with the bus
nodes, an error message is displayed.
The communication module answers with its CANaddress or with 0 if no
address exists (dependent on C00350). The data telegrams for
communicating with the communication module itself, however, are not
visible on the CAN bus.
@ Note!
Additional information about the configuration of the
communication module can be found in the online help of the
system bus configurator.
If the configuration of a communication module is successful, the Lenze
tools can use it for communication.
Only the selectionof the bus systemusedis performedinthe Lenze tools, all
system bus-specific settings and the selection of the communication
module are carried out exclusively via system bus configurator.
@ Note!
While some of the older program versions of the Lenze tools still
offer setting options for interrupt and I/O address, they are
meaningless in the context of the communication module.
After completing the
configuration
Commissioning
First switch-on
6
6.5
6.5.3
6.5-6 EDSFEW EN 04/2005
6.5.3 First switch-on
2181FEW001H
Fig. 6.5-1 Signalling on the front of the communication module
A
( )
YELLOW On The ModemCANis ready
(M)
Blinking Active communication over the telephone,
the ModemCANhas answered.
(E)
RED See L 6.5-7 ERR LED
(R)
GREEN RUNLED or diagnostic interface active
(P)
GREEN On The ModemCANis supplied with voltage.
Signalling
Commissioning
First switch-on
6
6.5
6.5.3
6.5-7 EDSFEW EN 04/2005
Status display (LED) Explanation
Connection status to the bus, two-coloured LED (green/red)
OFF Connection to the master not established
Green
CANopen status (Z)
Red
CANopen error (F)
Constant RED lighting
Z: Bus off
Quick BLINKING (flicker) Automatic baud rate detection is active Q ( )
GREEN BLINKING every 0.2 seconds
Z: Pre-Operational, F: None
1 x RED BLINKING 1 s OFF
Z: Pre-Operational, F: Warning Limit reached
1 x RED BLINKING, 1 s OFF
Z: Pre-Operational, F: Node Guard Event
Constant GREEN lighting
Z: Operational, F: None
Z: Operational, fault: Warning Limit reached
Z: Operational, F: Node Guard Event
Z: Operational, F: Sync Message Error
GREEN BLINKING every second
Z: Stopped, F: None
Z: Stopped, F: Warning Limit reached
Z: Stopped, F: Node Guard Event
Tab. 6.5-1 Signalling acc. to DR303-3
Signalling acc. to DR303-3
Commissioning
First switch-on
6
6.5
6.5.3
6.5-8 EDSFEW EN 04/2005
1. The LED is lit. The communication module performs some internal
initialisations.
2. The initialisation phase of the periphery starts:
LED (RUN-LED) is lit.
3. After the initialisation of the CAN controller:
LED (RUN-LED) is blinking.
4. After the initialisation of the internal or external modem:
LED Ais lit.
The device is now ready and can receive calls.
Signalling sequence after
switch on
Data transfer
6
6.6
6.6.1
6.6-1 EDSFEW EN 04/2005
6.6 Data transfer
6.6.1 Data transfer via CAN
2181FEW008
Master and drive controller communicate with each other by exchanging
data messages via the CANbus. The data area in the data message contains
either network management data, parameter data or process data.
In the drive controller, different communication channels are allocated to
the parameter data and process data.
The communication module ModemCAN 2181 is suitable (apart from the
transfer of IEC61131programs andapplicationdata, e.g. curvedata) onlyfor
the transfer of parameter data.
Parameter data
These are e. g.
Operating parameters
Diagnostics information
Motor data
As a rule the transfer of parameters is not as time-critical as the transfer of process data.
Parameter data channel (SDO, Service Data Objects)
Provide access to all Lenze codes and all CANopen indices.
Changes to parameters are normally saved automatically in the drive controller (note
C0003).
The structure of the CANmessages is described in the CANcommunication
manual.
Data transfer
6
6.6
6.6.1
6.6-2 EDSFEW EN 04/2005
@ Note!
For the value range of the Lenze code, please refer to the
operating instructions for the drive controller (see Code list).
When communication modules are used, the properties and the behaviour
of a drive controller integratedinto the network canbe changedby a higher
level master (e. g. a PLC).
The parameters to be changed are contained in the codes of Lenze drive
controllers.
The drive controller codes are addressed using the index on access via the
communication module .
Theindexfor theLenzecodenumber is intherangebetween16576(40C0
hex
)
and 24575 (5FFF
hex
).
Conversion formula:
Index [dec] = 24575 - Lenze code number
dec hex
Index = 24575 - Lenze code Index
hex
= 5FFF
hex
- (Lenze code)
hex
Index = 24575 - 1 = 24574 Index
hex
= 5FFF
hex
- 1 = 5FFE
hex
The communication module has two parameter data channels which are
both activated in the Lenze setting.
@ Note!
In order to establish the compatibility with CANopen, the second
parameter data channel must be switched off via code C1200,
see (L 6.7-8).
Access to the drive controller
codes
Indexing of codes using the
example
C0001 (operating mode)
CANopen parameter channels
Data transfer
Data transfer via the diagnostics interface
6
6.6
6.6.2
6.6-3 EDSFEW EN 04/2005
6.6.2 Data transfer via the diagnostics interface
@ Note!
This function is temporarily not available.
2181FEW007
The 9400 drive controller series has a diagnostic interface. This is a
hot-pluggable point-to-point connection. It enables parameter data,
IEC61131 programs and other application data to be exchanged.
The 9400 drive controller series has a routing function so that it is also
possibletoaccess, viathediagnosticinterface, lower level devicesconnected
together on a different bus.
Data transfer
Data transfer via modem
6
6.6
6.6.3
6.6-4 EDSFEW EN 04/2005
6.6.3 Data transfer via modem
2181FEW005
Data transfer by modemis performed using the PPP protocol that provides
secure data transmission.
The system bus configurator serves to automatically establish the
automatic dial-up connection on the PC side (see arrow).
Thebaudrateonthetelephonelineis adjustedbybothmodems. Depending
on the quality of the connection, it is reduced automatically, if required,
based on 33.6 kbits/s.
6
6.7
6.7-1 EDSFEW EN 04/2005
6.7 Lenze codes and CANopen objects
The behaviour of the communication module is defined by setting
parameters for (Lenze) codes. These codes are exchanged as part of a
message via the CAN bus.
In the following table you will find an overview of codes relevant for the
communicationmodule andthe CANobjects implemented. Please note the
references to additional information.
@ Note!
Convention for differentiating between the implemented
CANopen indices and Lenze codes:
CANopen index: I- + (index)
Lenze code: C + (code number)
Column Content Meaning
Code C0353 Code C0353
Subcode 1
2
Subcode 1 for the code
Subcode 2 for the code
Index 5E9E Necessary for addressing the code in bus messages.
Information as hexadecimal number.
Conversion:
24575 - Lenze code (C0353) = 24222
dec
= 5E9E
hex
Lenze Factory setting for the code (termed Lenze setting in the
following)
Selection 1 {1 %} 99
1, 2, 3, 5
T
For a range:
Minimum value {smallest increment/unit} maximum value
For fixed value
Display code (no configuration possible)
Important - Additional, important information on the code (bold
print: code designation in GDC)
Howto read the tables for
Lenze codes
6
6.7
6.7-2 EDSFEW EN 04/2005
Code Subcode Index
[hex]
Name
See
C0002 - 5FFD Load parameter set L 6.7-13
C0099 - 5F9C Display of the software version L 6.7-13
C0150 - 5F69 Status word L 6.7-13
C0200 - 5F37 Software manufacturers product code L 6.7-3
C0350 5EA1 CANnode address L 6.7-3
C0351 - 5EA0 CANbaud rate L 6.7-4
C0358 - 5E99 Reset node L 6.7-4
C0359 5E98 CANstatus L 6.7-5
C0360 1
2
5E97 CANtelegramcounter L 6.7-7
C0361 1
2
5E96 CANbus load L 6.7-7
C1200 5B4F Parameter data channel operating
mode
L 6.7-8
C1201 5B4E Communication time-out (CAN) L 6.7-8
C1202 5B4D Time limit for node search L 6.7-8
C1203 5B4C Repeat tests L 6.7-9
C1204 5B4B Password protection L 6.7-14
C1205 5B4A Call-back telephone number L 6.7-14
C1206 5B49 Modeminitialisation command L 6.7-15
C1207 5B48 Switch over internal/external modem L 6.7-15
C1208 5B47 Country code L 6.7-16
C1209 5B46 Detection of the baud rate L 6.7-9
C1213 5B42 Connection via CANor diagnostic
interface
L 6.7-13
C1215 5B40 Time exceeded during automatic baud
rate detection
L 6.7-9
C1223 5B38 User name L 6.7-16
C1225 5B36 Baud rate of the external modem L 6.7-16
C1226 5B35 Modemreset L 6.7-17
C1227 5B34 Delay time for search telegrams L 6.7-10
Index [
hex
] Subindex Name See
I-1000 0 Device type L 6.7-11
I-1001 0 Error register L 6.7-11
I-1017 - Producer heartbeat time L 6.7-11
I-1018 0...4 Identity object L 6.7-12
Lenze codes
CANopen objects
implemented
6
6.7
6.7.1
6.7-3 EDSFEW EN 04/2005
6.7.1 Description of the codes relevant for CAN
Code Subcode Index
[ ]
Possible settings Important
[hex]
Lenze Selection
C0200 - 5F37 - - Software manufacturers product
code
Data format: VS
Access: R
During initialisation of the module it is determined which device is
connected as a user based on the manufacturers product code.
Value displayed for the ModemCAN: 33S2181F_10000.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0350 5EA1 63 0 {1} 63
(127)
CAN node address
Data format: I32
Access: R/W
Max. address for communication
via
Lenze systembus : 63
CANopen: 127.
The node address can be set via the CAN bus using the code C0350.
If zero is used as the address, the communication module does not have a
dedicated node address. It can then not be addressed fromthe CANbus (no
parameter setting, node guarding etc.), but only serves as a dialling-in
feature for reading parameters via the CAN bus.
If the communicationmodule shouldhave anaddress, check, after the baud
rate has been detected, whether this address is still free. Then, the
implemented CANopen object 1000 is tried to be read. If another node
already has this address, another free address is selected automatically.
@ Note!
Node addresses in the range of 64 ... 127 can only be assigned if
the code C1200 is set to the value 0 (CANopen conformity).
Changes to the setting are applied after
Reset node or Reset communication via the bus system
Reset node using the code C0358
C0200:
Software manufacturers
product code
C0350:
General address assignment
6
6.7
6.7.1
6.7-4 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0351 - 5EA0 0 0
1
2
3
4
5
16
500 kbits/s
250 kbits/s
125 kbits/s
50 kbits/s
1000 kbits/s
20 kbits/s
autom.
detection
CAN baud rate
Data format: I32
Access: R/W
The baud rate over the CAN bus can be set using this code.
Changes to the setting are applied after:
A reset node command via the bus system
A reset node using the code C0358
Prior to accessing the CAN bus, the baud rate used is determined by the
communication module and compared with the baud rate configured.
If the two values are different, the baud rate determined is used. The baud
rate detected by the communicationmodule canbe readusing code C1209.
If there is no data traffic on the CAN bus, the baud rate cannot be
determined. The subsequent behaviour of the communication module
depends on the selection configured in code C0351:
Selection 0 ... 5
After a time-out that can be configured using code C1215, the CAN bus
is accessed with the baud rate configured.
Selection 16 (automatic detection of the baud rate)
The communication module does not access the bus until a baud rate
can be detected.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0358 - 5E99 0 0
1
No function
CANreset
Reset node
CANbus reset - set up nodal point
Data format: I32
Access: R/W
After a reset any changes to communication parameters such as baud rate
or node address are applied.
Entries with new baud rates or changes to the node address only become
valid after a node reset.
A node reset can be performed by:
Reset node using code C0358
C0351:
Set transfer rate
C0358:
Reset node
6
6.7
6.7.1
6.7-5 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0359 5E98 T 0
1
2
3
4
Operational
Pre-Operatio
nal
Warning
Bus Off
Stopped
CAN status
Status display
Data format: I32
Access: R
This code displays the current operating status of the CAN controller. Here
a differentiation is made between 4 states:
Selection 0: Operational
In this state the bus system is fully functional.
Selection 1: Pre-Operational
In this state only parameters (codes) can be transferred via the bus system.
It is not possible to exchange process data. To change to the Operational
state a network management message must be output on the bus.
A state change from Pre-operational to Operational can be made with
the following actions:
A drive is defined as the master using code C0352. When connecting
to the mains an automatic state change for the entire drive system is
performed after the defined boot-up time C0356/1.
Using code C0358 reset node (prerequisite: C0352 = 1).
Using the binary reset node input signal that can be set, e. g. using
the code C0364 via a terminal given an appropriate configuration
(prerequisite: C0352 = 1).
A network management message from a CAN master.
Selection 2: Warning
Error messages have been received if the state is Warning. The CANnode
is now only passive; no more data are sent from the drive controller.
The reason for this situation can be:
A missing bus terminator
Inadequate shielding
Potential differences at the ground connection for the control
electronics
An excessively high bus load
CAN node is not connected to the bus
C0359:
CAN status
6
6.7
6.7.1
6.7-6 EDSFEW EN 04/2005
Selection 3: Bus Off
The frequency of the erroneous messages has resulted in the CAN node
decoupling itself from the bus. It is possible to switch to the
Pre-Operational state with:
A trip reset
A reset node
Selection 4: Stopped
Only NMT telegrams can be received.
The state can be changed to Pre-Operational by:
Reset node via the code C0358
6
6.7
6.7.1
6.7-7 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0360 1
2
5E97 T 0 .... 4294967295 CAN
Telegramcounter (number of all
telegrams that are determined for
this node)
Counter value > 4294967295:
Start again at 0
/1: all messages sent
/2: all messages received
Data format: I32
Access: R
All CAN telegrams transmitted and received of this node are counted.
The counters have 32bits, i. e. whenavalue of 4294967295is exceeded, the
counting process starts again at 0.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0361 5E96 T 0 .... 100% CAN
Bus load
Data format: I32
Access: R
Using this code the percentage total bus loadcanbe determined. Erroneous
messages are not taken into account here.
@ Note!
The bus load for all devices involved should not exceed 80 %.
If other devices, e. g. decentralised inputs and outputs are
connected, these messages are also to be taken into account.
C0360:
Telegramcounter
C0361:
Bus load diagnostics
6
6.7
6.7.1
6.7-8 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1200 5B4F 2 0, 1 or 2 Operating mode - parameter data
channel
Data format: I32
Access: R/W
This code indicates which of the two parameter data channels is used to
communicate with other nodes. The unused parameter data channels can
be switched off, if required.
All Lenze controllers have two parameter data channels with different
addressing. Theaddress of the parameter channel 2is calculatedas follows:
Address of parameter data channel 2 =
Address of parameter data channel 1 + offset 64
Selection Accessible address range Active parameter data channels
0 1...127 SDO1
1 1...63 SDO1 / SDO2
2 65...127 SDO1 / SDO2
@ Note!
The selection 0 means that the bus is operating in compliance
with CANopen and there is no limitation on the address space.
In this case, the parameter data channel SDO2 is inactive.
zl
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1201 5B4E 1500 0 {1ms} 10000 Data format: I32
The time set defines the time frame withinwhicha CANnode must respond
to a request.
If there is no response of the node, the requesting module assumes that the
node is not available.
zl
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1202 5B4D 1000 0 {1ms} 10000 Data format: I32
For node search, the time set is regularly maintained. It must be selected
high enough to enable the nodes to have enough time to respond.
Otherwise, a too high value delays the search.
@ Note!
If required, the settings in C1202 must be adapted if the delay
time for search telegrams increased with code C1227.
C1200:
operating mode
C1201:
Communication time-out
(CAN)
C1202:
6
6.7
6.7.1
6.7-9 EDSFEW EN 04/2005
zl
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1203 5B4C 1 0 {1} 10 Data format: I32
The value to be set in code C1203 indicates the number of repetitions of
those CAN telegrams which have not reached the receiver.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1209 5B46 T 0
1
2
3
500 kbits/s
250 kbits/s
125 kbits/s
50 kbits/s
Detection of the baud rate
Data format: I32
Access: R
3
4
16
50 kbits/s
1000 kbits/s
nothing
detected
Code C1209 can be used to determine which transfer rate was detected on
the CAN bus.
When 16 is indicated, there is no data traffic on the CAN bus.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1215 5B40 1000 0 {1ms} 60000 Time exceeded during automatic
baud rate detection
Data format: I32
Access: R/W
By defining a time-out in code C1215, the baud rate (display with code
C1209) on the CAN bus can be detected.
The baud rate is not checked if the value configured in code C1215 is set to
zero.
When the time-out configured in code C1215 elapses, the CAN bus is
accessed (for further information and limitations: see description of code
C0351).
C1203:
Repeat tests
C1209:
Read bus baud rate
C1215:
Time-out (automatic baud
rate detection)
6
6.7
6.7.1
6.7-10 EDSFEW EN 04/2005
zl
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1227 - 5B34 0 0 {1ms} 100 Data
format:
I32
Selection Meaning
0 Quickest possible search
... ...
... ...
Searching the CANbus during the start of a PC programcan lead to faults if
a bus is heavily loaded. In order to prevent this, a delay time between the
transmissiontelegrams canbeset. This, however, leads toanincrease of the
total search time. If required, C1202 must be adapted accordingly.
C1227:
Delay time for search
telegrams
6
6.7
6.7.2
6.7-11 EDSFEW EN 04/2005
6.7.2 Description of the CANopen objects implemented
TheCANopenindexI-1000
hex
gives thedeviceprofilefor this device. It is also
possible to include additional information here that is defined in the device
profile itself. If no specific device profile is used, the content is 0000
hex
.
Index [
hex
I-1000 0 Device type U32 0 ... (2
32
- 1) ro
Bit assignment in the telegram data
5th byte 6th byte 7th byte 8th byte
LSB
Device profile number
MSB
Additional information
Reading the error register
Index [
hex
I-1001 0 Error register U8 0...255 ro
Error status for the following bit assignment in the data byte (U8):
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Error status
0 0 0 0 0 0 0 0 No error
0 0 0 0 0 0 0 1 Error in the
0 0 0 1 0 0 0 1 Communication error
Index [
hex
I-1017 - Producer heartbeat
time
U32 U 16 rw
The heartbeat message is sent cyclically by the heartbeat generator
(producer) to one or more recipients (consumers).
After configuringtheheartbeat producer time, theheartbeat protocol starts
at the transition from the NMT state INITIALISATION to the NMT state
PREOPERATIONAL (if predefined value > 0).
@ Note!
Unlike node / life guarding monitoring, the heartbeat protocol
does not contain a Remote Transmit Request (RTR).
It is therefore not necessary for the recipient to answer after a
heartbeat.
I-1000
hex
:
Device type
I-1001
hex
:
Error register
I-1017
hex
:
Producer heartbeat time
6
6.7
6.7.2
6.7-12 EDSFEW EN 04/2005
Entry of vendor ID
Index [
hex
] Subindex Name Data type Value range Authorisation
I-1018 0 ... 4 Identity object Identity Module-specific ro
The identification number for this object has been determined by
Organisation CAN in Automation e. V. and can be read out using this
object:
Subindex Meaning
0 Highest subindex
1 Vendor ID
2 Product code
3 Revision number
4 Serial number
I-1018
hex
:
Identity object
6
6.7
6.7.3
6.7-13 EDSFEW EN 04/2005
6.7.3 Description of the general codes
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0002 5FFD 0 0: Implemented
1: Load factory
calibration
Parameter set management
Data format: I32
Access: R
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0099 5F9C T Display: x.y Software version
Data format: FIX32
Access: R
The display designates
x: main version
y: index
Code Subcode Index
[ ]
[hex]
Lenze Selection
C0150 5F69 T Status word
Data format: B16
Access: R
The binary interpretation of the displayed decimal value reflects the bit
statuses of the status word:
Bit 0: Ready for operation
Bit 1: Dial-up connection is available
Bit 2: Internal error
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1213 5B42 0 0
1
CAN
Diagnostics
interface
Connection via CAN or diagnostics
interface
Data format: FIX32
Access: R/W
The fieldbus connection is to be entered in code C1213:
C 1213 = 0
Connection of ModemCAN 2181 and drive controller via the CAN bus.
C1213 = 1
Connectionof theModemCAN2181tothediagnostics interfaceonthedrive
controller 9400.
@ Note!
It is not possible to operate both connections on the
communication module in parallel.
C0002:
Parameter set management
C0099:
Software version
C0150:
Status word
C1213:
Fieldbus connection
Description of the codes relevant for the modem
6
6.7
6.7.4
6.7-14 EDSFEW EN 04/2005
6.7.4 Description of the codes relevant for the modem
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1204 5B4B - Blank: no password
protection
Password protection
Data format: VS
Access: W
CodeC1204serves toprotect thecommunicationmoduleModemCAN2181
against unauthorised access by assigning a password.
Duringdial-up, thepasswordsavedinthePCis comparedwiththepassword
saved in the communication module:
Dialling in is continued if both passwords are identical.
The dial-up will be interrupted immediately or after a short waiting
time when the passwords or user names are not identical (see code
C1223).
@ Note!
In code C1204 it is possible to enter a new password via the
CAN bus at any time or to enter no password by leaving the
selection field blank.
The password is not reset when loading the Lenze setting.
@ Note!
This function is temporarily not available.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1205 5B4A - Data format: VS
Access: R/W
Code C1205 serves to enter a telephone link (call-back telephone number)
which will be immediately called back after dial-up.
If there is notelephone number enteredinC1205, nocall-back is performed,
the connection remains and is directly used for remote maintenance.
@ Note!
The use of the call-back function requires administrator rights.
Changes of this code will only be effective by renewed mains
switching or modem reset (code C1226).
C1204:
Password
C1205:
Call-back telephone number
6
6.7
6.7.4
6.7-15 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze
C1206 5B49 AT&FE1Q&K3&D2&C1 Data format: VS
Access: R/W
@ Note!
The Lenze setting is sufficient to initialise the modem.
If, however, no connection could be established, it is possible to
adapt the initialisation command via suitable AT commands.
Only change the value of this code if it is really required!
A wrong initialisation command may make the dial-up
impossible. In this case, the Lenze setting of the modem must be
loaded and the AT commands entered before must be corrected.
Code C1206 provides the internal or external modemwith an initialisation
command consisting of several AT commands.
@ Note!
Tip!
The annex of this manual provides a part of the entire
commands for the communication module ModemCAN 2181.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1207 5B48 0 0 Internal
Modem
Switch over internal/external
modem
f
1 External
modem
Data format: FIX32
Access: R/W
It is possible to switch betweenan internal and external modemusing code
C1207.
This code can only be written via CAN.
@ Note!
C1206:
Modeminitialisation
C1207:
Switch over internal /
external modem
6
6.7
6.7.4
6.7-16 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1208 5B47 253 See
L 6.9-2
Data format: FIX32
Access: R/W
Using the code C1208, the code for the country in which the modemis used
can be entered.
The internal modemis approved for use inmany countries. However, as the
required features vary slightly, the modem must configure itself to the
relatedconditions. For thispurposeit isnecessarytoenter thecorresponding
country code. Within Europe the country code is the same.
@ Note!
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1223 5B38 Lenze User name
Data format: VS
Access: R/W
Code C1223 serves to enter a user name. The code is pre-assigned with the
user name Lenze by the Lenze setting.
@ Note!
The user name is not reset when loading the Lenze setting.
Code Subcode Index
[ ]
[hex]
Lenze Selection
C1225 5B36 3 0 9600 bit/s Data format: FIX32
/
1 19200 bit/s
Access: R/W
2 38400 bit/s
3 57600 bit/s
Code C1225 defines the baud rate via which the communication module
communicates with external modems. Most modems are provided with an
automatic baudrate recognitionso that this parameter does not need tobe
changed. Here, only in exceptional cases must the baud rate be set, which
theexternal modemhas asstandard. If theinitialisationwiththeconfigured
baud rate fails, a new one is automatically tried to be used.
@ Note!
C1208:
Country code
C1223:
User name
C1225:
Baud rate of the external
modem
6
6.7
6.7.4
6.7-17 EDSFEW EN 04/2005
Code Subcode Index
[ ]
[hex]
Lenze Selection
p
C1226 5B35 0 0: No function
1: Modemreset
Data format: I32
Access: R/W
Achange of the modemparameters will onlybe effectiveby renewedmains
switching or using the code C1226.
C1226:
Modemreset
Troubleshooting
6
6.8
6.8.1
6.8-1 EDSFEW EN 04/2005
6.8 Troubleshooting
Possible cause of error Diagnostics Remedy
The device is not switched on Power LED does not illuminate Check external voltage supply
CANbus error ERR LED is lit or blinking Check CANwiring
6.8.1 Signalling of the CANopen RUN LED and ERROR LED
The CANopen ERROR LED displays the status of the physical CAN level and
shows errors on the basis of missing CAN messages (SYNC, GUARD or
HEARTBEAT). It is lit red.
No. ERROR LED STATUS Description
1 OFF No error The device is ready for operation.
2 Individual
lighting up
Warning limit is
reached
At least one of the error counters of the CAN
controller has reached or exceeded the warning
level (too many error frames).
are running. (ERROR LED and RUNLED flicker
alternately).
4 Double
lighting up
Error control
event
A guard event (NMT slave or NMT master) or
heartbeat event (heartbeat consumer) has
occurred.
5 Triple lighting
up
Sync error The sync message has not been received within
the time configured for the time monitoring of
the communication cycle..
6 On Bus Off The CANcontroller is in the bus-off state.
The CANopen RUNLEDdisplays the CANopen-NMT status. It is lit up green.
No. CAN RUN LED STATUS Description
are running. (ERROR LED and RUNLED flicker
alternately). Optional
2 Single
lighting up
STOPPED The device in the STOPPED state.
3 Blinking PRE-OPERATION
AL
The device is in the PREOPERATIONAL state.
4 On OPERATIONAL The device is in the OPERATIONAL state.
CANopen ERROR LED
CANopen RUN LED
Troubleshooting
6
6.8
6.8.1
6.8-2 EDSFEW EN 04/2005
The following message states are distinguished:
Signalling Meaning
LED is lit On
LED is not lit OFF
LED flickers Isophase on and off with approx. 10 Hz: on for approx. 50 ms and off
for approx. 50 ms.
LED is blinking Isophase on and off with approx. 2.5 Hz: on for approx. 200 ms,
followed by off for approx. 200 ms.
Single lighting up of the
LED
A short lighting up (approx. 200 ms) followed by a long off phase
(approx. 1000 ms).
Double lighting up of
the LED
LED shortly lights up twice in one sequence (approx. 200 ms),
Triple lighting up of the
LED
LED shortly lights up thrice in one sequence (approx. 200 ms),
Message states and lighting
rates
Appendix
Modem standards
6
6.9
6.9.1
6.9-1 EDSFEW EN 04/2005
6.9 Appendix
6.9.1 Modem standards
Application range Name
Data transfer V.34
V.32bis
V.22bis
V.22
V.23
V.21
Bell212A
Bell103
Error correction V.42 (LAP-Mor MNP 2-4)
Data compression V.42bis p
MNP5
Appendix
Country list
6
6.9
6.9.2
6.9-2 EDSFEW EN 04/2005
6.9.2 Country list
The national telephone standards differ somewhat. For this reason the
communication assembly needs to be configured for use in certain
countries.
The modem used supports the following standards:
CTR21 (Common Technical Regulation):
This approval applies for all EU countries including Norway and
Switzerland. It is based on the TBR21 standard prepared by the ETSI
(European Telecommunications Standard Institute).
FCC Part 68 (Federal Communications Commission):
This approval applies for the USA.
Some countries require special adaptations which must be entered into the
decimal code with code C1208 for this device (see table below).
Thefollowinglistsprovides informationonthecountries inwhichthedevice
can be used in relation to telecommunication standards.
@ Note!
If the respective country is not in the list, only an external
modem that complies with the related national regulations is
allowed to be used.
Code
Country hex dec Approval
Argentina 07 7 available
Australia 09 9 available
Austria FD 253 CTR21
Belgium FD 253 CTR21
Brazil 16 22 available
Canada B5 181 available
Chile 99 153 available
China B5 181 available
Cyprus FD 253 CTR21
Czech Republic FD 253 CTR21
Denmark FD 253 CTR21
Estonia FD 253 CTR21
Finland FD 253 CTR21
France FD 253 CTR21
Germany FD 253 CTR21
Great Britain FD 253 available
Greece FD 253 CTR21
Greenland FD 253 CTR21
Hong Kong 99 153 available
Hungary FD 253 CTR21
India 99 153 available
Indonesia 99 153 available
Appendix
Country list
6
6.9
6.9.2
6.9-3 EDSFEW EN 04/2005
Approval
Code
Country Approval dec hex Country
Ireland FD 253 CTR21
Israel B5 181 CTR21
Italy FD 253 CTR21
Japan 00 0 available
Korea B5 181 available
Liechtenstein FD 253 CTR21
Luxembourg FD 253 CTR21
Malaysia 6C 108
Mexico B5 181 available
Netherlands FD 253 CTR21
NewZealand 7E 126 available
Norway FD 253 CTR21
Philippines B5 181 available
Poland 99 153 available
Portugal FD 253 CTR21
Russia B5 181 available
Singapore 96 156 available
Slovakia FD 253 CTR21, in preparation
Slovenia FD 253 available
South Africa 9F 159
Spain FD 253 CTR21
Sweden FD 253 CTR21
Switzerland FD 253 CTR21
Taiwan FE 254 available
Turkey FD 253 available
USA B5 181 available
Appendix
AT commands
6
6.9
6.9.3
6.9-4 EDSFEW EN 04/2005
6.9.3 AT commands
6.9.3.1 General modem control commands
Controls the preferred error-correction mode to be negotiated in a
subsequent data connection. This command is affected by the OEM
firmware configuration.
Command Default Defined values Result codes
\N 5 \N0 Selects normal speed buffered mode
(disables error-correction mode). (Forces
&Q6).
OK
Otherwise
ERROR
\N1 Serial interface selected: Selects direct mode
and is equivalent to &M0, Q0 mode of
operation. (Forces &Q0). Parallel interface
selected: Same as \N0.
\N2 Selects reliable (error correction) mode. The
modemwill first attempt an LAPMand then
an MNP connection. Failure to make a
reliable connection results in the modem
hanging up.
(Forces &Q5, S36=4 and S48=7).
\N3 Selects auto-reliable mode. This operates the
same as \N2 except failure to make a reliable
connection results in the modemfalling back
to the normal speed buffered mode. (Forces
&Q5, S36=7 and S48=7).
\N4 Selects the LAPMerror-correction mode.
Failure to make an LAPMerror-correction
connection results in the modemhanging up.
(Forces &Q5 and S48=0). Note: The K1
command can override the \N4 command.
\N5 Selects MNP error-correction mode. Failure to
make an MNP error-correction connection
results in the modemhanging up. (Forces
&Q5, S36=4 and S48=128).
The modem loads the factory default configuration (profile). The factory
defaults areidentifiedfor eachcommandandintheS-parameter parameter
descriptions. A configuration (profile) consists of a subset of S-parameters.
- - &F0 Restore factory configuration 0. OK
ERROR if the
&F Restore factory configuration 1.
ERROR if the
modemis
connected.
Selects which user profile which will be used after a hard reset.
&Y - &Y0 The modemwill use profile 0. OK
ERROR if
<value> > 1 or
NVRAMis not
&Y1 The modemwill use profile 1.
NVRAMis not
installed or is
not
operational.
Command: \N
Operating mode - error
correction
Command: &F
Restore factory configuration
(profile)
Command: &Y
Designate a default reset
profile
Appendix
AT commands
6
6.9
6.9.3
6.9-5 EDSFEW EN 04/2005
Saves the current (active) configuration (profile) including S-parameters in
one of the two user profiles in NVRAM, as denoted by the parameter value.
This commandwill yieldanerror message if the NVRAMis not installed or is
not operational as detectedby the NVRAMtest. The current configurationis
comprised of a list of storable parameters illustrated in the &V commands.
These settings are restored to the active configuration upon receiving a
Z-command or at power up. (See &Y command).
&W 0 &W0 Store the current configuration as profile 0. OK
Otherwise
&W1 Store the current configuration as profile 1.
Otherwise
ERROR
Command: &W
Store current configuration
Appendix
AT commands
6
6.9
6.9.3
6.9-6 EDSFEW EN 04/2005
6.9.3.2 Interface commands for the DEE modem
Selects thesubset of theresult codemessages usedbythemodemtoinform
the DEE of the results of commands. Blind dialing is enabled or disabled by
country parameters. If the user wants to enforce dial tone identification, a
W can be placed in the dial string (see D-command which is not described
in this Manual). The information below is based upon the default
implementation of the X results table. If the modem is in Faksimile mode
(+FCLASS=1, 1.0 or 2), the only message sent to indicate a connection is
CONNECT without a speed indication.
X 4 X0 Disables reporting of busy tones unless
forced otherwise by country requirements;
send only OK, CONNECT, RING, NOCARRIER,
ERROR and NOANSWER result codes. Blind
dialing is enabled/disabled by country
parameters. If busy tone detection is
enforced and busy tone is detected, NO
CARRIER is reported. If dial tone detection is
enforced or selected and dial tone is not
detected, NOCARRIER will be reported
instead of NODIAL TONE. The value 000b is
written to S22 bits 6, 5 and 4, respectively.
OK
Otherwise
ERROR
X1 Disables reporting of busy tones unless
forced otherwise by country requirements:
send only OK, CONNECT, RING, NOCARRIER,
ERROR and NOANSWER and CONNECT XXXX
(XXXX = rate). Blind dialing enabled/disabled
by country parameters. If busy tone detection
is enforced and busy tone is detected, NO
CARRIER is will be reported instead of BUSY. If
dial tone detection is enforced or selected
and dial tone is not detected, NOCARRIER
will be reported instead of NODIAL TONE.
The value 100b is written to S22 bits 6, 5 and
4, respectively.
X3 Enables reporting of busy tones; send only
OK, CONNECT, RING, NOCARRIER, ERROR, NO
ANSWER and CONNECT XXXX. Blind dialing is
enabled/disabled by country parameters. If
dial tone detection is enforced and dial tone
is not detected, NOCARRIER will be reported.
The value 110b is written to S22 bits 6, 5 and
4, respectively.
X4 Enables reporting of busy tones; send all
messages. The value 111b is written to S22
bits 6, 5 and 4, respectively.
Command: X
Extended result codes
Appendix
AT commands
6
6.9
6.9.3
6.9-7 EDSFEW EN 04/2005
6.9.3.3 Call control commands
Forces DTMF dialing until the next P dial modifier or P command is received.
ThemodemsetsanS-parameter bit toindicatethat eachsubsequent dialing
should be conducted in tone mode. The DP command (not described in this
manual) overrides this command. Clears S14 bit 5. This command may not
be permitted in some countries. (See P command).
T OK
Forces pulse dialing until the next T dial modifier or T command is received.
Sets S14 bit 5. As soon as a dial command is executed, which explicitly
specifies a dialing mode for that particular call (e. g. ATDT...), this command
is overridden so that all future dialing will be tone dialled. (See T
command).This command may not be permitted in some countries.
P OK
This command causes the modem to generate the guard tone selected by
this command(DPSKmodulationmodes only). Theparameter value, if valid,
is written to S23 bits 6 and 7. This command may not be permitted in some
countries.
&G 0 &G0 Disables guard tone (default). <value> = 0 to 2
&G1 Disables guard tone.
Otherwise
ERROR
&G2 Selects 1800 Hz guard tone.
ERROR
Determines the make/break ratio used during pulse dialing. The default is
country-dependent. Theparameter value, if valid, is writtentoS28bits 3and
4.
&P 0 &P0 Selects 39%-61%make/break ratio at 10
pulses per second.
OK
Otherwise
&P1 Selects 33%-67%make/break ratio at 10
pulses per second.
ERROR
pulses per second.
pulses per second.
Command: T
Set tone dial default
Command: P
Set pulse dial default
Command: &G
Select guard tone
Command: &P
Select pulse dial make/break
ratio
Appendix
AT commands
6
6.9
6.9.3
6.9-8 EDSFEW EN 04/2005
6.9.3.4 Modulation control commands
This extended-format compound parameter controls the manner of
operation of the modulation capabilities in the modem. It accepts six
subparameters. Syntax:
+MS=[<carrier>[,<automode>[,<min_tx_rate>[,<max_tx_rate>
[,<min_rx_rate> [,<max_rx_rate>]]]]]] Where possible <carrier>,
<min_tx_rate>, <max_tx_rate>, <min_rx_rate> and <max_rx_rate> are
listed in the following table:
Modulation <carrier> Possible (<min_rx_rate>, <min_rx_rate>, (<min_tx_rate>)
and <max_tx_rate>) rates (bps)
Bell 103 B103 300
Bell 212 B212 1200 Rx/75 Tx or 75 Rx/1200 Tx
V.21 V21 300
V.22 V22 1200
V.22bis V22B 2400 or 1200
V.23 V23C 1200
V.32 V32 9600 or 4800
V.32bis V32B 14400, 12000, 9600, 7200, or 4800
V.34 V34 33600, 31200, 28800, 26400, 24000, 21600, 19200, 16800,
14400, 12000, 9600, 7200, 4800, or 2400
56K K56 56000, 54000, 52000, 50000, 48000, 46000, 44000, 42000,
40000, 38000, 36000, 34000, 32000
V.90 V90 56000, 54667, 53333, 52000, 50667, 49333, 48000, 46667,
45333, 44000, 42667, 41333, 40000, 38667, 37333, 36000,
34667, 33333, 32000, 30667, 29333, 28000
V.92
downstream
V92 56000, 54667, 53333, 52000, 50667, 49333, 48000, 46667,
45333, 44000, 42667, 41333, 40000, 38667, 37333, 36000,
34667, 33333, 32000, 30667, 29333, 28000
V.92
upstream
V92 48000, 46667, 45333, 44000, 42667, 41333, 40000, 38667,
37333, 36000, 34667, 33333, 32000, 30667, 29333, 28000,
26667, 25333, 24000
Note: Some <carrier> values may not be supported by certain modemmodels. For example,
modemmodels supporting V92 do not support K56.
Tab. 6.9-1 +MS command supported rates
Command: +MS
Modulation selection
Appendix
AT commands
6
6.9
6.9.3
6.9-9 EDSFEW EN 04/2005
+MS <carrier>
A string that specifies the preferred modemcarrier
to use in originating or answering a connection.
<carrier> values are strings of up to eight
characters, consisting only of numeric digits and
upper case letters. <carrier> values for ITU standard
modulations take the form: <letter><1-4
digits><other letters as needed>. Defined values are
listed in Tab. 6.9-1.
OK - Valid
subparameter
string
Otherwise
ERROR
<automode>
A numeric value which enables or disables
automatic modulation negotiation (ITU-T V.32bis
Annex A or V.8). 0 = Automode disabled. 1 =
Automode enabled (default).
<min_rx_rate> and <max_rx_rate>
Numeric values which specify the lowest
(<min_rx_rate>) and highest (<max_rx_rate>) rate
at which the modemmay establish a receive
connection. May be used to condition distinct limits
for the receive direction as distinct fromthe
transmit direction. Values for this subparameter are
decimal encoded, in units of bit/s. The possible
values for each modulation are listed in Tab. 6.9-1.
Actual values will be limited to possible values
corresponding to the entered <carrier> and fallback
<carrier> values as determined during operation.
(Default = lowest (<min_rx_rate>) and highest
(<max_rx_rate>) rate supported by the selected
carrier).
<min_tx_rate> and <max_tx_rate>
Numeric values which specify the lowest
(<min_rx_rate>) and highest (<max_rx_rate>) rate
at which the modemmay establish a transmit
connection. Non-zero values for this subparameter
are decimal encoded, in units of bit/s. The possible
values for each modulation are listed in Tab. 6.9-1.
Actual values are limited to possible values
corresponding to the entered <carrier> and fallback
<carrier> values as determined during operation.
(Default = lowest (<min_tx_rate>) and highest
(<max_tx_rate>) rate supported by the selected
carrier).
Report commands
+MS? Reports current rates
Response:
+MS:<carrier>,<automode>,<min_tx_rate>, <max_tx_rate>,
<min_rx_rate>,<max_rx_rate> Note:The current active settings are reported
under control of the +MR parameters.
Example:
+MS: K56, 1,300,33600,300,56000 for default values.
This example allows maximumsystemflexibility to determine optimal receive
and transmit rates during operation.
+MS=? Reports supported range of parameter values
Response:
+MS: (< carrier> range),(<automode> range),(<min_tx_rate>
range),(<max_tx_rate> range),(<min_rx_rate> range),(<max_rx_rate> range)
Example 1:
+MS:(B103,B212,V21,V22,V22B,V23C,V32,V32B,V34,
K56,V90),(0,1),(300-33600),(300-33600),(300-56000),(300- 56000)
Example 2:
+MS:(B103,B212,V21,V22,V22B,V23C,V32,V32B,V34,
V90,V92),(0,1),(300-33600),(300-33600),(300-56000),(300- 56000)
Appendix
AT commands
6
6.9
6.9.3
6.9-10 EDSFEW EN 04/2005
Whenthemodemisconfiguredtoalloweither option, themodemwill select
Bell or CCITTmodulationsfor alinespeedconnectionof 300or 1200bps. Any
other linespeedwill useaCCITTmodulationstandard. Theparameter value,
if valid, is written to S27 bit 6.
B 0 B0 Selects CCITT operation at 300 or 1200 bps
during call establishment and a subsequent
connection (default).
OK
Otherwise
ERROR
B1 Selects BELL operation at 300 or 1200 bps
during call establishment and a subsequent
connection.
Command: B
CCITT or Bell
Appendix
AT commands
6
6.9
6.9.3
6.9-11 EDSFEW EN 04/2005
6.9.3.5 Data compression commands
Enables or disables data compression negotiation. The modem can only
performdata compression on an error-corrected link. The parameter value,
if valid, is written to S41 bits 0 and 1.
%C %C0 Disables data compression. Resets S46 bit 1. OK
%C1 Enables MNP 5 data compression
negotiation. Resets S46 bit 1.
ERROR
%C2 Enables V. 42bis data compression. Sets S46
bit 1.
%C3 Enables both V.42bis and MNP 5 data
compression. Sets S46 bit 1 (default).
Command: %C
Enable/disable data
compression
Appendix
AT commands
6
6.9
6.9.3
6.9-12 EDSFEW EN 04/2005
6.9.3.6 S-registers
Certainmodemvalues, or parameters, arestoredinmemorylocationscalled
S-registers. Use the S-command (not described in this manual) to read or to
alter the contents of S-registers (see previous section). *Register value may
be stored on one of the two user profiles with the command &W.
Register Unit Range Default Description
S0 1 ring 0 - 255 0 Number of rings to auto-answer:
Sets the number of rings until the modemanswers.
ATS0=0 disables the auto-answer completely. *
S3 decimal 0 - 127 13 (^M) Carriage return character:
Sets the command line and result code terminator
character. Pertains to asynchronous operation only.
S4 decimal 0 - 127 10 (^J) Line feed character:
Sets the character recognised as a line feed. Pertains to
asynchronous operation only. The line feed control
character is output after the carriage return control
character if verbose result codes are used.
S6 seconds 2 - 255 2 Wait time before dialing or for dial tone:
1. Sets the length of time, in seconds, that the modem
will wait before starting to dial after going off-hook
when blind dialing. This operation, however, may be
affected by some ATX options according to country
restrictions. The Wait for dial tone call progress
feature (W dial modifier in the dial string) will
override the value in register S6 (when configured for
US).
will wait for dial tone when encountering a W dial
modifier before returning NODIAL TONE result code.
(W class). Default is country-dependent. The modem
always pauses for a minimumof 2 seconds, even if
the value of S6 is less than 2 seconds.
S7 seconds 1 - 255* 50 Wait time for carrier, silence, or dial tone:
will wait for carrier before hanging up. The timer is
started when the modemfinishes dialing (originate),
or 2 seconds after going off-hook (answer). In
originate mode, the timer is reset upon detection of
answer tone if allowed by country restrictions.
2. Sets the length of time, in seconds, that modemwill
wait for silence when encountering the @dial
modifier before continuing with the next dial string
parameter.
will wait for dial tone when encountering a W dial
modifier before continuing with the next dial string
parameter (US model). The default is
country-dependent. *
S8 seconds 2 - 255 2 Pause time for dial delay:
Sets the time, in seconds, that the modemmust pause
when the , dial modifier is encountered in the dial
string. *
Appendix
AT commands
6
6.9
6.9.3
6.9-13 EDSFEW EN 04/2005
Description Default Range Unit Register
S10 0.1 s 1 - 255 14 Lost carrier to hang up delay:
Sets the length of time, in tenths of a second, that the
modemwaits before hanging up after a loss of carrier.
This allows for a temporary carrier loss without causing
the modemto disconnect. When register S10 is set to
255, the modemfunctions as if a carrier is always
present. *
The actual interval the modemwaits before
disconnecting is the value in register S10 minus the
value in register S9. Therefore, the S10 value must be
greater than the S9 value or else the modemdisconnects
before it recognises the carrier..
Note: For call waiting detection, if the modemis set to
US country code and S10 >=16, then the modemwill
detect the call waiting tone and hang-up the line. If S10
<16, the modemwill not detect call waiting tone.
* Register value may be stored on one of two user profiles with the command &W.
Index
6
6.10
6.10-1 EDSFEW EN 04/2005
6.10 Index
A
Ambient temperature, 6.3-1
Appendix, 6.9-1
Application range, 6.2-1
Automatic baud rate detection, 6.7-9
B
Baud rate of the external modem, 6.7-16
Bus cable length, 6.4-7
Bus load diagnostics, 6.7-7
C
C0002, Parameter set management, 6.7-13
C0099, Software version, 6.7-13
C0150, status word, 6.7-13
C0200, Software manufacturers product code, 6.7-3
C0350, General address assignment, 6.7-3
C0351
- Baud rate setting, 6.7-4
- Set transfer rate, 6.7-4
C0358, Reset node, 6.7-4
C0359, CANstatus, 6.7-5
C0360, telegramcounter, 6.7-7
C0361, Bus load diagnostics, 6.7-7
C1200, parameter data channel operating mode, 6.7-8
C1201, communication time-out (CAN), 6.7-8
C1202, time limit for node search, 6.7-8
C1203, repeat tests, 6.7-9
C1204, Password, 6.7-14
C1205, CALL-back telephone number, 6.7-14
C1206, Modeminitialisation, 6.7-15
C1207, Switch over internal / external modem, 6.7-15
C1208, Country code, 6.7-16
C1209, Read bus baud rate, 6.7-9
C1213, Fieldbus connection, 6.7-13
C1215
- automatic baud rate detection, 6.7-9
- Time-out, 6.7-9
C1223, country code, 6.7-16
C1225, baud rate of the external modem, 6.7-16
C1226, modemreset, 6.7-17
C1227, delay time for search telegrams, 6.7-10
Cable lengths, 6.4-7
Cable resistance, 6.4-6
Cable specification, 6.4-6
Cable type, 6.4-6
Cable-cross section, 6.4-7
CALL-back telephone number, 6.7-14
CANstatus, 6.7-5
CANopen objects, 6.7-1
CANopen objects implemented, 6.7-2
CANopen parameter channels, 6.6-2
Capacitance per unit length, 6.4-6
Climatic conditions, 6.3-1
6.6-2
Code numbers / index, Conversion, 6.6-2
Commissioning, 6.5-1
- Before you start, 6.1-1
Commissioning with the systembus configurator, 6.5-2
Communication time-out (CAN), 6.7-8
Communication via CAN, 6.4-3
Communication via the diagnostics interface (9400), 6.4-4
Connections, 6.4-1
Country code, 6.7-16
D
Data transfer, 6.6-1
Data transfer via modem, 6.6-4
Data transfer via the diagnostics interface, 6.6-3
Delay time for search telegrams, 6.7-10
Description of the CANopen objects implemented, 6.7-11
Description of the codes relevant for CAN, 6.7-3
Description of the codes relevant for the modem, 6.7-14
Description of the general codes, 6.7-13
Device type, 6.7-11
Dimensions, 6.3-3
E
Electrical installation, 6.4-3
Elements of the communication module, 6.4-1
Error register, 6.7-11
Index
6
6.10
6.10-2 EDSFEW EN 04/2005
Examples, Indexing of Lenze codes, 6.6-2
F
Features, 6.2-1
Fieldbus connection, 6.7-13
First switch-on, 6.5-6
G
General data, 6.3-1
H
Hardware version, Type code, 6.2-1
I
I-1000, Device type, 6.7-11
I-1001, Error register, 6.7-11
I-1017, Producer heartbeat time, 6.7-11
I-1018, Identity object, 6.7-12
Identification, 6.2-1
Identity object, 6.7-12
Index, Conversion, 6.6-2
Indexing of Lenze codes, 6.6-2
Installation, 6.4-1
- Electrical, 6.4-3
- Mechanical, 6.4-2
Installation of required drivers, 6.5-3
Installation of the systembus configurator, 6.5-3
L
Lenze codes, 6.7-1, 6.7-2
M
Mechanical installation , 6.4-2
Modeminitialisation, 6.7-15
Modemreset, 6.7-17
N
Node address, 6.7-3
O
Operating conditions, 6.3-1
Overall cable length, 6.4-7
P
Parameter data channel operating mode, 6.7-8
Parameter set management, 6.7-13
Password, 6.7-14
Pluggable terminal strip, Use, spring connection, 6.4-5
Pluggable terminal strips, handling, 6.4-5
Pollution degree, 6.3-1
Producer heartbeat time, 6.7-11
R
Rated data, 6.3-2
Read bus baud rate, 6.7-9
Repeat tests, 6.7-9
Reset node, 6.7-4
S
Segment cable length, 6.4-7
Signalling, 6.5-6
Signalling acc. to DR303-3, 6.5-7
Software manufacturers product code, 6.7-3
Software version, 6.7-13
- Type code, 6.2-1
Specification of the transmission cable, 6.4-6
Status word, 6.7-13
Switch over internal / external modem, 6.7-15
Systemrequirements, 6.5-2
T
Technical data, 6.3-1
Telegramcounter, 6.7-7
Terminal data, 6.4-5
Terminals, data, 6.4-5
Time limit for node search, 6.7-8
Time-out, 6.7-9
Transmission cable, specification, 6.4-6
Troubleshooting, 6.8-1
Type code, 6.2-1
Type of protection, 6.3-1
U
User name, 6.7-16
Index
6
6.10
6.10-3 EDSFEW EN 04/2005
V
Validity of the Instructions, 6.2-1
Voltage supply, 6.4-5
Appendix
Content
7
7-1 EDSFEW EN 04/2005
7 Appendix
This part of the Communication Manual includes additional
information on Lenze products which can be used for remote
maintenance.
Content
Software Manual DriveServer
Software Manual Busserver S7
Appendix 7
7-2 EDSFEW EN 04/2005
A
Ambient conditions, 5.3-1
Ambient temperature, 5.3-1, 6.3-1
Appendix, 6.9-1
Application, as directed, 1.3-4
application as directed, 1.3-4
Application range, 5.2-1, 6.2-1
Automatic baud rate detection, 5.7-11, 6.7-9
B
Baud rate of the external modem, 6.7-16
Bus cable length, 5.4-6, 6.4-7
Bus load diagnostics, 5.7-9, 6.7-7
C
C0002, Parameter set management, 5.7-3, 6.7-13
C0093, Type, 5.7-3
C0099, Software version, 5.7-3, 6.7-13
C0150, status word, 5.7-3, 6.7-13
C0200, Software manufacturers product code, 5.7-3, 6.7-3
C0202, MPCs, 5.7-4
C0350, General address assignment, 5.7-5, 6.7-3
C0351
- Baud rate setting, 5.7-6, 6.7-4
- Set transfer rate, 5.7-6, 6.7-4
C0358, Reset node, 5.7-6, 6.7-4
C0359, CAN status, 5.7-7, 6.7-5
C0360, telegramcounter, 5.7-9, 6.7-7
C0361, Bus load diagnostics, 5.7-9, 6.7-7
C1200, parameter data channel operating mode, 5.7-10,
6.7-8
C1201, communication time-out (CAN), 5.7-10, 6.7-8
C1202, time limit for node search, 5.7-10, 6.7-8
C1203, repeat tests, 5.7-11, 6.7-9
C1204, Password, 6.7-14
C1205, CALL-back telephone number, 6.7-14
C1206, Modeminitialisation, 6.7-15
C1207, Switch over internal / external modem, 6.7-15
C1208, Country code, 6.7-16
C1209, Read bus baud rate, 5.7-11, 6.7-9
C1210, IP address, 5.7-15
C1211, subnet mask, 5.7-16
C1213, Fieldbus connection, 6.7-13
C1214, MAC-ID, 5.7-16
C1215
- automatic baud rate detection, 5.7-11, 6.7-9
- Time-out, 5.7-11, 6.7-9
C1223, country code, 6.7-16
C1224, gateway, 5.7-17
C1225, baud rate of the external modem, 6.7-16
C1226, modemreset, 6.7-17
C1227, delay time for search telegrams, 5.7-12, 6.7-10
Cable lengths, 5.4-6, 6.4-7
Cable resistance, 5.4-5, 6.4-6
Cable specification, 5.4-5, 5.4-7, 6.4-6
Cable type, 5.4-5, 6.4-6
Cable-cross section, 5.4-6, 6.4-7
CALL-back telephone number, 6.7-14
CAN status, 5.7-7, 6.7-5
CANopen objects, 5.7-1, 6.7-1
CANopen objects implemented, 5.7-2, 6.7-2
CANopen parameter channels, 5.6-2, 6.6-2
Capacitance per unit length, 5.4-5, 6.4-6
CE conformity, 1.3-4
Climatic conditions, 5.3-1, 6.3-1
5.6-2, 6.6-2
Code numbers / index, Conversion, 5.6-2, 6.6-2
Commissioning, 5.5-1, 6.5-1
- Before you start, 5.1-1, 6.1-1
Commissioning with the systembus configurator, 5.5-1,
6.5-2
Commissioning with the web server, 5.5-5
Communication time-out (CAN), 5.7-10, 6.7-8
Communication via CAN, 6.4-3
Communication via the diagnostics interface (9400), 6.4-4
Conformity, 1.3-4
Connections, 5.4-1, 6.4-1
Controller
- application as directed, 1.3-4
- labelling, 1.3-4
Country code, 6.7-16
D
Data transfer, 5.6-1, 6.6-1
Appendix 7
7-3 EDSFEW EN 04/2005
Data transfer via Ethernet, 5.6-3
Data transfer via modem, 6.6-4
Data transfer via the diagnostics interface, 6.6-3
Definition of notes used, 3.3-1
Delay time for search telegrams, 5.7-12, 6.7-10
Description of the CANopen objects implemented, 5.7-13,
6.7-11
Description of the codes important for the Ethernet
interface, 5.7-15
Description of the codes relevant for CAN, 5.7-5, 6.7-3
Description of the codes relevant for the modem, 6.7-14
Description of the general codes, 5.7-3, 6.7-13
Device type, 5.7-13, 6.7-11
Dimensions, 5.3-3, 6.3-3
E
Electrical installation, 5.4-3, 6.4-3
Elements of the communication module, 5.4-1, 6.4-1
Error register, 5.7-13, 6.7-11
Examples, Indexing of Lenze codes, 5.6-2, 6.6-2
F
Features, 5.2-1, 6.2-1
Fieldbus connection, 6.7-13
First switch-on, 5.5-11, 6.5-6
G
Gateway, 5.7-17
General data, 5.3-1, 6.3-1
Guide, 2.1-1
H
Hardware version, Type code, 5.2-1, 6.2-1
I
I-1000, Device type, 5.7-13, 6.7-11
I-1001, Error register, 5.7-13, 6.7-11
I-1017, Producer heartbeat time, 5.7-13, 6.7-11
I-1018, Identity object, 5.7-14, 6.7-12
Identification, 5.2-1, 6.2-1
Identity object, 5.7-14, 6.7-12
Index, Conversion, 5.6-2, 6.6-2
Indexing of Lenze codes, 5.6-2, 6.6-2
Installation, 5.4-1, 6.4-1
- Electrical, 5.4-3, 6.4-3
- Mechanical, 5.4-2, 6.4-2
Installation of required drivers, 5.5-2, 6.5-3
Installation of the systembus configurator, 5.5-2, 6.5-3
IP address, 5.7-15
L
Labelling, controller, 1.3-4
Legal regulations, 1.3-4
Lenze codes, 5.7-1, 5.7-2, 6.7-1, 6.7-2
Liability, 1.3-5
M
MAC-ID, 5.7-16
Manufacturer, 1.3-4
Mechanical installation , 5.4-2, 6.4-2
Modeminitialisation, 6.7-15
Modemreset, 6.7-17
MPCs, 5.7-4
N
Node address, 5.7-5, 6.7-3
Notes, definition, 3.3-1
O
Operating conditions, 5.3-1, 6.3-1
Operator, 3.1-1
Overall cable length, 5.4-6, 6.4-7
P
Parameter data channel operating mode, 5.7-10, 6.7-8
Parameter set management, 5.7-3, 6.7-13
Password, 6.7-14
Personnel, qualified, 3.1-1
Pluggable terminal strip, Use, spring connection, 5.4-4,
6.4-5
Pluggable terminal strips, handling, 5.4-4, 6.4-5
Pollution degree, 5.3-1, 6.3-1
Producer heartbeat time, 5.7-13, 6.7-11
Protective insulation, 5.3-2
Appendix 7
7-4 EDSFEW EN 04/2005
R
Rated data, 6.3-2
Read bus baud rate, 5.7-11, 6.7-9
Repeat tests, 5.7-11, 6.7-9
Reset node, 5.7-6, 6.7-4
S
Safety instructions, 3-1
- definition, 3.3-1
- design, 3.3-1
- general, 3.2-1
Segment cable length, 5.4-6, 6.4-7
Signalling, 5.5-11, 6.5-6
Signalling acc. to DR303-3, 5.5-12, 6.5-7
Software manufacturers product code, 5.7-3, 6.7-3
Software version, 5.7-3, 6.7-13
- Type code, 5.2-1, 6.2-1
Specification of the transmission cable, 5.4-5, 5.4-7, 6.4-6
Status word, 5.7-3, 6.7-13
Subnet mask, 5.7-16
Switch over internal / external modem, 6.7-15
Systemrequirements, 5.5-1, 6.5-2
T
Technical data, 5.3-1, 6.3-1
Telegramcounter, 5.7-9, 6.7-7
Terminal data, 5.4-4, 6.4-5
Terminals, data, 5.4-4, 6.4-5
Time limit for node search, 5.7-10, 6.7-8
Time-out, 5.7-11, 6.7-9
Transmission cable, specification, 5.4-5, 5.4-7, 6.4-6
Troubleshooting, 5.8-1, 6.8-1
Type, 5.7-3
Type code, 5.2-1, 6.2-1
Type of protection, 5.3-1, 6.3-1
U
User name, 6.7-16
V
Validity of the Instructions, 5.2-1, 6.2-1
Voltage supply, 5.4-4, 6.4-5
Preface, 1.1-1
W
Warranty, 1.3-5
Waste disposal, 1.3-5
L

Software Manual
DriveServer
2 DMS-Version 2.0 - 06/2006 - TD05/TD14 L

This Manual is valid for the DriveServer as of version 1.1
Copyright
2006 Lenze Drive Systems GmbH. All rights reserved.
Imprint
Lenze Drive Systems GmbH
Postfach 10 13 52, 31763 Hameln, Deutschland
Phone.: ++49 (0)5154 / 82-0
Fax: ++49 (0)5154 / 82-2111
E-mail: Lenze@Lenze.de
Copyright information
All texts, photos and graphics contained in this documentation are subject to
copyright protection. No part of this documentation may be copied or made
available to third parties without the explicit written approval of Lenze Drive
Systems GmbH.
Liability
All information given in this documentation has been carefully selected and
tested for compliance with the hardware and software described.
Nevertheless, discrepancies cannot be ruled out. We do not accept any
responsibility or liability for any damage that may occur. Required correction
will be included in updates of this documentation.
Trademarks
Microsoft, Windows and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe
Systems Incorporated in the U.S.A. and/or other countries.
All other product names contained in this documentation are trademarks of
the corresponding owners.
L 2.0 EN 3
DriveServer
Contents

Contents
1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Definition of notes used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Connection to the target system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.1 Direct fieldbus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.2 Fieldbus connection via PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 Component selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 Structure of the DriveServer system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2 More functions of the DriveServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 OLE for Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 DCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1.1 General settings for OPC server and OPC clients(s) . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1.2 More settings for the OPC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2 LECOM bus server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2.1 User interface of the LECOM configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2.2 Selection and configuration of the COM interface . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2.3 Detection of the LECOM drives connected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3 Bus server for the system bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4 DriveServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.1 User interface of the DriveServer configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.4.2 DriveServer selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.4.3 Assignment between bus server and DriveServer . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1 Starting the DriveServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2 Access via OPC clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.1 DriveServer configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.2 Application programs with OPC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
DriveServer
Contents
4 2.0 EN L

7 DriveServer architectures (examples). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1 Access via a LAN (Local Area Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.2 Transparent access using a PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.3 Access to different fieldbus systems via a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1 Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1.1 Lenze bus server S7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.1.2 RS232/RS485 interface converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.2 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Your opinion is important to us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
L 2.0 EN 5
DriveServer
About this Manual
Conventions used

1 About this Manual
The Manual contains information on the Lenze DriveServer V1.1.
The DriveServer is a software which provides easy integration of drives into open
automation structures based on OPC (OLE for Process Control).
The DriveServer also provides the following:
> Easy exchange of subordinated fieldbus systems because of fieldbus variants.
> Access to drive parameters using unambiguous names instead of code numbers.
> Exchange of parameter data
> Use of multi-axis systems with subnetworks (in preparation)
> Simplified explanation of complex sequences
> Integration and combination of drive tools made by different manufacturers
1.1 Conventions used
This Manual uses the following conventions to distinguish between different types of
information:
Type of information Writing Examples/notes
Variable identifier italics Set bEnable to TRUE...
Window range The message window... / The Options dialog box...
Control element bold The OK button... / The Copy command... / The Properties tab... / The
Name input field...
Sequence of
menu commands
If several commands must be used in sequence to carry out a function,
then the individual commands are separated by an arrow: Select
FileOpen to...
Keyboard command <bold> Press <F1> to open the Online Help.
If a command requires a combination of keys, a "+" is placed between
the key symbols:
With <Shift>+<ESC> you can...
Program code Cour i er
IF var 1 < var 2 THEN
a = a + 1
END IF
Keyword Courier
bold
Hyperlink underline Hyperlinks are highlighted references which are activated by means of a
mouse click.
Step-by-step
instructions

Step-by-step instructions are indicated by a pictograph.
DriveServer
About this Manual
6 2.0 EN L

This documentation uses the following signal words and symbols to indicate danger and
important information:
Safety information
Layout of the safety information:
Application notes
@Pictograph and signal word!
(characterise the type and severity of danger)
Note
(describes the danger and suggests how to avoid the danger)
Pictograph Signal word Meaning
@
Danger! Danger of personal injury through dangerous electrical voltage
Indicates an impending danger that may lead to death or severe personal injury if
the corresponding measures are not taken.
@
Danger! Danger of personal injury through a general source of danger
_
Stop! Danger of material damage
Indicates a potential danger that may lead to material damage if the corresponding
@
Note! Important note for trouble-free operation
Tip! Useful tip for easy handling

L 2.0 EN 7
DriveServer
System requirements

2 System requirements
The following minimum requirements on hardware and software must be met to use the
DriveServer:
> Microsoft Windows 98/Me, Windows NT 4.0 or Windows 2000/XP
> IBM compatible PC with Intel Pentium-90 processor
> 64 MB RAM; 128 MB RAM with Windows 2000/XP
> 80 MB free hard disk capacity
> CD-ROM drive
> Pointer (mouse, track ball, etc.)
> Free slots/interfaces according to the requirements of the fieldbus connection module
used.
Tip!
When using the DriveServer in a network we recommend Windows NT, Windows
2000 or Windows XP as operating system. With Windows 98 it is not possible to
start the DriveServer automatically via a DCOM connection.
@ Note!
These notes refer to a DriveServer system with one PC only.
If the DriveServer is used on a local network, the system requirements apply
to all PCs connected.
The requirements for the free interfaces only refer to the PC which is to be
used with fieldbus connection modules.
DriveServer
System requirements
Connection to the target system
8 2.0 EN L

2.1 Connection to the target system
The communication with the target system (controller, Drive PLC, etc.) requires a fieldbus-
specific interface module for the PC and the corresponding fieldbus modules for the target
systems to be connected.
> The following table gives an overview of the transfer media which are included in the
basic DriveServer package:
Bus system Max. number of target systems
PC interface Required
hardware components
Required
software components
System bus (CANopen)
Parallel
interface
(LPT port)
63 PC system bus adapter 2173
incl. connection cable and voltage supply
adapter
for DIN keyboard connection (EMF2173IB)
for PS/2
keyboard connection (EMF2173IBV002)
for PS/2
keyboard connection with electrical isolation
(EMF2173IBV003)
Bus server for system bus
(included in the basic
DriveServer package)
USB
(Universal
Serial Bus)
63 PC system bus adapter 2177
incl. connection cable (EMF2177IB)
LECOM
Serial port
(COM port)
1
(RS232)
Fieldbus module EMF 2102IB V001 or V004
PC system cable RS232/485, 5
m (EWL0020)
Bus server for LECOM
(included in the basic
DriveServer package)
31
(RS485)
Fieldbus module EMF 2102IB V001
PC system cable RS232/485, 5
m (EWL0020)
RS232/RS485 interface converter
with automatic change of direction.
See appendix: RS232/RS485 interface
converter (L 35)
52
(optical
fibre)
Fieldbus module EMF 2102IB V003
Optical fibre adapter (EMF2125IB)
Power supply for adapter (EJ0013)
Optical fibre cable (EWZ0007)
L 2.0 EN 9
DriveServer
System requirements

2.1.1 Direct fieldbus connection
Since the system bus is not master/slave oriented, new participants can be added to the
fieldbus system without special recognition of the central master.
All nodes can communicate with each other. It is thus possible to connect a PC directly to
the corresponding bus through a system bus interface module. All devices connected can
be addressed.
2.1.2 Fieldbus connection via PLC
If the system consists of a master and several slaves, it is often difficult to connect a
fieldbus interface module to the bus in parallel.
If the master is a PLC, it is possible to get to the fieldbus master via a PLC-OPC server and
then address the drives. We offer a similar solution for the PROFIBUS-DP which uses a
Siemens Simatic S7 PLC as master.
More information on this solution can be found in the appendix.
Lenze bus server S7 (L 35)
PC PLC
PC
PLC
DriveServer
Software installation
10 2.0 EN L

3 Software installation
How to install the DriveServer...
1. Start Windows.
2. Insert the DriveServer CD-ROM into your CD-ROM drive.
If the auto-start function of your CD-ROM drive is activated, the installation
program will be started automatically and you can proceed with step 5.
3. Go to Start menu and select Run...
4. Enter the letter for your CD-ROM drive followed by ":\setup.exe"
(e.g. "e:\setup.exe") and confirm the entry by clicking OK.
5. Follow the instructions of the installation program.
@ Note!
Windows NT/2000/XP
Installation under Windows NT/2000/XP requires administrators rights!
Windows 98
The DriveServer installation program checks whether the DCOM version
installed is correct.
If required, the program suggests the installation of a DCOM update.
If the DCOM version found is not correct, the DriveServer software cannot be
installed!
L 2.0 EN 11
DriveServer
Component selection

3.1 Component selection
The DriveServer installation program enables you to select the components you want to
install on your PC.
Component Information
DriveServer OPC server for Lenze drives
Bus server LECOM Drivers for the communication through LECOM
Bus server system bus Drivers for the communication through system bus
Online Help
(German/English)
Context-sensitive help for the program
Online Manuals
(German/English)
Manuals for the program in Portable Document Format (PDF) for display in
Adobe Reader
Creation of program groups Creation of a program group through the Windows start menu
@ Note!
If you want to use fieldbuses different from LECOM or system bus to access the
controller, install the appropriate OPC bus server.
To provide a DriveServer access to drives networked via PROFIBUS-DP and
controlled via Siemens SIMATIC S7-SPS, Lenze offers, e.g. the bus server S7.
Appendix: Lenze bus server S7 (L 35)
Please observe the instructions for the installation/commissioning of the bus
server hardware/software!
DriveServer
Introduction
Structure of the DriveServer system
12 2.0 EN L

4 Introduction
The main concept of the DriveServer can be compared with a printer driver:
The printer driver provides all special data required for a specific printer. Every Windows-
conform and printable program uses a standardised interface to set up the printer. The
dialog box is called "Printer features". Although the interface is standardised, the
parameters can be set for a specific printer.
The DriveServer also provides a standardised interface to enable access to the drives via
different fieldbus systems.
4.1 Structure of the DriveServer system
The following figure shows the basic components of the DriveServer system:
> Drives
In the centre you can see the drives which are addressed by several PC programs, for
instance visualisation and parameter setting programs.
> Fieldbuses
The drives are connected through different fieldbuses, which require different drivers.
> Bus servers
Drivers are fieldbus-specific OPC servers with DRIVECOM DriveServer profile as offered
by manufacturers of fieldbus cards. These OPC servers, called "bus servers", provide all
information required for different bus systems. Since, however, they are not especially
configured for drive systems, a configuration without the DriveServer would be very
complicated.
> DriveServer
The DriveServer itself does not have any special fieldbus features. It has, however,
especially been written for the Lenze drive technology and is therefore able to carry out
many configuration tasks without manual support from the user.
> Software tools
OPC clients for communication with the DriveServer can be any software tool that has
an OPC interface, e.g. visualisation, diagnostics and parameter setting programs.
Drives
Fieldbuses
Bus servers
DriveServer
Software tools
Programming
Diagnostics
Parameter setting
Production data acquisition
Visualisation
(OPC clients)
L 2.0 EN 13
DriveServer
Introduction
More functions of the DriveServer

4.2 More functions of the DriveServer
DCOM
Because of the use of the Windows technology DCOM, the DriveServer can overcome
computer limits via Ethernet.
> The software tools used do therefore not have to be installed on the computer, but can
also be included in the fieldbus module.
> In a local network, access is possible from any station connected.
LECOM/system bus
The DriveServer is delivered with the bus servers for LECOM and system bus, since these
two fieldbus systems are mainly used with Lenze drives.
> An overview of more bus servers offered by Lenze and third-party manufacturers, can
be obtained from the Appendix. They have been optimised for use with the DriveServer
to reduce configuration tasks.
4.3 OLE for Process Control
OLE for Process Control (OPC) defines an interface based on the Microsoft Windows
technologies OLE, COM and DCOM which enables data exchange between different
automation units and PC programs without having any problems with drivers and
interfaces.
Sometimes this tool is also called "Software plug", because programs of different
manufacturers can be easily connected for communication. Especially manufactures of
visualisation systems use OPC since it is then possible to do without special drivers for
different units.
OPC was created in 1996 in the United States and since then has been spread in the
automation industry. The user group OPC Foundation comprises more
than 150 companies, among them is Lenze.
Basic structure
The basic structure of OPC is a client/server system. An OPC server provides data which are
read out of a drive via a fieldbus system. These dat can be accessed through an OPC client
(e.g. parameter setting program, visualisation). Depending on the data, changes via the
OPC client are also possible.
> Several OPC clients can access one or several OPC servers (n:n connection) at the same
time.
DriveServer
Introduction
OLE for Process Control
14 2.0 EN L

Items/Groups
Usually data is exchanged via so-called OPC items which are represented by process
variables and unit parameters (codes).
> The OPC items can be arranged in OPC groups according to logical or dynamical aspects.
Thus, for instance, all OPC items which are to be updated cyclically, can be saved in the
same OPC group. OPC items and OPC groups are always in the OPC server. The OPC
clients log on the OPC server and specify the name of the OPC item they want to access.
> OPC items can also have specific properties. A property is a feature which informs the
user, for instance, about the value limits or units of an OPC item.
Browse function
In addition to the Read and Write functions of OPC items, most OPC clients also support the
browse function. The Browse function helps the OPC client to find all OPC items (also
parameters) available on an OPC server.
> Since most OPC servers require the configuration of OPC items, it can sometimes be
very costly to configure all parameters of a drive. The DriveServer, however,
automatically detects the drives connected and displays all parameters available in a
logic order when using the browse function. The user only has to select the parameters
to be accessed from the OPC client.
COM/DCOM
Since OPC is based on the Microsoft Windows technologies COM and DCOM it is also
possible to access an OPC server from several computers via a local network.
> For instance, the OPC server can be on an industrial PC in the field and the OPC client
can be a PC in an office, the two can be connected via a LAN (Local Area Network), such
as Ethernet.
> The standardised OPC interface also enables the data transfer from the drive into the
Internet.
L 2.0 EN 15
DriveServer
Configuration
DCOM

5 Configuration
One of the main objectives of the DriveServer is to reduce the configuration of the system
to a minimum (Plug and Drive). Unfortunately, it is not possible to completely do without
a configuration.
> This chapter describes the configuration of DCOM and the bus server for LECOM and
system bus.
> If you use different bus servers, the configuration must be obtained from the
corresponding Instructions.
5.1 DCOM
The OPC standard enables the user, for instance, to access DriveServer data on a local
network. To protect the PC from unauthorised access, the safety standards do not allow
OPC access. Before commissioning the DriveServer, these settings must be checked and
changed, if required.
> The easiest is to adapt the standard parameters. They apply to all servers installed on
the PC.
> Individual DCOM configuration for single servers is only required for special
applications.
@ Note!
Ensure that the drives connected to the bus have different addresses before the
configuration of the bus server.
For this, it may be necessary to individually connect the drives to the bus
system and configure them accordingly.
Alternatively, the address of a drive can be changed using the keypad.
@ Note!
The settings described in this chapter should be agreed by a system's
administrator (because they have an influence on the safety checks) to ensure
easy commissioning of the DriveServer.
With Windows 98 it is not necessary to configure DCOM if the communication is
not required between several PCs.
DriveServer
Configuration
DCOM
16 2.0 EN L

5.1.1 General settings for OPC server and OPC clients(s)
Windows XP
How to configure DCOM under Windows XP...
1. Go to the Start menu and select Run...
2. Enter "dcomcnfg" into the input field and click OK to open the Microsoft
Management Console (MMC).
Go to the tree structure on the left-hand side and select Console
rootComponent servicesComputer
to go to the object My computer.
3. Highlight the object My computer and select ActionProperties to open the dialog
box Properties of My computer.
4. Select the tab Standard properties.
5. Activate DCOM on this computer.
6. Go to the Standard authentication level and set "No".
7. Go to the Standard idenfication level and set "Anonymous".
8. Select the tab COM standard safety.
9. Click the Change standard button to define the users for access and start
authorisation for the DriveServer. The easiest way is to select "Everybody".
10. Click the OK button to save the settings.
11. Select FileExit to exit the Microsoft Management Console.
Windows NT/2000
How to configure DCOM under Windows NT/2000...
2. Enter "dcomcnfg" in the input field and click OK to open the dialog box DCOM
properties.
6. Go to the Standard idenfication level and set "Anonymous".
7. Select the tab Standard safety.
L 2.0 EN 17
DriveServer
Configuration
DCOM

8. Click the Change standard button to define the users for access and start
authorisation for the DriveServer. The easiest way is to select "Everybody".
9. Click OK to save the settings and close the dialog box.
Windows 98/Me
How to configure DCOM under Windows 98/Me...
properties.
6. Go to the Standard identification level and set "Identify".
7. Select the tab Standard safety.
In this tab you can define the standard authorisation for access and start.
8. Activate Remote connection.
@ Note!
With Windows 98/ME it is not possible to start OPC servers automatically
through a DCOM connection; a manual start is required.
Therefore we recommend to use Windows NT/2000/XP when connecting
several PCs.
DriveServer
Configuration
DCOM
18 2.0 EN L

5.1.2 More settings for the OPC server
Furthermore, it is necessary to enter the users who are authorised to use all server
applications.
Windows XP
How to configure the server applications under Windows XP...
2. Enter "dcomcnfg" into the input field and click OK to open the Microsoft
Management Console (MMC).
Go to the tree structure on the left-hand side and select Console
rootComponent servicesComputer
to go to the object My computer.
3. Go below the object My computer and select the folder DCOM configuration to
display the existing DCOM applications on the right-hand side.
4. Select the application OPCenum" or "OPC Server List Class".
5. Select the command ActionProperties to open the dialog box Properties for the
application selected.
6. Select the tab Identity.
7. Activate the option box Interactive user.
Exception: When selecting the "OPCenum" application, activate the option box
System account (services only) instead.
9. Repeat steps 5 to 8 for the applications
"Lenze OPC LECOM server",
Lenze OPC system bus server" and
"Lenze OPC DriveServer",
if you have installed these components on your PC.
10. Select FileExit to exit the Microsoft Management Console.
L 2.0 EN 19
DriveServer
Configuration
DCOM

Windows 98/Me, Windows NT/2000
How to configure the server applications under Windows 98/Me, Windows NT or
Windows 2000...
properties.
3. Select the tab Applications.
4. Go to the list field Applications and select the application "OPCenum" or "OPC
Server List Class".
5. Click Properties to open the dialog box Properties for the application selected.
6. Select the tab Identity.
7. Activate the option box Interactive user.
Exception: When selecting the "OPCenum" application under Windows NT/
2000, activate the option field System account (services only) instead.
9. Repeat steps 5 to 8 for the applications
"Lenze OPC LECOM server",
Lenze OPC system bus server" and
"Lenze OPC DriveServer",
if you have installed these components on your PC.
DriveServer
Configuration
LECOM bus server
20 2.0 EN L

5.2 LECOM bus server
The LECOM bus server is configured with the program LECOM configurator" and consists
of the selection and configuration of the COM interface and the detection of the connected
LECOM unit.
How to configure the LECOM bus server
1. Go to the Start menu and select ProgramsLenzeDriveServerLECOM
configurator.
2. Confirm the info dialog box Lenze OPC Server LECOM by clicking OK.
The configuration saved last will be loaded automatically.
If you want to create a new configuration, select FileNew.
5.2.1 User interface of the LECOM configurator
The LECOM configuration tool is subdivided into two sections
> The left side indicates the configuration entries in form of a tree, similar to directories
of the Microsoft Explorer.
> The right side shows possible settings for the configuration entry selected from the
tree.
If you create a new configuration, the first visible entry will be Lecom".
Tip!
If a plus sign appears in front of the element in the tree structure, this element
includes subelements:
A click on the plus sign opens the list of subelements. A minus sign is now
displayed.
When you click the minus sign, the list of subelements will be closed again.
L 2.0 EN 21
DriveServer
Configuration
LECOM bus server

5.2.2 Selection and configuration of the COM interface
In a first step, add the serial interface to which the drives are connected, to the
configuration.
How to configure the COM interface...
1. Click Add COM interface to open the dialog box Name and number of the COM
interface:
2. Enter the name (freely selectable) and the COM number of the interface used and
confirm the entries by clicking OK.
The added communication port is indicated as configuration entry in the LECOM
configuration tool.

3. Go to the list field Baud Rate and select the baud rate for the drives connected.
Lenze controllers are default set to 9600 baud.
Next configuration step:
Detection of the LECOM drives connected (L 22)
DriveServer
Configuration
LECOM bus server
22 2.0 EN L

5.2.3 Detection of the LECOM drives connected
In this second configuration step the LECOM drives connected to the PC are to be detected
by means of the search function of the LECOM configurator.
Tip!
If you want to reduce the time required for automatically finding all drives
connected to the bus, enter the maximum number of the devices to be found in the
input field Number of drives to be found.
How to detect the LECOM drives connected...
1. Click Search to start the search.
The search progress is indicated in a dialog box.
If the number of drives entered under the input field Number of drives to be
found have been found, a box is displayed which asks the user whether the
search is to be continued or not.
The drives found are listed as configuration entry below the COM interface:
The LECOM configuration tool automatically creates several OPC items for every
drive. It is thus possible for the DriveServer to detect the drive automatically.
For special applications, more OPC items can be added manually. In general,
however, the DriveServer creates the OPC items.
2. Select FileSave to save the current configuration.
3. Select FileExit to exit the LECOM configurator.
L 2.0 EN 23
DriveServer
Configuration
Bus server for the system bus

5.3 Bus server for the system bus
The bus server for the system bus is configured via the program "System bus configurator".
The configuration consists of the setting of the communication parameters for the
selected interface module.
Go to Start menu and select
ProgramsLenzeCommunicationSystembus configurator to open the system
bus configurator.
Tip!
Detailed information on the system bus configurator can be found in the CAN
Communication Manual and the Online Help for the system bus configurator.
DriveServer
Configuration
DriveServer
24 2.0 EN L

5.4 DriveServer
Since all fieldbus specific settings are saved directly in the corresponding bus server, the
DriveServer must only get the information which bus server is to be used.
The DriveServer is configured via the program "DriveServer configurator".
Go to Start menu and select
ProgramsLenzeDriveServerDriveServer configurator to start the DriveServer
configurator.
5.4.1 User interface of the DriveServer configurator
The DriveServer configuration tool is subdivided into two sections:
> The left side indicates the name area of the DriveServer in form of a tree, similar to
directories of the Microsoft Explorer.
> When you select a parameter or a group of parameters in the name area, the right sides
indicates the corresponding parameter data.
List of symbols used for the classification of elements used for the names:
Icon Element/meaning
OPC server (DriveServer)
The DriveServer represents the highest level in the name area.
Online
This element includes a list of all bus servers and drives assigned to DriveServer.
Offline
Whereas the Online element shows all physically connected drives, this element also allows to
configure "Offline drives" for simulation purposes.
Offline drives are also listed in the name area of the DriveServer but do not require a bus server.
How to add an offline drive:
Click the element Offline in the name area to get a list of all controllers known to the
DriveServer.
Select the controller wanted and click OK to add this controller to the list of offline drives.
Bus server
Every fieldbus system requires its own bus server which then ensures communication between all
drives connected.
Drive
A drive is connected to a bus server or configured as Offline drive" (see Offline").
L 2.0 EN 25
DriveServer
Configuration
DriveServer

Tip!
If a plus sign appears in front of the element in the tree structure, this element
includes subelements:
A click on the plus sign opens the list of subelements. A minus sign is now
displayed.
When you click the minus sign, the list of subelements will be closed again.
Group
A group is a classification of parameters for a drive. The parameters are grouped according to their
functionality.
This enables you to find a parameter without knowing its code number. For instance, the group
"Diagnostics" includes all parameters required the diagnostics of the corresponding drive.
Groups can be further classified by subgroups.
Parameters
Parameters represent the lowest level of the name.
Icon Element/meaning
DriveServer
Configuration
DriveServer
26 2.0 EN L

5.4.2 DriveServer selection
Since a network environment can comprise several DriveServers (OPC servers), the
DriveServer to be configured is to be selected first.
How to select the DriveServer to be configured...
1. Select FileChoose OPC server to open the dialog box Choose OPC server:
2. Go to the input field Computer name and select a PC or go to Network and select a
PC from the network environment, the DriveServers of which are to be shown for
selection.
If the DriveServer configuration tool and DriveServer are installed on the same
PC, the presetting for localhost" does not have to be changed.
3. Click Refresh to get a list of all DriveServers available in the PC selected.
4. Select the DriveServer to be configured from the list field.
5. Click OK to save the selection and close the dialog field.
5.4.3 Assignment between bus server and DriveServer
The program distinguishes between normal" OPC servers and OPC bus servers:
> OPC servers usually require a difficult and expensive configuration.
> Lenze OPC bus servers and the bus servers listed in the appendix have been optimised
for the use with DriveServer and do therefore not need much configuration.
Tip!
We recommend to only use OPC servers which also show bus server features!
How to assign bus servers to the DriverServer...
1. Select FileConnect to establish a connection to the DriveServer selected.
Wait until the dialog box Please wait disappears and the connection to the
DriveServer is completed.
2. Select ConfigurationBus server to open the dialog box Bus server configuration.
L 2.0 EN 27
DriveServer
Configuration
DriveServer

3. Click Refresh to get a list of all bus servers available on the PC selected in the left
list field:
In the default setting the control field Bus server is activated so that the list field
only displays OPC servers with bus server features.
Click Network to get a list of bus servers which are installed on another PC in the
network environment.
4. Assign the bus servers to the DriveServer by highlighting the corresponding bus
server in the left list field and clicking Add.
The bus servers assigned to the DriveServer are listed in the right list field.
You can also undo the adding of a bus server by selecting it from the right list
field and clicking Delete.
The description of the bus server is also used in the name area of the
DriveServer. For a better overview, we recommend to change the preset
description of the bus server into a shorter one or to use the fieldbus name
(LECOM, CANopen, etc.) only.
For this purpose select the corresponding bus server from the right list field and
click again the highlighted area to change into the editing mode.
DriveServer
Configuration
DriveServer
28 2.0 EN L

5. After the corresponding bus server has been added, click OK to save the settings
and close the dialog field.
The bus servers assigned to the DriveServer and all connected drives are now listed
under the Online element:
6. Select FileDisconnect to disconnect a bus server from the DriveServer selected.
7. Select FileExit to exit the DriveServer configurator.
The configuration is completed and the DriveServer can be started.
Operation (L 29)
L 2.0 EN 29
DriveServer
Operation
Starting the DriveServer

6 Operation
The DriveServer enables communication via several media. As OPC server it operates in the
background and does therefore not feature its own user interface. This interface is
provided by the OPC clients which communicate with the DriveServer.
Tip!
In general every PC program with OPC interface, e.g a visualisation, can be used as
OPC client and thus access drive parameters via the DriveServer.
Before we will give you further information on the software components, the next
paragraph will inform you about how the DriveServer starts.
6.1 Starting the DriveServer
The DriveServer is started automatically when an OPC client wants to access it. Then, the
DriveServer starts all bus servers and identifies the drives by means of the addresses sent
from the bus servers.
Identification means that the DriveServer checks every address for Lenze controllers. If a
Lenze controller is indicated in the address, the DriveServer detects the parameters of the
corresponding controller. Based on this information, the name area for the DriveServer
system is created, which lists all drives with its parameters in form of a tree. OPC clients can
access the tree by means of the OPC browse function via two ways:
> Hierarchical
The name area corresponds to the tree structure created by the DriveServer.
> Flat
The name area consists of only one level which includes all elements.
The following illustration shows a part of the (hierarchical) tree structure for a DriveServer
system with three fieldbus systems connected - PROFIBUS-DP, CANopen and LECOM:
DriveServer
Operation
Access via OPC clients
30 2.0 EN L

6.2 Access via OPC clients
The DriveServer can be accessed by the following software components which serve as
OPC clients and have been optimised for Lenze controllers:
> The DriveServer configurator which has already been described in the previous chapter.
DriveServer (L 24)
> The parameter setting program Global Drive Control with OPC interface (as of version
4.3).
> ActiveX controls, which can be integrated into your application.
6.2.1 DriveServer configurator
You have already used the program DriveServer configuration tool" to configure the
DriveServer.
The DriveServer configurator is an OPC client which expects the DriveServer as OPC server.
If your system is configured as described in chapter 5, you can access the name area of the
DriveServer system via the DriveServer configurator.
How to access the name area of the DriveServer system...
1. Go to Start menu and select
ProgramsLenzeDriveServerDriveServer configurator to start the DriveServer
configurator.
2. Select the corresponding DriveServer from the Tree structure and click Connect.
The DriveServer will be started. The drives connected to the assigned bus servers
are identified and listed in the name area.
@Warning!
Since you have an Online connection with the controller, every change of a
parameter value will take immediate effect.
Only make changes when you are sure that they will not lead to any damage of
machinery or persons!
L 2.0 EN 31
DriveServer
Operation
Access via OPC clients

The following figure shows a part of a name area for a system consisting of a 9300 Servo
inverter" which is connected to the DriveServer via LECOM:
> If you select a parameter or a group of parameters from the name area, the current
parameter data will be indicated on the right. With same parameters these data can be
changed.
> Entries under Code" are indicated in different colours depending on their meaning.
6.2.2 Application programs with OPC interface
Every PC program which supports the OPC interface can access the name area of the
DriveServer and thus the drive parameters by using the OPC browse function.
> For instance, a visualisation program can be used. The configuration of the
visualisation system only requires the assignment of the display elements of the
visualisation and the corresponding parameters in the name area.
> For further information please see the documentation of the program.
Colour Meaning
Green The parameter data have not been read from the file yet.
Light grey The parameter data can be read only
Black The parameter data can be read and changed.
If you double click a parameter value, a dialog box for changing the current parameter value will
appear.
Red The parameter data cannot be read from the drive (e.g. due to transfer errors).
DriveServer
DriveServer architectures (examples)
Access via a LAN (Local Area Network)
32 2.0 EN L

7 DriveServer architectures (examples)
In the following subchapters you will find a short description of architectures implemented
with the DriveServer. Since there are so many configurations possible, the following
examples can only show some typical DriveServer architectures:
Access via a LAN (Local Area Network)
Transparent access using a PLC (L 33)
Access to different fieldbus systems via a LAN (L 34)
7.1 Access via a LAN (Local Area Network)
The following figure shows a system architecture which allows access to a drive network
in a LAN (e.g. Ethernet).
> The fieldbus (e. g. CANopen) is connected to an industrial PC.
> The corresponding bus server and the DriveServer are installed on this industrial PC.
> The industrial PC is also connected to the local Ethernet network.
> Diagnostics/parameter setting for the drives can be made via all PCs connected to the
Ethernet network. The only condition is that an OPC client is installed (e. g. the
parameter setting program Global Drive Control with OPC interface).
L 2.0 EN 33
DriveServer
Transparent access using a PLC

7.2 Transparent access using a PLC
Fieldbus systems with one master only are often used with a PLC. It is then not possible to
have a direct connection to the fieldbus.
The following figure shows a system architecture with a Simatic S7 control made by
Siemens as PLC.
> The drives are connected to the PLC via PROFIBUS-DP
> The two PLCs are interconnected via an MPI bus.
> The PC with the DriveServer is also connected to the MPI bus and uses a bus server for
the PLC (Lenze S7-MPI OPC server) instead of a bus server for the fieldbus system.
> Special Lenze function modules in the S7 program allow access to the drives from the
PC via a PLC as if the PLC was not connected.
Tip!
More information about the Lenze S7-MPI OPC server can be obtained from the
"XXX" documentation which is part of the delivery.
DriveServer
Access to different fieldbus systems via a LAN
34 2.0 EN L

7.3 Access to different fieldbus systems via a LAN
Since the DriveServer can access different fieldbus systems at the same time it is possible
to create a 'superimposed' master system which results in complete independence.
The following figure shows a system architecture with the three fieldbus systems:
CANopen, Profibus-DP and LECOM
> Every fieldbus is connected with an industrial PC.
> The industrial PC are interconnected via a local Ethernet network.
> Also normal PCs are connected to this Ethernet network. The master system built up is
completely independent of the fieldbus used.
L 2.0 EN 35
DriveServer
Appendix
Accessories

8 Appendix
8.1 Accessories
8.1.1 Lenze bus server S7
The bus server S7 is a fieldbus-specific OPC server according to DRIVECOM specification
which enables the Lenze DriveServer to access drives which are connected via PROFIBUS-
DP and controlled via Siemens SIMATIC S7 PLC.
The following figure shows the architecture of such a system:
> The PC with the DriveServer is connected to the PLC via a bus system (MPI, Ethernet or
PROFIBUS). The DriveServer uses the bus server S7 as OPC bus server.
> The S7 program uses special Lenze function blocks via which the DriveServer can access
the drives through the PLC as if the PLC was not connected.
> The drives are connected to the PROFIBUS master of the PLC via PROFIBUS-DP.
8.1.2 RS232/RS485 interface converter
The operation of a LECOM network based on RS485 an interface converter is required for
the connection to the PC. It must be provided with an automatic change of direction since
due to the use of two cores only half duplex operation is possible.
We recommend to use the following product:
I-7520 isolated RS232 on RS485 converter
Supplier Spectra Computersysteme GmbH
Humboldstrae 36
70771 Leinfelden/Echterdingen
DriveServer
Anhang
Glossary
36 2.0 EN L

8.2 Glossary
B
Bus server Fieldbus-specific OPC server according to the DRIVECOM specification.
OPC
DRIVECOM
C
CAL Abbr. for "CAN Application Layer". Communication standard (CiA DS 201-207)
which provides objects, protocols and services for the event or polling-
controlled transmission of CAN messages and the transmission of greater
data ranges between CAN nodes. Furthermore, CAL offers effective processes
for an automatic assignment of message identifiers, the initialisation and
monitoring of network nodes, and the assignment of an individual
identification to network nodes.
CAN Abbr. for "Controller Area Network". Serial, message-oriented and not node-
oriented bus system for max. 63 nodes.
CANopen Communication profile (CiADS301, Version4.01), which has been developed in
conformity with the CAL under the umbrella association of the CiA ("CAN in
Automation").
CiA Abbr. for "CAN in Automation (e. V.)": International users' and manufacturers'
organisation which has the target to impart knowledge on the internationally
standardised CAN bus system (ISO 11898) worldwide and advance the
technical development.
Code Parameters of Lenze devices for setting the device functions.
COM Abbr. for "Component Object Model": A software architecture developed by
Microsoft for creating programs from individually executable software
components (objects) which are only connected when the program is running.
Controller Generic term for Lenze frequency inverters, servo inverters and PLCs.
D
DCOM Abbr. for "Distributed Component Object Model": COM which allows the
distribution of executable objects on different PCs connected to the same
local network.
COM
DRIVECOM "DRIVECOM User Group e.V.": Association of international drive
manufacturers, universities, and institutes which has the target to develop a
simple integration of drives into open automation systems
Internet: http://www.drivecom.org
DriveServer Lenze Software, which provides easy integration of drives into open
automation structures based on OPC ("OLE for Process Control").
OPC
H
Hyperlink Highlighted references which are activated by means of a mouse click.
L
LECOM Lenze bus system based on RS232, RS485 or LWL (optical fibre).
L 2.0 EN 37
DriveServer
Anhang
Glossary

M
Menu bar Bar in the upper position of the application window below the title bar which
displays the names of the menus which open when being clicked with the
mouse.
MPI Abbr. for "Multi-Point-Interface": Bus system which is integrated for instance
into Siemens PLC.
O
OLE Abbr. for "Object Linking and Embedding": Insertion of functional objects into
other applications, e.g. a Microsoft Excel table into a Microsoft Word
document.
OPC Abbr. for "OLE for Process Control": Defines an interface based on the
Microsoft Windows technologies OLE, COM and DCOM which enables data
exchange between different automation devices and PC programs without
having any problems with drivers and interfaces.
COM
DCOM
P
PDF Abbr. for "Portable Document Format", a universal file format developed by
the Adobe company for exchanging electronic documents. Adobe's freely
available software Adobe Reader serves to display and print PDF files,
independent of the application and platform used.
Internet: http://www.adobe.com
PLC Abbr. for "Programmable Logic Controller"
S
System bus (CAN) A Lenze bus system similar to the CANopen communication profile (CiADS301,
Version4.01).
CAN
T
Title bar Bar in the upper position of the application window which contains the
program icon and the program name in the left-most position and the
window icons in the right-most position.
Window icon
W
Window icon Button in the right-most position of the title bar to change the window format
or close the window.
DriveServer
Index
38 2.0 EN L

9 Index
A
Application notes 6
B
Browse function 14
Bus server for the system bus 23
Bus server S7 35
Bus servers 12
C
COM 14
COM interface 21
Connection to the target system 8
Conventions used 5
Copyright 2
Copyright information 2
D
DCOM 13, 14, 15
Direct fieldbus connection 9
drives 12
DriveServer configuration tool 24, 30
E
E-mail to Lenze 39
F
Feedback to Lenze 39
Fieldbus connection via PLC 9
Fieldbuses 12
G
Groups 14
H
hardware components 8
I
Imprint 2
Installation 10
Items 14
L
Layout of the safety information 6
LECOM 8, 13
LECOM bus server 20
LECOM configuration tool 20
Liability 2
Local Area Network 32
N
name 30
O
Offline 24
OLE for Process Control 13
Online 24
OPC interface 31
OPC server selection 24
P
Parameters 25
Plug and Drive 15
PROFIBUS-DP 35
R
RS232/RS485 interface converter 35
S
Safety information 6
software components 8
Software tools 12
Starting performance 29
Structure of the DriveServer system 12
System bus (CANopen) 8
System bus configuration tool 23
System requirements 7
T
Trademarks 2
Transparent access 33
U
User interface 7
L 39
These Instructions were created to the best of our knowledge
and belief to give you the best possible support for handling
our product.
L

Software Manual
Bus server S7
2 DMS-Version 2.0 - 06/2006 - TD05/TD14 L

This Manual is valid for the bus server S7 from version x.x
Copyright
2006 Lenze Drive Systems GmbH. All rights reserved.
Imprint
Lenze Drive Systems GmbH
Postfach 10 13 52, 31763 Hameln, Germany
Phone.: ++49 (0)5154 / 82-0
Fax: ++49 (0)5154 / 82-2111
E-mail: Lenze@Lenze.de
Copyright information
All texts, photos and graphics contained in this documentation are subject to
copyright protection. No part of this documentation may be copied or made
available to third parties without the explicit written approval of Lenze Drive
Systems GmbH.
Liability
All information given in this documentation has been carefully selected and
tested for compliance with the hardware and software described.
Nevertheless, discrepancies cannot be ruled out. We do not accept any
responsibility or liability for any damage that may occur. Required correction
will be included in updates of this documentation.
Trademarks
Microsoft, Windows and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe
Systems Incorporated in the U.S.A. and/or other countries.
All other product names contained in this documentation are trademarks of
the corresponding owners.
L 2.0 EN 3
Bus server S7
Contents

Contents
1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Definition of notes used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 Connection to the target system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Supported protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1 IBHLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.2 COMxMPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.3 MPI Simatic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.4 PROFIBUS-DP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.5 SOFTNET TCP/H1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.6 TCP direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Supported PLC hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Component selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1 Configuration of the interface module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Bus server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2.1 User interface of the S7 configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2.2 Automatic PLC detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.3 Manual addition of PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.4 PLC parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.5 Automatic drive detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2.6 Manual addition of drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2.7 Drive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2.8 Configuration of subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.9 Manual removal of configuration entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2.10 Saving the current configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2.11 Exit the S7 configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 Creating a STEP7 project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1 Overview of the STEP7 blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 Typical program flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Files provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.3.1 STEP7 library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.3.2 STEP7 example programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.3.3 Device description files of the Lenze drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Bus server S7
Contents
4 2.0 EN L

5.4 Creation of new projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5.1 Configuring the MPI interface of the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.5.2 Configuring the PROFIBUS interface of the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.5.3 Configuring further hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.6 Creating a STEP7 program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.6.1 Accessing a drive via OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.6.2 Accessing several drives via OPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.6.3 Accessing the drives connected to PROFIBUS-CPs . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.6.4 Access to process and parameter data from the PLC . . . . . . . . . . . . . . . . . . . . . . . 37
5.7 Testing the STEP7 program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.7.1 Structure of the DriveServer name area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.8 Optimisation of the cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.9 Accessing PLC data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1 Time load of the PLC cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.2 Transmission times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.3 Communication function parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.3.1 FB90 (FB DRIVE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.3.2 FB91 (FB DRIVE CP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.3.3 FC90 (FC parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.3.4 FC91 (FC process data three words) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.3.5 FC92 (FC process data, two words) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.3.6 FC93 (FC process data, three words, CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.3.7 FC94 (FC process data, two words, CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.4 Remote maintenance via modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.5 S7-400 example project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.5.1 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.5.2 Program blocks used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.5.3 Symbolic variable names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.5.4 OB1/FC4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.5.5 Process data transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.5.6 Control of the parameter data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.5.7 Reading a parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.5.8 Writing a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
L 2.0 EN 5
Bus server S7
Contents

6.6 Example project S7-300 with PROFIBUS-CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.6.1 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.6.2 Program blocks used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.6.3 Symbolic variable names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.6.4 OB1/FC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.6.5 Process data transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.6.6 Control of the parameter data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.6.7 Reading/writing a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.7 S7 configurator - settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.7.1 'Common settings' tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.7.2 'S7 PLC' tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.7.3 'Device' tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.7.4 'Block' tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.7.5 'Item' tab (for device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7.6 'Item' tab (for block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.8 FAQ - Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Your opinion is important to us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Bus server S7
About this Manual
Conventions used
6 2.0 EN L

1 About this Manual
This Manual contains information on the Lenze bus server S7.
The bus server S7 is a fieldbus-specific OPC server according to DRIVECOM specification
which enables the Lenze DriveServer to access drives which are connected via PROFIBUS-
DP and controlled via Siemens SIMATIC S7 PLC.
The following figure shows the architecture of such a system:
> The PC with the DriveServer is connected to the PLC via a bus system (MPI, Ethernet or
PROFIBUS). The DriveServer uses the bus server S7 as OPC bus server.
> The S7 program uses special Lenze function blocks via which the DriveServer can access
the drives through the PLC as if the PLC was not connected.
> The drives are connected to the PROFIBUS master of the PLC via PROFIBUS-DP.
1.1 Conventions used
This Manual uses the following conventions to distinguish between different types of
information:
Type of information Writing Examples/notes
Variable identifier italics Set bEnable to TRUE...
Window range The message window... / The Options dialog box...
Control element bold The OK button... / The Copy command... / The Properties tab... / The
Name input field...
Sequence of
menu commands
If several commands must be used in sequence to carry out a function,
then the individual commands are separated by an arrow: Select
FileOpen to...
Shortcut <bold> Press <F1> to open the Online Help.
If a command requires a combination of keys, a "+" is placed between
the key symbols:
With <Shift>+<ESC> you can...
Program code Cour i er
IF var 1 < var 2 THEN
a = a + 1
END IF
Keyword Courier
bold
Hyperlink underline Hyperlinks are highlighted references which are activated by means of a
mouse click.
Step-by-step
instructions

Step-by-step instructions are indicated by a pictograph.
L 2.0 EN 7
Bus server S7
About this Manual

This documentation uses the following signal words and symbols to indicate danger and
important information:
Safety information
Layout of the safety information:
Application notes
@Pictograph and signal word!
(characterise the type and severity of danger)
Note
(describes the danger and suggests how to avoid the danger)
@
Danger! Danger of personal injury through dangerous electrical voltage
@
Danger! Danger of personal injury through a general source of danger
_
Stop! Danger of material damage
Indicates a potential danger that may lead to material damage if the corresponding
@
Note! Important note for trouble-free operation
Tip! Useful tip for easy handling

Bus server S7
System requirements
8 2.0 EN L

2 System requirements
The following minimum requirements on hardware and software must be met in order to
operate the bus server S7:
> Microsoft Windows 98/Me, Windows NT 4.0 or Windows 2000/XP
> IBM compatible PC with Intel Pentium-90 processor
> 64 MB Random Access Memory (RAM); 128 MB RAM with Windows 2000/XP
> 80 MB free hard disk capacity
> CD-ROM drive
Please also observe the system requirements of the interface module!
(See the following subchapter.)
Tip!
We recommend to use a Windows NT, Windows 2000 or Windows XP operating
system!
With the same hardware, the program execution times are much shorter under
Windows NT/2000/XP than under Windows 98/Me.
When several computers are interconnected, it is not possible to start OPC
servers automatically through a DCOM connection with Windows 98/Me.
2.1 Connection to the target system
The PC must be equipped with an interface module suitable for the bus system used to
communicate with the PLC.
> It is possible to use standard network cards for Ethernet connections.
> The following interface modules are available for MPI/PROFIBUS:
See also: Configuration of the interface module (L 15)
Manufacturer Designation Order number Version/description
Siemens CP5611 6GK1561-1AA00 PCI card (32-bit) to connect a PU or PC with
PCI bus to PROFIBUS or MPI.
CP5511 6GK1551-1AA00 PCMCIA card (16-bit) to connect a PU or
notebook to PROFIBUS or MPI.
PC adapter RS-232 6ES7972-0CA23-0XA0 RS-232 MPI or PROFIBUS
PC adapter USB 6ES7972-0CB20-0XA0 USB MPI or PROFIBUS
Helmholz PC adapter RS-232 700-751-1VK11 RS-232 MPI or PROFIBUS
IBH Softec IBHLink 2026 Adapter cable Ethernet MPI
@ Note!
Please observe the Installation/Commissioning Instructions for the interface
module given by the manufacturer!
L 2.0 EN 9
Bus server S7
System requirements
Supported protocols

2.2 Supported protocols
The bus server S7 supports the following protocols:
@ Note!
Detailed information on the supported protocols and additional hardware/
software requirements can be found in the following subchapters:
Bus server
S7
S
i
e
m
e
n
s
C
o
m
m
u
n
i
c
a
t
i
o
n
d
r
i
v
e
r
MPI Simatic
PROFIBUS-DP
SOFTNET
TCP/H1
TCP direct
COMx MPI
PROFIBUS-DP
IBHLink MPI
PROFIBUS-CP
Ethernet-CP
Ethernet
RS-232
RS-232, USB, MPI,
Ethernet, Teleservice
PROFIBUS
Ethernet
Ethernet
S7-300/400
PROFIBUS-DP
Bus server S7
System requirements
Supported protocols
10 2.0 EN L

2.2.1 IBHLink
2.2.2 COMxMPI
Use "MPI Simatic" as protocol if the Siemens communication driver (V5.0 or higher) is
installed on your PC or simultaneous access with Lenze and Siemens software is required.
> "x" stands for the number of the COM port used.
2.2.3 MPI Simatic
2.2.4 PROFIBUS-DP
PC interface Transmission medium PLC interface Additional software required
Ethernet Ethernet IBHLink adapter cable
Ethernet MPI
IBHNet (V1.1 or higher)
COMx RS-232 PC adapter
RS-232/485 MPI
-
USB USB PC adapter
USB MPI
Siemens communication driver
(V5.0 or higher)
COMx RS-232 PC adapter
RS-232/485 MPI
Siemens CP5611
(PCI card)
MPI MPI
Siemens CP5511
(PCMCIA card)
Modem Teleservice Siemens teleservice
adapter MPI
(V5.0 or higher) and
Siemens teleservice
(V5.0 or higher)
Ethernet Ethernet IBHLink adapter cable
Ethernet MPI
(V5.0 or higher) and
IBHNet (V1.1 or higher)
COMx RS-232 PC adapter RS-232/485
PROFIBUS-CP
(V5.0 or higher)
USB USB PC adapter USB
PROFIBUS-CP
Siemens CP5611
(PCI card)
PROFIBUS PROFIBUS-CP
Siemens CP5511
(PCMCIA card)
L 2.0 EN 11
Bus server S7
System requirements
Supported protocols

2.2.5 SOFTNET TCP/H1
Under normal circumstances, the TCP protocol is used. When using older CPs it may
happen that only the Siemens H1 protocol is supported. This is why the bus server S7 also
supports the H1 protocol.
2.2.6 TCP direct
If the corresponding Siemens software is installed on your PC, we recommend to use
"SOFTNET TCP/H1" as protocol. Also use "SOFTNET TCP/H1" as protocol if simultaneous
access with Lenze and Siemens software is required.
Ethernet Ethernet TCP/H1 Ethernet-CP Siemens SOFTNET/SIMATICNET
(V3.0 or higher)
Ethernet Ethernet TCP Ethernet-CP -
Bus server S7
System requirements
Supported PLC hardware
12 2.0 EN L

2.3 Supported PLC hardware
The following PLC hardware is supported: Siemens S7-300 and S7-400
> For S7-400, the controllers must be connected to the PROFIBUS of the CPU.
> For S7-300, the controllers can also be connected to the PROFIBUS-CP.
> If an Ethernet connection is to be established between PC and PLC, the PLC must be
equipped with an Ethernet CP (e.g. CP343-1, CP443-1).
> If a PROFIBUS connection is to be established between PC and PLC, the PLC must be
equipped with a PROFIBUS CP (e.g. CP343-5, CP443-5).
Required PLC data blocks/RAM requirements
Two data blocks are required for data exchange with the drives. In addition, one function
block instance is to be activated for each drive to be addressed. This means that one data
block per drive (instance DB) is required for data management.
The RAM requirements of the PLC can be obtained from the following table:
Function block type RAM requirements Number of function blocks required
Data exchange DB 508 bytes 2
Instance DB 150 bytes Number of drives
@ Note!
The number of PLCs which can be simultaneously addressed depends on the
interface module of the PC or PLC.
The Siemens PC adapter only supports 4 communication links. Therefore, only
4 PLCs can be addressed simultaneously.
For more information, please refer to the documentation on the interface
module provided by the manufacturer.
L 2.0 EN 13
Bus server S7

3 Software installation
How to install the S7 bus server...
1. Start Windows.
2. Insert the CD-ROM DriveServer with bus server S7" into your CD-ROM drive.
If the auto-start function of your CD-ROM drive is activated, the installation
program will be started automatically and you can proceed with step 5.
3. Go to Start menu and select Run...
4. Enter the letter for your CD-ROM drive followed by ":\setup.exe"
(e.g. "e:\setup.exe") and confirm the entry by clicking OK.
5. Follow the instructions of the installation program.
Tip!
For notes about the DCOM configuration, please refer to the DriveServer"
Software Manual.
@ Note!
Windows NT/2000/XP
Installation under Windows NT/2000/XP requires administrators rights!
Windows 98
DCOM is not installed as standard in Windows 98 and must be installed
separately, if necessary.
The bus server installation program checks if DCOM has been installed and
suggests to install DCOM if DCOM is not available.
The bus server software cannot be installed without DCOM.
Bus server S7
Component selection
14 2.0 EN L

3.1 Component selection
From the installation program of the DriveServer you can select the components you want
to install on your PC. The selection is done in two steps:
1. Selection of the DriveServer components (see "DriveServer" Software Manual)
2. Selection of the bus server components:
Component Information
Bus server S7 Driver for communication with Siemens SIMATIC S7 PLC
Online Help
(German/English)
Context-sensitive help for the program
Online Manuals
(German/English)
Manuals for the program in Portable Document Format (PDF) for display in
Adobe Reader
L 2.0 EN 15
Bus server S7
Configuration
Configuration of the interface module

4 Configuration
4.1 Configuration of the interface module
If "MPI Simatic", "PROFIBUS-DP" or "SOFTNET TCP/H1" is to be used as protocol, the
corresponding interface module must be configured first so that the bus server can
establish a communication with the PLC.
For all other protocols the required communication parameters are directly adjusted in the
bus server configurator!
How to configure the PG/PC interface...
1. Go to the Start menu and select SettingsSystem control.
2. Double-click the Set PG/PC interface symbol to open the Set PG/PC interface dialog
box:
3. Configure the interface according to your system environment and confirm the
settings by clicking OK.
@ Note!
The configuration program for the interface module is part of the Siemens
communication drivers which can be automatically installed during the
installation of the STEP 7 configuring software but also by various other Siemens
software products.
Bus server S7
Configuration
Bus server configuration
16 2.0 EN L

4.2 Bus server configuration
The bus server is configured via the "S7 configurator" program. Upon configuration, the
PLC and the drives configured in the respective PLC program are selected.
How to start the S7 configurator...
1. Go to the Start menu and select
ProgramsLenzeDriveServerS7 configurator.
2. Confirm the info dialog field Lenze OPC S7 server by clicking OK.
The configuration saved last will be loaded automatically.
If you want to create a new configuration, select FileNew.
4.2.1 User interface of the S7 configurator
The S7 configurator is divided into two sections:
> The left side indicates the configuration entries in form of a tree, similar to directories
of the Microsoft Explorer.
> The right side shows possible settings for the configuration entry selected from the
tree.
If you create a new configuration, the first visible entry will be Lecom".
L 2.0 EN 17
Bus server S7
Configuration

Tip!
If a plus sign appears in front of a configuration entry, this configuration entry
has further subelements.
A click on the plus sign opens the list of subordinated configuration entries.
A click on the now appeared minus sign closes the subordinated
configuration entries again.
A detailed description of the different tabs can be found in the appendix.
S7 configurator - settings (L 62)
4.2.2 Automatic PLC detection
First the PLCs connected must be specified. For this purpose the scan function of the S7
configurator can be used for the protocols "MPI Simatic", "PROFIBUS-DP" and "COMx MPI".
> For all other protocols and as an alternative to the scan function PLCs can also be added
manually to the configuration.
Manual addition of PLCs (L 19)
Tip!
The scan function scans the MPI network for connected PLCs and for the drives
configured in the respective PLC program.
Configuration of the bus server is only possible when the PLC program has been
completed.
In order that the drives configured in the PLC program can be detected by the
scan function, it is required that the PLC with the completed PLC program has
been in the RUN mode once. Only then the instance data which also includes the
PROFIBUS address are stored in the online data block!
It might be useful to perform the scanning already earlier to check the
communication connection.
How to search for PLCs connected...
1. Enter the number of the PLC slot on which the CPU card is plugged into the input
field Slot number.
The slot position of the CPU card depends on the PLC type and the power supply
used for the PLC.
2. Select the protocol to be used from the protocol list field.
If the interface module used supports several protocols and if the Siemens
communication drivers are installed on the PC, it is recommended to select that
protocol which uses the Siemens communication drivers.
Bus server S7
Configuration
18 2.0 EN L

3. Click Scan to start the search.
The scanning progress is indicated in a dialog box.
If several CPUs are connected to the bus and the CPU cards are plugged into
different slots, the scan must be repeated several times with the corresponding
setting in the Slot number input field.
The PLCs found and the drive configured in the PLC program are added to the tree view as
configuration entries.
Tip!
The S7 configurator automatically creates several OPC items for every drive. It is
thus possible for the DriveServer to detect the drive automatically.
Scan at the servers start
If the Scan at the servers start control field is activated, the PLC and the drives configured
in the PLC program are detected during every start of the bus server.
> This option is useful if the bus server is connected to a portable PC which is operated at
different systems.
> If the bus server is operated at only one system, this option should be deactivated to
speed up starting the bus server.
> If several CPUs are connected to the bus:
Only one CPU slot number is considered for the scan during the start of the bus
server.
If the CPU cards are plugged on different slot positions, this option is not useful since
not all PLCs can be found.
L 2.0 EN 19
Bus server S7
Configuration

4.2.3 Manual addition of PLCs
For the protocols "SOFTNET TCP/H1" and "TCP direct" and alternatively to the scan function
you can also add the PLCs connected manually to the configuration.
How to add a PLC manually to the configuration...
1. Click the Add S7 control to add a PLC to the configuration.
2. Enter a name for the PLC into the Name of the new PLC input field.
The name may only contain letters. It must not contain any special characters.
3. Click the OK button to accept the entry.
The PLC is added with the entered name as configuration entry to the tree view,
and you can now configure its parameters (protocol, address, CPU slot number etc.)
in the dialog area on the right.
Bus server S7
Configuration
20 2.0 EN L

4.2.4 PLC parameters
The following table contains all parameters relevant for the PLC configuration. Which
parameters can be set depends on the protocol selected.
Parameter name Meaning
Protocol Selection of the connecting path between PC and PLC.
Connection to the target system (L 8)
Response time Maximum time in [s], response of the PLC is waited for.
When the PLC does not respond within the time specified, a faulty connection is
possibly the reason and an error is reported.
Normally, the standard setting can be maintained.
PLC address
1)
Address of the PLC connected to the PC.
In case of an MPI-/PROFIBUS connection, the MPI-/PROFIBUS address must be set
only.
In case of an Ethernet connection, the IP or H1 address must be set in addition to
the MPI address.
CPU slot number Slot in which the CPU card of the PLC is plugged.
Standard: 2
In case of subsystems, this parameter refers to the PLC in the subsystem, not to
the master PLC. Configuration of subsystems (L 23)
Mounting rack number Mounting rack in which the CPU card of the PLC is plugged.
Standard: 0
In case of subsystems, this parameter refers to the PLC in the subsystem, not to
the master PLC. Configuration of subsystems (L 23)
PC-MPI address
1) 2)
MPI- or PROFIBUS address of the PC
Baud rate
2)
Transmission speed on the MPI bus between PC and PLC.
Max. MPI address
2)
Highest node address on the MPI bus.
Single master
2)
Activate this control field if the PC is the only master on the bus. Otherwise the
system could come to a standstill if due to a communication error a token gets lost.
Routing in MPI/TCP/H1
subnetworks
Selection of the subnetwork type if the selected protocol permits routing in
subsystems. Configuration of subsystems (L 23)
For protocols and PLCs which support the "Routing function".
Subnetwork ID Identification of the subnetwork.
Target MPI/TCP/H1 address Address of the PLC in the subsystem.
Job list DB number
1)
Number of the data block which is used for data exchange between PC and PLC.
This number is also detected by the scan function.
If the number of the included Lenze blocks are not changed, enter "80" for DB80.
Maximum number of devices
to be scanned
For time reasons, especially when scanning for connected devices during the server
start, the highest drive address to be checked can be entered.
If the value "0" is set, all drive addresses are scanned (standard).
Scan during server start The PROFIBUS addresses used are automatically detected and do not need to be
configured manually.
1)
This parameter is already set correctly after the PLC has been detected automatically.
2)
This parameter is only valid for the "COMx MPI" protocol.
L 2.0 EN 21
Bus server S7
Configuration

4.2.5 Automatic drive detection
If the PLC is connected to the PC and the PLC program has already been transferred to the
PLC, the drives configured in the PLC program can be automatically detected if this had not
yet been done by the automatic detection of the PLC.
How to scan for drives connected...
1. Select a corresponding PLC in the tree view.
2. Ensure that the PLC with the completed PLC program has been in the RUN mode
once. Only then the instance data which also includes the PROFIBUS address are
stored in the online data block!
3. Click the Scan button to start the scan for drives.
The scan progress is indicated in a dialog box.
The detected drives are added to the tree view as configuration entries below
the PLC selected.
Furthermore the scan function automatically detects the number of the
"DB OPC" data block which is used for the data exchange between PC and PLC.
Tip!
The S7 configurator automatically creates several OPC items for every drive. It is
thus possible for the DriveServer to detect the drive automatically.
Scan during server start
If the Scan at the servers start control field is activated, the drives configured in the PLC
program of the corresponding PLC are detected during every start of the bus server.
> This option is useful, if the bus server is connected to a portable PC which is operated
at different systems.
Bus server S7
Configuration
22 2.0 EN L

4.2.6 Manual addition of drives
As an alternative to using the scan function you can also add drives to the configuration
manually.
How to add a drive manually to the configuration...
1. Select the PLC from the tree view to which a drive is to be added.
2. Click the Add device button.
3. Enter a name for the device into the Name of the new device input field.
The name may only contain letters. It must not contain any special characters.
4. Click the OK button to accept the entry.
The device is added as configuration entry to the tree view with the name entered
and you can now configure its device parameter in the dialog area on the right.
4.2.7 Drive parameters
Parameter name Meaning
DP address of the device PROFIBUS address
Time-out Time in [s], which the bus server is maximally waiting for the processing of a
parameter job.
During a parameter set transfer, many jobs are transmitted at the same time so
that, depending on the cycle time of the CPU, waiting times of up to 20 - 30 s may
arise for some jobs.
In case of problems during the parameter set transfer, always try a higher time-
out setting first.
L 2.0 EN 23
Bus server S7
Configuration

4.2.8 Configuration of subsystems
If the PLC which is connected to the PC is provided with a "routing function", it is also
possible to access controllers which are not connected to the PROFIBUS of this (master) PLC
but the PROFIBUS of a subordinated PLC.
The following illustration shows an example for such an architecture:
> The SIMATIC 400 in this example is the master PLC and directly connected to a PC via
Ethernet.
> The SIMATIC 300 is the subsystem, to which a controller is connected via PROFIBUS.
> An MPI connection exists between the master PLC and the subsystem.
> Note that not only both PLCs but also the PC with its properties must be entered into
the STEP 7 project.
For this purpose use the STEP 7 service program "NetPro".
Required configuration steps
To access the controller at the subsystem (of SIMATIC 300), the following configuration
steps are required:
1. Manual addition of the master PLC to the configuration. Manual addition of PLCs (L
19)
2. Selection of the protocol and input of the address of the master PLC.
3. Entry of the slot number and the mounting rack number of the subsystem.
4. Selection of the subnetwork type (in this example: "MPI").
5. Entry of the subnetwork ID (for this see the tip on the following page).
6. Entry of the address of the subsystem (MPI, TCP or H1 address).
After these steps the subsystem can already be accessed and now it can be detected by
means of the scan function on which addresses the controllers in the PLC program of the
subsystem have been configured.
Bus server S7
Configuration
24 2.0 EN L

Tip!
In the STEP 7 program the subnetwork ID can be detected as follows:
Start the "NetPro" service program, e.g. by double-clicking a network in the
SIMATIC manager or by clicking "Connections" with focused CPU.
Click with the right mouse button on the network which connects all control
elements and select the Object properties command in the context menu
shown.
Enter the subnetwork ID indicated in the Object properties dialog box into the
Lenze S7 configurator.
The following illustration shows a possible configuration:
Tip!
If controllers are connected both to the PROFIBUS of the master PLC and the
PROFIBUS of the subsystem, two PLCs must be configured in the Lenze S7
configurator.
In this case, the data for the master PLC are identical for both configuration
entries.
For the PLC shown by the subsystem, the subsystem data must be entered
additionally, as described before.
L 2.0 EN 25
Bus server S7
Configuration

4.2.9 Manual removal of configuration entries
Configuration entries (PLCs, devices, OPC items, etc.) can be removed from the tree view
any time.
How to remove a configuration entry...
1. Select the configuration entry from the tree view, which is to be removed again
including all subordinated configuration entries.
2. Click the Delete button.
Before the entry is deleted, a safety query is made.
3. Confirm the safety query with Yes to remove the configuration entry from the tree
view or click No to abort the process.
4.2.10 Saving the current configuration
Select FileSave to save the current configuration.
Tip!
Select FileSave as... to save the current configuration with a different name.
4.2.11 Exit the S7 configurator
Select FileExit to exit the S7 configurator.
@ Note!
If there are changes not saved yet, it is queried if these changes are to be saved.
Bus server S7
Creating a STEP7 project
Overview of the STEP7 blocks
26 2.0 EN L

5 Creating a STEP7 project
5.1 Overview of the STEP7 blocks
The following figure gives you an overview of the different STEP7 blocks:
In this description symbolic names are used for the blocks. If you want to use these names
instead of the corresponding block numbers in the STEP7 project, you first have to create
them in the symbol table.
In the following subchapter, the program structure will be explained in detail.
Symbolic
block name
Block number Function
FB DRIVE FB90 One instance of the "FB DRIVE" is to be called for each drive.
Allocate one instance data block to each instance.
Each instance checks cyclically, if there is a job for the corresponding drive
in the data block "DB OPC" or "DB S7PAR" and executes it, if required.
DB OPC db80 "DB OPC" is used for data exchange between the bus server and the
drives.
In the "DB OPC" a list is stored with jobs for the corresponding controllers.
DB S7PAR db81 Use "DB S7PAR" to write parameter data out of the PLC.
The parameter data jobs are written into the "DB S7PAR" by means of the
"FC parameter" function.
FB DRIVE
DB OPC
PROFIBUS-DP
PA PE
DB S7PAR
S7
PA PE
Process data channel
Drive 1
OPC via
S7 protocol
FC
parameter
FC
process
data
L 2.0 EN 27
Bus server S7
Typical program flow

5.2 Typical program flow
The following figure shows the typical sequence of a STEP7 program with OPC access:
> The "OB1" standard block forms the basis which is included in every STEP7 program
and which is automatically called at each cycle. From "OB1", all other function blocks
are called which are required for the corresponding application.
> In the illustration the "OB1" standard block calls the "FC1" function which activates the
accesses to the drives.
> In every cycle the "FC process data" function is called in "FC1" to process the process
data. Since the access to the process data via OPC is not possible, the exchange
between PLC and OPC jobs can be ignored here.
> For the OPC access the "FB DRIVE" block is called repeatedly. Here, an instance with an
own block must be created for each drive.
> Each instance of "FB DRIVE" accesses two data blocks, the "DB OPC" and the "DB S7PAR".
> Each time the "FB DRIVE" is called (multiple use), a special instance data block has to be
transmitted which contains the data for the respective drive, e.g. the PROFIBUS
address. The "FB DRIVE" itself does not use any global data.
> "DB OPC" and "DB S7PAR" must not be changed by the user. However, the user may
write parameter data jobs from the PLC by means of the "FC parameter" function into
the corresponding fields of the "DB S7PAR".
> The "FC parameter" function can be called at any position in the "FC1".
> The change between the parameter data jobs from the OPC and the PLC is made by the
"FB DRIVE".
> The "FC process data" function is not affected by this and continues to be called in every
cycle.
DBx OPC
DBx
DBx
FC1
DBx
OB1
DB S7PAR
FC
process data
FB DRIVE
parameter
d 2 rive
FB DRIVE
parameter
drive 1
FB DRIVE
parameter
d n rive
FC
process data
FB DRIVE
parameter
FB DRIVE
parameter
FB DRIVE
parameter
FC
parameter
FC
parameter
Bus server S7
Files provided
28 2.0 EN L

5.3 Files provided
5.3.1 STEP7 library
The different blocks are available as a library and can be used in every STEP7 program. The
following table gives you an overview of the blocks available in the library:
After the "DriveServer with bus server S7" software is installed, the library is saved as
standard in the directory: "C:\Programs\Lenze\DriveServer\S7".
How to integrate the library into the STEP7 environment...
1. Select FileDearchive in the S7 manager.
2. Select the "Ldslib.arj" file in the subdirectory "\S7" of the DriveServer installation.
3. Select the target directory.
(Normally the subdirectory "\s7libs" of the STEP7 installation.)
Block number Symbolic
block name
Function Version
DB30 Data block for the data exchange with external PROFIBUS
communication processor (CP)
When using UDT93 (transmission).
DB31 Data block for the data exchange with external PROFIBUS
communication processor (CP)
When using UDT93 (receive).
DB80 DB OPC Data block for parameter data jobs via OPC.
DB81 DB S7PAR Data block for parameter data jobs from the PLC.
FB90 FB DRIVE Function block
One instance is to be created for each drive.
2.3
FB91 FB DRIVE CP Function block
One instance is to be created for each drive.
1.0
FC90 FC parameter Function for parameter data jobs from the PLC. 1.2
FC91 FC process data Function for process data access (3 process data words) 1.2
FC92 FC process data Function for process data access (2 process data words) 1.2
FC93 FC process data CP Function for process data access (3 process data words)
When using an external PROFIBUS communication
processor (CP)
1.3
FC94 FC process data CP Function for process data access (2 process data words)
When using an external PROFIBUS communication
processor (CP)
1.3
UDT90
...
UDT93
Universal data type for parameter data access to Lenze drive
controllers.
L 2.0 EN 29
Bus server S7
Files provided

5.3.2 STEP7 example programs
The scope of supply of the bus server S7 includes the following example programs which
only differ in the hardware configuration.
After the "DriveServer with bus server S7" software is installed, the example programs are
saved as standard in the directory: "C:\Programs\Lenze\DriveServer\S7".
Tip!
If you want to use one of the example programs, adapt the hardware configuration
to your system environment.
Detailed information on creating a STEP7 program:
Creating a STEP7 program (L 33)
How to integrate an example program into the STEP7 environment...
1. Select FileDearchive in the S7 manager.
2. Select the corresponding file ("Ldsexmpl.arj/.zip" or "Ldsexmp2.arj/.zip") in the
subdirectory "\S7" of the DriveServer installation.
3. Select the target directory.
(Normally the subdirectory "\s7proj" of the STEP7 installation.)
Tip!
After dearchiving the example project, it is queried if the project shall be opened. If
you negate it, the project may not be entered into the project list and must be
opened later via the Browse command.
5.3.3 Device description files of the Lenze drives
After the "DriveServer with bus server S7" software is installed, the device description files
of the Lenze drives for PROFIBUS are saved in the "C:\Program\Lenze\DriveServer\GSD"
directory. Copy these files into the subdirectory "\s7data\GSE" of the STEP7 installation.
Tip!
Current versions of the GSE files can be found on our Internet homepage
http://www.Lenze.de in the ServiceDownloadsPROFIBUS area.
File name Hardware configuration
Ldsexmpl.arj/zip PLC S7-400 with CPU412-2DP
Ldsexmp2.arj/zip PLC S7-300 with CPU312-2DP and CP342-5
Bus server S7
Creation of new projects
30 2.0 EN L

5.4 Creation of new projects
Tip!
The following steps are described exemplarily with STEP7 in version 5.0. In other
STEP7 versions the single dialogs may vary slightly.
Select FileAssistant 'New project' in the SIMATIC manager for a guided project
creation.
When creating the project, observe the following points:
> Select your hardware.
In our example we use a SIMATIC 300 with CPU 315-2 DP.
> Blocks need not be added yet.
> We recommend to use IL as the language for all blocks.
Once the required information has been entered, the assistant creates a project structure
similar to the one shown below:
The next step is to configure the MPI and the PROFIBUS interface for the project. More
details about this can be found in the next chapter.
5.5 Hardware configuration
The Hardware Manager is used to configure the hardware used.
How to open the Hardware Manager...
1. Select the CPU 315-2 DP entry in the STEP7 project structure.
2. Double-click the Hardware symbol in the right window area to open the Hardware
Manager.
So far, the Hardware Manager only lists the CPU-315-2 with integrated DP master.
L 2.0 EN 31
Bus server S7
Hardware configuration

5.5.1 Configuring the MPI interface of the CPU
How to configure the MPI interface of the CPU...
1. With the right mouse button click the CPU315-2 DP(1) entry to open the Context
menu.
2. Go to Context menu and select Object properties to open the Object properties
dialog box.
3. Click the Properties button in the General tab in the Interface group field to open
the Properties - MPI interface dialog box.
4. Configure the MPI address and the MPI subnetwork in the Parameter tab.
5.5.2 Configuring the PROFIBUS interface of the CPU
How to configure the PROFIBUS interface of the CPU...
1. Select the DP master line in the Slot table .
2. Select InsertDP master system, unless a DB master system has been created
automatically.
If a DP master system has already been automatically created:
With the right mouse button click the DP master system entry to open the
Context menu.
Go to Context menu and select Object properties to open the DP master system
dialog box.
3. Enter the DP node address of the DB master into the DP master system dialog box.
4. Moreover, create a new PROFIBUS subnetwork with DP profile and the required
baud rate.
5. Select ViewCatalog to open the hardware catalog to add PROFIBUS devices.
6. Select the corresponding device from the list and use the mouse to drag it onto the
graphically illustrated PROFIBUS string.
If no Lenze modules are available in the hardware catalog (e.g. Lenze module
2131 under PROFIBUS-DPFurther field devicesDrives2131), it must be
checked if the Lenze GSE files are saved on the hard disk in the correct directory.
If required, update the catalog via ExtrasUpdate catalog.
7. Select a configuration for the corresponding device.
Here it is decisive to select a configuration which consistently transmits the
parameters with a length of 8 bytes.
Use e.g. "PAR(8ByteKons.)+PZD(2WorteKons)" or
"PAR(4Wortekons.)+PZD(3WorteKons)".
Bus server S7
Hardware configuration
32 2.0 EN L

8. Enter the PROFIBUS device address of the drive controller onto which the module
is plugged.
In STEP7 from version 5.1 there is no automatic call for configuration selection.
Mark the desired configuration in the catalog window and draw the object with
the mouse into the module list.
9. Double-click the first line in the Module list to open the Properties of DP slave dialog
box.
The Hardware Manager automatically suggests a suitable I/O address, in this
example I/O address 1000.
Each device may have different I/O addresses. It is important that the input and
the respective output use the same I/O address.
The I/O addresses allocated must be indicated later when calling the "FB DRIVE"
and should therefore be written down here.
We recommend that I/O address 1000 is used for initial testing.
10. Enter the settings for the process data channel into the second line of the Module
list.
The settings depend on the respective application.
The settings done must be indicated later when calling the "FB DRIVE" and
should therefore be written down here.
The hardware configuration for the drive is now complete.
11. Further drives require an analog processing.
5.5.3 Configuring further hardware
Depending on the hardware equipment of the PLC used, other hardware components may
be configured with the Hardware Manager e.g. communication processors for PROFIBUS or
Ethernet.
> More information can be obtained from the corresponding hardware documentation.
> After the hardware configuration has been completed, you can exit the Hardware
Manager and continue with the implementation of the Lenze function blocks into the
project. Learn more about this in the following chapter.
L 2.0 EN 33
Bus server S7
Creating a STEP7 program

5.6 Creating a STEP7 program
To implement the Lenze function blocks, several options are possible. For a simple test, the
blocks supplied in the SIMATIC manager can be copied from the library into a new project.
In the first step, communication is to be performed via OPC with only one drive connected
to the PROFIBUS master of the CPU.
5.6.1 Accessing a drive via OPC
Tip!
For a first commissioning, the example programs provided can be used. Only the
hardware configuration must be adapted to your system environment.
STEP7 example programs (L 29)
If you want to create a program on your own, you simply have to integrate the supplied
blocks into the SIMATIC Manager.
@ Note!
If you have configured drive controllers in your project which are temporarily
disconnected from the mains, please observe the following:
Controllers which are disconnected from the mains, and thus being
deenergised, are not recognised as PROFIBUS nodes anymore by the PLC. This
can be avoided by supplying the function module/fieldbus module with
external voltage.
Instances of the "FB DRIVE" for disconnected controllers must be skipped in
the PLC program.
A query can be made via the status words of the blocks "FC91", "FC92",
"FC93" or "FC94". If the status word of these blocks returns a "0", the
controller is not connected (or not available). and the respective "FB DRIVE"
instance must be skipped. Control of the parameter data access (L 54)
When an S7-300 is used, not only can controllers be addressed that are directly
connected to the PROFIBUS master of the CPU card but also controllers with are
connected to an external PROFIBUS communication processor (CP).
For this use the "FB DRIVE CP" block instead of the "FB DRIVE" block.
Bus server S7
34 2.0 EN L

How to create an own program...
1. Create a new project with the "OB1" block.
2. Select FileOpen.
3. Click Libraries and select LenzeDriveServer.
In the new window, you will find all blocks contained in the LenzeDriveServer"
library.
4. Enter the blocks "FB90", "DB80" and "DB81" simply per Drag and Drop into your
new project.
5. Call an instance of the "FB90" in the "OB1".
For this enter the following program code in IL: CALL FB90, DBxxx
(xxx stands for a free data block number). The data block will be automatically
created by this call.
6. Edit the list of transfer parameters.
Example for a transfer parameter list:
Transfer parameters used in the above list:
> The Tag parameter must be left open.
> In this example, the PROFIBUS address is address 9.
> I/O address "1000" is set as device parameter in the Hardware Manager.
> "T1" is to be used as timer.
> Since the Time-out parameter was not specified, the default setting (1 s) is used.
> The flag byte "MB100" is used to ascertain if an instance is accessing an I/O.
Tip!
The PROFIBUS and I/O addresses must be configured twice, once in the Hardware
Manager and once in the calling program. It must be ensured that both data
correspond to each other!
CALL " Lenze- Dr i veSer ver _FB" , DB100 FB90
Tag : =
PB_Addr ess : =B#16#9
EA_Addr ess : =1000
Dr i veSer ver _DB : =" Lenze- Dr i veSer ver _FB" DB80
Dr i vePar _DB : =" S7- Par amet er " DB81
Ti mer Nr : =T1
Ti meOut : =
Busy : =MB100
BE
L 2.0 EN 35
Bus server S7

Provided that a drive is available at PROFIBUS address 9, the system can be operated with
this program.
> Load the program into the PLC and try to detect the drive automatically using the S7
configurator.Automatic PLC detection (L 17)
> Once the completed configuration has been registered and saved with the S7
configurator, the DriveServer can access all parameters of the drive.
Tip!
The PLC programs can be written in any PLC programs, the "FB DRIVE" (FB90)
function block is, however, protected, and cannot be processed in any of these
languages.
5.6.2 Accessing several drives via OPC
The project is to be expanded to enable communication with several drives.
> Add the corresponding devices to the Hardware Manager as described for the drive
already configured.
> Select one instance of the "FB DRIVE" (FB90) function block for every drive connected in
the program.
One instance data block, one timer and one flag bit each is allocated to every
instance.
The remaining parameters are to be determined in the same way as described in the
example of communication with one drive only.
5.6.3 Accessing the drives connected to PROFIBUS-CPs
When an S7-300 is used, not only can controllers be addressed that are directly connected
to the PROFIBUS master of the CPU card but also controllers with are connected to an
external PROFIBUS communication processor (CP).
> For this, please use the block "FB DRIVE" instead of the block "FB DRIVE CP" in the STEP7
program.
Bus server S7
36 2.0 EN L

Example for a transfer parameter list:
Transfer parameters used in the above list:
> The Tag parameter must be left open.
> In this example, the PROFIBUS address is address 9.
> The FirstDriveDW parameter defines the byte position of the first data word of the
controllers connected.
For each controller, 8 data words are reserved in the data blocks "DriveSend_DB" or
"DriveRecv_DB". The first 4 data words are required for parameter access and the
following 4 data words for process data accesses.
The controllers must have successive I/O addresses.
> "DriveSend_DB" is the send block for communication with CP.
The block consists of up to 15 variables of data type "UDT91" ... "UDT93". The data
type to be used depends on the number of process data words used.
The scope of supply includes "DB30" with "UDT93" (4 process data words).
> "DriveRecv_DB" is the receive block for communication with CP.
The block consists of up to 15 variables of data type "UDT91" ... "UDT93". The data
type to be used depends on the number of process data words used.
The scope of supply includes "DB31" with "UDT93" (4 process data words).
> "T1" is to be used as timer.
> Since the Time-out parameter was not specified, the default setting (1 s) is used.
> The flag byte "MB100" is used to ascertain if an instance is accessing an I/O.
CALL " Lenze- Dr i veSer ver _FB" , DB100 FB91
Tag : =
Fi r st _Dr i veDW : =0
Dr i veSend_DB : =" Lenze- Dr i veSer ver _Send" DB30
Dr i veRecv_DB : =" Lenze- Dr i veSer ver _Recv" DB31
Dr i veSer ver _DB : =" Lenze- Dr i veSer ver _FB" DB80
Dr i vePar _DB : =" S7- Par amet er " DB81
Ti mer Nr : =T1
Ti meOut : =
Busy : =MB100
BE
@ Note!
If you want to address controllers connected to the PROFIBUS master of the CPU
and controllers connected to an external PROFIBUS communication processor
(CP), it must be ensured that each PROFIBUS address is only assigned once.
It is not possible to address two controllers with the same PROFIBUS address,
even if the controllers are operated at different PROFIBUS lines.
L 2.0 EN 37
Bus server S7

Tip!
You can use the provided "Ldsexmp2.arj" example program for testing.
If possible, the controllers should always be operated with the PROFIBUS master
of the CPU, since communication will thus be slightly faster.
5.6.4 Access to process and parameter data from the PLC
The following functions from the "LenzeDriveServer" library can be used to access process
and parameter data from the PLC:
Tip!
The aforementioned example program "Ldsexmpl.arj" contains both OPC and PLC
accesses, and can be used as basis for your own program developments.
Block number Symbolic
block name
Function
FC90 FC parameter Function used to write parameter data jobs in DB S7PAR.
FC90 (FC parameter) (L 45)
FC91 FC process data Function for process data access (3 process data words)
FC91 (FC process data three words) (L 47)
FC92 FC process data Function for process data access (2 process data words)
FC92 (FC process data, two words) (L 47)
FC93 FC process data Function for process data access (3 process data words) when using an
external PROFIBUS communication processor (CP)
FC93 (FC process data, three words, CP) (L 48)
FC94 FC process data Function for process data access (2 process data words) when using an
external PROFIBUS communication processor (CP)
FC94 (FC process data, two words, CP) (L 49)
Bus server S7
Testing the STEP7 program
38 2.0 EN L

5.7 Testing the STEP7 program
When the program has been completed, it can be loaded into the PLC and tested. The S7
configurator can be used for program testing.
You can use the S7 configurator to scan the PLC program for the drives used.
> The configuration tool first tries to detect which data blocks are allocated as job lists.
> The instance data blocks for the drives are then scanned.
For every drive found, a corresponding configuration entry is created in the tree
structure in the left part of the S7 configurator. The block number of the job list is
entered into the input field provided.
If these entries correspond to the expected result, further tests can be made with the
DriveServer:
> Save the configuration file of the S7 configurator and start the configuration of the
DriveServer. For more information, please refer to the "DriveServer" Software Manual.
5.7.1 Structure of the DriveServer name area
Each controller has its own name within the DriveServer. This name consists of the
following elements separated by a hyphen.
> Address of the master PLC
> Subnetwork ID (in round brackets, only if a slave PLC exists)
> Address of the slave PLC (only if a slave PLC exists)
> PROFIBUS address of the controller
Example:
> Two controllers with PROFIBUS address "9" and "10" are connected to a master PLC with
MPI address "2".
> In addition, a slave PLC is connected to this master PLC via TCP.
> The corresponding TCP subnetwork has the subnetwork ID "0086:0006"
> The slave PLC has the IP address "192.168.14.164"
> A controller with PROFIBUS address "4" is connected to the slave PLC.
L 2.0 EN 39
Bus server S7
Optimisation of the cycle time

5.8 Optimisation of the cycle time
When the "FB DRIVE" block is called, the PLC cycle is always under load, even if no
parameter communication takes place. Since several parameters are checked when
"FB DRIVE" is called, programming errors can be detected and the corresponding error
messages can be indicated. However, the checking costs computing time.
To save computing time, you can operate the "FB DRIVE" in expert mode. This reduces the
required computing time by approx. 50 %.
How to activate the expert mode for FB DRIVE...
1. Open the instance data block.
2. Set the variable XpertMode to TRUE:
Tip!
If you have already created a program, which uses an older version of the "FB 90"
block, STEP7 will indicate different time stamps for the "FB 90" block and the
corresponding instance data block.
If so, go to the IL editor and create a new STEP7 instance data block. Then you can
use the expert mode.
@ Note!
When the expert mode is activated, "FB DRIVE" no longer checks the transferred
parameters!
Therefore, the expert mode should only be activated if you are sure that the
transferred parameters are correct.
Bus server S7
Accessing PLC data
40 2.0 EN L

5.9 Accessing PLC data
With the bus server S7, you can access both the parameters of the controllers and the PLC
data. You can use any OPC client to access the PLC data and, in some cases, to change them.
The following PLC data can be accessed via OPC:
> Flags
> Data blocks
> Inputs
> Outputs
> Timer
> Counter
For every data type to be read, a block must be added to the configuration within which the
individual OPC items must be configured.
See also: 'Block' tab (L 66)
'Item' tab (for block) (L 68)
L 2.0 EN 41
Bus server S7
Appendix
Time load of the PLC cycle

6 Appendix
6.1 Time load of the PLC cycle
The function blocks are called cyclically so that the PLC cycle is loaded permanently.
> The exact processing time depends on the computing power of the CPU.
> In case of effective communication, processing takes longer than if a block is called and
no job is available.
> In case of a completed PLC program, the cycle load can be reduced by switching on the
expert mode. Optimisation of the cycle time (L 39)
The following table contains typical processing times for two different CPUs:
Block number Processing time
Operation CPU 412-2 DP (S7-400) CPU 315-2 DP (S7-300)
FC90 < 0.1 ms 0.6 ms
FC91 < 0.1 ms 0.7 ms
FC92 < 0.1 ms 0.6 ms
FB90 < 1 ms 1 ... 7 ms
Expert mode < 1 ms 1 ... 3 ms
Idle state < 1 ms 1 ... 2 ms
FB91 1 ... 7 ms
Expert mode 1 ... 3 ms
Idle state 1 ... 2 ms
Bus server S7
Appendix
Transmission times
42 2.0 EN L

6.2 Transmission times
The following characteristics are important for the transmission times.
Output parameters:
> Global Drive Control (GDC) and DriveServer were used to load a complete parameter
set.
> An S7-315 (cycle time: 15 ms) and an S7-412 (cycle time: 2 ms) were used as PLC.
> PROFIBUS was set to 1.5 Mbit/s.
> Different interface modules were used.
> MPI transmission speed: 187.5 KBaud
> Baud rate of the serial interface for PC adapter connection: 38.4 KBaud
Transmission times detected for one parameter set:
@ Note!
Please note that the times indicated are minimum values!
If PROFIBUS is under high load or if a complex program is to be processed,
times will rise accordingly and may be considerably longer.
Communication disturbances and access to PROFIBUS devices that are not
available may substantially affect transmission times.
The transmission times also depend on the operating system used. To reach
optimum transmission times we recommend to use Windows NT, Windows
2000 or Windows XP.
PLC Controller Interface module
Type Connection PC/PLC connection Transmission time
S7-315 PROFIBUS on CPU 82xx vector CP5511 (187.5 KBaud) 44 s
CP342-5 82xx vector CP5511 (187.5 KBaud) 54 s
PROFIBUS on CPU 93xx CP5511 (187.5 KBaud) 107 s
CP342-5 82xx vector PC adapter 64 s
S7-412 PROFIBUS on CPU 82xx vector (FIF) CP5511 12 s
82xx vector (AIF) CP5511 13 s
82xx vector (FIF) PC adapter 24 s
82xx vector (FIF) Ethernet 11 s
93xx CP5511 30 s
93xx PC adapter 56 s
93xx Ethernet 28 s
L 2.0 EN 43
Bus server S7
Appendix
Transmission times

In summary, the following can be concluded:
> The transmission time considerably depends on the PLC cycle time. Basically the
following applies: The higher the cycle time the lower the influence of the bus speeds.
> A quick connection between PC and PLC accelerates the data transmission. However,
the cycle time is the limiting factor.
> Some CPU cards permit the transmission speed of the MPI bus to be set to up to
12 Mbit/s. If technically possible, this speed advantage should be taken.
> However, the PROFIBUS transfer rate only has a minor influence on the transmission
time of a parameter set.
Bus server S7
Appendix
Communication function parameters
44 2.0 EN L

6.3 Communication function parameters
6.3.1 FB90 (FB DRIVE)
Function block
> One instance is to be created for each drive.
> This function block requires the SFC14/15 functions.
6.3.2 FB91 (FB DRIVE CP)
Function block
> One instance is to be created for each drive.
> This function block requires the SFC58/59 functions.
Parameters Data type Possible values/meaning
Tag IN: STRING Special identifier; do not change
PB_Address IN: BYTE 0 ... 31 PROFIBUS address of the drive (hexadecimal)
Address 1 = "1", address 15 = "F"
EA_Address IN: INT I/O address of the drive (decimal)
DriveServer_DB IN: BLOCK_DB Data block with parameter data job list via OPC (e.g.
"DB80")
DrivePar_DB IN: BLOCK_DB Data block with parameter data list from the PLC (e.g.
"DB81")
TimerNo IN: TIMER Timer for monitoring the drive (e.g. "T1")
Time-out IN: S5TIME Timeout for monitoring.
If no specification is available, the default setting
"S5T#1S" (= 1 s) is used.
Busy OUT: BYTE Status of the function:
0x00 Not active (jobs have been processed)
0x01 Active (jobs are still being processed)
0x10 Incorrect identifier in the data block, incorrect data block
indicated or overwritten:Reload the data block
0x11 PB_Address parameter is incorrect (permitted values: 1 ...
123)
0x40 Count parameter is outside the range 0 ... 31
0xF0 In PB_Address no module is configured
0xF1 Length of source range <> length of configured user data
0xFF General I/O access error
PB_Address IN: BYTE 0 ... 31 PROFIBUS address of the drive (hexadecimal)
FirstDriveDW IN: INT Byte offset of the first data word of the drive in the data
exchange DB (decimal)
DriveSend_DB IN: BLOCK_DB Data exchange DB for transmit requests to the external
PROFIBUS communication processor (CP)
DriveRecv_DB IN: BLOCK_DB Data exchange DB for read requests from the external
L 2.0 EN 45
Bus server S7
Appendix

6.3.3 FC90 (FC parameter)
Function for parameter data jobs from the PLC.
DriveServer_DB IN: BLOCK_DB Data block with parameter data job list via OPC (e.g.
"DB80")
DrivePar_DB IN: BLOCK_DB Data block with parameter data list from the PLC (e.g.
"DB81")
TimerNr IN: TIMER Timer for monitoring the drive (e.g. "T1")
Time-out IN: S5TIME Timeout for monitoring.
If no specification is available, the default setting
"S5T#1S" (= 1 s) is used.
Busy OUT: BYTE Status of the function:
0x00 Not active (jobs have been processed)
0x01 Active (jobs are still being processed)
0x10 Incorrect identifier in the data block, incorrect data block
indicated or overwritten:Reload the data block
123)
0xF0 In PB_Address no module is configured
0xF1 Length of source range <> length of configured user data
0xFF General I/O access error
DrivePar_DB IN: BLOCK_DB Data block with parameter data (e.g. "DB80")
Count IN: INT 0 ... 31 Memory location in the "DrivePar_DB"
PB_Address IN: BYTE PROFIBUS address of the drive (hexadecimal)
R_W IN: BOOL TRUE Read drive
FALSE Write drive
Code IN: WORD Lenze code (hexadecimal): W#16#XX
Subcode IN: BYTE Lenze subcode (hexadecimal): B#16#XX
W_Value IN: DINT Value to be transmitted (FIX32)
Status OUT: BYTE Status of the function:
0x00 No errors
0x80 Controller error, for details see R_Value parameter
0x81 When "FB90" is called, the information on
"DriveServer_DB" or "DrivePar_DB" are invalid
(identification is missing or wrong).
Use the blocks supplied with the DriveServer library.
123)
0x83 Peripheral error, for details see R_Value parameter
0x84 Job could not be processed within the time set via the
TimeOut parameter.
Bus server S7
Appendix
46 2.0 EN L

R_Value OUT: DINT Read value (FIX32)
If the status = 0x83, a peripheral error occurred:
F0 F0 F0 F0 Module does not exist or SFC is not available
(decimal: -252 645 136)
F1 F1 F1 F1 Data length <> 8 bytes
(decimal: -235 802 127)
FF FF FF FF Other I/O error
(decimal: -1)
If the status = 0x80, the controller has reported an error.
More error codes than listed in the following and further details can
be obtained from the description of the corresponding PROFIBUS
interface module.
06 03 00 00 No right to access
06 05 00 10 Impermissible job parameter
06 05 00 11 Invalid subindex
06 05 00 12 Data length too large
06 07 00 00 Object does not exist
06 08 00 00 Data types do not correspond
08 00 00 20 Job cannot be executed at the moment
08 00 00 21 Cannot be executed due to local control
08 00 00 22 Cannot be executed due to operating status of the device
08 00 00 30 Exit value range
08 00 00 40 Collision with other values
Trigger INOUT: BOOL TRUE Start job processing.
Is automatically reset to FALSE, the job is completely
processed and the result is on hand.
L 2.0 EN 47
Bus server S7
Appendix

6.3.4 FC91 (FC process data three words)
Function for process data access
Consistent process data transfer is a prerequisite for using this function!
6.3.5 FC92 (FC process data, two words)
The function FC92 can be used for both consistent and inconsistent process data transfer.
EA_Address IN: INT I/O address of the process data channel (e.g. 1008)
Enable IN: BOOL TRUE Drive enabled
FALSE Drive inhibited
QSP IN: BOOL TRUE Quick stop (QSP) active
FALSE Quick stop (QSP) not active
Reset IN: BOOL FALSETRUE TRIP reset executed
Setpoint1 IN: INT Process setpoint (AIF-IN:W1)
ControlWord IN: WORD Control word according to DRIVECOM specification
Bit0 ... Bit4 are hidden and cannot be described.
RDY OUT: BOOL TRUE Drive is ready for operation
FALSE Drive is not ready for operation
Trip OUT: BOOL TRUE Drive signals TRIP
FALSE Drive does not signal TRIP
ActualValue1 OUT: INT Actual process value (AIF-OUT:W1)
StatusWord OUT: WORD Status word according to DRIVECOM specification
EA_Address IN: INT I/O address of the process data channel (e.g. 1008)
Bus server S7
Appendix
48 2.0 EN L

6.3.6 FC93 (FC process data, three words, CP)
Consistent process data transfer is a prerequisite for using this function!
L 2.0 EN 49
Bus server S7
Appendix

6.3.7 FC94 (FC process data, two words, CP)
The "FC94" function can be used for both consistent and inconsistent process data transfer.
Bus server S7
Appendix
Remote maintenance via modem
50 2.0 EN L

6.4 Remote maintenance via modem
Siemens, for instance, offers a teleservice-capable TS adapter for remote maintenance.
This is connected on the systems side between the MPI port of the PLC and a standard
modem. The programming unit also equipped with a modem is now able to communicate
with the PLC via a standard telephone line.
Instead of using the programming device to carry out the remote maintenance, you can
also use the bus server installed at a PC equipped with a modem.
In addition to the TS adapter for the PLC, the following software components are required
for the PC to carry out remote maintenance via a modem:
> Siemens TeleService
> Siemens STEP7
@ Note!
The connection with the remote maintenance system must always be
established manually.
The bus server may only be started after the connection has been established,
otherwise communication is not possible.
Modem connection
TS adapter
MPI
PLC
PROFIBUS-DP
L 2.0 EN 51
Bus server S7
Appendix
S7-400 example project

6.5 S7-400 example project
The "LenzeDriveServer" example project described in this chapter can be found in the sub-
directory "\S7" of the DriveServer installation.
6.5.1 Hardware configuration
> An S7-400 station is used as PLC.
> CPU 412-2 DP and power supply PS 407 10A are configured in a RACK 400.
> A PROFIBUS-DP subnetwork with master system No. 1 and a baud rate of 1.5 Mbit/s is
available.
> A Lenze fieldbus module of type 2131 is used as DP slave. This fieldbus module can be
used for 8200 and 9300 drive controllers.
PROFIBUS address: "9" (hexadecimal)
Start address of parameter channel: "1000"
Start address of process data channel: "1008"
Communication with 8 bytes of consistent parameter data and two process data
words (configuration "PAR(8ByteKons.)+PZD(2words)")
The following illustrations shows the hardware configuration in the Hardware Manager:
Tip!
The slot table of the Hardware Manager lists the settings of the parameter channel
(slot 0) and process data channel (slot 1).
The data in the columns I address and O address are required in the PLC program
for calling the "FC92" function:
6.5.2 Program blocks used
The project folder Blocks contains the following program blocks:
Slot I-address O-address
Block Function
OB1 Organisation block (program cycle); is used to call "FC4"
FC4 Function 4; is used to call all other blocks
FB90 Function block "FB DRIVE", enables parameter access via OPC and from the PLC
FC90 "FC parameter" function for parameter data jobs from the PLC
FC91/FC92 Function for DP process data (3 words/2 words)
Bus server S7
Appendix
52 2.0 EN L

6.5.3 Symbolic variable names
Symbolic names are used in the LenzeDriveServer" example project. These names are
saved in the symbol table.
> Input parameters:
> Output parameters:
DB80 "DB OPC" data block for data exchange between OPC and "FB90"
DB81 "DB S7PAR" data block for data exchange between "FC90" and "FB90"
DB100 Instance data block for "FB90" (DP-Slave1)
SFC14/SFC15 System modules for communication via PROFIBUS-DP
UDT90 Universal data type for parameter data access to Lenze drive controllers
VAT10 Variable table for changing the example parameters
Block Function
Icon Address Data type Comment
Enable M10.0 BOOL TRUE = Enable drive
QSP M10.1 BOOL TRUE = Set quick stop
Reset M10.2 BOOL TRUE = Reset TRIP in the drive
TriggerRead M10.6 BOOL TRUE = Start reading a parameter
TriggerWrite M10.7 BOOL TRUE = Start writing a parameter
Code MW202 WORD Lenze code number of the parameter
Subcode MB201 BYTE Lenze subcode number of the parameter
WriteValue MD204 DINT Value to be transmitted (FIX32)
ControlWord MW24 WORD Control word according to DRIVECOM specification
PB-Address MB200 BYTE PROFIBUS address of the drive
TimeOutTimer_OPC T1 TIMER Timer for monitoring the drive
DB-OPC-Server DB80 DB80 Data block for parameter data jobs via OPC
S7-Parameter DB81 DB81 Data block for parameter data jobs from the PLC
Icon Address Data type Comment
RDY M30.0 BOOL TRUE = Drive is ready for operation
Trip M30.1 BOOL TRUE = TRIP set in the drive
BUSY MB150 BYTE TRUE = Parameter data jobs are still being processed
ActualValue1 MW32 INT Actual process value
Setpoint1 MW20 INT Process setpoint
ReadValue MD224 DINT Read value (FIX32)
StatusWord MW36 WORD Status word according to DRIVECOM specification
WriteStatus MB210 BYTE Status of the function FC90 (FC Parameter) when writing
a parameter
ReadStatus MB220 BYTE Status of the function FC90 (FC Parameter) when reading
a parameter
WriteResult MD214 DINT Error code displayed when writing a parameter was not
successful
Value MD228 DINT Contains parameter W_Value within the read routine,
can be ignored when reading a parameter.
L 2.0 EN 53
Bus server S7
Appendix

We recommend the use of symbolic variable names for clarity. However, they are not
compulsory.
6.5.4 OB1/FC4
In "OB1" only the "FC4" function is called in which all other blocks are called.
6.5.5 Process data transmission
FC4, network 1
The following call is used to transmit two process data words (2PZD).
> Process data word 1 is always the DRIVECOM control word.
> Process data word 2 can be freely selected.
> The start address for the process data channel can be obtained from the hardware
configuration. (here: "1008")
> The Enable, QSP and Reset inputs are connected so that the controller is enabled:
Enable = TRUE
QSP = FALSE
Reset = FALSE
> The second process data word is assigned to the setpoint input.
> Control word and status word conform to the DRIVECOM specification.
> The DRIVECOM state machine is already implemented in "FC92".
> The RDY and TRIP outputs informs about the controller state.
> ActualValue1 is the value read out.
See also: FC92 (FC process data, two words) (L 47)
FC91 (FC process data three words) (L 47)
CALL FC 92 / / FC92, 2 PZD
EA_Addr ess : =1008 / / I - addr ess, deci mal
Enabl e : =" Enabl e" / / BOOL
QSP : =" QSP" / / BOOL
Reset : ="Reset " / / BOOL
Set poi nt 1 : =" Set poi nt 1" / / I NT, deci mal
Cont r ol Wor d : =" Cont r ol Wor d" / / WORD, cont r ol wor d
RDY : =" RDY" / / OUT, BOOL
TRI P : =" TRI P" / / OUT, BOOL
Act ual Val ue1 : =" Act ual Val ue1" / / OUT, I NT
St at usWor d : =" St at usWor d" / / OUT, st at us wor d
@ Tip!
When three process data words are to be transmitted, the "FC91" block must be
used.
Bus server S7
Appendix
54 2.0 EN L

6.5.6 Control of the parameter data access
The"FB90" ("FB DRIVE") enables the parameter data access both via OPC and from the PLC.
The change-over between both protocols takes place automatically.
> For each drive (DP slave) an instance of the "FB90" must be called. Moreover, an
instance block for variable storage is required every time.
> Parameter data jobs via OPC are stored in the "DB OPC".
> Parameter data jobs from the PLC are stored in the "DB S7PAR".
FC4, network 2
> The StatusWord serves to check if the corresponding controller is switched on at all
(StatusWord <> 0). If not, the call of "FB90" is skipped.
> In the example the "FB90" uses the instance data block "DB100" for variable storage.
> The Tag input is enabled.
> The PROFIBUS device address and the start address of the parameter channel are
indicated as shown above.
> In the example, both parameter data blocks ("DB80", "DB81") are used.
> The output byte Busy provides information about the communication status.
See also: FB90 (FB DRIVE) (L 44)
L " St at usWor d" / / di sconnect ed
L 0 / / cont r ol l er
==I / / ar e
SPB NEXT / / ski pped.
CALL FB 90 , DB100
Tag : = / / STRI NG
PB_Addr ess : =B#16#9 / / BYTE, B#16#x
EA_Addr ess : =1000 / / E addr ess deci mal
Dr i veSer ver _DB : =" DB- OPC ser ver " / / DBx; z. B. DB80
Dr i vePar _DB : =" S7 par amet er " / / DBx; z. B. DB81
Ti mer Nr : =" Ti meOut Ti mer _OPC" / / TI MER
Ti meOut : =S5T#1S / / TI ME
Busy : =" BUSY" / / OUT, BYTE
NEXT: NOP 0
L 2.0 EN 55
Bus server S7
Appendix

6.5.7 Reading a parameter
FC4, network 3
> The TriggerRead variable is always set to TRUE.
> After a completely processed parameter read request, TriggerRead is automatically
reset to FALSE.
> When "FC90" is called and R_W = TRUE, a read request for a drive parameter is
transmitted.
> The data is exchanged with the "FB DRIVE" ("FB90") via the "S7 parameter" data block
("DB81").
> Input parameters are the request number, PROFIBUS address, write/read request and
the code and subcode to be read.
> Output parameters are the read value and the status byte.
> When a write request for a drive parameter is to be transmitted, the R_W parameter
must be set to FALSE.
See also: FC90 (FC parameter) (L 45)
UN " Tr i gger Read"
= " Tr i gger Read"
CALL FC 90 / / dat a t ypes
Dr i vePar _DB : =" S7 par amet er " / / DB81
Count : =0 / / deci mal : 0- 31
PB_Addr ess : =" PB addr ess" / / B#16#9
R_W : =TRUE / / FALSE or TRUE
Code : =" Code" / / W#16#C, code 12
SubCode : =" Subcode" / / B#16#0, subcode 0
W_Val ue : =" Val ue" / / DI NT or L#xxx
St at us : =" ReadSt at us" / / OUT, BYTE, st at us byt e
R_Val ue : =" ReadVal ue" / / OUT, DI NT, val ue
Tr i gger : =" Tr i gger Read" / / I NOUT, BOOL
Bus server S7
Appendix
56 2.0 EN L

6.5.8 Writing a parameter
FC4, network 4
> The TriggerWrite variable is always set to TRUE.
> After a completely processed parameter write request, TriggerWrite is automatically
reset to FALSE.
> When "FC90" is called and R_W = FALSE, a write request for a drive parameter is
transmitted.
> The data is exchanged with the "FB DRIVE" ("FB90") via the "S7 parameter" data block
("DB81").
> Input parameters are the request number, PROFIBUS address, write/read request, code
and subcode and the actual value.
> Output parameters are the read value and the status byte.
> When a read request for a drive parameter is to be transmitted, the R_W parameter
must be set to TRUE.
UN " Tr i gger Wr i t e"
= " Tr i gger Wr i t e"
CALL FC 90 / / dat a t ypes
Dr i vePar _DB : =" S7 par amet er " / / DB81
Count : =1 / / deci mal : 0- 31
PB_Addr ess : =" PB addr ess" / / B#16#9
R_W: =FALSE / / FALSE or TRUE
Code : =" Code" / / W#16#C, code 12
SubCode : =" Subcode" / / B#16#0, subcode 0
W_Val ue : =" Wr i t eVal ue" / / DI NT or L#xxx
St at us : =" Wr i t eSt at us" / / OUT, BYTE, st at us byt e
R_Val ue : =" Wr i t eResul t " / / OUT, DI NT, val ue
Tr i gger : =" Tr i gger Wr i t e" / / I NOUT, BOOL
L 2.0 EN 57
Bus server S7
Appendix
Example project S7-300 with PROFIBUS-CP

6.6 Example project S7-300 with PROFIBUS-CP
The "LenzeDriveServer" example project described in this chapter can be found in the
subdirectory "\S7" of the DriveServer installation.
6.6.1 Hardware configuration
> An S7-300 station is used as PLC.
> CPU 315-2 DP, CP 342-5 and power supply PS 307 10A are configured in a RACK 300.
> There is a PROFIBUS-DP subnetwork with master system number "1" (connected to the
CPU) and another with the number "180" (connected to the CP). The controllers are
connected to the second master system.
> Lenze fieldbus modules of type 2133 and 2131 are used as DP slave. These fieldbus
modules can be used for 8200 and 9300 drive controllers.
PROFIBUS addresses: "4" and "5" (hexadecimal)
Communication with 8 bytes of consistent parameter data and four process data
words (configuration "PAR(cons.)+PZD(4words)")
The following illustrations shows the hardware configuration in the Hardware Manager:
6.6.2 Program blocks used
The project folder Blocks contains the following program blocks:
Block Function
OB1 Organisation block (program cycle); is used to call "FC1"
FC1 Siemens FC block "DP_SEND"
FC2 Siemens FC block "DP_RECV"
FC3 Function 3; is used to call all other blocks
FB91 Function block "FB DRIVE CP", enables parameter access via OPC and from the PLC
FC90 "FC parameter" function for parameter data jobs from the PLC
FC93/FC94 Function for DP process data (3 words/2 words)
DB80 "DB OPC" data block for data exchange between OPC and "FB90"
DB81 "DB S7PAR" data block for data exchange between "FC90" and "FB90"
DB30/31 Data blocks for data exchange between CPU and external communication processor (based
on "UDT93")
DB90/100 Instance data blocks for "FB91"
SFC57/SFC58 System modules for communication via PROFIBUS-DP
Bus server S7
Appendix
58 2.0 EN L

6.6.3 Symbolic variable names
The symbolic variable names used are the same as in the "S7-400" example project
described before. Symbolic variable names (L 52)
We recommend the use of symbolic variable names for clarity. However, they are not
compulsory.
6.6.4 OB1/FC3
First, the "FC3" function is called in "OB1" in which all further Lenze blocks are called.
Furthermore the Siemens "DP_SEND" or "DP_RECV" FC blocks are called which are required
for the data exchange with the communication processor.
The CPLADDR parameter requires the I/O address of the PROFIBUS-CP, which is listed in the
slot table of the Hardware Manager:
> Ensure that the address is given in a decimal format (here: "256"), but the functions
"FC1" and "FC2" require hexadecimal entries (here: "100").
As a further parameter a data block must be specified, which is used for the data exchange
between communication processor and CPU.
> In the example, "DB30" is used for transmission and "DB31" for reception. in the data
blocks 16 bytes are reserved for one controller each when using "UDT93" (4 process
data words).
> The number of controllers must be entered in the parameter RECV (in the example:
"15").
UDT90 - UDT93 Universal data types for parameter data access to Lenze controllers
VAT4 Variables table for changing the example parameters
Block Function
CALL FC 1
CPLADDR : =W#16#100
SEND : =P#DB30. DBX 0. 0 WORD 15
DONE : =M1. 0
ERROR : =M1. 1
STATUS : =MW2
CALL FC 2
CPLADDR : =W#16#100
RECV : =P#DB31. DBX 0. 0 WORD 15
NDR : =M1. 2
ERROR : =M1. 3
STATUS : =MW3
DPSTATUS : =MB12
Slot I-address O-address
L 2.0 EN 59
Bus server S7
Appendix

6.6.5 Process data transmission
FC3, network 1
The following call is used to transmit two process data words (2PZD).
> Process data word 1 is always the DRIVECOM control word.
> Process data word 2 can be freely selected.
> The FirstDriveDW parameter defines the byte position of the first data word of the
controllers connected.
> For each controller, 8 data words are reserved in the data blocks "DriveSend_DB" or
"DriveRecv_DB". The first 4 data words are required for parameter access and the
following 4 data words for process data accesses.
> The controllers must have successive I/O addresses.
> The Enable, QSP and Reset inputs are connected so that the controller is enabled:
Enable = TRUE
QSP = FALSE
Reset = FALSE
> The second process data word is assigned to the setpoint input.
> Control word and status word conform to the DRIVECOM specification.
> The DRIVECOM state machine is already implemented in "FC94".
@ Note!
Due to the maximum block size of 240 bytes, maximally 15 controllers can be
addressed with one block. This maximum number depends on the number of
process data words used.
If more than 15 devices are to be supported, further data blocks must be created
for the data exchange and the functions "FC1" and "FC2" must be called cyclically
for these blocks.
For more information on the blocks "FC1" and "FC2" please see the Siemens
STEP7 documentation.
CALL FC 94
Fi r st Dr i veDW : =8
Dr i veSend_DB : =" Dr i veSend_DB"
Dr i veRecv_DB : =" Dr i veRecv_DB"
Enabl e : =" Enabl e"
QSP : =" QSP"
Reset : =" Reset "
Set poi nt 1 : =" Set poi nt 1"
Cont r ol Wor d : =" Cont r ol Wor d"
RDY : =" RDY"
TRI P : =" TRI P"
Act ual Val ue1 : =" Act ual Val ue1"
St at usWor d : =" St at usWor d"
Bus server S7
Appendix
60 2.0 EN L

> The RDY and TRIP outputs informs about the controller state.
> ActualValue1 is the value read out.
Tip!
When three process data words are to be transmitted, the "FC93" block must be
used.
See also: FC94 (FC process data, two words, CP) (L 49)
FC93 (FC process data, three words, CP) (L 48)
6.6.6 Control of the parameter data access
The"FB91" ("FB DRIVE CP") enables the parameter data access both via OPC and from the
PLC. The change-over between both protocols takes place automatically. Thus, the block
operates fully equivalent to the "FB90".
> For each drive (DP slave) an instance of the "FB91" must be called. Moreover, an
instance block for variable storage is required every time.
> Parameter data jobs via OPC are stored in the "DB OPC".
> Parameter data jobs from the PLC are stored in the "DB S7PAR".
FC3, network 2
> The StatusWord serves to check if the corresponding controller is switched on at all
(StatusWord <> 0). If not, the call of "FB91" is skipped.
> In the example the "FB91" uses the instance data block "DB100" for variable storage.
> The Tag input is enabled.
> The PROFIBUS node address and the data blocks for the data exchange with the
communication processor and the byte offset are displayed as shown.
L " St at usWor d"
L 0
==I
SPB NEXT
CALL FB 91 , DB100
Tag : =
Fi r st Dr i veDW : =0
Dr i veSend_DB : =" Dr i veSend_DB"
Dr i veRecv_DB : =" Dr i veRecv_DB"
Dr i veSer ver _DB : =" DB- OPC- Ser ver "
Dr i vePar _DB : =" S7 par amet er "
Ti mer Nr : =" Ti meOut Ti mer _OPC"
Ti meOut : =S5T#1S
Busy : =" BUSY"
NEXT: NOP 0
L 2.0 EN 61
Bus server S7
Appendix

> In the example the data blocks "DB80" ("DB-OPC server" ) and "DB81" ("S7 parameter")
are used for "DB OPC" and "DB S7PAR".
> The output byte Busy provides information about the communication status.
See also: FB91 (FB DRIVE CP) (L 44)
6.6.7 Reading/writing a parameter
The functions for reading and writing a parameter are called regardless whether the device
connected to the PROFIBUS of the CPU or an external communication processor. In both
cases the "FC90" function is used.
Reading a parameter (L 55)
Writing a parameter (L 56)
Bus server S7
Appendix
S7 configurator - settings
62 2.0 EN L

6.7 S7 configurator - settings
When you select a configuration entry in the tree view of the S7 configurator, a tab is
displayed in the right window area on which the parameters of the corresponding
configuration entry can be changed.
6.7.1 'Common settings' tab
The Common settings tab is displayed if the topmost configuration entry "S7" has been
selected from the tree view/list view.
Scan for
control
systems
connected
Tip!
The parameters relevant for the PLC configuration depend on the protocol
selected. PLC parameters (L 20)
For the protocols "MPI Simatic", "PROFIBUS-DP" and "COMx MPI", the PLCs connected can
be automatically detected via the Scan button. Automatic PLC detection (L 17)
If the Scan at the servers start control field is activated, the PLC and the drives configured
in the PLC program are detected during every start of the bus server.
> This option is useful, if the bus server is connected to a portable PC which is operated
at different systems.
> If several CPUs are connected to the bus:
Only one CPU slot number is considered for the scan during the start of the bus
server.
If the CPU cards are plugged on different slot positions, this option is not useful since
not all PLCs can be found.
For the protocols "SOFTNET TCP/H1" and "TCP direct" and alternatively to the scan function
you can also add the PLCs connected manually to the configuration. Manual addition of
PLCs (L 19)
Button Function
Add new S7 PLC Click this button to add an S7 PLC to the configuration.
A dialog box is shown in which the name of the PLC to be added is defined. After
confirming with OK the S7 PLC tab is displayed.
The name for the PLC must not already be assigned for another PLC, and the name
must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) { } [ ] @ , < > ! % &
| = # .
Parameters Meaning
Slot number Enter the number of the slot on which the CPU card is plugged into this input field.
The slot position of the CPU card depends on the PLC type and the power supply
used for the PLC.
Protocol Select the protocol to be used from this list field.
If the interface module used supports several protocols and if the Siemens
communication drivers are installed on the PC, it is recommended to select that
protocol which uses the Siemens communication drivers.
L 2.0 EN 63
Bus server S7
Appendix

Create LOG
file
When the Create LOG file control field is activated, the S7 bus server logs selectable events
in a LOG file.
Further
settings
6.7.2 'S7 PLC' tab
The S7 PLC tab is displayed if the configuration entry is selected from the tree view/list view
for a PLC.
Parameters Meaning
Path name for LOG file Path name of the LOG file to be created.
Click the Browse button to select a LOG file already available.
Maximum size (KB) Maximum size of the LOG file.
Shorted size (KB) If the LOG file exceeds the value entered in Maximum size, so many entries, starting
with oldest one, are deleted until the size of the LOG file has been reduced to the
value entered in Reduced size.
Temporary buffer size (KB) Size of the memory in RAM, which is used for the temporary storage of LOG data if
writing into the LOG file is not possible. When this temporary storage is full, the
oldest entries will be overwritten.
Saved actions Selection of events which are to be logged in the LOG file.
Select the event to be logged with one mouse click.
A selected entry is shown in inverse video.
Click again if you want to deactivate the selection again.
Parameters Meaning
Comment (Optional) entry of a comment on the configuration entry.
The entered comment is stored in the configuration file and is only visible in the
S7 configurator.
Button Function
Add Click this button to add a PLC to the configuration.
A dialog box is shown in which the name of the PLC to be added is defined. After
confirming with OK the S7 PLC tab is displayed for the PLC added.
The name for the PLC must not already be assigned for another PLC, and the name
| = # .
Rename Click this button to rename the PLC selected.
After this, enter the new name into the dialog box New name and confirm this
entry with OK.
Delete Click this button to delete the PLC selected.
A query appears if you really want to delete the configuration entry. By clicking
the No button, you can abort the function.
Bus server S7
Appendix
64 2.0 EN L

Search for
Lenze
devices
If the PLC is connected to the PC and the PLC program has already been transferred to the
PLC, the drives configured in the PLC program can be automatically detected via the Scan
button if this had not yet been done by the automatic detection of the PLC. Automatic
drive detection (L 21)
Further
settings
Add buffer Click this button to add a block to the selected PLC.
A block serves to create OPC items which enable the access to any blocks in the
PLC (e.g. data blocks, timers, counters, inputs, outputs, etc.).
A dialog box is shown in which the name of the block to be added is defined. After
confirming with OK the configuration entry is added to the PLC selected.
The name for the block must already be assigned for another block, and the name
| = # .
If you select the configuration entry added, the Block tab is shown in which the
parameters of the block can be changed.
Add Device Click this button to manually add a device to the selected PLC.
A dialog box is shown in which the name of the device to be added is defined.
After confirming with OK the configuration entry is added to the PLC selected.
The name for the device must not already be assigned for another device, and the
name must not contain any special characters as e.g.: / * - + : ; \ " ' ( ) { } [ ] @ , < >
! % & | = # .
If you select the configuration entry added, the Device tab is shown in which the
parameters of the device can be changed.
@ Note!
The parameters relevant for the PLC configuration depend on the protocol
selected. PLC parameters (L 20)
Button Function
Parameter/option Meaning/function
Max. number of found
devices
For time reasons, especially when searching for connected devices during the server
start, the highest drive address to be checked can be entered.
If the value "0" is set, all drive addresses are searched (standard).
Scan at the servers start If this control field is activated, the drives configured in the PLC program of the
corresponding PLC are detected during every start of the bus server.
This option is useful, if the bus server is connected to a portable PC which is
operated at different systems.
If the bus server is operated at only one system, this option should be deactivated
to speed up starting the bus server.
Parameters Meaning
S7 configurator.
L 2.0 EN 65
Bus server S7
Appendix

6.7.3 'Device' tab
The Device tab is displayed if the configuration entry is selected from the tree view/list
view for a device.
Button Function
Add Click this button to add a device to the configuration.
After confirming with OK the S7 PLC tab is displayed for the device added.
! % & | = # .
The new device is assigned to the PLC which has also been assigned to the device
selected before.
Rename Click this button to rename the selected device.
entry with OK.
Delete Click this button to delete the selected device.
Add item Click this button to manually add an item to the device selected.
A dialog box is shown in which the name of the item to be added is defined. After
confirming with OK the configuration entry is added to the device selected.
The name for the item must not already be assigned for another item, and the
! % & | = # .
If you select the configuration added, the Item tab (for device) is shown in which
the parameters of the item can be changed.
Add buffer Click this button to add a block to the PLC which is superordinated to the device.
A block serves to create OPC items which enable the access to any blocks in the
PLC (e.g. data blocks, timers, counters, inputs, outputs, etc.).
confirming with OK the configuration entry is added to the PLC selected.
| = # .
If you select the configuration entry added, the Block tab is shown in which the
parameters of the block can be changed.
Parameters Meaning
DP address of the device Profibus address of the selected device.
Time-out Time in [s], which the bus server is maximally waiting for the processing of a
parameter job.
During a parameter set transfer, many jobs are transmitted at the same time so
that, depending on the cycle time of the CPU, waiting times of up to 20 - 30 s may
arise for some jobs.
In case of problems during the parameter set transfer, always try a higher time-
out setting first.
S7 configurator.
Bus server S7
Appendix
66 2.0 EN L

6.7.4 'Block' tab
The Block tab is displayed if the configuration entry is selected from the tree view/list view
for a block.
Tip!
A block serves to create OPC items which enable the access to any blocks in the PLC
(e.g. data blocks, timers, counters, inputs, outputs, etc.).
Button Function
Add Click this button to add a block to the configuration.
confirming with OK the S7 PLC tab is displayed for the block added.
| = # .
The new block is assigned to the PLC which has also been assigned to the block
selected before.
Delete Click this button to delete the block selected.
Rename Click this button to rename the block selected.
entry with OK.
Add item Click this button to manually add an item to the block selected.
confirming with OK the configuration entry is added to the block selected.
! % & | = # .
If you select the configuration added, the Item tab (for block) is shown in which
the parameters of the item can be changed.
Add device Click this button to add a device to the PLC which is subordinated to the block.
After confirming with OK the configuration entry is added to the PLC.
! % & | = # .
If you select the configuration entry added, the Device tab is shown in which the
parameters of the device can be changed.
Parameters Meaning
Type of the block Selection of the block type (data block, timer, counter, inputs, outputs, etc.).
Number of the DB If the Data block entry is selected in the list field Block type, the number of the data
block can be defined in this input field.
L 2.0 EN 67
Bus server S7
Appendix

Static config. If the Static configuration control field is activated and if several write requests are
available in a transaction at the same time, these are not executed successively but in one
step. Thus, all parameters involved are written at the same time.
> If the Static writing control field is activated in addition, the total block will be written
over.
Further
settings
6.7.5 'Item' tab (for device)
The Item tab is displayed if the configuration entry is selected from the tree view/list view
for an item.
Bit mask When the Masking in bits is activated, a mask can be defined within the range for the
incoming data (4 bytes).
Parameters Meaning
Size Size of the static configuration in bytes.
Start offset Offset (in bytes) for the start of the static configuration.
Parameters Meaning
S7 configurator.
Button Function
Add Click this button to add an item to the configuration.
confirming with OK the S7 PLC tab is displayed for the item added.
! % & | = # .
The new item is assigned to the device which has also been assigned to the item
selected before.
Delete Click this button to delete the selected item.
Rename Click this button to rename the item selected.
entry with OK.
Parameters Meaning
Source Source (parameter, input process data, output process data) for the selected item.
Target data type Target data type (characters, byte, short, etc.) for the selected item.
Code Code number of the selected item.
Subcode When the Extended addressing control field is activated, you can specify a subcode
number in addition.
Parameters Meaning
Start bit Starting position of the mask within the 4-byte area.
Number Size of the mask, all following bits have the value "0".
Bus server S7
Appendix
68 2.0 EN L

Example:
Scaling When the Scaling control field is activated, scaling is executed with the value of the
selected item according to the following formula: Scaled value = k * X + q
Limits When the Limits control field is activated, the lower and upper limit for the selected item
can be specified in the Limits from/to input fields.
Further
settings
6.7.6 'Item' tab (for block)
The Item tab is displayed if the configuration entry is selected from the tree view/list view
for an item.
Tip!
The items assigned to a device serve to access the drive parameters, whereas items
assigned to a block access any blocks in the PLC (e.g. data blocks, timers, counters,
inputs, outputs, etc.).
1 0 1 ... 1 0 1 1 0 1 0 1 0 1 0 1 0 1 ... ...
0 0 0 ... 1 1 0 1 0 1 ... 0 0 0 0 0 0 0 0 0 0
Count/Anzahl
From/Startbit
Incoming data
Masked data Count/Anzahl
MSB
MSB
LSB
LSB
MSB = Most Significant Bit (bit 31), LSB = Least Significant Bit (bit 0)
Parameters Meaning
K "k" constant for scaling.
q "q" constant for scaling
Scaled output type During scaling, the data type can also be changed. Here, the data type of the scaled
value is determined by the following three parameters:
Real (decimal value) or int (integer)
Number of bits (1, 8, 16, 32, 64)
Signed/unsigned
Parameters Meaning
Limits from/to Lower limit/upper limit
Writing a value which is outside these limits, is not possible.
If the read value of an item is outside the limits defined, the OPC quality of which
gets the "bad" status.
Only read When this control field is activated, the value of the item selected can be read only.
Analog When this control field is activated, the item selected is treated as an analog or
discrete item.
S7 configurator.
L 2.0 EN 69
Bus server S7
Appendix

Scaling When the Scaling control field is activated, scaling is executed with the value of the
selected item according to the following formula: Scaled value = k * X + q
Limits When the Limits control field is activated, the lower and upper limit for the selected item
can be specified in the Limits from/to input fields.
Further
settings
Button Function
Add Click this button to add an item to the configuration.
confirming with OK the S7 PLC tab is displayed for the item added.
! % & | = # .
The new item is assigned to the block which has also been assigned to the item
selected before.
Delete Click this button to delete the selected item.
Rename Click this button to rename the item selected.
entry with OK.
Parameters Meaning
Byte Position of the first byte in the block.
Bit position Bit position in the block in case of an item of bit type.
Length Maximum number of characters in case of an item of STRING type
With a length = 100, max. 99 characters can be displayed.
Item type Item data type (bit, word, float, string, etc.).
Parameters Meaning
K "k" constant for scaling.
q "q" constant for scaling
Scaled output type During scaling, the data type can also be changed. Here, the data type of the scaled
value is determined by the following three parameters:
Real (decimal value) or int (integer)
Number of bits (1, 8, 16, 32, 64)
Signed/unsigned
Parameters Meaning
Limits from/to Lower limit/upper limit
Writing a value which is outside these limits, is not possible.
If the read value of an item is outside the limits defined, the OPC quality of which
gets the "bad" status.
Only read When this control field is activated, the value of the item selected can be read only.
Analog When this control field is activated, the item selected is treated as an analog or
discrete item.
S7 configurator.
Bus server S7
Appendix
FAQ - Frequently asked questions
70 2.0 EN L

6.8 FAQ - Frequently asked questions
Question Answer
Which baud rate is to be set for the MPI interface module
in the PG/PC control?
Dependent on the interface module and PLC.
(Standard: 187.5 kbit/s)
Is it possible to change the block numbers of the Lenze
blocks if they have already been assigned in the current
STEP7 project?
Yes
Can the bus server S7 only work with the block numbers
known to it?
No, the bus server S7 also works with modified block
numbers.
Can the bus server S7 also find drives, if the PLC is in STOP
mode?
Yes, but the PLC must have been in RUN mode at least
once before.
Can the DriveServer also find drives and parameters if
the PLC is in STOP mode?
No, to find drives and parameters, the PLC must be in
RUN mode.
Which Siemens software is required for the operation of
the S7 bus server?
This depends on the prevailing case of operation. In the
most cases, no special Siemens software is required.
Supported protocols (L 9)
How can I find out if the Siemens communication drivers
are installed on the PC?
When the Siemens communication drivers are installed,
the configuration program "Set PG/PC interface" is
located in the system control.
How can I find out which version of the Siemens
communication drivers is installed on the PC?
Open the "Set PG/PC interface" configuration program in
the system control.
In the title bar of the program the version is displayed.
If the corresponding information is not displayed, it
can be detected by searching in the Windows system
directory for the "S7EPATDX.CPL" file and looking at
the version properties.
How do I install the Siemens communication drivers? The Siemens communication drivers are included in the
Siemens STEP7 basic package and are automatically
installed during the installation of STEP7.
Which operating system should be used? We recommend to use Windows NT, Windows 2000 or
Windows XP.
With the same hardware, the program execution
times are much shorter under Windows NT/2000/XP
than under Windows 98/Me.
When several computers are interconnected, it is not
possible to start OPC servers automatically through a
DCOM connection with Windows 98/Me.
Which protocol/driver do I have to select? For some PC modules (e.g. PC adapters) it is possible to
select which driver is to be used.
If available, the Siemens communication driver shall
always be used.
Is it possible to work simultaneously with STEP7 and the
DriveServer/Global Drive Control?
Yes, in case of parallel operation, the Siemens
communication driver must always be used.
Since communication with the S7 is, however, very
often comparatively slow, the baud rate of the two
applications might be reduced depending on the
amount of data to be transmitted.
Can you see in the PLC program if the drive controller is
switched on?
Yes, a request can be executed via the status words of
the "FC91", "FC92", "FC93" or "FC94" blocks.
If the status word of these blocks indicates "0", the
controller is switched off (or not available) and the
corresponding "FB DRIVE" instance must be skipped.
Control of the parameter data access (L 54)
A prerequisite for this kind of monitoring is the
additional use of the process data channel.
In addition, the drive controllers should use an
external 24V supply.
L 2.0 EN 71
Bus server S7
Appendix
FAQ - Frequently asked questions

Should the drive controllers use an external instead of an
internal 24V supply?
Yes, absolutely, otherwise PROFIBUS will slow down if
devices are missing. In addition, this allows you to detect
easily in the PLC program if drive controllers are switched
on.
Why does the "Cant make directory..." error message
appear when the "Ldslib.arj" library or the "Ldsexmpl.arj"
example project are opened in the DOS window with the
"arj.exe" program that is used as standard by STEP7?
The "arj.exe" DOS program can only open archives up to
a certain directory depth which can be exceeded if STEP7
is installed in a subdirectory (e.g. "c:\Programs\...")
instead of the root directory of the hard disk (e.g. "c:\...").
In this case open the ZIP archives "Ldslib.zip"/
"Ldsexmpl.zip" with the "pkzip25.exe" program
provided with STEP7 instead of the ARJ archives
"Ldslib.arj"/"Ldsexmpl.arj"
The archiving program to be used is configured in the
SIMATIC manger via the command ExtrasSettings.
Question Answer
Bus server S7
Index
72 2.0 EN L

7 Index
A
Access via OPC 33
Application notes 7
Automatic PLC detection 17
B
Baud rate 20
C
COMxMPI 10
Conventions used 6
Copyright 2
Copyright information 2
CPU slot number 20
D
DB OPC 26, 28
DB S7PAR 26, 28
Device description files 29
DP address of the device 22
DriveServer name area 38
E
E-mail to Lenze 73
Ethernet 8
Expert mode 39
F
FB DRIVE 26, 28, 44
FB DRIVE CP 28, 44
FC parameter 28
FC process data 28
Feedback to Lenze 73
Files provided 28
I
IBHLink 10
Imprint 2
Installation 13
Interface module 8
J
JOb list DB number 20
L
Layout of the safety information 7
Liability 2
M
Manual addition of PLCs 19
Max. MPI address 20
Mounting rack number 20
MPI 8
MPI interface 31
MPI Simatic 10
P
PC-MPI address 20
PG/PC interface 15
PLC cycle 41
PLC hardware 12
PROFIBUS 8
PROFIBUS interface 31
PROFIBUS-DP 10
Program flow 27
Protocols 9
R
RAM requirements 12
Response time 20
Routing function 23
S
S7 configurator 16
Safety information 7
Scan at the servers start 18
Scan during server start 21
Scan function 17
Single master 20
SOFTNET TCP/H1 11
STEP7 blocks 26
STEP7 library 28
Subnetwork ID 20
T
TCP direct 11
Time-out 22
Trademarks 2
Transmission times 42
U
User interface 8
L 73
These Instructions were created to the best of our knowledge
and belief to give you the best possible support for handling
our product.

EMF2180IB-EMF2181IB Remote Maintenance v2-0 en

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

EMF2180IB-EMF2181IB Remote Maintenance v2-0 en

Enviado por

Direitos autorais:

Formatos disponíveis

EDSFEW

Preface and general information

Reference to another documentation

Tip! Useful tip for easy handling

Tip! Useful tip for easy handling

Você também pode gostar